yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Loustsoul:
If it's one less step, then it's one less thing to screw up and brick my phone! 🤣🤣
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - December 2022 - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

13.0.0 (TQ1A.221205.011, Dec 2022)	Flash	Link	b144b4262b6a349efe756a9446c9e9ce9123d839280f5e5b06ebbc661c577b68
13.0.0 (TQ1A.221205.012, Dec 2022, O2 UK)	Flash	Link	4406695deca324c94ef49b9be594362e350d45bdf2e7fad40cf147cdcfe5dc89
[Google Pixel 7 Pro] Nekromantik:
touch screen updates. lets see if it improves the occasional issues
[Google Pixel 7 Pro] Tracker31:
where to get changelog?
[Google Pixel 7 Pro] roirraW "edor" ehT:
New software features have arrived to the Pixel family - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
Pixel Update Bulletin—December2022 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] Morgrain:
Wat o.o

Finally it's back.

It still boggles the mind that Google thought it was a good idea to give us battery usage info of "last 24 hours".

Whoever came up with that idea deserves to get fired and thrown out of the tech industry, indefinitely.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Note, I had the Panther links in my post. Now Cheetah links. Please don't flash the Panther images or you'll brick.
[Google Pixel 7 Pro] Ghisy:
Fyi, the platform tools haven't been updated: latest is still 33.0.3.
[Google Pixel 7 Pro] LLStarks:
Looking forward to QPR2 tomorrow or Wednesday. Rolling release Android never stops.
[Google Pixel 7 Pro] pogo-airsupport:
I believe QPR2 starts in January no?
[Google Pixel 7 Pro] LLStarks:
Depends on how many betas they want for a March feature update. It's a 3-4 month cycle.

Next month could be Android 14 DP1.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I could be misremembering, but I thought Google decided to not again have two separate Android Betas going on at the same time (a QPR Beta and a new full Android version Beta/Developer Preview). But I don't know when the next version of Android DP1 will come out.
[Google Pixel 7 Pro] Lughnasadh:
The QPR betas for A13 will end in March. So basically the QPR2 betas will be the last ones. No QPR3 betas for A13 it seems.

I believe the first A13 Developer Preview build was released in February, so I would expect a similar timeframe for A14. Google has stated the A14 Betas will start in April (or after the A13 QPR2 betas are finished in March). So it's the A13 QPR betas and the A14 betas they are trying to avoid overlapping, it seems.
[Google Pixel 7 Pro] LLStarks:
I don't know how Google threads that needle.
[Google Pixel 7 Pro] Gordietm:
Is anyone's security and privacy settings unified now? Mine isn't.
[Google Pixel 7 Pro] Lughnasadh:
Mine isn't either.
[Google Pixel 7 Pro] Gordietm:
According to the pixel drop features, it's supposed to be, so maybe next month.
[Google Pixel 7 Pro] r3sp:
So does we beta users get an December update? Or should we flash back to stable :/
[Google Pixel 7 Pro] dimm0k:
root still works in Dec update I take it?
[Google Pixel 7 Pro] Lughnasadh:
You should get the stable QPR1 (December update) build.

EDIT: That is, assuming you are enrolled in the beta program. If you flashed the beta without enrolling then I don't think you will get the OTA update and will have to flash it manually.
[Google Pixel 7 Pro] BIGWORM:
This is my first time looking to update km the P7P. Currently running the November stable. Any chance I can update to QPR1 without wiping?
[Google Pixel 7 Pro] Lughnasadh:
Yes. The build released today is the December/QPR1 stable release, so for those on the stable builds is just a normal monthly security update, albeit a big one because it includes the QPR1 stable stuff. No wipe is needed.
[Google Pixel 7 Pro] LeshaRB:
Hi can you help me?

Why I have such error

Bootloader is open, and I have root
[Google Pixel 7 Pro] swieder711:
Quick process from Nov to Dec update.

Unhide magisk

Patch init_boot

Edit flash_nowipe with "fastboot --disable-verity --disable-verification update image-cheetah-tq1a.221205.011.zip"

Flash no_wipe

fastboot flash init_boot m_init_boot.img
[Google Pixel 7 Pro] Lughnasadh:
It's because you are rooted. Flash the stock init_boot.img to unroot and try again.

Or flash the factory image, use Android Flash Tool or Pixel Flasher. You can even sideload the full OTA image.
[Google Pixel 7 Pro] LeshaRB:
I would like to update without data loss ... is it possible?
[Google Pixel 7 Pro] BIGWORM:
This was literally just answered.
[Google Pixel 7 Pro] sensation4gking:
If I am hoping for a miracle that Verizon gets bootloader unlocked. Is it ok if I take ota updates right now or no?
[Google Pixel 7 Pro] EtherealRemnant:
It's not worth holding back your device in hopes a bootloader exploit will be found. It is extremely unlikely to happen.
[Google Pixel 7 Pro] whatsisnametake2:
I see in the release notes it mentions fixes that could pertain to the scrolling issues. anyone got any feedback on that yet?
[Google Pixel 7 Pro] taysandman:
Learning about Pixel OTAs + retain root.

* Unhide Magisk + disable modules

* Flash stock init_boot.img

* OTA or OTA side load

* Re-patch / flash init_boot.img

Question on side load. Google says to check System update before side loading?

I'm still on Oct - Pixel took it upon itself to start downloaded and I paused it.

Upon reviewing it shows resume...without any build info which I find annoying - pretty sure wants to update to Nov. It OK to sideload OTA in this paused state?

Which leads my 2nd question - is it that OTA via phone always incremental / delta. IE I need Nov OTA before Dec. 2 separate updates in this case?

But side load OTAs are full so one can jump to latest release via single ota side load?

I'm kinda leaning toward only dealing update / re-root quarterly so prefer the single update. Would also like to know how to block OTA check / auto download. Anything native or can I block with afwall+? (Auto updates was disabled in dev options but it still began downloading anyway)

Lastly will safeynet fixes periodically get broken with OTAs?

Thanks
[Google Pixel 7 Pro] kornball:
Sure hope the December 2022 update and rollout are smoother than last year's!
[Google Pixel 7 Pro] vurtomatic:
Hello everyone. I'm attempting an update for the first time after using PixelFlasher previously.

I'm trying to run flash-all.sh but receiving this error on the Mac:

-bash: flash-all: command not found

I have everything in the platform-tools folder. init_boot.img is patched and ready to go.

I just need to run flash-all.sh.

One outstanding question from the instructions: What does

Apply Magisk Stable to it.

mean? I already have Magisk on the phone from previously rooting it. Do I need to reinstall it?

Or do I simply flash init_boot after flash-all.sh is done?

UPDATE:

Used the Android Flash Tool to flash the update and then fastboot flash for init_boot. Booted, re-enabled Magisk, and everything's back to normal. Didn't have to reinstall Magisk.

I also learned I can't use "fastboot", needed to use "./fastboot", even thought I already have "platform-tools" in my PATH and I was already in the same directory.
[Google Pixel 7 Pro] Dark_Eyes_:
Is it just me or I can't seem to find the new Security& Privacy hub, and the Google One VPN is still not activated after the December update? Maybe it has to do with the safetynet module in magisk?
[Google Pixel 7 Pro] Lughnasadh:
It's not just you. Could be we need a server side update, a Google Play System update or the like. Doesn't have anything to do with the safetynet mod b/c I'm not using that.
[Google Pixel 7 Pro] EtherealRemnant:
It sure feels like this update is much smoother and I had no complaints about the smoothness of the last one really. Just seems even more responsive. I wonder if they're boosting the CPU cores sooner? I'll have to watch the battery for the next week or so.

I turned on the AOD to see and it seems to get stuck on a higher brightness after getting a notification so I turned it back off. It's still not working the way it used to here where you could have always on turned off but pick up your phone and it would go to the AOD interface, it's still only sporadically showing the AOD when gently moving the phone around, still goes to the lock screen if you pick it up or tap it. This is one of the only things I miss from my OnePlus is how nice their AOD was. Incoming text messages would show up a full preview of only the text on an otherwise turned off screen. The Pixel adds a notification to the AOD but it doesn't expand it, so you have to interact with the screen anyway which kicks it to the lock screen before you can even expand the incoming message...
[Google Pixel 7 Pro] Cj719:
If I haven't previously disable verity, will this trigger a wipe?
[Google Pixel 7 Pro] EtherealRemnant:
Yes because it will reboot to recovery and tell you that you have to wipe.
[Google Pixel 7 Pro] K1nsey6:
Im surprised its a 64bit app, being so old
[Google Pixel 7 Pro] sharksfan7:
My Pixel 7 is the first phone I've run rooted since my OnePlus 6T on Android 9. It appears the process to OTA update has changed since the last time I did it a few years ago. If I follow the steps in post #2 of this thread to update (running modified flash-all.bat w/ full factory image, patching the init_boot.img in Magisk, flashing patched .img), will this automatically put the new images on the inactive slot then switch it to active? Or do I need to manually switch slots first then run flash-all.bat?
[Google Pixel 7 Pro] i5lee8bit:
You don't need to switch slots manually, generally ever, when updating your phone. If you flash full factory image, it'll just install over your current active slot and done. If you sideload OTA zip, it'll flash to the other slot and change slots for you and boot (you won't even notice it happening tbh).

One question though: are you currently running with verity/verification disabled? If you don't know what I'm talking about, it's probably a "no", but keep in mind if you want to flash a custom kernel for this device you'll need to disable them. And unfortunately that will require a data wipe the first time you do it, and then you need to remember to disable again each time you update on future updates. There's a very slim chance they'll find a workaround to needing them disabled eventually but I wouldn't count on it. More info on this can be found in the OP's and kernel development threads (e.g. Kirisakura). If you don't care about flashing custom kernels, simply disregard this last point and the next.

But my major reason for that last point is that if you are running verity and verification disabled, in that case you may want to manually switch slots and flash full factory image with v/v disabled as a means of being overcautious. My reasoning for this is that you never know when you may run into a bootloop from a bad flash, which will automatically trigger an active slot switch, and once it attempts to boot without those flags disabled, you're beat and have to wipe. So out of an abundance of caution, I flashed both slots last month with the flags disabled.
[Google Pixel 7 Pro] sharksfan7:
Thanks, @i5lee8bit. When I rooted my P7, I don't think I did anything to disable verity/verification. I just patched/flashed the init_boot.img then configured some stuff in Magisk. I don't plan on running a custom kernel.

I didn't think I could sideload just the OTA being rooted. Thought I needed to flash the full factory image and re-root. It's been a while since I've done this. Looks like I need to do a bit more research before I do this update.
[Google Pixel 7 Pro] otonieru:
For me who is on Singapore unit,

i will never get those One VPN, sad story.
[Google Pixel 7 Pro] kornball:
With the update to battery usage in Settings, is the graph gone for anyone else? Everything is properly listed in usage since last full charge, but there is no longer any sort of graph.
[Google Pixel 7 Pro] vlubosh:
wait few hours, it will be there, the same was with latest BETA
[Google Pixel 7 Pro] Techboyz97:
I was on T1B3.221003.008. I received an update yesterday night. Now I'm on TQ1A.221205.011 but I don't see the changes. Exemple : the battery usage graph shows the full charge on a day and not up to 7 days. The Security and Privacy are separated and not merged.
[Google Pixel 7 Pro] vurtomatic:
I thought I used to be able to tap the battery icon in the status bar to open battery settings. That seems to be gone after the Dec update?
[Google Pixel 7 Pro] Lughnasadh:
Some of the changes likely require a server side update, Google Play System update, Google Play Services update or the like.
[Google Pixel 7 Pro] taysandman:
Thanks.

I believe your correct it was just downloading OTA which was paused and shouldn't impact OTA side load. Just Google pointing it out made me wonder...

You're right my terminology was wrong. Retain data and re-root.

My only thought on full factory images vs OTAs via phone is that the Nov update showed ~30MB download. Yet looking at factory images over ~2.5GB. That's a big difference to write to nand storage to gain 30MB worth of security updates. So been curious about OTAs to help extend Pixels life. (Haven't actually looked if Google gives any write endurance specs on Pixel.)

However I did end up using Google's chrome flash tool to update to Dec last night. (Factory image) Didn't unroot. Just disable modules and unhide magisk and flash. Upon boot magisk was uninstalled. Re-install Magisk and re-patch init_boot. Re-enable modules. All went well including safetynet. I really do hope the guru devs over at TWRP will grace us with Pixel 7 / 6 support. Image backups help calm the nerves when doing system updates. :)

Regarding root after update I briefly read a few guides I believe mentioning "keeping root" with update. Pre-downloading the factory image + init_boot patch. Then re-packing factory image's zip to include patched init_boot. Allegedly flashing all in single update.

Thanks for suggestions. I'll explore roirraW "edor" #1318 to completely disable auto OTAs.

Coming from VZW note 8 which had to stay on Android 7 for last 5+ yrs to keep root. So quite rusty on these OTA things. :)
[Google Pixel 7 Pro] waldoud:
Hello everyone, I have a question, what difference would there be between the uk and the global, can this version change be done?
[Google Pixel 7 Pro] simplepinoi177:
As I understood the twitter post roirraW "edor" ehT posted about in post #1438, OTA's can be more than the simple size (~30MB in this instance) it posts in the System Update page in the OS. Updating through OTA can take painstakingly long; it felt like 30 minutes when I did it once on my wife's unrooted phone. Also, (according to the twitter post) it seems to depend a lot on its compression when it comes to processing. Depending on your internet speed, if you can download the 2.5GB relatively quickly (Google's servers have always been lightening in my experience), flashing the full factory is faster than the device slowly downloading the 30MB (I don't know why it took so long to download the 30MB) and then uncompressing and then installing/processing the OTA update. Running the flash-all on the Full Factory Image is usually finished in under 2 minutes (in my experience, YMMV). Also, it's not like you have to load the 2.5GB on the phone, just on your computer. Also, again, @roirraW "edor" ehT explains it best on how flashing and laying down the whole system image as an update is better than incrementally applying little patches over time. In one update it might just be 30MB worth of updates/changes, but after (let's say 4) months of around 30MB here and there, it adds up to 120MB months of incremental and intermittent data being patched here and there in variable places. Sorry I'm not explaining it well, i'm hoping the rode warrior can...

I think I've seen something like that; but from what I can recall on the instance I saw it, it was for a specific circumstance of attempting to repair a messed up partition and/or it was just put up in theory as a thought experiment. Now, I could be completely wrong so I hope some expert would come and correct me if I am, but I recall momentarily seeing that when running the flash-all command process, it checks and "validates" the partitions on the device and it may check it against the image files in the Factory Image zip. If I'm correct and that's true (again, I am completely guessing and could be completely wrong and hope an expert would correct if I am), then messing with the init_boot image file and changing it from what is stock may incur some bad juju; in my head I imagine it akin to checksums not matching. I dunno, just a thought/guess/concern 🤷‍♂️

In any case, I'm happy it all worked out for you and I'm glad I could help some...

If you had already flashed the global and wished to flash the UK one (or vice-versa), as I understand it, you can simply dirty-flash it over whatever is already installed/flashed. For November, I flashed/installed the Global, but wanted to install the Verizon one, and was told & able to just flash the Verizon one over the Global one with no issues.

If you are asking for a complete explanation on the difference between the two, that's a different question I am willing to let someone else answer ;)
[Google Pixel 7 Pro] linuxares:
Hi!

Anyone know why with the OTAs my phone won't even start installing/downloading them? It like instantly "nopes" when I try to download.

I have no clue why since it doesn't give me any information what have gone wrong.

EDIT: I run the Telia version for November so might be why?

EDIT2: Found the issue. Magisk init_boot wasn't loved by the OTA updater. Restored the image file now it OTA updates.
[Google Pixel 7 Pro] madmuthertrucker:
I was wondering if I could switch slots before flashing each new update? kind of like what the phone does when it gets the OTAs.
[Google Pixel 7 Pro] proxyx:
After flashing Q1A.221205.011 to slot A on my P7P, I attempted to flash the same to slot B. However, when I attempt to do so and issue the "fastboot reboot bootloader "command, the P7P hangs at a black screen and eventually reboots to slot A. Im never able to flash-all on slot B because I can't get to it. Is this recoverable? Seems like without slot B i run the risk of a bricked device if something were to happen to slot A.
[Google Pixel 7 Pro] Lughnasadh:
What commands and in what order are you giving?

This should work:

adb reboot bootloader
fastboot --set-active=b (Since you are currently on slot a)
fastboot getvar current-slot (To confirm you are now on slot b)
flash-all.bat
[Google Pixel 7 Pro] proxyx:
Yes that's the order of operations that I performed. I just tried the following:

adb reboot bootloader
fastboot --set-active=b
fastboot continue

and that gave a black screen and I noticed a couple of times a line flashed at the bottom of the screen then it eventually rebooted to slot A. Is slot B corrupted? If so, any way to recover?
[Google Pixel 7 Pro] proxyx:
Got it to flash. Thank you very much for your input!
[Google Pixel 7 Pro] Lughnasadh:
So you did exactly the commands I gave you?
[Google Pixel 7 Pro] Lughnasadh:
Glad you got it to flash! Just to be clear, did you get it to flash by issuing the exact commands I gave you or did you do something else?
[Google Pixel 7 Pro] proxyx:
I followed the procedure you recommended. Thanks again!
[Google Pixel 7 Pro] Lughnasadh:
@roirraW "edor" ehT Regarding Posts #1535-41...

I believe these problems occurred because this person had never flashed the firmware to slot b (e.g. in cases where it's a new phone), thus when they set their active slot to b and issued the fastboot reboot bootloader command, there was nothing to boot into so it bootlooped back to slot a.

I would like to suggest that in the OP, Post #2, Section 11,

OPTIONAL: If you want to flash both slots, after this first time, then after do the following

:, that it be noted that if the user has never flashed the firmware to their inactive slot (via OTA, flashing factory image, etc.) that they skip the fastboot reboot bootloader command, thus preventing what happened above from occurring.

EDIT: Apparently that person thinks they did successfully flash the firmware to both slots beforehand, so maybe this wasn't the case in this instance.
[Google Pixel 7 Pro] proxyx:
I had flashed the previous firmware to both slots successully. Or at least I thought I did. Why this latest firmware misbehaved I'm not certain, but I think your advice to the OP holds merit since it has proven to resolve my issue. Appreciate everyone's help.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you, I'll take a look just as soon as I can.
[Google Pixel 7 Pro] Tasneem khan:
Hi everyone i have P7P UK Global version i just want to know which Factory Image I should download i know i should download the UK one but what if i download the other one what's the difference between those...? And what will happen...
[Google Pixel 7 Pro] xdrc45:
You could use either one. The main difference would be that the UK version would be optimized for your regions network/basebands. If you did flash the global version it would boot and work fine but you might sacrifice your network connectivity
[Google Pixel 7 Pro] Tasneem khan:
Thank you 🙏
[Google Pixel 7 Pro] simplepinoi177:
Thank you for this clarification! I was going to follow the instructions from badabing2003 on post #1341 because I haven't installed an OTA nor flashed to both slots before, but didn't understand the reason why I was to skip rebooting to bootloader and was going to omit that, so I am very grateful you clarified this for me and saved me a whole lot of headache!
[Google Pixel 7 Pro] tauio111:
Diff - d0cad09ea568776f62e1ac270056907a0f0d2637^! - platform/packages/apps/CarrierConfig - Git at Google

This is the only difference I think. The modem and confseq files are indentical on the o2 and the main firmware versions. Use the o2 one if you're their client.
[Google Pixel 7 Pro] Tasneem khan:
Thank you
[Google Pixel 7 Pro] State.of.mind:
I updated my phone from Nov to Dec. However, when I try to root the Dec update i get the error below. Any ideas on how to fix this?

"FAILED (remote: partition (init_boot) not found)"
[Google Pixel 7 Pro] xdrc45:
Have you tried "fastboot flash init_boot" and then click on the patched image and drag and drop it in to cmd?

You could try flashing the slots directly.

"fastboot flash init_boot_a magisk_patched_boot.img"

"fastboot flash init_boot_b magisk_patched_boot.img"
[Google Pixel 7 Pro] binoysankar:
I am on Dec pixel feature drop and still having 2 seperate Security and Privacy menu in settings. I have heard that this menu is now combined? Any idea why its different for me?
[Google Pixel 7 Pro] JakeDHS07:
It's a server side rollout not in the actual update itself. Not sure if it's attached to the play system update or play services but it will eventually change. Idk anyone who has it yet.
[Google Pixel 7 Pro] binoysankar:
I did the play system update few minutes back which does not include this.
[Google Pixel 7 Pro] JakeDHS07:
Yeah I don't have it yet either. Guess we'll have to wait and see
[Google Pixel 7 Pro] Gordietm:
Yesterday the Security and Privacy settings were combined on my phone. I rebooted during the day and it showed up.
[Google Pixel 7 Pro] State.of.mind:
What version of magisk is everyone using? Stable or Canary?
[Google Pixel 7 Pro] Lughnasadh:
Stable 25.2. Canary 25205 works as well.
[Google Pixel 7 Pro] madmuthertrucker:
I'm using stable.
[Google Pixel 7 Pro] madmuthertrucker:
I noticed that right after the update that Hold for Me and Direct My Call had disappeared. Then they were back later and trying to download en-US for awhile. Now everything is fine. It was odd.
[Google Pixel 7 Pro] State.of.mind:
This method worked. I'm still not sure why the other method wouldn't work.