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

[AllusionPDX]

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]

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]

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.

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.

 

[vurtomatic]

The last green highlight box shows the options to Disable Verity and Disable Verification.

GitHub - badabing2005/PixelFlasher: Pixel™ phone flashing GUI utility with features.

Pixel™ phone flashing GUI utility with features. Contribute to badabing2005/PixelFlasher development by creating an account on GitHub.

github.com

 

[HipKat]

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!

 

[badabing2003]

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

 

[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

 

[mad4some]

Has anyone been using PF to successfully flash custom roms? I've heard there's some available "out in the wild"

 

[wgrant]

Updated in 4 minutes, retained root. Love this tool.

 

[chaos193]

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.

 

[HipKat]

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]

Has anyone been using PF to successfully flash custom roms? I've heard there's some available "out in the wild"

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]

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]

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]

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.

 

[HipKat]

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

 

[EtherealRemnant]

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.

 

[HipKat]

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.

Absolutely agree

 

[jmac052002]

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!

 

[badabing2003]

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.