KPM/KPM-Next is NOT supported. This is an upstream issue where proper kallsyms support was removed. To prevent users from bricking their devices (getting stuck at the OEM logo), CONFIG_KALLSYMS has been explicitly disabled.
Required Firmware (Alioth)
You MUST flash this specific firmware before installing the kernel.
Failure to do so will result in a boot loop at the OEM logo.
Note: If switching back to other kernels (e.g., MagicTime), ensure you restore the original or kernel-specific firmware to avoid sensor issues or boot loops.
SUSFS & Uname Spoofing
Uname spoofing is supported and functional.
Recommendation: Use it only if necessary. If you do use it, spoof version 5.10.xx or higher.
Warning: Spoofing below 5.10.xx overrides the built-in RE404 spoofs, which will cause boot loops on Android 16 ROMs.
Glitches
You might encounter the issue of the touch being unresponsive for few seconds after boot into system or recovery. This issue persists across the bpf upstream of E404
Meta Modules & Mounting
I recommend using Magic Mount rs metamodule along with kernel as it leaves mountinfo mostly clean & detection free due to susfs.
Mountify or any tmpfs based ofs mounting is supported.