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.

Release v7.3.1.0

• Add PI Analysis Report to the Main Toolbar for easy access.
• If debug option is not selected, keybox check will redact serial numbers and issuers, if you want to see those, enable debug.
• Added custom ROM injection apps to PI Analysis Report (list taken from PlayIntegrity Fork by @osm0sis).
  • Xiaomi.eu
  • EliteRoms
  • hentaiOS
  • Evolution X
  • PixelOS
• Made the PI Analysis Report dialog smaller (with scroll bar) to accomodate for smaller displays.

Release v7.3.0.0

• New Feature: PI (Play Integrity) Analysis Report.
  The feature will generate a device analysis report that you could post online to get assistance on Play Integrity related issues.
  The report will inherently reveal sensitive information about your device such as:

  • Device id and other device related details.
  • Magisk (if available):
    • modules list.
    • denylist.
  • TrickyStore (if available):
    • /data/adb/tricky_store/spoof_build_vars
    • /data/adb/tricky_store/keybox.xml (Not the contents, just the serial numbers of the certificates and if they are revoked or not)
    • /data/adb/tricky_store/target.txt
  • PlayIntegrity Fork (if available):
    • /data/adb/modules/playintegrityfix/custom.pif.json
    • /data/adb/modules/playintegrityfix/custom.app_replace.list
    • /data/adb/modules/playintegrityfix/scripts-only-mode
  • PlayIntegrityFix (if available):
    • /data/adb/modules/playintegrityfix/pif.json
    • /data/adb/pif.json
  • Whether a testkey ROM is used or not.
  • logcat for PlayIntegrity and TrickyStore related logs.

  NOTE:
  This report will be saved at a location of your choosing, and will not be part of PixelFlasher captured logs (even though you see it in the console), so rest assured, if you submit support.zip for PixelFlasher related issues, even if you had generated such report, it will never be included in the support.zip file.
  
  Your privacy is yours to keep.

• In PIF Manager you can edit TrickyStore's targets.txt.

• Miscellaneous fixes and improvements.

Release v7.2.0.1

• Set a default PIF format to json to allow displaying the print when Processing Image in PIF Manager.
• When PIF Manager is used with an unrooted device or one without granting su permissions to shell, display a message to inform the user about the reduced PIF Manager functionality.

Release v7.2.0.0

• In Magisk Manager, added the option to install Tricky Store module. (You now have 3 PIF related modules to choose from, Playintegrity Fix, Playintegrity fork, Tricky Store).
• Updates to PIF Manager:
  • Option to convert from Json to prop (Env) format and vice versa (Tricky Store uses prop format) .
  • Compatible with Tricky Store (latest CI), you can now edit / update / test using Trick Store module.
    Note: Tricky Store module does not yet support automatic updates, hence PixelFlasher is currently setup to point to the latest release in Github, this still uses Json file to spoof prints, use the latest CI.
  • If you have multiple PIF modules, for example if you use Trick Store and PiFork together, you can select which module's print you want to edit / update by selecting from the combo box. (Only enabled PIF modules are listed).
  • When loading prints from favorites, or console output, or using Smart Paste, PixelFlasher automatically converts the print to the format (json / prop) that the module requires.
  • Added option to push keybox.xml file to Tricky Store's predefine path.
  • Added a button to generate FrameworkPatcher compatible code for use in Android.java, just select the print, generate code and paste it in the proper section of Android.java to use your custom print with FrameworkPatcher.
    Note: the generated code by default is commented out, as you can select multiple prints, just uncomment the ones you want to apply.
• Added option to backup / restore /data/adb directory, please be aware that this only backs up / restores /data/adb/*, any modules that installs files outside this path will not be backed up, as it's impossible to know what all modules do.
• New features in My Tools Manger
  • Different methods to launch application.
  • Option to enable / disable launching detached process.
  • Option to insert separator.
    Note: Start with the defaults and experiment if default behavior is unacceptable.
• Miscellaneous fixes and improvements.

Release v7.1.1.1

• Bugfix: #222 Customize My Tools menu is duplicatede when no tools are added.

Release v7.1.1.0

• Windows versions of PixelFlasher are now signed (self-signed).
  Hopefully this would cut down on false positive virus / trojan alerts, but it should also get rid of Unrecognized app warnings.
  PixelFlasher.crt is the certificate, and ca_badabing2005.crt is the root CA.
• Bugfix: #221 handle a corner case exception.

Release v7.1.0.0

• Add license headers to source files.
• Improved logging.
• By request, PIF Manager now supports processing img files to extract PIF prints. (This is in addition to supporting zip files of factory / OTA images).
• Check keybox.xml tool now provides more extensive report about the keybox.

Release v7.0.0.0

• When sideloading OTA, automatically cancel a previous OTA (in progress or completed but not rebooted), which assures a better success rate. (Only applies to rooted devices that are in adb mode).
• Added My Tools Menu, you can now add custom tools to PixelFlasher to easily launch your favorite tools / apps (example odin3).
• Added Process Image in PIF Manager, PixelFlasher can now process a device image and extract PIF print from it with a single click. (Currently supported image types are, Pixel firmware, Pixel OTA, images with payload.bin, Samsung firmware).
• When reading device details, report the sys.oem_unlock_supported prop value.
• Miscellaneous minor improvements.