Database Develop

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

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

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)

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)

Thank you as always

Thanks. Great Info as usual.

[UPDATE/KEEP ROOT GUIDE] DEC 2020 (RQ1A.201205.008) "FLAME" Magisk/Stock Boot Images

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
* Also note, AT&T now has a separate firmware for Dec 2020 - f*** you AT&T!
**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 "RQ1A.201205.008, Dec 2020"!
Magisk v21.1 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675600323
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675600325
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675600324
----------------------------------------------
-------------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.201105.002, Nov 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rp1a.201105.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675582552
flame-rp1a.201105.002-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675582551
December 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rq1a.201205.008-9c641763.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 flame-rp1a.201105.002-factory-boot.img
3. fastboot flash dtbo flame-rp1a.201105.002-factory-dtbo.img
......* these steps to restore stock recovery; dtbo.img also necessary for some kernel installations.
......* won't hurt to flash both anyway, so if you're unsure, go ahead and do both.
-----------------
4. use volume keys to change selection to boot to Recovery Mode
......- when you reach the android symbol with No Command, hold power button, tap volume up, in case you've forgotten
5. choose option "Apply update from ADB"
6. adb sideload flame-ota-rq1a.201205.008-9c641763.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-rq1a.201205.008-magisk_patched-21.1.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.
-------------------------------------------------
-------------------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/t/...r-booting-into-magisk-core-only-mode.3991739/
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

[UPDATE/KEEP ROOT GUIDE] JAN 2021 (RQ1A.210105.003) "FLAME" Magisk/Stock Boot Images

GravityBox [R] was pre-released today! Thus, I was able to update, using this very method, all the way from August 2020 thru January 2021. Entire process took only about an hour, with no hiccups. =) =) =)
But luckily, that also means I can actually start confirming again, personally, that everything is working fine. I can happily report everything is working great after this update. SafetyNet is passing with the correct configurations, and January 2021 build is working perfectly so far with Kirisakura 6.6.6.
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**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 "RQ1A.210105.003, Jan 2021"!
Magisk v21.2 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709389
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145709388
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145709390
----------------------------------------------
-------------UPDATE PROCESS BELOW-------------
----------------------------------------------​
EASY UPDATE / SEAMLESS KEEP-ROOT UPDATE PROCESS (using a PC - a very intuitive, effective, and relatively safe method).
** You can only follow this guide verbatim if coming EXACTLY from build "11.0.0 (RQ1A.201205.008, Dec 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rq1a.201205.008-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675600324
flame-rq1a.201205.008-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675600325
January 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rq1a.210105.003-e1f3575f.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 flame-rq1a.201205.008-factory-boot.img
3. fastboot flash dtbo flame-rq1a.201205.008-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-rq1a.210105.003-e1f3575f.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-rq1a.210105.003-magisk_patched-21.2.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/t/...r-booting-into-magisk-core-only-mode.3991739/
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

[EDIT 01-13-2021] YET ANOTHER NEW SAFETYNET WORKAROUND (AS OF AROUND JANUARY 12 / 13):
Please see this post: https://forum.xda-developers.com/t/guide-edxposed-gpay-discussion.3992607/post-84285539

welcome to the wonderful world of Android 11!!! nice to have u here with us mate. update went smoothly like always! thanks and keep it up!!

tulsadiver's way no longer working on flame R build

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

IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**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=2188818919693776334
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693776333
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693776329
----------------------------------------------
-------------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.
flame-rq2a.210305.006-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145746630
flame-rq2a.210305.006-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145746632
April 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rq2a.210405.005-ec0467a7.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 flame-rq2a.210305.006-factory-boot.img
3. fastboot flash dtbo flame-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 flame-ota-rq2a.210405.005-ec0467a7.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-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!

thx mate but the patched boot image link seems to be wrong, goes to some random rom for a different device
actually dtbo link goes to magisk file, lucky! since I dont need this month dtbo for now, will flash update and report back
update went smoothly thx again m8!!

Thanks man, my bad. AFH wigged out when I initially uploaded the files and stopped after the first one. When I went back to re-up the last 2, I must have copied the URL's out of order, and somehow just mistyped some completely, lol. Should be fixed now, thanks for the heads up!

should work if I don't upgrade the last month, or two monts ago?? (I mean, update directly of the jan or feb update) or I must update each OTA???

caballero221 said:
should work if I don't upgrade the last month, or two monts ago?? (I mean, update directly of the jan or feb update) or I must update each OTA???
Click to expand...
Click to collapse
Follow the previous month guides if you want to OTA per month (you can't skip months doing the OTA method). Otherwise download the full factory image, extract the files and edit the script (.bat / .sh depending on your OS) file to remove the "-w" flag so you don't wipe data, run the script to flash the full factory image to update to current month, then reboot to bootloader and flash the magisk patched boot image in the OP (make sure your Magisk Manager version installed is also at least v22.0 before this last step).

[UPDATE / KEEP ROOT GUIDE] MAY 2021 (RQ2A.210505.002) - "FLAME" Magisk & Stock Boot / DTBO Images

(Sorry guys, this would have been up sooner, but Android File Host hasn't been letting me upload all day for some reason, so I just temporarily uploaded May 2021's files to my Google Drive for now instead. Enjoy! --- moved back to AFH )
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 "FLAME" ONLY, NOT PIXEL 4 XL "CORAL"!!
**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.210505.002, May 2021"!
Magisk v22.1 Patched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794194
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=2188818919693794193
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=2188818919693794195
----------------------------------------------
-------------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.210405.005, Apr 2021". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rq2a.210405.005-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693776329
flame-rq2a.210405.005-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693776333
May 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rq2a.210505.002-6509c4b3.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 flame-rq2a.210405.005-factory-boot.img
3. fastboot flash dtbo flame-rq2a.210405.005-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-rq2a.210505.002-6509c4b3.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-rq2a.210505.002-magisk_patched-22100.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 EdX/LSposed 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!

Thanks for sharing