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

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
New Release: (See full details here on xda or here at github)
April 03, 2022 v2.0.0.0-pre release.
  • Major refactoring
  • Added Advanced (Expert) mode UI.
  • Basic mode keeps UI simple and hides expert features.
  • Support for setting active slot.
  • Reboot options (recovery, system, bootloader)
  • Moved custom ROM options to expert mode.
  • Added custom flashing to expert mode, can now flash to live (temporary root), or custom flash any image to any partition.
  • Moved flashing to both slots, disabling verity / verification to expert mode.
  • Many other improvements, validations and checks.
  • Updated documentation.
 

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
This error doesn't make sense to me. Got this while trying to prepare 12.1.0 (SP2A.220305.013.A3, Mar 2022):

Code:
PixelFlasher 2.0.0.0

No previous flashable package is found for the selected firmware!
Selected Device:
    Device ID:          1C041FDF6000G1
    Device Model:       oriole
    Device is Rooted:   True
    Device Build:       SQ1D.220205.004
    Device Active Slot: a
    Device Mode:        adb
    Magisk Version:     24.3:MAGISK (24300)

Rebooting device 1C041FDF6000G1 to bootloader ...

==============================================================================
  PixelFlasher 2.0.0.0             Preparing Package                              
==============================================================================
ERROR: Android device model oriole does not match firmware model Pixel6
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
This error doesn't make sense to me. Got this while trying to prepare 12.1.0 (SP2A.220305.013.A3, Mar 2022):

Code:
PixelFlasher 2.0.0.0

No previous flashable package is found for the selected firmware!
Selected Device:
    Device ID:          1C041FDF6000G1
    Device Model:       oriole
    Device is Rooted:   True
    Device Build:       SQ1D.220205.004
    Device Active Slot: a
    Device Mode:        adb
    Magisk Version:     24.3:MAGISK (24300)

Rebooting device 1C041FDF6000G1 to bootloader ...

==============================================================================
  PixelFlasher 2.0.0.0             Preparing Package                             
==============================================================================
ERROR: Android device model oriole does not match firmware model Pixel6
Can you show what firmware file did you select? (full filename / path)
 

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
Ok, the tenth time it worked. I have no idea why. But after the preparation has finished i get this error when trying to flash:

Code:
Traceback (most recent call last):
  File "Main.py", line 489, in _on_flash
  File "modules.py", line 728, in flash_phone
AttributeError: 'NoneType' object has no attribute 'id'
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
C:\Hämtade Filer\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip
That is really weird.
The fact that it reported that the firmware model is Pixel6, it means that the selected factory image was named pixel6.zip
The program picks up the factory image model from the filename
In this case `oriole-sp2a.220305.013.a3-factory-8bea92d1.zip` , and it extracts the first portion of the name before `-`
Seeing that there is no Pixel6 in your filename, I'm quite stumped, by any chance is it possible that you initially chose a filename that was named pixel6?
I asked for full path in case there was local / issues that was tripping on parsing
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
Ok, the tenth time it worked. I have no idea why. But after the preparation has finished i get this error when trying to flash:

Code:
Traceback (most recent call last):
  File "Main.py", line 489, in _on_flash
  File "modules.py", line 728, in flash_phone
AttributeError: 'NoneType' object has no attribute 'id'
do you mind turning on verbose mode , clearing the console, selecting the firmware, the phone, and then hitting the prepare package, and share full console output?

You can share privately if you want.
 

RobbyRobbb

Senior Member
Aug 17, 2012
170
32
Code:
PixelFlasher 2.0.0.0 started on 2022-04-04 18:06:25
debug: Loading configuration file: C:\Users\Admin\AppData\Roaming\PixelFlasher.json ...
debug: {
    "advanced_options": false,
    "custom_rom": false,
    "custom_rom_path": null,
    "device": null,
    "disable_verification": false,
    "disable_verity": false,
    "firmware_path": "C:\\H\u00e4mtade Filer\\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip",
    "flash_both_slots": false,
    "height": 918,
    "magisk": "com.topjohnwu.magisk",
    "mode": "keepData",
    "patch_boot": true,
    "phone_path": "/storage/emulated/0/Download",
    "platform_tools_path": "C:\\Android\\cmdline-tools\\platform-tools",
    "verbose": true,
    "version": "2.0.0.0",
    "width": 1328
}

Previous flashable package is found for the selected firmware!
The package is of the following state.

Patch Boot:           True
Custom Rom:           False



Selected Device:
    Device ID:          1C041FDF6000G1
    Device Model:       oriole
    Device is Rooted:   True
    Device Build:       SQ1D.220205.004
    Device Active Slot: a
    Device Mode:        adb
    Magisk Version:     24.3:MAGISK (24300)


==============================================================================
  PixelFlasher 2.0.0.0             Preparing Package                               
==============================================================================
Found a previous package oriole-sp2a.220305.013.a3 deleting ...
debug: Resource Dir: C:\Temp\Tmp\_MEI11922\bin\7z.exe
Found Bundled 7zip.
zip/unzip operations will be faster
Unzipping Image: C:\Hämtade Filer\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip into C:\Android\cmdline-tools\platform-tools ...
debug: "C:\Temp\Tmp\_MEI11922\bin\7z.exe" x -bd -y "C:\Hämtade Filer\oriole-sp2a.220305.013.a3-factory-8bea92d1.zip"
Unzip time1: 3 seconds
Unzipped into oriole-sp2a.220305.013.a3 folder.
Extracting boot.img from image-oriole-sp2a.220305.013.a3.zip ...
debug: "C:\Temp\Tmp\_MEI11922\bin\7z.exe" x -bd -y -o"C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3" "C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3\image-oriole-sp2a.220305.013.a3.zip" boot.img
Unzip time2: 1 seconds
Deleting boot.img from phone in /storage/emulated/0/Download ...
Making sure boot.img is not on the phone in /storage/emulated/0/Download ...
Deleting magisk_patched.img from phone in /storage/emulated/0/Download ...
Making sure magisk_patched.img is not on the phone in /storage/emulated/0/Download ...
Transfering boot.img to the phone in /storage/emulated/0/Download ...
debug: "C:\Android\cmdline-tools\platform-tools\adb.exe" -s 1C041FDF6000G1 push "C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3\boot.img" /storage/emulated/0/Download/boot.img
C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3\boot.img: 1 file pushed, 0 skipped. 160.6 MB/s (67108864 bytes in 0.399s)

Making sure boot.img is found on the phone in /storage/emulated/0/Download ...
Detected a rooted phone with Magisk Tools: 24.3:MAGISK (24300)

Creating patched boot.img ...
- Unpacking boot image
Parsing boot image: [/sdcard/Download/boot.img]
HEADER_VER      [4]
KERNEL_SZ       [23250567]
RAMDISK_SZ      [1380095]
OS_VERSION      [12.0.0]
OS_PATCH_LEVEL  [2022-03]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [lz4_legacy]
RAMDISK_FMT     [lz4_legacy]
VBMETA
- Checking ramdisk status
Loading cpio: [ramdisk.cpio]
- Stock boot image detected
- Patching ramdisk
Loading cpio: [ramdisk.cpio]
Add entry [init] (0750)
Create directory [overlay.d] (0750)
Create directory [overlay.d/sbin] (0750)
Add entry [overlay.d/sbin/magisk32.xz] (0644)
Add entry [overlay.d/sbin/magisk64.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/magisk32.xz] -> [.backup/.rmlist]
Record new entry: [overlay.d/sbin/magisk64.xz] -> [.backup/.rmlist]
Create directory [.backup] (0000)
Add entry [.backup/.magisk] (0000)
Dump cpio: [ramdisk.cpio]
- Repacking boot image
Parsing boot image: [/sdcard/Download/boot.img]
HEADER_VER      [4]
KERNEL_SZ       [23250567]
RAMDISK_SZ      [1380095]
OS_VERSION      [12.0.0]
OS_PATCH_LEVEL  [2022-03]
PAGESIZE        [4096]
CMDLINE         []
KERNEL_FMT      [lz4_legacy]
RAMDISK_FMT     [lz4_legacy]
VBMETA
Repack to boot image: [new-boot.img]
HEADER_VER      [4]
KERNEL_SZ       [23250567]
RAMDISK_SZ      [1956730]
OS_VERSION      [12.0.0]
OS_PATCH_LEVEL  [2022-03]
PAGESIZE        [4096]
CMDLINE         []
Patch time: 7 seconds

Looking for magisk_patched.img in /storage/emulated/0/Download ...
Found /storage/emulated/0/Download/magisk_patched.img
Pulling /storage/emulated/0/Download/magisk_patched.img from the phone ...
debug: "C:\Android\cmdline-tools\platform-tools\adb.exe" -s 1C041FDF6000G1 pull /storage/emulated/0/Download/magisk_patched.img "C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3\magisk_patched.img"
Replacing boot.img with patched version ...
debug: "C:\Temp\Tmp\_MEI11922\bin\7z.exe" a "C:\Android\cmdline-tools\platform-tools\oriole-sp2a.220305.013.a3\image-oriole-sp2a.220305.013.a3.zip" boot.img
Package is successfully created!
Zip time: 4 seconds
Total elapsed time: 17 seconds
Traceback (most recent call last):
  File "Main.py", line 489, in _on_flash
  File "modules.py", line 806, in flash_phone
UnboundLocalError: local variable 'fastboot_options' referenced before assignment
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
Silly question. If I am understanding it, it is written in python. Is there any plans on porting it to linux?
Not silly at all, that's the idea, to have it ported to other platforms

I do have have few other neat features in the pipeline that I'm working on, so this might take a back seat, though I do welcome a pull request if someone wants to tackle that.
 

tom1807

Senior Member
Tested the program today, worked flawlessly. And very fast, if keeping in mind that Google needs a "lifetime" for optimizing the device.
I saw the problem reported above, is there a possibility that the program has a problem when the filepath has special letters?
In this case "C:\Hämtade Filer\". or maybe the space between the 2 words?

Cheers
Tom
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
Tested the program today, worked flawlessly. And very fast, if keeping in mind that Google needs a "lifetime" for optimizing the device.
I saw the problem reported above, is there a possibility that the program has a problem when the filepath has special letters?
In this case "C:\Hämtade Filer\". or maybe the space between the 2 words?

Cheers
Tom
If you look at the debug output, you'd see that file paths are passed between double quotes, this was fixed few versions ago, so space is definitely not an issue anymore.
Local potentially could be (as my locale is English), but I think it is not either, you can see that RobbyRobb confirmed that it is working fine for him, the issue he experienced was an oversight on my part not initializing a variable in basic mode, which got fixed with hotfix 2.0.1.
t-ryder in Germany also has it working without any issues, so I think we don't have a locale issue either.

In case you discover anything that does not work, just report it here or at Github, and I'll tackle it.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    Google released SDK Platform-Tools v34.0.1
    Changelog:


    Cheers
    Tom
    The link still points to 34.0.0. Also, the changelog doesn't include the skipping of fastbootd issue (268872725) so I would recommend people still use 33.0.3 for now if flashing factory images or anything else which may need to be flashed in fastbootd.
    2
    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.
    1
    The link still points to 34.0.0. Also, the changelog doesn't include the skipping of fastbootd issue (268872725) so I would recommend people still use 33.0.3 for now if flashing factory images or anything else which may need to be flashed in fastbootd.
    Damn it, you are right, I thought they would have updated the link, but there is also no direct link available.
    1
    Awesome thank you. But where can I find 25206? I looked on releases I didn't see it. I'm sure I just didn't look in right place
    This should be it...

    1
    .... See I did look on that repo too I passed it right up. Thanks again. I'm gonna use that to patch my .img. Then I'll get back to you if for some reason I don't gain root
  • 17
    PF_promo-banner.png

    This is the support thread of PixelFlasher for Google Pixel 6
    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 manual steps) 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 (or init_boot.img for Pixel 7 / 7 Pro).
      • 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 or patched image.
      • Flash just the boot / init_boot image.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Option to flash to inactive slot.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Device architecture.
      • 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.
      • Active slot.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable (official)
      • beta (official)
      • canary (official)
      • debug (official)
      • alpha
      • delta
      • special build that disables modules, used to recover from bootloops due to bad module(s) when safe mode does not work.
    • Magisk Backup Manager, screenshot.
      • 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.
    • 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 (an app) 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.
    • Package (Application) Manager, screenshot:
      • Disable (Freeze)
      • Enable
      • Uninstall
      • Install APK
      • Download APK
      • Multi-Select
      • Show Package Details.
    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 6 devices, generic issues that are device agnostic should be discussed in the main thread.
    6
    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.
    5
    Thank you for the consideration.
    No donation, this is simply giving back to the community that has given me a lot over the years.
    5
    Update:
    Version 2.0.1 which includes a hotfix for issue reported here.
    5
    New Release:
    April 17, 2022 v2.3.0 release
    • Optional automatic check for updates feature.
    • Added help menu links to:
      - Report an issue
      - Feature Request
      - PixelFlasher Project Page
      - PixelFlasher Community (Forum)
      - Homeboy76's Guide
      - V0latyle's Guide
      - Open Configuration Folder
      - Check for New Version
    • Icons for menu items.
    • Link to download Pixel Firmware.
    • Link to download Android Platform Tools.
    • Unlock Bootloader.
    • Lock Bootloader.
    • SOS (experimental) - disable Magisk modules to get out of bootloop.
    • Additional flashing options:
      - product
      - system
      - system_ext
      - system_other
      - vbmeta_system
      - vbmeta_vendor
    • Added sideload flashing option.
    • Updated documentation.
    • Further improved console messages for troubleshooting.
    • Linux build using Github Actions.
    • Manual build for Kali Linux.