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

Search This thread

Thebear j koss

Senior Member
I think you mean slot. It's important to understand that each CRITICAL partition has two slots - bootloader_a, bootloader_b; boot_a, boot_b; system_a, system_b. However, the /data partition has only one slot. This is why it is not possible to "dual boot" on A/B devices.

My point was that while making nandroid backups with TWRP is pretty convenient, it should also be possible to dump the partitions of a slot via ADB without using TWRP.

Additionally, it's not the A/B layout itself that makes custom recovery difficult; it's the fact that most A/B devices do not have a bespoke /recovery partition; instead, the recovery kernel is in the boot image, alongside the system kernel. This normally isn't a problem, as installing TWRP (the right way, by patching the boot image) replaces the recovery kernel with TWRP; the problem is, since Magisk also patches the boot image, it seems the two do not play well together. I have been unable to install both TWRP and Magisk; this results in a boot loop.

Therefore, I maintain that the best way to use TWRP is via live booting, and it should not be installed..
Ok, it doesn't really matter as on a pixel device your data should be getting backed up and 1 slot should have a working boot if you are switching a & b on system/security updates. (Besides the google gaffe of the android 13 update of needing both slots updated). I liked custom recoveries, but they aren't really necessary, and on newer devices not feasible at this point. I wasn't disagreeing with you, but as stated also above there are other options to backup things and you should always have a working slot to boot.
 

V0latyle

Forum Moderator
Staff member
Ok, it doesn't really matter as on a pixel device your data should be getting backed up
Some data is backed up. App data and anything in storage (besides photos) is not.
and 1 slot should have a working boot if you are switching a & b on system/security updates. (Besides the google gaffe of the android 13 update of needing both slots updated). I liked custom recoveries, but they aren't really necessary, and on newer devices not feasible at this point. I wasn't disagreeing with you, but as stated also above there are other options to backup things and you should always have a working slot to boot.
I don't really understand what your point is? Of course we all want our devices to work; it seems like you're saying one slot should be kept "pristine" while you make changes to the other slot? This isn't necessarily a good idea - you can't flash a custom ROM on slot B while you have the stock firmware on slot A. I mean, you can, but it won't work because both slots share the same /data partition.

If you're talking about updates, this is really just a matter of preference - some people prefer to update alternate slots via OTA, while others (like myself) like to flash both slots every time using the factory image.
 
Thanks for the useful information. Like I said earlier, I've been out of rooting/mods/custom stuff for about the last 5 years, so it's like learning to do things all over again as things have changed a lot. The more questions and answers posted on this topic the more it helps me understand how things work since they have changed. It will help others as well (so long as they read the discussion). Pixel Flasher is a life saver for me after being out of the game for so long. Same as Wugfresh's toolkit helped me back in the day.
 

badabing2003

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

badabing2003

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

Kris Chen

Senior Member
Jan 10, 2013
748
316
Taoyuan
Google Pixel 6 Pro
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.

New version v4.5 cannot be opened in my Win11 pro.
I checked the background and I found pixelflasher was running but it just couldnot be loaded on my win11 pro desktop.
Even I tried to kill them all and tried it again, the result was the same.Now I tried v4.4 to flash new releasing Dec ROM and without any problem.
I hope developer to fix it.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,563
1,841
New version v4.5 cannot be opened in my Win11 pro.
I checked the background and I found pixelflasher was running but it just couldnot be loaded on my win11 pro desktop.
Even I tried to kill them all and tried it again, the result was the same.Now I tried v4.4 to flash new releasing Dec ROM and without any problem.
I hope developer to fix it.
Thanks, I'm aware, I just don't have any data / error logs to understand what is going on, and I cannot reproduce the issue on multiple Windows 11 computers.

See this issue at GitHub.
See if any worked for you, and if you can try with AV off, that could help.
Please supply support.zip, you can generate it with 4.4.0.0
Hopefully the logs will include something.
 

bush911

Senior Member
Oct 12, 2012
814
345
重庆
Google Nexus 5
Google Pixel
New version v4.5 cannot be opened in my Win11 pro.
I checked the background and I found pixelflasher was running but it just couldnot be loaded on my win11 pro desktop.
Even I tried to kill them all and tried it again, the result was the same.Now I tried v4.4 to flash new releasing Dec ROM and without any problem.
I hope developer to fix it.
same for windows 10
 

badabing2003

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

badabing2003

Recognized Contributor
Sep 17, 2012
1,563
1,841
What I was wondering is whether I can use your flasher to update Pixel 3 from Android 11 to latest Android 12.
I pixel 3 was rooted and was with Lsposed and several moudules.
Yes you should be able to.
  • Download the Android 12 firmware
  • process
  • create patch
  • disable Magisk modules (you can do so in PF) (you can keep Safetynet fix and systemless hosts enabled)
  • flash
  • enable modules that are safe to enable,
 

bush911

Senior Member
Oct 12, 2012
814
345
重庆
Google Nexus 5
Google Pixel
Yes you should be able to.
  • Download the Android 12 firmware
  • process
  • create patch
  • disable Magisk modules (you can do so in PF) (you can keep Safetynet fix and systemless hosts enabled)
  • flash
  • enable modules that are safe to enable,
Thank you so much. It is good to know, I have already updated Pixel 6 several times via your App, which really rocks
 

Top Liked Posts

  • There are no posts matching your filters.
  • 1
    Sorry if this was said, I'm skimming the thread for now. Will read everything later.
    Will this work on the newest beta OS?
    You're aware about the issue of needing to patch p7p boot and installing it on p6p to get the beta rooted right?

    Assuming that you want to update p6p, what you could do is first extract the boot.img from P7P firmware
    After processing the p6p firmware in PF
    navigate to the directory where PF extracted the boot.img
    (Click on the boot.img in PF, and it should tell you the path in the console)
    Replace that file with the one you extracted from p7p
    patch and then flash as you would.
    If this is the first time you're using PF, please check the usage documentation.
  • 40
    PF_promo-banner.png
    This is the support thread of PixelFlasher for Google Pixel 6 Pro
    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 Pro devices, generic issues that are device agnostic should be discussed in the main thread.
    13
    New Release:
    Sep 04, 2022 v3.7.0 release
    • New Feature: Install Magisk into the phone, PixelFlasher displays information about the latest available Magisk versions (stable, beta, canary, debug) and offers the choice to install a selection.
    • New Feature: Install compatible apk file onto the device from PixelFlasher menu.
    • Check Android Platform Tools version and warn if it is old.
    • Block flashing when stock flash_all.bat file is tampered with.
    • Don't bother with flashing if bootloader is locked.
    • More validations and exceptions handling.
    • Improved logging.
    11
    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.
    10
    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.
    10
    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.