Develop Bugs

TWRP & Root

I'm so confused with this phone. Google sent me a 128gb Pixel XL which I activated on my Sprint account. I'm fairly comfortable with rooting, flashing, TWRP, SuperSU, etc., however for the life of me I cannot get TWRP to stick.
Background...
Phone came to me straight from Google, and updated to 8.0 immediately (this was in August). Since, the phone doesn't appear to have been updated as I was still on 8.0 from August I believe
Here's what I did...
Unlocked the phone, using TWRP image, boot to it via fastboot, flash the installer TWRP zip, and then issues happen.
On 3.2.1.0-0 it reboots to system (even if I go back into TWRP's main setting and Reboot Recovery). If I use 3.2.0.0-0, it gives me an ERROR 1 code. I've tried using systemless root method (with the modified TWRP img, Aroma Installer for SU, etc.). I've tried using the 2 most recent TWRP images from their website. I initially started with this guide ([GUIDE] Pixel XL Android 8(OREO) Unlock/Install Stock Images + Kernels/Recovery +). I then tried this method using Systemless root ([Guide] How to systemlessly root your Pixel XL on Android 8.0 (SuperSU)).
I even tried flashing the OTA manually, which caused other issues, mainly bootloops. I finally got the most recent 8.0 OTA to work after multiple errors (which appear to be caused by outdated platform_tools). When trying to flash the OTA, only OPR1 would flash, OPR3 would always just hang or throw errors (sorry, no changelog, which I know is not helpful). Am I not correct that OPR3 is what is needed for a Sprint (US carriers) based phone? Regardless, everything is up, and running now in 8.0, however I can't take the OTA (it fails when trying to download), and I still can't get TWRP to stick.
Is there anything obvious I'm missing? I can boot to TWRP, but can't flash it, regardless of what I do. I've searched and most issues I've found in getting TWRP to stick either has to do with flashing the boot.img from an OTA or using 3.2.1.0 instead of 3.2.2.0. Funny thing, I don't see the 3.2.2.0 img file, just the flashable zip. Someone please help me, even if it is to tell me I'm in over my head and should stick to a stock rom.

I think you should simplify your life.
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file.
That will update your phone, but leave settings a data in tact. Again, remove the -w so you don't wipe user data.
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
I do it each month this way. It takes 15 minutes and I have zero problems.

To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.

TonikJDK said:
Each month grab the full image. Edit the flash-all bat file and remove the -w you will see near the end. Reboot the phone into fastboot mode and run the flash-all bat file..
Click to expand...
Click to collapse
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
TonikJDK said:
Then boot to TWRP and root it. Skip installing TWRP, too many hassles on this phone.
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
TonikJDK said:
FYI, on the January update SuperSU no longer works, you will need to root with Magisk.
Click to expand...
Click to collapse
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?

vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
2 different methods, same result. Make sure to thoroughly follow instructions with whatever method you try and you'll be fine.

vestaviajag said:
So you're saying grab the Full OTA? Should I start with the last month before the version I'm on? Currently on OPR1.170623.023 (Nov 2017). Does it make a difference that I'm a Sprint service, as in using OPR1 vs OPR3?
Click to expand...
Click to collapse
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?[/QUOTE]
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.

TonikJDK said:
So fastboot into TWRP img everytime I want to flash a custom ROM?
January update of SuperSU or the OTA? I was under the impression Magisk couldn't be flashed on stock kernels, I'm guessing this changed?
I will try this. Between yours and Tonik's advice, one of these is bound to work, right?
Click to expand...
Click to collapse
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
https://developers.google.com/android/images
I can't help you on ROMs, I don't do them. Are there any 8 ROMs for this phone?
But I would never flash anything on this phone without being near a computer. So I skip flashing TWRP. Just as easy to fastboot it.
SU is not being updated any more. So I mean the Google January update breaks SU. I have been using Magisk on stock for several months now. If you want to stick with SU you will need to flash December Google.[/QUOTE]
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?

Chance Ill said:
I
Hmmmm.......SU not being updated anymore? I've been using magisk for awhile now so I haven't been keeping up. What's your source?
Click to expand...
Click to collapse
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....

TonikJDK said:
SU beta thread, Chainfire announced he is no longer involved at all. He stopped by a few days ago, got rather upset at some of the posts. We have not heard a word from the new owners in two years.....
Click to expand...
Click to collapse
Oh ok. I do remember coming across Chainfire's announcement awhile ago but was unaware that the new owners hadn't been active with the community. That's disappointing to say the least.

Chance Ill said:
To make your life even more simplicit, you can use Skipsoft Toolkit. Its automated and does all the heavy lifting for you. I have TWRP install without any issue.
Click to expand...
Click to collapse
Tried this, for some reason wouldn't work. Tried the TWRP and it wouldn't due to OpenSourceScript or something. Then tried rooting and installing busybox, it wouldn't do this either. It attempted to flash it to sd card, another place, and finally in the right storage for this device, and it wouldn't for some error. No specifics on the error were given.
TonikJDK said:
I use the full image, after taking out the -w from this link. Since you are flashing the whole image you can just get the latest.
Click to expand...
Click to collapse
Tried this next, removed the -w, and used flash-all in fastboot. This worked, however after I upgraded to 8.1 OPM1, I left it alone. Will try again tonight to root, and attempt flashing magisk for the first time.
Thanks for all the advice!

Couldn't install system update

I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?

ranlil said:
I am unlocked and was rooted with Magisk and the OTA OPM1.171019.013 tried to install and failed. I uninstalled Magisk thinking it might resolve the problem. It didn't. I have OPM1.171019.011 and would really like the update and reinstall Magisk to be rooted. Is there a way to get this update to install?
Click to expand...
Click to collapse
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761

I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?

kellybrf said:
I've got the same issue. it said failed a few days ago, now it just stays on step 1 of 2. read duce's thread but it's about his script, is there any way to get the ota to take?
Click to expand...
Click to collapse
Were your rooted or had custom recovery before you started?

Badger50 said:
Were your rooted or had custom recovery before you started?
Click to expand...
Click to collapse
rooted, twrp, magisk

kellybrf said:
rooted, twrp, magisk
Click to expand...
Click to collapse
Then that's why you can't take the ota. Need to be unrooted and on stock recovery for OTA's.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
https://forum.xda-developers.com/pi...ol-deuces-bootloop-recovery-flashing-t3704761
Click to expand...
Click to collapse
Thanks!! Worked as described.

Badger50 said:
Look over this thread for problems with OTA's and rooting :good:
Click to expand...
Click to collapse
I had a look over there, and it looked a bit scary. I don't want to do the critical unlock. (I still have the stock bootloader) Instead I found another way that involved patching a factory image.
My steps where:
Download the latest factory image
Checked the SHA256, then unpacked the zip
Extracted the boot.img file from the image-taimen-<version>.zip
Copied the boot.img onto my device (adb push or drag and drop)
Used Magisk to patch it. (Install button, then "patch boot image file") (NB: The patched boot image is about half the size of the original. This is normal)
Copied the patched_boot.img back to my PC, and renamed it back to boot.img
Put the patched boot.img back into the image-taimen-<version>.zip replacing the original
Once I had modified system image, I then flashed my device in the usual way using flash-all.sh (NB: You need to remove the -w switch from the last fastboot command so that it does not wipe the user data).
The end result is that my phone is updated to the latest November firmware, and I still have root with Magisk.
Next month, I will try again with an OTA, but if that does not work, then the above process should be easy and reliable.

Ota update for pixel 2 xl with magisk and twrp already installed

I am sure this has been asked and answered 100 times but for the life of me I can't find a definite answer. I have a Pixel 2 XL and it is rooted and I have Magisk and TWRP installed on it. I want to be able to install the OTA for this month, but I do not want to lose anything on the phone. I also would rather not lose Magisk or TWRP. Normally on my android phones I use ROMs and can just update through TWRP, but I want to stay on stock because I don't want to lose Active Edge. So can someone please help me by giving me step by step instructions or point me to instructions that are simple to follow so I can take the OTA?
I really appreciate the help.

I was having the same problem and was helped by some of the members here.. Best way is to flash the firmware after removing the -w from the flash all file. Then flash twrp and magisk.
Ota

Thanks for your help. I will try that.

magicmaker said:
Thanks for your help. I will try that.
Click to expand...
Click to collapse
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:

Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.

rank78 said:
Sorta related...
Are there any ROMS that come rooted so I don't have to go through the monthly process of backup/unroot/update/root/restore?
Would love to just flash a ROM update and be done.
Click to expand...
Click to collapse
Not that I'm aware of, but maybe some on the horizon...

Badger50 said:
Here's a quick little guide I made for updating monthly factory images. Hopefully it'll help you out :good:
Click to expand...
Click to collapse
Hi, quick question
I am only able to do them steps above if I have done 'fastboot unlock_critical'? I have only done 'fastboot unlock'
Also I would need to boot into TWRP and flash a kernel + magisk to retain root?

You have to issue the "fastboot unlock_critical" command in order for the bootloader to update, since the bootloader is included in both factory images and full OTAs. Speaking of full OTA's, one of our recognized developers, @elliwigy, revealed (thread here) that it is possible to flash a full OTA image through TWRP, which eliminates the need to open the factory image and remove the -w flag from the last line. Flashing the OTA works because TWRP doesn't check signatures like the stock recovery. You will lose both root and TWRP upon reboot however, so you will still need to connect to a PC in order to reinstall TWRP so you can subsequently replace the stock Kernel with the Flash Kernel and then root.
I can verify this works, as I tried it with the May update.

Root pie Dec update (v10.0.2)

I got update from oero to pie via OTA today,
I tried many patched boot.img and root maunally by patching stock img but its stuck on boot screen.. Any idea??

Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.

Hakkinan said:
Download the OTA, extract the images from the payload, flash the stock boot.img in both slots. After your phone boots you can download the latest magisk manager, use it to patch the stock boot.img that you already downloaded and use it to root your device.
Click to expand...
Click to collapse
What's mean " in both slots " ?
I tried to patch boot.img maunally but my device stuck on boot animations, So I flashed back stock boot.img into fastboot without root agian..

This is an A/B device which means that it has two slots for every partition (A and B). You need to flash the stock boot in the same partirion that it currently being used, flashing It in both is just to be safe in future updates.

Oh hey try this one: https://drive.google.com/file/d/1dBX2dZV_wWgSip8d9lk0lrO_JHfxGdKU/view?usp=sharing

Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.

FRibeiro1400 said:
Sorry if this has been asked before, but I didn't find it anywhere on this forum. I am also stuck on a bootloop after installing Pie update. I had Magisk installed and I've uninstalled it - didn't reboot. After, I've applied the Pie update. Didn't reboot. Went back to Magisk app and then did install - install to inactive slot. After that have a "nice" bootloop. How can I get the unpatched boot.img? Thanks in advance.
Click to expand...
Click to collapse
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?

FRibeiro1400 said:
Thank you so much! I am going to try it later, hopefully I can get my phone back fully working. If it's not asking too much, what are the commands I have to type to install it on both slots?
Click to expand...
Click to collapse
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"

Hakkinan said:
"fastboot flash boot_a boot.img" and "fastboot flash boot_b boot.img"
Click to expand...
Click to collapse
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?

HaN5aR said:
Stuck on boot agian..
I tried flash OTA manual by fastboot & flash patched stuck too!
I think I need reset to root?
*NOTICE: I installed Xposed framwork on oreo, May that's problem?
Click to expand...
Click to collapse
Wait, did you try to flash the whole OTA?

Hakkinan said:
Wait, did you try to flash the whole OTA?
Click to expand...
Click to collapse
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations

Hakkinan said:
Download the OTA zip that is available here, extract the boot.img and flash it in both slots. After that you can easily patch the stock image with Magisk Manager and install magisk like you would usually do (direct install).
Click to expand...
Click to collapse
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?

HaN5aR said:
At first I updated from oreo to pie via OTA without any VPN
I failed to root it so, I tried flash it again from HERE but facing the same problem with root it stuck on bootanimations
Click to expand...
Click to collapse
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
FRibeiro1400 said:
Unfortunatelly, it seems the link for the OTA zip was removed, so, phone will stay bricked thanks to the lack of instructions of how to update to Pie when Magisk is installed. Why do they remove the links?
Click to expand...
Click to collapse
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.

Hakkinan said:
Ok, now i understand what is happening. It bootloops as soon as you reboot after installing magisk right? If so, then i need to know what you are doing to install magisk.
First the server is down, nobody removed the file, you just need to wait for it to go up again. Second, you can easily revert your phone back to 10.0.1.0 and stay there, your phone isn't bricked and it doesn't have to stay in this current state.
Click to expand...
Click to collapse
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.

FRibeiro1400 said:
I never had 10.01.0 installed. I was on Oreo and got the update this morning. I've followed the rule for OTA with Magisk and it was the wrong thing to do. If, at least, there was a warning to NOT follow the instructions, all would be sorted. Maybe I can find a link somewhere with this update, as I don't want to lose my data. On Xiaomi official site, the last rom available is version V9.6.11.0.ODLMIFF. Unless I install this one back.
Click to expand...
Click to collapse
Doesn't matter if you had 10.0.1.0 previously or not. You can download it and install it without losing data.

Question Are the newer US ver still allowing,rooth with TWRP?

Seeing a lot of issues with Android 11 and 12 unlocking the bootloader and applying root. Is now not a good time to upgrade or should I wait for a boot image?

Not quite sure what you're referring to, but there are zero issues with unlocking the bootloader or rooting your device...

I can't speak for TWRP. I have had issues with it the last few versions so I had to make due without it. If I am mistaken about having twrp on the OP9 Pro on the newest LE2125 c61 update, I'd be interested.
Anyway, my response is mostly to address your question regarding root. Here are the steps that worked for me.
[OnePlus 9 Pro][ROM][OTA][Oxygen OS] Repo of Oxygen OS Builds
As OnePlus doesn't always provide download links for all of their OxygenOS ROMs & OTA update zips, we've created an index to put the links in one post so that they're easy to find. Note: This is not a support thread for issues you may have with...
forum.xda-developers.com

I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.

I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.

intense21 said:
I am coming off the oneplus 7pro was enjoying TWRP and Magisk, with Exposed now I am hearing TWRP isn't working on anything above 10.0 ver. Guess I have to do so more research or pay Monfrio a ransom to work on TWRP.
Click to expand...
Click to collapse
there is no need for TWRP...

Smedslund said:
I have been rooted since day one on both A11 & A12. I'm running stock and haven't had a single issue.
Avoid TWRP, it's known to not work properly on A12
If you like to flash a custom ROM. Follow the instructions and you will be fine.
Click to expand...
Click to collapse
How do you root without twrp? or you mean to just boot twrp and not install it?

CtrlValCanc said:
How do you root without twrp? or you mean to just boot twrp and not install it?
Click to expand...
Click to collapse
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.

Smedslund said:
Use Magisk, patch bootimg , install and reboot.
Read this usefull guide.
Click to expand...
Click to collapse
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!

CtrlValCanc said:
thank you, i couldn't find what boot.img to download (and how), but this guide has already all!
Click to expand...
Click to collapse
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.

vincemue said:
I always just sideload. (downdload magisk apk & rename to zip before)
this way you do not need the extra boot.img I think.
Click to expand...
Click to collapse
could you explain better? I never used sideload before. What commands do you use?

CtrlValCanc said:
could you explain better? I never used sideload before. What commands do you use?
Click to expand...
Click to collapse
If you want to install any add-ons, Reboot to Recovery, then when your device reboots, click Apply Update, then Apply from ADB, then adb sideload filename.zip those packages in sequence. (GAPPS or Magisk for example)
for example for magisk:
download the newest magisk apk version
after download, rename it and instead of .apk do it .zip
go into revovery and click Apply Update, then Apply from ADB
command is : "adb sideload Magisk-v2X.X.zip"
you must exchange X for your version.
Boot images gets patched
please note that I am not an expert, that is just what I found somewhere and use since then.
if you need more information you could also check the install instructions for lineageOS to get to know some basics: https://wiki.lineageos.org/devices/lemonadep/install