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

[badabing2003]

thanks so much for this tool i will be donating sir thanks for your hard work...my pixel 7 pro just got that much more exciting to own!

Thanks for your consideration.
No donation is necessary, see the main thread OP here.

 

[jmac052002]

Thanks for your consideration.
No donation is necessary, see the main thread OP here.

Sorry I read that and completely forgot well thanks again for your hard work and awesome tool for our pixels!

 

[djcsurf]

The package manager works well, I only uninstalled YT & YT Music but very simple and so easy with this app. Thanks again

 

[krkhaha]

Hi. I know how to flash factory image with Pixel flasher but which option should I select if I'd like to flash full ota?

 

[badabing2003]

Hi. I know how to flash factory image with Pixel flasher but which option should I select if I'd like to flash full ota?

 

[EtherealRemnant]

Went to use Pixel Flasher to update to the new software. Updated it to 4.5.0.0 first. It seems to be failing to make a stock backup for Magisk.

Checking to see if Magisk made a backup of the source init_boot.img
Magisk has NOT made a backup of the source init_boot.img
Triggering Magisk to create a backup ...
Making sure stock-boot.img is found on the phone ...

2022-12-05 14:47:21 ERROR: /data/adb/magisk/stock-boot.img is not found!
Return Code: 1.
Stdout: .
Stderr: ls: /data/adb/magisk/stock-boot.img: Permission denied
.
Aborting run_migration ...

Transfering init_boot.img_1384d5ad.img to the phone in /data/adb/magisk/stock-boot.img ...

2022-12-05 14:47:21 ERROR: Encountered an error.
Return Code: 1.
Stdout: adb: error: stat failed when trying to push to /data/adb/magisk/stock-boot.img: Permission denied
.
Stderr: .
Aborting Backup...

Triggering Magisk again to create a backup ...
Making sure stock-boot.img is found on the phone ...

2022-12-05 14:47:22 ERROR: /data/adb/magisk/stock-boot.img is not found!
Return Code: 1.
Stdout: .
Stderr: ls: /data/adb/magisk/stock-boot.img: Permission denied
.
Aborting run_migration ...


Checking to see if Magisk made a backup of the source init_boot.img
It looks like backup was not made.

I verified that shell has root permissions in Magisk so I don't know what the issue is. It's not a big deal since I don't plan to actually unroot, just thought I would point it out.

It also flashed to both slots even though I had flash to inactive slot checked.

It went fine otherwise though.

 

[BIGWORM]

Went to use Pixel Flasher to update to the new software. Updated it to 4.5.0.0 first. It seems to be failing to make a stock backup for Magisk.



I verified that shell has root permissions in Magisk so I don't know what the issue is. It's not a big deal since I don't plan to actually unroot, just thought I would point it out.

It also flashed to both slots even though I had flash to inactive slot checked.

It went fine otherwise though.

Do I need to have the flags for disabling verity and the other one (name escapes me) checked even though I had them checked when I flashed stock, which I'm running right now?

 

[EtherealRemnant]

Do I need to have the flags for disabling verity and the other one (name escapes me) checked even though I had them checked when I flashed stock, which I'm running right now?

Yes. If you don't disable verity and verification each time you do an OTA, you can't run a custom kernel without wiping your phone to disable them later.

 

[badabing2003]

Went to use Pixel Flasher to update to the new software. Updated it to 4.5.0.0 first. It seems to be failing to make a stock backup for Magisk.



I verified that shell has root permissions in Magisk so I don't know what the issue is. It's not a big deal since I don't plan to actually unroot, just thought I would point it out.

It also flashed to both slots even though I had flash to inactive slot checked.

It went fine otherwise though.

Yes I'm aware of that, there will be fix soon for that.
FYI, this is not an issue, Magisk makes the backup only after applying the Patch, PF actually triggers a backup when creating a Patch to make sure it's there if need be.
That part was not running as su which is why it failed, Magisk would have still created the backup on flashing / reboot

As for flashing to both slots, I would need support.zip to investigate.

 

[EtherealRemnant]

Yes I'm aware of that, there will be fix soon for that.
FYI, this is not an issue, Magisk makes the backup only after applying the Patch, PF actually triggers a backup when creating a Patch to make sure it's there if need be.
That part was not running as su which is why it failed, Magisk would have still created the backup on flashing / reboot

As for flashing to both slots, I would need support.zip to investigate.

Gotcha. Good to know.

I did some investigation in the logs and for some reason the switch never actually changed until I closed and restarted the app (when I last used it in November, I flashed both slots, and now decided to do it the "proper" way going forward). The new log now shows it's flashing the inactive slot now so it shouldn't be a problem going forward.

 

[badabing2003]

Yes. If you don't disable verity and verification each time you do an OTA, you can't run a custom kernel without wiping your phone to disable them later.

Just be aware that the Flags to disable verity / verification are fastboot flags not adb sideload flags.
if you happen to use PF sideload flashing feature instead of flashing firmware, those options will not apply.

I will put out a warning so that it is obvious.
@BIGWORM be aware

 

[badabing2003]

Gotcha. Good to know.

I did some investigation in the logs and for some reason the switch never actually changed until I closed and restarted the app (when I last used it in November, I flashed both slots, and now decided to do it the "proper" way going forward). The new log now shows it's flashing the inactive slot now so it shouldn't be a problem going forward.

I would love to get your support.zip to see what corner case caused it so that I fix it.

 

[banshee28]

For some reason I cant run the latest PixelFlasher-Ubuntu-22.04. I CAN run 4.4.0 and all previous versions fine. I guess maybe there are some new Pre-Req's? I am running the latest glibc:

ldd (Ubuntu GLIBC 2.31-0ubuntu9.9) 2.31

 

[badabing2003]

For some reason I cant run the latest PixelFlasher-Ubuntu-22.04. I CAN run 4.4.0 and all previous versions fine. I guess maybe there are some new Pre-Req's? I am running the latest glibc:

ldd (Ubuntu GLIBC 2.31-0ubuntu9.9) 2.31

Do you get any errors?
Are you on Ubuntu 22.04 or another Linux flavor / version ?

 

[EtherealRemnant]

Just be aware that the Flags to disable verity / verification are fastboot flags not adb sideload flags.
if you happen to use PF sideload flashing feature instead of flashing firmware, those options will not apply.

I will put out a warning so that it is obvious.

Is there a reason to sideload instead of using fastboot?

I would love to get your support.zip to see what corner case caused it so that I fix it.

You've got PM.

 

[badabing2003]

Is there a reason to sideload instead of using fastboot?

If you don't care about rooting, and want to flash quickly, it is much faster than on the phone.
Otherwise no.

You've got PM.

Thanks.

 

[vurtomatic]

Thanks for the new version, just in time for the Dec 5 update.

I've used PixelFlasher twice on my rooted Pixel 7 Pro and have never check disable verity/verification.

If I'm using PixelFlasher for the Dec 5 update with "disable verity/verification" checked, does this mean it's a do-over—my existing data/apps will be wiped clean?

I think I've read that checking disable verity/verification will wipe everything clean but I thought I also read one post that said it won't wipe the phone, just want to confirm.

 

[JakeDHS07]

It's a yes and no situation. Toggling disabled for those doesn't wipe your device. However, you will have to wipe to boot after disabling them

 

[vurtomatic]

It's a yes and no situation. Toggling disabled for those doesn't wipe your device. However, you will have to wipe to boot after disabling them

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.

 

[vurtomatic]

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