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

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
PF_promo-banner.png

This is the support thread of PixelFlasher for Google Pixel 7 Pro
PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.

Basic mode: Should suit most users. Some of the features in basic mode are:
  • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
  • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
    No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
    No more setting airplane mode and clearing storage to retain Safetynet passing.
  • Display details of boot.img.
    • SHA1 checksum.
    • Origin (file it was extracted from).
    • Whether it is patched or not, and if it is patched.
      • What version of Magisk was used to patch it.
      • On what device it was patched.
      • Date of patching.
      • The SHA1 of the source boot.img file.
    • Option to Live boot from a choice of boot.img.
  • Choose to keep data or wipe data while flashing.
  • Ability to flash even if multiple devices are connected to the computer.
  • Display information about the phone.
    • ID
    • Hardware model.
    • Current installed firmware (build).
    • If it is rooted with Magisk.
    • Magisk version (Magisk Tools).
    • Magisk Manager version (the app).
    • List installed Magisk modules.
    • Connection mode (Adb | Fastboot | Sideload | Recovery).
    • Bootloader version.
    • Android OS API version.
    • Convenient quick links to download Android platform tools or device firmware.
  • Magisk Manager installation UI, screenshot. Supported versions:
    • stable
    • beta
    • canary
    • debug
  • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
    • Name
    • Version
    • Description
    • Enabled / Disabled.
  • Display Android Platform Tools (SDK) version and warn / block if the version is old.
  • Install APK file from the computer onto the device.
  • Advanced features are hidden to keep the interface simple and easy to follow.
  • A lot of checks and validations for smooth operation.
  • Automatic check for program updates.
Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
  • The ability to flash custom ROM (with or without patching boot.img)
  • Option to flash to both slots.
  • Option to flash to inactive slot.
  • Options to disable verity and or verification.
  • Ability to change the active slot.
  • Ability to live boot to custom boot.img (temporary root).
  • Ability to boot to recovery.
  • Ability to flash custom image: boot, recovery, radio, kernel, ...
  • Ability to sideload an image.
  • Lock / Unlock bootloader.
  • Option to gain temporary root (good for testing or checking things out).
  • SOS Disable Magisk modules to get out of bootloop (experimental).

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.

Troubleshooting:
  • See this post.
  • Generate Sanitized support.zip file (File Menu) and submit that with your report.
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.
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
Pre-Release:
Oct 13, 2022 v4.2.0 pre-release
  • Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
  • Added Pixel 7 / 7p partitions flashing options to custom flash.
  • Improved patching process using boot_patch, add more patch file validations.
  • Check for Magisk backup and trigger Magisk to backup if missing.
  • Add more logging messages for troubleshooting.
  • Code optimization / improvements.
  • Bug Fix #28 Error when opening download link without a device selected.
  • Added set_version script to easily set the product version.
  • Print path of the selected boot to console, for easy copy / paste.
 

banshee28

Senior Member
Aug 31, 2010
255
49
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!!
 
  • Like
Reactions: galaxys

skaforey

Senior Member
Nov 5, 2009
595
396
San Diego, CA
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.
 
  • Like
Reactions: badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
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.
 
  • Like
Reactions: skaforey

losticloud

Member
Nov 3, 2021
10
1
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

Recognized Contributor
Sep 17, 2012
1,565
1,843
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.
 
  • Like
Reactions: Homeboy76

losticloud

Member
Nov 3, 2021
10
1
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
 
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! 😅
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
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

Member
Nov 3, 2021
10
1
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.
 

Attachments

  • support.zip
    11.4 KB · Views: 35

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
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

Recognized Contributor
Sep 17, 2012
1,565
1,843
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.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Yet another painless process doing the January updates thanks to the the brilliant mind of @badabing2003 and his creation of this intuitive and easy to use software! Happy New Year! Cheers!
    4
    Hi all,

    I'm trying to figure out how to use pixel flasher.

    My P7pro is rooted with verity and verification disabled. But, PF does not recognize my device to be rooted. So, my question is how do I get PF to recognize root and to update + retain root and verity & verification left disabled?
    Did you allow root access for "[SharedUID] Shell" (com.android.shell) in Magisk? That's used by PF to detect root.
    If you use Magisk Hide you can also set the new package name (not app name) in the PF settings.
    4
    You downloaded the OTA instead of the factory image. OTA's won't flash using the Pixel Flasher Tool. An OTA has to be sideloaded. You need the full factory image from here to flash with PFT.
    Actually OTA can be flashed in PF, but you will not retain root.
    To flash OTA, choose custom flash, select SIDELOAD in the dropdown and choose your file and not the flash button.

    People who don't want root and want a quick update choose that option. It is much faster than doing OTA on the phone.
    4
    Another update, another P7P flash using this tool with less than a handful of mouse clicks and zero issues.

    Even if you have been using ADB for years like me, why choose to make things more difficult?
    3
    You reminded me I need to get some canned pressurized air :sneaky: My laptop is less than a month old so it's not the dust, but I definitely need to have those canned air handy!



    That's a good tip to keep in mind. If I run into the same situation—spinning beach ball, PixelFlash is hung and not responding—would it be safe to try un/replugging? Typically I'd worry un/replugging the phone will interrupt the flash and causing some unpredictable problems/bricking.
    if the phone is showing to be in fastbootd mode
    Something like this (not an exact device image, but it should look similar and say fastbootd)
    Google-Pixel-Android-10-fastbootd-Dedicated-Fastboot-Mode.jpg

    And PixelFlasher is displaying in the console
    < waiting for [some_device_id] >
    you can unplug re-plug
    PF has launched the equivalent of flash_all and which has issued the fastboot command, it's waiting for response and is tuck in that state.
    It would be safe if the above is observed.
  • 41
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 7 Pro
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.

    Basic mode: Should suit most users. Some of the features in basic mode are:
    • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
    • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
      No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
      No more setting airplane mode and clearing storage to retain Safetynet passing.
    • Display details of boot.img.
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    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.

    Troubleshooting:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    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.
    14
    New Release:
    Nov 09, 2022 v4.4.0 release
    • New feature: Font and Font size should be configurable by the user #33
    • New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
      Handy to access a device remotely.
      Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
      I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
    • Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
    • Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
    • Minor UI Improvements
    • If Magisk does not create a backup attempt to trigger Magisk to create one.
    • Update readme to include Pixel 7 / 7P specific info.
    12
    New Release:
    Dec 04, 2022 v4.5.0 release
    • New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
    • New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
    • Use latest Python updated packages.
    • Ubuntu 22.04 support.
    • Miscellaneous improvements.
    12
    So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

    The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

    A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

    I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
    Like @JakeDHS07 said, these options are already in PixelFlasher.

    Don't take this the wrong way, but if you just came back over from iPhone and admittedly are a bit out of date, you shouldn't be asking for features without understanding what exactly you're asking for.
    For example you say,

    if you read the post on the krisakura kernel ...

    And you expect me to hunt for Krisakura Kernel post and learn the process? For something you're not willing to understand? You haven't even linked the post.
    I'm sorry but this only tells me that you don't want to put any effort in helping yourself, you just expect it to be delivered on a platter.

    I suggest the following.
    If you want to flash a Krisakura Kernel, go over that post, understand the steps / the process, apply it to your phone, if you have any problems regarding that, ask them in that forum.
    Repeat this few times, then identify the pain points, the parts where you think if it were automated would save you time and be less error prone.
    Come back and explain your workflow, and describe how adding such and such feature into PF would ease that pain point and I would seriously consider it if it is feasible.

    This is from the OP in the main thread.

    1668803698944.png


    Tools like PF could be used by the following types of users.
    • People who know the process, know exactly what goes into modding the phone manually, and want to save time and effort repeating the same tedious process each and every time they want to flash / mod.
      And if anything goes wrong, they know how to recover, or ask pertinent contextual questions.
      This is the main audience of PF, people in this group not only are capable of understanding the steps, but are also in position to help others.
    • People new to the game, that find the initial learning curve steep to overcome, but are willing to learn, comparing the console output to the manual steps outlined in the guides and trying to make sense of the workflow / steps and learning along the way. People in this group would eventually become proficient and graduate to the first group.
    • People who don't care about learning, they are merely lazy leeches that just want things to be done for them. PF is not intended for this type of users, if I wanted to attract this group I would have charged for the program.
    • People who are incapable of learning / following guides, although I don't believe that this group exists at XDA, but if there are rare few of them, then I respectfully suggest that modding is not for them.
    10
    Pre-Release:
    Oct 13, 2022 v4.2.0 pre-release
    • Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
    • Added Pixel 7 / 7p partitions flashing options to custom flash.
    • Improved patching process using boot_patch, add more patch file validations.
    • Check for Magisk backup and trigger Magisk to backup if missing.
    • Add more logging messages for troubleshooting.
    • Code optimization / improvements.
    • Bug Fix #28 Error when opening download link without a device selected.
    • Added set_version script to easily set the product version.
    • Print path of the selected boot to console, for easy copy / paste.