How To Guide [Pixel 6 Pro] Easy STEP BY STEP Unlock-Root-Update

[roirraW "edor" ehT]

Hi Az Biker. I was following your guide to the letter. Everything worked as you said until I got to the fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.037.zip. I got :
--------------------------------------------
Bootloader Version...: slider-1.0-7714574
Baseband Version.....: g5123b-91479-210916-B-7738070
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'slider-1.0-7714574'.
Update requires 'slider-1.0-7860951'.

fastboot: error: requirements not met!

So what do I do now?

First, and please don't take this badly, it is discouraged to post the same question in multiple threads or multiple times unless absolutely necessary (like no answer for days), and certainly not within 15 minutes of each other.

@vlubosh answered you in the other thread here, and I agree with his answer. Basically, since you're starting from scratch anyway, you can just use the full firmware flash (albeit modified to disable verity and verification as well) instead of using the OTA update. This won't guarantee you won't have the same problem updating the same way you tried when the next OTA comes out next week, but this will get you going for now. See his specific answer in the other thread I linked to.

 

[Lughnasadh]

Hi Az Biker. I was following your guide to the letter. Everything worked as you said until I got to the fastboot update --disable-verity --disable-verification image-raven-sd1a.210817.037.zip. I got :
--------------------------------------------
Bootloader Version...: slider-1.0-7714574
Baseband Version.....: g5123b-91479-210916-B-7738070
Serial Number........:
--------------------------------------------
extracting android-info.txt (0 MB) to RAM...
Checking 'product' OKAY [ 0.001s]
Checking 'version-bootloader' FAILED

Device version-bootloader is 'slider-1.0-7714574'.
Update requires 'slider-1.0-7860951'.

fastboot: error: requirements not met!

So what do I do now?

A few things you can try in addition to what @Az Biker said:

1. Try flashing the bootloader manually fastboot flash bootloader <nameofbootloader.img>

If that works then immediately reboot into the new bootloader and run the fastboot update command again

2. After you get that error (you should still be in fastboot), immediately run the fastboot update command again. Have seen this work for 1 person in the past.

3. Try different cables

4. Make sure Platform Tools are up-to-date

5. Try the flash-all method

EDIT: 6. Use Android Flash Tool as @roirraW "edor" ehT said or you can always just update via OTA and then disable verity and verification afterwards so you won't have to wipe again when new update comes out on Dec. 6.

 

[nummerGDD]

would an adb backup work to restore my data after i wipe and root?

 

[GivIn2It]

OK Az Biker, heres how I got it sorted. The Android Flash Tool won't, as of now, pick up .037 from a search. It will open .037 from one of the links on the firmware page. I did that, but it kept failing network wise, so I went to the flash-all.bat and looked at it. I couldnt figure out what ultimoose did, especially since there is a line in that file that contains "fastboot -w" and I could not find that on the internet or in the fastboot help file. So I decided to make my own batch file to fix the particular problem I had, a bootloader mismatch. Here are its contents:

fastboot flash bootloader bootloader-raven-slider-1.0-7860951.img
fastboot reboot-bootloader
ping -n 5 127.0.0.1 >nul
fastboot flash radio radio-raven-g5123b-92009-211008-b-7805583.img
fastboot reboot-bootloader

At this point I was ready to continue with your guide at step 7. I took a while, it went to fastbootd screen but wasnt done copying files. Waited until the files finished copying, did a factory reset (had to but meant nothing since the phone's brand new) booted into system. Being paranoid that the verification verity hadn't taken due to a reference in the raven file copy about vbmeta not being present or some such (I forgot the specifics) I ran fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img again just to be sure. Then I was able to complete your guide without a hitch. I think this bootloader mismatch problem might be .037 specific.
Finished setting up the device, re booted, still rooted, success. Updates Disabled.

I damn well won't be updating until a foolproof way to do so without losing root surfaces.

What would be helpful info: what does "fastboot -w" mean?
Is there a way to check if the "verification verity" thingy stuck, is active, etc...

Thanks for your help, Az Biker

I find this forum quite hard to navigate. When I do "search this thread" the software returns all kinds of crazy results unreleated to the current thread. Bring back the old XDA!

 

[Dragon Kumera]

So I am bit confused. Last time I did this was pixel xl gen 1 verizon model before the lockout.

I just got pixel 6 pro but waiting till christmas to open it. So I was gonna try and get all the files ready first.

I downloaded the ota images that are in zip file and dont see a flash all like I did with pixel xl gen 1 ota images.


Also this whole --disable-verity --disable-verification really confuses me.

 

[Az Biker]

OK Az Biker,

-w in the FLASH ALL script is the command to WIPE data.

After replacing the -w with the disable verity command, SAVE the file, reopen the file and verify the replaced command stuck.

I'm not sure how to tell if it worked other than being able to keep root after rebooting

So I am bit confused. Last time I did this was pixel xl gen 1 verizon model before the lockout.

I just got pixel 6 pro but waiting till christmas to open it. So I was gonna try and get all the files ready first.

I downloaded the ota images that are in zip file and dont see a flash all like I did with pixel xl gen 1 ota images.


Also this whole --disable-verity --disable-verification really confuses me.

I never use OTAs for updating. I always use the factory image.

With the factory image zip, you unzip that initial folder, then a secondary zip folder is created from unzipping the initial zip.

Open the SECOND unzipped folder and there is the FLASH ALL script. Within the FLASH ALL script there is this line

127.0.0.1 >nul fastboot -w update image-raven-sd1a.210817.036.zip

remove the -w and replace it with --disable-verity --disable-verification then SAVE the file, reopen it to ensure the edit is saved (otherwise you erase everything), make sure you leave only ONE space between the existing text and the text you inserted.

 

[Dragon Kumera]

-w in the FLASH ALL script is the command to WIPE data.

After replacing the -w with the disable verity command, SAVE the file, reopen the file and verify the replaced command stuck.

I'm not sure how to tell if it worked other than being able to keep root after rebooting



I never use OTAs for updating. I always use the factory image.

With the factory image zip, you unzip that initial folder, then a secondary zip folder is created from unzipping the initial zip.

Open the SECOND unzipped folder and there is the FLASH ALL script. Within the FLASH ALL script there is this line

127.0.0.1 >nul fastboot -w update image-raven-sd1a.210817.036.zip

remove the -w and replace it with --disable-verity --disable-verification then SAVE the file, reopen it to ensure the edit is saved (otherwise you erase everything), make sure you leave only ONE space between the existing text and the text you inserted.

Ok I apparently downloaded the wrong images from the factory image link lol. So just redownloaded and got a flash all bat file so changed bat to txt and edited it that way then changed back to bat.


So once I unlock the bootloader and flash with this it will all be set and unlocked/root? I will just have to install magisk?

 

[Az Biker]

Ok I apparently downloaded the wrong images from the factory image link lol. So just redownloaded and got a flash all bat file so changed bat to txt and edited it that way then changed back to bat.


So once I unlock the bootloader and flash with this it will all be set and unlocked/root? I will just have to install magisk?

I don't change the flash all .bat file to a text file (not sure if that borks anything or not), I just right click and EDIT the flash all.bat file and save it.

 

[Dragon Kumera]

I don't change the flash all .bat file to a text file (not sure if that borks anything or not), I just right click and EDIT the flash all.bat file and save it.

Ya It just opens it in text file anyways. But I am on windows 11 so kinda forgot where they moved edit to.

Also apparently december ota update in a day?

 

[roirraW "edor" ehT]

Also apparently december ota update in a day?

Yes, in a little more than 13 hours.

 

[kash_si]

Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?

There are some really good guides by V0latyle here & here, and by roirraW "edor" ehT here which are great for veteran/regular users who are really familiar with adb/fastboot and the commands, steps used in the unlocking, rooting environment.

This step by step is for people like ME who are not adb/fastboot gurus, who need every step spelled out so we don't brick our over-priced flagship devices

............

Great guide with step by step instructions. Much appreciated.

Just rooted my TMO P6P.

Thanks

 

[OMGBrowniez]

Thanks for the awesome step-by-step. For those flashing from windows a bit of advice: You can use PowerShell to do the whole process by placing .\ before the commands.

 

[almahix]

Ready to Unlock, Root, and Update factory images on your Pixel 6 Pro?

Thanks AZ_Biker. This is an excellent resource and much appreciated. I am in between power user and fastboot expert, mostly just not overly intrepid. I unlocked the bootloader right after unpacking the box, but haven't rooted yet as I don't look forward to having to reload all the data I will lose. As an aside, I remember you from a previous forum, perhaps OnePlus 7 Pro? Nice to see you again.

 

[hospadam]

Disregard, I caught my own mistake

 

[minhgi]

So if follow this step to unverified my boot, this willwipe my data? First time attempting root for P6P and OEM Bootloader alreadied unlocked and coming from P2XL.

***WARNING: the following step erases your data, ALL OF IT, this is REQUIRED the first time you update and root. See UPDATE Factory Image WITHOUT Wiping Data: near bottom of OP to update after root, without wiping your data ***

8- Flash the factory image by typing fastboot update --disable-verity --disable-verification (drag the image.zip file here OR type in the file name (image-raven-xxxxxxxxx.zip) hit enter

 

[Lughnasadh]

So if follow this step to unverified my boot, this willwipe my data? First time attempting root for P6P and OEM Bootloader alreadied unlocked and coming from P2XL.

***WARNING: the following step erases your data, ALL OF IT, this is REQUIRED the first time you update and root. See UPDATE Factory Image WITHOUT Wiping Data: near bottom of OP to update after root, without wiping your data ***

8- Flash the factory image by typing fastboot update --disable-verity --disable-verification (drag the image.zip file here OR type in the file name (image-raven-xxxxxxxxx.zip) hit enter

Yes, just as it says. After that you can update without wiping your data.

 

[minhgi]

Yes, just as it says. After that you can update without wiping your data.

darn....i have all my apps setup already. Hard decision to make...

 

[Lughnasadh]

darn....i have all my apps setup already. Hard decision to make...

You can wait a bit and follow the development in the thread I'm linking. He's working on a Magisk version that will enable you to flash Magisk-patched boot images and still boot without having to disable verity and verification. Actually, he's trying to get it incorporated into the official Magisk but until then is making his own version. He's tested it on another device (Pixel 5a) but is waiting until the December update comes out to test it on this device.

And he is also working on his own tools as well (see OP in the thread).

[DEV][EOL] Vbmeta Patcher, Devinfo Patcher, and Boot Image Tool

The original purpose of these three apps was to help deal with the changes in Android 12 when taking an OTA. Most of the functionality has been superseded by the newest builds of Magisk. Vbmeta Patcher is still useful when migrating from Magisk...

forum.xda-developers.com

 

[minhgi]

You can wait a bit and follow the development in the thread I'm linking. He's working on a Magisk version that will enable you to flash Magisk-patched boot images and still boot without having to disable verity and verification. Actually, he's trying to get it incorporated into the official Magisk but until then is making his own version. He's tested it on another device (Pixel 5a) but is waiting until the December update comes out to test it on this device.

And he is also working on his own tools to do the same as well (see OP in the thread).

[DEV][EOL] Vbmeta Patcher, Devinfo Patcher, and Boot Image Tool

The original purpose of these three apps was to help deal with the changes in Android 12 when taking an OTA. Most of the functionality has been superseded by the newest builds of Magisk. Vbmeta Patcher is still useful when migrating from Magisk...

forum.xda-developers.com

this looks promising. thanks. I spend half a day setting up my phone. It's not fun when you have alot of MFA apps set up on the phone already.

 

[slingblade01]

I just received my P6P. It's still in the box waiting to be rooted.
I know an important update is due out any day now.
I also see Magisk will be tested and significantly improved after the update release.

Should I wait a few days or is the update expected near the end of the month?