Themes / Apps / Mods ðŸ“³ðŸ”¥PixelFlasher for Google Pixel 7 Support Thread.

Search This thread
By:
Advanced…
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
SirRhor said:
I thought of something. I am trying to flash older firmwares for a Pixel 7 and 7 Pro LOCKED to Verizon, therefore no luck unlocking the bootloader, so PixelFlasher would no work in this case, right?
Click to expand...
Click to collapse
When flashing OTA images through sideload, the bootloader does not need to be unlocked,
However I don't know if OTA allows downgrade.
 
SirRhor

SirRhor

Senior Member
Oct 24, 2011
1,267
722
New York
rhor.deviantart.com
Samsung Galaxy Tab A8
Google Pixel 7
badabing2003 said:
When flashing OTA images through sideload, the bootloader does not need to be unlocked,
However I don't know if OTA allows downgrade.
Click to expand...
Click to collapse
Yes, unfortunately I can downgrade from OTA either.
I however downgraded PixelFlasher to 4.10.0.0 and the firmware processing went fine. On 5.0.0.1 and later, the processing shows the error.
 

Attachments

  • support_2023-05-27_13-49-58-4.10.zip
    3.4 KB · Views: 9
  • support_2023-05-27_13-50-58-5.0.0.1.zip
    2.6 KB · Views: 8
D

Deleted member 12589431

Guest
Detected Unsupported firmware, with payload.bin, perhaps in a future version it could be supported
 

Attachments

  • PixelFlasher_2023-05-31_16h32m56s.log
    4.4 KB · Views: 10
  • Like
Reactions: elong7681
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
13gears said:
Detected Unsupported firmware, with payload.bin, perhaps in a future version it could be supported
Click to expand...
Click to collapse
panther-ota-tq2a.230505.002-c3d87694.zip

You're loading OTA image not a factory image.
Click on that left green link icon next to the factory image selection to open up a download page of factory image for your device.

Next version of PF will support OTA patching.
 
  • Like
Reactions: elong7681 and Deleted member 12589431
D

Deleted member 12589431

Guest
2023-05-31 18:57:29 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 10 seconds ...
2023-05-31 18:57:46 No Device is selected!

2023-05-31 18:57:46 ERROR: Unable to detect the device.
You can try scanning for devices and selecting your device (it should be in bootloader mode).
and then press the same Flash button again.

2023-05-31 18:58:57 Scanning for Devices ...
No Devices found.

PixelFlasher_2023-05-31_18h41m43s.log - BayFiles

bayfiles.com bayfiles.com
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
13gears said:
2023-05-31 18:57:29 User Pressed Ok.
Rebooting device REDACTED to bootloader ...
Waiting 10 seconds ...
2023-05-31 18:57:46 No Device is selected!

2023-05-31 18:57:46 ERROR: Unable to detect the device.
You can try scanning for devices and selecting your device (it should be in bootloader mode).
and then press the same Flash button again.

2023-05-31 18:58:57 Scanning for Devices ...
No Devices found.

PixelFlasher_2023-05-31_18h41m43s.log - BayFiles

bayfiles.com bayfiles.com
Click to expand...
Click to collapse
Is your bootloader unlocked?
 
D

Deleted member 12589431

Guest
badabing2003 said:
Is your bootloader unlocked?
Click to expand...
Click to collapse
Should be. Dev settings -> OEM unlock. Yet I didn't reboot the phone, just poked the slider. Hmm. I'm stuck on the bootloader screen says FASTBOOT MODE, STATUS LOCKED. Guess I can boot past this and try the process again. Unless you have a better idea.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
13gears said:
Should be. Dev settings -> OEM unlock. Yet I didn't reboot the phone, just poked the slider. Hmm. I'm stuck on the bootloader screen says FASTBOOT MODE, STATUS LOCKED. Guess I can boot past this and try the process again. Unless you have a better idea.
Click to expand...
Click to collapse
OEM unlock and bootloader unlock are two different things, your bootloader needs to be unlocked.
You can press on that unlock button, but be WARNED, it will wipe your phone.
You can go to the help menu | links and check any of the the guides to learn more about bootloader unlocking.
 
  • Like
Reactions: V0latyle
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
8,332
4
13,708
The Heartland of America
Google Pixel 5
Google Pixel 5a
badabing2003 said:
OEM unlock and bootloader unlock are two different things, your bootloader needs to be unlocked.
You can press on that unlock button, but be WARNED, it will wipe your phone.
You can go to the help menu | links and check any of the the guides to learn more about bootloader unlocking.
Click to expand...
Click to collapse
This.

OEM Unlocking does not unlock the bootloader; it functions as a safety that allows the bootloader to be unlocked.
 
D

Deleted member 12589431

Guest
I hear you all. However, I cannot "fastboot flashing unlock" when the phone is booted as it just says "waiting for any device", and when I'm in Fastboot Mode I can't run ADB. So.. I donno.. help
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
13gears said:
I hear you all. However, I cannot "fastboot flashing unlock" when the phone is booted as it just says "waiting for any device", and when I'm in Fastboot Mode I can't run ADB. So.. I donno.. help
Click to expand...
Click to collapse
Switch Android platform tools to version 33.0.3
Then reboot to bootloader
and issue fastboot devices
if you see your device ID listed, then you can try the unlock.
If you don't, update your drivers (there is a download link in the help menu)
 
  • Like
Reactions: Deleted member 12589431
D

Deleted member 12589431

Guest
It was a driver issue. I got the official USB Google driver and all is good. Flashing now and sh!tting bricks. Thanks for your helps, hope this is the last you hear from me.
 
  • Like
Reactions: dexlemaffo and badabing2003
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
New Release:
June 01, 2023 v5.2.0.0 release
  • Update build workflows
  • Add payload_dumper functionality to PixelFlasher to handle OTA files, thanks to vm03 for sharing source code.
  • Added rules engine code to better / easier management of the UI widgets enabling / disabling.
  • Auto detect Pixel OTA image and extract boot / init_boot / vbmeta for patching and flashing.
  • Add Full OTA mode, which flashes full OTA image, while optionally retaining root, and best of all, for A/B devices, both slots are bootable, you can even have one rooted and one not.
 
  • Like
  • Love
Reactions: Skysurfer77, c0mputeRb0y, bjevers and 1 other person
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
New Release:
June 06, 2003 v5.3.0.0 release
  • Added Github Action build on Windows 2019 with Python 3.8 to support Windows 7.
  • PixelFlasher now supports loading and processing Samsung Firmware (at least my Samsung's 😀), it would extract AP, BL, CSC, Home_CSC ... and then extract boot.img.lz4 from AP and unpack the lz4.
    When creating a patch from the set boot.img, PixelFlasher will also create boot.tar to be flashed as AP to retain root.
    If there was a way to pre-load odin with the extracted files, flashing could also be automated.
    I know, what does PixelFlasher have anything to do with Samsung firmware? I added it for my own use.
 
  • Like
Reactions: ekeppel, elong7681, t-ryder and 1 other person
M

mruno

Senior Member
Aug 27, 2010
212
58
Google Pixel 7
EDIT: I was able to get the "Flash Pixel Phone" button to work after reselecting & processing the firmware.

I am unable to update to the June update. I believe it may be due to this error:

Code: 
Getting package com.topjohnwu.magisk path on the device ...
2023-06-14 05:53:31 ERROR: Could not get package com.topjohnwu.magisk path.
Return Code: 1.
Stdout: .
Stderr: .

Thanks for the assistance.
 

Attachments

  • support_2023-06-14_05-57-11.zip
    9 KB · Views: 9
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,037
4,696
mruno said:
EDIT: I was able to get the "Flash Pixel Phone" button to work after reselecting & processing the firmware.

I am unable to update to the June update. I believe it may be due to this error:

Code: 
Getting package com.topjohnwu.magisk path on the device ...
2023-06-14 05:53:31 ERROR: Could not get package com.topjohnwu.magisk path.
Return Code: 1.
Stdout: .
Stderr: .

Thanks for the assistance.
Click to expand...
Click to collapse
That is only an indication that you have hidden Magisk or using a version of non-original Magisk the package name of which is not com.topjohnwu.magisk
That is not the issue.

Please do not filter out files from support.zip, what you sent me does not have anything regarding the problem you are reporting, which honestly is quite vague.
I am unable to update to the June update. I believe it may be due to this error:
Click to expand...
Click to collapse
 
You must log in or register to reply here.

Similar threads

hammered58
How To Guide Rooted my Pixel 7
Replies
130
Views
24K
41rw4lk
41rw4lk
sirhc
Development Paranoid Android Topaz Beta 1 - Google Pixel 7
Replies
77
Views
20K
O.J. Simpson
O.J. Simpson
Duhjoker
Development [Rom][13.0.0_r20]AICP Pixel 7 & Pixel 7 pro[Panther][Cheetah]
Replies
70
Views
16K
fress
fress
thesm4rt1
Question What Magisk modules are you using?
Replies
93
Views
22K
EngineManShawn
EngineManShawn
t-ryder
General Pixel 7 display size rumors
Replies
29
Views
10K
nikitasius
nikitasius

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 3
    badabing2003
    badabing2003
    New Release:
    Sep 19, 2023 v5.8.0.0 release
    • Added support for scrcpy (Screen Copy), you can now launch scrcpy to the attached device, configuration is done in the main settings window.
    • Completely redid the wireless connection, there is now wireless manager, that shows history, status and quick selection from history, and supports wireless debugging which requires pairing and is the only option for newer OS-es.
    • For crDroid and other non Pixel firmware automatically set to Full OTA mode (ie sideload) if payload.bin is detected.
    • Added a button to reboot to userspace fastboot (fastbootd).
    • Added system menu to be able to move, resize, minimize, maximize. (useful when the window is of the screen)
    • When extracting from payload.bin, optionally also extract (if available) dtbo.img, super_empty.img, vendor_boot.img, vender_kernel_boot.img in addition to boot.img and init_boot.img (configurable in the settings), as some of these images are needed for 3rd party firmware flashing.
    • On Linux, display a message when terminal app is not set and open shell feature is used.
    • For Samsung devices, when creating a tar file of a patched boot, use POSIX tar format.
    • Miscellaneous fixes and improvements.
    View
    1
    badabing2003
    badabing2003
    doomwithdon said:
    Can I use full OTA as flash mode and keep data? Or is keep data possible only if factory image flash mode is selected?
    Click to expand...
    Click to collapse
    Yes, with full OTA there is only keep data, there is no wipe data possibility.
    View
    1
    badabing2003
    badabing2003
    omegalulred said:
    Question, how do i recover from boot loops, from magisk/lsposed modules?

    I used this utility to install magisk and that's it. How do i enter recovery? To disable modules for example
    Click to expand...
    Click to collapse
    The easiest would be to use the SOS button
    This work if your phone during bootloop gets a brief access to adb.
    Often this is not the case, and the sos button will not be able to disable the modules.

    You can also boot to safe mode by using the key combination, and that would disable Magisk modules
    But again this does not always work.

    your last option would be to flash a special Magisk version that gives you root without loading the modules.
    You would need that so that you can disable the module.
    To learn more about this option, in PF, select Install Magisk and then select special and read the instructions.
    1695435340349.png
    View
    1
    badabing2003
    badabing2003
    New Release:
    Sep 24, 2023 v5.8.0.1 release
    • Bug fix: #99 Settings not opening on linux/arch based distro
    View
  • 19
    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 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
    8
    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
    8
    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
    7
    badabing2003
    badabing2003
    New Release:
    Mar 14, 2023 v4.8.1 release
    • #47 Feature request: Added partition manager - Allows to erase partitions, and / or dump / backup partitions to PC.
    • Added more visual troubleshooting event flows.
    • Added warning message for when Android platform tools versions 34.0.0 and 34.0.1 are used.
    • Improved support.zip redactions.
    • Added Support.Zip generator button on the Main screen.
    • APK Install option can now set the ownership to Play Store Market (useful for Android Auto)
    • Check and warn the user when Magisk Canary versions 25207, 25208, 25209 and 25210 are being used.
    • Bug fixes and other improvements.
    View
    6
    badabing2003
    badabing2003
    New Release:
    Feb 12, 2023 v4.8.0 release
    • #50 Support for Android 14 Developer Preview for Pixel 7 and Pixel 7 Pro
    • #48 Do not allow patching with hidden Magisk (stub) and adb shell not granted root rights.
    • Block using Android Platform Tools version 34.0.0 and display a warning because it has known issues
    • Disable Magisk Backup Manager button if root access to adb shell is not granted.
    • Button to Open adb shell connected to the selected device.
    • Work in Progress: Generate graphical activity log to visualize the activity and speed up troubleshooting.
    View

New posts