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

Root clockwork mod 3

androidlover14

Android Enthusiast
Ok so I have been trying to flash this in terminal but have been having no luck. Does anyone know how to get this working? The post about it is in the cyanogen section of droid haacks on droidforums.net.

EDIT: Ok so I got it working. If anybody wants to use CW 3.0.0 just do the following.

Disclaimer: Up to my knowledge it has been working on the OG Droid but I don't see why it won't work on a phone like the nexus one which is stock android. I also take no blame if you mess up your phone in the process.

1) Download the recovery Link
2) Go to Root Explorer (or any other file manager the gives you access to system) and check system/bin or system/xbin for a flash_image file.
2a)If you don't have the file in either download it from here.
2b) If you had to download the flash image then unzip it, long press the flash image inside of the file, press permissions and check the whole top row.
3) In Root Explorer go to system and press Mount R/W. Then move the flash image into system/bin or system/xbin (I moved it into system/bin fwiw).
4) Finally in terminal do the following steps exactly as written/typed.

$su
#flash_image recovery /sdcard/sholes-cwm3src-2.img
#reboot recovery

*Pay attention to the spaces and the underscores!
Enjoy:D
 
I think you have to flash SPR once and then reflash CW3 in ROM Manager and it'll take. Thats worked for me about 4 times in the past 5 days...I'm going ROM Crazy...Switching and trying new ones...Hope that helps...

KevO
 
Yes. But I wasn't surprised at CyanogenMod getting updated, I was surprised at nobody else updating their ROMs on it (and ClockworkMod, which Koush himself makes, right?). For me at least, it's a lot more enticing to try out a ROM, kernel, etc when it's on ROM Manager.
 
Yes. But I wasn't surprised at CyanogenMod getting updated, I was surprised at nobody else updating their ROMs on it (and ClockworkMod, which Koush himself makes, right?). For me at least, it's a lot more enticing to try out a ROM, kernel, etc when it's on ROM Manager.

Yeah I just love the simplicity of it being right there almost instantly in your possession.
 
From what I have seen and experienced its just design changes and performance boost as in faster backups and installation. More organized. Also needed to install CM7 supposedly.
 
Have they moved "wipe /sdcard" to somewhere where I'm not paranoid of accidentally pressing it when I'm wiping the other partitions while installing a new ROM?
 
Have they moved "wipe /sdcard" to somewhere where I'm not paranoid of accidentally pressing it when I'm wiping the other partitions while installing a new ROM?

No, actually, but I'm always terrified I'll do it whenever I'll go to wipe /cache. :P

That would be why it is a two step process, so you should be reading that second page carefully where you have all the nos and the one yes that you have to scroll to get to.
 
That would be why it is a two step process, so you should be reading that second page carefully where you have all the nos and the one yes that you have to scroll to get to.

It doesn't mention anywhere on that second page what you're wiping, so if you accidentally hit wipe /sdcard instead of wipe /cache, you'd think you were saying yes to wipe /cache until it started wiping /sdcard.
 
It doesn't mention anywhere on that second page what you're wiping, so if you accidentally hit wipe /sdcard instead of wipe /cache, you'd think you were saying yes to wipe /cache until it started wiping /sdcard.

This is why I always use factory reset to wipe data and cache, then go into the partitions menu (mounts and storage in CW 3) to wipe boot and system, which keeps me from getting anywhere near format sdcard, and there's no way I can do that accidentally.

Thanks for the instructions androidlover -- worked perfectly! But wow, that bright orange is almost too much!
 
This is why I always use factory reset to wipe data and cache, then go into the partitions menu (mounts and storage in CW 3) to wipe boot and system, which keeps me from getting anywhere near format sdcard, and there's no way I can do that accidentally.

Thanks for the instructions androidlover -- worked perfectly! But wow, that bright orange is almost too much!

your welcome;). I have heard that there might be another new version of clockwork so I'll try to keep you guys posted.
 
It doesn't mention anywhere on that second page what you're wiping, so if you accidentally hit wipe /sdcard instead of wipe /cache, you'd think you were saying yes to wipe /cache until it started wiping /sdcard.

I've doubted myself plenty of times - so I go back and double check myself.

This is why I always use factory reset to wipe data and cache, then go into the partitions menu (mounts and storage in CW 3) to wipe boot and system, which keeps me from getting anywhere near format sdcard, and there's no way I can do that accidentally.

Thanks for the instructions androidlover -- worked perfectly! But wow, that bright orange is almost too much!

Yeah, that is not too pretty at all.
 
Well, I had a pretty bad experience with CW3 last night. I kept getting low memory resources errors when I tried to flash the image on my current ROM, so I needed to backup my current ROM, then boot into recovery, wipe everything and install a new ROM. Once I successfully flashed CW3, I restored the ROM I had been using, but it took me a little while to realize that some of my system apps, which were working perfectly before I started all of this, didn't restore correctly (neither my Market nor Calendar apps would launch, and when I tried to use an update zip to reinstall those apps to /system/app, they still wouldn't work. Then other things started going wonky -- for instance, all of the apps installed on my SD card went missing (not just the icons from my launcher, I'm saying they weren't installed at all anymore). This was particularly weird, because they were there when I first booted up after the restore. I tried booting back into recovery and wiping all the partitions again prior to doing another restore, but I got errors in trying to wipe both system and boot. I restored the original backup again anyway, and continued having the same problems.

So, I went into ROM Manager and flashed back to CW 2.5.0.1 (which took several tries of flashing alternate recovery and CW before it held), booted into recovery again and successfully wiped all partitions (no errors) then restored the exact same backup I had originally made and guess what? Everything restored perfectly this time. All of the my /system/apps, including Market and Calendar are working perfectly again and I've seen no other weird issues.

Anyway, I thought I would report this in case anyone else had a bad experience restoring a backup using CW3. Bottom line is, if you flash back to 2.5.0.1, your backup should once again restore properly. Needless to say, at least for my Droid, CW3 isn't a good fit!
 
Thanks for the report. I am wondering about this new version as it is not coming from the usual channels. Koush is involved with Cyanogen, but he has moved on to the Incredible as far as porting CM. He is (I thought) the author of both Rom manager and CMRecovery, however when you go to clockworkmod.com now, it says it's under construction. (?) Finally, I went to koush's website this morning and he said the next version of rom manager will not be dependant upon CMRecovery only, but if your custom recovery isn't compatible with the 'pss off' commands from RM, it may not work properly.

Oh, and there was a newer version of this CMR3 released, it's called "cwm-3.0.0.5.img" and I have it in my huge folder below.
 
Does CW3 do a better job recognizing 32GB microSD cards? Clockwork2.5 chokes on it half the time and doesn't recognize it. Makes swapping ROMs, backup/restore a royal pain :p
 
there seems to be a problem with restoring backed up roms with #3...for some reason it neglects to install the google apps, ie; no market, no talk, no calendar sync, etc. I have no idea how or why, but when I flashed back to #2.5.whatever this problem went away...after I formatted and re-partitioned my sd and in general wondered wtf is going on.
 
Back
Top Bottom