Repository navigation
Report a problem
mpse-engineering edited this page Oct 14, 2026
·
1 revision
- how you got the kit:
- git clone — record both:
git rev-parse HEAD= ____________________________ and the tag/branch you have (git describe --tags): ____________________________ - ZIP — the exact ZIP filename: ____________________________
- tarball from the maintainer directly — its sha256 (all 64 chars): ____________________________
- git clone — record both:
-
./verify.shverdict (it prints ALL CHECKS PASS on healthy copies; works inside a git clone as-is):
- phone model (
adb shell getprop ro.product.model): ______________ - firmware build ID (
adb shell getprop ro.build.display.id): ______________ - step02 fingerprint line (the exact line prepare.sh/step02 printed and accepted on your copy): ____________________________
- distro (
head -1 /etc/os-release): ______________ - kernel (
uname -r): ______________ - guide chapter 4 done (USB access ruled sane)? yes/no: ____
- Script + step number that failed: ____________________________
- Last ~30 terminal lines, verbatim (no screenshots of text):
(paste here) - Log filename in logs/ (the file itself, not pasted text, for the issue attachment): ____________________________
- Did insurance complete green in this workspace before the failure? yes/no: ____
- If a root step: did the Magisk app show "Installed"? Version?
- boot loops? yes/no: ____
- reaches stock home screen? yes/no: ____
-
adb devicessees it? yes/no: ____ - download mode reachable (power off ~10 s, hold VOL_UP, plug USB)? yes/no: ____
One sentence, what you think went wrong:
No personal data, account names, IMEI, or serials in the issue. The
kit's logs/ files contain partition fingerprints, not personal data —
paste/attach those freely. Replace anything personal with [redacted]
before posting.