Troubleshooting

Magisk troubleshooting

Search for your symptom or paste the error message, try the first fix, and follow the link for the full steps. Most problems come from a bad module, the wrong image being patched, or, since v31.1, root that was never granted ahead of time in the Superuser tab.

Last updated 8 sourcesHow we check pages

Find your symptom

Type part of the error message or what you see. Matching answers open with the likely cause and the first fix to try. Error messages are quoted as the Magisk app and its scripts show them.

Bootloop right after installing a module

Likely cause: the module is incompatible with your phone or Android version.

First fix: let the phone fail to boot twice; Magisk then starts in Safe Mode with all modules disabled. With USB debugging on, adb wait-for-device shell magisk --remove-modules removes every module and reboots. Full steps

Won't boot right after flashing the patched image

Likely cause: the image is from a different build, was patched on another phone, or went to the wrong partition (boot instead of init_boot).

First fix: flash the stock image from the same firmware back to the same partition with fastboot (not on Samsung). Full steps

All modules are suddenly disabled and Zygisk is off

Likely cause: Magisk's automatic Safe Mode. After two boots in a row that don't finish, Magisk disables every module and Zygisk on the next boot so the phone can start.

First fix: remove the module that broke booting (usually the last one installed or updated), re-enable the others, and turn Zygisk back on. How Safe Mode works

Magisk app shows "Not Installed" or "Installed: N/A"

Likely cause: the patched image isn't running (wrong image, build or partition), or, up to v30.7, a leftover hidden Magisk "stub" app conflicts with the full app.

First fix: run adb shell magisk -c. If it prints a version, remove any hidden copy of the app (named "Settings" by default). If not, re-check what you patched. Full steps

An app can't get root / no root prompt appears

Likely cause: since v31.1 there are no prompts: apps must be granted root ahead of time. On v30.7 and older, a saved "deny", or Automatic response set to Deny.

First fix: open the Superuser tab. On v31.1 tap + (Grant Superuser) and tick the app. Full steps · how su works

A module manager or root app lost root after updating Magisk

Likely cause: v31.1 removed root pop-ups; apps no longer ask, they must already be allowed.

First fix: open the Magisk app's Superuser tab and grant the app. Full steps

adb shell su: Permission denied

Likely cause: the Shell has no root grant. Since v31.1 it must be granted ahead of time; on v30.7 and older the Superuser access setting may be "Apps only" or "Disabled".

First fix: v31.1: Superuser tab → + → tick Shell (search "adb"). v30.7: set Superuser access to "Apps and ADB". Full steps

The Magisk app disappeared after updating to v31.1

Likely cause: v31.1 no longer reinstalls the Magisk app automatically when it is missing, and it removed app hiding.

First fix: nothing is broken: root and modules keep working without the app. Install the APK again from the download page when you need to change settings.

"Requires additional setup" appears after flashing

Likely cause: expected once after installing by patching an image. Magisk's install guide says to accept the prompt and let it reboot.

First fix: accept it. If it comes back after every reboot, reinstall Magisk from the app's Install button.

"Abnormal state": a "su" binary not from Magisk has been detected

Likely cause: another root solution, or a leftover from one, is on the phone.

First fix: remove the other root solution (or flash stock firmware), then reinstall Magisk. Only one root solution can be installed at a time. Magisk vs KernelSU

"Unsupported Magisk version"

Likely cause: the installed Magisk is older than the app supports (v22.0 for the v30.7 and v31.1 apps), so the app acts as if Magisk were missing.

First fix: update Magisk itself by patching and flashing a new image. How to update

Patching fails: "Boot image patched by unsupported programs"

Likely cause: the image you selected was already modified by another tool, such as another root solution or a custom kernel installer.

First fix: patch the untouched image from the official firmware for your exact build. Magisk's script says: "Please restore back to stock boot image". Patching guide

Patching fails: "Unable to unpack boot image"

Likely cause: the file isn't a boot image Magisk can read: the wrong image (such as vbmeta.img), a damaged download, or, on v30.7, a whole firmware zip instead of the extracted image.

First fix: extract init_boot.img or boot.img from the firmware for your build. The v31.x app can also take an OTA zip, payload.bin or factory image zip directly. Patching guide

Module install fails: "This zip is not a Magisk module!"

Likely cause: the installer can't find module.prop at the top level of the zip. Often the zip contains a folder that contains the module, or you downloaded GitHub's "Source code" zip instead of the release zip.

First fix: download the module's release zip, or re-zip from inside the module folder. Module zip layout

"Module suspended because Zygisk isn't enabled"

Likely cause: the module is a Zygisk module and Zygisk is off, possibly switched off by Magisk's Safe Mode.

First fix: Magisk settings → turn on Zygisk → reboot. If it turns itself off again, a module is crashing at boot. Enabling Zygisk

"Zygisk module not loaded due to incompatibility"

Likely cause: the module's native library doesn't fit your phone, for example no build for your CPU architecture. Magisk marks it with zygisk/unloaded.

First fix: install an updated release of the module, or ask its developer. Why it happens

Zygisk is on in settings but the Home screen shows No / Disabled

Likely cause: you haven't rebooted, another Zygisk (Zygisk Next, ReZygisk, NeoZygisk) is installed, or zygote crashed repeatedly and Magisk rolled Zygisk back for that boot.

First fix: reboot once. Use only one Zygisk implementation. If it stays off, disable Zygisk modules one by one. About Zygisk

Banking or other app says the phone is rooted

Likely cause: the app's own root detection, or a failing Play Integrity verdict.

First fix: turn on Zygisk, add the app to the DenyList with Enforce DenyList on, and get the Magisk app out of sight. Then check whether the app needs a verdict a rooted phone can't get. Full steps

Play Integrity fails / Wallet won't add cards

Likely cause: on Android 13 and newer, DEVICE integrity requires hardware proof of a locked bootloader, and Google says Wallet doesn't support rooted or unlocked phones.

First fix: read what is achievable first. Play Integrity and root

Lost root after a system update

Likely cause: the update replaced the patched image.

First fix: patch the new firmware's image and flash it. Next time on A/B phones, use Install to Inactive Slot (After OTA) before rebooting. Full steps

Uninstall says "Stock backup doesn't exist!"

Likely cause: Magisk keeps a stock backup only when it patched the partition on the phone itself. After a manual fastboot flash there usually is none.

First fix: flash the stock image for your current build with fastboot instead. Uninstall guide

Hidden Magisk app has a blank icon

Likely cause: expected: the hidden "stub" app contains no icon resources. (App hiding exists up to v30.7; v31.1 removed it.)

First fix: open it and accept the offer to create a home-screen shortcut, which has the correct icon.

Samsung: “Secure Check Fail: (VBMETA)” or “Only official released binaries are allowed”

Likely cause: the bootloader is locked, KnoxGuard is still Prenormal, or the phone runs One UI 8 or later, which can't be unlocked.

First fix: flash the complete stock firmware to boot again, then check the One UI version and Download mode values. Samsung errors

OEM unlocking is greyed out or missing

Likely cause: the phone is carrier-locked or hasn't checked in online yet, or (Samsung) it runs One UI 8 or later, or it is a US or Canadian Samsung model.

First fix: connect to the internet, wait and restart. If it stays greyed out, this phone may not be unlockable. Check your brand

Motorola: “(bootloader) Preflash validation failed”

Likely cause: a known Magisk issue on some Motorola phones, reopened in September 2026.

First fix: check the Magisk issue for the current workaround before retrying. Motorola errors

Prevent the worst case

  • Keep USB debugging on, with your computer approved, so magisk --remove-modules works even when the phone won't boot.
  • Keep a copy of the stock firmware for the build you are running, so you can restore the original image.
  • Install or update one module at a time and reboot in between, so you know which one to blame.
  • Before a system update, follow the update guide instead of letting the update install on its own.

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