[UPDATE/KEEP ROOT GUIDE] NOV 2020 (RP1A.201005.004) "CORAL" Magisk/Stock Boot Images

[i5lee8bit]

[UPDATE/KEEP ROOT GUIDE] NOV 2020 (RP1A.201005.004) "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: https://twitter.com/topjohnwu/status/1272136975022084097?s=19


ALL FILES BELOW ARE FOR "RP1A.201105.002, Nov 2020"!
[Mid-Month Update] Magisk v21.1 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675583368
Magisk v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675576858
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675576853
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675576854

----------------------------------------------
-------------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 (RP1A.201005.004, Oct 2020)". But the general idea is the same for other builds, you just need the correct files for your device.

coral-rp1a.201005.004-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675557938
coral-rp1a.201005.004-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675557937
November 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rp1a.201105.002-e4f4e179.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-rp1a.201005.004-factory-boot.img
3. fastboot flash dtbo coral-rp1a.201005.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-rp1a.201105.002-e4f4e179.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-rp1a.201105.002-magisk_patched-20.4.img
9. done, start the phone
(Optional - Flash custom kernel. If you had a custom kernel, you need to re-flash it)

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.


Please Note: I still haven't upgraded to Android 11, so the usual warnings apply. Please see previous month's update guides for additional info and troubleshooting.

 

[i5lee8bit]

PASSING SAFETYNET: Use the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choose option 2 - Force BASIC key attestation. This forces BASIC HW attestation and allows SafetyNet to pass again. This also works (along with proper setup) with EdXposed (big thanks to eg1122's guide here). The MagiskHide Props Config module and info on using it can be found here: https://xdaforums.com/apps/magisk/m...just search for it in the Magisk Manager app.

Specific EdXposed build required to pass SafetyNet: Also big thanks to cracky.ice who found that, as of this posting, we need to use EdXposed build 4563 (v0.4.6.4). See cracky.ice's original post here. Apparently Google changed something again that makes SafetyNet fail with EdXposed on build 4564 (v0.5.0.6), regardless of using the MagiskHide Props Config module. EdXposed build 4563 (v0.4.6.4) can be downloaded directly from here: https://ci.appveyor.com/project/ElderDrivers/edxposed/builds/35441002/artifacts

------------------------------
-----------------------------------------
------------------------------​

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://xdaforums.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://xdaforums.com/showpost.php?p=82509691&postcount=16

 

[Morgrain]

Upgraded with your method and everything worked out fine. Thank you very much.

 

[blue2018]

Everything works well. Thanks a lot for your sharing.

 

[fuarkgl3]

Thanks as always. Helps a lot

 

[rob_z11]

Yes, thanks for sharing. I was able to flash your rooted kernel. Just quick question on how to flash custom kernel without those kernel tools..

 

[i5lee8bit]

OP updated with patched boot image with Magisk v21.1

If it doesn't work for some reason, simply flash back Magisk v21.0. Don't see why it wouldn't, but just because I haven't tested yet.

Edit: I should also mention, if you have a custom kernel flashed already on November build, I would recommend restoring (flashing) stock November dtbo img, along with flashing the new Magisk 21.1 patched boot image, then re-flashing the kernel after booting back up. Otherwise, you'll potentially have a modified dtbo from previous kernel install, along with a stock, magisk-patched, non-kernel modified boot image and I'm not sure if it'll make things wonky and cause issues leading up to or during re-flashing your kernel. Normally I'd say just direct install the update via Magisk Manager but for some reason since moving to the Pixel 4, it hasn't worked for me. Weird because it worked on HTC U12+, which is also an A/B partitioned device.

 

[Morgrain]

The december update is out. Anyone here already tried it out? Can someone share the magisk file?

 

[i5lee8bit]

The december update is out. Anyone here already tried it out? Can someone share the magisk file?

Just put the baby down for the afternoon nap, gonna start working on this now. =)

I still haven't updated to Android 11 yet (no GravityBox) - but could someone answer this one question for me? It's the one thing that really makes me hesitant / anxious about going to Android 11. Did they completely remove 3 button navigation, or is it still available? I friggin' hate gesture navigation, and really hope 3 button is still available.

Anyways, thanks. Hold tight and I should have the files up soon.

edit: it's up. https://xdaforums.com/t/update-keep...5-008-coral-magisk-stock-boot-images.4200261/
new XDA is getting on my nerves... lol

 

[Morgrain]

Just put the baby down for the afternoon nap, gonna start working on this now. =)

I still haven't updated to Android 11 yet (no GravityBox) - but could someone answer this one question for me? It's the one thing that really makes me hesitant / anxious about going to Android 11. Did they completely remove 3 button navigation, or is it still available? I friggin' hate gesture navigation, and really hope 3 button is still available.

Anyways, thanks. Hold tight and I should have the files up soon.

On my P4 XL , stock Android 11 November Patch , I can still change to 3-button navigation under "Gestures". They did remove the 2 button nagivation.

No, thank you. Without your good guide/seamless update idea, updating rooted Pixels would be much more hassle