How To Guide [CLOSED] Firmware is out! Get your root on!

[V0latyle]

Update 12/15/21: Magisk 23016 incorporates fixes for vbmeta header patching; disabling verity/verification is no longer necessary. Update and root should work as it always has - simply patch and flash the boot image.

Any update method can be used. If you've already disabled verity/verification, simply don't worry about it at next update; no need to re-enable.

I am closing this thread.

Spoiler: Deprecated

On Android 12, boot verification must be disabled in order to run a patched boot image. Unfortunately, if you have never disabled it before, it will require you to wipe data. To be clear:
***************************************************
PERMANENT ROOT CURRENTLY REQUIRES A DATA WIPE.
***************************************************
However, if you don't want to lose your data, you can "live boot" the patched image as long as /vbmeta and /boot are stock. This will allow you to use temporary root. DO NOT attempt to Direct Install Magisk to the boot image.

For subsequent updates, it is imperative that you do not allow the device to boot into system before you have disabled Verified Boot.

What this means: If you sideload the OTA, IMMEDIATELY reboot to bootloader and reflash /vbmeta with --disable-verity and --disable-verification. If you dirty flash the factory image, make sure you add these two switches to the command.

If you fail to do this, and allow the device to boot into system, you WILL have to wipe data to disable it again.
IF YOU ARE ROOTED, DO NOT USE AUTOMATIC UPDATES AS THIS WILL REFLASH /VBMETA WITHOUT DISABLING BOOT VERIFICATION!

Factory Images

OTA Images

Latest Magisk Canary

Spoiler: To root:

1. On your device, enable Developer Options (tap build number 8 times), and enable the OEM Unlocking toggle. Reboot to bootloader:

2. adb reboot bootloader

3. Unlock bootloader:
   

   fastboot flashing unlock

4. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img and vbmeta.img from this zip.
5. Flash vbmeta:
   

   fastboot flash vbmeta --disable-verity --disable-verification <drag and drop vbmeta.img>

6. Allow the device to boot into Android. Once you have Magisk installed, copy the boot.img and patch it in Magisk, then copy it back to your PC.
7. Reboot to bootloader.
8. Flash patched boot image:

   fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>

9. Reboot into system.

Spoiler: For subsequent updates:

1. Download the latest factory image and extract it. Inside, you will find the bootloader image, the radio image, and the image-device-buildnumber.zip. Extract boot.img from this zip.
2. Reboot to bootloader.
3. Update bootloader and radio if they are out of date. BE CAREFUL, A MISTAKE CAN BRICK YOUR DEVICE! If you update the bootloader, remember to reboot back to bootloader so that the update reads the correct bootloader version.
4. Update system:
   

   fastboot update --disable-verity --disable-verification <drag and drop image-device-buildnumber.zip here>

   Note: If you get an error for bootloader/radio version, this means you need to update bootloader and/or radio; go back to step 3.
5. Allow the device to boot into Android. Copy the boot.img and patch it in Magisk, then copy it back to your PC.
6. Reboot to bootloader.
7. Flash patched boot image:

   fastboot flash boot <drag and drop magisk_patched-23xxx_xxxxx.img>

8. Reboot into system.

I personally do not recommend updating via OTA Sideload, as you would have to download and extract the factory zip anyway. AUTOMATIC OTA WILL LOSE ROOT AND REQUIRE A WIPE TO ROOT AGAIN.

Spoiler: If you choose to update via OTA Sideload:

1. Sideload the OTA. When complete, IMMEDIATELY reboot to bootloader.
2. Reflash vbmeta:

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

3. Boot to system and allow the update to complete.
4. Patch and flash the boot image.

Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification. Reflash vbmeta with the --disable options.

If you run into this recovery message

This means that verity and verification were not disabled before, and a wipe is required to proceed.

 

[Nekromantik]

one person had to wipe data otherwise it would not boot with verity disabled

 

[V0latyle]

one person had to wipe data otherwise it would not boot with verity disabled

Yeah, this is an ongoing issue with the Pixel 5 as well.

 

[snovvman]

Is the current belief that P6P/P6, like P4a and later will require a wipe when rooting after an update either by full image or OTA sideload?

 

[Cares]

If I disable verity and verification will it wipe my device? Also will this wipe remove my eSIM data?

I already unlocked bootloader and setup my device fully so I prefer to not have to start over.

Can I edit the flash.bat to disable verity and verification but remove the wipe flag?

fastboot update --disable-verity --disable-verification raven.zip

 

[rester555]

Wow, they are using an older image. I wonder if it includes the security update that we received when we first got the phone? The load that ends in .036....

EDIT: I am not sure I can do this since I updated to the .036 update. The boot image might be different.

 

[Goofy19882]

Grab it here!

Factory image - SD1A.210817.015.A4

OTA - SD1A.210817.015.A4

Magisk 23011

To root:

1. Download the factory image. Extract it, then extract the raven-image.zip inside it
2. Copy boot.img to your phone. Patch with Magisk, then copy patched image back to PC.
3. Unlock bootloader:
   

   fastboot flashing unlock

4. Flash vbmeta:
   

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

5. Flash patched boot image:
   

   fastboot flash boot magisk_patched-23xxx_xxxxx.img

6. Reboot, and you're done!

Note: If you run into a bootloader message
failed to load/verify boot images
this means you forgot to disable verity and verification.
If you run into a recovery message
Can't load Android system. Your data may be corrupted
Go ahead and factory wipe, it shouldn't be a big deal since you just did that with the bootloader unlock.

Thanks. Can confirm root is working perfectly
Didnt had to wipe data. Just did a clean wipe before doing rhe adb things

 

[rester555]

Thanks. Can confirm root is working perfectly
Didnt had to wipe data. Just did a clean wipe before doing rhe adb things

Did you have the Day 1 OTA security update before doing this?

 

[Goofy19882]

Did you have the Day 1 OTA security update before doing this?

No I havnt. Maybe this could be a problem

 

[kboya]

Super cool.
This isn't my bag anymore but I'm really pleased that Root is out already. It was only a matter of time and who knows what might be next with route.
Happy days with voice text (in the UK!)

 

[rester555]

No I havnt. Maybe this could be a problem

Agreed. I would be careful taking the OTA and trying to patch the boot image.

 

[Nekromantik]

Agreed. I would be careful taking the OTA and trying to patch the boot image.

I did that and it works fine. Im sure the kernel did not get updated in the OTA.

 

[rester555]

I did that and it works fine. Im sure the kernel did not get updated in the OTA.

Just for clarity. You took the Day 1 OTA on the P6 Pro. You then extracted the boot.img and vbmeta.img from today's binaries and patched boot.img in magisk. Went to bootloader, did the disabling of verification with vbmeta and then flashed the patched magisk image?

 

[Nekromantik]

Just for clarity. You took the Day 1 OTA on the P6 Pro. You then extracted the boot.img and vbmeta.img from today's binaries and patched with magisk. Did the disabling of verification with vbmeta and then flashed the patched magisk image?

Yes
I had to factory reset after disabling verity.

 

[rester555]

Yes
I had to factory reset after disabling verity.

Did you have to factory reset booted up or through recovery?

 

[Nekromantik]

Did you have to factory reset booted up or through recovery?

it wont boot after you disable verity so you get sent back to recovery where you can factory reset

 

[rester555]

it wont boot after you disable verity so you get sent back to recovery where you can factory reset

I think I will do a wipe.

 

[Starzboy77]

I just got my Pro and set it up and transferred data. Guess I'll have to start over when I unlock the bootloader.

Question though, when future OTAs release, what should we do? Okay to install and just lose root until new binaries are provided to re-root or would we install to new slot through magisk to keep root?

 

[V0latyle]

Is the current belief that P6P/P6, like P4a and later will require a wipe when rooting after an update either by full image or OTA sideload?

The potential workaround, which doesn't seem to be solid, is to sideload the OTA, then immediately enter fastboot, and flash /vbmeta and /boot. Sometimes you'll still end up in Rescue Party, where you can either flash back to stock and try again, or give up and wipe. We are still testing over at the Pixel 5 forum.

If I disable verity and verification will it wipe my device? Also will this wipe remove my eSIM data?

No - these flags themselves do not command a wipe; data wipe is separate. I'm not sure about eSIM but I have never had an issue with my phone provisioning on Verizon after a wipe.

I already unlocked bootloader and setup my device fully so I prefer to not have to start over.

Can I edit the flash.bat to disable verity and verification but remove the wipe flag?

Yes.

Wow, they are using an older image. I wonder if it includes the security update that we received when we first got the phone? The load that ends in .036....

EDIT: I am not sure I can do this since I updated to the .036 update. The boot image might be different.

Yeah, I would wait until the .036 firmware drops.

 

[Cares]

Well I removed the wipe flag and added disable verify and verification but got an error that didn't let me boot. I had to factory wipe unfortunately. So I guess I'm back to setting up my device.