How To Guide Platform-Tools v34.0.3 has a different bug - May 1, 2023 TQ2A.230505.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
- Thread starter roirraW "edor" ehT
- Start date
-
- Tags
- bootloader pixel 7 pixel 7 pro root
Also looks like the new version flashes everything as part of the Super partition.
A good deal faster tbh.
A good deal faster tbh.
Okay, I was wrong. Just tried to update my Pixel 6 Pro to A14 Beta 2.1 using Platform Tools 34.0.3. Opened up command line from the Platform Tools folder and ran flash-all.bat and got the
ANDROID_PRODUCT_OUT error. Grrrr...33.0.3 worked fine, btw.
Thanks, and +1'd it. Interesting about being noticeably faster.
Thanks for the report.
In other, albeit unimportant, news - on the following page:
Android Beta Program
Android Beta Program allows you to enroll your Android device for beta releases.
Sometimes it says Android Devices, sometimes Android Phones, and sometimes, like in that example above, "Android Android Devices". It makes the same exact changes for that and another FAQ entry on that page. Occasionally, there's a 12 or 24-hour lull in changes, and then suddenly they change back and forth between the various available wording options multiple times in an hour or so.
I have to wonder what is going on behind the scenes when this happens. I'm sure two Google employees aren't actually trying to exert their preference over each other. Weird!
I just got a factory unlocked Pixel 7 Pro. I unlocked the Bootloader, used Magisk to patch init_boot.img but had problems with flash-all.bat script.
Here is the output when it went off the rails
And now it's in a boot loop.
I am able to get back to Fastboot Mode (and to Recovery Mode)
1) Can anyone help me recover from this boot loop?
2) Anyone recognize what might have gone wrong?
Here is the output when it went off the rails
Code:
...
extracting product.img (2857 MB) to disk... took 12.380s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.010s]
Sending sparse 'product_b' 1/12 (262112 KB) OKAY [ 6.721s]
Writing 'product_b' OKAY [ 0.402s]
Sending sparse 'product_b' 2/12 (262124 KB) OKAY [ 6.758s]
Writing 'product_b' OKAY [ 0.404s]
Sending sparse 'product_b' 3/12 (262128 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
Press any key to exit...And now it's in a boot loop.
I am able to get back to Fastboot Mode (and to Recovery Mode)
1) Can anyone help me recover from this boot loop?
2) Anyone recognize what might have gone wrong?
What version of Platform-Tools are you using? If on any 34.x version, then the easiest solution is to go back to v33.0.3:
Technically, 34.0.3 also works (whereas 34.0.0 and 34.0.1 are very broken), but 34.0.3 may require you to jump through some hoops to work correctly, whereas 33.0.3 will just work as is.
Just be back in bootloader (fastboot) mode and start the flash-all.bat back from scratch.
Cheers and good luck! Let us know how things go.
Edit: Otherwise, if that doesn't solve it, then different USB cable and different USB port, or even rebooting the computer is worth trying.
Yes you can get out of it, it failed in the middle of flashing, all you have to do is flash again to a successful end.
Why did it fail you might ask,
- Make sure the downloaded firmware's checksum matches what is published.
- It could be communication issue
- Try another cable
- Try another USB port, preferably USB2
- Makes sure the drivers are up to date.
aer0zer0
Recognized Contributor
I ended up buying a faster cable. The c -> c cable provided by Google just stopped working for these newer 14 builds. I got a the USB 4 cable from Spigen, and these new images bats started flashing properly again.
That's my best guess.
That's my best guess.
Yes, you're correct; I previously did have that problem, but have since corrected it. It was not the culprit here.
Since I could easily get into fastboot (bootloader), I was able to just try it again.
I did use a different cable (Anker this time, my "good")
It did work. For both slot-a, and then slot-b.
Whether the previous cable/usb port was to blame, I'll never know.
Thanks as always for your help, y'all!
It's just incredible to me that
our phones shoot 10's of GBs of HDR+ 10-bit 4kp60 video
and still... a very common and accurate troubleshooting tip is
"try a different cord"
our phones shoot 10's of GBs of HDR+ 10-bit 4kp60 video
and still... a very common and accurate troubleshooting tip is
"try a different cord"
Were you using the black or the white Google cable?
aer0zer0
Recognized Contributor
The white c -> c that Google provided. Bought the black USB 4 c -> c from Spigen.
Another issue with PT 24.x.x found by me... 
"fastboot cannot work when %username% in Windows OS contains non latin characters"
Already created issue: https://issuetracker.google.com/issues/284450364
But do not be surprised at such a large number of errors, since Google massively rewrites fastboot
"fastboot cannot work when %username% in Windows OS contains non latin characters"
Already created issue: https://issuetracker.google.com/issues/284450364
But do not be surprised at such a large number of errors, since Google massively rewrites fastboot
And another one... 
issuetracker.google.com
fastboot failed to format partitions or running "fastboot -w" on some devices
Google Issue Tracker
fastboot failed to format partitions or running "fastboot -w" on some devices
Thanks for sharing! That issue tracker page https://issuetracker.google.com/issues/284450364 shows up blank (but perpetually "loading", while saying "Access denied" at the bottom. Your other link for the other issue works for me fine, and I've +1'd it.Another issue with PT 24.x.x found by me...
"fastboot cannot work when %username% in Windows OS contains non latin characters"
Already created issue: https://issuetracker.google.com/issues/284450364
But do not be surprised at such a large number of errors, since Google massively rewrites fastboot
Looks like broken link. Fixed.
For what it's worth, the first link https://issuetracker.google.com/issues/284450364 still doesn't work, even if I try it through a VPN without a Google account. Still says "Access denied".
Second link https://issuetracker.google.com/issues/284335462 works fine.
Strange things... Now even i can't access my own issue. Maybe time to report issue about Google issue trackerFor what it's worth, the first link https://issuetracker.google.com/issues/284450364 still doesn't work, even if I try it through a VPN without a Google account. Still says "Access denied".
Second link https://issuetracker.google.com/issues/284335462 works fine.
Top Liked Posts
-
1
Pending to merge: https://android-review.googlesource.com/c/platform/system/core/+/2613189Another issue with PT 24.x.x found by me...
"fastboot cannot work when %username% in Windows OS contains non latin characters"
Already created issue: https://issuetracker.google.com/issues/284450364
But do not be surprised at such a large number of errors, since Google massively rewrites fastboot -
6
For what it's worth, Mishaal Rahman said he tested it and the problem has been fixed.55
LOL! Nice.
LOL!!You're welcome! I have no idea if this is a feature or a bug, and I'm guessing Google doesn't either
Just for reference (but I recommend still sticking to @badabing2003's advice), on Windows, you:
- Right-click the start button
- Choose System from the pop-up menu
- Over on the FAR right, choose "Advanced system settings". Instead of steps 1 & 2, you can also click (left) on the start button and start typing Advanced system settings, and eventually you'll see "View advanced system settings", and click on that.
- Click on "Environment Variables" at the bottom on the default Advanced tab at the top.
- Under the bottom "System variables" section, click "New".
- For Variable name, put in:
-
Code:
ANDROID_PRODUCT_OUT
-
- For Variable value, put in the full path to your platform-tools folder. For example:
-
Code:
S:\platform-tools\
-
5Comparison of old and new 34.0.1 (utilities version changes)
Old:
ADB: 1.0.41 (34.0.1-9680074)
Fastboot: 34.0.1-9680074
Make_f2fs (casefold): 1.15.0 (2022-05-20)
Mke2fs: 1.46.6 (1-Feb-2023)
New:
ADB: 1.0.41 (34.0.1-9979309)
Fastboot: 34.0.1-9979309
Make_f2fs (casefold): 1.16.0 (2023-04-11)
Mke2fs: 1.46.6 (1-Feb-2023) -
60Pixel 7 Pro [Cheetah]
Updated May 13, 2023
Note that more than three users have said that 34.0.1 (even May 10, 2023's binary update of 34.0.1) did not work correctly for them. I recommend sticking with 33.0.3 (just below these quotes)
Someone reported it to Google (added a comment about 34.0.1 to the existing 34.0.0 report).
The download links for 33.0.3:
Factory Images for Nexus and Pixel Devices | Google Play services | Google Developers
developers.google.com
Google Pixel Update
Android Security Bulletins | Android Open Source Project
source.android.com
Here there be dragons.
I am not responsible for anything at all. 
VERY IMPORTANT - On the Pixel 7/Pro, we use Magisk to patch
Thanks to @edcsxz, @Lughnasadh, and @AndyYan for news about that and confirming it.init_boot.img, NOT boot.img AND we flash the patched init_boot to the init_boot partition - do not flash it to the boot partition.
Moved @mariusnoor's provided zero-day OTA.zip to Post #8 - Old news from the OP.
INDEX:
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
- How to Root the first time / aka How to unlock the Bootloader
- Unlocking Bootloader (required in order to root)
- How to update each month (and also how to root)[requires an unlocked bootloader for updating via this factory image method]
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following
- SafetyNet
- Optional steps when updating - flashing custom kernels
- The two schools of thought on disabling Verity and Verification
- ADB/Fastboot and Windows USB Drivers - direct download links and the most recent changelog
- Post #3 - Other, most important resources:
- A list of other important apps
- TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
- Factory Images (requires an unlocked bootloader)
- Full OTA Images(doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
- @mariusnoor's provided official URL to download the zero-day OTA to
TD1A.220804.031.
- @mariusnoor's provided official URL to download the zero-day OTA to
- Check warranty status
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)- Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
- Find problem apps, Magisk, and LSposed Modules by (three different methods)
- 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)
- How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
- How to unroot
- Post #4 - Build ID definitions
- Post #5 - Blank
- Post #6 - Regarding P7P 5G model numbers and capabilities, and how to determine your hardware version
- Post #7 - My personal advice for how to get your device back up and running as you had it before a factory reset
- Post #8 - Old news from the OP
Thank you to the following users who have all contributed greatly to my knowledge of Pixels since I came back to XDA a year ago after a few years of mostly inactivity. Apologies if I miss anybody. In alphabetical order:
41Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers
Unlocking Bootloader / Rooting / Updating:
How to Root the first time / aka How to unlock the Bootloader:
Unlocking the bootloader will factory reset your device. There is no way around this. I highly suggest never re-locking your bootloader once you unlock it. If you do ever re-lock the bootloader, only do so after restoring the phone to 100% stock by using the latest Pixel 7 Pro Factory Image or Official Google Android Flash Tool.
Verizon variants:
T-Mobile and AT&T variants:
The direct-from-Google (or other retailers who aren't U.S. Carriers), the factory Carrier Unlocked Pixels:
The rest of the world's carriers:
Other than trying the things I mentioned above, there is nothing else that anyone on XDA can do to help get OEM unlocking to be ungrayed.
Unlocking Bootloader (required in order to root)
How to update each month (and also how to root) [requires an unlocked bootloader for updating via this factory image method]
- These three instructions only apply if you're already rooted and updating from one firmware version to another:
- Made sure all Magisk Modules have been updated.
- Disable all Magisk Modules.
- UNhide Magisk!
- If you are going to use the Official Google Android Flash Tool, then skip the steps I indicate with FAB(Flash-All.Bat).
- 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
- If using the Android Flash Tool to update/dirty flash, you should have the following items notselected:
- Always use the latest ADB/Fastboot (SDK Platform Tools) and Windows USB Drivers.
- Unzip the Platform Tools.
- Download the latest Pixel 7 Pro Factory Image (at the bottom of the "Cheetah" section).
- Unzip the factory image to the same
platform-toolsfolder, i.e. so that flash-all.bat and all other files are in the same folder as ADB and Fastboot from the platform-tools. - * FAB VERY important - Edit the
flash-all.bat(on Windows) orflash-all.sh(on Linux) and remove the-wfrom thefastboot update image-cheetah-etcetera.zipline. This will keep the script from wiping your phone when you run it. - Extract only the
init_boot.imgfile from theimage-cheetah-etcetera.zipto the sameplatform-toolsfolder. - Copy the init_boot.img from the PC to the phone's internal storage.
- On the phone: Apply Magisk Stable to the new stock
init_boot.img. NOTE: It is always possible that an Android Update (Monthly, QPR [Quarterly Platform Release], new major Android versions, and Beta versions) might need a new version of Magisk Stable, Beta, or Canary from GitHub to work correctly. XDA forum for Magisk is here.- Launch the Magisk app.
- Beside "Magisk", click "Install".
- Click "Select and Patch a File", and choose the init_boot.img that you just copied to the phone's storage.
- Copy the Magisk'd init_boot.img (filename similar to
magisk_patched-25200_1a2B3c.img)back over to the computer. - * FAB Run commands:
Code:adb reboot bootloader flash-all.bat (on Windows) or flash-all.sh (on Linux) (Note: At least two Apple Macintosh users had trouble using the flash-all.sh - at least one of those users, everything went smooth once they used a Windows PC for this part of the process)IMPORTANT - The flash-all will take several minutes and reboot on its own several times including to a mode called "FastbootD", and finally reboot into full Android when it's done. Do not interrupt this process. On the FastbootD screen on the phone, do not use any of the manual selection options - let the flash-all script do it's work. Do not unplug your phone until it has fully booted into Android.
Thanks to @PurppleMonkey and @xgerryx for suggesting a warning about this. Thanks to @simplepinoi177 for suggesting the "FastbootD" clarification. - On the phone:
- Wait for the phone to boot normally.
- OPTIONAL: If you want to flash both slots, after this first time, then after do the following:
Code:adb reboot bootloader fastboot --set-active=other flash-all.bat
- On the computer:
- Open a Command Prompt and navigate to the
platform-toolsfolder. - Run command:
Code:adb reboot bootloader - After phone has rebooted into Bootloader (Fastboot) mode, run command:
Code:fastboot flash init_boot magisk_patched-25200_1a2B3c.img fastboot reboot
- Open a Command Prompt and navigate to the
- Unlock the phone.
- Confirm that the phone boots completely normally.
- Cautiously re-enable Magisk Modules.
- Reboot.
- Confirm everything worked fine.
- If the phone won't boot correctly after having enabled Magisk Modules, see either of the two solutions below:
-
- Find problem apps, Magisk, and LSposed Modules by (three different methods) section in my next post. After following that link, you may have to scroll up a little bit and the section title will be highlighted.
-
SafetyNet:
Use whichever of these is newer than the other:
- @Displax Universal SafetyNet Fix Mod on XDA.
- Official Universal SafetyNet Fix released by @kdrag0n available at XDA.
Optional steps when updating - flashing custom kernels:
ADB/Fastboot & Windows USB Drivers:
Platform Tools was updated in August 2022 to v33.0.3 (don't use the newer v34.0.0 - it has issues):
22
Indeed. My MOD is a temporary solution until kdrag0n release accurate fix.
I didn't change the update channel in the module on purpose so that everyone can upgrade to the new official version automatically without any problems.21Other, most important resources
A list of other important apps: - be sure to thank the respective OPs:
- Here's the Magisk section of XDA's forums, for rooting. Magisk on GitHub.
- @[email protected]'s section for Nova Launcher / Nova Launcher Prime - been using this since early 2012!
- @capntrips' thread [DEV] Kernel Flasher
- [KERNEL] CleanSlate |S2S|AdBlock|VIB|BatterySvr - Thanks @tbalden!
- [Kernel] [Android Stable]Kirisakura for Pixel 7/Pro aka "Pantah" - thanks @Freak07!
- [KERNEL]Despair Kernel - Thanks @DespairFactor!
- Multi Timer StopWatch - this multiple timer app is the bomb. Got widgets, customization like crazy, you name it.
- See my review with screenshots about Multi Timer StopWatch here.
- @Chainfire's thread [APP][5.0+][2020.12.22] CF.lumen v3.74 - I used to use this app to enable my phones to go extra dim before Android developed the better native capability for that, and the app has been confirmed to work on the Pixel 7 Pro for color control, too
- @jorrik98's thread [Themes / Apps / Mods] Better Internet Tiles - Bring back Wi-Fi and mobile data toggles! (non-root)
- @VR25's thread Advanced Charging Controller (ACC)
- CrazyBoyFeng's ACC Settings
- MatteCarra's AccA (Advanced Charging Controller App)
- @siavash79's thread [MOD][Xposed+Magisk][Pre-Release] AOSP Mods - System modifications for AOSP-based Android 12+. This is a big one for me, personally.
- @Quinny899's thread [APP][ROOT][11+][19/07] Classic Power Menu - Power Menu Replacement w/ Wallet, Controls on Android 11, 12, 13+
- Swift Backup
- @j4velin's thread [APP] Wallpaper Changer - been using this since mid-2011!
- @Jawomo's thread [Themes / Apps / Mods] aodNotify - Notification Light / LED - see my post in that thread here for the proper offsets to use the front camera notification circle on the Pixel 7 Pro.
- @Jawomo's thread [APP] dynamicSpot - iPhone 14 Pro Dynamic Island for android!
One of these two options:
- 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).
Select the options to:- Wipe
- Force flash all partitions
- Re-lock bootloader
- Flash the completely stock init_boot.img from the same firmware version that you're on:
Code:adb reboot bootloader fastboot flash init_boot init_boot.img
TWRP [not made for the Pixel 7 (or 6) Pro yet - will update when or if ever it has - don't hold your breath]
Factory Images (requires an unlocked bootloader)
Full OTA Images (doesn't require an unlocked bootloader - you can ask questions in this thread, but I won't be providing the steps necessary, as I always use the factory image)
Check warranty status - *may* reveal if a phone is refurbished, only if the phone was refurbished through Google - thanks to @Alekos for making me aware of the site.
Official Google Pixel Update and Software Repair(reported as of January 23, 2022 to still not be updated for the Pixel 6/Pro - no idea if it has yet now, or if it will be for the 7/Pro)
Official Google Pixel Install fingerprint calibration software (also available at the bottom of the Update and Software Repair page above) - I believe this is only helpful if you've replaced the screen - if it's anything like the Pixel 6 Pro: if you have the screen replaced, then you *must* have the fingerprint reader replaced as well.
Find problem apps, Magisk, and LSposed Modules by (three different methods):
- Google's Help Page for Find problem apps by rebooting to safe mode - this can be a lifesaver and keep you from having to do a restore to 100% complete stock or even from having to do a factory reset. This will deactivate all Magisk modules, and they'll remain deactivated even after you boot normally after briefly booting to safe mode. You can re-enable the Magisk modules as you wish to try to narrow down the problem if it was caused by a Magisk module. This can even get things working again after a Magisk Module wasn't finished installing and potentially causing a bootloop.
- You can also follow @Jon8RFC's advice:
Worked for me yesterday when I accidentally tried some old version of a Magisk Module. You have to reinstall your Magisk Modules, but if you're using a third-party widget, it won't disable them like Safe mode does. - (May only be for mis-behaving LSposed modules):
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)
How to determine if you already have Verity and Verification disabled (required for custom kernels for now)
Alternative two more manual ways of checking:I keep seeing this asked, so I added a Magisk module for it to the linked Github release. With the module installed, you can just run:
Code:su avbctl get-verity avbctl get-verification
I spent way more time debugging that I downloaded Github's HTML of theupdate-binaryscript rather than the raw file than I care to admit. Off to bed.
- Post #2 - Unlocking Bootloader / Rooting / Updating | SafetyNet | ADB/Fastboot & Windows USB Drivers:
