yashsingh1/xdaforums huggingface dataset:
[Google Pixel 7] badabing2003:
New Release:

Apr 14, 2024 v6.9.2.0 change log:

Add a new experimental feature to downgrade without a wipe and potentially switch from Beta to Stable without a wipe (untested).

Credit to @tbalden for the discovery and @capntrips for the details of the process.

Select any img file and get additional image info.

#190 fix, scrcpy launch improvement.

Improved Menu to disabled advanced features when it's not enabled in the settings. (Previously only other GUI elements were hidden or disabled).

If KernelSU or APatch is installed, report their version as part of device details.

Improved logging.

Improved santization.

Other minor improvements and added stability.
[Google Pixel 7] badabing2003:
Update Release:

Apr 16, 2024 v6.9.2.5 change log:

Roll up MacOS related changes. #187 and #190

Logging improvements

When Magisk delta is installed, automatically set the package to: io.github.huskydg.magisk
[Google Pixel 7] badabing2003:
Update Release:

Apr 19, 2024 v6.9.3.0 change log:

Update AVBTool to use RSA library instead of depending on an external openssl.

English typo corrections.

When flashing OTA, give the option to continue, even if it is a downgrade.

Github action: Fix MacOS build deployment issue.
[Google Pixel 7] badabing2003:
Update Release:

May 08, 2024 v6.9.4.0 change log:

Added encryption to support.zip for extra privacy / security.

Regression bug fix: When a Magisk module was disabled in Magisk, it was not reflected in PixelFlasher.

Added Refresh button to refresh Magisk module list at will.

When Apply Custom ROM checkbox is checked, make sure that a ROM file is also selected, otherwise ignore the selection.

After rebooting to bootloader, if the device is not detected, sleep 5 seconds and try again.

Update Readme to include a link to proper USB driver setup on Linux systems.
[Google Pixel 7] mugendon:
I already used PixelFlasher for a lot of updates, but today for the first time I encountered a problem after I successfully flashed the May OTA to my Pixel 7 (with version 6.9.4.0). As usual I wanted to start another OTA flash to also flash the other Slot, but this time that just resulted in the following error:

I already restarted PixelFlasher und reconnected my Pixel 7, but that didn't help. The support.zip is attached.
[Google Pixel 7] badabing2003:
Why are you trying to flash February release after flashing May release?

Firmware: F:\Downloads\pixel7\Factory Images\24.05\panther-ota-uq1a.240205.002-016d485b.zip
[Google Pixel 7] mugendon:
This is a really good question, because I just pressed the "Flash Pixel Phone" button again after the flash of the May OTA was done without closing the application in between.

As you might have noticed the folder name was "\24.05\". So this was the folder I had chosen for PixelFlasher to download the May (05) OTA into. And of course I also picked this file for flashing otherwise it wouldn't have flashed the May update in the first try (also had to process and make a patched magisk boot img).

But I checked the folder again and it didn't include the May but as your support log says the February OTA. Which is kinda strange.

Now I deleted the February OTA from the folder and redownloaded the May OTA with PixelFlasher. I chose the new OTA in the device image drop down, processed it and guess what, it showed that I already got a patched boot img for it. But the boot img didn't match the May OTA, but the February OTA. Which is strange again, since it shouldn't mix that up.

I deleted the patched boot img and created a new one. Now the flashing worked like a charm as always.

But this behavior is really really strange. To add a little more info: My device had the February update (thus PixelFlasher already had to deal with the February OTA a few months ago) and I directly flashed the May OTA.
[Google Pixel 7] badabing2003:
Thanks for the info, can you create another support file, in case I can spot something in there?

What you're explaining should not happen, I want to make sure that there isn't an issue with the program.
[Google Pixel 7] mugendon:
Yes, see the attached file. Btw. I moved the OTA from the "Factory Images" dir to the "Full OTA Images" dir in the meantime.

It is interesting that although I redownloaded the May OTA file today that the "select a boot/init_boot" table still shows yesterday in the "Date" column. Probably because I already processed the May OTA yesterday and the "Source SHA1" is the same.
[Google Pixel 7] badabing2003:
Thanks for the support file.

I think I know what might have happened.

When you downloaded 0505 image, you saved it as 0205, possibly by clicking on a pre-existing file which was 0205 and the save as dialog picking up the filename.

See this

2024-05-11 21:30:17 Starting background download for: https://dl.google.com/dl/android/aosp/panther-ota-ap1a.240505.005-1f3cc637.zip to be saved to F:\Downloads\pixel7\Factory Images\24.05\panther-ota-uq1a.240205.002-016d485b.zip
please be patient ...

2024-05-11 21:30:17 Downloading: https://dl.google.com/dl/android/aosp/panther-ota-ap1a.240505.005-1f3cc637.zip ...

ℹ️ 2024-05-11 21:31:15 Download: F:\Downloads\pixel7\Factory Images\24.05\panther-ota-uq1a.240205.002-016d485b.zip completed! in 59 seconds
2024-05-11 21:31:15 Download Successful File downloaded successfully: https://dl.google.com/dl/android/aosp/panther-ota-ap1a.240505.005-1f3cc637.zip and saved to F:\Downloads\pixel7\Factory Images\24.05\panther-ota-uq1a.240205.002-016d485b.zip

==============================================================================
2024-05-11 21:32:27 User initiated firmware selection
==============================================================================
The following firmware is selected:
panther-ota-uq1a.240205.002-016d485b.zip
Selected Firmware panther-ota-uq1a.240205.002-016d485b.zip SHA-256: 1f3cc6375af39e8de0fa4ef2019427d2ecd88144b24a52d5b8c3c0a0188b6363
WARNING: Expected to match 1f3cc637 in the panther-ota-uq1a.240205.002-016d485b.zip but didn't, please double check to make sure the checksum is good.

See how you're downloading https://dl.google.com/dl/android/aosp/panther-ota-ap1a.240505.005-1f3cc637.zip

but saving as panther-ota-uq1a.240205.002-016d485b.zip even though the file is actually 0505

And this is confirmed later on when you load the firmware, PF warns you that the checksum of the firmware did not match what's on the filename.

Which is exactly the case, the checksum 1f3cc6375af39e8de0fa4ef2019427d2ecd88144b24a52d5b8c3c0a0188b6363 is the correct checksum for 0505, but the filename has 016d485b

So when you continued to process, PF stored the boot.img / init_boot.img as belonging to 0205 firmware, because it gets that from the filename.

Later on when it did the validation to make sure you were not downgrading, it failed.
[Google Pixel 7] mugendon:
This sounds plausible. I guess I copied the 24.02 folder and renamed it to 24.05 and forgot about the also copied file in it. Then in the save dialog I probably clicked on the existing file. Or something like that.

Glad it was highly likely a mistake by me and you don't have to dig through your code for it. Hope you haven't wasted too much time with the logs.

Thanks for your help.
[Google Pixel 7] badabing2003:
Update Release:

May 17, 2024 v6.9.5.0 change log:

Added Pixel 8a (akita) support.

Updated Pixel device end of life dates based on Google's published data.

Added an option to refresh Google Images download links, useful on release days when you want an immediate refresh.

Memory improvements when building Google Images list.

Added additional troubleshooting debug messages when a device is not detected.

Minor bug fixes and improvements.
[Google Pixel 7] ldeveraux:
Went to update my pixel to latest yesterday and pixelflasher (latest on Windows 11) froze for like a half hour while phone in recovery mode. I went to reboot (status in pixelflasher didn't look like it had started) now the phone won't do anything. No screen, no power, can't use any of the magic button keys or plug in power to start this thing. Attaching the support zip file here.
[Google Pixel 7] badabing2003:
Everything was ok until your device (as part of factory flashing) tried to reboot to fatsbootd mode

extracting super_empty.img (0 MB) to disk... took 0.000s
Rebooting into fastboot OKAY [ 0.000s]
< waiting for REDACTED >

Your device should not be in recovery mode.

We've been saying this for a long time, people stop using factory images unless you really have to, full OTA does a better job, and is much safer, it always flashes to inactive slot, and it never wipes, and if anything goes wrong, it boots back to the previously working active partition.

In any case, too late for your device,

If you can make youre device detected in bootloader or recovery mode, most likely it can be fixed unless there is a hardware issue, speaking of which, other than possible cable / PC connection / driver issue, your device should havee been able to boot to bootloader mode after flashing half way and getting stuck at fastbootd.
[Google Pixel 7] ldeveraux:
I grabbed an image like I have for a year, directly from Google. I saw the VZW image available, that's what I used.

I don't know how I would even get into bootloader or recovery, no response at all from the phone. When it was in the menu, I had full access, I think that was fastbootd mode? I selected reboot to recovery (I think?), it rebooted, got stuck on the Google screen. I then tried to reboot and now it won't power on. If it's a lost cause, then I learned a lesson. I wonder if there's anything at all to try. I've tried booting with any and all key combinations without luck
[Google Pixel 7] badabing2003:
Does you PC make a sound when you connect the phone?

Check in device manager and see what it reports as?

sometimes draining the battery and then trying after a charge helps.
[Google Pixel 7] Magnivore:
Trying a dry run of May's image (problems occurred in main thread ~1 month ago, see here), and my phone ended on a 'your device is corrupt, press to continue' screen. PF also said the device timed out. Am I supposed to hit continue sometime during the flash process? After hitting continue it went to the 'off but charging' screen, at which point I was able to boot it through another 'corrupt device' screen. Historically I could swear I've never touched it during a test or real run.

Support file attached.

EDIT: Despite my computer making a noise when my phone is plugged in PF is no longer detecting my phone.
[Google Pixel 7] badabing2003:
Dry run cannot cause a damage, all it does is instead of actually performing the flashing, it echoes the command that would have been executed had it not been in dry mode.

So basically, all that's being tested is that your device can reboot to bootloader, be detected, and if need be reboot to fastbootd, be detected and then reboot to system

Here's the entire script that was ran

chcp 437
@ECHO OFF
:: This is a generated file by PixelFlasher v6.9.5.0
:: cd C:\Users\REDACTED\AppData\Roaming\PixelFlasher\factory_images\panther-ap1a.240505.005
:: pf_boot.img: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\boot_images4\e58c0dca22b7812b1f569a8c2161dfd498c36956\magisk_patched_26400_e58c0dca_075ca29c.img
:: Android Platform Tools Version: 35.0.1-11580240

PATH=%PATH%;"%SYSTEMROOT%\System32"
echo "C:\Users\REDACTED\Desktop\My stuff\Android stuff\platform-tools\fastboot.exe" -s REDACTED flash bootloader bootloader-panther-cloudripper-14.4-11458464.img
"C:\Users\REDACTED\Desktop\My stuff\Android stuff\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo "C:\Users\REDACTED\Desktop\My stuff\Android stuff\platform-tools\fastboot.exe" -s REDACTED flash radio radio-panther-g5300q-231218-240404-b-11673025.img
"C:\Users\REDACTED\Desktop\My stuff\Android stuff\platform-tools\fastboot.exe" -s REDACTED reboot-bootloader
ping -n 5 127.0.0.1 >nul
echo "C:\Users\REDACTED\Desktop\My stuff\Android stuff\platform-tools\fastboot.exe" -s REDACTED --skip-reboot update image-panther-ap1a.240505.005.zip

The fact that you had corrupt message, means that you needed to interact with the device to continue past that message, and if you didn't do so in time, then PF will not detect your device.

You shouldn't be using factory unless you really have to, use OTA, it's safer.
[Google Pixel 7] Magnivore:
Two questions. First, once the dry run was done I unplugged my phone, replugged it, and restarted PF and it still didn't detect my phone. My question and concern is, why is that happening?

Second, what do you mean by that last part? I think I downloaded 0505.005, and the only other version that's simpler to that is 004. What an I missing here?
[Google Pixel 7] badabing2003:
Possibly you still have a hanging adb process.

Kill that, or do adb kill-server or reboot PC

Check the OP of the main thread, there are two different format images, factory and full OTA.

Full OTA is the recommended one, it's safer.
[Google Pixel 7] ldeveraux:
I just plugged it in when I got home and it does make the sound when I connect/disconnect, so maybe it's on? i've been through every category in Device Manager and can't see it there in any capacity. I wonder if the screen blew, is that a thing that can happen?I tried checking if adb or fastboot recognized a device and it didn't.
[Google Pixel 7] badabing2003:
You should see

View attachment 6105561

If you see it as a serial device, it's not a good sign

I never heard of screen blowing, but if that were the case, adb should still see the device.

Try to boot to safe mode with key combo and see if that helps.
[Google Pixel 7] ldeveraux:
Weird that that's in the Display Adapters category. Regardless, I have nothing. If I plug in my working S10, it shows under Portable Devices. No ADB, no Fastboot. I tried power and volume up to force to reboot to safe mode, screen stays black but I still get the connection sound. Just strange there's no indication of any device change in Manager. I presume there's nothing Pixelflasher can do when connected?
[Google Pixel 7] badabing2003:
If working Samsung is also not seen, then you have a driver / port issue.

Reinstall drivers or better yet test on another pc
[Google Pixel 7] ldeveraux:
No, I said the working Samsung IS SEEN by the PC, it's seen by multiple computers. Just the Pixel isn't seen anywhere.
[Google Pixel 7] Dr Grato:
Hi buddy. Based on my previous experience, u need to try change the cable too. Yes, I tried 5 cables due to this issue, and the most expensive one is not always the right one. Maybe u can ask your friends that managed to do it, and borrow their cable.
[Google Pixel 7] ldeveraux:
I've tried many cables. I don't think a specific cable will magically make the screen turn on

Sent from SM-G975U using ReLabs
[Google Pixel 7] badabing2003:
Update Release:

June 04, 2024 v6.9.6.0 change log:

#204 Fix Pyinstaller issue, thanks to PR from @cjshearer.

PIF Import favorites can now import recursively including subdirectories.

Added Device | Check otacerts menu option to quickly check if the ROM is signed.

Sync banned kernel list with @osm0sis published list.

Improved exception handling

Improved debug messages for troubleshooting

Fix timing issue for a corner case cleanup before unzipping is completed.

AVBTool improvements.
[Google Pixel 7] ldeveraux:
I let my phone die completely, I think? It's been 2 weeks. I just plugged it into a PC and while it definitely doesn't appear to power on, I see it in Device Manager under Ports > USB Serial Device (COM11). Then nothing. Any chance of recovering it from that info?
[Google Pixel 7] badabing2003:
I'm afraid when you see your device as USB Serial Device, it's a hard brick.

There are some threads about using EDL tools, but I have not seen any success stories with Pixels.

I hope I'm wrong, but perhaps your only course of action is RMA.
[Google Pixel 7] ldeveraux:
I already moved on from the phone, just hoping to recover some of my app data. Google's 'generous' warranty expired 1.5 months ago, so no RMA, and I don't want to pay to have it repaired. I assume there are no threads using EDL tools specific to the Pixel?
[Google Pixel 7] badabing2003:
You can check this thread, it has some posted tools, but I don't think anyone had success.

Guide: Unbrick Pixel 6 Oriele or Pixel 6 Pro "Raven"

Pixel 6 Pro runs on a Google Tensor CPU which is in fact an Exynos CPU This means that there is Exynos boot recovery in the CPU You can repair the bootloader using the Samsung Exynos Tool Nothing could be flashed from the mode, however it...

xdaforums.com

I know it's not for your device, but it is a starting point.
[Google Pixel 7] badabing2003:
Update Release:

June 24, 2024 v6.9.8.0 change log:

Improve Check keybox.xml to report if the certificate is software signed, also report about all included certificates.

Added settings option Keep temporary support files in case one needs to inspect the support files.

Add Github action to build on MacOS 12, MacOS 11 runner has been deprecated.

Update Pixel beta links from A14 to A15.

Minor bug fixes and improvements.
[Google Pixel 7] ozyk100:
Hi there

I tried to update my phone to the Jun OTA but it always fails on the 'verification' on 49%.

I downloaded OTA file through PF and repeated the same process like I always do but it always fails.

After looking at the console I noticed that it errors out on patching the init_boot image. I cleared the console and created support file so you can take a look at it and tell me (again 🤣) where is (my) mistake.

I'm using older version of PF because Windows 10, in it's infinite wisdom, is reporting trojan on the newest version from github.

I checked that the platform tools are v33.03 and that I have the latest version of stable Magisk v27.0

Thank you in advance
[Google Pixel 7] badabing2003:
You were using The latest PF and then decided to go older

PixelFlasher 6.9.8.0 started on :2024-06-25 21:29:41

Just add an exception in AV and use the latest, it's better.

By the way you also have a good patch

Looking for magisk_patched_27000_9610d62e_25d69480.img in /storage/emulated/0/Download ...
Checking for /storage/emulated/0/Download/magisk_patched_27000_9610d62e_25d69480.img on the device ...
File: /storage/emulated/0/Download/magisk_patched_27000_9610d62e_25d69480.img is found on the device.
Pulling /storage/emulated/0/Download/magisk_patched_27000_9610d62e_25d69480.img from the phone to: magisk_patched_27000_9610d62e_25d69480.img ...
Pulling remote file: /storage/emulated/0/Download/magisk_patched_27000_9610d62e_25d69480.img from the device to: C:\Users\REDACTED\AppData\Roaming\PixelFlasher\tmp\magisk_patched_27000_9610d62e_25d69480.img ...
Return Code: 0
Getting SHA1 of C:\Users\REDACTED\AppData\Roaming\PixelFlasher\tmp\magisk_patched_27000_9610d62e_25d69480.img ...
SHA1 of magisk_patched_27000_9610d62e_25d69480.img file: 25d694802df8c428b949cfdf23abf4402f7dbdf0

Getting SHA1 of source init_boot.img ...
Source init_boot.img's SHA1 is: 9610d62e90fc809ab1df24030224407615c07ae3
Getting SHA1 from Magisk config ...
Magisk Config's SHA1 is: e58c0dca22b7812b1f569a8c2161dfd498c36956

Checking to see if Magisk made a backup of the source init_boot.img
Magisk has NOT made a backup of the source init_boot.img
Triggering Magisk to create a backup ...
Making sure stock_boot.img is found on the device ...
Triggering Magisk run_migration to create a Backup of source boot.img
run_migration completed.
Magisk backup for 9610d62e90fc809ab1df24030224407615c07ae3 was successful

Extracting SHA1 from magisk_patched_27000_9610d62e_25d69480.img ...
SHA1 embedded in C:\Users\REDACTED\AppData\Roaming\PixelFlasher\tmp\magisk_patched_27000_9610d62e_25d69480.img is: 9610d62e90fc809ab1df24030224407615c07ae3
Comparing source init_boot.img SHA1 with SHA1 embedded in 9610d62e90fc809ab1df24030224407615c07ae3 (they should match) ...
Good: Both SHA1s: 9610d62e90fc809ab1df24030224407615c07ae3 match.

But in any case, the issue with with a previous OTA.

Do this

Menu | Device | Cancel OTA Update

View attachment 6117294

And then flash OTA again.
[Google Pixel 7] ozyk100:
I did initially tell the Windows AV to ignore the trojan detection but later decided to use older version of PF thinking that the flashing issue was maybe connected to false detection and windows was blocking 'something' from PF.

Anyway, I'm at work right now and away from pc. Moments ago I tried to update Osm0sis PIF fork module to v9 and after rebooting it has updated my firmware to June version and I lost root.

Since you said that the patched image was done correctly, I'm guessing that canceling the OTA in menu/device won't be necessary and all I have to do is flash patched init_boot image.

Will report later when I get home and it's done.
[Google Pixel 7] badabing2003:
Correct.
[Google Pixel 7] ozyk100:
Done and done... Everything went smoothly! Thank you for your help and quick response.
[Google Pixel 7] rhyno81:
Hooping you can help me with my current issue. I've flashed a bunch of times without issue but, it keeps failing this time and im not sure why. Thanks for all you do and any help you can provide.
[Google Pixel 7] badabing2003:
see 4 posts above yours
[Google Pixel 7] rhyno81:
That did it. Thanks for the help.
[Google Pixel 7] badabing2003:
New Release:

July 4, 2024 v7.0.0.0 change log:

When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).

Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).

Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).

When reading device details, report the sys.oem_unlock_supported prop value.

Miscellaneous minor improvements.
[Google Pixel 7] badabing2003:
Latest Release:

July 11, 2024 v7.1.0.0 change log:

Add license headers to source files.

Improved logging.

By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).

Check keybox.xml tool now provides more extensive report about the keybox.
[Google Pixel 7] badabing2003:
Update Release:

July 14, 2024 v7.1.1.1 change log:

Bugfix: #222 Customize My Tools menu is duplicatede when no tools are added.

July 14, 2024 v7.1.1.0 change log:

Windows versions of PixelFlasher are now signed (self-signed).

Hopefully this would cut down on false positive virus / trojan alerts, but it should also get rid of Unrecognized app warnings.

PixelFlasher.crt is the certificate, and ca_badabing2005.crt is the root CA.

Bugfix: #221 handle a corner case exception.