Awesome KernelSU

A curated list of KernelSU resources: official documentation, variants, modules, tools, and device kernels.

What is KernelSU?

KernelSU is a kernel-based root solution for Android. Unlike userspace tools such as Magisk, it runs inside the Linux kernel and grants root access to apps directly in kernel space.

Key Features

Root Access Control - Only permitted apps can access or see su; all other apps remain unaware of it
Kernel-Level Isolation - Root access operates in kernel space, preventing userspace tampering and detection
Metamodule System - Pluggable module infrastructure for systemless /system modifications
Advanced Permission Control: Granular app-level root access management with customizable profiles
App Profile System: Customizable groups, capabilities, and SELinux rules for fine-grained root privilege control
Module Configuration System: Built-in key-value store for modules to save persistent or temporary settings

Note

Official KernelSU targets Android GKI 2.0 devices (kernel 5.10+). Compatibility ultimately depends on the device's KMI, not just the kernel version- see the installation guide.

Learn More: Comprehensive KernelSU Guide | Official Documentation | Official Module Repo

Getting Started

Prerequisites

Before installing KernelSU, ensure you have:

Unlocked bootloader (required for all installation methods)
Complete data backup (always backup before modifying your device)
ADB and Fastboot tools installed on your computer
Compatible device (check compatibility below)

Tip

New to bootloader unlocking? Check out the comprehensive guide at Awesome-Android-Root

New to KernelSU?

Check Compatibility -Install the KernelSU Manager and open it:
- Not installed → officially supported.
- Unsupported → you must build a kernel yourself (see Unofficially supported devices and Device Kernels).
Choose Installation Mode
- GKI Mode: Replaces device kernel (universal compatibility, works on Samsung Knox)
- LKM Mode: Loads as kernel module (preserves optimizations, easy updates)
See Installation Modes
Download Manager
- Get the official Manager APK for your chosen variant (links in Variants section)
Install KernelSU
- Follow the installation guide for your chosen method
Install Metamodule
- Required only if you use modules that modify /system files (e.g. meta-overlayfs). See Metamodules.
Verify Installation
- Open KernelSU Manager and confirm root status

Installation Modes

On GKI devices KernelSU historically supports two modes. The official guide recommends:

LKM- for phones.
GKI- for emulators, WSA, and Waydroid.

LKM (Loadable Kernel Module)

Loads KernelSU as a kernel module without replacing the original kernel.

Keeps the stock kernel and manufacturer optimizations.
Updates and OTA can be done in-app (including "install to inactive slot").
Does not replace the boot partition, so it does not trigger AVB.
Can be temporarily uninstalled without a reboot.
Patches the ramdisk- on Android 13+ devices this means the init_boot partition, not boot.

GKI (Generic Kernel Image)

Replaces the original kernel with a GKI image.

Works without official firmware, as long as the KMI matches.
Useful for devices where LKM cannot work (e.g. Samsung devices with KNOX enabled).

Note

Since v3.0, official KernelSU has dropped GKI image builds (the build guide is now archival) and recommends building the LKM with Ylarod/ddk. Official releases ship LKM modules and the Manager, not boot.img files. Forks (KernelSU-Next, SukiSU-Ultra, etc.) still provide GKI builds.

Click here for quick comparison

GKI Mode	LKM Mode
Universal GKI device compatibility	Preserves original kernel and optimizations
Works on Samsung Knox devices	Easy in-app updates
Independent of firmware updates	OTA-friendly
Better for heavily modified devices	No AVB/dm-verity issues
More stable on custom ROMs	Can disable without reboot
Loses manufacturer kernel optimizations	Preserves manufacturer tuning
Requires manual fastboot flashing	Requires official firmware
Must reflash after major updates	May not work on all devices
	Less compatible with modified firmware

Tip

Full instructions: Official installation guide- including KMI and security-patch-level explanations.

Metamodules

A metamodule is a special module that provides the module mounting infrastructure. Since v3.0, official KernelSU no longer mounts modules itself- it delegates mounting to a metamodule.

Important

A metamodule is needed only for modules that modify /system files (the system directory). Modules that only use scripts, sepolicy, or system.prop work without one. Only one metamodule can be installed at a time.

Note the scope: metamodule-based mounting applies to official KernelSU (v3.0+) and ReSukiSU. KernelSU-Next and SukiSU-Ultra still ship built-in mounting (Magic Mount / OverlayFS).

Available metamodules

Metamodule	Mounting	Notes
meta-overlayfs	OverlayFS	Official reference implementation- recommended starting point. Also on the official module repository.
mountify	OverlayFS	Third-party; supports APatch/Magisk too.
meta-hybrid_mount	OverlayFS + Magic Mount	Third-party; dual-engine with auto-fallback ("Hybrid Mount").

Installing Your First Metamodule

Step-by-Step Installation:

Download metamodule ZIP from GitHub releases (meta-overlayfs recommended)
Open KernelSU Manager > Modules
Tap "Install from storage" (➕ button)
Select the metamodule ZIP file
Reboot device

The active metamodule will be displayed in your module list with a special designation.

Tip

Browse the full, current list of metamodules and modules at the official module repository.

Details & switching procedure: Official metamodule guide

KernelSU Variants

Warning

Everything below Official KernelSU is a community fork/derivative, not an official project. Features of one variant do not apply to the others.

Official KernelSU

The original KernelSU implementation for modern Android devices

📋 View Details

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+).

[!CAUTION] Recent kernel versions introduced a breaking change that can make KernelSU fail or kernel-panic on x86_64. Check the official repository for current status.

Resources:

KernelSU-Next

Enhanced fork with extended compatibility, modern UI, and innovative features.

📋 View Details

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:

SukiSU-Ultra

Kernel-based root solution with KPM support, built-in SUSFS, and broad GKI/non-GKI compatibility.

📋 View Details

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:

ReSukiSU

A newer fork of SukiSU-Ultra focused on multi-manager support and a metamodule-based module system.

📋 View Details

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:

Wild KSU- archived

Note

The Wild KSU fork (WildKernels/Wild_KSU) is archived (last release v3.1.2). It is no longer maintained as a root variant. The WildKernels team still ships KernelSU/SUSFS device kernels- see Device Kernels.

Comparison

Feature	Official KernelSU	KernelSU-Next	SukiSU-Ultra	ReSukiSU
Status	Official, active	Active fork	Active fork	Active fork
Kernel support	GKI 2.0 (5.10+); 4.14+ manual	4.4–6.6	5.10+ GKI; 4.4+ non-GKI/manual; 3.x experimental	5.10+ GKI; 3.4+ manual
Android version	12+ (GKI); 10+ community	9+	7+	7+
Module mounting	Metamodule (3.0+)	Metamodule + dual mount toggle	Magic Mount / Metamodule	Metamodule
KPM	❌	❌	✅	✅
SUSFS	Via kernel patch	Via kernel patch	Built-in management	Built-in management
Multi-manager	❌	❌	❌	✅ (KSU/RKSU/MKSU/Suki)
Architectures	arm64, x86_64	arm64, arm, x86_64	arm64, arm, x86_64 (some/partial)	arm64, arm, x86_64
Installation modes	LKM (GKI image deprecated)	GKI / LKM	GKI / LKM	GKI / LKM
Module backup/restore	❌	✅	❌	❌
Auto updates	⚠️ LKM only	✅	⚠️ Manual	⚠️ Manual
Root hiding	Metamodule-based	Advanced (unmount)	SUSFS built-in	SUSFS built-in
UI/UX	Material 3 + Magica	Material You	Enhanced + WebUI	Enhanced
Legacy support	❌	⚠️ Limited	✅ Extensive	✅ Extensive
Best for	Modern devices	Power users	KPM / legacy / hiding	Multi-manager setups

Note

SUSFS is a separate kernel-patch addon (gitlab.com/simonpunk/susfs4ksu)- it is not part of KernelSU itself. "Built-in management" means the Manager can control SUSFS on a SUSFS-patched kernel; it does not bundle the kernel patches.

Which Variant Should You Choose?

Choose Official KernelSU if:

✅ Modern device (2021+)
✅ GKI 2.0 support
✅ Want maximum stability
✅ Prefer official support
✅ OTA compatibility priority

Choose KernelSU-Next if:

✅ Kernel 4.4–6.6
✅ Want latest features
✅ Prefer modern UI
✅ Auto-updates desired
✅ Advanced module mgmt

Choose Wild KSU if:

✅ Kernel 4.4–6.6
✅ Root hiding priority
✅ Want SUSFS integrated
✅ Customization focused
✅ Nightly build access

Choose SukiSU-Ultra if:

✅ Need KPM support
✅ Legacy non-GKI device
✅ Want built-in SUSFS
✅ Banking app hiding
✅ 32-bit ARM device

Modules & Tools

The primary source for modules is the official module repository.

Zygisk & frameworks

KernelSU has no built-in Zygisk; use a standalone implementation for Zygisk modules.

ZygiskNext- standalone Zygisk implementation.
ReZygisk- open-source, transparent Zygisk implementation.
LSPosed- Xposed framework (requires Zygisk).

Module managers

MMRL- modern module manager with a built-in repository, updates, backup/restore, and WebUI support.

Root hiding

SUSFS- kernel patches + userspace addon providing root-hiding mechanisms (experimental; requires a SUSFS-patched kernel).
SuSFS4KSU- addon root-hiding service for KernelSU.

Warning

These provide root-hiding mechanisms and may improve compatibility with apps that perform root checks. They do not guarantee passing Play Integrity or bypassing any given banking app, and often require additional configuration.

Device Kernels

Prebuilt kernels save you from compiling. Always verify the exact device model, Android version, kernel version, and security-patch level before flashing.

For anything not listed here, check the maintained community list of KernelSU-Next unofficially supported devices, the XDA KernelSU tag, or GitHub topic/search results.

Project	Devices	Notes
WildKernels- GKI	GKI 2.0 (5.10+) devices	KernelSU + SUSFS; active
WildKernels- Sultan	Google Pixel	Sultan base + SUSFS; active
WildKernels- OnePlus	OnePlus devices	KernelSU + SUSFS; active
WildKernels- Samsung	Samsung devices	KernelSU + SUSFS; active
YuzakiKokuban- Samsung	Galaxy S23/S24/S25, Tab S10	KernelSU kernel sources (`sm8550`, `sm8650`, `sm8750`, `mt6989`); active
KernelSU LKM- OnePlus 12	OnePlus 12	LKM for OxygenOS/ColorOS; active
topnotchfreaks- msm-5.15	Redmi Note 12/13 4G, Redmi Pad SE, Redmi 15/POCO M7	SukiSU-Ultra + KPM + SUSFS variants; active

Kernel selection checklist: exact device match · matching Android/kernel version · security-patch level (anti-rollback can brick on older patches) · active maintenance · a copy of your stock boot.img for recovery.

Building from Source

Official KernelSU: build the LKM with Ylarod/ddk (recommended since v3.0). The GKI and non-GKI build guides are archival- How to build · Integrate for non-GKI.
Forks (KernelSU-Next, SukiSU-Ultra, ReSukiSU) still support direct kernel integration- see each repository's kernel/setup.sh.
Tools: AnyKernel3 (packaging/flashing) · kernel_build_action (GitHub Actions builds).
Vendor kernel sources: Google · Xiaomi · OnePlus · Samsung.

Documentation

Community

Telegram

@KernelSU- official announcements channel.
@KernelSU_group- official community group.
@Sukiksu- SukiSU community.
@ReSukiSU- ReSukiSU community.

Other

Troubleshooting

Note

Before troubleshooting, ensure you have a backup of your stock boot image. This is crucial for recovery.

Common Issues

Issue	Possible Cause	Solution
Bootloop	Incompatible kernel/module	Flash stock boot.img via fastboot, disable modules
App Crashes	SELinux policy conflicts	Check and adjust SELinux policies in app profiles
Module Not Working	No metamodule installed (KSU 3.0+)	Install a metamodule first; verify module compatibility
Root Not Detected	Manager not installed properly	Reinstall KernelSU Manager, verify kernel version
Play Integrity Failing	Root detection	Install Shamiko or SuSFS, configure hiding properly
Update Failed	Insufficient storage/corrupt download	Clear cache, re-download, ensure adequate storage
Banking Apps Not Working	Root detection	Configure app profiles, install hiding modules
System Unstable	Conflicting modules	Disable modules one by one to identify culprit

Emergency Recovery

Warning

If your device is in a bootloop, follow these steps immediately to restore functionality.

🚨 Click to expand: Bootloop Recovery & Emergency Procedures

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:

Boot into TWRP/custom recovery
Flash stock boot image from recovery
Wipe cache and dalvik cache
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:

Create file /data/adb/modules/.disable_modules before boot
This disables all modules for troubleshooting
Remove problematic modules
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"

Debugging Commands

🔍 Click to expand: Debug Commands & Diagnostics

# 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

Device-Specific Issues

📱 Click to expand: Device-Specific Troubleshooting

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

Performance Issues

⚡ Click to expand: Performance Troubleshooting

System Slowdown

Diagnosis:

Identify problematic modules: Disable modules one by one
Check CPU throttling: Monitor thermals and frequency scaling
Review I/O performance: OverlayFS overhead on slow storage
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:

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

App Compatibility

🏦 Click to expand: Banking & Gaming App Compatibility

Banking/Payment Apps

Solutions:

Configure app profiles: Restrict root access for sensitive apps
Enable advanced hiding: Install SuSFS or Shamiko modules
Check Play Integrity: Use Play Integrity API tester
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

Getting Help

💬 Click to expand: Support Resources & Log Collection

Information to Provide

When seeking help, include:

Device Information: Model, Android version, kernel version
KernelSU Variant: Official, Next, Wild KSU, or SukiSU-Ultra + version number
Installation Method: How you installed KernelSU
Metamodule: Which metamodule is installed (KernelSU 3.0+)
Reproduction Steps: Detailed steps to reproduce the issue
Logs: Relevant log files (dmesg, logcat, module logs)
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"

Support Priority

Official Documentation: Check kernelsu.org FAQ
GitHub Discussions: Search existing issues and discussions
Telegram Groups: Ask in appropriate variant-specific group
XDA Forums: Device-specific threads
Reddit: r/KernelSU for general questions

⬆ Back to Top

FAQs

Frequently asked questions about KernelSU - Quick answers to common queries.

General Questions

What is a Metamodule and why do I need one?

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:

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

See Understanding Metamodules for complete details.

What is KernelSU and how does it differ from Magisk?

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

Key Differences:

Aspect	KernelSU	Magisk
Architecture	Kernel-level	Userspace
Security	Superior isolation	Good but less isolated
Module System	Metamodule-based (3.0+)	Magic Mount (built-in)
Installation	GKI / LKM modes	Boot patching
Compatibility	Requires compatible kernel	Universal
Future-proof	Built for modern Android	Legacy support focus

Which installation mode should I use: GKI or LKM?

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.

Which KernelSU variant should I use?

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.

Is KernelSU safer than Magisk?

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.

Can I use Magisk modules with KernelSU?

Compatibility varies:

Module Type	Compatibility
Simple modules	✅ Most work without changes (with metamodule)
Complex modules	⚠️ May need adaptation for metamodule system
Zygisk modules	⚠️ Require ZygiskNext or ReZygisk
Hardware-specific	✅ Usually compatible

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

Will KernelSU break OTA updates?

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!

Installation & Setup

What changed in KernelSU 3.0 and how does it affect me?

Major Changes in KernelSU 3.0+:

⚠️ Module mounting removed from core: Fresh installations now require a metamodule for modules to work
⚠️ Official GKI image mode dropped: Build LKM with Ylarod/ddk; the GKI build guide is archival (forks still ship GKI builds)
📦 Official module repository: Verified, security-reviewed modules at modules.kernelsu.org
🛡️ Reduced detection surface: seccomp + ioctl hooks (v2.0) plus metamodule architecture make detection harder
🪄 Magica jailbreak mode (v3.2+): Optional deeper system access
🔧 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.

How do I check if my device is compatible?

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.

Do I need to uninstall Magisk before installing KernelSU?

Yes, strongly recommended:

✅ Uninstall all Magisk modules
✅ Uninstall Magisk completely
✅ Flash stock boot image
✅ Then install KernelSU

They will conflict if installed together.

Can I have both Magisk and KernelSU installed?

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

How do I backup before installing?

Essential backups:

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

Modules & Features

Where can I find KernelSU modules?

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!

My modules aren't working after installing KernelSU 3.0+, why?

You need a metamodule!

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

Solution:

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

See Understanding Metamodules for details and alternatives.

Can I switch between different metamodules?

Yes, but with caution:

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

To switch:

Uninstall all regular modules
Uninstall current metamodule
Reboot device
Install new metamodule
Reboot again
Reinstall regular modules

Popular choices:

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

What are App Profiles and how do I use them?

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

What is KPM (Kernel Patch Module) in SukiSU-Ultra?

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.

Troubleshooting

My device is in bootloop, what do I do?

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!

Banking apps aren't working, how do I fix this?

Root hiding setup:

Install Shamiko or SuSFS module
Configure DenyList in KernelSU Manager
Add banking apps to DenyList
Hide KernelSU Manager app
Test with Play Integrity checker

See Troubleshooting for detailed steps.

How do I verify KernelSU is working?

Quick verification:

# Check kernel
cat /proc/version | grep KernelSU

# Test root
su -c "id"

# Or open KernelSU Manager and check status

Contributing

Contributions are welcome- new tools, modules, maintained device kernels, and documentation fixes. See CONTRIBUTING.md.

Disclaimer

Rooting and kernel modification can void warranties, brick devices, and expose security vulnerabilities. This list is provided for educational and informational purposes only- you assume all risks.

KernelSU and its derivatives are independent, community-driven projects. They are not affiliated with or endorsed by Google, Android, or any device manufacturer.

Legal & Safety Information

Educational Purpose Only

This documentation is provided for educational and informational purposes only. Users are solely responsible for:

Understanding and complying with local laws
Following device warranty terms
Maintaining device security
Device modifications and consequences

No Warranty or Liability

Contributors and maintainers are NOT liable for:

Device damage or bricking
Data loss or corruption
Warranty violations
Legal consequences
Security vulnerabilities

Safety Best Practices

🛡️ Click to expand: Essential Safety Guidelines

Always Do:

Action	Why It Matters
✅ Create complete backups	Essential for recovery
✅ Read documentation thoroughly	Understand before acting
✅ Test on non-critical devices	Avoid daily driver risks
✅ Keep stock firmware	Emergency recovery option
✅ Research device-specific issues	Know your device limitations
✅ Understand security implications	Protect your data

Never Do:

Action	Risk
❌ Proceed without backups	Irreversible data loss
❌ Grant root to untrusted apps	Security compromise
❌ Install unknown modules	Malware/instability
❌ Ignore security warnings	Serious vulnerabilities
❌ Modify without understanding	System damage

Important

KernelSU and its derivatives are independent, community-driven projects. They are not affiliated with, endorsed by, or connected to Google, Android, device manufacturers, or any other commercial entities.

License

This project is licensed under the MIT License.

Acknowledgments

Special thanks to all contributors who made KernelSU possible.

Project Creators

tiann - Creator of KernelSU, visionary behind kernel-based root solutions
topjohnwu - Magisk creator, inspiration for systemless modifications

Derivative Maintainers

KernelSU-Next Team - Enhanced fork development and innovation
Wild KSU Team (WildKernels) - Customization and root hiding focused fork
SukiSU-Ultra Team - KPM integration, legacy device support and compatibility
ReSukiSU Team - Multi-manager support and metamodule integration

Community Contributors

Module developers creating useful tools
Documentation translators and writers
Community moderators and support staff
Everyone who shares knowledge

Special Recognition

All kernel developers maintaining device-specific builds
Community members providing support
Contributors to this awesome list

Made with ❤️ by the KernelSU Community

_{Last Updated: August 2026 | Maintained by Fynks}

⬆ Back to Top

Name		Name	Last commit message	Last commit date
media		media
.gitignore		.gitignore
CONTRIBUTING.md		CONTRIBUTING.md
LICENSE		LICENSE
README.md		README.md

Latest commit

History

Folders and files

Repository files navigation

Awesome KernelSU

Contents

What is KernelSU?

Key Features

Getting Started

Prerequisites

New to KernelSU?

Installation Modes

LKM (Loadable Kernel Module)

GKI (Generic Kernel Image)

Metamodules

Available metamodules

Installing Your First Metamodule

KernelSU Variants

Official KernelSU

KernelSU-Next

SukiSU-Ultra

ReSukiSU

Wild KSU- archived

Comparison

Which Variant Should You Choose?

Modules & Tools

Zygisk & frameworks

Module managers

Root hiding

Device Kernels

Building from Source

Documentation

Community

Troubleshooting

Common Issues

Emergency Recovery

Bootloop Recovery

Module-Related Issues

Debugging Commands

Device-Specific Issues

Samsung Devices

OnePlus Devices

Xiaomi Devices

Google Pixel Devices

Performance Issues

System Slowdown

Random Reboots

App Compatibility

Banking/Payment Apps

Game Apps

Getting Help

Information to Provide

Log Collection Script

Support Priority

FAQs

General Questions

Installation & Setup

Modules & Features

Troubleshooting

Contributing

Disclaimer

Legal & Safety Information

Safety Best Practices

License

Acknowledgments

About

Topics

Resources

Contributing

Stars

Watchers

Forks

Used by

Contributors