yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Ghisy:
This is my update path every month: I disable verity and verification and also uses a custom kernel so YMMV. I'm also rooted.

MAKE A BACK-UP of anything important

** Check if platform tools are up to date!! **

** Disable Magisk Hide!! **

** Disable Magisk modules!! **

** Disable Substratum overlays!! **

1- Within the Platform Tools folder, find the FLASH-ALL (.bat) file

2- Open it with text editor and replace -w with --disable-verity --disable-verification in file (keep ONE space between commands)

3- Verify FASTBOOT DEVICES by typing CMD in the address bar of the same platform tools folder

4- adb reboot bootloader

5- Type FLASH-ALL

6- Let it boot into system and settle for a minute

7- Patch the boot image:

Connect your device and PC and put the extracted init_BOOT.img file (from the CURRENT factory image you are flashing) on your device where you can easily find it

Open Magisk and choose SELECT AND PATCH FILE (select the init_BOOT.img you just put on your device)

Copy the new PATCHED init_BOOT.img from your download folder back into your PLATFORM TOOLS folder where the fastboot application is located on your PC

8- Boot device into fastboot/bootloader, connect device and PC

9- Type fastboot flash init_boot --slot=all (drag and drop patched init_boot.img here OR type in the file name magisk_patched-xxxxxxxxxx.img)

10- Reboot into System

** Flash custom kernel **
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's in my instructions. If you want to flash custom kernels, you have to disable Verity and Verification. If you never disabled them before, you'll have to completely wipe after you do. You don't have to disable them if you're not going to flash a custom kernel.

You don't ever want to let it re-lock your bootloader unless you're selling/trading in the phone.

You're welcome!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Google Pixel Update - November 2022 - Google Pixel Community
[Google Pixel 7 Pro] dr.wtf:
So, according to the guide, I have to flash the rom, patch the init_boot and then flash the init_boot.

Can I patch the init_boot on the old rom and then just flash the rom and afterwards directly flash init_boot and skip a reboot?
[Google Pixel 7 Pro] EtherealRemnant:
Flashed to both slots with PixelFlasher but accidentally skipped the patching of the boot image so I did that manually and flashed it manually myself. Everything seems to be great.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Usually, yes, you can. I just prefer to do it after booting completely stock unrooted successfully on the new firmware to confirm nothing weird is amiss. :)

Whoops! :)
[Google Pixel 7 Pro] whitewallman:
Hello and thank you,

Question: I have an unlocked Pixel 7 Pro that I use on Verizon network. Should I flash the November update or the November Verizon MVNO update (.003)?

I have unlocked bootloader and rooted with magisk.
[Google Pixel 7 Pro] swieder711:
Worked perfectly.

I edited the flash-all file.

I unhid Magisk, but left everything running. Root restored.

Just waiting for Freak to update his kernel.

Used the Verizon version on my Google P7P
[Google Pixel 7 Pro] EtherealRemnant:
Yeah it's my first time using PixelFlasher since my 3 XL like a year or so ago and I hadn't granted root permissions to shell. Problem has been rectified going forward but honestly it wasn't that big of a deal.

It sure is nice having access to full images again though. OnePlus stopped releasing anything but incremental for the US OnePlus 9 and it made for a real headache when trying to update while rooted, sometimes still refusing to flash after restoring images with Magisk. This was cake by comparison.
[Google Pixel 7 Pro] vurtomatic:
Oh, so disabling Magisk Hide won't affect the banking apps that it's meant to be "hiding" from?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Normally you want to use the firmware that's made for the carrier you're on, so yes, the Verizon version of the firmware. They're interchangeable, just usually some tweaks/optimizations for particular carriers that they weren't able to integrate into a single global image this month.

It will affect it while it's unhidden. Always re-hide it when done. Of course, I don't unhide mine the way I update.
[Google Pixel 7 Pro] Ghisy:
It will but you can re-hide it right after you've updated and rooted again. Not sure disabling Magisk Hide is necessary but I always do it just in case!
[Google Pixel 7 Pro] whitewallman:
Thank you. I was apprehensive flashing the Verizon MVNO image since Verizon P7pro has locked bootloader and I'm unlocked.
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome! Pixel firmware will never affect whether your bootloader is unlocked. It will always stay unlocked until you lock it.
[Google Pixel 7 Pro] Tracker31:
if you use msm tool for unbrick your phone your bootloader would be locked, is it?
[Google Pixel 7 Pro] Minux31:
Trying to flash-all.sh to update, and I got this :

Sending 'bootloader_a' (12260 KB) OKAY [ 0.054s]
Writing 'bootloader_a' (bootloader) Flashing pack version cloudripper-1.0-9074510
(bootloader) flashing platform gs201
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition ufs
(bootloader) Validating partition partition:0
(bootloader) Validating partition partition:1
(bootloader) Validating partition partition:2
(bootloader) Validating partition partition:3
(bootloader) Validating partition bl1_a
(bootloader) Validating partition pbl_a
(bootloader) Validating partition bl2_a
(bootloader) Validating partition abl_a
(bootloader) Validating partition bl31_a
(bootloader) Validating partition tzsw_a
(bootloader) Validating partition gsa_a
(bootloader) Validating partition ldfw_a
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition ufs
(bootloader) Flashing partition partition:0
(bootloader) Flashing partition partition:1
(bootloader) Flashing partition partition:2
(bootloader) Flashing partition partition:3
(bootloader) Flashing partition bl1_a
(bootloader) Flashing partition pbl_a
(bootloader) Flashing partition bl2_a
(bootloader) Flashing partition abl_a
(bootloader) Flashing partition bl31_a
(bootloader) Flashing partition tzsw_a
(bootloader) Flashing partition gsa_a
(bootloader) Flashing partition ldfw_a
(bootloader) Loading sideload ufsfwupdate
OKAY [ 0.860s]
Finished. Total time: 0.914s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.050s
< waiting for any device >
Sending 'radio_a' (111152 KB) OKAY [ 0.484s]
Writing 'radio_a' (bootloader) Flashing pack version g5300g-220908-220908-M-9040061
(bootloader) Flashing partition modem_a
OKAY [ 0.462s]
Finished. Total time: 0.947s
Rebooting into bootloader OKAY [ 0.000s]
Finished. Total time: 0.050s
< waiting for any device >
--------------------------------------------
Bootloader Version...: cloudripper-1.0-9074510
Baseband Version.....: g5300g-220908-220908-B-9040061
Serial Number........: xxxxxxxxxxxxxxx
--------------------------------------------
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 version of fastboot

Latest platform tools, and I disabled all Magisk modules, Zygisk too ...

Any idea ?
[Google Pixel 7 Pro] swieder711:
Is it possible that you mixed up the Cheetah and Panther update files?
[Google Pixel 7 Pro] Minux31:
No, I just dowloaded cheetah file, unziped in my plateform-tools directory :
[Google Pixel 7 Pro] swieder711:
(deleted, I am on VZ so my files were different)

Did you check the SHA-256 Checksum?
[Google Pixel 7 Pro] Minux31:
I just dowloaded this one : cheetah-td1a.221105.001-factory-f2793a62.zip (my P7P is a global version)
[Google Pixel 7 Pro] Minux31:
Yes, it's good
[Google Pixel 7 Pro] swieder711:
Do you want to try the Google Flash tool instead of the flash-all.bat?
[Google Pixel 7 Pro] Minux31:
Yes, why not, I'll try
[Google Pixel 7 Pro] roirraW "edor" ehT:
There is no working unbrick method for the Pixel 6/Pro/6a and Pixel 7/Pro. MSM tool isn't for these CPUs.

FYI, I'm not ignoring you, just multitasking like crazy, busy with work. :) I'll try to take a closer look in a bit, even if you solved it by then.
[Google Pixel 7 Pro] tauio111:
edit flash-all.sh and replace "fastboot" with "./fastboot" so it will use the new fastboot in the directory.

For some reason the fastboot binary version in for example the Archlinux repo is not correct, even if the package version indicates it is.

from Google:

./fastboot --version

fastboot version 33.0.3-8952118

from Archlinux repo:

fastboot --version

fastboot version 33.0.3p1-android-tools

33.0.3p1 doesnt seem to like the new pixels
[Google Pixel 7 Pro] Minux31:
Thank you, I understand :)

btw flashing with Google Flash tool worked, but I will also try to find out why command line didin't
[Google Pixel 7 Pro] roirraW "edor" ehT:
Glad the Flash Tool worked for you!
[Google Pixel 7 Pro] dr.wtf:
For me, adding the folder to PATH helped...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Warning, multiple users in @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+ have reported that using AOSP Mods option to enable quick-pin login (automatically unlocks after you enter the fourth digit) is broken on the November update on both Pixel 6 and 7 / Pro.

Just turn off quick unlock. Most or all other options are working in the mod.
[Google Pixel 7 Pro] badabing2003:
Adding `./` to fastboot is the better approach for @Minux31, because it looks like he has another version of platform tools in another path that gets loaded.

I think the best way is to make sure you only have one and only one version of platform tools (the latest) downloaded from Google and not the repository packages, and add that to your path, and always update that folder with the latest.

This way you don't even have to extract the monthly images into the same folder as platform tools (maintaining separation of concerns and keep that folder free of other files), and still be able to run flash-all from anywhere (ie wherever you chose to unpack it).
[Google Pixel 7 Pro] synesthete:
@roirraW "edor" ehT I noticed that in your guide there is a note about people on macOS having problems. Depending on how they have their terminal set up they might be getting an error like: "zsh: command not found: flash-all.sh" when executing the "flashall.sh" command. I'm on macOS and use the following command instead:

sh flash-all.sh

I used this when I rooted the phone in October and just updated to the November firmware using this command.
[Google Pixel 7 Pro] bradhoschar:
So, just be 100% clear. If we're not going to flash custom kernel, we don't need to worry about init_boot.img to update to Nov patch?

Also, we can just uninstall magisk, update with the Android Flash Tool, install, then install Magisk to root again, right? Sorry, Post #2 is kinda confusing.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thank you! I'll re-research some users in this thread who had the trouble and point them to your post when I can take the time.
[Google Pixel 7 Pro] roirraW "edor" ehT:
The only thing you don't have to worry about if you're not going to flash a custom kernel it's disabling Verity and Verification (and wiping after).

init_boot.img is the file you root with Magisk and then flash too the init_boot partition.

Whether using the Android Flash Tool or the firmware image zip method, there's no need to uninstall Magisk, and doing so would just lead to more steps to re-root. Whichever of those two methods you use, you'll still need the firmware image zip because you need the init_boot.img file from the inner zip to re-root that file with Magisk.

I'd be happy to modify the steps if you can help me figure where exactly needs adjustment. I'm constantly in search of ways to make things clearer.

Thanks.
[Google Pixel 7 Pro] bradhoschar:
I think someone posted the modified init_boot.img last month, so I didn't have to do any of the legwork to modify it, that's where I was getting stuck.

So, just disable all magisk mods> Flash Tool> extract init_boot from factory image, flash in bootloader> regain root?

It's not that it's *unclear*, but I might seperate root, unroot, for custom kernels, for stock kernel, but that's just my OCD! You do WAY more than enough in this thread!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I see.

Correct.

Well, thank you!

I've thought about a slight re-arrangement related to those things, although possibly not quite the way you describe, but I'm still just thinking about it. 😁
[Google Pixel 7 Pro] Lughnasadh:
For some reason the Jeopardy music just started playing in my head. I have no idea why 😂

Sorry, back to your regularly scheduled non-off topic programming...
[Google Pixel 7 Pro] bradhoschar:
That worked perfectly! I'd give ya a raise if I could! Thanks again!
[Google Pixel 7 Pro] roirraW "edor" ehT:
LOL you both!
[Google Pixel 7 Pro] WorldOfJohnboy:
Just a FYI, I used the Props editor to revert the fingerprint back to Pixel 7 Pro, installed November update and the new Safetynet Module and everything works perfectly! (CTS passed without Issue)

I also was finally able to update Google Camera without force closing, so it was my Pixel 6 Pro "spoofed" fingerprint that was causing that issue!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome, good to hear on both!
[Google Pixel 7 Pro] Minux31:
Thank you for your answers, I think you point out the problem : I have plateform-tools from Arch, and from Google at the same time, so modify fastboot to ./fastboot in the script should do the work :)
[Google Pixel 7 Pro] krkhaha:
A lot of mixed information. Really long time ago was much easier to understand any tutorial. I looking for information how to update stock and don't lost root and don't turn on Verity or something like that.
[Google Pixel 7 Pro] goRt:
Post #2 in this thread
[Google Pixel 7 Pro] krkhaha:
There is nothing about updating without lost root.
[Google Pixel 7 Pro] PurppleMonkey:
Tadaaaa my new pixel 7 is on November Update thanks to @roirraW "edor" ehT !

(By the way, my first phone sent to google was deemed "irreparable"....)
[Google Pixel 7 Pro] PurppleMonkey:
'cause you have to re-root everytime you update even if you keep your data (-w removing step)

You can keep magisk app (and desable magisk module), but you have to patch init_boot again after updating.
[Google Pixel 7 Pro] krkhaha:
I think with Pixel flasher is possible 🤔
[Google Pixel 7 Pro] goRt:
Yes, pixel flasher automates it for you
[Google Pixel 7 Pro] Ghisy:
Hmmm, I just had a random reboot on my P7P, what the heck?! (October firmware, rooted, Kirisakura kernel and AOSPMods)

Once the new Kirisakura drops, I'll update to November and hopefully no more reboot.
[Google Pixel 7 Pro] rester555:
What's the easiest way to disable magisk modules now? Adb? Through the app?
[Google Pixel 7 Pro] IdrisMC:
What prevents me from updating with OTA and than using magisk to patch inactive slot
[Google Pixel 7 Pro] roirraW "edor" ehT:
Instead of having my tutorial cover every single way that can be done, I choose to only share the way I do it. The only side-effects of not having root the first time you boot stock on new firmware are that I have to reboot into bootloader again to flash the rooted init_boot.img (I like to confirm everything's working just fine when completely stock on new firmware before I re-root) and then get into the AOSP Mods app for it to take full effect again (possibly also I have to import my last saved settings for AOSP Mods, I can't remember).

I have nothing against other ways of doing things, but there are all sorts of variations that could be covered. I feel the OP is already complex enough and full of plenty of information.

You're welcome! Woah!

Step #20 in Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

How to update each month (and also how to root)

[requires an unlocked bootloader for updating via this factory image method]

I don't use that method because it's often been unreliable. The only thing that prevents you is whether the method happens to be working this month. I can't say either way. I always use the firmware zip.
[Google Pixel 7 Pro] WillyRy:
I was wondering the same thing, as that's what I did with the Zero day update. But i wasn't rooted before the OTA.

AFIAK once rooted one needs the full OTA, where sometimes OTAs are incremental packages?

Although OTA, then extracting init_boot.img with phone's file explorer and patching with phone saves a couple steps, one still needs to Fastboot flash on a computer so it doesn't totally eliminate the need for a PC
[Google Pixel 7 Pro] Enddo:
for those who may be a bit confused about the update process. I have put together a full walkthrough that covers the entire process.
[Google Pixel 7 Pro] Enddo:
this feature has been spotty (at best) since the Pixel 6. even now, this has caused people to run into a bootloop and lose their data
[Google Pixel 7 Pro] roirraW "edor" ehT:
Surprise new image:

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

developers.google.com

13.0.0 (TD1A.221105.001.A1, Nov 2022, Telia)	Flash	Link	8c02369293402dc629728e0966d2ccc1976f513ed783ea2f64dcd1e55e221b3e
[Google Pixel 7 Pro] Ghisy:
Apparently, Telia is a Swedish company.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Added to Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version

Thanks, @Sib64!
[Google Pixel 7 Pro] nobrain3000:
Can i use this method when i'm on custom kernel?
[Google Pixel 7 Pro] HiM@L:
oh man. I forgot to disable verity while flashing Nov image. does that mean I need factory reset to flash custom kernel?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Spoiler content hidden.

See @Nekromantik's post below instead.
[Google Pixel 7 Pro] Namelesswonder:
Much newer radio and modem on TD1A.221105.001.A1, even newer than QPR1 Beta 3.1.

Firmware Image​

Radio Version​

TD1A.221105.001​

radio-cheetah-g5300g-220908-220908-b-9040061​

TD1A.221105.001.A1​

radio-cheetah-g5300g-220908-221031-b-9238462​

TD1A.221105.003​

radio-cheetah-g5300g-220908-221006-b-9144834​

T1B3.221003.003​

radio-cheetah-g5300g-220923-221001-b-9127780​

T1B3.221003.008​

radio-cheetah-g5300g-220923-221028-b-9229469​
[Google Pixel 7 Pro] Ghisy:
Another one now... The heck is going on with this phone?! 🤔
[Google Pixel 7 Pro] Ghisy:
Worth flashing on the worldwide November update?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hasn't happened to me yet on any firmware version so far.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Adding to OP. Thank you!
[Google Pixel 7 Pro] Nekromantik:
i dont thnk you need to factory reset when disabling verity IF you dont have the device corrupt message.

if you flashed nov update and forgot but have not flashed custom kernel then you can re flash the nov update and disable it. formatting only happens if you dont disable and then flash custom kernel and get device corrupt message.
[Google Pixel 7 Pro] piotrkruczek:
Will do to just flash new radio over November 3.1. update? :unsure:
[Google Pixel 7 Pro] EtherealRemnant:
Seeing how you're on a custom kernel, it's my bet it's the kernel. This is why I largely stopped using custom kernels because they introduced random instability. This phone is rock solid stable for me. So much better than the OnePlus 9 I came from.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes. You can always flash back the one from the QPR1 Beta 3.1 if the newer radio does worse for you.
[Google Pixel 7 Pro] Ghisy:
I think @roirraW "edor" ehT is also using Kirisakura and has no problems?
[Google Pixel 7 Pro] EtherealRemnant:
Just because one person doesn't have problems doesn't mean that another will have the same experience. That's the frustration of software development.
[Google Pixel 7 Pro] Ghisy:
I know.

I don't think I've seen others complaining about random reboots in the Kirisakura thread though.
[Google Pixel 7 Pro] Lughnasadh:
Given that I don't he's disabled verity and verification, I don't think he's using Kiri or any other custom kernel.
[Google Pixel 7 Pro] EtherealRemnant:
Again, that means nothing. Restore the stock kernel and see if it's still happening. Standard troubleshooting step.
[Google Pixel 7 Pro] Namelesswonder:
You are free to flash the radio from TD1A.221105.001.A1 over QPR1 Beta 3.1, but things might break. The build on QPR1 Beta 3.1 might be older but it is still from a slightly newer branch which might cause issues with cellular or other features that are new in QPR1.

Possibly, just flashing the radio over the global release should work. Safest bet would be to dirty flash the entire image, you will need to patch and flash the init_boot from TD1A.221105.001.A1, the image hashes did change.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Lughnasadh is 100% correct, I have not disabled Verity and Verification on the P7P (yet), so I haven't flashed any custom kernels. I'm just stock, rooted, with AOSP Mods and a few other Magisk/Lposed modules, but have had no issue.

^ This. Always return to as close to the stock condition as "reasonably" possible to confirm the same behavior. Unrooted if necessary. I know it's no small suggestion, but it's the price of modifying stock (and having issues). When done, if you confirm the issue still happens on 100% stock (you don't have to relock the bootloader, but enabling Verity and Verification would be good), then you should see about exchanging the phone.

If you exchange the phone without doing that first, you might have the same issue when running a new phone the exact same way.
[Google Pixel 7 Pro] pp085ster:
So I flashed the November update on my rooted Pixel 7 yesterday, but now I have a new OTA update at 11mb. Is this the TD1A.221105.001.A1 update? Considering it's for this Swedish Telia operator, can I flash? And if yes, any reason to recommend flashing it?

Thanks
[Google Pixel 7 Pro] Ghisy:
My bad, I was sure you were on Kirisakura.

I might just flash the November update and use the stock kernel for a couple of days. I'll see if I have some time to do that tonight.
[Google Pixel 7 Pro] EtherealRemnant:
If the phone is offering the OTA, there's something that it's meant to fix, so I would install it.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Usually, if there's firmware offered for your specific carrier, then you may have a better network experience using it. Since it just came out today, of course, you couldn't have known yesterday. I would try it if I was on Telia. Also, did you turn off automatic updates in Developer Options? It's known that Google can still get around that when they want to, but just thought I'd ask.

That's okay! Sorry for the confusion. :)

Good luck! For what it's worth, I hope it's not the hardware so you don't have to exchange it. The software can be fixed if that's the problem.
[Google Pixel 7 Pro] pp085ster:
That's the thing, I live in the US and have the unlocked version of the phone bought straight from Amazon, so I am not sure why it'd be proactively offering me an update meant for this Swedish Telia operator.

I was not aware of that auto update setting in Developer Preferences, I have deactivated it now. Thanks!
[Google Pixel 7 Pro] roirraW "edor" ehT:
I see. I thought you were saying you were on Telia, also.

You're welcome!
[Google Pixel 7 Pro] Ghisy:
@roirraW "edor" ehT, have you updated to November stable yet? Any problem with AOSPMods?

Some users on Telegram reported quick PIN unlock not working. If that's it, I'm fine disabling for now if I do update.