Where Does Magisk Store Modules and Settings?
Where Magisk keeps modules, its settings database and scripts on Android, and how rescue mode works.
Last updated
Magisk keeps all persistent state under one system data tree on Android. Modules install as ID named folders with metadata and scripts inside. The settings plus root permission database sits beside them as one file.
Boot scripts split into early and late directories that run at different stages. Pending upgrades stage in a separate folder until next reboot. Everything here needs a root shell to browse, so file managers without root show nothing. Deny lists share the database file, so one backup covers root rules.
Where Magisk stores this, by platform
/data/adb/modules
System data tree with modules, settings database, scripts and binaries. Needs a root shell to browse. Volatile mirrors live separately per boot.
Frequently asked questions
A Magisk module bootlooped my phone. How do I recover?
Reboot into safe mode or delete the modules tree from a custom recovery shell. The settings database survives while every module unloads. Reinstall modules one by one after booting clean to find the culprit.
Where is the live Magisk tmpfs mount?
Query the tmpfs path command to print the live mount for your setup. Volatile mirrors of modules and config live there per boot and vanish on restart. Persistent state always sits in the adb tree in this post.
Notice an outdated path? Let us know.