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

Search This thread

tom1807

Senior Member
I am aware that these commands won't brick anything, it was more like hint for "happy to help".
Below the output of the command "adb shell cd /data/local/tmp; /data/local/tmp/busybox unzip /data/local/tmp/pf.zip"

C:\ADB>adb shell cd /data/local/tmp; /data/local/tmp/busybox unzip /data/local/tmp/pf.zip
Archive: /data/local/tmp/pf.zip
inflating: AndroidManifest.xml
inflating: classes.dex
inflating: META-INF/MANIFEST.MF
inflating: META-INF/CERT.SF
inflating: META-INF/CERT.RSA

pf.zip attached

Cheers
Tom
 

Attachments

  • pf.zip
    26.5 KB · Views: 8
  • Like
Reactions: badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
I am aware that these commands won't brick anything, it was more like hint for "happy to help".
Below the output of the command "adb shell cd /data/local/tmp; /data/local/tmp/busybox unzip /data/local/tmp/pf.zip"



pf.zip attached

Cheers
Tom
Thanks,
I see what is happening,
When you hide Magisk Manager, it gets replaced with just a stub, which does not include the assets required to create a patch file.
Later I'll make changes to PF to only attempt to use the root Magisk to create a patch when Magisk is hidden.
And I'll probably revive Manual and UIAutomator choices.

Thanks for helping out with the troubleshooting.
 
  • Like
Reactions: tom1807

badabing2003

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

badabing2003

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

awesomeo3000

Member
Dec 29, 2011
38
12
@awesomeo3000
Please provide support.zip (PixelFlasher Menu | Help)
That would allow me to analyze what might have gone wrong.

I suspect fastboot drivers, but have to check to be certain.
I haven't been able to open PixelFlasher since then. When I open it, it just freezes on loading, and never opens. Running MacOS 12.2. Will try to re-install PixelFlasher and run the Android install to the phone again.

When I use PixelFlasher to install updates, will it keep the root on my phone, along with other things like custom propsconf settings? Or will I need to redo those after every update?
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
I haven't been able to open PixelFlasher since then. When I open it, it just freezes on loading, and never opens. Running MacOS 12.2. Will try to re-install PixelFlasher and run the Android install to the phone again.

When I use PixelFlasher to install updates, will it keep the root on my phone, along with other things like custom propsconf settings? Or will I need to redo those after every update?
In your initial report here you reported a problem with flashing, but you did not include logs from the flashing part
That is why I asked for support.zip
You also didn't have an issue launching PixelFlasher.
What changed? Why can't you launch it anymore?

When flashing has gone ok, the phone should boot to system, the fact that you had to reboot to system yourself suggests that the flashing process did not complete.

If you follow the Basic mode guide, and Keep data with selected patched image, you will retain root
As for retaining build.props, I don't know, I suspect not, that is part of System which is updated.

You can also grab the log files from
~/Library/Application Support/PixelFlasher/logs
But they won't be sanitized.
 

pdaemon

Member
Nov 11, 2011
14
0
Hi,

I'm running Linux Mint 21 and previously Pixel Flasher was working...now it loaded, but when I click on Browse for example it crashes and comes up with the following errors in the console:

[email protected]:/mnt/Datastore/Media/Android ROMS$ ./PixelFlasher-Linux
Loading configuration File ...

(PixelFlasher-Linux:1355406): Gtk-WARNING **: 08:42:17.220: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
Aborted (core dumped)


I'm running the latest version of Pixel Flasher. I tried creating the sanitized log, but it crashes when I try and do that. All other applications on my systems are running OK.

Thanks!

Regards
pdaemon
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
Hi,

I'm running Linux Mint 21 and previously Pixel Flasher was working...now it loaded, but when I click on Browse for example it crashes and comes up with the following errors in the console:

[email protected]:/mnt/Datastore/Media/Android ROMS$ ./PixelFlasher-Linux
Loading configuration File ...

(PixelFlasher-Linux:1355406): Gtk-WARNING **: 08:42:17.220: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../../../../gtk/gtkiconhelper.c:494:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/Mint-Y/actions/16/image-missing.svg: Unable to load image-loading module: /usr/lib/x86_64-linux-gnu/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: /lib/x86_64-linux-gnu/librsvg-2.so.2: undefined symbol: pango_attr_overline_new (gdk-pixbuf-error-quark, 5)
Aborted (core dumped)


I'm running the latest version of Pixel Flasher. I tried creating the sanitized log, but it crashes when I try and do that. All other applications on my systems are running OK.

Thanks!

Regards
pdaemon
Can you please try running the Kali version?
Lots of people have better success with Kali build.
I know this thing is supposed to be cross platform, WxPython is pita to get it to build.
Of course you can always try building it yourself.

Let me know how it goes.
 

pdaemon

Member
Nov 11, 2011
14
0
Can you please try running the Kali version?
Lots of people have better success with Kali build.
I know this thing is supposed to be cross platform, WxPython is pita to get it to build.
Of course you can always try building it yourself.

Let me know how it goes.
Hi,

That is working!

Thanks alot....just wondering...what's the difference? Are you able to incorporate the changes, so that the Linux version works?

Cheers pdaemon
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
Hi,

That is working!

Thanks alot....just wondering...what's the difference? Are you able to incorporate the changes, so that the Linux version works?

Cheers pdaemon
Like I said building these are a major Pita.
There is no difference between the two in terms of functionality, it's the WxPython module that runs into issues with GTK.
If Kali build works, just use that, no one yet have reported issues with it.
I might drop building the Ubuntu one and just rename the Kali build Linux :)
 

pdaemon

Member
Nov 11, 2011
14
0
Like I said building these are a major Pita.
There is no difference between the two in terms of functionality, it's the WxPython module that runs into issues with GTK.
If Kali build works, just use that, no one yet have reported issues with it.
I might drop building the Ubuntu one and just rename the Kali build Linux :)
Ok, thanks, that sounds good!

I appreciate you getting back to me so quickly!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
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,354
1,550
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.
 
  • Like
Reactions: tom1807

badabing2003

Recognized Contributor
Sep 17, 2012
1,354
1,550
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.)
 

flobo09

Member
Jan 26, 2011
38
5
Just a suggestion but shouldn't PixelFlasher flash to both slots by default?

I have been using it for a few months & while it had always worked with no issue before, something ****ed up there & it bricked my Pixel 6 trying to flash/upgrade to Android 13 & triggering anti rollback on the other slot that was still A12.

It's fine as i have multiple phones, did a warranty exchange & google replaced my Pixel 6 within a few days with a brand new one.
I flashed A13 on both slots right away to be safe and it's all working perfectly again but it feels to me this issue could all be avoided if it always flashed to the inactive slot as well by default.

It looks "safer" to me, am i missing something obvious there?
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Maybe I still have a chance because even though adb devices does not return any devices, I can fastboot reboot the device from terminal. So I can probably flash some image, but I don't want to try anything randomly right now so waiting to see if anybody has ideas. Now I wish I could cross-post this with the pixel 7 thread.
    Good news. I used Android Flash Tool to flash TD1A.221105.001 (9104446). Lost all my configurations, but phone is working again. Though I still get the "your device is corrupt" message, but now it works when you press continue and I can boot into the phone. So now I repeated all the manual command executions. And now it worked fine, and I have root.

    God I wish I wasn't so stupid yesterday and flashed the boot.img. Is there a way to get rid of the "your device is corrupt" message?!#@!
    1
    @awesomeo3000
    Something is not right on your Mac.
    Looking at the terminal output you sent, I see lots of wrong things there.
    But don't fret, this can be solved / fixed, you don't want to go through this every month.
    Reach out to me privately pass me your username and device id, so that I give you precise commands to execute.
    Probably best when we're both are online at the same time.
    Tell me about your availability / timezone.
    Once I do, I would need execution of one command and one command only (no multiple tries of different variations), based on the output of that, I will give you the next command.
    Troubleshooting 101 :)

    I have to ask you, you said you had to wipe your device or at least it ended up wiped.
    Is wiping still an available option to you? or you rather not?
    There are different ways to approach this, and if wiping is an option, we'll take the easy route of clean start.
    1
    Hi all!

    I would like to root my Pixel 6 but I've been out from the modding scene since 2017 and everything is different now! My Pixel 6 is bootloader-locked, stock Android 13 manual installed when it came out via adb (didn't want to wait for the ota).

    I'm having difficult times understanding if I can root directly with this tool and also the slots thing, does it apply to my case too?

    Thanks in advance!
    I encourage everyone to read up on the guides, learn the what it takes to mod manually before jumping into using automated tools that do it for you.
    Granted the learning curve at first could be steep, but the benefits are enormous, if anything goes wrong or not according to the plans, you would know how to recover.

    If you still want to use PF without investing in learning the manual way,
    The Basic Usage steps on the Main page page or the Github page is what you need to follow.
    However considering that you're bootloader is locked, you need to unlock it first, PF has a button to do it, but it is not part of the automated process, as one would probably do this once.
    Furthermore to be able to unlock the bootloader, you need to enable developer mode, turn on OEM unlock and ADB Debugging ...
    Details of all of these are mentioned in the Guide threads, there are few great such guides links in the Help menu of PF, and you probably could find other good guides as well.

    Speaking of slots, it applies to your device, Pixel 6 has two slots, but you don't have to worry about it, the only recommendation I would make is flash to inactive slot, this way if anything goes wrong, you can still go back to the previous slot, and if everything goes well, the inactive becomes the current active and you're good,
    You repeat that on next month's release, this way you always have something to fallback to.

    Good luck and don't shy away to ask questions if anything is unclear.
    1
    I think I will follow the part about unlocking bootloader and then use your tool to root. Is this fine?
    Yes this is fine

    I still don't understand the part about slots, when should I enable "flash to inactive slot"? When I flash the boot.img or the patched_boot.img?
    Typically with PF, you don't flash the boot.img, you flash the patched_boot.img, PF automates the process for you so that with one flash you're updated and patched.

    The basic flow is as follows
    - you download a firmware, and select it in PF, no need to unpack the zip or extract files from it, just point to it, PF does the rest.
    - you process the firmware (just press the button) which extracts and shows the the boot.img
    - you select the boot and press the patch button
    - you select your flash options (this is when you choose flash to inactive slot, and keep data)
    - you flash
    1
    Did everything and all went like a charm! So easy and straightforward!

    I still have a question about monthly updates: Which updates I'm allowed to do directly on phone and which need to be done via PF to preserve root?

    Thanks again for your help!
    I wouldn't do anything on the phone,
    Much easier / quicker / reliable to do on PF,
    Repeat the process as you did now.
  • 16
    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 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 6 devices, generic issues that are device agnostic should be discussed in the main thread.
    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.
    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.