MAKOSU MANAGER / GKI 2.0

MakoSU

Reliable kernel-root management packed into one clean manager.

MakoSU keeps permissions, KMI matching, SuSFS, KPM, modules, and kernel flashing consistent under a single release contract.

Explore features →Read the docs View source

Android 8.0+: Min manager version
5.10 - 6.12: Official KMI support
7 KMI groups: Bundled per release
3 ABIs: Rust userspace components

MANAGER CAPABILITIES

Surgical daily operations with clear failure stories

Features are organised around real maintenance workflows: identify the device, pick the right module, manage hiding configs, and preserve recovery paths when flashing fails.

Smart KMI matching

Reads Android KMI markers and loads the corresponding LKM instead of forcing based on kernel version alone.

Centralized SuSFS

Unified management of hidden paths, mappings, stat, vname, logs, and auto-start configs.

Recoverable module updates

New modules are staged and validated first; on failure, the manager restores the previous config and module state.

Signature identity contract

The package name, APK Release certificate, and expected kernel hash are maintained as a single release contract.

KPM and flashing tools

Provides KPM, module management, boot image patching, and kernel flashing.

Material + Miuix

Two management UIs, theme switching, and fallback icons — balancing information density with operational efficiency.

RELEASE KMI SET

Seven formal KMI variants — no fuzzy matching

Current releases target GKI 2.0. Vendor ABI, symbols, config, and KMI markers must still match; 5.4 / GKI 1.0 is not included in the formal release set.

View release contract →

Android 125.10android12-5.10

Android 135.10android13-5.10

Android 135.15android13-5.15

Android 145.15android14-5.15

Android 146.1android14-6.1

Android 156.6android15-6.6

Android 166.12android16-6.12

SUSFS USERSPACE

Configuration reliability over feature stacking

MakoSU applies transactional handling to the SuSFS userspace chain, reducing jank, concurrent overwrites, and unrecoverable states during boot.

Atomic save

Temporary files, fsync, and atomic replacement reduce the risk of config corruption after abnormal interruption.

Strict parsing

Rejects truncated data, duplicate fields, oversized content, and trailing garbage.

Single read

The manager reads the entire config in one root call, reducing UI lag caused by repeated command invocations.

Failure rollback

Auto-start modules and backup recovery attempt to return to the last known good state on failure.

RELEASE CONTRACT

The manager and kernel must agree on one identity

Changing the package name or certificate is not a cosmetic UI change. Any identity field change requires rebuilding the KMI and re-verifying the APK v2 certificate.

Application ID: com.makosu.manager
Certificate DER size: 0x0549
Release KMI variants: 7
Userspace ABI: arm64 / armv7 / x86_64

RECOVERY FIRST

Prepare a recovery path before flashing

A mismatched kernel, LKM, signing identity, or target partition can make a device unbootable. Keep the original image and a working Fastboot or Recovery path.

View source →