📳🔥 PixelFlasher a GUI tool for flashing

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 / init_boot.img management UI, select the boot / init_boot 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 / Play Integrity passing.
• Display details of boot.img(or init_boot.img for Pixel 7 or newer devices).
  • 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 (Full OTA flashing always keeps data).
• Ability to flash even if multiple devices are connected to the computer.
• Option to flash to inactive slot (Full OTA always flashes to inactive slot).
• Display information about the phone.
  • ID
  • Hardware model.
  • Device architecture.
  • Current installed firmware (build).
  • If it is rooted and with which tool and version.
  • Which of the supported rooting applications are installed and their respective versions.
  • 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.
  • And a lot more...
• In app download of all Pixel phone / watch firmware images and full OTA images (past an present).
• Rooting Application installation UI, screenshot. Supported versions:
  • stable (official)
  • beta (official)
  • canary (official)
  • debug (official)
  • alpha
  • delta canary (Kitsune)
  • delta debug (Kitsune)
  • KernelSU
  • KernelSU-Next
  • Apatch
  • Magisk zygote64_32 canary
  • Special builds that disable modules (used to recover from bootloops due to bad modules).
    • Magisk special v27001
    • Magisk special v26401
    • Magisk special v25203
• 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 settings management, screenshot:
  • Enable / disable Magisk modules, this comes in handy to disable suspect modules before an upgrade.
  • Install Magisk module (zip selection).
  • Direct install common Magisk modules:
    • @chiteroman PlayIntegrityFix
    • @osm0sis PlayintegrityFork
    • TrickyStore
    • ZygiskNext
  • Enable / disable Zygisk.
  • Enable / disable Magisk denylist.
  • Add / remove application to Magisk denylist (through PixelFlasher's App Manger).
  • Grant / deny / SU permissions to an app, with control of (through PixelFlasher's App Manger):
    • Enable / disable notifications
    • Enable / disable logging
    • Grant until (Forever, 10 min, 20 min, 30 min, 60 min)
  • Revoke SU permissions
• 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.
• Wireless Manager, to wirelessly connect to adb debug or adb wireless with pairing support.
• Advanced features are hidden to keep the interface simple and easy to follow.
• Easily open ADB shell to the device.
• Support for Genymotion Scrcpy to mirror Android devices (video and audio) via USB or over TCP/IP, and allows to control the device with the keyboard and the mouse of the computer.
• A lot of checks and validations for smooth operation with quite verbose console output to inform about every step of the operation.
• Automatic check for program and Magisk module updates.
• App Manager, screenshot:
  • Disable (Freeze)
  • Enable
  • Uninstall
  • Install APK
  • Download APK
  • Launch
  • Kill
  • Clear Application Data
  • Multi-Select
  • Show Package Details.
  • Add / remove app to Magisk denylist.
  • Control app's superuser permissions, screenshot.
  • Export Application list
  • Filtering
• Configurable Toolbar
• Pif Manager (see a bit outdated but still valid UI Workflow)
  • Automatically detect Pif related installed modules and manage.
    • Pull / Modify / Push Pif prints to device
    • Cleanup DroidGuard
    • Push keybox.xml
    • Edit TrickyStore Target
    • Process an image file to extract Pif print
    • Process build prop(s) to extract Pif Print
    • Check / Auto-check Play Integrity.
      • Play Integrity API Checker
      • Simple Play Integrity Checker
      • Android Integrity Checker
      • TB Checker
      • Play Store
      • YASNAC
    • Automatically get Pixel Beta Pif ()
    • Get Xiaomi Pif
    • Get TheFreeman193 random Pif
    • Conversion tools
    • Built in json validation
• PI (Play Integrity) Analysis Report to troubleshoot PI related issues.
  • 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 if the certificates 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.
  • Droidguard VM list.
  • If any custom ROM injection apps are installed from:
    • Xiaomi.eu
    • EliteRoms
    • helluvaOS
    • hentaiOS
    • Evolution X
    • PixelOS
  • Check overlays (if contents of /debug_ramdisk is visible without root)
• My Tools, add / remove and manage personal tools to be launched from within the app.
• Dev Tools
• Check keybox validity (one or many)
  • If the certificates in the keybox are on revocation list.
  • If they are AOSP certificates
  • If they are expired or expiring soon.
  • If they are long chained.
  • If any of the certificate issuers are on shadow banned list.
• AVB Image info tool
• AVB downgrade preparation tool.

• The ability to flash custom ROM (with or without patching boot / init_boot)
• 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 / init_boot (temporary root).
• Ability to boot to recovery, fastbootd, safe mode, download mode and sideload.
• 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.
• Force option when flashing.
• Option to skip rebooting.
• Option to wipe.
• Partition Manager:
  • Erase single or multi partitions.
  • Dump / create backup of single or multi partitions and save to PC.

Prerequisites​

• Android SDK Platform-Tools.
• USB Debug turned on in Developer Options and authorized for your computer. (see excellent guide links in credits section below).
• Android Pixel phone factory image or Android Pixel phone full OTA image.
• Bootloader unlocked phone if you want to root or flash Factory image (see excellent guide links in credits section below). Note: Stock OTA sideloading does not require an unlocked bootloader.
• On Windows: The latest Google USB drivers installed in adb and fastboot modes.
• On MacOS: Allow USB Accessory to connect (very important!).
• On Linux: User needs to be added to plugdev group.