Database Info

[GUIDE] Rooting your Essential PH-1

WARNING: Before attempting to root your device, do note that by unlocking your bootloader and modifying your device with root, ROMs, etc... you are risking voiding your warranty! I am NOT responsible for what you do to your device either, so follow these instructions at your own risk. Make sure you know what you're doing, it's best to understand the process rather than just copy and paste commands and such.
Useful and important general information can be found in the second post here.
NOTES
1. If you flash the TWRP Installer when you've already got Magisk installed, your device will keep booting to the recovery. You should be able to fix this by just simply reflashing Magisk.
2. If you have TWRP installed via the TWRP Installer, you will not be able to install stock OTA updates. You will have to reflash the stock boot image for whatever build you're running beforehand.
3. The prebuilt TWRP image may not have touch functionality if you're using the September 2018 Update or newer. Patching the boot image, however, for these builds with the TWRP Installer will allow touch to work flawlessly. Here is a pre-patched September 2018 Boot Image with TWRP. It should also work with builds newer than September. Since it's based off the September 2018 update, I suggest not using this as your main boot image but rather just as a replacement for the pre-built TWRP image from the official TWRP thread.
4. Simple "flash and forget" boot images pre-patched with Magisk and TWRP are provided by @aer0zer0 and are available here. They are based on ianmacd's variant of Magisk. If you are running stock, you can flash these boot images to get root and TWRP instead of following the guide to patch it yourself. Here is January's.
If you don't care about TWRP and simply want to just root your device, you can just simply patch the boot image for your ROM with the Magisk Manager and flash it in fastboot with
Code:
fastboot flash boot patched_boot.img
The link to the boot images for most stock builds can be grabbed from my Google Drive link in the second post or from the back-to-stock zips.
REQUIREMENTS
An unlocked bootloader
Working adb and fastboot environment, along with knowledge on how they work.
The latest build of TWRP along with the TWRP Installer. Read Note 3 above beforehand.
1. Download the latest build of TWRP and the TWRP Installer. Transfer the TWRP Installer zip to your device.
2. Reboot your phone into fastboot. Once in fastboot, change your device's current slot using the command
Code:
fastboot set_active other
If the command above doesn't work for you, use fastboot getvar current-slot followed by fastboot -aX, replacing "X" with the slot opposite (a or b) from your current slot.
3. Once your device's current slot has been switched, flash the TWRP image you downloaded earlier using the command
Code:
fastboot flash boot twrp.img
Depending on your version of fastboot, the above command might not work either. In that case, you can enter the following command, replacing "X" with your current slot (a or b).
Code:
fastboot flash boot_X twrp.img
4. Once TWRP has been flashed, boot into the recovery.
5. Once you have booted into TWRP, simply flash the TWRP Installer zip.
6. Once you have finished flashing the TWRP Installer zip, boot to recovery on the OPPOSITE slot. You can do this from TWRP by going to "Reboot", then selecting the opposite of the current slot (if on A, select Slot B. If on B, select Slot A), then select "Recovery." You can also do this through fastboot by running the same command from step 2.
7. Once you have booted back into TWRP, simply flash the Magisk zip and you are now good to go! Feel free to flash anything else like kernels while you're at it.
8. Reboot. :good:
NOTE: TWRP WILL remain installed on your device so long as you reflash the installer zip after every update.

Important Information for the Essential PH-1 can be found here. Keep it bookmarked.
Tips on updating via OTA after rooting can be found here.
In the case that you mess something up on your device, you may find it helpful to revert back to stock with the unofficial factory images graciously provided by @invisiblek and @aer0zer0 over here.
Official TWRP XDA Thread for the Essential PH-1
Join the Essential PH-1 Discord Server! -- Lots of cool people here!
Join the Essential PH-1 Development Telegram Channel!
Stock Boot Images for most builds can be found at my Google Drive link here.
Have a Red Verity Warning when booting your device? Click here.
If the link to the boot.fix.red image isn't working, you can also find it here or in my Google Drive link in the first post.
Essential Phone (PH-1) Partition Layout
Dumping Boot Images
1. Find the current slot with
Code:
fastboot getvar current-slot
or
Code:
adb shell getprop ro.boot.slot_suffix
2. Switch to the opposite slot in Fastboot using the command
Code:
fastboot set_active other
3. Flash TWRP using the command
Code:
fastboot flash boot twrp.img
4. Now, boot into TWRP and use the following command from your PC, replacing X in "boot_X" with the original slot from step 1 (a or b). TRIPLE CHECK:
Code:
adb shell dd if=/dev/block/bootdevice/by-name/boot_X of=/sdcard/boot.img
5. Profit! Don't forget to switch back to the original partition with the same command from step 2!
extractTarFork() error when restoring data from a TWRP backup
1. Reinstall the ROM from which the backup is based on.
2. Wipe your data. You can do this from the recovery or from fastboot using the command
Code:
fastboot -w
3. Boot into the ROM. When going through the initial setup, use the EXACT same security setup as the one from your backup. For example, if you used a Fingerprint + Password in the backed up ROM, use the exact same combo along with the exact same password as well. There is no need to set up anything else, like accounts.
4. Flash, install, and reboot into TWRP. You should now be able to restore the data backup without any issues.

AFH mirrors for images:
Build NMJ32F
NMJ32F patched boot image
NMJ32F factory image
Build NMJ20D
NMJ20D patched boot image
NMJ20D factory image
TWRP (alpha v4)

Thanks for getting the latest boot image up so quickly.

Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?

how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.

prgopala said:
how to install the NMJ32F ota update when you are already rooted on NMJ20D?
Tried adb sideload but cannot install obviously because boot-loader is unlocked and is rooted.
Click to expand...
Click to collapse
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.

Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?

@bmg1001 , good looks, here are more free XDA points to trade in for that pool table, lol.

gk1984 said:
Factory reset no longer required if your bootloader is already unlocked? Does TWRP read encypted storage now? Or is that still a problem?
Click to expand...
Click to collapse
As far as I know, TWRP still doesn't have decryption fully working just yet, but installing Magisk works fine without any factory resets.

prozo said:
Thanks for the detailed guide, it worked great!
Any idea how to install xposed sdk 25? I tried the adb sideload function and the Magsik Module but both failed. Any ideas?
Click to expand...
Click to collapse
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.

Did anyone manage to disable encryption? I tried everything and failed

bmg1001 said:
Xposed works fine for me. Make sure you installed the correct Xposed Installer/Manager apk linked in the thread for the Xposed Module. Also, it may take a reboot or two for Xposed to fully activate.
Click to expand...
Click to collapse
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?

prozo said:
Maybe I'm not gathering the information correctly, using the Magisk Module itself doesn't work, sideloading the zip file via the adb fastboot TWRP.img doesn't work either, using the actual Xposed APK installer doesn't work either. I rebooted the phone about 4 times before removing it entirely.
Any chance you can walk me through how you got it installed without the TWRP recovery fully installed?
Click to expand...
Click to collapse
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt

prozo said:
Thanks for replying so quickly I appreciate it, the file you linked keeps opening on my end and fails to install saying it's corrupt
Click to expand...
Click to collapse
The apk should be the same one found here: https://forum.xda-developers.com/xposed/unofficial-systemless-xposed-t3388268

bmg1001 said:
All I did was install the Xposed APK and then the Xposed Magisk Module. After two reboots, the apk said everything was working. This is the apk I used: https://drive.google.com/file/d/16-OHpswcngp1KLtkWCBDwwl8AvFafR5H/view?usp=drivesdk
Click to expand...
Click to collapse
Alright I got it to work
So I didn't use the APK instead I downloaded the zip from the XDA thread that is specifically for Magisk Module and then added via the modules tab on the left side of the Magisk Module APK.
After I restarted I had the newly installed APK to download and install the proper version of Xposed 88.2 sdk25
Another restart and boom I got the active module notification in green.
Thanks man!
Thread for downloads can be found here:
https://www.google.com/amp/s/forum....ed/unofficial-systemless-xposed-t3388268/amp/

Thank you for this!
My PH-1 is arriving today. SooOoo excited!

spotmark said:
You need to flash the system and boot images from Invisiblek's stock ROM dump. You'll then be unrooted and will be able to accept the update.
Click to expand...
Click to collapse
Would using flashfire work to install the ota?

drocny87 said:
Would using flashfire work to install the ota?
Click to expand...
Click to collapse
Couldn't tell you. I just used TWRP to flash the system and boot, and then took the update, and then rerooted.

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

Best way to apply OTA to rooted phone

Hi all,
I've tried different methods to apply the November OTA to my Pixel 3, but so far none has worked seamlessly. Here's what I've tried so far:
- TWRP install the full OTA from Google (fails with a timestamp error)
- sideloading the full OTA from Google (same timestamp error)
- using topjohnwu's suggestion from his Magisk GitHub, which in short temporarily unroots the phone to allow the regular OTA process to take place, then before rebooting use Magisk Manager to patch the boot image of the spare partition (in this scenario, the phone won't even boot fully, it does boot but eventually restarts before hitting the lockscreen).
Is there any correct way to apply OTAs straight from the phone, without using a computer? If not, what would be the best way to update the Pixel 3?

Why not just flash-all (minus the -w) the system image?

sliding_billy said:
Why not just flash-all (minus the -w) the system image?
Click to expand...
Click to collapse
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.

GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.

sliding_billy said:
Understood. I have just got so used to installing with the flash-all that is second nature. OTA through TWRP wasn't even working for a long time on the OG Pixel series, and putting the ~700 MB OTA file on the phone seemed like a waste since I only had a 32GB. Either way, permanent TWRP and Magisk are still installed directly from the phone and the TWRP .img fastboot boot needs a computer anyways so there is really no way to avoid the computer completely from end to end.
Click to expand...
Click to collapse
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.

GryphonBR said:
Well, if I could apply a full OTA directly from an already installed TWRP, then it'd be as simple as reinstalling TWRP and Magisk after the OTA. I was used to doing this on AOSP-based ROMs like Ressurection Remix or CyanogenMod/LineageOS.
Click to expand...
Click to collapse
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.

sliding_billy said:
No way to do it on a Pixel device (that I am aware of) since TWRP needs ran from outside of the OS. I seem to remember this coming up a bit when the OG Pixel first launched, and then it was just accepted to use fastboot boot.
Click to expand...
Click to collapse
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!

GryphonBR said:
Yeah, there's something funky about how TWRP works with the A/B setup, because of the embedded recovery into boot and such, I assume. In any case, at this point it seems like I actually can get it updated using fastboot, so that'll have to do for the time being.
Thanks for bouncing off ideas with me!
Click to expand...
Click to collapse
Any time. Good luck!

GryphonBR said:
Because that requires a computer. I'd rather have a solution that would allow me to update on the fly; preferably, flashing an OTA through TWRP, which would then allow me to also reflash TWRP itself and Magisk. But, then again, this would simply be my optimal scenario - if it can't be done, I'll stick to flash-all.
Click to expand...
Click to collapse
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.

TonikJDK said:
Last I heard flashing OTA in twrp is broken, but even if it is fixed as soon as you flash the OTA you would lose TWRP. So you still need a computer to boot to TWRP to install it and/or root.
The key point is you have to boot to TWRP before you can flash either it or Magisk.
Click to expand...
Click to collapse
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.

GryphonBR said:
But that's what I was trying to do in the first place: booted from TWRP, apply OTA than flash TWRP and Magisk.
Which doesn't boot up, unfortunately. Not sure why.
Click to expand...
Click to collapse
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.

TonikJDK said:
Right, it is broke that way right now. It's hard to do because recovery where TWRP sits and boot are the same partition now. Touch one you touch both. So when you flashed the OTA you wiped TWRP out of recovery.
Click to expand...
Click to collapse
That's true, but when I'm using TWRP that's the runtime instance, not the installed one. So even if it gets overwritten by the OTA installation, it wouldn't matter since it would still be active at that moment.

I went nuts trying to figure out how to sideload the Nov OTA update through TWRP (was always easy with my OG Pixel) and then figured it doesnt work lol. Just did like was already suggested and took out the -w from the OTA and it went smooth after I updated my platform tools. This is the way I will do it from now on even if TWRP gets fixed which that looks unlikely.

Anyone do it without using TWRP?

Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Yes, download the factory image and edit the flash-all batch file to remove the -w. Alternately, you can flash the stock boot image of your current os version and use the stock recovery to sideload the ota. Either way twrp will be replaced with the stock recovery.
Sent from my [device_name] using XDA-Developers Legacy app

Dbzruben said:
Anyone do it without using TWRP?
Click to expand...
Click to collapse
Method that worked for me (Fi Pixel3 (blueline), on Nov update, previously rooted via Magisk 17.3 Patch Boot Image File method) has been posted elsewhere & doesn't require TWRP installation. This assumes your device is already OEM Unlocked, has Developer Options/USB Debugging enabled/setup and you have the latest ADB/Drivers installed on your PC:
Download Dec Factory image (blueline-pq1a.181205.006)
Download TWRP 3.2.3-0 bootable image (twrp-3.2.3-0-blueline.img)
Download Magisk 17.3 zip
Download Magisk Manager 6.0.1 APK
Download Magisk Uninstaller (Canary)
Move TWRP bootable image file to ADB folder on PC (Win7 for me)
Unzip Dec image contents into ADB folder on PC
Find the Dec Boot.img file from extracted Dec image contents and copy it to Device Storage (Download folder)
Move Magisk Manager APK & Magisk Uninstaller zip to Device Storage (Download folder)
Modify the flash-all.bat file from the extracted Dec image contents location in Notepad (remove the -w) and save/overwrite the file back to the same directory & close Notepad
Open up command window from ADB folder on PC
adb reboot bootloader
fastboot boot twrp-3.2.3-0-blueline.img​
"Install" the Magisk Uninstaller zip (via TWRP) wait for that to finish then reboot to bootloader.
(Re)Open a command window from your PC's ADB folder if you closed it.
flash-all (with the -w previously removed in Notepad). Wait for it to finish.
fastboot reboot (if it doesn't boot back to System once finished)​
(Now in Android after 1st system boot) Check that Dec update has taken (Settings->System->About Phone->Build Number). No root.
To continue rooting Dec Image:
Install Magisk Manager APK (from Settings->Storage->Files->Download folder)
Open MM (ignore/dont install anything via MM if prompted). No root (as of yet).
In MM: Settings->Update Channel-> Change to "Beta"
Swipe down in MM to "Update" MM and "Install" v17.3 (17302.zip hotfix) via Patch Boot Image File method (using Dec Boot.img previously extracted and put into Device Storage (Download folder)).
Output Patched_Boot.img should now be located in Device Storage (Download folder).
Copy Patched_Boot.img file from Device Storage to ADB folder on PC
Open up a command window from ADB folder on PC again:
adb reboot bootloader
fastboot flash boot_a Patched_Boot.img
fastboot flash boot_b Patched_Boot.img
fastboot reboot​
(assuming everything took) Open up MM, confirm Magisk 17.3 is installed & you have root
Re-Install all relevant MM modules (i did not have Active Edge module previously installed but heard there were issues with this module & root)

There's way more steps in that than needed and really doesn't address how to apply an ota to a rooted phone.
Line 13 is the only thing that would apply.
Sent from my [device_name] using XDA-Developers Legacy app

I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.

Serial Kazama said:
I cont root my pixel with Dezember Update. It stock on bootloop after i flashed the patched Magisk images.
Click to expand...
Click to collapse
Have you tried to root using twrp and the magisk zip?
Sent from my [device_name] using XDA-Developers Legacy app

Find the solution, i forgot to use the Magist Uninstaller Zip before i root the new OTA. My fault. Thx anyway!

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

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

EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide exactly if coming from build QQ2A.200405.005, Apr 2020. But the general idea is the same for other builds, you just need the correct files for your device.
coral-qq2a.200405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796390
coral-qq2a.200405.005-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796391
May 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-qq2a.200501.001.b2-8309f363.zip
I DID NOT BOOT BACK INTO O/S UNTIL ALL STEPS WERE COMPLETED - I DID THIS TO ENSURE EVERYTHING WOULD BOOT BACK UP WITH MAGISK / EDXPOSED ALL RUNNING PROPERLY RIGHT AWAY
1. boot into bootloader
----------------
** I was on custom kernel, so I needed to flash BOTH the stock boot and dtbo images
2. fastboot flash boot coral-qq2a.200405.005-factory-boot.img
3. fastboot flash dtbo coral-qq2a.200405.005-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload coral-ota-qq2a.200501.001.b2-8309f363.zip
7. Once the OTA sideload is done, Reboot to bootloader (you'll also notice it's now on the other slot after OTA flashed)
8. fastboot flash boot coral-qq2a.200501.001.b2-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it. I've only personally tested with Kirisakura though.)
This was a 100% seamless update that required no additional / re-setup of any of my Magisk or EdXposed setups. All of the factory files can be found here https://developers.google.com/android/images. boot.img and dtbo.img are in their corresponding full Factory Image zips, and the ota zip is under Full OTA Images.
EDIT: Issues after updating?
If you end up unable to boot or bootlooping afterwards, you most likely have a module that isn't playing nice with the new build. There are 2 main things you can do:
1. Flash the new factory untouched boot image. You will of course lose root, and all modules will be disabled. However, it should at least get you able to boot back up quickly if you're in a bind.
2. I would recommend checking Tulsadiver's thread: https://forum.xda-developers.com/pixel-4-xl/how-to/magisk-modules-disabler-booting-magisk-t3990557
Instead of reverting to stock boot image, fastboot boot (NOT FLASH) Tulsadiver's boot image. This will boot your phone in Magisk Core-Only Mode, with all modules disabled but root retained. From here you can open Magisk Manager and disable suspect modules. Before rebooting, go to Magisk Manager's settings and disable Magisk Core-Only Mode. Once you disable the incompatible module, the phone should boot back up.

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

Perfect method. Thank you.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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