Best For: Modern flagship devices (2021+) prioritizing stability and official support

✨ Key Features:

• Official GKI 2.0 support (kernel 5.10+)
• Battle-tested stability
• Regular security updates & maintenance
• Comprehensive official documentation
• Wide device compatibility for modern phones
• Active development by original author

Technical Specs:

• Kernel Support: 5.10+ (GKI 2.0), 4.14+ with manual compilation
• Android Version: 12+ (official), 10+ (community builds)
• Architecture: arm64-v8a, x86_64
• Special Support: WSA, ChromeOS, container-based Android

🔗 Resources:

• 📥 Download Manager APK
• 📖 Official Documentation
• 💬 Telegram Channel
• 🐛 Report Issues

Best For: Power users wanting cutting-edge features and broader device compatibility

✨ Enhanced Features:

• Extended kernel support (4.4-6.6, GKI & non-GKI)
• Dual module system (Magic Mount + OverlayFS with seamless toggle)
• Beautiful Material You UI with dynamic theming
• Advanced module management (backup/restore, bulk ops, dependencies)
• Automatic update system with rollback capability
• WebUI X framework for advanced module interfaces
• Built-in developer tools (logcat, performance monitor)
• Configurable OverlayFS options

Technical Specs:

• Kernel Support: 4.4 - 6.6 (Non-GKI & GKI)
• Android Version: 9+
• Architecture: arm64-v8a, armeabi-v7a, x86_64
• Update Frequency: Very active development with frequent updates

🔗 Resources:

• 📥 Download Manager APK
• 📖 Official Website
• 💬 Telegram Community
• 🐛 Report Issues

Best For: Legacy devices and users requiring advanced root hiding for banking apps

✨ Unique Features:

• Broad legacy kernel compatibility (3.4-5.4+) with extensive backports
• Built on Magic Mount technology for enhanced stability
• KPM (Kernel Patch Module) integration
• SuSFS built-in for superior root hiding
• Multi-architecture including 32-bit ARM support
• Enhanced manager with SuSFS management panel
• Legacy device optimizations
• Community-maintained device database

Technical Specs:

• Kernel Support: 3.4 - 5.4+ (Non-GKI focused)
• Android Version: 7+
• Architecture: arm64-v8a, armeabi-v7a, x86_64
• Update Frequency: Active community-driven development

🔗 Resources:

• 📥 Download Manager APK
• 📖 Official Website
• 📚 Installation Guide
• 💬 Telegram Group

1. Kernel-Level Isolation: Root access operates in kernel space, preventing userspace tampering
2. App Profile System: Granular per-application permission control with temporal restrictions
3. Hardware-Level Protection: Utilizes ARM TrustZone and hardware security features
4. Verified Boot Compatible: Maintains system integrity verification where possible
5. Advanced Hiding: Kernel-level hiding harder to detect than userspace methods

1. Zero System Modification: No changes to system partitions, preserving OTA capabilities
2. OverlayFS Efficiency: More efficient than bind mounting with better performance
3. Future-Proof Design: Built for modern Android security models and requirements
4. Developer-Friendly: Clean APIs and comprehensive documentation
5. Modular Architecture: Easy to extend and customize

1. Multiple Derivatives: Options for different use cases and device compatibility
2. Active Development: Regular updates and feature additions across all variants
3. Growing Module Repository: Expanding collection of high-quality modules
4. Community Support: Knowledgeable community with expert developers
5. Documentation: Comprehensive guides in multiple languages

Advantages:

• Enhanced security and hiding capabilities
• Better performance with OverlayFS
• Future-proof architecture for modern Android
• Maintained OTA compatibility

Considerations:

• Module compatibility may require updates
• Different app profile management approach
• Learning curve for new concepts
• Some Magisk-specific features unavailable

Migration Steps:

1. Backup all data and current setup
2. Document installed modules and configurations
3. Uninstall Magisk completely
4. Flash stock boot image
5. Install KernelSU using preferred method
6. Reinstall compatible modules
7. Configure app profiles

Essential Steps:

• Complete system restoration recommended
• Fresh start with modern practices
• Understanding of new security model
• Backup and data migration planning

Benefits:

• Dramatically improved security
• Modern Android compatibility
• Systemless approach
• Active development and support

Advantages:

• ✅ Strong universality for modern devices
• ✅ Official support and regular updates
• ✅ Clean installation with minimal configuration

Step-by-Step:

# 1. Download boot.img from releases
# Visit: https://github.com/tiann/KernelSU/releases/latest

# 2. Boot device to fastboot mode
adb reboot bootloader

# 3. Flash the kernel
fastboot flash boot boot.img

# 4. Reboot device
fastboot reboot

# 5. Install KernelSU Manager APK after boot

# 6. IMPORTANT: Install a metamodule for module support
# Download meta-overlayfs and install via KernelSU Manager

More Details: GKI Installation Guide

Advantages:

• ✅ Preserves original kernel and manufacturer optimizations
• ✅ Less intrusive modification
• ✅ Easier to revert to stock
• ✅ OTA-friendly (install to inactive slot)
• ✅ Easy in-app updates
• ✅ No AVB/dm-verity issues

Requirements:

• Stock/official firmware
• Compatible kernel version

Step-by-Step:

1. Install KernelSU Manager APK on device
2. Grant necessary permissions
3. In Manager, select "Install" → "Select and Patch a File"
4. Choose your stock boot.img file
5. Manager will patch it with KernelSU (LKM mode)
6. Flash patched boot via fastboot:

# Transfer patched boot to PC
adb pull /sdcard/Download/kernelsu_patched_xxxxx.img

# Boot to fastboot
adb reboot bootloader

# Flash patched image
fastboot flash boot kernelsu_patched_xxxxx.img

# Reboot
fastboot reboot

7. Install metamodule after first boot for module support

Complete Guide: LKM Mode Installation

Advantages:

• ✅ User-friendly, minimal PC usage
• ✅ Automatic patching process
• ✅ Simplest for non-technical users
• ✅ Supports both GKI and LKM modes

Step-by-Step:

1. Extract boot.img from your device firmware
2. Install KernelSU Manager APK on device
3. Grant necessary permissions
4. Select "Install" → "Select and Patch a File"
5. Choose your boot.img file
6. Manager patches boot image automatically
7. Flash patched boot via fastboot or custom recovery

# Flash patched boot via fastboot
adb pull /sdcard/Download/kernelsu_patched_*.img
adb reboot bootloader
fastboot flash boot kernelsu_patched_*.img
fastboot reboot

8. Install metamodule after first boot for module support

Detailed Tutorial: Manager Patching Guide

Advantages:

• ✅ Device-optimized performance
• ✅ Pre-tested stability
• ✅ Additional features (SUSFS, optimizations)
• ✅ No compilation required

Step-by-Step:

1. Find your device in Prebuilt Kernels section
2. Download appropriate kernel zip
3. Flash via TWRP or fastboot:

Via TWRP:

1. Boot to TWRP recovery
2. Install → Select kernel zip
3. Swipe to flash
4. Reboot system

Via Fastboot:

adb reboot bootloader
fastboot flash boot kernel.img
fastboot reboot

4. Install KernelSU Manager APK
5. Verify installation in Manager

Advantages:

• ✅ Full customization control
• ✅ Latest features and patches
• ✅ Learn kernel development

Requirements:

• Linux build environment (Ubuntu 20.04+ recommended)
• Kernel source code for your device
• Cross-compiler toolchain
• Build dependencies (see Building from Source)

Quick Overview:

1. Setup Linux build environment
2. Clone kernel source and KernelSU repository
3. Apply KernelSU patches
4. Configure kernel (enable CONFIG_KSU)
5. Compile kernel
6. Package with AnyKernel3
7. Flash to device

Full guide: See Building from Source section

✨ Key Features:

• ✅ Built-in module repository with 100+ modules
• ✅ Automatic module updates
• ✅ Module backup/restore functionality
• ✅ Dependency management
• ✅ WebUI support for advanced modules
• ✅ Material You design language
• ✅ Dark/Light theme support
• ✅ Detailed module information and changelogs

📥 Download: MMRL Latest Release

[!IMPORTANT] Building kernels requires significant disk space (50GB+) and time. Ensure you have a proper Linux environment.

# Install dependencies (Ubuntu/Debian)
sudo apt update
sudo apt install -y git build-essential kernel-package fakeroot libncurses5-dev \
  libssl-dev ccache bison flex libelf-dev bc python3

# Install cross-compiler
sudo apt install -y gcc-aarch64-linux-gnu gcc-arm-linux-gnueabihf

# Clone KernelSU
git clone https://github.com/tiann/KernelSU

[!TIP] Use ccache to speed up subsequent builds. Enable it with export USE_CCACHE=1 and export CCACHE_DIR=~/.ccache.

# 1. Clone your device kernel source
git clone <kernel_source_url> kernel

# 2. Apply KernelSU patches
cd kernel
curl -LSs "https://raw.githubusercontent.com/tiann/KernelSU/main/kernel/setup.sh" | bash -

# 3. Configure kernel
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- <defconfig>

# 4. Enable KernelSU in config
./scripts/config --file .config -e CONFIG_KSU

# 5. Build kernel
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j$(nproc)

# 6. Package with AnyKernel3
# Copy Image.gz-dtb or Image to AnyKernel3 directory
# Zip and flash

[!WARNING] Building with wrong toolchain or configuration can produce non-bootable kernels. Always test on non-critical devices first.

• arm64-v8a: Primary support (64-bit ARM) - most modern devices
• x86_64: Intel/AMD 64-bit (emulators, some tablets)
• armeabi-v7a: 32-bit ARM (legacy devices, SuKiSu-Ultra only)

name: Build Kernel
on:
  push:
    branches: [ main ]
  workflow_dispatch:
jobs:
  build:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - name: Build Kernel with KernelSU
        uses: dabao1955/kernel_build_action@main
        with:
          kernel-url: <your_kernel_repo>
          branch: <branch_name>
          config: <defconfig_name>
          arch: arm64

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

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"

• 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

• Fastboot Commands: Use fastboot oem unlock for bootloader
• Color OS Migration: Recent devices need special handling for OxygenOS vs ColorOS
• Parallel Apps: OxygenOS parallel apps may conflict with root
• Slot System: A/B partition devices need careful slot management

• Anti-Rollback: Be careful with MIUI version downgrades (brick risk)
• Bootloader Unlock: Xiaomi requires waiting period (up to 168 hours)
• MIUI Optimizations: Some MIUI features conflict with KernelSU
• Vendor Mismatch: Ensure kernel matches vendor version

• Hardware Attestation: Strong SafetyNet 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

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

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

Prevention:

• Avoid aggressive kernel tweaks
• Monitor temperature during stress tests
• Ensure adequate RAM for modules
• Use stable kernel versions

Solutions:

1. Configure app profiles: Restrict root access for sensitive apps
2. Enable advanced hiding: Install SuSFS or Shamiko modules
3. Check SafetyNet: Use YASNAC or 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 SafetyNet checker

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

When seeking help, include:

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

#!/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
• Legacy devices (Android 7-8, kernel 3.4-5.4) → SuKiSu-Ultra

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)
• ✅ 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
• ⚠️ 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. ✅ LKM mode improvements: Better stability and OTA support
3. 🛡️ Reduced detection surface: Harder for banking apps to detect
4. 🔧 Flexible mounting: Choose between OverlayFS, Magic Mount, or hybrid approaches

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

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 SafetyNet 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

Common causes:

• ❌ No metamodule installed (KernelSU 3.0+)
• ❌ Incompatible module version
• ❌ Insufficient permissions
• ❌ Module conflicts
• ❌ Mounting system not supported

Solutions:

1. Check if metamodule is installed (KernelSU 3.0+ requirement)

   • Open KernelSU Manager > Modules
   • Look for active metamodule (e.g., meta-overlayfs)
   • If missing, install one from Understanding Metamodules

2. Check module logs: /data/adb/modules/[module]/install.log

3. Verify module compatibility with your KernelSU version

Quick steps:

1. Setup Linux build environment
2. Clone kernel source
3. Apply KernelSU patches
4. Configure kernel (enable CONFIG_KSU)
5. Compile kernel
6. Package with AnyKernel3

See Building from Source for detailed guide.

Absolutely! Contributions welcome:

• 🐛 Report bugs on GitHub
• 💻 Submit pull requests
• 📦 Create and share modules
• 📚 Improve documentation
• 💬 Help in community support
• 🧪 Test beta versions

Always Do:

Never Do: