ShizuStore

Shizuku-Next

rushiranpise

14.0.36-next · GitHub

Download APK
Shizuku implementations Android 7.0+ 1 day ago Apache-2.0
8.4k ShizuStore
367.7k GitHub
2k Stars
7 MB Size

More about this app

Maintained continuation of thedjchi's fork: automated pairing without typing, start method selection, watchdog, in-app shell terminal, app-ops/firewall manager and a Material 3 UI

Shizuku Next

Shizuku-Next

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

Home screen Apps screen Settings screen

Stars Downloads Latest Stable Latest Beta Issues Crowdin

About

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.

Download

Get the latest build from Releases.

Features

Starting and reliability

  • Start through wireless debugging, USB debugging, root, or the Samsung FOTA-agent system UID path 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 on Android 11 to 16.
  • Optional mode to hide Developer options and ADB settings.
  • Clearer startup status, diagnostics, and failure logs.

Manager tools

  • 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.

Firewall

The firewall uses Android's OEM deny chain 3. It can exist from Android 11, but some Android 11 and 12 ROMs do not expose it. The Firewall row appears only after the device answers that the chain is available. Open Labs > Firewall, turn the switch at the top on, then switch on the apps whose network access should be blocked. Work profile and cloned apps appear as their own rows, keyed by user. On Android 13 and newer, the cellular icon beside a blocked app blocks it only on mobile data instead of on every network.

Modules and compatibility

  • 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 FOTA-agent system-UID, and no-Wi-Fi startup methods are not available on every device. Only install modules and scripts you trust.

Requirements

  • 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: Samsung devices that ship the FOTA agent (com.sdet.fotaagent). For SMTShell on older One UI, use the Custom command system start.
  • Start on boot: Supported start methods only.

See the wiki for setup and troubleshooting guidance.

Privacy

  • 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.

Translations

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

Support the project

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.

Developer guide

API

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.

Build

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.

Contributing

  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.

Credits

  • 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.

License

Licensed under Apache License 2.0.

Star History

Close

How Shizuku is used

Can run typed shell commands, browse restricted files, install apps and manage permissions, network, WiFi, display and power 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 manager app uses Shizuku to act as the shell user, running commands and reaching system services the app itself cannot reach.

  • Run shell commands: type any command in the in app terminal and it runs as shell with working directory and saved variables kept between commands.
  • Browse restricted files: open folders the app cannot see itself, such as shared Android/data and Android/obb, with listing, reading, copying, moving, renaming, deleting, zipping and unzipping done through privileged file access and shell commands.
  • Install packages: install APK and split package files with chosen flags for replace, downgrade and grant all, applied with the pm install shell command through the privileged file service.
  • Manage app permissions: view and change runtime and development permissions through the permission service, verified with shell commands.
  • Control app operations: view and change background run, notifications, clipboard, camera, microphone and similar switches with cmd appops shell commands.
  • Manage battery behavior: view and change standby bucket with am commands, and check battery exemption with dumpsys deviceidle and cmd deviceidle commands.
  • Filter app network: check and change whether an app is blocked with cmd connectivity shell commands and the connectivity interface reached as shell.
  • Manage app state: force stop, clear data, suspend, disable, uninstall and restore apps with am and pm shell commands.
  • Manage WiFi networks: view saved networks, show saved passwords, connect, forget and re add networks with the WiFi service reached as shell and cmd wifi shell commands.
  • Change display settings: apply a chosen resolution, density and refresh rate with the wm size, wm density, settings and cmd uimode shell commands.
  • Control power options: reboot, reboot to recovery or bootloader, shut down and turn the screen off with svc power and key event shell commands.
  • Inspect device status: show battery, usage history, CPU, display and kernel status with dumpsys battery, dumpsys batterystats, dumpsys cpuinfo, dumpsys display and cat /proc/version shell commands.
  • Launch activities: send broadcasts, start activities and press the assistant key through am broadcast, am start and input keyevent shell commands.

Android APIs or commands used

  • ParcelFileDescriptor.open
  • java.io.File.listFiles
  • java.io.File.mkdirs
  • java.io.File.renameTo
  • java.io.File.delete
  • android.content.pm.IPackageManager.getInstalledPackages
  • android.content.pm.IPackageManager.getPackageInfo
  • android.permission.IPermissionManager.grantRuntimePermission
  • android.permission.IPermissionManager.revokeRuntimePermission
  • android.permission.IPermissionManager.checkPermission
  • android.os.IUserManager.getUsers
  • android.net.IConnectivityManager.getFirewallChainEnabled
  • android.net.IConnectivityManager.setFirewallChainEnabled
  • android.net.IConnectivityManager.getUidFirewallRule
  • android.net.IConnectivityManager.setUidFirewallRule
  • android.net.IConnectivityManager.updateMeteredNetworkDenyList
  • android.net.wifi.IWifiManager.getPrivilegedConfiguredNetworks
  • sh -c
  • pm install
  • pm grant
  • pm revoke
  • pm uninstall
  • pm install-existing
  • pm clear
  • pm list packages
  • cmd appops set
  • cmd appops get
  • cmd appops query-op
  • am get-standby-bucket
  • am set-standby-bucket
  • am force-stop
  • am broadcast
  • am start
  • dumpsys battery
  • dumpsys batterystats
  • dumpsys cpuinfo
  • dumpsys display
  • dumpsys deviceidle whitelist
  • cmd deviceidle whitelist
  • cmd connectivity get-chain3-enabled
  • cmd connectivity set-chain3-enabled
  • cmd connectivity get-package-networking-enabled
  • cmd connectivity set-package-networking-enabled
  • cmd wifi list-networks
  • cmd wifi status
  • cmd wifi connect-network
  • cmd wifi forget-network
  • cmd wifi add-network
  • cmd uimode night
  • wm size
  • wm density
  • svc power reboot
  • svc power shutdown
  • input keyevent
  • settings get
  • settings put
  • unzip -v
  • cat /proc/version
  • logcat -d

Notable details

Some installs can use the normal package installer without Shizuku. Private app data under data/data stays unreachable even as shell, so the file browser reports the platform refusal.

Close

Changelog

What's new for version 14.0.36-next

Features

  • settings: add palette style selection
  • settings: add custom hex accent color
  • settings: add amoled background, accent and contrast options

Fixes

  • i18n: drop empty translation files before merging
  • home: center debugging button icon and label together
  • start: run intent starts expedited and replace stale attempts
  • home: center debugging button labels
  • apps: revoke temporary access with permanent grants
  • apps: show one-time grants in app list
  • settings: include shell bookmarks in backups
  • shell: avoid stale selection crash
  • shell: avoid crash when copying long output
  • start: handle redacted wireless debugging on Android 17
docs, CI and chores (4 changes)

Documentation

  • readme: clarify Samsung system UID start

CI

  • add fixed-name latest APK asset
  • scan release APK with VirusTotal

Chores

  • i18n: new translations from Crowdin

Full Changelog: https://github.com/rushiranpise/Shizuku-Next/compare/v14.0.35-next...v14.0.36-next

VirusTotal

Scan report

0 malicious, 0 suspicious, 65 undetected

Close

Permissions

23 permissions requested

  • android.permission.RECEIVE_BOOT_COMPLETED
  • android.permission.FOREGROUND_SERVICE
  • android.permission.SCHEDULE_EXACT_ALARM
  • android.permission.INTERNET
  • android.permission.USE_LOOPBACK_INTERFACE
  • android.permission.ACCESS_LOCAL_NETWORK
  • android.permission.NEARBY_WIFI_DEVICES
  • android.permission.CHANGE_WIFI_MULTICAST_STATE
  • android.permission.POST_NOTIFICATIONS
  • android.permission.USE_BIOMETRIC
  • android.permission.USE_FINGERPRINT
  • android.permission.PACKAGE_USAGE_STATS
  • android.permission.DUMP
  • android.permission.ACCESS_NETWORK_STATE
  • android.permission.REQUEST_IGNORE_BATTERY_OPTIMIZATIONS
  • android.permission.FOREGROUND_SERVICE_SPECIAL_USE
  • android.permission.CHANGE_WIFI_STATE
  • android.permission.REQUEST_DELETE_PACKAGES
  • android.permission.REQUEST_INSTALL_PACKAGES
  • android.permission.UPDATE_PACKAGES_WITHOUT_USER_ACTION
  • android.permission.WRITE_SECURE_SETTINGS
  • moe.shizuku.manager.permission.MANAGER
  • android.permission.WAKE_LOCK
Close