Database Info

[GUIDE] STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential

[GUIDE] NOOB-Friendly STEP-BY-STEP Instructions to Install Monthly OTA updates on Rooted Essential PH-1
Introduction: I know there are many threads already posted that answer how to install OTA on rooted devices but unfortunately they get lost in massive threads that are often not NOOB friendly. I do not claim to be an expert but I have spent a long time reading threads and found the method I will detail below the easiest for me to follow on a monthly basis. I will do my best to give credit where credit is due to the original authors but my apologies in advance if I miss anything.
Just to start the prerequisites I have are a Windows 10 PC, Essential PH-1, with Stock OS and stock unlocked Bootloader. I have tried using TWRP in the past but I found this method simpler. I don't know whether my instructions will work for you or not if you already have TWRP installed but I can let one of the experts respond and I will be happy to update the guide based on feedback.
Part 1 - Downloads
Start by downloading the following items and storing them locally on your PC if you don't have them already
Download the latest OTA Monthly build from here: https://www.essential.com/developer/current-builds Note: Just check off that you are looking for "Current Builds" and click "Submit Form" and then click "Download (OTA)" link beneath the newest release you want.
Download the newest stock boot image here from bmg1001's google drive Credit:bmg1001
(FIRST TIME ONLY) Download and install the Windows driver (if you don't already have on your computer) from here: https://storage.googleapis.com/essential-static/Essential-PH1-WindowsDrivers.exe
(FIRST TIME ONLY) Download ADB tool (if you don't have already on your computer) from here: https://developer.android.com/studio/releases/platform-tools.html This link is directly from Essentials site here in their "Before Sideloading" section it is the link entitled "You'll need the latest ADB tool"
To continue you must have developer options USB Debugging enabled which I presume was already done previously if your phone is rooted but if not you must do so before proceeding.
To Enable Developer Options: Settings App> System> About Phone> Scroll Down to Bottom and tap 7 times on the "Build Number"
To Enable USB Debugging: Settings App> Developer Options> USB Debugging (Set to Enabled)
Part 2 - Sideload the OTA Update
DISCLAIMER: This method if done properly should not wipe any of your data, however I take no responsibility and it is always advisable to back up your data before proceeding with any updates if you wish. I will be honest that I have now done this several times and never had any issues.
Unzip the ADB tool (link above in downloads section is for "platform-tools") and save it to a folder easily accesible on your computer (for this demonstration I will use "C:\platform-tools")
Copy the OTA update file to your ADB folder i.e. "C:\platform-tools" and rename it "OTAupdate.zip" (it is not necessary to rename it, just makes this simpler for the guide)
Verify the checksum of the image. I use hashtab which allows you to right click on any file and click properties and see the hashes as a tab in the properties menu. The SHA-256 is listed right under the OTA download link just copy and paste it in to the hashtab to verify
Remove your PIN / Password before sideloading by going to Settings> Security & Location> Screen Lock> Set it to None (this probably isn't necessary I just do it as a precaution)
Plug Essential Phone into computer and make sure that it says USB Debugging Enabled
Open the folder "C:\platform-tools" in Windows File Explorer and hold shift and right click in the window and you select the option "Open Powershell window here" from the context menu (works in Windows 10 can't speak for earlier Windows versions). If you don't see it the first time Shift+right click on a different part of the empty white window and you should see it appear.
Verify your device is properly connected by typing
Code:
adb devices
and you should see your device listed
Type
Code:
adb reboot recovery
Note:If you're unable to use ADB to reboot into recovery, you can use the key combination for your device. While device is off to boot into Recovery mode, press and hold Volume-Up button while pushing Power button to boot.
Your device is now in Recovery mode. An Android logo with red exclamation mark should appear on screen. Hold the Power button, then press the Volume-Up button one time. When the menu appears, select Apply update from ADB.
Run the following command:
Code:
adb devices
Then check that your device shows up with “sideload” next to its name
Run the following command:
Code:
adb sideload OTAupdate.zip
where OTAupdate.zip is the name of the file you downloaded and verified
Once the update finishes, select Reboot system now to reboot your phone
At this point you should have a stock updated essential device but without root. The remainder of this guide will use Magisk to restore your device to root.
Part 3 - Re-root your Device with Magisk
Copy newest boot image from here that you downloaded earlier to a folder directly on your phone. I personally put it in my "Download" folder on my phone so I can find it easily
Open Magisk Manager and click Install>Install>Patch Boot Image
Select the boot image from step 1 and then let Magisk proceed in creating a patched image file
Copy the file "magisk_patched.img" file that Magisk just created from your device back to the computer and put it in the ADB folder "C:\platform-tools"
Plug in phone and open powershell same as before (shift+ right click> Open Powershell window here)
Type
Code:
adb reboot bootloader
to reboot your phone into fastboot
Confirm your phone is in fastboot by typing
Code:
fastboot devices
Then check that your device shows up with “fastboot” next to its name
Execute the command
Code:
fastboot flash boot magisk_patched.img
Restart your phone and you are done! Don't forget to put your phone PIN/Password back if you disabled security in the earlier step.
You should now have a successfully updated phone with full ROOT access with Magisk. I know that this guide seems like a lot of steps but it really goes very quickly, I just tried to be detailed and NOOB-Friendly.
Hope this helps all of my fellow XDA members!! Please share any and all feedback. Thanks!
Full credit goes to this thread for helping me with everything: [GUIDE] Rooting your Essential PH-1

The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
The way I do *updates* is different (not the initial TWRP/ root).
I use the same Essential developer link as in part 1-1. I also have a copy of twrp-installer-mata-3.2.3-0 zip file on my device.
Boot to TWRP, and do a complete nandroid.
Then install the OTA file just like it's any other zip and when it's done, install the twrp-installer-mata-3.2.3-0 zip file. You can simply put them both into the flash queue before starting the flash.
This TWRP installer will install to both slots ensuring that the inactive slot has it installed. Wipe dalvik and then reboot to system which will be in the opposite slot from the one you started at.
The OTA will always flash to the inactive slot and the bootloader will switch to the slot the OTA was flashed to.
The initial boot takes a few minutes. Once I verify the ROM boots correctly, then I reboot to TWRP and flash Magisk. This ensures that Magisk get installed to the same slot that is now active.
I agree it's safer to remove screen pin, so far I have gotten away with never remembering to do that [emoji16]
If the flash fails, the bootloader should just switch you back to the original slot. I would expect that to boot fine, with one exception... The bootloader was changed between 8.1.1 and 9.0. So if you are going between major versions, the original slot will bootloop after the update.
One more note, a pet peeve of mine; when referencing a post that is older, make sure that you review the forums for changes. TWRP might have a required newer release, the methods that once worked may no longer work. If you are not sure or comfortable recovering, then don't be an early adopter. [emoji6]
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
you know i just finished writing my own guide to do it after i had trouble with the sticky posts. for me, magisk couldnt find the stock boot so i had to pretty much redo it. i did most things with back-to-stock and fastboot. but now i really wanna try your method through twrp. i been using the patched_twrp_magisk_stock.img images which have twrp and magisk in the same image. using your method, in twrp, could i flash the ota, the patched_twrp_magisk_stock.img, switch slots in twrp, flash patched_twrp_magisk_stock.img again, then switch back to the original slot and reboot system? thanks!
this thread has the patched_twrp_magisk_stock.img images
https://forum.xda-developers.com/essential-phone/development/stock-7-1-1-nmj20d-t3701681

@andypiznti
There's no need to manually switch slots. And no reason to flash the TWRP *installer* file twice. The first time it runs, it patches both slots.
IMHO, trying to control slots is what gets people into trouble.
I do pay attention to what slot I'm on before I start though. In TWRP, if you go to the reboot menu, it will tell you. But the way I flash, I stay on the slot I started with. The OTA will always flash to the opposite slot - which should be the inactive slot. Flashing the TWRP *installer* file just once, patches both slots.
Just wipe dalvik (and cache but there is no cache partition so it will error - just ignore the error) then reboot to system like we've done after custom ROMs for years.
The next boot, the bootloader knows to switch to the slot with the newest OS.
After a successful boot, when you return to TWRP, you'll see the slot is the opposite one from when you started. But you didn't need to do any slot switching.
Don't force things. Let the slots take care of themselves.
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...

ktmom said:
@andypiznti
I also think, there is less likely to be trouble with Magisk and the boot.img, if you boot fully after an update, before returning to recovery to flash Magisk. Remember that both TWRP and Magisk are making changes to the boot.img.
Final thought, unless I seriously misunderstand Magisk, if you rooted using an all-in-one boot.img you won't have a back up of the "stock" boot.img to restore, making the Magisk uninstaller useless. The backup made when installing Magisk is stored on the data partition, not the boot partition. This is why the instructions in BTS tell you to flash the stock boot.img and provide a copy of it.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
ok that answers a lot. thanks! the guide i made for myself had me flashing the stock image with bts. i was curious about the full boot after an update, i was thinking the same thing in that it might cause problems with magisk, but i also thought twrp would cause problems too. the reason i mentioned switching slots and flashing is the all-in-one img only flashes to one slot at a time, i believe.
heres my guide for reference, its kinda long. but these were the exact steps i followed and was successful. had to flash the img twice, kept rebooting into recovery if i didnt.
Applying OTA for Essential Phone when Magisk doesn't have stock boot
Boot to recovery with Magisk
Back up at least system and boot
Boot to bootloader with TWRP
Extract back to stock (BTS) for CURRENT INSTALLED VERSION, not the update BTS version
Once in bootloader, connect phone->old phone plug, SSD plug
Run flashallnowipe.bat, once bootloader reboots, select Start, unplug phone
Uninstall Magisk like a regular app
Do OTA->settings->advanced->system update
after reboot->reboot while holding volume down until in download/fastboot mode
***REMEMBER!! Flash on the opposite slot of the current slot
***so if im on slot a, flash slot b.
make sure to extract Essential_ADB_and_FASTBOOT.zip in BTS folder then->cmd-here.exe
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch to other slot
fastboot --set-active=a
fastboot --set-active=b
***Just to double check, REMEMBER!! Flash on the opposite slot of the current slot
fastboot getvar current-slot
***
fastboot flash boot_a dec_patched_twrp_magisk_stock.img
fastboot flash boot_b dec_patched_twrp_magisk_stock.img
***Switch back to orig slot
fastboot --set-active=a
fastboot --set-active=b
On the phone fastboot menu, select Start, unplug phone
Manager asks if you wanna install it, no, it downloads the wrong one, maybe works now?
Install Magisk Manager->https://github.com/ianmacd/MagiskBuilds
IT HAS TO BE THIS APK, Download any apk version from above github, install
when you open Manager, then download the newest apk, dont update image
Manager and Image update daily, ignore till next month OTA
Click to expand...
Click to collapse

hssxda said:
The beauty of my method in the OP is you don't need to worry at all about the correct "slots" like you have to with TWRP...
Click to expand...
Click to collapse
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

ktmom said:
I don't know what more I could do to make the point it's not necessary to work about slots in TWRP.
Click to expand...
Click to collapse
Well, all of your posts describing your method contains the word "slot" multiple times so it is obviously a relevant concern otherwise you wouldn't have mentioned it. My post did not contain the word even once...
I see no need to use TWRP. What advantage does it have?

ktmom said:
I don't know what more I could do to make the point it's not necessary to worry about slots in TWRP.
@andypiznti. The all-in-one is Fastboot flashed to either slot one at a time. All of this makes life harder than it needs to be.
My post was suggesting an alternative. Use the OTA, no Fastboot, no PC just have the TWRP installer file I linked so you don't lose TWRP.
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini
Click to expand...
Click to collapse
oh yes, definitely doing that next time. thanks!! i found this post thats exactly your method in a little less words.
https://forum.xda-developers.com/es...1-1-nmj20d-t3701681/post78194778#post78194778

Jeebus...
We didn't like the other 15 goddamn threads with the same topic...
XDA is cancer

what works for me at the time to flash the patched image was
fastboot flash boot_a patched_boot.img
fastboot flash boot_b patched_boot.img
note: i am on pie
thanks for the guide.

Really helped lots, thank you.

January update is out, who might like to patch boot.img with TWRP and Magisk?

kma_29 said:
January update is out, who might like to patch boot.img with TWRP and Magisk?
Click to expand...
Click to collapse
Go to the stock room thread
"find somebody that you think is undeserving of your compassion and give it to them" - Christian Picciolini

OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264

morphius88 said:
OP, if you want to avoid having to sideload the whole OTA, you can have it done directly by your phone by flashing the stock boot image for the current version that you are one and then updating from the settings (or notification). Then just continue with flashing the rooted boot image for the new update. I feel like that is safer than both TWRP and sideloading the full OTA (in reference to keeping data safe).
https://forum.xda-developers.com/showpost.php?p=76828139&postcount=1264
Click to expand...
Click to collapse
Thanks

@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip

jionny said:
@bmg1001 are you still providing the stock boot images on your google drive. I am looking for the Feb stock boot image or can someone tell me how to get it. I tried extracting from the Feb OTA but did not see it listed in that zip
Click to expand...
Click to collapse
Yep, I have it in the same Google Drive folder where the other month's images are posted.

bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Sorry chalk that up to me not paying attention. I was looking for it after Jan but its actually the first one listed. Thanks!

bmg1001 said:
Yep, I have it in the same Google Drive folder where the other month's images are posted.
Click to expand...
Click to collapse
Hi one more thing, this is my third time updating and rooting via this method. The last two times worked flawlessly however this time I did update the OTA but when I try to reroot and go to adb devices I see my phone listed then when I reboot recovery it does however when I try fastboot devices my phone does not show and nothing happens, any help will be appreciated

May 2020 QQ2A.200501.001.B2 "CORAL" Magisk-Patched Boot Img [+UPDATE/KEEP ROOT GUIDE]

May 2020 QQ2A.200501.001.B2 "CORAL" Magisk-Patched Boot Img [+UPDATE/KEEP ROOT GUIDE]
Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.
I've also installed and tested / verified that Kirisakura 4.2.0 is working great with this month's patch so far.
Also have EdXposed Canary 0.5.0.0 (4548) YAHFA installed. SafetyNet still passing as of now.
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796392
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261796399
THESE FILES ARE FOR 10.0.0 (QQ2A.200501.001.B2, May 2020, All carriers except TW) ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
If these files and/or guides are helpful, please drop a thanks and let me know. =)

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide exactly if coming from build QQ2A.200405.005, Apr 2020. But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796390
coral-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796391
May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq2a.200501.001.b2-8309f363.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-qq2a.200405.005-factory-boot.img
3. fastboot flash dtbo coral-qq2a.200405.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations
-----------------
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-qq2a.200501.001.b2-8309f363.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-qq2a.200501.001.b2-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.)
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.
EDIT: Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have a 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 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.

Worked like a charm, just like previous months. 3 minutes total once the factory image was downloaded. (I edit the flash-all and remove the -w) Thanks a bunch!

Perfect method. Thank you.

[email protected] said:
perfect method. Thank you.
Click to expand...
Click to collapse
hi good day...
With this method can i activate motionsense and always leave it active?
I belong to a country where the factory does not come active and i would like to have it, only i have read that every time the telephone is re-enabled.
In advance thanks for the help.

I just used this Magisk file and after it boots up past the G logo - All i get is a black screen. the only thing that I can do is hold the power button and reboot to same result. I had to revert to factory boot to restore with no root. What am I missing? PS I just used step 8 and 9...
I am on the May update already///

aaronc_98 said:
I just used this Magisk file and after it boots up past the G logo - All i get is a black screen. the only thing that I can do is hold the power button and reboot to same result. I had to revert to factory boot to restore with no root. What am I missing? PS I just used step 8 and 9...
I am on the May update already///
Click to expand...
Click to collapse
It seems some of your previously installed modules/mods (using systemui) are interfering with the new update. I had the same issue a while back and eventually had to remove all Magisk modules and start afresh.

sidhaarthm said:
It seems some of your previously installed modules/mods (using systemui) are interfering with the new update. I had the same issue a while back and eventually had to remove all Magisk modules and start afresh.
Click to expand...
Click to collapse
That is the thing though. I was not rooted and I had uninstalled Magisk for the last several months. So now I wanted to root again, and followed steps 8 and 9 after installing Mag Manager. Could the sysemui mods you are referring to be from many months ago before when I uninstalled Magisk/

aaronc_98 said:
That is the thing though. I was not rooted and I had uninstalled Magisk for the last several months. So now I wanted to root again, and followed steps 8 and 9 after installing Mag Manager. Could the sysemui mods you are referring to be from many months ago before when I uninstalled Magisk/
Click to expand...
Click to collapse
Its' hard to say without knowing what is/was installed bud. In my case I had some mods that changed accent colours, fonts and clock positions etc. I learnt the hard way and always made sure that I remove such modules before upgrading. I just upgraded from April to May OTA and it all seems to have gone down well. Root restored, Face Unlock working and Kirisakura 4.5 flashed

sidhaarthm said:
Its' hard to say without knowing what is/was installed bud. In my case I had some mods that changed accent colours, fonts and clock positions etc. I learnt the hard way and always made sure that I remove such modules before upgrading. I just upgraded from April to May OTA and it all seems to have gone down well. Root restored, Face Unlock working and Kirisakura 4.5 flashed
Click to expand...
Click to collapse
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!

aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Yes, hang on, let me find the steps I took to fix.
---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------
aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Look at this post - https://forum.xda-developers.com/showpost.php?p=81926759&postcount=46
I had success following these instructions. There's some other posts I found on XDA where users had similar issue - this is the only way without having to fully wipe and restore.
Hope it helps!:good:

aaronc_98 said:
Ok - does anyone have any idea hot to solve this problem given the situation? I also did the May OTA recently with no issues. would I need to download the whole factory image to solve? Any other ideas?
I just tried to install the patched img again with the same results - black screen
Thank you in advance for any help!
Click to expand...
Click to collapse
Just curious, but are you fastbooting the patched.img via power shell or command prompt? And, are your platform-tools up to date, and are you using a USB A to C cable?

Badger50 said:
Just curious, but are you fastbooting the patched.img via power shell or command prompt? And, are your platform-tools up to date, and are you using a USB A to C cable?
Click to expand...
Click to collapse
Fastbooting from command prompt
Platform tools downloaded yesterday
Yes on the USB cable
---------- Post added at 10:42 PM ---------- Previous post was at 10:41 PM ----------
sidhaarthm said:
Yes, hang on, let me find the steps I took to fix.
---------- Post added at 10:36 PM ---------- Previous post was at 10:32 PM ----------
Look at this post - https://forum.xda-developers.com/showpost.php?p=81926759&postcount=46
I had success following these instructions. There's some other posts I found on XDA where users had similar issue - this is the only way without having to fully wipe and restore.
Hope it helps!:good:
Click to expand...
Click to collapse
Unfortunatey, it does not look like it is working for me, when I open an abd shell and then type su nothing happens. What is supposed to happen? The curorsor just move down to the next line.
This is of course after fastbooting the patched img and have the system ui crash (black screen)

Try booting in Magisk Core-Only mode. If it boots, it probably was an old module causing the issue. Then you can open Magisk Manager and try disabling modules until you find the problematic one, and remove it.
See this thread for more info: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I haven't had to boot into Magisk core mode yet on this device so I can't help you much. But according to Tulsadiver (OP of that thread), I believe he said the April boot image works fine for May (see pg 13).
Good luck!

i5lee8bit said:
Try booting in Magisk Core-Only mode. If it boots, it probably was an old module causing the issue. Then you can open Magisk Manager and try disabling modules until you find the problematic one, and remove it.
See this thread for more info: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
I haven't had to boot into Magisk core mode yet on this device so I can't help you much. But according to Tulsadiver (OP of that thread), I believe he said the April boot image works fine for May (see pg 13).
Good luck!
Click to expand...
Click to collapse
Unfortunately, I dont think that i can do this since it says you must be rooted for either method. The problem is that I am not rooted and have not been for some time, but now i am trying to root via magisk...

aaronc_98 said:
Unfortunately, I dont think that i can do this since it says you must be rooted for either method. The problem is that I am not rooted and have not been for some time, but now i am trying to root via magisk...
Click to expand...
Click to collapse
Try flashing the May Magisk patched boot image (which will root the phone), then fastboot boot image-new.img (NOT FLASH), the image Tulsadiver shares in his OP: https://androidfilehost.com/?fid=4349826312261766039 - don't worry the device says Pixel XL in AFH - he probably just uploaded it to an old folder of his. It's definitely the 4 XL core only boot image.
This should start up your phone rooted, but with all modules disabled.
Edit: also, I'm pretty sure he's referring to needing root in order to follow his processes and use those methods to generate the core-only boot image itself. However, he provides the bootable image for you luckily. Either way, I would still flash the May Magisk patched boot image first, otherwise when you reboot after booting core mode it'll just boot back into the existing boot file (in your case, stock). Also, I just tested for you, and that image-new.img works perfectly fine. I just tried it on my phone and it booted into core mode, exactly as if I did it through Magisk Manager. I also didn't need to use the additional script or delete the .disable_magisk file in the /cache folder - all I needed to do was uncheck core only mode in Magisk Manager. YMMV. I would also recommend installing Magisk Manager .apk before any of this to make your life easier.
So for you:
1. Install Magisk Manager if you haven't already - https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
2. Reboot into bootloader
3. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
4. fastboot boot image-new.img
5. Hopefully the O/S loads, open Magisk Manager, disable offending modules.
6. In Magisk Manager, go to settings and uncheck "Magisk Core Only Mode" option.
7. Reboot.

i5lee8bit said:
Try flashing the May Magisk patched boot image (which will root the phone), then fastboot boot image-new.img (NOT FLASH), the image Tulsadiver shares in his OP: https://androidfilehost.com/?fid=4349826312261766039 - don't worry the device says Pixel XL in AFH - he probably just uploaded it to an old folder of his. It's definitely the 4 XL core only boot image.
This should start up your phone rooted, but with all modules disabled.
Edit: also, I'm pretty sure he's referring to needing root in order to follow his processes and use those methods to generate the core-only boot image itself. However, he provides the bootable image for you luckily. Either way, I would still flash the May Magisk patched boot image first, otherwise when you reboot after booting core mode it'll just boot back into the existing boot file (in your case, stock). Also, I just tested for you, and that image-new.img works perfectly fine. I just tried it on my phone and it booted into core mode, exactly as if I did it through Magisk Manager. I also didn't need to use the additional script or delete the .disable_magisk file in the /cache folder - all I needed to do was uncheck core only mode in Magisk Manager. YMMV. I would also recommend installing Magisk Manager .apk before any of this to make your life easier.
So for you:
1. Install Magisk Manager if you haven't already - https://github.com/topjohnwu/Magisk/releases/tag/manager-v7.5.1
2. Reboot into bootloader
3. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
4. fastboot boot image-new.img
5. Hopefully the O/S loads, open Magisk Manager, disable offending modules.
6. In Magisk Manager, go to settings and uncheck "Magisk Core Only Mode" option.
7. Reboot.
Click to expand...
Click to collapse
Thank you! You are my hero! Thank you for taking the time to explain this- everything is working as expected

aaronc_98 said:
Thank you! You are my hero! Thank you for taking the time to explain this- everything is working as expected
Click to expand...
Click to collapse
Glad it worked out for you. Make sure you thank Tulsadiver for his work too, his core-only guide is totally clutch
I'm gonna edit the OP for some basic steps in case of errors. Thanks for keeping us posted.

i5lee8bit said:
Another month, another update. I'll keep churning out these patched / stock file uploads and easy noob-friendly update guides while guinea pigging the updates, so long as my area is still on lockdown and I'm not back to work yet, lol.
Click to expand...
Click to collapse
Thanks for the patched kernel. I usually patch the kernel before I flash the update so I can boot with a patched kernel after the update. I was distracted and forgot. You saved me bunch of extra work!

Little hint from a Xperia 5 User.
use: fastboot --set-active=b
To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.
use: fastboot --set-active=a
To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.
BR
---------- Post added at 16:44 ---------- Previous post was at 16:43 ----------
Little hint from a Xperia 5 User.
use: fastboot --set-active=b
To change to the B System and repeat the Steps for the Kernel flashing. Magisk likes that to survive OTA Updates.
use: fastboot --set-active=a
To change back to the Primary System and boot up. Install Magisk Manager and You are good to go! System Images are flashing in both Slots without the need to do that. But Kernels have to be flashed in both Slots if they are changed. Figured that out by inspecting some Zips who are Magisk and Kernel related.
BR

[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

Question "Your device is corrupt" after November Update with Magisk OTA method.

I followed this guide exactly: https://topjohnwu.github.io/Magisk/ota.html
Before starting the guide, I had a pretty new Pixel 7 Pro with the latest version of Magisk successfully installed (with bootloader UNLOCKED) and some small Magisk modules to tweak things (iOS emojis). I made sure to restore boot images and got the "restoration complete" toast message.
I saw the notification for the November update, downloaded and installed it. I did NOT reboot after that. I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
My device rebooted, and showed me the bootloader unlocked screen, then showed me the "your device is corrupt" warning and said "press power button to continue". I pressed the power button and my device is now stuck on the Google logo.
Has this happened to anyone else? And is there any way to fix this (preferably without data loss)?

Pritster5 said:
I followed this guide exactly: https://topjohnwu.github.io/Magisk/ota.html
Before starting the guide, I had a pretty new Pixel 7 Pro with the latest version of Magisk successfully installed (with bootloader UNLOCKED) and some small Magisk modules to tweak things (iOS emojis). I made sure to restore boot images and got the "restoration complete" toast message.
I saw the notification for the November update, downloaded and installed it. I did NOT reboot after that. I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
My device rebooted, and showed me the bootloader unlocked screen, then showed me the "your device is corrupt" warning and said "press power button to continue". I pressed the power button and my device is now stuck on the Google logo.
Has this happened to anyone else? And is there any way to fix this (preferably without data loss)?
Click to expand...
Click to collapse
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.

I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?

Freak07 said:
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
Click to expand...
Click to collapse
Glad you're on our forum Freak!

Pritster5 said:
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?
Click to expand...
Click to collapse
Remove "-w" from the flashall.bat, I believe that ensures you keep data.

I'm also a bit confused by this step: "flash it via fastboot on your device with nov firmware." Are you saying that I should flash october init_boot.img onto my phone, which already has the Nov firmware installed? Or do I have to merge the Oct init_boot.img into the Nov firmware (full factory image TD1A.221105.001)

Pritster5 said:
I'm also a bit confused by this step: "flash it via fastboot on your device with nov firmware." Are you saying that I should flash october init_boot.img onto my phone, which already has the Nov firmware installed? Or do I have to merge the Oct init_boot.img into the Nov firmware (full factory image TD1A.221105.001)
Click to expand...
Click to collapse
yes, you flash the old outdated init_boot via fastboot on november firmware.
afterwards you flash back the correct one for november. that will hopefully clear the avb bug you´re experiencing.
You flash only this img, not anything else. do precisely the steps I described. you don´t have to flash the full firmware, as you already updated to november if I read your initial post correctly and OTA to november was successful.
Pritster5 said:
I see. Thank you so much for this info. I will try and report back my results. Has this bug been fixed in newer versions of Magisk or Android? I feel like it's a high priority bug given that it soft-bricks peoples devices.
EDIT: And does this process result in data loss?
Click to expand...
Click to collapse
no it has not been fixed.
no, with the steps detailed there´s no data loss.
I wouldn´t recommend updating your phone with the magisk flash to inactive slot method. That´s not working for most people on p6 and p7 devices.
Pain-N-Panic said:
Remove "-w" from the flashall.bat, I believe that ensures you keep data.
Click to expand...
Click to collapse
the method I described doesn´t involve using that script. no data will be lost.

I then went into the Magisk app and tapped "install to inactive slot (after OTA)" and rebooted from within the Magisk app.
Click to expand...
Click to collapse
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61

Freak07 said:
yes, you flash the old outdated init_boot via fastboot on november firmware.
afterwards you flash back the correct one for november. that will hopefully clear the avb bug you´re experiencing.
You flash only this img, not anything else. do precisely the steps I described. you don´t have to flash the full firmware, as you already updated to november if I read your initial post correctly and OTA to november was successful.
no it has not been fixed.
no, with the steps detailed there´s no data loss.
I wouldn´t recommend updating your phone with the magisk flash to inactive slot method. That´s not working for most people on p6 and p7 devices.
the method I described doesn´t involve using that script. no data will be lost.
Click to expand...
Click to collapse
devsk said:
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61
Click to expand...
Click to collapse
If what @devsk states is true, you also need to flash back stock boot.img from november firmware via fastboot @Pritster5.
fastboot flash boot boot.img
Since magisk can patch init_boot.img´s, I assumed it would account for pixel 7 pro, having ramdisk inside init_boot instead of boot.img. It´s a bad design choice by magisk app to show this option to users on Pixel 7 pro in that case. :/ but even on pixel 6, the forums are full of people running into issues with that method.

devsk said:
How do you expect this to work for p7p? The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition.
Update Magisk using the method outlined in the main thread for OTA and Magisk: https://forum.xda-developers.com/t/...-safetynet-all-relevant-links.4502805/page-61
Click to expand...
Click to collapse
Where can I see what devices are supported for that method? I assumed that the guide worked for anyone with A/B partitioning. It would be helpful if there was a notice of this somewhere on the guide or any other obvious place.

The easiest way to recover is to follow that guide and flash the whole ROM (it will fix both the boot and init_boot partitions). *Make sure* to remove -w from the flash-all.bat or flash-all.sh, whichever one you are using. This part is important. "-w" command line argument wipes your data and you don't want that.
I just updated my p7p using this method this afternoon and it worked fine.

Pritster5 said:
Where can I see what devices are supported for that method? I assumed that the guide worked for anyone with A/B partitioning. It would be helpful if there was a notice of this somewhere on the guide or any other obvious place.
Click to expand...
Click to collapse
That link is specifically for p7p

devsk said:
That link is specifically for p7p
Click to expand...
Click to collapse
Oh I meant where can I see what devices support the Magisk "Install to inactive slot" guide.
You said "The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition."
How are you aware of this? Did you find this out by reading the code itself or was there a notice of this somewhere?

Pritster5 said:
Oh I meant where can I see what devices support the Magisk "Install to inactive slot" guide.
You said "The Magisk code has not been updated yet to flash init_boot partition instead of boot partition on p7p. Of course, it will corrupt your boot partition."
How are you aware of this? Did you find this out by reading the code itself or was there a notice of this somewhere?
Click to expand...
Click to collapse
Actually, this got me thinking and I looked at the code. Looks like the magisk code (the bash function find_boot_image) seems to be doing the right thing by treating init_boot ahead of boot partition.
Do you have the logs from that run of "Install to inactive slot"?

devsk said:
Actually, this got me thinking and I looked at the code. Looks like the magisk code (the bash function find_boot_image) seems to be doing the right thing by treating init_boot ahead of boot partition.
Do you have the logs from that run of "Install to inactive slot"?
Click to expand...
Click to collapse
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
EDIT: Should I just use the Android flash tool instead if I don't have access to ADB? Or should I instead just follow Freak07's steps since his steps don't require adb access?

Pritster5 said:
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
Click to expand...
Click to collapse
Just restore your device by flashing the whole ROM. This will get rid of magisk and you should have no problem booting back into the system. You will have lost the root at that point. Once inside, transfer the init_boot.img into /sdcard and run magisk and ask it to patch that. Bring the patched file to your PC, and flash it to init_boot partition like the guide says. At that point, you should be able to boot back into the system and root should be good.
I did not disable Magisk modules and it worked fine. I have magiskhide props, shmiko, systemless hosts, zygisk - lsposed, universal safety net fix.
If you have trouble with Magisk modules, you can recover by booting into Safe Mode (restart and press down volume and keep it pressed). Magisk detects the Safe Mode and disables the modules. Done that many times.

Pritster5 said:
I don't believe so, as I can only connect to my phone via PC over fastboot mode right now, so I'll have to check for logs after fixing my device.
One other question though, the guide you linked mentioned disabling magisk modules before flashing the factory image. I was never able to do that because I used the inactive slot guide which made no mention of it. Will the enabled magisk modules prevent me from using the guide you linked?
I am also unable to do this step as I can't transfer files from my pc to my p7p when I cant access the phone aside from fastboot mode: "Copy the init_boot.img from the PC to the phone's internal storage." Can I skip this step?
EDIT: Should I just use the Android flash tool instead if I don't have access to ADB? Or should I instead just follow Freak07's steps since his steps don't require adb access?
Click to expand...
Click to collapse
in the end it doesn´t matter how you do it.
Flashing the complete firmware with -w removed or using the web flasher might be easier as it´s kind of a one click solution.
However simply flashing entire november firmware, might not get you out of the avb corruption loop. It might but, but it might not depending on what went wrong. If it´s the bug that I think it is, avb gets cleared when flashing an older outdated init_boot.img.
You can try to just flash the entire nov firmware with any of the methods suggested. If it doesn´t clear the avb corruption bug, flash back older init_boot from oct firmware, followed by current init boot as I originally suggested.

Freak07 said:
That´s a bug within AVB. Unfortunately it can happen on Pixel 6 and 7 devices.
There´s one thing that can clear it:
I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still.
Then download november factory image, extract init_boot.img, flash it via fastboot as well. This might get you out of the loop.
If you want you can use a magisk_patched init_boot.img as well so you´re rooted.
That last step should get you out of the corruption loop, as flashing outdated init_boot and then correct init_boot will somehow clear avb.
I´ll attach patched init_boot.img from november firmware TD1A.221105.001, Nov 2022 for you.
Click to expand...
Click to collapse
Ok so I did this part:
"I know this sounds a bit counter intuitive, but download october factory image, extract init_boot.img, flash it via fastboot on your device with nov firmware.
fastboot flash init_boot init_boot.img
Try to let it boot, if it fails or crashes go back to bootloader via long press power and volume down. (can take up to 30 seconds on p7pro)
If it boots already don´t forgot to flash init_boot from november firmware still."
And it works, however when I go to "About Phone" the build number is still the October version. Is this expected, given that I flashed the october init_boot.img onto a phone with November firmware? Or did my phone perhaps reboot into the older partition which the phone ran before switching to the inactive slot?
EDIT: Even after flashing the november init_boot.img after temporarily reverting to the october init_boot.img, it's still showing that I have build TD1A.220804.031 installed.

"followed by current init boot as I originally suggested."
Should I reboot back into fastboot mode again to do this?
Thank you guys so much for the help so far btw, I'm already back up and running and just need to finish the steps you mentioned.

@devsk Here are the logs you wanted:

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.