How To Guide [GUIDE] Pixel 6 Pro "raven": Unlock Bootloader, Update, Root, Pass SafetyNet
- Thread starter V0latyle
- Start date
Yes. The update was pushed August 4. This was the file that I used to patch the boot.img. I am still getting the OTA prompt. I am going to give it another try.
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.
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.
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
I will test again with .004 when the August update comes out so I can just jump forward with that if there are issues!
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.
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.
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.
Sorry if I also ask, but despite the date, is
12.1.0 (SQ3A.220705.004, Jul 2022)
the latest Factory Image, i.e. the August update?
12.1.0 (SQ3A.220705.004, Jul 2022)
the latest Factory Image, i.e. the August update?
That's the latest but it's not the August update. That hasn't been released yet.
fil3s
Senior Member
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?
fil3s
Senior Member
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?
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.
-
104
WARNING! IF YOU ARE UPDATING TO ANDROID 13 FOR THE FIRST TIME, READ THIS FIRST!
Official updates for this device will end October 2024.
If you are looking for my guide on a different Pixel, find it here:
- Pixel 3
- Pixel 3XL
- Pixel 3a
- Pixel 3aXL
- Pixel 4
- Pixel 4XL
- Pixel 4a
- Pixel 4a (5G)
- Pixel 5
- Pixel 5a
- Pixel 6
Discussion thread for migration to 24.0+.
Note: Magisk prior to Canary 23016 does not incorporate the necessary fixes for Android 12+.
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:
- Latest SDK Platform Tools - if Platform Tools is out of date, you WILL run into problems!
- USB Debugging enabled
- Google USB Driver installed
- I recommend using Command Prompt for these instructions; some users have difficulty with PowerShell.
Make sure the Command Prompt is running from your Platform Tools directory!
Android Source - Setting up a device for development
- Follow these instructions to enable Developer Options and USB Debugging.
- Enable OEM Unlocking. If this option is grayed out, unlocking the bootloader is not possible.
- Connect your device to your PC, and open a command window in your Platform Tools folder.
- Ensure ADB sees your device:
If you don't see a device, make sure USB Debugging is enabled, reconnect the USB cable, or try a different USB cable.Code:
adb devices
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. - Reboot to bootloader:
Code:
adb reboot bootloader - Unlock bootloader: THIS WILL WIPE YOUR DEVICE!
Select Continue on the device screen.Code:
fastboot flashing unlock
- Install Magisk on your device.
- Download the factory zip for your build.
- Inside the factory zip is the update zip: "device-image-buildnumber.zip". Open this, and extract boot.img
- Copy boot.img to your device.
- Patch boot.img with Magisk: "Install" > "Select and Patch a File"
- 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.
- Reboot your device to bootloader.
- Flash the patched image:
Code:
fastboot flash boot <drag and drop master root.img here> - Reboot to Android. Open Magisk to confirm root - under Magisk at the top, you should see "Installed: <Magisk build number>
- Before you download the OTA, open Magisk, tap Uninstall, then Restore Images. If you have any Magisk modules that modify system, uninstall them now.
- Take the OTA update when prompted. To check for updates manually, go to Settings > System > System Update > Check for Update
- 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.
- You should now be updated with root.
- Download the OTA.
- Reboot to recovery and sideload the OTA:
Once in recovery:Code:
adb reboot sideload
Code:adb sideload ota.zip - When the OTA completes, you will be in recovery mode. Select "Reboot to system now".
- Allow system to boot and wait for the update to complete. You must let the system do this before proceeding.
- Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
Please note that the factory update process expects an updated bootloader and radio. If these are not up to date, the update will fail.
- Download the factory zip and extract the contents.
- Reboot to bootloader.
-
Compare bootloader versions between phone screen and bootloader.img build numberIf bootloader is updated, reboot to bootloader.Code:
fastboot flash bootloader <drag and drop new bootloader.img here> -
Compare baseband versions between phone screen and radio.img build numberIf radio is updated, reboot to bootloader.Code:
fastboot flash radio <drag and drop radio.img here> - Apply update:
When the update completes, the device will be in fastbootd. Reboot to bootloader.Code:fastboot update --skip-reboot image-codename-buildnumber.zip - Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
flash-allscript 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-woption so it doesn't wipe your device.
The scripted commands should look like this:
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.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>
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.
- Follow the instructions on the Android Flash Tool to update your device. Make sure Lock Bootloader and Wipe Device are UNCHECKED.
- When the update completes, the device will be in fastbootd. Reboot to bootloader.
- Boot the master root image (See note 1):
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.Code:
fastboot boot <drag and drop master root.img here> - Your device should boot with root. Open Magisk, tap Install, and select Direct Install.
- Reboot your device. You should now be updated with root.
SafetyNet has been deprecated for the new Play Integrity API. More information here.
In a nutshell, Play Integrity uses the same mechanisms as SafetyNet for the BASIC and DEVICE verdicts, but uses the Trusted Execution Environment to validate those verdicts. TEE does not function on an unlocked bootloader, so legacy SafetyNet solutions will fail.
Before asking any questions, please read this post.
For help passing Play Integrity verdicts, see this thread.
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:
- "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 @badabing2003 , @pndwal , @Displax , @Az Biker , @ipdev , @kdrag0n , @Didgeridoohan , and last but not least, @topjohnwu for all their hard work!9Magisk 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.7Magisk 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
