yashsingh1/xdaforums huggingface dataset:
[Google Pixel 6 Pro] Markelijk:
I tried to update to the .037 update, however, the factory image flashing didn't work. When running the flash-all.bat with the --disable-verity --disable-verification flags, I get the following:

extracting super_empty.img (0 MB to disk... took 0.000s

Rebooting into fastboot

< waiting for any device >

Sending 'super' (4 KB) FAILED (Write to device failed (Unknown error))

fastboot: error: Command failed

Press any key to exit

Does anyone know the solution? I'm currently stuck in fastboot mode. I did try to reflash the .036 factory, but I get the same error unfortunately.
[Google Pixel 6 Pro] s3axel:
Had a similar issue with the system partition.... I finally resolved this by booting into recovery, selecting "adb sideload" and sideloading the OTA update package. Just be very careful to follow the procedure outlined here (OTA sideload section) so your device isn't inadvertedly wiped in the process !
[Google Pixel 6 Pro] Markelijk:
Thanks for your quick answer. How to I use adb sideload? When I go to recovery, there's an Android icon with 'No command' text. cmd on Windows 11 states that adb is unauthorised.
[Google Pixel 6 Pro] s3axel:
Had that as well, when you see the Android icon you are actually not in the recovery - you need to short press the "power" button and the "volume up" button directly one after the other to get into the actual recovery menu where you can select adb sideload (see video here for details) - took me a few approaches to get the timing correct, though ;)
[Google Pixel 6 Pro] Markelijk:
Dude you are my hero. I flashed the OTA via recovery nad the update is done successfully!! I also rerooted and din't even loose any files. Thank you sooo much!
[Google Pixel 6 Pro] henihazbay:
I just updated it. I think i have some good news on the battery.

Bear in mind that the phone is in exactly the same spot, with all the settings unchanged before and after the update.

Look at the flattened battery depletion.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Updated OP with link to Verizon's changelog site for the P6P. Thanks to those who gave a link to it.

Also added a copy of the up-to-date changelog in case it disappears.

List of all Pixel monthly security bulletins

Copy of Verizon changelogs in case they disappear
[Google Pixel 6 Pro] roirraW "edor" ehT:
Wasn't necessarily the wrong place, doesn't hurt having it here too. :)
[Google Pixel 6 Pro] Az Biker:
Device needs to be in bootloader/fastboot mode.

You stated you were in 'recovery'.

And the fastboot command is fastboot devices
[Google Pixel 6 Pro] henihazbay:
Google just posted a blog post saying this mid November update is for US and Japan.

How weird!
[Google Pixel 6 Pro] galaxys:
Think that small update is for the fingerprint fix...
[Google Pixel 6 Pro] Batfink33:
Pushing the fix out quickly in the biggest territory so all the influencers stop making videos about how to FP is bad?
[Google Pixel 6 Pro] roirraW "edor" ehT:
November software update for Pixel 6 and Pixel 6 Pro (US and Japan only, selected carriers)
[Google Pixel 6 Pro] roirraW "edor" ehT:
For the "November 1" update: Google Android Pixel Security Update - Nov 2021
[Google Pixel 6 Pro] DanielF50:
Weird indeed, working perfectly for me in the UK though 😅
[Google Pixel 6 Pro] Burt Squirtz:
Lol this. PR strategy/decision.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I think I have to take a mental health break. Too many folks on here are lashing out at others, and this is one of the reasons why I was hardly active on here for the last five years. I'm turning off all notifications, so I won't see if anyone quotes or mentions me unless I manually look. I'll try to be back, especially if there's something new that needs adjusting in the OP.
[Google Pixel 6 Pro] Morgrain:
This also saddens me quite a bit.

It's a shame that Google didn't push out this essential update (makes the FP actually useful) to the rest of the world. Even though I don't really get the "Japan" decision, since that's not a place where many reviews come from. So why prioritize/enable that country to get the update, but not other nations? (especially since there is only one general firmware for the rest of the world, meaning Google doesn't even have to tinker, they could just release it).

I get that they want to bundle that fix with the december update, but since they already made a mid-cycle hotfix firmware that is compatible with non-US/japan, that's just an odd decision. If not for this Japan availability, I would fully support your PR strategy statement, but since not everything adds up, I'll just go ahead and call it odd.
[Google Pixel 6 Pro] Norma Stitz:
In my upgrade 8 seemed to have lost Google Pay access. It was confirmed working in 0.36.

Can anyone confirm GPay working in 0.37? I figured I'd at least check before starting over.

View attachment 5465505
[Google Pixel 6 Pro] Norma Stitz:
Oh wtf? Gpay appears to be working again. I swear it was giving me the bootloader detection error a few days ago, and I've none nothing since then. Maybe it has a short memory.

I'll have to make a purchase later to confirm, but it appears I no longer have a problem.
[Google Pixel 6 Pro] hanschke:
I got my phone yesterday and have done a full upgrade to latest factory image before I have done anything ;)

I have unlocked the bootloader and maybe I have taken the wrong magisk build but patched the boot.img and stuck on it after flashing it. If I try do disable --disable-verity --disable-verification I stuck on fastboot with I cannot boot into do a wipe. Does I need the wipe?
[Google Pixel 6 Pro] Morgrain:
Which magisk build did you use? There shouldn't be a "maybe" when you tinker with your device - check the guides and then check the version that you downloaded, if you have the incorrect version, that should be obvious rather quickly.

Does the system give you any sort of error message?

Your text is a bit incomprehensible, since there are a couple of information missing (maybe read over it again, add what's missing & iron out the typing errors?)

In case you run into a bootloader message like "failed to load/verify boot images", you forgot to disable verity and verification BEFORE booting (wipe required).

As the OP explains (please always read the guides thoroughly before you attempt to tinker with your phone)

As a general statement: Permanent root currently requires a double wipe!

You should also take a look into the linked guides, like that one

https://xdaforums.com/t/firmware-is-out-get-your-root-on.4353565/
[Google Pixel 6 Pro] Dragon Kumera:
Just thought to add something. It wont ask you for anything google sign in related unless connecting to wifi. So if you skip that and then do it, you can bypass that.
[Google Pixel 6 Pro] 96carboard:
You CANNOT skip connecting wifi because the unlock switch will be disabled.
[Google Pixel 6 Pro] Dragon Kumera:
Wait what?! Is this a recent change?
[Google Pixel 6 Pro] 96carboard:
Not with P6. Maybe with respect to older phones.
[Google Pixel 6 Pro] Dragon Kumera:
Ya pixel 6/6 pro I'm new to so that why I was surprised. (won't be opening mine till Christmas so that why I couldn't check myself.
[Google Pixel 6 Pro] 96carboard:
But in any case, yeah, you don't connect the wifi until you're actually through the initial setup phase, that way you don't have to connect a goober account.
[Google Pixel 6 Pro] Dragon Kumera:
yup
[Google Pixel 6 Pro] roirraW "edor" ehT:
https://source.android.com/security/bulletin/pixel/2021-12-01

@henihazbay posted a better format post about the December update here:

https://support.google.com/pixelphone/thread/139017133/google-pixel-update-december-2021?hl=en:
[Google Pixel 6 Pro] 96carboard:
I was starting to wonder if I was insane, having to reboot my phone every couple of days because of no outgoing audio.
[Google Pixel 6 Pro] roirraW "edor" ehT:
One does not preclude the other 😜 (applies to me too).
[Google Pixel 6 Pro] Morgrain:
Fix for issue causing microphone to cut out during calls in certain conditions *[1].

I've seen that fix with two Pixel phones before. Classic Google. Re-implementing old bugs that are already fixed, just to fix them again.
[Google Pixel 6 Pro] roirraW "edor" ehT:
@magooo said here:
[Google Pixel 6 Pro] Blade22222:
Quick question, the only way to relock the bootloader is with the fastboot command right? I'm on verizon and want to flash that factory image for the modems and dont want to end up with a locked bootloader.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Correct. It doesn't matter what you flash, it can't relock your bootloader.
[Google Pixel 6 Pro] Blade22222:
Thanks. Was a samsung user till they started locking there phones.
[Google Pixel 6 Pro] A.Priori:
MSM tools for oneplus phones would like a word!
[Google Pixel 6 Pro] roirraW "edor" ehT:
You're welcome! After the Pixel 1 got it's last update two years ago, my wife and I briefly re-flirted with Samsung via the Galaxy Note 10+ 512 GB model. Great hardware, couldn't stand the software and unreliable GMail and chat notifications. So glad Google made a 512 GB model P6P.
[Google Pixel 6 Pro] fyoory:
Is there a more comprehensive list of fixes than this "Fixed an issue with non descriptive summary"?
[Google Pixel 6 Pro] roirraW "edor" ehT:
A ton of details at links available in these posts (also linked to in the OP, just search for "update" and you'll find it eventually).

Pixel Update Bulletin—December 2021 - news is December OTA isn't coming until 13th

Latest Pixel Feature drop enables ultra-wideband on P6P, Now Playing enhanc's, Quick Tap to Snap, conversation mode, Pixel Buds A-Series bass boost
[Google Pixel 6 Pro] vibrantliker:
are we all updating keeping root same way as last update:

replace -w with --disable-verity --disable-verification in the flash-all.bat file and run the flash-all command. Then let it reboot, patch the boot image, return to bootloader and flash the patch boot image
[Google Pixel 6 Pro] blackroseMD1:
This was the method I attempted. I've tried flashing the patched boot image twice now, but Magisk says it's not installed.
[Google Pixel 6 Pro] Dataman100:
Same here. Magisk 23015 may not support the new update
[Google Pixel 6 Pro] blackroseMD1:
Yeah, that's what I was thinking. I'll try again once Magisk updates.
[Google Pixel 6 Pro] vibrantliker:
wow, it would be too easy if it worked, right?
[Google Pixel 6 Pro] Dataman100:
It's never "easy'. That's why we do it. Lol!
[Google Pixel 6 Pro] Nergal di Cuthah:
/me impatiently reloading magisk for a new version lol
[Google Pixel 6 Pro] cd993:
Sameee. Kinda wish I noticed root wasn't working before I flashed it but it's 10:45pm here in the UK, who knows, perhaps I'll wake up tomorrow and there'll be a solution lol
[Google Pixel 6 Pro] fil3s:
I used Android flash tool 😦 I only had root for one day on my 6pro. Can't wait for Twrp
[Google Pixel 6 Pro] cubemario:
The Magisk Alpha team is working on it and made a PR to fix it.

Pixel 6 pro, recent android december update breaks root. · Issue #5057 · topjohnwu/Magisk

Device: Google Pixel 6 Pro 512GB Android version: Android 12 (SQ1D.211205.016.A1, Dec 2021) Magisk version name: 5d6d241 Magisk version code: 23015 The recent android december update for google pix...

github.com
[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?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Looks like there is now a fourth December P6P/P6 image (for AU carriers).

View attachment 5483315
[Google Pixel 6 Pro] V0latyle:
In case anyone wasn't aware, Magisk 23016 has been released.

This version incorporates a vbmeta header fix that makes disabling verity/verification unnecessary.

Additionally, there is a fstab fix for the Pixel 6 / Pro.

If you are using the "special" Pixel 6 fixed alpha, make sure you use Complete Uninstall, then install Magisk 23016 and re-patch.

If you're on 23015 or older, simply update Magisk.

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.
[Google Pixel 6 Pro] Utini:
So if I am currently on a system with disabled verity/verification, then I need to flash the system without the disable flags. This will full wipe again?
[Google Pixel 6 Pro] V0latyle:
You don't need to change anything. And no, enabling verity/verification after it was disabled does not require a wipe.

All you have to do is update to 23016, then when the January update comes, update normally without disabling verity/verification. That's it.
[Google Pixel 6 Pro] Utini:
Oh okay, thanks! Thought changing the verity status will always wipe.

Not sure if this fits here but:

I flashed A4 build (I am from Europe) and I have a "Verizon Service App" as system app installed on my phone.

Verizon doesn't even exist in Europe?
[Google Pixel 6 Pro] Ghisy:
Wait. If I just uninstalled the "special" Magisk app and installed the latest Canary (23016) then re-patched (direct install), am I good? I was on the previous Canary before the special build.

I didn't do the whole "Complete Uninstall" thing.
[Google Pixel 6 Pro] V0latyle:
If you have root, yes.

It's generally better to use Complete Uninstall when switching Magisk channels.
[Google Pixel 6 Pro] Nergal di Cuthah:
That's what i did so far so good going on 4 hours heavy use
[Google Pixel 6 Pro] Ghisy:
I do so phew! Thanks.

I've been rooting all my phones since the HTC Desire but this Pixel 6 is making me a noob again at times... 😅
[Google Pixel 6 Pro] V0latyle:
Right there with you, I cut my teeth on the OG Moto Droid...my next phone was a HTC Droid Incredible.
[Google Pixel 6 Pro] blackroseMD1:
Awesome. Thanks for the heads up. All updated and rooted again.

That vbmeta fix sure is handy.
[Google Pixel 6 Pro] rester555:
So if you are coming from stock, never rooted, essentially we are back to downloading magisk 23016 and flashing the magisk patched image to obtain root correct?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Correct.
[Google Pixel 6 Pro] roirraW "edor" ehT:
I finally updated the OP to match our up-to-date December 2021 needs.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Updated post # 4 with the Verizon 12/16/2021 "System Update 2" details.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Updated post #2 with

The usefulness of having Verity and Verification enabled

(now that it's not needed for root).
[Google Pixel 6 Pro] roirraW "edor" ehT:
TL;DR - no major changes. I wouldn't bother upgrading in any hurry.

There are now two new versions of SafetyNet-Fix:

v2.1.3 (Riru)

Direct link: https://github.com/kdrag0n/safetynet-fix/releases/download/v2.1.3/safetynet-fix-v2.1.3.zip

v2.2.1 (Zygisk)

Direct link: https://github.com/kdrag0n/safetynet-fix/releases/download/v2.2.1/safetynet-fix-v2.2.1.zip

Changes for both versions from previous:

Fixed under-display fingerprint sensor on Realme devices (thanks @osm0sis, @byxiaorun, @Jowat97)

Clarified definition of "basic attestation" in readme

Add check to prevent installation on unsupported Android versions (7.x and older)
[Google Pixel 6 Pro] bobby janow:
@roirraW "edor" ehT So this network connectivity disaster is becoming problematic for me. Let's say I wanted to unlock the bootloader simply to flash the November radio. Upon unlocking it's a full wipe and nothing I can do about that one. So then I can flash the radio easily enough and I'm sitting with a wiped device December update / Nov radio. Can I then relock the bootloader without consequences currently and in the future updates? Also, when I relock the bootloader it will boot into whatever I had prior to locking, right? And one more..lol.. can I preemptively wipe with a -w so that when I unlock it won't wipe again. Silly I'm sure but that would be great. I'm not sure though if I can even flash a full image with a locked bootloader.
[Google Pixel 6 Pro] roirraW "edor" ehT:
It has always been my impression (and experience when I've done it on other devices) that every time you toggle the bootloader locked->unlocked OR unlocked->locked, it performs a mandatory factory reset. I always recommend being 100% fully stock before locking the bootloader, but just having the radio be different than stock December *might* be okay.

I'm not responsible...blah...blah...blah.

But yes, when you relock the bootloader, it will factory reset and then boot into what you had prior to relocking - although I have no idea if it switches to the other set of partitions. I don't think so, but I'm definitely not an authority regarding Pixel (and other dual-partition Android phones) partition switching.

No, wiping before you unlock or relock the bootloader won't keep it from factory resetting when you switch from locked to unlocked or from unlocked to locked.

I have no idea about flashing full images with a locked bootloader, as I always go with an unlocked bootloader from the time I get a phone, or very shortly after, and I leave it that way.

If you do flash the November radio.img on top of the December update, whether you relock the bootloader or not, keep in mind that the next OTA (expected next Monday, but who knows) might not work since you won't be running 100% December. And even if it tries to work, it might not successfully finish. I would recommend turning off automatic updates if you run with a Franken-Android.
[Google Pixel 6 Pro] Lughnasadh:
Just to add what @roirraW "edor" ehT said, you need to have an unlocked bootloader to flash factory images. However, you don't need an unlocked bootloader to flash Full OTA images.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Thank you! Maybe one of these days I'll remember. LOL! Does needing an unlocked bootloader also apply to the Android Flash Tool (website)?
[Google Pixel 6 Pro] LLStarks:
I'm surprised how tolerant the phone is of modem downgrades. Mixing low-level, critical partitions is always risky and some phones can brick if you flash something it doesn't like. Modem typically needs to be flashed to both slots unless that's changed recently. As long as the kernel doesn't care, there's typically no harm done.

Unless the system updater can opt for a full flash, I would expect a delta-based OTA to fail. For me, a wipe-less factory flash when coming from a frankenstein partition setup or reverting to a pure December would be best.

I don't particularly like mixing critical partitions unless it's essential to unlocking your bootloader and/or keeping it unlocked. Haven't done it since the Verizon Galaxy S3, which was locked and then increasingly re-asserted that lock with each OTA until Kitkat made it permanent. How to prevent? Leaked ICS engineering bootloader, pre-release ICS recovery, Kitkat modem, Lineage for everything else. For other phones like the OnePlus One, the worst you'll see is Lineage complain about an older trust zone.
[Google Pixel 6 Pro] bobby janow:
@roirraW "edor" ehT Thanks guys. I'm going to wait until the January update but if it's delayed it might be time to go for it. I was pretty sure about the mandatory wipe with no saving anything unless I could magically get Titanium to work. Lol. If I did try to relock the bootloader and it failed the OEM switch should allow me to recover. Thanks again.
[Google Pixel 6 Pro] Lughnasadh:
EDIT: OEM unlocking in Developer Options needs to be toggled on.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Updated post # 4 regarding the December OTA being officially paused, as many had suggested as what happened.

Thanks to @bizdiddy 's post Pixel 6/Pixel 6 Pro December update PAUSED that made me aware.

December 2021 Update Paused
[Google Pixel 6 Pro] Lughnasadh:
Guessing this means no update on Monday 😞
[Google Pixel 6 Pro] Ghisy:
Are you serious Google? Why are they slacking so much with Android 12?

Goodness, does that mean I will have to wait until February to actually use my P6P? I'm disappointed :(
[Google Pixel 6 Pro] Lughnasadh:
I edited my original answer just to clarify. OEM unlocking in developer options needs to be toggled on. I don't "believe" you have to actually do the "fastboot flashing unlock" command.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Ah! Thank you! Makes sense since it can unlock the phone by itself with it toggled.
[Google Pixel 6 Pro] Kris Chen:
Sorry that I need to confirm this statement:

1. If I want to clean flash ROM, I don't need to key-in comment "fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img" before flashing magisk patched boot img file, right ?

2. If I receive ROM OTA, I download OTA file and extracting boot img and then use magisk v236016 to patch boot img

file. Then I also needless to key in comment " "fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img" before flashing magisk patched boot img file, right ?

3. Any magisk new version updated, I just need to update it directly in magisk manager, right ?
[Google Pixel 6 Pro] roirraW "edor" ehT:
Correct, not needed as of Magisk Canary build 23016. (Unless you plan on using a custom kernel that hasn't been updated with the same fixes that Magisk 23016 has. If you're going to use the stock kernel, you're fine.)

If you root, do not attempt to take actual over-the-air updates. You should disable that in Developer Options.

Personally, I use the full factory image zip every time (with "-w " removed so it doesn't wipe). There are other ways to do it as well using Google's OTA zip file, but to some others and myself, it makes more sense to just use the full factory image zip. You need the full boot.img that's inside the second zip that's inside the full firmware zip anyway, to run Magisk on it.

Correct. Always unhide the Magisk app if you've used its option to hide it, update the Magisk app, and then use the new Magisk app to root the new boot.img. I manually flash the new rooted boot.img myself. Your mileage may vary if you attempt Direct Install.
[Google Pixel 6 Pro] roirraW "edor" ehT:
January 2022 update bulletin posted. Note, we're not supposed to receive any further update to the Pixel 6 Pro until late January. Link in post #4.
[Google Pixel 6 Pro] Morgrain:
As far as Google statement went

Google Pixel Update - January 2022 - Google Pixel Community

You are probably right, and we will receive the update in "late" January, even though per Googles statement, chances are we could even get it tomorrow, or in a week already. Meaning the "time frame" is relatively open, Google left the chances between now and the end of january, per statement.
[Google Pixel 6 Pro] roirraW "edor" ehT:
Absolutely, I agree with you. :) For my own expectations, I don't mind just assuming "late/r January" means early February with all the other Pixel updates. LOL!
[Google Pixel 6 Pro] LLStarks:
Might just be a week delay. For all we know, 12L Beta 2 could be tomorrow and include the Pixel 6.

Google is just covering their ass for what they hope to overdeliver and ahead of promised timelines.
[Google Pixel 6 Pro] roirraW "edor" ehT:
XDA article: January 2022 Android security update now rolling out, fixes bug that prevented emergency calls
[Google Pixel 6 Pro] galaxys:
Not rolling out for us:

Pixel 6: N/A

Pixel 6 Pro: N/A
[Google Pixel 6 Pro] roirraW "edor" ehT:
Not yet, no. :)

and...

https://9to5google.com/2022/01/04/pixel-6-january-update/
[Google Pixel 6 Pro] roirraW "edor" ehT:
The December full firmware zips and OTA files have finally been pulled from https://developers.google.com/android/images#raven and https://developers.google.com/android/ota#raven.

See separate thread Alternate links to December full factory image.