Database Info

[UPDATE/KEEP ROOT GUIDE] JULY 2020 (QQ3A.200705.002) "CORAL" Magisk/Stock Boot Images

[UPDATE/KEEP ROOT GUIDE] JULY 2020 (QQ3A.200705.002) "CORAL" Magisk/Stock Boot Images
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the July 2020 (QQ3A.200705.002) update.
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR JULY 2020 QQ3A.200705.002!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886725
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886726
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682886727
THESE FILES ARE FOR "10.0.0 (QQ3A.200705.002, Jul 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on July, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200605.001, Jun 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq3a.200605.001-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824137
coral-qq3a.200605.001-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261824136
July 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq3a.200705.002-f7e8f879.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq3a.200605.001-factory-boot.img
3. fastboot flash dtbo coral-qq3a.200605.001-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq3a.200705.002-f7e8f879.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq3a.200705.002-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
*Kirisakura 4.7.5 seems to work fine so far!
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)

Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than June 2020?
Download the July 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)

Thanks again for this service, i have no issues.

i5lee8bit said:
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886725
Click to expand...
Click to collapse
Just a friendly heads up - people should be individually patching their own boot images and not flashing patched boot images from other devices, as per topjohnwu himself
https://twitter.com/topjohnwu/status/1272136975022084097?s=19

wrongway213 said:
Just a friendly heads up - people should be individually patching their own boot images and not flashing patched boot images from other devices, as per topjohnwu himself
https://twitter.com/topjohnwu/status/1272136975022084097?s=19
Click to expand...
Click to collapse
Thanks for the heads up! Didn't realize this. I'll update the OP when I get to my laptop. A while back I compared hashes of someone else's prepatched boot image to one I made and they were identical so I (incorrectly) assumed it would always be fine. Thinking about it more I can definitely see MM patching slightly differently based on current config, makes sense. Thanks for the direct reference too :good::good:

Anyone having battery issues with this update?
Dropped from 100% to 50% and then 18% in like 10 mins. Restarted phone and now stuck on 50%, doesn't change charging or discharging.

Hi. So I previously used your steps to flash to the June update. Now I'm trying to flash to the July update, but every time I try to enter recovery mode, it just reboots my phone. This is the first time this has happened to me, what am I doing wrong?
Really hope my phone isn't bricked without me installing anything new

crisco654 said:
Hi. So I previously used your steps to flash to the June update. Now I'm trying to flash to the July update, but every time I try to enter recovery mode, it just reboots my phone. This is the first time this has happened to me, what am I doing wrong?
Really hope my phone isn't bricked without me installing anything new
Click to expand...
Click to collapse
Did you already flash the June stock boot and dtbo images? Recovery won't boot unless you have stock boot image (changes to the boot image by custom kernels, and I believe Magisk as well, cause Recovery mode not to work).
You need to first boot into BOOTLOADER, then flash the stock boot and dtbo images. Only then you should be able to boot to recovery.
Skimpy007 said:
Anyone having battery issues with this update?
Dropped from 100% to 50% and then 18% in like 10 mins. Restarted phone and now stuck on 50%, doesn't change charging or discharging.
Click to expand...
Click to collapse
No issues with battery on either my phone or wife's phone (4 XL and 4) on July update with Kirisakura kernel... Sorry, but it sounds like it could be a hardware problem? D:

Thank you for this useful guide OP - works a treat each time. I've been following it for the last 3 months

i5lee8bit said:
Did you already flash the June stock boot and dtbo images? Recovery won't boot unless you have stock boot image (changes to the boot image by custom kernels, and I believe Magisk as well, cause Recovery mode not to work).
You need to first boot into BOOTLOADER, then flash the stock boot and dtbo images. Only then you should be able to boot to recovery.
No issues with battery on either my phone or wife's phone (4 XL and 4) on July update with Kirisakura kernel... Sorry, but it sounds like it could be a hardware problem? D:
Click to expand...
Click to collapse
Thanks, this worked!

After flashing the July Ota and kernel my pixel was not certified, clearing Play store and Play services it is ok.
Face-unlock was also not working, after installing the full image and no extra kernel it was working(removing the -w).
This morning Face-unlock is working, but my Pixel 4 xl in Play Store is not certified, after clearing the Play store and service it is certified.
Someone else also this issue?
Jos

Skimpy007 said:
Anyone having battery issues with this update?
Dropped from 100% to 50% and then 18% in like 10 mins. Restarted phone and now stuck on 50%, doesn't change charging or discharging.
Click to expand...
Click to collapse
I've got some bad news for you.... looks like you've been hit with a hardware problem that just happened to coincide with doing this update. Take a look at this thread for some details:
https://support.google.com/pixelphone/thread/25796722?hl=en&dark=1
I'm just a few days into my second Pixel 4 XL (refurbed unfortunately) because of this issue. There is a "squeeze" trick to get the battery to operate normally, but I've yet to see it do anything but buy a little extra time.

Might be temporary or just luck.
Upgraded to 11 beta 2 was still doing it. So smacked it off my dash while driving ( pissed of course ), restarted and.... So far so good...? Lol

Is there a guide for doing this on MAC OS?

Update:
SDK Platform-Tools: r30.0.4

Thank you for this understandable step by step guide!
i5lee8bit said:
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "10.0.0 (QQ3A.200605.001, Jun 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
[ ... ]
Click to expand...
Click to collapse
Your instructions are golden.
It was the first time that I managed to update my Pixel 4 with the Android 11 beta without having to set everything up afterwards ... You saved me a weekend of work.
Once again many thanks :good:

August images out. Any chance of a premodded boot image?

elkay said:
August images out. Any chance of a premodded boot image?
Click to expand...
Click to collapse
just started the thread. editing the guide part right now
https://forum.xda-developers.com/pixel-4-xl/how-to/update-root-guide-aug-2020-qq3a-200805-t4142635
Homeboy76 said:
Update:
SDK Platform-Tools: r30.0.4
Click to expand...
Click to collapse
I haven't updated to that yet, but thanks for the heads up. I was able to update with 30.0.1 with no problems, but I'll do it now. Thanks.
kdoggy said:
Is there a guide for doing this on MAC OS?
Click to expand...
Click to collapse
I don't own a single Mac, but I'm pretty sure it's the same command line commands, except you would run them in terminal. Just make sure you have the sdk command line tools properly set up. You can download them directly from Google: https://developer.android.com/studio/releases/platform-tools
There's a version specifically for Mac OS.

i5lee8bit said:
...I haven't updated to that yet, but thanks for the heads up. I was able to update with 30.0.1 with no problems, but I'll do it now. Thanks...
Click to expand...
Click to collapse
:good:

[UPDATE/KEEP ROOT GUIDE] MAR 2021 (RQ2A.210305.006) "CORAL" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210305.006, Mar 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746586
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746583
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145746585
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.210205.004, Feb 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq1a.210205.004-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145727318
coral-rq1a.210205.004-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145727317
March 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210305.006-c7e59bf8.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq1a.210205.004-factory-boot.img
3. fastboot flash dtbo coral-rq1a.210205.004-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq2a.210305.006-c7e59bf8.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210305.006-magisk_patched-22.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!

I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.

neomasterpt said:
I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.
Click to expand...
Click to collapse
Did you try flashing the patched img to both slots?
Code:
fastboot flash boot magisk_patched.img --slot all

worked like a charm. thanks

The update itself worked with your method. However since then my phone keeps freezing after I try to unlock it. Ergo it boots up normally, I see the start screen but when I try to unlock it by writing down my pin, the phone freezes and instandly restarts. I already tried booting to safemode and disabling all magisk modules, but it seems that this did not work.

This is my method works all the time.
patched boot.img via magisk
fastboot flash bootloader<bootloader.img>
fastboot reboot bootloader
fastboot flash radio<radio.img>
fastboot reboot bootloader
fastboot --skip-reboot update<image.zip>
fastboot reboot bootloader
fastboot flash boot<patchedboot.img>
fastboot reboot

neomasterpt said:
I've tried this but it keeps rebooting into fastboot mode with "no valid slot to boot". Also tried other kernels but can only boot to the unpached boot img.
Click to expand...
Click to collapse
Did you get this sorted out?
Morgrain said:
The update itself worked with your method. However since then my phone keeps freezing after I try to unlock it. Ergo it boots up normally, I see the start screen but when I try to unlock it by writing down my pin, the phone freezes and instandly restarts. I already tried booting to safemode and disabling all magisk modules, but it seems that this did not work.
Click to expand...
Click to collapse
I would try flashing the stock boot image and see if you can get in.
Maybe can also try flashing the full factory image with the -w removed in the script file. Just run stock first (don't replace the boot.img with the Magisk patched boot) to make sure it's not Magisk related.
I hate to bring potential bad news, but I had something similar happen, twice now. Though not exactly as described. Both times I had to full wipe too... First time, I woke up to my phone being completely out of space, and while I could unlock, I would only have a few seconds (seemingly random) to use the phone before it would freeze and reboot. I thought maybe it had to do with the phone running out of space at the time.
When it happened again a few months later, my phone had plenty of space. But like last time, phone would boot up, I would unlock, and then it would run like crap until eventually forced rebooting. Trying all combinations of stock / Magisk / modified boot images, flashing full firmware (with -w removed), rolling back to previous firmware... Nothing worked and eventually it just got stuck at the G logo. Had to full wipe at that point, but luckily I had backups of my important stuff.
First time happened on Android 10, second time happened on Android 11. Weird. There's actually a thread I read a while back with people describing the same issue, and ultimately seems like only a full wipe fixed it.
Oh and one last thing - for me, while I can't prove it, both times it happened shortly after I installed the Storage Isolation / Redirect (Riru) app / module... Didn't occur to me until later that maybe that somehow messed with some permissions related to System UI that even disabling the module later wouldn't fix. I use it on my other devices without issue, but I have since never installed it back on my P4XL and no problems in months. Also both times, Magisk Manager was also acting crazy, and I couldn't flash new modules or anything. It kept saying it didn't have storage permissions, even though it did, and no amount of uninstalling / reinstalling / etc would bring it back to a working state. Again why I somewhat suspect Storage Isolation was causing some weird stuff to happen...
But since it only happened to you after updating, hopefully it's something else, and hopefully going stock can maybe get you back running. Maybe one of the partitions failed to update or something, and flashing the full image can help. Just remember to remove the "-w" flag in the batch / shell file or it'll wipe your data!!!
Edit: oh, this is probably pretty important, were you already running Magisk v22.0? Magisk Manager is completely revamped in 22.0, and I wouldn't be surprised if you would have problems if running older Magisk Manager with Magisk 22.0. If you were still on 21.x and Manager 8.x, I would flash last months firmware (-w removed, blah blah), update to Magisk 22.0, and then run the OTA... Best of luck, I hope it all works out for you!

Booted my old ssd with windows 10 just to update from feb to march.
Everything fine so far using your files no idea whats wrong with my new Windows ssd tho lol

I'm also getting the "no valid slot to boot" both with the self patched boot image and the one posted here.
Tried this command "fastboot flash boot magisk_patched.img --slot all" did not work.

Jesus1988 said:
Did you try flashing the patched img to both slots?
Code:
fastboot flash boot magisk_patched.img --slot all
Click to expand...
Click to collapse
Nope! did not work!
I can boot with Cleanstate kernel also. Just not Magisk. also tried to patch cleanstate but the patched version wont boot.

neomasterpt said:
Nope! did not work!
I can boot with Cleanstate kernel also. Just not Magisk. also tried to patch cleanstate but the patched version wont boot.
Click to expand...
Click to collapse
Were you already on Magisk 22.0 before updating?
Either way, flash this month's factory dtbo and boot images to their respective partitions. See if you can boot. Could be working the way you described because another installation patched your dtbo and it needs to be reverted.
If you were on Magisk 21.x before updating, upgrade Magisk Manager (now just Magisk.apk) to 22.0. Make sure to follow all warnings on Magisk's changelog (if Magisk Manager app package was hidden before, unhide before updating).
Flash the Magisk 22.0 patched boot image. Flash either the one in the OP or patch it yourself using Magisk (Manager) 22.0. Boot the phone. If it works, flash kernel in EX / FR KM.
Also please let me know if you were on Magisk 22.0 or 21.x before updating. I wanna know if this could cause problems as I mentioned previously.

i5lee8bit said:
Were you already on Magisk 22.0 before updating?
Either way, flash this month's factory dtbo and boot images to their respective partitions. See if you can boot. Could be working the way you described because another installation patched your dtbo and it needs to be reverted.
If you were on Magisk 21.x before updating, upgrade Magisk Manager (now just Magisk.apk) to 22.0. Make sure to follow all warnings on Magisk's changelog (if Magisk Manager app package was hidden before, unhide before updating).
Flash the Magisk 22.0 patched boot image. Flash either the one in the OP or patch it yourself using Magisk (Manager) 22.0. Boot the phone. If it works, flash kernel in EX / FR KM.
Also please let me know if you were on Magisk 22.0 or 21.x before updating. I wanna know if this could cause problems as I mentioned previously.
Click to expand...
Click to collapse
Still does not work.
And yes I was on v22.

neomasterpt said:
Still does not work.
And yes I was on v22.
Click to expand...
Click to collapse
But you can boot stock? Did you try booting in safe mode yet?
If you can't even boot to safe mode while Magisk patched boot is installed, as a last resort, and may be overkill because unfortunately I don't physically have access or know your whole setup, download the Feb 2021 full factory image. Flash it with the "-w" flag removed so you don't lose data. Install Magisk 22.0 apk, patch the stock boot file (for Feb 2021) and flash it. Hopefully it boots back to your previous state on Feb 2021 firmware before attempting upgrade.
Now we can try 2 different directions. Overkill version: open Magisk Manager and (complete) uninstall. Now take the OTA as per OP instructions and hopefully it boots now. You should be rooted but now with no modules installed.
Or, try disabling any potential modules that may be causing problems before updating again. Reboot once fully after disabling before doing upgrade. I would recommend disabling anything that targets SystemUI, as well as Ed/LS-posed. Or perhaps it could be an Xposed module itself.
Good luck.

I had to do a full wipe before getting root to work and boot. Probably due to something with Magisk updating to v.22

[UPDATE/KEEP ROOT GUIDE] APR 2021 (RQ2A.210405.005) "CORAL" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: twitter dot com /topjohnwu/status/1272136975022084097?s=19 (until I figure out how to stop new XDA from forcing the URL to embed a giant twitter posting in the middle of the post...)
ALL FILES BELOW ARE FOR "RQ2A.210405.005, Apr 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776322
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776321
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693776320
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ2A.210305.006, Mar 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
coral-rq2a.210305.006-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145746585
coral-rq2a.210305.006-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145746583
April 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq2a.210405.005-0d148a1d.zip
DO NOT BOOT BACK INTO O/S UNTIL ALL STEPS ARE COMPLETED - THIS ENSURES EVERYTHING BOOTS BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-rq2a.210305.006-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210305.006-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-rq2a.210405.005-0d148a1d.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)
This is a 100% seamless update that requires no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
-------------------------------------------------
-------------------TROUBLESHOOTING-------------------
-------------------------------------------------​
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Since Magisk v21.x, Core Only mode has been replaced by using Android's built-in Safe Mode. Booting into Safe Mode should essentially boot you back into your system but with all modules disabled (as well as Magisk Hide). Keep in mind that even after you reboot, modules will remain disabled, unless you re-enable them first. Also remember to re-enable Magisk Hide if you had it enabled before.
Please see @Didgeridoohan's guide for more details: https://www.didgeridoohan.com/magisk/MagiskModuleIssues#hn_Core_Only_Mode
It's also worth mentioning, his guide is extremely well-made and contains a lot of useful information that could benefit all Magisk users and modders. I highly recommend looking through it anyway!

@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?

niko26 said:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Maybe you should update your platform tools to the latest version: it's v31.0.0 as of February 2021. Your log says you're running 30.0.4.

Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?

DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
You'll have to re-root after each update. The method used to keep root when updating via OTA was removed from Magisk b/c it was causing problems on Pixels.

niko26 said:
@i5lee8bit - thanks, worked fine on my Pixel 4 XL. However, during the OTA process my console showed me following error message:
Code:
C:\Unified_Android_ToolKit\platform-tools_r30.0.4-windows\platform-tools> adb sideload C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip
serving: 'C:\Temp\pics\coral-ota-rq2a.210405.005-0d148a1d.zip' (~94%) adb: failed to read command: No error
The device itself showed something across the lines of exit error code 0.
Everything seems to be running ok so far. Do I have to worry about the OTA stopping to transfer at 94%?
Click to expand...
Click to collapse
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
DinarQ8 said:
Hi. This first time happens to me when I reboot the phone the Root is gone and have to flash the magisk_patched again!! Please is there any suggestion on how I keep Root after reboot?
Click to expand...
Click to collapse
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...

i5lee8bit said:
Like @Ghisy already said, definitely start with trying newest platform tools. I've had that error come up before but experienced no problems.. weird thing is it happened to my wife's Pixel 4, but not my Pixel 4 XL when I did the updates right after another. So used the same platform tools, PC, etc. Another thing to consider that may help you feel better is that some custom ROMs actually expect that to happen when installing their ROM as a sideload OTA, so could indeed be nothing to worry about.
If it really really worries you, you could always flash the full factory image with "-w" removed from the script file, and either replace the boot.img with the Magisk patched one (rename it first), or flash it separately later. But for now if everything is working normally and it indicates you're on April 2021, I wouldn't worry about it.
What @Lughnasadh said is certainly true; is this what you mean? Or the way I read your question, are you losing root between reboot despite flashing the Magisk patched boot image? Are you sure you flashed it? Are you doing fastboot flash boot (file.img) or doing fastboot boot (file.img)? Make sure you're actually flashing it, not just booting to it. If all else fails, try doing a complete uninstall of Magisk and then start over (hopefully won't be necessary). I've never heard of anyone having the problem you're having though, and it sounds more like you're fastboot booting to the Magisk patched image, and not actually fastboot flashing it...
Click to expand...
Click to collapse
Ohhh yes thanks to remember me i forgot to write FLASH i was only boot without flash. Thanks for all

im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help

@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?

Ghisy said:
@i5lee8bit Good stuff as usual, updated fine over here! Thanks!
Does anyone know the update process for Magisk now that everything is unified? I used to update manager then patch the boot image again. Is it still the same process from Magisk 22 to 22.1 (today's update)?
Click to expand...
Click to collapse
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.

@Lughnasadh Yeah, I'm already rooted on v22. Just did the app update then direct install and it worked fine! I've been in the rooting game since the HTC Desire but the latest changes with Magisk confused me for a minute there!
Thanks

bluizzo said:
im having an issue with getting root back. i followed the instructions and when its time to reboot to the system, i get the splash screen but it reboots back to the bootloader or itll reboot twice and send me to the OS but without Magisk. ive done the factory image thing and still the same thing. i need help
Click to expand...
Click to collapse
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Lughnasadh said:
If you are already rooted on Magisk 22.0, you should be able to just update the app to 22.1 and then do the direct install method to update root (I just did this and everything was fine using Beta channel). If you were unrooted and installing root for the first time (rather than updating), patching the boot image would be the way to go.
Click to expand...
Click to collapse
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.

i5lee8bit said:
Hey sorry, had a really busy week and haven't been on XDA in a few days. Did you get this resolved yet?
My first thought was you were probably bootlooping due to a Magisk (or Xposed) module that doesn't agree with the new firmware. Because that could cause a bootloop, kicking you back to bootloader and eventually forcing a safe mode boot, disabling all Magisk modules and MagiskHide... only problem with this is that afterwards, you should still have root, though with all modules and MagiskHide disabled (I'm more attuned to believe this was actually your case, not that you were "losing root" per se. When it boots back up, are you able to go into Magisk Manager and toggle your modules? Also, what does it say on the manager's home page under "Magisk" and "App" sections? (the parts titled "Installed"). You'll also want to make sure you're running / have installed Manager v22.0 (if flashing the Magisk patched image I provided in the OP; you can always update Magisk / Magisk Manager to v22.1 afterwards).
Sounds like you already tried flashing the 04-2021 full factory image too? Which would eliminate the possibility you maybe flashed the wrong boot / dtbo / or OTA files. If all else fails:
Re-flash full factory image (remove the -w flag in the script file - it sounds like you already did this so I'm assuming you know why) and it should boot unrooted - but you should be able to use the phone.
Make sure Magisk Manager version is 22.0 (i.e. same version as patched in the OP, though 22.1 would work fine too), and if not, grab it from topjohnwu's github and install it.
Reboot to bootloader and flash the Magisk patched boot image in OP (fastboot flash boot coral-rq2a.210405.005-magisk_patched-22.0.img).
Boot the phone. Hopefully you're done.
But if it bootloops, boot it in safe mode (this will disable all your modules as well as MagiskHide). Reboot again.
Open Magisk Manager and all modules should be disabled... time to test for the culprit!
Remember to re-enable MagiskHide, if you had it enabled before. It does not automatically re-enable like it did back in the pre-Magisk 21.0 days. Wow, this post ended up being a lot longer than I expected, and you might not even need the help anymore, lol (though I hope you did get it resolved sooner than later). But at least I can link to this as reference for future guides. Best of luck to you.
Exactly as @Lughnasadh said, this is what I do too (except I'm using stable channel). Direct Install used to give me problems, but that was almost a year ago (a bit after I first got the phone last March), but it hasn't given me any problems since. Even in the very unlikely chance it did cause problems, you could always re-flash the patched boot image in the OP and then patch the stock boot image yourself using Magisk Manager and flash it.
Click to expand...
Click to collapse
Nah, you're good fam. I ended up accidentally flashing the factory img and I'm back with root. Thank you for your help and the guides

How To Guide Rooting the Google Pixel 6a

Rooting the Pixel 6a is just about as easy as any other factory unlocked pixel, but because so many people have had issues with unlocking their bootloaders, I figured I'd post my exact personal steps I took when a Pixel 6a came into my tech shop to be rooted, and I discovered the current bug with Rooting
What You'll Need:
- June 2022 Firmware OTA Update Installed at least: Do this on device. Do Not download the OTA update from google's firmware website.
- ADB/Fastboot/Google Drivers for Windows: I use this to install- ADB 15sec Installer
- Magisk Manager APK: Github - Magisk Github Releases
- Firmware Matching Currently Installed: Google FW page - Google Official Firmware Downloads - you need this for the boot.img file
- A Windows Computer
- A USB-C cable to connect to your phone to the computer
OEM Unlock Bug
With early units sold by Google, they're shipping with a bug where OEM Unlock stays grayed out. Here's the only way I got around this issue
1.) Log out of any Google Account on the device
2.) Connect to Wifi, check for updates without your sim card in the device. There is a bug where it will potentially download the update for your carrier sim
3.) At minimum, you should get the June 2022 security patch update. Run the update and remember which update it is for when you download the firmware to get boot.img
4.) When the update is finished, Factory Reset your device either from settings or Android recovery
5.) Go through Android setup without sim card in, and don't connect to wifi, finish setup without logging into a google account or anything
6.) When setup is done, connect to wifi and put your sim back in.
7.) Pay attention in your notifications for "Preparing your Device" notification.
8.) When that notification pops up, enable Developer options (tap build number a bunch of times)
9.) OEM Unlock should be possible to enable now. Also enable USB Debugging
Pre-Root Setup
1.) Install Magisk Manager from Github
2.) Use 7zip (or any other ZIP opening program) to extract the boot.img from your firmware download from google
-- the boot.img is inside another zip file that's in the download from google. very easy to get
3.) Put the Boot.img on your phones internal storage
4.) Open Magisk Manager, and select your Boot.img from internal storage. Patch the boot.img to make it a rooted boot.img
5.) With your phone connected to the computer, move the magisk_patched.img from sdcard/downloads to your computer
6.) If USB debugging is properly enabled, now you can open CMD and reboot to bootloader with
Code:
adb reboot bootloader
Unlocking the bootloader
1.) With the device connected, OEM Unlock enabled, and booted to bootloader, you can unlock the bootloader with the following command
Code:
fastboot flashing unlock
-- If nothing changes on your phone screen, use Device Manager to make sure the device is recognized via google drivers: vid here on that - Quick Fastboot Drivers Install Tutorial
2.) On your phone, use the volume keys to select Unlock Bootloader, then hit the power button, device should reboot back to bootloader
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
4.) Now you can reboot back into your device and you should be rooted!
Code:
fastboot reboot
Congrats! Now you're bootloader unlocked and rooted! GrapheneOS is already available if you want a degoogled rom, haven't seen another rom pop up yet
all done from there
updating your device when rooted
I do not have a pixel 6a specifically for this right now to confirm this will work, but on every other device with OTA's, this has been my process.
1.) Download your OTA using the system update part of Settings
2.) When it pops up and is ready to restart to finish installing the update, DO NOT CLICK RESTART IN SETTINGS/SYSTEM UPDATE
3.) Go to Magisk Manager, and select Install next to Magisk
4.) Select "Install to Inactive Slot (After OTA)
5.) When its done patching the boot partition, hit restart in Magisk
Your OTA Update is now rooted

To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!

To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.

Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?

jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.

these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)

ctfrommn said:
Correct, though I would probably fastboot boot first just to make sure it boots up ok. When it does you can reboot to recovery and flash it.
Click to expand...
Click to collapse
here it is and does and works perfectly well thank you for everything.

Im starting work on my custom kernel now so hopefully MVK for Bluejay will be ready in the coming days/weeks.

Zaxx32 said:
To save time and effort here is the magisk patched boot.img for June 2022 patch level, Carrier Unlocked 6a from the Google Store. Make SURE you are on build SD2A.220601.003 before flashing!
Click to expand...
Click to collapse
As this thread ages, not everyone will have the June 2022 update. That's why I suggested/put the steps in to do it themselves with matching firmware to what their device is on.
benji said:
To get the `OEM Unlock` option in Developer Options to work, it's simpler to just manually flash 12.1.0 (SD2A.220601.004, Jun 2022, Verizon, Verizon MVNOs) and then wipe.
Even though it's label as Verizon, it should work for all carriers.
Click to expand...
Click to collapse
This DID NOT work for me. That's why I wrote this up the way I did.
jejemc said:
Hello, if we have already unlocked the bootloader, we just have to do this: start cmd then fastboot flash boot magisk_patched.img then restart the phone?
Click to expand...
Click to collapse
If you're bootloader is already unlocked, you just have to flash the patched magisk boot img, correct. I wrote this up for those having issue with not having the ability even if it is an unlocked from google device
frank93 said:
these instructions sound like "the usual process", but for the 6a isn’t there something to patch regarding vbmeta as well?
(never had a phone that "needed" this, but in my understanding it "should" be necessary with the 6a? won’t have time to try out myself before the weekend, just asking ..)
Click to expand...
Click to collapse
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)

KaptinBoxxi said:
3.) flash the boot partition with the magisk patched boot.img
Code:
fastboot flash boot magisk_patched.img
Click to expand...
Click to collapse
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.

KaptinBoxxi said:
Correct, these are basically the usual steps. There's nothing regarding vbmeta flashing in this case of just rooting stock firmware. You only need to do that with ROMs (GSI's mainly)
Click to expand...
Click to collapse
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.

stormcrank said:
I followed your steps to a T. Still can't unlock. I'm convinced there is a fault with my device itself at this point.
Click to expand...
Click to collapse
they will warranty replace if it for sure fails still. Its a silly situation, but mistakes happen

binary**# said:
Just a heads up. As already told by ctfrommn, it's always a better approach to first boot the magisk patched boot file. And if everything works well and good, you could then Direct Install it via Magisk.
Although directly flashing should also work, but its always better to be on the safer side.
Click to expand...
Click to collapse
I may not be very active on XDA, but have been rooting and rom'ing devices since the palm pre, first android phone was the droid x. I've never heard of this step, its never been needed. Its an extra pointless step that is just tethered root. You don't need to do it. As long as you don't download a random Boot.img, like the one for some reason attached to a reply on this thread and get it yourself from the firmware matching your device OR flashing Magisk via TWRP/Lineage Recovery with adb sideload, there's no reason to fastboot boot the boot.img.

You may have never run into an issue flashing a boot image but I've built thousands of roms and kernels and have learned the hard way more than once to measure twice, cut once.
That said, as long as you're simply patching a stock boot.img it's likely not an issue.

Followed all steps, on SD2A.220601.003SD2A.220601.003. OEM unlock still greyed

Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?

Voxilli said:
Nice work, Kaptinboxxi. Everything worked fine. How should we handle updates after rooting? Will a security patch break root? If so, what is the best process to root it again?
Click to expand...
Click to collapse
Yes, each update will require reflashing a patched kernel for the new build.

You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io

Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
Good call...I guess I've never messed with that as I flash so many kernels anyway.

Lughnasadh said:
You can also do the "Install to Inactive Slot" method in Magisk to update and keep root. This has been a bit of a hit and miss for some people on the Pixel 6 series, though. The misses may be in large part be due to people having modified their partitions or not restoring the necessary images while being on a custom kernel.
OTA Upgrade Guides
The Magic Mask for Android
topjohnwu.github.io
Click to expand...
Click to collapse
That's what I've done with my OnePlus 7T for the last three years. Any repercussions for doing it this way versus patching the kernel?

Question Fail safe ota method

I don't wanna risk the on device ota via restoring images through magisk again
Does the following check out?
I'd greatly appreciate if someone, perhaps @V0latyle could look over it, you already helped me a lot the last time.
Download ota, as well as firmware and check if boot.img got updated (or perhaps someone on an updated phone can check but idk how to even check your boot version)
Either patch new boot.img or keep the old one at hand if it didn't get updated
Disable all magisk modules and reboot
Go to magisk -> uninstall -> restore images and reboot
Go in sideload mode and sideload the ota
Reboot to system so the ota can complete
Turn off and boot again from magisk patched boot.img
Direct install through magisk and enable modules
Reboot so modules work and done
All those reboots might not be necessary but I don't know if f.e. magisk modules immediately stop affecting the system after disabling them or if a reboot is required to fully disable them, same with unrooting, even after restoring images the current system has still root so I might need to reboot before sideloading.
I know that technically I don't need to unroot at all for sideloading to work but I really want to make this as safe as it can get.

G5-User7080 said:
I don't wanna risk the on device ota via restoring images through magisk again
Does the following check out?
I'd greatly appreciate if someone, perhaps @V0latyle could look over it, you already helped me a lot the last time.
Download ota, as well as firmware and check if boot.img got updated (or perhaps someone on an updated phone can check but idk how to even check your boot version)
Either patch new boot.img or keep the old one at hand if it didn't get updated
Disable all magisk modules and reboot
Go to magisk -> uninstall -> restore images and reboot
Go in sideload mode and sideload the ota
Reboot to system so the ota can complete
Turn off and boot again from magisk patched boot.img
Direct install through magisk and enable modules
Reboot so modules work and done
All those reboots might not be necessary but I don't know if f.e. magisk modules immediately stop affecting the system after disabling them or if a reboot is required to fully disable them, same with unrooting, even after restoring images the current system has still root so I might need to reboot before sideloading.
I know that technically I don't need to unroot at all for sideloading to work but I really want to make this as safe as it can get.
Click to expand...
Click to collapse
No need to unroot or restore images. You can disable modules if you want. Just sideload the OTA, and live boot the old patched image, then perform Direct Install in Magisk.
By the way, instead of creating a new thread, you could have asked this question in an existing one...

V0latyle said:
By the way, instead of creating a new thread, you could have asked this question in an existing one...
Click to expand...
Click to collapse
Perhaps I could have, I am hoping that this way it might be easier to find for others than having to look somewhere on the 30th post of a thread that is about a bricked device after ota.
V0latyle said:
No need to unroot or restore images. You can disable modules if you want. Just sideload the OTA, and live boot the old patched image, then perform Direct Install in Magisk.
Click to expand...
Click to collapse
mhh I see, I'm just a little scared of the ota process after what happened the last time so I wanna be like extra sure nothing can go wrong.
Doesn't help that I don't really understand what OTA's do exactly..
That I don't have to unroot when flashing factory makes sense as I'm just overwriting boot anyway.
Is an OTA the same thing essentially? Like is it basically a bunch or partitions in a zip that get flashed over whatever is there previously?
Meaning all things that could go wrong or get checked happen through the system update app rather than through the OTA itself?
Also you are saying "unroot or restore images", is that not the same thing?
And let's say boot gets updated and I live boot the older outdated image, does that not matter at all?

why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.

frank93 said:
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.
Click to expand...
Click to collapse
This sounds like the "Quick Method" mentioned here:
https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/
You're doing that?

frank93 said:
why do you wanna take the OTA route if you already downloaded the complete firmware package anyway? i’ll do a firmware flash (instead of OTA) without wiping each month and that’s it, i’ll even patch boot.img before flashing (and flash it directly together with the rest of the new firmware). works just fine.
Click to expand...
Click to collapse
As far as I understood sideloading OTA is the most safe and uncomplicated way

media-fort said:
This sounds like the "Quick Method" mentioned here:
https://www.xda-developers.com/how-to-install-ota-updates-keep-root-google-pixel-phone/
You're doing that?
Click to expand...
Click to collapse
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.

G5-User7080 said:
Perhaps I could have, I am hoping that this way it might be easier to find for others than having to look somewhere on the 30th post of a thread that is about a bricked device after ota.
Click to expand...
Click to collapse
Well, I had thought there were existing guides in this section, but either I was mistaken or they've been buried.
G5-User7080 said:
mhh I see, I'm just a little scared of the ota process after what happened the last time so I wanna be like extra sure nothing can go wrong.
Doesn't help that I don't really understand what OTA's do exactly..
Click to expand...
Click to collapse
Maybe explaining it could help you. I'll do so in response to your questions below.
G5-User7080 said:
That I don't have to unroot when flashing factory makes sense as I'm just overwriting boot anyway.
Click to expand...
Click to collapse
Exactly.
G5-User7080 said:
Is an OTA the same thing essentially? Like is it basically a bunch or partitions in a zip that get flashed over whatever is there previously?
Click to expand...
Click to collapse
Regardless of whether installed through system update or via sideload, the OTA package always installs to the other slot - if you're currently running on slot A, it installs to slot B, and vice versa. See A/B (Seamless) System Updates
G5-User7080 said:
Meaning all things that could go wrong or get checked happen through the system update app rather than through the OTA itself?
Click to expand...
Click to collapse
OTA through system update doesn't always seem to work for rooted users; some have suggested that it may be necessary to restore images in Magisk to pass verification checks in order for the update to succeed. Others, like me, don't bother with the OTA updates anymore because 1) OTA through system updates just don't seem to work and 2) Magisk patching inactive slot still seems to have issues. I personally prefer to use the factory images, but the OTA method is technically safer.
OTA sideload should always work, and AFAIK it doesn't matter what state your device is in. It overwrites whatever is on the currently inactive slot; there's no need to remove modules or restore images or unroot as the boot image gets overwritten with the new boot image.
G5-User7080 said:
Also you are saying "unroot or restore images", is that not the same thing?
Click to expand...
Click to collapse
No, they aren't.
When your device boots, it loads the contents of the /boot partition into memory - ramdisk and kernel. This remains in memory while the system is running.
Hence, if the boot image has been patched, you'll boot with root.
When you perform "Restore Images" in Magisk, this uses root access to restore the unpatched image to /boot. But, since the patched boot image was already loaded into RAM, you still have root.
If you reboot at this point, you'll lose root because the now unpatched boot image is loaded into memory.
G5-User7080 said:
And let's say boot gets updated and I live boot the older outdated image, does that not matter at all?
Click to expand...
Click to collapse
Yes and no.
After an OTA update, you want to let the system boot with the new boot image. This is because the boot image has a signature that matches the system image; if these don't match, the update engine determines that the update was a failure, and will recycle you back to the original slot. So, the boot image that the system loads after the update has to be the new one. It doesn't matter if it's been patched or not - you could, for example, download the factory image, extract the boot image from it, patch the boot image in Magisk, then sideload the OTA, force your phone to boot into bootloader, and flash the new patched image.
Patching to inactive slot in Magisk is supposed to avoid all this, and can only be used if you update through system. It works like this:
You're rooted on the February release on slot A.
You restore images in Magisk, but do not reboot.
You install the OTA through system updates. This installs to slot B
When it prompts you to reboot to finish the update, instead you go back to Magisk and use Patch Inactive Slot - this uses root access to perform the Magisk patch on the new boot image in /boot_b
You then reboot, and the system switches to slot B, and loads with root because you patched the boot image.
However, this doesn't seem to be working for everyone. Some phones don't even "see" the OTA update is available for some reason.
Therefore, this is the method I recommend you use to install the OTA update:
Download the OTA update for your device from Pixel OTA Images
In Magisk, go to Reboot > Reboot to recovery
Once in recovery mode, hold Power and click Volume Up. Then, select "Apply update from ADB" and connect your phone to your computer.
On your PC, open a command line in your ADB Platform Tools folder, and type adb sideload <path to OTA zip> - to make this easier, just drag and drop the OTA zip into the command window.
Once the update completes, let your phone boot to system. You will not have root, so it won't matter if you didn't disable Magisk modules.
Let the system complete the post-update work (there's a notification with a gear icon) and get stabilized. Wait a few minutes.
Assuming you still have USB debugging enabled, use ADB to reboot to bootloader: adb reboot bootloader or you can just do it manually - reboot your device and hold Volume Down
You can now live boot an older patched boot image: fastboot boot <drag and drop patched boot image>
You should boot with root. Note: if your phone bootloops, see my note below)
In Magisk, go to Install > Direct Install. This uses the "temporary root" of the patched image you've loaded into memory to patch the new boot image
Reboot once more. You should now be on the new boot image with root.
If your phone boot loops, double check to make sure you're still on the latest update. You can check this in Settings > About, but it's also displayed on the notification windowshade under the Quick Settings tiles. Make sure this matches the OTA image you just installed. If it doesn't, this means that your device has recycled back to the "old" slot for some reason, and you'll have to start over.
If you want to play it safe, you can use this guide to extract the new boot.img from the OTA payload. You'd then patch this manually in Magisk, and after installing the update, you'd reboot to bootloader and flash to /boot.
If you still bootloop on the new boot image after patching, you probably need to disable Magisk modules. You can do this via command line:
adb --wait-for-device shell magisk -remove-images

frank93 said:
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
Click to expand...
Click to collapse
Damn, I tried this and it seems that my PC cannot write the image to the Pixel 6a?!
Do I have old ADB drivers or whats the reason for that?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Edit:
Sry, I'm not involved here all the time. Figured it out myself. Reason for the failure were the freakin' platform_tools_r34. Switched to r33 and worked straight away..
https://forum.xda-developers.com/t/...el-7-pro-support-thread.4505287/post-88134573

V0latyle said:
Well, I had thought there were existing guides in this section, but either I was mistaken or they've been buried.
Click to expand...
Click to collapse
Not in the 6a forum as far as I'm aware, there might be more in the Pixel 6 forum, but I've already seen your guide that covers all kinds of methods.
V0latyle said:
the OTA package always installs to the other slot
Click to expand...
Click to collapse
Wouldn't it make sense to restore the unrooted boot partition on the currently active slot given that OTA will switch me to the currently inactive slot?
So that after the OTA procedure I'm in the same situation as now, being on a rooted slot with having the original unrooted slot as sort of "backup".
V0latyle said:
there's no need to remove modules or restore images or unroot as the boot image gets overwritten with the new boot image.
Click to expand...
Click to collapse
I think it was on the magisk ota guide but im not sure, that it said that it's important to disable all system modifying modules before attempting an update.
While all modules I use should by systemless,.. I think?.. I still think it's just easier to disable them all and re-enable them later, just to avoid trouble and make it easier to write in a guide, as in "just disable them and don't bother checking if theyre really all systemless".
V0latyle said:
After an OTA update, you want to let the system boot with the new boot image.
Click to expand...
Click to collapse
Yes, that was my intention, let it boot normally without touching anything to complete the OTA.
Didn't know I would have to wait a few minutes after already being in the system tho to wait for the notification, I'll look out for that.
V0latyle said:
In Magisk, go to Reboot > Reboot to recovery
Once in recovery mode, hold Power and click Volume Up. Then, select "Apply update from ADB" and connect your phone to your computer.
Click to expand...
Click to collapse
Is this equivalent to the way you described in your Pixel 6 guide?
As in doing adb reboot sideload to go to sideload mode, followed by adb sideload ota.zip
V0latyle said:
If your phone boot loops, double check to make sure you're still on the latest update.
Click to expand...
Click to collapse
If it bootloops how would I even get back into system?
Why would it even bootloop, if there is a known cause can't I just avoid whatever is causing it to begin with?
I mean I don't assume I'll bootloop following the steps carefully but this time I'll post and wait for replies before just nuking everything like last time ^^
V0latyle said:
If you want to play it safe, you can use this guide to extract the new boot.img from the OTA payload.
Click to expand...
Click to collapse
Yes, I'd prefer to make it as safe as possible.
Is the boot.img extracted from the OTA the same as the one from the according firmware?
Would be easier to just extract that on PC.
Oh and two more question that came to mind.
When restoring images through magisk it replaces the rooted boot partition with the stock one.
But root only disappears on next reboot.
So can I restore images and then directly do adb reboot sideload followed by doing the OTA?
Meaning I don't need to do one reboot back to system to sort of "complete the unrooting preocedure"?
Is that the same for magisk modules?
If I want to disable them just in case, do I need to reboot once after for them to like get removed from the system or are they instantly disabled the moment I press the "disable module" switch?

G5-User7080 said:
Not in the 6a forum as far as I'm aware, there might be more in the Pixel 6 forum, but I've already seen your guide that covers all kinds of methods.
Wouldn't it make sense to restore the unrooted boot partition on the currently active slot given that OTA will switch me to the currently inactive slot?
So that after the OTA procedure I'm in the same situation as now, being on a rooted slot with having the original unrooted slot as sort of "backup".
Click to expand...
Click to collapse
Not if you're going to sideload the OTA. There's no point to doing so.
G5-User7080 said:
I think it was on the magisk ota guide but im not sure, that it said that it's important to disable all system modifying modules before attempting an update.
While all modules I use should by systemless,.. I think?.. I still think it's just easier to disable them all and re-enable them later, just to avoid trouble and make it easier to write in a guide, as in "just disable them and don't bother checking if theyre really all systemless".
Click to expand...
Click to collapse
Yeah, this is the "safe" option. I just use MHPC + USNF mod + systemless hosts so I don't bother disabling, but those who use Xposed or other more "invasive" system mods might want to.
G5-User7080 said:
Yes, that was my intention, let it boot normally without touching anything to complete the OTA.
Didn't know I would have to wait a few minutes after already being in the system tho to wait for the notification, I'll look out for that.
Click to expand...
Click to collapse
This is because it seems to take a few minutes for the system to "get happy" and decide that all is well, and if you live boot an older boot image before it does so, it will assume the update failed and recycle back to the old slot.
G5-User7080 said:
Is this equivalent to the way you described in your Pixel 6 guide?
As in doing adb reboot sideload to go to sideload mode, followed by adb sideload ota.zip
Click to expand...
Click to collapse
Yep. The commands and the method is exactly the same for all Pixel devices. The only thing that is different are the files. Only the Pixel 7 / 7 Pro are slightly different in that we have to patch init_boot instead of boot.
G5-User7080 said:
If it bootloops how would I even get back into system?
Click to expand...
Click to collapse
Use the command I gave you: adb --wait-for-device shell magisk --remove-modules while booting
G5-User7080 said:
Why would it even bootloop, if there is a known cause can't I just avoid whatever is causing it to begin with?
Click to expand...
Click to collapse
There isn't a known cause, the exception being trying to boot an old boot image without letting the system complete the update post-reboot as described above
G5-User7080 said:
I mean I don't assume I'll bootloop following the steps carefully but this time I'll post and wait for replies before just nuking everything like last time ^^
Yes, I'd prefer to make it as safe as possible.
Is the boot.img extracted from the OTA the same as the one from the according firmware?
Would be easier to just extract that on PC.
Click to expand...
Click to collapse
Yes. It's just packaged differently.
Since Payload Dumper requires Python, I've found it simpler to just use the factory image - although if you're at that point, you may as well just flash the factory image anyway.
G5-User7080 said:
Oh and two more question that came to mind.
When restoring images through magisk it replaces the rooted boot partition with the stock one.
But root only disappears on next reboot.
So can I restore images and then directly do adb reboot sideload followed by doing the OTA?
Meaning I don't need to do one reboot back to system to sort of "complete the unrooting preocedure"?
Click to expand...
Click to collapse
I never suggested you'd need to reboot after restoring images. Once you've restored the original boot image, that's what is in the boot partition. It takes effect immediately. What doesn't take immediate effect is what's currently running in memory, which is why I pointed out that upon a reboot, your device will load the unpatched image because that's what's in the partition. But, as I explained above, there's no point to restoring the original boot image if you're sideloading the OTA. The only time this ever appears to be necessary is when you're taking OTA through system update.
G5-User7080 said:
Is that the same for magisk modules?
If I want to disable them just in case, do I need to reboot once after for them to like get removed from the system or are they instantly disabled the moment I press the "disable module" switch?
Click to expand...
Click to collapse
I am honestly not sure about this one, but since we are talking about OTAs, the point is moot - when the update completes and the phone reboots, it's booting an unpatched boot image, meaning there's no way for the modules to load. It doesn't matter if you've made changes to system, either, because the system partition also has two slots - system_a and system_b
The only thing that MIGHT matter is when you boot the patched image, because if you haven't disabled modules, they will load during boot, and if one of them causes a bootloop for whatever reason....It still shouldn't matter because in this case, the device -should- try to boot the same slot again, and since you never patched the new boot image, it will boot without root.

V0latyle said:
I am honestly not sure about this one, but since we are talking about OTAs, the point is moot - when the update completes and the phone reboots, it's booting an unpatched boot image, meaning there's no way for the modules to load. It doesn't matter if you've made changes to system, either, because the system partition also has two slots - system_a and system_b
Click to expand...
Click to collapse
yea it seems like its the same as restoring images, it disables them but obviously they are already loaded for the current session and probably don't get "unloaded", they just won't load again from the next boot on, so I don't think there would be any need to reboot, except when you want to do something in system that requires modules to be disabled.
So it seems like we'll have to wait til like the 20th for the march update, so I'll just go straight for the april one.
Considering what you said, would this be the correct procedure, just to confirm?
Extract boot.img from factory image and patch it, then move it to pc.
In Magisk app, disable all modules.
On pc do adb reboot sideload and after rebooting in download mode adb sideload ota.zip
Choose "reboot system" from menu or use adb reboot... does that command work in download mode?
Let it reboot, unlock, wait for the update completed notification to appear.
Confirm that adb debugging is still enabled and the version number below quick tiles matches the update, then do adb reboot bootloader.
Live boot the new magisk patched boot.img with fastboot boot patched_boot.img.
Magisk app -> Install -> Direct Install, then re-enable all modules and reboot.
done
Additionally, I'm wondering what all the different "menus" are for.
Like first there is bootloader where you can flash partitions through the fastboot command and enter recovery or boot system.
Then there is the recovery that... doesn't really do anything when it's stock?
Then there is sideload or download mode that is accessed from the recovery.
Then there is adb fastboot, does that bring you to the fastbootd screen? I have no idea what that is for.

G5-User7080 said:
yea it seems like its the same as restoring images, it disables them but obviously they are already loaded for the current session and probably don't get "unloaded", they just won't load again from the next boot on, so I don't think there would be any need to reboot, except when you want to do something in system that requires modules to be disabled.
So it seems like we'll have to wait til like the 20th for the march update, so I'll just go straight for the april one.
Considering what you said, would this be the correct procedure, just to confirm?
Extract boot.img from factory image and patch it, then move it to pc.
In Magisk app, disable all modules.
On pc do adb reboot sideload and after rebooting in download mode adb sideload ota.zip
Choose "reboot system" from menu or use adb reboot... does that command work in download mode?
Click to expand...
Click to collapse
ADB commands work in recovery mode, yes.
G5-User7080 said:
Let it reboot, unlock, wait for the update completed notification to appear.
Confirm that adb debugging is still enabled and the version number below quick tiles matches the update, then do adb reboot bootloader.
Live boot the new magisk patched boot.img with fastboot boot patched_boot.img.
Magisk app -> Install -> Direct Install, then re-enable all modules and reboot.
done
Click to expand...
Click to collapse
If you're going to download the factory image, why not just use Pixel Flasher to perform a factory flash? Contrary to popular belief, flashing the factory image itself does not wipe data. OTA updates are still the "safest" way but I've been using the factory image for a couple years now on my Pixel 5 and have never had a problem.
G5-User7080 said:
Additionally, I'm wondering what all the different "menus" are for.
Like first there is bootloader where you can flash partitions through the fastboot command and enter recovery or boot system.
Then there is the recovery that... doesn't really do anything when it's stock?
Then there is sideload or download mode that is accessed from the recovery.
Then there is adb fastboot, does that bring you to the fastbootd screen? I have no idea what that is for.
Click to expand...
Click to collapse
Bootloader is used for flashing bootloader, modem, and boot.
Recovery mode is a small kernel in of itself that can perform functions that the bootloader can't, and provides a software interface to perform a "safe" recovery should the device stop working - like flashing an OTA.
Sideload mode is part of that recovery software interface - it allows you to serve OTA files over ADB
Fastbootd is "userspace fastboot" that allows advanced flashing functions.
More information on fastbootd

V0latyle said:
If you're going to download the factory image, why not just use Pixel Flasher to perform a factory flash? Contrary to popular belief, flashing the factory image itself does not wipe data. OTA updates are still the "safest" way but I've been using the factory image for a couple years now on my Pixel 5 and have never had a problem.
Click to expand...
Click to collapse
cause I'd need to remove the -w from the update command in the flashall.bat as well as possibly add --skip-reboot
I can see the day coming when I simply forget doing that and wipe my device by accident.
Or when using pixel flasher I might just forget to untick the wipe option.
I want to use a method that ideally I only have to prepare once, say if I could just make a "flash factory without wipe" script that works every time, but due to changing version numbers I have to use the new script every time.

G5-User7080 said:
cause I'd need to remove the -w from the update command in the flashall.bat as well as possibly add --skip-reboot
Click to expand...
Click to collapse
You don't have to use the script. Learn to do the commands manually. You don't have to skip reboot either, but if you want to flash a patched boot image, it helps.
G5-User7080 said:
I can see the day coming when I simply forget doing that and wipe my device by accident.
Or when using pixel flasher I might just forget to untick the wipe option.
Click to expand...
Click to collapse
Pixel Flasher settings are persistent....
G5-User7080 said:
I want to use a method that ideally I only have to prepare once, say if I could just make a "flash factory without wipe" script that works every time, but due to changing version numbers I have to use the new script every time.
Click to expand...
Click to collapse
You seem to misunderstand how flashing the factory image works. You don't have to use the script. Learn to use ADB and fastboot commands manually. You can follow my guide for the 6 Pro here; the commands are all the same.
Otherwise, you can use Pixel Flasher. All you have to do is set it up once, and the settings persist even after updates. This is what I've gone to as a means to simply free myself for other tasks while my phone is updating; I used to do it manually.

frank93 said:
yes, sounds like that’s "my way" of doing it. originally got this from a magisk-issue-comment here, basically it’s a "complete firmware flash with an already patched boot.img, no wipe", and that’s it. never done an OTA/sideload for years tbh.
Click to expand...
Click to collapse
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
I don't want to brick my device, therefore I've always deleted these Login infos before full flashing process.
But after each full flash, it's always very annoying to add all that info again, for each banking app, for Google pay and so on....

media-fort said:
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
Click to expand...
Click to collapse
i never logged out or deleted anything before flashing. it "feels" like an OTA, i just flash (without wipe) and after the next boot the device is ready to be used.

media-fort said:
If you flash a full factory image via fastboot (without wiping the device in that process), is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
And can I stay logged into my Google Account on the device before flashing as well?
Click to expand...
Click to collapse
Flashing a full firmware w/o wiping = OTA update. Since an OTA won't delete anything of your settings/data, a full firmware flash w/o wiping will do the same.
All settings, data and apps are stored on /userdata. When saying "without wiping", then it means "do not erase /userdata".

WoKoschekk said:
Flashing a full firmware w/o wiping = OTA update. Since an OTA won't delete anything of your settings/data, a full firmware flash w/o wiping will do the same.
All settings, data and apps are stored on /userdata. When saying "without wiping", then it means "do not erase /userdata".
Click to expand...
Click to collapse
Almost, but not quite.
Flashing the full factory firmware installs it to the currently active slot and can be done regardless of what version you're already on; if you try to flash the system update alone, it'll complain if it doesn't see the right bootloader and radio version but you can use --force to get around that
Flashing the OTA installs it to the currently INACTIVE slot and can only be done when you're on an OLDER version.

V0latyle said:
Almost, but not quite.
Flashing the full factory firmware installs it to the currently active slot and can be done regardless of what version you're already on; if you try to flash the system update alone, it'll complain if it doesn't see the right bootloader and radio version but you can use --force to get around that
Flashing the OTA installs it to the currently INACTIVE slot and can only be done when you're on an OLDER version.
Click to expand...
Click to collapse
yes, that's right. but regarding to the question
media-fort said:
is it safe and possible to leave your login information for screen unlock (password, fingerprint) installed before flashing?
Click to expand...
Click to collapse
it doesn't matter which slot is active.