CyanogenMod on LGC660

Search This thread

aiamuzz

Senior Member
Dec 24, 2011
509
46
OK, next step: Do you have ADB installed on your computer? If so, run "adb shell", and inside the shell do "su" followed by "cat /data/data/com.koushikdutta.rommanager/files/rommanager.sh" (i need the output of this last command)
Code:
adb shell
$ su
# cat /data/data/com.koushikdutta.rommanager/files/rommanager.sh

After that, download http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-c660.img, put it in your SD card, open adb shell again, and do "su", followed by "/data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img". Once again, I need the output of the last command.

Code:
adb shell
$ su
# /data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img



The first set of commands when executed gives the following output...
Code:
$ su
# cat /data/data/com.koushikdutta.rommanager/files/rommanager.sh
[COLOR="Red"][B]echo 3 > /proc/sys/vm/drop_caches ; /data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/clockworkmod/download/1816511162 ; sync ;#
[/B][/COLOR]

The second set of commands when executed gives the following output...

Code:
# /data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img
[COLOR="Red"][B][1]   Illegal instruction     /data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img[/B][/COLOR]

When executed with the true path '/mnt/sdcard/'
Code:
# /data/data/com.koushikdutta.rommanager/files/flash_image recovery  /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img
[COLOR="Red"][B][1]   Illegal instruction     /data/data/com.koushikdutta.rommanager/files/flash_image recovery /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img[/B][/COLOR]

When executed from within SD card where the .img file resides.
Code:
# /data/data/com.koushikdutta.rommanager/files/flash_image recovery recovery-clockwork-5.0.2.7-c660.img
[COLOR="red"][B][1]   Illegal instruction     /data/data/com.koushikdutta.rommanager/files/flash_image recovery recovery-clockwork-5.0.2.7-c660.img[/B][/COLOR]


awaiting next set of diagnostic procedures ...

thnx.

---------- Post added at 06:42 AM ---------- Previous post was at 06:10 AM ----------

Could the 'Illegal Instructions' error be a result of improper R/W permission ???
 

Angenit

Senior Member
Dec 15, 2011
144
44
Ok now i get this!! But when trying the second one still receiving "[1] Illegal instruction"
 

Attachments

  • dos2.jpg
    dos2.jpg
    13.3 KB · Views: 86

varoon88

Member
May 25, 2011
32
9
OK, next step: Do you have ADB installed on your computer? If so, run "adb shell", and inside the shell do "su" followed by "cat /data/data/com.koushikdutta.rommanager/files/rommanager.sh" (i need the output of this last command)
Code:
adb shell
$ su
# cat /data/data/com.koushikdutta.rommanager/files/rommanager.sh

After that, download http://download.clockworkmod.com/recoveries/recovery-clockwork-5.0.2.7-c660.img, put it in your SD card, open adb shell again, and do "su", followed by "/data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img". Once again, I need the output of the last command.

Code:
adb shell
$ su
# /data/data/com.koushikdutta.rommanager/files/flash_image recovery /sdcard/recovery-clockwork-5.0.2.7-c660.img


Good to see Ricardo here :)

Here you go man, i am attaching the output you asked for those commands
and the Log file

For me the Recovery installation in Rom manager, takes like 2 mins (Depends on internet conn i think)


PS: I am getting the same results as everyone else. " Illegal instruction"

Awaiting you response :)
 

Attachments

  • alogcat.2012-01-03-12-17-57+0530.pdf
    56 KB · Views: 34

aiamuzz

Senior Member
Dec 24, 2011
509
46
aremcee is Ricardo !!!
sorry i didn't look into your profile...
thanks for looking into.
 

aremcee

Retired Recognized Developer
Feb 1, 2010
452
1,818
aremcee is Ricardo !!!
sorry i didn't look into your profile...
thanks for looking into.

OK, got it. It's a bug in ROM Manager, I'll ask koush to take a look. In the meantime, use the attached flash_image (unzip it, "adb push flash_image /data/local/; chmod 755 /data/local/flash_image)
 

Attachments

  • fi.zip
    6.8 KB · Views: 216

varoon88

Member
May 25, 2011
32
9
OK, got it. It's a bug in ROM Manager, I'll ask koush to take a look. In the meantime, use the attached flash_image (unzip it, "adb push flash_image /data/local/; chmod 755 /data/local/flash_image)

Thanks Ricardo !! Would be great if you could forward it to Koush :)

If we use this flash image , would it then fix the problem ?
plz could you explain a bit.

THanks a lot ricardo, appreciated !
 

aiamuzz

Senior Member
Dec 24, 2011
509
46
OK, got it. It's a bug in ROM Manager, I'll ask koush to take a look. In the meantime, use the attached flash_image (unzip it, "adb push flash_image /data/local/; chmod 755 /data/local/flash_image)

This is what i did.......i think i have flashed the recovery successfully.......

1. adb push flash_image /data/local/
Output :
Code:
223 KB/s (13964 bytes in 0.060s)
2. adb shell
3. su
4. chmod 755 /data/local/flash_image
5. /data/local/flash_image recovery /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img
Output
Code:
flashing recovery from /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: successfully wrote block at b10c00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00320000
mtd: successfully wrote block at b10c00340000
mtd: successfully wrote block at b10c00360000
mtd: successfully wrote block at b10c00380000
mtd: successfully wrote block at b10c003a0000
mtd: successfully wrote block at b10c003c0000
mtd: successfully wrote block at b10c003e0000
mtd: successfully wrote block at b10c00400000
mtd: successfully wrote block at b10c00420000
mtd: successfully wrote block at b10c00000000

So should i try restarting into recovery ???

thnx.
 
  • Like
Reactions: faizan05

varoon88

Member
May 25, 2011
32
9
This is what i did.......i think i have flashed the recovery successfully.......

1. adb push flash_image /data/local/
Output :
Code:
223 KB/s (13964 bytes in 0.060s)
2. adb shell
3. su
4. chmod 755 /data/local/flash_image
5. /data/local/flash_image recovery /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img
Output
Code:
flashing recovery from /mnt/sdcard/recovery-clockwork-5.0.2.7-c660.img
mtd: successfully wrote block at b10c00000000
mtd: successfully wrote block at b10c00020000
mtd: successfully wrote block at b10c00040000
mtd: successfully wrote block at b10c00060000
mtd: successfully wrote block at b10c00080000
mtd: successfully wrote block at b10c000a0000
mtd: successfully wrote block at b10c000c0000
mtd: successfully wrote block at b10c000e0000
mtd: successfully wrote block at b10c00100000
mtd: successfully wrote block at b10c00120000
mtd: successfully wrote block at b10c00140000
mtd: successfully wrote block at b10c00160000
mtd: successfully wrote block at b10c00180000
mtd: successfully wrote block at b10c001a0000
mtd: successfully wrote block at b10c001c0000
mtd: successfully wrote block at b10c001e0000
mtd: successfully wrote block at b10c00200000
mtd: successfully wrote block at b10c00220000
mtd: successfully wrote block at b10c00240000
mtd: successfully wrote block at b10c00260000
mtd: successfully wrote block at b10c00280000
mtd: successfully wrote block at b10c002a0000
mtd: successfully wrote block at b10c002c0000
mtd: successfully wrote block at b10c002e0000
mtd: successfully wrote block at b10c00300000
mtd: successfully wrote block at b10c00320000
mtd: successfully wrote block at b10c00340000
mtd: successfully wrote block at b10c00360000
mtd: successfully wrote block at b10c00380000
mtd: successfully wrote block at b10c003a0000
mtd: successfully wrote block at b10c003c0000
mtd: successfully wrote block at b10c003e0000
mtd: successfully wrote block at b10c00400000
mtd: successfully wrote block at b10c00420000
mtd: successfully wrote block at b10c00000000

So should i try restarting into recovery ???

thnx.

Sorry, but did u unzip the flash_image in a specific folder or anywhere ?

I wish u all the luck, whatever u do, Please keep us posted

Thanks :)
 

aiamuzz

Senior Member
Dec 24, 2011
509
46
Thank you so much Ricardo !!!

Code:
ClockworkMod Recovery v5.0.2.7

[COLOR="Cyan"][B]- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- poweroff
-+++++Go Back+++++
_________________________________
[/B][/COLOR]
ClockworkMod Recovery v5.0.2.7
[COLOR="Red"][B]E: Bad boot message
"recovery "
[/B][/COLOR]


Is the 'bad boot message' error normal ? or needs some fixing ?

@Ricardo
So now can you please advice which version of the Cyanogen Nightly build ROM do we attempt first ?

thanks,

---------- Post added at 12:27 PM ---------- Previous post was at 12:20 PM ----------

Sorry, but did u unzip the flash_image in a specific folder or anywhere ?

I wish u all the luck, whatever u do, Please keep us posted

Thanks :)

Yes !

Please extract the file somewhere and then run this command

adb push /complete/path/where/file/has/been/extracted/flash_image /data/local/

and follow the rest of the commands as mentioned earlier.......
 
  • Like
Reactions: varoon88

varoon88

Member
May 25, 2011
32
9
Thank you so much Ricardo !!!

Code:
ClockworkMod Recovery v5.0.2.7

[COLOR="Cyan"][B]- reboot system now
- apply update from sdcard
- wipe data/factory reset
- wipe cache partition
- install zip from sdcard
- backup and restore
- mounts and storage
- advanced
- poweroff
-+++++Go Back+++++
_________________________________
[/B][/COLOR]
ClockworkMod Recovery v5.0.2.7
[COLOR="Red"][B]E: Bad boot message
"recovery "
[/B][/COLOR]


Is the 'bad boot message' error normal ? or needs some fixing ?

@Ricardo
So now can you please advice which version of the Cyanogen Nightly build ROM do we attempt first ?

thanks,

---------- Post added at 12:27 PM ---------- Previous post was at 12:20 PM ----------



Yes !

Please extract the file somewhere and then run this command

adb push /complete/path/where/file/has/been/extracted/flash_image /data/local/

and follow the rest of the commands as mentioned earlier.......

Mann !!! :(
I did what Ricardo said and then did what you said.
Dont know what went wrong.
But now i cant move past the LG logo ???
Nothing is happening, Please tell me there is a way to fix this
Please anybody please help :(
 

aiamuzz

Senior Member
Dec 24, 2011
509
46
Mann !!! :(
I did what Ricardo said and then did what you said.
Dont know what went wrong.
But now i cant move past the LG logo ???
Nothing is happening, Please tell me there is a way to fix this
Please anybody please help :(


:rolleyes:

Did you get the similar outputs as the ones i had posted ?
Hope it did not get stalled somewhere midway and you hadn't noticed ?

Hope your phone was rooted and superuser was already installed.

BTW i booted into recovery from 'ROM Manager'

what did you do 'hard-key' boot into recovery ?

@Ricardo need your help here...
 

varoon88

Member
May 25, 2011
32
9
:rolleyes:

Did you get the similar outputs as the ones i had posted ?
Hope it did not get stalled somewhere midway and you hadn't noticed ?

Hope your phone was rooted and superuser was already installed.

BTW i booted into recovery from 'ROM Manager'

what did you do 'hard-key' boot into recovery ?

@Ricardo need your help here...

I got similar outputs yes !!
It said writing flash_image at this speed. Exactly like yours.
Then I did the second command :
Which had first 6-7 lines like : "Error out of memory"
But after 7 lines it said Writing sucessfully exactly like yours.

Thats when i rebooted in recovery from Rom Manager itself.

Now it doesnt go after LG logo ?? Really hope i get some help for this.

Begging and Praying for Ricardo to help me.
 

aiamuzz

Senior Member
Dec 24, 2011
509
46
I got similar outputs yes !!
It said writing flash_image at this speed. Exactly like yours.
Then I did the second command :
Which had first 6-7 lines like : "Error out of memory"
But after 7 lines it said Writing sucessfully exactly like yours.

Thats when i rebooted in recovery from Rom Manager itself.

Now it doesnt go after LG logo ?? Really hope i get some help for this.

Begging and Praying for Ricardo to help me.

Seems like those 6-7 lines could be the culprit :mad::mad::mad:
you should have posted the exact output along with the error lines...

To what i understand its a block-to-block writing into the memory.......

Please ping ricardo on this .......

In the meanwhile i found this link ....... please research over it !!! before you try it.......better still, you wait until one of the experts takes a look into this issue.

http://xdaforums.com/showthread.php?t=1229407&page=2

http://xdaforums.com/showthread.php?t=1160364&page=1
 
Last edited:

lovish1

Member
Nov 18, 2011
47
3
Mann !!! :(
I did what Ricardo said and then did what you said.
Dont know what went wrong.
But now i cant move past the LG logo ???
Nothing is happening, Please tell me there is a way to fix this
Please anybody please help :(

Installing the rom again may resolve your problem..

Love is eternal - Albus dumbledore
 

varoon88

Member
May 25, 2011
32
9
Seems like those 6-7 lines could be the culprit :mad::mad::mad:
you should have posted the exact output along with the error lines...

To what i understand its a block-to-block writing into the memory.......

Please ping ricardo on this .......

In the meanwhile i found this link ....... please research over it !!! before you try it.......better still, you wait until one of the experts takes a look into this issue.

http://xdaforums.com/showthread.php?t=1229407&page=2

http://xdaforums.com/showthread.php?t=1160364&page=1

Thanks man, i was looking all over google, found those also. But it needs device specific files i guess. Right now im doing this http://www.lg-phones.org/how-to-flash-lg-optimus-pro-c660.html
Have a look see if this can work, im gonna give it a try

Installing the rom again may resolve your problem..

Love is eternal - Albus dumbledore

Any idea where i can find that ?


A few more links to research on similar type of issues faced...

http://xdaforums.com/showthread.php?t=1248644

http://xdaforums.com/showthread.php?t=1107009

until help arrives via an expert .......

Thanks man, thanks everyone. I know i will get this fixed. Ricardo plz if u can help me in any way it would mean alot to me.

CM7 team or ricardo. Plz guys im in a bad situation, :(
 

aremcee

Retired Recognized Developer
Feb 1, 2010
452
1,818
Thanks Ricardo !! Would be great if you could forward it to Koush :)

After talking to him and doing a few tests myself... I can't reproduce this.

Which version of ROM Manager are you people running? The current one from Market? (Open RM, and look at the version, it's written at the top of the app's window)
 

varoon88

Member
May 25, 2011
32
9
Ricardo !! or any one else !!

Can anyone else give me a working KDZ firmware of LG C660.

I need to reflash the original firmware .

Thanks in advance
 

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    I really like this! I allways help when people needs help... I think i'm very kind, but not one 'thank you!', nothing!

    So nice :) - not!
    2
    aremcee is Ricardo !!!
    sorry i didn't look into your profile...
    thanks for looking into.

    OK, got it. It's a bug in ROM Manager, I'll ask koush to take a look. In the meantime, use the attached flash_image (unzip it, "adb push flash_image /data/local/; chmod 755 /data/local/flash_image)
    1
    Can the experts from this forum help the 'LG Optimus Pro C660' users with the issue of not being able to boot into recovery/bootloader to create a nandroid backup.

    As users have already posted here, every time we try to boot into recovery through the following ways...

    1. Rom Manager
    2. Key Combinations (Vol Up/Dn + Home + Power button)
    3. Quickboot App
    4. A command through the ADB Shell

    All the above has resulted in a factory default restore. A green Android'bot appears for a second and so, and the phone is restored to factory settings.

    Please Help !!!!!!!

    PS : Seems like the Bootloader/recovery needs to be cracked for this LG Optimus Pro C660.

    thanks,



    Exactly the same problem as my other PRO friends. plz sombody help us.

    Recovery seems to be the issue, But guys. Check out this guys, who actually released CM7 on optimus pro

    Search for "Ricardo Cerqueira" on Google plus


    Scroll down and you will see pictures of CM7 working on pro. So seems he has un -locked the bootloader. Plzz somebody share with us :D
    1
    Just to add as a datapoint - I installed 7.2 RC on my C660R (canadian version called gossip pro, fido networks).

    Ran into a few issues at first:
    1. com.android.phone kept crashing. was able to find out from aLogCat that it was a StkService process issue (sim card toolkit). I bought a new simcard (was running an old card), and that issue went away. I also unlocked my phone at the same time, so it may have been that as well.

    2. SD card unmounting issue - was using a no name 2GB that came with the phone. Switched it with a Kingston class 4 SD card, and unmounts have gone away

    Hope this helps anyone with a LG Gossip Pro C660R