Temporary root on a locked Android bootloader, one boot at a time.
Curated compatibility index for DirtyFrag, GhostLock, POSIX CPU timer, Adreno GPU loaders, KernelSU late-load managers, and runtime modules.
Search devices, browse uncollapsed hardware and module tables, and read offline.
Supported devices · Tools and managers · Modules and apps · Quick start · FAQ
- What is temporary root?
- Supported devices
- Tools and managers
- Modules
- Firmware and recovery resources
- Research resources
- Quick start
- Troubleshooting and FAQ
- Contributing and disclaimer
- Sources
Tip
New here? Read What is temporary root? first, find your exact model in Supported devices, then follow Quick start. If your build is not listed, do not try the closest one.
Important
This project is only for accumulating all knowledge, tools, modules, and other resources relating to temporary rooting in one place. Unfortunately, porting temporary solutions to specific devices is out of scope of this project.
Temporary root gives an app or an ADB shell UID 0 on the current boot without unlocking the bootloader or flashing a boot image. A loader exploits a kernel bug, starts a root daemon, and late-loads a KernelSU kernel module. A KernelSU-compatible manager can then grant su. A full reboot unloads the module and ends the session.
The loader that works depends on the device, its firmware build, and its kernel. Match all three.
Click to show how the loaders work
The loaders use one of these kernel bugs:
- DirtyFrag (CVE-2026-43284) is a page-cache write bug in ESP-in-UDP decryption. A run either works or stops with an error. The loader needs a kernel module built for the device's KMI. Forks and chained loaders extend it: DirtyFalg-vr disarms vivo and iQOO
vr.kotracepoint hooks (__tracepoint_sys_exit) before loading KernelSU, DFReroot persists a system-UID app inpackages.xmlafter an initial temporary root so subsequent boots use DirtyFrag directly, and LSPromise chainsCVE-2026-49881(Android 17 TelecomInCallController->system_server, fixed in SPL2026-09-01) into DirtyFrag without Shizuku. - GhostLock (CVE-2026-43499) is a futex priority-inheritance use-after-free that gives a controlled kernel write. It is a race, so retries and kernel panics are normal. A working payload depends on the exact kernel layout.
- The Adreno GPU route (CVE-2025-21479) is a GPU command-packet defect that lets the GPU overwrite its own page tables for physical read/write. RootMyVivo, CVE-2025-21479-FX5P, and Quest
cheeseports ship it for vulnerable Snapdragon devices whose GPU firmware predates Qualcomm's June 2025 fix.
A few ports use other device-specific routes, such as a vendor service on MIUI or Honor, or a fastboot-issued permissive command line. Their table row says so.
POSIX CPU timers (CVE-2026-98260, a use-after-free on non-leader exec() fixed upstream in Linux commit acb03d388181) underpin RootMyS24, TimerRoot, SamTimer, GhostKey, Shark, and single-target 6.18.21 ports for OnePlus 16 (PYB110) and HONOR Win2 (BRM-AN00). Its CVE record lists fixed stable releases 6.1.191, 6.6.158, 6.12.112, 6.18.54, and 7.2.8, with 7.3 also marked unaffected. The same vendor-backport caveat applies.
Non-kernel privilege escalation and bootloader-unlock tools sit outside RAM-only temporary root:
- Limited / non-kernel privilege escalation (not KernelSU root):
CVE-2024-31317(Zygote injection on pre-2024-06-01SPL reaching UID1000/ app UIDs),CVE-2026-49881(TLPE, Android 17 Telecom ->system_server, fixed in SPL2026-09-01), andDirtyInit(u:r:init:s0ADB shell viaCVE-2026-43284withoutsuor KernelSU). - Bootloader unlock bypasses and boot-chain tools: Separate from temporary root; they modify partitions, AVB state, or unlock fastboot and carry factory-reset or brick risks.
CVE records give these patch floors. DirtyFrag and GhostLock affect older branches than the ones listed.
| Kernel | DirtyFrag fixed | GhostLock fixed |
|---|---|---|
| 5.10 | 5.10.255 | 5.10.261 |
| 5.15 | 5.15.205 | 5.15.212 |
| 6.1 | 6.1.171 | 6.1.175 |
| 6.6 | 6.6.138 | 6.6.140 |
| 6.12 | 6.12.87 | 6.12.86 |
| 6.18 | 6.18.28 | 6.18.27 |
| 7.0 | 7.0.5 | 7.0.4 |
Vendors backport fixes out of order and sometimes change a kernel without changing the version string, so treat these numbers as a hint. The loader's own vulnerability check decides.
It enables:
sufor apps you approve, through a KernelSU-compatible manager.- A root shell while the bootloader stays locked and the boot image stays stock.
- Modules that mount files or hook apps at runtime, for the current boot.
- A session that leaves the verified-boot chain, the stock kernel, and the recovery partitions untouched.
It does not:
- Survive a full reboot.
- Unlock the bootloader or allow unsigned images, custom ROMs, kernels, or recoveries.
- Run modules that need to start before Android, replace boot scripts, or write a partition.
- Guarantee Play Integrity, banking apps, or recovery from a bad module.
- Cover every device. A profile is built for a specific model and kernel layout.
A soft reboot restarts Android's interface and system services, not the kernel, so root and module mounts stay. A full reboot loads the stock kernel again and clears root. Files under /data/adb can remain, but nothing loads them. Do not delete that directory blindly to "unroot". It also holds module files and data other root tools rely on.
Shizuku runs a service as the shell user through ADB and is not root, though several loaders use it as a transport. adb root works only on builds that allow it. Virtual-root apps (dual-space and parallel-space tools) sandbox selected apps and never grant UID 0. Magisk, KernelSU, and APatch boot-image installs are permanent and need an unlocked bootloader. KernelSU's late-load mode is a component of temporary root, not a root method by itself.
Warning
Temporary root is full root for the session. Privilege-escalation code running in the kernel delivers it. A wrong profile or a lost race can panic the device. An incompatible module can bootloop it, and a partition write can make it unbootable. Verify the exact model, firmware build, and uname -r against the upstream project before running a loader. Back up data you cannot lose. Only use hardware you own or have explicit permission to modify.
Status shows who reported the result and what happened. Each device page includes the status definitions table. A generated profile is not a confirmed target. Check the loader's live table before running. A newer release does not inherit an older result.
Match the full kernel release your phone reports. Two phones on the same Android release can differ in kernel build, page size, and vendor hardening, so a partial match is not enough. If a kernel or tool version is missing, treat it as unknown.
Device tables, status definitions, and per-brand compatibility notes live on dedicated pages:
| Brand / group | Loaders |
|---|---|
| Samsung Galaxy | Root My Galaxy, Root My Galaxy Next, Root My Galaxy Ultra, Root My Galaxy Extended, RootMyS24, GhostSam, SamTimer, GhostKey, GhostLock-Galaxy, UniRoot, ghostlock-a17, SM-A166W port |
| Google Pixel | Root My Pixel, TimerRoot, LSPromise |
| OnePlus | ghostlock-oneplus, Anchor, Root My Device (tqmane), Shark, OnePlus 16 PYB110 kit |
| OPPO | ghostlock-oneplus, Root My Device (Witaqua), Shark, CVE-2025-21479-FX5P |
| Realme | ghostlock-rmx5085, DirtyFrag, Shark |
| vivo and iQOO | RootMyVivo, DirtyFalg-vr, Shark, yuehong-privilege-assistant, GhostLock-X200, DirtyFrag, DFRoot, iQOO Z9 / vivo T3 port, Adreno port |
| Xiaomi and Redmi | ghostlock-oneplus, Root My Device (Witaqua), DirtyFrag, GhostLock App, DFRoot, TimerRoot, Shark, CVE-2026-43499-popsicle |
| ASUS | zenfone9-ghostlock |
| Nothing | Root My Device (tqmane) |
| Honor | ANB Root, CVE-2026-98260-BRM-AN00, MnemosyneLab/ghostlock-honor |
| HMD and Nokia | DFRoot |
| Amazon, NVIDIA, Meta, Meizu, and TCL | R0rt1z2/GhostLock, GhostLock NVIDIA Shield, Root My Device (Witaqua), Meizu 20 Pro / 21 |
See the Supported Devices overview for all brand pages in one index.
These tables are maintained upstream and change more often than this README. Check your exact model, build, and uname -r. If they differ from this page, use the upstream table.
A temporary root setup needs a loader, a KernelSU-compatible manager, and whatever transport the loader uses. Some apps bundle all three.
| Tool / latest version | Method | Coverage / note |
|---|---|---|
| DirtyFrag / Latest version | DirtyFrag | Samsung-focused; other vulnerable devices/KMIs may work, on-device; no Shizuku required |
| DirtyFalg-vr / Latest version | DirtyFrag | Hardened DirtyFrag fork for vivo/iQOO (vr.ko tracepoint disarm via BTF or Rust libvrext.so boot/OTA extraction, W1c verification, fsync kmsg log, 8 LKMs 5.10 to 6.18), on-device; no Shizuku required |
| DFRoot / Latest version | DirtyFrag | Broad, manager-agnostic, on-device |
| DFReroot / Latest version | DirtyFrag (second-stage) | Persists a system-UID app in packages.xml after an initial temporary root so subsequent boots run DirtyFrag directly; tested Galaxy S26 One UI 8.5; author recommends DFRoot for simpler use |
| LSPromise | CVE-2026-49881 + DirtyFrag |
Android 17 untrusted_app -> KernelSU chain without Shizuku; Pixel 10 initial Android 17 release tested (pre-2026-09-01 SPL); fails on Pixel 6a / 6.1.xxx-android14 |
| yuehong-privilege-assistant / Latest version | Multi-method | Multi-method launcher (roro.stellar.yuehong, Android 10+, arm64) integrating Stellar wireless debugging, DirtyFalg-vr, GhostLock, GhostKey, and vivo/iQOO wired OTG mode |
| Shark (kpgc10kai fork) / Upstream releases | 98260 UAF | One-tap temp root + hot manager switching (KSU-Universal: KernelSU, KernelSU-Next, BakaSU, SukiSU Nova/Ultra, FinaSU) across 7 chains (6.6.118 to 6.18.21) for OnePlus, OPPO, Realme, vivo/iQOO, Xiaomi 18 Pro; Shizuku/Stellar; Yunnijian/Shark source repo removed Nov 2026 |
| UniRoot / Latest version | DirtyFrag + GhostLock | Samsung Galaxy, on-device; V5 is DirtyFrag-first with an in-app ksud patcher and no Shizuku, while the classic GhostLock path is retained; Galaxy A15 4G confirmed |
| GhostSam / Latest version | Both | Galaxy S22, S26, Z Fold8, ADB |
| GhostLock App / Latest version | GhostLock | Multi-brand uname -r profiles, on-device/ShizukuUser-reported success on the Redmi Note 14 4G with v1.2 |
| Root My Galaxy / Latest version | GhostLock | Selected Galaxy builds, on-device/Shizuku |
| Root My Galaxy Next / Latest version | GhostLock + DirtyFrag | Independent fork of Root My Galaxy; KernelSU, KernelSU-Next, and BakaSU (ReSukiSU) payload flavours, on-device/wireless ADB/Shizuku |
| Root My Galaxy Ultra / Latest version | GhostLock + DirtyFrag | Fork of Root My Galaxy Next for Galaxy S26 Ultra (m3q), on-device/Shizuku; KernelSU, KernelSU-Next, BakaSU, and KowSU managers |
| Root My Galaxy Extended / Latest version | GhostLock + 98260 UAF | Fork of Root My Galaxy for Galaxy S25 series (SM-S931B, SM-S936B unvalidated, SM-S937B CZF1, SM-S938B CZG3/CZZI4 One UI 9 beta), on-device/Shizuku |
| SamTimer | 98260 UAF | Samsung Galaxy CVE-2026-98260 Shizuku app -> KernelSU-Next 3.4.2 (ksud-next-generic-kdp), auto-root + safe-boot module disabler; tested SM-S921N (6.1.162, One UI 9) |
| GhostKey / Latest version | 98260 UAF | Ongoing CVE-2026-98260 Shizuku port targeting Galaxy S25 Ultra (SM-S938B, 6.6.127 One UI 9) |
| Root My Pixel / Latest version | GhostLock | Pixel 6 to 11, Shizuku; retries common |
| TimerRoot / Latest version | 98260 UAF | Pixel 6 to 11 and selected Xiaomi/Redmi kernels, Shizuku; Pixel 7a and 9a hardware-tested, other Pixel 6 to 11 profiles QEMU-only; exact uname -r and page size required |
| RootMyVivo / Latest version | GhostLock + DirtyFrag | vivo/iQOO GhostLock and DirtyFrag targets, Shizuku/ADB |
| Root My Device (Witaqua) / Latest version | GhostLock | Xiaomi 17T Pro, 14T Japan, Quest 3, on-device |
| Root My Device (tqmane) / Latest version | GhostLock | Nothing Phone (3a), OnePlus Pad 3, Shizuku |
| RootMyS24 / Latest version | GhostLock + 98260 UAF | Selected Galaxy S24/S24 Ultra, Z Flip6, Z Fold6 CN builds, Shizuku/ADB; see exact target notes |
| GhostLock-Galaxy / Latest version | GhostLock | Galaxy Z Fold6 SM-F9560, ADB/Shizuku |
| ghostlock-oneplus / Latest version | GhostLock | OnePlus, Xiaomi, OPPO, ADB |
| GhostLock-for-OnePlus / Latest version | GhostLock | Ace 6T, OnePlus 15 PLK110, ADB |
| ghostlock-a17 / Latest version | GhostLock | Galaxy A17 SM-A175F, ADB; shell only |
| R0rt1z2/GhostLock / Latest version | GhostLock | Amazon Fire devices and TCL T653T02, ADB; 4.14 is the default branch, with 5.4, 4.4, 5.10, and 5.15 branches for other targets; choose the exact kernel branch |
| GhostLock NVIDIA Shield / Latest version | GhostLock | Shield TV Pro 2019, ADB; no su |
| cve-2025-21479_iqooneo8 / Latest version | Adreno GPU | iQOO Neo8 SM8475 on 5.10.198, ADB; pre-Jun-2025 GPU |
| GhostLock-X200 / Latest version | GhostLock | vivo X200 PD2415 b57, PC or companion app |
| MT6989-ghostlock Unavailable |
GhostLock | Historical vivo T3 Ultra V2426 target; repository unavailable |
| ANB Root / Latest version | GhostLock | HONOR 80 Pro Flat ANB-AN00, Shizuku; single MagicOS build; signing-key migration |
| Redmi K70 Pro temp root / Latest version | MIUI service | Redmi K70 Pro (manet), HyperOS 3/Android 16, PC + ADB/fastboot |
| ghostlock-s26 / Latest version | GhostLock | Galaxy S26 series, ADB; merged into GhostSam |
| IonStackQuest3 / Latest version | GhostLock | Quest 3 listed incrementals, ADB; newer builds patched |
| DirtyInit / Latest version | DirtyFrag | Samsung devices with the page-cache write bug, ADB; hooks init (u:r:init:s0) for a dirtyinit socket shell, not KernelSU/su |
DirtyFrag's latest checked release is v1.17. It stages ksud from the selected manager's libksud.so. Samsung requires diabl0w's KernelSU build. Other devices can use the managers upstream names. Since v1.17, LKM selection uses the kernel's GKI level and vendor Android release rather than the marketing Android version. Read the run log and stop if the kernel has no supported module.
Click to show which kernel modules each loader ships
GhostSam ships one DirtyFrag module per KMI and marks its set as follows. DirtyFrag also builds modules per KMI. Its repository contains the prebuilt set. These are upstream module statuses, not verification labels from this repository. The KMI is not the full target. Two phones on the same KMI can still differ in kernel build, page size, and vendor hardening.
| KMI | Status | Notes |
|---|---|---|
android12-5.10 |
Tested | |
android13-5.10 |
Untested | |
android13-5.15 |
Tested | |
android14-5.15 |
Untested | |
android14-6.1 |
Partial | Kernels up to 6.1.71; later 6.1 builds are not supported by this module. |
android15-6.6 |
Tested | |
android16-6.12 |
Tested | |
android17-6.18 |
Untested |
Other device-specific ports:
- ghostlock-emerald for POCO M6 Pro 4G.
- zenfone9-ghostlock for ASUS Zenfone 9.
- ghostlock-rmx5085 for Realme GT 7T.
- Meizu 21 GhostLock for Meizu 21, and meizu20pro-temp-root for Meizu 20 Pro (
meizu_20Pro_CN, Flyme12.6/12.7,5.15.119). - iQOO Z9 / vivo T3 port for iQOO Z9 5G and vivo T3 5G.
- ghostlock-xringo1 for XRING O1 on
6.6.77and6.6.118. - SM-A166W port for Galaxy A16 5G.
- OnePlus 16 PYB110 kit for OnePlus 16 (
PYB110,6.18.21ColorOS 17 / Android 17,CVE-2026-98260-> KernelSU or FinaSU). - HONOR Win2 BRM-AN00 port for HONOR Win2 (
BRM-AN00,6.18.21MagicOS 11 / Android 17,CVE-2026-98260-> BakaSU). - CVE-2026-43499-popsicle for Xiaomi 17 / Pro / Ultra (
6.12.23,CVE-2026-43499; caveat: new apps crash after exploit until reboot). - CVE-2025-21479-FX5P for OPPO Find X5 Pro (
PFEM00,5.10.168/5.10.198, Adreno KGSLCVE-2025-21479-> KernelSU 3.3.0). - cheese, eureka_panther-adreno-gpu-exploit-1, and cheese-cake for Adreno A7xx (
CVE-2025-21479) on pre-August 10, 2025 Meta Quest 3 / 3S and Snapdragon 8-class builds.
A multi-device repack can bundle legitimate payloads and still add code. Do not treat one as a trusted upstream, and do not grant root to a loader you cannot identify.
| Manager | What it is | Use it for |
|---|---|---|
| KernelSU | Upstream kernel-based root manager | GKI devices; late-load support |
| KernelSU-Next | KernelSU fork | Devices a loader names it for |
| KowSU | KernelSU fork | Alternative manager for loaders that support it |
| SukiSU Nova | KernelSU fork, formerly SukiSU Ultra | Pixel TimerRoot profiles and other targets that name it or SukiSU Ultra |
| BakaSU | KernelSU fork, formerly ReSukiSU | Pixel profiles and other targets that name it; payload feeds still label the flavour resukisu |
| diabl0w KernelSU | Samsung-patched KernelSU | Samsung DirtyFrag and several Galaxy ports |
Use the manager the loader names. On Samsung, use diabl0w's build. A manager alone does not provide temporary root.
Click to show why the manager choice matters
The manager must provide libksud.so, the library a loader uses to stage ksud on the device. A manager without that library cannot produce root. Use a build from the project itself.
The driver is the kernel module the loader stages, and it is fixed for the boot. Some managers check its UAPI and refuse to run, or show an update banner, when the manager is newer than that driver. That is a match problem, not a missing app update: install a manager build whose UAPI matches the staged driver, then reboot before changing the manager family. Loaders that pin a manager link, and forks such as Root My Galaxy Next and Root My Galaxy Ultra that choose a manager from the payload or backend, exist to keep that pairing consistent.
Do not use a manager's install, flash, or patch-boot-image actions on a locked phone. Those actions write protected partitions and can hardbrick the device.
| Tool | What it does | Why it matters |
|---|---|---|
| Shizuku | ADB-privileged API bridge, runs as the shell user | Several loaders stage payloads through it. It is not root. |
| Anchor | One-tap launcher for the ghostlock-oneplus chain | Sets up local ADB with its own key. Requires a one-time adb tcpip 5555 setup |
| Android Platform Tools | adb, fastboot |
Build checks, logs, sideloading, uninstall recovery |
| Termux | Terminal emulator | uname -r, su, and on-device checks |
| Obtainium | APK updates from GitHub releases | Keeps loaders on the project's release channel |
- Download from the project's own release page. Avoid reuploads, Telegram mirrors, paid builds, and remote-root services.
- Check the release tag and date, and compare published hashes or signing certificates when the project provides them.
- Build from source when you can. A clean VirusTotal result is not proof that an exploit APK is safe.
Click to show limited / non-kernel privilege escalation tools
These tools reach a limited privilege level (such as system_server UID 1000 or app-UID Zygote injection) rather than kernel root, or require an already permissive SELinux state:
| Tool | Mechanism / CVE | Scope and limitations |
|---|---|---|
| TLPE | CVE-2026-49881 (Telecom InCallController) |
Android 17 untrusted_app -> system_server (UID 1000), not kernel root; fixed in Android SPL 2026-09-01 (used as stage 1 in LSPromise) |
| zygote-CVE-2024-31317 | CVE-2024-31317 (Zygote command injection) |
Android 14 and earlier up to SPL 2024-05-01 (fixed in 2024-06-01); grants UID 1000 or app UID under SELinux, not kernel root |
| Magica | Zygote seccomp disable (archived) | Android 10 to 16 diagnostic/utility flow; requires SELinux permissive or existing privilege, not an exploit by itself |
Click to show bootloader unlock and AVB/preloader tools (separate scope and higher risk)
[!WARNING] Unlike RAM-only temporary root, these tools modify bootloader state, AVB metadata, or protected partitions, often trigger a factory reset, or require BROM/EDL/hardware access. Misuse can permanently brick a device.
| Tool | Target / SoC | What it does |
|---|---|---|
| QuestStack | Meta Quest 1 (49845030443200410), Quest 2 (50670960048600150 web) |
Chains GhostLock with CVE-2021-1931 ABL downgrade to unlock the bootloader (factory-resets device) |
| gbl_root_canoe | GBL / UEFI Android boot chain | Boot-chain / GBL-level unlock and root research |
| qualcomm_avb_exploit_poc / qualcomm_noavb_exploit_common | Qualcomm (NO_AVB, archived) |
Qualcomm AVB bypass PoC and helper framework for qualifying unverified boot chains |
| oppo-mtk-fastboot-unlock | MediaTek OPPO / OPlus | Unlocks fastboot on susceptible MediaTek OPPO models |
| kaeru / fenrir | MediaTek (lk / preloader) |
kaeru spoofs unlock state / bypasses boot checks on supported MTK chains; fenrir was archived and deprecated in September 2026 |
| mtkclient | MediaTek BROM / preloader | Low-level BROM/EDL dump, flash, and bootloader unlock utility |
Click to show where to ask about porting
Porting a temporary-root solution to a specific device is out of scope here. Use the relevant upstream project for development and device-specific help. These references explain why a generated profile is only a candidate: the GhostLock App porting guide, the Root My Galaxy payload notes, or the ghostlock-oneplus README.
Temporary root can run modules that mount files or hook apps after Android starts. It usually cannot run modules that need early boot, boot-script replacement, kernel drivers, or partition writes.
Full uncollapsed compatibility tables, status labels, not-recommended entries, and risk-reduction rules live on Modules and Apps:
- Module list: Metamodules, Zygisk providers, Xposed forks, hiding, audio, performance, and system patches.
- App list: Root apps and Xposed modules for ad blocking, HyperOS, One UI, backup, and networking.
- Not recommended: Modules and tools with reported bootloop or hardbrick risk on locked bootloaders.
- Reducing module risk: One-at-a-time soft-reboot testing and recovery steps.
Temporary root does not replace recovery or flash a boot image. Device-specific loaders often need stock kernel and boot artifacts for analysis or offset extraction. Use these resources to obtain firmware for your own device for those purposes or for recovery. Do not use them to distribute proprietary images.
| Resource | What it provides | Notes |
|---|---|---|
| Bifrost | Cross-platform Samsung firmware downloader by model/CSC | Community download tool, not a flashing tool; availability depends on Samsung's servers. The former SamsungFirmware/Server link is unavailable. |
| Odin (unofficial mirror) | Samsung flash tool | Verify the download's provenance; restore only signed stock firmware for the exact model/region if download mode works |
| Google Pixel factory images | Official Pixel factory images | Boot.img for Pixel KMI/offset derivation |
| vivo kernel/target references | RootMyVivo payload catalog | Exact kernel builds and payload references per vivo/iQOO model; not a boot-image mirror |
| NVIDIA Shield firmware | Shield Experience images | mdarcy 9.2.4 target image |
Firmware images are proprietary. Download them only from the vendor or the project that distributes them, and only for devices you own. This site does not host or mirror any firmware, boot image, or APK.
Primary sources for temporary-root research. These document the exploits, offsets, and porting workflows. They are not root tools.
| Resource | What it covers |
|---|---|
| NebuSec IonStack (CyberMeowfia) | Original IonStack PoC for CVE-2026-43499 (GhostLock) |
| GhostLock App porting guide | Kernel profile porting, uname -r matching, MediaTek kernel_phys_load/kernel_phys_offset |
| Root My Galaxy payload notes | Samsung per-build offsets and payload structure |
| ghostlock-oneplus offset extraction | extract_target.py, extract_btf.py, stack-layout feasibility |
| DirtyFrag / DFRoot | DirtyFrag (CVE-2026-43284) technique and page-cache write capability |
| DirtyFalg-vr | vivo vr.ko tracepoint disarming and libvrext.so boot/OTA offset extraction for DirtyFrag |
| V4bel InfinityCore | Disclosure of CVE-2026-98260 (POSIX CPU timers UAF) and related Linux kernel LPEs |
| vivo/iQOO 6.6.127 CVE-2026-98260 notes | Porting analysis for iQOO Z10 Turbo Pro (PD2453, 6.6.127) without exploit binaries |
| Xiaomi nezha CVE-2026-98260 port | Target-specific CVE-2026-98260 porting notes for Xiaomi nezha (OS4.0.4.0) |
| rootWithoutUnlockBootloaderList | Community taxonomy of locked-bootloader root, GBL/ABL, and unlock bypass tools |
| CVE records | CVE-2026-43284, CVE-2026-43499, CVE-2026-98260, CVE-2026-49881, CVE-2025-21479, CVE-2024-31317 |
-
Record the exact target. Save the model, firmware build, Android version, security patch, and full kernel release where you can read them after a reboot.
adb shell getprop ro.product.model adb shell getprop ro.product.device adb shell getprop ro.build.display.id adb shell getprop ro.build.version.release adb shell uname -r
Without a computer, the About phone page in Settings gives the model and build.
uname -rin Termux gives the kernel. -
Match the exact build upstream. Use Supported devices for a confirmed starting point, then open the loader's own live table. If the project does not list your exact model, build, and kernel, stop. Do not try the closest one.
-
Back up and plan recovery. Copy data you cannot lose, and know how to reach safe mode, download mode, or a service center for that model before you run anything.
-
Install the manager the loader names. Open it once to register its services. Do not use its install, flash, or patch-boot-image actions. On Samsung with DirtyFrag, use diabl0w's KernelSU build.
-
Run the loader. Install it from the upstream release page. Grant the permissions or transport it asks for. Confirm it detected the expected model and kernel, then start the run and keep it in the foreground. Do not start a second run while the first is still working.
-
Verify, then test modules one at a time.
adb shell su -c id
Expected output starts with
uid=0(root). The SELinux context can differ. Ifsuis missing, the exploit may have completed while the late-load failed. See Troubleshooting. Install one module, soft reboot, and test. A soft reboot keeps root. A full reboot clears it. Use the manager's soft-reboot action rather thanadb reboot.
Nothing in this workflow flashes, patches, or installs a boot image. If a guide asks you to, it is a permanent-root procedure.
Click to show GhostLock panics or reboots instead of finishing
A GhostLock panic is a failed attempt at a race, not by itself a brick. Wait for the phone to reboot, then retry if the build is supported. Stop if it panics at the same stage every time, if it bootloops with modules disabled, or if it becomes unusually hot.
A DirtyFrag panic more often points to a wrong KMI, a profile mismatch, or vendor hardening rather than timing.
Click to show Samsung shows "reboot device - d2" or will not enter download mode
There are two causes. The download-mode gate on One UI 8.5 and later refuses download mode while a lock-screen credential is set. Android still boots. Remove the screen lock, power off, hold Volume Up and Volume Down together, then connect USB.
A modified protected image is different. The bootloader rejects it and Android does not boot. Key combinations will not help. If the phone does not appear over USB, contact Samsung or a repair service. If download mode opens, flash signed stock firmware for the exact model and region with Odin. Do not mix firmware from another model, and do not use a "D2 bypass" APK.
Click to show ADB does not list the device or says unauthorized
Check the cable, port, and USB debugging setting, then run adb devices again. For unauthorized, unlock the phone and accept the RSA prompt. For no devices, try another cable and port and check lsusb. Pair wireless debugging before it appears.
Click to show The loader reports "not vulnerable" or "patching failed"
The kernel is patched, the vendor backported a fix, or the build has an accidental mitigation. There is no app-side fix, and downgrading firmware on a locked phone can wipe data or brick it. Check the upstream issue tracker and stop.
Click to show Does temporary root survive a full reboot?
No. A full reboot loads the stock kernel, unloads the module, and removes the su daemon and module mounts. Files under /data/adb can remain but are inactive. If the build is still supported, run the loader again.
Click to show Does a soft reboot keep root?
Usually. A soft reboot restarts Android's userspace and system_server, not the Linux kernel, so the late-loaded module stays and module mounts reactivate. That is why module installs often ask for one. adb reboot is a full reboot.
Click to show Does the method unlock the bootloader or wipe data?
No. It does not unlock the bootloader, and there is no unlock-induced wipe. A failed run, a module bootloop, or a recovery attempt can still cost data, so back up first.
Click to show How do I know whether my device is supported?
Record the model code, build display ID, and full uname -r, find the device in Supported devices, then confirm the target in the loader's live table. If the exact build is missing from both, stop.
Click to show Why does the exact kernel build matter?
Offsets come from a specific kernel build. Compiler settings and vendor hardening change the layout. A 4K-page profile does not cover a 16 KB page build. A vendor can backport the fix without changing the version string. An OTA can move the build or close the bug, so recheck before updating.
Click to show Do I need a computer or Shizuku?
Not always. DirtyFrag, Root My Galaxy, GhostLock App, RootMyVivo, and Root My Device can run on the phone itself. Root My Pixel needs Shizuku, which can be started over wireless debugging without a PC. Some profiles need a one-time ADB setup, and command-line ports are easier from a computer. Shizuku is an ADB bridge, not root.
Click to show Which root manager should I install?
The one the loader documents. Samsung DirtyFrag requires diabl0w's KernelSU build. Root My Pixel expects the BakaSU manager named in its README. Root My Galaxy Next follows the flavour of the payload it resolves, and Root My Galaxy Ultra follows the backend chosen in its settings. A manager alone does not give temporary root. If a manager asks for a kernel update while the app is current, match its UAPI to the loaded driver instead of reinstalling root.
Click to show Which modules can work?
Modules that mount files or hook apps at runtime can work. Modules that need to start at early boot, replace boot scripts, load a kernel driver, or write a partition generally cannot. See Modules, install one at a time, and keep the loader's module-disable switch reachable.
Click to show Root is missing after a run that looked successful
The exploit likely completed and the late-load failed. Check that you installed the manager the loader names, selected it in the loader, and matched the kernel. Disable auto reboot if it is on, then run again and read the log. If the log shows a patched kernel or a profile mismatch, stop.
Click to show The manager says update required but it is the newest release
That banner is a UAPI match check between the manager and the late-loaded driver, not a notice that a newer app exists. The driver is the module the loader staged for this boot, so it cannot be updated without a fresh root run, and a newer manager release can require a newer driver than the loader ships. Install a manager build whose UAPI matches the staged driver. Many loaders pin one, and KernelSU-Next publishes development manager builds in its Build Manager CI workflow. Then open the manager and confirm the backend is working before testing su. Re-rooting does not change the banner, a manager-spoofed artifact uses a different package ID, and GitHub CI artifacts expire, so prefer the loader's link or the project's own repository.
Click to show What do I do after a module bootloop?
A full reboot clears root and the kernel module. Open the loader, set modules to disabled, run it again, and remove the module. DirtyFrag's module switch works without root.
If Android does not start, try safe mode. Hold Volume Down during boot. Android may also offer it after repeated crashes. Safe mode may not disable a late-loaded kernel module, so the loader switch remains the reliable path. On a user build, adb uninstall <loader-package> removes the loader without root. If the phone does not appear over USB and neither recovery nor download mode opens, stop and seek service support.
Click to show Will banking apps or Play Integrity work?
Maybe, but nothing here guarantees it. A locked bootloader helps some checks, while root, manager packages, module files, and SELinux state are all detectable. Strong integrity verdicts usually fail. Test the app before you depend on it.
Click to show How do I report a new device or module result?
Open an issue or pull request with the exact model, build, full uname -r, Android version, loader and manager versions, module version, result, and the relevant log tail. Use the templates linked from Contributing. Attach the log tail and exact build so someone else can repeat the run.
Read CONTRIBUTING.md before opening an issue or pull request. Use the concise device-report, module-report, or correction template.
- Maintainer Verified is reserved for results supplied or directly confirmed by this repository's maintainer, with a linked report.
- User Reported identifies community evidence that the maintainer has not independently verified. Accepting a report does not promote it to maintainer verification.
- Tested, Experimental, and the module outcome labels describe results, not who verified them. Keep missing information explicit and do not infer broader device support.
This index collects knowledge and links to public projects. Requests to develop or port a root solution for a particular device belong in the relevant upstream project, not here. Report loader bugs upstream. Report stale or incorrect index entries here.
Contributions must cite primary sources, preserve uncertainty, and exclude credentials, personal data, proprietary firmware, and APK reuploads. Edit README.md, docs/modules/index.md, or the brand pages under docs/devices/, then run bun run sync:readme. The script generates docs/guide.md.
Content is MIT licensed. Contributions are accepted under the same terms. Linked tools carry their own licenses and documentation.
This is a community-maintained index. It does not develop, audit, or guarantee the linked projects, and it is not affiliated with Google, Samsung, KernelSU, NebuSec, or any loader maintainer. Use these tools only on devices you own or have explicit permission to modify.
Click to show primary sources
- CVE records: CVE-2026-98260, CVE-2026-43284 (NVD), CVE-2026-43499 (NVD). KernelSU: module guide, bootloop rescue.
- Device and profile sources: Root My Galaxy payloads, GhostLock App supported devices, RootMyVivo catalog, Root My Device payloads, Root My Device project.
- Loader documentation: ghostlock-oneplus, GhostSam, GhostLock-Galaxy, R0rt1z2/GhostLock branches, GhostLock NVIDIA Shield, ghostlock-a17, ghostlock-s26, GhostLock-X200, ANB Root, cve-2025-21479_iqooneo8, redmik70pro, Root My Galaxy Next, Root My Galaxy Ultra, Root My Galaxy Extended, DirtyFalg-vr, Shark (kpgc10kai fork), Shark Releases, yuehong-privilege-assistant, DFReroot, LSPromise, SamTimer, GhostKey, OnePlus 16 PYB110 kit, HONOR Win2 BRM-AN00 port, CVE-2026-43499-popsicle, CVE-2025-21479-FX5P, meizu20pro-temp-root.
- Research, managers, and boot-chain references: SukiSU Nova, V4bel InfinityCore, TLPE, cheese, QuestStack, gbl_root_canoe.
- Manager version matching: KernelSU-Next UAPI check, Build Manager CI, Root My Galaxy Ultra manager table.
- Module/app compatibility: community lists from r/androidroot and r/HyperOS, and the XDA testing thread.
- Maintainer reports: Redmi Note 13 4G (sapphire), DirtyFrag, NeoZygisk confirmation.
- Update checks: DirtyFrag v1.17, RootMyVivo 1.4.3, Root My Galaxy Ultra 1.4.2, TimerRoot
timer-p7abeta, RootMyS24 supported firmware, ANB Root v2.4.0, HMA late-load issue #130. - Background: awesome-android-root, NebuSec IonStack.