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

Search This thread
By:
Advanced…
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
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 7a 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.
 
  • Like
Reactions: MpandAUS, spider1163, Yaotl and 5 others
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
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
 
Last edited:
  • Like
Reactions: Slim2none4u, dexlemaffo, openlatedotorg and 1 other person
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
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.
Update:
Patch Release:
v5.1.0.1 release
  • Exception handling when device is not in the listed Pixel devices.
v5.1.0.2 release
  • Skip testing fastbootd in dry run mode if Android platform tools version is > 34, is it no longer supports fastbootd (at least 34.0.3 does not)
 
Last edited:
  • Like
Reactions: Slim2none4u
G

Gp3322

New member
May 30, 2023
3
1
Thank you so much for this awesome software! When trying to trying to patch the int.boot from the factory image I run into the following error "Detected Unsupported firmware, with payload.bin". Is this truly unsupported or am I doing something wrong?

I also tried extracting the payload.bin to manually pull out int.boot and patch it, which I think worked, but in the console field said something about a low confidence match and aborted the flash.

Any help would be greatly appreciated.

I downloaded the following build from google: lynx-ota-tq2b.230505.005.a1-766dbd16
Using: platform-tools_r34.0.3-windows
Pixel Flasher: v5.1.0.2 release
 

Attachments

  • support_2023-05-29_18-42-49.zip
    39.7 KB · Views: 16
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
Gp3322 said:
Thank you so much for this awesome software! When trying to trying to patch the int.boot from the factory image I run into the following error "Detected Unsupported firmware, with payload.bin". Is this truly unsupported or am I doing something wrong?

I also tried extracting the payload.bin to manually pull out int.boot and patch it, which I think worked, but in the console field said something about a low confidence match and aborted the flash.

Any help would be greatly appreciated.

I downloaded the following build from google: lynx-ota-tq2b.230505.005.a1-766dbd16
Using: platform-tools_r34.0.3-windows
Pixel Flasher: v5.1.0.2 release
Click to expand...
Click to collapse
You are selecting an OTA image instead of firmware image.
If you click on that green button on the left of firmware selection, it should open a download link for your device, download that and process that.

Manually extracting init_boot from payload.bin is ok for patching, which you did the first time around, and it create a proper patch.
But then you proceeded to trying to patch the patched file, why would you do that?
That's when PF aborted with low confidence level.
 
  • Like
Reactions: Gp3322
G

Gp3322

New member
May 30, 2023
3
1
You are 100% correct! I was using the OTA instead of the full image. Once I found the correct file, everything fell into place.
 
  • Like
Reactions: badabing2003
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
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
Reactions: Slim2none4u and dexlemaffo
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
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: dexlemaffo, Slim2none4u and purgy
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
New Release:
June 16, 2003 v5.3.1.2 release
  • Set Active slot now automatically reboots to system after setting the slot, unless "No Reboot" option is selected.
  • Update Ubuntu 20.04 build to be aligned to the same methods that Ubuntu 22.04 build uses.
  • Improve confidence value calculation when comparing compressed sha1 against normal sha1 to account for shift.
  • Do not abort when the sha1 comparison confidence value is low, leave the choice to the user.
  • Update Windows builds (both) as wxPython wheel path changed, rely on a more persistent URL instead.
 
  • Like
Reactions: purgy and Slim2none4u
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
tim1aust said:
2 questions in re. PixelFlasher and P7a.. a) is P7a supported yet? (seems like yes) b) is PixelFlasher from AUR for Manjaro *at the same build level* (it has 5.3.1.2 in lower left)as the one from Github, et.al?

I figured it would be easier to just have a supported AUR package, so I installed that. But when I tried to use it for P7a with latest Full image, it couldn't patch the file (said it couldn't find boot.img). Of course, for P7 & P7a, it should firstly be looking for init_boot.img. Could it be due to the fact that this was a new phone which didn't yet have Magisk installed? (I guess that's 3 questions :) Anyway, I wound up gettng Magisk installed from scratch, so my P7a now has it installed. I'm hoping to use PixelFlasher from AUR next time.

TIA,
Tim
Click to expand...
Click to collapse

Original Post:
@tim1aust
I'm answering you in here to keep the Magisk thread clean of PF specific discussions.

Yes, PF supports Pixel 7a (lynx)
If you provide a support file, I could check what might have happened.
 
tim1aust

tim1aust

Member
May 27, 2023
14
11
Thanks for answering, and pointing me to correct thread.

Unfortunately, I don't have a support file, unless the tool automatically saved one and I wasn't paying attention.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
tim1aust said:
Thanks for answering, and pointing me to correct thread.

Unfortunately, I don't have a support file, unless the tool automatically saved one and I wasn't paying attention.
Click to expand...
Click to collapse
Yes, the tool creates logs, and when you click on the support button, it processes them and redacts sensitive information and creates a zip file for upload.
All you have to do is launch PF, and hit the button and share the file.
 
tim1aust

tim1aust

Member
May 27, 2023
14
11
Great, attaching it here. Thanks for your help!
 

Attachments

  • support_2023-06-21_15-15-11.zip
    111.1 KB · Views: 8
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
tim1aust said:
Great, attaching it here. Thanks for your help!
Click to expand...
Click to collapse
Thanks
Sorry I'm confused, you reported an issue with Pixel 7a (Lynx), but all I see is logs regarding Pixel 7 (Panther).
You mentioned about failed patching.
But I see nothing wrong with patching.


Code: 
Creating a patch ...
Cleaning up...
- Unpacking boot image
Parsing boot image: [/sdcard/Download/init_boot_bea42eca.img]
HEADER_VER      [4]
KERNEL_SZ       [0]
RAMDISK_SZ      [2068178]
PAGESIZE        [4096]
CMDLINE         []
RAMDISK_FMT     [lz4_legacy]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
- Pre-init storage partition device ID: REDACTED
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk64.xz] (0644)
Add entry [overlay.d/sbin/stub.xz] (0644)
Patch with flag KEEPVERITY=[true] KEEPFORCEENCRYPT=[true]
Loading cpio: [ramdisk.cpio.orig]
Backup mismatch entry: [init] -> [.backup/init]
Record new entry: [overlay.d] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/stub.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/sdcard/Download/init_boot_bea42eca.img]
HEADER_VER      [4]
KERNEL_SZ       [0]
RAMDISK_SZ      [2068178]
PAGESIZE        [4096]
CMDLINE         []
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER      [4]
KERNEL_SZ       [0]
RAMDISK_SZ      [2528130]
PAGESIZE        [4096]
CMDLINE         []
PATCH_SHA1:     081f1391
PATCH_FILENAME: magisk_patched_26100_bea42eca_081f1391.img
Cleaning up ...
Checking patch log: /data/local/tmp/pf_patch.log ...
Getting file content of /data/local/tmp/pf_patch.log on the device ...
Return Code: 0
Deleting /data/local/tmp/pf_patch.log from the device ...
Return Code: 0

Looking for magisk_patched_26100_bea42eca_081f1391.img in /storage/emulated/0/Download ...
Checking for /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img on the device ...
File: /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img is found on the device.
Pulling /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img from the phone to: magisk_patched_26100_bea42eca_081f1391.img ...
Pulling remote file: /storage/emulated/0/Download/magisk_patched_26100_bea42eca_081f1391.img from the device to: "/home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img" ...
Return Code: 0
Getting SHA1 of /home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img ...
SHA1 of magisk_patched_26100_bea42eca_081f1391.img file: 081f1391b700afb8ef5b28b4dce6db0bdb6d5d38

Getting SHA1 of source init_boot.img ...
Source init_boot.img's SHA1 is: bea42eca0a4e06eac0e876c2e7b9f518ade87874

Extracting SHA1 from magisk_patched_26100_bea42eca_081f1391.img ...
SHA1 embedded in /home/REDACTED/.local/share/PixelFlasher/tmp/magisk_patched_26100_bea42eca_081f1391.img is: bea42eca0a4e06eac0e876c2e7b9f518ade87874
Comparing source init_boot.img SHA1 with SHA1 embedded in bea42eca0a4e06eac0e876c2e7b9f518ade87874 (they should match) ...
Good: Both SHA1s: bea42eca0a4e06eac0e876c2e7b9f518ade87874 match.


Magisk Version: 26.1:26100
Patch time: 5 seconds
 
tim1aust

tim1aust

Member
May 27, 2023
14
11
The attempt was made yesterday.. 6-20. Is there a log from that date? The ones for panther were when I was using PF for my P7.

--tim
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
3,035
4,684
tim1aust said:
The attempt was made yesterday.. 6-20. Is there a log from that date? The ones for panther were when I was using PF for my P7.

--tim
Click to expand...
Click to collapse
OK I see it now.
What is this file? where did it come from?
lynx-factory-23410002.zip

Code: 
Selected Firmware lynx-factory-23410002.zip SHA-256: 033c2d0381aec8e4538a393baa9fdd86bfc7f24578fa8e4db9f7d9ea49756948
 
You must log in or register to reply here.

Similar threads

2015Ducatimulti
Question Who Ordered the Pixel 7A?
Replies
51
Views
4K
st0nedpenguin
st0nedpenguin
Dayuser
General Google Pixel 7a reviews
Replies
9
Views
2K
drchips42
drchips42
V
Development Paranoid Android Topaz Beta 1 - Pixel 7a
Replies
21
Views
3K
insestito
insestito
2015Ducatimulti
Question Pixel 7A rooted use "Pixel 7 pro root guide"
Replies
5
Views
2K
Saswata Chakraborty
Saswata Chakraborty
V
Development [ROM] [OFFICIAL] PixelBlaster-OS v6.4 for Pixel 7a [13]
Replies
16
Views
2K
C
Cheesytators

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 8
    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 7a 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
    4
    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
    3
    badabing2003
    badabing2003
    New Release:
    June 23, 2023 v5.3.3.0 release
    • #79 Bug-fix: Package Manager column stays unsorted when filtered.
    • Warn users that extract the contents of firmware and use the image inside as firmware, which is no good.
    • Warn users of Android Platform-Tools 34.0.3 about potential issues and suggest using 33.0.3
    • Package manager bug fixes and improvements.
    View
    3
    badabing2003
    badabing2003
    New Release:
    July 16, 2023 v5.5.1.1 release
    • #84, further UI improvements for smaller screens.
    • Better dark mode handling for MacOS and Linux.
    • #86, improved handling of space characters in paths.
    View
    3
    badabing2003
    badabing2003
    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.
    View

New posts