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

[letmedanz]

Thank you so much for your work

 

[Misterxtc]

Why the heck did I wait so long to use this? This is the easiest way to update by far. Thanks much.

 

[schmeggy929]

Ok, so I updated using PF, rebooted and made sure everthing worked great. So I figured i try to get inactive up to same version. Same procedure as before. selected patched init_boot.img and checked flash to inactive slot. Flash went well no errors. Rebooted phone and after colorful google boot text phone goes black and nothing. Manually reboot and same thing. rebooted again and switched slots, phone boots to colorful Google text and goes black. Then decided to reflash with non-root firmware. Im back on Slot A and everything is working. Flashed patch init-boot.img and back to root.
So any idea why after successfully flashing latest firmware and then flashed same firmware to inactive slot and doesn't boot?

 

[badabing2003]

Ok, so I updated using PF, rebooted and made sure everthing worked great. So I figured i try to get inactive up to same version. Same procedure as before. selected patched init_boot.img and checked flash to inactive slot. Flash went well no errors. Rebooted phone and after colorful google boot text phone goes black and nothing. Manually reboot and same thing. rebooted again and switched slots, phone boots to colorful Google text and goes black. Then decided to reflash with non-root firmware. Im back on Slot A and everything is working. Flashed patch init-boot.img and back to root.
So any idea why after successfully flashing latest firmware and then flashed same firmware to inactive slot and doesn't boot?

support.zip file (from the help menu) would go a long way towards explaining the why.
Please submit one and I'll take a look at it.

 

[banshee28]

I would really like to be able to get the latest PF to work with Linux Miint, but cant get the pre-req Python setup. Any easy way to get this working? I guess the latest Mint still does not/wont have the req'd Python?

 

[Fishawy]

I only used PF once to root the phone when I first got it almost 4 months ago, and been updating/rooting using the Android Flash Tool and commands.

I'm now wanting to update and retain root using PF, is the process different? Currently reading through the main thread and Github, and wondering if there's a beginner-friendly summary on how to do that.

Edit: All good. Updated using PF, easy process. Thanks Dev.

 

[schmeggy929]

support.zip file (from the help menu) would go a long way towards explaining the why.
Please submit one and I'll take a look at it.

Here ya go, thank you for all you do and a great app.

 

[Wmateria]

Can i go back to January Patch from February?

 

[badabing2003]

Ok, so I updated using PF, rebooted and made sure everthing worked great. So I figured i try to get inactive up to same version. Same procedure as before. selected patched init_boot.img and checked flash to inactive slot. Flash went well no errors. Rebooted phone and after colorful google boot text phone goes black and nothing. Manually reboot and same thing. rebooted again and switched slots, phone boots to colorful Google text and goes black. Then decided to reflash with non-root firmware. Im back on Slot A and everything is working. Flashed patch init-boot.img and back to root.
So any idea why after successfully flashing latest firmware and then flashed same firmware to inactive slot and doesn't boot?

You started with the device on slot a and January build
You updated to February build, to active slot with the following options (why are you disabling verity / verification, even though that is not an issue)

Custom Flash Options:   True
Disable Verity:         True
Disable Verification:   True
Flash Both Slots:       False
Force:                  False
Verbose Fastboot:       False
Temporary Root:         False
Flash To Inactive Slot: False

Everything went well and you booted to slot a February build

Selected Device on 2023-02-06 20:12:25:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              a
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230205.001.D2
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9288096
    Magisk Manager Version:         
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:             
    Magisk Modules:
        AOSP Mods (Full version)            enabled   2.4.1
        Powerhint_Cheetah                   enabled   v4
        Themer                              enabled   1.2.3B2
        ViPER4Android Reverse Engineered    enabled   v0.1.0
        JamesDSP Manager                    enabled   v4.6 (8-4-2022)
        Audio Modification Library          enabled   v4.2
        Font Manager                        enabled   v5.6.45
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0
        Zygisk - LSPosed                    enabled   v1.8.6 (6712)

Then you decided to flash again this time to inactive slot (ie b) with the following options

Custom Flash Options:   True
Disable Verity:         True
Disable Verification:   True
Flash Both Slots:       False
Force:                  False
Verbose Fastboot:       False
Temporary Root:         False
Flash To Inactive Slot: True

Again everything went well and the system booted properly to slot b

Selected Device on 2023-02-06 20:17:04:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230205.001.D2
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9288096
    Magisk Manager Version:         
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  25.2:25200
    Magisk Config SHA1:             
    Magisk Modules:
        AOSP Mods (Full version)            enabled   2.4.1
        Powerhint_Cheetah                   enabled   v4
        Themer                              enabled   1.2.3B2
        ViPER4Android Reverse Engineered    enabled   v0.1.0
        JamesDSP Manager                    enabled   v4.6 (8-4-2022)
        Audio Modification Library          enabled   v4.2
        Font Manager                        enabled   v5.6.45
        Systemless Hosts                    enabled   1.0
        Universal SafetyNet Fix             enabled   v2.4.0
        Zygisk - LSPosed                    enabled   v1.8.6 (6712)

Not sure why, but you tried to change the active slot to a again

Rebooting device REDACTED to bootloader ...
Waiting 5 seconds ...
Setting active slot to slot [a] for device 29141FDH3001H9 ...

Selected Device on 2023-02-06 20:17:34:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              a
    Device Mode:                     f.b
    Device Unlocked:                 True

Once b becomes active and bootable, a becomes unbootable, this is expected, only one slot is bootable, (see earlier posts if you're interested to know why this happens)
Then while in bootloader mode, you switched to b, and flashed to inactive slot (that would be a)
That worked, and you now you are on a.

I would really like to be able to get the latest PF to work with Linux Miint, but cant get the pre-req Python setup. Any easy way to get this working? I guess the latest Mint still does not/wont have the req'd Python?

Have you tried to use the published Kali build, and or Ubuntu 22.04 built?
What happens? what errors do you get?
What version of Mint do you have?
Have you tried to build from source?

Can i go back to January Patch from February?

You can try, the worst that will happen is that it won't work and you will go back to February.
I don't have much experience with reverting, I only attempted once to revert to an older firmware and it didn't work for me, but that doesn't mean that it won't work for you either.
Others might chime in with their experiences.
Curious why you want to go back

 

[schmeggy929]

Once b becomes active and bootable, a becomes unbootable, this is expected, only one slot is bootable, (see earlier posts if you're interested to know why this happens)
Then while in bootloader mode, you switched to b, and flashed to inactive slot (that would be a)
That worked, and you now you are on a.



Thank you for that info.

 

[Slim2none4u]

Can i go back to January Patch from February?

I've never had a problem going back to any firmware. Other than the time thaey added the anti-rollback to the pixel 6 on that one update one month which i cant remember which one it was. Other than that one time, I've always been able to roll back on all my Pixel phones.

 

[Lughnasadh]

You can try, the worst that will happen is that it won't work and you will go back to February.
I don't have much experience with reverting, I only attempted once to revert to an older firmware and it didn't work for me, but that doesn't mean that it won't work for you either.
Others might chime in with their experiences.
Curious why you want to go back

Flashing back to an older firmware shouldn't be a problem, in my experience.

 

[banshee28]

Have you tried to use the published Kali build, and or Ubuntu 22.04 built?
What happens? what errors do you get?
What version of Mint do you have?
Have you tried to build from source?

Yep, tried both and same results. I know you helped before since this is related to Python but I have not been able to fix it and figured since my Mint OS is updated at latest and would work.

[34124] Error loading Python lib '/tmp/_MEIOeO16o/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIOeO16o/libpython3.10.so.1.0)

Python 2.7.18

 

[badabing2003]

Yep, tried both and same results. I know you helped before since this is related to Python but I have not been able to fix it and figured since my Mint OS is updated at latest and would work.

[34124] Error loading Python lib '/tmp/_MEIOeO16o/libpython3.10.so.1.0': dlopen: /lib/x86_64-linux-gnu/libm.so.6: version `GLIBC_2.35' not found (required by /tmp/_MEIOeO16o/libpython3.10.so.1.0)

Python 2.7.18

Python 2.7.8?

The library it needs is python 3.10
Have you tried uninstalling python 2.7 and installing python 3.10?

 

[banshee28]

Python 2.7.8?

The library it needs is python 3.10
Have you tried uninstalling python 2.7 and installing python 3.10?

I think I did try to install python 3 but had issues. Will have to look into it more.

 

[Nekromantik]

I updated to latest version on Windows and used it to flash Feb update but I lost root
re flashed patched boot img and got root back

 

[Wmateria]

I've never had a problem going back to any firmware. Other than the time thaey added the anti-rollback to the pixel 6 on that one update one month which i cant remember which one it was. Other than that one time, I've always been able to roll back on all my Pixel phones.

I was able to go back to the January Patch again from February, thanks.

Wallet works again, and I no longer have battery drain with the latest KiriSakura. I had a weird experience with February Patch, had the latest Magisk with SafetyNet passed.. downloaded Yasnac, to double check and everything passed., but no matter what I do... Wallet did not worked and it was always flagging me that my phone was rooted, even with Zigisk enabled. I tried also Magisk Hide,, it did not worked either.

Whatever Google did, broke the latest Magisk 25.2, and battery drain is bad with the latest February Patch, even with a clean install.

 

[Slim2none4u]

I updated to latest version on Windows and used it to flash Feb update but I lost root
re flashed patched boot img and got root back

You most likely either did not patch the boot.img before flashing or you didn't select the patched boot.img before flashing. When done correctly, the update process, while keeping root, is flawless.

 

[Slim2none4u]

I was able to go back to the January Patch again from February, thanks.

Wallet works again, and I no longer have battery drain with the latest KiriSakura. I had a weird experience with February Patch, had the latest Magisk with SafetyNet passed.. downloaded Yasnac, to double check and everything passed., but no matter what I do... Wallet did not worked and it was always flagging me that my phone was rooted, even with Zigisk enabled. I tried also Magisk Hide,, it did not worked either.

Whatever Google did, broke the latest Magisk 25.2, and battery drain is bad with the latest February Patch, even with a clean install.

I am not having any of these issues on my P7P. Everything went smooth and banking/Gpay still work fine. Battery hasn't changed and i also use Kirisakura kernel.

 

[badabing2003]

I updated to latest version on Windows and used it to flash Feb update but I lost root
re flashed patched boot img and got root back

You shouldn't have lost root, a simple oversight of selecting the stock boot instead of the patched boot after creating a patch and before hitting the flash button could cause that.
You'd think you wouldn't make a silly mistake like that, well I've got news for you, I did that mistake and lost root, and wondered if I had introduced a regression in the latest release, only checking the logs exposed my shortcomings.

I can take a look at you logs if you want.
Another possibility is that the last step in flashing is actually flashing the patch, if anything goes wrong during that, the phone will remain in stock state, not that something should go wrong, but anything is a possibility.