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

Search This thread
By:
Advanced…
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
lexpower said:
Here is the full log with latest firmware.
The only change is that now I don't have that red screen at the beginning saying phone is corrupted.
Click to expand...
Click to collapse
So what is the state of the phone, still in bootloader mode? I still see communication issue.

Please click on the big support button, or select the option from the help menu.
It generates a sanitized support file that redacts sensitive information like username , device id, and has structured even log that is useful for troubleshooting, copying and pasting the console log not only exposes sensitive information, but it is less useful for troubleshooting.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
swour said:
Thanks for creating this most useful tool! The first round of flashing went flawless.


Regarding the correct procedure to flash to the inactive slot for monthly updates. Is activating the option enough or does the user have to manually switch the active slot at some point? In other words, can flashing to inactive slot be left activated for each update and PixelFlasher will do the rest?
Click to expand...
Click to collapse
Correct, just set the checkbox, and PF will remember it, and after flashing to inactive slot it will switch to the correct slot that you just flashed.
 
  • Like
Reactions: swour
N

nIsmoAddict

Senior Member
Nov 4, 2013
50
17
Hi,

This might be a silly question, but if I am updating my the December release, can I just flash the March 13th release or will I need to flash each update from January to current?
Also, if I flash the global build (13.0.0 (TQ2A.230305.008.C1, Mar 2023)) if I'm in the US ya?
1680771363006.png
 
M

mko000

Senior Member
Jul 27, 2011
511
268
Google Nexus 4
Sony Ericsson Xperia Arc
nIsmoAddict said:
Hi,

This might be a silly question, but if I am updating my the December release, can I just flash the March 13th release or will I need to flash each update from January to current?
Also, if I flash the global build (13.0.0 (TQ2A.230305.008.C1, Mar 2023)) if I'm in the US ya?
View attachment 5881797
Click to expand...
Click to collapse

No (you only need to flash the latest update) and yes (the other build is only for Canada).
 
  • Like
Reactions: nIsmoAddict and Homeboy76
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
New Release:
Apr 10, 2023 v4.8.2 release
  • Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
  • Display USNF related flag values when selecting a device.
  • Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
  • Link to download Google USB Driver is added in the help menu.
  • Added more visual troubleshooting event flows.
  • Install APK now defaults to Non Market.
  • Added Install APK cancel option.
  • You can now select an app in package manager and right click to launch it on the phone.
  • Minor bug fixes and other improvements.
 
  • Like
  • Love
Reactions: letmedanz, xdrc45, VerticalCobra and 22 others
Slim2none4u

Slim2none4u

Senior Member
Oct 28, 2011
912
579
49
Livermore Falls
www.youtube.com
Verizon Droid Incredible 2
Sprint HTC EVO 4G LTE
binoysankar said:
Hello @badabing2003, I am facing an issue such that when I add the factory images and click on the "Patch" button for the magisk patch image it does not show up in the list of boot images. I tried enabling the "Show All boot.img" option but not successful. I confirmed the magisk image is sucessfully generated in the path. but not visible in the application.
Currently as a workaround I used to rename the "magisk_patched_xxx.img" to "init_boot.img" and flash it.
PFA screenshots and support.zip
Click to expand...
Click to collapse
Its your version of Magisk, Use Stable.
 
N

niko26

Senior Member
May 5, 2010
197
72
badabing2003 said:
New Release:
Apr 10, 2023 v4.8.2 release
  • Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
  • Display USNF related flag values when selecting a device.
  • Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
  • Link to download Google USB Driver is added in the help menu.
  • Added more visual troubleshooting event flows.
  • Install APK now defaults to Non Market.
  • Added Install APK cancel option.
  • You can now select an app in package manager and right click to launch it on the phone.
  • Minor bug fixes and other improvements.
Click to expand...
Click to collapse
Nice, thanks for the constant updates. I just realized that you do not support the most recent last two versions of the platform tools, versions 34.0.0 and 34.0.1. I might missed your explanation - what's the reason for this? I always thought it is mandatory to use the latest versions for the latest firmware builds.
 
Last edited:
  • Like
Reactions: Homeboy76 and lupastro82
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
niko26 said:
Nice, thanks for the constant updates. I just realized that you do not support the most recent last two versions of the platform tools, versions 34.0.0 and 34.0.1. I might missed your explanation - what's the reason for this? I always thought it is mandatory to use the lates versions for the latest firmware builds.
Click to expand...
Click to collapse
They're buggy and can't get into userspace fastboot (fastbootd)
 
  • Like
Reactions: Blade22222, niko26 and HipKat
lupastro82

lupastro82

Senior Member
Jul 16, 2018
103
18
Google Pixel 7 Pro
Tested today for first time to update my P7P (usually I use factory-image with patched init and removed -w flag).

Issue for P.T. release (latest cannot work for unknow reason, old in my hd cannot work because too old... then, download via website (just tried a lot of time to generate a valid link: https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip ).
After of this, my device is valid rooted with magisk via init_boot.img, but in pixel flasher looks like not-rooted.
Anyway, flash without issue. 👍
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
lupastro82 said:
Tested today for first time to update my P7P (usually I use factory-image with patched init and removed -w flag).

Issue for P.T. release (latest cannot work for unknow reason, old in my hd cannot work because too old... then, download via website (just tried a lot of time to generate a valid link: https://dl.google.com/android/repository/platform-tools_r33.0.3-windows.zip ).
After of this, my device is valid rooted with magisk via init_boot.img, but in pixel flasher looks like not-rooted.
Anyway, flash without issue. 👍
Click to expand...
Click to collapse
If you are rooted but PF is telling you that you're not, that is because you have not grant su (root) rights to adb shell.
Check basic usage step 2 in OP or at Github.
 
  • Like
Reactions: HipKat, Slim2none4u and lupastro82
A

Aphex13

Senior Member
Aug 21, 2010
454
201
Kansas
Sony Xperia Z Ultra
Huawei Nexus 6P
krkhaha said:
Hi i tried patch latest pixel factory image as always. Process is okay. I can see notification is done but I can't see that patched boot image to select. Always was here two boot img. Patched and stock
ibb.co

PXL-20230411-230834639-01 hosted at ImgBB

Image PXL-20230411-230834639-01 hosted in ImgBB
ibb.co ibb.co
Click to expand...
Click to collapse
I had the same problem a while back. You need to downgrade your Magisk to v25.2 (stable). Then try again.

Edit: The new Magisk v26.1 (stable) version also works, I just tried it.
Just don't use the 26.0 (beta).
 
Last edited:
  • Like
Reactions: krkhaha and badabing2003
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
  • Like
Reactions: krkhaha and Josh
R

Ripthulhu

Senior Member
Jul 20, 2013
64
19
Is anyone else having issues with regaining root on the April update? I flashed the full firmware through pixel flasher without wiping data, then patched init_boot through pixel flasher.
All goes well and the phone boots, but Magisk keeps telling me it's not installed. I tried latest stable Magisk, 2.5.2, and also tried manually patching and flashing init_boot. No dice, same result
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
2,299
3,233
Ripthulhu said:
Is anyone else having issues with regaining root on the April update? I flashed the full firmware through pixel flasher without wiping data, then patched init_boot through pixel flasher.
All goes well and the phone boots, but Magisk keeps telling me it's not installed. I tried latest stable Magisk, 2.5.2, and also tried manually patching and flashing init_boot. No dice, same result
Click to expand...
Click to collapse
This could be one of two things.

Two Magisks fighting over, one hidden and one not.
You can detect this by one of two ways.
Try a root app that previously worked, see if it still gets root, if it does then you have a hidden Magisk, and the unhidden manager is having issues.
Or install TB Checker from play store and run the tests and see what it finds

You patched with broken version of Magisk.

Easiest way to resolve this.
Flash stock init_boot (no need for full factory)
Find and uninstall all Magisk managers, hidden or otherwise, make sure TB Checker different find any.
Install 25.2 or 26.1 (I prefer 25.2), create patch and just apply the patch.

The Flash Boot button just flashes the selected boot image
 
  • Like
Reactions: Ripthulhu
R

Ripthulhu

Senior Member
Jul 20, 2013
64
19
badabing2003 said:
This could be one of two things.

Two Magisks fighting over, one hidden and one not.
You can detect this by one of two ways.
Try a root app that previously worked, see if it still gets root, if it does then you have a hidden Magisk, and the unhidden manager is having issues.
Or install TB Checker from play store and run the tests and see what it finds

You patched with broken version of Magisk.

Easiest way to resolve this.
Flash stock init_boot (no need for full factory)
Find and uninstall all Magisk managers, hidden or otherwise, make sure TB Checker different find any.
Install 25.2 or 26.1 (I prefer 25.2), create patch and just apply the patch.

The Flash Boot button just flashes the selected boot image
Click to expand...
Click to collapse
You are right, it was a hidden Magisk throwing a wrench in the process. Odd, I'm pretty sure I unhidden it before doing the update but I guess not.
I removed the second Magisk and unhidden the original one and it works again.
Thank you for your reply!
 
  • Like
Reactions: badabing2003
D

djcsurf

Senior Member
Jan 9, 2011
2,025
443
Kent
I major f___ed up today, so use to using PF that just got in the same habit of using it forgetting that I added another module and hidden magisk. Now in a permanent bootloop unable to do a thing as PF can't pick up device in ADB
 
You must log in or register to reply here.

Similar threads

roirraW "edor" ehT
How To Guide Platform-Tools v34.0.3 has a different bug - May 1, 2023 TQ2A.230505.002 Global - Unlock bootloader / Root Pixel 7 Pro [Cheetah] / SafetyNet
Replies
3K
Views
202K
Displax
Displax
Freak07
Development [Kernel][04.05.2023][Android 13.0.0 Stable]Kirisakura_Raviantah 1.0.4 for Pixel 7/Pro aka "Pantah"
Replies
1K
Views
143K
Freak07
Freak07
roirraW "edor" ehT
General May 16, 2023 QPR3 Beta 3.2 T3B3.230413.009 - Pixel 7 Pro [Cheetah] - [thread also for future Android QPR Betas]
Replies
476
Views
64K
WillyRy
WillyRy
N
Development [ROM][UNOFFICIAL][cheetah/panther] LineageOS 20.0 for the Pixel 7 Pro/7
Replies
329
Views
47K
J
jake.99x3
eg1122
Themes / Apps / Mods ★ Post your Google Pixel 7 Pro Home Screens ★
Replies
307
Views
43K
Morphine1
Morphine1

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 15
    badabing2003
    badabing2003
    New Release:
    May 19, 2023 v5.0.0.1 release
    • #75 Bug fix, when device is in bootloader, type error.
    • #74 Added Support for Pixel 7a (lynx)
    • Configuration option to define the file manager to use on Linux (default: Nautilus)
    • Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
    • Support for additional types of Factory / ROM files.
    • Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
    • New advanced option, ability to choose the patching method (with recommendations).
    • Added Recovery Image patching option.
    • Advanced option to enable the use of busybox shell (default off).
    • Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
    • Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
    • Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
    • Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
    • #66, when checking the patched files internal SHA1, provide a confidence rating.
    • Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
    • Added fastbootd testing to Dry Run.
    • Added Github actions to build all the targets on Github.
    • Code refactoring, bug fixes and improvements
    View
    10
    badabing2003
    badabing2003
    New Release:
    May 25, 2023 v5.1.0.0 release
    • Support for Android platform tools version 34.0.3, and automatic setting of ANDROID_PRODUCT_OUT environment to workaround a regression introduced in version 34.0.3
    • Temp workaround to avoid selecting root method patching when Magisk Delta is detected.
    • Nicer looking / clearer manual patching dialog.
    • When a Pixel device is selected, PixelFlasher now displays additional information about the device's support.
      Things like: Device name, version end date, security update end date, Android version, name, codename, release date, end date.
    • Boot image list box now displays the applied PixelFlasher patch method.
    • Auto-resize boot image list box columns for better readability.
    • Precautionary cleanup up of leftover files on the phone in case root detection software keys on presence of such files.
    • #77 added attrict3 to requirements.txt in case it helps with certain builds (it shouldn't be needed).
    • Bug fixes and improvements.
    View
    7
    badabing2003
    badabing2003
    krkhaha said:
    Hi. Can use this tool to update Pixel 7 pro without root? There is bootloader locked. No any modifications. I can't find last update in system OTA.
    Click to expand...
    Click to collapse
    If your bootloader is unlockable, then the only thing you could do with PF is flash OTA image which you download from Google
    This is the latest for your device
    The list is here.

    The advantage of flashing through PF as opposed to doing it on the phone is it is faster and you can jump from any version to the latest without doing each incrementally.
    Specially for phones that haven't been updated for a while, it could take really long on the phone.

    Enable advanced options in configuration
    Select Custom flash
    Select Sideload dropdown,
    Browse for the file you downloaded
    Hit the Flash Pixel Phone button.

    If your bootloader is unlockable, then you can do everything, and get rooted, you can also unlock it in PF

    Good luck
    View
    6
    V
    vurtomatic
    Max969 said:
    Maybe you should mention that explicitly in the manual. :)
    Click to expand...
    Click to collapse

    Max969 said:
    But then you explain it literally here afterwards anyway. ;)

    Operating instructions are often written in such a foolproof way because many people think differently and have different ideas/habits.

    Was just a tip, thanks for your great work and passion.
    Click to expand...
    Click to collapse

    There's literally numbered steps with accompanying graphic so a user can follow 1, 2, 3, 4, 5, etc.'

    And @badabing2003 is maintaining the app plus provide support in this thread whenever we have questions or run into problems.

    If a user can't follow instructions to use a GUI that simplifies copy-pasting commands into CLI, maybe the user shouldn't attempt rooting. It's almost guaranteed that there will be other more difficult challenges maintaining and using a rooted phone. Like trying to outsmart the security checks to use Wallet, certain tools becoming undependable, etc. **** will get broken and the user needs some self-sufficiency and ability to troubleshoot or, follow instructions. When I run into trouble, I double check the instructions, I search the forum or the thread if anyone else has encountered it, then I ask for help. <-- There's a tip right there.
    View
    5
    badabing2003
    badabing2003
    Max969 said:
    Maybe you should mention that explicitly in the manual. :)
    Click to expand...
    Click to collapse
    There is so much explicit mentions that can be added all over the place.
    If I have to spell out everything literally, then all I'd be doing is writing documents and not working on the app.

    Next select the factory image, the application will recognize the phone model from the image name.
    You can download factory images by clicking the Image of link next to it.
    Click to expand...
    Click to collapse
    Do you see any mention of extract the image?
    A factory image is the whole thing, not just one zip inside the factory image,
    there's bootloader, radio ...
    You're selecting a zip, not a folder.
    Enough said.
    View
  • 54
    badabing2003
    badabing2003
    PF_promo-banner.png


    This is the support thread of PixelFlasher
    (PixelFlasher is an open-source self contained GUI tool to facilitate Pixel phone device flashing/rooting/updating with extra features).

    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.

    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:
    If you need support or assistance, the best way to get is by generating a support file from within PixelFlasher.
    You can hit that big Support button on the main screen, or select it from the Help menu.
    The generated support.zip file is sanitized (redacted) to keep your sensitive information (username device id ...) private.
    View
    28
    badabing2003
    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.
    View
    25
    badabing2003
    badabing2003
    New Release:
    Apr 10, 2023 v4.8.2 release
    • Include additional Magisk versions in the check to display a warning dialog when the user has installed one of the known versions to have issues.
    • Display USNF related flag values when selecting a device.
    • Check the downloaded Google firmware checksum to match the one in the filename and warn if it does not.
    • Link to download Google USB Driver is added in the help menu.
    • Added more visual troubleshooting event flows.
    • Install APK now defaults to Non Market.
    • Added Install APK cancel option.
    • You can now select an app in package manager and right click to launch it on the phone.
    • Minor bug fixes and other improvements.
    View
    16
    badabing2003
    badabing2003
    New Release:
    Apr 30, 2023 v4.10.0 release
    • Added no reboot option, with this option selected, after flashing is completed, the phone will not reboot to system, giving a chance to take other actions before reboot.
    • Added built-in file editor, you can now edit the flash script before running, in case you want to customize it (needless to say, should only be used if you know what you're doing)
    • Added a button to open an explorer in working directory, useful for people who want full control, perform manual actions by following guides, but using PixelFlasher to do the prep work.
    • Made the Firmware and Rom Process buttons, full with text. It wasn't obvious for some.
    • Detect and handle Magisk Zygote64_32 automatically, thanks to @Namelesswonder for adding the necessary marker.
    View
    15
    badabing2003
    badabing2003
    New Release:
    May 19, 2023 v5.0.0.1 release
    • #75 Bug fix, when device is in bootloader, type error.
    • #74 Added Support for Pixel 7a (lynx)
    • Configuration option to define the file manager to use on Linux (default: Nautilus)
    • Configuration option to define the terminal emulator to use on Linux (default: gnome-terminal).
    • Support for additional types of Factory / ROM files.
    • Checksum validation of firmware / ROM files (if part of the checksum is in the name, otherwise just display)
    • New advanced option, ability to choose the patching method (with recommendations).
    • Added Recovery Image patching option.
    • Advanced option to enable the use of busybox shell (default off).
    • Auto detect firmware / rom with init_boot and use init_boot for creating patches, this way future firmware don't have to be manually added to PixelFlasher.
    • Auto detect devices with init_boot and use init_boot for flashing, this way future devices don't have to be manually added to PixelFlasher.
    • Auto-popup the detected devices dropdown after a scan, to make it obvious to select that next. (Thanks @pndwal for the idea)
    • Show SHA-256 of adb and fastboot binaries, as Google keeps on messing up Android Platform-tools, it's necessary to whitelist / blacklist specific binaries.
    • #66, when checking the patched files internal SHA1, provide a confidence rating.
    • Check, valdiate and warn if necessary when flashing an image patched with Magisk Zygote64_32, as there are wipe implications, provide links to documentation.
    • Added fastbootd testing to Dry Run.
    • Added Github actions to build all the targets on Github.
    • Code refactoring, bug fixes and improvements
    View

New posts