[JB][412][CWM] ClockWorkMod 6.0.2.8 (FREEDOM for EUR-xxx)

Search This thread

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
i can on top , a quick note on restore 4.1.2 backup, it works fine.

i tried to install my custonexus, and it failed probably due to the boot.img is 4.0.3 and old kernel, which is not compatible with upgraded tegra partitions and new bootparams from bootloader.

but i did a full recovery from cwm from internal storage, and im back to normal!
so perfect for backup / restore now when all fails
 
  • Like
Reactions: faisal222

Atomix86

Senior Member
Jul 5, 2011
1,170
273
Impossible to unlock the bootloader, as I have been saying the past few days, it just hangs. I have tried over and over and over, never works. Also get the following error in the cmd window:
 

Attachments

  • NOBLFORYOU.jpg
    NOBLFORYOU.jpg
    81.4 KB · Views: 1,171

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
Impossible to unlock the bootloader, as I have been saying the past few days, it just hangs. I have tried over and over and over, never works. Also get the following error in the cmd window:

it hangs and hangs and yet, hangs... just be patient! i waited probably 30sec which i believe is the trigger since then it has run the "wipe/factory reset correctly, which it does)

you can easily see it works , when all your settings are lost at next boot and it start at setupwizard again!! then! you are unlocked.
but yes, it will hang forever, just wait and pull battery and you should be ok.
So, if i downgrade, root my v10h, install v20a with skydev method, unlock and follow the rest of your thread it's ok ?
yes, remember to root and follow skydev method to have all files prepped for a v20a install, so /data is not wiped by accident, you do NOT want that. or its all back and restore v10 and back on the saddle once more
 

AlderCass

Senior Member
Jan 27, 2013
427
157
Cork
www.aldercass.com
When unlocking the bootloader, for the adb reboot-bootloader step, when you get to the boot screen saying "Running Factory Reset for the first Bootloader Unlock :: Please wait...", about how long should the wait be? Mine's been on this screen for about 5 minutes so far, is this normal?

---------- Post added at 02:07 PM ---------- Previous post was at 02:06 PM ----------

Or is it at that point I should wait 30 secs and pull out the battery?
 

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
@AlderCass
yes, just 30sec and pull battery, i believe that did it for me here, i had the lock issue also the first 2-3 times, then i started waiting when i read that wipe was done after unlock accept in nexus7 and then it worked when i waited some more.
 

Atomix86

Senior Member
Jul 5, 2011
1,170
273
it hangs and hangs and yet, hangs... just be patient! i waited probably 30sec which i believe is the trigger since then it has run the "wipe/factory reset correctly, which it does)

you can easily see it works , when all your settings are lost at next boot and it start at setupwizard again!! then! you are unlocked.
but yes, it will hang forever, just wait and pull battery and you should be ok.
I appreciate what you're saying, but I have waited 15 minutes the last time and nothing. I don't think theyr'e all unlockable tbh.

---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------

When unlocking the bootloader, for the adb reboot-bootloader step, when you get to the boot screen saying "Running Factory Reset for the first Bootloader Unlock :: Please wait..."
How did you get it to say that? Mine just hangs on a black screen :confused:
 

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
I appreciate what you're saying, but I have waited 15 minutes the last time and nothing. I don't think theyr'e all unlockable tbh.

---------- Post added at 04:11 PM ---------- Previous post was at 04:10 PM ----------


How did you get it to say that? Mine just hangs on a black screen :confused:

hmmm, why not skip this and move on to "root" 4.1.2, maybe that emulated unlock bootloader, is nothing, since bootloader already continue to say locked, even if i install boot/recovery without problems. maybe bootloader is default disabled but the way to get message saying it is tricky.

try without, you do not lose much, except a v20a install to fix it.
 

Atomix86

Senior Member
Jul 5, 2011
1,170
273
hmmm, why not skip this and move on to "root" 4.1.2, maybe that emulated unlock bootloader, is nothing, since bootloader already continue to say locked, even if i install boot/recovery without problems. maybe bootloader is default disabled but the way to get message saying it is tricky.

try without, you do not lose much, except a v20a install to fix it.
I tried to do this without unlocking, two things:

Firstly, even in su mode the terminal emulator didnt allow me to flash the images so..

Secondly I used adb shell and it flashed them BUT it would not boot just had a tiny red text when turning on saying "Security error: boot signature" then immediate bootloop.
 
  • Like
Reactions: Dexter_nlb

Subhajitdas298

Senior Member
Sep 10, 2012
412
34
Kolkata
the steps are as simple as explained, 3 commands and you are using CWM native, which replaces stock now, so it works with VOL-down to start and so on.

so all you do is unlock + root it like explained.

i can confirm the "Unlocked" feature remains, i have flash v10h 4 times now, and i only unlocked my device once.

not for me. I am not an android know it all. I was expecting click by click guide or a pictured guide. And what to do first, root or unlock?
 

AlderCass

Senior Member
Jan 27, 2013
427
157
Cork
www.aldercass.com
How did you get it to say that? Mine just hangs on a black screen :confused:

I dunno, it seems like luck and persistence. I downloaded the newsest SDK, ran adb reboot-bootloader and it rebooted to the black screen with LG icon and at the top in tiny text it had that message but seemed stuck, so I pulled the battery but it still had all my settings intact when I booted so it was obviously unsuccessful so I tried again and the same message on the LG boot screen showed up only this time almost straight away it said "Done" so I rebooted and the factory reset was indeed successful and the bootloader unlock check says unlock - but now I have a new problem, when I go to adb reboot-bootloader again so that I can try fastboot oem unlock, I get this:


*edit* just had to run adb kill-server
 

Attachments

  • Untitled-1.jpg
    Untitled-1.jpg
    24.4 KB · Views: 732
Last edited:

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
I tried to do this without unlocking, two things:

Firstly, even in su mode the terminal emulator didnt allow me to flash the images so..

Secondly I used adb shell and it flashed them BUT it would not boot just had a tiny red text when turning on saying "Security error: boot signature" then immediate bootloop.

at least it confirms that our "Unlocked" information shown in hiddenmenu is accurate then! that is good information.
problem is then for the many, that we cannot relock our device if we want to.
 

Tim_Pan

Senior Member
Aug 20, 2011
191
138
GuangZhou
hmmm, why not skip this and move on to "root" 4.1.2, maybe that emulated unlock bootloader, is nothing, since bootloader already continue to say locked, even if i install boot/recovery without problems. maybe bootloader is default disabled but the way to get message saying it is tricky.

try without, you do not lose much, except a v20a install to fix it.

unlocked device.
successfully flashed but it seems kernel or recovery exist bugs that the phone boots into recovery automatically when booting.:confused:
 

Atomix86

Senior Member
Jul 5, 2011
1,170
273
I dunno, it seems like luck and persistence. I downloaded the newsest SDK, ran adb reboot-bootloader and it rebooted to the black screen with LG icon and at the top in tiny text it had that message but seemed stuck, so I pulled the battery but it still had all my settings intact when I booted so it was obviously unsuccessful so I tried again and the same message on the LG boot screen showed up only this time almost straight away it said "Done" so I rebooted and the factory reset was indeed successful and the bootloader unlock check says unlock - but now I have a new problem, when I go to adb reboot-bootloader again so that I can try fastboot oem unlock, I get this:
Ok I guess ill just try over and over till i throw it against a wall lol, as for your error have you tried killing the old adb server?
 

Dexter_nlb

Senior Member
Feb 12, 2009
5,459
4,550
Copenhagen
unlocked device.
successfully flashed but it seems kernel or recovery exist bugs that the phone boots into recovery automatically when booting.:confused:
not here, just try and exit normally in recovery, this problem you mention happens when you power-off pulling battery when recovery is running. then it will run last status type again.

but now I have a new problem, when I go to adb reboot-bootloader again so that I can try fastboot oem unlock, I get this:
that looks more like you got 2 android devices attached to your pc now :)

Ok I guess ill just try over and over till i throw it against a wall lol, as for your error have you tried killing the old adb server?
maybe a keycombi thing as well? press volup/down and wait 30 secs?
guides for nexus7 says you have to accept policy by using volup key maybe that is what happens here, but no text is shown.
 

AlderCass

Senior Member
Jan 27, 2013
427
157
Cork
www.aldercass.com
Ok I guess ill just try over and over till i throw it against a wall lol, as for your error have you tried killing the old adb server?

Yep killing the server worked!

I ran adb bootloader-unlock and it booted to the LG logo screen with "Now ready" at the top at which point I ran fastboot oem unlock - at this point you have to be quick to select the unlock option on your phone's screen because when I did it the first time the options disappeared just when I noticed they were even on the screen because I was watching command prompt not my phone, so I had to reboot and try again, at which point:
 

Attachments

  • Untitled-1.jpg
    Untitled-1.jpg
    30.6 KB · Views: 650

Top Liked Posts

  • There are no posts matching your filters.
  • 127
    tested and confirmed that after "Unlocked" is shown in hidden phonemenu(dial 3845#*880#) using fastboot oem unlock or adb reboot oem-unlock, we got access to install recovery from root shell in recovery or during regular bootup.

    updated - now uses latest 6.0.2.8 + fixed adb usb in recovery when connecting to pc.

    pre-required
    - unlock bootloader , if you got a EUR-xxx in Settings->about phoné->software version, otherwise it seems you cannot unlock your model.
    (adb reboot-bootloader ; fastboot oem unlock -> enable unlock -> wait 30sec -> remove battery)
    Some notes on Unlocking bootloader
    - try and make sure your phone is fully charged (100% if possible, this might do good for the unlock mechanism to work)
    - remember, if you s/w upgrade menu has bootloader state: unlocked - it is ok,
    - if hidden dialer menu(3845#*880#) says Unlocked, it is ok.
    - rooted v20a device (follow instructions from here ) (new easier root method)


    GUIDE:
    1. when you are running unlocked bootloader and is rooted goto step 2.
    2. download attached zip files and extract content to internal sdcard location
    3. use adb shell or terminal from market and execute the commands below
    4. you are now running with native CWM recovery and unsecure boot, which enable adb root at boot instantly.

    5. boot into recovery, by rebooting device and hold VOL-DOWN during bootup. (from power-off = keep holding vol-down during power on)

    execute these 2 commands for recovery image install
    Code:
     su
    cat /mnt/sdcard/recovery-6028.img >/dev/block/mmcblk0p1
    sync

    or see screenshot here
    34t92mx.jpg


    do this at your own risk, and do NOT try this on old 4.0.3, which is not with unlocked bootloader, and you are required to install KDZ again.
    note: unsecure boot is not included anymore, as it was beta v20a based.

    THANKS to:
    skydev - for his continued effort in finding root and giving our device full freedom with boot/recovery.
    16
    here the new unsecure boot from the new update (v20a aneubk)

    get root, follow dexters instructions and then adb is running at root all the time and flashing with fastboot is working again (with secure boot it didnt work)
    4
    RC from CyanogenMod posted unlocking tutorial for L9 (which now has official update). Maybe we should have wait for official release. And maybe Dexter_nlb could add this in OP. (I don't know if this is valid for our device):

    Unlocking the LG Optimus L9

    The L9's (p760) update to Jellybean from LG started rolling out today. It has a ton of new stuff for people who are interested in keeping the stock ROM, and another new thing that's of interest to us: the bootloader is now unlockable.

    How?

    Step 1 - After installing the JB update (I don't know if there are any leaks, but it so avoid them. The real update is out), make sure you have a SIM in your phone and
    let it stay on for at least 30 continuous minutes. This is important!. If you skip this step, you may end up with a permanently locked device.

    ... (further is not important for us)
    4
    well im stuck! When i enter reboot bootloader phone restart and lg sign is on, but on the top of screen there is nothing. And when i enter fastboot i got this (see picture). But if i unplug cable i got text running factory reset for the first bootloader unlock and thats it. Nothing happens.

    update your tools
    4
    Updated post #1 with CWM 6.0.2.8 + adb connection fix (now you can use adb in recovery too)