rushiranpise/Shizuku-Next

Shizuku-Next

An enhanced fork of Shizuku that lets apps use system APIs through ADB or root.

Shizuku-Next continues development of thedjchi's Shizuku fork, based on the original RikkaApps/Shizuku.

It keeps Shizuku's package name and API, so compatible apps continue to work.

Important: This fork uses a different signing key. Uninstall the official Shizuku or thedjchi's fork before installing Shizuku-Next. A server started by the previous app may remain active until stopped or the device is rebooted.

If you want the original app, visit RikkaApps/Shizuku.

Get the latest build from Releases.

• Start through wireless debugging, USB debugging, root, or Samsung system UID where supported.
• Automatically handles wireless-debugging pairing, including reading the pairing code on supported devices.
• Optional start on boot, watchdog restarts, automatic recovery, and configurable restart timing.
• TCP mode, USB-port recovery, and experimental startup without Wi-Fi.
• Optional mode to hide Developer options and ADB settings.
• Clearer startup status, diagnostics, and failure logs.

• Material 3 interface with Home, Apps, Modules, Labs, and Settings.
• Manage Shizuku access, app permissions, app ops, battery settings, and app network access, with a fallback to the platform's own firewall API on ROMs whose connectivity command is missing.
• Inspect app details and launch activities.
• Built-in shell, log viewer, file browser, and app installer.
• Manage saved Wi-Fi networks and export/import their credentials.
• Force dark mode and hide selected device settings for chosen apps.
• Batch permission changes, searchable app lists, and device information.
• Tasker and other automation support through intents and status broadcasts.

• Experimental ADB module support, including module actions, services, and WebUI. Writing a module covers the format: module.prop, the environment a script runs in, the WebUI bridge, trust, and how a module gets found.
• Stealth mode and in-app updates.
• Android TV and VR-friendly UI support.
• MediaTek compatibility fixes and improvements for some devices.

Some features are experimental or device-dependent. Root, Samsung system-UID, and no-Wi-Fi startup methods are not available on every device. Only install modules and scripts you trust.

• Android 7.0 or newer
• Wireless debugging: Android 11 or newer; supported Android TVs are also compatible.
• USB/PC start: A computer with ADB.
• Root start: A rooted device with working root access.
• System UID start: Supported Samsung devices only.
• Start on boot: Supported start methods only.

See the wiki for setup and troubleshooting guidance.

• No tracking or analytics.
• No telemetry or proprietary libraries.
• No Google Play Services dependency.
• Open-source code and reproducible builds.
• Internet access is used for wireless-debugging connections, for checking and downloading GitHub updates, and for the module lists, which are read from GitHub.

The app requests permissions for features such as notifications, background services, wireless debugging, and boot startup. See the app's permission page and source code for details.

Help translate Shizuku-Next on Crowdin. See docs/translations.md for translation details.

Shizuku-Next is free and contains no ads. If you'd like to support development, you can buy me a coffee.

Please also consider supporting the upstream projects: thedjchi and RikkaApps/Shizuku.

The API documentation and demo project are available in the Shizuku-API repository.

Shizuku may run with different privileges depending on the start method. Check the server UID and permissions before assuming root access. Prefer ShizukuBinderWrapper over calling transactRemote directly when possible.

git clone --recurse-submodules https://github.com/rushiranpise/Shizuku-Next.git
cd Shizuku-Next
./gradlew :manager:assembleDebug

For a release build, run:

./gradlew :manager:assembleRelease

The debug task builds a debuggable server. In Android Studio, enable Always install with package manager in the Run/Debug configuration when debugging shizuku_server.

1. Fork the repository.
2. Create a feature branch.
3. Make and test your changes.
4. Commit and push your branch.
5. Open a pull request.

• RikkaW / RikkaApps - original Shizuku, server, and API.
• thedjchi - upstream fork and many inherited features.
• kerneldroid - Nightzuku, where the ADB modules feature comes from: the module format itself, actions and services, and the window.Shizuku WebUI bridge.
• Shevery - the published module API and guide this app's module support is written against, and the module catalogue it searches.
• ShizuWall (AhmetCanArslan) - the firewall's fallback to the system API where a ROM has no connectivity command for it to use, and the technique behind it: the interface reached as Shizuku with a wrapped binder, by reflection.
• Xhizuku - the other implementation of that format, whose documentation this one is checked against.
• KernelSU-Next - the card, chip and tab layout the modules list and the Material 3 interface follow.
• MMRL - the label component whose default accent colour the module cards' size chip follows.
• All upstream contributors and Crowdin translators.

Licensed under Apache License 2.0.