Themes / Apps / Mods ðŸ“³ðŸ”¥PixelFlasher for Google Pixel 7 Pro Support Thread.

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
@badabing2003 sad to report the latest v4.5 doesn't launch at all for me. I double-click, the app icon zooms like it's launching, then the Finder window blinks and nothing happens.

I'm on MacOS 10.14.6 (previously I ran PixelFisher on MacOS 12 Monterey). Is there a minimum OS version I need? I'm checking the Github page but don't see mention of restrictions.
You went from Monterey to Mojave?
That's quite old
PF is build on Catalina.

1670282473815.png
 
  • Like
Reactions: vurtomatic

JakeDHS07

Senior Member
This is probably why I'm confused!

Sorry please bear with me. It sounds like it's a do-over then?

Checking "disable verity/verification" in PixelFlasher won't cause the wipe.

But after doing that, my phone will automatically wipe itself when I restart it because of the toggles?

Cos I don't want to have to reinstall and set up everything again.
The phone will not automatically wipe but when it boots up, it will take you to the recovery and say that the data is corrupted and that you must perform a wipe. Once those toggles are disabled, as long as you do that every time you update then you won't have to wipe again
 
  • Like
Reactions: vurtomatic

banshee28

Senior Member
Aug 31, 2010
255
49
Do you get any errors?
Are you on Ubuntu 22.04 or another Linux flavor / version ?
Latest Linux Mint
I double click on the file after I add exec to it as I normally do and nothing happens.

cli I get this:
Code:
[8385] Error loading Python lib '/tmp/_MEI26Pyp9/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEI26Pyp9/libpython3.10.so.1.0)
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
Latest Linux Mint
I double click on the file after I add exec to it as I normally do and nothing happens.

cli I get this:
Code:
[8385] Error loading Python lib '/tmp/_MEI26Pyp9/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEI26Pyp9/libpython3.10.so.1.0)
See my answer here and see if installing the library works.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
New Release:
Dec 05, 2022 v4.6.0 release
  • Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.
  • #39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
  • #39 Do the Magisk backup only when rooted.
  • Decouple OTA sideload from needing factory image.
  • Other minor improvements.
 

banshee28

Senior Member
Aug 31, 2010
255
49
See my answer here and see if installing the library works.
Yea looked into this but did not see this as a simple install, and I would rather not mess with changing the current setup. Would MInt eventually/soon get this update automatically?

I went back to my W laptop and tried the latest version there, and updated to the latest Platform tools 33.0.3, but on reboot it said device not found. I had this before when the Windows drivers were the older version.

I can create a support zip tomorrow if needed.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
Yea looked into this but did not see this as a simple install, and I would rather not mess with changing the current setup. Would MInt eventually/soon get this update automatically?

I went back to my W laptop and tried the latest version there, and updated to the latest Platform tools 33.0.3, but on reboot it said device not found. I had this before when the Windows drivers were the older version.

I can create a support zip tomorrow if needed.
Yes please do.
 

Znil

Senior Member
Sep 6, 2010
61
15
Samsung Galaxy Tab S2
OnePlus 6
Of course,
Just start PF in last state which should have everything already, toggle to (flash to inactive slot) make sure keep data is selected.
Flash
Your main slot will not be touched, the other slot will be flashed and become active.
Moving forward in the future monthly flashes, just flash to inactive slot, this way you always have something good to fallback to.
Is there a way to know if both slots are good? I did flash to inactive slot last time but I don't think my phone switched the active slot. I want to update now to the december update but I don't want to risk losing all data again. @badabing2003
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
Is there a way to know if both slots are good? I did flash to inactive slot last time but I don't think my phone switched the active slot. I want to update now to the december update but I don't want to risk losing all data again. @badabing2003
Your phone is working now, let's assume it is on slot a, do your update to flash to inactive slot.
If everything goes well, your phone should be on slot b and latest version, if your phone gotta back to a, then it would still be on Nov release. That shouldn't happen, but if does, create support.zip and let me take a look.
 
@badabing2003

First of all, thanks for a great tool.

Applying a firmware update to my new (but already manually magisk'ed P7P) for the first time, I ran into an issue though. The first flash (after a successful dry run) failed, I installed the patched version of the 221205 firmware to the inactive slot but the phone would not boot from either slot. A subsequent flash succeeded and brought the phone back

Logfilecut follows, what went wrong/did I do wrong? Thanks.

< waiting for 2A281FDH3009SP > Sending 'super' (5 KB) OKAY [ 0.000s] Updating super partition OKAY [ 1.046s] Resizing 'product_a' OKAY [ 0.007s] Resizing 'system_a' OKAY [ 0.006s] Resizing 'system_dlkm_a' OKAY [ 0.006s] Resizing 'system_ext_a' OKAY [ 0.004s] Resizing 'system_b' OKAY [ 0.004s] Resizing 'vendor_a' OKAY [ 0.019s] Resizing 'vendor_dlkm_a' OKAY [ 0.006s] Resizing 'vendor_b' OKAY [ 0.004s] archive does not contain 'boot_other.img' archive does not contain 'odm.img' archive does not contain 'odm_dlkm.img' extracting product.img (2778 MB) to disk... took 9.792s archive does not contain 'product.sig' Resizing 'product_a' OKAY [ 0.009s] Sending sparse 'product_a' 1/11 (262112 KB) OKAY [ 0.595s] Writing 'product_a' OKAY [ 0.277s] Sending sparse 'product_a' 2/11 (262124 KB) OKAY [ 0.508s] Writing 'product_a' OKAY [ 0.275s] Sending sparse 'product_a' 3/11 (262128 KB) FAILED (Error reading sparse file) fastboot: error: Command failed rebooting to bootloader ... Rebooting into bootloader FAILED (Write to device failed (no link)) fastboot: error: Command failed Sleeping 5-10 seconds ... flashing pf_boot ... Warning: skip copying init_boot image avb footer (init_boot partition size: 0, init_boot image size: 8388608). Sending 'init_boot' (8192 KB) FAILED (Write to device failed (no link)) fastboot: error: Command failed rebooting to system ... Rebooting FAILED (Write to device failed (no link)) fastboot: error: Command failed 2022-12-06 12:36:52 Done! Flashing elapsed time: 160 seconds ------------------------------------------------------------------------------
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
@badabing2003

First of all, thanks for a great tool.

Applying a firmware update to my new (but already manually magisk'ed P7P) for the first time, I ran into an issue though. The first flash (after a successful dry run) failed, I installed the patched version of the 221205 firmware to the inactive slot but the phone would not boot from either slot. A subsequent flash succeeded and brought the phone back

Logfilecut follows, what went wrong/did I do wrong? Thanks.

< waiting for 2A281FDH3009SP > Sending 'super' (5 KB) OKAY [ 0.000s] Updating super partition OKAY [ 1.046s] Resizing 'product_a' OKAY [ 0.007s] Resizing 'system_a' OKAY [ 0.006s] Resizing 'system_dlkm_a' OKAY [ 0.006s] Resizing 'system_ext_a' OKAY [ 0.004s] Resizing 'system_b' OKAY [ 0.004s] Resizing 'vendor_a' OKAY [ 0.019s] Resizing 'vendor_dlkm_a' OKAY [ 0.006s] Resizing 'vendor_b' OKAY [ 0.004s] archive does not contain 'boot_other.img' archive does not contain 'odm.img' archive does not contain 'odm_dlkm.img' extracting product.img (2778 MB) to disk... took 9.792s archive does not contain 'product.sig' Resizing 'product_a' OKAY [ 0.009s] Sending sparse 'product_a' 1/11 (262112 KB) OKAY [ 0.595s] Writing 'product_a' OKAY [ 0.277s] Sending sparse 'product_a' 2/11 (262124 KB) OKAY [ 0.508s] Writing 'product_a' OKAY [ 0.275s] Sending sparse 'product_a' 3/11 (262128 KB) FAILED (Error reading sparse file) fastboot: error: Command failed rebooting to bootloader ... Rebooting into bootloader FAILED (Write to device failed (no link)) fastboot: error: Command failed Sleeping 5-10 seconds ... flashing pf_boot ... Warning: skip copying init_boot image avb footer (init_boot partition size: 0, init_boot image size: 8388608). Sending 'init_boot' (8192 KB) FAILED (Write to device failed (no link)) fastboot: error: Command failed rebooting to system ... Rebooting FAILED (Write to device failed (no link)) fastboot: error: Command failed 2022-12-06 12:36:52 Done! Flashing elapsed time: 160 seconds ------------------------------------------------------------------------------
Thanks,
This is a communication problem between the phone and the computer.
It could be any of the following.
Bad cable, bad USB port, bad drivers, disruption during the flashing, old or buggy Android platform tools, using USB hub ...
People have better success using USB 2.0 port directly on the pc.
 
  • Like
Reactions: Homeboy76
Thanks,
This is a communication problem between the phone and the computer.
It could be any of the following.
Bad cable, bad USB port, bad drivers, disruption during the flashing, old or buggy Android platform tools, using USB hub ...
People have better success using USB 2.0 port directly on the pc.
Ok, so I know where to look in case it happens again (the 2nd flash attempt succeeded and the phone is up).

For the tools, I use SDK Version: 33.0.3-8952118 and the USB-C cable is connected directly to the motherboard.

I assume that "flashing to the inactive slot" is usually the correct way to preserve the current active slot (though I wonder why I could not boot from any of the two slots)?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,845
I assume that "flashing to the inactive slot" is usually the correct way to preserve the current active slot (though I wonder why I could not boot from any of the two slots)?
Yes flashing to inactive slot is usually the correct way.
If you supply support.zip file, I can take a look as to why you couldn't boot.
 

otonieru

Senior Member
May 7, 2011
3,553
2,276
Djakarta
Well, my last Pixel was 2XL before adopted the 7 Pro last month,

Glad to find such an easy tool, flash everything smoothly while retaining root & everything. Kudos
 

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.
  • 42
    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.