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

[mruno]

I'm new to the pixel family. Root worked very well (wihtour pixel flasher). Now I stumbled over a question which is rather related to the PF but maybe can be answered here anyway.
How does the beta opt-on or opt-out procedere work with focus on data loss.
Is it possible, coming from stock rom, to simply flash the current beta to opt-in and opt-out with the next stable release without full wipe. I read that in the end of the beta there will be the chance to come to the stable release without wiping data.

Shortend question: Can I switch between stable and beta release (each way) wihtout data loss?

PS. @badabing2003 congrats and thank you for such a master piece of software and your unstopable support.

Check out the verbiage "Once you're enrolled" at the bottom of this page: https://www.google.com/android/beta#devices

 

[Bestiole222]

Hi to everyone, I'd like to disable verity and verification on my phone to install custom kernel and I saw that there's an option in pixelflasher. Do I have to do this operation each time I install a ROM update or it's only one time? Because I read that these operation needs a wipe data.
Has someone install a custom rom patched with pixel flasher?
Thanks in advance for your answers ans thanks a lot for this great tool.

 

[badabing2003]

Hi to everyone, I'd like to disable verity and verification on my phone to install custom kernel and I saw that there's an option in pixelflasher. Do I have to do this operation each time I install a ROM update or it's only one time? Because I read that these operation needs a wipe data.
Has someone install a custom rom patched with pixel flasher?
Thanks in advance for your answers ans thanks a lot for this great tool.

I believe you have to select those options every time you flash, don't quote me on this as I don't use custom ROM, if I'm not mistaken the wipe is only when you switch from one state to the other, again this is pure speculation, I'll let someone who flashes custom ROM speak up.

 

[bao_gg]

My Pixel 7 is on TQ1A.221205.011 build. I just unlocked the bootloader so all the user data are gone. Now I want to use PF to root the phone. So on PF I can browse to find the platform tools which version is 33.0.3 and factory image (panther-tq1a.221205.011-factory-ab58bb03.zip). I processed the zip file and saw there is a boot.img file showed up. I think for P7 we should use ini.boot.img. Is it OK to go ahead? And do I need to flash into inactive slot for safety reason?
Also I haven't installed Magisk yet. Is there a option that I can get Magisk Delta? My final purpose is to root the phone and then get 32-bit app supported.

 

[badabing2003]

My Pixel 7 is on TQ1A.221205.011 build. I just unlocked the bootloader so all the user data are gone. Now I want to use PF to root the phone. So on PF I can browse to find the platform tools which version is 33.0.3 and factory image (panther-tq1a.221205.011-factory-ab58bb03.zip). I processed the zip file and saw there is a boot.img file showed up. I think for P7 we should use ini.boot.img. Is it OK to go ahead? And do I need to flash into inactive slot for safety reason?
Also I haven't installed Magisk yet. Is there a option that I can get Magisk Delta? My final purpose is to root the phone and then get 32-bit app supported.

where do you see boot.img ?
In the list you see boot.img?
or just the label to the left.
Select the boot and the console should show you the path and filename. PF knows that it needs to use init_boot with P7

Yeah, flash to inactive.
There is an option to install Magisk Alpha and Magisk Delta are supported, and they can be installed all from PF.
Make sure you only install one, and when installing, make sure you first unhide magisk, if you have one hidden.
After installation if PF says Magisk not found, just update the package name in the PF configuration section (Magisk delta has different package name, soon to be released next PF should do this automatically)

 

[bao_gg]

Thank you badabing2003 for help.
I mean the file is the zip file with SHA1 and Package Fingerprint.
The left there is "select a boot.img".

 

[bao_gg]

Installed Delta first but PF did not detect it as you said the package name is different.
And then choose stable version everything works like a charm.
One more thing: Open magisk app I just see "App 25.2 installed". Above that there is a Magisk logo but shows Installed N/A.

 

[badabing2003]

Installed Delta first but PF did not detect it as you said the package name is different.

You didn't have to change it if you wanted the Delta, all you had to do is go to pF configuration and enter the Delta's package name io.github.huskydg.magisk

One more thing: Open magisk app I just see "App 25.2 installed". Above that there is a Magisk logo but shows Installed N/A.

Did you create a patched boot using magisk and flashed that? or you just installed Magisk Manager?

 

[bao_gg]

My bad. I installed the magisk and then forgot to flash the patched file.
After flashing pixel phone, at first it says system is corrupt and restart automatically and then got stuck on Goolge logo.

 

[bao_gg]

Tried to recover the device by hold power key for 30s.
I think the problem is the magisk is not fully installed because the Magisk logo beside the "Reboot to bootloader" is greyed out.

 

[badabing2003]

Tried to recover the device by hold power key for 30s.
I think the problem is the magisk is not fully installed because the Magisk logo beside the "Reboot to bootloader" is greyed out.

Please provide a support.zip file from PF help menu and I'll take a look.
The Main thread and the Github are linked in the OP, both of which has the usage details.

 

[bao_gg]

Thanks.

 

[badabing2003]

Thanks.

You had never updated your phone previously?
Just flash to both slots and you should be fine.
Why not go with January update? or better yet on Monday with the February drop?

 

[bao_gg]

I planned using PF to update Jan patch. Now I would wait for Feb one.
According to the main thread, we need to grant root permission to shell in Magisk. But I can't find this option.
Thank you.

 

[badabing2003]

New Release:
Feb 05, 2023 v4.7.0 release

• Added Magisk Backup Manager:
  • List all Magisk backups currently on the device.
  • Highlight the one that is backup of the current installed version.
  • Delete backups.
  • Manually add backup from PC.
  • Auto Backup: PixelFlasher figures out what needs to be backed up, and if it finds it on the PC, it creates the backup.
• Added Reset on Magisk Manager package name setting to reset to default: com.topjohnwu.magisk
• Linux / Mac build.sh now switches to the PixelFlasher folder if it is run from elsewhere.
• Magisk installer improvements:
  • When installing Magisk Alpha or Delta, PixelFlasher updates the configuration to match the package name to the respective Magisk package.
  • Magisk installer window displays the package name.
  • You can now copy to clipboard, the download URL and package ID.
• Magisk Manager columns are now wider for better readability.
• Package Manager improvements:
  • Added Search / Filter option.
  • Show count of filtered packages.
  • Application Name (label column).
  • "Get Application Names" Button to resolve all package application names. This is a slow process, hence PixelFlasher caches them.
  • Button to download (pull) APKs from the device. (Multiple downloads in one shot is also supported).
  • Other under the hood improvements.
• When selecting a firmware or ROM file, sha256 is printed to console and displayed on hover, to validate if it matches the published sha256.
• More verbose logging that helps with troubleshooting.
• Double click on "ADB Connected Devices" to invoke adb kill-server which is handy at times, specially when dealing with Wifi ADB.
• Moved existing links under Help Menu | Links, and added few more handy links.
• Added timestamp to support.zip filename.
• On request, spinning cursor with text "Please be patient ..." is now displayed in red.
• Flashing to inactive slot is now in basic configuration instead of advanced configuration.
• Preparation work for version 5.0 DB improvements.

 

[bjevers]

@badabing2003 I'm having an issue and not sure what the problem is. I first flashed the latest update to my Pixel 7 Pro and it went fine. Next, I tried to update just a normal Pixel 7, but his time it fails with a message saying it can't find the Magisk patched boot image. Yes, I processed and patched the panther boot image. I have attached a support zip. I had the same issue last month and I think I fixed it by deleting the PixelFlasher folder under AppData\Roaming. I will do that now to verify and update this post.

EDIT: Nope, deleting the folder didn't work. Not sure what I did last time.

EDIT 2: Now I remember, I have 2 Pixel 7 devices (1 for each of my daughters). I plugged in the other one and everything went fine. And I used that patched image to flash the second Pixel 7. Just not sure why the one doesn't work for patching. They both have the same version of Magisk.

 

[badabing2003]

@badabing2003 I'm having an issue and not sure what the problem is. I first flashed the latest update to my Pixel 7 Pro and it went fine. Next, I tried to update just a normal Pixel 7, but his time it fails with a message saying it can't find the Magisk patched boot image. Yes, I processed and patched the panther boot image. I have attached a support zip. I had the same issue last month and I think I fixed it by deleting the PixelFlasher folder under AppData\Roaming. I will do that now to verify and update this post.

EDIT: Nope, deleting the folder didn't work. Not sure what I did last time.

You have Magisk hidden, hence no Magisk Manager, just a stub.
And you have not granted adb shell access, hence root is not allowed.
You can't create a patch.
Best to grant root access, but if for whatever reasons you don't want to, then unhide Magisk before patching so that full Magisk Manager is available to create a patch.

I'd add login in the next version to block you from attempting to patch when your phone is in this state.

 

[bjevers]

You have Magisk hidden, hence no Magisk Manager, just a stub.
And you have not granted adb shell access, hence root is not allowed.
You can't create a patch.
Best to grant root access, but if for whatever reasons you don't want to, then unhide Magisk before patching so that full Magisk Manager is available to create a patch.

I'd add login in the next version to block you from attempting to patch when your phone is in this state.

Hmm, I have it hidden on all 3 phones and it worked fine on 2 of them.

Ok, I think I figured it out. I have the Magisk package name set to the phone that didn't work in the advanced settings and since it couldn't find that on 2 of the phones, it patched with the Magisk included with PF. Correct?

 

[badabing2003]

Hmm, I have it hidden on all 3 phones and it worked fine on 2 of them.

Ok, I think I figured it out. I have the Magisk package name set to the phone that didn't work in the advanced settings and since it couldn't find that on 2 of the phones, it patched with the Magisk included with PF. Correct?

No because you have not granted root access to adb shell.
See Basic Usage point 2.

 

[praveenpc]

I have windows 7 with 32 bit. It shows error .." Check your computer's system information to see whether you need a x86 or x64 version....."