yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] 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
[Google Pixel 6 Pro] Lughnasadh:
Yes, just as it says. After that you can update without wiping your data.
[Google Pixel 6 Pro] minhgi:
darn....i have all my apps setup already. Hard decision to make...
[Google Pixel 6 Pro] Lughnasadh:
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).

https://xdaforums.com/t/dev-vbmeta-...-boot-image-tool.4360405/page-2#post-86057943
[Google Pixel 6 Pro] minhgi:
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.
[Google Pixel 6 Pro] 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?
[Google Pixel 6 Pro] roirraW "edor" ehT:
The update is supposed to be Monday the 13th. After that, typically it's the first Monday of every month - it's just had some unusual update release dates (and in the case of November, two of them) due to extensive bug fixes.
[Google Pixel 6 Pro] WhiteReign:
Trying to get this but every time I do the directions I cant get out of bootloader. Sad Day Here! Even tried to change to fastboot set_active b and a
[Google Pixel 6 Pro] Az Biker:
I'm waiting until the January update drops.

December update was delayed, and if you can live without it until the January image drops, might as well go through the process once rather than now and again in a few weeks.

Make sure you have all the updated SDK tools, a few USB cables, and that you unzip the image TWICE and work with the second unzipped files.

The step by step is pretty detailed and thorough, so should be cut and dry to follow.

If you still get hung up, type the steps you are taking here, and we'll see if we can figure out what's going on.
[Google Pixel 6 Pro] Ghisy:
Dude, I rooted mine when I first unboxed it!! :D

Although, to be fair, I'm still using my 4 XL for now. I'm waiting for that December update and the HUGE amount of fixes that comes with it. I'm also not totally sold on Android 12 so I'm waiting for OS fixes as well.

(OT: I usually wait a few months to buy a Pixel and only pre-ordered the P6P because of the Bose 700 offer over here. Sold the headphones to a co-worker a few days ago so my P6P only cost me 680 euro (around $760))
[Google Pixel 6 Pro] Az Biker:
Oh make no mistake, mine was rooted just after I got it.

I just meant I'm not 'updating' my factory image until the January image drops 😁😁😁
[Google Pixel 6 Pro] Ghisy:
Ahhhh my bad then! I'll update mine tomorrow probably. There's nothing on it (except for Magisk) so if I mess up, there's no data loss there!
[Google Pixel 6 Pro] WhiteReign:
Thank you!!
[Google Pixel 6 Pro] slingblade01:
Thanks. I'll start on it tomorrow when the image is listed.
[Google Pixel 6 Pro] LLStarks:
Bumping for the OTA.
[Google Pixel 6 Pro] dd805bb:
just tried rerooting the december update. no dice. it was fun while it lasted for me. in magisk logs says denied mirror blah blah blah. i tried a few times. same everytime. anyone else got this too?
[Google Pixel 6 Pro] rester555:
Root is broken in latest December build
[Google Pixel 6 Pro] old_fart:
help ! I cannot get to first base here.

( asus tuf x570+ ) -and- ( windoze ten )

What to do when the 'fastboot' does nothing but wait . . . and do nothing . . . forever ?

I am using the Goog's 'platform-tools_r31.0.3-windows' and

'adb devices' -- returns a device in the list .... Ya !

'fastboot devices' -- returns nothing .... boo !

My ten year old mb died last week and I am using this new ryzen one today.

I have tried many different cables and no change.

NEW Note. found cache clear ( Google System Framework ) and cleared it . . .

Now instead of immed. fail, it tries forever to find an update. So, bottom line, no fix for me.
[Google Pixel 6 Pro] Az Biker:
I have the same Asus Tuf!

If you're getting response on adb but not fastboot, either your fastboot command is wrong fastboot devices or you have a temperamental USB port.

I believe the same drivers and SDK tools work for adb and fastboot equally, so I doubt it's a SDK issue.

I've never used adb so this might be a dumb question, but are you in the same window as the fastboot application and using the URL bar from THAT folder when typing fastboot devices?

Outside of these two ideas, I'm at a loss.

Best of luck, report back here what was wrong and how you fixed it once you get it up and running!
[Google Pixel 6 Pro] old_fart:
Thank you for helping.

To get into fastboot, i'll power off, then hold volume down, then press on power and waalaa . . .up pops fastboot on the phone. Then i'll go to android tools ( newest ones ) and type 'fastboot devices' and get naadaa. I used adb to give an app permission to work beyond initial level. I just got desperate and did a 'factory reset', hoping that would clear a glitched memory. But no joy. Same issue with zero change -AND- long setup ( settings and apps ) gone.

I talked to Google Fi support which was like talking to an idiot. They ultimately said I should warrantee replace the phone.

Last time this was working ( with old mobo - a month ago ) the usb was old and slow. This ryzen usb is ten times faster . . . maybe it's a speed issue ?
[Google Pixel 6 Pro] Az Biker:
You're booting into the bootloader menu right?

And you're opening command prompt by typing typing cmd from the address bar within the same folder that has the fastboot application? (It'll be within the second unzip image folder)

If so I'm out of suggestions.
[Google Pixel 6 Pro] old_fart:
yes and yes and wishing I did not have to replace . . . Maybe I'll go to my son's house and hi-jack his machine for an test. He's not a rotten kid...
[Google Pixel 6 Pro] Az Biker:
I wish I had better answers for you. Sorry.
[Google Pixel 6 Pro] old_fart:
Tried something off the wall. What the heck, what's to loose . . .

.

adb devices

List of devices attached

19091FDEE008K0 device

( this is good )

adb sideload raven-ota-sq1d.211205.017-5576891c.zip

adb: sideload connection failed: closed

adb: trying pre-KitKat sideload method...

adb: pre-KitKat sideload connection failed: closed

( no go . . . )
[Google Pixel 6 Pro] Lughnasadh:
Do you have the latest USB drivers installed? https://developer.android.com/studio/run/win-usb

And you mentioned trying different cables, but what about different ports?
[Google Pixel 6 Pro] old_fart:
Thank you.

Went into Device Manager and looked under 'portable devices' and saw it was Not happy-ville... Oh snap ! As you correctly guessed ( dang you're smart ! ), I needed to install the usb drivers to the pc. Then the Device Manage shows things in great shape.

Next used instructions from :

How to manually sideload an OTA update

Whenever Google pushes out a firmware update to any of its Pixel or Nexus devices, someone either catches the OTA update file...

9to5google.com

Went into built-in recovery mode and saw the dead android. What the heck ! Did the two finger dance of <up vol> & <pwr> ( many many times ) to get to the REAL recovery mode area. Wow ! Lots of good stuff here.

Did : adb devices

List of devices attached

19091FDEE008K0 sideload

( looks peachy )

Next did :

adb sideload raven-ota-sq1d.211205.017-5576891c.zip

Total xfer: 2.00x

( on pixel, acknowledged the zip, verified the zip, and installed the zip )

Rebooted and the p6p and settings, about, android version says I'm running the latest.

This all started because 'update' was glitched and hosed. Okay so now the 'update' seems to be fine.
[Google Pixel 6 Pro] Lughnasadh:
Awesome. Glad you got it going. Yep, outdated drivers, platform tools, or bad cables/ports are very common causes when glitches like this happen.
[Google Pixel 6 Pro] Utini:
Since the newest magisk changelog says that disable-verity is not required anymore:

Anyone tried it yet? How to proceed with the update when I already disabled verity?
[Google Pixel 6 Pro] Dave Lister:
I would say that until someone verifies that you can update without using --disable-verity and --disable-verification after having used those flags in the past, to just continue including them. It shouldn't hurt anything.
[Google Pixel 6 Pro] deusfaux:
ppl are saying it's not required for updates anymore. MY question 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] V0latyle:
@Az Biker, in case it hasn't been addressed already, disabling verity/verification is no longer required with Magisk 23016. Further, it incorporates a fstab fix specifically for the Pixel 6 / 6 Pro, so users should update ASAP

Anyone who is either using the Pixel 6 alpha, or who has hidden the Magisk app, must uninstall it before installing the new Canary.
[Google Pixel 6 Pro] Az Biker:
Thanks for the heads up, I'll update the OP accordingly.

So basically, back to the previous (pre disable verity) method of flashing the new factory image:

flash factory img

pull the boot.img and patch via the 23016 canary,

reboot using patched Magisk boot.img,

profit.

And can we just unhide Magisk app, or is uninstalling it the only method?
[Google Pixel 6 Pro] V0latyle:
Yup. We are back to the age old familiar method of rooting Pixels.

Regardless of whether one updates via automatic OTA, ADB sideload, ADB factory flash, or Android Flash Tool, the only thing that will need to be done to gain root is patch and flash the boot image.

Going forward, one can potentially avoid having to extract the boot image every time; use one boot image patched with 23016 as the "master", then after update, live boot that image and perform Direct Install in Magisk.

If someone is using Canary but hidden, the best process would be to update from within Magisk. Not sure if it should be unhidden prior to update. The issue is with manually installing the new APK - it won't install as an update, but a new app if the original is hidden.

I understand there was an alpha developed specifically for the Pixel 6; anyone using that will need to remove it before installing the new canary.
[Google Pixel 6 Pro] Dave Lister:
I updated Canary 23015 to 23016 via the app while it was hidden, extracted and patched the boot.img from the Dec update, and flashed everything with no issues.
[Google Pixel 6 Pro] V0latyle:
Good to know, thank you.
[Google Pixel 6 Pro] clipdawg05:
hello, i accidentaly flashed boot of oriole instead of raven for my 6p. everything seems to work. do i need to reflash or is it ok to stay
[Google Pixel 6 Pro] roirraW "edor" ehT:
I just personally confirmed that the boot.img is different on the P6 than the P6P, for the same factory image release version, so yes, I would reflash the correct boot. The boot was the only one you flashed from the wrong firmware?

Please do not offer your phone up as a sacrifice to the Phone Darwin award gods. :D
[Google Pixel 6 Pro] clipdawg05:
really, what happened to you. when you flashed the wrong boot. This is my first time unlocking and rooting since moto x3 so i dont really know what i am doing. just trying to follow instructions.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I didn't flash the wrong boot. I already had the Raven firmware zip downloaded, so I downloaded the corresponding Oriole firmware zip, extracted the boot.img out of each and checked their hash. They had different hashes so they're different files. When I said "I would reflash the correct boot," I just meant if I were in your shoes (and had flashed the wrong boot), I would flash the right one even if things are working so far. I was just reporting that the files are different so that yes, you should flash the correct boot.img. Don't forget to Magisk root the new boot.img before you flash it.

I hope I never flash the wrong boot. I may have before on some previous phone, I don't recall, but if so was probably a very long time ago like my first Android phone in 2010. I don't want to find out what happens and hope that I'm lucky like you are. :)

Understood - I was a little rusty on the Pixel 6 Pro too, but only two years worth of rust.
[Google Pixel 6 Pro] Golf c:
Strange issues flashing different kernels. I tried to go from Despair to another one and bootlooped. Dirty flashed factory image without disabling verity and verification. Tried to flash a kernel with boot image only. Bootlooped. Flash stock boot and perfectly fine.

I either need to disable verity and verification or I have a mismatched factory image with that particular kernel? I thought we could flash kernel boot images with unlocked bootloader and verity and verification enabled? I might be wrong about that. Very busy today and ran out of time to test my theories. Lol
[Google Pixel 6 Pro] V0latyle:
Disabling verity/verification should not be necessary, because you're getting a bootloop. If that were the problem, you wouldn't boot at all - device would remain in bootloader with the error message at the bottom "failed to load/verify boot images"

The December update introduced some new challenges, so if you're trying to use a pre-December kernel on the December firmware, that may be why. Try downgrading to November and see if you still bootloop with a custom kernel. Custom kernels will need to be updated with the fstab fix to work with the December release.
[Google Pixel 6 Pro] Golf c:
Thank you. The kernel is supposed to be a December image. Now that you mentioned it. It's not a traditional bootloop. I can't remember exactly what happened but it wouldn't boot. I had to toggle power buttons to get back to bootloader. I have to figure out the different kernels with the 4 images and the kernels with just the boot image. I'm stable on stock right now. But want to get back to tinkering when I get a chance.
[Google Pixel 6 Pro] V0latyle:
Try wiping cache. You can do this from bootloader:

fastboot erase cache
[Google Pixel 6 Pro] Golf c:
I will try that thanks. I know I still have remnants of magisk left also. Just going to be awhile till I get back to a PC. Luckily I'm stable. Just trying to figure out all these things like everyone else. Your very knowledgeable and kind. Thanks again.
[Google Pixel 6 Pro] Dragon Kumera:
but wasnt the cache partition removed? I tried with my pixel xl gen 1 on custom os and it errored.
[Google Pixel 6 Pro] Dragon Kumera:
So I guess this is not void and no longer should be done?

Should I delete the flash.bat script and just re unzip a non-modified one?
[Google Pixel 6 Pro] Az Biker:
I looped trying to flash Despair as well.

You have to flash a few additional files along with the patched image. Look at yesterday's comments on the Despair thread.

You're correct, that step is no longer required which is why it's removed from the instructions in the OP.

I'd start with the original factory flash-all.bat file.
[Google Pixel 6 Pro] Golf c:
I flashed the despair zip with no issues. Trying to flash another kernel with just a boot image screwed me up. Could have sworn he said we could flash other kernels. Probably misunderstood
[Google Pixel 6 Pro] non1oson:
thats helpful. for me ive already shifted and installed everything, settings, 2fas and allllllllll. is it possible to clone our 6 pro or similar? i havent done the intial unlock and root so im going to get a wipe. fully updated 6 pro today. i want root for bouncer app and app manager or just app manager to block apps that want permissions i dont want it to have, thats all really. any advice for users in my position?

or anyone else have advice they can share?
[Google Pixel 6 Pro] Ghisy:
Aren't we supposed to flash the stock kernel first in between custom kernels? I've always done that in the past and had no problems.
[Google Pixel 6 Pro] Golf c:
Afaik it's been off and on per device. It's always a good practice to do I think. Well I just rooted the stock boot image with new canary magisk without disabling verity and verification. So I know that works. I'm about to flash despair again in exkm. I guess my only question is do we need to disable verity and verification to flash certain custom kernels? Could have sworn I did it before. I think freak has a fix in his kernel for that.

Edit: Despair zip worked in exkm. So it's the other kernel with boot image only that won't work for me.
[Google Pixel 6 Pro] darbylonia:
Thanks for this guide! It really saved me as I had to recover from a soft-brick!🤪
[Google Pixel 6 Pro] roirraW "edor" ehT:
I believe the custom kernels each need to implement the same fix that Magisk Canary 23016 did, so that they don't require Verity and Verification to be disabled. I don't know which ones have already or which ones haven't. Since I've had them disabled and I wanted to put the latest CleanSlate back on, I played it safe and didn't flash vbmeta, so that I wouldn't change the status back to Enabled, since I'm not clear if CleanSlate has implemented the necessary fix. It may have, I'm just not positive.
[Google Pixel 6 Pro] Golf c:
Yep. I had it in my head that I could flash kernels without that disabled. probably from P5. I should have kept my vbmeta disabled, but I dirty flashed the factory image. That's what I get for being wrong. Lol.
[Google Pixel 6 Pro] Az Biker:
Just the .zip file, right? 107 0r 108?

I think I just tried flashing the patched despair kernel image (without the additional files) and that caused my bootloop.
[Google Pixel 6 Pro] Golf c:
I'm on 1.09 zip. Vbmeta enabled. Yep. Patching despair and another boot image doesn't work without disabling vbmeta. You can patch stock boot and flash despair zip in kernel manager
[Google Pixel 6 Pro] Ultimoose:
Question related to the sideload file -

I'm on a unlocked P6P purchased from google.

There are 4 options for sideload files, one for AU and EMEA don't apply to me. But that leaves 1 with no special designation and one for US Carriers.

I'm assuming I need the first one? The SQ1D....016.A1 December update? And not the SQ1D...017 December US Carriers update?
[Google Pixel 6 Pro] Lughnasadh:
That is correct. The A1 version, according to Google, is the global unlocked version purchased from Google.
[Google Pixel 6 Pro] Ultimoose:
Thank you so much for that validation @Lughnasadh I really appreciate it! :)
[Google Pixel 6 Pro] The.Jericho.Initiative:
Hello,

Thank you for the guide, I have two questions.

At the beginning of your walkthrough, you recommend downloading the most current factory image from the link provided - which would be December - I am unlocked, running US carrier agnostic from November - SD1A.210817.036. You then say to unzip the primary image, and a secondary image. Where did the second zip file come from? Am I simply creating two separate directories from one zip archive?

Regarding my second point of confusion, I downloaded the SDK from the link you provided, it contains no variation of a 'flash all' batch file. I have to assume I'm functionally retarded, but I cannot determine where my mistake has been made. The rest of your process seems relatively straightforward, but absent a clear understanding at the outset, I'm compelled to ask for clarification.

I sincerely appreciate any assistance you can offer.
[Google Pixel 6 Pro] roirraW "edor" ehT:
The second zip is inside the first zip.

The SDK (Platform Tools) doesn't have the flash-all.bat. The (first) zip file referenced in your first question above has the flash-all.bat.
[Google Pixel 6 Pro] kash_si:
Hopefully the attached screenshots will help.

I am using - "raven-sd1a.210817.037-factory-0827bca4.zip" as example.

The Contents of the First Zip file are -

View attachment 5490553

The Contents of - image-raven-sd1a.210817.037.zip file from the Main zip file above are -

View attachment 5490555

Hope this helps. Good Luck.
[Google Pixel 6 Pro] The.Jericho.Initiative:
My apologies.

My mistake is that somehow I seem to have downloaded: raven-ota-sq1d.211205.017-5576891c rather than: raven-sq1d.211205.017-factory-bf3da4b2. The second file does indeed include a second zip and a flash-all.bat

Having downloaded the incorrect file, I was lacking the context of the .bat residing in the image folder saved within the platform tools folder. Given that I was reading through the process before actually attempting it, I thought the SDK's platform tools folder was the original location of the .bat file.

You've helped me find what I needed.

Thank you.
[Google Pixel 6 Pro] The.Jericho.Initiative:
The flash-all method failed the device into a boot loop. I ended up side-loading the OTA with success, then the Magisk patched files weren't visible to the PC... Finally got it all patched, Zygisk enabled, denylists, et al.

Rooting hasn't been this lively in a while.
[Google Pixel 6 Pro] Dragon Kumera:
I been wondering this since it came out and never got a solid correct answer.
[Google Pixel 6 Pro] The.Jericho.Initiative:
I personally did not flash A1. I chose the US Carriers version.

Not that you particularly care what I did, simply that I am not seeing any negative externality of that choice. The device is working normally, I applied the safetynet 2.2.1 fix, configured and enforced deny lists, turned on Zygisk, and hid Magisk - with perfect success - including test setups of GPay, Netflix, et al.

I would not personally select the global image because I see no direct benefit in doing so. From what I understand, the US carrier version has specific and updated radio information that the global variant does not.

Hope this relieves a degree of pressure from your choice.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Me too, since as far as my understanding, the main differences between the versions are radio optimizations for the carriers available in the region the firmware is intended for.
[Google Pixel 6 Pro] Nergal di Cuthah:
I too, chose US carriers, as far as I've seen A1 is for Canada (and Australia before they got their own branch)
[Google Pixel 6 Pro] whatsisnametake2:
i'm new to pixel phones. if I root, then I later unroot, does it leave any trace that i've done so? I know samsung have a fuse trip thing. anything similar on pixel?
[Google Pixel 6 Pro] roirraW "edor" ehT:
No, not if you fully restore the factory image and re-lock the bootloader (in that order). I *think* re-locking the bootloader will factory reset your device (just like it does when you unlock the bootloader), so that's why you should be fully stock before re-locking the bootloader.

Nothing similar on Pixel as on Samsung. Google doesn't gimp your phone for unlocking the bootloader, and no permanent changes whatsoever.
[Google Pixel 6 Pro] whatsisnametake2:
ok thanks very much for the info. I thought I would try root for various things like hbm and substratum whilst it's still in the return period. will google pay and banking apps still work?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome!

Yes, if you follow the directions [How To Guide] Working SafetyNet with Pixel 6 Pro Android 12.

I think there are a few people around the world that couldn't get a banking app (I think particular banks) working, but most of us, yes, as long as you fix SafetyNet and add all your banking apps to Magisk Canary 23016's Deny list so they can't see root.