[UPDATE/KEEP ROOT GUIDE] NOV 2020 (RP1A.201105.002) "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: 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=10763459528675583594
Magisk v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675576858
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675582551
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675582552
----------------------------------------------
-------------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.
flame-rp1a.201005.004-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675562113
flame-rp1a.201005.004-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675562112
November 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rp1a.201105.002-d6fbf151.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.201005.004-factory-boot.img
3. fastboot flash dtbo flame-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 flame-ota-rp1a.201105.002-d6fbf151.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-rp1a.201105.002-magisk_patched-21.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.
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.
And apologies about the recent tardiness on these update guides lately. Once all my preferred mods are successfully updated for Android 11, I'll actually be doing these updates myself and these guides will be much more prompt like before. =)
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://forum.xda-developers.com/ap...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://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
as always thank u for the quality guide mate. easy and quick to follow!
vdevl said:
as always thank u for the quality guide mate. easy and quick to follow!
Click to expand...
Click to collapse
Well heads up, because I just updated OP with the 21.1 update that just dropped this morning, haha. Please let me know if it works, should you try flashing it. Thanks.
Also, copied from my P4 XL thread: "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."
i5lee8bit said:
Well heads up, because I just updated OP with the 21.1 update that just dropped this morning, haha. Please let me know if it works, should you try flashing it. Thanks.
Also, copied from my P4 XL thread: "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."
Click to expand...
Click to collapse
hey mate i never replied before but yea the 21.1 patch worked fine b4. i heard december update had some signifcant feature drops so i came here to look for update--holy hell xda has evolved!!!! llol. anyway ill wait patiently for ya mate, thx as always
Related
[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] OCT 2020 (RP1A.201005.004) "FLAME" Magisk/Stock Boot Images
IF YOU ARE STILL ON AUGUST (ANDROID 10/Q) BUILD, PLEASE FOLLOW THE SEPTEMBER GUIDE (click here) FIRST! AND READ ALL WARNINGS AND ADDITIONAL INFO IN FIRST 2 POSTS!
PLEASE NOTE: I STILL HAVE NOT UPDATED TO ANDROID 11 YET, SO PLEASE FLASH AT YOUR OWN RISK AS ASSISTANCE FROM ME WILL BE VERY LIMITED. PLEASE BE KIND TO ONE ANOTHER AND HELP EACH OTHER OUT!
PLEASE DROP A THANKS IF YOU STILL FIND THESE GUIDES HELPFUL! :good:
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: https://twitter.com/topjohnwu/status/1272136975022084097?s=19
ALL FILES BELOW ARE FOR "RP1A.201005.004, Oct 2020"!
Magisk Canary v21.0 Patched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562385
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=10763459528675562112
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=10763459528675562113
[SAFETYNET INFO]: Again, I'm not updating myself yet, so I'm not sure about this. I will update this info as others report back. On Android 10, using the MagiskHide Props Config module (or an alternate module created by Displax, though I prefer Didgeridoohan's module) and choosing option 2 - Force BASIC key attestation would force BASIC HW attestation and allow SafetyNet to pass again. This works perfectly for me, and I even run additional mods including EdXposed. I'm not sure if this works on Android 11, and I won't be able to confirm myself for a while. If anybody tries it, please let me know and I'll update this section. The module and info on using it can be found here: https://forum.xda-developers.com/ap...just search for it in the Magisk Manager app.
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.200720.009, Sep 2020)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rp1a.200720.009-factory-dtbo.img: https://www.androidfilehost.com/?fid=10763459528675562111
flame-rp1a.200720.009-factory-boot.img: https://www.androidfilehost.com/?fid=10763459528675562110
September 2020 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rp1a.201005.004-9e17c7b4.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.200720.009-factory-boot.img
3. fastboot flash dtbo flame-rp1a.200720.009-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-rp1a.201005.004-9e17c7b4.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-rp1a.201005.004-magisk_patched-21.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.
-------------------
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
just want to report happily that i waas able to update to october with no problems using your guide. followed your september guide yesterday and then october today. no problems at all, buttery smooth mate! thanx..!
The instructions are great as a reminder,
I only work on the console every month or two and without the bullet points I wouldn't always be able to finish the update so quickly.
Thank you very much ?
So.. I've rooted and taken OTA's and rerooted dozens of times.. But I finally got around to factory resetting now stable is here. On OCT build, i flash the patched boot img and upon rebooting, Magisk shows I'm still not rooted. Any advice?
Update: Flashed canary debug apk. patched stock boot img, and flashed. now rooted. wierd
What about if I'm not rooted and on the October update for Android 11? I've tried a couple different times to root and I always get a fail when I try to flash the patched boot image.
Hey,
here is a quick guide:
=== you need these websites ===
https://developers.google.com/android/images
https://developers.google.com/android/ota
https://github.com/topjohnwu/magisk_files/tree/canary
step by step
1. download https://github.com/topjohnwu/magisk_files/archive/canary.zip
that's Magisk
2. copy app-debug.apk on your Pixel 4 (XL) and install the app
3. Open an Image (NOT OTA!) with 7-zip, there is another big zip-file inside, extract boot.img and dtbo.img
4. Copy boot.img on your Phone, download-folder, just like Magisk.apk
5. Open Magisk and Patch boot.img -> magisk-patched.img
6. Copy magisk-patched.img on your PC
7. now simply proceed as described in the instructions above.
Nothing can go wrong with these self-patched files
i5lee8bit said:
8. fastboot flash boot flame-rp1a.201005.004-magisk_patched-21.0.img
Click to expand...
Click to collapse
Hey guys, novice rooter here:
Can someone explain this step to me? Where do I get this file from if im on the beta version of Magisk?
Fwaiiiz said:
Hey guys, novice rooter here:
Can someone explain this step to me? Where do I get this file from if im on the beta version of Magisk?
Click to expand...
Click to collapse
load canary magisk apk: https://github.com/topjohnwu/magisk_files/blob/canary/app-debug.apk and install, then update magisk in the app
go to: https://developers.google.com/android/images
read
and download factory image for your pixel phone - 11.0.0 (RP1A.201105.002, Nov 2020) is last image for flame https://dl.google.com/dl/android/aosp/flame-rp1a.201105.002-factory-351561c6.zip
unzip the image, and you get another zip file: image-flame-rp1a.201105.002.zip
unzip image-flame-rp1a.201105.002.zip and you get a file named boot.img
copy boot image to your phone
patch boot image with magisk - you have made the magisk patch yourself ? now copy the magisk-patched.img from your phone to your pc, that's the file you ask for, but for the November Update
I hope you can now Update all you want
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
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.210305.006, Mar 2021"!
Magisk v22.0 Patched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746631
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=17248734326145746632
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=17248734326145746630
----------------------------------------------
-------------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.210205.004, Feb 2021)". But the general idea is the same for other builds, you just need the correct files for your device.
flame-rq1a.210205.004-factory-dtbo.img: https://www.androidfilehost.com/?fid=17248734326145727338
flame-rq1a.210205.004-factory-boot.img: https://www.androidfilehost.com/?fid=17248734326145727339
March 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/flame-ota-rq2a.210305.006-bab4ffbc.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.210205.004-factory-boot.img
3. fastboot flash dtbo flame-rq1a.210205.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 flame-ota-rq2a.210305.006-bab4ffbc.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.210305.006-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 for continued work mate. guide worked perfectly! like always. updated just in time for kirisakura 7.1.1 too lol
Seems like @vdevi and I are the only ones rooting their phones? :O
darkriff said:
Seems like @vdevi and I are the only ones rooting their phones? :O
Click to expand...
Click to collapse
Well, fwiw, there have been at least 13 downloads of this month's patched boot image I uploaded, lol. So I guess there are other lurkers out there enjoying this phone rooted.
Although, compared to 42 downloads as of right now for my patched Pixel 4 XL boot image. I'm just glad the phones are so similar that most of the same mods work for the P4 that are made for the P4XL. If it weren't for my wife owning this particular model and me doing the work already anyway, I probably wouldn't be bothering with these threads.
I have ordered a pixel4 that I will be receiving soon, and would like to ask whether this thread subject (March 2021) root scheme will pass SafetyNet tests (so that I can use bank apps etc).
Has anyone tested, or can I more or less assume that any of the rooted ROMs for pixel4 under this forum passes SafetyNet?
reikred said:
I have ordered a pixel4 that I will be receiving soon, and would like to ask whether this thread subject (March 2021) root scheme will pass SafetyNet tests (so that I can use bank apps etc).
Has anyone tested, or can I more or less assume that any of the rooted ROMs for pixel4 under this forum passes SafetyNet?
Click to expand...
Click to collapse
Not sure about custom ROMs, but I don't see why not. Yes, this root scheme / setup will pass SafetyNet. Just use this Magisk module along with it:
GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
Google SafetyNet attestation workarounds for Magisk - GitHub - kdrag0n/safetynet-fix: Google SafetyNet attestation workarounds for Magisk
github.com
Will also pass with Xposed. If using LSposed, should just pass, period, unless you really stray from the defaults or mess something up. If using EdXposed, best to use WhiteList mode, otherwise turn on Pass SafetyNet option. I highly prefer LSposed these days.
I don't see a need for custom ROM anymore, and this coming from someone who used custom ROMs on every single Android I've ever owned all the way up to my last phone, the HTC U12+.
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).