• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root ClockWorkMod

salvy512

Android Enthusiast
May 22, 2012
271
53
Currently talking to someone who is trying to help us create a CWM for our phone and he says that this is his first build


-SPECIAL THANKS TO utkanos at rootzwiki who built this, and to the CWM team for there hard work on recovery :).


I am NOT responsible for what happens to your phone, I am not sure what this can do to your phone, I did not test this on my phone so i cannot confirm ANYTHING about it.

You must be rooted to try this

Recovery Test1 Link:
Pulled until further notice.

This may help you, this may not
Flashing instructions:

When I have it working I will post the recovery and the instructions again, pulled until I can get it working.





This did not work for me, I did trywith these instructions but my phone does not recognize the flash_image command and that must be because we don't have one lol. Im not sure how else to do it though
 
Flash_Image does not come on a stock rom and must be installed. Download the zip from this top of this link

Flash image - CyanogenMod Wiki

Extract the zip and place this flash_image file on your sdcard.

Use a root file manager to copy it to the system > bin folder

Open terminal and run the following 2 command

SU

mount -o rw,remount /system /system

chmod 755 /system/bin/flash_image

Reboot to remount system as ro and you should now have working flash_image
 
Upvote 0
Flash_Image does not come on a stock rom and must be installed. Download the zip from this top of this link

Flash image - CyanogenMod Wiki

Extract the zip and place this flash_image file on your sdcard.

Use a root file manager to copy it to the system > bin folder

Open terminal and run the following 2 command

SU

mount -o rw,remount /system /system

chmod 755 /system/bin/flash_image

Reboot to remount system as ro and you should now have working flash_image

$ su
su
# mount -o rw remount /system /system
mount -o rw remount /system /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o rw,remount /system /system
mount -o rw,remount /system /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/build1.img
flash_image recovery /sdcard/build1.img
error scanning partitions: No such file or directory
#
 
Upvote 0
$ su
su
# mount -o rw remount /system /system
mount -o rw remount /system /system
Usage: mount [-r] [-w] [-o options] [-t type] device directory
# mount -o rw,remount /system /system
mount -o rw,remount /system /system
# chmod 755 /system/bin/flash_image
chmod 755 /system/bin/flash_image
# flash_image recovery /sdcard/build1.img
flash_image recovery /sdcard/build1.img
error scanning partitions: No such file or directory
#

So looks like flash_image went in ok but is having an issues either seeing the sdcard or recovery file or is having an issues detecting the recovery partition

Let me see what I can find. I wonder since this phone is emmc it may not work

Edit.. Looks like from looking at other phones that flash_image doesn't work on phones setup with mmc. It works on phone with yaffs like the optimus V.. We're gonna have to have another method.. If I'm wrong someone correct me please
 
Upvote 0
Quote from a post by jcase in the "let's get the... "
# mount point fstype device [device2]

/cache ext4 /dev/block/mmcblk0p6 #/misc emmc /dev/block/mmcblk0p8 /misc emmc /dev/block/mmcblk0 /boot emmc /dev/block/mmcblk0p9 /system ext4 /dev/block/mmcblk0p12 /data ext4 /dev/block/mmcblk0p13 /recovery emmc /dev/block/mmcblk0p14

/sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0 /sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

we probably could run a dd command to the block listed here. We also would need to have busybox installed. By the way this list was pulled from the. Tot file.
 
Upvote 0
Quote from a post by jcase in the "let's get the... "
# mount point fstype device [device2]

/cache ext4 /dev/block/mmcblk0p6 #/misc emmc /dev/block/mmcblk0p8 /misc emmc /dev/block/mmcblk0 /boot emmc /dev/block/mmcblk0p9 /system ext4 /dev/block/mmcblk0p12 /data ext4 /dev/block/mmcblk0p13 /recovery emmc /dev/block/mmcblk0p14

/sdcard vfat /dev/block/mmcblk0p15 /dev/block/mmcblk0 /sdcard/_ExternalSD vfat /dev/block/mmcblk1p1 /dev/block/mmcblk1

we probably could run a dd command to the block listed here. We also would need to have busybox installed. By the way this list was pulled from the. Tot file.

I showed the guy this :
/recovery emmc /dev/block/mmcblk0p14
 
Upvote 0
So, who is brave enough to try this?

Code:
adb push build1.img /data/local/tmp/build1.img
adb shell
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/dev/block/mmcblk0p14 of=/sdcard/mmcblk0p14.backup bs=4096
dd if=/data/local/tmp/build1.img of=/dev/block/mmcblk0p14 bs=4096

For those with more experience, do I have anything wrong here?

Should I just give it a shot?
 
Upvote 0
So, who is brave enough to try this?

Code:
adb push build1.img /data/local/tmp/build1.img
adb shell
su
mount -orw,remount /dev/block/system /system
mount -orw,remount /dev/block/data /data
dd if=/dev/block/mmcblk0p14 of=/sdcard/mmcblk0p14.backup bs=4096
dd if=/data/local/tmp/build1.img of=/dev/block/mmcblk0p14 bs=4096

For those with more experience, do I have anything wrong here?

Why data local tmp? Instead of .backup maybe .img? Otherwise looks good to me as you will be backing up the block.
 
  • Like
Reactions: ktb83
Upvote 0
1. No reason really, I suppose I could just push it to the sdcard or other locations. After some searching i just found that this way worked for others, so I wasn't going to stray...

2. .img would be fine too.

Thanks.

i tried the commands you gave and im stuck in bootloop
man I fail =/ It only boot loops if I try to boot recovery
 
Upvote 0

BEST TECH IN 2023

We've been tracking upcoming products and ranking the best tech since 2007. Thanks for trusting our opinion: we get rewarded through affiliate links that earn us a commission and we invite you to learn more about us.

Smartphones