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

Search This thread
By:
Advanced…
wilberfan

wilberfan

Senior Member
Jan 4, 2011
611
121
So Cal
nVidia Shield Android TV (2017)
OnePlus 7T
Oooh...seconds too late! Just tried it (successfully) on my Windows machine. Is it safe to repeat the procedure on the same phone (via Mac)?

[edit] Let me try a Dry Run.

Dry run on the Mac seems to have executed and rebooted. PixelFlasher app is 'frozen' on the Mac after the phone rebooted (Beachball-of-Death) so I can't copy/paste anything from the console.
 
Last edited:
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
wilberfan said:
Oooh...seconds too late! Just tried it (successfully) on my Windows machine. Is it safe to repeat the procedure on the same phone (via Mac)?

[edit] Let me try a Dry Run.

Dry run on the Mac seems to have executed and rebooted. PixelFlasher app is 'frozen' on the Mac after the phone rebooted (Beachball-of-Death) so I can't copy/paste anything from the console.
Click to expand...
Click to collapse
Interesting,
You can kill it, probably killing fastboot should be enough, if not kill PixelFlasher, and start it again, then go straight to help and generate sanitized support.zip file.
By any chance did you unplug the phone while it was doing the dry run? it does could of reboots and then boots to system.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
@wilberfan
Ok found the saving issue,
This one should be able to save the file.
It was MacOS specific, just like the previous error.
 

Attachments

  • PixelFlasher.zip
    19.4 MB · Views: 27
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
wilberfan said:
Here's the support.zip.
Click to expand...
Click to collapse
Thank you for the support file,
I really don't see any errors or anything for that matter that would hint an issue.
So each time you attempt a dry run, you get PixelFlasher freezing? Or was it a one time thing?
The version 3.3.3 we know it had an issue with flashing on Mac, but I believe you said you got it frozen with 3.3.4?
Happens all the time?

Thanks
 
wilberfan

wilberfan

Senior Member
Jan 4, 2011
611
121
So Cal
nVidia Shield Android TV (2017)
OnePlus 7T
The app freeze is consistent at the end of the dry run--after the procedure finishes and the phone reboots into the system. If I check Activity Monitor on the Mac, the fastboot process is running at 76.x% and the app is unresponsive. And, yes, it's happened every time with v3.3.4.
 
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
wilberfan said:
The app freeze is consistent at the end of the dry run--after the procedure finishes and the phone reboots into the system. If I check Activity Monitor on the Mac, the fastboot process is running at 76.x% and the app is unresponsive. And, yes, it's happened every time with v3.3.4.
Click to expand...
Click to collapse
Thanks for the confirmation and sorry for bothering you, I don't have a MAC, so I'm doing all this in a container, but I cannot connect a physical device, I can do adb over tcp but not fastboot over tcp, so can't reproduce.

Can you try this attached version and see if it still does the same thing, I made a change and am hoping that it will fix the issue.

Thanks
 

Attachments

  • PixelFlasher.zip
    19.4 MB · Views: 18
wilberfan

wilberfan

Senior Member
Jan 4, 2011
611
121
So Cal
nVidia Shield Android TV (2017)
OnePlus 7T
badabing2003 said:
Thanks for the confirmation and sorry for bothering you, I don't have a MAC, so I'm doing all this in a container, but I cannot connect a physical device, I can do adb over tcp but not fastboot over tcp, so can't reproduce.

Can you try this attached version and see if it still does the same thing, I made a change and am hoping that it will fix the issue.

Thanks
Click to expand...
Click to collapse
Success! (?) No app hang or runaway fastboot process this time. Didn't see anything frightening in the app console...

Honestly not a bother; happy to help! As an 'intermediate noob', I'm really grateful to have a tool at my disposal to help with system upgrades (I've had to completely restore my phone twice in the last two weeks after botched attempts and resulting bootloops--which literally takes hours each time.) So, thank you.
 

Attachments

  • support.zip
    30.7 KB · Views: 12
  • Like
Reactions: Thebear j koss and stoph8n24
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
wilberfan said:
Success! (?) No app hang or runaway fastboot process this time. Didn't see anything frightening in the app console...

Honestly not a bother; happy to help! As an 'intermediate noob', I'm really grateful to have a tool at my disposal to help with system upgrades (I've had to completely restore my phone twice in the last two weeks after botched attempts and resulting bootloops--which literally takes hours each time.) So, thank you.
Click to expand...
Click to collapse
Thank you very much.
You have helped improve the program, specially on MacOS.
Very much appreciated.
I will release an official 3.3.4 thanks to you.
 
  • Like
Reactions: Slim2none4u, Thebear j koss and stoph8n24
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
wilberfan said:
Agreed. This thing is wonderful. Just used it to upgrade to A13b3.2 from b3.1.

Is there some place we could toss a couple of Gratitude Bucks your way...?
Click to expand...
Click to collapse
Thanks for your consideration.
No donation is necessary.
To avoid repeating myself, I have added a donation section in the OP to explain my reasoning.
 
  • Like
Reactions: elong7681, Lughnasadh, Thebear j koss and 1 other person
Slim2none4u

Slim2none4u

Senior Member
Oct 28, 2011
882
546
49
Livermore Falls
www.youtube.com
Verizon Droid Incredible 2
Sprint HTC EVO 4G LTE
wilberfan said:
Agreed. This thing is wonderful. Just used it to upgrade to A13b3.2 from b3.1.

Is there some place we could toss a couple of Gratitude Bucks your way...?
Click to expand...
Click to collapse
badabing2003 said:
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.
Click to expand...
Click to collapse
 
  • Like
  • Love
Reactions: HippoMan, Thebear j koss and wilberfan
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
hithekillswitch said:
This looks like an amazing tool. I am trying to install on Mac and I keep getting ""PixelFlasher" can't be opened because Apple cannot check it for malicious software. This software needs to be updated. Contact the developer for more information." Monterey 12.4 if that matters.
Click to expand...
Click to collapse
Unfortunately I don't have access to Macs and have to rely on Mac Users / Owners to troubleshoot this.
I build it in Catalina docker container, and it is not signed, perhaps that is why you're getting the error.
And obviously is works in the docker container (I test that before each release)
I know that real Mac users reported success with it, you should see it in this or one of the support threads.

Do you have Intel or M1 CPU? I doubt that it would make a difference.
Are you able to open the dmg and get the drag to Application UI?
1656603382358.png


If Yes, Can you double click on PixelFlasher instead of dragging to Application?
If dmg does not open, maybe I can give you the App and you try that.


Or maybe you can try some of the suggestions mentioned in here
www.lifewire.com

How to Fix 'Cannot Be Opened Because the Developer Cannot be Verified' Error on Mac

Troubleshoot and fix this error on Mac by locating an updated version of the app or bypassing the app security settings; plus, why you see this error.
www.lifewire.com www.lifewire.com
 
V0latyle

V0latyle

Forum Moderator
Staff member
Feb 20, 2011
5,864
1
9,194
The Heartland of America
Google Pixel 5
Google Pixel 5a
So, I've finally decided to try this. Pretty slick. Just a couple suggestions:
  • Add the ability to select a previously patched boot image, then live boot it. Maybe a little redundant since your tool automatically patches the new boot image.
  • Provide some sort of log readout so the user can see exactly what is happening, as well as the option to save the log file for troubleshooting and review. The program doesn't really tell you what it's doing while it's flashing the factory image, and while I noticed your warning to be patient, it would still be nice to be able to see the command readout.
 
  • Like
Reactions: HippoMan
badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,860
2,445
V0latyle said:
So, I've finally decided to try this. Pretty slick. Just a couple suggestions:
  • Add the ability to select a previously patched boot image, then live boot it. Maybe a little redundant since your tool automatically patches the new boot image.
Click to expand...
Click to collapse
Happy to hear that you gave a shot.
If I understand you correctly, I believe what you want is already there, see if this does it.
First turn on advanced mode.
You can do that through the File Menu | Advanced Configuration and then select Enable Advanced Options.
The UI should change and you should see additional options.
1657147687740.png
1- Once you create the patched boot.img, select it (highlight)
2- Choose Custom Flash
3- Select boot
4- Hit the Paste button, and it will paste the currently selected boot.img path
5- Select Live boot, or Flash, in your case I suppose you want Live Boot
Ignore the Flash both slots selection from my image, that is not necessary, I just had it on when taking the screenshot and didn't feel like taking another one
6- Hit the flash Pixel Phone and you should get what you want.

  • Provide some sort of log readout so the user can see exactly what is happening, as well as the option to save the log file for troubleshooting and review. The program doesn't really tell you what it's doing while it's flashing the factory image, and while I noticed your warning to be patient, it would still be nice to be
Click to expand...
Click to collapse

You don't see anything scrolling in the Console window (#7)? as it is flashing or patching, you should see the output reflected in the console, if you don't it could be a bug that I need to investigate.
Keep in mind that the console only refreshes if the line is complete, ie a newline is sent, there are some parts in the flash output (while extracting data) the output does not have a newline until it completes the extraction, not much I can do there, but that is only one line that should make you wait till it completes, each line should print and scroll.

Also you can turn on the verbose button for the console to get even more verbose logging, I think the app is very verbose to start with, and that options makes it even more verbose, I usually keep it on to see exactly what is happening.

Lastly, if you want to see current or previous logs.
Help menu | Open configuration Folder
Navigate to logs folder and you'd see all the logs.

You can also choose Create Sanitized support.zip from the Help menu.
This will zip up the logs and the configuration details, and redact (sanitize) all personal data (device id, user name ...) It helps with troubleshooting and making the program better.

1657148626917.png
 

Attachments

  • 1657148607302.png
    1657148607302.png
    24.7 KB · Views: 18
  • Like
Reactions: elong7681 and Slim2none4u
You must log in or register to reply here.

Similar threads

T
[ROM] [BETA] [ANDROID 7] PrimeOS: Android for Laptops/PCs - V0.6.1
Replies
5K
Views
2M
kamazok
kamazok
lokeshsaini94
[GUIDE] [how to] CREATE OWN ROM [FOR ANY ANDROID DEVICE] [FOR N00B] [EASIEST METHODS]
Replies
1K
Views
1M
alisadty
alisadty
D
Amazing Temp Root for MediaTek ARMv8 [2020-08-24]
Replies
2K
Views
777K
HoanG8
HoanG8
S
Intel Android Devices Root / Temp Recovery Session
Replies
1K
Views
940K
travellerny
travellerny
C
[rom] Unofficial CyanogenMod 10 for many AllWinner A10 tablets
Replies
615
Views
788K
D
doralice

Top Liked Posts

24 Hours 30 Days All time
  • There are no posts matching your filters.
  • 6
    badabing2003
    badabing2003
    zaras27 said:
    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 ?
    Click to expand...
    Click to collapse
    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
    View
    6
    badabing2003
    badabing2003
    zaras27 said:
    I follow your instructions but no way to work .please see the support
    Click to expand...
    Click to collapse
    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
    View
    6
    badabing2003
    badabing2003
    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.
    View
    4
    H
    HypromanGT
    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
    View
    4
    badabing2003
    badabing2003
    doggydog2 said:
    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.
    Click to expand...
    Click to collapse
    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.
    View
  • 118
    badabing2003
    badabing2003

    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.
    View
    8
    badabing2003
    badabing2003
    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.
    View
    7
    badabing2003
    badabing2003
    V0latyle said:
    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?
    Click to expand...
    Click to collapse
    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.
    View
    7
    badabing2003
    badabing2003
    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.
    View
    7
    badabing2003
    badabing2003
    oscarmaldonado said:
    @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.
    Click to expand...
    Click to collapse
    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.
    View

New posts