Root ROM Manager and ClockworkMod ... many updates, questionable functionality.

[messenger13]

You guys convinced me to try ROM Manager and ClockworkMod Recovery because it is "obviously superior" in every way, shape and form. So, why so many updates ... especially for CwMod? And why does it seem that every other "update" causes something to break? And why is it that every time I tap on "Reboot into Recovery", it NEVER works. I have yet to have it boot into Recovery even once. It reboots, and that's it. O joy. Thankfully, I have the 'Boot Control' widget that boots into recovery each and every time, without fail.

Gotta tell ya folks. So far, I'm not too awfully impressed. Sure I see the added functionality. But I'm also experiencing more than my share of FAIL.

 

[Nicks88]

I have never had any of those issues that you are experiencing. I have noticed all the updates, but maybe someone will know if they are either "doin' work" or having troubles.

EDIT: Back the truck up....I did have an issue. I tried to back up a rom a few times and it was a no go. Had to flash alternate recovery and back again to get it to work. Most likely due to the numerous updates.

 

[d33z]

I have had issues getting into recovery the last 3 or 4 updates. I had to flash an alternate recovery (SPRecovery), then reflash Clockwork before I could boot into recovery. That being said...

I was able to boot into Clockwork recovery with the update that was released today. I did not have to flash an alternate recovery with this update.

 

[nstallion]

This has only really been an issue the past couple of weeks. I've run into it twice - not being able to boot into recovery and having to flash SP Recovery and back again. Other than that, ClockworkMod Recovery has always worked flawlessly for me.

What I really don't understand is what all they are doing to it with these updates. I guess I should look at the changelogs because I see no difference.

 

[YankeeDudeL]

I don't really think SPR vs CW is really an issue. They both work just about the same except CW you don't need to rename to update and SPR works faster (especially in nandroid).

As for ROM Manager, I like that I can seamlessly flash the diff recoveries, and fix permissions more than anything else. I rarely ever use a ROM from there, but it's nice to know I can if I so choose.

 

[bamaredwingsfan]

I have had issues getting into recovery the last 3 or 4 updates. I had to flash an alternate recovery (SPRecovery), then reflash Clockwork before I could boot into recovery. That being said...

I was able to boot into Clockwork recovery with the update that was released today. I did not have to flash an alternate recovery with this update.

Ive noticed this alot here in the last 7 days

 

[Eristotle]

Hmmm..I've never had it NOT reboot into recovery when I've selected the option. Reboots into recovery for me every time.

I keep rom manager and the cwm recovery seperate...at least in practice. Rom manager has become seriously bloated since its introduction and I really don't have much of a need or desire to open it that often. I simply keep and use the cwm recovery on my phone and get my files off the web like I always have. The HUGE benefit I like with the cwm recovery is to be able to flash any zip with any name that is stored anywhere on my SD card w/o having to rename everything to update.zip and having it only on the root of the card. With cwm I can flash a rom, then flash a theme, then flash a kernel without having to reboot and rename files between each flash. Also the option to wipe the boot and system partitions (as well as data and cache) is a nice feature too.

If you don't like rom manager, uninstall it. I probably should too...I rarely use it. But the cwm recovery (which is obviously my recovery of choice) remains in place until you flash back to spr.

 

[Eristotle]

Edit: Honestly, I rarely ever choose the "Reboot Into Recovery" option in Rom Manager because like I said...i'ts become bloated. I almost always do what I've done since the day I rooted my phone....hold down the x key, hit the power button, and continue holding the x until the recovery screen appears.

 

[MonmouthDroid]

I agree. I like the added functionality, but I have found a version of clockwork mod that works, and i have not updated it because every single time i update it doesn't work properly. I am still on 1.8.2.0 which is 13 updates older than the newest 2.0.1.3 version.

 

[nstallion]

Edit: Honestly, I rarely ever choose the "Reboot Into Recovery" option in Rom Manager because like I said...i'ts become bloated. I almost always do what I've done since the day I rooted my phone....hold down the x key, hit the power button, and continue holding the x until the recovery screen appears.

The problem is, recently that doesn't work either. For me, the past few updates have all broken recovery mode. Even holding down X didn't work. Have to flash SP Recovery and back after every update just to get recovery to work. Very annoying.

 

[Redflea]

I love CW Recovery, recent problems with it not launching sometimes haven't been a significant issue, the fix has been simple/fast.

I haven't had any recovery launch problems since I flashed to 2.0.1.0.

I used ROM Manager to install the JRummy 1.1 Froyo last night, and all the options it allowed me to choose in ROM Manager was very convenient and easy to use.

I do agree that the frequent updates are concerning...the more you touch code the more opportunities you have to make mistakes, but to date ROM Manager/CW Recovery have never failed to do what I ask them to do (once I get CW to launch ).

 

[messenger13]

I flashed back to SPR and was able to reboot in recovery flawlessly. Kinda funny that ROM Manager seems to like SPR better. Then I reflashed the newest CwM and rebooting into recovery werkd. About freakin time!

 

[droid_freak]

You guys convinced me to try ROM Manager and ClockworkMod Recovery because it is "obviously superior" in every way, shape and form. So, why so many updates ... especially for CwMod? And why does it seem that every other "update" causes something to break? And why is it that every time I tap on "Reboot into Recovery", it NEVER works. I have yet to have it boot into Recovery even once. It reboots, and that's it. O joy. Thankfully, I have the 'Boot Control' widget that boots into recovery each and every time, without fail.

Gotta tell ya folks. So far, I'm not too awfully impressed. Sure I see the added functionality. But I'm also experiencing more than my share of FAIL.

I would agree 100% as I have been using ROM Manager/ClockworkMod and it has been getting worse with each upgrade. I am having the same problems.

 

[OMJ]

make you guys have the erase recovery option in rom manager checked. It helps stop all this I cant boot into recovery stuff

 

[rdsok]

You guys convinced me to try ROM Manager and ClockworkMod Recovery because it is "obviously superior" in every way, shape and form. So, why so many updates ... especially for CwMod? And why does it seem that every other "update" causes something to break? And why is it that every time I tap on "Reboot into Recovery", it NEVER works. I have yet to have it boot into Recovery even once. It reboots, and that's it. O joy. Thankfully, I have the 'Boot Control' widget that boots into recovery each and every time, without fail.

Gotta tell ya folks. So far, I'm not too awfully impressed. Sure I see the added functionality. But I'm also experiencing more than my share of FAIL.

If you don't mind some unverified rumor ( unverified by me at least ) and some possible conjecture on what I think may be happening with some of these issues...

First the rumor that I've read ( and haven't taken time to read the change log to verify, too lazy and really didn't care about the details ) ... many of the updates are to support all the various phones that CW is made to work for... ie N1, Nexus, Droid etc etc... So an added function or bugfix made for only one phone would still see an update on all phones using it... in short not all updates are made for just the Droid.

For my conjecture or "theory" if you will endulge my loose use of the word ( its loose because again, I have nothing but a gut feeling to back this up )... Have you noticed the number of users reporting to having to clear data/cache etc multiple times in order to flash a new ROM, any ROM, it doesn't appear to be specific? I've always thought that it was strange that just one erase didn't automatically work... that sometimes it takes several to address the issues reported. I believe there is a clue in that alone... that the clearing isn't working 100% so when flashing either a new rom or recovery in this case, its not unusual for the first time that its written that something doesn't go 100% resulting in the issues reported. In almost all, except a few cases, the user can correct the issue by flashing a different recover and the re-flashing the new one and then it works fine. All of this seems to indicate a problem in either the hardware that is inconsistant or the flash routine that is... I've seen many issues similar to this reported with SPR when flashing ROM's but probably not as many as CWR has reported I'll grant you ( probably because of its popularity ).

I believe these issues would nearly disappear if a dev could find the underlying cause and address it. I don't think its the recovery method used that is in question... I think its the hardware or the flash routine that is the root cause of these types of troubles we've seen reported.

 

[skryer]

It has actually (finally) been working mostly well for me (all chevys kernels give me a corrupted zip error) and nandroid is still crazy slow. So i prefer my backups/kernel flashing done in SP and rom flashing done in CW

 

[gwwjpd]

You can add me to the ROM Manager/ClockWorkMod recovery FAIL list too.

I was fine and happy until yesterday, running Pete's latest with P3s 1GHz kernel with 928's Black Glass theme, Fab's NexFont.zip and a Metamorph Droidicide battery indicator in the notification bar.

The problem came when I wanted to flash a faster kernel, flashed P3's 1.2GHz, which had ran fine on my phone with other ROM's and configurations of themes and what not. No problem for about half the day, then a random reboot. Usually not a problem, just a boot into recovery and flash back to a lower kernel would fix it.

But, during the half a day running fine at 1.2GHz an "update" to ROM Manager came up. The problem, it broke recovery, so the random reboot turned into an "M", DROID, and Red Eye "Boot Loop from Hell". No amount of battery pulls would get it out of the loop. Couldn't get into recovery or load the ROM.

What to do, what to do. Well after about 30 minutes and a slight panic attack, I remembered my "In case of FUBAR" folder on my PC. It contained my solution RSD Lite and a SPRecovery file.

I connected my Droid to my computer, turned phone on, held up on the D-pad, it booted into bootloader (a good sign), ran RSD Lite to flash the recovery file. After what seemed like an eternity, finally SPRecover 0.99.3b, restored a stable nandroid, (I often backup the same setup in CM and SPRecover) now I'm back to fine and happy.

A bit scary for a while. So a big thank you to all the phone guides, moderators and poster this forum. I have learned so much about android in the last few months.

 

[StingRay]

I think it was mentioned somewhere that the primary problem is that ROM Manager is not optimized for those of us using any of the Froyo ROMs....Koush has not used any Froyo (until now that source is released) so he was not going to adjust ROM Manager for these various ROMs floating out there and that is why some of the problems have come up....

now that Froyo source has been released we should see improvements...

if I've misrepresented anything I apologize, but that is what I believe was noted elsewhere...

 

[ska.t73]

I think it was mentioned somewhere that the primary problem is that ROM Manager is not optimized for those of us using any of the Froyo ROMs....Koush has not used any Froyo (until now that source is released) so he was not going to adjust ROM Manager for these various ROMs floating out there and that is why some of the problems have come up....

now that Froyo source has been released we should see improvements...

if I've misrepresented anything I apologize, but that is what I believe was noted elsewhere...

+5

Yes you are correct the issues with the CWM flashing has to do with conflicts between 2.2 and CWM... As Koush has been known to say in the past, he will not fix things for "leaked" ROMs...

 

[wadsface]

I had a problem about a week ago (dont remember which version) with the phone sticking at the Moto logo and needing a battery pull to restart. And I would have to go in and flash SPR then reflash CW and then not choose to reboot into recovery from ROM Manager, but do it manually with restart and holding x. This problem went away in one of the updates, maybe lasted about a day and has been fine ever since.

I don't mind using SPR, it just seems to me like a reliable back-up to the feature rich ROM Manager/CWR.