yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] simplepinoi177:
So I finally got the chance to update the firmware late last night. After, I saw this post and realized I flashed the non-Verizon-specific version (because I have such an irrational fear like that whitewallman had quoted below and didn't even consider the Verizon-specific version). I didn't realize that although "they're interchangeable", there are those "tweaks/optimizations for [that] carriers", which I am very interested in since I am having intermittent problems with Verizon since upgrading my SIM card...

Now I don't know how to proceed. Should I just dirty flash the Verizon version on top of the non-Verizon-specific November version that's already applied without the "-w" and call it a day? Or is it somehow required/worth it to downgrade first before applying the Verizon version? Or should I abandon it altogether for this time and hope Verizon puts out another carrier specific one and try not to make the mistake again?
[Google Pixel 7 Pro] simplepinoi177:
I am cognizant that there is really no way for Verizon to lock the bootloader once unlocked as how involved it is to unlock the bootloader (oem unlock toggle, load bootloader, special request screen, physical volume button selection and confirmation) makes it highly unlikely it would be as easy as applying their firmware update, but I was just as hesitant irrationally believing that flashing Verizon's image might somehow "screw" or "make-wonky" with a device that was unlocked (when their devices are supposed to be locked) but on their network. I know it makes no sense, but I put it in my mind, however incorrectly, that better to err on the side of caution and not mess with it. 🤷‍♂️
[Google Pixel 7 Pro] roirraW "edor" ehT:
I actually haven't, yet, not because I don't want to, but I've just been crazy busy with work, real-life, and the few moderation duties I've had time for, and I've still got one moderation duty that I haven't been able to attend to yet.

Yes, I posted in this thread yesterday that at least 2-3 users in [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ reported that problem.

Yes, just dirty flash it.

It's okay. As far as human irrational fears go, you are definitely allowed to have that one - not that you need my permission. :)

You are not the only user who has been concerned about this possibility, and it's only because of my six years of Pixel experience that I know there's nothing to be concerned about. I had the Verizon Pixel 1 which had a brief bug in the Verizon firmware on Android 7.10 that was patched on 7.11 which allowed it to be OEM unlocked, and once I toggled that, unlocked the bootloader, and was still able to update every month using Verizon firmware when it was available and there were never any issues.

And then I stopped using Verizon and never bought another Verizon device. :)
[Google Pixel 7 Pro] pp085ster:
I had this issue too. Just have to disable quick PIN for now, everything else works fine.
[Google Pixel 7 Pro] Schroeder09:
So if we have an unlocked P7P that we are rooting but we will be on the Verizon network We should download the Verizon image? Or Do we use the unspecific image?
[Google Pixel 7 Pro] morphius88:
I too am on verizon but just updated with the regular November update. I wasnt sure what would happen just like @simplepinoi177 was saying. I wonder what the verizon specific tweaks are there over the regular unlocked OTA. If anyone knows, PM me or share here (if its allowed to discuss).
[Google Pixel 7 Pro] roirraW "edor" ehT:
Verizon carrier = Verizon image :)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Likely just tweaks to the radio.img to better handle the Verizon network. It would probably be impossible for anyone to specify the exact details of what's different other than Google themselves.
[Google Pixel 7 Pro] whatsisnametake2:
a user on the latest beta reported the scrolling issues being fixed. any feedback on how it is with this main november release?
[Google Pixel 7 Pro] morphius88:
Woops, I enabled the Easy unlock option in AOSP and now I cant get back into the phone, just goes back to lockscreen. Just saw people reported issues with that. I guess I should read before doing anything next time.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

Step # 20 - If the phone won't boot correctly after having enabled Magisk Modules, see either of the two solutions below.

Edit: There are two different options listed there: one is to remove all Magisk Modules, and the second is to disable all Magisk Modules using safe mode. Safe Mode has the unfortunate side-effect, at least on third-party launchers such as Nova Launcher Prime (which I use), you'll have to set your home screen widgets back up. For some apps, it's no big deal, but for the one weather app I use, it's a little bit of a pain, so I opt for the first way, but it's your choice.

I don't know from first-hand experience if there is any other way to get around the issue since I haven't even updated to November yet because I just haven't had time. :)
[Google Pixel 7 Pro] badabing2003:
Can't you dirty flash the October release, disable Easy unlock and then flash back the November release?

This is from a non-AOSP user so take it with a grain of salt.
[Google Pixel 7 Pro] Pritster5:
Could we make a version of this guide on GitHub? That way we can all contribute to the guide and offer suggestions/fix typos etc. And it would be easy to update the guide with new build info, etc.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Just my opinion that's risky itself and a bit like dynamite where a hammer will do the job. 😁 Anytime you downgrade without wiping you risk corrupting app data into something that the later re-upgraded Android won't expect.

It could work, or it might not plus it would be a risk losing everything. 🤷‍♂️
[Google Pixel 7 Pro] badabing2003:
Thanks for warning.

I understand with OS version updates, but even monthly update can cause that?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You can do anything you want with the information you get from my posts here, and I don't want any credit if you make something anywhere else. I'm just attempting to organize the information that mostly comes from others.

If you quote anyone other than me, you should probably ask their permission.

I'll be sticking here. 😁

If you do think I should change or add something here, though, it won't hurt to suggest it to me.

You're welcome! Absolutely.

Sometimes there are major enough non-obvious changes, similar to sometimes the previous month's custom kernel will work on the new month's firmware, sometimes it won't. It's a gamble, but I'm not a betting person.😂
[Google Pixel 7 Pro] morphius88:
I ended up removing all the modules and reinstalling. Yes it cost me 10 extra minutes to set everything back up but I am back to working. I saved a copy of my AOSP Mod settings prior to OTA so I was able to import the settings back and check off the offending option.

Edit: I went with option 1 in step 20 of the OP.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome, glad it worked for you. A slight pain, but worth it.
[Google Pixel 7 Pro] Pritster5:
Makes sense. In that case, I think you should add some info at step 10. On that step you correctly tell people using the FAB script to run certain commands. For people using the Android Flash Tool, this is where they should click "Install Build".
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks for your suggestion.

I've taken a look. My instructions are telling users what steps to skip from my flash-all.bat steps, not aimed at instructing users on how to use the Android Flash Tool.

Google could also change the Android Flash Tool at any time (or all the time) and since I don't normally use it except in emergencies, I wouldn't know unless someone told me. Having the Android Flash Tool-specific steps in there would also mean even more steps I have to micro-manage the instructions for when things inevitably change. If I were going to have Android Flash Tool-specific steps, I would likely have them in their own section separated completely from the flash-all.bat instructions, which adds to my belief this would snowball my efforts even further. :)

I hope you understand where I'm coming from.
[Google Pixel 7 Pro] Pritster5:
That's quite reasonable. I'll work on my own guide for Android Flash Tool users then, as that tool seems more convenient to me with its UI rather than editing batch scripts.
[Google Pixel 7 Pro] simplepinoi177:
I agree. You really are doing so much to list things out step-by-step and clear & simple as possible without getting too complicated for the novice user to understand nor branching out so much to cover numerous other avenues that it would get confusing and hard to keep track (for even the followers of the thread). It seems that it doesn't occur to some people that there are dedicated threads for the Android Flash Tool or PixelFlasher or Magisk or SafetyNetFix or custom kernels that explains things step by step in their own respective methodology and capabilities that they can go to to refer or see what steps are tailored to those...

There's already so much information and steps to consider; you keeping it whittled down as much as you have is great & perfect. Thank you.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Cool. Cheers.

Well, thank you, and you're welcome!
[Google Pixel 7 Pro] grandzu:
After installing the Nov cheetah 13.0.0 (TD1A.221105.001 update, is it normal to still get the notifications to install the security update?
[Google Pixel 7 Pro] JakeDHS07:
Yes because they are separate. Sometimes they even have different dates.
[Google Pixel 7 Pro] J0hnx:
What is that version 13.0.0 (TD1A.221105.001.A1, Nov 2022, Telia)?

Could be flashed to any Pixel 7 PRO device - global? (I just have Telia EE and fighting with VoLTE atm, wonder if this can help)

UPD: flashed this ROM, no changes with IMS registration
[Google Pixel 7 Pro] bhammler:
I'm getting this error while updating:

extracting android-info.txt (0 MB) to RAM...

Checking 'product' OKAY [ 0.000s]

fastboot: error: device requires partition vendor_kernel_boot which is not known to this versio

n of fastboot
[Google Pixel 7 Pro] roirraW "edor" ehT:
Exactly what security update notification is this?

It's for users on the Telia carrier. You can flash any Pixel firmware that's made for the Pixel 7 Pro. Which version would work best for you can be different, but yes, the Telia version is what you should default to, when there is a separate version.

This can vary from month to month. When the Telia isn't available for a new month, you should just use the "Global" one (the one that doesn't indicate a particular carrier).

It looks to me like you are using an old version of Fastboot. It's possible you have an old version in a different location and have that location added to Windows" PATH assignment, which makes it check there for the command before anywhere else.

If you instead use the full path of the newest version of Fastboot that you have extracted in the command line, then it should be explicitly using it, so you could modify your Fastboot command(a) to be, for example:

*C:\Users\my user folder name\Downloads\platform-tools\fastboot.exe"

followed by the usual command line switches. You can modify the flash-all.bat to reflect the necessary changes.

It would be better if you find and get rid of any old versions of ADB and Fastboot, though.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Nestbox makes running Linux virtual machines easy on Google's Pixel 6 or later smartphones - Liliputing

Nestbox makes running Linux virtual machines easy on Google's Pixel 6 or later smartphones

liliputing.com
[Google Pixel 7 Pro] mxalbert1996:
If you restore the original image as described here before the OTA you can install it without any issues.

For Pixel 7 Pro you can flash the patched init_boot.img, boot, install Kernel Flasher, flash original init_boot.img in the app and install Magisk again in Magisk app so that you get a backup of the original init_boot for you to restore before the OTA.

I'm also wondering because I've been using this method for many years and only failed ~2 times on Pixel 6 Pro (probably because I was using stable Magisk which lacked some fixes). Even in those cases I flashed the factory image and it booted without data loss.
[Google Pixel 7 Pro] badabing2003:
I wonder if Magisk uninstall restores the backup to boot or init_boot partition?

Has anyone tested that?

Personally I'd stay away from OTA methods.
[Google Pixel 7 Pro] Lughnasadh:
It appears that it is not restoring the stock init_boot.img, at least from several reports I've seen. A couple of people who used the "Install to Inactive Slot" method in Magisk had it fail, I believe due to the fact that after they "Restored images" they were still rooted because Magisk didn't backup or replace the stock init_boot.img, only the boot.img. However, when they manually flashed the stock init_boot.img they were then able to take the OTA successfully.

I've been suggesting to people that if they want to update their firmware while preserving root, they should use your Pixel Flasher. Either that, or just update another way and re-root.

Magisk won't backup init_boot.img · Issue #6378 · topjohnwu/Magisk

Device: Pixel 7 Android version: 13 Magisk version name: cf9957c Magisk version code: 25205 I'm using the latest version of Magisk on my pixel 7 and everything works fine. However, there is a small...

github.com

Magisk wants to patch boot part instead of init_boot on devices that ship A13 · Issue #6380 · topjohnwu/Magisk

Device: Pixel 7 Global Android version: 13 (comes with A13 and therefore used init_boot) Magisk version name: latest debug Magisk version code: 25205 On devices that ship with A13 (pixel 7 for now)...

github.com
[Google Pixel 7 Pro] mxalbert1996:
It restores init_boot partition. I've successfully upgraded to November firmware using this method.
[Google Pixel 7 Pro] mxalbert1996:
See https://github.com/topjohnwu/Magisk/blob/master/scripts/util_functions.sh#L429

init_boot has higher priority than boot so if init_boot partition exists Magisk will prefer that over boot.
[Google Pixel 7 Pro] Lughnasadh:
Interesting. Then wonder why it isn't working for many.

EDIT: I see it was added back in March.

Add init_boot parition · topjohnwu/Magisk@50b159b

The Magic Mask for Android. Contribute to topjohnwu/Magisk development by creating an account on GitHub.

github.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Regarding the easy unlock problem in AOSP Mods:

Thanks, @swieder711 for reporting!
[Google Pixel 7 Pro] tauio111:
Something new was added to the confseq files of dk_telia (denmark), even when comparing to the 3.1 beta release file. Forcing it from Wildcard to dk_telia, I did not see any differences atleast in the UE caps message from the previous dk_telia confeqs, hence I do not know what it could be. No new carriers were added.

Telia EE whitelists devices for VoLTE, their IMS server will not accept your device and will return an error 403. Unless Telia removes whitelisting, there is nothing else to do. I do not know wether the whitelisting is useragent based or imei range based. You could try and ask Telia to allow the Pixel 7 series but previous sources say they wont do it.
[Google Pixel 7 Pro] Dbj.Dhaval:
I am on Oct month update with verity and verification disabled on slot A. If I use android flash toll and tick disable verity and verification the update will flash in slot A or B? Also while choosing disable verity and verification will the tool disable my current slot A or B
[Google Pixel 7 Pro] badabing2003:
I believe Android flash tool operates on the Current Active Slot, whichever that happens to be. It does not touch the other slot.

If I'm mistaken I appreciate to be told, so that I know.
[Google Pixel 7 Pro] J0hnx:
Hello, saw whitelist statements in web and I have already called them 3x times in last two weeks also directly asking if whitelist exist. Well, the story is the same, they say that every device is welcome(might be a misleading answer actually, I agree). Asked them to switch off and on VoLTE-no positive result of doing that. Wrote an E-mail to them, from where got forwarded for making a call.

Actually I just wonder, what is their IMS server and how you ping that (or send http request)?
[Google Pixel 7 Pro] Ghisy:
Alright, updated to November with the usual method! Rooted again and restored AOSPMods settings.

I'm staying on stock kernel until Kirisakura is updated. Let's see if any random reboot happens.
[Google Pixel 7 Pro] tauio111:
You can see those messages through an app called Network Signal Guru. You should see IMS messaging every 10 seconds under the "Signaling" page if the VoLTE switch has been switched on in the phone settings and the phone has been rebooted after that.
[Google Pixel 7 Pro] roirraW "edor" ehT:
As @badabing2003 said, Android Flash Tool will flash the same slot that you currently have it set to.
[Google Pixel 7 Pro] pndwal:
Can be complex reading issues due to having boot, vendor_boot, init_boot and vendor_kernel_boot...

Earlier the Devs were saying ramdisk didn't exist in /boot as it was moved to/vendor_boot although what's called 'generic ramdisk' did still remain in /boot and worked fine for patching at least with Magisk's manually-add-missing-ramdisk parts (originally for A only legacy SAR) function... I'm not sure if they still view generic ramdisk w/o vendor ramdisks as No ramdisk now but I'd say not, especially as /boot definitely has no ramdisk in P7 w/ generic ramdisk moved to /init_boot which is still missing vendor parts but works fine for magiskinit patching...

I think the new understanding is clearly that generic Ramdisk is what constitutes ramdisk for magiskinit purposes... Other ramdisks must be merged later (after first init ?) as I understand things...

Of course all this GKI complexity is to further address fragmentation and improve Treble / Mainline compatibility for Long-Term Supported updates, uninhabited Android platform release upgrades, ability to contribute kernel changes back to upstream Linux etc. etc. PW
[Google Pixel 7 Pro] mad4some:
I have the "Auto System Updates" toggle off in developer settings but my phone keeps trying and failing to update each morning (approx) anyway. I used to freeze "system update" in titanium backup but I don't see that in this build. Is there a way to kill updates completely? I always select "do not auto update apps" so I can control which ones get updated but this morning apparently this setting got turned back on and apps I do not want updated were all done and I think it is this system update attempt that is responsible.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I have no idea if this will help you, but I made a note of this relatively recent Pixel 6 Pro thread:

https://xdaforums.com/t/how-do-i-bl...ing-up-every-single-day.4489915/post-87427181

That's the link to one of the relevant posts, but you might want to read the whole thread, which is only nine posts long.
[Google Pixel 7 Pro] jdoe6783:
Ok so I can confirm that not enabling OEM unlock before putting your Verizon sim card in isnt required. I didn't put my SIM in and the option isn't greyed out.
[Google Pixel 7 Pro] mad4some:
Lol....I cussed a bunch getting that same exact popup on my OP 8t that made absolutely no sense since I was running a custom rom. I tried everything to kill that popup! Anyway, I'm gonna take the updates once I get some time and plan on using pixel flasher as that sounds easiest. I just can't stand when a setting gets changed by google system in the background.
[Google Pixel 7 Pro] HiM@L:
If I were to flash factory image with verity disabled. what would the command be?

is it flash factory image then reboot to bootloader again and then, extract vbmeta and run fastboot command for disable-verity?
[Google Pixel 7 Pro] badabing2003:
Edit the flash-all script and on every line that you have fastboot, add the following option

--disable-verity

and if you also want to disable verification, add this too

--disable-verification

You need to make sure you add it right after the fastboot word to be certain you don't insert it wrongly
[Google Pixel 7 Pro] Lughnasadh:
The part you would change in the flash-all.bat file is highlighted in yellow, including removing the -w to preserve data during future updates. Then just run flash-all.bat

@Echo off

:: Copyright 2012 The Android Open Source Project

::

:: Licensed under the Apache License, Version 2.0 (the "License");

:: you may not use this file except in compliance with the License.

:: You may obtain a copy of the License at

::

:: http://www.apache.org/licenses/LICENSE-2.0

::

:: Unless required by applicable law or agreed to in writing, software

:: distributed under the License is distributed on an "AS IS" BASIS,

:: WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.

:: See the License for the specific language governing permissions and

:: limitations under the License.

PATH=%PATH%;"%SYSTEMROOT%\System32"

fastboot flash bootloader bootloader-cheetah-cloudripper-1.0-9231809.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot flash radio radio-cheetah-g5300g-220923-221028-b-9229469.img

fastboot reboot-bootloader

ping -n 5 127.0.0.1 >nul

fastboot --disable-verity --disable-verification update image-cheetah-t1b3.221003.008.zip

echo Press any key to exit...

pause >nul

exit
[Google Pixel 7 Pro] Ytujok:
Hello! Pls, help me, I have communication problems on my p7p, I want to try to install the firmware TD1A.221105.001.A1, although I have an excellent operator from Telia, but suddenly it will help. Can you tell me if it can be done and where to download it?
[Google Pixel 7 Pro] Ghisy:
⚠

Hmmm, there's an update on the Play Store for "Google Play Protect Service". I'm avoiding this update thinking it might mess up passing Safetynet with the modded USNF module...
[Google Pixel 7 Pro] nicorvienne:
hi,

i updated and it has no effect passing Saftynet (USNF 2.3.1/kdrag0n-mod Displax) / PlayStore:33.0.16-21[0]
[Google Pixel 7 Pro] roirraW "edor" ehT:
All: I'm a bit overwhelmed right now with real-life work and other responsibilities. I hope you all can continue to help each other in my absence, and that I don't have to stay away too long. Thank you.
[Google Pixel 7 Pro] nicorvienne:
Hi Dude,

first THX for all and take your time!
[Google Pixel 7 Pro] vurtomatic:
Take care, priorities!
[Google Pixel 7 Pro] Schroeder09:
what are the ramifications of disabling verity and verification? does this make the phone less secure? does it trip safety net or something? I only ask because ive read through some of the rooting thread. I understand disabling these wipes the phone.

I received my pixel 7 pro yesterday and plan to root with these steps. I'd really like to start my phone up and root it before moving all my data to it. I'm confused about the kernel portion of instructions. It's listed last, but it really happens first in the process, right? Also, the process to get a custom kernel seems really daunting as compared to how it used to be where you just flashed a .zip file in TWRP or magisk. So, the questions are:

1.) do I disable verity and verification first? does this make the phone less secure? if so and there is a fix later so these don't need turned back on will I be able to flip them back ON without wiping the phone?

2.) does the kernel flashing portion happen right after unlocking the bootloader and disabling verity and verification?

3.) after that then proceed with the root instructions?

4.) then let the "welcome to your pixel" stuff start and run on the phone again?