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

[krakout]

Sooo the first preview of A14 dropped. Who's gonna try flashing it?

 

[Slim2none4u]

Sooo the first preview of A14 dropped. Who's gonna try flashing it?

I am flashing now. Will report back.
A NOTE!!
When using PF to do this it gives a warning about the Phone (mine being Bramble 4a5G) that you are flashing, in my case bramble-beta.

Edit: Added Support zip just for info.

Edit2: All went well and maintained root. I did disable all modules before hand.

This was all just a test to see if it works.

PLEASE DO NOT TAKE THIS AS A GUIDE!

 

[krakout]

I am flashing now. Will report back.
A NOTE!!
When using PF to do this it gives a warning about the Phone (mine being Bramble 4a5G) that you are flashing, in my case bramble-beta.

Crossing fingers for you

Rooted?

 

[miimaa]

Thanks for the info! I will try again tomorrow.

And thank you very much for your good work! I'm an old school recovery-flasher since Android 2.3. Adb and coding is cryptonite to me and that's why your software has been a lifesaver for me.

I updated to the new version and everything went smoothly.

I also managed to keep the root this time. No user errors.

 

[Isijos1]

Hi. Sorry if it has already been mentioned above and for my English. If I'm in stable, can I flash a beta with PF? If so, would I lose data and/or root? Thanks so much!!

 

[Slim2none4u]

Hi. Sorry if it has already been mentioned above and for my English. If I'm in stable, can I flash a beta with PF? If so, would I lose data and/or root? Thanks so much!!

Read the post above yours.
Rule number 1 READ READ READ

 

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

So looking at this further, it appears I have 3.8 installed already.

Python 3.8.10

$ which python3
/usr/bin/python3

Would this be compatible?

 

[badabing2003]

So looking at this further, it appears I have 3.8 installed already.

Python 3.8.10

$ which python3
/usr/bin/python3

Would this be compatible?

Could be, but am not sure.
If you attempt to build it with 3.8 it could work.

 

[Nekromantik]

would be good to have option to restore stock kernel inc other partitions when you swap kernels.
instead of flashing manually or just doing a full reflash

 

[badabing2003]

would be good to have option to restore stock kernel inc other partitions when you swap kernels.
instead of flashing manually or just doing a full reflash

I'm not sure I follow.
How would you do it manually, and how will the tool figure out your intent and do it for you?
If you're flashing multiple partitions, which by the way are in the image.zip file, and you want to be selective, it's going to take a lot more time, extracting those, and the flashing one by one.
flashing image.zip would be the easier / faster and clearer way, besides it does not require additional UI that could confuse users that don't need such advanced features.

Did I understand the request correctly?

 

[banshee28]

On my Windows install using 4.7 and the lattest Platform tools 33.0.3, it starts off fine but when the phone reboots it shows unable to detect device. Its rooted and when connected to the PC all adb cmd's work perfectly.

Also, even though its rooted and working fine, it shows the "x" vs check-mark under ADB Connected Devices status. Could that be the issue?

 

[banshee28]

Update: I guess I lost the option to allow root access to shell during the last update and never realized it. Added that and now it shows up as "rooted".
However flashing still shows "No device is seletectd" after rebooting. I know I had this issue before trying to remember what the solution was.

 

[Nekromantik]

I'm not sure I follow.
How would you do it manually, and how will the tool figure out your intent and do it for you?
If you're flashing multiple partitions, which by the way are in the image.zip file, and you want to be selective, it's going to take a lot more time, extracting those, and the flashing one by one.
flashing image.zip would be the easier / faster and clearer way, besides it does not require additional UI that could confuse users that don't need such advanced features.

Did I understand the request correctly?

Yes that is true. You understood fine. Guess only option is manually doing it as it depends on what partitions the kernel changed.

 

[Dave_247]

Just a heads up/warning not to use the new version 34 of platform tools, at for whatever reason Goole seems to have done something funky, as it seems to skip booting into fastbootd and tries to flash the final few petitions without it, except it can't so it fails and will just lead to a bootloop.

 

[badabing2003]

Yes that is true. You understood fine. Guess only option is manually doing it as it depends on what partitions the kernel changed.

I can't think of any way it adding smarts to PF to select the right partitions, the only future potential improvement I can see is that have UI similar to Odin, listing all the images in a file, or should I be listing partitions on the device?
And allowing you to select multiple of them.
Although a minor improvement, I'm not sure if it is worth the trouble.
If this interests you I suggest you submit feature request at GitHub.
It won't be a priority, but it could get done one day.

Just a heads up/warning not to use the new version 34 of platform tools, at for whatever reason Goole seems to have done something funky, as it seems to skip booting into fastbootd and tries to flash the final few petitions without it, except it can't so it fails and will just lead to a bootloop.

Thanks for the heads up, I'll keep an eye.
Are these widespread issues or isolated cases?

 

[Blade22222]

Just a heads up/warning not to use the new version 34 of platform tools, at for whatever reason Goole seems to have done something funky, as it seems to skip booting into fastbootd and tries to flash the final few petitions without it, except it can't so it fails and will just lead to a bootloop.

I also had this issue yesterday. I think they mistakenly released it as there is no patch notes for it.

 

[badabing2003]

Update: I guess I lost the option to allow root access to shell during the last update and never realized it. Added that and now it shows up as "rooted".
However flashing still shows "No device is seletectd" after rebooting. I know I had this issue before trying to remember what the solution was.

You didn't lose that option,
You never had it set in the first place.

Looks at these logs, check the dates and the line about "Device is Rooted"

Selected Device on 2023-02-06 23:00:03:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Selected Device on 2023-02-10 19:35:24:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Selected Device on 2023-02-10 19:38:49:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Selected Device on 2023-02-10 19:41:18:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Selected Device on 2023-02-10 19:44:11:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Selected Device on 2023-02-10 19:47:45:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk

Load time: 11 seconds

Selected Device on 2023-02-10 19:51:53:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                False
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk


2023-02-10 20:00:03 Scanning for Devices ...
1 Device(s) are found.

Selected Device on 2023-02-10 20:00:04:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  831a398b:25206
    Magisk Config SHA1:              5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
    Magisk Modules:
        De-bloater                          enabled   v1.0

Selected Device on 2023-02-10 20:05:37:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  831a398b:25206
    Magisk Config SHA1:              5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
    Magisk Modules:
        De-bloater                          enabled   v1.0
        Systemless Hosts                    enabled   1.0
    

Flash Mode:             dryRun

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

Selected Device on 2023-02-10 20:07:50:
    Device ID:                       REDACTED
    Device Model:                    cheetah
    Device Active Slot:              b
    Device Mode:                     adb
    Device is Rooted:                True
    Device Build:                    TQ1A.230105.002.A1
    Device API Level:                33
    Device Architecture:             arm64-v8a
    Device Bootloader Version:       cloudripper-1.0-9231809
    Magisk Manager Version:          831a398b:25206
        Checked for Package:         com.topjohnwu.magisk
    Magisk Version:                  831a398b:25206
    Magisk Config SHA1:              5a03a7d73f5b7a2d4fa11ea3615945be8475dcc1
    Magisk Modules:
        De-bloater                          enabled   v1.0
        Systemless Hosts                    enabled   1.0

On 2023-02-10 20:00:04 you must have enabled that option, but you did not flash after that (you only did a dry run) to say that you lost it after flashing, that should not happen at all, and all this time I have never seen that happen.

Also keep in mind, after flashing is completed or anytime you reboot from fastboot to System PF will always show no device is detected / selected.
That is because, for PF to detect that a device is connected, it needs to keep the script running and constantly doing adb check, and the reboot could take time, meanwhile you would be under the impression that flashing is not completed and PF will appear hung.
It is by design that as soon as flashing is completed, PF clears the device selection and reports that flashing is complete.
If you want to select your device again, you should do a scan and then select the device.

 

[Dave_247]

Thanks for the heads up, I'll keep an eye.
Are these widespread issues or isolated cases?

I only know it to occur on the Pixel 7 Pro as that is the device I own, but judging from the release notes that Google did put out and the nature of the issue, I suspect it will likely affect any device that relies on rebooting to the userspace fastbootd as part of the update process, though I have no idea what (if any) other devices also require this.

For what it's worth I've created an issue in Google's issue tracker in the hope that it will be picked up and fixed sooner by someone who has a much deeper knowledge of Android then I.

Google Issue Tracker

issuetracker.google.com

 

[rexsmith9886]

flashed February patch over jan patch and magisk delta root was retained including data on pixel 7

all went good. thanks

I use flash on both slots for dirty upgrade without formatting. I also tick disable verity and verification across every flash. is it fine to do ?

 

[Guido83]

I could not flash the latest image to my P7Pro. Always got this error:

Sending sparse 'super' 1/1 (4194303 KB)            FAILED (Sparse file is too large or invalid)

The phone did not boot anymore. The only way to get it booting again was to use the website flasher from google