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!

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.

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).

Android 10 root/twrp

Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?

More details will be needed to help. Bootloader unlocked? Guessing yes since you say you had twrp. Check the guide section for root instructions.

Yes I have it unlocked. I looked at the guide and it looks like I will have to reflash the stock rom which I'd like to avoid.

Kreuger said:
Hey guys. I accidentally (don't ask) installed the update for Android 10 from 9 stock and lost my twrp and root. Is there any way to at least get root back without having to reinstall everything?
Click to expand...
Click to collapse
Since, twrp is not available yet for Android 10 (Q), I suggest one of the three following options:
1. If you have to re-flash the Pixel 3 XL Android 10 (Q) Factory image, do #4 'keep data' in this Guide.
2. If your Pixel 3XL has the latest Android 10 (Q) Factory image installed, just do #9 A. in this Guide to root.
3. If you are on a Custom ROM follow the OP Instructions in the Custom ROM thread to root.

Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?

Kreuger said:
Apparently I have the Sept update (QP1A.19711.020.C3) but I currently have no available updates. Am I good to just use your step 2?
Click to expand...
Click to collapse
Yes!
Why not do #1 update your Pixel 3 XL to the February Factory image (QQ1A.200205.002). You will not lose your data (need to reinstall anything). Then do #2 to root.

I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.

Kreuger said:
Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Some people are reporting that issue. You can set the custom channel to canary/canary debug manually. Check the magisk thread.

Thank you. I tried to find it on the github site and found nothing.

Kreuger said:
Thank you. I tried to find it on the github site and found nothing.
Click to expand...
Click to collapse
It is under the magisk files repo.

Kreuger said:
I guess I can do it that way. Thanks.
Edit: Do I need to use a custom kernel? I don't really require one. Also in magisk manager, theres no way to select the canary channel. All I see is stable, beta and custom.
Click to expand...
Click to collapse
Kernel/Kernel Managers are optional. #10 B ,in the guide, updated.

Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.

Kreuger said:
Hey so I patched the image and flashed the file, I'm stuck on the screen with the google logo and progress bar. Also, does it matter that I used adb reboot fastboot to get to the fastboot menu? I noticed it said fastbootd which ive never seen before. It seemed easier to do it that way.
Edit: Ive decided to try flashing another rom.
Click to expand...
Click to collapse
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.

wangdaning said:
For flashing boot.img you should reboot bootloader. Fastboot is a separate thing now for system files to be flashed. Boot, bootloader, and radio are flashed in bootloader, others in fastbootd.
Click to expand...
Click to collapse
Ah I was unaware. Thanks

Question Upgrading to Android 13 Question

Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony

tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
- Do I really need to install 13 to both slots?
- Is root / Magisk working fine on 13?
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
it would be recommended to flash at least the bootloader to both slots, root works perfectly fine

tonyfiore75 said:
Hi,
I am currently on Android 12, rooted with Magisk, and I update each month using the latest Factory Image.
If (when) I upgrade to Android 13...
- I know it's usually recommended to do a clean install when you go to a brand new build, which means wiping data. I'm okay with this ASIDE from the fact that I have GBs worth of music on my phone which takes forever to both back up and restore.
Click to expand...
Click to collapse
I haven't wiped before flashing a new version of Android on my Pixel phones in the last 5-6 years. Android 13 Stable that I manually updated using the full factory image, coming from the first Android 12 July update has worked fine for me.
Good thing, too, because I hate starting from scratch any more.
(I too have hundreds of GBs of music on my phone)
tonyfiore75 said:
- Do I really need to install 13 to both slots?
Click to expand...
Click to collapse
"Have to"? No. It would be good advice to install it to both slots, though.
tonyfiore75 said:
- Is root / Magisk working fine on 13?
Click to expand...
Click to collapse
Yes.
tonyfiore75 said:
- Any other suggestions on how to make this upgrade easier?
Thanks in advance!
Tony
Click to expand...
Click to collapse
No. Everything was just like every month's normal update process for me with flashing the full firmware zip to update, and then I flashed it again to the other slot the next day.

Thanks, everyone! I really appreciate it. I'll just flash the update as I normally would (editing the .bat file) to Slot A and then do the same to Slot B. Or can you flash it to -all slots at the same time? I know I used to do that with my Pixel 4 but that may have just been when flashing the magisk file.

tonyfiore75 said:
Or can you flash it to -all slots at the same time?
Click to expand...
Click to collapse
Yes, you can.

Cool, thanks.

Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!

jumpet said:
Sorry it's my first time with root and a custom kernel in the pixel, I have never updated it because I installed it on June, could you post a guide with the commands please?
Thanks a lot!
Click to expand...
Click to collapse
Hiya! Just click the yellow How To Guide quick filter at the top of list of threads in this section, and there are at least two or three threads for how to update. The OP of the thread in my signature below also has the commands.

roirraW edor ehT said:
Yes, you can.
Click to expand...
Click to collapse
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?

Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.

tonyfiore75 said:
If I have to flash to both slots with the factory image, do I also have to flash to both slots with the updated Magisk file as well?
Click to expand...
Click to collapse
Not really. Just do it on the slot you end up running. The slot you won't be running won't have root, but that's okay. You'll likely never actually use the other slot, and if by some rare chance you do, it's an easy thing to flash the Magisk'd stock boot.img to it at that time.

acwcanada said:
Didn't come to the forum to read messages in the past few days! I updated my P6P from A13 beta 4.1 to official using the factory image -w method as I have done it in the past 10 months. It is now running smoothly and I didn't encounter any problem so far. I start reading messages saying that A13 has to be flashed in slot A and slot B. Since I already upgrade my machine with normal method, I still able to keep my data, root and API integrity, and most import booting up normally, so do I have do it again to reflash to this Slot A/B thing? I am not so sure I understand this new requirement, so sorry if this question sounds stupid.
Click to expand...
Click to collapse
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.

I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.

rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
That's how I do it every month

roirraW edor ehT said:
I'm trying to answer on mobile, so it's tough for me because most detailed support I give I do from the computer but I can't right now.
Check out the OP and last few pages of the thread on my signature below (use desktop mode in a mobile browser if necessary) for more information about flashing to both slots.
Look at it this way. Normally you only flash the full factory image once (so only to one slot). This time you did it once already, so now you'll have to switch slots and flash it to the other slot.
You could then switch slots again and use the slot you already re-rooted. Both slots have the same exact apps and app data - the second flashed slot just won't have the rooted boot.img that you already have on the slot you're running now.
Click to expand...
Click to collapse
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?

acwcanada said:
OK, thanks so much, achieved done that. One more question, how about the future updates? Do we have to do it every month in the future when Google provide the monthly updates?
Click to expand...
Click to collapse
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.

Lughnasadh said:
No, you only needed to flash to both slots this one time just to make sure both slots were on A13.
Click to expand...
Click to collapse
Thank you for the feedback.

rhetorician said:
I think it's most simple to use the Google flash tool. You don't have to wipe anything, just unroot, run the tool, reroot. Not script editing and praying that you didn't screw anything up.
Click to expand...
Click to collapse
No need to unroot - just run the tool (making sure wipe or force flash all partitions isn't selected), and then reroot.
I like the satisfaction of getting my hands a little dirty, plus the knowledge that if something goes wrong, it's most probably my fault!
I also like to Magisk my own boot.img from the factory image, and if I'm going to download it anyway, I figure might as well flash it.