• Target: GKI 2.0 devices (kernel 5.10+). WSA, ChromeOS, and container-based Android are supported.
• Architectures: arm64-v8a and x86_64.
• Module mounting: metamodule-based (v3.0+).
• Non-GKI: dropped since v1.0 (last version v0.9.5); the integration guide is archival.
• Notable changes: seccomp+ioctl supercall (v2.0), selinux hide (v3.2.x), optional "jailbreak" mode via Magica (v3.2+).

Resources:

• Download Manager APK
• Official Documentation
• Official Module Repository
• Telegram Channel
• Report Issues

• Kernel support: 4.4–6.6 (non-GKI 4.x–5.4 LTS; GKI 5.10–6.6; 6.6+ experimental).
• Module mounting: built-in Magic Mount + OverlayFS, switchable from settings.
• Features: module backup & restore, auto-updates, bulk install, hide hosts (unmount), SuSFS controls, SU-allowlist backup.
• Architectures: arm64-v8a, armeabi-v7a, x86_64 (same x86_64 panic caveat as upstream).
• Community device list: Unofficially supported devices

Resources:

• Download Manager APK
• Official Website
• Supported Devices
• Telegram Community
• Report Issues

• Kernel support: non-GKI 4.4+; GKI 5.10+; 3.x (3.4–3.18) experimental.
• Module mounting: built-in Magic Mount.
• KPM (Kernel Patch Module) support- run code in kernel space (based on KernelPatch).
• SUSFS management built into the Manager (the kernel still needs SUSFS patches).
• Architectures: arm64-v8a, armeabi-v7a (bare), x86_64 (some).

Resources:

• Download Manager APK
• Official Website
• Installation Guide
• Telegram Group

• Module mounting: metamodule-based.
• Multi-manager: works with the KernelSU, MKSU, RKSU, and SukiSU managers.
• Kernel support: GKI 2.0 (5.10+); 3.4+ with manual build.
• Releases: pre-release/CI builds so far (latest tag v4.2.0-rc1)- check the repository.

Resources:

• Download Manager APK
• Official Website
• Installation Guide
• Telegram Group

Bootloop Recovery

Immediate Steps:

# 1. Enter fastboot mode (Power + Volume Down)
# 2. Connect device to PC
# 3. Flash stock boot image
fastboot flash boot stock_boot.img

# 4. If needed, clear cache
fastboot erase cache

# 5. Reboot
fastboot reboot

Alternative via Recovery:

1. Boot into TWRP/custom recovery
2. Flash stock boot image from recovery
3. Wipe cache and dalvik cache
4. Reboot system

Prevention:

• Always keep stock boot image backup
• Test kernels with temporary boot first: fastboot boot test_boot.img
• Create TWRP backups before major changes
• Keep emergency download mode access available

Module-Related Issues

Safe Mode Boot:

1. Create file /data/adb/modules/.disable_modules before boot
2. This disables all modules for troubleshooting
3. Remove problematic modules
4. Delete the disable file and reboot

Commands:

# Disable all modules
adb shell su -c "touch /data/adb/modules/.disable_modules"
adb reboot

# Remove specific module
adb shell su -c "rm -rf /data/adb/modules/[module_name]"
adb reboot

# View module logs
adb shell su -c "cat /data/adb/modules/[module_name]/install.log"

# Check KernelSU status
cat /proc/version | grep KernelSU
su -c "kernelsu --version"

# Kernel logs
dmesg > /sdcard/dmesg.log
cat /proc/last_kmsg > /sdcard/last_kmsg.log

# KernelSU specific logs
logcat -s "KernelSU" > /sdcard/kernelsu.log
logcat -b all > /sdcard/full_logcat.log

# Module installation logs
cat /data/adb/modules/*/install.log > /sdcard/module_logs.log

# Check SELinux status
getenforce
sestatus

# List loaded modules
ls -la /data/adb/modules/
cat /data/adb/modules/*/module.prop

# Check mount points
mount | grep overlay
mount | grep /system

# Verify root access
su -c "id"
su -c "whoami"

# Check kernel config
zcat /proc/config.gz | grep KSU

# Monitor system resources
top -n 1
free -h
df -h

Samsung Devices

• Knox Triggered: Some Samsung devices trip Knox warranty bit (irreversible)
• Secure Boot: May need to disable secure boot verification in kernel
• Encryption Issues: Some kernels incompatible with Samsung encryption
• OEM Unlock: Ensure OEM unlocking is enabled in Developer Options

OnePlus Devices

• Fastboot Commands: Use fastboot oem unlock for bootloader
• Generic GKI: OnePlus devices generally do not support generic GKI builds - use manufacturer-specific kernels
• Anti-Rollback: Be careful about security patch levels; flashing older kernels can brick devices
• Slot System: A/B partition devices need careful slot management

Xiaomi Devices

• Anti-Rollback: Be careful with MIUI version downgrades (brick risk)
• Bootloader Unlock: Xiaomi requires a waiting period via the Mi Unlock Tool
• MIUI Optimizations: Some MIUI features conflict with KernelSU
• Vendor Mismatch: Ensure kernel matches vendor version

Google Pixel Devices

• Hardware Attestation: Strong Play Integrity enforcement on newer Pixels
• Verified Boot: Orange state warning on boot (normal)
• Titan M Security: Hardware security module affects root hiding
• OTA Updates: Easy to re-root after OTAs with KernelSU

System Slowdown

Diagnosis:

1. Identify problematic modules: Disable modules one by one
2. Check CPU throttling: Monitor thermals and frequency scaling
3. Review I/O performance: OverlayFS overhead on slow storage
4. Analyze system logs: Look for kernel errors or warnings

Commands:

# Monitor CPU usage
top -m 10

# Check I/O stats
iostat -x 1 10

# View thermal zones
cat /sys/class/thermal/thermal_zone*/temp

# Check for errors
dmesg | grep -i error
logcat | grep -i error

Random Reboots

Troubleshooting:

1. Check kernel logs: dmesg and /proc/last_kmsg
2. Monitor memory usage: Look for OOM (Out Of Memory) killer activity
3. Verify hardware stability: Stress test without KernelSU
4. Test minimal config: Remove all modules temporarily

Banking/Payment Apps

Solutions:

1. Configure app profiles: Restrict root access for sensitive apps
2. Enable advanced hiding: Install SuSFS or Shamiko modules
3. Check Play Integrity: Use Play Integrity API tester
4. Hardware attestation: Some devices use hardware-based detection (harder to bypass)

Recommended Setup:

# Install hiding modules
# 1. Install Shamiko module
# 2. Install SuSFS4KSU module
# 3. Configure DenyList in manager
# 4. Reboot device
# 5. Test with Play Integrity checker

Game Apps

Anti-cheat Detection:

• Some games detect root and ban accounts
• Use hiding modules carefully
• Configure app profiles to deny root access
• Consider using non-rooted profiles for gaming

Information to Provide

When seeking help, include:

1. Device Information: Model, Android version, kernel version
2. KernelSU Variant: Official, Next, Wild KSU, or SukiSU-Ultra + version number
3. Installation Method: How you installed KernelSU
4. Metamodule: Which metamodule is installed (KernelSU 3.0+)
5. Reproduction Steps: Detailed steps to reproduce the issue
6. Logs: Relevant log files (dmesg, logcat, module logs)
7. Module List: All installed modules and versions

Log Collection Script

#!/system/bin/sh
# Collect comprehensive logs for troubleshooting

LOGDIR="/sdcard/kernelsu_logs_$(date +%Y%m%d_%H%M%S)"
mkdir -p "$LOGDIR"

# System info
getprop > "$LOGDIR/system_props.txt"
uname -a > "$LOGDIR/kernel_info.txt"
cat /proc/version > "$LOGDIR/kernel_version.txt"

# KernelSU info
su -c "kernelsu --version" > "$LOGDIR/kernelsu_version.txt" 2>&1

# Logs
dmesg > "$LOGDIR/dmesg.log"
logcat -d > "$LOGDIR/logcat.log"
cat /proc/last_kmsg > "$LOGDIR/last_kmsg.log" 2>/dev/null

# Module info
ls -laR /data/adb/modules > "$LOGDIR/modules_list.txt"
cat /data/adb/modules/*/module.prop > "$LOGDIR/modules_props.txt" 2>/dev/null

# Mount info
mount > "$LOGDIR/mount_points.txt"
df -h > "$LOGDIR/disk_usage.txt"

echo "Logs collected in: $LOGDIR"

From KernelSU 3.0+, the built-in module mounting system was removed. A metamodule is now required to provide module mounting infrastructure.

Why this change?

• Reduced detection: KernelSU itself doesn't mount modules, making it harder to detect
• Flexibility: Choose your preferred mounting method (OverlayFS, Magic Mount, Hybrid)
• Stability: Core KernelSU remains stable while mounting systems evolve

Quick Start:

1. Download meta-overlayfs (recommended for beginners)
2. Install via KernelSU Manager > Modules
3. Reboot device
4. Now you can install regular modules

See Understanding Metamodules for complete details.

KernelSU is a kernel-based root solution operating in kernel space, while Magisk operates in userspace.

Key Differences:

Choose based on your device and needs:

LKM Mode (Recommended for most):

• ✅ Keeps manufacturer kernel optimizations
• ✅ Easy updates via app
• ✅ OTA-friendly
• ✅ Works with stock firmware
• ⚠️ Requires official firmware

GKI Mode:

• ✅ Universal compatibility
• ✅ Works on Samsung Knox devices
• ✅ Better for custom ROMs
• ⚠️ Loses manufacturer optimizations
• ⚠️ Manual updates required

See Installation Modes for detailed comparison.

Quick Selection Guide:

• Modern devices (Android 12+, kernel 5.10+) → Official KernelSU
• Mid-range devices (Android 9–11, kernel 4.4–6.6) → KernelSU-Next
• Root hiding focus (Android 9+, kernel 4.4–6.6) → Wild KSU
• KPM / legacy / built-in SUSFS (Android 7+, broad kernel support) → SukiSU-Ultra
• Multi-manager / SukiSU ecosystem → ReSukiSU

See KernelSU Variants for detailed comparison.

Yes, in several ways:

• ✅ Kernel-level operation prevents userspace attacks
• ✅ App Profile system for granular permission control
• ✅ Zero system modification maintains integrity
• ✅ Hardware security integration (ARM TrustZone)
• ✅ seccomp + ioctl hooks (v2.0+) eliminate many side-channel detection vectors
• ✅ Metamodule architecture reduces detection surface

However, both are safe when properly configured.

Compatibility varies:

Remember: You must install a metamodule first for any modules to work on KernelSU 3.0+.

Generally no:

• ✅ System partition remains unmodified
• ⚠️ Boot partition may need re-patching after OTA
• ✅ LKM mode has OTA survival features (install to inactive slot before rebooting)
• ⚠️ Manual re-installation may be required for major updates

Always keep your patched boot image backup!

Major Changes in KernelSU 3.0+:

1. ⚠️ Module mounting removed from core: Fresh installations now require a metamodule for modules to work
2. ⚠️ Official GKI image mode dropped: Build LKM with Ylarod/ddk; the GKI build guide is archival (forks still ship GKI builds)
3. 📦 Official module repository: Verified, security-reviewed modules at modules.kernelsu.org
4. 🛡️ Reduced detection surface: seccomp + ioctl hooks (v2.0) plus metamodule architecture make detection harder
5. 🪄 Magica jailbreak mode (v3.2+): Optional deeper system access
6. 🔧 Flexible mounting: Choose between OverlayFS, Magic Mount, or hybrid metamodules

What you need to do:

• Fresh installations: Must install a metamodule before modules will work
• Existing installations: Continue to work normally (no action needed)
• Upgrading: May need to install a metamodule if modules stop working

Recommended metamodule: meta-overlayfs for most users

See Understanding Metamodules for complete details.

Check your kernel version:

# Via ADB
adb shell uname -r

# On device terminal
uname -r

Then refer to the Compatibility Matrix to find the right variant.

Yes, strongly recommended:

1. ✅ Uninstall all Magisk modules
2. ✅ Uninstall Magisk completely
3. ✅ Flash stock boot image
4. ✅ Then install KernelSU

They will conflict if installed together.

No. They modify the boot process differently and will conflict. Choose one solution for your device.

Essential backups:

1. 💾 Full TWRP backup (if available)
2. 💾 Backup stock boot.img (critical!)
3. 📝 Document installed modules
4. 💾 Export app data
5. 💾 Save important files to external storage

Top Sources:

• MMRL - Modern module manager with repository
• Awesome Android Root - Curated collection
• GitHub - Search "kernelsu module"
• Telegram - Community-shared modules
• XDA Forums - Device-specific modules

⚠️ Remember: For KernelSU 3.0+ fresh installations, you must first install a metamodule before regular modules will work!

You need a metamodule!

KernelSU 3.0+ removed built-in module mounting. Fresh installations require a metamodule to provide mounting infrastructure.

Solution:

1. Download meta-overlayfs (recommended)
2. Install via KernelSU Manager > Modules
3. Reboot device
4. Now regular modules will work

See Understanding Metamodules for details and alternatives.

Yes, but with caution:

⚠️ Only ONE metamodule can be active at a time.

To switch:

1. Uninstall all regular modules
2. Uninstall current metamodule
3. Reboot device
4. Install new metamodule
5. Reboot again
6. Reinstall regular modules

Popular choices:

• meta-overlayfs: Official, recommended for most
• mountify: Advanced, cross-platform support
• meta-hybrid_mount: Maximum compatibility with auto-fallback

App Profiles provide granular root permission control:

• ⚙️ Custom UID/GID assignment
• 🔒 Capability restrictions
• 🛡️ SELinux context customization
• ⏰ Time-based access control
• 🔐 Namespace isolation

Configure in KernelSU Manager under each app's settings.

Learn more: App Profile System Guide

KPM allows running code directly in kernel space, similar to Loadable Kernel Modules (LKM). It provides the ability to do inline-hook and syscall-table-hook in kernel space - capabilities not available in other KernelSU variants. This is an exclusive feature of SukiSU-Ultra.

Enable it by setting CONFIG_KPM=y when building the kernel.

Emergency recovery:

# 1. Enter fastboot mode (Power + Volume Down)
# 2. Connect to PC
# 3. Flash stock boot image
fastboot flash boot stock_boot.img

# 4. Reboot
fastboot reboot

This is why you ALWAYS keep a stock boot.img backup!

Root hiding setup:

1. Install Shamiko or SuSFS module
2. Configure DenyList in KernelSU Manager
3. Add banking apps to DenyList
4. Hide KernelSU Manager app
5. Test with Play Integrity checker

See Troubleshooting for detailed steps.

Quick verification:

# Check kernel
cat /proc/version | grep KernelSU

# Test root
su -c "id"

# Or open KernelSU Manager and check status

Always Do:

Never Do: