Troubleshooting

Magisk installed but root not working

Two different problems look alike: Magisk isn't running at all, or Magisk runs but a particular app (or adb) doesn't get root. One command tells them apart. Then follow the branch that matches, including the big change in v31.1, now the stable release: there are no root pop-ups any more.

Last updated 7 sourcesHow we check pages

Step 1: is Magisk actually running?

What "not running" looks like in v31.1

  1. The Magisk card is the one that matters. Not Installed in red means the app can't see a running Magisk. When root works it shows a version, such as 31.1 (31100).
  2. The App card's Installed line is only the version of the app itself. It shows a number even when Magisk isn't running, so it proves nothing about root.
The two cards are easy to confuse. Illustration drawn from the Magisk v31.1 app's source code: same labels and layout, simplified look. Not a screenshot; v30.7 looks different.

The Magisk app's Home screen can show Not Installed (v31.1) or Installed: N/A (v30.7) even when Magisk is running. Ask Magisk itself instead. From a computer (or a terminal app on the phone, without adb shell):

Check the installed and running versions
$adb shell magisk -c # installed binaries: a line ending in :MAGISK:R and the version code in brackets $adb shell magisk -v # version of the running Magisk daemon

Neither command needs root. If they print a version, Magisk is running and the problem is the app or a root permission. If the shell answers that magisk is not found, Magisk isn't running. The tree below takes it from there.

Find the cause

Does adb shell magisk -c print a version?
Based on Magisk's FAQ, app strings and su source code at v30.7 and v31.1, checked October 26, 2026.

Magisk isn't running: check what you patched

  • Wrong image: phones that launched with Android 13 or later normally need init_boot.img, not boot.img. If your firmware has init_boot.img, patch and flash that. Some devices need vendor_boot.img. See patching a boot image.
  • Wrong build: the image must come from the exact firmware build installed. A mismatched image may boot without Magisk, or not boot at all.
  • Wrong slot: on A/B phones, fastboot flash init_boot writes to the current slot. If you switched slots in between, the patched image may sit on the inactive one.
  • No boot ramdisk (Ramdisk: No): Magisk is installed in recovery and is active only when you boot through the recovery key combination and release the keys at the splash screen. A normal power-on starts Android without Magisk. See Magisk in recovery.
  • A system update replaced the image: after an OTA, the new build runs a stock image. Patch the new build's image, and use the update guide next time.
  • Additional setup: after flashing, open the app and accept Requires additional setup. It reboots once. If the prompt returns after every reboot, reinstall Magisk with the app's Install button.

The app says Not Installed or N/A, but magisk -c works

Magisk's FAQ (up to v30.7) names the usual cause: you once used Hide the Magisk app, and the hidden "stub" app is still installed next to a newly installed full app. The two conflict, and the full app can't see root.

  1. Open Settings → Apps and look for the hidden app. By default it is named Settings, or it has the name you chose when hiding. There may be more than one.
  2. Uninstall every hidden copy, then open the full Magisk app again.
  3. If it still shows N/A, uninstall the full app and install the version that matches the installed Magisk (the version magisk -c printed) from the download page.
  4. Check second spaces, work profiles, "parallel apps" tools and other users for extra copies of the Magisk app, hidden or not.

Other messages you may see instead:

  • "Unsupported Magisk version": the installed Magisk is older than the app supports (v22.0 for the v30.7 and v31.1 apps). The app then acts as if Magisk were not installed. Update Magisk by patching and flashing again.
  • "Abnormal state: A "su" binary not from Magisk has been detected": another root solution (or a leftover from one, such as KernelSU or an old SuperSU) is present. Remove it and reinstall Magisk.
  • "Running this app as a system app isn't supported" or "Magisk is installed to external storage": install the APK as a normal app on internal storage.

From v31.1, app hiding and the stub app no longer exist, so the stub conflict can't happen there. v31.1 also stops reinstalling the Magisk app automatically. If the app is gone, root keeps working; install the APK again when you need to change settings.

v31.1: no more root pop-ups

Magisk v31.1, the current stable release, removed the root request prompt. According to its changelog, superuser access is now "explicitly granted ahead of time in the Superuser tab". In the source, any app or shell without a saved rule is denied silently, so a root app that worked by prompting on v30.7 just fails after the upgrade.

Granting root in v31.1

  1. Open the Superuser tab in the bottom bar.
  2. Tap + (its label is Grant Superuser) and pick the apps that should have root. For adb shell su, pick Shell.
There are no pop-ups in v31.1: an app gets root only after you add it here. Illustration drawn from the Magisk v31.1 app's source code: same labels and layout, simplified look. Not a screenshot; v30.7 looks different.
  1. Open the Magisk app's Superuser tab.
  2. Tap the + button (Grant Superuser) and tick the apps that should have root. Turn on Show system apps to find system apps.
  3. For adb shell su, grant the Shell entry; it is always listed, and searching "adb" finds it. The release notes say the prompt flow didn't work for callers like adb shell on Headless System User Mode devices, which is one reason it was removed.
  4. Open the root app again. No reboot is needed.

If you are still on v30.7 or older, prompts work as before; see the next section.

v30.7 and older: an app can't get root

  • A saved "deny": open the Superuser tab and make sure the app isn't set to denied. A prompt that timed out or was dismissed counts as a deny, and that decision may have been saved.
  • Automatic response: in Magisk's settings, Automatic response set to Deny rejects every new request without a prompt. Set it to Prompt.
  • Superuser access: the Superuser access setting can be Disabled, Apps only, ADB only or Apps and ADB. If adb shell su fails but apps work, it is probably Apps only.
  • Work profile or second user: with Multiuser mode set to Device owner only, apps in other users and profiles are always denied.
  • The prompt never appears: it is shown by the Magisk app. If the app is missing or broken, reinstall it from the download page.

Both versions: the DenyList and su

  • An app on the DenyList with Enforce DenyList on has Magisk's changes reverted in its processes, so it can't use root. Don't put root apps on the DenyList; it is meant for apps that should not see Magisk. See Zygisk and the DenyList.
  • Magisk's su is served by Magisk's daemon. If magisk -c works but su fails, check that magisk -v also answers (the daemon is up), reboot once, then test from adb shell with su -c id. It should print uid=0(root).
  • If the phone loops after you change something here, see fixing a Magisk bootloop.

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