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

[V0latyle]

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:

• Pixel 3
• Pixel 3XL
• Pixel 3a
• Pixel 3aXL
• Pixel 4
• Pixel 4XL
• Pixel 4a
• Pixel 4a (5G)
• Pixel 5
• Pixel 5a
• Pixel 6

For best results, use the latest stable Magisk release.
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

Spoiler: Downloads

Pixel OTA Images
Pixel Factory Images
Magisk Stable, Magisk Canary - Magisk GitHub

Spoiler: Unlock Bootloader

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:

   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:

   adb reboot bootloader

6. Unlock bootloader: THIS WILL WIPE YOUR DEVICE!

   fastboot flashing unlock

   Select Continue on the device screen.

Spoiler: Initial Root / Create Master Root Image

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:

   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>

Spoiler: Update and Root Automatic OTA

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.

Spoiler: Update and Root OTA Sideload

1. Download the OTA.
2. Reboot to recovery and sideload the OTA:

   adb reboot sideload

   Once in recovery:
   

   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):

   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.

Spoiler: Update and Root Factory Image

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. Spoiler: Update bootloader if necessary

   Compare bootloader versions between phone screen and bootloader.img build number

   fastboot flash bootloader <drag and drop new bootloader.img here>

   If bootloader is updated, reboot to bootloader.
4. Spoiler: Update radio if necessary

   Compare baseband versions between phone screen and radio.img build number

   fastboot flash radio <drag and drop radio.img here>

   If radio is updated, reboot to bootloader.
5. Apply update:
   

   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):

   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:

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.

Spoiler: Update and Root using PixelFlasher <<RECOMMENDED FOR NOVICES>>

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.

Spoiler: Update and Root using the Android Flash Tool

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):

   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.

Spoiler: Pass SafetyNet/Play Integrity

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.

However, @Displax has modified the original Universal SafetyNet Fix by kdrag0n; his mod is able to force basic attestation instead of hardware, meaning that the device will pass BASIC and DEVICE integrity.

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

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:

• YASNAC - GitHub

To check Play Integrity status:

• Play Integrity Checker - NOTE: MEETS_STRONG_INTEGRITY will ALWAYS fail on an unlocked bootloader.

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!

 

[roirraW "edor" ehT]

Thanks! Awesome write-up/explanation.

 

[Ghisy]

Now THIS is a useful thread! Thanks

I might try to root my P6P this week-end.

If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)

"6. Reflash vbmeta to disable boot verification"

 

[Cares]

Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img

 

[V0latyle]

Now THIS is a useful thread! Thanks

I might try to root my P6P this week-end.

If I already took the OTA from Google, can I just go to #6? (there's no data on my phone yet, just BL unlocked)

"6. Reflash vbmeta to disable boot verification"

Yes. You're basically on a clean factory flash. It might still throw a "corrupted" error at you but a factory reset fixes it.

Is it necessary to flash modified boot to "slot all"? I never did this before without issues. I always just did flash boot modifiedboot.img

Not really; I prefer to do that after OTA because OTA is an out of band update that installs to the inactive slot. You don't really have to use the slot commands at all, but I've come into the habit of using them.

 

[rickysidhu_]

The steps for a rooted update via OTA worked perfectly for me! Thank you a tonne for the guide. I was thinking I would have to factory reset for every monthly update, glad we dodged that bullet!

Thanks again.

 

[Bandsalat]

Is there any way to go back to DM Verity + AVB enabled without wiping after this?

 

[roirraW "edor" ehT]

Is there any way to go back to DM Verity + AVB enabled without wiping after this?

See @V0latyle's more informed answer below.

 

[avetny]

Thank you for your time. This thread should be sticky

 

[V0latyle]

Is there any way to go back to DM Verity + AVB enabled without wiping after this?

Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.

 

[xpdragon]

@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​

 

[mkhcb]

For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?

Someone needs to make a batch file for the above.

 

[V0latyle]

@V0latyle, Is there any downside of using Factory Update vs OTA Sideload for monthly update? Since I will need to download the factory zip anyway for both methods, I would go with the factory update.​

Nope, no downside that I'm aware of; many people used the factory images for updates on Android 11 and prior without any problems. Just make sure you flash it with --disable-verification --disable-verity

For the Android flash tool method, can't you just patch the boot image and add it to the flash tool and skip the reboot to then flash the patched boot?

Someone needs to make a batch file for the above.

I think you're confusing Android Flash Tool with something else. Take a look at the link - you connect your phone via USB and can install firmware direct from Google. There is no option to substitute your own files, which is a good thing.

As for adding the boot image to the flash process...I would avoid this, personally. You CAN edit the flash-all.bat to do this and some members here have. But, P6 and P6 Pro users have run into problems using a boot image they patched prior to updating, so here is my recommendation:

Flash the factory image with verity and verification disabled, and let the update complete including a boot to system. Once in system, you can then patch the boot image, reboot to bootloader, and flash it to /boot.

 

[Bandsalat]

> Yes - this is in fact the default state if the "disable" flags are not used. All you'd have to do is reflash vbmeta without any flags. Make sure you fully intend to do so, because 1. You won't be able to run a modified boot image, thereby preventing permanent root and 2. If you decided to disable vbmeta again, you would have to wipe data again.

Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.

 

[V0latyle]

Tried that, but the P6 Pro fails to boot and just goes back to the bootloader after this.

Tried what, exactly? It's easier to help if you're more specific about what you did and what result you're getting. Is there a message at the bottom of the bootloader screen?

 

[biTToe]

I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Are they equivalent i.e., does the order matter?

 

[roirraW "edor" ehT]

I have a dumb question:
There seem to be two different commands to disable flags:
fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
&
fastboot flash --disable-verity --disable-verification vbmeta vbmeta.img

Are they equivalent i.e., does the order matter?

No, the order doesn't matter; yes, they're equivalent.

 

[V0latyle]

No, the order doesn't matter; yes, they're equivalent.

The way I like to think of it is like this:

[Application: Fastboot/adb] [Command: What you want to do] [Destination: Where you want it to be done] [Modifiers: How you want it to be done] [Payload: What you want to be put there]

Those of us who grew up with DOS would probably do it like this:

fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification

But I believe it could also be done like this:

fastboot --disable-verity --disable-verification flash vbmeta vbmeta.img

 

[biTToe]

Those of us who grew up with DOS would probably do it like this:
fastboot flash vbmeta vbmeta.img --disable-verity --disable-verification

I'm the old DOS guy. THIS makes sense

 

[V0latyle]

I'm the old DOS guy. THIS makes sense

Right? Imagine feeling old because you were born prior to 1990