GhostLock-X200 v1.0 - temporary root toolchain for vivo X200 (PD2415 / b57 kernel) based on CVE-2026-43499. For authorized security research only.
⚠️ Legal and Safety Notice (Please Read First)
This repository is intended solely for security research and educational purposes, and may only be used on devices that you own or for which you have obtained explicit written authorization. Using this tool on others' devices without authorization may violate local laws and regulations. Using this tool may cause abnormal device reboots, data corruption, system anomalies, warranty voidance, and other consequences; please assess the risks yourself. The authors assume no liability for any direct or indirect damages, and are not responsible for any misuse. By continuing to read or use this repository, you indicate that you understand and agree to bear all risks and responsibilities yourself.
A temporary root toolchain for vivo X200 (PD2415 / Dimensity 9400 / b57 kernel), based on the CVE-2026-43499 (GhostLock) kernel vulnerability: no Bootloader unlocking required, no flashing required, and no data wiping. Running it grants temporary root, which is lost after a reboot.
Features • Supported Devices • Differences from Other Projects • Quick Start • How It Works • Directory Structure • License
root.ps1: automatically detects device and kernel, automatically installs missing dependencies, automatically generates offsetslog\, and on panic/watchdog it automatically
collects pstore and other diagnostics and packages them (AI-readable); just send them as prompted for analysisdevices/<device name>/;
for devices not yet included, offsets can be extracted automatically and a module generated; however, apart from X200 b57, whether other
devices can be rooted must be tested and adapted by yourself (the ko must be recompiled with vermagic/modversions for the target kernel);
the tool only provides automatic extraction and feasibility pre-checks (warnings such as init_boot misselection, unknown MTK family, etc., recommend against proceeding)to be filled, a four-level automatic fill chain
permissive_restore kernel module, which fixes KernelSU's network/hotspot anomalies on this device in enforcing
mode (see "Differences from same-origin projects" below)| Device | System / Kernel | Status |
|---|---|---|
| vivo X200 (PD2415) | 16.1.12.2.W10 (tested and verified) | ✅ Available |
| vivo X200s | 16.1.12.12.W10 (same b57 kernel: kernel SHA256 identical to X200, offset cross-validation consistent with third-party verified target.h; not tested on a physical device) | ⚠️ Can try (exact match to x200_b57 module on the same kernel, verify yourself) |
| vivo X200 (PD2415) | 16.1.12.12.W10 (same kernel build b57) | ⚠️ Not tested |
| vivo X200 (PD2415) | Other 16.1.x, kernel b57af212129c | ⚠️ Not tested, can try |
| vivo X200 (PD2415) | Kernel >= 6.6.140 | ❌ Fixed, unavailable |
| iQOO Neo11, etc. (same 6.6.89 MTK kernel) | Same kernel | ⚠️ Not tested, requires your own secondary development |
前提:内核 < 6.6.140(CVE-2026-43499 未修复)且构建为
6.6.89-android15-8-gb57af212129c。未实测的机型/构建需要自行验证。完整说明见
使用说明。
适配口径:本项目仅对表中标 ✅ 的 vivo X200(PD2415 / 16.1.12.2.W10 / b57 内核)做过完整真机适配。其余所有机型(含同内核的 X200s)均为 未实测 / 需自行适配:偏移可自动重建、ko vermagic 可自动重打,但能否 root 不保证,需按目标机型/内核自行二次开发(modversions ABI 需同构建内核 源码重编 ko)。
其他机型:非官方支持列表的机型允许强行尝试,工具不会阻止运行;偏移会 自动从素材重建,运行中异常重启会自动打包诊断日志。最终能否 root 取决于目标 机型/内核的二次开发适配(模块 vermagic 需按目标内核重新编译),需自行适配, 不保证直接可用。
MTK 机型可行性提示:除已实测的 b57 族外,MTK(天玑/helio)未知 内核族不推荐投入——社区公开记录(vivo PD2241/天玑9200)显示 KernelSnitch 时序在 MTK 上不可靠(KASAN_HW_TAGS/MTE 干扰、PANIC_ON_OOPS 无试错空间、 vivo RSC 调度器破坏 pselect/pi 链)。运行本工具选素材时会自动预检并提示。
permissive_restore 模块
修复 enforcing 下 KernelSU 网络/热点异常,并提供一键脚本、动态偏移重建与
异常重启自动诊断。本仓库为 PC 版工具链;如需在手机端直接一键 root(通过 [Shizuku]
(https://github.com/RikkaApps/Shizuku) 授权,无需电脑 adb),请使用配套的
ghostlock-x200-app。两者共用
同一套提权链与机型模块(PC 版 devices/<id> → App 版 payload/<id>)。
下载 Release 资产 ghostlock-x200-root-v1.3.4.zip 并解压(zip 内含
prebuilt/ 二进制与 modules/*.ko,缺一不可);
唯一入口:双击 run_root.bat(运行结束后窗口停留,报错不闪没);或命令行:
powershell -ExecutionPolicy Bypass -File root.ps1
Run logs and abnormal restart diagnostic packages are stored uniformly in the log\ folder within the package
(log\ghostlock_root_<timestamp>.log / log\ghostlock_diag_<timestamp>.zip,
the console will print the full path); send the diagnostic package to the maintainer/Agent for analysis as prompted.
For advanced usage such as multi-device adaptation, offline offset generation, device module sharing, and new device compilation, see Usage Guide docs/USAGE.zh-CN.md.
Seven-stage chain: permissive (SELinux) → kptr → KASLR base → dynamic offsets → ko relocation → cred leak + CAPSROOT → load permissive_restore/kernelsu → restore permissive after 25s. For architecture and component descriptions, see docs/ARCHITECTURE.zh-CN.md.