Install and start Shizuku¶
Shizuku lets apps you approve perform supported Android debugging tasks. Root is not required. For Android Auto installation, start the service and authorize KingInstaller before installing the patched APK.
Choose an implementation¶
| Option | When to use it |
|---|---|
| Shizuku-Next | The default for these guides and the KingInstaller workflow. |
| Porter | An alternative with its own setup guide. Shizuku-only clients need its compatibility companion. |
| ShizukuPlus | An advanced option for clients that specifically require Plus features. Follow that build’s compatibility instructions. |
Keep an existing working setup. When switching, follow the chosen project’s replacement instructions. Next and the original Shizuku use different signing keys. Porter’s Shizuku compatibility companion cannot coexist with another Shizuku provider; use its guided migration before removing anything.
Download the release APK from Assets, not a source-code archive, and install it on your phone.
Start on Android 11 or newer¶
These steps require a usable Wireless debugging setting and usually Wi-Fi.
- Enable Developer options, usually by tapping Build number repeatedly under About phone.
- Open Developer options → Wireless debugging and authorize the network if asked.
- Open Shizuku-Next and choose its wireless pairing flow. Allow permissions needed for pairing.
- In Android’s wireless-debugging settings, choose Pair device with pairing code. Keep the dialog open and follow Next’s pairing instructions.
- Return to Next and tap Start. Wait until it reports that the service is running.
- Open KingInstaller or another client, enable its Shizuku option and approve that app’s access request.
Start with a computer¶
For Android 10 or older, or when wireless debugging is unavailable, install Android SDK Platform-Tools, enable USB debugging, connect the phone and approve the computer.
Check the connection:
adb devices
Open the installed provider’s computer-start instructions and run the exact command it displays. With multiple devices, add -s DEVICE_SERIAL immediately after adb.
After restarting the device¶
Check that the service is running before using a client that needs it. You may need to start it again. If a client cannot connect, check its permission and reopen it after switching providers.