Repository navigation
unlock bootloader on helio g100 (xiaomi redmi note 15 4g code: spinel) #436
Unanswered
miko-ko-byte
asked this question in
Q&A
Replies: 1 comment
|
Hello! Regarding unlocking... You can try patching the LK. However, it's worth keeping in mind that even if everything works and bootloader is unlocked, you should be aware that flashing a stock LK will lock the bootloader. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Summary: Carrier-locked official unlock isn’t an option. Tried the eng-preloader + eng-firmware route, then the RPMB magic erase method from this repo. seccfg unlock reports success every time, but the magic comes back before fastboot ever shows up, and fastboot oem unlock fails outright.
Steps taken (chronological):
Official Mi Unlock blocked due to carrier lock.
Flashed an “eng” preloader sourced from a Russian forum (unverified). Phone boots slower afterward; some tools now report “brom” state.
Flashed a full eng firmware (sourced from YouTube). Phone now reports Android 15 in some places but behaves/looks like Android 11, with an Android 5-era boot logo and unfamiliar bundled apps - likely a franken-build, provenance unclear.
Enabled “OEM unlocking” in Developer Options - this stuck.
fastboot oem unlock - fails.
mtkclient initially failed to connect - none of the DA files bundled with the eng firmware worked. Found a working DA loader (MT6789.bin) elsewhere online.
mtkclient wasn’t picking up --loader reliably in all commands (had to place the flag right after da, before the subcommand - some runs still fell back to the stock MTK_DA_V6.bin). At one point replaced MTK_DA_V6.bin inside mtkclient’s own folder with the working loader to force it.
Flashed remaining partitions from the eng firmware via mtkclient - some partitions didn’t flash because of the loader-argument issue above.
mtk.py da seccfg unlock - reports “Successfully wrote seccfg.” every time.
fastboot getvar unlocked - still no.
Dumped RPMB (mtk.py da rpmb r), found the Jz8PNRUF magic at two offsets 16 MiB apart (same location, alias):
Erased that sector (rpmb e --sector 65504 --sectors 4), then ran seccfg unlock again without touching the power button in between (stayed in BROM via vol-key re-entry).
Booted to fastboot to check → still unlocked: no.
Re-dumped RPMB after that boot → magic was back at the same two offsets. Confirms the preloader restores it on every boot before LK/fastboot is reached, not just on a full power cycle.
Ran scan_lk.py on the eng lk.img → COMPATIBLE_FULL, same magic found at two internal offsets, all expected lock functions detected (mi_check_magic, get_lock_state, seccfg_set_lock_state, etc.), oem unlock/oem lock/oem lks present in fastboot.
Flashed the full eng firmware set, confirmed OEM unlocking toggle again, tried both:
Current blocker: MT6789/spinel isn’t in the known-sector table (MT6781/MT6769Z/MT6833/MT6877 only). Behavior matches the Tier 3b pattern (MT6877/”earth” in issue #8) — preloader rewrites the magic on every boot, so there’s no way to reach fastboot without the restore happening first.
Question: Is there any known way to patch/bypass this at the preloader level for MT6789, or is this chip still unsupported? Happy to provide preloader/LK dumps, RPMB dumps, or test anything.
All reactions