Where Does KernelSU Store Modules and Data?
Where KernelSU keeps its modules, boot backups and helper tools on Android, and how paths compare to Magisk.
Last updated
KernelSU keeps modules in the same shared tree as Magisk with identical folder layouts. Metadata, mount flags and scripts follow the same names, which makes module zips install on either system. Its own tools diverge into a separate ksu tree beside the shared one.
BusyBox, boot backups and logs live in that private tree rather than Magisk paths. Everything here needs a root shell to browse. Copy module folders across systems freely but keep tool paths per manager. Profile rules share the same trees, so module plus tool backups stay paired.
Where KernelSU stores this, by platform
/data/adb/modules
Shared module tree identical to Magisk layout. Private tools, backups and logs sit in the sibling ksu tree. Needs a root shell to browse.
Frequently asked questions
Can I migrate Magisk modules to KernelSU by copying folders?
Both keep installed modules in the same shared modules tree, so module folders transfer directly. BusyBox and boot backups live in different homes per system. Check the ksu tree beside the shared one for KernelSU only files.
Where does KernelSU stash the stock boot backup?
Open the manager and use direct install, which backs up the stock image beside the ksu tree automatically. Restoring picks the backup matching the recorded hash. Keep the backup until an OTA cycle proves the new image stable.
Notice an outdated path? Let us know.