SUSFS LKM x86_64 is ymuuuu's x86_64 port of inforcqb's susfs4ksu-lkm. It loads susfs as a kernel module next to KernelSU Next on x86_64 Android emulator images. You don't need a custom kernel, and nothing replaces the ramdisk. Root the emulator first with KernelSU Next AVD.
What's in the module
- A
susfs_guard_lkm.kofor each of eight KMIs, fromandroid12-5.10toandroid17-6.18. The boot script picks the one matching your kernel release. - The x86_64
susfscommand-line tool, installed to/data/adb/ksu/bin/susfswithsusandksu_susfssymlinks, for manager modules that call the classic CLI. - Userspace talks to it through the reboot-ABI supercall and the
/proc/susfs_*nodes, the same interface as upstream.
What's been tested
On the Android 16 x86_64 emulator (kernel branch android15-6.6): loading at boot, ksud susfs version answering v2.3.0, ksud susfs support answering Supported, sus_path hiding paths from apps while root and shell still see them, the uname spoof, and the kstat, opath and open_redirect tables.
The other seven KMIs are built by CI but haven't been tried on a device yet. The AArch32 compat layer stays arm64-only.
Installation
- In the KernelSU Next manager, go to Modules and install
susfs_lkm_x64.zipfrom storage. Or runksud module install susfs_lkm_x64.zip. - Reboot. The module loads itself on every boot.
- Check it with
ksud susfs version. You should see v2.3.0.
Loading the .ko by hand
The separate susfs_guard_lkm.ko download is for a one-off manual load. Plain insmod won't work, because five of the symbols it needs aren't exported to modules on any GKI kernel. Use this instead:
ksud insmod /path/to/susfs_guard_lkm.koIt hides itself from lsmod on purpose. Look for /sys/module/susfs_guard_lkm to confirm it's loaded.