Compatible Magisk-mirroring provides older, “pure” Magisk module installers with a mounted view of original system files on environments where the traditional Magisk mirror is absent or incompatible. It is primarily a developer-compatibility layer for install scripts that must read an untouched file before generating an overlay replacement.
Original Files for Legacy Installers
The helper supplies the mirror semantics expected by installers written before Magisk 28 and by modules ported to alternative root managers.
Clean Source View
Lets an installer read a system file before another module's overlay obscures the underlying version.
Early-Boot Helper
Installs a small script under /data/adb/post-fs-data.d to prepare compatible mirroring for later installs and execution.
Script Compatibility
Targets installers whose customize.sh expects magisk --path and the traditional .magisk/mirror layout.
The Problem It Solves
Consider an audio module that reads /vendor/etc/audio_policy_configuration.xml, changes a few entries, and writes the result into its own overlay. During an update, the visible vendor file may already be the copy mounted by that module or another one. Building from that modified input can duplicate changes or silently produce the wrong result.
Traditional Magisk installers use $(magisk --path)/.magisk/mirror for the unmodified source. Magisk 28.0/28.1 and several Magisk variants, KernelSU, and APatch do not always expose the same interface, which is the compatibility gap this module addresses.
KernelSU and APatch Script Changes
KernelSU and APatch do not permit a replacement command named magisk in their root-framework binary directories. The compatibility module therefore installs ksu-magisk.
A legacy module being adapted for those managers must call ksu-magisk --path, or define alias magisk='ksu-magisk' early in each relevant shell script. Installing this helper alone does not rewrite third-party ZIP files automatically.