• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[CWM][24/01] ClockworkMod 5 Recovery For LG Nitro HD

Search This thread

bytecode64

Senior Member
Sep 3, 2011
104
83
Saudi Arabia
Cwm v5.0.2.7 For LG Nitro HD (P930) /Optimus LTE
Current Status: Operational
Installation/Update Instructions:
Before installing make sure that your phone is rooted
Code:
Backup your existing recovery:
1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]

Flash the new recovery by:
1) Download the bc64-recovery.rar and extract it
2) Copy the extracted bc64-recovery.img to your /sdcard
3) via terminal emulator or adb shell execute:
[COLOR="Magenta"]
su
cd /sdcard
cat bc64-recovery.img > /dev/block/mmcblk0p13[/COLOR]

All Done!
Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)

Screenshots:



Video:
Code:
http://www.youtube.com/watch?v=okr8PWeQ30E

ChangeLog:
Code:
v0.2 B20120124 
Changes:
* Added postrecoveryboot.sh to clear out boot command
* Added Partition/fs Utils (useful for rom dev in formatting/checking ext4 fs)
-e2fsck_static
-mke2fs_static
-resize2fs_static
-tune2fs_static
v0.1 B20120120 (Initial Release)

Known Issues:
Code:
wrong timestamps
Tested On:
Code:
Atnt LG Nitro HD  (P930)
LG Optimus LTE (SU640)
Thanks To:
Code:
schwin97
[email protected]
Malnilion
repherb 
aquariuz23
gte460z 
and everyone else who contributed to this thread :P
Download:
Code:
http://www.mediafire.com/?mnf53sxmp5aifd9

Source Code (Sorry , too lazy for github fttb):
Code:
http://www.mediafire.com/?f27d8j8d7mc8qi8

For Rom Developers:
It seems that default cwm format is messing up (due to ext4 file system) , Please use (edify) the following script to format the data and cache partition (or System)
Code:
#Format Data
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
#Format Cache
/sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p28

# After Format Verify the FIle System
/sbin/e2fsck_static -y /dev/block/mmcblk0p30
/sbin/e2fsck_static -y /dev/block/mmcblk0p28

Edify (To Format System):
Code:
run_program("/sbin/mke2fs_static", "-t" , "ext4" "/dev/block/mmcblk0p27");
AND 
run_program("/sbin/e2fsck_static", "-y", "/dev/block/mmcblk0p27");
 
Last edited:

bytecode64

Senior Member
Sep 3, 2011
104
83
Saudi Arabia
@belth219 could you do a "cat /proc/partitions" on your cell and post its results?

Also providing the results for the above command for nitro HD would also be very usefull.
 

yetsz

New member
Dec 26, 2011
1
0
This is the result of my lu6200
Another version of p930
# su
su
# cat /proc/partitions
cat /proc/partitions
major minor #blocks name

179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1048576 mmcblk0p26
179 27 327680 mmcblk0p27
179 28 1548288 mmcblk0p28
179 29 16384 mmcblk0p29
179 30 1024 mmcblk0p30
179 31 229376 mmcblk0p31
259 0 4096 mmcblk0p32
179 32 7774208 mmcblk1
179 33 7773184 mmcblk1p1
#
$ cat /proc/mounts
cat /proc/mounts
rootfs / rootfs ro,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p26 /system ext4 rw,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p28 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p27 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p29 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p31 /lgumsg ext4 rw,nosuid,nodev,relatime,barrier=1,data=order
ed 0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
 
Last edited:

wohaha

New member
Dec 26, 2011
1
0
My phone is LU6200,too. Could you tell me if I can install this mod on my phone? The only difference of 2 device is the CPU
 

bytecode64

Senior Member
Sep 3, 2011
104
83
Saudi Arabia
I dont think it would work on your device as im sure it has diffrent kernel , upload your boot.img , i will port it once i get nitro hd confirmation
 

belth219

Member
Dec 9, 2011
18
0
Shanghai
SU640

# cat /proc/partitions
cat /proc/partitions
major minor #blocks name

7 0 2111 loop0
179 0 3526656 mmcblk0
179 1 32768 mmcblk0p1
179 2 1024 mmcblk0p2
179 3 1024 mmcblk0p3
179 4 1 mmcblk0p4
179 5 1024 mmcblk0p5
179 6 5120 mmcblk0p6
179 7 5120 mmcblk0p7
179 8 10240 mmcblk0p8
179 9 1024 mmcblk0p9
179 10 3072 mmcblk0p10
179 11 3072 mmcblk0p11
179 12 8192 mmcblk0p12
179 13 16384 mmcblk0p13
179 14 32768 mmcblk0p14
179 15 3072 mmcblk0p15
179 16 3072 mmcblk0p16
179 17 3072 mmcblk0p17
179 18 3072 mmcblk0p18
179 19 1024 mmcblk0p19
179 20 8192 mmcblk0p20
179 21 16384 mmcblk0p21
179 22 73728 mmcblk0p22
179 23 8192 mmcblk0p23
179 24 24576 mmcblk0p24
179 25 8192 mmcblk0p25
179 26 1024 mmcblk0p26
179 27 860160 mmcblk0p27
179 28 327680 mmcblk0p28
179 29 3072 mmcblk0p29
179 30 1957638 mmcblk0p30
179 31 16384 mmcblk0p31
259 0 2048 mmcblk0p32
179 32 15622144 mmcblk1
179 33 15618048 mmcblk1p1
254 0 2110 dm-0

# cat /proc/mounts
cat /proc/mounts
rootfs / rootfs rw,relatime 0 0
tmpfs /dev tmpfs rw,relatime,mode=755 0 0
devpts /dev/pts devpts rw,relatime,mode=600 0 0
proc /proc proc rw,relatime 0 0
sysfs /sys sysfs rw,relatime 0 0
none /acct cgroup rw,relatime,cpuacct 0 0
tmpfs /mnt/asec tmpfs rw,relatime,mode=755,gid=1000 0 0
tmpfs /mnt/obb tmpfs rw,relatime,mode=755,gid=1000 0 0
none /dev/cpuctl cgroup rw,relatime,cpu 0 0
/dev/block/mmcblk0p27 /system ext4 ro,relatime,barrier=0,data=ordered 0 0
/dev/block/mmcblk0p22 /tombstones ext4 rw,nosuid,nodev,relatime,barrier=1,data=o
rdered 0 0
/dev/block/mmcblk0p1 /firmware vfat ro,relatime,fmask=0000,dmask=0000,allow_utim
e=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,errors=remount-ro 0 0
/dev/block/mmcblk0p30 /data ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
,noauto_da_alloc 0 0
/dev/block/mmcblk0p12 /persist ext4 rw,nosuid,nodev,relatime,barrier=1,data=orde
red 0 0
/dev/block/mmcblk0p28 /cache ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordere
d 0 0
/dev/block/mmcblk0p31 /mpt ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered
0 0
/dev/block/mmcblk0p23 /mm ext4 rw,nosuid,nodev,relatime,barrier=1,data=ordered 0
0
/dev/block/mmcblk0p14 /system/etc/firmware/misc_mdm vfat ro,relatime,fmask=0000,
dmask=0000,allow_utime=0022,codepage=cp437,iocharset=iso8859-1,shortname=lower,e
rrors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/sdcard vfat rw,dirsync,nosuid,nodev,noexec,relatime,
uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,iocharse
t=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
/dev/block/vold/179:33 /mnt/secure/asec vfat rw,dirsync,nosuid,nodev,noexec,rela
time,uid=1000,gid=1015,fmask=0002,dmask=0002,allow_utime=0020,codepage=cp437,ioc
harset=iso8859-1,shortname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
tmpfs /mnt/sdcard/.android_secure tmpfs ro,relatime,size=0k,mode=000 0 0
/dev/block/dm-0 /mnt/asec/com.cyandroid.pianofull-1 vfat ro,dirsync,nosuid,nodev
,relatime,uid=1000,fmask=0222,dmask=0222,codepage=cp437,iocharset=iso8859-1,shor
tname=mixed,utf8,tz=UTC,errors=remount-ro 0 0
 

schwin97

Senior Member
May 26, 2010
126
33
OK...

I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...

---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------

Upon using anreboot to boot into recovery I get...

Code:
Enter the fastboot...
Enter the fastboot...

Long time no see!

And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...

Now to see if I can reboot normally?

---------- Post added at 09:09 AM ---------- Previous post was at 09:05 AM ----------

And it still boots normally and is fully functional when it does boot!!! Good progress so far. Now, does anyone know how to determine the driver it is looking for? I think if I find the right driver I can get into fastboot mode and do anything else that is necessary?
 

bytecode64

Senior Member
Sep 3, 2011
104
83
Saudi Arabia
OK...

I just ran 'cat /dev/zero > /dev/block/mmcblk0p27', remounted my system partition as read/write and copied the recovery.img into the directory. Just rebooted in hopes it will flash the recovery image to the recovery partition p27 above. Will now attempt rebooting into recovery to see if anything happened...

---------- Post added at 09:05 AM ---------- Previous post was at 09:01 AM ----------

Upon using anreboot to boot into recovery I get...

Code:
Enter the fastboot...
Enter the fastboot...

Long time no see!

And the LG logo beneath it... It also attempted to install a new driver 'android', but couldn't find it on my computer. Very excited that we are moving closer to getting a 'real' recovery mode on the phone...

Now to see if I can reboot normally?

Why did you ran cat /dev/zero > /dev/block/mmcblk0p27?

as of this http://forum.xda-developers.com/showpost.php?p=20514396&postcount=32 post your recovery partition should be /dev/block/mmcblk0p27

so To be me steps would have been:
1) Backing up recovery partition using dd
2) Remounting System partiton as read write
3) copying recovery.img to /system and flashing the recovery.img
4) booting into recovery
 

schwin97

Senior Member
May 26, 2010
126
33
I agree, but when I miss the part about putting the recovery image in the system directory for it to automatically reflash, I started running the steps to flash the recovery image as people flash the boot image...

An extra step that luckily didn't have any bad consequences...

---------- Post added at 09:18 AM ---------- Previous post was at 09:16 AM ----------

For fastboot you should have andriod sdk installed , get it at :
Code:
http://developer.android.com/sdk/download.html

I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
 

schwin97

Senior Member
May 26, 2010
126
33
Sure did. I have the drivers that are needed when the phone boots up normally? Just when it boots up in this new recovery mode that it is asking for a new driver? It shouldn't be asking for anything new, but it is... Another question - after it loads up the new recovery image from the /system directory should it remove the recovery image? If so, then if the recovery image is still in the system directory we may have a problem?

---------- Post added at 09:44 AM ---------- Previous post was at 09:39 AM ----------

As I had thought - recovery.img is still in the system directory... Does this indicate a problem?
 

belth219

Member
Dec 9, 2011
18
0
Shanghai
I have the sdk installed - but my laptop is asking for a driver - is the driver within the sdk download? If I don't give it the driver then it says the device didn't get installed correctly and fastboot doesn't see it.
You should install the LGMobile update which can be downloaded from LG official website.
That is a useful tool.
 

Top Liked Posts

  • There are no posts matching your filters.
  • 23
    Cwm v5.0.2.7 For LG Nitro HD (P930) /Optimus LTE
    Current Status: Operational
    Installation/Update Instructions:
    Before installing make sure that your phone is rooted
    Code:
    Backup your existing recovery:
    1) [COLOR="Magenta"]cat /dev/block/mmcblk0p13 > /sdcard/recovery-backup.img[/COLOR]
    
    Flash the new recovery by:
    1) Download the bc64-recovery.rar and extract it
    2) Copy the extracted bc64-recovery.img to your /sdcard
    3) via terminal emulator or adb shell execute:
    [COLOR="Magenta"]
    su
    cd /sdcard
    cat bc64-recovery.img > /dev/block/mmcblk0p13[/COLOR]
    
    All Done!
    Now to Boot into recovery , press the vol down+pwr button , when it asks you to factory reset , tap twice the pwr button to confirm (dont worry it wont format your device)

    Screenshots:



    Video:
    Code:
    http://www.youtube.com/watch?v=okr8PWeQ30E

    ChangeLog:
    Code:
    v0.2 B20120124 
    Changes:
    * Added postrecoveryboot.sh to clear out boot command
    * Added Partition/fs Utils (useful for rom dev in formatting/checking ext4 fs)
    -e2fsck_static
    -mke2fs_static
    -resize2fs_static
    -tune2fs_static
    v0.1 B20120120 (Initial Release)

    Known Issues:
    Code:
    wrong timestamps
    Tested On:
    Code:
    Atnt LG Nitro HD  (P930)
    LG Optimus LTE (SU640)
    Thanks To:
    Code:
    schwin97
    [email protected]
    Malnilion
    repherb 
    aquariuz23
    gte460z 
    and everyone else who contributed to this thread :P
    Download:
    Code:
    http://www.mediafire.com/?mnf53sxmp5aifd9

    Source Code (Sorry , too lazy for github fttb):
    Code:
    http://www.mediafire.com/?f27d8j8d7mc8qi8

    For Rom Developers:
    It seems that default cwm format is messing up (due to ext4 file system) , Please use (edify) the following script to format the data and cache partition (or System)
    Code:
    #Format Data
    /sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p30
    #Format Cache
    /sbin/mke2fs_static -t ext4 -b 4096 /dev/block/mmcblk0p28
    
    # After Format Verify the FIle System
    /sbin/e2fsck_static -y /dev/block/mmcblk0p30
    /sbin/e2fsck_static -y /dev/block/mmcblk0p28

    Edify (To Format System):
    Code:
    run_program("/sbin/mke2fs_static", "-t" , "ext4" "/dev/block/mmcblk0p27");
    AND 
    run_program("/sbin/e2fsck_static", "-y", "/dev/block/mmcblk0p27");
    8
    The wait is over !, the news you all have been waiting for! , :D:D:D
    7
    It is similar to LG Revolution 4G (LG VS910)
    http://wiki.rootzwiki.com/LG_Revolution_Software_Breakdown
    the LG Revolution 4G (LG VS910) recovery and CyanogenMod source
    https://github.com/thecubed/android_device_lge_revolution
    Maybe you can get some inspiration from it.
    7
    delay , as im preparing for my exams :S , i did added some tools and tweaking to the init script , now accessible via adb to backup restore and perform some simple tasks via commad line , system,sdcard,internal storage is now accessible , UI is the only thing left now :s. ill be posting (hopefully) the updated reovery.img and source today

    EDIT:
    Patching the graphics.c , it seems that the swap framebuffer support is not enabled for kernel , so ill give the patched graphics.c a try before uploading the source and scrambled recovery
    7
    Ok guys its online . check the first post , flash it and let me know :D