Releases: badabing2005/PixelFlasher
Releases · badabing2005/PixelFlasher
Release v7.4.2.2
- Improve the Github Action that updates the Cask.
- Handle 'grep' is not recognized as an internal or external command error.
Release v7.4.2.1
- To future proof APatch Alternate patching, give an option to the user to proceed even if the requirements aren't met.
- Add more debug messages when
CONFIG_KALLSYMS=y
is not detected.
Release v7.4.2.0
- Pixel August 2024 Update: Due to bootloop issues when using the APatch app for patching, manual APatch patching is recommended. PixelFlasher automates this manual process—just select
Patch with APatch Alternate
. You’ll be prompted to choose between the latest release or the latest pre-release of Kernel Patch tools. - APatch Validation: Added validation for APatch patching to ensure the kernel is a supported version and that
CONFIG_KALLSYMS
is enabled. - Homebrew Cask Support: Added a Homebrew cask install option for macOS, ensuring automatic updates. Use the command:
brew install badabing2005/pixelflasher/pixelflasher
. - PR Merge #239: On Linux, PixelFlasher now uses
xdg-open
(if available) instead of Nautilus, thanks to @aarjaneiro. - 16K Page Size Preparation: In preparation for the upcoming 16K page size feature in Android, PixelFlasher now reports the current page size.
- Miscellaneous: Various minor improvements.
Release v7.4.1.2
- Update the readme for MacOS installation to include
brew install
option
Release v7.4.1.1
- Bump version to 7.4.1.1
- Thank you @yurikoles for the cask.
Release v7.4.1.0
- Added cask for MacOS brew install
- Added Github action to auto update the cask on release
- Additional exception handling.
Release v7.4.0.0
- Improved Performance: Some Magisk module update URLs were slow to respond, making PixelFlasher appear frozen. Added an option in settings to bypass module update checks.
- Module Updates: Explicitly report which modules encounter update issues.
- Device Recognition: Added Pixel 9 series and Pixel Watch series to the recognized Google devices list for enhanced device details.
- UI Enhancements: Added widgets to control PiFork's advanced granular spoofing settings, making it easier to change print contents.
- Model Detection: When extracting PIF print from an image, if the model is not in the Google device list, it is now picked up from
vendor.prop
. - Bugfix #235: Fixed utf-8 encoding issues in application names when exporting from App Manager.
- Bugfix #236: Enabled the
Push keybox.xml
button even when using TrickyStore forks. - Error Reporting: Now reports an error when the device state is not one of the recognized states ['device', 'recovery', 'sideload', 'rescue']. This addresses issues with custom platform tools.
- Permissions Check: Detects misconfigured permissions of platform tools and guides the user to Google documentation.
- Help Menu Update: Added a link to the TrickyStore GitHub repo under the Help menu (thanks @VisionR1).
- PI Analysis: Added a check in PI analysis reports for visible overlays without root.
- Keybox Testing: Added multi-select capability when testing keyboxes.
- New Feature #237: Added a
Push print, no validation
button, allowing users to push prints without validation, preserving comments in thepif.json
. - Default Settings: With spoof functionality removed from TrickyStore, PIF Manager now prioritizes default selection to PIF/PiFork module instead of TrickyStore.
- Miscellaneous: Various small improvements.
Release v7.3.2.0
- Added Droidguard VM list to
PI Analysis Report
- More flexible code for Zygisk state and Magisk denylist enforced state.
- PIF Manager, favorites improvement.
- Bugfix: targets.txt editing was not pushed to device.
- Support for upcoming PiFork features (currently only available in PiFork CI builds).
- Added more exception handling.
Release v7.3.1.2
- Bugfix: Corner case bug when TrickyStore (with non-existant spoof-build-vars) is active along PiFork with custom.pif.json, the contents of custom.pif.json was not being loaded in Active Pif console.
Many thanks to @frank93 for discovering the issue and then doing multiple tests to help narrow down the issue.
Release v7.3.1.1
- Make sure device_pif variable is always stored as string.
- When doing DG Cleanup, print instead of debug.