Database Info

[Guide] Install Magisk on your device, updated to handle OTAs easily

[Update in 1st September 2018] Magisk v17 stable has been released, so the August security update: a new method, more OTA-compliant, is written.
Hi all, this section is quite gaunt, so I'll post my experience on unlocking and rooting my brand new Mi A2 Lite.
I'm not responsible if you make some mistake and accidentally transform your phone in a stone (but it's almost impossible)... <3
How to root
0. You need "debug usb" and "oem unlock" enabled under "developer options" on phone's settings.
1. First, if you don't have already done it, unlock phone's bootloader:
Code:
adb reboot bootloader
fastboot oem unlock
ATTENTION: THIS WILL WIPE YOUR DEVICE, ALL USER DATA WILL BE LOST! And no, when you'll have finish this guide, you can't lock it again (each lock-unlock operation will wipe the device)
2. Download ROM system image from official site. Pay attention to download the corresponding version of your actual OS (look in system settings your current build number).
3. Extract "boot.img" from the just downloaded archive and put somewhere in your device (e.g. in a microSD, just remember where you put it).
4. Download and install Magisk Manager apk.
5. Open Magisk, choosing "yes" when it asks to install Magisk-v*.zip, then choose "patch boot image" and select "boot.img" copied in step 3.
6. At the end of patching process, Magisk will tell you where "patched_boot.img" is been stored, keep a note on it and close.
Now's the updated part, that will make possible to apply OTAs:
7. Copy "patched_boot.img" on your computer, then run this on a terminal:
Code:
adb reboot bootloader
fastboot boot patched_boot.img
fastboot reboot
This will temporarily give you root privileges (until next reboot).
8. Magisk Manager can now make the root permanent: open it and tap "Install", then "direct install (recommended)". This way (instead of flashing directly patched_boot.img) Magisk Manager can remove and reinstall root privileges directly.
9. Just to be sure that your phone doesn't install updates without your acknowledgement, go to Developer Options and disable "Automatic system updates".
Ta-dà! Now you should have Magisk permanently installed (you can check it re-opening Magisk Manager).
-------------------------------------------------------
Time to update? Here's how
If you've followed what is written above, applying an OTA should be quite easy now.
a. Go to Magisk Manager → Uninstall → Restore Images. Do not reboot now or you will have Magisk uninstalled!
b. Now go to Settings → System → System Update and apply OTA. If it fails you've some tweak on system partition that you've forgot to remove, so try to figure it out and retry. Wait for the installation to complete. DO NOT RESTART NOW.
c. Open Magisk Manager again and press Install → Install to Inactive Slot.
d. Reboot and enjoy
-------------------------------------------------------
Troubleshooting
- If your phone seems bootlooping, try to switch it off and on again (sometimes it doesn't start on first boot). If it keeps doing that, donnoh, reflash original "boot.img" and start again!
- For someone seems that Magisk 16 doesn't work well, but since the stable branch has reached 17.0, just use it!
- If you already have rooted your phone in different ways that this one explained here (and you don't have "uninstall" option on Magisk Manager), I suppose that the simpliest way to follow this guide is to reflash factory boot.img and start from the beginning of this post again, but if you figure out alternative ways, post them here!
-------------------------------------------------------
References
https://forum.xda-developers.com/mi-a1/how-to/mi-a1-monthly-updates-t3750419
https://forum.xda-developers.com/showpost.php?p=77448469&postcount=49
https://forum.xda-developers.com/mi-a1/how-to/root-mi-a1-oreo-8-0-disabling-ota-magisk-t3728654
https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
Thanks to BubuXP for the efforts that he puts in this thread, helping anyone who's got problem following this guide.
Have a nice day!

If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).

few minutes has past and Im looking here at endless boot animation:/
so I do fastboot factory flash, did it again and now no issues at all,thanks!

BubuXP said:
If you posted this a couple of hours early, I'd save a couple hours of my life doing other things instead of discovering by myself what you just wrote :laugh:
However, add to your guide to change the update channel in Magisk Manager to "beta" instead of stable, because only starting from 16.7 (the actual beta version) has support to A/B partitions scheme (the one used by our device). When the new stable version of Magisk will be released, that could be removed.
Add also that installing modules isn't possible out of the box, because both Magisk Manager and Android stock lack the unzip binary (I'm searching for a solution).
Click to expand...
Click to collapse
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote

I had another ROM installed,It was more "light" than this one posted here. Many google app was added after I did flash. My phone should be global version and I buy it from local store. It was ODLMIFF also.
edit:seems that screen cast is not working

kidoucorp said:
That's weird, (saw also your message in the other thread)I didn't had all these issues and I'm using magisk 16.0 (no beta). I could also install modules out of the box without having to do anything special
Edit : added quote
Click to expand...
Click to collapse
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 XL forum that fixes some weird behaviors other users had., I will try it too.
EDIT 1: I usually do all my operations under Debian Linux. This time I used the Mi Flash tool under Windows, and I patched the boot.img with 16.0.
I don't know what of the two changes fixed the problem, but now it's working without problems (but the first time I tried directly with your boot.img patched with 16.0 and it was not working ).
FYI, sha512 of the old and new fastboot image downloaded were the same, so it was not a problem of defective download.

BubuXP said:
That's weird indeed...
I've re-downloaded the fastboot image and I'm flashing it right now, then I will retry patching boot.img
I found an updated 16.7 version in the Pixel 2 forum that fixes some weird behaviors other users had., I will try it too.
Click to expand...
Click to collapse
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:

mik.y said:
Im using 16.0. Also phone sometimes wont boot, stuck at screen with unlocked text or stuck in boot animation. I guess xiaomi is very wrong choice for somebody who want customize his android:laugh:
Click to expand...
Click to collapse
I edited my previous post, just to inform you.
I think those problems arise because the phone is too young, many things have to be fixed by Xiaomi. And also things will get better when the new stable Magisk that will support new Android features will be released.

1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that

I'm not sure, but apparently I found the culprit.
The only way to make Magisk work flawlessly is following the guide in the first post.
I mean, if I use the patched_boot.img made in another phone it causes always some problems, as if Magisk in the process of patching the boot.img put a signature of the actual phone inside the img and it will work fine only in the same phone that created the patched boot.img
Not only this, but if I flash the phone with the stock ROM via fastboot, and then use the patched_boot.img created previously on the same phone before flashing, it won't work neither (something in the "signature" changes, like it is a new phone).
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).

BubuXP said:
Probably using the beta channel with 16.7 could improve your situation. I'm using 16.7 right now, following the OP guide, and it is working great (until now).
Click to expand...
Click to collapse
I can confirm that I'm using Magisk stable 16.0, and everything works fine, but I suppose it's because I've flashed booth partition A and B. I've updated the first post anyway, thanks!
kidoucorp said:
1st time it bootlooped, I got the screen "Android can't boot, retry or factory reset?". I pressed retry and it booted.
The only bug I'm facing is reboot from the power menu is not working, it never boots (bootloop). Shutdown then start the phone work perfectly. I can live with that
Click to expand...
Click to collapse
My old Mi A1 does the same too, it's a bit strange but once you know it, you can handle it

It works !!
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.

eddiechanks said:
Device: Mi A2 Lite (4/64GB) global version.
(cpu-z reports: Snapdragon 626 @2.02 GHz)
Using Magisk 16.7 and boot.img from global rom "V9.6.4.0.ODLMIFF (Android O) " (oem rom from xiaomi).
Only difference is the method which I tried and fail initially, was I cmd "adb reboot bootloader" from the PC which doesn't work for me.
It says failed to write boot_a and boot_b.
I had to do the hardware reset to get into fastboot. (pressing vol-down and power button simultaneously).
Once I am in fastboot mode, from the PC cmd execute the following sequence
1. fastboot flash boot_a patched_boot.img
2. fastboot flash boot_b patched_boot.img
3. fastboot reboot
And voila!, it works beautifully. Thanks for all the contributors of this thread
It runs all apps including apps that cannot be rooted. (have to do the "hide" magisk)
So far so good, no issue to be found.
Have a great day people.
Click to expand...
Click to collapse
Same for me. Just extract the boot.img from the official Xiaomi rom (downloadable from their website), patch that through Magisk manager, and flash the patched .img to boot_a and boot_b using fastboot. Works flawlessly.
Only thing I haven't been able to do is remove the forced encryption. I was able to change the encryption password however using vdc cryptfs.

worked flawlessly, did have to re-install magisk manager after flashing the patched boot images, but all was fine after a quick apk reinstall.

Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !

arnofor said:
Hi guys,
Sorry for those newbie questions (I come from an old Nexus 5 with Lineage, and I am far from magisk) :
How is going the update ? will it be OTA ? Will it be manual (in this case where do I find the file) ? Do we need to re-root after OS update ?
Thanks in advance !
Click to expand...
Click to collapse
The OTA update should be automatic, but I'm not sure 100%
However, after every system update, you have to do the boot patching procedure again but using the boot.img from the new version.

Can I do the unlock part and the rest in a couple of weeks? Without data loss?

ncar123 said:
Can I do the unlock part and the rest in a couple of weeks? Without data loss?
Click to expand...
Click to collapse
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?

BubuXP said:
You can unlock whenever you want, but every time the bootloader is locked or unlocked, the phone resets its data (but I'm not 100% sure, maybe it's only locking or only unlocking).
But why unlocking now and wait 2 weeks? Couldn't you unlock the phone directly in 2 weeks when you are ready?
Click to expand...
Click to collapse
I don't want to setup my phone with my data twice...

ncar123 said:
I don't want to setup my phone with my data twice...
Click to expand...
Click to collapse
So it's ok. Unlock now while you don't have any data in the phone and whenever you want, you can install Magisk later.

January 2020 updates are out

January 2020 updates are out
https://support.google.com/pixelphone/thread/24852169?hl=en
Notable fixes in the attachment.

How about the boot image patched with root?

Interested in a pre-patched as well, tried doing my so my self like past updates and was unbootable

What's the deal with the TMO/Fi builds?

Still haven't gotten Dec OTA on TMO

I downloaded within 60 seconds of it being released, unzipped and patched boot.img with magisk, flashed (without -w), flashed boot, and everything is GOOD. So much smoother than whatever the hell happened in December. One of the fixes they listed was "Fix for devices stuck during boot on Android 10" so I assume that was them breaking it in December
I flashed the TMO/Fi version because I'm on Fi. No idea why they split it up, does our phone have a 5G radio?

That's weird, I wonder if it's because of me skipping December. Generally I can do the same but even after full wiping I can't boot a patched boot I made.

Posted boot unpatched in thread in guides

Here is the patched boot
This is the patched boot image for Jan 2020 (ATT or VZW or Sprint)....NOT TMO or GoogleFi!
I used magisk to patch it. So if you are on any of the 4 carriers EXCEPT TMO, this should work just fine. After rebooting and system update gets applied, reboot into bootloader.
copy the image file into your adb folder and then flash it as follows:
fastboot flash boot magisk_patch.img (and note that you must have installed platform tools and the fastboot driver on Windows for this to function)
You can download the full OTA for any carrier at : https://developers.google.com/android/ota (and select crosshatch files and the Jan file for your carrier (first one build 002 is for VZW/ATT/SPR, 003 for TMO/GoogleFi)
Make sure to unzip the attachment! http://www.filedropper.com/magiskpatched

**UPDATE - Figured out. Installed Nova Launcher from web version of play store on my Pixelbook to Pixel 3 XL - that gave me a little more time between app closing pop-up to search for Pixel Launcher in actual Play Store on phone to uninstall updates and reinstall.
Updated from the November patch and Pixel Launcher keeps stopping. Looked for update in Play Store (challenging because of the app stopping loop) and nothing ... any suggestions? other than wiping the phone

Do not wipe System
JaceAlvejetti said:
That's weird, I wonder if it's because of me skipping December. Generally I can do the same but even after full wiping I can't boot a patched boot I made.
Click to expand...
Click to collapse
The OTA files are cumulative and do not need to apply December. If you are doing this correctly, you should be booted into recovery (android default not twrp) and issue the following
command: adb sideload myfilename.zip (this should be an OTA that is about 1.3GB in size). Wiping Data is unnecessary too.
---------- Post added at 07:55 PM ---------- Previous post was at 07:51 PM ----------
JaceAlvejetti said:
Interested in a pre-patched as well, tried doing my so my self like past updates and was unbootable
Click to expand...
Click to collapse
1) Make sure you have ADB and Fastboot installed along with the driver for Windows Fastboot interface.
2) Reboot the phone into normal recovery.
3) You should see a robot with it saying "no command"
4) Press Power and Volume up together for a few seconds
5) From the menu, move to adb sideload choice with volume keys
6) from a command window in Windows, where your adb files are located,
adb sideload ota-file-name-here.zip (you should start the command window elevated as Administrator)
7) reboot normally and let the system apply the update.
8) reboot into bootloader
9) fastboot flash boot magisk_patched.img
10) Profit

While I thank you for the tutorial, I am up and running after a sad wipe, I figured it may have been caused by an errant magisk add-on but without twrp I had no way to pull it back, after wiping I'm alive again, though I will give adb sideload a try in the future, I have been using flashall without the -w wipe since getting my p3 for every update, I'll go check the other thread for a 003/tmo-fi magisk. Sidenote os is Linux, what are these windows and command windows you speak of? Are they like terminals, elevated as Administrator is that root? I kid, I appreciate you trying to help!, I was planning a wipe eventually anyway to clean the system out, this just pushed it ahead.

JaceAlvejetti said:
While I thank you for the tutorial, I am up and running after a sad wipe, I figured it may have been caused by an errant magisk add-on but without twrp I had no way to pull it back, after wiping I'm alive again, though I will give adb sideload a try in the future, I have been using flashall without the -w wipe since getting my p3 for every update, I'll go check the other thread for a 003/tmo-fi magisk. Sidenote os is Linux, what are these windows and command windows you speak of? Are they like terminals, elevated as Administrator is that root? I kid, I appreciate you trying to help!, I was planning a wipe eventually anyway to clean the system out, this just pushed it ahead.
Click to expand...
Click to collapse
You need to remove magisk modules before you update in the future. They will often cause issues even if you are doing the flash all method. I would also suggest you follow the below. No patching or flashing needed.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).

TonikJDK said:
You need to remove magisk modules before you update in the future. They will often cause issues even if you are doing the flash all method. I would also suggest you follow the below. No patching or flashing needed.
https://topjohnwu.github.io/Magisk/tutorials.html#ota-installation).
Click to expand...
Click to collapse
Remove or just disable? Would switching to core only mode be enough? I will use the factory image not OTA. I cannot get OTAs where I live.
Edit: Nevermind, just bit the bullet and tried. Disabling them is enough. Only thing that broke was Viper4Android.
Disable all modules
Reboot system
Reboot bootloader
Flash-all minus the -w
Reboot bootloader
Flash magisk_patched.img
Re-enable modules

wangdaning said:
Remove or just disable? Would switching to core only mode be enough? I will use the factory image not OTA. I cannot get OTAs where I live.
Edit: Nevermind, just bit the bullet and tried. Disabling them is enough. Only thing that broke was Viper4Android.
Disable all modules
Reboot system
Reboot bootloader
Flash-all minus the -w
Reboot bootloader
Flash magisk_patched.img
Re-enable modules
Click to expand...
Click to collapse
Agreed about disabling modules, but it also doesn't hurt to go back to stock boot before a flash-all since you are going to have to redo root and kernel anyways. As for Viper4Android, the one Audio Modification Library module was updated a week or so ago, so if you hadn't already updated that module pulling it back down would have broke V4A. I had to uninstall all of the modules and the V4A app and start the process again of installing, but it did come back with the new Audio Mod module.

sliding_billy said:
Agreed about disabling modules, but it also doesn't hurt to go back to stock boot before a flash-all since you are going to have to redo root and kernel anyways. As for Viper4Android, the one Audio Modification Library module was updated a week or so ago, so if you hadn't already updated that module pulling it back down would have broke V4A. I had to uninstall all of the modules and the V4A app and start the process again of installing, but it did come back with the new Audio Mod module.
Click to expand...
Click to collapse
Modules were all up to date. I actually clicked to remove the Audio Modification Library and the V4A modules (without reboot) and then ran the V4A app driver install to reboot. When it rebooted everything worked. I now have V4A working and no Audio Modification Library module.

wangdaning said:
Remove or just disable? Would switching to core only mode be enough? I will use the factory image not OTA. I cannot get OTAs where I live.
Edit: Nevermind, just bit the bullet and tried. Disabling them is enough. Only thing that broke was Viper4Android.
Disable all modules
Reboot system
Reboot bootloader
Flash-all minus the -w
Reboot bootloader
Flash magisk_patched.img
Re-enable modules
Click to expand...
Click to collapse
Should you try "fastboot flash boot --slot all magisk_patched.img" to ensure both slots are patched?

wangdaning said:
Modules were all up to date. I actually clicked to remove the Audio Modification Library and the V4A modules (without reboot) and then ran the V4A app driver install to reboot. When it rebooted everything worked. I now have V4A working and no Audio Modification Library module.
Click to expand...
Click to collapse
Good deal. I am on Havoc myself, so I hadn't messed with yesterday's update except to u[date my wife's P3.

Tekken Lord said:
Should you try "fastboot flash boot --slot all magisk_patched.img" to ensure both slots are patched?
Click to expand...
Click to collapse
I did do that.

wangdaning said:
I did do that.
Click to expand...
Click to collapse
There are several Magisk versions. I am using the latest Canary Debug (20.3.242xxxx), and never have any issue.

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

[UPDATE/KEEP ROOT GUIDE] AUG 2020 (QQ3A.200805.001) "CORAL" Magisk/Stock Boot Images
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!
Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the August 2020 (QQ3A.200805.001) update.
**IT IS HIGHLY RECOMMENDED TO PATCH THE STOCK BOOT IMAGE YOURSELF, FROM YOUR OWN DEVICE, USING MAGISK MANAGER. WHILE THERE'S A GOOD CHANCE THE FILE I PROVIDED BELOW WILL BE IDENTICAL (USE A FILE HASH CHECKSUM TOOL IF YOU'RE CURIOUS), THERE IS ALSO A CHANCE THEY MAY HAVE SMALL, BUT SIGNIFICANT, VARIANCES**
Thanks for the info and link, @wrongway213
Link to @topjohnwu's post: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR AUGUST 2020 QQ3A.200805.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682906526
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682906525
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682906527
THESE FILES ARE FOR "10.0.0 (QQ3A.200805.001, Aug 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!
Also, as most of us know by now, it looks like Google flipped HW attestation back on, and so SafetyNet will now fail (not just on August, but even previous builds). basicIntegrity test passes, but ctsProfile fails (due to hardware attestation method Google flipped back on), regardless of EdXposed / Magisk Hide status. Until people way smarter than us figure it out, if ever, I can't tell you how to fix it other than reverting back to full stock and locked bootloader. Oh well, carry on. Root is still more important to me anyway - for me the pros still far outweigh the cons.
[SAFETYNET UPDATE!!]: Another temporary SafetyNet fix available, thanks to @Displax. Just note some users have mentioned it could have some unforeseen side effects, as it changes your build prop's entry for your device model name to an unknown in order to force BASIC hardware attestation. Use at your own risk. Big thanks to Displax! Face unlock now working again on my TD Bank and Citi mobile apps. Also worked on my wife's P4 "flame". =)
Just flash Displax's zip file in Magisk Manager: https://forum.xda-developers.com/showpost.php?p=83028387&postcount=40656

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

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

Flashed already and working fine without wiping or any changes from July build. Thanks!

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

onlyguynamedniles said:
I've been using your method for a few months with success but for some reason no when i try to sideload the coral zip file i get the following message. " adb: failed to read command: No error". Any idea why this would be happening? I've been trying for well passed an hour now with no success.
Click to expand...
Click to collapse
Not sure but could be a bad download (try redownloading the OTA zip, and/or verify with Google's hash on their downloads page).
Or maybe try updating to latest sdk platform tools.

You're truly the man for doing these each month, and saving my **** wifi the trouble of downloading the full factory image

i5lee8bit said:
Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have an old Magisk module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly and have a working phone if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.
- See this post (or thread) for more tips / context / an example: https://forum.xda-developers.com/showpost.php?p=82509691&postcount=16
Coming from an earlier build than July 2020?
Download the August 2020 Full Factory Image .zip file and extract it. BEFORE RUNNING THE FLASH-ALL BATCH / SHELL FILE, EDIT THE FILE AND REMOVE THE "-w" FLAG FROM THE LAST FASTBOOT LINE. If you fail to remove -w, your phone will be wiped when it reaches this step. After flashing the full factory image, your phone will automatically reboot into O/S. From here, reboot back into bootloader, and flash the new Magisk patched boot image.
SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)
Click to expand...
Click to collapse
Here is what I have been doing and it has worked well for me:
1. Flash the latest build (not OTA) via Android Flash tool - my 4XL reboots just fine, and you get to keep everything, settings, files etc. It doesn't wipe your phone.
2. Fire up Adb, put the phone into fastboot mode, flash your patched .img - and that is literally it.
Hope this helps
---------- Post added at 11:13 PM ---------- Previous post was at 11:10 PM ----------
onlyguynamedniles said:
I've been using your method for a few months with success but for some reason no when i try to sideload the coral zip file i get the following message. " adb: failed to read command: No error". Any idea why this would be happening? I've been trying for well passed an hour now with no success.
Click to expand...
Click to collapse
Flash the latest build via Android Flash tool, the phone will reboot, then flash the patched .img via Adb = profit

Worked to perfection. Took me less than 10min. Great work again!

Updated the OP with yet another SafetyNet fix.
Sorry guys, I haven't had as much time for XDA in the last month or two, and the fix (huge thanks to @Displax!!!) just totally wooooshed past me... over a month and a half ago apparently, lol. His Magisk module basically modifies part of the build prop to change your device model as reported to an unknown, thus forcing BASIC hardware attestation. Apparently it could have some side effects, such as possibly breaking home automation (discussed in the DU thread briefly), so use it at your own risk. It's just so very nice to be able to face unlock my main banking apps again!
Also, thanks to DU for their new thread... not just for their historically awesome work, but also it was where I randomly read them vaguely referencing some patch to fix SafetyNet, haha.

Hey @i5lee8bit,
This is an awesome guide, I updated my P4XL to July then to August using this without a hitch!
Although, I would suggest to add a link to Google USB driver in the process: https://developer.android.com/studio/run/win-usb Because my PC wasn't recognizing my P4XL and I realized I didn't have the driver installed for ADB through USB.
Anyway, thanks a lot for your monthly update guide :good:

Android 11 has been released. Anyone tried this method out to upgrade?

Hi OP @i5lee8bit, are you planning to publish and updated guide for Android 11 update? ?

sidhaarthm said:
Hi OP @i5lee8bit, are you planning to publish and updated guide for Android 11 update? ?
Click to expand...
Click to collapse
Also interested in a prebuilt boot image. Other threads are saying root/magisk work find with 11.

I see no reason this method wouldn't work to update to Android 11. My procedure is essentially restoring stock boot / dtbo (and therefore stock recovery) which allows us to then sideload the OTA. Immediately after the manually applied OTA, we are then flashing the new patched boot image before even giving the phone a chance to boot back up, making it "seamless".
Unfortunately as I mentioned a while back, I won't be updating to Android 11 right away as I want to wait until certain things are updated for R (mostly GravityBox and kernel). I actually rely a LOT on GravityBox customizations and it's not worth it for me to live without it for the time being, and I'd rather wait to make sure kernel also is stable (I also rely a lot on CleanSlate features, which are built into Kirisakura).
However, I'll still be publishing a how-to guide soon. I reached out to someone who already successfully patched and rooted / booted the Sept 2020 build and hopefully they can share the file with me. Meanwhile, I will not be installing Canary Magisk Manager on my device (sorry guys, lol) and potentially deal with headaches with my daily driver phone, so I need the patched boot image from elsewhere.
There are several warnings I want to add to the new post as well. Like making sure all modifications (namely frameworks such as Riru and EdXposed) are already updated to R-compatible builds, otherwise bootloops will almost be guaranteed. But like always, it should be very easy to at least boot into unrooted, stock boot image should you run into any problems.
@sidhaarthm and @elkay, would you guys be willing to test the update method before I publish the Sept 2020 guide? I'm still waiting to hear back about the patched boot image but hopefully I'll hear back soon.

i5lee8bit said:
I see no reason this method wouldn't work to update to Android 11. My procedure is essentially restoring stock boot / dtbo (and therefore stock recovery) which allows us to then sideload the OTA. Immediately after the manually applied OTA, we are then flashing the new patched boot image before even giving the phone a chance to boot back up, making it "seamless".
Unfortunately as I mentioned a while back, I won't be updating to Android 11 right away as I want to wait until certain things are updated for R (mostly GravityBox and kernel). I actually rely a LOT on GravityBox customizations and it's not worth it for me to live without it for the time being, and I'd rather wait to make sure kernel also is stable (I also rely a lot on CleanSlate features, which are built into Kirisakura).
However, I'll still be publishing a how-to guide soon. I reached out to someone who already successfully patched and rooted / booted the Sept 2020 build and hopefully they can share the file with me. Meanwhile, I will not be installing Canary Magisk Manager on my device (sorry guys, lol) and potentially deal with headaches with my daily driver phone, so I need the patched boot image from elsewhere.
There are several warnings I want to add to the new post as well. Like making sure all modifications (namely frameworks such as Riru and EdXposed) are already updated to R-compatible builds, otherwise bootloops will almost be guaranteed. But like always, it should be very easy to at least boot into unrooted, stock boot image should you run into any problems.
@sidhaarthm and @elkay, would you guys be willing to test the update method before I publish the Sept 2020 guide? I'm still waiting to hear back about the patched boot image but hopefully I'll hear back soon.
Click to expand...
Click to collapse
I'd be very happy to test and establish the method with you ??

sidhaarthm said:
I'd be very happy to test and establish the method with you ?
Click to expand...
Click to collapse
Thanks, PM sent!

Awesome that you guys are figuring it out. I'll just wait then and reap the good news later

Just used this method to upgrade from Beta 3 to 11 (Final) and it worked perfectly! Thanks for making this awesome guide!

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

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

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

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

worked like a charm. thanks

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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