[UPDATE/KEEP ROOT GUIDE] Jun 2020 (QQ3A.200605.001) "FLAME" Magisk-Patched Boot Image

[i5lee8bit]

[UPDATE/KEEP ROOT GUIDE] Jun 2020 (QQ3A.200605.001) "FLAME" Magisk-Patched Boot Image

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

Hey guys, yup, I'm still furloughed... ;_;

So anyway, here are the factory and Magisk Patched (v.24 is still the latest as of typing this) boot images for the June 2020 (QQ3A.200605.001) update.

ALL FILES BELOW ARE FOR JUNE 2020 QQ3A.200605.001!
Magisk v20.4 Patched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824456
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=4349826312261824455
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=4349826312261824457

THESE FILES ARE FOR "10.0.0 (QQ3A.200605.001, Jun 2020)" ONLY! PLEASE ONLY FLASH IF YOU KNOW WHAT YOU'RE DOING!

Everything seems to work fine so far. Magisk v.24 and EdXposed 5.0.0 (4548 YAHFA). SafetyNet Passing for now... Kirisakura 4.7.5 (just released today!) works great too!

If these files and/or guides are helpful, please drop a thanks and let me know. Thanks! =)

 

[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 exactly if coming EXACTLY from build qq2a.200501.001.b2, May 2020. But the general idea is the same for other builds, you just need the correct files for your device.

flame-qq2a.200501.001.b2-factory-dtbo.img: https://www.androidfilehost.com/?fid=4349826312261796523
flame-qq2a.200501.001.b2-factory-boot.img: https://www.androidfilehost.com/?fid=4349826312261796524
June 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-qq3a.200605.001-09888a47.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-qq2a.200501.001.b2-factory-boot.img
3. fastboot flash dtbo flame-qq2a.200501.001.b2-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 flame-ota-qq3a.200605.001-09888a47.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.200605.001-factory-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.

 

[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

 

[ahalol]

Thank you for the update as always

 

[caballero221]

Thank you for the update and the post.

Everything works fine, but the pixel launcher keeps crashing after reboot. Also, the recent app menu don't work. Any suggestions?

EDIT:
Solved reinstaling last version of com.google.android.apps.nexuslauncher

 

[ruxxzif]

mine is qq3a.200705.002 , the above step working for my version?