yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] badabing2003:
https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip - Windows

https://dl.google.com/android/repository/platform-tools_r33.0.3-darwin.zip - Mac

https://dl.google.com/android/repository/platform-tools_r33.0.3-linux.zip - Linux
[Google Pixel 7 Pro] laser03251:
Will try this when I get home from work today. And do you recommend opening the cmd prompt window from inside the extracted folder?
[Google Pixel 7 Pro] V0latyle:
That's the easiest way, yes. ADB only works if PATH is the platform tools folder.
[Google Pixel 7 Pro] V0latyle:
There's a bug in their bug report...

"imporper"
[Google Pixel 7 Pro] roirraW "edor" ehT:
Regarding blue command prompt versus black. PowerShell opens blue, so maybe you were in PowerShell instead.

FYI, the links to the 33.0.3 Platform-Tools are also in the OP.

And as @V0latyle said, that's the way I do it. I make sure that ADB is not listed in Task Manager and if so, kill it, as it could be an old version running from previously, extract the Platform-Tools, and open a Command Prompt from within that folder. I don't fool with PowerShell.
[Google Pixel 7 Pro] madmuthertrucker:
I have been using Powershell. It's blue alright. I didn't know that other way until @Lughnasadh mentioned it.
[Google Pixel 7 Pro] WoKoschekk:
Download and extract v33.0.3 => open the extracted folder called ~\platform-tools=> inside your Explorer window: type cmd in the address bar and hit Enter => ADB/Fastboot is ready

Here are two commands for testing:

### list all options to see if 'flashing unlock' is available:
fastboot -h

### check the version of fastboot:
fastboot --version
[Google Pixel 7 Pro] laser03251:
Will try this when I get home and report back! Thank you
[Google Pixel 7 Pro] humb13:
Yesterday I tried updating my phone to the March edition of the image files Google makes available. As you know it's a simple matter of unzipping the files into the platform tools folder and running flash-all.bat after removing the -w (wipe). It's not the first time I've done this and I've never had an issue -- until now.

Sadly I wasn't aware of the fact that 34.0.1 was buggy. I ran it and it bricked my phone. Worst of all, it was a hard brick, the phone is dead and won't boot up or respond to any commands. Google wasn't very helpful so I dropped it off at UbreakIFix to see if they could bring it back to life. I ordered another refurbished phone from Amazon to replace this one if they can't fix it. Oh well.. shiit happens.

Bottom line: Stay away from 34.01 like the plague!! After quite a bit of effort I found of copy of 33.0.3 -- sadly it's too late, the damage is done :(
[Google Pixel 7 Pro] laser03251:
It worked!!! thank you all for your help. Now on to rooting
[Google Pixel 7 Pro] supermansaga:
Is it possible that the Google Play Systems version still remains in February when the rest has moved onto March? Thx. If so, how could I manually update it these days? Would I have to reroot solely for it?

Google Play system update for March 2023 includes new Wallet features, performance optimizations, and more

And a little something for loyalty card fans

www.xda-developers.com
[Google Pixel 7 Pro] No.9527:
Does anybody can't pass safetynet & slay Intergrity check after TQ2A.230305.008.C1 update?

I have root the new update and everything work perfect except device certification, can't use G wallet and can't find Netflix, no matter use Magisk or Magisk delta via Zygisk with module shamiko, USNF(mod), it's all the same.
[Google Pixel 7 Pro] WoKoschekk:
Following your link, I found an answer in the 2. sentence:
[Google Pixel 7 Pro] terlynn4:
It's working for me with magisk stable, but it was a bit of a pain this time. After hiding magisk, zygisk, denylist, USNF-mod, I also had to go into app settings and clear data for several google apps: Play Store, Play Services, and Google Framework (I think that's all?). Then reboot again and I was able to pass safetynet, use Wallet, etc.
[Google Pixel 7 Pro] WoKoschekk:
The known bug in v34.0.0 can't hard brick your device. This version is only skipping boot into fastbootd when flashing dynamic partitions. But your bootloader is still intact and should boot into bootloader menu. At this point you should be able to flash a new firmware.

Your phone is powered off and display remains black when pressing power? Did u try to hold the power button for at least 30-40 sec.? What happens when charging it?
[Google Pixel 7 Pro] anthonnyb98:
Hello, I am having this error when trying to flash the init_boot, could you help me to know why?

PS C:\Users\antho\Desktop\Pixel 7 Pro\platform-tools> fastboot flash init_boot "C:\Users\antho\Desktop\Pixel 7 Pro\platform-tools\magisk_patched-25200_4F9Ey.img"

target reported max download size of 261095424 bytes

sending 'init_boot' (8192 KB)...

OKAY [ 0.197s]

writing 'init_boot'...

FAILED (remote: partition (init_boot) not found)

finished. total time: 0.208s
[Google Pixel 7 Pro] supermansaga:
But it's already released
[Google Pixel 7 Pro] JakeDHS07:
Released and exists yes. But as usual with Google it's a staged rollout and unlike the monthly updates there's no way to proper sideload those yet so we have to either wait for it to be pushed to us or keep attempting to pull it until eventually it works. Hopefully some day they add the sideload for those that don't want to wait.
[Google Pixel 7 Pro] No.9527:
I've tried all the steps, still the same, thanks anyway.
[Google Pixel 7 Pro] simplepinoi177:
You might want to try CMD (Command Prompt) vs. PowerShell...

And of course the obligatory make sure you use the latest up-to-date (working without bugs) r33.0.3 platform-tools and USB-A cord works best...

Hope this helps and works out for you...
[Google Pixel 7 Pro] simplepinoi177:
EVERY SINGLE time I have issues with SafetyNet not passing or issues with Wallet, I do the above ^^ and it works...

The last time I had issues, I learned that if you don't reboot, it all won't apply until after...that and finding out clearing data for Play Services or Framework removes the cards in Wallet, not clearing data for Wallet!

The only time it may not have worked was when the original non-Displax-mod was used and it had its issues...

Are you using Magisk canary or stable Magisk?
[Google Pixel 7 Pro] supermansaga:
USB-C also works which is one of the reasons I switched from iphone 14 to P7P
[Google Pixel 7 Pro] simplepinoi177:
True....most of the times...

But if you ever have random issues where nothing seems to troubleshoot & fix it, ask any veteran of Pixels here; changing to USB-A 2.0 cords would end up doing the trick very randomly without any clear reason why!🤯
[Google Pixel 7 Pro] WoKoschekk:
And you have it already installed with the current security patch for March.

Visit https://source.android.com/docs/security/bulletin/asb-overview

and you'll see that the CVEs (Common Vulnerabilities and Exposures) under "Google Play system updates"

are also included in the security patch for March '23:
[Google Pixel 7 Pro] No.9527:
I've re-flash-all to both slots and re-root again, atfer clean G Apps（services） Data & Cache, It's still fail to certificate. T_T

All Bank or payment apps work perfectly with Shamiko (or enforce Denylist) + HMA , I would like to uninstall Lsposed and try again.
[Google Pixel 7 Pro] Schroeder09:
Anyone notice anything new or different performance-wise on the march update? There was a note in the change log from Google about optimizing battery performance in "certain situations" or something like that. I was hoping to see a 2-5% increase in battery life. I don't see anything. I was holding my breath. I don't remember an update *ever* noticeably increasing battery life. They only ever make it tank.

Anyone experience anything notable on the battery life front?
[Google Pixel 7 Pro] anthonnyb98:
Thanks for answering, my solution was to change init_boot to a more specific command, init_boot_b and now it works normally.
[Google Pixel 7 Pro] xunholyx:
It's blue instead of black because on recent releases of Windows it opens PowerShell instead of Command Prompt. It's okay though. You can use PowerShell. For your first command enter "cmd" (without quotation marks of course) and PowerShell will work like command prompt after that.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I'm sorry to hear about what happened.

It sounds like you already dropped the phone off for service, but otherwise, as @WoKoschekk suggests, and I have had to do over the years every great once in a while, sometimes I've just had to let the phone sit for 30 minutes and then plug it in and try it again, but his suggestion of holding the power button down for at least 40 seconds is also a good one.

Did you re-check all the steps in post 2 about SafetyNet? What version of USNF are you using? I didn't have to do anything special, although I didn't bother checking my integrity results using YASNAC and Integrity Checker until just now, and they both pass as usual (besides strong).

That's odd, but glad you got it working!
[Google Pixel 7 Pro] Paz9:
Is that v2.3.1? Mod.
[Google Pixel 7 Pro] roirraW "edor" ehT:
That's the only Mod version I've heard of, so I'm sure it is.
[Google Pixel 7 Pro] Ivixmax:
Hello mate can you say me how to extract init_boot.img of pixel 7 normal version? Thanks in advance
[Google Pixel 7 Pro] bigknowz:
Well done! Is gpay working?
[Google Pixel 7 Pro] 96carboard:
If you supply fastboot with kernel and ramdisk separately, it should still be possible. Fastboot boot has up to 3 parameters;

boot image:
boot KERNEL [RAMDISK [SECOND]]
[Google Pixel 7 Pro] roirraW "edor" ehT:
We can't pass SafetyNet / Basic Integrity, so probably not.
[Google Pixel 7 Pro] AndyYan:
DSU method in #175, or more detailed in separate thread.

Cool, didn't know it's a thing.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Interesting! Thank you. I'll certainly test this out today when we get our two. Or tomorrow if they deliver very late.
[Google Pixel 7 Pro] Ghisy:
Good findings about the init_boot, that's what I read on Telegram earlier today then.

I'm still waiting for the full factory image to do anything. Once I've unlocked the bootloader, I'll reflash the factory image clean. I hope it will include that 73 MB patch that I've seen people getting today.
[Google Pixel 7 Pro] Humpie:
Oops I've overwritten my boot partition instead of init_boot... Anyone have the boot.img too?

https://ota.googlezip.net/packages/ota-api/package/674427f7501c86422e9b502666af8a47cbd3cff7.zip only gives me around 70MB, so I don't think that's the full OTA anymore. At least I cannot dump the payload...
[Google Pixel 7 Pro] AndyYan:
The other thread
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks much to @reaper000 who noticed I put a single instance of "boot_init.img" instead of "init_boot.img" in my instructions. I had it reference the right named file everywhere except the actual steps. LOL!

Cheers @reaper000!
[Google Pixel 7 Pro] dary1zhu:
sorry was wrong about the integrity thing, basic integrity passes but 'MEET_DEVICE_INTEGRITY' in the Play Integrity API Checker app fails. (edited in my original post)
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks!
[Google Pixel 7 Pro] Annie the Eagle:
So currently SafetyNet will pass for basic integrity, but not for Device Integrity? Even with the MOD version that @Displax made? :(
[Google Pixel 7 Pro] dary1zhu:
right, and cts fails as well
[Google Pixel 7 Pro] Annie the Eagle:
Aww, that sucks. Hopefully we won't have to wait weeks for a SafetyNet fix :/
[Google Pixel 7 Pro] mariusnoor:
Can confirm (with modded universal SafetyNet Fix + Magisk Props).

Play Integrity API Checker:

MEETS_DEVICE_INTEGRITY: fail

MEETS_BASIC_INTEGRITY: pass

MEETS_STRONG_INTEGRITY: fail

YASNAC:

Basic integrity: pass

CTS profile match: fail
[Google Pixel 7 Pro] tauio111:
Does Network Signal Guru work on a rooted Pixel 7?

This is a critical tool for direct modem control and cellular (4G/5G) modem data inspection.

And if there is anyone in an "unofficial country", does the 5G enablement trick from the Pixel 6 series work aswell?
[Google Pixel 7 Pro] simplepinoi177:
It's curious, but I've found that specifying the slot is sometimes needed....and I've only seen it needed on people that are using PowerShell....
[Google Pixel 7 Pro] roirraW "edor" ehT:
Very interesting. Thank you!
[Google Pixel 7 Pro] humb13:
Apparently that's exactly what happened. For months I've been using flash-all.bat for the monthly update and never had a problem -- until now. The only difference was I made the mistake of upgrading the platform tools to 34.0.1 without realizing this release is buggy. I'm convinced if I'd stuck with the old 33.1.0 nothing bad would have happened.

When I initiated the process everything went well until it gave me an error message about not enough space (this error is documented) and stopped. Repeating the process didn't work either. Not knowing what to do, I pressed the power button. After that all I could get was the Google logo. The phone then shut off completely. It is totally dead. I've pressed the power button for one full minute, nothing! Pressing the power button together with volume down for a minute didn't help either. Plugging it into the PC didn't help - the PC won't see it. When you plug it into a charger the phone doesn't react at all - no light, no vibration, absolutely no reaction of any kind. It's almost as if someone went in and removed the battery.

When I took it in for possible repair, I explained to the guy that if he so much as managed to boot into the fastboot mode I could do the rest. It goes without saying he couldn't get the phone to start either. I just left it there to see if anyone could come up with a solution.

I've been screwing around with phones for several years. I've soft-bricked quite a few and always managed to bring them back to life. I have never hard-bricked a phone until now. Weird!

In the mean time I had to bite the bullet and replace it. Oh well....
[Google Pixel 7 Pro] simplepinoi177:
same thing happened below to @JJT211...i can't believe a bug in platform-tools/fastboot.exe can cause such a hard brick that it would mess up the mobo that it wouldn't even pull power anymore...!

goes to show how vulnerable the pixels are when I'm fastboot(d) and/or in the middle of flashing!

it does seem that, when r34 inevitably causes an error, if you hard reset or keep attempting, it messes up the mobo irreparably (found in both these cases; but only cases I've seen)...
[Google Pixel 7 Pro] roirraW "edor" ehT:
Well, they finally updated

Pixel Update Bulletins | Android Open Source Project

source.android.com

to list March, although we already had access to it before it was listed there:

Pixel Update Bulletin—March 2023 | Android Open Source Project

source.android.com

Still v1.0, so the document hasn't changed. They do have all the languages listed, and they usually don't, that soon, even if it had come out on the 6th like we had expected.
[Google Pixel 7 Pro] pndwal:
I'm not a Pixel user and this advice may not help, but sometimes when you cannot see Fastboot screen device may still be in Fastboot mode!... So even if blind (black screen), some old tips I posted for other devices may help:

... I put more old tips in this post:

https://xdaforums.com/t/guide-begon...stuck-on-preloader-mode.4000433/post-81723621

Hope some can be used / adapted for bricked Pixels... 🙃 PW
[Google Pixel 7 Pro] xunholyx:
That stuff might work with MTek but it won't work with QC or Tensor. At least as far I've seen. Thanks for the input, but since you've never had a Pixel device or even a Nexus device (afaik) you should probably stay in your lane. No offense indeed. It's just that you have very limited knowledge with what's going on here.
[Google Pixel 7 Pro] pndwal:
Actually working fastboot with blackscreen can occur on QC... I had this also on Huawei Ascend Y550.

It occurred to me the possibility may not have been explored ... and I did write (in bold) "this advice may not help", but whatever... PW
[Google Pixel 7 Pro] simplepinoi177:
this might be.... but after reading his instructions (here and there post he linked), it made me sore for removable batteries 😅😢😩

-for those who don't want to read, many of his instructions instruct doing that in the first step...

R.I.P. Motorola Droid, Droid 3, and Galaxy S5...
[Google Pixel 7 Pro] WoKoschekk:
I can confirm it. The same happend with Moto G6+, SDM630:

https://xdaforums.com/t/moto-g6-plus-black-screen.4421285/

https://xdaforums.com/t/cant-see-blackscreen-only-in-fastboot-mode.4544765/
[Google Pixel 7 Pro] WoKoschekk:
In theory it's impossible to brick the device due to a failed flashing attempt in fastbootd mode. The firmware of a Pixel device consists of two separate packages:

1. bootloader/radio images

2. firmware images (image***.zip)

While the firmware images being flashed in fastbootd mode, the bootloader is first flashed in bootloader mode. So, after getting the error message with v34.0.0 the updated bootloader is valid and should be able to boot the device into fastboot menu.

Aside from that the Pixel is an A/B device and in case of an unbootable slot it should fallback to the non-updated slot.

Why are some devices only boot looping and a few others are hard bricked?

What about EDL? Does the new Titan M2 support a similar function?
[Google Pixel 7 Pro] amders:
@roirraW "edor" ehT have you update to march? and what version of fastboot do you use?

does update method on post #2 safe to execute?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes.

33.0.3

Yes.

:)
[Google Pixel 7 Pro] amders:
done... but i lose volte.. using magisk module T-T
[Google Pixel 7 Pro] roirraW "edor" ehT:
I don't have any experience with VOLTE. I haven't paid any attention to whether I can use it or not. Hopefully, someone else can help you with it.
[Google Pixel 7 Pro] powershift:
I'm trying to root using magisk and found that boot.img is not what I want to use and that I need init_boot.img. That file is not in the download for tq2a.230305.008.c1. Where do I get init_boot.img?

anon@dev:~/android/platform-tools$ ls ../builds/Pixel7Pro/bramble-tq2a.230305.008.c1/
total 6.8G
drwxr-x--- 2 anon anon 4.0K Mar 18 15:10 .
drwxr-xr-x 3 anon anon 4.0K Mar 18 15:02 ..
-rw-r--r-- 1 anon anon 123 Dec 31 2008 android-info.txt
-rw-r--r-- 1 anon anon 96M Dec 31 2008 boot.img
-rw-r----- 1 anon anon 8.6M Mar 3 16:04 bootloader-bramble-b5-0.5-9430388.img
-rw-r--r-- 1 anon anon 16M Dec 31 2008 dtbo.img
-rw-r----- 1 anon anon 997 Mar 3 16:04 flash-all.bat
-rwxr-x--x 1 anon anon 1.1K Mar 3 16:04 flash-all.sh
-rwxr-x--x 1 anon anon 1.1K Mar 3 16:04 flash-base.sh
-rw-r----- 1 anon anon 2.2G Mar 3 16:04 image-bramble-tq2a.230305.008.c1.zip
-rw-r--r-- 1 anon anon 2.4G Dec 31 2008 product.img
-rw-r----- 1 anon anon 147M Mar 3 16:04 radio-bramble-g7250-00247.1-230113-b-9488784.img
-rw-r--r-- 1 anon anon 4.9K Dec 31 2008 super_empty.img
-rw-r--r-- 1 anon anon 360M Dec 31 2008 system_ext.img
-rw-r--r-- 1 anon anon 817M Dec 31 2008 system.img
-rw-r--r-- 1 anon anon 26M Dec 31 2008 system_other.img
-rw-r--r-- 1 anon anon 8.0K Dec 31 2008 vbmeta.img
-rw-r--r-- 1 anon anon 4.0K Dec 31 2008 vbmeta_system.img
-rw-r--r-- 1 anon anon 96M Dec 31 2008 vendor_boot.img
-rw-r--r-- 1 anon anon 728M Dec 31 2008 vendor.img
anon@dev:~/android/platform-tools$
[Google Pixel 7 Pro] WoKoschekk:
Unpack the zip file.
[Google Pixel 7 Pro] powershift:
It was unpacked, but for clarity here is the contents:

anon@dev:~/android/platform-tools$ ls ../builds/Pixel7Pro/bramble-tq2a.230305.008.c1/unpack/
total 4.5G
drwxr-xr-x 2 anon anon 4.0K Mar 18 17:35 .
drwxr-x--- 3 anon anon 4.0K Mar 18 17:35 ..
-rw-r--r-- 1 anon anon 123 Dec 31 2008 android-info.txt
-rw-r--r-- 1 anon anon 96M Dec 31 2008 boot.img
-rw-r--r-- 1 anon anon 16M Dec 31 2008 dtbo.img
-rw-r--r-- 1 anon anon 2.4G Dec 31 2008 product.img
-rw-r--r-- 1 anon anon 4.9K Dec 31 2008 super_empty.img
-rw-r--r-- 1 anon anon 360M Dec 31 2008 system_ext.img
-rw-r--r-- 1 anon anon 817M Dec 31 2008 system.img
-rw-r--r-- 1 anon anon 26M Dec 31 2008 system_other.img
-rw-r--r-- 1 anon anon 8.0K Dec 31 2008 vbmeta.img
-rw-r--r-- 1 anon anon 4.0K Dec 31 2008 vbmeta_system.img
-rw-r--r-- 1 anon anon 96M Dec 31 2008 vendor_boot.img
-rw-r--r-- 1 anon anon 728M Dec 31 2008 vendor.img
anon@dev:~/android/platform-tools$
[Google Pixel 7 Pro] Lughnasadh:
That looks like a Pixel 4a 5G firmware.
[Google Pixel 7 Pro] WoKoschekk:
Pixel 7 Pro:

android-info.txt
boot.img
bootloader-cheetah-cloudripper-1.0-9618366.img
dtbo.img
flash-all.bat
flash-all.sh
flash-base.sh
init_boot.img
product.img
pvmfw.img
radio-cheetah-g5300g-221229-230210-b-9589366.img
super_empty.img
system.img
system_dlkm.img
system_ext.img
system_other.img
vbmeta.img
vbmeta_system.img
vbmeta_vendor.img
vendor.img
vendor_boot.img
vendor_dlkm.img
vendor_kernel_boot.img
[Google Pixel 7 Pro] powershift:
What lead you to that conclusion?
[Google Pixel 7 Pro] Lughnasadh:
The first line in the code you posted has bramble-tq2a.230305.008.c1 in it.
[Google Pixel 7 Pro] powershift:
That isn't the build I'm running. What you posted is an unreleased beta version. My phone has the stable version running on it TQ2A.230305.008. I'm confused. If I try using the boot.img with magisk and then doing a test boot with the patched image, the phone doesn't boot and gets stuck at the bootloader screen.
[Google Pixel 7 Pro] powershift:
This is the url I used https://dl.google.com/dl/android/aosp/cheetah-tq2a.230305.008.c1-factory-cefc4e56.zip
[Google Pixel 7 Pro] Lughnasadh:
Official download page...

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

developers.google.com
[Google Pixel 7 Pro] WoKoschekk:
Have a look at your bootloader.img + radio.img. The device's name of a Pixel 7 Pro is "cheeta" and "bramble" (like yours) is the Pixel 4a 5G.
[Google Pixel 7 Pro] powershift:
That page only has over the air updates and the latest update is already flashed to my device. I need the latest build with the init_boot.img, but I'm not seeing it anywhere.
[Google Pixel 7 Pro] WoKoschekk:
The same that I used.

Magisk needs a ramdisk to patch.

/ # magiskboot unpack /sdcard/boot.img
Parsing boot image: [/sdcard/boot.img]
HEADER_VER [4]
KERNEL_SZ [24958429]
RAMDISK_SZ [0]
PAGESIZE [4096]
CMDLINE []
KERNEL_FMT [lz4_legacy]
VBMETA

#####

/ # magiskboot unpack /sdcard/init_boot.img
Parsing boot image: [/sdcard/init_boot.img]
HEADER_VER [4]
KERNEL_SZ [0]
RAMDISK_SZ [2063503]
PAGESIZE [4096]
CMDLINE []
RAMDISK_FMT [lz4_legacy]
VBMETA

As you can see, boot.img has no ramdisk inside (RAMDISK_SZ=0).
[Google Pixel 7 Pro] Lughnasadh:
That page has the factory images on it. Download the factory image and extract the init_boot.img.
[Google Pixel 7 Pro] powershift:
If you used the same download url and it had the init_boot.img when you downloaded it, then they changed the release because it isn't there anymore.
[Google Pixel 7 Pro] Lughnasadh:
Yep. All devices released with Android 13 had the generic ramdisk moved from the boot.img to the init_boot.img.
[Google Pixel 7 Pro] powershift:
I didn't see the acknowledge button. After clicking that I see the build and I'm dl'ing it now. Thanks.
[Google Pixel 7 Pro] powershift:
I didn't see the acknowledge button at first. I downloaded the build from that page and it had the init_boot.img in it. The bad link is on the xda-developers blog https://www.xda-developers.com/how-to-download-android-13/
[Google Pixel 7 Pro] Lughnasadh:
Yeah, always download from the official download page.