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

Search This thread
A bit off topic but I wanted to put this out there and see if anyone else had the same thing happen... I updated an app in the playstore tonight called "Android System Intelligence" by Google and it caused me to lose root. I just reflashed the January release with Pixel Flasher and everything went back to normal. Not sure why it happened, but I just wanted to let you know to keep an eye out for the update. Sorry for posting this here but thought you should know about it.
 
  • Like
Reactions: J.Michael

krakout

Senior Member
A bit off topic but I wanted to put this out there and see if anyone else had the same thing happen... I updated an app in the playstore tonight called "Android System Intelligence" by Google and it caused me to lose root. I just reflashed the January release with Pixel Flasher and everything went back to normal. Not sure why it happened, but I just wanted to let you know to keep an eye out for the update. Sorry for posting this here but thought you should know about it.
Weird, I had that update too and I was fine...
 
  • Like
Reactions: J.Michael
Weird, I had that update too and I was fine...
I've never had an issue with this app before but when I updated it this time I lost root. Couldn't have even been anything else, I haven't updated anything since yesterday and nothing that could have the ability to remove root access has been done in a while. Very strange, I can't figure it out.
 

Thebear j koss

Senior Member
i had a question about the issue im having with the flasher. i have a google pixel 6a IN2015 running android 13 and whenever i add the factory image to it then add custom rom to flash and so far every Rom error's saying its missing the boot file, but it flashes flawlessly using fastboot. anyone know why im not about to flash custom with the flasher
Probably need to flash to both slots.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
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.
 
Last edited:

V0latyle

Forum Moderator
Staff member
If you have a Pixel 5a support thread, I missed it

After flashing my Pixel 5 and having the aforementioned hang on reboot, used to update my wife's 5a. Detected device via ADB, all went well until commanded reboot to bootloader. ADB ceased to work, could not detect device even via command line, even after killing PF and using command line to kill then start server. PC reboot got ADB working again, and was able to subsequently continue flashing with PF.

PF did not hang this time, got Completed message when device rebooted to bootloader and subsequently live booted the patched image

Why are there two Verbose options?
 
  • Like
Reactions: J.Michael

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
If you have a Pixel 5a support thread, I missed it
no,
I wish the forum supported linked threads, basically a single thread would show up in the relevant forums by just creating a symlink, without needing to have separate threads in each.
PF issues / questions / releases are all common,
Often I have to answer the same question in different forum, because the user posts it in their phone version's forum, if it was a single thread, the answers would be seen by all.
The other advantage is that I wouldn't need to create full threads in 5a, 4, 4a, 4xl ... you get the drift.
I just haven't created those, thinking that the usage is minimal.


After flashing my Pixel 5 and having the aforementioned hang on reboot, used to update my wife's 5a. Detected device via ADB, all went well until commanded reboot to bootloader. ADB ceased to work, could not detect device even via command line, even after killing PF and using command line to kill then start server. PC reboot got ADB working again, and was able to subsequently continue flashing with PF.

PF did not hang this time, got Completed message when device rebooted to bootloader and subsequently live booted the patched image
For this support.zip would help, I'm curious to see what is going on.


Why are there two Verbose options?
One is PF console log (the one on the left), offering a bit more verbose messages (as if it is not verbose enough)
The other with flash options is a fastboot flag.
 

V0latyle

Forum Moderator
Staff member
no,
I wish the forum supported linked threads, basically a single thread would show up in the relevant forums by just creating a symlink, without needing to have separate threads in each.
We do have a way to do this....we'd basically have to delete your support threads, then move this thread to one of the device sections, then move to each new section with a redirect, so there would basically be a "chain" of redirects that would end up at this thread here. Pain in the ass but that's how we did this. There are redirects in the Pixel 2 through 4a 5g sections that all point to one thread; there's unfortunately no way to create standalone symlinks, at least not with our Xenforo configuration
PF issues / questions / releases are all common,
Often I have to answer the same question in different forum, because the user posts it in their phone version's forum, if it was a single thread, the answers would be seen by all.
The other advantage is that I wouldn't need to create full threads in 5a, 4, 4a, 4xl ... you get the drift.
I just haven't created those, thinking that the usage is minimal.
Yeah, I get it
For this support.zip would help, I'm curious to see what is going on.
Read up boiiii
One is PF console log (the one on the left), offering a bit more verbose messages (as if it is not verbose enough)
The other with flash options is a fastboot flag.
What does it do? I've never used --verbose
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
We do have a way to do this....we'd basically have to delete your support threads, then move this thread to one of the device sections, then move to each new section with a redirect, so there would basically be a "chain" of redirects that would end up at this thread here. Pain in the ass but that's how we did this. There are redirects in the Pixel 2 through 4a 5g sections that all point to one thread; there's unfortunately no way to create standalone symlinks, at least not with our Xenforo configuration
Sweet, that is very cool, that's exactly what I need.
Assuming that it is not too much trouble on Moderators, only if knew one :LOL:
Can threads be merged into one thread so that past notes are not lost?
More importantly, I love that thread you started, thanks for pointing out, I would have never noticed.
If that approach works (I need to read up on it) I can easily add support for it in PF to simplify the whole process.

What does it do? I've never used --verbose
You get messages like these

Code:
fastboot: verbose: Do flash radio_a radio-oriole-g5123b-107485-221101-b-9242015.img
fastboot: verbose: target reported max-download-size of 261095424 bytes

Maybe I should merge the two, seeing that it's not too much that is being added.
 

V0latyle

Forum Moderator
Staff member
Sweet, that is very cool, that's exactly what I need.
Assuming that it is not too much trouble on Moderators, only if knew one :LOL:
We have specific areas of responsibility, unfortunately mine does not include Google. @roirraW "edor" ehT is assigned to this section, and was the one who discovered the ability to do this.
Can threads be merged into one thread so that past notes are not lost?
Yep
More importantly, I love that thread you started, thanks for pointing out, I would have never noticed.
If that approach works (I need to read up on it) I can easily add support for it in PF to simplify the whole process.
Unfortunately no one has volunteered yet
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
We have specific areas of responsibility, unfortunately mine does not include Google. @roirraW "edor" ehT is, and was the one tho discovered the ability to do this.

Yep

Unfortunately no one has volunteered yet
Thanks, I'll reach out to @roirraW "edor" ehT that would make it so much cleaner and better for everyone.

Unfortunately no one has volunteered yet
I might,
I have a PIxel XL, and the only reason I don't flash other things on it is because I have unlimited full quality photos / videos upload, so I keep it for that.
But I heard that there are Magisk modules that give you that ability, so if that works, I might use the XL for experimentation.
 

roirraW "edor" ehT

Forum Moderator
Staff member
Thanks, I'll reach out to @roirraW "edor" ehT that would make it so much cleaner and better for everyone.


I might,
I have a PIxel XL, and the only reason I don't flash other things on it is because I have unlimited full quality photos / videos upload, so I keep it for that.
But I heard that there are Magisk modules that give you that ability, so if that works, I might use the XL for experimentation.
@V0latyle wasn't saying that one of my areas of responsibility are the Google sections (they're not) - he was just saying that I introduced him to the idea of the "hardlinked" threads that I had noticed.

You can find the list of moderators and the sections they cover here at all times:

The Google sections are considered "Other" currently.
 
  • Like
Reactions: Thebear j koss

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
@V0latyle wasn't saying that one of my areas of responsibility are the Google sections (they're not) - he was just saying that I introduced him to the idea of the "hardlinked" threads that I had noticed.

You can find the list of moderators and the sections they cover here at all times:

The Google sections are considered "Other" currently.
Thanks for the clarification.
So any one of the moderators listed under "other" should be able to help me out?
If so, I'll reach out to one.

Many thanks.
 

V0latyle

Forum Moderator
Staff member
@V0latyle wasn't saying that one of my areas of responsibility are the Google sections (they're not)
My mistake, I thought they were.
Thanks for the clarification.
So any one of the moderators listed under "other" should be able to help me out?
If so, I'll reach out to one.

Many thanks.
Yep. You could find it easier to use the Report button on one of your threads which will pop up for all the mods in this area, and just explain what you want to do and to contact you via PM for more details
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,637
1,799
Samsung Galaxy Tab A series
...
Often I have to answer the same question in different forum, because the user posts it in their phone version's forum, if it was a single thread, the answers would be seen by all.
...
You could just answer PixelFlasher questions in this thread, regardless of where the question was asked. Use the "Quote" button where you find the question, come here and "Insert quotes" in the "Reply" box.

We can form a committee to decide whether you should put any response in the originating thread to alert other readers that there is a response in this thread.
 

torlik

Member
Oct 11, 2016
9
4
Hi there. I've trying to update pixel 7 with the latest firmware (root device with magish). I don't know why but my computer reboot during process..... At the moment of fastboot command. Now Im getting a bootloop.



Any idea how to fix that? Without losing data?
Thank you!
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,823
2,387
Hi there. I've trying to update pixel 7 with the latest firmware (root device with magish). I don't know why but my computer reboot during process..... At the moment of fastboot command. Now Im getting a bootloop.

Please create a support. zip file from the help menu an I'll take a look.

Did I read that right?
Your computer

Any idea how to fix that? Without losing data?
Thank you!
 
Last edited:

Top Liked Posts

  • 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
  • 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.
    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
    5
    @xzenx1234x Please stop posting about this here, I told you already that this is off topic, you started a thread about it, why are you still posting it here?
    5
    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
    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
  • 116

    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.