[UPDATE/KEEP ROOT GUIDE] JULY 2020 (QQ3A.200705.002) "FLAME" Magisk/Stock Boot Images

[i5lee8bit]

[UPDATE/KEEP ROOT GUIDE] JULY 2020 (QQ3A.200705.002) "FLAME" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4-XL "CORAL"!!

Here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the July 2020 (QQ3A.200705.002) 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 JULY 2020 QQ3A.200705.002!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886736
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=8889791610682886734
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=8889791610682886735

THESE FILES ARE FOR "10.0.0 (QQ3A.200705.002, Jul 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 July, 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.

 

[i5lee8bit]

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

flame-qq3a.200605.001-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261824457
flame-qq3a.200605.001-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261824455
July 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq3a.200705.002-01ce0fff.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 flame-qq3a.200605.001-factory-boot.img
3. fastboot flash dtbo flame-qq3a.200605.001-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 flame-ota-qq3a.200705.002-01ce0fff.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 flame-qq3a.200705.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. I've only personally tested with Kirisakura though.)
*Kirisakura 4.7.5 seems to work fine as of initial write up.

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.

SafetyNet not passing? READ OP AGAIN. (not fixable as of this posting)

 

[i5lee8bit]

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/how-to/magisk-modules-disabler-booting-magisk-t3991739
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 June 2020?

Download the July 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)

 

[ahalol]

Thank you as always

 

[everonline]

Thanks. Great Info as usual.