cyb3rl00m/prune-debloater
System ToolsDebloat and optimize Android phones with risk-rated package removal, previews and per-change undo.
What it is
Prune is an open-source Android debloater and optimizer, positioned as the Android counterpart of desktop tools like WinUtil. It scans installed packages, explains what each one is, rates the risk of removing it, and applies changes at four debloat levels, from removing obvious junk to handling every changeable package yourself. It originally targeted Samsung Galaxy devices, but version 2.0 adds manufacturer detection and dedicated rules for Samsung, Pixel, Xiaomi/Redmi/POCO, Huawei, Honor, OPPO/OnePlus/realme and Motorola, with generic support for other Android 9+ phones. Notably, only the Android emulator has been used for automated testing; no brand has been tested on physical hardware by the project yet (compatibility notes).
The target user is an Android owner who wants fewer preinstalled apps and less background data collection but still wants a way back. Every change is previewed, recorded with its prior state, verified against Android after execution, and can be undone. Package identification combines names, labels, installer information, manufacturer, Android version, Prune's rule files and the community database from Universal Android Debloater Next Generation; unrecognized packages are marked Unknown rather than safe (README).
Quick start
Prerequisites: an Android 9 (API 28) or newer device, and Wi-Fi for the wireless-debugging path. HarmonyOS NEXT cannot run Android apps and is not supported.
- Download
Prune-2.0.0.apkfrom the latest release and allow installation from your browser or file manager. Compare it withSHA256SUMS.txtif you want to verify the file. - Install Shizuku from Google Play or its GitHub releases.
- Enable Developer options by tapping Build number 7 times (the menu path differs by manufacturer), then turn on Wireless debugging.
- In Shizuku, choose Start via Wireless debugging → Pairing, enter the pairing code, then tap Start.
- In Prune, open Home → Set up → Authorize Prune in Shizuku.
- Answer which phone features you use, choose a debloat level, review the preview, and apply. After any change, use Restore → History to undo it.
Without Shizuku or root, Prune can export the plan as an ADB script to run from a computer. On Xiaomi/Redmi/POCO you must also enable USB debugging (Security settings); on OPPO/OnePlus/realme you must enable Disable permission monitoring.
Permissions and operations
A normal Android app cannot disable or remove system packages, so Prune works at three tiers. Standard install allows scanning, classification, duplicate detection, compatibility reports, opening app settings and uninstalling apps you installed. With Shizuku via wireless debugging, disabling, uninstalling for the user, restoring, background restriction, permissions, notifications, battery exemptions, animation scales, cache trimming, compilation and battery estimates become available. Root via Magisk/KernelSU/APatch is optional and never required. Shizuku stops after a reboot and must be started again.
Safety and limitations
Locked packages include telephony, emergency calling, IMS, System UI, Settings, package installers, network stack, Bluetooth, NFC, biometrics, Play Services and WebView, plus manufacturer-critical apps; they cannot be selected even in Custom mode. "Disable" and "Uninstall for this user" keep the original APK, and pm install-existing restores it. Commands are passed as argv lists rather than shell strings, with strict validation of package names, app-ops, permissions and settings.
Limitations are significant: real-phone behavior, Shizuku user-service binding and root paths still need device testing; manufacturer rule files are hand-curated and incomplete; package names can change between firmware versions and regions; battery estimates depend on firmware-specific dumpsys batterystats output; and Prune only works on the current Android user, not Secure Folder, Second Space or work profiles. The project is GPL-3.0-or-later.
Build from source
JDK 17 and Android SDK 35 are required. Clone the repository, then run ./gradlew testDebugUnitTest assembleDebug. The package database is generated from tools/rules/*.json plus the community list with python3 tools/build_db.py. Contribution guidance is in CONTRIBUTING.md.
HotRepo's take
On the HotRepo new-project list for 2026-11-22, the repository recorded 123 stars and 6 forks, with 23 stars gained in the roughly one-hour observation window; the trajectory covers only that snapshot, so the project's per-language daily rank is not known. The substance here is the release engineering: locked packages, preview and verified undo, and a documented permission model, but the project itself states on that same snapshot date that no physical phone has been tested. That gap between the test status and the reach of a debloating tool is the main observation for anyone considering it.
Written by AI from the project's public information and HotRepo's records, updated . The project's own docs are the source of truth.
You might also like
- Universal-Debloater-Alliance/universal-android-debloater-next-generationA Rust GUI that uses ADB to remove preinstalled system apps from non-rooted Android devices, improving privacy, attack surface and battery life.
- ChrisTitusTech/lg-debloatA Python CLI that trims promotions and background apps on rooted LG webOS TVs, with a restorable state record.