Clockworkmod freezes while recovering data

KhaosKid

Member
Dec 16, 2010
9
0
0
(Please forgive me for my incredibly novice knowledge of this topic) I decided to install stock Froyo in the sticky thread above but before that, I had backed up everything through Clockworkmod. I flashed everything, and went to the CwM recovery screen (the one with the red text) and went to advanced restore. I then selected recover data. It seems to be working fine until it gets to the file "c93d8eae," at which it freezes. Does someone know any work arounds for this?
 
(Please forgive me for my incredibly novice knowledge of this topic) I decided to install stock Froyo in the sticky thread above but before that, I had backed up everything through Clockworkmod. I flashed everything, and went to the CwM recovery screen (the one with the red text) and went to advanced restore. I then selected recover data. It seems to be working fine until it gets to the file "c93d8eae," at which it freezes. Does someone know any work arounds for this?

There is no workaround. You don't use advanced restore. You use the one above it that just says restore.
 
I tried the default restore and it restored the system, but halted at the exact same place during the data restore.
 
How long are you waiting for it to try to work? Depending on the size of your backup, a restore can take up to 10-15 minutes. I tend to just put my phone down and ignore it for a bit when I'm doing this as to prevent the "it's not working, ill try again" syndrome.
 
Well it gives me progress, telling me which file specifically is being restored currently. But this particular file will not restore. It halts the process and I've let it sit idle for a good half an hour before finally killing it. It just won't progress past that point.
 
Well it gives me progress, telling me which file specifically is being restored currently. But this particular file will not restore. It halts the process and I've let it sit idle for a good half an hour before finally killing it. It just won't progress past that point.

I restore the specific storage files using titanium backup. Could be worth looking into for ya. It's much easier that way if you ask me.
 
Well I looked into Titanium Backup, and it seems like I can only restore backups made specifically through Titanium Backup.
 
This is probably the specific issue GizmoDroid identified (with my help, ok, it was pretty much all him but I got the ball rolling) and then he and jt1134 corrected with the latest cwm. When you are in clockworkmod recovery, before you restore a nandroid, from the main cwm menu, scroll to mounts and storage and make sure it says mount in front of dbdata and data. Then try restoring your nanndroid backup. Eventually it would be a good idea to flash the latest cwm via ODIN:

cwm-recovery-ALL-3-30-FIX.tar
 
Both of those are set to mount, and I flashed the CwM Recovery included in your post. Should I retry the restore?
 
Actually now that I read that, I'm not sure it really applies to or helps you. That is mostly dealing with running into a FC boot loop after you finish restoring a nandroid backup. It doesn't mention anything about hanging up during the restore. Sorry.
 
:( Is there any way I can get this backup to go through?

Which recovery were you using the first time you got stuck during your restore? Was it the last red cwm-all or the red cwm froyo which looks the same but had the bitmap error messages in white lettering toward the bottom of the screen like below?

E:Missing bitmap progress_empty (code -1)
E:Missing bitmap progress_fill (code -1)
CwM Voodoo Lagfix Recovery v2.5.1.x
 
The first time I got stuck, I was using red cwm-all.

Sorry, I'm at a loss. I know the previous iterations of cwm all had problems restoring nandroid backups, but I can't remember seeing anything about the restore not finishing. Hopefully someone smarter than me will see this and can lend a hand.
 
When you are in clockworkmod recovery, before you restore a nandroid, from the main cwm menu, scroll to mounts and storage and make sure it says mount in front of dbdata and data.

If it says mount, it means you're currently not mounted, thus, giving you the option. You want it to say unmount, which would imply that you currently are mounted. It's a 2 way toggle so you're only given the opposite choice of your current state. Just like if a light switch is on, the only thing you can do with it is turn it off.
 
Okay so I mounted the two options that had previously been unmounted (Thanks for the correction), and retried the recovery. It stalled at the same place, on the same file.
 

Trending Posts

Forum statistics

Threads
957,080
Messages
6,971,382
Members
3,163,709
Latest member
texmaster