Troubleshooting

Below is a list of common problems and potential solutions. Before proceeding, please ensure you are using the latest version of the app. If your problem isn't listed or the solutions do not work for you, review the existing GitHub issues to see if your issue was already reported. Otherwise, please submit a GitHub issue or email thedjchidev@gmail.com.

I can't install the Shizuku fork on my device

• If you currently have the original Shizuku installed, you must uninstall it before installing this fork. The apps are signed with different developer keys.

Tip

Once you have installed this fork, you can perform any future updates without uninstalling.

I can't enter the pairing code

• On MIUI (Xiaomi & POCO) devices, switch the notification style (found under Notifications > Notification Shade) to "Android"
• Try enabling the "Legacy pairing" option in Shizuku's settings

I can't start Shizuku manually

• Ensure Shizuku is whitelisted in all firewall, ad-block, and VPN apps. They can restrict network access, which prevents Shizuku from starting.
• Try toggling Wireless Debugging off/on if you are stuck on the searching dialog.
• Ensure Shizuku is paired with wireless debugging. If it's already paired, try un-pairing and re-pairing it. If that still doesn't work, try tapping "Revoke USB debugging authorizations" in Developer Options and re-pair.

Shizuku isn't starting on boot

Note

If needed, follow these instructions to enable USB debugging and set up ADB on your computer so you can run the commands in this section.

• Ensure "Start on boot" is enabled in settings. If it was already enabled, try disabling and re-enabling it.
  • On some devices, there may be an additional per-app "Auto-start" setting which you must also enable.
• Disable battery optimizations for Shizuku.
  • ZTE Devices: Additionally, go to Settings > Battery > Optimize by Scenes > Sleep Mode and toggle ON and OFF again. Due to an OS bug, it shows as disabled by default but is actually enabled and will prevent Shizuku from starting on boot at night.
• Ensure Shizuku is whitelisted in all firewall, ad-block, and VPN apps. They can restrict network access, which prevents Shizuku from starting.
• Try re-granting the WRITE_SECURE_SETTINGS permission (required to toggle USB and Wireless Debugging on boot):
  • adb shell pm grant moe.shizuku.privileged.api android.permission.WRITE_SECURE_SETTINGS
• Try grant the following permissions to ensure Shizuku can run in the background:
  • adb shell cmd appops set moe.shizuku.privileged.api RUN_IN_BACKGROUND allow
  • adb shell cmd appops set moe.shizuku.privileged.api RUN_ANY_IN_BACKGROUND allow

Note

Shizuku can only start on boot if you are on Android 11+. It will also only start once you are connected to a Wi-Fi network, as this is required for the startup process.

The status card says "The permission of ADB is limited"

• On MIUI (Xiaomi & POCO) devices, enable "USB debugging (Security options)" in Developer Options. Note that this is a separate option from "USB debugging."
• On ColorOS (OPPO & OnePlus) devices, disable "Permission monitoring" in Developer Options.
• On Flyme (Meizu) devices, disable "Flyme payment protection" in Developer Options.

Shizuku keeps stopping randomly

• If you are using a Samsung device, try dialing *#0808# in the phone app and selecting MTP + ADB from the menu, then hit OK (even if it was already selected).

• If you are using a non-Samsung device, go to Settings > Developer Options > Default USB configuration and set to "Charging only" or "No data transfer."

• Enable the "Disable adb authorization timeout" option in Developer Options.

• Do not disable USB debugging or Developer Options while Shizuku is running.

• Disable battery optimizations for Shizuku.

• On EMUI (Huawei) devices, enable "Allow ADB debugging options in 'Charge only' mode" in Developer Options.

• On MIUI (Xiaomi & POCO) devices, disable the scan feature in MIUI's "Security" app, since it will disable Developer Options.

• On Sony devices, do not click on the dialog that shows after connecting a USB cable, as it switches the USB mode.

Note

If you use Android Auto and connect with a physical cable, Shizuku will crash. Similarly, switching USB modes will also cause Shizuku to crash. There is no known fix for this behavior. Consider using the watchdog to keep Shizuku alive in these cases.

One of my apps is not working with Shizuku

• Go to "Authorized apps" in Shizuku and toggle the app off/on.

Note

Before reporting a bug about Shizuku not working with a specific application, please make sure that the bug is due to Shizuku itself, and not a faulty implementation of Shizuku in the other app. I cannot control how other apps implement Shizuku's API.

I keep seeing a Toast message that says "This service is only supported on TV devices"

• Some apps (e.g., Tasker, MacroDroid) have an option to "keep accessibility services running." Shizuku must be excluded from these lists.
  • Tasker: go to Preferences > Monitor > Keep Accessibility Running and make sure Shizuku is unchecked
  • MacroDroid: go to Settings > Keep Accessibility Services Running and make sure Shizuku is unchecked