yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
I wouldn't wait for the battery to run out. I would be proactive and try to force it off. See Google's instructions here for the Pixel 6 and later: Turn your Pixel phone on & off. Despite the display being black, the phone is still functioning to some level, but obviously, we can't know exactly to what extent without trying.

Once you force the phone off, press the Volume Down and Power buttons for a couple of seconds. You're supposed to release the buttons when the bootloader (fastboot mode) appears, but obviously, you'll just have to use your best guess without being able to see what the phone is doing.

At the point that you think the phone should be in bootloader (fastboot mode), connect it (and only this single Android device) to your computer, open a command prompt, and navigate to where you have the latest platform-tools extracted. Try to perform the command:

fastboot devices

If the command results in a serial number, you know that the phone is actually in bootloader (fastboot mode). If you get the serial number response, immediately go here: Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own). On the flash site, check the boxes for full wipe, force flash all partitions, and make sure the box for relocking the bootloader is unchecked.

Everything should be back to normal.

Good luck! You may have to try several times just to be sure you're holding the buttons down for the right length of time. Whatever you do, don't take too much time before you contact Google, if you don't have any luck in the meantime.

Nothing stood out to me as being a likely culprit when I read what you wrote, but first things first, let's try to get the phone going again, or if that's impossible, get a replacement phone from Google.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks added to the OP for @DespairFactor who released Despair Kernel for the Pixel 7 Pro (which also works for the Pixel 7). Note they they also provide AK3 Zip versions of the kernel, which only require Verity to be disabled - this does still require a factory reset in combination with Despair kernel, and preferably before flashing the kernel Zip in Kernel Flasher app. XDA thread for the Kernel Flasher app is here. You can still disable Verity and factory reset after flashing the kernel to get your phone working again.

LOL, I already have @DespairFactor in the thanks, I'm just overloaded with trying to catch up with information. :D
[Google Pixel 7 Pro] DespairFactor:
Also lowered the voltage of the display a bit:)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yep, I'm looking forward to flashing it when I can catch my breath. :D Either later today or sometime tomorrow. Thank you!
[Google Pixel 7 Pro] slubgob:
This is probably something really basic I'm messing up, but I'm stuck. I've got the most recent platform tools, my drivers are updated, and I've unlocked the bootloader. USB debugging enabled. USB mode not changed. Using a Windows machine. Using a cord that worked fine with my 4XL.

Following the directions, I dl'ed the cheetah factory image to the platform tools and unzipped it to the same folder. Went into the unzipped folder, modified the flash-all.bat. Used 7Zip to extract the init_boot.img to the platform tools folder.

Fired up a command window from the platform tools folder. ADB reboot into bootloader. Confirmed the bootloader sees the phone with fastboot devices.

This is where I get stuck: When I flash-all.bat I get "'flash-all.bat' is not recognized as an internal or external command, operable program or batch file."

Any thoughts about what I might be doing wrong?
[Google Pixel 7 Pro] badabing2003:
What does dir command show?
[Google Pixel 7 Pro] i5lee8bit:
Thanks so much for your thoughts and insight man. I wasn't expecting you to really analyze my posts, certainly not so quickly, and I totally understand having a life outside of XDA so no worries at all! I see what you're saying though, thanks for clarifying.

Yeah, I'm just gonna deal with not being able to easily pay for stuff from my phone. Unfortunately since I'm now mostly stay at home dad chasing around a 2 year old all day, I almost exclusively use my phone to take care of bills, shop, communicate, etc. Otherwise I'd just do those things on my laptop/desktop, no big deal. But I've basically concluded on the same thought as you - just leave it alone for now and hope it gets settled.

I did send feedback to Google via the GPay app as well as through the system settings. Couldn't find a feedback jawn in Chrome.

One final thing I noticed (that makes it super easy to test out if you're affected by this). The same crash occurs when i try to open Tips & Support. The very last menu entry at the bottom of Android settings. If I tap it, it'll just flash really quickly (like a window trying to open and immediately closing). 2nd time, "Google Support Services keeps stopping" message. After that, it'll keep flashing every time I tap, but won't say about Google Support Services keeps stopping. This is the SAME EXACT behavior as what happens when I tap the Get Help 3 dot menu entry in GPay. I'd be curious for others to try this...

Anyway, you're crazy dude. It's like another full time job keeping up with all the posts in this thread. I salute you, good sir!! 😀

EDIT: ADDING FOR EASY VISIBILITY, IF YOU SEE THIS, CAN YOU PLEASE TRY OPENING YOUR SETTINGS AND TAP "TIPS & SUPPORT", THE VERY LAST ENTRY UNDER SYSTEM SETTINGS? Let me know if it opens for you, or crashes (and in particular, gives a force close / keeps stopping message about Google Support Services). Trying to see if this is a more widespread issue or if it's just me... 😢. My prior posts explain how this is a sort of "symptom" of bigger issues (Chrome not syncing, GPay not loading, possibly more). Thanks!
[Google Pixel 7 Pro] slubgob:
"Directory of C:\Users\[username]\Desktop\platform-tools_r33.0.3-windows" and a list of what's in the folder.

Dumb thought -- do I need to change my directory or start the command window from the unzipped image where the flash-all.bat file is i.e. C:\Users\[username]\Desktop\platform-tools_r33.0.3-windows\cheetah-td1a.220804.031-factory-6152f6f3\cheetah-td1a.220804.031 ?
[Google Pixel 7 Pro] i5lee8bit:
Try typing in just "flash-all", no .bat. That would eliminate if it's a problem with possibly having hidden extensions enabled in Windows. Batch files run regardless whether you append the .bat to the end.

You could also just double click the bat file from Windows Explorer.

edit: just saw your new post you submitted while I was typing above. You need to run the flash-all.bat while cd'd into the folder that actually contains it. An easy way to do this would be to browse to whatever folder contains flash-all.bat and all the factory image files you extracted to, go to the address bar at the top, and just type in cmd and press enter. It's a general Windows trick that will open a command prompt window already cd'd to that directory.
[Google Pixel 7 Pro] PurppleMonkey:
So.... I tried, the command "fastboot devices" automatically returns me to line in the command prompt BUT on trying again the manipulation to turn it off the phone went cold (so I assume it was turned off). I tried the manipulation to put it in bootloader mode and when I type "Fastboot devices", this time the command prompt returns to the line without the possibility of typing a new command... strange, isn't it?

I assume the phone is in bootloader mod but... it is bricked ?
[Google Pixel 7 Pro] dmbardal:
No crash here.

Pixel 7 (Not pro). Rooted. Xposed (LSPosed), SafetynetFix. Passes everything.
[Google Pixel 7 Pro] slubgob:
OK, did that. Fastboot rebooted a few times, then the command window returns "fastboot: error: device requires partition vendor_kernel_boot which is not known to this versoin of fastboot"

The phone is in fastboot. Boots normally when I hit start. Checking the build number of on TD1A.220804.009A2. That should be .031 if it went correctly, right?
[Google Pixel 7 Pro] i5lee8bit:
Sounds like you have an old version of adb / fastboot platform tools and your PC is using them instead. Did you ever install Minimal ADB / Fastboot tools, Samsung drivers pack sort of thing, or basically anything that contained ADB/fastboot? You'll need to uninstall those.

You can also check what version is being used by typing in

adb version

If it's not 33.0.0.3 (or whatever, sorry, not at PC right now), it's using an older version that was installed to your PC at some point.

Also, that means that no, it did not fully flash the new firmware (correct, it should say .031)

Edit: just checked "adb version" output on PC. It should show you the version (should be 33.0.3), as well as the environmental variable path that Windows looks for it under. What does it say for you? Because this can vary, I'm not sure if you unzipped adb / fastboot tools to where you unzipped the firmware files, or installed an adb/fastboot pack, or had it installed via Android Studio's SDK Manager (my preferred way, because it adds the environment variables automatically to Windows paths. And it's very easy to keep your tools updated to newest version). Let me know what adb version output says, and we should be able to figure this out.
[Google Pixel 7 Pro] slubgob:
Yeah, it's 33.0.3. Debug bridge version 1.0.40. Version 4986621

No, never installed minimal ADB or Fastboot tools that I recall. Samsung drivers maybe from the Nexus days? Didn't encounter this problem with the 4XL, though.

Maybe I'll just install drivers and adb on a computer that has never had them and try again from there...

Got get going, family wants to go hiking...
[Google Pixel 7 Pro] roirraW "edor" ehT:
I just realized what you said the solution was. I don't know if it's necessary for everyone, but I just did that for myself too, and can confirm it stays denied when I only deny the com.google.android.gms. I'll add that to my list in the instructions later. As always, it doesn't hurt.

Thanks!

Sounds like you have the factory image zip extracted to a subfolder of the platform-tools folder, therefore even you're in the platform-tools folder on command prompt and type flash-all.bat, the batch file can't be found.

The flash-all.bat and all the rest of the files from the factory image zip should be in the same folder as the ADB and Fastboot commands.

No sweat, you're welcome!

Tips and Support works fine for me.

FYI, in Google Chrome on Android, hit the menu button and the last entry is Help and feedback, if that helps any.

See my answer to you earlier in this post. I think you have the factory image unzipped into a subfolder of where the ADB and Fastboot commands are.

It probably is bricked, yes, if you force turned it off and then attempted to use the hardware keys to get into the bootloader (fastboot mode). If it's bricked in a way that you can't get a response from Fastboot commands, then only Google can help you.

I highly discouraged anyone from using any third party repackage of the platform-tools. They were more useful when the only way to get them from Google's official source was to install their developer tool, which was overkill for those of us just wanting the platform-tools.

Ever since several years back (6+?) they provided direct downloads of just the platform-tools, you should stick with them.

For every month's update, I freshly extract the latest platform-tools so I have a clean folder structure you start with.

Also, always remember to kill your old adb instance, either with adb's command options to kill server, or by using Windows or similar Task Manager, otherwise you can inadvertently be using an old version of adb that's still running on the background instead of the one in the folder you're running it from.
[Google Pixel 7 Pro] wrongway213:
I've been looking all over the forums and trying to find a way to flash a kernel without having to wipe, as I currently have verity enabled. If I'm reading this right, there is a way and I have missed it. I would greatly appreciate a nudge in the right direction, cuz I am ready for kernel flashing and really wish to avoid setting the device up again if possible.

Thanks for your time and maintaining such an informative thread for all us 7 series users!
[Google Pixel 7 Pro] badabing2003:
lol,

I wanted to see the list so that I could advise you on what to do.

Please paste the output of this command

dir /s/b
[Google Pixel 7 Pro] roirraW "edor" ehT:
You bet, you're welcome. Disabling Verity, alone, does not require a factory reset.

Disabling Verification does require a factory reset. There's no need to disable Verification if you flash the AK3 Zip version.

@DespairFactor's AK3 Zip version of his kernel only requires Verity to be disabled, hence as long as you flash the AK3 Zip variant from his provided Google Drive download link, only disable Verity before flashing.

Even if you forget to disable it before flashing it, there's no destructive consequences - just boot to the Bootloader (fastboot mode) and disable it, then you can boot normally.

They also anticipate that eventually, like on the Pixel 6 Pro, you won't have to disable anything to flash the AK3 Zip.
[Google Pixel 7 Pro] wrongway213:
Thank you so much for the detailed answer! This is very useful and now I guess the only decision is whether to disable verity and flash AK3 or to wait and see. Gonna look more into verity on the 6+ series devices and see the pros/cons and go from there. Thanks again!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Adding thanks in the OP to @capntrips for everything you do: especially AK3 work and Kernel Flasher app (XDA thread here).
[Google Pixel 7 Pro] capntrips:
Right back at you. I frequently check your threads when I'm out of the loop on something.
[Google Pixel 7 Pro] slubgob:
That appeared to be my issue. Thank you!!!

Sweat a little bit with the various reboots and long while on fastbootd, but it looks to have worked. Now on to patching in Magisk.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome! Thanks for letting us know about the success. You're welcome!

Note that you *can* have files in different places than this, you just have to tell fastboot (or any command performed in command prompt) where the files are if they're not in the same folder - but I like to keep things simple and keep them all in the same place.

@badabing2003 tagging you for your possible interest that it was the problem we thought.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm glad you also figured out that my typo of "three" meant "the". :D
[Google Pixel 7 Pro] Lughnasadh:
Opens fine for me.

EDIT: Just realized this may have been meant only for The Rode Warrior and not everyone. If so, sorry and disregard.
[Google Pixel 7 Pro] badabing2003:
Thanks,

Happy to see that it all worked out.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I hope I caught you in time. Apparently normally, disabling Verity doesn't require a factory reset, but in combination with @DespairFactor's Despair kernel so far, even the AK3 Zip does require a factory reset. They're working on it and may have a solution to not require a factory reset eventually, but not yet.

Apologies for the misinformation.
[Google Pixel 7 Pro] Ghisy:
By the way, Kirisakura is coming soon for the P7P! :D

https://xdaforums.com/t/kernel-04-1...pixel-6-pro-aka-raviole.4358435/post-87583795
[Google Pixel 7 Pro] wrongway213:
That's what I had surmised from the thread and so I haven't flashed anything yet. Thank you for being so diligent to reply with this! Great info for anyone else who might have read your reply earlier. You're doing a great job keeping this massive amount of info straight! No worries at all, friend.
[Google Pixel 7 Pro] sliu821:
I'm getting nothing when I do a fastboot devices.

I am using windows 11 pro

I did oem unlock and turned on usb debugging. I connect the phone and updated the usb driver to the google usb driver. now the driver shows as Android Device-> Android Composite ADB interface. the 7 pro shows USB debugging donnected. but it still shows nothing.

I also tried the troubleshooting steps to turn on fast startup and turning off driver signature enforcement.

What am I missing?
[Google Pixel 7 Pro] Ghisy:
If your phone is booted up, try:

adb devices

If this works (an ID will show up on cmd), type

adb reboot bootloader

Then proceed with whatever you wanna do in fastboot.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Awesome news, thanks for sharing! The more, three merrier.

Whew, I'm relieved. You're welcome. I'll try not to make that same mistake again. 😬 Thank you for your kind words!

When you did fastboot devices, were you already in the bootloader (fastboot mode)? With Android running, the command is

adb devices

Once you

adb reboot bootloader

Then you can

fastboot devices
[Google Pixel 7 Pro] Bad Bimr:
Not my first time doing this but something has me stumped. To be honest I went about rooting the Pixel 7 like any other pixel before it. Did 3 Pixel 6A's last month and all were on Android 13.

Latest Platform Tools (Older USB drivers)

Unlocked bootloader

USB Debugging

Installed Magisk 25.2 (I mistakenly patched the boot.img)

Reboot into bootloader

fastboot boot patched boot.img (always test so no boot loop)

NO ROOT

crossed my fingers and

fastboot flash boot patchedboot.img

Still No Root

Saw this thread and decided to flash the stock boot image.

fastboot flash boot boot.img --slot all

Used Magisk to patched the int_boot.img

Tried to flash using

fastboot flash init_boot_a patched-int_boot.img (NO ROOT)

Tried

fastboot boot init_boot_a patched-int_boot.img (NO ROOT)

What am I doing wrong?

All help will be greatly appreciated.

Thanks

BB
[Google Pixel 7 Pro] roirraW "edor" ehT:
Update your drivers and let us know if it still has issues. Link in the second post.

I haven't tried flashing the Magisk'd init_boot.img to a particular slot. Try

fastboot flash init_boot magiskpatchedinitboot.img

You can also refer to the rest of Post 2 for flashing it. Good luck! Let us know what the result is.
[Google Pixel 7 Pro] JakeDHS07:
This just made my night. Been using @Freak07 kernels on my Pixel 4 XL for years. Glad to see I'll still be able to. Fantastic news.
[Google Pixel 7 Pro] Bad Bimr:
!!! AWESOME !!! It Worked. I did update the to the Rev 13 USB drivers. Now to add a few modules and SafteyNet Fix.

EDIT: I installed the following modules Advanced Charging Controller (ACC), MagiskHide Props Config, and Universal SafteyNet Fix (v2.3.1 MOD2). I also activated Systemless Hosts.

I configured Magisks DenyList. GPay & Wallet accepted my CC cards so everything looks good.

Only thing that was weird was I hide Magisk and changed the name from settings to something else and after a reboot it was system again? Renamed it again and now all seems good. Something weird & wacky always happens.

Thank You!
[Google Pixel 7 Pro] i5lee8bit:
Nah man, I appreciate it. It was a general request for anyone. I'm just at a loss as to why my phone keeps ending up in this broken state. It would make me feel better if it were happening to other people too (as much as I don't wish others this problem). At least then I would know it's not just me, lol
[Google Pixel 7 Pro] roirraW "edor" ehT:
Great! Was it the USB driver or the fastboot flash init_boot magiskpatchedinitboot.img that solved the issue? You're welcome!

I am a little worried about it, on your behalf. About the only thing remaining other than waiting, that I can think off is to start off completely from scratch with a locked bootloader and minimal apps to start. If you pursue that avenue, I would start off with the Official Google Android Flash Tool (OEM Unlocking needs to be toggled on - you do not have to manually unlock the bootloader - their site will do that on its own). Choose the options to wipe, force flash all partitions (which also wipes), and the option to re-lock the bootloader.

Now see if the issue persists while completely stock and with minimal apps. I know this is drastic, but if the issue still happens, I would consider talking to Google to get a replacement phone. If it doesn't happen, it could mean one of two things: 1) that the Android Flash Tool fixed the issue - it definitely fixes things that the factory image zip doesn't, as testified to by myself and a dozen or more other users over the last year in the Pixel 6 Pro section. 2) it could just mean that it's something while rooted that's causing the issue.

That would also be a good step to have taken before talking to Google.

If you do pursue getting your phone replaced, sooner would be better than later since Google is less likely to replace your phone with a refurbished device since the phone only just came out. I don't know how long it would take for them to replace it, however.

Responding to this part late. It helps to be a little crazy. 🤪 Thank you for your kind words!

Responding to this very late, congratulations and I understand - I'm glad she doesn't have to deal with this too.
[Google Pixel 7 Pro] i5lee8bit:
You know what though, you might be onto something... When I tried to flash .031 onto my wife's panther, I kept getting errors as soon as it reached one of the chunks of the vendor (iirc) partition, the problem parsing error. That was from command line, and even the online tool (except online tool didn't tell me exactly what, but I knew). It happened using multiple ports, multiple USB cables.. until I plugged in using an old HTC USB 2.0 cable!! But I did my cheetah first with no issues using a USB A -> C 3.0 cable. Maybe it did flash something improperly unknowingly. I'll try the online flash tool with a 2.0 cable and see what happens... Not sure how "drastic" I'll go and when I'll get the chance, but again I truly appreciate your advice!!

Edit and PS: just curious, what kind of problems happened that the online tool fixed back in the P6 days? Nothing super detailed, just curious. 🙂
[Google Pixel 7 Pro] NepoRood:
I could be off, but I think you may have a corrupted slot. Take it with a grain of salt, in my experience weird things can and often do happen...

IF it were me, I'd wipe and flash the stock firmware to both slots. This will insure the device is completely clean of any kind of modifications. Afterwards, let it run for a day or so and see if the problem persists.
[Google Pixel 7 Pro] i5lee8bit:
Thanks, I'll do a combination of both your advice. Appreciate it!!
[Google Pixel 7 Pro] Agenesis:
Anyone able to pass CTS profile check yet? Got Lsposed + magisk installed. There doesn't seem to be a fingerprint profile for our devices yet.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, with the below:

Plus the rest of the SafetyNet steps I have listed at the link below for Post #2:

You don't need the MagiskHide Props Config at all any more. It probably won't hurt anything, but you can just at least disable the module with @Displax' work on the USNF MOD 2.0.
[Google Pixel 7 Pro] slubgob:
So the issue was that I had the files from the factory image of a subfolder of platform tools. Once I moved everything to the same folder, it worked.

Thank you for your patience and help!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting, indeed. Good luck again!

I'm really not good at remembering a list of things that the Android Flash Tool fixed. I don't remember even for myself what exactly the issue was. It wasn't always the same issue for everyone, but there were likely a few at least who each had the same weird issues as each other.

All of the issues were of the type in general that start out "Well this is strange" or "I don't understand why this keeps happening". You get the idea. Sorry I can't be more specific. For myself, it was at least five to nine or more months ago. In all of these particular reported cases, using the Android Flash Tool solved the issue. Obviously, it's not a miracle worker, but there's something different about it than using the factory image.
[Google Pixel 7 Pro] NepoRood:
The flash tool is the same as using fastboot to flash the factory images, only difference is it uses WebUSB (to flash images using fastboot) The online tool helps to prevent "user error", you just plug in the device and follow the prompts

Edit: there is more to it than that, lol, that's just a "basic" explanation