System Architecture
AI Translation Notice
This documentation page is an English summary synced from the canonical Chinese architecture guide. See Chinese Architecture for full prose.
MuMu ReSukiSU isolates untrusted offline image preparation from privileged host disk writes and Android early-boot execution across three explicit domains.
Interactive Architecture Diagram
Three-Domain Isolation
- Offline Build & Whole-Disk Audit (Linux / Cross-Platform Python)
- Validates
2,465,270,784-byte VDI topology and partition hashes viasrc/mumu_resukisu/images.py. - Builds
kernelsu.ko(235 undefined symbols,vermagic=6.1.90-perf+) anddriver-initfrom pinned upstream Git commits, patches fixedBootFsslots (norc=1 preinit=0), edits ext4 system daemon metadata (e2fsck-verified), removes the vendor overwrite step, and audits every VDI 1 MiB COW block before emittingcandidate.json.
- Validates
- Windows Single-Instance Controller (
binding.py&controller.py)- Binds explicit instance directory,
MuMuManager.exe, andsystem-diff.vdipaths after verifying shut-down state and built-in root disablement. - Requires three consecutive shutdown confirmations, locks the private diff disk exclusively (
CreateFileWshare=0 + non-blockingmsvcrt.locking), savesrollback.vdi+ atomic journal under.state/<sha256>/, writes candidate blocks, and verifies read-back.
- Binds explicit instance directory,
- Android 15 Early-Boot Runtime (
native/loader/&native/prestage/)driver-initruns only in early PID-1 context (exits64otherwise) to loadkernelsu.koand execute/resukisu-migrate-prestagebeforeswitch_root.stock-migration.hseparates/datastock daemon preservation (3753880-byte/system/xbin/dusk) from system-VDI rollback: exact stock binaries are backed up durably on/dataand verified before exposingksud; unknown executables halt cleanly.