Clockwork Recovery update

I uninstalled rom manager and reinstalled rom manager and now from rom manager I can initiate a back up or a restore. Before this I was getting a bott loader loop. Also if I initiated a "reboot into recovery" from rom manager it would get to recovery, but on the way there I would see an awful screen of color looking like an original Nintendo game that froze up.
 
Arghhh! I uninstalled ROM MGR and reinstalled. Saw the new 3.0.0.1 and flashed through Rom Mgr. Stuck in bootloader again. So went back and flashed PC.zip file back to good 2.? version, updated to 3.0.0.0, which works in Rom Mgr. When I reboot from the Orange recovery in 3.0.0.0 I get the crazy color screen as well, but it does reboot.
 
I am having an issue as well. I used Unrevoked 3 to Root (which installed Clockwork. I updated Clockwork thru ROM Manager today to 3.0.0.1. When I boot into Recovery thru ROM Manager it still says 2.5.0.1. I have rebooted the EVO an few times and that does not help. In ROM Manager it says the version is 3.0.0.1. I uninstalled and reinstalled and still the same issue. Does anyone know what the issue could be. My recovery screen is still green. Thnaks
 
Don't use freds p36 zip anymore, its been updated after that, I have the 3.0 version and it works fine. Update through rom manager.

Clockworkmod DOES wipe dalvik.

The only thing amon does that clockworkmod can't is it backs up your wimax partition, so I always keep 1 nandroid from among ra just in case I mess up my 4g.

Clockworkmod works fine.
 
  • Like
Reactions: 2CupsWithString
Don't use freds p36 zip anymore, its been updated after that, I have the 3.0 version and it works fine. Update through rom manager.

Clockworkmod DOES wipe dalvik.

The only thing amon does that clockworkmod can't is it backs up your wimax partition, so I always keep 1 nandroid from among ra just in case I mess up my 4g.

Clockworkmod works fine.


Well, I am not sure, BUT it looks like the Clockwork backup now includes the Wimax (it now creates a winax file on any new backup created)
 
  • Like
Reactions: igotsanevo4g
I installed clockworkmod recovery 3.0.0.0 today and flashed my kernel with it and had no problems.
 
Word over at XDA is that CW3 needs newer hboots to work right. - Which I think is pretty funny since I've been crusading for hboot .76 - kind of makes sense though I guess.
 
Well im never giving up my 76 hboot, til death.

Im also going to do a back up and restore with the new hboot to see how it goes.
Then test if it will restore older backups.

Ive flashed cm6.1.2 over 6.1.1 and all was well so it still flashes stuff right. So far...
 
Last edited:
+1,000

thankfully I made a nandroid yesterday, I had to fastboot flash 2.5.0.1 back to get a restore that worked. I had 3.0, it backed up fine, the restore blew up right in my .76 hboot face lol.

I guess htc really drew a line in the sand here with hboot 2.10.
 
Doing a restore of the new nandroid i just made... Hope my phone doesnt catch fire, steal my TV and run down the street.

Update-Working so far :cool:
 
It actually... Worked great! :D
Gonna try to restore an older one right now.
Gosh my phone is a tank, i think its afraid to brick on me. Ill whip its ass if it does permanently lol
 
LOL that's awesome. On my 3.0 restore I just got FCs all over the place, I tried a cache/dalvik wipe & fix permissions but still no joy.
 
LOL that's awesome. On my 3.0 restore I just got FCs all over the place, I tried a cache/dalvik wipe & fix permissions but still no joy.

THANK YOU for you help getting me back to 2.5.0.1
where i never had one single issue using that CWM issue

i went against my better judgement, flashing a v .0 today !
thanks again !
 
Now ANOTHER update is being pushed. I accepted cause im a nut. Its 3.0.0.2

Testing now... haha

Update, works great. I restored an old back up of gingerbread and flashed a kernel in there. Well this was after a aborted installtion of an update for the AC rom in the works, but it was probably the rom and not the recovery.
 
Last edited:
I got the update as well to test it out and still no good for me, it's fine on the backup but no good on the restore. (lol just got a random rom reboot as I was typing this).