How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet

Search This thread

Cornloaf

Member
Jul 9, 2007
24
1
Downloaded 12.1.0 (SQ3A.220705.004, Jul 2022) and applied. Phone reboots and it gives me a warning that my system is corrupt. Phone will not boot. I attempted this two times and then went back to 12.1.0 (SQ3A.220705.003, Jul 2022) and it took that successfully. I will wait until the August update comes out.
 

V0latyle

Forum Moderator
Staff member
Fastboot cannot load Master root?
What error do you get?
Downloaded 12.1.0 (SQ3A.220705.004, Jul 2022) and applied. Phone reboots and it gives me a warning that my system is corrupt. Phone will not boot. I attempted this two times and then went back to 12.1.0 (SQ3A.220705.003, Jul 2022) and it took that successfully. I will wait until the August update comes out.
What process did you follow?
 
  • Like
Reactions: roirraW "edor" ehT

Cornloaf

Member
Jul 9, 2007
24
1
What error do you get?

What process did you follow?
I get the red text "OS is corrupted" screen, press power to continue and it shows the Google logo and stays there. I have to hold down power/vol for 30+ seconds to shut it off.

I have tried three methods on here and got the same results. First time OTA was bugging me to install the update so I uninstalled Magisk (restored images), ran the update, installed Magisk on inactive slot and rebooted. This was the first time I got the corrupt OS error. I only had the .003 image so I restored that on the device, reapplied root, etc.

The next time I tried to update I used the Update and Root OTA sideload method. Same error with OS corrupted.

The final time (which I tried twice) was the Update and Root Factory Image method. I removed the -w so it would not overwrite my data. This also resulted in the corrupt OS screen.

After the failure with the OTA method, I made sure to have the patched boot.img from both .003 and .004 available just in case I was not able to get the device booted and back into Magisk.
 

V0latyle

Forum Moderator
Staff member
I get the red text "OS is corrupted" screen, press power to continue and it shows the Google logo and stays there. I have to hold down power/vol for 30+ seconds to shut it off.

I have tried three methods on here and got the same results. First time OTA was bugging me to install the update so I uninstalled Magisk (restored images), ran the update, installed Magisk on inactive slot and rebooted. This was the first time I got the corrupt OS error. I only had the .003 image so I restored that on the device, reapplied root, etc.

The next time I tried to update I used the Update and Root OTA sideload method. Same error with OS corrupted.

The final time (which I tried twice) was the Update and Root Factory Image method. I removed the -w so it would not overwrite my data. This also resulted in the corrupt OS screen.

After the failure with the OTA method, I made sure to have the patched boot.img from both .003 and .004 available just in case I was not able to get the device booted and back into Magisk.
OTAs can be pretty tricky. What version of Magisk are you using? There have bene issues with patching inactive slot prior to 25.2.

I had a similar problem on my wife's 5a when I tried to update via automatic OTA/patch inactive slot. Sideloading the OTA fixed the issue.

Most of the time, the reason why you'd get the Rescue Party screen is because system has detected a problem with the boot image - either the version doesn't match what you expected (like if you tried to boot an old boot image after updating) or there's a problem with the boot header.

You may be able to get running simply by flashing the boot image corresponding to the update. Don't use a patched boot image; focus on getting your device working again.
 
  • Like
Reactions: roirraW "edor" ehT

Cornloaf

Member
Jul 9, 2007
24
1
OTAs can be pretty tricky. What version of Magisk are you using? There have bene issues with patching inactive slot prior to 25.2.

I had a similar problem on my wife's 5a when I tried to update via automatic OTA/patch inactive slot. Sideloading the OTA fixed the issue.

Most of the time, the reason why you'd get the Rescue Party screen is because system has detected a problem with the boot image - either the version doesn't match what you expected (like if you tried to boot an old boot image after updating) or there's a problem with the boot header.

You may be able to get running simply by flashing the boot image corresponding to the update. Don't use a patched boot image; focus on getting your device working again.
I did get the device working again by using the Update and Root Factory Image method and rolling back to 003. I think I will stick with this version until the true August update comes out.
 

V0latyle

Forum Moderator
Staff member
I did get the device working again by using the Update and Root Factory Image method and rolling back to 003. I think I will stick with this version until the true August update comes out.
Oh okay, so maybe it's an issue with the .004?

I don't have a Pixel 6 so I can't test this
 
  • Like
Reactions: roirraW "edor" ehT

chinghaqa

Member
Aug 18, 2015
6
3
Hi V0latyle,i have some qustion by google pixel 6 pro
i come Taiwan my pixel 6 pro is unlock+ROOT
I have a few questions to ask
1. I swiped the SQ3A.220705.001.B1 card version. In this screen, the card has been stuck for a long time. Is it normal reading or really stuck. I updated it before.
I have a few questions to ask
1. I swiped the SQ3A.220705.001.B1 card version. In this screen, the card has been stuck for a long time. Is it normal reading or really stuck. I updated it before.
messageImage_1660283181114.jpg
 

V0latyle

Forum Moderator
Staff member
Hi V0latyle,i have some qustion by google pixel 6 pro
i come Taiwan my pixel 6 pro is unlock+ROOT
I have a few questions to ask
1. I swiped the SQ3A.220705.001.B1 card version. In this screen, the card has been stuck for a long time. Is it normal reading or really stuck. I updated it before.
It does take a while. The OTA package is transferred to the device, which then unpacks it and installs it to the inactive slot. This takes time.
 
  • Like
Reactions: roirraW "edor" ehT

V0latyle

Forum Moderator
Staff member
  • Like
Reactions: jcp2

fil3s

Senior Member
Aug 30, 2014
1,550
411
43
bendigo
mobiledevices11.blogspot.com
I'm not sure if this is related to root or magisk modules, but does anyone experience extreme lag on their p6pro? The phone lagged badly on 12.1 and I thought I was free of it on a13 beta but after installing a few magisk modules, the phone can become unusable sometimes. Anyone else experienced this?
 

Lughnasadh

Senior Member
Mar 23, 2015
3,904
4,172
Google Nexus 5
Huawei Nexus 6P
I'm not sure if this is related to root or magisk modules, but does anyone experience extreme lag on their p6pro? The phone lagged badly on 12.1 and I thought I was free of it on a13 beta but after installing a few magisk modules, the phone can become unusable sometimes. Anyone else experienced this?
Mine runs great with only 4 Magisk mods installed (Busybox, JamesDSP, Substratum & Systemless Hosts). Maybe uninstall your mods and install one by one to see if one of them is the culprit?
 
  • Like
Reactions: fil3s

fil3s

Senior Member
Aug 30, 2014
1,550
411
43
bendigo
mobiledevices11.blogspot.com
Mine runs great with only 4 Magisk mods installed (Busybox, JamesDSP, Substratum & Systemless Hosts). Maybe uninstall your mods and install one by one to se
Screenshot_20220814-031229.png
e if one of them is the culprit?

I uninstalled magisk the phone was really bugging out. Husky bootloop Saver might've been the issue. I'm back on magisk canary with no modules installed
 

Top Liked Posts

  • There are no posts matching your filters.
  • 5
    Thanks all,
    OEM is already unlocked.
    with out --slot all command , i have the same issue:

    C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools>fastboot flash boot magisk_patched-25200_LDJee.img
    Warning: skip copying boot_b image avb footer (boot_b partition size: 67108864, boot_b image size: 100663296).
    Sending 'boot_b' (98304 KB) OKAY [ 2.306s]
    Writing 'boot_b' (bootloader) unable to update boot image: use unmerged...
    FAILED (remote: 'failed to flash partition (boot_b)')
    fastboot: error: Command failed
    C:\Users\Admin\Desktop\platform-tools_r33.0.3-windows\platform-tools>

    Jumped from a android 12 original rom rooted to android 13.

    i have also sideloaded android 13 after applying the android 13 upgrade.
    Are you using the correct boot image to patch? The size seems to be off. The boot image should be around 64 MB. Looks like you may be using a boot image from a different device.
    5
    The need for Displax's USNF mod depends are what you are trying to do. For example, many people need that mod to use the new Google Wallet. For other things, kdragon's USNF may be sufficient.
    4
    Oh, I see what you mean. Unlocking the bootloader. I don't have Netflix so I have no experience with it, but have you implemented the items in the Pass Safetynet section of the OP? Also, on Android 13 a slightly different Universal SafetyNet Fix might be needed. See How To Guide Rooted, passing SafetyNet, Play Integrity, and GPay/Wallet contactless on A13 stable.

    @V0latyle I don't know if you want to include links to the modded version of the SafetyNet fix as linked to from that other thread ^. Others and I found it necessary in order to pass more certification on Android 13 than the official SafetyNet Fix does. Hopefully, the official version implements the necessary fixes eventually.
    I knew there was something I was forgetting...Since I'd have to modify every single one of my 9000 guides, this may take a bit
    4
    Thanks for your reply.

    Upgraded to 33.0.3 but i have the same issue.
    I use the image from the last android 13 official rom : 13.0.0 (TP1A.220624.021, Aug 2022)
    Right, but for which device (raven, oriole, bluejay, etc) and what is the exact name of the image you are patching (boot.img, vbmeta.img, etc).
    Where did you download it from? The ONLY acceptable source for Magisk APKs is the official GitHub, linked in the OP.

    When you're asked specific questions, you should give specific answers. If you don't give us the information we ask for, we can't be of much help.
    size: 67108864, boot_a image size: 100663296).
    Sending 'boot_a' (98304 KB)
    The image size is wrong, I think you're using the wrong image as @Lughnasadh pointed out. The size looks similar to the boot image of the 765G devices (4a 5g, 5, 5a) at 98,304KB (100,663,296 bytes). The correct boot image size for the Raven is 65,536KB (67,108,864 bytes)

    Make sure you are using THIS factory package, and ONLY use the boot image from it.

    The boot image you have been using is NOT from a Tensor series factory package. I don't know where you got it from, but you either took some shortcuts or ignored the instructions completely.
    4
    It took me a while to get comfortable with it myself and to figure it out, but this is what I've been doing with every update since July for my P6P (including upgrading to 13):

    1. Uninstall Magisk with restore (can leave modules)
    2. Hook phone to PC & switch to file transfer
    3. Open cmd prompt
    4. adb reboot fastboot
    5. Navigate to and select recovery
    6. Select apply update from adb > click power button to select
    7. adb sideload ota raven-ota-<whatever>.zip
    8. Reboot phone, allow setup to finish
    9. Extract full zip
    10. Extract boot.img from the other zip within the folder
    11. Copy boot.img to the phone
    12. Reinstall Magisk
    13. Patch boot.img
    14. Disconnect/reconnect phone from/to computer and select File Transfer again
    15. Copy patched boot img back to computer
    16. adb reboot fastboot
    17. fastboot flash boot --slot=all magisk_patched-<whatever>.img
    18. Reboot phone
    Hello! In general, your method looks fine to me just on a quick inspection - however, the main problem with Android 13 is when the bootloader (not boot) isn't installed to both slots. Until the Android 13 Stable bootloader is flashed to both slots, there is a chance that you could wind up with a fully bricked phone that can only be repaired by sending it in to Google.

    The very first thing anyone (who is concerned) should do when manually updating on any Pixel 6 is:
    Code:
    adb reboot bootloader
    fastboot --slot all flash bootloader bootloader.img

    After that, all update processes can be done absolutely just like any other month - no matter what method you use.
  • 92
    ⚠️⚠️⚠️ WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!⚠️⚠️⚠️

    If you are looking for my guide on a different Pixel, find it here:
    Update 6-20-22: Magisk 25.1 is recommended as this includes fixes for OTA updates, as well as support for the Android 13 beta.
    Discussion thread for migration to 24.0+.

    DO NOT use any version of Magisk lower than Canary 23016 as it does not yet incorporate the necessary fixes for Android 12 and your device.


    WARNING: YOU AND YOU ALONE ARE RESPONSIBLE FOR ANYTHING THAT HAPPENS TO YOUR DEVICE. THIS GUIDE IS WRITTEN WITH THE EXPRESS ASSUMPTION THAT YOU ARE FAMILIAR WITH ADB, MAGISK, ANDROID, AND ROOT. IT IS YOUR RESPONSIBILITY TO ENSURE YOU KNOW WHAT YOU ARE DOING.

    Prerequisites:


    Android Source - Setting up a device for development


    1. Follow these instructions to enable Developer Options and USB Debugging.
    2. Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
    3. Connect your device to your PC, and open a command window in your Platform Tools folder.
    4. Ensure ADB sees your device:
      Code:
      adb devices
      If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.
      If you see "unauthorized", you need to authorize the connection on your device.
      If you see the device without "unauthorized", you're good to go.
    5. Reboot to bootloader:
      Code:
      adb reboot bootloader
    6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
      Code:
      fastboot flashing unlock
      Select Continue on the device screen.

    1. Install Magisk on your device.
    2. Download the factory zip for your build.
    3. Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
    4. Copy boot.img to your device.
    5. Patch boot.img with Magisk: "Install" > "Select and Patch a File"
    6. Copy the patched image back to your PC. It will be named "magisk_patched-23xxx_xxxxx.img". Rename this to "master root.img" and retain it for future updates.
    7. Reboot your device to bootloader.
    8. Flash the patched image:
      Code:
      fastboot flash boot <drag and drop master root.img here>
    9. Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>

    1. Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
    2. Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
    3. Allow the update to download and install. DO NOT REBOOT WHEN PROMPTED. Open Magisk, tap Install at the top, then Install to inactive slot. Magisk will then reboot your device.
    4. You should now be updated with root.

    1. Download the OTA.
    2. Reboot to recovery and sideload the OTA:
      Code:
      adb reboot sideload
      Once in recovery:
      Code:
      adb sideload ota.zip
    3. When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
    4. Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
    5. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: You can use Payload Dumper to extract the contents of the OTA if you want to manually patch the new boot image. However, I will not cover that in this guide.

    Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
    1. Download the factory zip and extract the contents.
    2. Reboot to bootloader.
    3. Compare bootloader versions between phone screen and bootloader.img build number
      Code:
      fastboot flash bootloader <drag and drop new bootloader.img here>
      If bootloader is updated, reboot to bootloader.
    4. Compare baseband versions between phone screen and radio.img build number
      Code:
      fastboot flash radio <drag and drop radio.img here>
      If radio is updated, reboot to bootloader.
    5. Apply update:
      Code:
      fastboot update --skip-reboot image-codename-buildnumber.zip
      When the update completes, the device will be in fastbootd. Reboot to bootloader.
    6. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    7. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    8. Reboot your device. You should now be updated with root.
    Note: If you prefer, you can update using the flash-all script included in the factory zip. You will have to copy the script, bootloader image, radio image, and update zip into the Platform Tools folder; you will then have to edit the script to remove the -w option so it doesn't wipe your device.
    The scripted commands should look like this:
    Code:
    fastboot flash bootloader <bootloader image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot flash radio <radio image name>
    fastboot reboot bootloader
    ping -n 5 127.0.0.1 > nul
    fastboot update  --skip-reboot <image-device-buildnumber.zip>
    Once this completes, you can reboot to bootloader and either boot your master patched image, or if you patched the new image, flash it at this time.

    PixelFlasher by @badabing2003 is an excellent tool that streamlines the update process - it even patches the boot image for you.
    The application essentially automates the ADB interface to make updating and rooting much easier. However, it is STRONGLY recommended that you still learn the "basics" of using ADB.

    For instructions, downloads, and support, please refer to the PixelFlasher thread.

    1. Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
    2. When the update completes, the device will be in fastbootd. Reboot to bootloader.
    3. Boot the master root image (See note 1):
      Code:
      fastboot boot <drag and drop master root.img here>
      Note: If you prefer, you can download the factory zip and manually patch the new boot image, then flash it after the update. Do not flash an older boot image after updating.
    4. Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
    5. Reboot your device. You should now be updated with root.

    Please note that the SafetyNet API has been deprecated for the Play Integrity API. Because Play Integrity relies on Hardware Key Attestation for the MEETS_STRONG_INTEGRITY evaluationType, it is not possible, nor will it ever be, to pass Play Integrity on a modified system with an unlocked bootloader. More information here.

    However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod forces the "old" SafetyNet attestation, as if your device were running a version of Android older than 8.0.

    Mod available here. Do not use MagiskHide Props Config with this mod.

    Please note that this is a temporary solution; any apps that remove legacy support for SafetyNet will not benefit from this; the only reason this hasn't already happened is because doing so would prevent anyone using legacy Android versions older than 8.0 from using said apps.

    This is my configuration that is passing Safety Net. I will not provide instructions on how to accomplish this. Attempt at your own risk.

    Zygisk + DenyList enabled
    All subcomponents of these apps hidden under DenyList:
    • Google Play Store
    • GPay
    • Any banking/financial apps
    • Any DRM media apps
    Modules:
    • Universal SafetyNet Fix 2.3.1 Mod - XDA post
    To check SafetyNet status:
    To check Play Integrity status:
    I do not provide support for Magisk or modules. If you need help with Magisk, here is the Magisk General Support thread. For support specifically with Magisk v24+, see this thread.

    Points of note:
    • The boot image is NOT the bootloader image. Do not confuse the two - YOU are expected to know the difference. Flashing the wrong image to bootloader could brick your device.
    • While the Magisk app is used for patching the boot image, the app and the patch are separate. This is what you should see in Magisk for functioning root:
      screenshot_20211218-194517-png.5486339
    • "Installed" shows the version of patch in the boot image. If this says N/A, you do not have root access - the boot image is not patched, or you have a problem with Magisk.
    • "App" simply shows the version of the app itself.
    • If you do not have a patched master boot image, you will need to download the factory zip if you haven't already, extract the system update inside it, then patch boot.img.
    • If you prefer updating with the factory image, you can also extract and manually patch the boot image if desired.
    • Some Magisk modules, especially those that modify read only partitions like /system, may cause a boot loop after updating. As a general rule, disable these modules before updating. You are responsible for knowing what you have installed, and what modules to disable.


    Credits:
    Thanks to @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!
    9
    Magisk Stable is now at version 24.1, so I will no longer be providing any Magisk updates.

    You can use any version of Magisk now - Stable, Beta, or Canary. as long as it is 23016 or newer.

    Once again, if you want to switch versions of Maagisk, it is HIGHLY RECOMMENDED that you "Complete Uninstall" within Magisk before installing the new version. Multiple instances of Magisk can break root.

    If you simply want to update Magisk, the best way to do so is from within the app.


    Once the February update is out, I will perform some testing with installing to inactive slot, and if it works, I will update this guide.

    Given the low activity on this thread, I will probably close it if everything goes well with the next update.

    Thank you all for your testing and contributions.
    8
    My update process is to remove vbmeta.img (in addition to removing the -w flag in the flash-all script) from the factory zip before I flash it in fastboot. Seems to have worked so far, ymmv.
    7
    Magisk Canary updated to 23019
    Changes:
    - [Zygisk] Skip loading modules into the Magisk app to prevent conflicts
    - [MagiskBoot] Change `zopfli` to a more reasonable config so it doesn't take forever
    - [General] Several `BusyBox` changes

    Preferred method of update is from within Magisk app.


    If installing for the first time, here is the APK Download
    7
    I just used this method, (same one described on Magisk website here https://topjohnwu.github.io/Magisk/ota.html) and it worked perfectly, both root and safetynet.
    Can someone explain to me why you see all kind of guide to update which are far more complicated than that ?
    Part of it is due to device differences - non A/B devices can't use seamless updates, so re-rooting is only possible by either patching the boot image directly, or by flashing Magisk in a custom recovery.

    Part of it is also due to user preferences. Some people, like me, prefer to update using the factory images, instead of OTA.

    And part of it is probably a bit of misinformation mixed in with anecdotes, where people who don't fully understand how the process works, but they declare that something has to be done a certain way because of what worked for them.

    I try to stick to the first two. I've spent a lot of time learning about how Android works, so I make a point of providing instructions that align with how everything is supposed to be done, while accommodating alternatives for those who want them.

    Are you 100% sure?

    Cause topjohnwu said that OTA patching from within Magisk was broken for Pixel devices.

    See here

    Notice the date of that post, 16 months ago. Magisk Canary 23017 re-incorporated the ability to install to inactive slots.

    I have been following the commits closely, so when 23017 was released, I announced it in my guides. Had you read back a couple pages, your question has been answered.

    If you don't believe me, check the commits here.