hi Guys!
I just wanted to share my work with you.
I created a working TWRP recovery for the Pixel on Android O developer preview 4, that can boot and decrypt the /data partition. I don't own a Pixel XL, so I can't test, but @Chainfire did a few quick tests and it seems to be working on his Pixel XL too. So I would say you can try and see if it works for you. Please keep in mind, that I didn't test it, and neither Chainfire, or myself or anyone else can be blamed if it doesn't work, or damages your phone (shouldn't actually, but who knows..).
If you are still not scared enough, please follow this link to the Pixel forums and check out my work:
https://forum.xda-developers.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
Good luck!
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
sahilarora2003 said:
When I try to flash it via fastboot it says file is not signed. What am I doing wrong here? I wanted to be rooted and I am on Android op4 preview. Please guide me how to root. Thank you everyone.
Click to expand...
Click to collapse
Its in the instructions but here is the command and you shouldn't flash it but instead fastboot it.
fastboot boot trwp.img
flash the latest supersu 2.82 sr1
NVM. Mission accomplished. Thank you for help.
feimummy said:
I test it on my pixel xl， working well.
Thank you very much.
But it seems to not be able to flash supersu
Click to expand...
Click to collapse
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
SR2 flash fine
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
You can try SR2 flash fine.
gubacsek said:
To root, you don't even need recovery. Use @Chainfire's boot-to-root.img (fastboot boot it), and it will do the job for you. Easiest way to root...
And don't forget to thank him!
Click to expand...
Click to collapse
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
feimummy said:
Thank you for your answer.
Thank Chainfire.
But my phone Pixel XL is at home now,I will try it later.
Is it this one?
https://download.chainfire.eu/1011/CF-Root1/root-marlin-pixelxl.zip
Click to expand...
Click to collapse
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
gubacsek said:
Yes, that should be it!
Although Chainfire has released a new version in zip format, with a lot of pixel (XL) related fixes. You can also try to flash that one using my modded TWRP.
Click to expand...
Click to collapse
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
——————————The final outcome——————————
I have solved the problem with this SuperSU version:
https://forum.xda-developers.com/showpost.php?p=72686197&postcount=10481
Thanks a lot.
feimummy said:
I have used your modded TWRP to flash SuperSU zip,but there was nothing happened after rebooting the phone.
And I also try "fastboot boot boot-to-root.img" just now,there was still nothing happened...
View attachment 4236828
I mean,it was so strange that SuperSU can not be flashed into my Pixel XL with these two methods.
Click to expand...
Click to collapse
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
gubacsek said:
Try to flash the original boot.img first.
1. reboot to bootloader
2. fastboot flash boot.img from the factory image zip
3. fastboot boot recovery.img
4. in the recovery, flash supersu
Or you can skip points 3 and 4, and fastboot boot boot-to-root.img
Click to expand...
Click to collapse
Sr2 flash fine!
caballon said:
Sr2 flash fine!
Click to expand...
Click to collapse
Great! Nice to see that everything is working I had this itching, you know, when something is not as it should be, because I wanted to have Android O, but there was no recovery to do what I want... Now this feeling is gone, and I'm relaxed again
The only thing missing is a flashable zip. Is my current "itch"
Very nice. I booted into TWRP with no issue. I had already used boot-to-root so I did not have to flash SR2 in TWRP but nice knowing we have it working for the XL.
Thank you for making this sir.
Work like a charm in Final Android O!!! Thanks man.
caballon said:
Work like a charm in Final Android O!!! Thanks man.
Click to expand...
Click to collapse
Same here!
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
liam_davenport said:
People have successfully rooted O Final? I used the img but I can't flash zips or access any folders they all have weird names is that due to Encryption?
Click to expand...
Click to collapse
Had this already sometimes on 7.1.2 with twrp rc 1 and 2. Must be an encryption error. Only way for me to use the phone again was to start all over with flashing factory image with flash-all.bat.
liam_davenport said:
People have successfully rooted O Final?
Click to expand...
Click to collapse
Reboot until you get prompted for your PIN in recovery, then flash SuperSU v2.82 SR3 from here.
Related
https://dl.twrp.me/angler/
So flash, much excite, such new. Wow.
Edit - I know I sound weird but I don't like dirty flashes. I always reboot into bootloader, fastboot erase recovery and then fastboot flash recovery twrp.img ( I rename it twrp.img for short) then boot into it. I have done this for years on BL unlocked devices and never had a problem flashing twrp. It's just ME, but I think it is fun typing the stuff, and it assures me that I have a clean state and am not dirty flashing anything! Also, on others phones I use RASHR instead of flashify. Once again, personal preference but have had better luck.
XDA Thread updated
And backs up with finger print
^ That's great news.
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
synnyster said:
I tried flashed this but after trying to reboot into recovery got the broken android icon. Reflashed back to older version and it worked. Not sure if I had a corrupt come. Do you have to reboot the bootloader after flashing from fastboot for it to take? I just rebooted to system after flashing.
Click to expand...
Click to collapse
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
I flashed via fastboot after I updated to the newest android February security patch.
synnyster said:
I flashed via fastboot after I updated to the newest android February security patch.
Click to expand...
Click to collapse
Okay you're on stock?
Gytole said:
Just out of curiosity, did you use flashify? I know two other people that it borked the flash also. I recommend rashr. But I also flash via otg cable and usb drive. I'd say you most likely had a bork download. Delete the img, run trimmer, redownload it. And flash via rashr and reboot and respond if it fixed it. Good luck!
Click to expand...
Click to collapse
Gytole said:
Okay you're on stock?
Click to expand...
Click to collapse
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
synnyster said:
Stock systemless root. Used Heisenberg's guide step 10 to update. Saw TWRP 3.0 so decided to try that.
Click to expand...
Click to collapse
Fastboot erase recovery, then reflash twrp recovery, boot into recovery and reflash systemless root.
No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM...
You gotta:
"Download the latest TWRP image file (.img) from the download link and boot TWRP. Go to install and find and select the Images... button. Browse to the image that you downloaded and select it. Choose recovery and swipe to flash."
OP's method seems like the best bet though...
Sent from my Nexus 6P using Tapatalk
"No problem dirty flashing here, but the process is a little different than it was on my previous phone where you would just flash it like a ROM..."
That's cause you're use to flashing zips people make flashable, i'm old school and use img's hahaha "LET'S MAKE FLASHING FUN!" Shutup Gytole...
Just out of curiosity has anyone tried flashing twrp as boot? I also have a thread in the tmobile G3 section and I almost wonder if thats why they bork their phone...lol
Just did it on my girlfriends G3 through twrp and was like, "they totally flashed it as boot...."
Used twrp manager from Google store was simple and easy
ROADKING17 said:
Used twrp manager from Google store was simple and easy
Click to expand...
Click to collapse
Way to deviate from the norm! Haha
Gytole said:
Way to deviate from the norm! Haha
Click to expand...
Click to collapse
Takes all kinds...
Sent from my Nexus 6P using Tapatalk
No need for this thread, as there is a TWRP thread in the development forum.
Thread closed.
http://www.pocketables.com/2016/08/official-android-nougat-released.html
Pulled directly from my device and uploaded to my AFH site.
https://drive.google.com/open?id=0B0OpOqUNqeKkb19UbGxBV2NPc28
Stock, decrypted boot image, w. Verity disabled.
What version of android where you coming from?
spunks3 said:
What version of android where you coming from?
Click to expand...
Click to collapse
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
digitalhigh said:
I had the MM version installed. However, this has system.transfer.list and vendor.transfer.list - meaning - it *should* be the FULL ROM.
Click to expand...
Click to collapse
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Deadlights said:
So we should be good to wipe all in twrp, flash the update zip, then seperately flash the boot.img and maybe supersu?
Click to expand...
Click to collapse
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
What steps did you follow to get TWRP and root ?
So how is OTA different from full image?
digitalhigh said:
All of the above worked for me!!
Also, Magisk Manager confirmed and working with PHH Root for AndroidPay+root.
Click to expand...
Click to collapse
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
MRL3GS said:
What steps did you follow to get TWRP and root ?
Click to expand...
Click to collapse
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Deadlights said:
Nice! Thanks man :good:.. I guess it'll handle vendor for us?
Click to expand...
Click to collapse
Yep, /vendor is included, as well as updates to bootloader, etc.
kolyan said:
So how is OTA different from full image?
Click to expand...
Click to collapse
It does not encrypt if you were not previously encrypted, this is the biggest difference
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
When i try to setup pay I get "android pay cant be used" :S
MRL3GS said:
When i try to setup pay I get "android pay cant be used" :S
Click to expand...
Click to collapse
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
digitalhigh said:
Ahaha! Sorry. Magisk requires you have Magisk manager installed, and then you use the manager to disable root when you want to use Pay. My bad.
http://forum.xda-developers.com/devdb/project/dl/?id=19924&task=get
Click to expand...
Click to collapse
Thanks all working now
digitalhigh said:
It should go something like this:
1. Flash OTA. I used TWRP.
2. Reboot to bootloader. Reflash TWRP. Flash unlocked boot image.
3. Fastboot format cache and fastboot format userdata if coming from an ROM that was encrypted.
4. Reboot to TWRP.
5. Flash magisk, phh superSU.
6. Reboot.
7. ????
8. PROFIT.
It is one and the same. It is the OTA image I received by enrolling my 6.0.1 device in the beta, and downloaded.
Click to expand...
Click to collapse
Working great for me! Thanks again man!
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Worked for me Thank you!!!! Still kept super su and twrp!!!
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
hutzdani said:
Working great thanks !
Just to confirm for others :
1. Flash ROM don't reboot system !
2. Flash TWRP don't reboot system !
3. Flash the modified boot image, now reboot system !
4. Let it boot fully and make any app updates
5. Reboot into recovery
6. Flash SU
7. Wipe caches
8. Reboot and away you go !
I came from the latest MM security update and dirty flashed so be warned mileage may vary !
Click to expand...
Click to collapse
Flash the TWRP image file from TWRP? And what is the modified boot image?
Sent from my Nexus 6P using Tapatalk
Batfink33 said:
Is anyone getting E:unknown command for patching system and vendor when flashing
Is that normal
Click to expand...
Click to collapse
Me everything works fine tho just i cant get root to wrk the app keeps freezing on me can't grant root?
Sent from my Nexus 6P using Tapatalk
This thread was originally for Pixel-specific rooting instructions, but by now the SuperSU ZIP and TWRP are fully supported:
- Fastboot boot TWRP
- Install latest SuperSU ZIP (v2.79-SR3 at the time of writing)
Note that at this time I recommend against fastboot flashing TWRP. With the Pixel's new partition layout, the recovery files are inside the boot partition, and so is SuperSU. If you flash both, SuperSU's internal boot image backup will not be of the original boot image, but of TWRP. This means that neither the 'full unroot' option in SuperSU, nor incremental OTA update through FlashFire, will work as expected.
OR
- Use CF-Auto-Root for Pixel (not released at the time of writing, but should be released soon)
Nice work!
Hell Yeah!!! Thanks @Chainfire, your time as well as others that have made this and the bootloader unlock happen is appreciated very much.
Sent from my Pixel XL using Tapatalk
can we flash another kernel such as elementalX on top of this?
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
How does this relate?
Ker~Man said:
How does this relate?
Click to expand...
Click to collapse
because I attempted to not really thinking about that its systemless and wasnt sure if root would persist. after attempting to flash boot elementalX's kernel my device just powered off so i immediately reflashed root and all is okay now
diabl0w said:
can we flash another kernel such as elementalX on top of this?
Click to expand...
Click to collapse
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
I did read the readme.. so not sure what your getting at
cwalker0906 said:
Lol if you read chainfires instructions you would have e your answer,but it short no, not until they add it
Click to expand...
Click to collapse
chainfire said:
- If you want to use a custom kernel, simply 'fastboot boot' the root image again after flashing the custom kernel. This has been tested with a few custom kernels and found to work well so far.
Click to expand...
Click to collapse
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
lexcyn said:
It was a valid question since this flashing method is different than what we are used to due to the difference in partitions and the file system.
Click to expand...
Click to collapse
okay thanks, so i guess the answer is actually yes
Thanks @Chainfire - booted and working well!
thanks..emoji..root explorer.. viper.. naptime.. titanium.. yes..
if new kernel must boot boot to root again..
Seems I cannot remount /system_root as rw (to copy Emoji font over).
marlin://system_root/system/fonts # mount -o remount,rw /system_root
mount: '/dev/block/bootdevice/by-name/system_a'->'/system_root': Device or resource busy
Edit: Nevermind, used Solid Explorer and granted it SuperUser and seemed to work. Strange.
Does anyone have the stock boot.img for the pixel xl? I don't have the data to download the full factory image.
Life is good!
Thanks to all involved, especially Chainfire.
You Rock!
Worked like a charm. Thanks @Chainfire!
Can't thank you enough. Works perfectly.
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
spunks3 said:
can someonone please post the exact steps they are using?
I just unlocked my bootloader. then tried flashing the root-boot img file, it did the reboots, but when i complete android setup, theres no SuperSU and if i install the .apk, it still does not detect root...
just reflashed stock boot.img, locked and unlocked bootloader. waiting for instrustion.
thanks!
Click to expand...
Click to collapse
fastboot boot boot-to-root.img
lexcyn said:
fastboot boot boot-to-root.img
Click to expand...
Click to collapse
what about superSU?
Tools needed: boot.img extractor. I recommend the one created by osm0sis from this thread:
https://forum.xda-developers.com/sho....php?t=2073775
The first method was developed by osm0sis and removes magisk and all modules.
1. Unpack magisk_patched.img
2. Unzip overlay.dremove1.zip and place overlay.d folder in ramdisk folder.
3. Repack IMG
4. fastboot boot image-new.img created by repacking 8mg
This method is an offshoot of osm0sis version but boots core-only mode. Afterwards, remove the .disable-magisk file from the /cache folder for modules to work. Dot files are hidden files so if your root explorer can't see hidden files, run the "Remove disable_magisk" bat file in ADB.
1. Same as above but use the overlay.dcoreonly1.zip
For both methods you must be rooted for it to work. These are not cure all's for all bootloops.
Remove .disable_magisk bat file
https://www.androidfilehost.com/?fid=4349826312261684994
****************************************
Here is a fastboot bootable image to boot you into Magisk core-only mode in case you bootloop due to flashing a bad module and TWRP is not enough.
Once in fastboot:
fastboot boot image-newpixel3.img
You will boot with root but modules disabled. After you remove the offending module you will need to go to /cache folder and delete the .disable_magisk file before your modules will work.
fastboot boot image-newpixel3Remove.img
This one should remove magisk and all modules, then reboot and magisk should reinstall itself (ask to install necessary binaries). This is what osm0sis uses to recover from failed flashes. See this post:
https://forum.xda-developers.com/pi...odules-disabler-booting-magisk-t3976625/page2
Images are in this common folder. Pick the appropriate image for your phone.
6-4-20
https://www.androidfilehost.com/?w=files&flid=313291
Amazing! Thanks
I can confirm this worked on Android 10/Q. I can't use the canary patch method for magisk because I forgot to remove the modules before upgrading to Android 10. This method works like a charm, it removed the incompatible modules allowed me to by pass the bootloop.
Thank you so much for sharing!
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
wao20 said:
For those who are wondering, these are the steps:
adb reboot bootloader
fastboot flash boot image-new.img
fastboot reboot
Done!
Click to expand...
Click to collapse
Second step should be:
fastboot boot image-new.img
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Alxoom33 said:
Any idea if this works on the Pixel 2 and 2XL?
Sent from my Pixel C using Tapatalk
Click to expand...
Click to collapse
No, but you have TWRP. You don't need it.
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Click to expand...
Click to collapse
Only since the update to android 10
Alxoom33 said:
P3 doesn't have TWRP? Wow!!! I knew I didn't like that phone.
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Tulsadiver said:
I just came across a time when I couldn't even boot TWRP on my Pixel 2. Here is a boot with root, core-mode Magisk image for Pixel 2 XL.
https://www.androidfilehost.com/?fid=1899786940962594367
Click to expand...
Click to collapse
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Alxoom33 said:
Yeah, I remember those days. Thanks for the image. Can it be flashed in TWRP or strictly adb/fastboot?
Sent from my Pixel 2 XL using Tapatalk
Click to expand...
Click to collapse
I've only used fastboot.
Tulsadiver said:
Here is a fastboot bootable image to boot you into Magisk core-only mode. If you bootloop due to flashing a bad module, in fastboot:
fastboot boot image-new.img
You will boot with root but modules disabled.
Tested by me and @123SIT whom contributed on the project.
Made from Pixel 3 XL but should work on the Pixel 3 also.
Image
https://mega.nz/#!NE5yGaBA!0HLSWvdD4x4cOmo35HrDGrGNxTAUGW4LpkpVv1ygwVI
Thanks to @ApeironTsuka for his guide and everyone on the Magisk support thread like @jcmm11 for their patience and help.
Click to expand...
Click to collapse
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
sliding_billy said:
Here is a link to it on my GDrive. Can you please let me know when you've got it so I can delete it?
https://drive.google.com/file/d/1rg5wENhILz8ah8jSdLne2OtaLYGOhdBI/view?usp=sharing
Click to expand...
Click to collapse
got it! thanks this time too!
FcukBloat said:
got it! thanks this time too!
Click to expand...
Click to collapse
No problem. It's good to be a pack rat. I hope it worked.
FcukBloat said:
can't reach the mega link, can you guys please upload it somewhere else please? I am stuck on bootloop as I 'm typing...
Click to expand...
Click to collapse
Mega link seems to be working. Open with chrome, not mega app.
Edit: I've added a AFH download link.
i tried with chromium based browser (vivaldi) from both phone and pc and link didn't work, probably it was a WiFi problem, thanks for adding alternative link though. and your core mode image worked like a charme! and thanks again also to sliding billy for initial mirror support
Just what I needed. Thank you
How did you create it? I want to make sure I have one of these images on hand in the future when I need to fix things
Simply works, thank you!
Holy cow, thanks man. I can't believe @topjohnwu let this slide through. Without TWRP wtf are you supposed to do, reflash the whole OTA/factory image?!
EDIT: Wait, now I can boot and apparently have root but I can't access any of my rooted apps. It says "waiting for root". Magisk Manager gives me an "app not installed" error but it is installed on the device. When I click it it says "upgrade to full Magisk Manager" and does nothing. How am I supposed to delete the module folder?
EDIT: Can't access terminal, can't do anything. Permission denied via ADB as well.
EDIT: DO NOT DELETE MAGISK MANAGER OR ALTER IT IN ANY WAY WHEN USING CORE MODE. You will be stuck like me. I had to nuke my phone and reflash everything. PIA
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
T4gB0t said:
Hi everybody,
I'm trying to root my OnePlus 7t Pro with android 11 installed, but I can't figure out a way how to do so...
I read some other posts/threads and tried to root it installing Magisk canary but it still didn't work (it got stuck in the booting process, and I had to flash the stock boot image to get it working again). Does anybody have an other idea of something I could try? Magisk doesn't same to get it patched regardless of which version I use...
Thank you in advance for your help!
Click to expand...
Click to collapse
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Hw4ng3r said:
You said it got stuck in booting process, was this after a fastboot flash patchedboot.img?
Click to expand...
Click to collapse
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
T4gB0t said:
Yes, exactly... Sorry for not specifing. I patched the image, flashed it and than my phone stopped booting correctly and I had to flash the stock image to make it work again. I searched a little bit and found out that it was Magisk's fault and read that I had to try with the canary version, so I did but it still did not work and I was stuck on the same point as before.
Click to expand...
Click to collapse
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Hw4ng3r said:
Have you tried just fastboot boot patched.img and doing a direct install through Magisk?
I know some people reported their phones borking after trying to fastboot flash.
Click to expand...
Click to collapse
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
T4gB0t said:
Sorry, I'm not really sure if I understood what you meant....
I thought that maybe I could try to downgrade to android 11 to then root and upgrade while remaining root. What do you think about this idea? And do you know how I could downgrade my phone? I did some research but did not find anything useful...
Click to expand...
Click to collapse
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Hw4ng3r said:
So you would take your stock Android 11 boot.img and patch it like you would in Magisk Manager. Save the patched.img to your computer. Reboot to bootloader and apply command fastboot boot patched.img. this should restart your phone using the patched.img. once it starts, go into Magisk Manager and click Install > Direct Install > Reboot when asked.
You could certainly go back to A10 from A11 but you will lose all your data. The method above does work. Where did you get the stock boot.img?
Click to expand...
Click to collapse
I downloaded the software from the official website and used payload dumper to extract the boot image. To be sure that I understood everything... you suggested to use "fastboot boot patched.img" instead of "fastboot flash boot patched.img", and once the phone restarted to go to magisk manager and click direct install.
Do I need Magisk Manager canary or the normal version for this to work and do I have to mantain the canary version or can I install the normal version once it is rooted?
Either 22.1 or Canary works for A11
Hw4ng3r said:
Either 22.1 or Canary works for A11
Click to expand...
Click to collapse
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
T4gB0t said:
Okay thank you very much, I'll try and tell you. Thank you for your awesome help
Click to expand...
Click to collapse
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
T4gB0t said:
One last question, is it normal that the "unlocked bootlader message" when booting shows up for almost two minutes? When I had Android 10 it did not take that much...
Click to expand...
Click to collapse
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Hw4ng3r said:
Yes for some reason, I noticed that as well on my device.
FYI, the patched boot may only work with Magisk canary
Click to expand...
Click to collapse
So not Magisk v.23 but Magisk canary?
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Hw4ng3r said:
I know that there was rooting issues back at the end of last year, but I'm not sure exactly what version of Magisk it was at the time.
If you want to pass safety net on A11, I've read success posts with canary and Magisk hide
Click to expand...
Click to collapse
Okay thanks, I'll try with v.23 first and If that does not work than I'll try with the canary one. Thank you very much!!!
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Wacko1805 said:
Hiya, just use this TRWP. Decryption works on Android 11 (only tested on lineage).
Reboot to fastboot and use
fastboot flash recovery_a recovery.img
And
fastboot flash recovery_b recovery.img
And reboot to recovery.
Releases · Systemad/android_device_oneplus_hotdog
TWRP tree for OnePlus 7T/Pro (Hotdog/hotdogb). Contribute to Systemad/android_device_oneplus_hotdog development by creating an account on GitHub.
github.com
Click to expand...
Click to collapse
Okay thank you, I'll try if the other method does not work
T4gB0t said:
Okay thank you, I'll try if the other method does not work
Click to expand...
Click to collapse
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Hw4ng3r said:
Decrypt does not work on OOS and you do not need TWRP to Magisk.
Click to expand...
Click to collapse
I'm sorry to bother you again, but I tried with "fastboot boot patched.img" and it still did not work. It got stuck while booting again with "unable to parse kernel log" as error message. Do you have any other suggestions?
P.S. I got a full backup with "adb backup -apk -all -shared -f /path/to/location" today and thought about just doing a factory reset, trying to root the phone, restore the backup. Do you think that might actually work? Thank you for your help!
How exactly did you patched your boot.img?
FSadino said:
How exactly did you patched your boot.img?
Click to expand...
Click to collapse
I tried doing it with magisk (both v.23 and canary)