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

Root OFFICIAL CWM 6.0.2.7 and CWM Touch

superr said:
you are in fastboot mode (green android, red led). Put the recovery.img in your adb directory, and enter the following:

[HIGH]fastboot flash recovery recovery.img[/HIGH]
[HIGH]fastboot reboot[/HIGH]

enjoy
Click to expand...

what do you mean put the img into the adb directory? i have the img in the platform-tools folder right now, is that right? and the platform-tools folder is in a folder called Android, which is in my C Drive
 
benjiu3 said:
what do you mean put the img into the adb directory? i have the img in the platform-tools folder right now, is that right? and the platform-tools folder is in a folder called Android, which is in my C Drive
Click to expand...

yes, if fastboot is in the platform-tools directory then the img should be there, and if its not named recovery.img dont put
fastboot flash recovery recovery.img

it wont work, because there is no file there called recovery.img
either change the file name to recovery or put in what the file is called in the fastboot command, like if you downloaded it from my link it would be
fastboot flash recovery CWM-6.0.2.7-warp2.img
exactly like that
 
junkie2100 said:
yes, if fastboot is in the platform-tools directory then the img should be there, and if its not named recovery.img dont put
fastboot flash recovery recovery.img

it wont work, because there is no file there called recovery.img
either change the file name to recovery or put in what the file is called in the fastboot command, like if you downloaded it from my link it would be
fastboot flash recovery CWM-6.0.2.7-warp2.img
exactly like that
Click to expand...

yea the img was already renamed to recovery. so i put "fastboot flash recovery recovery.img" and it says waiting for device. its still in fastboot mode
 
ok well if it hasnt been unplugged since going into fastboot mode then you are unable to use the fastboot method. restart the phone manually by pulling the battery then use this adb install method

adb push recovery.img /sdcard/cwm.img
adb shell
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p13
rm /sdcard/cwm.img
reboot recovery

and that should pop cwm right up
 
benjiu3 said:
yea the img was already renamed to recovery. so i put "fastboot flash recovery recovery.img" and it says waiting for device. its still in fastboot mode
Click to expand...

Same thing happend to Me wen i first Tried installing Cwm. If u got into device management in ur computer n unkown device shows up WHILE ur in fastboot Mode, then U have to install a driver for that. Guspeed helped Me out wit this b4 but i figured That out on my own
 
junkie2100 said:
ok well if it hasnt been unplugged since going into fastboot mode then you are unable to use the fastboot method. restart the phone manually by pulling the battery then use this adb install method

adb push recovery.img /sdcard/cwm.img
adb shell
su
dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p13
rm /sdcard/cwm.img
reboot recovery

and that should pop cwm right up
Click to expand...

when i got to the part where i had to type in "dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p13" it says cannot open for read: no such file or directory
 
yea, i figure its easier to just do the adb method than try to explain the steps to driver checking and fixing again. ive posted the steps to do it a couple different times on other threads but i dont remember where and i dont feel like searching for them, plus there is always the issue when you are using pre-usb 2.0 spec ports, i fought with that one for days and ended up having to learn the adb method kuz i was physically incapable of using fastboot with my computer
 
benjiu3 said:
when i got to the part where i had to type in "dd if=/sdcard/cwm.img of=/dev/block/mmcblk0p13" it says cannot open for read: no such file or directory
Click to expand...

ok but did the adb push command say it sent it? if the adb push doesnt work its not gonna be on there. and if you changed ANYTHING even a single letter of capitalized something it will not work correctly, you must input everything EXACTLY as i instructed
 
junkie2100 said:
yea, i figure its easier to just do the adb method than try to explain the steps to driver checking and fixing again. ive posted the steps to do it a couple different times on other threads but i dont remember where and i dont feel like searching for them, plus there is always the issue when you are using pre-usb 2.0 spec ports, i fought with that one for days and ended up having to learn the adb method kuz i was physically incapable of using fastboot with my computer
Click to expand...

before you replied again i tried the fastboot method again.
so i think i got it to work!!!
on cmd it says
finished. total time: 1.782s

does this mean it worked?? its still in fastboot
 
also, if you do not have an sd card in the phone
A this will not work
and
B you cant make a backup or install a zip without an sd card so there is no real point to having cwm
 
benjiu3 said:
so i think i got it to work!!!
on cmd it says
finished. total time: 1.782s

does this mean it worked?? its still in fastboot
Click to expand...

yes that should mean it worked
fastboot reboot and immediately hold the down volume and power buttons before the android pops up and it should give you clockworkmod
 
why not do adb reboot bootloader?

Then adb fastboot flash recovery recovery.img? It will work the same and is easier imo

Plus it flashes straight from your PC skipping the sdcard all together
 
shinru2004 said:
why not do adb reboot bootloader?

Then adb fastboot flash recovery recovery.img? It will work the same and is easier imo

Plus it flashes straight from your PC skipping the sdcard all together
Click to expand...

he was having fastboot issues, which in that case using an alternate method is easier than trying to debug someone elses computer via forum posts lol
 
junkie2100 said:
he was having fastboot issues, which in that case using an alternate method is easier than trying to debug someone elses computer via forum posts lol
Click to expand...

This is very true :p And thank you for your hard work. You managed what PlayfulGod, Myself, Downthemachine, and a few others couldn't.... :)

I have to ask though how did you do it?
 
shinru2004 said:
This is very true :p And thank you for your hard work. You managed what PlayfulGod, Myself, Downthemachine, and a few others couldn't.... :)
Click to expand...

thank you, and it was my pleasure, i was dieing to get a stable recovery myself and see what roms would come of it so i did everyone a favor including myself, and if it will help you out at all in your work our device tree is here

http://androidforums.com/warp-sequent-all-things-root/669558-cm10-development.html

it seemed to fix things when we uncommented the line referring to the custom init (recovery.rc) it was either that or referencing the other kernel, all our work is spelled out in this thread

http://androidforums.com/warp-sequent-all-things-root/669168-cwm-6-development.html

it was all based off of playfulgods tree, just alot of editing of the boardconfig.mk and recovery.rc
not 100% sure what finally flipped that switch and made everything stable but i know it happened right after we changed what kernel we were building with and uncommented the line about using a custom recovery init from playfulgods original boardconfig.mk file
i have a feeling it was the init part though and my init is just a mashup of alot of different sources i picked apart
as you can see though in that thread, it just kinda started working all the sudden. we were about to give up for the night lol
 
basically playfulgod had a very good start, it just needed to be tweaked in the right manner to function. and after ALOT of trial and error we found the switch and on came the lightbulb

once i saw what driver the computer was using when it rebooted to a black screen, i realized what the phone was doing when it rebooted itself (going into ftm mode) and i figured out that it had to be something to do with a command passed to the device after being booted, what im thinking is that we were just using the default init file which contained info on starting the ftm mode, so once it ran through all the normal commands it would go through those because it wouldnt know to stop, that knowledge was programmed into the original recovery but its not in ours. so it would just keep executing and force us into ftm mode after a couple minutes
 
junkie2100 said:
yes, anything that worked on the old clockworkmod will work on this clockworkmod
Click to expand...

so, I tried flashing your Deodex_Sequent.zip without success.

What I did:
boot into recovery
went to mounts and storage
format cache, system, data (no boot?)
went to advanced
wipe dalvik cache
install zip from sd
chose Deodex_Sequent.zip
flashed without errors
reboot system
stuck on green android guy
CWM backup saved the day

edit: I realize this is not necessarily the correct thread, but it might have something to do with cwm since it seemed to work for others using cwm4
 
superr said:
so, I tried flashing your Deodex_Sequent.zip without success.

What I did:
boot into recovery
went to mounts and storage
format cache, system, data (no boot?)
went to advanced
wipe dalvik cache
install zip from sd
chose Deodex_Sequent.zip
flashed without errors
reboot system
stuck on green android guy
CWM backup saved the day

edit: I realize this is not necessarily the correct thread, but it might have something to do with cwm since it seemed to work for others using cwm4
Click to expand...

lol umm dude, you formatted your system partition. who told you to format your system partition? that is a HORRIBLE idea. try it again, this time only wipe cache and dalvik
 
I have always formatted my /system. Learned from the pros over at AC in the Optimus V forums. How else do you remove the files when you change roms?
 
while i have you here tho, i was wondering if you could do something for me, i wanted to run a test of sorts. put this recovery.rc im about to upload into our tree and rebuild to see if it will enable ftm mode or just screw things up
 
You must log in or register to reply here.
Back
Top Bottom