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

Search This thread

AllusionPDX

Senior Member
Jan 10, 2012
138
27
Google Pixel 7 Pro
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
 

JakeDHS07

Senior Member
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
Those options are already part of the application if you are using Expert mode 👍
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
Like @JakeDHS07 said, these options are already in PixelFlasher.

Don't take this the wrong way, but if you just came back over from iPhone and admittedly are a bit out of date, you shouldn't be asking for features without understanding what exactly you're asking for.
For example you say,

if you read the post on the krisakura kernel ...

And you expect me to hunt for Krisakura Kernel post and learn the process? For something you're not willing to understand? You haven't even linked the post.
I'm sorry but this only tells me that you don't want to put any effort in helping yourself, you just expect it to be delivered on a platter.

I suggest the following.
If you want to flash a Krisakura Kernel, go over that post, understand the steps / the process, apply it to your phone, if you have any problems regarding that, ask them in that forum.
Repeat this few times, then identify the pain points, the parts where you think if it were automated would save you time and be less error prone.
Come back and explain your workflow, and describe how adding such and such feature into PF would ease that pain point and I would seriously consider it if it is feasible.

This is from the OP in the main thread.

1668803698944.png


Tools like PF could be used by the following types of users.
  • People who know the process, know exactly what goes into modding the phone manually, and want to save time and effort repeating the same tedious process each and every time they want to flash / mod.
    And if anything goes wrong, they know how to recover, or ask pertinent contextual questions.
    This is the main audience of PF, people in this group not only are capable of understanding the steps, but are also in position to help others.
  • People new to the game, that find the initial learning curve steep to overcome, but are willing to learn, comparing the console output to the manual steps outlined in the guides and trying to make sense of the workflow / steps and learning along the way. People in this group would eventually become proficient and graduate to the first group.
  • People who don't care about learning, they are merely lazy leeches that just want things to be done for them. PF is not intended for this type of users, if I wanted to attract this group I would have charged for the program.
  • People who are incapable of learning / following guides, although I don't believe that this group exists at XDA, but if there are rare few of them, then I respectfully suggest that modding is not for them.
 
Thanks for chiming in.
This is more targeted to @AllusionPDX and others who request such auxiliary features.

A stated previously, I don't have the necessary understanding of the process / tools involved in achieving ... whatever (I say whatever because honestly I don't even know what we're doing, there is a mention of Powerhint which apparently is a Magisk module, so why PF's Magisk Module manager is not used to enable / disable it? and if it is used, what exactly it is missing?)

Yeah I can research, dig and learn, which would require my time and effort, which is not in abundance.
That is why I asked for manual steps.

I see mention of "just restore from backup instead of having to re-configure each time"
What am I backing up? what are the backups? in what format? where are they persisted? Are they already previously made or PF has to create them? at what point in the process the backup is made / restored?
You can see where this is going.

"Kernel Flashing Apps like EXKM," which suggests that there are other tools, why this tool and not others? Questions about limitations / and usefulness to others.

Automating / programming something requires detailed understanding of the precise process of all possible paths.
I'm not against adding features that could help XDA members, if this is something doable and within the reasonable scope of PF's usage, however simply asking for such features without providing the required details is not going to motivate me in looking into it.

Lastly, I don't intend to flash Kernels and experiment on my main driver, so even if I'm inclined to add such feature, I wouldn't be able to test it and would require the commitment of the requester not only to provide the details I ask, but also to do the testing, which of course comes with risks.
Just my opinion, those aren't necessary. Magisk has to be set up before it can flash any mods. And Kernels are just as easy to flash with a Flash Manager, like EX, et al.

Last night, I soft-bricked my phone flashing a Substratum Theme (Still not sure what happened) and had to do a Factory Reset, friggin lying in bed at 3AM, but once I did, came to my Computer, rebooted to Windows, started the Flash Tool and in 3 minutes, I was up and running.

Sadly, I hadn't done a Swift Backup or a Storage Backup in a week so I'm gonna lose some stuff and restoring thousands of pics is taking for-EVER, but the tool works perfectly as it is!
 
  • Sad
Reactions: badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
Just my opinion, those aren't necessary. Magisk has to be set up before it can flash any mods. And Kernels are just as easy to flash with a Flash Manager, like EX, et al.

Last night, I soft-bricked my phone flashing a Substratum Theme (Still not sure what happened) and had to do a Factory Reset, friggin lying in bed at 3AM, but once I did, came to my Computer, rebooted to Windows, started the Flash Tool and in 3 minutes, I was up and running.

Sadly, I hadn't done a Swift Backup or a Storage Backup in a week so I'm gonna lose some stuff and restoring thousands of pics is taking for-EVER, but the tool works perfectly as it is!
Sorry to hear about your troubles, and happy to learn that the tool is doing its job well.
Thanks
 
  • Like
Reactions: HipKat
Sorry to hear about your troubles, and happy to learn that the tool is doing its job well.
Thanks
One thing I just thought of. I HOPE I didn't just waste a few hours restoring things because I had Don't Wipe selected with disable Verity and Verification, coming from a Factory Rest. Gonna check that real quick....

EDIT: Nope, starting over......
Lessons learned
 
Last edited:
  • Sad
Reactions: badabing2003

chaos193

Member
Jul 5, 2011
16
9
Haven't rooted my phone since 2014, a Oneplus One. Coming back to this I was very reluctant to root my phone given all the steps needed. Tried using PixelFlasher. On first try, unlocked the booloader, patched the init.boot using Magisk, gain root all while disabling verity and verification. Not once a bootloop happened. Dev you have no idea how much I appreciate this tool. Thanks a lot.
 
Haven't rooted my phone since 2014, a Oneplus One. Coming back to this I was very reluctant to root my phone given all the steps needed. Tried using PixelFlasher. On first try, unlocked the booloader, patched the init.boot using Magisk, gain root all while disabling verity and verification. Not once a bootloop happened. Dev you have no idea how much I appreciate this tool. Thanks a lot.
I was in the same boat and came away with the same sense of gratitude!
 

Light_Wing

Senior Member
Has anyone been using PF to successfully flash custom roms? I've heard there's some available "out in the wild" :cool:
yes, if GrapheneOS is considered custom rom :)

the GraphineOS docs say to lock the bootloader after following their steps see here and i tried it (before trying to add magisk to it...) and it changes the message about unlocked bootloader to something about booting a different os (then the original).
now after installing it with magisk, i was about to lock it again, but got the big caps lock WARNING to NEVER EVER lock it without returning to or firmware... or it will BRICK.

now im hesitant to do it, but already did it once before i rooted (with the custom rom = GrapheneOS)

anyone know if this will for sure brick, or the warning is just in case?
and if its for sure, then why did it not break when it was without magisk?
 

EtherealRemnant

Senior Member
yes, if GrapheneOS is considered custom rom :)

the GraphineOS docs say to lock the bootloader after following their steps see here and i tried it (before trying to add magisk to it...) and it changes the message about unlocked bootloader to something about booting a different os (then the original).
now after installing it with magisk, i was about to lock it again, but got the big caps lock WARNING to NEVER EVER lock it without returning to or firmware... or it will BRICK.

now im hesitant to do it, but already did it once before i rooted (with the custom rom = GrapheneOS)

anyone know if this will for sure brick, or the warning is just in case?
and if its for sure, then why did it not break when it was without magisk?
You cannot re-lock the bootloader with Magisk as it will instantly fail AVB verification.
 

Light_Wing

Senior Member
You cannot re-lock the bootloader with Magisk as it will instantly fail AVB verification.
so it just wont let me lock it?
if so ill try...

i also found a post about building your own GrapheneOS with Magisk, and re signing, then locking bootloader. and it tells you to just to make sure not to disable OEM unlocking later in dev settings, in case something happens due to root, as long as its open you can recover from it, and if not then thats when you get a hard brick (this is what i understood, maybe im wrong)

here is the link to that post
 

EtherealRemnant

Senior Member
so it just wont let me lock it?
if so ill try...

i also found a post about building your own GrapheneOS with Magisk, and re signing, then locking bootloader. and it tells you to just to make sure not to disable OEM unlocking later in dev settings, in case something happens due to root, as long as its open you can recover from it, and if not then thats when you get a hard brick (this is what i understood, maybe im wrong)

here is the link to that post
This is a really dangerous thing to attempt to do with a device that doesn't have a low level recovery tool like OnePlus does with the MSM Tool. When you re-lock the bootloader, it automatically untoggles that switch as it factory resets the phone, so if something goes wrong, there's no way to recover as usually these bricks won't let you get into recovery, just fastboot, and you require an unlocked bootloader to flash with fastboot.
 

EtherealRemnant

Senior Member
Agreed. It's a solid rule to never relock your Bootloader until you're ready to trade your device in. Especially if it's just to remove a stupid warning on a reboot
Even then, it's best to use the Android Flash Tool to do this, to make sure you actually are back to full stock so you don't brick anyway.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,565
1,843
New Release:
Dec 04, 2022 v4.5.0 release
  • New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
  • New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
  • Use latest Python updated packages.
  • Ubuntu 22.04 support.
  • Miscellaneous improvements.
 

Top Liked Posts

  • 2
    will this work on a t-mobile pixel 7pro?just so im clear this isnt a unlocking and rooting tool correct just a flashing tool?
    If the phone is locked by your mobile provider, this tool will not unlock it.
    However if you phone is oem / booltloader unlockable, then this tool will help you unlock it, and then root.

    Hope that answers your question.
    1
    I was 99% sure that was the answer I was going to get 👍.. thanks for taking the time and explaining it in more detail..
  • 4
    Yet another painless process doing the January updates thanks to the the brilliant mind of @badabing2003 and his creation of this intuitive and easy to use software! Happy New Year! Cheers!
    4
    Hi all,

    I'm trying to figure out how to use pixel flasher.

    My P7pro is rooted with verity and verification disabled. But, PF does not recognize my device to be rooted. So, my question is how do I get PF to recognize root and to update + retain root and verity & verification left disabled?
    Did you allow root access for "[SharedUID] Shell" (com.android.shell) in Magisk? That's used by PF to detect root.
    If you use Magisk Hide you can also set the new package name (not app name) in the PF settings.
    4
    You downloaded the OTA instead of the factory image. OTA's won't flash using the Pixel Flasher Tool. An OTA has to be sideloaded. You need the full factory image from here to flash with PFT.
    Actually OTA can be flashed in PF, but you will not retain root.
    To flash OTA, choose custom flash, select SIDELOAD in the dropdown and choose your file and not the flash button.

    People who don't want root and want a quick update choose that option. It is much faster than doing OTA on the phone.
    4
    Another update, another P7P flash using this tool with less than a handful of mouse clicks and zero issues.

    Even if you have been using ADB for years like me, why choose to make things more difficult?
    3
    You reminded me I need to get some canned pressurized air :sneaky: My laptop is less than a month old so it's not the dust, but I definitely need to have those canned air handy!



    That's a good tip to keep in mind. If I run into the same situation—spinning beach ball, PixelFlash is hung and not responding—would it be safe to try un/replugging? Typically I'd worry un/replugging the phone will interrupt the flash and causing some unpredictable problems/bricking.
    if the phone is showing to be in fastbootd mode
    Something like this (not an exact device image, but it should look similar and say fastbootd)
    Google-Pixel-Android-10-fastbootd-Dedicated-Fastboot-Mode.jpg

    And PixelFlasher is displaying in the console
    < waiting for [some_device_id] >
    you can unplug re-plug
    PF has launched the equivalent of flash_all and which has issued the fastboot command, it's waiting for response and is tuck in that state.
    It would be safe if the above is observed.
  • 41
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 7 Pro
    PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/updating with extra features.

    Basic mode: Should suit most users. Some of the features in basic mode are:
    • Simple UI interface, click and go. No more command line, no more placing all files in one directory.
    • boot.img management UI, select the boot.img file to patch and click the patch button. Fully Automated patching with Magisk (without user interaction) and perform upgrades without losing root.
      No more manually extracting files transferring to the phone, patching / re-flashing and doing multiple reboots.
      No more setting airplane mode and clearing storage to retain Safetynet passing.
    • Display details of boot.img.
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

    For full details on where to download / usage and feature set of the tool, visit the main thread at XDA or the project's Github page.

    Troubleshooting:
    • See this post.
    • Generate Sanitized support.zip file (File Menu) and submit that with your report.
    Note: This thread is meant for issues and problems faced in Google Pixel 7 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
    14
    New Release:
    Nov 09, 2022 v4.4.0 release
    • New feature: Font and Font size should be configurable by the user #33
    • New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
      Handy to access a device remotely.
      Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
      I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
    • Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
    • Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
    • Minor UI Improvements
    • If Magisk does not create a backup attempt to trigger Magisk to create one.
    • Update readme to include Pixel 7 / 7P specific info.
    12
    New Release:
    Dec 04, 2022 v4.5.0 release
    • New look (Artwork / Icons), compliments of @t-ryder (thank you), based on Material design icons.
    • New Feature: Package Manager, Install / Uninstall / Freeze (disable) / Unfreeze (enable) packages even system ones (root not required). Handy with Wifi ADB.
    • Use latest Python updated packages.
    • Ubuntu 22.04 support.
    • Miscellaneous improvements.
    12
    So, if you read the post on the krisakura kernel in the p7p forums, he notes the steps needed including disable verity and such.

    The power hint module isn't very important as it can be flashed later, however the kernels themselves for this phone have to do a special workaround with each run.

    A possible resolution would be to enable the --disable-verity and other flags as an option in your application.

    I just came back over from iphone so admittedly I personally am a bit out of date as I haven't had an android since the pixel 3. I wish I could offer your more assistance!
    Like @JakeDHS07 said, these options are already in PixelFlasher.

    Don't take this the wrong way, but if you just came back over from iPhone and admittedly are a bit out of date, you shouldn't be asking for features without understanding what exactly you're asking for.
    For example you say,

    if you read the post on the krisakura kernel ...

    And you expect me to hunt for Krisakura Kernel post and learn the process? For something you're not willing to understand? You haven't even linked the post.
    I'm sorry but this only tells me that you don't want to put any effort in helping yourself, you just expect it to be delivered on a platter.

    I suggest the following.
    If you want to flash a Krisakura Kernel, go over that post, understand the steps / the process, apply it to your phone, if you have any problems regarding that, ask them in that forum.
    Repeat this few times, then identify the pain points, the parts where you think if it were automated would save you time and be less error prone.
    Come back and explain your workflow, and describe how adding such and such feature into PF would ease that pain point and I would seriously consider it if it is feasible.

    This is from the OP in the main thread.

    1668803698944.png


    Tools like PF could be used by the following types of users.
    • People who know the process, know exactly what goes into modding the phone manually, and want to save time and effort repeating the same tedious process each and every time they want to flash / mod.
      And if anything goes wrong, they know how to recover, or ask pertinent contextual questions.
      This is the main audience of PF, people in this group not only are capable of understanding the steps, but are also in position to help others.
    • People new to the game, that find the initial learning curve steep to overcome, but are willing to learn, comparing the console output to the manual steps outlined in the guides and trying to make sense of the workflow / steps and learning along the way. People in this group would eventually become proficient and graduate to the first group.
    • People who don't care about learning, they are merely lazy leeches that just want things to be done for them. PF is not intended for this type of users, if I wanted to attract this group I would have charged for the program.
    • People who are incapable of learning / following guides, although I don't believe that this group exists at XDA, but if there are rare few of them, then I respectfully suggest that modding is not for them.
    10
    Pre-Release:
    Oct 13, 2022 v4.2.0 pre-release
    • Support for Pixel 7, 7p (init_boot extraction and patching / flashing).
    • Added Pixel 7 / 7p partitions flashing options to custom flash.
    • Improved patching process using boot_patch, add more patch file validations.
    • Check for Magisk backup and trigger Magisk to backup if missing.
    • Add more logging messages for troubleshooting.
    • Code optimization / improvements.
    • Bug Fix #28 Error when opening download link without a device selected.
    • Added set_version script to easily set the product version.
    • Print path of the selected boot to console, for easy copy / paste.