I tried to relock the bootloader on my Find 7 (which I'm pretty sure was unlocked since I installed a custom rom).

fastboot oem lock

After that nothing. Windows console is "stuck". Any clue?

  • Just to gauge what you've done, is your device discoverable via adb while its on? If so, then run adb reboot bootloader, which should then boot to fastboot mode. Alternatively it might appear as a selectable option using hw keys. Once in fastboot mode, run fastboot devices to see if its recognized. – filoxo Aug 14 '15 at 17:19
  • fastboot works. and fastboot devices shows my device – dragonmnl Aug 14 '15 at 19:21

I see the same behavior on my Find 7. I also seem to recall the device arriving unlocked. As far as I can tell, it simply does not support locking the bootloader.

Running unlock just instantly says OK despite the fact that Developer Options does not contain the "Enable OEM Lock" setting at all (on the latest ColorOS 2.1.5i software, which is Android 5.0 — the version where that feature was added). I also cannot find anything about (un)locking the Find 7's bootloader online other than one obscure Thai site that seems like it is probably trying to get clicks by reposting the same instructions for multiple devices.

| improve this answer | |

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.