Themes / Apps / Mods 📳🔥PixelFlasher for Google Pixel 7 Pro Support Thread.
- Thread starter badabing2003
- Start date
Cool, thanks. I never really understood the two slot system very well. So I got everything setup on slot a now, including root, magisk modules, banking etc. If I now flash to inactive slot, I just have to patch the firmware first in PF and flash this patched firmware and I will retain all data, settings etc and the inactive slot becomes active?
Slim2none4u
Senior Member
- Oct 28, 2011
- 837
- 501
- 49
Slim2none4u
Senior Member
- Oct 28, 2011
- 837
- 501
- 49
If you used PF to patch / flash your active slot a, you already have a patched firmware for November release, just select it and select flash inactive slot, you don't need to repeat creating a patch, you could if you wanted to but why?
Slim2none4u
Senior Member
- Oct 28, 2011
- 837
- 501
- 49
Well "here" is for PF not custom recoveries.
Here is where you should be posting your question. Maybe try to refine your search criteria.
Or using the search function on XDA.
[RECOVERY] - TeamWin Recovery Project [CROSSHATCH] [OFFICIAL]
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
forum.xda-developers.com
Hello, I haven't rooted my phone since 2013 with my Oneplus One so bear with me on this. When prompting for bootloader unlock command, There's no warning popped out in bootloader mode. This happened both using the pixel flasher and normal command prompt method. On the cmd, it's still waiting for device but my device is already in bootloader mode. Does it mean my pc don't have the necessary driver for the device in bootloader mode? Appreciate the help
well i knew someone would point me in the right direction i mean i am in the general vicinityWell "here" is for PF not custom recoveries.
Here is where you should be posting your question. Maybe try to refine your search criteria.
Or using the search function on XDA.
[RECOVERY] - TeamWin Recovery Project [CROSSHATCH] [OFFICIAL]
[RECOVERY] TWRP 3.6.0_11-0 - TeamWin Recovery Project Introduction: Team Win Recovery Project or TWRP for short, is a custom recovery built with ease of use and customization in mind. We started from the ground up by taking AOSP recovery and...
May I request the option to have a kernel and powerhint module flasher built in so that its just restore from backup instead of having to re-configure each time?
I'm not too familiar with those
Tell me the manual steps that you take to achieve the end goal and I'll see if it can be done.
HipKat
Recognized Contributor
Powerhint is a Magisk Module companion for the Kirisakura Kernel. For the kernel, you'd have to borrow the process from one of the Kernel Flashing Apps like EXKM, etc
JakeDHS07
Senior Member
Take a look at this discussion by @V0latyle and @Lughnasadh
@roirraW "edor" ehT here explains it nicely the behavior.
Disabling only verity, which does not require a wipe, worked for custom kernels on on the Pixel 6 series. However, with the Pixel 7 series, both verity and verification need to be disabled (at this time at least) when using custom kernels, thus it does require a wipe the first time you disable both of these.
When the Pixel 7 series first came out there was a thought that disabling only verity would work (as well as the changes to AK3 that were previously implemented), as it did with the Pixel 6 series, when using custom kernels. That turned out not to be the case.
Last edited:
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.
Similar threads
Top Liked Posts
-
There are no posts matching your filters.
-
4Yet 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
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
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.3
if the phone is showing to be in fastbootd modeYou reminded me I need to get some canned pressurized air
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.
Something like this (not an exact device image, but it should look similar and say fastbootd)
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
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.
- 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.
14New 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.
12New 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
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,
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.
10Pre-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.
