Xhizuku
4.0.0.r1.317f8a7 · GitHub
More about this app
Maintained Shizuku fork with Material 3 Expressive UI, ADB module runner, onboarding wizard, server monitor and built-in diagnostics
Xhizuku 
Xhizuku is a fork of Nightzuku, maintained by xeonleonreal. It provides a robust, high-performance interface for applications to use system APIs directly with elevated permissions (root/ADB).
This project tracks the latest Android platform developments, including Android 16/17 target stability, introduces a revamped Modern Material 3 Expressive UI using Jetpack Compose, includes a full ADB-backed ZIP modules runner, onboarding wizard for new users, XStatus monitor and Magisk-style bottom menu.
Important
Migration Action Required: Due to the package identity upgrade (moe.shizuku.privileged.api -> xeonleon.xhizuku), you MUST UNINSTALL any older official Shizuku Manager app from your device before installing Xhizuku. Otherwise, they will conflict.
Upstream project reference: https://github.com/RikkaApps/Shizuku
Fork additions
Nightzuku
- Jetpack Compose manager UI with Material 3 Expressive components, motion, switches, and rounded icon treatment.
- Android 16/17 target work with current preview SDK/build tooling in this fork.
- ADB Modules screen for installing and managing ZIP modules.
- Module features:
module.prop, banner, enable/disable switch,action.sh, policy-gatedservice.sh, local WebUI, delete, path checks, size limits, output limits, and last-run logs. - Module policy settings: Safe mode, Full access, and background action control.
- Debug test module under
test-modules/adb-test-module.
Xhizuku
- Onboarding wizard, that helps users to migrate from shizuku
- Magisk style menu
- Theme color overide in Xhizuku
- XStatus: CPU, GPU, memory and swap usage in an ongoing notification
- Expandable card descriptions on the status page (tap the arrow to show or hide long explanations)
- ..and many more! See full additions
Documentation
- ADB Modules guide
- ADB Modules API reference
- Xhizuku Connectors API
- Android 17 Compatibility
- Wear OS Compatibility*
- Wear OS Pairing Guide*
- Android TV Support*
- NightDog Watchdog
- *Please be aware that this is a new fork and I didnt check for these yet
Background
When developing apps that require root, the standard approach is running commands in a su shell. This is slow, unreliable due to text processing, and limited to available commands. Even with ADB, apps often require root for privileged operations.
Xhizuku provides a high-performance alternative by allowing apps to use system APIs directly with elevated permissions.
How does Xhizuku work?
Android uses binder for interprocess communication (IPC) between apps and the system server. The system server checks the UID/PID of the client to enforce permissions.
Xhizuku guides users to start a Xhizuku server process with root or ADB. When an authorized app starts, it receives a binder to the Xhizuku server.
Xhizuku acts as a proxy, receiving requests from the app and forwarding them to the system server. This allows apps to use system APIs with the server's elevated permissions (root or ADB), making it almost identical to using system APIs directly.
Screenshots
📸 Click to open Screenshot Gallery
Phone UI
![]() Main Screen |
![]() Authorized Apps |
||
![]() ADB Modules |
![]() Module WebUI |
||
![]() Settings |
![]() Onboarding Wizard |
||
Developer guide
API & sample
Official API and samples are available at: https://github.com/RikkaApps/Shizuku-API
Technical Details
ADB Permissions: ADB permissions vary by system version. Check available permissions in the Shell AndroidManifest. Use
ShizukuService#getUidorShizukuService#checkPermissionto verify server capabilities.Hidden API Restrictions: From Android 9, hidden API usage is restricted. Use tools like AndroidHiddenApiBypass if necessary.
Android 8.0 & ADB: On API 26, ADB lacks permissions to use
registerUidObserver. If your app process is not started by an Activity, you may need to start a transparent activity to trigger binder transmission.Direct
transactRemoteUsage: Signatures for hidden APIs change between Android versions. WhileShizukuBinderWrapperhandles most cases, direct transaction calls must be carefully verified against the target platform's AIDL definitions.
Developing Xhizuku
Build
- Clone with
git clone --recurse-submodules - Build with Gradle:
./gradlew :manager:assembleDebug
The :manager:assembleDebug task generates a debuggable server. Ensure "Always install with package manager" is checked in Android Studio to use the latest server code during debugging.
License
All code is licensed under Apache 2.0.
- Icon Usage: You may not use
manager/src/main/res/mipmap*/ic_launcher*.pngfor anything other than displaying Xhizuku. - Identity: You may not use
Shizukuas an app name or usemoe.shizuku.privileged.apias an application ID in derived works. The current package identity isxeonleon.xhizuku.
Credits
- RikkaApps for Shizuku itself
- Razgame for app list fix
- kerneldroid for Nightzuku
Star History
How Shizuku is used
Can run console commands, ADB modules and WebUI shell, monitor status, view logs and manage app access via `sh -c` and system services
This is an AI-assisted analysis of Shizuku-related usages in the app's public source code. It is best effort, so it may not catch every single usage.
How this app uses Shizuku
This fork uses Shizuku as its privileged backend to run shells, inspect the server and manage clients.
- Run console commands: users can type shell commands in the console tab which are executed with
sh -cthrough Shizuku with output, exit code and elevated status shown. - Run ADB modules: users can install modules and run their bundled action and background service scripts as a privileged shell through Shizuku with results and logs shown in the modules list.
- Power module Web UIs: a module web interface that declares shell support can send shell commands through Shizuku and get output, exit code and timeout status back in the Web UI.
- Monitor server status: users can see CPU use, memory and swap use, load average and GPU use collected through privileged reads of
cat /proc/stat,cat /proc/meminfo,cat /proc/loadavgand GPU nodes. - Check ADB port: users can see the wireless debugging port read with
getprop service.adb.tcp.portandgetprop persist.adb.tcp.portthrough the privileged shell. - View server logs: users can open a filtered server log view that runs
logcatthrough Shizuku and shows only Shizuku related lines, with copy and share actions. - Run diagnostics tests: users can run built in checks that execute
idin a privileged shell, count packages through the privileged package service and read device model, brand and build fingerprint values through Shizuku. - Manage authorized apps: users can see which apps requested access and allow or deny them, backed by privileged package and permission manager queries and flag updates.
- Review audit history: users can review recent allow and deny decisions and usage counts retrieved through the Shizuku server.
Android APIs or commands used
sh -ccat /proc/statcat /proc/meminfocat /proc/loadavgcat /sys/class/kgsl/kgsl-3d0/gpu_busy_percentagelogcat -d -t 1500 -v timepidof shizuku_servergetprop service.adb.tcp.portgetprop persist.adb.tcp.portidIPackageManager.getInstalledPackagesIPackageManager.getPackageInfoIPackageManager.getApplicationInfoIPermissionManager.checkPermissionIPermissionManager.grantRuntimePermissionIPermissionManager.revokeRuntimePermissionUserManager.getUsersandroid.os.SystemProperties.get
Notable details
Status collection, console commands and server logs fall back to a local shell and direct reads when the privileged shell is unavailable. Package and user lookups return empty or local only results without Shizuku.
Changelog
What's new for version 4.0.0.r1.317f8a7
1. Ported from kerneldroid
- Blocked termux backdoor (Frant flags manager-only)
- managerAppId app-id compare
- Revoked apps no longer respawn (UID_OBSERVER_IDLE removed)
- Permission state pushed to clients
- Module ZIP path traversal hardened
- Module scripts run in $MODDIR; module dirs readable by server
- Module output capped; index.htm; trust cleared on delete
2. Fixed
- Fixed a logging system
- Log refresh race wiped newer results
- App log fixed and now works normally.
- Audit show now a uid and package of app.
3. Added:
- Developer menu, Check logs, Spoof activation, Tools
- Added Permission Audit
Permissions
13 permissions requested





