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

[badabing2003]

@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.

 

[JakeDHS07]

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

 

[vurtomatic]

You went from Monterey to Mojave?
That's quite old
PF is build on Catalina.

View attachment 5778269

Oof ok. I no longer have the previous laptop so I'm now on my 10-yr old MacBook Air that's on Mojave :-/

I'll try @roirraW "edor" ehT 's guide!

 

[banshee28]

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:

[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]

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:

[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]

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]

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]

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.

 

[banshee28]

Just used 4.4.0 on Linux, worked perfectly! All updated. Would prefer to keep using Linux build.

 

[rage302]

A short feedback:
Just updated my P7Pro from TD1A.221105.001 (Nov) to TQ1A.221205.011 (Dec) with keeping verity/verification disabled and persisting root using PixelFlasher 4.6.0.0 -> NO PROBLEMS, ALL GOOD!

Thank you.

greetings rage

 

[Beefheart]

Another update, another flash using Pixel Flasher with zero issues.

I don't know why anyone would use anything else.

 

[Znil]

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]

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.

 

[akxak]

@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]

@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.

 

[akxak]

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]

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.

 

[Znil]

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.

It worked, thanks a lot.

 

[otonieru]

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

 

[badabing2003]

New Release:
Dec 06, 2022 v4.6.1 release

• #40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.
• Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.
  Credit to gecowa6967 at XDA.