yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] ElvisXNX:
does this guide work on pixel 6a?

i have a pixel 6a, based on my research "oem unlocking" being grayed out is a big problem with pixel 6a but my device does not have that problem (see attached screenshots), that's a good thing i believe;

i have little to no experience in rooting but i do a lot of os tweaking, i run linux (fedora 38) on my laptop, just installed `android-tools` package and downloaded "12.1.0 (SD2A.220601.003.B1, Jul 2022)" factory image because i want to downgrade from android 14 to android 12, i have no idea which of the 12.1.0 images in the " "bluejay" for Pixel 6a" list at developer.google.com/android/images to download because i'm not in america so i don't use any of those carriers, so i picked the most unspecific one

should proceed with this guide at my own risk or should i go somewhere else more suitable?

p.s. this pixel 6a is a new device, no risk of data loss
[Google Pixel 6 Pro] Nergal di Cuthah:
Iirc you cannot downgrade to 12 because of the bootloader change that came with 13
[Google Pixel 6 Pro] ElvisXNX:
"bootloader change"? what does that mean?
[Google Pixel 6 Pro] majorfigjam:
Put simply, Google fixed a serious flaw in the Android 12 bootloader, and tripped a software fuse to stop anyone rolling back from 13+ to 12. It's described fully on the Google site where you would have downloaded the image.

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

There's also a sticky thread on the subject of roll back, at the top of page 1 here

Put even more simply, if you try to roll back to 12, YOU WILL LIKELY BRICK your 6A.
[Google Pixel 6 Pro] Nergal di Cuthah:
HARD BRICK! not fixable!. As major laid out don't do it

In fact if you haven't done it, go now and flash the bootloader to the slot not being used.

Her's the link from your device's forum, where you should be instead of p6p

PSA: Android 13 Botloader Anti-Rollback

***Note: THIS IS NOT A ROOT GUIDE. For updating and root instructions, check out my guide here.*** From the Pixel Images page: This applies to ALL Pixel 6 devices, regardless of whether or not you're rooted! This does NOT affect other Pixel...

xdaforums.com
[Google Pixel 6 Pro] ElvisXNX:
thanks for the heads-up guys, (luckily) i have only downgraded to android 13, not android 12, but now i'm running grapheneos on android 14 build UP1A.231105.003.2023112900 and it seems to have solved the app incompatibility issues i encountered on stock android 14
[Google Pixel 6 Pro] Lw00d:
when you first disable Verified Boot . you must wipe. then after that . you could keep updating every month with out wiping data.
[Google Pixel 6 Pro] BlakeSm:
What's the best way to backup everything un-rooted?
[Google Pixel 6 Pro] ram4ufriends:
This thread exactly has that. I just updated to 037 version without wiping, patched boot image and has root now.

https://xdaforums.com/t/read-this-before-updating.4356231/
[Google Pixel 6 Pro] Lw00d:
you really dont have any good option if you not rooted.

just do a google backup.
[Google Pixel 6 Pro] roirraW "edor" ehT:
No. You have to disable verity and verification as well, and you have to wipe after you disable them.
[Google Pixel 6 Pro] Utini:
You should add the commands to also update bootloader and radio upon initial unlock & root.

Else someone might ending updating to latest firmware without updating radio & bootloader ;-)

You should also mention that the initial unlock & root with disable-veritfy will wipe the phone :)
[Google Pixel 6 Pro] A.Priori:
Just what I was looking for to get started; hoping this is easy as my OP phones. I'll report back.
[Google Pixel 6 Pro] mcwups1:
I just received my 6 Pro. Looks like I'm already up to date out of the box. If I want to root, after I unlock bootloader (already done), I just have to install Magisk, grab Boot.img, from update file from Google, and patch it like normal?

Thanks in advance.
[Google Pixel 6 Pro] Az Biker:
Instruction to update factory image WITHOUT wiping data are near the bottom of the OP:

UPDATE Factory Image WITHOUT Wiping Data:

When you flash the factory image in STEP 8, it includes the bootloader, and radio.

Unzip the second image folder to see what is flashed when you type flash-all.

bootloader-raven-slider-1.0-7753224

flash-all

flash-all.sh

flash-base.sh

radio-raven-g5123b-92009-211008-b-7805583

image-raven-sd1a.210817.036

You still have to disable verity prior to installing Magisk.

From OP:

UPDATE Factory Image WITHOUT Wiping Data:

1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file

2- Open it with text editor and replace -w with --disable-verity --disable-verification in file (keep ONE space between commands)

3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder

4- Type FLASH-ALL

5- Let it boot into system and settle for a minute

6- Patch the boot image (follow steps 10, 12 -18 above)

OR you can follow these steps (below) skipping the factory image altogether:

Verified Boot is disabled by flashing /vbmeta with disable flags:

Code:

fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img
[Google Pixel 6 Pro] Oaklands:
In the initial instructioins, what boot image are we supposed to use? I tried the .37 version and get the slider error. I am doing this before rooting.

Edit: I think I figured it out. I was supposed to use .36 version to start. Going to try now.

Edit: That's what it was. All unlocked and rooted. Thanks for the ops post
[Google Pixel 6 Pro] michaelrager:
I am trying to move an app to the system and I keep getting the error that the System ROM does not have enough space. Can you help? I am not an expert, more of a novice, so the easiest way would be best thanks all!
[Google Pixel 6 Pro] Ultimoose:
Looks like I'm maybe a week to 10 days out from getting mine. I just wanted to say thank you to the OP for collecting and posting this information. it's been a while (2xl still daily driver) since I've done this and this kind of thread takes the stress out of getting back into it.
[Google Pixel 6 Pro] michaelrager:
I have been trying to do what is recommended when I search for possibilities, for example unistall apps you can install from google play so they are removed from system apps (this does nothing about giving me more space btw,) but to no avail.
[Google Pixel 6 Pro] mcwups1:
I obviously need to read up more on this. Before, I was extracting certain files and putting them in my "platforms sdk" file, and flashing those files from there.

I accidently hit "run" on the .bat file, and it installed the .037 from my extracted zip file without removing anything or putting in the platforms file. I didn't have to use CMD or anything. Crazy.

.037 is installed. Now, I just need to extract boot image for patching I guess.

I tried updating with fastboot and with instructions from one of the instructions and got this....
[Google Pixel 6 Pro] KOLIOSIS:
A bit rusty on root/etc..... been using ADB disabling on my past few devices vs root.

Anyhow,I'm kinda lost on the steps for root/patching boot image in Magisk....

I'm b/l unlocked,but,not sure what to do next.

Do I need to disable DM verity/vbmeta THEN flash the image,then reboot (possible factory reset) ,then patch the boot image (in Magisk) & flash in fastboot?

Trying to follow along w/a couple of tutorials on YouTube,but,the methodology seems to be a little different in each vs what's posted here @ XDA....

THX for any feedback.
[Google Pixel 6 Pro] E30Nova:
Does this work for carrier versions as well or only unlocked models?

I want to get the phone through T-Mobile because it’s faster than ordering from Google. My last Pixel phone was an unlocked model so I don’t know if that makes a difference.
[Google Pixel 6 Pro] Lughnasadh:
Yes, you will need to flash vbmeta.img with the 2 flags disabled:

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

After flashing this your phone should boot into Rescue Party, where you will have to factory reset. After this you can patch your boot image in Magisk, go back into the bootloader and flash the patched boot image with fastboot.

Going forward, when you do your monthly security updates you will have make sure you don't flash the vbmeta.img without disabling those 2 flags or you will have to wipe/factory reset again. You can follow the "Update factory image without wiping data" section in the OP (I find this the easiest), or there are other guides/methods in the forums you can follow (e.g. Sideloading the OTA... https://xdaforums.com/t/firmware-is-out-get-your-root-on.4353565/ ).
[Google Pixel 6 Pro] mcwups1:
Please excuse my stupidity. I updated to .037 and edited the .bat file to say "-w --disable-verity --disable-verification" before flashing. Does this not take care of it?
[Google Pixel 6 Pro] Lughnasadh:
You need to remove the -w and replace it with --disable-verity --disable-verification if you want to keep your data. Otherwise, you are defeating the purpose. The purpose is to update without having to wipe data. Leaving the -w in wipes data.
[Google Pixel 6 Pro] mcwups1:
Right, I wanted to wipe. It's a brand new phone that was on .036, and not yet activated. I'm wondering if I did wipe, with the --disable-verity --disable-verification into the .bat file, am I good to go ahead and install Magisk, and from now on, not wipe on future updates, or do I have to do this extra step after (fastboot flash vbmeta --disable-verity --disable-verification vbmeta.img)?
[Google Pixel 6 Pro] ElvisXNX:
per my knowledge once a pixel 6 is upgraded to android 13 its new bootloader will prevent from rolling back to android 12, so if i downgrade bootloader version then there will be no anti-rollback mechanism anymore, therefore i can downgrade to android 12 with no problems, right?

my bootloader version is currently bluejay-1.3-10674934 on this grapheneos (bluejay-factory-2023112900.zip image), while previous version was bluejay-1.2-8893284 on stock android 14 (UP1A.231105.003);

i have done some research (https://www.xda-developers.com/google-pixel-6-series-android-13-anti-rollback-bootloader-version)

and found that bluejay-1.2-8893284 is the bootloader version that implements anti-rollback mechanism, does that mean my newer bootloader versions also has anti-rollback? or is it a one-time thing?
[Google Pixel 6 Pro] Nergal di Cuthah:
Nope this will trip the fuse and you will be bricked

You really should take your issue to the bluejay board this is raven and there might be small differences (though i don't think there are)

Edit: there was a major flaw in the twelve bootloader. 12 wont run on 13 bootloader. It's the bootloader that can't be rolled back not the os. The os just breaks on the 13 bootloader.
[Google Pixel 6 Pro] Az Biker:
After the initial update, follow the UPDATE without wiping data instructions near the bottom of the OP. You'll always have to re-root since the new boot.img needs to be patched my Magisk.
[Google Pixel 6 Pro] mcwups1:
It appears that everything is fine. I have Magisk installed after patching image. I'm not getting any modules to pop up in the search though, so I guess I'll head to Magisk thread to see what's up there.
[Google Pixel 6 Pro] Lughnasadh:
Oh, you wanted to wipe, lol. My misunderstanding. Yeah, what @Az Biker said.

The Magisk Repo has been removed from the Magisk app. You can use this instead...

Release 0.1.2 Update · Fox2Code/FoxMagiskModuleManager

Add Traditional Chinese Translation by @cracky5322 Add fallback support links for a few modules

github.com
[Google Pixel 6 Pro] KOLIOSIS:
I successfully flashed the 2 flags & factory reset.

However,when I try to flash the patched boot image,I keep getting an error of image not found.

Should I be using the command from the OP (Step 17)?

My apologies if I missed something.

Also,is it OK to rename the patched boot image,as long as it has .img at the end?

One more seemingly obvious question:

Just want to make sure I'm patching the right thing....the file named "boot",from the .zip file.......
[Google Pixel 6 Pro] Lughnasadh:
You shouldn't need to flash to both slots. So you can just do fastboot flash boot <nameofpatchedbootimage.img>.

You should be able to rename the patched boot image (although I have never done it). I usually just put it in a labeled folder and copy and paste the name into the command prompt.

You should be patching the boot.img that you extracted from the factory image. It's located in the image-raven-sd1a.210817..037 zip file within the factory image (assuming you are on build .037).

If you are still having problems, then 2 things to check:

1. Make sure your Platform Tools are up-to-date. Latest I believe is 31.0.3

2. Make sure you have the correct (and latest) USB drivers installed on your computer... https://developer.android.com/studio/run/win-usb

EDIT: Oh, one very important thing. Make sure you are using the latest Canary version of Magisk.
[Google Pixel 6 Pro] KOLIOSIS:
Root has been achieved, thank you for your time & assistance, it's much appreciated. ✌️
[Google Pixel 6 Pro] Lughnasadh:
No problem. Glad you got it going 👍✌️
[Google Pixel 6 Pro] KOLIOSIS:
Yes,this does work on T-Mobile US models, that's what I have.
[Google Pixel 6 Pro] E30Nova:
Awesome, thanks!
[Google Pixel 6 Pro] Ultimoose:
Setting up a new P6P. Downloaded the lastest image 037 from google. (Not the verizon one)

Try to flash it, get a failure on version-bootloader check, has xxxx, wants xxxxx.

Download 036, flash that, no problems.

Try to flash 037 again and same problem, boot-loader failed the check. Any advice?

C:\ADB\platform-tools>fastboot update --disable-verity --disable-verification C:\ADB\RavenNovember37\image-raven-sd1a.210817.037.zip

--------------------------------------------

Bootloader Version...: slider-1.0-7753224

Baseband Version.....: g5123b-92009-211008-B-7805583

Serial Number........: 1A221FDEE005P4

--------------------------------------------

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.000s]

Checking 'version-bootloader' FAILED

Device version-bootloader is 'slider-1.0-7753224'.

Update requires 'slider-1.0-7860951'.

fastboot: error: requirements not met!
[Google Pixel 6 Pro] Ultimoose:
Never mind, I just added the -- disable commands to the flashall batch file instead and got 37 installed. Leaving this here in case it helps someone else.
[Google Pixel 6 Pro] Ultimoose:
@Az Biker Just wanted to say thanks again. All unlocked, rooted and safetynet'ed. Even etrade is working and it's one of those PITA apps in regards to figuring out if you're rooted or not.

Now comes the unfun part of setting the new phone up again.
[Google Pixel 6 Pro] Az Biker:
Glad everything went smoothly for you! Stop playing on the intranetwebs and get that device set up... slacker :p :p ;P
[Google Pixel 6 Pro] Ultimoose:
LOL, doing that now. SMS Backup and Restore is currently restoring 4 years of text messages on the P6P, probably an hour to go on that one. Probably about halfway done with data dumps from my 2XL -> OTG usb -> P6P. Plenty of progress bar watching going on. :)

Totally unrelated Google Auth makes it crazy simple to transfer entries over. I was pleasantly surprised about that.
[Google Pixel 6 Pro] me_droid:
Researching all this prior to my P6 purchase, think I'm ready. Just not clear on the safetynet part - how did you handle the safetynet setup? Thanks for the info.
[Google Pixel 6 Pro] mbonus:
https://xdaforums.com/t/working-safetynet-with-pixel-6-pro-android-12.4354149/
[Google Pixel 6 Pro] Ultimoose:
Just had to install the 'universal safetynet fix', see the post above for instructions.
[Google Pixel 6 Pro] Az Biker:
Sorry for the late response.

As other have already posted, just see the post (two above this one) for SafetyNet instructions (y)
[Google Pixel 6 Pro] GivIn2It:
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?
[Google Pixel 6 Pro] Az Biker:
Sorry for the slow response. Unfortunately, I don't have an answer for you. I've never received this error message, and this process has worked both times I've used it.

The thing that I don't get is, even if you're flashing the same bootloader that's already on your device, it should still flash like normal, just like doing a fresh install of the same factory image.

All I can suggest is start over after bootloader unlock steps, make sure you have the correct factory image, and that your spacing in fastboot is right (one space breaks between commands).

Hopefully someone with more experience will notice the problem and chime in.

If you figured it out, post the fix or what went wrong here for future reference :D

Good luck!

UPDATE: was looking through the threaqd to see if anyone else hit this, and found this a few posts above your original post:

Never mind, I just added the -- disable commands to the flashall batch file instead and got 37 installed. Leaving this here in case it helps someone else.
[Google Pixel 6 Pro] roirraW "edor" ehT:
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.
[Google Pixel 6 Pro] Lughnasadh:
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.
[Google Pixel 6 Pro] nummer:
would an adb backup work to restore my data after i wipe and root?
[Google Pixel 6 Pro] 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!
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] 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 :D

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.
[Google Pixel 6 Pro] Dragon Kumera:
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?
[Google Pixel 6 Pro] Az Biker:
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.
[Google Pixel 6 Pro] Dragon Kumera:
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?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes, in a little more than 13 hours.
[Google Pixel 6 Pro] kash_si:
Great guide with step by step instructions. Much appreciated.

Just rooted my TMO P6P.

Thanks (y)(y)(y):cool::cool:
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] almahix:
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.
[Google Pixel 6 Pro] hospadam:
Disregard, I caught my own mistake :)