Themes / Apps / Mods PixelFlasher for Google Pixel 6a Support Thread.

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
Not sure if this should be of concern, but upgrading to today's Android release, I got this (very early on, while selecting the device and firmware):

Code:
2022-09-12 18:44:06 ERROR: Exception during Magisk modules processing
Exception: not enough values to unpack (expected 2, got 1)

Everything seemed to work fine, though.
Thanks for reporting it,
Yeah that does not effect patching or flashing, it's just about get list of Magisk modules and managing them.

If you could provide a support.zip file I can take a look.
This way whatever is causing it, could be addressed in the next version.
Thanks
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
PixelFlasher 4.0.0 pre-release:
Sep 25, 2022 v4.0.0 pre-release
  • New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
    See Patching flow chart for details.
  • New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
  • New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
  • New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
  • New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
    Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
  • New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
  • New spinner to indicate PixelFlasher activity.
  • Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
  • PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
    This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
  • PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
    This is just an extra validation.
  • Code cleanup / refactoring, adding more validations and exception handling.
  • Print debug details when encountering non compliant Magisk modules.
  • Firmware link now takes you to the device's download page instead of just the general download page.
  • To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
  • Allow sideload even if bootloader is locked.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
New Release:
Oct 03, 2022 v4.1.0 release

  • Patching is now fully automatic with or without root.
    PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)
    UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.
  • Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.
  • Speed improvements for device property reading.
  • Speed improvements for Magisk modules reading.
 
  • Like
Reactions: Meloferz

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
  • NOTICE:
    I'm marking version 4.1.0 release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.
    On my test phones they were available.
    Unless you have unzip on your phone, you should avoid using this version.
    Sorry about this oversight.
 
  • Like
Reactions: Meloferz

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
Update Release:
Oct 03, 2022 v4.1.1. release
  • Bug Fix: Bundle busybox with PixelFlasher to be used for unzipping Magisk.
  • Bug Fix #25, use the Magisk Manager version number instead of Rooted Magisk version number.
  • Cosmetic changes and a bit more logging.
 
  • Like
Reactions: Meloferz

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
Update Release:
Oct 04, 2022 v4.1.2 release
  • include busybox binaries for different Android architectures (arm64-v8a, armeabi-v7a, x86_64, x86)
  • don't use hidden Magisk for patching, as it is a stub only.
 
  • Like
Reactions: Meloferz

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
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.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
New Release:
Oct 15, 2022 v4.3.0 release
  • New: You can now download and install alpha and delta Magisk versions in addition to the official stable, beta, canary and debug versions.
  • Bug fix: Generating support.zip file was modifying the main db file unnecessarily.
  • Bug fix: When patching with Magisk Manager the version of Magisk Manager was not being displayed in the boot images table.
  • Bug fix: MacOS downloaded Magisk had space in the file path, which was causing failed installation.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
Oct 16, 2022 v4.3.0.1 release
  • Bug fix: #30 Error during firmware processing file extraction phase.
  • PixelFlasher-Linux is now labeled PixelFlasher-Ubuntu (It is built on Ubuntu which is not compatible with all Linux flavors. Even though PixelFlasher-Kali is more compatible, it is still not a one size fits all solution.)
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
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.
 

gilnfld

Senior Member
Dec 14, 2009
221
118
St. John's
Hey there @badabing2003 ,

Thanks for the great flasher -- I have used this on a couple of older phones but wanted to quickly ask a flashing question for my new phone.

I have a brand new still in box Pixel 6a. I want to right away - - before doing anything else on the device -- deal with the bootloader flashing to bothe slots issue for A13. It comes with A12 on the slots and I wandered if you can walk me through the process of doing this through your app.

I am quite familiar with flashing/fastboot commands etc I just wanted to know the order in your app. I have the latest platform-tools and the latest november factory image for the 6a. As mentioned I want to do this as soon as I take the device the box. So I assume step one is boot into bootloader with combination key, do a 'fastboot flashing unlock' then fire up your app and here is where I am not entirely certain about the order; I know technically i am only needing to flash the A13 bootloader on the inactive partition install but can i just do a full install of the entire zip package with the 'flash to both slots' ?

Tnx,

gs
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
Hey there @badabing2003 ,

Thanks for the great flasher -- I have used this on a couple of older phones but wanted to quickly ask a flashing question for my new phone.

I have a brand new still in box Pixel 6a. I want to right away - - before doing anything else on the device -- deal with the bootloader flashing to bothe slots issue for A13. It comes with A12 on the slots and I wandered if you can walk me through the process of doing this through your app.

I am quite familiar with flashing/fastboot commands etc I just wanted to know the order in your app. I have the latest platform-tools and the latest november factory image for the 6a. As mentioned I want to do this as soon as I take the device the box. So I assume step one is boot into bootloader with combination key, do a 'fastboot flashing unlock' then fire up your app and here is where I am not entirely certain about the order; I know technically i am only needing to flash the A13 bootloader on the inactive partition install but can i just do a full install of the entire zip package with the 'flash to both slots' ?

Tnx,

gs
Yes you can do a full install of the entire zip package with Flash to both slots be done with it.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
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.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
New Release:
Dec 05, 2022 v4.6.0 release
  • Added single click button to easily flash just the boot/init_boot (stock or patched) to the phone.
  • #39 Display Flash Option changes in the console, and allow flashing to inactive slot in basic mode.
  • #39 Do the Magisk backup only when rooted.
  • Decouple OTA sideload from needing factory image.
  • Other minor improvements.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,443
1,679
New Release:
Dec 06, 2022 v4.6.1 release
  • #40 Handle locale related exceptions which were causing PixelFlasher to not launch on some Windows 11 systems.
  • Add the ability to download and install a special Magisk version that has modules loading intentionally disabled. Required to get out of bootloops and manage to disable modules.
    Credit to gecowa6967 at XDA.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    PF_promo-banner.png


    This is the support thread of PixelFlasher for Google Pixel 6a
    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 6a devices, generic issues that are device agnostic should be discussed in the main thread.
    5
    PixelFlasher 4.0.0 pre-release:
    Sep 25, 2022 v4.0.0 pre-release
    • New Feature: On supported devices, where device is not yet rooted (or adb shell su not allowed), an option to control the Magisk Manager GUI (drive UI) to programmatically control the app through UIAutomator and create a patched boot.img
      See Patching flow chart for details.
    • New Feature: Detect if Magisk Manager is at a higher version than installed Magisk, warn the user of a potential rare corner case and offer a choice of patching method.
    • New Feature: Temporary Root, when flashing if you choose this option, the phone will be flashed with unpatched boot.img, but Live boot to patched boot.img to provide a temporary root.
    • New Feature: Warn the user to flash both bootloader slots if their device is a Tensor device (Pixel 6, Pixel 6a, Pixel 6 Pro), if current version of OS is lower than Android 13.
    • New Feature: Flash to inactive slot. Unlike OTA flashing factory image flashing is always done on the current active slot, with this option selected, PixelFlasher will write to inactive slot. This allows one to revert to current working state in case anything goes wrong. This feature combined with Temporary Flash provides best method to test a new firmware without risking losing current working setup.
      Note: You should avoid this option if you are on a Tensor device and are upgrading from Android 12 to Android 13 (see the previous feature).
    • New Feature: Detect and operate on devices that are in Sideload or Recovery mode.
    • New spinner to indicate PixelFlasher activity.
    • Renamed Reload button to Scan, to better reflect the button's function. After a scan print the count of devices found.
    • PixelFlasher previously used MD5 to uniquely identify boot images (patched or otherwise), with version 4.0.0 PixelFlasher now uses SHA1 instead of MD5.
      This has no bearing on the functionality, it just better aligns with Magisk way of identifying and tagging boot images.
    • PixelFlasher now extracts the embedded SHA1 of a Magisk Patched images (only available in newer devices) and assures that it matches the source boot.img's SHA1.
      This is just an extra validation.
    • Code cleanup / refactoring, adding more validations and exception handling.
    • Print debug details when encountering non compliant Magisk modules.
    • Firmware link now takes you to the device's download page instead of just the general download page.
    • To better reflect the file details, transferred and stored boot.img files are now suffixed by their shortened SHA1, while magisk_patched.img files are now suffixed by shortened SHA1 of their source boot.img.
    • Allow sideload even if bootloader is locked.
    3
    This seems interesting. I was just looking into options to disable verity and or verification, root, and flash a custom kernel. It seems this application is an all in one. If all goes as planned, will my data and apps remain? Or am I basically starting all over. My bootloader is already unlocked. Thanks for sharing.
    If you don't choose wipe data, or force in flash options, then you should keep your data.
    3
    Update Release:
    Oct 05, 2022 v4.1.4 release
    • Rooted Magisk patching will now automatically back up stock-boot.img (more to come).
    • Bug Fix #27, handle version exception.
    2
    New Release:
    Aug 24, 2022 v3.6.0 release
    • When a device is selected, the Bootloader version is displayed. (Useful for Pixel 6* devices with ARB). Works in adb and fastboot modes.
    • Added a button to dump full device info (useful for troubleshooting). Works in adb and fastboot modes.
    • Improved tooltips.