Skip to content

v4.0.0

…or adb shell su allowed), an option to control the Magisk Manager GUI (drive UI) to programatically control the app through [UIAutomator](https://developer.android.com/training/testing/other-components/ui-automator) and create a patched boot.img

See [Patching flow chart](images/Patching%20boot.png) 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 bootloaders 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 falshing 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 Fetaure: 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 identifing 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, transfered 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.
Assets 2