Develop Bugs

Step by step update instructions please.

Hi. Thoroughly confused on how to update my phone since this Google signature nonsense started in May.
I have TWRP 3.1.0-0RC2 installed.
Running May 2017 build for Verizon NHG47L.
Super User 2.79 SR3.
Can someone please give a detailed set of instructions on how to properly update my phone to the current build.
Thanks.

defens23 said:
Hi. Thoroughly confused on how to update my phone since this Google signature nonsense started in May.
I have TWRP 3.1.0-0RC2 installed.
Running May 2017 build for Verizon NHG47L.
Super User 2.79 SR3.
Can someone please give a detailed set of instructions on how to properly update my phone to the current build.
Thanks.
Click to expand...
Click to collapse
You only needed the boot sig file for the May bootloader. It hasn't been necessary for the June or July bootloaders so the instructions should be the same as you already know but simpler because you don't need to flash the boot sig file at all.

https://forum.xda-developers.com/pixel-xl/how-to/guide-updates-unlocked-bootloader-root-t3530088
this, I think, is what you want

y2grae said:
https://forum.xda-developers.com/pixel-xl/how-to/guide-updates-unlocked-bootloader-root-t3530088
this, I think, is what you want
Click to expand...
Click to collapse
Yes. That's what I was looking for. For some reason I lost TWRP and couldn't get it to stick. So I was just using the ADB sideload method. Now, for whatever reason, TWRP is back on my phone so I'd like to try to use TWRP to sideload the OTA. I've never done that before.
Thanks.

defens23 said:
Yes. That's what I was looking for. For some reason I lost TWRP and couldn't get it to stick. So I was just using the ADB sideload method. Now, for whatever reason, TWRP is back on my phone so I'd like to try to use TWRP to sideload the OTA. I've never done that before.
Thanks.
Click to expand...
Click to collapse
order i did was
*fastboot boot twrp.img (i lost on last install)
flash twrp proper
reboot to recovery
flash ota
flash elemental 14 (i was on 12...!)
flash magisk
flash twrp again
boot into system
profit

If you are rooted and unlocked can you accept the update notification?

I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!

wonderrx said:
I haven't been offered it yet, but I know it's coming so wanted to ask, trying to stay on the official channel.
If you accept the update will I lose root and have to re-root?
I'm out of practice since the Nexus 6P tether worked out of the box.
Thanks in advance!
Click to expand...
Click to collapse
The OTA probably won't work because when you root with Magisk you flash a modified boot image. Process would be as follows before taking the OTA.
Flash stock boot image from the Image Version you are currently on (i.e. Flash the October Boot Image)
Reboot
Take OTA
Re-root using Magisk using the November Boot image to patch
add tethering line to build.prop or get the Magisk Module
Profit
You would need to repeat this for each monthly update to keep root.

I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips

Cowbell_Guy said:
I had always thought this was the best way to install OTAs. Someone correct me if I'm wrong?
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Click to expand...
Click to collapse
Normally yes but I'm not sure if the partition structure is identical on the new Pixels but you could always try @topjohnwu 's method and report back.

I didn't think you could do an OTA with an unlocked bootloader, is that true? If so, topjohnwu's method wouldn't work anyway.

New 8.1 OTA with only Magisk

Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks

freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
Worst things that could happen are: OTA fails to install or you have to reinstall Magisk through fastbooting/T
WRP, so just try it.
I just flash full factory image and flash TWRP, Flash Kernel, and Magisk again, instead of waiting for OTA to be available through the phone.

freemandjango said:
Hello, my pixel 2 xl only has Magisk installed with Root and is on stock December 5th 8.1 update. I was wondering if the instructions of the official 'seamless OTA' installation would work with this January update (instructions here https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md). Basically, the instruction allows users to install OTA by disabling Magisk and re-installing it while the OTA is being applied.
I'm quite afraid to try it and was wondering if anyone can confirm.
Thanks
Click to expand...
Click to collapse
To be safe i would use the flash-all for December update. It will take to back to stock kernel and remove magisk. Then take the January ota. I think that is a sure way and doesn't take to many step.

Better to do flash all bat of January Factory Image, and reflashing magisk after that,
You can edit the flashing script, removing -w to prevent it wiping your data

I've tried it twice to no avail. I was able to go back to magisk and reinstall. I haven't lost anything. Ymmv...

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!

Is there an easy way to update an unlocked/rooted Pixel 3a XL?

I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom

Tom2112 said:
I unlocked my bootloader and rooted my Pixel 3a XL as soon as I got it. But I've been unable to install the OTA and security updates since (September 2019). I've been digging around in the forum trying to figure out how to load the updates. I was really hoping Flashfire would work, but it gives me errors - something about the root not being available or right... but my root works for everything else I've tried (maybe its an issue with Magisk)...
Anyway, I was hoping to find a simple way to install the updates. Help!
Thanks in advance,
Tom
Click to expand...
Click to collapse
I have seen postings about people fastboot flashing back the original boot.img, then taking the ota then repatching the new boot image and flashing it via fastboot. Not as simple as you hoped i am sure but it works.
The other way is to download the full image, remove the -w option in the flashsall.bat and then run the modded flashall file. You then need to patch the new boot image as above and fastboot flash that to regain root. I have not found any other ways to get updates besides doing one of the 2 above every month

Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.

Tom2112 said:
Thanks, adm1jtg! I appreciate the help.
Unfortunately, I tried the second method you mentioned on my own... but I missed the part about removing the -w from the flashall.bat. Faaaaaaaaaaaqqqqqqqq!!! And ended up wiping my phone.
But now I think I'll remember that -w trick! I love learning things the hard way. LOL
I'm still going to hold out hope that someone will come along and make an app like FlashFire to script the process for us.
Click to expand...
Click to collapse
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Sideloading the ota would be a great option EXCEPT he said he was on a much older version... Like sept.
My understanding is that the ota for dec would only contain changes implemented for the month of December, this in this scenerio he would not get the patches for October and November with your method and i am not even sure if it would boot after that mismatch
It's really not saving much work if any over flashing the full version, and with the full version they're is no potential for bootloop due to missing some patches or updates. It's just much safer.

thatsupnow said:
Why wouldn't you just side load the OTA and be done with it?? Easy instructions where you'll download the OTA image. Easier than what your currently doing
Click to expand...
Click to collapse
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?

Tom2112 said:
Um... prolly because I'm dumb... and maybe a little because I couldn't find instructions on how to do it properly. I don't suppose you happen to have a link to how to do the OTA sideload thing properly?
Click to expand...
Click to collapse
https://developers.google.com/android/ota

The most simple way to update while keeping root would be to follow the instructions for "Devices with A/B Partitions" at the following link in the Magisk documentation:
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation
Basically, Magisk allows you to restore the original boot image to the current partition so you can take the OTA when it arrives on your phone. Before rebooting you install Magisk to the inactive slot so that when the phone restarts you retain root without having to mess with Fastboot.

Delete Me!
Think all you have to do is click uninstall magisk, dont reboot... Take ota, but before reboot click install magisk/ install to empty slot...
Oops didnt see the reply above

OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?

Tom2112 said:
OK, so when this month's security update came out, I tried to following the Magisk instructions (uninstall Magisk, restore stock boot, flash OTA, etc...) but when I went to uninstall Magisk and restore the stock boot, it tells me there is no stock boot image to restore! Dammit. Now what?
Click to expand...
Click to collapse
This should be a one time issue. One of the latest versions of Magisk changed the default location of the boot.img backup. They released it in December after most of us had already upgraded to the December Pixel update. This means we used the older version of Magisk when we installed the Dec update and it saved the backup to the old/original location. We then updated Magisk sometime later in December, but the Magisk update doesn't move the backup file to the new location (a poor execution from the Magisk team IMHO). Because we are now on the updated version, it expects the boot.img backup to be in the new location, but it is still in the old location and Magisk doesn't check that old location (again, a poor execution from the Magisk team IMHO).
To fix this you have several options.....
Option one is to find the original backup location that Magisk used for the boot.img and move it to the new backup location that Magisk uses. Unfortunately, I don't know where those backup locations are and didn't feel like researching it, so I used one of the other methods.
Option two is to "reinstall" Magisk (choose the patch file option and select the stock boot.img that may still on the phone from whatever the last update was (if you sideloaded the update and then had to rerooted the phone)- or download it from the applicable factory image and move it to the phone) to force Magisk to backup the current boot.img file to the new location. Stop after this initial step (ie you don't actually need to flash the patched file because it has already been done). Then you should be able to follow the normal Magisk update process to move to the January update.
That being said, I have horrible success being able to take the updates OTA (they usually fail) and usually end up sideloading the update. That is the final option - sideload the Jan update and then reroot the phone using the normal root method (ie getting Magisk to patch the stock boot.img file and then flashing the patched file).