Grab the latest release from GitHub Releases. See each release's notes for details.

• Universal permission provider: a single interface unifying Root, ADB Shell, and Dhizuku (Device Owner) as permission sources.
• OneUI 8+ theming fix: keeps theme engines such as Hex Installer and Substratum working on Android 16/17 and OneUI 8+.
• Dhizuku mode: shares the system Device Owner Binder with any app holding Shizuku permission — configurable via ADB, no Root required.
• Customizable gestures: swipe left, swipe right, long press and more, configurable per app.
• In-app changelog: view release highlights right after an update without leaving the app.
• Batch management: select multiple apps to grant/revoke permissions or hide them in one tap.
• Activity log: real-time audit of API calls and su bridge commands, with app icons and live refresh.
• Root compatibility hub: a dashboard for legacy Root apps with fine-grained module controls (Magisk spoofing, auto-grant, file interception, etc.).
• Universal SU automation: one-tap "magic settings" that points all installed Root apps at the ShizukuX SU bridge.
• Service diagnostics: diagnose and fix service startup issues (including Samsung Auto Blocker).
• Built-in feature guidance: every enhancement ships an info icon explaining its purpose in plain language.
• Quick Settings tile: view and toggle service status from the notification shade.

ShizukuX provides exclusive system interfaces that the original Shizuku does not have, for advanced automation and tooling:

• AICore+ automation bridge: Root-free privileged UI automation for AI tools (hierarchy dump, tap/swipe). (intro commit)
• AVF (Virtual Machine) manager: run isolated Linux/Microdroid VMs with GPU acceleration. (intro commit)
• Privileged storage proxy: authenticated access to restricted paths (/data/data/, /data/app/) for backup and file management. (intro commit)
• Device spoofing (Spoof Device Identity in Settings): present different device information to the system to bypass model-specific restrictions. (intro commit)
• Smart bridge (AI Core Plus): privileged NPU scheduling and screen-context intelligence. (intro commit)
• Window Manager Plus: force free-form window resizing, manage floating bubble bars and elastic overlays. (intro commit)
• System theme bridge (Overlay Manager Plus): Root-free privileged Overlay management for theming (e.g. Hex Installer). (intro commit)
• Network & DNS governor: manage private DNS and firewall routing to power Root-free ad blocking. (intro commit)
• Deep process control (Activity Manager Plus): let process managers kill apps more aggressively and set standby buckets. (intro commit)
• Continuity bridge: securely transfer state and tasks between multiple ShizukuX devices. (intro commit)

Without touching a single line of code, ShizukuX makes ordinary Shizuku apps faster and more compatible:

• Transparent shell interceptor: routes common pm, am, and settings commands to faster native APIs.
• Local ADB proxy: emulates an ADB server on port 15555 so legacy apps keep working with Shizuku after wireless debugging is off.
• SU bridge: a Shizuku-based su alternative for Root-free apps that support custom Root paths.
• plus command-line tool: a privileged CLI usable inside rish.
• Dynamic app database: syncs app descriptions and suggestions from GitHub in real time to keep the UI current.

Everything in ShizukuX is optional. Toggle features under the Plus features category in Settings:

• Transparent shell interception
• Individual Plus APIs (AVF, storage, smart, etc.)
• Home screen card display
• Activity log

ShizukuX installs under its own package name (xyz.shizuku.extra.api) and can coexist with the original Shizuku. Since most Shizuku apps only check for the moe.shizuku.privileged.api package name, ShizukuX ships a lightweight Compat Hub — a tiny companion app that registers that package name and forwards binder/permission requests to ShizukuX.

If a third-party app can't detect ShizukuX:

1. Start the ShizukuX service first (ADB or Root method).
2. On the home screen, use the Compat Hub card to install the companion app (it ships inside the APK; installation depends on a running service, so start the service first).
3. Reopen the third-party app — it should now detect Shizuku and receive the service binder.

You can also install the drop-in variant, which registers directly as moe.shizuku.privileged.api (do not install it alongside the original Shizuku).

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

• Root mode: requires a rooted device
• Wireless debugging mode: Android 11+ and all Android TVs
• PC ADB mode: all devices
• Boot startup: available in wireless debugging or Root mode only

On Android 16+, ShizukuX requests the new local network protection permission to keep wireless debugging discovery and pairing working; on Android 17, it transparently handles the hidden API deviceId change so authorized apps remain visible and permission grants keep working.

Documentation for the exclusive Plus APIs lives in ShizukuX-API (the api submodule of this repository points to it).

ShizukuX is a community-driven enhanced fork originating from thedjchi/Shizuku (itself a fork of RikkaApps/Shizuku), continued through ShizukuPlus. This project has no affiliation with the original RikkaApps team.

Thanks to the following upstream contributors and projects whose work made ShizukuX possible:

• RikkaApps / Rikka — the Shizuku foundation and its elegant API design.
• thedjchi — intermediate fork with experience improvements, and home of the Android 17 (SDK 37) compatibility work that ShizukuX's A17 support was ported from.
• kerneldroid / Nightzuku — source of the Android 17 hidden API deviceId compatibility (Android17Compat / InstalledPackagesCompat reflection layer) and local network protection handling.
• LandonMoran — ported Nightzuku's Android 17 support into the thedjchi fork and validated it end-to-end on a real Android 17 device (pairing, service startup, authorized app list), providing the on-device verification basis for ShizukuX's port.
• Muntashir Akon — the aShell You codebase that inspired the terminal and shell automation features.
• iamr0s — Dhizuku for the unified Device Owner permission mode, and AndroidAppProcess for standalone Java process execution.
• pascua28 — native Samsung System UID 1000 privilege integration.
• kerneldroid — the Nightzuku fork that inspired our Android 16/17 (SDK 37) hidden API resilience (handling deviceId) and UI modernization.
• ShizukuExt-SystemUID — the concept of system-level UID 1000 privilege beyond normal limits.

Full license texts for each library: OPEN_SOURCE_LICENSES.md | NOTICE

Apache 2.0

• Special thanks to AkayamiShurui42 for proactive security research and stability patches (ref: #239).
• Thanks to AlexeiCrystal for pinpointing the MIUI crash and proposing the Compat Hub scheme for legacy apps (#241, #242).
• Thanks to ddnexus and kai-bash for flagging the Device Owner factory-reset pitfall and Google Backup conflicts (#237).
• Thanks to Kevinco1 for feedback on Root compatibility app detection (#243).
• Thanks to aragortsantiago6-beep, 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).
• Thanks to gmm96 for multiple rounds of logcat debugging that finally isolated the Cached Apps Freezer binder delivery bug (#371).
• Thanks to odorizzioficial for a complete Brazilian Portuguese translation (#409) and a detailed report on Samsung "Sleeping apps" watchdog freezes (#415).