[Optimus L3, L5, L7 Android Development] HanSolo77:
Cannot get CWM to run on my E610

Problem

I have tried various ways, but I did not manage to get CWM running on my E610. I can boot normally, I just cannot get into a working recovery mode. Initially, with the stock ROM, [Vol-] would give me the "download mode" during boot. Now, when I hold [Vol-] the two menu/back buttons light up briefly, and the phone goes dark again. If I continue holding power too long, the phone starts normally.

Versions

Phone: LG-E610 (with NFC)

Android: 4.1.2

Baseband: MSM7225A-1-AA

Kernel: 3.4.0

Build: JZ054K

Software: E61020d-EUR-XX

Stuff I Tried

These are the things I tried (I rooted the phone successfully, got SuperSU installed, and got a working adb on multiple machines and operating systems – actually I worked with Linux, OS X and Windows, trying just about everything I could find):

I managed to flash "20d+root + cwm.kdz" onto my phone (using the KDZ_FW_UPD_EN tool), which I assumed to give me a custom "CWM" recovery. (This took me a long time, because I did not have a real Windows machine, and KDZ_FW_UPD_EN would not work in VirtualBox.)

I learned about "adb reboot bootloader", and used "fastboot flash recovery .../cwm6.0.5.0_flashable/recovery.img".

I learned about "adb install" and installed an "[E610]unlock_1.0_signed.apk", pressed the "unlock" and "install CWM" buttons.

I installed the free "ROM Manager" from ClockWorkMod, but it did not find a matching CWM download. (I actually tried the "m4" one listed, but did not really expect it to work.)

I learned about "adb push" and put "recovery-clockwork-6.0.2.8-e610.img" and "emmc_appsboot.bin" (which I found identically in a "JB-need.rar", an "Arquivos.zip", an "e610.zip", and as separate attachments) into /sdcard, then used "adb shell" and dd to overwrite mmcblk0p5 and mmcblk0p17.

I similarly tried to install the newer cwm6.0.5.0_flashable.img from a different thread.

I recently performed a factory reset through the Android settings app.

After all this, I consider myself kind of lucky that I apparently did not brick the phone yet (even though I accidentally wrote the CWM image to mmcblk0p7 once, because of my eyes being tired now). :)

Checksums:

emmc_appsboot.bin: SHA ca95f56aaf608229fc9ba78d32da10df0d14ceeb / MD5 71b64b6bc47a203a694993b2f76d2580

recovery-clockwork-6.0.2.8-e610.img: SHA 67b8e487e23c8460fc9163aa3a9b9818252865b3 / MD5 8caf397ec0d423c0277ff68e3cb9553a

cwm6.0.5.0_flashable.img: SHA 02c4fe78f225a6f95c0f40aca2b500d0456d2dc0 / MD5 dbedef5e123f3254e59bf9514d2d6de9

My preferred way of working now is via adb.

Questions

Please – can anybody tell me what more I can try to get a working CWM?

Two possible reasons that I have in the back of my head are

a "locked" bootloader (I assume this has something to do with "secure boot" and signature checks preventing CWM execution), but as far as I can see, many of the things I tried should have unlocked the phone (writing to mmcblk0p5, using "[E610]unlock_1.0_signed.apk", apparently even the original kdz flashing), or

an incompatible kernel version. I did not specifically try changing the kernel yet. Is that completely independent of the recovery and device ROMs? I think I read that the kernel is on a separate partition and will be used for both?

Also, is there anything else I should try in this forum? I can't open a new thread yet, so I fear this post will not have the right visibility.