Android Enthusiasts Stack Exchange is a question and answer site for enthusiasts and power users of the Android operating system. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am using a Samsung Galaxy Nexus and CWM as recovery. Even though I locked my bootloader after installing the recovery, I can flash Cyanogenmod 10 using CWM without any errors. Now I am wondering why this works?

When I unpack the Cyanogenmod 10 .zip on my computer, there's also a boot.img, so I guess it also replaces the bootloader? Maybe when the bootloader is locked, this step is skipped (but no error shown) and the stock ROM bootloader is also OK?

This ends up in my final question: While it works, am I maybe missing a bootloader update when flashing Cyanogenmod while my bootloader is locked?

share|improve this question
The boot.img file is written the /boot partition, not the bootloader partition. They're different. – eldarerathis Oct 2 '12 at 16:13
Thanks! Hmm, then in which case do I actually have to unlock the bootloader? What about changing the recovery, I guess this is also not the bootloader partition? – Oct 2 '12 at 16:46
Correct, the recovery image exists on a separate partition. From what I know (but I'm not 100% positive) you really only need to unlock the bootloader on the Galaxy Nexus to be able to flash unsigned images via fastboot. – eldarerathis Oct 2 '12 at 23:56

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Browse other questions tagged or ask your own question.