Pixel 6/Pro December OTA links are live
Happy flashing: https://developers.google.com/android/ota
Posted Dec 13, 2021, 9:16 PM UTC
2131
Which image for US Verizon user? Others have said Verizon. This time it only says US carriers.
4
Fuck here we go again
7
Should just be the regular US version. They don't usually have carrier specific versions.
1
Yea, I hear you, but if you look at the previous images, they say Verizon.
Makes me wonder if I should hold off so I'm not back on the wrong update path like what happened when the phone first came out.
0
Yes there was a Verizon specific image last time, I have a Verizon device and still no OTA update. I'm going to wait until it gets pushed out for now.
2
Looks like they haven't made the OTA live in US yet. Tempted to sideload
4
I just sideloaded. The phones feels more or less the same. Looks like a lot of the bug fixes were general under the hood stuff.
4
Do you know if I can flash the us carrier build over the A1 I have already sideloaded. I have the unlocked 6 pro with verizon Sim
1
Justgot it in Canada.
-6
That's not the US bruh
6
Bit the bullet and sideloaded. The entire process took me like 15 minutes and most of the fixes appear under the hood so there's no real big reason to update if you haven't gotten the update yet.
I personally say just wait for the OTA.
2
What country are you in? I see the update is 2.42gb. I see others from the UK are 215mb. Just ask because others are saying it takes a while for the update to finish when installing.
1
I'm US.
The OTA image files covers the complete operating system so that's why the files are so large. The update through the phone is 215mb.
1
Ok me too, thanks for the clarification.
1
So if I have a french Pixel 6 pro in Denmark and sideloaded the mid November update, which OTA should I install?
I've been trying through settings with no luck.
2
Would aideloading wipedata ? It shouldn't right ?
1
No, it won't wipe data.
2
It shouldn't unless you intentionally wipe but it's still good practice to always back up your shiz anyways
1
[deleted]
1
So with a P6P from the Google Store in Ireland, should I flash the "EMEA carriers" image, or the "regular" Dec 2021 one?
1
You should have it ready to update at the software update section, by now. No need to sideload anything.
1
That's what I hoped, but it's not showing for me... even after several reboots.
Starting to worry it may be because I flashed the mid-month fingerprint-OTA a few weeks ago. Now neither of the OTA images will flash; I get an Error 21 "Footer is wrong" when I try either one, despite the checksums being correct.
Whelp.
Scratch that, I was being dumb (opened the Factory Images page on my laptop rather than the OTA Images page). Was able to flash after all, but still no idea if the A1 or the A4 is the right one.
2
That was not meant for EMEA users, only US and JP I think. Maybe you'll have to factory reset...
1
Google page shows the 016.A4 build ("EMEA Carriers") for Ireland.
1
Anyone else looking to keep root only to see that there is not a "boot.img" file in the updated OTA image for "US Carriers"? I guess I will have to wait until there is a boot image available...
1
Well I guess they are suggesting that rooted Pixels not run the December update yet.
https://forum.xda-developers.com/t/root-users-read-this-before-updating.4356231/page-8
1
comments
Do you know if I can sideload the us carrier OTA over the already sideloaded A1 OTA? Will that brick my 6 pro? I' not rooted.
1
How annoying is the animation for the fingerprint sensor now... Oof. Hopefully that's just a new bug or something 🥲
1
Looks exactly the same for me, what is yours doing?
1
It's like it tries to do the animation twice or something. I feel like before from the AOD it had a fluid circle wave type thing that expanded out for the fingerprint icon. It slows down the unlocking process. Or maybe I've lost it
Edit: seems to have resolved after 24 app updates, finishing update bar cleared, and a reboot
1
Does anyone know which file I should flash on my unlocked 6 Pro? I'm not sure if the one ending in A1 is the correct file.
1
My device wasn't buggy, and yet I'm still super excited for this update! So many fixes to the notoriously half-baked Android 12 release. *giddy*