Troubleshooting

Fixes by symptom

Find what you see, open it, and follow the fix. Each one links to where people solved it.

On this page

A. Pairing: the code notification never appears or can't be used

1The pairing notification never shows up

What you see

You tap Pairing in Shizuku, but no notification appears.

Why

Shizuku needs permission to post notifications. Without it, there is nothing to type the code into.

Fix

Open Settings, then Apps, then Shizuku, then Notifications.
Allow notifications.
Tap Pairing in Shizuku again.

Sources: Issue 997

2The notification has no Enter pairing code button

What you see

Shizuku's notification is there, but you can't find a button to type into.

Why

On some skins, such as MIUI and HyperOS, the button only shows when the notification is expanded.

Fix

Tap the small down arrow on Shizuku's notification to expand it.
Tap Enter pairing code.
If the pairing in progress notification stays after it worked, check Wireless debugging, then Paired devices. An entry called shizuku means you are paired.

Sources: Issue 205

3The notification still won't work

What you see

You expanded it, allowed notifications, and it still fails.

Why

The phone hides the notification or cuts Shizuku's network when it is in the background.

Fix

Open split screen with Shizuku on one half and Settings, then Developer options, then Wireless debugging on the other.
Tap Pair device with pairing code.
Shizuku stays in front, so the phone can't cut its network or hide its notification. Enter the code in the notification.

Sources: Issue 222, Issue 1044

4Android 15 or newer: the notification shows only a short status

What you see

The notification won't accept the code.

Why

Android 15 hides interactive notification content while any app records or shares the screen.

Fix

Stop the screen recording or sharing app.
Or turn on Developer options, then Disable screen share protections.
Pair again.

Sources: Issue 868

5The keyboard vanishes while you type the code

What you see

The reply box loses focus, or the keyboard closes. Seen on Pixel 8 and other phones.

Why

Overlay or gesture apps (such as Edge Gestures) and apps that draw over other apps trigger it.

Fix

Pause those apps, then try again.
Or use split screen with a messaging app: open its text box to bring up the keyboard, then tap back into Shizuku's reply field.
Or, from a computer, run this while the reply field has focus, with your six digits:
```
adb shell input text 123456
```

Sources: Issue 459, Issue 358

6Shizuku crashes in a loop when you tap the code field

What you see

Seen on some realme phones and custom systems.

Why

One reporter traced it to the screen's smallest width setting.

Fix

Open Developer options, then Smallest width.
Set it above about 400.
Reported by one user. Try it if nothing else works.

Sources: Issue 1788

7There is no notification shade or no reply box at all

What you see

Meta Quest, kiosk devices and some TVs.

Why

Pairing needs a notification you can reply to. These devices can't do that.

Fix

Use the computer way instead.

Sources: Discussion 581, Issue 2114, Issue 368

B. Pairing: stuck on Searching for pairing service, or pairing fails

8Stuck on Searching for pairing service

What you see

Shizuku's notification keeps searching.

Why

The search needs local network access, and many brands cut it as soon as an app goes to the background.

Fix

Let Shizuku run in the background with no battery limits. Your brand's steps.
Pair in split screen (fix 3).
Turn Wireless debugging off and on again, then pair.

Sources: Shizuku setup guide, Issue 222

9The phone blocked Shizuku's network

What you see

Pairing fails every time, often on MIUI.

Why

The phone has taken away Shizuku's permission to use the network.

Fix

Open Shizuku's app permissions in Settings.
Allow network access again.
Pair again.

Sources: Issue 178

10Android 15: the search never ends, though the code is showing

What you see

The code is on screen, but Shizuku never finds it.

Why

Users found the code field only appears after the search is stopped.

Fix

Tap Stop searching on Shizuku's notification.
The code field appears. Type the code.

Sources: Issue 955, Issue 938

11The pairing service is never detected

What you see

Seen on iQOO Neo6 and others.

Why

Unknown. One reporter fixed it after two days of trying.

Fix

Reset network settings: Settings, then System, then Reset, then Reset Wi-Fi, mobile and Bluetooth. This forgets saved Wi-Fi networks.
Reported by one user. Try it if nothing else works.

Sources: Issue 1045

12Your Wi-Fi blocks the search

What you see

Pairing never finds anything on this network.

Why

The pairing service is announced over the local network (mDNS). Guest, office, hotel and isolated networks often block that.

Fix

Use your home network, or a hotspot from another phone.
Advanced check: a service browser app shows whether _adb-tls-pairing services are visible.

Sources: Android adb docs, Issue 222

13A VPN or proxy app breaks it

What you see

Permission denied, or nothing happens.

Why

A VPN or proxy can route Shizuku's connection to the phone itself the wrong way. The report is old, but the advice holds.

Fix

Pause VPN, proxy, firewall and ad blocking apps.
Pair and start.
Turn them back on afterwards.

Sources: Issue 18

14Pairing broke after Samsung Smart Switch

What you see

Nothing fixes pairing on a phone set up with Smart Switch (Galaxy S25).

Why

Settings moved over from the old phone broke it.

Fix

Only a factory reset without restoring settings fixed it. Reported by one user. A true last resort: back up first.

Sources: Issue 1072

15Pairing failed shows, but Shizuku runs

What you see

A Pairing failed notification, while Shizuku says it is running.

Why

An old Shizuku bug, fixed in later builds.

Fix

If Shizuku says it is running, ignore the notification.
Update Shizuku.

Sources: Issue 380, Issue 457

C. Starting: paired, but Start fails

16SSLProtocolException CERTIFICATE_UNKNOWN when you tap Start

What you see

An error with those words.

Why

Pairing was skipped, or the pairing record was lost.

Fix

Pair again first. Pairing steps.
Then tap Start.

Sources: Issue 638, Issue 205, Issue 333

17Paired, but Start does nothing or fails

What you see

You tap Start and nothing changes.

Why

The official manual gives this as the first thing to try.

Fix

Turn Wireless debugging off.
Turn it on again.
Tap Start in Shizuku.

Sources: Shizuku setup guide, Issue 300, Issue 260, Issue 222

18Stuck on Waiting for service

What you see

After shizuku_starter exit with 0, it waits forever.

Why

On some phones starting takes a while, or the phone's own restrictions block it.

Fix

Wait a little.
Turn Wireless debugging off and on.
Restart the phone and start again.
On OnePlus or OPPO, also turn on the system optimization switch. How.

Sources: Issue 260, Issue 312, Issue 353

19fatal: can't kill, please stop existing Shizuku first

What you see

An error that names a process number.

Why

An old Shizuku server is still running.

Fix

Stop Shizuku from the app, or reinstall it.
Start again.

Sources: Issue 467

20Shizuku shows the old version running

What you see

For example 13.5 running after you installed 13.6.

Why

The old server process is still alive.

Fix

Stop Shizuku, or restart the phone.
Start again so the new one loads.

Sources: Issue 1253, Issue 2012, Issue 1602

21Only Start with root is shown

What you see

No wireless or computer options.

Why

Shizuku runs in a second user or second space.

Fix

Switch to the main user of the phone and use Shizuku there.

Sources: Issue 559

22Shizuku's Developer options button says to turn them on, though they are on

What you see

The button in Shizuku doesn't take you there.

Why

That button is only a shortcut into Settings, and on some Samsung A series phones it does nothing.

Fix

Open Settings yourself and go to Wireless debugging.

Sources: Issue 867, Issue 531

23Emulators, app cloners and Xposed

What you see

Shizuku won't start in BlueStacks or a cloned app.

Why

Shizuku doesn't support emulators or app cloners. Xposed modules that hook Shizuku can also break the start.

Fix

Use Shizuku on the real phone, not cloned.
Turn off Xposed modules that touch Shizuku.

Sources: Issue 218, Issue 467, Issue 251

D. Shizuku stops by itself

24It stops at random

What you see

Shizuku stopped and you don't know why.

Why

The real work is done by a background process that adb starts. Anything that restarts adb, or turns debugging off, stops it.

Fix

Let Shizuku run in the background with no battery limits.
Never turn off USB debugging or Developer options.
Set Default USB configuration, then No data transfer. On Android 8: Select USB configuration, then Charge only.
On Android 11 or newer, turn on Disable adb authorization timeout.

Sources: Shizuku setup guide, Issue 147, Issue 234

25It stops when the screen turns off or locks

What you see

Fine while you use it, gone after the screen locks.

Why

Seen again and again on Moto g31, a Lenovo tablet, Redmi, POCO and OnePlus.

Fix

Set Developer options, then Default USB configuration to No data transfer or charge only.
Samsung One UI 8: pick Charging phone only. Details.

Sources: Issue 277, Issue 293, Issue 1426

26It stops every morning, or after some hours

What you see

Shizuku ran yesterday, not today.

Why

Android drops the adb authorization after a while of not being used.

Fix

Turn on Developer options, then Disable adb authorization timeout.

Sources: Issue 294, Issue 230

27It stops when you unplug the computer cable

What you see

Gone as soon as the cable is out.

Why

USB debugging is switched off on unplug, or the USB mode changes.

Fix

Keep USB debugging on.
Set the USB default to No data transfer in Developer options, not in the pop up you get when you plug in.

Sources: Issue 267, Issue 379, Issue 304

28It stops when you change the USB mode or plug into a computer for file transfer

What you see

Gone after you switch USB modes.

Why

Each of these restarts adb, and everything adb started stops with it. This is expected and can't be avoided.

Fix

Start Shizuku again afterwards.
Avoid changing the USB mode while you need it.

Sources: Issue 311, Issue 366

29It stops when you leave Wi-Fi or turn Wi-Fi off

What you see

Gone after Wi-Fi drops.

Why

If both USB debugging and Wireless debugging are off, adb exits and takes Shizuku with it.

Fix

Keep USB debugging on. With it on, users report Shizuku survives Wi-Fi off and even airplane mode.
Some brands still stop it. Start it again.

Sources: Discussion 1000, Issue 544, Discussion 225, Issue 1011

30Changing from Wi-Fi to mobile data

What you see

Does it stop Shizuku?

Why

On a stock Pixel, no, if you follow fix 24. But once Shizuku has stopped, nothing can restart it without you.

Fix

Follow fix 24.
If it stopped, start it again.

Sources: Discussion 322

31Battery settings for the app aren't enough

What you see

You set Shizuku to unrestricted, and it still stops.

Why

The server is a separate adb process. App battery settings mostly help pairing and searching. adb restarts and the phone's process killers are the real causes.

Fix

Follow fix 24, especially the USB default and keeping debugging on.
Your brand's keep running steps.

Sources: Issue 234, Issue 237

32Plugging into Android Auto over USB stops it

What you see

Gone after you connect to the car.

Why

Android Auto changes the USB mode, as in fix 28.

Fix

Start Shizuku again after you leave the car.

Sources: Issue 1478

E. After a restart, and starting by itself

33Everything is gone after a restart

What you see

Shizuku says it isn't running.

Why

That is by design for the wireless and computer ways. Pairing is kept.

Fix

Wireless: open Shizuku and tap Start. No pairing.
Computer: plug in and run the start command again.

Sources: Shizuku setup guide, Issue 641

34Start by itself without root (13.6.0 or newer)

What you see

You want it to start on its own.

Why

Release 13.6.0 added a start without root on Android 13 or newer, on a trusted Wi-Fi network.

Fix

Update to 13.6.0 or newer.
Turn on the switch labelled Start on boot (root). It works without root too.
Allow your Wi-Fi network for good in the Wireless debugging prompt.

Sources: Release 13.6.0, Issue 1149, Issue 1254

35Community recipes for starting by itself

What you see

MacroDroid, Tasker, Termux.

Why

People have built macros and scripts that turn on wireless debugging and connect to the phone's own adb. They are unofficial.

Fix

For advanced users only. Read the discussions linked below.

Sources: Discussion 461, Discussion 462

36Root mode doesn't start on boot

What you see

Rooted, but not running after a restart.

Why

Shizuku has to receive the boot signal, which needs background permission.

Fix

Let Shizuku run in the background.
Rooted users can use Sui instead. KernelSU builds have been unreliable.

Sources: Shizuku setup guide, Issue 206, Issue 266

F. Starting from a computer

37The basic flow

What you see

You want the computer steps in short.

Why

Starting with a computer works on any Android version.

Fix

Install Google's SDK Platform Tools.
Turn on USB debugging.
Run adb devices and accept Allow USB debugging with Always allow.
Paste the start command from Shizuku's View command.
PowerShell, macOS and Linux need ./adb. Full steps.

Sources: Shizuku setup guide, Android adb docs

38start.sh: No such file or directory, or the command does nothing

What you see

An error about start.sh, usually with a command from a website.

Why

Shizuku 13.6.0 changed the start command. It now points to a file inside Shizuku's install folder, and that path is different on every phone.

Fix

In Shizuku, open Start by connecting to a computer.
Tap View command and copy it.
Paste it into the terminal.

Sources: Release 13.6.0, Issue 1206, Issue 547, Issue 531, Issue 2076

39Permission denied when you run the command

What you see

The terminal says permission denied.

Why

The path is wrong (adb can't read /data/user/0/...), or old files are left over.

Fix

Copy the command from View command again.
Still failing? One user cleared Shizuku's folder /sdcard/Android/data/moe.shizuku.privileged.api/files and force stopped the app, and it worked.

Sources: Issue 24, Issue 40

40adb devices shows no permissions (Linux)

What you see

In charge only mode.

Why

The computer can't use the phone in that USB mode.

Fix

Try another computer, or another USB mode just for the start. Reported by one user.

Sources: Issue 267

41No computer, and Android 10 or older

What you see

No Wireless debugging and no computer.

Why

Older Android has no wireless pairing on the phone.

Fix

Run adb from a second Android phone over an OTG cable, for example with a terminal app. For advanced users.

Sources: Discussion 431

42Wireless debugging needs Wi-Fi, but you have none

What you see

No Wi-Fi network around.

Why

Wireless debugging needs a Wi-Fi connection, but not internet.

Fix

Turn on a hotspot on another phone, or use a cheap access point, just to start.
Your phone's own hotspot usually doesn't work.

Sources: Issue 183, Discussion 611, Android adb docs

G. Profiles, users and spaces

43It won't run in a work profile, Secure Folder, second space or Private Space

What you see

Shizuku fails or shows only root.

Why

adb can't reach files in other users, so Shizuku must live in the main user.

Fix

Install and start Shizuku in the main user of the phone.

Sources: Issue 393, Issue 559, Issue 837

H. Running, but apps can't do what they promise

44adb power is limited, not root

What you see

An app says it can't do something, even with Shizuku running.

Why

adb can't do everything. For example it can't list /data. What adb may do differs between Android versions.

Fix

Check the app's own notes on what works without root.

Sources: Issue 413, Shizuku README

45Android/data access fails or is partial (Android 14 to 16)

What you see

A file manager can't open app folders.

Why

It often depends on the app using Shizuku.

Fix

Update that app. Users fixed Android 16 Android/data access by updating their file manager (ZArchiver 1.0.10).

Sources: Issue 426, Issue 1574

46rish or Termux fails on Android 14 or newer

What you see

rish won't run.

Why

Android 14 refuses to run code files that can be written to.

Fix

Copy the rish files into the terminal app's own data folder, not /sdcard.

Sources: Release 13.5.2, Issue 331

47Shizuku 13.6.0 runs, but some apps do nothing (MediaTek and Transsion)

What you see

Shizuku says running, but an app's feature fails.

Why

A MediaTek framework change crashes the user services some apps start in 13.6.0.

Fix

Users went back to Shizuku 13.5.4, or used a community fork, until a fix ships.
To go back, uninstall Shizuku and install 13.5.4 from GitHub releases.

Sources: Issue 1198, Issue 1171, Issue 2048, Issue 1252

48Shizuku 13.6.0 hangs after Wi-Fi changes (some Android 16 builds)

What you see

It stops responding after Wi-Fi goes off and on.

Why

A 13.6.0 problem on some Android 16 builds.

Fix

Reporters went back to 13.5.4.
They turned off Google Play auto update for Shizuku only.

Sources: Issue 2443, Issue 2436, Issue 2448

I. Where to get it

49The Google Play build is old

What you see

Play offers an older version than GitHub.

Why

For a long time Play served 13.5.4, which breaks on Android 16 QPR1 and One UI 8.5.

Fix

Uninstall the Play version first, because the two are signed differently.
Install the latest release from GitHub (or IzzyOnDroid).

Sources: Issue 1431, Issue 1125, Issue 2133, Discussion 2249

50Is Shizuku still maintained?

What you see

Few updates, and a busy issue list.

Why

Upstream work has slowed, and the issue tracker is full of spam. Several community forks carry fixes, for example for Android 17.

Fix

This guide covers the official app and doesn't recommend a fork.

Sources: Discussion 1132, Issue 1965, Issue 2330

Problems on one brand only

Each phone page lists the problems seen on that brand, with sources.