• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

[UPDATE / KEEP ROOT GUIDE] JUNE 2021 (RQ3A.210605.005) - "CORAL" Magisk & Stock Boot / DTBO Images

Search This thread

i5lee8bit

Senior Member
Jul 18, 2006
405
815
New Jersey
IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!

==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools
==> Official Factory Image / OTA - Downloads / Flashing Guide Here (recommend reading): https://developers.google.com/android/images

**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 "RQ3A.210605.005, Jun 2021"!
Magisk v23.0 Patched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345554
Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345555
Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=14943124697586345553

----------------------------------------------
-------------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.210505.002, May 2021". But the general idea is the same for other builds, you just need the correct files for your device.

coral-rq2a.210505.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693794180
coral-rq2a.210505.002-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693794183
June 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq3a.210605.005-4e7b2427.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

*. make sure installed Magisk (Manager) app version is equal to or greater than the Magisk pre-patched version boot image provided
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-rq2a.210505.002-factory-boot.img
3. fastboot flash dtbo coral-rq2a.210505.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 coral-ota-rq3a.210605.005-4e7b2427.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-rq2a.210605.005-magisk_patched-23000.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!
 

i5lee8bit

Senior Member
Jul 18, 2006
405
815
New Jersey
Quick note - apologies for going radio silent towards the middle / end of last month. Things are really starting to get busy in life, and all of the "big ticket" life changes are all converging on us at once! Went on a ~1500mi road trip to visit family for the first time in a long time... with a toddler :O
Also just bought our first house... closing is happening soon... starting new jobs... I have knee surgery coming up in a few weeks during all this and moving and stuff... and all while raising a toddler who is going to be 2 years old at the end of the year!

Anyway, I added the notes and a link regarding latest platform SDK tools. Thanks to everyone who recommended that before. Hopefully it helps prevent or leads people to solve silly issues due to using outdated SDK tools.

Besides that, like I said things are getting extremely busy and I'm finding it a bit tougher to keep up with XDA stuff. Fortunately, according to the downloads counters on AFH, it seems like plenty of people are still finding these guides useful, so I'm glad I could help in that respect.

If you are helped by these guides, I would appreciate if you could express your thanks by hitting the thanks button. Apologies if I'm not around as much for the next several weeks, but I hope you all have a great summer! =)
 

i5lee8bit

Senior Member
Jul 18, 2006
405
815
New Jersey
@i5lee8bit, I appreciate your posts dude!

You're a Gravity Box user, right? Any problem with June update or all smooth? I know Google did a feature drop this month.

No problems noted yet, at least for the particular mods I happen to use in the GB arsenal. =)

Pretty much all the mods I use are for functionality and almost never for cosmetics. A few randomly off the top of my head being remapping navbar keys, adding left / right cursor keys to navbar, volume key cursor controls, statusbar quicksettings lockdown, advanced reboot menu. These all seem to work without issue so far. I also flashed Kirisakura 7.4.3 and it seems to be working well so far too.

I say go ahead and OTA. Working nicely here. =)

Also in case you didn't know, C released an update to GB (v 11.0.3) just a few days ago, so make sure you grab that too if you haven't already.
 

crisco654

Member
Jul 17, 2014
34
8
Quick note - apologies for going radio silent towards the middle / end of last month. Things are really starting to get busy in life, and all of the "big ticket" life changes are all converging on us at once! Went on a ~1500mi road trip to visit family for the first time in a long time... with a toddler :O
Also just bought our first house... closing is happening soon... starting new jobs... I have knee surgery coming up in a few weeks during all this and moving and stuff... and all while raising a toddler who is going to be 2 years old at the end of the year!

Anyway, I added the notes and a link regarding latest platform SDK tools. Thanks to everyone who recommended that before. Hopefully it helps prevent or leads people to solve silly issues due to using outdated SDK tools.

Besides that, like I said things are getting extremely busy and I'm finding it a bit tougher to keep up with XDA stuff. Fortunately, according to the downloads counters on AFH, it seems like plenty of people are still finding these guides useful, so I'm glad I could help in that respect.

If you are helped by these guides, I would appreciate if you could express your thanks by hitting the thanks button. Apologies if I'm not around as much for the next several weeks, but I hope you all have a great summer! =)
Always thanks to you bro. These guides have been a godsend, and have made stuff so much easier. Now, I can breeze through the whole process in less than 10 mins. Much appreciated.
 

Morgrain

Member
Aug 4, 2015
41
11
There is a small mistake in the guide.

The uploaded magisk file is called

fastboot flash boot coral-rq3a.210605.005-magisk_patched-23000.img​

The guide however wants a

fastboot flash boot coral-rq2a.210605.005-magisk_patched-23000.img​

Ergo copying the guide won't work. The file name must either be changed or the text from the guide must be changed.

I changed the file name and it worked without an issue. Thanks again for your awesome guide. Updating a rooted phone has never been that easy.
 
  • Like
Reactions: 100kaa

Cememer

New member
Mar 18, 2021
3
0
Google Pixel 4 XL
I did the June update and can no longer get back to root(blackout after boot animation)...
I tried safe mode, removing modules with adb, uninstalling Magisk via TWRP, but the situation remained the same...
Is this because of my environment?
By the way, it boots normally with stock boot.img.
 

pdfruth

Senior Member
Jul 4, 2014
82
43
Hey all.
Been running with the June updates for a week or so now. So far, so good.
GPay has even been working... until today, that is.
No longer passing Safetynet (neither basic, nor ctsProfile).

Anyone else passing Safetynet?

EDIT: Got things working again by switching from EdXposed to LSposed
 
Last edited:

Cememer

New member
Mar 18, 2021
3
0
Google Pixel 4 XL
I did the June update and can no longer get back to root(blackout after boot animation)...
I tried safe mode, removing modules with adb, uninstalling Magisk via TWRP, but the situation remained the same...
Is this because of my environment?
By the way, it boots normally with stock boot.img.
Resolved. Probably because I did not uninstall magisk properly before updating.
I temporarily turned off the passcode, which gave me a grace period and could uninstall magisk from the app.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    IMPORTANT!! THESE FILES / THIS THREAD IS FOR PIXEL 4 XL "CORAL" ONLY, NOT PIXEL 4 "FLAME"!!

    ==> DOWNLOAD LATEST SDK PLATFORM TOOLS HERE: https://developer.android.com/studio/releases/platform-tools
    ==> Official Factory Image / OTA - Downloads / Flashing Guide Here (recommend reading): https://developers.google.com/android/images

    **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 "RQ3A.210605.005, Jun 2021"!
    Magisk v23.0 Patched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345554
    Factory Untouched Boot Image: https://www.androidfilehost.com/?fid=14943124697586345555
    Factory Untouched DTBO Image: https://www.androidfilehost.com/?fid=14943124697586345553

    ----------------------------------------------
    -------------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.210505.002, May 2021". But the general idea is the same for other builds, you just need the correct files for your device.

    coral-rq2a.210505.002-factory-dtbo.img: https://www.androidfilehost.com/?fid=2188818919693794180
    coral-rq2a.210505.002-factory-boot.img: https://www.androidfilehost.com/?fid=2188818919693794183
    June 2021 sideload OTA zip: https://dl.google.com/dl/android/aosp/coral-ota-rq3a.210605.005-4e7b2427.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

    *. make sure installed Magisk (Manager) app version is equal to or greater than the Magisk pre-patched version boot image provided
    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-rq2a.210505.002-factory-boot.img
    3. fastboot flash dtbo coral-rq2a.210505.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 coral-ota-rq3a.210605.005-4e7b2427.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-rq2a.210605.005-magisk_patched-23000.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!
    3
    Quick note - apologies for going radio silent towards the middle / end of last month. Things are really starting to get busy in life, and all of the "big ticket" life changes are all converging on us at once! Went on a ~1500mi road trip to visit family for the first time in a long time... with a toddler :O
    Also just bought our first house... closing is happening soon... starting new jobs... I have knee surgery coming up in a few weeks during all this and moving and stuff... and all while raising a toddler who is going to be 2 years old at the end of the year!

    Anyway, I added the notes and a link regarding latest platform SDK tools. Thanks to everyone who recommended that before. Hopefully it helps prevent or leads people to solve silly issues due to using outdated SDK tools.

    Besides that, like I said things are getting extremely busy and I'm finding it a bit tougher to keep up with XDA stuff. Fortunately, according to the downloads counters on AFH, it seems like plenty of people are still finding these guides useful, so I'm glad I could help in that respect.

    If you are helped by these guides, I would appreciate if you could express your thanks by hitting the thanks button. Apologies if I'm not around as much for the next several weeks, but I hope you all have a great summer! =)
    1
    @i5lee8bit, I appreciate your posts dude!

    You're a Gravity Box user, right? Any problem with June update or all smooth? I know Google did a feature drop this month.
    1
    There is a small mistake in the guide.

    The uploaded magisk file is called

    fastboot flash boot coral-rq3a.210605.005-magisk_patched-23000.img​

    The guide however wants a

    fastboot flash boot coral-rq2a.210605.005-magisk_patched-23000.img​

    Ergo copying the guide won't work. The file name must either be changed or the text from the guide must be changed.

    I changed the file name and it worked without an issue. Thanks again for your awesome guide. Updating a rooted phone has never been that easy.