shevery

Shevery

English | Русский | Қазақша | Qazaqşa (Latın) | Português | Español | العربية | 简体中文 | 日本語

Fork status

[!IMPORTANT] Side-by-Side Installation Supported: Thanks to its independent package ID (com.hamondev.shevery) and isolated permission namespace, you can now install Shevery directly alongside other Shizuku implementations without uninstalling them first. For legacy apps that explicitly check for moe.shizuku.privileged.api, you can optionally enable Compatibility Stubs in Settings once original Shizuku is removed. Upstream project reference: https://github.com/RikkaApps/Shizuku

Fork additions

• Jetpack Compose manager UI with Material 3 Expressive components, motion, switches, and rounded icon treatment.
• Device Owner Management & Integration: Full Device Owner management (app delegation scopes, ownership transfer, DPM-assisted ADB) inspired by and compatible with Dhizuku.
• Biometric Security & Protection: Master switch to require biometric or device PIN/pattern/password authentication with configurable timeouts and granular action protection.
• Dhizuku Experimental Support: Dedicated Device-Owner bridging system available inside Laboratory features.
• Better shell/adb based “Comput” feature with Gemini Explaination, Macros and Commandium AI Command create.
• Android 16/17 target work with current 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-gated service.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.
• Module Catalog with direct install.

Documentation

• Shevery Wiki
• Comput AI Agent guide
• Device Owner & Profile Owner guide
• Stealth Edition & Compatibility Stubs
• Accessibility Manager, USB Debugging Hiding & Network Firewall
• Tasker & MacroDroid Automation Guide
• Intents Reference
• ADB Modules guide
• ADB Modules API reference
• ADB Modules publishing & GitHub Catalog guide
• Shizuku Connectors API
• Android 17 Compatibility
• ErrorProtect Watchdog & Starter Recovery

Background

When developing apps that requires root, the most common method is to run some commands in the su shell. For example, there is an app that uses the pm enable/disable command to enable/disable components.

This method has very big disadvantages:

1. Extremely slow (Multiple process creation)
2. Needs to process texts (Super unreliable)
3. The possibility is limited to available commands
4. Even if ADB has sufficient permissions, the app requires root privileges to run

Shizuku uses a completely different way. See detailed description below.

User guide & Download

https://shizuku.rikka.app/

Screenshots

Click to open Screenshots

Main Screen	Comput Console
ADB Modules	Settings

How does Shevery works?

First, we need to talk about how app use system APIs. For example, if the app wants to get installed apps, we all know we should use PackageManager#getInstalledPackages(). This is actually an interprocess communication (IPC) process of the app process and system server process, just the Android framework did the inner works for us.

Android uses binder to do this type of IPC. Binder allows the server-side to learn the uid and pid of the client-side, so that the system server can check if the app has the permission to do the operation.

Usually, if there is a “manager” (e.g., PackageManager) for apps to use, there should be a “service” (e.g., PackageManagerService) in the system server process. We can simply think if the app holds the binder of the “service”, it can communicate with the “service”. The app process will receive binders of system services on start.

Shizuku guides users to run a process, Shizuku server, with root or ADB first. When the app starts, the binder to Shizuku server will also be sent to the app.

The most important feature Shevery provides is something like be a middle man to receive requests from the app, sent them to the system server, and send back the results. You can see the transactRemote method in rikka.shizuku.server.ShizukuService class, and moe.shizuku.api.ShizukuBinderWrapper class for the detail.

So, we reached our goal, to use system APIs with higher permission. And to the app, it is almost identical to the use of system APIs directly.

Developer guide

API & sample

https://github.com/RikkaApps/Shizuku-API

Migrating from pre-v11

Existing applications still works, of course.

https://github.com/RikkaApps/Shizuku-API#migration-guide-for-existing-applications-use-shizuku-pre-v11

Attention

1. ADB permissions are limited

   ADB has limited permissions and different on various system versions. You can see permissions granted to ADB here.

   Before calling the API, you can use ShizukuService#getUid to check if Shizuku is running user ADB, or use ShizukuService#checkPermission to check if the server has sufficient permissions.

2. Hidden API limitation from Android 9

   As of Android 9, the usage of the hidden APIs is limited for normal apps. Please use other methods (such as https://github.com/LSPosed/AndroidHiddenApiBypass).

3. Android 8.0 & ADB

   At present, the way Shizuku service gets the app process is to combine IActivityManager#registerProcessObserver and IActivityManager#registerUidObserver (26+) to ensure that the app process will be sent when the app starts. However, on API 26, ADB lacks permissions to use registerUidObserver, so if you need to use Shizuku in a process that might not be started by an Activity, it is recommended to trigger the send binder by starting a transparent activity.

4. Direct use of transactRemote requires attention

   • The API may be different under different Android versions, please be sure to check it carefully. Also, the android.app.IActivityManager has the aidl form in API 26 and later, and android.app.IActivityManager$Stub exists only on API 26.

   • SystemServiceHelper.getTransactionCode may not get the correct transaction code, such as android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages does not exist on API 25 and there is android.content.pm.IPackageManager$Stub.TRANSACTION_getInstalledPackages_47 (this situation has been dealt with, but it is not excluded that there may be other circumstances). This problem is not encountered with the ShizukuBinderWrapper method.

Developing Shizuku itself

Build

• Clone with git clone --recurse-submodules
• Run gradle task :manager:assembleDebug or :manager:assembleRelease

The :manager:assembleDebug task generates a debuggable server. You can attach a debugger to shizuku_server to debug the server. Be aware that, in Android Studio, “Run/Debug configurations” - “Always install with package manager” should be checked, so that the server will use the latest code.

CI builds

Every push to main, dev and nightly, and every pull request, runs the Build Android APK workflow. Each run always uploads both artifacts — there is no debug-or-release choice:

The release artifact is signature-verified with apksigner in every run. Fork pull requests build both variants with a generated keystore, so untrusted code never touches the release signing key.

How “Start(via Dhizuku)” works?

• First, you need to start Shevery by PC/OTG or Wireless Debugging.
• Next, start Dhizuku.
  • Do not start Shevery via Dhizuku first.

License

All code files in this project are licensed under Apache 2.0

Credits

• kerneldroid - for parts of App UI, Catalog Modules System and Android 17 support.
• iamr0s/Dhizuku - for Dhizuku Device Owner architecture and API concepts integrated into Shevery.
• RikkaApps/Shizuku - for Shizuku API and main sources.
• Landon Moran - for Dhizuku, TCP and etc. fixes.
• DP-Hridayan - for parts of “Comput” UI.
• protonpony/Shizuku-Keeper - for “Autostart on boot via Wireless Debugging”.

And…

Now, you can publish your ADB module! Follow this steps:

• Create your module.
• Create GH Repository for this module.
• Add topic “shevery-modules”
• Add sources and Release with module.

For fresh builds/CI of Shevery, go to Actions — every run attaches both a shevery-debug and a shevery-release APK artifact. But this APKs are unstable and can contain some bugs. If you found bugs on latest CI, you can report about it in Issues.