yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] schmeggy929:
It is definitely not just a Iconify issue with mods theming the Quick settings. I use Themer and updated to Dec Firmware and got the bootloop after flashing. I had to make several attempt to get phone in Safe Mode to remove the Themer Mod and all went ok. Fun setting all the defaults after coming out of Safe mode, lol.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It is indeed a PITA after using Safe Mode. One or two other alternatives for the future from Post #2:

You can also follow @Jon8RFC's advice:

Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does.

(May only be for mis-behaving LSposed modules):
[Google Pixel 7 Pro] siavash79:
What I've experienced is this: previous versions of android would ignore errors in overlay packages and move on, using default values instead of overlay values

Starting 14QPR1, it seems like overlay errors won't get ignored anymore, and instead, package loading falls into FCs. If the package is systemUI for example, that's the formula for a good bootloop

Why overlays have errors in them? Because some android intrrnal resource IDs have changed though updates, and overlays may rely on those IDs and now refer to wrong ones

For this reason, I don't think APK overlays are safe anymore. (Iconify tends to address this issue with building overlay packages on-device, and that can help reducing such errors)

A safer overlay practice is fabricated overlays, which has its own limitations

That's why PixelXpert doesn't use any kind of overlays anymore, to avoid infinite bootloops
[Google Pixel 7 Pro] wangdaning:
Can you not just boot with factory init_boot,img?
[Google Pixel 7 Pro] weriwd:
@roirraW "edor" ehT and @Homeboy76 , thank you for your advises. I managed to update from October to December following the manuall update in post#2 without any problems. My root is working perfectly fine, also passing YASNAC and Basic Integity.
[Google Pixel 7 Pro] I7210I:
Thank you :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks, @siavash79! By the way, when I was caught by surprise after updating PixelXpert to (3.0.0?) that my bottom of the screen space reappeared, I didn't even think to associate that with theming. LOL!

I'm not sure who you were asking, or if there was an issue someone was trying to solve, at this point.

Awesome, glad everything worked well for you.
[Google Pixel 7 Pro] Ghisy:
It turns out there must be a real incompatibility with Better Internet Tiles and the newest December feature drop.

My Wi-Fi tile does work to toggle my Wi-Fi but the SSID of my network doesn't show up anymore. It just says "On" or "Off" whether my Wi-Fi is active or not.

I hope @jorrik98 will be able to look into it at some point.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yet another reason that I might be staying on November for longer.

I think you might've mentioned previously (maybe in @jorrik98's thread), but are you using v3.0.0-beta.2 (from August)? Not that it would likely make any difference, but just thought I'd check.
[Google Pixel 7 Pro] Ghisy:
I do use this latest beta.
[Google Pixel 7 Pro] siavash79:
True. Some of the features were not Xposed. All of them are removed. Mostly theming, but some small stuff here and there too
[Google Pixel 7 Pro] jorrik98:
Starting from version 3.0.0, I switched from using a shell command to read connected WiFi ssid to using the location permission, which works al lot more reliably and shouldn't really break as it uses official android API's...

I'll see if I have any issues myself when I update my device
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you for keeping it in mind when you update (I haven't yet). As my own resources allow, I'm going to try to advocate for some specific developers on XDA to assist you as their own time allows.

I *thought* at least a couple of other users had reported success using Better Internet Tiles with the December firmware, but I don't know which version(s) they were using, and I don't remember which (P6P, P7P, P8P) Pixel model it was reported on, and too lazy to search right now. :D

I also don't know if only specific features were having trouble, so others might not experience any issues.
[Google Pixel 7 Pro] Ghisy:
I appreciate you chiming in!

I can live without a fully functioning version of your app for now but man, Google's implementation of their Internet tile is really dumb. I forgot how unfriendly this idea was. 🤦‍♂️

OT: who has a Pixel Watch here? Did you guys get the December update? I haven't been able to force it as usual, doesn't do anything.
[Google Pixel 7 Pro] avid_droid:
I'm still on Nov.1 I think on my watch. Might be even October (away from my watch). Also haven't received the Dec update for my p7p. Thanks to VZW.
[Google Pixel 7 Pro] roirraW "edor" ehT:
December Verizon-specific firmware (if you use your phone on Verizon or a Verizon MVNO, not if you have a Verizon variant of the phone, unless you're actually using it on Verizon, too):

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

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

developers.google.com
[Google Pixel 7 Pro] slayerdiabolus:
Anyone have a working solution for Google Wallet on 2023.12 update?

It's not working for me using https://github.com/osm0sis/PlayIntegrityFork/
[Google Pixel 7 Pro] synesthete:
Did you find your own custom fingerprint from an old device? That forK requires you to supply a custom fingerprint. If you haven't already done that, you can get more info from the following posts:

🔧 [MODULE] Play Integrity Fix (SafetyNet fix)

PLAY INTEGRITY FIX This module tries to fix Play Integrity and SafetyNet verdicts to get a valid attestation. BEFORE YOU START: - Your ROM must be signed with a private key from maintainer, you can check with this command: unzip -l...

xdaforums.com

and

[TOOLS][ZIPS][SCRIPTS] osm0sis' Odds and Ends [Multiple Devices/Platforms]

osm0sis' Odds and Ends -- Misc./Batch Tools, Flashable Zips, Scripts, etc. General Information In a nutshell, I just wanted a single thread to gather links to some of my other, larger projects, but also serve as a spot I could put some smaller...

xdaforums.com

If you don't want to deal with that right now, you can use the normal Play Integrity Fix module here:

GitHub - chiteroman/PlayIntegrityFix: Fix Play Integrity (and SafetyNet) verdicts.

Fix Play Integrity (and SafetyNet) verdicts. Contribute to chiteroman/PlayIntegrityFix development by creating an account on GitHub.

github.com

This one should work without issue at first, but is supposedly less stable and wallet might fail at some point. So far, I haven't had any issues with it. I just haven't had much time to go mining for old device fingerprints lately.
[Google Pixel 7 Pro] avid_droid:
Oh I miss flashing. I need to theme this boring phone. UI is getting to me at this point.
[Google Pixel 7 Pro] roirraW "edor" ehT:
As has been pointed out to me by @Homeboy76 (thank you!), the new Verizon images are missing now. Here is the proof they were there:

Here's the link, which still works:

14.0.0 (UQ1A.231205.015.A1, Dec 2023, Verizon)	Flash	Link	e4cb8579ea97142791503db1a3d5e2c39e9873d0fb71282ab8e67da7112c5eb2
[Google Pixel 7 Pro] roirraW "edor" ehT:
Verizon images are back with the same hash as before.

@Homeboy76
[Google Pixel 7 Pro] Karlo666:
After December update i got 5G and VoLTE working without any modifications(full stock).

ISP is Croatia A1.
[Google Pixel 7 Pro] Ghisy:
Just FYI, I was able to pull the December update for the OG Pixel Watch. It's currently installing. Finally!
[Google Pixel 7 Pro] ffuser1:
Does anyone have any benefits using Verizon firmware on Verizon's network? I tried it a few months ago and thought my connection was worse with 4g/5g switching issues, so I went back to stock.
[Google Pixel 7 Pro] Boogeyman820:
Got a question is this for just verizon or european pixel 7 pro too?
[Google Pixel 7 Pro] Homeboy76:
Just Verizon. Use the Global for European Pixel 7 Pro.
[Google Pixel 7 Pro] Boogeyman820:
Where do I find the global?
[Google Pixel 7 Pro] Homeboy76:
i

It is the other December 2023 factory/ota image:

https://support.google.com/pixelpho...e-dec-2023?hl=en&sjid=10685064539462631566-NC

- Scroll down to Software Versions
[Google Pixel 7 Pro] Boogeyman820:
The global xda is the one that say [november 6, 2023] right?

[Guide] [January 3, 2024] Root Pixel 7 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More

[Guide] [January 3, 2024] Root Pixel 7 Pro Unlock Bootloader + Pass SafetyNet + Both Slots Bootable + More Android Security Bulletin—January 2024 Pixel Update Bulletin—January 2023 Introduction This Guide is for Pixel 7 Pro owners that want to...

xdaforums.com
[Google Pixel 7 Pro] Homeboy76:
No, It is December 6, 2023.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You can find all Stable firmware on the Pixel 7 Pro sections of these pages (newest versions at the bottom of each devices' section). The links are also in the OP (both first and second post):

Factory Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

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

developers.google.com

The top one in the screenshot below is the "Global" release. The Global one each month is normally the one that doesn't specify what it is. I think that every once in a while there is no Global release, and there are instead several releases to cover all areas of the world, but normally there is a Global release.

Up until two days ago, the Global one was the only December firmware for this device, then they added the Verizon firmware. Note that the Verizon firmware should only be used if you use your device on Verizon or a Verizon MVNO. If you had a Verizon variant of Pixel 7 Pro, but used it with some other carrier, then Global is still what you would want.
[Google Pixel 7 Pro] Homeboy76:
My post #3,439 was misunderstanding, sorry. I sould have pointed him to your OP. :)
[Google Pixel 7 Pro] ystokar:
Note that zygisk currenlty is broken on A14 QPR2 Beta 2. Works with latest magisk canary build​
[Google Pixel 7 Pro] roirraW "edor" ehT:
No problems at all! It's good to have options and multiple ways to direct users in order to help, I just wanted to make sure they know they can always go to the OP to find the necessary links.
[Google Pixel 7 Pro] avid_droid:
Where? Mine is still on October
[Google Pixel 7 Pro] roirraW "edor" ehT:
July 1, 2024 TWD9.240705.001.A1 Pixel Watch 2 Wi-Fi (Aurora) and LTE (Eos) firmware updates / + root directions by LLStarks

Pixel Watch 2 Wi-Fi (Aurora) and LTE (Eos) July 1, 2024: For both LTE and Wi-Fi models: https://developers.google.com/android/images-watch https://developers.google.com/android/ota-watch...

xdaforums.com

Factory Images for Google Pixel Watch Devices | Google Play services | Google for Developers

developers.google.com

Full OTA Images for Google Pixel Watch Devices | Google Play services | Google for Developers

developers.google.com

There's also this:

How to force a System Update

I found video from last year, so I take no credit! As normal, go to Settings, scroll down to System Updates, in there it tells you if there is an update pending.....if you KNOW the update is already out, then tap the little watch icon on the...

xdaforums.com
[Google Pixel 7 Pro] simplepinoi177:
Hehe @roirraW "edor" ehT , this is the Pixel 7 Pro thread.....😏😉

But it's understandable....how many of these threads you maintain...
[Google Pixel 7 Pro] avid_droid:
OK. IM Blown away that this worked. I tapped the heck out of the watch icon and it actually worked. That's crazy. Thank you so much
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's why I was directing them to the PW2 area, lol! But yes, sometimes I have gotten confused about what thread I'm posting in.

Glad you found what you were looking for. :)
[Google Pixel 7 Pro] simplepinoi177:
sorry...i hadn't been following along and didn't realize it changed temporarily to speaking on the Pixel Watch
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's okay, actually they were responding to someone about the OG PW, and I forgot that detail and answered with things about the PW2, although some things (the locations of factory image and OTA, and the hint about how to force the watch to find the update apply to both PW1 and PW2. LOL!

I'll blame @Ghisy! 😉 Just kidding!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Play Store adding support for uninstalling apps from other Android devices

The Google Play Store is adding support for letting you uninstall apps from Android devices remotely from another device.

9to5google.com
[Google Pixel 7 Pro] Lughnasadh:
FYI: "In case you're wondering, there won't be a December 2023 Google Play System Update. The next GPSU version will be January 2024, which will, among other things, hopefully bring an update to the Android Runtime module that fixes a GC-related crash some apps with native code are having."--Mishaal Rahman
[Google Pixel 7 Pro] simplepinoi177:
Finally getting to updating to December and find something fascinating...

I run my P7P on Verizon, so I'm opting to flash the Verizon image, and came across a curious line in the flash-all...

Warning: skip copying radio_a image avb footer (radio_a partition size: 0, radio_a image size: 80076940)
sending 'radio_a' (78200 KB) OKAY [0.567s]
Writing 'radio_a' (bootloader) Flashing pack version g5300q-230927-231106-M-1105
(bootloader) Flashing partition modem_b
OKAY [0.559s]

Now looking at it, it did the same thing for the bootloader image, but still...I found it fascinating...maybe that's how they discern/make-a-difference when it's the Verizon update vs. the global...
[Google Pixel 7 Pro] simplepinoi177:
If i know what module is causing a bootloop (in my case Iconify), is there a way I could do the command adb wait-for-device shell magisk --remove-modules for a specific module and not all modules?
[Google Pixel 7 Pro] Fishawy:
Not sure if there's a command for a specific module, but I would just play it safe and reboot into Safe Mode to disable all.
[Google Pixel 7 Pro] simplepinoi177:
Thanks....I figure...and I was able to look at the adb Magisk options/arguments and it doesn't look like it's possible; only whether to reboot after applying or not...

I really rather not reset all my settings so that's why I'm opting to just use the remove--modules command....
[Google Pixel 7 Pro] Lughnasadh:
Make sure adb has root access and try this:

rm -rf /data/adb/modules/<module folder>
[Google Pixel 7 Pro] simplepinoi177:
lol awww man I should've waited! I would've tried this! grrr......that's my bad....that probably would've worked....although I don't know the folder Iconify would've been named....I was wondering/thinking if there was a way to use an adb command to manually remove the module folder though too! Because I've manually deleted trouble module folders in the past to "manually" delete them too!

UPDATE: for anyone else who might run into this problem....I haven't tried the quoted command, but just FYI, the folder name is, in fact "Iconify" -- so it would be rm -rf /data/adb/modules/Iconify

After some testing (to see what I might be able to do in Iconify), the above did not work when I got stuck in a soft-brick.

The above adb command needs "shell" or superuser permissions, and you can't get that without loading the OS and/or at startup; or in Recovery Mode...
[Google Pixel 7 Pro] simplepinoi177:
@roirraW "edor" ehT

I can confirm that QS Tile mods, even on Iconify, even on stable A14 (non QPR) December update, will, in fact, cause a soft-brick/infinite reboot -- as was discussed from post #3375 and for a couple of posts later. Since I read back and saw the issues before (although I mistakenly wasn't too worried because it seemed to be on mods like Better Internet Tiles, Repainter, or other UI mods; and i thought it might only be on QPR beta builds).

I was actually able to load up Iconify after re-rooting and setting everything back up, but once I imported the config file that loaded up the customizations (including the QS Tile mods I had), forced a "system must restart" and wouldn't get out of constantly rebooting. The only thing that worked for me was the adb shell magisk remove--modules command (although in the posts above, it might've not been necessary as I knew it was Iconify specifically).

Just thought should know....
[Google Pixel 7 Pro] Fishawy:
Thanks for the second confirmation. I also saw PixelXpert dev yesterday warning people about Iconify and Repainter causing serious damage on the latest builds.

I got rid of Repainter since A14 came out (not working), and as for Iconify I only use the fullscreen tweak. Too bad the QS Tile customisations are problematic (for now), I'll have to temporarily settle with their ugly stock shape lol.

To be more specific, you can still use PixelXpert to modify the QS Tiles count (rows and columns), working fine here, but not to modify their shape or dimensions.
[Google Pixel 7 Pro] simplepinoi177:
Yeah...and it's not just localized to QS Tiles shape like I had read in the initial stages, I was just customizing the "2-tone" font (and now that I think about it, the icon sizing), and that was enough to crash it...

confirmed...everything I had on my PixelXpert didn't cause a soft-brick...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for confirmation. I'm still holding off on updating. I would really miss Better Internet Tiles besides some other things.

Also good to have confirmed, thank you.
[Google Pixel 7 Pro] Ghisy:
Yeah, I do miss it now. What was Google thinking with the combined Internet tile? It's so dumb having to click several times to turn on/off Wi-Fi. 🤦‍♂️
[Google Pixel 7 Pro] Fishawy:
Just confirming here, Better Internet Tiles works perfectly fine on the stable December batch.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Also seems like a no brainer that users might want all their radio quick tiles to no not be able to be toggled when the screen is locked.

If I updated, I don't know if there's a chance I could make an Automate script that would work for all those tiles, and require unlocking.

I might have to experiment with that if don't want to wait to update eventually.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Oh! Interesting. The latest beta from GitHub, I assume (from a month or two ago), which I'm already using.
[Google Pixel 7 Pro] Fishawy:
Yep, 3.0.0-beta2 to be specific.
[Google Pixel 7 Pro] Psychlone:
I have the global Pixel 7 Pro and I've been flashing the global ROM to it all this time. My carrier is Verizon and yesterday after rebooting my phone it said there was an update and that my phone would be updated to A14. I've been keeping up with the stock (non QPR) on every release, so this caused some confusion.

So I came here and found this thread where I've been a half dozen times before and find that the Verizon variant ROM has an update. So here's my question... Should I be flashing the Verizon version and what is the difference between the Global that I'm currently on and the Verizon version?
[Google Pixel 7 Pro] Ghisy:
It doesn't work here unfortunately. I mean, it does, kind of: it toggles my Wi-Fi but never shows the SSID on the tile, only on/off.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's completely optional, and there wouldn't necessarily be any advantage, and could even be a disadvantage (at least until / unless you re-flashed the Global if you didn't like the Verizon build).

The Verizon or any other carrier / region-specific builds that ever come out are geared to have radio.img optimizations for that particular carrier or region - however, many users have found either negligible real difference in their carrier signal, or even still had noticeably better signal with the global firmware than the Verizon, so it's completely up to you whether you should try it or not.

I would suggest that if you're happy with your mobile signal, then don't bother. If you aren't, then you could try it. You could always go back to Global afterward if it gives you a worse signal. I would strongly suggest using the OTA file sideloaded, and if you find you're happy with whichever build you flash, encourage you to flash the OTA file sideloaded yet again, to get the same good build on both slots, but the second slot is always optional.
[Google Pixel 7 Pro] Psychlone:
Thanks Rode! Like a pro, always!!
[Google Pixel 7 Pro] Fishawy:
Had that before. Go to About tab, and select Restart app. Also ensure that the Shell method is Root and not Shizuku.

Last resort would be starting fresh with the app, which shouldn't be much of a hassle.

SSID shows correctly here.
[Google Pixel 7 Pro] Psychlone:
Question: Does Full OTA sideloaded wipe data? I definitely don't want to start over for the 3rd time in a week...
[Google Pixel 7 Pro] simplepinoi177:
No. No OTA wipes data. I mean, it kinda makes sense....OTA means Over The Air, and what kind of Over The Air update (from the system settings System Update) requires a factory reset/wipe-data?
[Google Pixel 7 Pro] roirraW "edor" ehT:
And to add to what @simplepinoi177 said, no root or update method I outlined in the OPs will wipe your data unless you ignore the exact steps (although as @simplepinoi177 said, there's no way for OTAs to wipe your phone).

The only things involving wiping on the OPs are unlocking the bootloader, and if you perform the optional step of disabling Verity and Verification (only in order to install custom kernels that require that).
[Google Pixel 7 Pro] Ghisy:
OK, this works but I have to do it every time I boot my P7P. I guess it's better than nothing.

Thanks for the tip!
[Google Pixel 7 Pro] Psychlone:
Thanks guys. I should've known this but for whatever reason I didn't. I use PixelFlasher (since it's easy) and I've always just flashed the Full Factory image and made sure Keep Data is checked.

I suppose from now on I'll just download the OTA and flash that since there's no difference in keeping data vs. wiping data (provided, again, that the Keep Data option is checked when flashing Full)

FWIW, I'm getting lazy in my old age. I am a previous crackflasher and would flash any new ROM to whatever device I had in my hand, going back to the OG D1. Stuff got really complicated for a while on some phones (Samsung, I'm looking at YOU), and then I decided to get this Pixel 7 Pro because it would allow me to flash more often but still be safe enough to not have to be without a phone for a day like was pretty common back in the day. I have left-over anxiety from some of those experiences and still hold my breath sporadically when flashing my P7P.

That laziness is what prompted me to use PixelFlasher. I have nothing against the manual flash, I've used your guide in the OP a couple times and it works great, just more steps for a lazy previous crackflasher like me. :)

On a side-note, I reached out to the Dev of Themer (the entire reason I wiped my phone the other day) and Umut said that chasing changes in Google's code is frustrating but he would be working on a fix as soon as he can get ahold of the source code.

Thanks again for the info, you REIGN!