GhostLock-App

中文: README_ZH.md

Supported Devices

Kernels are matched by exact uname -r; unsupported builds are rejected and the app shows the status at the top. Offsets live in src/kernels/<uname-release>/offsets.h — add new builds with the extractor's --register.

Quick Start

Open GhostLock and tap Run. KernelSU (me.weishu.kernelsu) or ReSukiSU (com.resukisu.resukisu) provides ksud for module loading; without it, W1/W2 still grant uid 0 but no module is loaded.

The route races two cores: the main thread hammers pselect while a consumer thread perturbs the waiter's priority. The pair defaults to the big cores (fallback 0/1), overridable via GHOSTLOCK_CORE / GHOSTLOCK_CONSUMER_CORE.

Command-Line Debugging

adb/shell has no seccomp filter, so W3 is skipped - handy for quick verification:

make ghostlock
adb push ghostlock /data/local/tmp/ghostlock
adb shell chmod 755 /data/local/tmp/ghostlock
adb shell /data/local/tmp/ghostlock

Offset Extraction

tools/extract_rs derives offsets from a boot.img (plus optional xbl_config.img), a full OTA ZIP, or an http(s) URL pointing at one. kallsyms come from --kallsyms or are recovered from the image's embedded table. pselect_waiter_shift and off_slide_loggers_0_1 are derived by the built-in arm64 disassembler. MediaTek images have no xbl_config.img and usually no BTF: the physical load address is derived from kallsyms _text (override with --phys).

cargo build --release --manifest-path tools/extract_rs/Cargo.toml
tools/extract_rs/target/release/ghostlock-extract.exe boot.img --xbl-config xbl_config.img --register
tools/extract_rs/target/release/ghostlock-extract.exe OTA.zip --format json --out offsets.json

--register saves the table under src/kernels/<uname-release>/offsets.h; --format c --out offsets.h dumps a standalone header.

On-device analysis

A full OTA can be analyzed entirely on the phone: boot plus xbl_config are extracted automatically. Pass --work-dir an app-writable dir when running inside the app sandbox. Cross-compile and push:

rustup target add aarch64-linux-android
$ndk = "$env:ANDROID_HOME\ndk\29.0.14206865\toolchains\llvm\prebuilt\windows-x86_64\bin"
$env:CC_aarch64_linux_android = "$ndk\aarch64-linux-android35-clang.cmd"
$env:AR_aarch64_linux_android = "$ndk\llvm-ar.exe"
$env:CARGO_TARGET_AARCH64_LINUX_ANDROID_LINKER = $env:CC_aarch64_linux_android
cargo build --release --target aarch64-linux-android --manifest-path tools/extract_rs/Cargo.toml
adb push tools/extract_rs/target/aarch64-linux-android/release/ghostlock-extract /data/local/tmp/
adb shell /data/local/tmp/ghostlock-extract /sdcard/OTA.zip

Importing offsets without rebuilding the app

New kernels no longer need an app rebuild: tap Import offsets.json and pick the extractor's JSON (single object or array), or push it to <GHOSTLOCK_HOME>/offsets.json (default /data/local/tmp). At startup native matches the current uname -r against imported entries before rejecting the kernel. Imports merge across files; a release already stored prompts before overwrite.

The app can also generate the JSON itself — Parse OTA link (full OTA ZIP URL) and Parse image (boot.img + optional xbl_config.img) run the extractor in-process and write offsets.json into the app data dir on success.

[{
  "release": "6.12.38-android16-5-g844001fb8721-ab14552068-4k",
  "kernel_phys_load": 3347054592,
  "pselect_waiter_shift": 0,
  "symbols": { "off_init_task": 37801728, "off_init_cred": 37891184 },
  "struct_fields": { "task_prio": 148, "task_cred": 2304 }
}]

Credits & License

Based on the following projects, licensed under Apache License 2.0 (see LICENSE):

• NebuSec/CyberMeowfia
• JoinChang/ghostlock-oneplus
• x-spy/CVE-2026-43499-popsicle