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

Root New Clockwork 2.0.0.5 broken?

S

SirVilhelm

Android Enthusiast
This morning I saw that there was an update to clockwork, version 2.0.0.5. I flashed it and tried to do a rom restore but couldn't get into recovery. I eventually had to flash back to the previous recovery and do the restore. Anyone else having this issue?
 
SirVilhelm said:
This morning I saw that there was an update to clockwork, version 2.0.0.5. I flashed it and tried to do a rom restore but couldn't get into recovery. I eventually had to flash back to the previous recovery and do the restore. Anyone else having this issue?
Click to expand...

Yep, same thing happened to me, but I was going to make a backup. I even flashed alternate recovery and back to the new clockwork and tried again, but no dice. I flashed back to 1.8.2.0 and successfully made my backup.
 
Did anyone attempt to flash to SPR and then back to the 2.0.0.5 CW and try it again? I just completed a backup on 2.0.0.5 without issue ( I didn't need to flash to SPR first ) so I wonder if what happed to the others reporting problems is similar to what's been reported on past CW issues.
 
rdsok said:
Did anyone attempt to flash to SPR and then back to the 2.0.0.5 CW and try it again? I just completed a backup on 2.0.0.5 without issue ( I didn't need to flash to SPR first ) so I wonder if what happed to the others reporting problems is similar to what's been reported on past CW issues.
Click to expand...


+1 mine is working fine.
 
I just flashed 2.0.0.5 as well, and rebooted into recovery without a hitch. I'm thinking it might have been 2.0.0.4 that caused my initial problem.
 
My Droid would not boot into clockwork recovery the first time that I flashed 2.0.0.5. So I flashed SPrecovery, then back to Clockwork 2.0.0.5, and was able to boot into Clockwork recovery and make a backup.
 
d33z said:
My Droid would not boot into clockwork recovery the first time that I flashed 2.0.0.5. So I flashed SPrecovery, then back to Clockwork 2.0.0.5, and was able to boot into Clockwork recovery and make a backup.
Click to expand...

+1...was trying to put Kangerade on but couldn't get into recovery so flashed SPRecovery and then back to 2.0.0.5 and voila...worked
 
CW 2.0.0.4 was giving me fits last night and today. YAY for the fixed update! No matter what I did I couldn't get into recovery, but it immediately worked on 2.0.0.5 :)

....on second thought, it may have been the update to Rom Manager, which prompted the CW update. At least it's all working again!
 
I just flashed a Chevy kernel right now on 2.0.0.5 no problem. I'll try to make a backup of my BB ROM through ROM manager.

*edit* Backing up seems to be successful as of right now (still going). Here's a question for you guys: Are you accessing CW through ROM manager, or manually booting into it? That could be the difference.
 
2.0.0.5 is dead for me. Won't even boot into recovery. I flashed back to 2.0.0.3 and that is working ok.

Joe
 
Same problems here... 2.0.0.5 just hangs at the Motorola logo when I try to backup or install. After moving back to 2.0.0.3 all is well.
 
Initially had issues rebooting to recovery from rom manager,that's resolved, always could get into it nanually (ctrlX).

My problem is even though it appears to create backup, I can't find the backup anywhere. This only happens on rom manager, if I manually launch cmrecovery itworks fine.
 
FYI, there is a new version out and it MAY have fixed it? Haven't had problems with it since i flashed new one: 2.0.0.7.
 
I was having the nothings happening problem, and i had to flash back to Sp then back to CW and now it seems to have fixed my problem.
 
Though bugs may of course show up in a particular version of CW Recovery, from my experience w/these problems w/recovery not launching, I really think this is an issue w/ROM Manager downloading/flashing CW Recovery...something in that process isn't working reliably on Froyo. Otherwise flashing to an older recovery and then back to the same one wouldn't be able to fix things. In the end it seems like the fix needs to come from ROM Manager, not from a particular version of CW Recovery.
 
You must log in or register to reply here.
Back
Top Bottom