Compare

Magisk vs Shizuku

These solve different problems. Magisk roots your phone, which requires an unlocked bootloader. Shizuku doesn't root anything: it runs a helper process with ADB (or root) privileges so apps written for it can call system APIs they normally couldn't, on a phone that stays locked.

Last updated 7 sourcesHow we check pages

Short answer

If the app you want supports Shizuku and only needs ADB-level permissions (permission managers, app freezers, debloaters, some backup and automation tools), use Shizuku. You keep a locked bootloader, your warranty status and Play Integrity. If you want modules, Zygisk, changes to system files, or an app that requires real root, you need Magisk and an unlocked bootloader. Check whether your phone can be unlocked with the compatibility checker.

At a glance

MagiskShizuku
Latest releasev31.1 stable (October 25, 2026); v30.7 (Feb 23, 2026) is the last for Android 6.0v13.6.0 (May 25, 2025), which added Android 16 QPR1 support
What you getFull root (su), modules, Zygisk, system changesApps that support Shizuku can call system APIs with ADB-level (or root) permissions
Unlocked bootloader?Required, which usually wipes the phoneNot required; nothing is flashed
SetupPatch and flash a boot image from a computerInstall the app and start it through wireless debugging (Android 11+), ADB from a computer, or root
After a rebootStill rootedMust be started again, unless rooted or auto-started on trusted Wi-Fi (v13.6.0, Android 13+)
UndoUninstall in the Magisk app; relocking the bootloader is a separate stepUninstall the app and turn off Developer options
LicenseGPL-3.0Apache 2.0

What each one lets you do

FeatureMagiskShizuku
Works with a locked bootloaderNoYes
Keeps Play Integrity DEVICE verdictNoUnlocked bootloaderYesPhone is unmodified
Grant or revoke app permissions (pm grant)YesYes
Disable or remove preinstalled apps for your userYesYes
Read or change other apps' private dataYesNo
Change system files (modules)YesNo
Hook into apps (Zygisk, Vector)YesNo
Change read-only system propertiesYesresetpropNo
Works with any app that asks for rootYesNoOnly apps built for Shizuku
Running after a reboot without doing anythingYesPartlyAndroid 13+: auto-start on trusted Wi-Fi
Shizuku started without root has the permissions of the ADB shell, which the Shizuku README says differ between Android versions. ADB commands from Android's adb documentation. Checked October 26, 2026.

How Shizuku works

Apps talk to Android's system services over Binder, and each service checks the caller's permissions. Shizuku starts a server process with ADB or root privileges and gives apps a Binder connection to it. The app sends its request to the Shizuku server, which forwards it to the system service with the server's privileges and passes the result back. Shizuku's README calls the alternative, running shell commands through su, “extremely slow” and “super unreliable”, because it means starting processes and parsing text.

How a Shizuku request travels

  1. 1AppCalls a system API through the Shizuku library
  2. 2Shizuku serverRuns as the ADB shell user, or as root on a rooted phone
  3. 3System serviceChecks the server's permissions, not the app's
  4. 4ResultReturned to the app over Binder
Based on the “How does Shizuku work?” section of the Shizuku README, checked October 26, 2026.

The limit is the shell user's permissions. The README warns that ADB “has limited permissions and different on various system versions”, so an app may offer fewer features under Shizuku than under root, and hidden-API restrictions apply from Android 9. Magisk's su has no such ceiling.

Starting Shizuku

  • Android 11 or later, unrooted: enable Developer options, then in the Shizuku app pair with Wireless debugging using the pairing code (once), and tap Start. No computer is needed. If it won't start, toggle Wireless debugging off and on.
  • Android 10 or earlier, unrooted: enable USB debugging, connect to a computer with Google's platform tools, and run the start command below (the one for Shizuku v11.2.0 and later).
  • Rooted phone: start it directly from the app. It can then start at boot.
Start Shizuku from a computer
$adb shell sh /sdcard/Android/data/moe.shizuku.privileged.api/start.sh

Some manufacturer skins need extra switches, according to Shizuku's guide: on MIUI (Xiaomi, POCO) also enable “USB debugging (Security options)”, on ColorOS turn off “Permission monitoring”, and on GrapheneOS you may need to turn off “Secure app spawning”.

Which do you need?

  • Shizuku is enough when the app supports it and the job fits ADB permissions: granting permissions, freezing or removing preinstalled apps for your user, changing settings the app couldn't otherwise reach. It is also the only choice on phones that can't be unlocked, such as recent US and Canada Samsung models.
  • You need Magisk for anything below the app layer: modules that change system files, Zygisk modules like Vector (formerly LSPosed), editing read-only properties with resetprop, reading other apps' data, or apps that require su.

You don't have to switch from one to the other. Shizuku keeps working after you root, and starting it with root removes the reboot chore. Going the other way, from Magisk to Shizuku only, means uninstalling Magisk; relock the bootloader only after restoring fully stock firmware, or the phone may not boot.

Common questions

Is Shizuku the same as root?

No. Without root, the Shizuku server runs with ADB shell permissions. That is more than a normal app gets, but much less than root: it can't touch other apps' data, system partitions or other processes' memory.

Is Shizuku safe?

Shizuku is open source (Apache 2.0) and published by RikkaApps; download it from the link in its GitHub README or shizuku.rikka.app. The real risk is what you authorize: every app you allow in Shizuku can act with ADB-level permissions while the server runs. Only allow apps you trust, and review the list in the Shizuku app.

Will banking apps work with Shizuku?

Shizuku doesn't unlock the bootloader or modify the system, so it doesn't affect Play Integrity. It does need Developer options and USB or wireless debugging turned on, and Shizuku's own guide tells you to leave them on. If an app objects to those settings, that is the app's own check, not Play Integrity. Rooted phones face a harder problem: see banking apps and root.

Why does Shizuku stop after every reboot?

Its setup guide says a start through wireless debugging or ADB must be repeated after each reboot, because of system limits. Since v13.6.0 it can start itself on Android 13 and later when the phone joins a trusted Wi-Fi network. On a rooted phone it can start at boot; if it doesn't, allow Shizuku to run in the background.

Shizuku keeps stopping on its own. What fixes it?

The setup guide lists: allow Shizuku to run in the background, keep USB debugging and Developer options on, set the default USB mode to charging only, and on Android 11 and later turn on “Disable adb authorization timeout”. Xiaomi phones on MIUI also need “USB debugging (Security options)”, and ColorOS phones need “Permission monitoring” turned off.

Does Shizuku work on Android 16 QPR2 and Android 17?

The latest release, v13.6.0 (May 25, 2025), added Android 16 QPR1 support. There has been no release since, and the release notes don't mention later versions, so check the project's GitHub issues for your Android build before relying on it.

Can I use Shizuku on a phone rooted with Magisk?

Yes. Shizuku can start with root, which also removes the restart-after-reboot chore. Alternatively, RikkaApps' Sui provides the same Shizuku API to apps on a rooted phone; its README says it requires Magisk.

Sources

This page is written from the sources below. If anything here disagrees with them, the upstream source is correct.

Found a mistake or something out of date? Tell us and we will check it against the source and fix the page. Confirmed corrections are listed in the corrections log.

Report a problem with this page