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

[Help] Updating to Android 11 while preserving root

I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?

SirHappyCatIII said:
I have a Pixel 3a that had Magisk installed and it has been rooted for a while. I want to upgrade to Android 11 but in Magisk Canary there is no option to install Magisk into the inactive slot. Am I missing a button somewhere or what?
Click to expand...
Click to collapse
I'm assuming youre still on 10 right? Follow the steps on magisk's github

Roarmaster said:
I'm assuming youre still on 10 right? Follow the steps on magisk's github
Click to expand...
Click to collapse
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.

SirHappyCatIII said:
The issue is that those steps are for the stable magisk build, but as far as I can tell only Magisk Canary supports android 11. The issue being that Magisk Canary doesn't seem to have a button to install magisk into the inactive slot after downloading the update.
Click to expand...
Click to collapse
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again

Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Alright, I was hoping to avoid the manual route, but I'll try it, thanks.

Roarmaster said:
I see, well you can also do it the manual way (which is what I did).
- First search for the factory image for the pixel 3a Android 11 September.
- Download that on your computer, unzip it, and look for the boot.img
- Transfer that boot.img file to your phone and patch it with magisk (install > patch file > boot.img)
- Transfer that magisk-patched.img back to your computer
- Download ADB for your computer
- After updating your phone to android 11, reboot to fastboot mode after checking that USB debugging is enabled in developer settings
- on your computer check if ADB is connected: "fastboot devices"
- if you see a device there, go to the next step
- using ADB, enter the following in your terminal: "fastboot flash boot your-magisk-patched-boot.img"
- you're now rooted again
Click to expand...
Click to collapse
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.

SirHappyCatIII said:
Well I've tried patching the boot image and flashing 3 times now to no avail. To be clear I updated to android 11, installed the latest canary magisk manager, downloaded stock images for pixel 3a, took the boot.img from the stock images, and patched it with magisk. Now when I try to flash the patched image I get infinite G logo.
Click to expand...
Click to collapse
In magisk manager, set the update channel to Canary before you patch the boot.img file

captain sideways said:
In magisk manager, set the update channel to Canary before you patch the boot.img file
Click to expand...
Click to collapse
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.

SirHappyCatIII said:
It is set to canary and I am on version d6dbab53. I'm going to downgrade to android 10 for now I suppose, I'm not sure what else I can do other than wait for stable magisk to support Android 11.
edit: seems like downgrading to android 10 required a device wipe. I might just need to live without root until I can get this to work.
Click to expand...
Click to collapse
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process ? let me know...
http://bit.ly/magiskcanarymanagerxda

captain sideways said:
It deffo works - start with a clean slate and do it step by step - I do this all the time and it does work.
Right so:
Flash a clean boot.img from the stock firmware files so your phone will boot.
When it boots, uninstall magisk manager all together and reboot.
Install the Magisk Manager linked below (confirmed working)
Set the update channel to Canary and reboot just to be sure. Open manager and see there is an update available to manager so update it and reboot.
Now copy the clean boot.img to your phone's download folder.
In manager, install magisk by selecting and patching the boot.img
Copy the resulting magisk_patched.img to your computer's adb folder.
Open command prompt as administrator and navigate to your adb folder so your prompt should reads C:/adb
At the prompt, type:
adb reboot bootloader
With your phone now in bootloader at your prompt, type:
fastboot flash boot magisk_patched.img
When it completes, start your phone. This is how I do and I've done it loads of times and I boot first time.
I have a few extra reboots in there and you can do it with less, but it just keeps every thing clean and fresh and in place while you master the process let me know...
http://bit.ly/magiskcanarymanagerxda
Click to expand...
Click to collapse
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.

SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked

Update: I wiped my entire phone, flashed stock images, and tried again. It worked first try. Maybe it had something to do with a module I had installed? No idea. Thanks for the help though everyone.
another update: seems like one of the modules i installed (probably riru edxposed?) stops the phone from booting. Time to wipe everything and try again yayyyy.

captain sideways said:
Ah OK, I'm sorry to hear that, I really am out of ideas now but hope you manage to get it sorted if you do, let me know cos I'll be wondering about it now trying to work it out ?
Did all of the steps work apart from your phone booting? Have a look at the file size of your magisk_patched.img in windows explorer, does it report as 0kb? That happened to me one time so I just did the whole process again and then it worked
Click to expand...
Click to collapse
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.

SirHappyCatIII said:
I think the Rira - EdXPosed module in magisk is what was stopping it from booting. I wiped my phone and restarted everything and installing magisk worked first try. As soon as I installed EdXposed and rebooted I got infinite G logo.
Click to expand...
Click to collapse
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone ? glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module ?

captain sideways said:
Ah lush, right, OK that makes sense
I've not used exposed since I had the moto x play (years ago) so don't have that on my phone glad you worked it out, it's good knowledge to have for the future
For reference, you don't need to wipe your phone, just flash the stock boot img then you can go into magisk manager and remove the offending module
Click to expand...
Click to collapse
Haha wish I knew that 3 hours ago. I don't know why I didn't think to just remove the module.

I know, it's a pain in the ass but you'll remember for the future?

SirHappyCatIII said:
I followed these steps exactly, and I have waited 15 minutes at the G logo. Nada. Not sure why it won't work, but I guess I will just need to live with it for now. Flashing stock boot image makes the phone boot again, but without magisk obviously.
Click to expand...
Click to collapse
I had issues also, rename the magisk_patched.img to boot.img, after I did that it booted and was rooted

Just an FYI, you can now set the update channel to beta and get the version of Magisk that supports android 11.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

How To Guide Rooting the Google Pixel 6a

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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