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

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,569
1,849
@badabing2003 when on the bootloader unlocked warning screen, the device shows up as an "Intel(R) USB 3.1 eXtensible Host Controller - 1.10"
I see that you have other devices
Uninstall the current adb / fastboot drivers from your system, and install the official ones from Google.
You need to put the device in the various modes adb / fastboot ... to be able to install the drivers for that mode, doing on adb alone is not enough.

When your other devices are properly identified under "Portable Devices" for adb, and as "Android Bootloader Interface" for bootloader.
Then plug your Pixel and see how it gets identified as it looping
 

djcsurf

Senior Member
Jan 9, 2011
2,003
435
Kent
New Release:
Nov 09, 2022 v4.4.0 release
  • 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.
Firstly I gotta say PF is a superb tool, your work is very much appreciated.
With your future releases will the option to uninstall apps include pre installed apps, being a little OCD about my P7P it would be a blessing 😁
 

Znil

Senior Member
Sep 6, 2010
61
15
Samsung Galaxy Tab S2
OnePlus 6
I see that you have other devices
Uninstall the current adb / fastboot drivers from your system, and install the official ones from Google.
You need to put the device in the various modes adb / fastboot ... to be able to install the drivers for that mode, doing on adb alone is not enough.

When your other devices are properly identified under "Portable Devices" for adb, and as "Android Bootloader Interface" for bootloader.
Then plug your Pixel and see how it gets identified as it looping
Thanks but I actually did install the official google drivers before using PF. I installed them in adb and bootloader. I used the root guide from this forum to unlock and root the device, though I did that on a different PC, but I did install the drivers since I knew that was necessary. You think unistalling and reinstalling would help? The only two modes are adb (when phone is on) and bootloader right? Or am I missing something?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,569
1,849
Thanks but I actually did install the official google drivers before using PF. I installed them in adb and bootloader. I used the root guide from this forum to unlock and root the device, though I did that on a different PC, but I did install the drivers since I knew that was necessary. You think unistalling and reinstalling would help? The only two modes are adb (when phone is on) and bootloader right? Or am I missing something?
right, as far as I know, two modes.
Do you still have access to the other PC?
How is it detected on the other PC?
 

Znil

Senior Member
Sep 6, 2010
61
15
Samsung Galaxy Tab S2
OnePlus 6
Ivmanaged to get into fastboot mode with my pixel 7 by letting the battery drain which took the phone out of the bootloop and then voldown + power when plugging in the charger. How shall I proceed now?
@badabing2003 I managed to fix the device! Did a full wipe and flash trough PF after getting into fastboot
 

Znil

Senior Member
Sep 6, 2010
61
15
Samsung Galaxy Tab S2
OnePlus 6
This is excellent, good job.
If you did not flash to both slots, make sure you do another run and flash to inactive slot, this way both your slots are good.
Otherwise your other slot is most likely still corrupt.
I did setup my phone already again. Rooted it etc. Can I still flash to the inactive slot without losing my data again? Thanks for the help
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,569
1,849
I did setup my phone already again. Rooted it etc. Can I still flash to the inactive slot without losing my data again? Thanks for the help
Of course,
Just start PF in last state which should have everything already, toggle to (flash to inactive slot) make sure keep data is selected.
Flash
Your main slot will not be touched, the other slot will be flashed and become active.
Moving forward in the future monthly flashes, just flash to inactive slot, this way you always have something good to fallback to.
 
  • Like
Reactions: Slim2none4u
The only way I know is by reading the release notes and see if it is something that you want / need.
It doesn't get updated that often anyways.
You can easily check the release notes in PF, by clicking on install Magisk, but not necessarily installing it, when you select the version, the bottom pane shows the release notes
View attachment 5757905
@badabing2003 Do you typically use the Canary version of Magisk?? I just use Stable, but was curious how other versions are working.
 

Top Liked Posts

  • 3
    What does it mean exactly?
    I would flash full stock, saving data, change active slot and then flash full stock again. Make sure you are using the latest ADB SDK also and not Minimal ADB.
    1
    Does the WIPE all data option also remove root?
    Yes if you flash the stock non patched image. Will leave device like you just bought it.
    1
    I've been using this Magjsk Alpha for over a year without issuses on Samsung devices and it run fine on Pixel too until today when I decided to update it from 44643ad7-alpha (25205) to 6ecc04a4-alpha (25206) and it ended up in a bootloop.

    Galaxy Tab S8+ with 6ecc04a4 works but Pixel doesn't. Magisk & LSPosed modules without the red X were installed on Pixel.
    Sound like an issue with Magisk Alpha or a conflict with one of the modules.
    But flashing stock and still not working suggests that something else got corrupted, which shouldn't happen, hence why I said if you flashed it correctly, then it would be an issue in Magisk Alpha.

    Should I only choose "Keep data" or "Disable verity & disable verification" as well? Should I tick "Flash to both slots" too?
    I would disable modules.
    Keep Data
    Flash to both slots. Inactive Slot
    Are you using custom ROM? did you Disable Verity / Verification previously? if you're on stock, then don't select them, otherwise you will wipe your data, on the other hand if you had previously selected those, then you want to select again.
    1
    I would flash full stock, saving data, change active slot and then flash full stock again. Make sure you are using the latest ADB SDK also and not Minimal ADB.
    This worked thanks a lot to you, @badabing2003, @Homeboy76 , @Lughnasadh and everyone else who tried to help.
  • 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.
  • 42
    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.
    11
    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.