Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.

[badabing2003]

This is the support thread of PixelFlasher
(PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

IMPORTANT:
Please do not ask questions the answers of which are already stated in the OP.
I will simply ignore the request, as I'm fed up of referring people to the post that has the answers.

Troubleshooting:
If you need support or assistance, please generate and provide a support file from within PixelFlasher.
You can hit that big Support button on the main screen, or select it from the Help menu.
The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
And no, a screenshot of the console or an excerpt from the console, does not make a support file.
Clearly state the issue you're encountering, what actions did you take, and what outcome you observed, and what outcome you had expected.
Do NOT modify the support file, keep it intact.

• See this post.
• Generate Sanitized support.zip file (File Menu) and submit that with your report.
• If your anti-virus program is telling you that PixelFlasher is a malware, or you are concerned in any way, please check this post.

 

[badabing2003]

Placeholder

 

[i5lee8bit]

Got Pixel 7 and Pixel 7 Pro (wife and me) on launch day. Both of us coming from 4 and 4 XL. Crazy how far things have come and continue to go. Love this community, and I'm sure I'm gonna love this tool too. Thanks OP!!

 

[galaxys]

Great to see GUI Tool! Kudos

 

[banshee28]

As soon as BB has my P7P in stock, I will then be taking this for a spin!! Thanks for making it compatible with P7P!!

 

[skaforey]

Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.

 

[badabing2003]

Used the pre-release version without any issues. Thank you so much for this amazing tool! Let me know if you want to see any logs or anything of the process. This was also the first time I used the tool to have it actually wipe data and that worked as well, and I appreciate the double checking before the data is wiped. Good to know if you accidentally have it on wipe all data that it will prompt you before you make a mistake.

Thanks for the feedback, no need for files considering that it worked fine.
It helps to get the confirmation as I don't have a Pixel 7 / 7P device.

 

[losticloud]

I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this

Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed

After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...

 

[badabing2003]

I managed to kill my Pixel. I went with the keep data option. Everything was good until it got to this

Sending sparse 'product_a' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed

After this it went into a bootloop. I got out of bootloop and tried it again. This time i got these errors and no it won't boot. When connected to my computer it shows up as usb3. Tried to send commands to it and nothing, tried holding power button, power + up volume, power + down volume and nothing.
Resizing 'vendor_a' OKAY [ 0.003s]
archive does not contain 'boot_other.img'
archive does not contain 'odm.img'
archive does not contain 'odm_dlkm.img'
extracting product.img (2811 MB) to disk... took 24.746s
archive does not contain 'product.sig'
Resizing 'product_b' OKAY [ 0.007s]
Sending sparse 'product_b' 1/11 (262116 KB) OKAY [ 6.766s]
Writing 'product_b' OKAY [ 0.354s]
Sending sparse 'product_b' 2/11 (262120 KB) OKAY [ 6.874s]
Writing 'product_b' OKAY [ 0.371s]
Sending sparse 'product_b' 3/11 (262128 KB) OKAY [ 6.851s]
Writing 'product_b' OKAY [ 0.358s]
Sending sparse 'product_b' 4/11 (262124 KB) OKAY [ 6.893s]
Writing 'product_b' OKAY [ 0.405s]
Sending sparse 'product_b' 5/11 (262116 KB) OKAY [ 6.719s]
Writing 'product_b' OKAY [ 0.365s]
Sending sparse 'product_b' 6/11 (262128 KB) OKAY [ 6.869s]
Writing 'product_b' OKAY [ 0.403s]
Sending sparse 'product_b' 7/11 (262128 KB) OKAY [ 6.899s]
Writing 'product_b' OKAY [ 0.359s]
Sending sparse 'product_b' 8/11 (262128 KB) OKAY [ 6.896s]
Writing 'product_b' OKAY [ 0.398s]
Sending sparse 'product_b' 9/11 (262140 KB) OKAY [ 6.909s]
Writing 'product_b' OKAY [ 0.362s]
Sending sparse 'product_b' 10/11 (262096 KB) OKAY [ 6.926s]
Writing 'product_b' OKAY [ 0.385s]
Sending sparse 'product_b' 11/11 (248408 KB) FAILED (Error reading sparse file)
fastboot: error: Command failed
rebooting to bootloader ...
Rebooting into bootloader FAILED (remote: 'Couldn't download data')
fastboot: error: Command failed
Sleeping 5-10 seconds ...

This sounds like a flaky communication problem.

1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable

When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?

I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.

 

[losticloud]

This sounds like a flaky communication problem.

1- Support.zip file from PF's help menu greatly helps
2- Make sure you are only using SDK 33.0.3 anything older will not work
3- Make sure your connection to the PC is solid, and the fatsboot drivers are good
4- USB 2 connections are more reliable

When you scan for devices in PF, does it detect the phone? in any mode?
if yes, what mode is that?

I'm going to step out for a little while, but don't worry, your phone is not dead, it can be revived and I'll do my best to support you along the way when I'm back.

1. do you want me to post it here or PM to you?
2. I downloaded 33.0.3 before starting
3. drivers are good
4. I tried usb 2 connection but doesn't do anything. If i use the usb c cable that it came with it shows up as port com3

I tried scanning with PF and it doesn't detect the device at, I used both usb c and usb 2 cable.

If you can help great, if not I can always do RMA since i just got device. Thank you in advance

If you can help great, if not I can start RMA process. Thank you

 

[K1nsey6]

Is this method keeping L1 and Safetynet?

 

[losticloud]

Is this method keeping L1 and Safetynet?

Yes, the pixel no longer shows up. it also stopped booting, it's just dark.

Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.

 

[K1nsey6]

Yes, the pixel no longer shows up. it also stopped booting, it's just dark.

Doing some searching i think its stuck in EDL mode and there's no recovery i have to return it or exchange it.

Holding down Power/Vol Up for 20 seconds isnt rebooting?

 

[losticloud]

Holding down Power/Vol Up for 20 seconds isnt rebooting?

Nope, doesn't even vibrate.

 

[simplepinoi177]

This sounds like a flaky communication problem.
...
4- USB 2 connections are more reliable
....

God is that still a thing?!?!?!
LOL, I remember when I first started rooting on my Pixel 2 XL, SOOOO many people were having issues using the USB-C connection, but once they used the legacy USB-A, things would suddenly work!
USB-C connections on a computer/laptop were still rather new-ish, so I figured that was the reason. I can't believe how many years later that this advice would still be relevant!

 

[losticloud]

I started RMA I’ll try this again in a few weeks when I get new one.

 

[badabing2003]

I started RMA I’ll try this again in a few weeks when I get new one.

Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.

 

[losticloud]

Sorry to hear that you have to go through RMA, the logs help in trying to see if there are any hints on what might have happened, they are sanitized, ie any sensitive information is redacted, so you can safely post it here.
Have you tried Google's Android flash tool, I know if the phone isn't detected it can't help, but maybe they can detect EDL mode.

I did try but the phone wasn't detected. Files are attached.

 

[badabing2003]

I did try but the phone wasn't detected. Files are attached.

Thanks,
It's interesting that you started with slot a, ran into the problem writing product 11/11
I'm assuming that the phone could no longer boot to slot a,
Because the next thing I see is the phone in bootloader mode with slot b being active, not sure why it would be in bootloader mode as slot b should have been intact, nothing was written to slot b yet.

I wonder if out of factory phones have both slots the same image.

Then you trying flashing again, again the exact same step of flashing product 11/11 it failed.
However unlike the first time, the phone was placed in bootloader mode on slot b.
I wonder if you were manually putting the phone into bootloader mode or it was eventually ending up in that state?

You tried yet another time, again on slot b, and again it failed on the exact same step.
After that we have no data, I suppose at that point you couldn't even put the phone in bootloader mode.

When you get your new device, I would strongly suggest that you inspect the USB cable, and also make sure the USB port is connected to the PC without a hub or anything, and preferably USB 2.
I know at this day and age it sounds silly, but the signs are failure in communication, or hardware problem.

If you search Google for similar problems, you'd find lots of cases where most of those are related to either the drivers, the cable or the USB port, here's one as an example.

Let us know how your phone goes, and best wishes.

 

[badabing2003]

New Release:
Oct 15, 2022 v4.3.0 release

• New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
• Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
• Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
• Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.