Contributors welcome! If you've found a bug or want to improve the codebase, please open an issue or pull request — the project is actively looking for contributors and collaborators.

⬇️ Download

Get the latest release from GitHub Releases — see the release notes there for what's changed recently.

✨ Shizuku+ Core Features

• Universal Privilege Provider: One interface for Root, ADB Shell, and Dhizuku (Device Owner).
• OneUI 8+ Theming Fix: Lets theming engines like Hex Installer or Substratum keep working on Android 16/17 and OneUI 8+.
• Dhizuku Mode: Share the system Device Owner binder with any app that has Shizuku permissions — set up via ADB, no root needed.
• Customizable Gestures: Swipe left, swipe right, and long-press actions, configurable per app.
• In-App Changelogs: See what's new after an update without leaving the app.
• Bulk Management: Multi-select apps to grant/revoke permissions or hide them in one tap.
• Activity Log: Audit trail of API calls and su bridge commands, with app icons and real-time updates.
• Root Compatibility Hub: Dashboard for legacy root apps, with granular module control (Magisk mocking, auto-grant, file interceptor, and more).
• Universal SU Automation: One-tap 'Magic Setup' to point all installed root apps at the Shizuku+ SU Bridge.
• Service Doctor: Diagnoses and fixes service startup issues (Samsung Auto Blocker included).
• Integrated Feature Guides: Every Plus feature has an info icon with a plain-language explanation of what it does.
• Quick Settings Tile: Check and toggle the service status from your notification panel.

🚀 Plus API Features

Shizuku+ provides exclusive system interfaces for advanced automation and tools — none of these exist in stock Shizuku:

• AICore+ Automation Bridge: Privileged UI automation (hierarchy dumps, tap/swipe) for AI-driven tools — no root needed. (added)
• AVF (Virtual Machine) Manager: Run isolated Linux/Microdroid VMs with GPU acceleration. (added)
• Privileged Storage Proxy: Authenticated access to restricted paths for backups and file management. /data/app/ and external /Android/data/ work in ADB mode; /data/data/ requires root (the server must run as UID 0 to cross app-private directory boundaries). (added)
• Device Spoofing (Spoof Device Identity in Settings): Present a different device identity to bypass device-specific restrictions. (added)
• Intelligence Bridge (AI Core Plus): Privileged NPU scheduling and screen context intelligence. (added)
• Window Manager Plus: Force free-form resizing, manage the Bubble Bar, and resilient overlays. (added)
• System Theming Bridge (Overlay Manager Plus): Privileged overlay management for rootless theming (e.g. Hex Installer). (added)
• Network & DNS Governor: Manage Private DNS and firewall routing for rootless ad-blockers. (added)
• Deep Process Control (Activity Manager Plus): Lets process managers kill apps and set standby buckets more aggressively. (added)
• Continuity Bridge: Secure state and task handoff between Shizuku+ devices. (added)

🛠️ Backporting & Optimizations

Shizuku+ makes regular Shizuku apps faster and more compatible without any code changes:

• Transparent Shell Interceptor: Routes common pm, am, and settings commands through faster native APIs.
• Local ADB Proxy: Emulates an ADB server on port 15555, so legacy apps can use Shizuku without Wireless ADB staying on.
• SU Bridge: A Shizuku-backed su drop-in for non-rooted apps that support a custom root path. Common root commands are translated into real framework operations where shell UID allows it — iptables --uid-owner per-app blocks become live NetworkPolicy restrictions, resetprop reads/writes real system properties, and chmod/chown apply for real — falling back to mocked success only when an operation genuinely requires root (e.g. flashing partitions or loading kernel modules).
• plus CLI Helper: A privileged command-line utility, available inside rish.
• Dynamic App Database: Keeps app descriptions and suggestions in the UI up-to-date from GitHub.

⚙️ Modular Control

Everything in Shizuku+ is optional. Use the Plus Features category in Settings to toggle:

• Transparent Shell Interception
• Individual Plus APIs (AVF, Storage, Intelligence, etc.)
• Home screen card visibility
• Activity Logging

🔌 Third-Party App Compatibility

Shizuku+ installs under its own package (af.shizuku.plus.api) so it can coexist with stock Shizuku. Because most Shizuku-aware apps look specifically for the moe.shizuku.privileged.api package, Shizuku+ ships a lightweight Compat Hub — a tiny companion app that registers that package name and forwards binder/permission requests to Shizuku+.

If third-party apps don't detect Shizuku+:

1. Start the Shizuku+ service (ADB or root).
2. On the home screen, use the Compat Hub card to install the companion (it's bundled in the app; installation goes through the running service, so start the service first).
3. Re-open the third-party app — it should now detect Shizuku and receive the service binder.

Alternatively, install the drop-in build, which registers as moe.shizuku.privileged.api directly (do not install it alongside stock Shizuku).

☑️ Requirements

Minimum: Android 7+ · Fully supported through Android 17 (SDK 37)

• Root mode: Requires a rooted device
• Wireless Debugging mode: Android 11+ and all Android TVs
• PC mode: All devices
• Start on boot: Available only with Wireless Debugging or Root mode

On Android 16+, Shizuku+ requests the new Local Network Protection permissions so wireless-debugging discovery and pairing keep working; on Android 17, it transparently handles the hidden-API deviceId change so authorized apps still appear and permission grants still apply.

📱 Developer Guide

See the Shizuku+-API repository for documentation on the exclusive Plus APIs.

🙏 Acknowledgements & Licenses

Shizuku+ is a community-driven enhancement and fork of thedjchi/Shizuku, which is itself a fork of the original RikkaApps/Shizuku. This project is not affiliated with the original RikkaApps team.

Thanks to the following upstream contributors and projects whose work makes Shizuku+ possible:

• RikkaApps / Rikka — For the foundational Shizuku project and its elegant API design.
• thedjchi — For the intermediate fork and quality-of-life improvements, and for carrying the Android 17 (SDK 37) compatibility work that Shizuku+'s A17 support is adapted from.
• kerneldroid / Nightzuku — Origin of the Android 17 hidden-API deviceId compatibility approach (the Android17Compat / InstalledPackagesCompat reflection layer) and Local Network Protection handling that this fork's A17 support descends from.
• LandonMoran — For porting Nightzuku's Android 17 support into the thedjchi fork and verifying it end-to-end on a physical Android 17 device (pairing, service start, and the authorized-apps list), which is the field validation Shizuku+'s port builds on.
• Muntashir Akon — For the aShell You codebase, which inspired the terminal and shell automation features.
• iamr0s — For Dhizuku, enabling the unified Device Owner privilege mode, and AndroidAppProcess for standalone Java process execution.
• pascua28 — For native Samsung System UID 1000 escalation integration.
• kerneldroid — For the Nightzuku fork, which inspired our Android 16/17 (SDK 37) hidden API resilience (handling deviceId) and UI modernizations.
• ShizukuExt-SystemUID — For conceptualizing systemic UID 1000 privilege escalation beyond standard limits.

Upstream Projects

Open Source Libraries

Full license texts and per-library details: OPEN_SOURCE_LICENSES.md | NOTICE

📃 License

Apache 2.0

Contributors

Thank you to everyone who has contributed code, translations, and testing to Shizuku+:

Code Contributors

Translation Contributors

Plus many more via community translation through Weblate — thank you to all translators!

Acknowledgments

• Special thanks to AkayamiShurui42 for the proactive security research and stability patches (Reference: #239).
• Thank you to AlexeiCrystal for identifying MIUI crash bugs and suggesting the Compat Hub workaround for legacy apps (#241, #242).
• Thank you to ddnexus and kai-bash for highlighting the Device Owner factory reset trap and Google Backup conflicts (#237).
• Thank you to Kevinco1 for feedback on root compat app detection issues (#243).
• Thank you to aragortsantiago6-beep and Scoop2389 (Pixel 9a) and ConversionRituals (Xiaomi) for on-device Android 16/17 testing, crash reports, and logs that drove the SDK 37 hidden-API and Local Network Protection compatibility fixes (#317, #323).
• Thank you to gmm96 for extensive multi-round logcat debugging across several builds that pinned down the Cached Apps Freezer binder-delivery bug (#371).
• Thank you to odorizzioficial for the complete Brazilian Portuguese translation (#409), and for the detailed report on the Samsung "Sleeping apps" Watchdog freeze (#415).

v13.6.0.r2551

Other

• ci: upgrade checkout and setup-java actions to v5 (887c7134)

📦 Recent Releases

📣 You're viewing an older release. Here are the current builds — update for the latest fixes:

🚀 Most recent major release — v13.6.0.r2603 App Backup overhaul: search/filter the app list by name or package, back up all apps at once with a single menu tap, toggle system-app visibility, and restore external data directly from any backup file (external.tar.gz). Each row now shows the app version name and a 'no-backup' badge when android:allowBackup=false, matching what Swift Backup and Neo Backup display. The SAF export directory is surfaced in the home card summary and in the completion Snackbar. After restoring ShizukuPlus settings a persistent Snackbar offers an immediate restart so theme/language changes apply without manually force-stopping the app.

🏛️ Major release of this build's era — v13.6.0.r2535 — Third-party app detection fix + AppOps IPC Parcel alignment (#480, #488, #491)

⚠️ Most recent critical fix — v13.6.0.r2590 Fixed Settings import/export silently reading/writing the wrong storage file on Android 7+ (exports were empty; imports had no effect). Fixed Feature Hub crash (ClassCastException) caused by migrateAutomationTrustedNetworks reading the wrong SharedPreferences file. Fixed AutomationService double-firing network firewall rule, not starting the app monitor for auto-hide-only users, and not restarting correctly at boot on API 24-25. Fixed WatchdogService clearing watchdog setting on transient foreground-start rejections.

Full Changelog