# How to start Shizuku?
# Start with root
For rooted devices, just start directly.
# Problems caused by manufacturers (non-root mode)
# 1. MIUI (Xiaomi) 💩
You need to enable "USB debugging (Security options)" in "Developer options".
For MIUI 11 and above, you must grant permission to user apps in Shizuku. This is because the custom permission is broken by MIUI, see Shizuku #45 (opens new window) and android-in-china/Compatibility #16 (opens new window).
Also, DO NOT use the scan feature in MIUI's "Security" app, since it will disable "Developer options".
# 2. ColorOS (OPPO) & OxygenOS (OnePlus) 💩
You need to disable "Permission monitoring" in "Developer options".
# 3. Flyme (Meizu) 💩
You need to disable "Flyme payment protection" in "Developer options".
# 4. EMUI (Huawei) 💩
You need to enable "Allow ADB debugging options in 'Charge only' mode" in "Developer options".
# 5. OriginOS (vivo) 💩
The system setting of OriginOS does not support split-screen, you need to enable "Force activities to be resizable" in "Developer options". See Shizuku #106 (opens new window).
# Start via wireless debugging
Android 11 and above support wireless debugging, so you can launch Shizuku directly on your device.
The following applies to Shizuku 12.4.0+.
- After the device restarts, you need to enable the "Wireless debugging" option again and restart Shizuku.
- "Wireless debugging" cannot be enabled when there is no WiFi connection (Shizuku already started is not affected).
- Do not disable "Developer options" or "USB debugging".
# Enable Wireless debugging
- Search the web for how to enable "Developer options" for your device model
- Enable "Developer options" and "USB Debugging"
- Enter "Wireless debugging"
- Enable "Wireless debugging"
This step only needs to be performed once.
- Notifications are disabled by default on some systems, you need to allow Shizuku to send notifications in the system's notification settings
- Start pairing in Shizuku
- Enable Wireless debugging
- Tap "Pair device with pairing code" in "Wireless debugging"
- Enter pairing code in Shizuku's notificaiton
# Start Shizuku
If it does not start, try disabling and enabling wireless debugging.
# Start by connecting to a computer
If your device is running Android 11 or above, please launch it via wireless debugging. It does not requires a computer.
For non rooted devices, you need to start Shizuku with
adb is not difficult, please read the tutorial below.
- After the device restarts, it needs to be connected to the computer again.
- Shizuku may stop randomly on some customized systems. Read the last part to see the solution.
# 1. What is
Android Debug Bridge (
adb) is a versatile command-line tool that lets you communicate with a device. The adb command facilitates a variety of device actions, such as installing and debugging apps, and it provides access to a Unix shell that you Can use to run a variety of commands on a device.
See Android Developer (opens new window) for more information.
# 2. Install
Download "SDK Platform Tools" provided by Google and extract it to any folder
Open the folder, right click to select
- Windows 10: Open PowerShell windows here (hold down Shift to show this option)
- Windows 7: Open command window here (hold down Shift to show this option)
- Mac or Linux: Open Terminal
adb, if success, you can see a long list of content instead of the prompt not finding adb.
- Please do not close this window. The "terminal" mentioned later refers to this window (if you closed the window, please go back to step 2)
- If you use PowerShell or Linux/Mac, all
adbshould be replaced with
# 3. Setting
adb you first need to turn on USB debugging on your device, usually by following these steps:
Open system Settings and go to About.
Click "Build number" quickly for several times, you can see a message similar to "You are a developer".
At this point, you should able to find "Developer Options" in Settings, enable "USB Debugging".
Connect the device to the computer and type
adb devicesin the terminal.
At this time, the dialog "Allow debugging" will appear on the device, check "Always allow" and confirm.
adb devicesagain in the terminal. If there is no problem, you will see something like the following.
List of devices attached XXX device
The steps for enabling Developer Options on different devices may vary, please search for yourself.
# 4. Start Shizuku
Copy the command and paste into the terminal. If there is no problem, you will see that Shizuku has started successfully in Shizuku app.
Command for Shizuku v11.2.0+
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh
Command for Shizuku v4.0.0+
adb shell sh /data/user/0/moe.shizuku.privileged.api/start.sh
adb shell sh /data/user_de/0/moe.shizuku.privileged.api/start.sh
Command for Shizuku v3.x
adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/files/start.sh
# 5. Shizuku randomly stops?
First, do not disable "USB debugging" and "Developer options".
Then you need to ensure that the USB usage mode does not change while connecting to computer. The common practice is to change the USB usage mode to "Charge only" in the "Developer options". The option on Android 8 is "Select USB configuration" - "Charge only", on Android 9+ the option is "Default USB configuration" - "No data transfer".
On some devices, such as Samsung, this may not work. At this point you need to check the notification that appears after connecting the computer to see the current USB usage mode, and change the mode in "Developer options" to that mode.
If that doesn't work, you can try to open the network adb (using the command
adb tcpip 5555) and then start Shizuku.
In addition, if your system shows a dialog like "Allow accessing files" after connecting USB, please just ignore it, because the USB usage mode will change from that.
# Sony devices
Don't click the dialog shows after connecting the USB.