How to Start Shizuku, and Get It Running Again
Three ways to start Shizuku (root, wireless debugging on Android 11+, or a computer), what to redo after a reboot, and fixes for when it won't start or keeps stopping.
Shizuku gives other apps the same system access that ADB has, so they can do things that normally need a computer: install apps with extra options, change secure settings, manage per-app network access. Shizuku itself is only the bridge. You start it once, then apps that support it ask for permission to use it.
Get Shizuku from Google Play, from its GitHub releases page, or from this site, where the APK is checked against IzzyOnDroid’s signed index. All three are the same app from the same developer. The rest of this guide follows the project’s own manual.
Pick your method
| Method | Works on | Needs | After a reboot |
|---|---|---|---|
| Root | Any rooted device | Root | Can start on its own |
| Wireless debugging | Android 11 and later | Nothing else | Start it again |
| Computer (ADB) | Android 7.0 and later; the only non-root way on Android 10 and earlier | A computer and a USB cable | Start it again |
The manual is explicit that the two non-root methods don’t survive a reboot. That is a limit of Android, not a bug in Shizuku. One exception came in Shizuku 13.6.0: its release notes add “auto start without root on Android13+ when connected to a trusted WLAN”. In the code, if Shizuku was last running without root, it switches wireless debugging back on at boot and starts itself. That only works on a Wi-Fi network the phone already trusts for wireless debugging, most likely one where you ticked Always allow on this network. The setting that controls it is labelled Start on boot (root), but it covers this case too.
Start with root
On a rooted device, open Shizuku and start it directly. If it doesn’t start by itself after a reboot, the manual’s fix is to allow Shizuku to run in the background (battery or background restrictions on many phones stop it).
Start with wireless debugging (Android 11 and later)
No computer needed. You pair once, then start it after each reboot, unless it starts itself on a trusted Wi-Fi network (see above).
Turn on the switches:
- Enable Developer options. On most phones: Settings › About phone, tap Build number several times until you see a message that you are a developer. The exact place differs by manufacturer.
- In Developer options, turn on USB debugging.
- Open Wireless debugging and turn it on. Wireless debugging works over a Wi-Fi network, as Android’s adb documentation describes it, so connect to Wi-Fi first. Without Wi-Fi, the root method is the one that works.
Pair (only the first time):
- In Shizuku, start the pairing process. It shows a notification.
- In Developer options › Wireless debugging, tap Pair device with pairing code.
- Type the code into the field in Shizuku’s notification.
Start: go back to Shizuku and start it. If it doesn’t start, turn Wireless debugging off and on again, then retry.
On GrapheneOS, the manual notes that Settings › Security › Secure app spawning may need to be turned off.
Start from a computer (any version, needed on Android 10 and earlier)
- Download Google’s SDK Platform Tools for your computer and extract it.
- Open a terminal in that folder and run
adb. If you see a long help text, it works. (In PowerShell, macOS or Linux, type./adbinstead ofadb.) - On the phone, enable Developer options and USB debugging, then connect the cable.
- Run
adb devices. Accept the Allow USB debugging prompt on the phone (tick Always allow), then runadb devicesagain. You should see your device listed. - Open Shizuku on the phone, find the computer (ADB) section and tap View command. Copy that command to the computer, paste it into the terminal and run it. In Shizuku 13.6.0 it looks like this, with a different folder name on every phone:
adb shell /data/app/~~…==/moe.shizuku.privileged.api-…==/lib/arm64/libshizuku.so
Shizuku should now show as running.
The old command no longer works. Guides, including Shizuku’s own website, still give adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh. That was for versions 11.2.0 to 13.5.4; 13.6.0 removed the start.sh script, and its release notes say “Update the start command”. The new path changes when Shizuku is updated, so copy it again after an update. If you start Shizuku from a script, the release notes suggest copying the file to a fixed place such as /data/local/tmp/shizuku and running it from there.
When it won’t start or keeps stopping
These fixes come from the manual’s FAQ, which notes that many manufacturers change Android in ways that interfere with Shizuku.
“Searching for pairing service” never finishes. Allow Shizuku to run in the background. Pairing needs local network access, and many phones cut network access for apps as soon as they aren’t on screen.
Pairing fails as soon as you tap “Enter pairing code” (Xiaomi, POCO). Change the notification style to Android in Settings › Notifications › Notification shade.
“Please go through the pairing step first.” Shizuku shows this when the connection fails with an SSL error, which means the phone isn’t paired with Shizuku, or the pairing was lost. Pair again as above.
“Can’t connect to wireless debugging service.” Wireless debugging is off, or the phone changed networks: Shizuku’s own hint is that “Wireless debugging” is automatically disabled when the network changes. Turn it on again on the same Wi-Fi and retry.
“Unable to generate key for wireless debugging.” The message continues: “This may be because KeyStore mechanism of this device is broken.” Starting from a computer avoids that step.
“please try to stop existing Shizuku from app first” when you run the command on a computer: a Shizuku server is already running. Stop it in the app, then run the command again.
It starts, but apps say the permission is limited.
- Xiaomi, POCO (MIUI): also enable USB debugging (Security settings) in Developer options. It is a separate switch from USB debugging.
- OPPO, OnePlus (ColorOS): disable Permission monitoring in Developer options.
- Meizu (Flyme): disable Flyme payment protection in Developer options.
Shizuku stops at random.
- Let Shizuku run in the background.
- Don’t turn off USB debugging or Developer options while you use it.
- In Developer options, set the USB mode to charge only: Default USB configuration › No data transfer on Android 9 and later (Select USB configuration › Charge only on Android 8).
- On Android 11 and later, turn on Disable adb authorization timeout.
- Huawei (EMUI): enable Allow ADB debugging options in “Charge only” mode.
- Xiaomi (MIUI): don’t run the scan in the Security app. It turns Developer options off.
- Sony: ignore the dialog that appears when you connect USB, because answering it changes the USB mode.
- Samsung with One UI 8: in the issue tracker’s summary for this problem (#1426), Default USB configuration set to Charging only or Debugging only is listed as what worked; that comes from users, not from the manual.
Apps can’t see Shizuku on Android 17. Since June 2026, users report that 13.6.0 shows no authorised apps on Android 17 and new authorisations fail, while apps authorised before the update keep working (issue #2180, still open). There is no official fix yet; 13.6.0, from May 2025, is the latest release.
What to use it for
Once Shizuku is running, the apps below can use it. Each one asks for Shizuku permission the first time. See the Shizuku apps list for a side-by-side comparison, including which ones also work without Shizuku.
Apps in this guide
-
Shizuku Lets other apps use Android’s system APIs with the same rights as ADB. You start it with wireless debugging on Android 11+, from a computer with ADB, or with root.Download -
Install with Options Installs APKs with options normally reserved for adb: test-only apps, downgrades, split APKs and Android 14’s blocked old apps.Download -
FireWall Blocks Blocks Wi-Fi or mobile data per app without root, through Shizuku or a local VPN.Download -
Private DNS Quick Toggle A Quick Settings tile that switches Android’s Private DNS between providers in one tap.Download -
Volume Manager Gives each app its own volume, from its own screen or a replacement volume popup.Download -
OwnDroid Puts Android’s device-owner and work-profile controls on your own phone: block uninstalls, disable the camera, manage users and more.Download
Sources
- Shizuku user manual (setup and FAQ) checked Sep 27, 2026
- Android Debug Bridge: wireless debugging requirements checked Sep 27, 2026
- Shizuku releases on GitHub (13.6.0: new start command, automatic start on a trusted Wi-Fi network) checked Oct 11, 2026
- Shizuku 13.6.0 source: the start command (Starter.kt) checked Oct 11, 2026
- Shizuku 13.6.0 source: starting at boot (BootCompleteReceiver.kt) checked Oct 11, 2026
- Shizuku issue #2180: Android 17 checked Oct 11, 2026