yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] 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.
[Google Pixel 6 Pro] V0latyle:
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?
[Google Pixel 6 Pro] 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?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, the order doesn't matter; yes, they're equivalent.
[Google Pixel 6 Pro] V0latyle:
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
[Google Pixel 6 Pro] biTToe:
I'm the old DOS guy. THIS makes sense
[Google Pixel 6 Pro] V0latyle:
Right? Imagine feeling old because you were born prior to 1990
[Google Pixel 6 Pro] saabsaviorlee:
I also have the "hide the magisk app" option greyed out. Is that a result of the debug magisk we had to use to root dec update?
[Google Pixel 6 Pro] mac796:
You should prob just download the factory image all you have to do is extract it twice to get the boot and VBmeta out of it. Little more work with the ota.
[Google Pixel 6 Pro] Lughnasadh:
Are you using John's latest test version? If not, uninstall the Magisk app you have and install his as the "Hide the magisk app" is not greyed out on that version.

Load fstab from system/etc · topjohnwu/Magisk@56eb1a1

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] saabsaviorlee:
Thank you! I didn't catch there was another magisk update between when I updated last night to this morning! Topjohn on top of it!
[Google Pixel 6 Pro] MArtyChubbs:
no need to extract VBmeta. Just modify line 23... replace the -w with --disable-verity --disable-verification Will look like this:

fastboot --disable-verity --disable-verification update image-raven-sq1d.211205.017.zip

save and execute
[Google Pixel 6 Pro] old_fart:
What does it mean when 'adb devices' works and returns the device number but 'fastboot devices' returns nothing ?
[Google Pixel 6 Pro] Brisky86:
Yeah it is strange.

I am doing a full zip download from the google images website (1.9 GB) and the folder has a "META INF" folder that does not contain the images...
[Google Pixel 6 Pro] mac796:
He was asking how to get the boot img out of an ota
[Google Pixel 6 Pro] bleez99:
I just downloaded the US copy, nothing wrong with the zip (12.0.0 (SQ1D.211205.017, Dec 2021, US carriers))
[Google Pixel 6 Pro] Dragon Kumera:
thx cause I had no idea where to download it in github
[Google Pixel 6 Pro] Dragon Kumera:
so I downloaded the wrong zip. I did the non-labeled one. I bought my 6 pro from google store
[Google Pixel 6 Pro] Nergal di Cuthah:
Ota doesn't have boot.img you have to get it from the factory zip if you're sideloading ota. Follow the steps in the first post (ota sideload NOT RECOMMENDED) i follow those (and use the above debug magisk) and successfully rooted the latest ota
[Google Pixel 6 Pro] bradhoschar:
Confirmed working with 12.0.0 (SQ1D.211205.017, Dec 2021, US carriers).

Pixel 6 pro.
[Google Pixel 6 Pro] bradhoschar:
I take that back. Getting this error when flashing modded boot.img:

C:\adb\fastboot.exe: unknown option -- slot=all
[Google Pixel 6 Pro] Brisky86:
Thank you! I knew it had to be a "user error." ;)
[Google Pixel 6 Pro] vibrantliker:
I tried updating the same way I did last time:

replace -w with --disable-verity --disable-verification in the flash-all.bat file

then replacd the boot.img in the zip with the one we patch in Magisk (today's updated magisk)

and ran Flash-all but I'm in a boot loop?

Any ideas?
[Google Pixel 6 Pro] alt130:
I installed 12.0.0 (SQ1D.211205.016.A1, Dec 2021) on my 6 Pro using method 3, and patching with the existing Magisk Canary (23015) did nothing (booted fine but no root). However when I tried to patch boot.img with the new test version it goes into a bootloop until I go back to the original boot.img. Tried patching and installing again just in case it was a glitch, but no dice.

Seems like others are successful, anyone using the same non-US carrier version or have any advice?
[Google Pixel 6 Pro] vibrantliker:
That seems to be my issue as well, using the non-us carrier version.
[Google Pixel 6 Pro] alt130:
Well as long as it isn't just me, that's comforting. I can deal without root for a bit. I knew I shouldn't have jumped on it right away. :)
[Google Pixel 6 Pro] vibrantliker:
Where are you located? Wondering if I should be using the US carrier version? I'm in the US but have always used the non US carrier versions prior.
[Google Pixel 6 Pro] bleez99:
--slot all
[Google Pixel 6 Pro] Nergal di Cuthah:
The current belief is that the u.s. Carriers is a merge of vzw firmware and t.mo firmware allowing for subwave 5g connection for all (that's the current belief as it is)
[Google Pixel 6 Pro] vibrantliker:
what version should we be flashing if in the U.S and bought unlocked from Google?
[Google Pixel 6 Pro] Nergal di Cuthah:
There are two non u.s. Firmware one for EMEA (Europe middle east Asia) and one for everyone else. Which did you install and where are you?
[Google Pixel 6 Pro] Nergal di Cuthah:
I did u. S carrier (I'm verizon of a unlocked from Google)
[Google Pixel 6 Pro] bradhoschar:
Still not working.

PS C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools> fastboot flash boot --slot all magisk_patched.img

C:\adb\fastboot.exe: unknown option -- slot

PS C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools>
[Google Pixel 6 Pro] bleez99:
Put the slot switch last.
[Google Pixel 6 Pro] Nergal di Cuthah:
This is the command look at it and compare it to yours

You're missing (at least) the = sign
[Google Pixel 6 Pro] fil3s:
Works for me 😕 grab it from the github link

Idk bro. I read somewhere about it
[Google Pixel 6 Pro] bradhoschar:
Um. ok....?
[Google Pixel 6 Pro] Nergal di Cuthah:
It doesn't need to be put last

It's

Slot=all you have slot all
[Google Pixel 6 Pro] bradhoschar:
Right. I tried:

fastboot flash boot --slot=all magisk_patched.img

and @bleez99 said to try:

fastboot flash boot --slot all magisk_patched.img
[Google Pixel 6 Pro] Nergal di Cuthah:
H

He was wrong, the first time you had a space between the dash - and the word slot
[Google Pixel 6 Pro] VegarHenriksen:
Can anyone here post a short little guide on how to get root with the december update installed? I have tried back and forth following this thread, but I can’t get it working without running into an issue.

What Magisk Manager version do I need?

Thanks!
[Google Pixel 6 Pro] dd805bb:
no it doesnt require a wipe. i know for fact because yesterday i tried the ota old way. wouldnt boot due verified boot. i refalsh the image without the -w and adding "vbmeta --disable-verity --disable-verification" to the flashall.sh. which the rooting thread shows. and no it doesnt disable encryption and is not tied to encryption. its tied to verifying both slots against each other. when it sees 2 diffrent boot images it throws a corrupted data message. a flashall with above mentioned quoted command instead of the -w(line where -w is). please dont post unless you read the original rooting thread. it mentions how to get back your data without wiping. Noob.
[Google Pixel 6 Pro] dd805bb:
unless the new canary magisk has pushed yet, its a no go. there is a fix, just waiting on the update to canary.
[Google Pixel 6 Pro] alt130:
See earlier in this thread.
[Google Pixel 6 Pro] alt130:
I installed the "everyone else" (unlabeled) version. I'm in Canada.
[Google Pixel 6 Pro] bleez99:
I'm not wrong. No equal sign. --slot all is last on the command line.

fastboot flash boot some.img --slot all

I use it monthly.

A lot more in the past day...

Trust me on this one.
[Google Pixel 6 Pro] Nergal di Cuthah:
I'm just saying what worked for me was following the OP which uses = nothing more nothing less. The error here was the initial extra space, the poster made in following the directions. I meant no offense in saying you were wrong, or your method wouldn't work (though it didn't in the poster's case) but only meant to point out (from their original post) that the space was there.
[Google Pixel 6 Pro] fil3s:
.\adb reboot bootloader

.\fastboot flash boot --slot=all <copy and paste the path of the magiskpatched boot.img>
[Google Pixel 6 Pro] fil3s:
Grab the zip file from here and extract it. It contains the magisk update
[Google Pixel 6 Pro] A.Priori:
+1 I'd appreciate it too
[Google Pixel 6 Pro] vibrantliker:
finally got it . Is it necessary to go back to a Canary version of Magisk after getting root back?
[Google Pixel 6 Pro] Lughnasadh:
This is assuming you have already disabled verity and verification. If you haven't, follow the steps in the OP first.

1.Uninstall your current Magisk app

2. Install the debug Magisk app version from here (under artifacts and you need to sign into Github)... https://github.com/topjohnwu/Magisk/actions/runs/1577670575

3. Extract the boot image from the factory image and place on your phone

4. Patch the boot image in the new Magisk app

5. Place the patched boot image in your Platform Tools folder

6. fastboot flash boot <nameofpatchedbootimage.img>

7. Reboot
[Google Pixel 6 Pro] Nergal di Cuthah:
I don't know necessary but the app (in the view of my screenshot) shows as uninstalled (unlike my screenshot) if you don't
[Google Pixel 6 Pro] bradhoschar:
Attempt #1: C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools> fastboot flash boot --slot=all magisk_patched.img

C:\adb\fastboot.exe: unknown option -- slot=all

PS C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools>

Attempt #2:

C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools> fastboot flash boot--slot=all magisk_patched.img

target reported max download size of 261095424 bytes

sending 'boot--slot=all' (65536 KB)...

OKAY [ 1.443s]

writing 'boot--slot=all'...

FAILED (remote: partition (boot--slot=all) not found)

finished. total time: 1.491s

PS C:\Users\bradh\Desktop\platform-tools_r31.0.3-windows\platform-tools>
[Google Pixel 6 Pro] fil3s:
You might have try

.\fastboot reboot bootloader

in fastboot. It worked for me
[Google Pixel 6 Pro] bradhoschar:
Yeah, I was in bootloader mode.
[Google Pixel 6 Pro] fil3s:
I mean reboot bootloader and in fastboot , fastboot reboot bootloader. Then attempt the command to flash
[Google Pixel 6 Pro] bradhoschar:
Oh, I did.

adb reboot bootloader

fastboot (the commands I listed)
[Google Pixel 6 Pro] fil3s:
I just followed the root in this thread. Guess I was just lucky 🤔

https://xdaforums.com/t/pixel-6-pro-easy-step-by-step-unlock-root.4361847/#post-85947357
[Google Pixel 6 Pro] Nergal di Cuthah:
Instead of trying to type the command, i copy the command from the OP (ctrl+c) then right click on my terminal (command prompt or powershell whichever you use) and it pastes the command. I then make sure the name of my bootpatch file is the same as in cmd prompt by copying and pasting the file name into command line
[Google Pixel 6 Pro] bradhoschar:
NM.
[Google Pixel 6 Pro] Brisky86:
So I feel like a child trying to learn a new language today.

I am logged in to Github and on the link provided but cannot for the life of me find the tab for "artifacts" to download.

Is this under the Actions -> Workflow - > Magisk Build and then under one of the actions to choose? If so do you know which one to select? I feel like I am making this way harder than it needs to be...

Thanks!
[Google Pixel 6 Pro] SailorOfTheMind:
So anyone have any ideas when it is stuck at the g logo and nothing responds - ie cannot hold power down volume button combinations. Its been stuck here for over an hour...i really feel like this might be it on a new phone unless someone has some ideas.
[Google Pixel 6 Pro] fil3s:
These are the three files in the zip take your choice of which one to use, but I used app-release.apk and it worked fine on my 6pro
[Google Pixel 6 Pro] bd177:
try holding the power + vol down buttons down for at least 5 minutes. that happened to me when I first got the phone. I can't remember what caused it but I turned to watch tv while I was holding down the buttons and when I looked at the phone , I was at the bootloader screen.
[Google Pixel 6 Pro] SailorOfTheMind:
Thanks for this. This has been a rough month so far...and wasn't being patient.
[Google Pixel 6 Pro] Brisky86:
Oh boy now I am stuck in fastboot mode and unable to boot...

Any ideas of how to revert it back?

I can successfully flash the boot images from before but it still will not boot and drops back to the fastboot screen...
[Google Pixel 6 Pro] fil3s:
Can you use the Android flash tool? Only enable disable vbmeta and disable verification

Android Flash Tool

flash.android.com
[Google Pixel 6 Pro] Brisky86:
That just happened to me and now I am not able to get out of fastboot mode...

I followed this guide to unbrick the phone. :D

https://www.droidwin.com/how-to-unbrick-google-pixel-6-pro-via-fastboot-commands/
[Google Pixel 6 Pro] Brisky86:
Yeah, I could not figure that out.

It seemed to only let me select images that it already had in a database instead of what I already downloaded.

Probably user error again.
[Google Pixel 6 Pro] Brisky86:
Well, the patched boot image that the release linked apk of Magisk creates causes my phone to not be able to boot.

Only the stock boot image allows my phone to boot back up.

I will try the debug version next and see if maybe that one works....
[Google Pixel 6 Pro] Brisky86:
Weird.

Neither the "release" or the "debug" patched boot images from Magisk allow my phone to boot.

Only the stock boot image works. Perhaps these are the wrong versions of Magisk?
[Google Pixel 6 Pro] fil3s:
You wanna get them from the original source? They definitely work. On the 6pro anyway.

Load fstab from system/etc · topjohnwu/Magisk@ecea07b

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 6 Pro] Nergal di Cuthah:
Are you on the unlabeled "other countries" firmware (or U.S. or EMEA)
[Google Pixel 6 Pro] js042507:
I just went through this. It worked for me perfectly. Just like previous OTA updating methods. However, yes you need to have the new magisk build. But NOT just the apk installed. Debug or release...whatever. After installing the new version, do a direct install magisk method. Then after reboot it should say magisk (boot - TOP section) has this new version. Honestly, no idea if that's necessary. But I made sure both the image and apk were on this new "6" version before starting the update.
[Google Pixel 6 Pro] Brisky86:
I am sorry I am not sure what I am missing here.

I download the Magisk APK and install the app.

I choose the first option to install Magisk and there is not a direct install method only a patch a file method (which I have been using the unzipped boot.img from the December update).

Then I go to fastboot and flash the patched boot image from Magisk, but then it crashed back into fastboot unable to boot.

When the phone was bricked I manually flashed the December update (so I now have that but without root).

I am guessing that when I did that it messed up verity and verification? Is there a way to check the status of those without wiping the phone?
[Google Pixel 6 Pro] js042507:
Hmmm. Yeah you lost root at some point if there was not a direct install method. If you're working now with the latest update, I'd say just go through the process again. Make sure you have that beta magisk installed, patch the boot.img from the DEC update, boot into fastboot mode, flash both verity and verification vbmeta.img, and then flash the patched .img. However...since you are already booted, it might wipe your phone. But if you think you did that already, then you might be fine. You only have to do that one time. Unless you install an update file again. Not sure if there is a way to check the status, sorry. Not off the top of my head at least.
[Google Pixel 6 Pro] Brisky86:
Yeah that's what I was afraid of that I would be starting from scratch again.

Oh well. I will see if I am motivated to do that again soon. Wiping, moving everything back over, and playing with all my settings again is not something I am going to do tonight.

Thanks everyone for the help.

I have been rooting phones forever but each phone iteration seems to have its own learning curves.
[Google Pixel 6 Pro] damngood98:
New canary is up
[Google Pixel 6 Pro] NUGZZ420:
So this was happening to me I tried a bunch of things and then booted into safe mode and rebooted and things were rooted and good to go.

I used the US Dec build and the Stable Magisk. I had tried with canary and was having the same problem you but now I turned on some of my magisk mods and it bootloops again but into safe mode boots fine so its probably one of your Modules

EDIT

If your using the Pixel Tweaks Nov Module there is a updated on I think that's what was causing the problem for me
[Google Pixel 6 Pro] V0latyle:
Magisk Canary was updated to 23016 last night. This includes a fix for the vbmeta header issue, meaning that disabling verity/verification should no longer be required, and we should be able to root as we did before.

Additionally, for the Pixel 6 and 6 Pro, fstab will now load from /system/etc which should fix the root issue many of you were having.

Q: "If verity/verification are disabled, do I need to enable them now?"

A: No. The only thing you have to do is update to Magisk 23016.

Q: "Will enabling verity/verification wipe my data?"

A: No.

I will be updating the OP to reflect this.
[Google Pixel 6 Pro] vibrantliker:
I'm so afraid to update this magisk module for all the trouble I had updating but I've been doing this for years. Just a matter of uninstalling the temp Dec apk for the one you posted here, correct?
[Google Pixel 6 Pro] V0latyle:
DO NOT UNINSTALL MAGISK TO UPDATE. YOU MAY LOSE ROOT.

Simply update from within the app. Or, download the APK I linked and install it.
[Google Pixel 6 Pro] vibrantliker:
I meant uninstall the apk, not uninstall magisk. I don't have an update option on my current Magisk Manager.
[Google Pixel 6 Pro] fil3s:
I'm lucky then 😪 I uninstalled the magisk app, installed new canary , updated by direct install.
[Google Pixel 6 Pro] vibrantliker:
Same, thanks!
[Google Pixel 6 Pro] Ghisy:
Do you usually repatch and reflash the Magisk patched boot.img after updating Magisk?

I usually don't but not sure on the Pixel 6 Pro.
[Google Pixel 6 Pro] V0latyle:
No. I update Magisk, then use Direct Install within the app to update the boot patch.
[Google Pixel 6 Pro] Az Biker:
You're patchi

You're patching the boot.img from the zip folder of the image you just flashed right?
[Google Pixel 6 Pro] vandyman:
I think there a little confusion on patching the boot. img.

Here is what I have done on the last two updates;

1 - Download the new factory image and extract the boot. img.

2 - Patch the new boot. img

3 - install the factory image.

4 - flash the patched image.
[Google Pixel 6 Pro] A.Priori:
does this mean we don't need to use the debug.apk to root Dec?
[Google Pixel 6 Pro] V0latyle:
I do this a little backwards:

* Update bootloader/radio if necessary

* Dirty flash factory update

* Boot to Android, patch the new boot.img

* Reboot to bootloader, flash patched boot image

Also...For those of you having issues, the file you should start with should be explicitly titled boot.img. NOT bootloader.

Correct, Canary 23016 should work.
[Google Pixel 6 Pro] Ghisy:
OK. I just uninstalled then installed the Magisk update using the apk (didn't have the canary channel because it was the Magisk unofficial mod). Then Direct Install worked!

I feel like this used to never work for some reason. Now I know. Thanks!
[Google Pixel 6 Pro] Nergal di Cuthah:
Ok so for January if I'm doing ota side load (not recommended) i can let it boot to system without first booting to recovery even though that step precedes flashing the boot?
[Google Pixel 6 Pro] sensui123:
I had the same question since that's what I like to do. Went back through the process and thought about it and that should be the case with the new Magisk canaries. The issue is the forced wipe in Android 12 if vbmeta isn't disabled with a modified boot image. But the new Magisk canary releases should take care of this so theoretically you don't have to reboot to bootloader to disable vbmeta anymore after the update. We'll see who wants to confirm this first with some experimentation.

Side note, huge thanks to the OP (@V0latyle) for maintaining these threads on rooting w/ crystal clear instructions. I know OTA isn't "recommended" by him per say but I prefer to update this way as it gives me better understanding of what's going on and ensures the user understands what they're flashing along the way instead of modifying the batch file and placing a couple files in the right places.....then subsequently adding another couple pages to these threads when things go wrong because the user has no idea what they broke (due to not reading carefully/downloading wrong files etc). The flexibility of Android/recovery is a 2 way blade....comes with some responsibility IMO otherwise I'd stick with just not rooting/unlocking these phones.
[Google Pixel 6 Pro] V0latyle:
Yep.

Sideload the OTA, then patch and flash the boot image.
[Google Pixel 6 Pro] V0latyle:
I still don't recommend using the OTA, simply because you have to download two large files instead of just one, but it's not nearly as critical anymore - you can update however you want, then just patch and flash the boot image.
[Google Pixel 6 Pro] fil3s:
So I could say, just use Android flash tool to update, then flash magisk boot image? Simple as that?
[Google Pixel 6 Pro] V0latyle:
Yes.
[Google Pixel 6 Pro] fil3s:
Awesome! :) That's brilliant
[Google Pixel 6 Pro] fil3s:
I can confirm this actually works on the AU Dec build on p6pro
[Google Pixel 6 Pro] Lw00d:
just flash using recommended option, in OP 1# post

root is good. thanks V0latyle
[Google Pixel 6 Pro] HereticBG:
If I'm understanding this right, do the "To update via fastboot using factory image" steps in the 1st post need to be updated to no longer include the "--disable-verity --disable-verification" flags in the update command much like the Android Flash Tool steps no longer have you check the Disable Verity and Disable Verification check boxes?
[Google Pixel 6 Pro] deusfaux:
no longer needing to disable veri x2 - is this only for existing rooted ppl whom are updating? that is, is it still required for first time root?

edit: apparently it's not required, as I'm up and running, using Magisk 23016, didn't manually disable those flags or anything, just the normal magisk flash procedure.
[Google Pixel 6 Pro] nafi2000:
I'm stuck on the G screen. the light bar under the G logo is flashing as usual.
[Google Pixel 6 Pro] nafi2000:
Updated using unpatched boot image and patched it using new magisk . Version 15 is not working for me.
[Google Pixel 6 Pro] Lughnasadh:
Just FYI, Version 23015 doesn't work for anyone because the December update broke it. Version 23016 has the necessary fstab load to system/etc commit to make it work on the December update. 👍
[Google Pixel 6 Pro] V0latyle:
Correct, no need to disable verity/verification anymore.