Internal Details

File Structure

Paths in “sbin tmpfs overlay”

One of Magisk’s breakthrough designs is sbin tmpfs overlay. It is required to support system-as-root devices, and also is the key to hiding Magisk from detection. All Magisk binaries, applets, mirrors, and other trivial stuffs are all located in the tmpfs mounted on /sbin. MagiskHide can just simply unmount /sbin and the bind mounts to hide all modifications easily.

# Binaries like magisk, magiskinit, and all symlinks to
# applets are directly stored in /sbin, so they
# are all in PATH for apps and shell to access them

# Magisk internal stuffs

# Magisk BusyBox path

# /data/adb/modules will be bind mounted here

# The configuration used in last installation

# Partition mirrors.
# There would be system, vendor, data, and possibly product
# in this directory, each is the mirror to the name of the partition

# Root directory patch files
# On system-as-root devices, / is not writable.
# All patched files are stored here and bind mounted at boot.

# The patched sepolicy file on system-as-root devices.
# This is required as /sepolicy does not exist
# on those devices and / is not writable.

Paths in /data

Some binaries and files should be stored on non-volatile storages in /data. In order to prevent detection, everything has to be stored somewhere safe and undetectable in /data. The folder /data/adb was chosen because of the following advantages:


# Folder storing general post-fs-data scripts

# Folder storing general late_start service scripts

# Magisk modules

# Magisk modules that are pending for upgrade
# Module files are not safe to be modified when mounted
# Modules installed in Magisk Manager will be stored here
# and will be merged into $SECURE_DIR/modules in the next reboot

# Database storing settings and root permissions

# All magisk related binaries, containing busybox,
# scripts, and magisk binaries. Used in supporting
# module installation, addon.d, Magisk Manager etc.
# This folder will be bind mounted to $BINMIRROR

Magisk Booting Process


magiskinit will replace init as the first program to run.


This triggers on post-fs-data when /data is properly decrypted (if required) and mounted. The daemon magiskd will be launched, post-fs-data scripts are executed, and module files are magic mounted.


Later in the booting process, the class late_start will be triggered, and Magisk “service” mode will be started. In this mode, service scripts are executed, and it will try to install Magisk Manager if it doesn’t exist.


Usually, system properties are designed to only be updated by init and read-only to non-root processes. With root you can change properties by sending requests to property_service (hosted by init) using commands such as setprop, but changing read-only props (props that start with ro. like and deleting properties are still prohibited.

resetprop is implemented by distilling out the source code related to system properties from AOSP and patched to allow direct modification to property area, or prop_area, bypassing the need to go through property_service. Since we are bypassing property_service, there are a few caveats:

Magic Mount

I will skip the details in the actual implementation and algorithm of Magic Mount, but you can always directly dive into the source code if interested. (bootstages.cpp)

Even though the mounting logic is pretty complicated, the final result of Magic Mount is actually pretty simple. For each module, the folder $MODPATH/system will be recursively merged into the real /system; that is: existing files in the real system will be replaced by the one in modules’ system, and new files in modules’ system will be added to the real system.

There is one additional trick you can use: if you place an empty file named .replace in any of the folders in a module’s system, instead of merging the contents, that folder will directly replace the one in the real system. This will be very handy in some cases, for example swapping out a system app.

If you want to replace files in /vendor or /product, please place them under $MODPATH/system/vendor or $MODPATH/system/product. Magisk will transparently handle both cases, whether vendor or product is a separate partition or not.


Here are some tidbits in Magisk but unable to be categorized into any sections: