yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] Neuken6969:
followed all the steps flawlessly ... guess i missed a step because now i can not flash cleanslate-pantah-1.4.0v2.zip on my pixel 7 pro says

"unsupported android security patch level"

sorry wrong tab and place to put my error
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hopefully, someone else is on Windows 11. I'm on 10. Tried starting from scratch? In Device Manager, uninstall the existing driver while the phone is connected, but in the uninstallation dialog, check the box to actually delete the installed driver.

Then go back, and have Device Manager scan for hardware changes (or just unplug and re-plug your phone), then tell the driver installation dialog to look for the driver in the location where you've extracted the latest official Google driver.

If need be, you can always go the Official Google Android Flash Tool route,

Normally (every month for firmware updates), if using the Android Flash Tool to update/dirty flash, you should have the following items not selected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

If you're going to setup your phone from scratch anyway (and/or disable Verity and Verification), you can select wipe and/or force flash all partitions.

You should check in the [KERNEL] CleanSlate |S2S|AdBlock|VIB|BatterySvr thread. I know I've seen other users report that problem, but I don't recall what @tbalden or others said was the solution. You can also check the [Kernel] [Android Stable]Kirisakura for Pixel 7/Pro aka "Pantah" thread since it's based on CleanSlate, and I don't recall if I saw users report that problem in just one of the threads or both, but I think it was at least in the base CleanSlate thread (the first one above).
[Google Pixel 7 Pro] roirraW "edor" ehT:
Actually, now that I think about it, the problem for other users was that they hadn't updated to the latest firmware before attempting to flash the custom kernel.

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

How to Root the first time / aka How to unlock the Bootloader

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

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

for how to update your firmware. Just make sure and use this type of fastboot update line in the flash-all.bat, to keep Verity and Verification disabled every single time you update or just flash the firmware:

fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification
[Google Pixel 7 Pro] roirraW "edor" ehT:
I forgot to add, and do the steps all over again (uninstalling and deleting driver / reinstalling driver) once you're booted into the Bootloader (Fastboot mode) and connected to the PC.
[Google Pixel 7 Pro] Ghisy:
Does anyone know if we can have auto-rotate on for the phone but not for the lock screen? I only found a general auto-rotate setting in the OS.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Your lockscreen rotates!?

If you're using AOSP Mods, the Miscellaneous setting "Force-unlock all screen rotations" is what enables that.
[Google Pixel 7 Pro] Ghisy:
Duh, you're right haha! Completely forgot I turned that on! Thanks.

Although I wish I could force all screen rotations (like a 360 rotation) but not for the lock screen. I might ask the dev but already asked to have a setting to modify heads-up duration!
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's funny because I had been previously looking for an option to allow the lockscreen to be landscape, without allowing all rotation normally. :) But it's not that important to me.

I used to like the all-way rotation on some previous phones, but if I grab my phone the wrong way, I want to know as soon as possible that I have it upside-down. LOL!

Glad it was something simple.
[Google Pixel 7 Pro] Neuken6969:
I read downloaded the firmware, extracted everything into my platform tools folder ran the bet file took out the minus w ere routed and I'm having the same issue
[Google Pixel 7 Pro] roirraW "edor" ehT:
If need be, you can always go the Official Google Android Flash Tool route,

Normally (every month for firmware updates), if using the Android Flash Tool to update/dirty flash, you should have the following items not selected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

If you're going to setup your phone from scratch anyway (and/or disable Verity and Verification), you can select wipe and/or force flash all partitions.
[Google Pixel 7 Pro] Neuken6969:
Thank you, I can try that route. I have already setup my new phone twice. A third time won't hurt lol.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Android Flash Tool should tell you if it's unsuccessful in updating your phone. If you go back to trying the factory image zip method, if you can copy and paste what the command line output is of the entire flash-all.bat into a:

[ c o d e ]

[ / c o d e]

code box here (without the spaces), that may tell us something helpful. There should be some point in which the processes' command line output should tell you something didn't work correctly.
[Google Pixel 7 Pro] schmeggy929:
Yeah it sounds like you didn't disable both verity and verification when flasher the firmware update
[Google Pixel 7 Pro] HipKat:
This Pixel Flasher to this reminds me of using an Arch Linux fork vs building Arch from Scratch.

Building from scratch takes longer and each step has to be executed correctly and in order. Flashing an Arch-based ROM does the work for you.
[Google Pixel 7 Pro] EtherealRemnant:
I had an issue while changing between pSIM+eSIM and dual eSIM that caused my phone to stop recognizing my Boost SIM card (it basically acted like no SIM was inserted even after reboots and network settings reset but worked fine with my other SIM) and I used the Android Flash Tool to get myself back to .031 (which fortunately fixed the issue). In doing this, I told it to not lock the bootloader. I could have sworn people were saying just having the bootloader unlocked didn't break GPay for them but it has indeed broken it for me so I guess I'm going to have to do the whole root and SafetyNet nonsense when I get back to my house on Monday.
[Google Pixel 7 Pro] EtherealRemnant:
Thanks for the excellent guide! All is working fine, at least as far as Wallet is concerned.

My SSFCU app continues to hate root and won't even load fully lol. Denylist makes no difference.

Fortunately I don't really need that app.
[Google Pixel 7 Pro] Dbj.Dhaval:
Coming from One plus 7Pro. Just received pixel 7pro and its on 220804.009.A2 build. I have not yet updated or setup my device. My questions are:

1. If I want to unlock bootloader can I use android flash tool to update to latest build and select Wipe Device, Force Flash all Partitions, Disable Verity & Verification unselect lock bootloader. Will this work? will the tool automatically update and unlock the bootloader(OEM unlocking toggle on manually)

2. By selecting Disable Verity & Verification in the above step is it for both slots?

3. After that the next step should be patch the init.boot file via magisk and flash? and then flash kernel?
[Google Pixel 7 Pro] xflowy:
I'm chiming in with a disable verity & verification question too.

I read somewhere, that if you disable it, you have to modify the flash-all everytime you upgrade flash a new image each month. is that right and where do i change that?
[Google Pixel 7 Pro] schmeggy929:
Probably would be easier to just update the phone from the phone. That would eliminate having to download multiple firmware to flash. update to latest, then you can unlock bootloader, select wipe, disable Verity and verification. This will only disable the current active slot Verity and Verification. Pixel Flasher is a similar app( on computer ) , with advanced features like patching init_boot.img for you.
[Google Pixel 7 Pro] schmeggy929:
That is correct, you will have to modify the Script inside the zip to disable Verity and Verification EVERY TIME. Or use the two other options, Android Flash Tool or Pixel Flasher.
[Google Pixel 7 Pro] xflowy:
thanks! but how do i have to modify it?
[Google Pixel 7 Pro] Dbj.Dhaval:
Okay so say suppose i update to latest firmware and follow the OP instruction to unlock bootloader. Again if i flash init.boot will it flash to only current slot or both? can anyone plz share the all flash file with instruction to disable verity & verification on both slots.
[Google Pixel 7 Pro] roirraW "edor" ehT:
It's possible that it used to be the case and it changed. I never have only my bootloader unlocked without being rooted, so I wouldn't know.

You're welcome!

Yes, yes, yes. :)

No, you'd have to manually change slots and then do the process over again the same way.

That's correct.

That's correct:

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

Optional steps when updating - flashing custom kernels

fastboot update image-cheetah-buildnumber.zip --disable-verity --disable-verification

To be clear, you only have to download the latest firmware, always. Also, taking OTAs is slower than using the factory image zip/flash-all.bat process.

Right-click on the flash-all.bat on Windows, choose Open With and select Notepad.

Only the current slot. The instructions are the same as in the OP, just do the process the first time, and then:

adb reboot bootloader
fastboot --set-active=other
fastboot reboot bootloader
flash-all.bat

So you're doing the flash-all.bat a second time on the second slot.
[Google Pixel 7 Pro] schmeggy929:
In the firmware zip you download, extract the zip, there will be a bunch of files and another zip. Open the Flash-all.sh file in Notepad. Remove the -w and add --disable-verity --disable-verification between Fastboot update and image-XXXXX.-cheetah.img. replace that file back into the zip.

ie.

fastboot update --disable-verity --disable-verification image-cheetah-td1a.220804.031.zip
[Google Pixel 7 Pro] schmeggy929:
Lol, I'm accustomed to always flashing firmware in order as someone who programs Motorola and Harris radios for Public Safety. I don't trust Google these firmware updates are cumulative.

I do understand the firmware updates are the entire OS and not patches, just my preference I guess.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm not a betting person, but I guarantee that the system firmware will be 100% identical if you merely flash the latest, or step through all the individual ones on the way. :) It's been like that since before I had my first Pixel in 2016. OTAs are cumulative, factory image zips contain the complete firmware. Either way, currently there is only a single newer firmware for the Pixel 7/Pro (until Monday when the next one should come out).
[Google Pixel 7 Pro] xflowy:
@roirraW "edor" ehT thanks very much mate! do i go with the a2 or the normal version when in germany?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

Unless a firmware specifically mentions your country, you should normally go with the one that isn't country-specific, but you shouldn't be using the .009.A2 or the 009.A5, anyway. You should be using the single .031 firmware since that is the latest. The .031 equates to the zero-day OTA both .009.xx firmware gets. Zero-day because it was available at least by the day the phone was officially available in people's hands.

From the instructions in Post #2:

Download the latest Pixel 7 Pro Factory Image (at the bottom of the "Cheetah" section).

And from the OP and Post #8:

13.0.0 (TD1A.220804.031, Oct 2022)	Flash	Link	6152f6f3d8437be0ef840ed7056f15d0f52ba181a1d029ff84bd9d83c860d49f
[Google Pixel 7 Pro] xflowy:
If I'm at the beginning of the process (and wont mind wiping), can I use this line also with the -w included?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, absolutely.
[Google Pixel 7 Pro] Lughnasadh:
To disable verity and verification on both slots (when not updating or flashing firmware), I imagine you could also do:

fastboot flash vbmeta --disable-verity --disable-verification --slot=all vbmeta.img

or

fastboot --disable-verity --disable-verification flash vbmeta_a vbmeta.img
fastboot --disable-verity --disable-verification flash vbmeta_b vbmeta.img

But that's probably neither here or there as the other methods already discussed are fine.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, absolutely.

I try not to present too many choices as it gets confusing to some people, plus it's even more information to "maintain". If there's a change in behavior or the details in the method, it's yet more things that the instructions have to be modified for.

I do think that the more choices available, the better. Just for the OP's sake, I want to keep it quasi-streamlined. That's why I prefer to make the OPs "Here's how I do (or would do) things" instead of "Here are all the ways you can do these things" except for a few alternate choices because sometimes there does seem to be inexplicable reasons something doesn't work normally.

All that said, I am definitely open if anyone has any suggestions for improvement, at all times. Many heads, like choices, are good! Kind of like Zaphod Beeblebrox. Well, that's not a good example. 😎
[Google Pixel 7 Pro] xflowy:
Ok i have to ask again: do it copy --disable-verity --disable-verification in the middle of the line or at the end. getting conflicting statements here..
[Google Pixel 7 Pro] roirraW "edor" ehT:
Doesn't matter where.
[Google Pixel 7 Pro] Lughnasadh:
Yeah, I wasn't suggesting that it be added to the OP (hence my statement at the end). Just throwing it out there. 👍
[Google Pixel 7 Pro] xflowy:
So I just finished the process by rooting. Booted up and now my pin isnt working - says wrong pin. Sim isnt inserted yet. Wtf?
[Google Pixel 7 Pro] roirraW "edor" ehT:
I thought you included the "-w" to wipe, or do you mean you had just set the pin after having rooted and rebooted and now it's not working? I've never seen that.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Sometimes I come off as if I'm giving a speech, otherwise known as "I can talk too much". LOL!
[Google Pixel 7 Pro] xflowy:
I wiped the phone with the flash-all. Booted it up and set it up (including the pin). Then I patched the boot_init, flashed it, booted up and thats where I'm at now.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Very weird. Yeah, I haven't seen that, nor read about anyone else having that issue. Hmmmmm.... I think you'd be okay if you wiped again. You could also try reflashing the stock unrooted init_boot.img, but it shouldn't make any difference what kernel you have on there.
[Google Pixel 7 Pro] roirraW "edor" ehT:
https://twitter.com/i/web/status/1587923675189108736
[Google Pixel 7 Pro] WorldOfJohnboy:
Hey all, I'm curious about something... as you may recall, I got CTS matched last month (before the process to do so was resolved here) by performing the following:

If this is not the case you might also need to fix your CTS profile match. You can resolve this by doing the following steps:

When I did that, the Pixel 7 Pro was not available in the 2nd to last step, so I chose Pixel 6 Pro--in essence, I spoofed my fingerprint (to my understanding).

Once the November update drops from Google, I want to install the full image, without wiping. When I do that, will my Fingerprint also reset to Pixel 7 Pro? If not, how would I SU and get it back to the "default" or Pixel 7 Pro? I realize that this may not be an appropriate question to ask here, but was hoping someone much more intelligent about fingerprints in this thread would be able to speak to it. (I've asked in a different thread as well, where I got the quoted steps above from.)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hello again! I'm not positive if MagiskHide Props Config keeps its own settings or writes settings once. I'm a little confused by part of your question, though. It could be just the wording, and I didn't get much sleep the night before last and I think I still have some brain drain.

At the most, you should probably just do the same steps you did the last time in order to spoof the Pixel 6 Pro - if that's what you want to do, and if that is fully required to get whatever your problems apps are to work.

Also, last month before you tried the MagiskHide Props Config, did you try Displax' new Universal SafetyNet Fix, which is a later minor revision of the test MOD version previously posted in this thread, and of the original MOD 2.0 which apparently had some typos - the latter which didn't work due to the typos but is now fixed if you download the latest one. You can get it either from XDA or on GitHub. I don't remember if it was already released by Displax when you were having the issue with your phone, or if you found your workaround before the MOD 2.0 USNF was released.

With it, you shouldn't need MagiskHide Props Config at all, to my understanding, although it is certainly possible that there are some weird exceptions. You can see my full SafetyNet instructions in

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

SafetyNet

It's a fine question to ask here, by the way.
[Google Pixel 7 Pro] mad4some:
Just starting out with bootloader unlock and stuck already o_O. OEM unlocking toggled on and using latest sdk tools phone is fully recognized in adb and fastboot and in device manager shows as "Pixel 7 Pro". I can't update any drivers as it reports: "best drivers already installed". Everytime I run "fastboot flashing unlock" it returns a long list of options to choose (never seen that before) and the "unlock bootloader" option is not showing up on the phone fastboot menu (vol up/down push power button). I read op and a number of pages but not all 56!!
[Google Pixel 7 Pro] capntrips:
Can you share the console output when you run the command?
[Google Pixel 7 Pro] roirraW "edor" ehT:
You can also force update the drivers by uninstalling the driver, but checking the optional box to delete it too, then install the driver and point it specifically to the folder where you extracted the latest driver. This needs to be done not just when Android is running (to get ADB working), but also when in the bootloader (fastboot mode).

Are you following the steps in Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:

Unlocking Bootloader

(required in order to root)

?

Besides those things, as @capntrips said, a codebox copy-paste of the command prompt results would be helpful, and so would a picture of what you see on the phone when you follow the steps.
[Google Pixel 7 Pro] EtherealRemnant:
adb reboot fastboot

Go to Device Manager > Portable Devices > Pixel 7 Pro. Now try to update the driver using the root of the driver folder from the zip file.

I ran into this same issue last night. Windows 10 was installing some adb-compatible drivers by default and it was refusing to update to the Google ones. Putting the phone in fastbootd revealed the proper device and upon updating that one, it updated all my drivers to Google.

Next type

where fastboot.exe

into cmd. If you have multiple copies, delete them. I had this issue on my home computer.
[Google Pixel 7 Pro] mad4some:
Here...
[Google Pixel 7 Pro] WorldOfJohnboy:
I don't really want to spoof... I only did so as my Corporate Apps were blocked until I could get CTS to go Green--once I spoofed to P6P, CTS Passed and my apps worked. If there is a way to get the P7P to pass CTS without spoofing, that is my preference. I cannot update my Google Camera app and I think it's because of the spoofing.
[Google Pixel 7 Pro] mad4some:
When I right click "Pixel 7 Pro" in DM only option I see is "uninstall device" and never see a delete driver option. Fastboot screen never changes when entering "fastboot flashing unlock"
[Google Pixel 7 Pro] capntrips:
What about the output of the following commands:

where fastboot
fastboot --version

Preferably a copy and paste into code tags, rather than a screenshot. If the where command reports a path other than your current one, you have an old one somewhere on your PATH that needs to be removed.

On Linux, you can prefix the command with ./ to use the local binary. You may be able to do something similar with Windows (e.g. .\fastboot.exe).
[Google Pixel 7 Pro] roirraW "edor" ehT:
Then try going into the device's properties first (in Device Manager), choose the Driver tab and choose uninstall there, then you should get the checkbox to delete the driver when you uninstall it.
[Google Pixel 7 Pro] mad4some:
Ok I already went there and no delete driver option. I'm out of time today to work on it but will figure out a way to get the proper driver installed tomorrow, thanks
[Google Pixel 7 Pro] Neuken6969:
Come to think of it there was a final line at the end that wasn't positive. I will run it when I get home, hopefully 2 hours. Should be leaving NYC in about 15 min.
[Google Pixel 7 Pro] EtherealRemnant:
If you do what I suggested above, it will work.
[Google Pixel 7 Pro] xflowy:
@roirraW "edor" ehT short slight off-topic since i'm returning my old 6 pro to its original state.

when i apply the flash-all.bat to both slots (with -w update included) the whole phone will be wiped, right?

thanks man! you are always a great help!

edit: i know that I wouldnt need to switch slots for that and one flash will do it..
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, the whole phone will be wiped, although personally when I return a phone to stock unrooted, I use the Android Flash Tool since it has a checkbox to also lock the bootloader, although now that I think about it, it would make more sense to use it once on your existing slot without relocking the bootloader, then switch slots and do it again but the second time let it lock the bootloader. 😁

The flash-all doesn't flash the other slot, so if you ever modified the other slot with a rooted and/or custom kernel, or disabled Verity and Verification on the other slot, you would want to switch slots and run the flash-all.bat again.

You're welcome! And thank you!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Did you click Uninstall (shown in that screenshot)? That's when the uninstall dialog, with a box you can check to delete the driver, appears.
[Google Pixel 7 Pro] HipKat:
OK, coming back to rooting after 11 years is like moving out of a small town and 10 yrs later coming home to a big city.

WTH is the deal with the slots? Of all his involved with rooting these, the slots are what I'm confused by
[Google Pixel 7 Pro] Lughnasadh:
For rooting you don't really need to worry about slots. Just patch your init_boot.img in Magisk and flash the patched image in fastboot and your current/active slot will be rooted.
[Google Pixel 7 Pro] HipKat:
Yeah I gathered that, I just wanna know wth they are
[Google Pixel 7 Pro] Lughnasadh:
A/B (seamless) system updates | Android Open Source Project

source.android.com

A/B (seamless) system updates | Android Open Source Project

source.android.com
[Google Pixel 7 Pro] roirraW "edor" ehT:
Hehe... Ninja'd again by @Lughnasadh. Actually, double ninja'd.

I'm sure there are better explanations, but the two slots carry two sets of the system files...the firmware. Both slots use the same user apps and (this is important) same app data (system and user). Someone correct me if any of that is wrong, but definitely same user apps and same user app data.

If something happens where one slot won't boot repeatedly, eventually the phone will switch slots and boot the other one. As @Lughnasadh said, you don't really have to worry about it.

You may choose to once you get more experienced in modern rooting, but don't worry about it for now. Keep it simple.
[Google Pixel 7 Pro] HipKat:
lol, I'm not good at simple! I hate not knowing things lol
[Google Pixel 7 Pro] roirraW "edor" ehT:
But you've got to admit that I have a lot of information to know in my now 8-post OP, already without dealing with the two slots. 😂

Fine. It has been port forth by several reputable users, and I do agree it makes sense, that every month when you update the firmware, it would be wise to switch slots before each time, and that for the first time flashing firmware on the phone at all, you should probably flash both slots.