{"id":93623,"url":"https://github.com/fynks/awesome-kernelsu","name":"awesome-kernelsu","description":"A curated list of KernelSU \u0026 its forks, tools, modules, and documentation","projects_count":156,"last_synced_at":"2026-10-16T23:00:20.896Z","repository":{"id":305445334,"uuid":"1021210694","full_name":"fynks/awesome-kernelsu","owner":"fynks","description":"A curated list of KernelSU \u0026 its forks, tools, modules, and documentation","archived":false,"fork":false,"pushed_at":"2026-08-22T17:21:18.000Z","size":388,"stargazers_count":92,"open_issues_count":2,"forks_count":6,"subscribers_count":3,"default_branch":"main","last_synced_at":"2026-09-27T11:36:38.787Z","etag":null,"topics":["android-development","android-root","apatch","custom-kernel","kernel","kernelsu","kernelsu-module","kernelsu-next","magisk","root","sukisu-ultra","wild-kernel"],"latest_commit_sha":null,"homepage":"","language":null,"has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"mit","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/fynks.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":"CONTRIBUTING.md","funding":null,"license":"LICENSE","code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null,"notice":null,"maintainers":null,"copyright":null,"agents":null,"dco":null,"cla":null}},"created_at":"2025-07-17T04:18:05.000Z","updated_at":"2026-09-24T12:43:37.000Z","dependencies_parsed_at":null,"dependency_job_id":"3759d363-641e-4e3f-b4ef-175513e3f532","html_url":"https://github.com/fynks/awesome-kernelsu","commit_stats":null,"previous_names":["fynks/awesome-kernelsu"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/fynks/awesome-kernelsu","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fynks%2Fawesome-kernelsu","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fynks%2Fawesome-kernelsu/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fynks%2Fawesome-kernelsu/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fynks%2Fawesome-kernelsu/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/fynks","download_url":"https://codeload.github.com/fynks/awesome-kernelsu/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/fynks%2Fawesome-kernelsu/sbom","scorecard":null,"host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":344836268,"owners_count":38331983,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2026-10-03T21:59:58.778Z","status":"online","status_checked_at":"2026-10-16T02:00:06.653Z","response_time":55,"last_error":null,"robots_txt_status":"success","robots_txt_updated_at":"2025-07-24T06:49:26.215Z","robots_txt_url":"https://github.com/robots.txt","online":true,"can_crawl_api":true,"host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"created_at":"2025-08-27T14:55:04.436Z","updated_at":"2026-10-16T23:00:20.897Z","primary_language":null,"list_of_lists":false,"displayable":true,"categories":["🛠️ Building from Source","Related Projects","Modules and Tools","Modules \u0026 Tools","❓ FAQ","Acknowledgments","Device Kernels","KernelSU Derivatives","Official Resources","📚 Documentation","🔧 Troubleshooting","KernelSU Variants","Prebuilt Kernels","Installation \u0026 Setup","Kernel Sources \u0026 Building","Development","Community","🔧 Installation","💬 Community","License","Getting Started","What is KernelSU?","Understanding Metamodules","Metamodules","Documentation"],"sub_categories":["Device-Specific Kernel Sources","Alternative Root Solutions","🛠️ Development \u0026 Debugging","Kernel Source Repositories","Essential KernelSU Modules","Framework Modifications","Building Tools \u0026 Scripts","Management Apps","System Optimization","Root Management \u0026 Hiding","Modules \u0026 Features","✅ Safety Best Practices","Root hiding","SuKiSu-Ultra (Non-GKI Specialized)","Latest Releases \u0026 Downloads","🔨 Integration \u0026 Building","📖 Core Documentation","💡 More Questions?","Getting Help","Official KernelSU","Official Tools","📦 Module Development","🆘 Recovery \u0026 Troubleshooting","KernelSU-Next","🏆 Official GKI Builds","KernelSU-Next (Enhanced Fork)","SuKiSu-Ultra","Pre-built Images \u0026 Kernels","Device-Specific Resources","Module Development","Derivative Communities","Forums \u0026 Discussion Platforms","Root Detection \u0026 Hiding","Metamodules (Required for Module Support)","✅ Pre-Installation Checklist","WildKernels (Multi-Device)","LG Devices","Xiaomi Devices","Samsung Devices","Motorola Devices","📦 Module Managers","Official Communities","🌐 Forums \u0026 Platforms","New to KernelSU?","Key Features","Prerequisites","Available Metamodules","Wild KSU","Available metamodules","SukiSU-Ultra","OnePlus Devices","Google Pixel Devices","What is a Metamodule?","ReSukiSU","Installing Your First Metamodule"],"readme":"\u003cdiv align=\"center\"\u003e\n\n\u003cimg src=\"./media/kernelsu-logo.svg\" alt=\"KernelSU Logo\" width=\"128\"/\u003e\n\n# Awesome KernelSU\n\n**A curated list of KernelSU resources: official documentation, variants, metamodules, modules, tools, and device kernels.**\n\n[![Awesome](https://awesome.re/badge.svg)](https://awesome.re)\n[![GitHub stars](https://img.shields.io/github/stars/fynks/awesome-kernelsu?style=flat-square\u0026logo=github)](https://github.com/fynks/awesome-kernelsu)\n[![License](https://img.shields.io/github/license/fynks/awesome-kernelsu?style=flat-square)](LICENSE)\n\n\u003c/div\u003e\n\n## Contents\n\n- [What is KernelSU?](#what-is-kernelsu)\n- [Recent Developments](#recent-developments)\n- [Getting Started](#getting-started)\n- [Installation Modes](#installation-modes)\n- [Metamodules](#metamodules)\n- [KernelSU Variants](#kernelsu-variants)\n- [Modules \u0026 Tools](#modules--tools)\n- [Device Kernels](#device-kernels)\n- [Building from Source](#building-from-source)\n- [Documentation](#documentation)\n- [Community](#community)\n- [Troubleshooting](#troubleshooting)\n- [FAQs](#faqs)\n- [License](#license)\n- [Acknowledgments](#acknowledgments)\n\n---\n\n## What is KernelSU?\n\n**KernelSU** is a kernel-based root solution for Android. The `su` binary, the root allowlist, and the permission checks live in the Linux kernel, so nothing in the system partition has to be modified to grant root.\n\n### Key Features\n\n- **Root access control** — root is granted per UID/package. Apps without a grant never see `su`.\n- **Kernel-level isolation** — the manager talks to the kernel over a small IOCTL interface, so a userspace app cannot rewrite the rules it is judged by.\n- **Metamodule system** — module mounting is delegated to a pluggable metamodule instead of living in the core.\n- **App Profile** — per-app UID, GID, supplementary groups, Linux capabilities, SELinux domain, and mount namespace.\n- **Module configuration store** — modules read and write persistent or per-boot key-value settings through `ksud module config`.\n- **Late-load mode** — the kernel module can be loaded after boot instead of at init, for use cases that need the stock boot path.\n- **Native module blacklist** — other kernel modules can be blocked at boot from the Manager.\n- **ADB root** — an optional `adb root` shell, optionally restricted to live adb sessions with `shell_su_adb_only`.\n- **SELinux hide** — optional kernel-side hiding of the SELinux mode and attribute state.\n- **Magica jailbreak mode** — root escalation on a boot that comes up with permissive SELinux.\n- **x86_64 support** — LKM builds for x86_64 cover emulators, WSA, Waydroid, and ChromeOS containers.\n\n\u003e [!NOTE]\n\u003e 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](https://kernelsu.org/guide/installation.html).\n\n\u003cbr\u003e\n\n\u003e **Read next:** [KernelSU rooting guide](https://awesome-android-root.xyz/rooting-guides/kernelsu-guide) · [Official documentation](https://kernelsu.org/) · [Official module registry](https://modules.kernelsu.org)\n\n## Recent Developments\n\nThe ecosystem shifted considerably over the last few release cycles. The changes that matter most:\n\n- **Upstream ships LKM only.** GKI `boot.img` builds are no longer published and the [build guide](https://kernelsu.org/guide/how-to-build.html) is explicitly archival. Releases now carry `lkm-*.ko` artifacts for every GKI generation up to Android 17 / 6.18, for both `arm64` and `x86_64`. Forks still publish GKI images.\n- **The Manager reads the KernelSU Modules API.** Modules live in their authors' own repositories and are published as immutable GitHub releases; [modules.kernelsu.org](https://modules.kernelsu.org/) only indexes them. New submissions are reviewed before they are listed, and the flow is documented in the [developer portal](https://developers.kernelsu.org/docs/).\n- **SUSFS is no longer tied to a rebuilt kernel.** [SUSFS as an LKM](https://github.com/inforcqb/susfs4ksu-lkm) loads `susfs_guard_lkm.ko` through `ksud`, and KernelSU-Next ships those artifacts per KMI.\n- **KPM is no longer SukiSU-exclusive.** [KPatch-Next](https://github.com/KernelSU-Next/KPatch-Next) ports KernelPatch to Magisk and KernelSU.\n- **The root-hiding toolchain changed.** Shamiko is retired with the LSPosed repositories archived; the current stack is SUSFS plus [Zygisk Assistant](https://github.com/snake-4/Zygisk-Assistant), [Integrity-Box](https://github.com/MeowDump/Integrity-Box), and [Play Integrity Fix](https://github.com/KOWX712/PlayIntegrityFix).\n- **Projects were renamed or retired.** ReSukiSU is now [BakaSU](https://github.com/Baka-SU/BakaSU), and [Wild KSU](https://github.com/WildKernels/Wild_KSU) is archived. The WildKernels team still publishes device kernels.\n\n## Getting Started\n\n### Prerequisites\n\n- **Unlocked bootloader** — required for every installation method.\n- **Stock boot image backup** — your only way out of a bootloop.\n- **ADB and fastboot** on your computer.\n- **A compatible device** — check with the Manager before anything else.\n\n\u003e [!TIP]\n\u003e Bootloader unlocking is device-specific and often gated. [Awesome Android Root](https://awesome-android-root.xyz/rooting-guides/how-to-unlock-bootloader) walks through the process.\n\n### Steps\n\n1. **Check compatibility.** Install the [KernelSU Manager](https://github.com/tiann/KernelSU/releases/latest) and open it:\n   - `Not installed` → the device is officially supported.\n   - `Unsupported` → you need to build the kernel yourself. See [Device Kernels](#device-kernels) and the [non-GKI integration guide](https://kernelsu.org/guide/how-to-integrate-for-non-gki.html).\n2. **Choose an installation mode** — [LKM](#lkm-loadable-kernel-module) or [GKI](#gki-generic-kernel-image).\n3. **Install KernelSU** following the [installation guide](https://kernelsu.org/guide/installation.html).\n4. **Install a metamodule** if you use modules that ship a `system/` directory. See [Metamodules](#metamodules).\n5. **Verify** that the Manager reports an installed kernel with a matching version.\n\n## Installation Modes\n\nTwo installation modes are documented. The official recommendation: **LKM for phones, GKI for emulators, WSA, and Waydroid.**\n\n### LKM (Loadable Kernel Module)\n\nLoads KernelSU as a kernel module instead of replacing the kernel.\n\n- Keeps the stock kernel and vendor tuning.\n- Upgrades in the Manager, including \"install to inactive slot\" after an OTA.\n- Patches the ramdisk, not the boot image, so AVB is not tripped.\n- Can be removed temporarily and re-enabled on the next reboot.\n- On Android 13+ the patched partition is **`init_boot`**, not `boot`.\n\n### GKI (Generic Kernel Image)\n\nReplaces the device kernel with a generic image.\n\n- Works on any device with a matching KMI, with or without official firmware.\n- The option for Knox-locked Samsung devices, where LKM cannot run.\n\n\u003e [!NOTE]\n\u003e Since the 3.0 line, official KernelSU no longer publishes GKI images — the build guide is archival and [Ylarod/ddk](https://github.com/Ylarod/ddk) is the recommended way to produce an LKM. Forks (KernelSU-Next, SukiSU-Ultra, BakaSU) and community builders still ship GKI images.\n\n\u003cdetails\u003e\n\u003csummary\u003eQuick comparison\u003c/summary\u003e\n\n| GKI mode | LKM mode |\n| --- | --- |\n| Universal GKI compatibility | Preserves the original kernel and tuning |\n| Works on Knox-locked devices | In-app updates, OTA-friendly |\n| Independent of firmware updates | No AVB or dm-verity issues |\n| Better on heavily modified devices | Can be disabled without a reboot |\n| Loses manufacturer kernel tuning | Needs matching official firmware |\n| Requires manual fastboot flashing | May not work on modified firmware |\n| Must be reflashed after major updates | |\n\n\u003c/details\u003e\u003cbr\u003e\n\n\u003e [!TIP]\n\u003e Full instructions, KMI matching, and security-patch-level rules: [official installation guide](https://kernelsu.org/guide/installation.html).\n\n## Metamodules\n\nA **metamodule** provides the module *mounting* infrastructure. Since the 3.0 line, official KernelSU does not mount modules itself — a metamodule does.\n\n\u003e [!IMPORTANT]\n\u003e A metamodule is required only for modules that ship a `system/` directory. Script-only, `sepolicy.rule`, and `system.prop` modules work without one. Only one metamodule can be active at a time.\n\nThis applies to official KernelSU, BakaSU, YukiSU, and FinaSU. KernelSU-Next and SukiSU-Ultra still carry their own mounting engines.\n\n### Available metamodules\n\n| Metamodule | Mounting | Notes |\n|---|---|---|\n| [**meta-hybrid_mount**](https://github.com/Hybrid-Mount/meta-hybrid_mount) | OverlayFS + Magic Mount | Listed in the [official registry](https://modules.kernelsu.org/). Picks the engine per module and per path, with automatic fallback. |\n| [**mountify**](https://github.com/backslashxx/mountify) | OverlayFS | Global mount mode, works with Magisk and APatch too. |\n| [**meta-magic_mount-rs**](https://github.com/Tools-cx-app/meta-magic_mount-rs) | Magic Mount | Rust rewrite of the Magic Mount metamodule, based on MKSU. |\n| [**meta-magic_mount**](https://github.com/backslashxx/meta-magic_mount) | Magic Mount | Original Magic Mount metamodule, for modules that need Magisk-identical mounts. |\n| [**zeromount**](https://github.com/Enginex0/zeromount) | Mountless | Kernel-level VFS path redirection, so nothing is added to the mount table at all. |\n| [**Meta-Overlayfsx**](https://github.com/RipperHybrid/Meta-Overlayfsx) | OverlayFS | Continuation of the original `meta-overlayfs` with a WebUI and a live mount inspector. |\n| [**MyOverlayFs**](https://github.com/MySU-org/meta-overlayfs) | OverlayFS | Another continuation of the original `meta-overlayfs`, with an ext4 image and a repair pass on boot. |\n\n\u003e [!NOTE]\n\u003e The original `KernelSU-Modules-Repo/meta-overlayfs` repository is no longer reachable, and `meta-overlayfs` is not in the official registry. The two continuations above keep the OverlayFS approach alive; `meta-hybrid_mount` is the only metamodule currently listed in the official registry.\n\n### Installing a metamodule\n\n1. Download the metamodule ZIP from its GitHub releases.\n2. Open the Manager → **Modules**.\n3. Tap the **➕** button and pick the ZIP.\n4. Reboot.\n\nThe active metamodule is marked in the module list.\n\n\u003e [!TIP]\n\u003e The full list of metamodules and modules: [modules.kernelsu.org](https://modules.kernelsu.org/). Details on switching: [metamodule guide](https://kernelsu.org/guide/metamodule.html).\n\n## KernelSU Variants\n\n\u003e [!WARNING]\n\u003e Everything below official KernelSU is a community fork. Features do not carry over between them, and a fork can add detection vectors or stop being maintained.\n\n### Official KernelSU\n\n[![GitHub](https://img.shields.io/badge/GitHub-tiann%2FKernelSU-blue?logo=github\u0026style=flat-square)](https://github.com/tiann/KernelSU)\n[![Release](https://img.shields.io/github/v/release/tiann/KernelSU?style=flat-square)](https://github.com/tiann/KernelSU/releases)\n[![Stars](https://img.shields.io/github/stars/tiann/KernelSU?style=flat-square)](https://github.com/tiann/KernelSU)\n[![Docs](https://img.shields.io/badge/Docs-kernelsu.org-green?style=flat-square)](https://kernelsu.org/)\n[![Telegram](https://img.shields.io/badge/Telegram-KernelSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/KernelSU)\n\n\u003e The original implementation, and the reference for everything else.\n\n\u003cdetails open\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Target:** GKI 2.0 (kernel 5.10+), including WSA, ChromeOS, and container-based Android.\n- **Architectures:** `arm64-v8a`, `x86_64`; `riscv64` `ksud`/`ksuinit` artifacts.\n- **Kernel coverage in releases:** Android 12 / 5.10 through Android 17 / 6.18.\n- **Mounting:** metamodule-based.\n- **Manager:** Material 3 and MIUI-style themes, app profiles, module config, `adb root`, Magica jailbreak mode, optional SELinux hiding, native module blacklist, late-load mode, `boot-patch-v2`, and a kernel-side `sulog` view.\n- **Not supported:** non-GKI kernels were dropped after the 1.0 line; the [integration guide](https://kernelsu.org/guide/how-to-integrate-for-non-gki.html) is archival.\n\n**Resources:** [Manager APK](https://github.com/tiann/KernelSU/releases/latest) · [Documentation](https://kernelsu.org/) · [Module registry](https://modules.kernelsu.org/) · [Telegram channel](https://t.me/KernelSU) · [Issue tracker](https://github.com/tiann/KernelSU/issues)\n\n\u003c/details\u003e\n\n### KernelSU-Next\n\n[![GitHub](https://img.shields.io/badge/GitHub-KernelSU--Next-blue?logo=github\u0026style=flat-square)](https://github.com/KernelSU-Next/KernelSU-Next)\n[![Release](https://img.shields.io/github/v/release/KernelSU-Next/KernelSU-Next?style=flat-square)](https://github.com/KernelSU-Next/KernelSU-Next/releases)\n[![Stars](https://img.shields.io/github/stars/KernelSU-Next/KernelSU-Next?style=flat-square)](https://github.com/KernelSU-Next/KernelSU-Next)\n[![Docs](https://img.shields.io/badge/Docs-kernelsu--next.github.io-green?style=flat-square)](https://kernelsu-next.github.io/webpage/)\n\n\u003e Wide kernel coverage, module backup, and prebuilt SUSFS loaders.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Kernel support:** non-GKI 4.x–5.4 in LTS mode, GKI 5.10 upward; released LKM artifacts cover Android 12 / 5.10 through Android 17 / 6.18.\n- **Mounting:** built-in Magic Mount and OverlayFS, switchable from settings.\n- **SUSFS:** ships `susfs_guard_lkm.ko` per KMI, with KPROBES hiding controls in the Manager.\n- **Manager:** module backup and restore, SU allowlist backup, bulk install, auto-updates, hide-hosts via app-profile unmount, spoofed-package Manager builds, native kernel-module blocking, `shell_su_adb_only`.\n- **Architectures:** `arm64-v8a`, `armeabi-v7a`, `x86_64`.\n- **Device list:** [unofficially supported devices](https://kernelsu-next.github.io/webpage/pages/devices.html).\n\n**Resources:** [Manager APK](https://github.com/KernelSU-Next/KernelSU-Next/releases) · [Website](https://kernelsu-next.github.io/webpage/) · [Issue tracker](https://github.com/KernelSU-Next/KernelSU-Next/issues)\n\n\u003c/details\u003e\n\n### SukiSU-Ultra\n\n[![GitHub](https://img.shields.io/badge/GitHub-SukiSU--Ultra-blue?logo=github\u0026style=flat-square)](https://github.com/SukiSU-Ultra/SukiSU-Ultra)\n[![Release](https://img.shields.io/github/v/release/SukiSU-Ultra/SukiSU-Ultra?style=flat-square)](https://github.com/SukiSU-Ultra/SukiSU-Ultra/releases)\n[![Stars](https://img.shields.io/github/stars/SukiSU-Ultra/SukiSU-Ultra?style=flat-square)](https://github.com/SukiSU-Ultra/SukiSU-Ultra)\n[![Docs](https://img.shields.io/badge/Docs-sukisu.org-green?style=flat-square)](https://sukisu.org/)\n[![Telegram](https://img.shields.io/badge/Telegram-SukiKSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/Sukiksu)\n\n\u003e The variant with KPM, built-in Magic Mount, and the deepest legacy device coverage.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Kernel support:** non-GKI 4.x–5.4 in LTS mode (3.x experimental), GKI 5.10 upward, with LKM, GKI, and built-in integration paths.\n- **Mounting:** built-in Magic Mount.\n- **KPM:** KernelPatch-style kernel modules, ported from APatch, with inline and syscall-table hooks.\n- **Manager:** built-in SUSFS management, Magica jailbreak mode, WebUI X, MIUI and Material themes, in-app language switcher, Zygisk implementation detection, multi-manager signature authorization, Android 8–11 support.\n- **Architectures:** `arm64-v8a`, `armeabi-v7a`, `x86_64`.\n\n**Resources:** [Manager APK](https://github.com/SukiSU-Ultra/SukiSU-Ultra/releases) · [Website](https://sukisu.org/) · [Installation guide](https://sukisu.org/guide/installation) · [Telegram](https://t.me/Sukiksu)\n\n\u003c/details\u003e\n\n### BakaSU\n\n[![GitHub](https://img.shields.io/badge/GitHub-Baka--SU%2FBakaSU-blue?logo=github\u0026style=flat-square)](https://github.com/Baka-SU/BakaSU)\n[![Pre-release](https://img.shields.io/github/v/pre-release/Baka-SU/BakaSU?style=flat-square)](https://github.com/Baka-SU/BakaSU/releases)\n[![Stars](https://img.shields.io/github/stars/Baka-SU/BakaSU?style=flat-square)](https://github.com/Baka-SU/BakaSU)\n[![Docs](https://img.shields.io/badge/Docs-bakasu.org-green?style=flat-square)](https://bakasu.org/)\n[![Telegram](https://img.shields.io/badge/Telegram-BakaSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/BAKASU_grp)\n\n\u003e Formerly **ReSukiSU**. A downstream of KernelSU through the SukiSU branch, with minimal hooks and multi-manager support.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Mounting:** metamodule-based.\n- **Multi-manager:** the official KernelSU Manager and the KOWSU Manager both work with a BakaSU kernel.\n- **Hook modes:** tracepoint syscall redirect (GKI 2.0), manual hook (Linux 3.4 to 6.18), and SUSFS inline hook.\n- **Kernel support:** GKI 2.0 (5.10+); older kernels down to 3.4 with a manual build.\n- **SUSFS:** built-in management, with the SUSFS backport limited to kernel 4.3+.\n- **Architectures:** `arm64-v8a`, `armeabi-v7a`, `x86_64`.\n- **Releases:** tagged as pre-releases, so watch the releases page rather than the \"latest release\" badge.\n\n**Resources:** [Manager APK](https://github.com/Baka-SU/BakaSU/releases) · [Website](https://bakasu.org/) · [Telegram group](https://t.me/BAKASU_grp) · [Telegram channel](https://t.me/BakaSU_Grp)\n\n\u003c/details\u003e\n\n### YukiSU\n\n[![GitHub](https://img.shields.io/badge/GitHub-Anatdx%2FYukiSU-blue?logo=github\u0026style=flat-square)](https://github.com/Anatdx/YukiSU)\n[![Release](https://img.shields.io/github/v/release/Anatdx/YukiSU?style=flat-square)](https://github.com/Anatdx/YukiSU/releases)\n[![Stars](https://img.shields.io/github/stars/Anatdx/YukiSU?style=flat-square)](https://github.com/Anatdx/YukiSU)\n[![Docs](https://img.shields.io/badge/Docs-yukisu.anatdx.com-green?style=flat-square)](https://yukisu.anatdx.com/)\n[![Telegram](https://img.shields.io/badge/Telegram-YukiSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/YukiSU)\n\n\u003e A KernelSU fork with a rewritten C++ userspace and its own kernel-level Zygisk implementation.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Scope:** ARM64 GKI 2.0 with LKM, and nothing else — the project keeps a deliberately narrow target.\n- **Userspace:** `ksud`, `ksuinit`, and `su` are rewritten in C++ rather than wrapping upstream binaries.\n- **Zygisk:** [YukiZygisk](https://github.com/Anatdx/YukiZygisk) is built in and managed from the Manager, so no separate Zygisk module is needed.\n- **Jailbreak mode:** the LKM can be loaded temporarily without touching the boot image; the root does not survive a reboot.\n- **Authentication:** the official Manager authenticates by signature; a SuperKey is available for private deployments.\n- **Mounting:** metamodule-based, following upstream.\n\n**Resources:** [Manager APK](https://github.com/Anatdx/YukiSU/releases) · [Website](https://yukisu.anatdx.com/) · [Telegram](https://t.me/YukiSU)\n\n\u003c/details\u003e\n\n### FinaSU\n\n[![GitHub](https://img.shields.io/badge/GitHub-LyraVoid%2FFinaSU-blue?logo=github\u0026style=flat-square)](https://github.com/LyraVoid/FinaSU)\n[![Release](https://img.shields.io/github/v/release/LyraVoid/FinaSU?style=flat-square)](https://github.com/LyraVoid/FinaSU/releases)\n[![Stars](https://img.shields.io/github/stars/LyraVoid/FinaSU?style=flat-square)](https://github.com/LyraVoid/FinaSU)\n[![Telegram](https://img.shields.io/badge/Telegram-FinaSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/FinaSU)\n\n\u003e A KernelSU fork with a built-in Zygisk engine, SUSFS support, and a theme store.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eView details\u003c/b\u003e\u003c/summary\u003e\n\n- **Zygisk:** the built-in FolkZygisk engine, with Manager controls.\n- **Hiding:** mount hiding, SELinux hiding, AVC log spoofing, unmount policy, and SUSFS support gated on kernel capability.\n- **Manager:** `.fpt` themes with a theme store, multi-page wallpapers, module repository browsing, in-app language picker.\n- **Kernel support:** GKI 5.10+; 4.14+ with a manual build.\n- **Architectures:** `arm64-v8a` first, with `x86_64` and `riscv64` hooks present.\n\n**Resources:** [Manager APK](https://github.com/LyraVoid/FinaSU/releases) · [Telegram](https://t.me/FinaSU)\n\n\u003c/details\u003e\n\n### KOWSU\n\n[![GitHub](https://img.shields.io/badge/GitHub-KOWX712%2FKernelSU-blue?logo=github\u0026style=flat-square)](https://github.com/KOWX712/KernelSU)\n[![Last commit](https://img.shields.io/github/last-commit/KOWX712/KernelSU?style=flat-square)](https://github.com/KOWX712/KernelSU)\n[![Stars](https://img.shields.io/github/stars/KOWX712/KernelSU?style=flat-square)](https://github.com/KOWX712/KernelSU)\n[![Telegram](https://img.shields.io/badge/Telegram-KOWSU-blue?style=flat-square\u0026logo=telegram)](https://t.me/kowsu_build)\n\n\u003e A personal upstream fork focused on Material theming and translation coverage.\n\nNo tagged releases — the Manager APK comes from the project's build channel. Kernel support follows upstream: GKI 2.0, with 4.14+ through manual integration. The channel also runs a [discussion group](https://t.me/kowchannelchat).\n\n### Wild KSU — archived\n\n\u003e [!NOTE]\n\u003e [Wild KSU](https://github.com/WildKernels/Wild_KSU) is archived and no longer maintained as a root variant. The **WildKernels** organisation still publishes KernelSU and SUSFS device kernels — see [Device Kernels](#device-kernels).\n\n### Comparison\n\n| Variant | Kernel support | Mounting | KPM | Multi-manager | Manager highlights | Best for |\n|---|---|---|---|---|---|---|\n| **Official KernelSU** | GKI 2.0 (5.10+), LKM to Android 17 / 6.18 | Metamodule | — | — | App profiles, module config, `adb root`, Magica, SELinux hide | Stability and OTA survival |\n| **KernelSU-Next** | Non-GKI 4.x–5.4 LTS, GKI 5.10+ | Magic Mount + OverlayFS toggle | — | — | Module/allowlist backup, prebuilt SUSFS LKM, bulk install | Wide kernel range without compiling |\n| **SukiSU-Ultra** | Non-GKI 4.x–5.4 LTS (3.x experimental), GKI 5.10+ | Built-in Magic Mount | ✅ | — | SUSFS controls, WebUI X, jailbreak mode | KPM and legacy devices |\n| **BakaSU** | GKI 2.0, 3.4+ manual | Metamodule | — | ✅ | Minimal hooks, built-in SUSFS management | Old kernels and a second Manager |\n| **YukiSU** | ARM64 GKI 2.0 | Metamodule | — | — | Built-in YukiZygisk, C++ userspace, temporary jailbreak mode | A self-contained Zygisk |\n| **FinaSU** | GKI 5.10+, 4.14+ manual | Metamodule | — | — | FolkZygisk, theme store | Customization |\n| **KOWSU** | GKI 2.0, 4.14+ manual | Metamodule | — | ✅ | Material theming, many translations | Upstream look with a different theme |\n| **Wild KSU** | Archived | — | — | — | — | Historic reference only |\n\n\u003e [!NOTE]\n\u003e SUSFS is a separate kernel-side project ([susfs4ksu](https://gitlab.com/simonpunk/susfs4ksu)), not part of KernelSU. \"Built-in management\" means the Manager can drive SUSFS on a SUSFS-capable kernel; the patches or the LKM loader are still required.\n\n\u003e [!NOTE]\n\u003e KPM is a SukiSU-Ultra feature. [KPatch-Next](https://github.com/KernelSU-Next/KPatch-Next) ports it to Magisk and KernelSU, so a KPM module can be used on a plain KernelSU build.\n\n### Picking a variant\n\n| Situation | Pick |\n|---|---|\n| Stock-ish GKI phone, firmware updates matter | Official KernelSU, LKM mode |\n| Kernel outside 5.10–6.18, or you want SUSFS without rebuilding | KernelSU-Next |\n| You need KPM modules or a very old kernel | SukiSU-Ultra |\n| You want the official Manager on a non-upstream kernel, or manual hooks down to 3.4 | BakaSU |\n| You want Zygisk bundled with the Manager | YukiSU or FinaSU |\n| Knox-locked Samsung, or an emulator image | GKI mode, from a fork or a community builder |\n\n## Modules \u0026 Tools\n\n\u003e The primary source for modules is the [official registry](https://modules.kernelsu.org/). It indexes modules that live in their authors' own repositories, published as immutable GitHub releases.\n\n### Publishing a module\n\n- [**KernelSU Modules registry**](https://modules.kernelsu.org/) — the catalog the Manager reads.\n- [**Developer portal**](https://developers.kernelsu.org/) — sign in with GitHub and submit a repository.\n- [**Developer documentation**](https://developers.kernelsu.org/docs/) — `module.yaml` reference, release action, closed-source distribution, check codes.\n- [**Example module**](https://github.com/KernelSU-Modules/example-module) — a minimal working layout.\n\n### Zygisk implementations\n\nKernelSU has no built-in Zygisk. Pick one of these and install it as a module.\n\n| Implementation | Notes | Release |\n|---|---|---|\n| [**ZygiskNext**](https://github.com/LSPosed/ZygiskNext) | The long-standing standalone implementation, now hosted by the LSPosed organisation. The original repository is [Dr-TSNG/ZygiskNext](https://github.com/Dr-TSNG/ZygiskNext). | [![Release](https://img.shields.io/github/v/release/LSPosed/ZygiskNext?style=flat-square)](https://github.com/LSPosed/ZygiskNext/releases) |\n| [**ReZygisk**](https://github.com/PerformanC/ReZygisk) | Transparent implementation, written to be auditable. | [![Release](https://img.shields.io/github/v/release/PerformanC/ReZygisk?style=flat-square)](https://github.com/PerformanC/ReZygisk/releases) |\n| [**NeoZygisk**](https://github.com/JingMatrix/NeoZygisk) | ptrace-based zygote injection. | [![Release](https://img.shields.io/github/v/release/JingMatrix/NeoZygisk?style=flat-square)](https://github.com/JingMatrix/NeoZygisk/releases) |\n| [**ZygiskNextNext**](https://github.com/VeryBaaad/ZygiskNextNext) | A from-scratch implementation, listed in the official registry. | [![Release](https://img.shields.io/github/v/release/VeryBaaad/ZygiskNextNext?style=flat-square)](https://github.com/VeryBaaad/ZygiskNextNext/releases) |\n| [**YukiZygisk**](https://github.com/Anatdx/YukiZygisk) | Kernel-level Zygisk, bundled with YukiSU. | [![Release](https://img.shields.io/github/v/release/Anatdx/YukiZygisk?style=flat-square)](https://github.com/Anatdx/YukiZygisk/releases) |\n| [**VexZygisk**](https://github.com/Lxiaoyao077/VexZygisk) | Kernel-level Zygisk; submitted to the official registry. | [![Release](https://img.shields.io/github/v/release/Lxiaoyao077/VexZygisk?style=flat-square)](https://github.com/Lxiaoyao077/VexZygisk/releases) |\n\nFor the Xposed layer on top of Zygisk: [**LSPosed**](https://github.com/LSPosed/LSPosed).\n\n### Module managers\n\n- [**MMRL**](https://github.com/MMRLApp/MMRL) — module manager with a built-in repository, updates, backup and restore, and the WebUI X runtime. Community repositories: [ZGUATION-PROJECTS/ZG-R](https://github.com/ZGUATION-PROJECTS/ZG-R) · [Yukari0201/mmrl-repo](https://github.com/Yukari0201/mmrl-repo).\n\n### Root hiding and attestation\n\n| Project | What it does | Release |\n|---|---|---|\n| [**SUSFS**](https://gitlab.com/simonpunk/susfs4ksu) | Upstream kernel patches and userspace tool for hiding root files and mounts. The `master` branch is frozen; per-kernel-version branches carry the current code. | [![Last commit](https://img.shields.io/gitlab/last-commit/simonpunk/susfs4ksu?style=flat-square)](https://gitlab.com/simonpunk/susfs4ksu) |\n| [**susfs4ksu**](https://github.com/ShirkNeko/susfs4ksu) | Actively maintained SUSFS tree. | [![Last commit](https://img.shields.io/github/last-commit/ShirkNeko/susfs4ksu?style=flat-square)](https://github.com/ShirkNeko/susfs4ksu) |\n| [**susfs4ksu-lkm**](https://github.com/inforcqb/susfs4ksu-lkm) | SUSFS ported to a loadable kernel module, loaded through `ksud`. Removes the need to rebuild the kernel. | [![Release](https://img.shields.io/github/v/release/inforcqb/susfs4ksu-lkm?style=flat-square)](https://github.com/inforcqb/susfs4ksu-lkm/releases) |\n| [**susfs-lkm-module**](https://github.com/matsuzaka-yuki/susfs-lkm-module) | KernelSU-compatible ZIP wrapper around the pinned SUSFS LKM. | [![Release](https://img.shields.io/github/v/release/matsuzaka-yuki/susfs-lkm-module?style=flat-square)](https://github.com/matsuzaka-yuki/susfs-lkm-module/releases) |\n| [**susfs4ksu-module**](https://github.com/sidex15/susfs4ksu-module) | Userspace addon service for SUSFS. | [![Release](https://img.shields.io/github/v/release/sidex15/susfs4ksu-module?style=flat-square)](https://github.com/sidex15/susfs4ksu-module/releases) |\n| [**ReSuSFS**](https://github.com/ahmed-alnassif/ReSuSFS) | Packaged SUSFS experience: strong hiding by default, built-in spoofing, config files, script manager. Listed in the official registry. | [![Release](https://img.shields.io/github/v/release/ahmed-alnassif/ReSuSFS?style=flat-square)](https://github.com/ahmed-alnassif/ReSuSFS/releases) |\n| [**Zygisk Assistant**](https://github.com/snake-4/Zygisk-Assistant) | Zygisk module that hides root for KernelSU, Magisk, and APatch. | [![Release](https://img.shields.io/github/v/release/snake-4/Zygisk-Assistant?style=flat-square)](https://github.com/snake-4/Zygisk-Assistant/releases) |\n| [**Integrity-Box**](https://github.com/MeowDump/Integrity-Box) | Toolset for Play Integrity and system environment management. | [![Release](https://img.shields.io/github/v/release/MeowDump/Integrity-Box?style=flat-square)](https://github.com/MeowDump/Integrity-Box/releases) |\n| [**Play Integrity Fix**](https://github.com/KOWX712/PlayIntegrityFix) | Universal Play Integrity fix, now maintained here. Listed in the official registry. | [![Release](https://img.shields.io/github/v/release/KOWX712/PlayIntegrityFix?style=flat-square)](https://github.com/KOWX712/PlayIntegrityFix/releases) |\n| [**TrickyStore**](https://github.com/5ec1cff/TrickyStore) | Spoofs the TEE/keystore attestation chain. Closed source. | [![Release](https://img.shields.io/github/v/release/5ec1cff/TrickyStore?style=flat-square)](https://github.com/5ec1cff/TrickyStore/releases) |\n| [**TrickyStoreOSS**](https://github.com/beakthoven/TrickyStoreOSS) | Open-source alternative to TrickyStore. | [![Release](https://img.shields.io/github/v/release/beakthoven/TrickyStoreOSS?style=flat-square)](https://github.com/beakthoven/TrickyStoreOSS/releases) |\n| [**Oh My Keymint**](https://github.com/qwq233/OhMyKeymint) | Custom keystore implementation for Android keystore spoofing. | [![Release](https://img.shields.io/github/v/release/qwq233/OhMyKeymint?style=flat-square)](https://github.com/qwq233/OhMyKeymint/releases) |\n| [**Duck ToolBox**](https://github.com/eltavine/Duck-ToolBox) | Attestation workbench: Tricky Store, TEESimulator, OhMyKeymint, and RKP tooling in one WebUI. | [![Release](https://img.shields.io/github/v/release/eltavine/Duck-ToolBox?style=flat-square)](https://github.com/eltavine/Duck-ToolBox/releases) |\n\n\u003e [!WARNING]\n\u003e These provide *root-hiding mechanisms*. They may improve compatibility with apps that check for root, but they do **not** guarantee a passing Play Integrity verdict or a working banking app, and most need a matching kernel and a correct configuration. Any paid \"keybox\" offer is a scam.\n\n\u003e [!NOTE]\n\u003e Shamiko was part of this stack and is no longer maintained — the LSPosed repositories that hosted it are archived. Zygisk Assistant and the SUSFS LKM path cover the same ground.\n\n### Kernel-side tooling\n\n- [**KPatch-Next**](https://github.com/KernelSU-Next/KPatch-Next) — standalone KPM implementation for Magisk and KernelSU, with an installer module in [KPatch-Next-Module](https://github.com/KernelSU-Next/KPatch-Next-Module). This is what makes KPM usable outside SukiSU-Ultra.\n- [**Ylarod/ddk**](https://github.com/Ylarod/ddk) — kernel driver development kit, the recommended way to build an LKM for a custom kernel.\n- [**AnyKernel3**](https://github.com/osm0sis/AnyKernel3) — packaging and flashing for kernel ZIPs.\n- [**kernel_build_action**](https://github.com/dabao1955/kernel_build_action) — GitHub Actions workflow that builds a kernel with KernelSU in CI.\n- [**KernelSU_Action**](https://github.com/xiaoleGun/KernelSU_Action) — another CI action for integrating KernelSU into a kernel tree.\n- [**KernelSU_General_porting_guide**](https://github.com/dabao1955/KernelSU_General_porting_guide) — Chinese-language guide to porting KernelSU to a non-GKI kernel.\n- [**kernelsu-coccinelle**](https://github.com/devnoname120/kernelsu-coccinelle) — automatic KernelSU patches for non-GKI kernels using Coccinelle.\n- [**KernelSU-Style-UI-Kit**](https://github.com/chenaizhang/KernelSU-Style-UI-Kit) — UI templates extracted from the KernelSU Manager, for building a custom manager.\n\n### Other projects\n\n- [**systemless-hosts**](https://github.com/symbuzzer/systemless-hosts-KernelSU-module) — hosts-file blocking as a systemless module.\n- [**KernelSUGrantToast**](https://github.com/NativeStar/KernelSUGrantToast) — show a Magisk-style toast when root is granted.\n- [**Nethunter for KernelSU**](https://github.com/SherlockChiang/Nethunter_for_KernelSU) — the NetHunter toolkit as a KernelSU module.\n- [**Droidspaces**](https://github.com/ravindu644/Droidspaces-OSS) — lightweight container runtime for rooted Android.\n- [**HyperUnlocked**](https://github.com/ukriu/HyperUnlocked) — unlock high-end Xiaomi features on more devices.\n- [**BRENE**](https://github.com/rrr333nnn333/BRENE) — KernelSU module bundling SUSFS support and other tweaks.\n- [**Awesome Android Root**](https://github.com/awesome-android-root/awesome-android-root) — the sibling list: root apps, modules, and guides across the whole scene.\n\n## Device Kernels\n\nPrebuilt kernels save you from compiling. **Verify the exact model, Android version, kernel version, and security-patch level before flashing.**\n\n\u003e For anything not listed here, check the maintained community list of [KernelSU-Next unofficially supported devices](https://kernelsu-next.github.io/webpage/pages/devices.html), the [XDA KSU tag](https://xdaforums.com/tags/ksu/), or GitHub topic search.\n\n| Project | Devices | Notes | Release |\n|---|---|---|---|\n| [WildKernels GKI](https://github.com/WildKernels/GKI_KernelSU_SUSFS) | GKI 2.0 (5.10+) | KernelSU + SUSFS | [![Release](https://img.shields.io/github/v/release/WildKernels/GKI_KernelSU_SUSFS?style=flat-square)](https://github.com/WildKernels/GKI_KernelSU_SUSFS/releases) |\n| [WildKernels OnePlus](https://github.com/WildKernels/OnePlus_KernelSU_SUSFS) | OnePlus | KernelSU + SUSFS | [![Release](https://img.shields.io/github/v/release/WildKernels/OnePlus_KernelSU_SUSFS?style=flat-square)](https://github.com/WildKernels/OnePlus_KernelSU_SUSFS/releases) |\n| [WildKernels Samsung](https://github.com/WildKernels/Samsung_KernelSU_SUSFS) | Samsung | KernelSU + SUSFS | [![Release](https://img.shields.io/github/v/release/WildKernels/Samsung_KernelSU_SUSFS?style=flat-square)](https://github.com/WildKernels/Samsung_KernelSU_SUSFS/releases) |\n| [WildKernels Sultan](https://github.com/WildKernels/Sultan_KernelSU_SUSFS) | Google Pixel | Sultan base + SUSFS | [![Release](https://img.shields.io/github/v/release/WildKernels/Sultan_KernelSU_SUSFS?style=flat-square)](https://github.com/WildKernels/Sultan_KernelSU_SUSFS/releases) |\n| [Action-Build](https://github.com/Numbersf/Action-Build) | OnePlus, QCOM and MTK | CI builds for SukiSU-Ultra, KernelSU, KernelSU-Next, and BakaSU | [![Release](https://img.shields.io/github/v/release/Numbersf/Action-Build?style=flat-square)](https://github.com/Numbersf/Action-Build/releases) |\n| [NonGKI_Kernel_Build_2nd](https://github.com/JackA1ltman/NonGKI_Kernel_Build_2nd) | Non-GKI devices | Non-GKI kernels with KSU and SUSFS | [![Release](https://img.shields.io/github/v/release/JackA1ltman/NonGKI_Kernel_Build_2nd?style=flat-square)](https://github.com/JackA1ltman/NonGKI_Kernel_Build_2nd/releases) |\n| [GKID-Kernels](https://github.com/ahmed-alnassif/GKID-Kernels) | GKI 2.0 | KernelSU/ReSukiSU + SUSFS, baseband guard | [![Release](https://img.shields.io/github/v/release/ahmed-alnassif/GKID-Kernels?style=flat-square)](https://github.com/ahmed-alnassif/GKID-Kernels/releases) |\n| [YuzakiKokuban](https://github.com/YuzakiKokuban) | Galaxy S23 / S24 / S25, Tab S10, Xiaomi | Samsung kernel sources built from Samsung's open source, with KernelSU + hybrid mount + SUSFS | [![Last commit](https://img.shields.io/github/last-commit/YuzakiKokuban/android_kernel_samsung_sm8750?style=flat-square)](https://github.com/YuzakiKokuban/android_kernel_samsung_sm8750) |\n| [kernel_msm-5.15](https://github.com/topnotchfreaks/kernel_msm-5.15) | Redmi Note 12/13 4G, Redmi Pad SE | SukiSU-Ultra, KPM, and SUSFS variants | [![Release](https://img.shields.io/github/v/release/topnotchfreaks/kernel_msm-5.15?style=flat-square)](https://github.com/topnotchfreaks/kernel_msm-5.15/releases) |\n| [KernelSU_LKM_For_Oneplus12](https://github.com/snowwolf725/KernelSU_LKM_For_Oneplus12) | OnePlus 12 | LKM for OxygenOS/ColorOS | [![Release](https://img.shields.io/github/v/release/snowwolf725/KernelSU_LKM_For_Oneplus12?style=flat-square)](https://github.com/snowwolf725/KernelSU_LKM_For_Oneplus12/releases) |\n\n**Kernel selection checklist:** exact device match · matching Android and kernel version · security-patch level (anti-rollback can brick on an older patch) · active maintenance · a copy of your stock `boot.img` for recovery.\n\n## Building from Source\n\n- **Official KernelSU:** build an LKM with [Ylarod/ddk](https://github.com/Ylarod/ddk). The GKI and non-GKI build guides are archival — [How to build](https://kernelsu.org/guide/how-to-build.html) · [Integrate for non-GKI](https://kernelsu.org/guide/how-to-integrate-for-non-gki.html).\n- **Forks** (KernelSU-Next, SukiSU-Ultra, BakaSU) still support direct kernel integration — see each repository's `kernel/setup.sh`.\n- **Packaging and CI:** [AnyKernel3](https://github.com/osm0sis/AnyKernel3) · [kernel_build_action](https://github.com/dabao1955/kernel_build_action) · [KernelSU_Action](https://github.com/xiaoleGun/KernelSU_Action).\n- **Vendor kernel sources:** [Google](https://android.googlesource.com/kernel/) · [Xiaomi](https://github.com/MiCode/Xiaomi_Kernel_OpenSource) · [OnePlus](https://github.com/OnePlusOSS) · [Samsung](https://opensource.samsung.com).\n- **Writing a module:** [Module guide](https://kernelsu.org/guide/module.html) · [WebUI](https://kernelsu.org/guide/module-webui.html) · [configuration API](https://kernelsu.org/guide/module-config.html) · [Difference with Magisk](https://kernelsu.org/guide/difference-with-magisk.html).\n\n## Documentation\n\n- [What is KernelSU?](https://kernelsu.org/guide/what-is-kernelsu.html)\n- [Installation](https://kernelsu.org/guide/installation.html)\n- [Metamodules](https://kernelsu.org/guide/metamodule.html)\n- [Module guide](https://kernelsu.org/guide/module.html) · [Module WebUI](https://kernelsu.org/guide/module-webui.html) · [Module configuration](https://kernelsu.org/guide/module-config.html)\n- [App Profile](https://kernelsu.org/guide/app-profile.html)\n- [Difference with Magisk](https://kernelsu.org/guide/difference-with-magisk.html)\n- [Unofficially supported devices](https://kernelsu.org/guide/unofficially-support-devices.html)\n- [FAQ](https://kernelsu.org/guide/faq.html) · [Rescue from bootloop](https://kernelsu.org/guide/rescue-from-bootloop.html)\n- [KernelSU Modules developer docs](https://developers.kernelsu.org/docs/)\n- [SUSFS rooting guide](https://awesome-android-root.xyz/rooting-guides/susfs-guide) · [Root framework comparison](https://awesome-android-root.xyz/rooting-guides/root-framework-comparison)\n\n## Community\n\n**Telegram**\n\n- [@KernelSU](https://t.me/KernelSU) — official announcements channel.\n- [@KernelSU_group](https://t.me/KernelSU_group) — official community group.\n- [@Sukiksu](https://t.me/Sukiksu) — SukiSU-Ultra channel.\n- [@BAKASU_grp](https://t.me/BAKASU_grp) — BakaSU group (the former ReSukiSU group).\n- [@YukiSU](https://t.me/YukiSU) — YukiSU contact channel.\n\n\u003e [!NOTE]\n\u003e KernelSU-Next and KOWSU publish through GitHub and their own build channels rather than a Telegram group.\n\n**Other**\n\n- [GitHub Discussions](https://github.com/tiann/KernelSU/discussions) · [Issue tracker](https://github.com/tiann/KernelSU/issues)\n- [r/KernelSU](https://www.reddit.com/r/KernelSU/) on Reddit\n- [XDA Developers — KernelSU tag](https://xdaforums.com/tags/ksu/)\n\n## Troubleshooting\n\n\u003e [!NOTE]\n\u003e Keep a stock boot image backup before you start. It is the only reliable way back from a bootloop.\n\n### Common issues\n\n| Issue | Likely cause | Fix |\n|---|---|---|\n| **Bootloop** | Incompatible kernel or module | Flash the stock `boot.img`; disable modules through safe mode |\n| **App crashes** | SELinux policy conflict | Adjust the app profile's SELinux rules |\n| **Module not working** | No metamodule installed on a 3.0+ install | Install a metamodule and reboot |\n| **Root not detected** | Manager not installed, or version mismatch | Reinstall the Manager, check the reported kernel version |\n| **Play Integrity failing** | Root detected | SUSFS plus a hiding module, and verify the verdict with a tester |\n| **Update failed** | Storage space or a corrupt download | Clear the cache and re-download |\n| **Banking app broken** | Root detected | Tighten the app profile and configure hiding |\n| **System unstable** | Conflicting modules | Disable modules one at a time |\n\n### Emergency recovery\n\n\u003e [!WARNING]\n\u003e If the device is in a bootloop, restore it immediately.\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eBootloop recovery\u003c/b\u003e\u003c/summary\u003e\n\n```bash\n# 1. Enter fastboot (Power + Volume Down), then connect the device\n# 2. Flash the stock boot image\nfastboot flash boot stock_boot.img\n\n# 3. If needed, clear the cache\nfastboot erase cache\n\n# 4. Reboot\nfastboot reboot\n```\n\n**From recovery:** boot TWRP or another custom recovery, flash the stock boot image, wipe cache and Dalvik, reboot.\n\n**KernelSU's own safe mode:** press Volume Down three times (press-release, press-release, press-release) after the first boot screen. All modules are disabled, and you can still uninstall them from the Manager.\n\n**From ADB, with a root shell:**\n\n```bash\nksud module list\nksud module disable \u003cid\u003e\nksud module uninstall \u003cid\u003e\nreboot\n```\n\n**If nothing boots:** boot a recovery, mount `data`, remove `/data/adb/ksud`, and remove `/metadata/ksu/modules.rc` and `/metadata/watchdog/ksu/modules.rc`. KernelSU then loads no modules at all.\n\n**Prevention:** always keep the stock boot image, test with `fastboot boot test_boot.img` first, and make a TWRP backup before large changes.\n\n\u003c/details\u003e\n\n### Debugging commands\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eDiagnostics\u003c/b\u003e\u003c/summary\u003e\n\n```bash\n# KernelSU status\ncat /proc/version | grep -i kernelsu\nsu -c \"ksud --version\"\n\n# Kernel and SELinux\nuname -r\ngetenforce\ncat /proc/filesystems | grep overlay\n\n# Module state\nsu -c \"ksud module list\"\nls -la /data/adb/modules/\ncat /data/adb/modules/*/module.prop\ncat /data/adb/modules/*/install.log\n\n# Mount points\nmount | grep overlay\nmount | grep -E \"/system|/product\"\n\n# Logs\ndmesg \u003e /sdcard/dmesg.log\nlogcat -s KernelSU \u003e /sdcard/kernelsu.log\ncat /proc/last_kmsg \u003e /sdcard/last_kmsg.log\n\n# Verify root\nsu -c \"id\"\n```\n\n\u003c/details\u003e\n\n### Device-specific notes\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eSamsung\u003c/b\u003e\u003c/summary\u003e\n\n- Unlocking the bootloader trips the Knox warranty bit permanently.\n- LKM cannot run on Knox-locked devices — GKI mode is the only route.\n- Some kernels are incompatible with Samsung's encryption; keep the stock image close.\n- OEM unlocking must be enabled in Developer Options.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eOnePlus\u003c/b\u003e\u003c/summary\u003e\n\n- Unlock with `fastboot oem unlock`.\n- OnePlus devices generally do not boot generic GKI images — use a device-specific kernel.\n- Anti-rollback makes older security-patch kernels a brick risk.\n- A/B slot devices need deliberate slot handling, especially with OTA updates.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eXiaomi\u003c/b\u003e\u003c/summary\u003e\n\n- Mi Unlock requires an account and a waiting period.\n- HyperOS/MIUI features sometimes conflict with KernelSU.\n- Downgrading MIUI versions risks a brick.\n- The vendor version must match the kernel you flash.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eGoogle Pixel\u003c/b\u003e\u003c/summary\u003e\n\n- Titan M and hardware attestation make root hiding harder on recent Pixels.\n- An orange verified-boot state after flashing is expected.\n- KernelSU re-roots cleanly after an OTA with LKM.\n\n\u003c/details\u003e\n\n### Performance and app compatibility\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003ePerformance\u003c/b\u003e\u003c/summary\u003e\n\n**System feels slow**\n\n1. Disable modules one at a time to find the culprit.\n2. Check thermal throttling and CPU frequency scaling.\n3. OverlayFS on slow storage adds I/O overhead; a mountless metamodule avoids it.\n4. Read `dmesg` and `logcat` for kernel errors.\n\n```bash\ntop -m 10\niostat -x 1 10\ncat /sys/class/thermal/thermal_zone*/temp\ndmesg | grep -i error\n```\n\n**Random reboots**\n\n1. Read `dmesg` and `/proc/last_kmsg`.\n2. Look for the OOM killer in the logs.\n3. Stress-test the hardware without KernelSU loaded.\n4. Test with no modules installed.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eBanking and gaming\u003c/b\u003e\u003c/summary\u003e\n\n**Banking and payment apps**\n\n1. Restrict root per app with app profiles.\n2. Install a hiding stack: SUSFS (LKM or patched kernel) plus Zygisk Assistant.\n3. Check the verdict with a Play Integrity tester rather than assuming.\n4. Remember that hardware attestation cannot be spoofed by any module.\n\n```bash\n# 1. Install the hiding modules\n# 2. Configure the app profile to deny root\n# 3. Reboot and test\n```\n\n**Games with anti-cheat**\n\n- Some titles detect root and ban accounts.\n- Deny root to the game through its app profile, and keep the game out of any hiding exceptions.\n- Use a separate profile or a non-rooted device for competitive play.\n\n\u003c/details\u003e\n\n### Getting help\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat to include in a report\u003c/b\u003e\u003c/summary\u003e\n\n1. **Device**: model, Android version, kernel version.\n2. **Variant and version**: which fork, and which release.\n3. **Installation method**: LKM or GKI, and which partition was patched.\n4. **Metamodule**: which one is installed.\n5. **Reproduction**: exact steps.\n6. **Logs**: `dmesg`, `logcat`, and module install logs.\n7. **Module list**: every installed module with its version.\n\n```bash\n#!/system/bin/sh\n# Collect logs for a bug report\n\nLOGDIR=\"/sdcard/ksu_logs_$(date +%Y%m%d_%H%M%S)\"\nmkdir -p \"$LOGDIR\"\n\ngetprop \u003e \"$LOGDIR/system_props.txt\"\nuname -a \u003e \"$LOGDIR/kernel_info.txt\"\ncat /proc/version \u003e \"$LOGDIR/kernel_version.txt\"\n\nsu -c \"ksud --version\" \u003e \"$LOGDIR/ksud_version.txt\" 2\u003e\u00261\n\ndmesg \u003e \"$LOGDIR/dmesg.log\"\nlogcat -d \u003e \"$LOGDIR/logcat.log\"\ncat /proc/last_kmsg \u003e \"$LOGDIR/last_kmsg.log\" 2\u003e/dev/null\n\nls -laR /data/adb/modules \u003e \"$LOGDIR/modules_list.txt\"\ncat /data/adb/modules/*/module.prop \u003e \"$LOGDIR/modules_props.txt\" 2\u003e/dev/null\n\nmount \u003e \"$LOGDIR/mount_points.txt\"\ndf -h \u003e \"$LOGDIR/disk_usage.txt\"\n\necho \"Logs collected in: $LOGDIR\"\n```\n\n\u003c/details\u003e\n\n#### Where to ask\n\n1. [kernelsu.org FAQ](https://kernelsu.org/guide/faq.html) and the official docs.\n2. GitHub Discussions and the issue tracker of your variant.\n3. The Telegram group for your variant.\n4. [XDA forums](https://xdaforums.com/tags/ksu/) for device-specific threads.\n5. [r/KernelSU](https://www.reddit.com/r/KernelSU/) for general questions.\n\n\u003cdiv align=\"right\"\u003e\n\u003ca href=\"#awesome-kernelsu\"\u003e⬆ Back to Top\u003c/a\u003e\n\u003c/div\u003e\u003cbr\u003e\n\n---\n\n## FAQs\n\n### General\n\n\u003cdetails open\u003e\n\u003csummary\u003e\u003cb\u003eWhat is a metamodule and why do I need one?\u003c/b\u003e\u003c/summary\u003e\n\nSince the 3.0 line, the built-in module mounting system was removed and a metamodule provides the mounting infrastructure instead.\n\n**Why the change**\n\n- **Less to detect** — KernelSU itself performs no mounts, so it exposes fewer signatures.\n- **Choice** — the mounting strategy becomes a module you can replace.\n- **Stability** — the core stays stable while mount implementations evolve.\n\n**Quick start**\n\n1. Download a metamodule ZIP — `meta-hybrid_mount` is listed in the [official registry](https://modules.kernelsu.org/), and the OverlayFS forks are linked above.\n2. Install it from the Manager → Modules.\n3. Reboot.\n\nSee [Metamodules](#metamodules).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eHow does KernelSU differ from Magisk?\u003c/b\u003e\u003c/summary\u003e\n\n| Aspect | KernelSU | Magisk |\n|---|---|---|\n| **Architecture** | Kernel-level | Userspace, ramdisk-based |\n| **Root control** | Per-app profiles with UID, GID, capabilities, SELinux domain | DenyList |\n| **Module system** | Metamodule-based (3.0+) | Magic Mount, built in |\n| **Installation** | LKM or GKI | Boot image patching |\n| **Compatibility** | Needs a matching kernel | Broad |\n| **Zygisk** | External implementation required | Built in |\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eLKM or GKI?\u003c/b\u003e\u003c/summary\u003e\n\n**LKM** — keeps the stock kernel, upgrades in the app, survives OTA, touches only the ramdisk. Use it on phones.\n\n**GKI** — universal across GKI devices, works on Knox-locked Samsung, independent of firmware. Use it on emulators, WSA, and Waydroid, or when a device-specific GKI image exists.\n\nOfficial releases no longer ship GKI images, so a GKI install comes from a fork or a community builder.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhich variant should I use?\u003c/b\u003e\u003c/summary\u003e\n\n- **GKI device, modern phone, stability first** → official KernelSU\n- **Kernel outside 5.10–6.18, or you want SUSFS without rebuilding** → KernelSU-Next\n- **KPM modules, or a very old kernel** → SukiSU-Ultra\n- **Manual hooks down to 3.4, or a second Manager** → BakaSU\n- **Bundled Zygisk** → YukiSU or FinaSU\n\nSee [KernelSU Variants](#kernelsu-variants).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eIs KernelSU safer than Magisk?\u003c/b\u003e\u003c/summary\u003e\n\nIn several respects, yes:\n\n- Root checks run in the kernel, so a userspace app cannot rewrite them.\n- The app profile system grants partial root instead of all-or-nothing.\n- The system partition stays untouched.\n- seccomp and ioctl hooks shrink the detection surface.\n- The metamodule architecture keeps mounting out of the core.\n\nBoth are safe when configured properly. Neither is invisible to a determined detector.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eCan I use Magisk modules with KernelSU?\u003c/b\u003e\u003c/summary\u003e\n\n| Module type | Compatibility |\n|---|---|\n| **Simple modules** | Usually work unchanged, once a metamodule is installed |\n| **Complex modules** | May need adaptation for the metamodule system |\n| **Zygisk modules** | Need ZygiskNext, ReZygisk, or a similar implementation |\n| **Hardware-specific** | Usually work |\n\nKernelSU does not support Magisk's `.replace` mechanism. Delete a file with `mknod filename c 0 0` instead, or use the `REMOVE` and `REPLACE` variables. The `KSU=true` environment variable distinguishes the two environments in module scripts.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWill KernelSU break OTA updates?\u003c/b\u003e\u003c/summary\u003e\n\nUsually not. The system partition is untouched, and in LKM mode the Manager can install to the inactive slot before you reboot. A major Android upgrade sometimes needs a re-patch. Keep a backup of the patched image.\n\n\u003c/details\u003e\n\n### Installation and setup\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat changed in the 3.0 line?\u003c/b\u003e\u003c/summary\u003e\n\n1. **Module mounting left the core** — fresh installs need a metamodule, and existing installs have to reinstall their modules after upgrading.\n2. **Official GKI image builds were dropped** — build an LKM with [Ylarod/ddk](https://github.com/Ylarod/ddk) instead. The GKI build guide is archival; forks still publish GKI images.\n3. **An official module registry** — reviewed modules at [modules.kernelsu.org](https://modules.kernelsu.org/), now backed by the KernelSU Modules API.\n4. **Magica jailbreak mode** — optional root escalation on a permissive-SELinux boot.\n5. **More hiding** — SELinux hiding, a native kernel-module blacklist, and `shell_su_adb_only` for ADB-only shell root.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eHow do I check whether my device is supported?\u003c/b\u003e\u003c/summary\u003e\n\n```bash\nadb shell uname -r\n```\n\nThen read the KMI out of the kernel string. `5.10.101-android12-9-...` means KMI `5.10-android12-9`; the sublevel is not part of the KMI. The Manager also tells you directly: `Not installed` means supported, `Unsupported` means you need to build the kernel.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eDo I have to uninstall Magisk first?\u003c/b\u003e\u003c/summary\u003e\n\nYes. Remove every Magisk module, uninstall Magisk, flash the stock boot image, then install KernelSU. The two patch the boot process differently and conflict.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat should I back up?\u003c/b\u003e\u003c/summary\u003e\n\n1. A full TWRP backup, if your device has a recovery.\n2. The stock `boot.img` — and `init_boot.img` on Android 13+.\n3. The list of your current modules.\n4. App data, exported to local storage.\n\n\u003c/details\u003e\n\n### Modules and features\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhere do I find modules?\u003c/b\u003e\u003c/summary\u003e\n\n- [**Official registry**](https://modules.kernelsu.org/) — reviewed, and the one the Manager reads.\n- [**MMRL**](https://github.com/MMRLApp/MMRL) and its repository collections.\n- [**Awesome Android Root**](https://awesome-android-root.xyz/apps-and-modules/) — the wider scene.\n- GitHub search, Telegram, and XDA for device-specific builds.\n\nFresh 3.0+ installs need a metamodule before any of them mount.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eMy modules stopped working after updating to 3.0+\u003c/b\u003e\u003c/summary\u003e\n\nInstall a metamodule. The 3.0 release notes call it out explicitly: after upgrading, modules have to be reinstalled once a metamodule is present. See [Metamodules](#metamodules).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eCan I switch metamodules?\u003c/b\u003e\u003c/summary\u003e\n\nYes, one at a time:\n\n1. Uninstall the regular modules.\n2. Uninstall the current metamodule.\n3. Reboot.\n4. Install the new metamodule.\n5. Reboot again.\n6. Reinstall the regular modules.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat are app profiles?\u003c/b\u003e\u003c/summary\u003e\n\nApp profiles define the root policy for a single app:\n\n- Custom UID and GID, and supplementary groups\n- Capability restrictions\n- SELinux context and rules\n- Mount namespace and unmount behaviour\n- Reusable templates\n\nConfigure them per app in the Manager. Full details: [App Profile](https://kernelsu.org/guide/app-profile.html).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eWhat is KPM?\u003c/b\u003e\u003c/summary\u003e\n\nKPM — Kernel Patch Module — runs code in kernel space with inline hooks and syscall-table hooks. It started in APatch and was ported to KernelSU by SukiSU-Ultra. It is no longer exclusive to SukiSU: [KPatch-Next](https://github.com/KernelSU-Next/KPatch-Next) provides a standalone implementation for Magisk and KernelSU.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eDo I need to keep the kernel and Manager versions in sync?\u003c/b\u003e\u003c/summary\u003e\n\nYes. The kernel and the Manager share an interface version, and a mismatched pair produces warnings and unstable behaviour. The Manager in the official release page matches the kernel in the same release.\n\n\u003c/details\u003e\n\n### Troubleshooting\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eMy device is in a bootloop\u003c/b\u003e\u003c/summary\u003e\n\n```bash\n# 1. Enter fastboot (Power + Volume Down) and connect the device\n# 2. Flash the stock boot image\nfastboot flash boot stock_boot.img\n\n# 3. Reboot\nfastboot reboot\n```\n\nThis is why the stock `boot.img` backup is not optional. Full procedures: [Rescue from bootloop](https://kernelsu.org/guide/rescue-from-bootloop.html).\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eBanking apps do not work\u003c/b\u003e\u003c/summary\u003e\n\n1. Install the hiding stack: SUSFS (LKM or patched kernel) and Zygisk Assistant.\n2. Deny root to the banking app in its app profile.\n3. Hide the Manager app.\n4. Verify with a Play Integrity tester.\n\nNo module guarantees a passing verdict on hardware-attested devices.\n\n\u003c/details\u003e\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eHow do I confirm KernelSU is working?\u003c/b\u003e\u003c/summary\u003e\n\n```bash\n# Check the kernel\ncat /proc/version | grep -i kernelsu\n\n# Test root\nsu -c \"id\"\n```\n\nThe Manager should also report an installed kernel and a matching version.\n\n\u003c/details\u003e\n\n---\n\n## Contributing\n\nContributions are welcome — new tools, modules, maintained device kernels, and documentation fixes. See [CONTRIBUTING.md](CONTRIBUTING.md).\n\n## Disclaimer\n\nRooting 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.\n\nKernelSU and its derivatives are independent, community-driven projects. They are not affiliated with or endorsed by Google, Android, or any device manufacturer.\n\n### Legal and safety information\n\n**Educational purpose only.** Users are solely responsible for understanding and complying with local laws, following device warranty terms, maintaining device security, and understanding the consequences of modifying a device.\n\n**No warranty or liability.** Contributors and maintainers are **not liable** for device damage or bricking, data loss or corruption, warranty violations, legal consequences, or security vulnerabilities.\n\n### Safety best practices\n\n\u003cdetails\u003e\n\u003csummary\u003e\u003cb\u003eGuidelines\u003c/b\u003e\u003c/summary\u003e\n\n**Always do**\n\n| Action | Why it matters |\n|---|---|\n| ✅ **Create complete backups** | Essential for recovery |\n| ✅ **Read the documentation thoroughly** | Understand before acting |\n| ✅ **Test on a device you can replace** | Avoid daily-driver risk |\n| ✅ **Keep stock firmware** | Emergency recovery option |\n| ✅ **Check device-specific issues** | Know your device's limits |\n| ✅ **Understand the security implications** | Protect your data |\n\n**Never do**\n\n| Action | Risk |\n|---|---|\n| ❌ **Proceed without backups** | Irreversible data loss |\n| ❌ **Grant root to untrusted apps** | Security compromise |\n| ❌ **Install unknown modules** | Malware or instability |\n| ❌ **Ignore security warnings** | Serious vulnerabilities |\n| ❌ **Modify without understanding** | System damage |\n\n\u003c/details\u003e\u003cbr\u003e\n\n\u003e [!IMPORTANT]\n\u003e 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 entity.\n\n---\n\n## License\n\n[![MIT License](https://img.shields.io/badge/License-MIT-blue.svg?style=for-the-badge)](LICENSE)\n\n**This project is licensed under the [MIT License](LICENSE).**\n\n---\n\n## Acknowledgments\n\n**Special thanks to everyone who made KernelSU possible.**\n\n**Project creators**\n\n- [**tiann**](https://github.com/tiann) — creator of KernelSU, and the reason kernel-based root is practical on modern Android.\n- [**topjohnwu**](https://github.com/topjohnwu) — Magisk creator, whose systemless model KernelSU inherits.\n\n**Derivative maintainers**\n\n- **KernelSU-Next** — wider kernel coverage, module backup, prebuilt SUSFS loaders.\n- **SukiSU-Ultra** — KPM integration, legacy device support, and the deepest Manager feature set.\n- **BakaSU** — minimal hooks and multi-manager support.\n- **YukiSU and FinaSU** — bundled Zygisk engines and a different Manager direction.\n- **KOWSU** — Material theming and translation coverage on top of upstream.\n- **WildKernels** — the device kernel projects that continue after Wild KSU was archived.\n\n**Community contributors**\n\n- Module developers building the modules, metamodules, and hiding tools in the registry.\n- Kernel maintainers shipping device-specific builds.\n- Documentation translators and writers.\n- Community moderators and support staff.\n- Everyone who shares knowledge.\n\n---\n\n**Made with ❤️ by the KernelSU community**\n\n\u003csub\u003eMaintained by [Fynks](https://github.com/fynks)\u003c/sub\u003e\n\n\u003cbr\u003e\n\n**[⬆ Back to Top](#awesome-kernelsu)**\n\n\u003c/div\u003e\n","projects_url":"https://awesome.ecosyste.ms/api/v1/lists/fynks%2Fawesome-kernelsu/projects"}