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

Search This thread

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
But cannot you copy the script to /data/cache or so and give it chmod 755 there
/data/cache is not accessible without root.
Do you know any accessible directory where I can change the permissions.
I found out that I can rename the lib*.so and use those as the binaries.
So we have all the file we need, we just need to execute them on the phone.

Update:
Found one
Code:
/data/local/tmp

Update2:
It worked
We can patch boot.img on unrooted devices just like we can on rooted ones using boot_patch all without user interaction, and as a bonus, if there is a new Magisk, we can use that to do the job instead of the older installed one, just in case of that rare corner case.
Needless to say, downloading of latest Magisk is done within PF, user just selects the flavor.
 
Last edited:

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
New Release:
Oct 03, 2022 v4.1.0 release

  • Patching is now fully automatic with or without root.
    PixelFlasher uses installed Magisk Manager binaries to create a patch (root binaries are only used if Magisk Manager is not available / accessible)
    UIAutomator no longer necessary, neither asking the user to manually patch and click ok when done.
  • Added an option to set a hidden Magisk package name so that PixelFlasher can find the Magisk and use it, the user still has a choice to use root binaries.
  • Speed improvements for device property reading.
  • Speed improvements for Magisk modules reading.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
  • NOTICE:
    I'm marking version 4.1.0 release as pre-release because I just found out that unzip is not normally available on the phone, which this new patching mechanism uses.
    On my test phones they were available.
    Unless you have unzip on your phone, you should avoid using this version.
    Sorry about this oversight.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
I don't know if this has been suggested before...Option to save the patched boot image somewhere for future use or troubleshooting?
It's already in PF (references kept in db)
It actually saves both , the original boot and the patched one.
Unless you delete them manually or through the App, they will be on your system
And there are many ways you can reach it.

1- if you browse the previous firmware, it will show you in the list.

2- if you click on Show all boot.img, you will see all your boot file, patched or otherwise
1664970146460.png


3- The easiest way to get a full path to the file is:
Select the boot enable choose Custom flash, and click on paste button,
1664970289504.png

You's see it pasted in the textbox and also printed in the console.

4- Lastly Help Menu | Open Configuration Folder, browse boot_images4 directory (boot_images is for PF versions older than version 4)
each sub-directory is a SHA1 of the boot file, and it either contains boot.img file, or magisk_patched_<SHA1 of source> file.

I can make it easier if you want, by printing the full path in console each time you select a boot in PF.

Update:
@V0latyle
I had totally forgotten that if you enable verbose console logging in PF,
Then PF will show in the console the full path of the file,
So your don't have to go through the above steps to figure it out.
In the next version, it will output the path even if verbose console logging is not enabled.
1665332100620.png
 
Last edited:

V0latyle

Forum Moderator
Staff member
It's already in PF (references kept in db)
It actually saves both , the original boot and the patched one.
Unless you delete them manually or through the App, they will be on your system
And there are many ways you can reach it.

1- if you browse the previous firmware, it will show you in the list.

2- if you click on Show all boot.img, you will see all your boot file, patched or otherwise
View attachment 5727523

3- The easiest way to get a full path to the file is:
Select the boot enable choose Custom flash, and click on paste button,
View attachment 5727525
You's see it pasted in the textbox and also printed in the console.

4- Lastly Help Menu | Open Configuration Folder, browse boot_images4 directory (boot_images is for PF versions older than version 4)
each sub-directory is a SHA1 of the boot file, and it either contains boot.img file, or magisk_patched_<SHA1 of source> file.

I can make it easier if you want, by printing the full path in console each time you select a boot in PF.
Yeah, I figured out that everything is in %appdata%/Roaming/PixelFlasher
 

dethknite

Senior Member
May 5, 2009
148
52
Unfortunately the latest updates break functionality of non-standard magisk releases such as alpha. Prior it would upload the boot.img and allow manual patching, then press ok to continue. Now it only allows for automated install of standard magisk if not detected. (I view the prior functionality as a helpful feature to some). Would be nice to have this option still as well.. such as patch if available, ask to install or ask to manually patch and continue.

(* NVM, I found in the settings an option to specify magisk package name. Awesome)
 
Last edited:
  • Like
Reactions: Slim2none4u

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
Unfortunately the latest updates break functionality of non-standard magisk releases such as alpha. Prior it would upload the boot.img and allow manual patching, then press ok to continue. Now it only allows for automated install of standard magisk if not detected. (I view the prior functionality as a helpful feature to some). Would be nice to have this option still as well.. such as patch if available, ask to install or ask to manually patch and continue.
Yes I will add that back for edge cases.
But the issue you're probably experiencing is a silly bug in detection of Magisk Manager version.
Because it does not get the version properly it assumes that it is not installed hence you situation.

I have a fix for it that should be out later today.
In fact once that is out, you don't even need to do manual patching, as long as the Installed Magisk Manager is not just a stub, it will extract the binaries from it's apk and use them to create the patch.
That is how it is supposed to be working if Magisk Manager is detected, regardless of the version.
 

dethknite

Senior Member
May 5, 2009
148
52
Yes I will add that back for edge cases.
But the issue you're probably experiencing is a silly bug in detection of Magisk Manager version.
Because it does not get the version properly it assumes that it is not installed hence you situation.

I have a fix for it that should be out later today.
In fact once that is out, you don't even need to do manual patching, as long as the Installed Magisk Manager is not just a stub, it will extract the binaries from it's apk and use them to create the patch.
That is how it is supposed to be working if Magisk Manager is detected, regardless of the version.
Yep.. you are correct. Even after switching to magisk canary it didn't find it. Glad to hear you already have a fix in the works. Thanks for the awesome automation. Saves at 10 - 15 minutes of tedious work.
 
  • Like
Reactions: badabing2003

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
1st. Nice tool. Thanks for your effort.
So noob question. Is it recommended to flash both slots when applying for a monthly upgrade?
Or just one?
If your phone is a Tensor based phone Pixel 6, 6a, 6 Pro
And you're upgrading from Android 12 to Android 13, I strongly suggest that you Flash to both slots, that's because of Anti Rollback Blocking (ARB)

1665148892987.png


If the monthly upgrade does not involve Android OS version upgrade, then my recommendation is to "Flash to
Inactive Slot
" which would behave similar to how OTA manages the upgrades.
Basically it applies the upgrade on the Inactive slot, if everything goes fine, the Inactive Slot becomes the active slot, and the previously active one becomes inactive.
If anything goes wrong, the system swaps the slots and boots back to previously working system.
Not only this approach provides better protection, your alternate slot is only one version behind if you do this every month.
 
  • Like
Reactions: tutuco

tutuco

Senior Member
Apr 16, 2007
65
6
SAO PAULO
Google Pixel 6 Pro
If your phone is a Tensor based phone Pixel 6, 6a, 6 Pro
And you're upgrading from Android 12 to Android 13, I strongly suggest that you Flash to both slots, that's because of Anti Rollback Blocking (ARB)

View attachment 5729383

If the monthly upgrade does not involve Android OS version upgrade, then my recommendation is to "Flash to
Inactive Slot
" which would behave similar to how OTA manages the upgrades.
Basically it applies the upgrade on the Inactive slot, if everything goes fine, the Inactive Slot becomes the active slot, and the previously active one becomes inactive.
If anything goes wrong, the system swaps the slots and boots back to previously working system.
Not only this approach provides better protection, your alternate slot is only one version behind if you do this every month.
Thanks, everything worked like a charm. Super easy.
 

J.Michael

Recognized Contributor
Jan 20, 2018
1,418
1,428
Samsung Galaxy Tab A series
If your phone is a Tensor based phone Pixel 6, 6a, 6 Pro
And you're upgrading from Android 12 to Android 13, I strongly suggest that you Flash to both slots, that's because of Anti Rollback Blocking (ARB)

View attachment 5729383

If the monthly upgrade does not involve Android OS version upgrade, then my recommendation is to "Flash to
Inactive Slot
" which would behave similar to how OTA manages the upgrades.
Basically it applies the upgrade on the Inactive slot, if everything goes fine, the Inactive Slot becomes the active slot, and the previously active one becomes inactive.
If anything goes wrong, the system swaps the slots and boots back to previously working system.
Not only this approach provides better protection, your alternate slot is only one version behind if you do this every month.
Are there two bootloader partitions?

Since the point of two slots seemed to be to provide a fallback in the event of a problem, I assumed the rollback prevention applied to each slot separately.
 

badabing2003

Recognized Contributor
Sep 17, 2012
1,454
1,697
Are there two bootloader partitions?
Yes there are two bootloader partitions.

Since the point of two slots seemed to be to provide a fallback in the event of a problem, I assumed the rollback prevention applied to each slot separately.
Your point makes perfect sense, but it looks like in this case Google deems protecting you from bootloader exploit is more critical than providing a fallback protection.
 
  • Like
Reactions: J.Michael

Top Liked Posts

  • There are no posts matching your filters.
  • 7
    New Release:
    Nov 09, 2022 v4.4.0 release
    • New feature: Font and Font size should be configurable by the user #33
    • New feature: Added WiFi-ADB connect / disconnect button. Left click to connect, Right click to disconnect.
      Handy to access a device remotely.
      Note: This only works in adb mode, so no fastboot or flashing features work for remote devices, but for patching / installing apks, managing Magisk modules it works well (basically anything that is done in adb).
      I personally use this to test patching on remote devices, and also use it to access / install apps to my watch.
    • Ground work for future features: Get installed Package list, and list which are disabled, enable / disable / uninstall apps. (Will be available in future release).
    • Move Flash Option Flash to inactive slot to Basic mode from Advanced mode..
    • Minor UI Improvements
    • If Magisk does not create a backup attempt to trigger Magisk to create one.
    • Update readme to include Pixel 7 / 7P specific info.
    5
    New to using the pixelflasher. I did use it to root and was so easy. How do I do the ota update after im rooted using the tool though?
    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
    4
    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.
    4
    No sorry I mean a factory image update. I just got an alert on my phone there is an ota update. This I can't do on my rooted phone so I used your PixelFlasher.
    OK All good than.
    By the way you can turn off those in Developer options so that it does not bother you on the phone.
    First Monday of every month there should be scheduled releases of the firmware.
    3
    Active/inactive slot refers to the partitions, yeah? Where can I read up or what to search for to understand more what they are, how they work etc?
    Not partitions but two sets of partitions

    In both slots you have /system, /boot, etc

    Google will be your friend. Search for A/B devices, read eg
  • 82

    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.
      • SHA1 checksum.
      • Origin (file it was extracted from).
      • Whether it is patched or not, and if it is patched.
        • What version of Magisk was used to patch it.
        • On what device it was patched.
        • Date of patching.
        • The SHA1 of the source boot.img file.
      • Option to Live boot from a choice of boot.img.
    • Choose to keep data or wipe data while flashing.
    • Ability to flash even if multiple devices are connected to the computer.
    • Display information about the phone.
      • ID
      • Hardware model.
      • Current installed firmware (build).
      • If it is rooted with Magisk.
      • Magisk version (Magisk Tools).
      • Magisk Manager version (the app).
      • List installed Magisk modules.
      • Connection mode (Adb | Fastboot | Sideload | Recovery).
      • Bootloader version.
      • Android OS API version.
      • Convenient quick links to download Android platform tools or device firmware.
    • Magisk Manager installation UI, screenshot. Supported versions:
      • stable
      • beta
      • canary
      • debug
    • Magisk modules management, enable / disable modules selectively, this comes in handy to disable suspect modules before an upgrade screenshot:
      • Name
      • Version
      • Description
      • Enabled / Disabled.
    • Display Android Platform Tools (SDK) version and warn / block if the version is old.
    • Install APK file from the computer onto the device.
    • Advanced features are hidden to keep the interface simple and easy to follow.
    • A lot of checks and validations for smooth operation.
    • Automatic check for program updates.
    Expert mode: (should only be turned on by experienced users). In addition to the basic features, you get:
    • The ability to flash custom ROM (with or without patching boot.img)
    • Option to flash to both slots.
    • Option to flash to inactive slot.
    • Options to disable verity and or verification.
    • Ability to change the active slot.
    • Ability to live boot to custom boot.img (temporary root).
    • Ability to boot to recovery.
    • Ability to flash custom image: boot, recovery, radio, kernel, ...
    • Ability to sideload an image.
    • Lock / Unlock bootloader.
    • Option to gain temporary root (good for testing or checking things out).
    • SOS Disable Magisk modules to get out of bootloop (experimental).

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