SukiSU kernel for Redmi K40 Pro+ (haydn)

The Redmi K40 Pro+ / K40 Pro / Mi 11i / Mi 11X Pro (codenamed haydn) is a fine device that Xiaomi eventually left on the last official stable HyperOS. That last build is the perfect place to run a custom kernel with proper root, so I built one and documented the result.

What this is

A flashable AGNi v7.16 based kernel for the official last stable HyperOS OS1.0.15.0.UKKCNXM (Android 14), with KernelSU (SukiSU-Ultra) and susfs integrated at the kernel level. It is packaged with AnyKernel3, so flashing it does not touch /data and you can roll back cleanly.

Key details

• Kernel: 5.4.302-AGNi_haydn_HyperOS_v7.16-stable-qgki
• Build: clang 18.0.1 / LLD 18.0.1, reproducible via build_ksu_kernel.sh
• Root: SukiSU-Ultra v3.1.8 (KernelSU driver, version 13250, uapi compatible v3)
• Hiding: susfs v1.5.10 (magic mount, kstat hide, uname/cmdline spoof)
• Hook style: kprobe (GKI 1.0), SELinux stays enforcing
• Modules: supported through ksud
• Touch, fingerprint, camera, WiFi, sensors and audio all keep the original behaviour

Compatibility

haydn / haydnin / M2012K11C — tested on the China HyperOS OS1.0.15.0.UKKCNXM build. Requires an unlocked bootloader.

What ships in the package

• AGNi_kernel-haydn-v7.16-HyperOS-KSU.zip — AnyKernel3 flash pack (kernel + dtb + dtbo)
• SukiSU_v3.1.8_13250-release.apk — the matching SukiSU manager
• build_ksu_kernel.sh + agni_haydn_v7.16.config — source build script and config
• checksums.txt — SHA-256 for all files

How to flash

1. Boot the Android 14 TWRP for haydn via fastboot boot twrp-*.img.
2. Back up your boot: dd if=/dev/block/by-name/boot_a of=/tmp/boot_a.img (and boot_b), then adb pull.
3. Push and flash the ZIP: adb push AGNi_kernel-...-KSU.zip /tmp/kernel.zip, then adb shell twrp install /tmp/kernel.zip.
4. Reboot, then install SukiSU_v3.1.8_13250-release.apk. The manager should show "working".

Notes

Keep only one KernelSU-family manager installed — if you previously used the official KernelSU / KSU-Next / another SukiSU manager, uninstall it first, otherwise the kernel responds to whichever it scans first. Also do not upgrade the manager to v4: that generation needs a v4 kernel driver.

To roll back, re-flash your original boot image and you are back to stock. This kernel is provided for the community under GPL.