yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7 Pro] roirraW "edor" ehT:
Try with 33.03 and without wiping first.

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

Optional steps when updating - flashing custom kernels

(expand the quote)
[Google Pixel 7 Pro] bird333:
Thanks!
[Google Pixel 7 Pro] roirraW "edor" ehT:
You're welcome!

Note that I named the wrong section, but the link does take you to the correct section, which is called:

Optional steps when updating - flashing custom kernels

Edited the post above, too.
[Google Pixel 7 Pro] xdagee:
I am getting this error -

FAILED (Sparse file is too large or invalid)

- when i typed the fash-all.bat command.

I have the latest platform tools, the bootloader unlocked, and I have followed all the processes.
[Google Pixel 7 Pro] Lughnasadh:
As stated above several times, use 33.0.3 and not the latest Platform Tools.
[Google Pixel 7 Pro] xdagee:
finally, was in a panick mode for a sec.
[Google Pixel 7 Pro] Markeee:
Can I sideload from beta to stable March if my bootloader is still locked without a wipe ?
[Google Pixel 7 Pro] biggiesmalls657:
Why would you ask for trouble?
[Google Pixel 7 Pro] Markeee:
I don't want to ask for trouble and definitely don't feel like getting wiped and going through a clean install was just wondering if you can do it or not
[Google Pixel 7 Pro] rage302:
Updated my P7P successful to stable March and VoWIFI (3 AT) is working now unexpectedly 😊.

greetings rage
[Google Pixel 7 Pro] old_fart:
Not having any luck with update. I am on the 'platform-tools_r33.0.3-windows' like I have been for many months. The integrity checker 'adb devices' works fine and shows my device and not nothing. My stopper / killer is that the 'Flash-all.bat' doing only one step ( chewing on the first instruction ) and then displays / saying . . . '< waiting for any device >' and then stays there. Well I tried over and over ( like an old fool ) while un-installing and re-installing stuff with no joy or success. Many hours repeating. Then I went to the big ( draconian ) step where I did a factory reset / wipe and then still no change / fix . . .

I know that 'recovery mode' ( side loading ) is an OTA thing and cannot be a path for me because I am rooted. OBTW, the Google One backup did a restore on clean reset / install with the Magisk re-installed later also . . . auto giving me back root like it has done before.

Wish I had twrp and then I would do a real full wipe. What the hell. Do a full nandroid backup and restore from the usb 'c' port. Wow, pixel reset / wipe is actually 'not' full...

So if I turn off and disable Google One and reset / wipe again . . . then I can try a side load ? But I believe I have a nasty glitch / bug. I need to understand and fix the bug.

So, anybody have a suggestion ?

update !

Used this . . .
[Google Pixel 7 Pro] SkylinesHD:
Where do you guys download the march image?

If I look on the factory images site, the latest one is February. Also cleared cache, used different device, browser, VPN.

I just don't get it
[Google Pixel 7 Pro] redukt:
Take a look...
[Google Pixel 7 Pro] ffuser1:
you're entering adb reboot bootloader before you try flash-all.bat, correct? And are you able to get into the bootloader? If not, make sure that you have your device set to file transfer / android auto mode after you plug in the USB cable, then make sure you accept commands from your computer in the pop-up on your phone.

Or you can just restart your phone in bootloader mode and flash-all.bat there. but you have to get into the bootloader

If you're still having issues try a different USB cable
[Google Pixel 7 Pro] SkylinesHD:
Yes, I take many looks and there is nothing..
[Google Pixel 7 Pro] rage302:
...switch the language to english on the top of the page... had the same issue ->

if this doesn't help -> clear your browsers cache or use an incognito tab.
[Google Pixel 7 Pro] SkylinesHD:
Wow, this indeed worked. How is this possible? lol

Thanks
[Google Pixel 7 Pro] Sh0X31:
@roirraW "edor" ehT nope had to wipe but 34.00RC2 is out xD

SDK Platform Tools release notes | Android Studio | Android Developers

Android SDK Platform-Tools is a component for the Android SDK.

developer.android.com
[Google Pixel 7 Pro] nomfway:
Uninstall Pixel Launcher updates from Play Store and install it back.

Pixel Launcher and Wallpapers & Style were crashing for me ever since I updated to March patch (008.C1), cleared cache & data and rebooted several times but no use. Fixed it by reinstalling the app updates.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Full OTA Images for Nexus and Pixel Devices | Google Play services | Google for Developers

developers.google.com

Sounds like good news for you!

RC2 has been listed on that page for a week, give or take, but the download is still the buggy 34.0.1. Also note that the RC2 says 34.0.0 RC2, which seems a step backward since 34.0.1 is available. Either way, none of the currently available 34.x versions will work because it won't enter fastbootD mode.
[Google Pixel 7 Pro] roirraW "edor" ehT:
I know this is too late now, but you can OTA sideload and keep root:

How to install OTA updates and keep root on your Google Pixel phone

Looking for a way to keep root access after OTA updates on your Google Pixel phone? Here's a step-by-step guide on how to do so.

www.xda-developers.com
[Google Pixel 7 Pro] Shabo09:
Didn't work anymore, right?

Someone tested this?
[Google Pixel 7 Pro] roirraW "edor" ehT:
Since I don't use OTAs and I use the full factory image, I didn't read the whole article, but it appears the article is directing users to use the full factory image anyway. I didn't notice anything in the directions that wouldn't work.
[Google Pixel 7 Pro] PremAccort:
i just updated my pixel 7 pro to march, when i try to flash patched magisk file, it says

sending 'init_boot' (8192 KB)...

OKAY [ 0.062s]

writing 'init_boot'...

FAILED

(remote: partition (init_boot) not found)

finished. total time: 0.113s

i tried using all the last 3 platform tools , 33.0.3, 34.0.0 , 34.0.1

any help would be appreciated.
[Google Pixel 7 Pro] boontje3:
thank you very much this totally fix it , never thought it could be so simple and it was pixel launcher cause i used nova launcher
[Google Pixel 7 Pro] Shabo09:
Pixel 7 has to be patched through the boot_init.img, so that's why I thought that. But you're right, full OTA is propably the safest way.
[Google Pixel 7 Pro] Shabo09:
You responded 4 months ago on the article hahahahaha

roirraW "edor" ehT 4 months ago

These instructions are wrong for the Pixel 7 and Pixel 7 Pro. On these new Pixels, it's the init_boot.img which needs patched by Magisk and flashed to the init_boot partition, and therefore also the stock init_boot.img that needs restored in order to unroot.
[Google Pixel 7 Pro] boontje3:
here is youtube tutorial that i follow when update while rooted
[Google Pixel 7 Pro] roirraW "edor" ehT:
Did you kill the adb server in between each time trying a different version of the Platform Tools? 34.x definitely won't work for flashing the update, but it's possible it would work fine for flashing a simple partition, although I'd still stick to 33.0.3 until the whole thing is fixed.

Try a different USB cable, different USB port, and/or reboot the computer. Sometimes switching from USB-A to USB-C ports (or vice-versa) does the trick as well.

You might want to distinguish between the "Full OTA" and the "full factory image" zips, because both exist. Full factory image zip is what I was referring to.

The article has been corrected and mentions the Pixel 7 series' requirement of using the init_boot.img.
[Google Pixel 7 Pro] Shabo09:
My Bad. Misinformed and didn't read wel. But found it funny that you reacted on it.
[Google Pixel 7 Pro] Shabo09:
I have a rooted P7P, but since I'm rooted I cannot find a new update for the phone. Updating OTA and flashing boot_init to inactive boot partition is therefore not possible.
[Google Pixel 7 Pro] xdagee:
great, but on step 3.

Edited Flash-all.bat by removing -w and adding -disable-verity and -disable-verification.

Does it mean that you already had -disable-verity and -disable-verification in your previous update, or is it new? Because i read that having verity and verification disable will require a wipe. asking. wanted to be sure.
[Google Pixel 7 Pro] PremAccort:
so i tried all you said and it didnt work, but i got it patched by using adb and fastboot++ v1.0.8.

so if anyone cant root pixel 7 pro after march update, use this https://xdaforums.com/t/tool-windows-adb-fastboot-february-2023.3944288/
[Google Pixel 7 Pro] old_fart:
Thank you for your input. Please note that I added and updated my midnight, original post of #2095 at 2:38 AM, in the morning. Our posts crossed paths in the blackness of night... So the second add to the midnight post was me telling y'all that it is working and updated, following the youtube video of content creator, Mister 'Explaining Android'... He gets a pat on the back and credit for giving me a fix. On the goog page, https://developers.google.com/android/images#cheetah

I clicked on the link 'flash' instead of the ( one hundred times before ) link of 'download' . . .

So that web update tool worked and updated me without me loosing existing data & root . . .

So, this secondary path of monthly updating is a very big deal and got me out of twelve hours of failure loop. Yaa for youtuber, 'Explaining Android' ! ! ! Bravo Zulu ! ! !

Yes, I still would love to know why my old update method is / was broken . . . In hind site, my best guess is that the phone was corrupted with a glitch. Maybe the phone still is . . . But I am running March now. Maybe the OP can add to his page two . . .
[Google Pixel 7 Pro] old_fart:
.

Thank you for you feedback and I will check it out maybe next month . . .
[Google Pixel 7 Pro] WoKoschekk:
Did u try to change the boot slot back to the non-updated one? That's the usual step when an update fails. If slot A is unbootable -> go back to slot B and vice versa.

that tool uses
[Google Pixel 7 Pro] kornball:
Sorry for my delay in replying. I did not have to do anything, actually. After a couple days, my phone started showing correctly as a P7. Hope yours is working by now!
[Google Pixel 7 Pro] roirraW "edor" ehT:
Yes, the two times you will absolutely be forced to wipe relating to disabling Verity and Verification are:

The very first time you disable them.

or

If you've disabled them previously, but you've since flashed an update without disabling them AND have also booted the phone.

You mean this that I already have? :)

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

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

TL;DR - for the seasoned repeat users

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

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

If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).

2. If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:

Deselect Wipe

Deselect Force Flash all partitions (which will also wipe)

Deselect re-lock bootloader

and also in:

Post #3 - Other, most important resources:

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)
[Google Pixel 7 Pro] kornball:
I just updated to the March P7 factory images and am currently using USNF 2.3.1 modded by Displax. Can anyone comment on whether 2.4.0 from kdrag0n or Displax's 2.4.0 MOD_1.2 provides better functionality nowadays? Apologies in advance, I have not followed the development/differentiation of these two mods.
[Google Pixel 7 Pro] old_fart:
.

Yes, thank you. I see it now hiding in plain site. Maybe because it does not mention the fork in instruction path ? Maybe because it does not say its ( bam ) the Chrome browser marshalling the adb platform executables to do it now now now... For me, it tossed up a very confusing circle blob. I had to ask myself 'why is this doing nothing circle here and why did it not start some action up ?

Well there were two somethings in the way of firing up. My web blocker 'Ublock Origin' was blocking and had to be toggled off for this webpage / site. Then also there was a small nondescript ( + ) message and toggle on the right side of the browser page bar, asking me to give Chrome permission to use the installed platform tools. My two cents . . . I think clicking on 'flash' it immediately is a whole lot nicer that the 'download' link . . .
[Google Pixel 7 Pro] roirraW "edor" ehT:
You should be using the latest from @Displax Universal SafetyNet Fix Mod on XDA, which is newer than the Official Universal SafetyNet Fix released by @kdrag0n available at XDA. I think there were some issues for some users starting with the February update that made the official USNF 2.4.0 not work as completely again.

Anyone correct me if I'm wrong.

You're welcome! That's why I hesitate to put anything more in the instructions than there is already, since there's already just so much, it's easy to overlook something.

It's good to have choices!
[Google Pixel 7 Pro] thereason00:
It's not :D It's been saying it's a Nexus 6P since at least November, but I resolved the issue I was having that I though was being caused by it reporting to apps as a Nexus 6P, so I'm not as concerned about it right this second. Just hoping it doesn't cause issues down the line.
[Google Pixel 7 Pro] roirraW "edor" ehT:
@Lughnasadh, as always, you're 100% correct. I flashed the March update including the Magisk'd init_boot.img to both slots, booted the slot it landed on, noted what slot that was, switched slots, fastboot reboot -ed, then the phone proceeded to attempt to boot four times before it indeed just reverted to the slot that was working after the update (which still worked).

So, flashing the full firmware to both slots seems useless, although having the updated bootloader at least, might save bacon again if Google does anything like they did with Android 12->13 without taking into account users might have the old bootloader on the alternate slot.

What a kerfuffle, and Holy Hand Grenades of Antioch! :)
[Google Pixel 7 Pro] kornball:
Thanks for clarifying! I assume it's safe to merely install on top of the previous version I have?
[Google Pixel 7 Pro] roirraW "edor" ehT:
:) You're welcome!

Displax' OP:
[Google Pixel 7 Pro] xunholyx:
There is no WINDTRE in Canada. There was Wind Mobile, but it was bought by Shaw Communications in 2016 and had it's name changed to Freedom Mobile. Also, it's a discount carrier. That's a European ad maybe from years ago. I don't know what WINDTRE is. It's never been in Canada afaik.

The major carriers here are Telus, Bell, and Rogers. Plus there are several discount carriers, some owned by the major ones.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Thanks! From what I can tell, WindTre is an Italian carrier.

Wind Tre - Wikipedia

en.wikipedia.org
[Google Pixel 7 Pro] bird333:
What happened with the 12 > 13 transition? Bootloop?
[Google Pixel 7 Pro] LLStarks:
Google Pixel 8 Pro gets revealed in newly leaked renders

It looks like the Google Pixel 8 Pro has leaked, giving us a excellent look at its exterior.

www.xda-developers.com

Flat.
[Google Pixel 7 Pro] krkhaha:
When I check Google website there is February update. There is nothing about march. Why I can't see that update

Screenshot-20230314-225624 hosted at ImgBB

Image Screenshot-20230314-225624 hosted in ImgBB

ibb.co
[Google Pixel 7 Pro] roirraW "edor" ehT:
On the Pixel 6 Pro, when Android 13 came out, they made it so that you would not be able to downgrade the bootloader. They don't do this often, and this might've even been the first time they've ever done that on a Pixel. When you upgraded to Android 13 and still had the Android 12 bootloader on the alternative slot, if Android 13 wouldn't boot for any reason, it would try to boot the other slot, which would hard brick it, and I do mean hard with absolutely no way to fix it without sending it back to Google.

Awesome! The curves on the 6 Pro bothered me a lot more than they do on this 7 Pro.

See below (from the page before this one):
[Google Pixel 7 Pro] laser03251:
Hello,

I am trying to unlock my bootloader and seem to be running into difficulty. I have successfully updated USB and fastboot drivers, my computer recognizes my device when I run both adb devices and fastboot devices (when in fastboot mode). However when I run the final command fastboot flashing unlock.. instead of something changing on my phones screen.. I get the following set of instructions in my powershell window (see attached image). If i try and toggle through the available commands using the volume buttons, there is no option for unlocking bootloader. Any tips / advice would be greatly appreciated!

Thanks!
[Google Pixel 7 Pro] Lughnasadh:
Assuming you have enabled OEM unlocking in Developer Options, try this:

-Use Command Prompt instead of PowerShell

-Use Platform Tools v. 33.0.3

-Use an A to C cable with USB 2.0 port
[Google Pixel 7 Pro] cmh714:
Well to start, it looks like a very old version of platform tools, so I'd start with an update of that first....
[Google Pixel 7 Pro] madmuthertrucker:
I would try what he said to the letter, older version and all. It can't hurt.
[Google Pixel 7 Pro] cmh714:
The platform tools from google are broken atm, so see this link for the last working version....https://xdaforums.com/t/guide-root-pixel-7-pro-with-magisk-unlock-bootloader-pass-safetynet-more.4505353/page-16#post-88261723
[Google Pixel 7 Pro] simplepinoi177:
To clarify a bit, platform tools v34 and v34.0.1 and v34 RC2 seem to be having problems with rebooting to fastbootd when running the flash-all; I've only read about the issue so I could be incomplete and there is more to it. But I believe those who have used r34 for flashing magisk patched .img files and such have been successful, so I'm inclined to think that using the most up-to-date for running the fastboot command to unlock the bootloader should be fine as it doesn't really require any kind of rebooting or booting into a specific mode (outside of rebooting after unlocking using the volume keys).

But I would say do this ^ . Powershell has always been iffy -- I'm unfamiliar with using it but supposedly you have to run commands with a "./" (at least in certain cases) so maybe that is what's missing -- (although you can supposedly try typing "cmd" as your first command in the powershell and it's supposed to run like cmd, but I wouldn't be too sure if it'll run without any hitches like running it straight from CMD) where CMD foregoes a lot of headaches powershell randomly puts up. And it usually doesn't make sense, but using a USB-A cord resolves random issues really frequently.
[Google Pixel 7 Pro] roirraW "edor" ehT:
Also in the OP with links directly from Google.
[Google Pixel 7 Pro] laser03251:
Thank you all for getting back to me. So I downloaded platform tools 33.0.3 and then did shift right click to open a command prompt from that address. Not sure why it's blue instead of black like traditional cmd. Will say that I also did regular cmd prompt from start menu with same steps and running that final command resulted in that same menu list of options without anything appearing on phone screen. I can definitely try a different USB cable and report back.
[Google Pixel 7 Pro] Lughnasadh:
Open your Platform Tools folder and in the address bar type "cmd" (without the ""). That will open up the command prompt directly from your Platform Tools folder. Then try again. If that doesn't work, definitely try different cables ports as mentioned above.
[Google Pixel 7 Pro] Dave_247:
Some minor good news regarding the platform tools bug, it seems someone from Google finally responded that they are aware of the issue and working on a fix. Maybe in 34.0.2 it will work. 😅

Google Issue Tracker

issuetracker.google.com
[Google Pixel 7 Pro] Lughnasadh:
Google concerning Platform Tools bug:

"Thanks, we've identified the root cause of this issue and are working on a fix."

Edit: Ninja'd 😅

Google Issue Tracker

issuetracker.google.com
[Google Pixel 7 Pro] simplepinoi177:
I'm inclined to believe that @laser03251 isn't "calling" from the wrong platform-tools folder (because he was able to "fastboot devices" successfully) or running the wrong command prompt (vs. powershell, because he stated running it from the Start menu)...

but anything's worth a try at this point...

This has got to be the first time I've seen the funky usb cable hiccup happening on the "flashing unlock" command...😕

*UPDATE -- laser03251 needs to update platform tools; I just looked back to his original post I realized when he stated he had "successfully updated...fastboot...", I jumped the gun and assumed he meant platform tools, but what he said exactly was "I have successfully updated USB and fastboot

drivers

"...not the same as updated platform-tools/fastboot.exe...
[Google Pixel 7 Pro] WoKoschekk:
Fastboot shows the help text in your screenshot. That's how to use the tool "fastboot". You see the syntax of all options and their arguments.

Your version of fastboot is older than Android 6. The ability to use flashing unlock was introduced with the initial release of Android 6.0.0 (r1). https://android.googlesource.com/platform/system/core/+/a873e1dc0280f5d21384ec03ba812f4336c5dec5^!/

The help text of fastboot since Android 6:

"usage: fastboot [ <option> ] <command>\n"
"\n"
"commands:\n"
" update <filename> reflash device from update.zip\n"
" flashall flash boot, system, vendor and if found,\n"
" recovery\n"
" flash <partition> [ <filename> ] write a file to a flash partition\n"
" flashing lock locks the device. Prevents flashing"
" partitions\n"
" flashing unlock unlocks the device. Allows user to"
" flash any partition except the ones"
" that are related to bootloader\n"
" flashing lock_critical Prevents flashing bootloader related"
" partitions\n"
" flashing unlock_critical Enables flashing bootloader related"
" partitions\n"
" flashing get_unlock_ability Queries bootloader to see if the"
" device is unlocked\n"
" erase <partition> erase a flash partition\n"
" format[:[<fs type>][:[<size>]] <partition> format a flash partition.\n"
" Can override the fs type and/or\n"
" size the bootloader reports.\n"
" getvar <variable> display a bootloader variable\n"
" boot <kernel> [ <ramdisk> ] download and boot kernel\n"
" flash:raw boot <kernel> [ <ramdisk> ] create bootimage and flash it\n"
" devices list all connected devices\n"
" continue continue with autoboot\n"
" reboot [bootloader] reboot device, optionally into bootloader\n"
" reboot-bootloader reboot device into bootloader\n"
" help show this help message\n"
"\n"
"options:\n"
" -w erase userdata and cache (and format\n"
" if supported by partition type)\n"
" -u do not first erase partition before\n"
" formatting\n"
" -s <specific device> specify device serial number\n"
" or path to device port\n"
" -l with \"devices\", lists device paths\n"
" -p <product> specify product name\n"
" -c <cmdline> override kernel commandline\n"
" -i <vendor id> specify a custom USB vendor id\n"
" -b <base_addr> specify a custom kernel base address.\n"
" default: 0x10000000\n"
" -n <page size> specify the nand page size.\n"
" default: 2048\n"
" -S <size>[K|M|G] automatically sparse files greater\n"
" than size. 0 to disable\n"

As you can see in your screenshot your fastboot version does not support flashing unlock and that's why the command fails and shows the help text.
[Google Pixel 7 Pro] supermansaga:
I gotta say this Youtube video rocks. I am able to update to March stable build as well and keeping root while using Magis 25209.
[Google Pixel 7 Pro] laser03251:
Any chance you can provide a link to the correct platform tools? I used 33.03 but I may be mistaken! Thank you all again for your help
[Google Pixel 7 Pro] laser03251:
Can you point me in the right direction to the correct / updated fastboot? I believe this is related to platforms sdk and I am pretty sure I downloaded 33.03 version. Thank you all again for your help!