yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
For quite a long time, I've had an issue with Better Internet Tiles where I would have to launch the app once in order to get those Quick Tiles to work. For almost as long, I made an Automate script to (among other things), after the second time I unlock the phone (because when I unlock the phone the first time, Automate isn't running yet), it quickly launches the Better Internet Tiles app, and then swipes "Back".

I actually also have it bring up the power menu, because I seemed to notice that Classic Power Menu wouldn't always come up the very first time I brought up the power options, but it would every time after that.

I don't know for certain if this would fix the issue you experienced, @Ghisy, but maybe. My Automate script actually isn't perfect on my P8P - it leaves the power menu up at the end, but I just swipe back myself. I haven't taken the time to try to tweak it more on my P8P. On my P7P, it works perfectly as is.

Here's a screenshot, and I've attached the Automate Flow (zipped), if anyone wants to use it. You have to change Automate's default setting, so that it runs all Automate Flows which were running previously after a reboot.

Spoiler content hidden.
[Google Pixel 7 Pro] bird333:
Hello, I'm concerned about this too. Does Iconify save a config file somewhere that I can restore? If so, where? My plan was to just 'disable everything' in Iconify before I updated. Is there a better way to go about it?
[Google Pixel 7 Pro] simplepinoi177:
yes...i found that Iconify can save 2 config files, but it still retains the problem...

it can save it ALL -- if you go to Settings, 3 dots at the top right, Import/Export -- or just the custom monet set up -- in Monet Engine, 3 dots at the top right, Import or Export.

Problem with the non-Monet config file is that it will still retain and apply any QS customization when you import it! there is a setting somewhere buried that i believe doesn't restart the SystemUI on apply or right away, but i wouldn't risk it (because it depends too much on the app's behavior on how it chooses to apply and might inadvertently restart the SystemUI anyways); and, for me, that's what did it -- simply importing forced a soft brick.

Other than my painstaking custom Monet (i configured all 65 boxes), the rest of the settings isn't too hard to re-set up without touching the QS customizations. If anything, just write down the numerical values on certain settings (positions, color, size, etc.), as the rest I'm sure memory will serve...
[Google Pixel 7 Pro] mochamoo:
I have the same situation. My concern has always been that Verizon might "do" something to break features that it doesn't like. It used to be that it blocked use of esim by non-Verizon sims for example. Not good for travellers or having 2nd non VZW lines. I am current with the non VZW build for December. So am not sure if it's trying to force the VZW build or not. Don't see a way to disable auto updates.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@bird333 and @simplepinoi177, I *thought* there was a place to export the Iconify configuration, and I had definitely done it sometime in the last couple of months, but I couldn't re-find the option yesterday when I finally updated to December.

I just added Iconify to my "Favorites" in Swift Backup. I have a nightly scheduled cloud backup for all apps and their data but only if the app version has upgraded, plus have it set to keep the old version of each app and data, but I have another nightly scheduled cloud backup for all my Favorites which backs those apps and their data up every night, plus I just manually ran a cloud backup on just that app and data.

I also noticed Iconify has an option to (I think from memory?) reset all settings back to their defaults.

The only option to disable auto updates is in Developer Options, although we know for a fact that Google has the capability to get past even that, as they did so on the Pixel 6 line when there was a security vulnerability in the bootloader they considered severe enough, plus the update would prevent downgrading the bootloader once it was upgraded, with the not really helpful exception for gimped "Developer Support images" of Android 12 for the Pixel 6/Pro/a.
[Google Pixel 7 Pro] mochamoo:
I would prefer to flash the update manually to avoid issues with root etc. For those who have taken this update is this the version that you end up with? It's all I see on the factory image page.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@mochamoo,

There are two December images. The one you posted a screenshot of is a Verizon-image. If you're using your phone on Verizon or a Verizon MVNO, then you can try that one. Otherwise, you most definitely want the Global image (the one at the top of this screenshot):
[Google Pixel 7 Pro] Psychlone:
FWIW, I've found the difference between Global and Verizon updates negligible.

I can't remember what db I was getting with either right off the top of my head, but they were definitely only a couple points apart and I definitely did not see anything that Verizon had removed. Currently running the Verizon update for now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Good to know, thank you!
[Google Pixel 7 Pro] bird333:
So you're saying you can't even modify the tiles after you have done the update?
[Google Pixel 7 Pro] mochamoo:
Was just concerned because phone is wanting to do an update when I already have the dec global version installed so don't know what it is wanting to send me. Someone mentioned the same thing happening to them so wondering what they ended up with.
[Google Pixel 7 Pro] simplepinoi177:
Yes...there wasn't an issue when I was on the November android 14 version. It was only after updating to December and importing the config file that it had issue and soft-bricked. I read it in the Pixel 8 Pro guide thread having issues, but I thought that it was limited to Better Internet Tiles or Themer or other, and that it had something to do with the custom shaping of it. I was wrong on both accounts. After getting everything back up and running, I went and only modified the text color and the text size, still caused a soft-brick. So I just stayed away from any customization of the QS completely.

I think I read somewhere that, even though they didn't have a Verizon device, they still flashed that and it stopped -- seems to have something to do with Google mistakenly thinking there's a new update; probably because Verizon's version of the update came after the global....
[Google Pixel 7 Pro] Psychlone:
This is exactly what happened to me, and being an old crackflasher from the olden days, I decided I'd rather flash the VZ update than to look at it. What it came down to for me is that I really didn't want to see that update nag every couple hours and I didn't want to just turn it off.

That's the beauty of owning a Pixel - if you decide you don't like whatever, it's easy to flash back and reroot if necessary.
[Google Pixel 7 Pro] EastonCo:
I am not sure if this has been an issue, I have been unable to find anything on it.

My Pixel 7 Pro, after this latest update, no longer runs Zygist. Magisk installs and runs, but after enabling Zygist and rebooting, it does not start and still says 'will enable after reboot'.

Anyone have any suggestions?
[Google Pixel 7 Pro] UberNorse:
Are you on stable or beta?
[Google Pixel 7 Pro] Ghisy:
Weird. I have no problem on Magisk stable and the latest feature drop (December). Unless you're using Magisk beta?
[Google Pixel 7 Pro] synesthete:
I haven't had that problem. Zygisk is working for me. I am using the latest Magisk Canary build and Android 14. Maybe try disabling any third party magisk/lsposed modules and rebooting.
[Google Pixel 7 Pro] pndwal:
Yeah, a fix for Android 14 QPR2 B2 changes was merged in Magisk 26403...

@EastonCo, can you confirm if fix in Magisk 26403+ for regression (apparently began sometime after 26001 since reverting to 26.0 fixed similar issues on other devices) affecting Android 14 solves issues for you?... I mentioned details here:

Seems this should fix issues in with late beta A14 firmware, but fix for "new method signatures and arguments" may help/be needed for other (stable etc) A14 builds by now also... 👍 PW
[Google Pixel 7 Pro] EastonCo:
Got ya, thank you. This is on Magisk 26400 so that explains it. Been a long end of the year!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android Security Bulletin—January 2024 | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - Jan 2024 - Google Pixel Community
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hot off the press!

Both Global and for those on Verizon or Verizon MVNO carrier firmwares released:

https://developers.google.com/android/images#cheetah

https://developers.google.com/android/ota#cheetah

https://support.google.com/pixelphone/community?hl=en

https://source.android.com/docs/security/bulletin/asb-overview
[Google Pixel 7 Pro] caitsith810:
I've always updated through PixelFlasher, but this time, it seems like the January update is giving me issues. Has something changed with the January update package causing this?
[Google Pixel 7 Pro] badabing2003:
Nope, nothing has changed.

Submit a support file in pixelflasher thread and I'll see what the issue.
[Google Pixel 7 Pro] dcarvil:
I have a Pixel 7 Pro purchased from woot.com for a very good price (48% off the google price). It was advertised as carrier unlocked. However, it appears to be a Verizon phone that has been reflashed with an carrier unlocked ROM. The IMEI begins with 35, which usually indicates Verizon. The SKU is GA03419-US. I have not been able to find what P7P model number that is.

I haven't opened the box, but if it cannot be bootloader unlocked I will return the phone. Does anyone know if a Verizon phone that has been reflashed can be unlocked? Any idea what P7P model SKU GA03419-US corresponds to?
[Google Pixel 7 Pro] Lughnasadh:
Your SKU doesn't match any of the numbers here, but does seem to fall in line with the other Verizon numbers listed there (Best Buy #s). For what it's worth, I believe my Pixel 6 Pro, 7 Pro and 8 Pro all have/had IMEIs that began with 35 and they were all unlocked versions directly from the Google Store, so I don't believe "35" is an indication of a Verizon model.

If your phone is a Verizon model I don't know how it could have been "reflashed with an carrier unlocked ROM" since the bootloader can't be unlocked on the Verizon models, therefore you can't flash anything on it.
[Google Pixel 7 Pro] dcarvil:
The reason I thought it had been reflashed is the "Software Version" on the box has been overlayed with a sticker stating "TQ2A.230505.002". That version is not specific to any vendor, though. The box is not shrink wrapped, but is sealed with security stickers.

The built-in SIM begins with 89148, which again indicates a Verizon phone.

The ultimate test is to open the box and see if the bootloader can be unlocked. I have not yet done that, in case it would impact my ability to return the phone. I was hoping someone on this thread could provide some insight without my opening the box.

Thanks for your input.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'd video the opening of the box, including first capturing the seals and all sides of the box and close-ups of the labels, and never taking first the box and then the phone out of camera-shot while powering it up and attempting to enable bootloader unlocking. If you can get that far (enabling bootloader unlocking), then you should be golden and that it's definitely not a Verizon phone, and as @Lughnasadh said, I don't know how it could be a Verizon phone reflashed to anything else since by a Verizon phone's very nature - the only things that can be flashed to it are official OTAs, and the firmware isn't what causes the device to be considered carrier unlocked (or bootloader unlockable).

If you really need to later, you can always blur out things in the video that you absolutely have to (if you end up connecting to your home Wi-Fi), although I'm not sure if you can do that on the phone directly unless you use third-party, probably paid software to do so.

If you have the option from an existing device, you could always create an insecure Wi-Fi hotspot and connect the new device to it, or just one with an easy password so that you're not giving anything away on the video.

It's possible that you might have to connect the device to some kind of internet before it will allow you to unlock the bootloader. I honestly don't remember for sure, but I know users have mentioned that from time to time over the years - I just don't specifically recall for myself, or if I even tried without connecting to the internet first.
[Google Pixel 7 Pro] Lughnasadh:
I wish I had some further insight without opening the box, but unfortunately I don't.
[Google Pixel 7 Pro] wangdaning:
https://store.google.com/us/repair?hl=en-US

Will tell you.
[Google Pixel 7 Pro] caitsith810:
Fixed the issue. It was a USB port issue on my end.

Thanks for your help though.
[Google Pixel 7 Pro] Anaëlle:
I updated to January patch with PixelFlasher without any problem, but when I flash the patches init_boot.img, the system bootloops regularly after a few seconds, I tried with Magisk and Kitsune Mask, I have the same problem with both, and rebooting into safe mode doesn't solve the problem either :/
[Google Pixel 7 Pro] badabing2003:
If you flash stock init_boot.img file and don't bootloop, then your issue is Magisk modules.

You need to boot to safe mode using the rooted init_boot, booting to safe mode with stock cannot disable Magisk modules.
[Google Pixel 7 Pro] dcarvil:
That was the first thing I tried. It just tells me warranty status cannot be determined, without giving any device information.

Thanks for the reply, though.
[Google Pixel 7 Pro] Anaëlle:
Yes, that's what I said, I rebooted into safe mode with parched init_boot, not stock
[Google Pixel 7 Pro] badabing2003:
Check this please.

GitHub - badabing2005/Magisk: Special Magisk with modules loading disabled.

Special Magisk with modules loading disabled. Contribute to badabing2005/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] Anaëlle:
It seems to have worked. The system stayed on long enough without rebooting for me to open Kitsune Mask and realize that the only module left activated was HuskyDG's Magisk Bootloop Protector (pretty ironic). Once the module has been removed and the system rebooted, no more bootloop. I'll have to find another bootloop protector though lol. Thanks a lot for your help!
[Google Pixel 7 Pro] Fishawy:
It bootlooped for me several times because there's an option inside to patch init_boot, which can be confusing. Selecting "no" also bootlooped still.

I have since shifted to Simple Bootloop Saver v2 by ez-me (can be found on the repos), and all is well (saved me a couple of times so it proved its worth). I've also seen a stripped down version of Magisk Bootloop Protector around (without patching anything), but Simple Bootloop Saver is good enough for me.
[Google Pixel 7 Pro] badabing2003:
I don't feel comfortable with this script either.

For starters, I don't see the need of using -r flag when removing the disable flag which is just a file, at best it is risky coding.

Furthermore it suffers from the same issue that @Anaëlle had, it does not disable itself which means if things change or there is anything wrong with the module, it would stay enabled and hence the ironic bootloop.

There is no need to keep it enabled after disabling all the other modules.

Lastly with no updateURL, if things change and cause bootloop, even if the author releases a new update, users won't be notified or get updated.

I personally prefer least modules approach, and if I bootloop due to a module, I know how to get out of it.

But that's just me.
[Google Pixel 7 Pro] Fishawy:
Thanks for the details, and agree on the point of not disabling itself.

Just wondering if you came across a module that happens to avoid those concerns. There's always the manual Safe Mode approach, but the paranoid me would feel a bit safer with a module in place lol.
[Google Pixel 7 Pro] badabing2003:
Honestly I never looked, so I'm not the best person to ask.

The script looks simple, you should be able to comment line 28 that deletes the disable file from the module just to be safer, and get rid of that dreaded rm -rf

I don't know enough to understand line 30, why it is needed and if .system_booting is a file or a directory, or even at that point any of those are ro or rw.
[Google Pixel 7 Pro] skyrood2:
hey all

does anybody know why A1 firmware versions were marked as "japanese carriers" before, but last two releases are marked as Verizon? I have a rooted japanese p7p and wondering if I can install this last Verizon ota?
[Google Pixel 7 Pro] refedit:
Hey guys

trying to flash latest factory via website android flash tool. But get stuck on PREPARING TO UPDATE. It reboots to fastboot mode but nothing happens..

I'm still on Android 13.

EDIT: Managed to flash latest upadate using Pixel Flasher. Life saver
[Google Pixel 7 Pro] roirraW "edor" ehT:
The A1 (or any other A2, etc) only means a further revision (from one without an A1 designation) - it doesn't mean a device that once got an A1 firmware will always get the A1 firmware. It's relatively arbitrary to us users.

If there isn't firmware specific to your carrier or region in a particular monthly update, then you want the "Global" firmware (the one that doesn't specify a particular carrier or region).

You can also see Post #4 - Build ID definitions. Thanks to @Namelesswonder for the information and resources they shared.

Sounds like a potential USB port or cable issue. If changing one or both of those doesn't help, I'd try rebooting the computer.

Also, while it's in Fastboot mode, check Windows' (assuming you're using) Device Manager entry for the phone and see if you need to install the driver again. The Driver needs to be installed twice, as Post #2 describes - once while the phone is fully running Android, then again when the phone reaches Fastboot/Bootloader mode. ...if you hadn't already done so, but still worth checking anyway.
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1744762602990043389
[Google Pixel 7 Pro] Lughnasadh:
https://twitter.com/i/web/status/1744766601814212747
[Google Pixel 7 Pro] refedit:
Used Pixel Flasher and managed to solve it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks to @Lughnasadh, I've corrected the following section of Post #3:

Find problem apps, Magisk, and LSposed Modules by (three different methods)

:

Magisk Safe Mode.

This can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can re-enable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.

It has been pointed out to me (thank you, @Lughnasadh!) that Google's Help Page for Find problem apps by rebooting to safe mode only gets you into System Safe Mode, not Magisk Safe Mode.

One of the Alpha developers (I don't know which one): "Many people wait for the animation to appear before pressing keys. They are misled by the documentation into thinking that system safe mode will trigger magisk safe mode. This is wrong, the time is wrong.

For safe mode to be recognized before the module is loaded, magisk must detect keystrokes earlier than the system. If you press the key after the animation appears, you will have missed the detection of magisk and will only trigger the system safe mode. You should press and hold volume down immediately after the bootloader unlock warning, and release it after the animation appears - if you do not want to trigger the system safe mode at the same time.

Safe mode can also be triggered through prop. When the computer is powered on, long press the restart button in the power menu and click OK on the "Reboot to Safe Mode" pop-up window, and the prop will be set. If magisk and the system read this prop the next time they are powered on, they will enter safe mode. Only in this way can we guarantee that everything will be triggered. But it is not practical, or in other words, it is meaningless to save bricks."
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Maps for Android now supports Bluetooth beacons for tunnel navigation

Google Maps now supports Bluetooth beacons in tunnels to improve navigation when GPS is not available, but it needs to be turned on.

9to5google.com
[Google Pixel 7 Pro] Fishawy:
I didn't even know that there's two of them! I'm only familiar with Magisk safe mode which disables all modules.

What's the difference between both? And how can one visually tell when booted?
[Google Pixel 7 Pro] roirraW "edor" ehT:
With Google's own System Safe Mode, your Magisk Modules wouldn't be disabled, assuming you have some, but almost anyone who is rooted would at minimum have the Systemless Hosts one enabled that comes with Magisk, I think. :)

With Magisk's Safe Mode, they'd be disabled.

I'm the opposite; I didn't know there was a Magisk Safe Mode. I thought it was just referred to me as "Safe Mode", and I found Google's instructions and thought that's all it was.

I will still avoid either Safe Mode as much as I can, since from what I understand, Magisk's Safe Mode will also disable your Widgets, like the System Safe Mode does, and I have one app that I use multiple widgets for - it's just a slight pain to set them back up.
[Google Pixel 7 Pro] simplepinoi177:
I avoid it because I've heard that it also resets all your system settings as well...! But apparently it conflicting reports because many say that it doesn't....I don't want to go through the headache and rather just use the adb remove-modules command....
[Google Pixel 7 Pro] Lughnasadh:
For what it's worth, the only thing safe mode has altered for me is removing widgets, as the Google documentation warns. But I've never had any system settings altered that I'm aware of.
[Google Pixel 7 Pro] Fishawy:
Magisk safe mode doesn't tamper with widgets, I confirm that from dozens of tests.

What is does is a) disables all modules including Systemless Hosts, and b) disable whatever customisations you have from said modules (for example, Iconify configuration "you should have a backup config", substratum lite config, PixelXpert customisations "you need your config export backed up").
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! Interesting.

Like @Lughnasadh, I don't recall it ever resetting my system settings, either, but I still want to avoid it. :)
[Google Pixel 7 Pro] simplepinoi177:
Thanks for the confirmation...I think I'll move forward with it when necessary then....maybe Google had changed it at some point for all i know/can-guess...
[Google Pixel 7 Pro] phoinix_gr:
Completely failing to pass SafetyNet, with PlayIntegrityFix_v15.2 Anyone facing the same issue? Any workarounds?
[Google Pixel 7 Pro] simplepinoi177:
anyone not implementing their own custom fingerprint will be "facing the same issue"....

implement a custom fingerprint / custom pif.json
[Google Pixel 7 Pro] phoinix_gr:
Thanks. That helped. Now passing using custom fingerprint
[Google Pixel 7 Pro] JoshuaUB78:
What fingerprint did you use?
[Google Pixel 7 Pro] phoinix_gr:
There are some scripts around , google it !