📳🔥 PixelFlasher, a GUI tool for flashing / updating / rooting / managing Pixel phones.

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
I stumbled on another problem related to rooting. I tried to make it easy on myself so I did as much of the rooting as possible from the PF interface:
  1. Installed Magisk Manager from PF.
  2. Patched boot.img from PF (which is actually invoking Magisk Manager on the phone to do the actual patching if I understand right).
  3. Flashed boot.img from PF.
In step 2 a backup of boot.img is placed in the Downloads folder of my phone but I don't think Magisk Manager is aware of this backup because when I try to do Uninstall Magisk > Restore Images (so I can perform an OTA update) I get a toast notification with "Stock backup does not exists!".

When I manually rooted my phone (without the help of PF) I could run Restore Images just fine. Is this something that can be fixed on your end? Or is this a Magisk Manager issue?
Without seeing the logs, I can't tell exactly what patching process was performed.
There are many ways that PF can patch (patches) a boot image.
You can take a look at this, (which by the way is outdated) to get an idea.
boot.img file in Downloads is only there for transferring the stock boot to the phone so that it gets used by one of the methods.
If your phone is already rooted, /data/adb/magisk is used to create a patch (call it boot_patch). That process will create a stock-boot.img file which will be copied to backup on reboot (requires root) or if the Magisk manager app is launched and the phone is already rooted.
If you are not rooted, PF will use your existing Magisk Manager (if one is installed) binaries to run a process similar to boot_patch, this will run from /data/local/tmp which is the only place we can run executable without root.
The created stock_boot.img will be in a directory that Magisk will not pickup on next reboot, and it can't place it yet in the required directory (/data/adb/magisk) because the phone is not rooted yet.
By the way boot_patch method is the most robust way of patching.
PF has all the code to create a backup file based on a selected boot.img file, I just don't have the UI for it yet.
The other two patching methods are,
1- using UIAutomator to programmatically click on buttons to create a patch from Magisk UI, but UIAutomator is slow and does not necessarily work on all Android versions.
2- Launch the app, and guide the user to click on the buttons to create a patch file and then resume in PF.
Both of those methods will make Magisk create a backup on reboot, but are cumbersome.
To keep the program simple, PF right now does not take either of those two paths, the code is all there, and a UI can be added to let the user choose, but that makes the program usage for beginners even harder and more confusing.
I might add those with a flag enabled in Advanced mode.
However a better approach is add the backup manager UI, the backend code is all there and is just missing the UI, Backup manager would list all the backups on the phone and allow you to add / delete backups.
 
  • Like
Reactions: jant90

Thebear j koss

Senior Member
I stumbled on another problem related to rooting. I tried to make it easy on myself so I did as much of the rooting as possible from the PF interface:
  1. Installed Magisk Manager from PF.
  2. Patched boot.img from PF (which is actually invoking Magisk Manager on the phone to do the actual patching if I understand right).
  3. Flashed boot.img from PF.
In step 2 a backup of boot.img is placed in the Downloads folder of my phone but I don't think Magisk Manager is aware of this backup because when I try to do Uninstall Magisk > Restore Images (so I can perform an OTA update) I get a toast notification with "Stock backup does not exists!".

When I manually rooted my phone (without the help of PF) I could run Restore Images just fine. Is this something that can be fixed on your end? Or is this a Magisk Manager issue?
I think it creates a backup of the magiskboot.img in your download folder. You can always pull original boot.img from the zip you used in PF. Or you can choose original boot.img in PF and flash that using PF.
 

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Thanks,

It is recommended that out of box devices, on the first flashing you flash on both slots, that's because out of box second slot is not bootable, and you want to have both slots bootable in case anything goes wrong.

It is also recommended that monthly updates are flashed to inactive slot, this assures that your fallback alternate slot is at most one version behind.
So basically do the same thing but select INACTIVE slot? Do I have to root that slot as well? Can it be unrooted?
The reason I ask is I just tried to lock the bootloader of a Pixel that was only flashed and never updated (OTA) to send in as a trade-in and the phone came to a black screen stating no operating system is availeable. i was lucky enough to re-unlock the bootloader and the phone booted. Taking the OTA now before I try to re-lock the bootloader.
Thanks Again
EDIT: IT WORKED bootloader locked and factory reset.
 
Last edited:
  • Like
Reactions: badabing2003

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Thanks,

It is recommended that out of box devices, on the first flashing you flash on both slots, that's because out of box second slot is not bootable, and you want to have both slots bootable in case anything goes wrong.

It is also recommended that monthly updates are flashed to inactive slot, this assures that your fallback alternate slot is at most one version behind.
When it rains it pours. Tried to flash the inactive slot on a Pixel 6a. It failed and now the phone is not responsive. Will not turn on and I cannot perform a hard reset, nothing seems to work. Plugged it into the wall, and it won't even show like it is charging? Just my day, LOL!
BB
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
When it rains it pours. Tried to flash the inactive slot on a Pixel 6a. It failed and now the phone is not responsive. Will not turn on and I cannot perform a hard reset, nothing seems to work. Plugged it into the wall, and it won't even show like it is charging? Just my day, LOL!
BB
Your last reply was:
EDIT: IT WORKED bootloader locked and factory reset.
I don't understand.
 
  • Like
Reactions: J.Michael

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Your last reply was:

I don't understand.
Sorry about the confusion. TWO different phones. The first was a Pixel 4a5G that crashed trying to lock bootloader. I replied to your message in that both slots should be flashed or bad things can happen.

Not wanting "bad things to happen" I attempted to flash the inactive slot of my daughter's Pixel 6a. That is what failed. Pixel Flasher on Win 10 was showed not responding. Phone stayed powered on for a bit but then lights out, nothing, zero response from device. Hard reset does not work. PC will not recognize the devise. I currently have it plugged in and crossing my fingers. I did reset my PC, does Pixel Flasher store logs?
Thanks
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
Sorry about the confusion. TWO different phones. The first was a Pixel 4a5G that crashed trying to lock bootloader. I replied to your message in that both slots should be flashed or bad things can happen.

Not wanting "bad things to happen" I attempted to flash the inactive slot of my daughter's Pixel 6a. That is what failed. Pixel Flasher on Win 10 was showed not responding. Phone stayed powered on for a bit but then lights out, nothing, zero response from device. Hard reset does not work. PC will not recognize the devise. I currently have it plugged in and crossing my fingers. I did reset my PC, does Pixel Flasher store logs?
Thanks
Yes, PF stores logs.
Just launch it and go to help menu and generate sanitized support.zip file and post it please.
 
  • Like
Reactions: J.Michael

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Here is the file. Thanks
 

Attachments

  • PFsupport.zip
    39.1 KB · Views: 4
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
Please do not post such a huge text data, PF nicely zips the necessary files, which by the way includes more than what you pasted here.
You just have to attach that.

Your log has a single flash attempt, all the others are cancelled by you.
The flash was going fine until this

Code:
Sending sparse 'system' 1/4 (262116 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed

This sounds like the connection was dropped while writing (never a good thing).
Could be bad cable, bad driver, USB port or accidental touch / unplug
 
Last edited:
  • Like
Reactions: Bad Bimr

Bad Bimr

Senior Member
Dec 29, 2010
230
37
Please do not post such a huge text data, PF nicely zips the necessary files, which by the way includes more than what you pasted here.
You just have to attach that.

Your log has a single flash attempt, all the others are cancelled by you.
The flash was going fine until this

Code:
Sending sparse 'system' 1/4 (262116 KB) FAILED (Write to device failed (no link))
fastboot: error: Command failed

This sounds like the connection was dropped while writing (never a good thing).
Could be bad cable, bad driver, USB port or accidental touch / unplug
WOW. I use a good quality Anker cable,. It has never has given me problems, but there is always a first time I guess. Anyway you know of anyway to boot up the phone or just call Google for Warranty?
Thanks Again

EDIT: On the phone with Google.
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
WOW. I use a good quality Anker cable,. It has never has given me problems, but there is always a first time I guess. Anyway you know of anyway to boot up the phone or just call Google for Warranty?
Thanks Again
If the phone is not responding to anything and is not detected, it would be impossible to fix.
One last thing you could try is let the battery drain completely and then plug it in and see if it is detected.
Outside that Google is your best bet.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
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.
 

flbenini

Senior Member
Apr 13, 2014
92
26
Why would you bother doing OTA update.
- Download firmware, select it
- Process it,
- Patch boot
- Flash to Inactive slot, keep data: Flash

It takes about 4 minutes or less

Done

Quick question: if I apply step 9 and disable Magisk modules, do I need to re-enable after flash? Or is it automatic and when the phone reboots the modules will be re-enabled?
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,649
1,824
Samsung Galaxy Tab A series
Quick question: if I apply step 9 and disable Magisk modules, do I need to re-enable after flash? Or is it automatic and when the phone reboots the modules will be re-enabled?
Not automatic -- whole point is they are disabled until you decide to risk trying one. Incompatible module can make it impossible to boot. Then it's a struggle to disable. This way, when you can't boot, you know whether a module is responsible.

Even safer, but more trouble, is deleting /data/adb/ to avoid problems if Magisk database becomes incompatible. If do that, then have to reinstall modules and reconfigure them.
 

dr.wtf

Senior Member
Dec 25, 2011
994
208
v4.5.0 does not work on Linux Mint 21

Code:
./PixelFlasher-Kali
Traceback (most recent call last):
  File "PixelFlasher.py", line 3, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "Main.py", line 17, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "wx/__init__.py", line 17, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "wx/core.py", line 12, in <module>
ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /tmp/_MEIBcSlf6/libstdc++.so.6)
[17855] Failed to execute script 'PixelFlasher' due to unhandled exception!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
v4.5.0 does not work on Linux Mint 21

Code:
./PixelFlasher-Kali
Traceback (most recent call last):
  File "PixelFlasher.py", line 3, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "Main.py", line 17, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "wx/__init__.py", line 17, in <module>
  File "PyInstaller/loader/pyimod02_importers.py", line 499, in exec_module
  File "wx/core.py", line 12, in <module>
ImportError: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.36' not found (required by /tmp/_MEIBcSlf6/libstdc++.so.6)
[17855] Failed to execute script 'PixelFlasher' due to unhandled exception!
That means that your system has old version of glibc
Because the program was built with the latest libraries / modules which have a dependency on it.
See this.
If you install the library, it should work.
 

moisthat

Senior Member
Jun 25, 2016
52
14
PF looks perfect for me.. My goal is to have my pixel 7 regularly updated and rooted in as pain free way as possible.

Apologies if already covered, just need a few confirmations before I pull the trigger please.

1) bootloader unlocked required before starting
2) rooted not required. Can flash boot image with PF, and once flashed give Shell root permissions for future updates
3) using this method, I can keep my phone updated regularly within PF by getting latest image, patching with magisk, and dirty flashing.

Thanks, if the above is yes for all 3, I'll get started!
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
PF looks perfect for me.. My goal is to have my pixel 7 regularly updated and rooted in as pain free way as possible.

Apologies if already covered, just need a few confirmations before I pull the trigger please.

1) bootloader unlocked required before starting
2) rooted not required. Can flash boot image with PF, and once flashed give Shell root permissions for future updates
3) using this method, I can keep my phone updated regularly within PF by getting latest image, patching with magisk, and dirty flashing.

Thanks, if the above is yes for all 3, I'll get started!
Yep, exactly.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 6
    I create a new folder into the Platform tools and I put only the adb and the fast boot .
    Since that is the first time and I'm already rooted from January without updating till now I will use for 1st time this tool . Do i have to care for something else ?
    That's not how you do it, don't just get the adb and fastboot files, unpack the Android Platform Tools 33.0.3 (not 34.0.1) and when you point PF where it is, point where adb and fastboot are , the other files in there are not decoration, they need to be there.
    Then follow the basic usage guide in the main thread OP
    6
    I follow your instructions but no way to work .please see the support
    When you unzip the Android Platform Tools
    Make sure you select the folder that has the adb and fastboot in it, not the parent folder that says Platform Tools.

    Code:
    ERROR: The selected path \\Ds\ds\Downloads\platform-tools_r33.0.3-windows does not have adb and or fastboot
    6
    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.
    4
    Just want to add my thanks for making this excellent tool available. I've used it several times now with no issues. It really takes the stress and drama out of keeping my devices up-to-date while keeping root.

    Thank You
    4
    yes, and on github too. Wasn't sure if the table in the middle will apply just the boot or the whole image and found the "Flash Boot" button or root process undescribed. Also manual describes "Flash Pixel Phone" button as it flashing boot only in all the points, so i'm not sure if it does the OTA update.
    If you follow the number sequence in basic usage, that is the main usage, everything else is additional features / tools.
    You can learn about what they do by hovering to show tooltip.
    PF needs a wiki for all the added tools / features aside from the basic usage, and it's on my TODO list, but it's low on the list because it is expected that the advanced features are used by experienced users who intuitively know what they are about.

    Flash Boot just flashes the selected boot file in the middle screen, it does not flash full factory.
    For full factory flashing you want to use the big Flash button above the console.

    OTA flashing can be done by enabling the advanced settings and then using custom flash with SIDELOAD selected.
    But that is intentionally in advance settings because you're have to know what to do, the OTA image is not patched, and you have to flash a patched boot as a follow up step.
  • 118

    PF_promo-banner_v4.png

    DESCRIPTION

    As the name suggests this is an application to flash (update) Pixel™ phones (possibly all Google™ made phones/tablets, YMMV.)
    PixelFlasher at its core is a UI layer (with bells and whistles) on top of adb / fastboot commands, hence many of its features can be used on non Pixel devices as well. (YMMV).
    The executable is self contained and does not require Python™ to be installed on the system.

    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).

    Prerequisites​

    Installation​

    PixelFlasher doesn't have to be installed, just double-click it and it'll start.
    Check the releases section for downloads.

    Supported platforms​

    • Windows
    • MacOSX
    • Linux (see this if you're having issues with a Linux build.)

    Usage

    Basic Mode

    1. First thing to do is select Android™ Platform Tools, if Android™ Platform Tools is already in your PATH environment, the application will detect it and pre-populate it.
      Otherwise you'd have to select where it is installed.
      You can download the lastest Android™ Platform Tools by clicking the Image of link next to it.
      If you have multiple versions, you can select another version, although it is best to always use the most recent version (The selected version will be identified and displayed.)
      If you already have your phone connected to the PC, the application will detect all connected devices
      (in adb, fastboot, sideload, recovery modes) and populate the combo box (2).
      Otherwise connect your phone to your PC, and hit the Scan button and then select your device.
    2. Select your device from the list in the combo box. The following information about the connected device is displayed.
      • (1st field) Rooted devices will be identified with a checkmark âś“. Note: If you want PixelFlasher to detect root, or automatically use Magisk to patch boot.img, you need to grant root permissions to shell in Magisk.
        Image of shell root access
      • (1st field) Non-Rooted devices will be identified with a âś—.
      • (1st field) Devices in fastboot mode will be identified with a ? (in fastboot mode, root status cannot be determined).
      • (2nd field) (adb), (f.b), (sid) or (rec) to indicate connection mode adb / fastboot / sideload / recovery.
      • (3rd field) Device ID.
      • (4th field) Device hardware.
      • (5th field) Current running firmware (in fastboot mode current firmware cannot be determined).
    3. Next select the factory image, the application will recognize the phone model from the image name.
      You can download factory images by clicking the Image of link next to it.
    4. Process the factory image. PixelFlasher will extract boot.img file from the factory image and populate it in the list below (5).
    5. Select boot.img from the list, the selected boot.img can be patched (6), or flashed (10).
    6. Optional: Select this option if you want to patch the boot.img with Magisk. If Magisk is not already be installed on your phone, PixelFlasher will install it for you.
      Your phone does not need to be rooted to create a patched boot.img file.
      This would be the typical choice for monthly updates.
      This option will allow updating the phone without losing root (not even temporarily).
      Note: See note above for granting root permissions to shell.
      Whether the phone is already rooted or not, the whole process is without any manual step.
    7. If you want to flash (10) a patched boot.img select the newly added entry.
      The following details are listed.
      • Image of patched-boot Indicates that the selection is patched.
      • SHA1 is (shortened for display only) sha1 of boot.img
      • Source SHA1 (shortened for display only) SHA1 of source boot.img extracted from the image (This should be the same as SHA1 of an unpatched boot.img)
      • Package Fingerprint is just the filename portion of the image (without the extension).
      • Patched with Magisk indicates the version of Magisk used to patch the image (if applicable).
      • Patched on Device indicates the device model that performed the patching. You should always use patched images that match the model of the device that it will be flashed on.
      • Date is the either the date the boot.img was extracted, or the date it was patched.
      • Package Path indicates the file from which boot.img was extracted.
    8. Select the Flash Mode
      • Keep Data: In this mode -w flag is removed from the flash scripts so that data is not wiped. This is commonly known as dirty flashing.
      • WIPE all data: As the text suggests, this will wipe your data, use it with caution!
        If this mode is selected PixelFlasher will ask for confirmation during the flashing phase.
      • Dry Run: In this mode, the phone will reboot to bootloader, and then mimic the flash actions (i.e. reboot into bootloader) without actually flashing anything (it prints to the console the steps it would have performed if dry run was not chosen). This is handy for testing to check if the PixelFlasher properly is able to control fastboot commands.
    9. Optional: Open Magisk Modules Manager and disable (uncheck) modules known to cause issues during upgrades (the below list has never caused issues for me, so I keep them enabled YMMV).
    10. Flash Pixel Phone This is the final step, to actually flash the phone in the selected Flash Mode.
      Note: Unlike the previous versions of the PixelFlasher, all the options are dynamic, i.e. depending on what you select before clicking the Flash button, there is no more concept of prepared package. PixelFlasher will first present you the selected options and ask for your confirmation if you want to proceed with flashing.

    Expert Mode
    To enable the export mode use the File Menu | Advanced Configuration and select Enable Advanced Options Image of PixelFlasher GUI
    Image of PixelFlasher GUI

    In this mode the following additional options are exposed (green bounding boxes), below notes are more for enumeration than a guide, as they should be trivial and obvious to an expert.

    1. Option to Change the Active Slot (the inactive slot is automatically selected).
      Option to reboot to Recovery.
    2. Options to Lock / Unlock bootloader, Option to disable Magisk modules when bootlooping.
    3. Apply Custom ROM. This replaces the factory ROM image with the selected file.
      PixelFlasher extracts boot.img from the ROM image and displays below for selection or patching. Please make sure to read the documentation of the chosen ROM, as each custom ROM instructions could be different.
      To be clear, this is what PixelFlasher does internally when this mode is selected, please understand it, and don't use it if the selected ROM guide does not fit the bill. You've been warned!
      • Keeps stock bootloader and radio images.
      • Replaces the stock ROM image with the selected custom ROM image.
      • Flashes in the chosen Flash Mode just like a stock image, i.e. bootloader, custom ROM and radio images in the original order that they were in the stock firmware.
      • Patching boot.img can be performed if the option is selected. You can select any of the listed boot.img.
      • Flash Mode is similar to basic flash mode described above in step 7.
    4. Custom Flash. select this to switch from flashing a Factory Image to flashing a single file.
    5. Browse to select a a valid image file (.img or .zip). Or select a boot.img from the list above and click on the paste button to paste the selected boot.img into the file selection. Choose the dropdown to select image type.
      • boot (can be flashed to Live or boot) - Expected file type .img
      • bootloader - Expected file type .img
      • dtbo - Expected file type .img
      • product - Expected file type .img
      • radio - Expected file type .img
      • recovery - Expected file type .img
      • super_empty - Expected file type .img
      • system - Expected file type .img
      • system_ext - Expected file type .img
      • system_other - Expected file type .img
      • vbmeta - Expected file type .img
      • vbmeta_system - Expected file type .img
      • vbmeta_vendor - Expected file type .img
      • vendor - Expected file type .img
      • vendor_boot - Expected file type .img
      • vendor_dlkm (the device will be put into fastbootd mode during this operation) - Expected file type .img
      • image - Expected file type .zip
      • SIDELOAD - Expected file type .zip
        Select the appropriate flash options. Note: For Tensor devices (Pixel 6, Pixel 6a, Pixel 6 Pro, Pixel 7, Pixel 7 Pro) When Flash to both slots option is selected, Pixelflasher flashes each slot individually to overcome a Google bug that fails with the option --slot=all

    Credits

    • First and foremost Magisk by John Wu which made rooting Pixel™ phones possible, without it none of this would have mattered.
    • Big thanks to [ryder203], [t-ryder] for his valuable ideas, feedback and testing. Your contributions are very much appreciated.
    • [Homeboy76] and [v0latyle] at xda for their excellent guides [here and here] on Pixel™ series phones. This program could not have been possible without their easy to follow guides.
      I strongly encourage all beginners to follow those guides rather than use this program, it is important to understand the basic steps involved before diving into one click tools or advanced tasks.
    • Marcel Stör's nodemcu-pyflasher source code which jump started my introduction to wxPython and eventually this program.
    • JackMcKew for pyinstaller Github Actions.
    • Endless counts of xda members and their posts that tirelessly answer questions and share tools. Too many to enumerate.

    Disclaimer

    Code:
    *******************************************************************************
    PLEASE DO YOUR PART AND READ / SEARCH / RESEARCH BEFORE USING THIS PROGRAM
    AND/OR ATTEMPTING ANY MODIFICATIONS ON YOUR DEVICE.
    THIS PROGRAM ASSUMES THAT YOU ALREADY KNOW HOW TO AND HAVE ALREADY UNLOCKED
    YOUR BOOTLOADER, ALREADY ROOTED YOUR DEVICE, AND KNOW HOW TO USE ANDROID SDK
    PLATFORM-TOOLS, ETC.
    THIS TOOL IS SIMPLY MY QUICK WAY OF UPDATING THE FIRMWARE WHILE ROOTED WITH
    MAGISK, WITHOUT LOSING DATA / REQUIRING A WIPE.
    MODIFYING YOUR DEVICE COMES WITH INHERENT RISKS, AND IT'S NOT MY RESPONSIBILITY
    IF YOU LOSE YOUR DATA OR BRICK YOUR DEVICE. THE TOOL I SHARE HAVE WORKED FOR ME,
    BUT THAT DOESN'T MEAN THAT YOU MAY NOT RUN INTO PROBLEMS. **BACKUP YOUR DATA.**
    *******************************************************************************

    No Donation
    I've been asked quite few times about donation, (here, here ... just to list a few).
    I'll put it here so that my stance is clear.
    This program will remain totally free, ad free, even donation free, it's my way to give a little back to the community that has given me years of support and joy.

    You can contribute by helping the next newcomer to learn the ropes and navigate through the maze of information.
    8
    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.
    7
    Forgive me if I've asked this before....does ADB shell need root access in order for Pixel Flasher to patch the boot image via Magisk?

    In other words, will the automatic patching work on unrooted devices?
    Here's a complete flow diagram of the patching process, hope it makes it clearer.

    1662558670612.png


    Drive UI and generate patched boot.img box is a new feature that will be available in 3.8.0 (hopefully to be released today), it uses UIAutomator to drive the UI and not require user interaction, the user can still decide to do it manually.

    Without su permissions on adb shell, PixelFlasher will report that the device is not rooted and will follow the flow of un-rooted.
    7
    New release:
    July 18, 2022 v3.4.0 release
    • Improvements to the boot extraction / categorization.
    • Live boot option directly from the selected boot.img UI, even though it was possible to live boot previously through the advanced menu, it is now super easy to select a boot.img (patched or otherwise) and Live boot to that image with a click of a button.
    • Added warning message in the splash screen and the help about menu, to inform users not to fall for opportunists who are claiming to be the developer of PixelFlasher with a donate button next to the download link. Reminder to all, this program will always be free, ad free, donation free; you should not be solicited for any form of payment.
    7
    @badabing2003 , I really like your work, well done, I couldn't find a donation link, can you please provide me with that. Thanks and keep up the good work.
    Thanks for your consideration, appreciated.
    Like I mentioned to other such queries, no donation is necessary, this is a payback to the community that has given me years of support and joy.
    If you want to do something good, help others who're just starting or struggling navigating through the maze of information.