yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] roirraW "edor" ehT:
That is definitely the correct command.

Official Instructions for Locking/Unlocking the Bootloader

fastboot flashing lock

If using Windows, check Device Manager and see if the driver shows as being installed. If not, Get the Google USB Driver. You should already have that and the latest Platform Tools since you obviously unlocked the bootloader but definitely double-check in Device Manager.

Can you do:

adb devices

?
[Google Pixel 6 Pro] Nergal di Cuthah:
Also did you re-enable allow oem unlock and usb debugging before trying the command?

Edit: oops quoted warrior not oq
[Google Pixel 6 Pro] vibrantliker:
View attachment 5459253

and fastboot devices:

View attachment 5459255

fastboot flashing lock:

View attachment 5459259

it says "invalid android images, skip locking"

Do you know what that means?

Should I reflash stock firmware and try again?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yes, flash the stock firmware. Your phone should be 100% stock before re-locking the bootloader - I believe I have that information in the OP. Also, you know that re-locking the bootloader will wipe your phone, correct (but so will flashing the stock firmware unless you remove the "-w" from the script)?

I think technically, you might be able to have your phone not 100% stock, but it's definitely got to be 99.9%. I'd always play it safe and reflash the factory image before re-locking unless you haven't rooted - but even if never rooted if all else fails, I'd still flash the factory image.

I don't think it even lets you disable the OEM Unlock in Developer Options if you already have the bootloader unlocked. It's grayed out for me, but good thought about USB debugging, although theirs is definitely enabled.
[Google Pixel 6 Pro] vibrantliker:
Thanks, is there a link somewhere with instructions for flashing the stock firmware? I usually take the ota's then reroot. Also, I want it to wipe the phone as I'm returning it and keeping the P6
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome!

In the OP of this thread in the Factory Images section is the link to Google's Factory Images for Nexus and Pixel Devices which includes the instructions for how to flash at the top (above the list of firmware for the various Pixels). Sometimes I just Google for Pixel Factory Image to find it. :)
[Google Pixel 6 Pro] vibrantliker:
Thanks, I was just trying that. It looks like I just click the flash-all.bat after I extract the firmware (after placing it in my platform-tools folder?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! Sounds right, although I usually open a command prompt in the Platform Tools folder and type "flash-all" from there, but double-clicking it might work too. I know it "should", but...
[Google Pixel 6 Pro] vibrantliker:
Why am I having so much trouble with this???

I see this when flashing the stock firmware at the end:

View attachment 5459317

and still can't lock bootloader
[Google Pixel 6 Pro] roirraW "edor" ehT:
Do you have everything/the platform tools in a very deep folder? If so, try moving it to closer to the root such as C:\Users\Me\Downloads\T\Platform Tools\.

Is that just from double-clicking it or did you try opening a command prompt in the Platform Tools folder and typing "flash-all" (enter)?

Check the SHA-256 hash to see if it matches what Google's site says it should be?

Try rebooting the PC?
[Google Pixel 6 Pro] vibrantliker:
Maybe I should just do a factory reset first?

ok, I'll try all that. what about doing a factory reset of the phone as well?
[Google Pixel 6 Pro] roirraW "edor" ehT:
You can't do a factory reset unless the phone is 99.9% stock, just like locking the bootloader. If the not being stock is what's causing your issues, then I doubt if you'll be able to factory reset, or at least I doubt if factory reset will solve your issues.

Also, factory reset just deletes all user data. It can't set your phone's actual firmware back to 100% stock if it's not already. It doesn't have some place it can get the full stock firmware from. You can try it if you want, but I won't hold my breath, and I'm not responsible on if it causes you more problems than solves.

I've been wrong before, though.

Are you sure the bootloader is actually unlocked?
[Google Pixel 6 Pro] vibrantliker:
yup, the bootloader is unlocked
[Google Pixel 6 Pro] vibrantliker:
I used Android Flash Tool and that flashed it, then I was able to lock the bootloader!!

​
[Google Pixel 6 Pro] roirraW "edor" ehT:
Awesome! Yay!
[Google Pixel 6 Pro] vibrantliker:
appreciate you trying to help me!
[Google Pixel 6 Pro] Maledict:
safetynet-fix v2.2.0, which supports Zygisk, has been released for free
[Google Pixel 6 Pro] V0latyle:
Those of you who have been using it...are you getting SafetyNet pass, any issue with security/DRM sensitive apps working?
[Google Pixel 6 Pro] capntrips:
SafetyNet is passing, and the three apps I use that detect root (bank, broker, insurance) are working, as well
[Google Pixel 6 Pro] V0latyle:
Nice. What about DRM (Amazon Prime, Netflix, etc)?

I believe Facebook detects root as well...I've discovered some odd behaviour when it does (not allowing use of an external browser for instance)
[Google Pixel 6 Pro] phaino00:
Downloaded both (Amazon and Netflix) from the playstore after passing SafetyNet with SafetyNet fix 2.2.0 installed.
[Google Pixel 6 Pro] V0latyle:
I'm not sure what I'm looking at there...I assume they work?
[Google Pixel 6 Pro] phaino00:
Sorry for the lack of clarity. They (Amazon and Netflix apps) do both work and the screenshot is a capture from the DRM Info app. 🤦
[Google Pixel 6 Pro] roirraW "edor" ehT:
New factory images and OTA images .037 and .037.A1 are available. Pixel 6 Pro Factory Images

Manually mashing my Check for update button results in nothing, so give it some time to OTA for those who aren't rooted (yet). Or wait to see if it makes anything worse for anyone who gets the OTA first. 😜

Everyone, make sure your phone is charged enough for whether you'll take the OTA or flash manually.
[Google Pixel 6 Pro] Lughnasadh:
Well, this is certainly a surprise. Probably a hotfix for something. Haven't found a changelog yet.
[Google Pixel 6 Pro] Nergal di Cuthah:
Otas are up too, but I'll wait until we make sure it doesn't kill root

Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com
[Google Pixel 6 Pro] roirraW "edor" ehT:
Yeah, November in general still shows "Coming soon" on the Pixel Update Bulletins page.

It won't kill root if you re-root the new boot.img and flash it.
[Google Pixel 6 Pro] V0latyle:
DO NOT take the automatic OTA if you're rooted. Not only will you lose root, you will lose the ABILITY to root, and you'll have to wipe data again to get it back.

Refer to my guide here on how to update and reroot. I recommend dirty flashing the factory zip.

Remember, if you take the automatic OTA, or otherwise update without re-disabling vbmeta, you will NOT be able to flash a patched boot image, and you will have to wipe to disable vbmeta again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
The automatic OTA "should" fail to apply when rooted, shouldn't it? At least it use to without any harm, but that was back before the disable verity/verification days.

Or is it just a matter of we don't have enough experience yet to say whether trying to take one will be harmful or not?
[Google Pixel 6 Pro] Nergal di Cuthah:
Already with you on that, i sideload only and follow your guide, which is easy and spot-on. I only meant that hopefully this update's boot is patchable with current canary of magisk. I follow both your and warrior's guides and have zero problems with my phone.
[Google Pixel 6 Pro] V0latyle:
There have been mixed experiences. I am still getting the notification to update on my P5. I have previously been able to install automatic OTAs while rooted; they may fail the first time, but usually work the second time.

Because of this new issue with vbmeta and data wipe, I disabled automatic updates in developer options. The notifications are annoying but I can deal with it until the December update comes out.

Previously, taking automatic OTA while rooted just meant you'd lose root until you could flash a patched boot image again.

But, because we now have to make sure verity and verification are disabled every time we update, it is critical that we do not allow the device to automatically update - the consequence being you have to wipe your device to get root back.

Personally I wouldn't even sideload the OTA because of the added complexity in needing to download the factory image as well. Save yourself the time and bandwidth and just dirty flash the factory image with verification and verity disabled. Or use the Android Flash tool to do the same thing.

Again, I would recommend that you don't bother with the OTA at all. Use the Factory Image method, either via ADB or via the Android Flash Tool.

I don't see why the update would interfere with patching, but I've seen stranger things happen.
[Google Pixel 6 Pro] Lughnasadh:
Just to let everyone know, updating to .037 and re-rooting (without wiping anything) worked with no problems. My method is to just replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. I then let it reboot, patch the boot image, return to bootloader and flash the patched boot image.

Canary 23014

EDIT: Thank you @ipdev for confirming my inquiry that this method would work back on Nov. 4 👍
[Google Pixel 6 Pro] stroke55:
Updated to 037 as well (dirty flash) with latest Magisk alpha. Safetynet is okay :)

Edit: I patched the boot.img before I flashed the OTA as Magisk is hidden and would have to be recovered after flashing the OTA.
[Google Pixel 6 Pro] Dr. Krieger:
What's the changelog for 037? Can't seem to find any.
[Google Pixel 6 Pro] spr33:
Not released yet
[Google Pixel 6 Pro] Nekromantik:
i not got notification for the update yet but may just download image
[Google Pixel 6 Pro] roirraW "edor" ehT:
Should be here when it's ready: Pixel Update Bulletins

But it still doesn't even list the .036 changes, so who knows when.
[Google Pixel 6 Pro] Az Biker:
.037 is a "maybe" update.

Just flash it.

Maybe you'll like it.

Maybe you won't.

:p :p :p
[Google Pixel 6 Pro] bouchigo:
The only difference I can notice is in the vendor.img. I'm not sure exactly what changed, but that seems to be the only image that changed size...of course there could be very small changes elsewhere that wouldn't be noticeable in file size.

Also, a new bootloader.
[Google Pixel 6 Pro] stroke55:
BTW with 037 the flickering screen while the device is off and you shortly press the power button (without starting the phone) has been fixed - at least on my device :)
[Google Pixel 6 Pro] eg1122:
Can confirm this method works!
[Google Pixel 6 Pro] blackroseMD1:
Worked for me as well. Thanks!
[Google Pixel 6 Pro] BlakeSm:
Only my bootloader is unlocked. If I want root do I have to wipe? I'm currently on .036
[Google Pixel 6 Pro] Nergal di Cuthah:
Yes because you need to do the verify step
[Google Pixel 6 Pro] vibrantliker:
How do you get into the flash-all.bat file?
[Google Pixel 6 Pro] blackroseMD1:
If you're on Windows, just right click on the file and select Edit. It should open up in Notepad. Then you can make the changes and save it.
[Google Pixel 6 Pro] tylermaciaszek:
I'm in pain, made a dumb mistake edited the flash-all.sh file not the .bat so I got wiped...
[Google Pixel 6 Pro] vibrantliker:
this line? fastboot -w update image-oriole-sd1a.210817.037.zip
[Google Pixel 6 Pro] blackroseMD1:
Yeah. Erase -w and replace it with --disable-verity --disable-verification
[Google Pixel 6 Pro] vibrantliker:
I was wondering, why can't we replace the boot.img with the one we patch in Magisk?
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think I did that once many years ago, but I realized before I ran the batch file.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Actual .037 OTA coming through now. 14.56 MB
[Google Pixel 6 Pro] eg1122:
You can, but you still have to do the disable commands.
[Google Pixel 6 Pro] vibrantliker:
like this:

fastboot --disable-verity --disable-verification update image-oriole-sd1a.210817.037.zip

?
[Google Pixel 6 Pro] vibrantliker:
by doing what blackroseMD1 said?
[Google Pixel 6 Pro] eg1122:
Yes
[Google Pixel 6 Pro] blackroseMD1:
Exactly.
[Google Pixel 6 Pro] vibrantliker:
and I can replace the boot.img with the one we patch in Magisk then I wouldn't have to go back and reroot?
[Google Pixel 6 Pro] Starzboy77:
Where can I get the flash-all bat files from?
[Google Pixel 6 Pro] roirraW "edor" ehT:
They come in the factory image zip file: Pixel 6 Pro Factory Images
[Google Pixel 6 Pro] Starzboy77:
Thanks!
[Google Pixel 6 Pro] vibrantliker:
Cool, gonna try that now, just put all this in my Platform tools folder and Flash-all?

View attachment 5460601
[Google Pixel 6 Pro] eg1122:
Did you replace the stock boot.img in the zip and edited the flash-all.bat? If so, I'd say you good to go. I have not done the replacement boot.img on pixel 6, but have done it before.
[Google Pixel 6 Pro] vibrantliker:
I did do both
[Google Pixel 6 Pro] Starzboy77:
Is replacing the stock boot.img required? Could I just patch the boot after flashing the OTA and then flash the patched boot to regain root?
[Google Pixel 6 Pro] eg1122:
That's what most do, myself included. @vibrantliker just wanted to do it all in one go.
[Google Pixel 6 Pro] vibrantliker:
WORKED!!
[Google Pixel 6 Pro] Starzboy77:
Do you run the flash all bat in bootloader?
[Google Pixel 6 Pro] vibrantliker:
I ran Flash-all in the command prompt
[Google Pixel 6 Pro] BlakeSm:
Will this wipe me if I haven't already done it?
[Google Pixel 6 Pro] eg1122:
Yes, boot phone into bootloader then run script
[Google Pixel 6 Pro] eg1122:
Disabling verity and verification will require wipe.
[Google Pixel 6 Pro] roirraW "edor" ehT:
FYI, my actual ~15 MB OTA is taking forever. It's been in the optimizing stage (before rebooting) for over half an hour.
[Google Pixel 6 Pro] Starzboy77:
Updated using flash-all.bat method. Worked perfectly and re-rooted. I assume this confirms we will be able to OTA without wiping which is great!

Also, thanks to everyone for your help!
[Google Pixel 6 Pro] cd993:
Is there a change log/bug fix list for the new 037 update?
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://xdaforums.com/t/new-factory...itory-of-relevant-links.4352027/post-85955107
[Google Pixel 6 Pro] Homeboy76:
Yes, you can take the OTA without wiping. If you are rooted and you take the OTA you will not be able to re-root until you wipe your device. Hence, the do not take the OTA posts above.
[Google Pixel 6 Pro] Starzboy77:
I meant that we can update our phones without wiping and retaining root. Consensus was that it was unknown if we could update while rooted without wiping. I assume we are more certain now that we will be fine.
[Google Pixel 6 Pro] Homeboy76:
Yeah you're right, we can update and re-root our device using the flash-all method with modified flash-all.bat file fastboot flash --disable-verty --disable-verification update image-oriole-SD1A.999999.999.zip without wiping your device. :)
[Google Pixel 6 Pro] LLStarks:
Heh. We all came to the same conclusion on the flash-all method. Google's flashing tool isn't quite ready.

For regular Pixel 6 bros: fastboot update --disable-verity --disable-verification oriole-sd1a.210817.037-factory-ae9f34e0.zip

To root just download the correct factory image, reach into the inner zip inside, pull out the boot, Magisk patch it.
[Google Pixel 6 Pro] mkhcb:
On the new update, I am having lots of TMo connectivity issues. Am I alone?
[Google Pixel 6 Pro] biTToe:
Thanks. I was confused because I didn't see that mentioned in the OP

Steps 6 & 7 are new to me. -not something I did on my 6XL

Thanks again

ƒ
[Google Pixel 6 Pro] 96carboard:
6 is just an easier way to reboot it into recovery than trying to shut it down and fiddle with volume+power buttons to start in the right mode. You had to do 7, no choice. Some older phones used "fastboot oem unlock". You'd have to ask google why they changed it.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Good point. I'll add to the OP. You might not remember 6 and 7, but you had to have done them one way or another, whether using a third-party tool to help automate that part or something else.
[Google Pixel 6 Pro] biTToe:
Ahhh...

to be fair, B/L unlock was a long time ago for me.

My P6P arrives tomorrow and I am hoping for root as well.

ƒ
[Google Pixel 6 Pro] biTToe:
Yup!

ƒ
[Google Pixel 6 Pro] dj24:
I'm sorry.. Complete noob here.. Are the steps you mentioned talking about BL unlocking or fully unlocking the phone for any sim/ carrier?
[Google Pixel 6 Pro] roirraW "edor" ehT:
BL = Bootloader. Most likely only your carrier can change whether your phone is carrier locked.
[Google Pixel 6 Pro] dj24:
Thanks. I'm trying to furiously catch up to you guys and furiously googling around looking for definition of some of these terminologies that are being thrown around like 'safety net' etc. As a complete noob what I need is a resource like a 'BL Unlocking and rooting 101' or something like that :)
[Google Pixel 6 Pro] 96carboard:
I don't know much about carrier locks -- I never have and never will buy a carrier locked phone. Best way to not have to worry about it ;)
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! We're all noobs sometimes. I'm aiming for this to be the "BL Unlocking and rooting 101" thread specific to the Pixel 6 Pro. I'll be improving it and supplying more complete information over time.

The general information supplied here will definitely be duplicative of other sources.
[Google Pixel 6 Pro] Highland3r:
Forgive the probably stupid question - never unlocked my Pixel 3 so no doubt things have moved on a lot... Does the bootloader unlock break stuff like mobile banking apps etc - or is it pretty low risk in terms of stuff not working...

Cheers
[Google Pixel 6 Pro] roirraW "edor" ehT:
Hello! No problem. Just five or so minutes ago I added the caveat in red to the OP:

Further note that this doesn't mean you won't be able to get around the issue. I am not going to dive into that because it's complicated and the problem hasn't affected me...yet. If it does affect me, I'll consider detailing how to get around it in this thread later - it would likely be a continuously evolving method. There have been solutions before like Magisk Hide, but from my understanding is it doesn't work anymore but there are other similar solutions.
[Google Pixel 6 Pro] Highland3r:
Nice one thanks - I'll leave things alone for the moment then and see what happens over the next few weeks/months
[Google Pixel 6 Pro] roirraW "edor" ehT:
All posts about Google Pay or banking will be reported to be deleted. Please keep this thread on-topic. If you want to post a new Question thread asking about specifics or people's experiences with banking, please do so.
[Google Pixel 6 Pro] roirraW "edor" ehT:
MOD EDIT: Quote removed since post removed.

Please re-read the title of this thread. This thread is to describe how to unlock the bootloader and root the phone. Please don't add any additional messages about Google Pay or any other banking apps. If you wish to make a central repository thread to report about how banking apps are affected by bootloader unlocking or rooting, then please make your own thread.

If anyone persists on discussing banking apps in this thread, I will have the thread locked and only update the first post as new information comes in. In the past for other devices in threads like these, there has never been any need to discuss banking apps.
[Google Pixel 6 Pro] roirraW "edor" ehT:
You are not helping, but I appreciate the thought. Please, everyone, restrain yourselves from talking about anything that the title of this thread is not about.

Nothing like harsh reminders about why I had become so much less active on XDA in the past several years.

The reason why banking / Google Pay will not be a subject of this thread is because they definitely will be affected without further measures, and those further measures will definitely be affected by further Android updates. It will be a constant struggle back and forth, and that is between those of you who are affected by such things, and the developers of the workarounds.
[Google Pixel 6 Pro] Lughnasadh:
I would agree. The Magisk, MHPC & Universal Safetynet Fix threads are really the place to go to discuss Google Pay and banking apps. That's where most of the information on these subjects are anyway and having Google Pay and banking apps working or not working is not specific to the Pixel 6.

Maybe it would help to put a link to those threads in the OP?
[Google Pixel 6 Pro] roirraW "edor" ehT:
It's not a horrible suggestion, thanks. I already have a link to the Magisk section in general. I'm resistant to putting anything in the OP that's not pertinent to the title. I'd rather someone, such as one of these folks who want to discuss it, make their own thread about the subject, and they can put the links to any other relevant threads in their OP. If someone makes such a thread, I'd be happy to link to their single thread at the top of the OP, and if folks ask in this thread despite the notice, I'll be friendly and point them there.

I try to keep things as simple as possible, and the OP is already going to be busy enough with information. The more information there is in the OP the more likely more people won't read even the important stuff at the top.
[Google Pixel 6 Pro] Ghisy:
So I guess we'll get the factory images from Google tomorrow? So we can finally know if patching the boot.img is the only requirement for rooting,
[Google Pixel 6 Pro] 96carboard:
What's special about tomorrow?
[Google Pixel 6 Pro] foobar66:
I'm rooted and upgraded .36 to .37. However, upon final reboot, Google logo appeared on splash screen with the white progress indicator underneath. After 20 secs or so, phone rebooted ... this bootloop kept repeating.

So I was NOT successful in upgrading and keeing data / installed stuff.

I have to say though that I had been playing around with some dalvik/vm properties and in a Magisk module and that might have caused some sort of incompatibility ... not sure because I don't have any logs.

Anyway ... had to "fastboot -w" to erase userdata and install all from scratch. Root was fine though, just had to click magisk and reboot. Luckily I had a Titanium backup so I was up and running pretty quickly.
[Google Pixel 6 Pro] bouchigo:
I read something on Droid-life, so I went to the Verizon update page, and there's a changelog. Supposedly the only change is finger print reader improvement.... I'm assuming it's the same for the regular .037 update. I attached an image.

No issues with connectivity here.
[Google Pixel 6 Pro] LLStarks:
Verizon says it fixes the fingerprint sensor and that appears to be accurate.

It's not perfect but noticeably better.

Google Pixel 6 Pro Software Update | Verizon Customer Support

Get instructions on downloading the latest software update for performance improvements to your Pixel 6 Pro, including current Android security patches.

www.verizon.com
[Google Pixel 6 Pro] s3axel:
On my Pixel 6 Pro the "fastboot update" method with factory image did not work, it always stated something about "could not find /system partition"....

Went through the adb sideload method instead, which luckily seems to have worked just fine....
[Google Pixel 6 Pro] henihazbay:
Noob question.

I have no issues when the device is on but when it's in recovery mode, adb won't show the list of devices.

I tried pretty much all I could find online:

Updated drivers

Updated adb

Anything I am missing?
[Google Pixel 6 Pro] Homeboy76:
Deleted! :rolleyes: