I have made many NANDROID backups in the past and today when I went to make my monthly backup it will not complete. It hangs on the last step "Generating md5 sum". Any idea??????
More info:
I went ahead and did a restore using the stalled backup and it did restore and boots up like normal. Clockwork Recovery must be screwed up, but at least the backup works.
How long did it stay? Mine take 10 minutes or so.
Sent from my ADR6300 using XDA App
I have never had it take 10 min in the past to make the md5 so after 4-5 min I am assuming it has hung. After battery pull there is a md5 file and I used that backup to do a restore to test it and it worked ok so I think clockwork is just not completing and showing done and/or rebooting when it is complete. It is not a huge problem I guess since I managed to get a backup that works.
I too have been having issues with making and reloading backups. Mine get hung up on generating MD5 sums and also Checking MD5 sums. I don't receive any errors at all, it just freezes when trying to create the back up and restore the backup. What gives?
I was using CWM 2.5.1.2 and downgrade to 2.5.1.1 and still same. I now downgrade to CWM 2.5.0.5 and it completed the md5 withint 90-120 sec. So I guess I am keeping the older version of CWM.
wpbear said:
More info:
I went ahead and did a restore using the stalled backup and it did restore and boots up like normal. Clockwork Recovery must be screwed up, but at least the backup works.
Click to expand...
Click to collapse
This is a known issue on newer builds of Clockwork. Mine generally takes 10 mins to generate MD5. Older versions of clockwork are still quick. Just give it time and it will finish.
Ok thanks. Is there any benefit of the newer builds that I will miss if I just keep using the older 2.5.0.5 instead of 2.5.1.2?
wpbear said:
Ok thanks. Is there any benefit of the newer builds that I will miss if I just keep using the older 2.5.0.5 instead of 2.5.1.2?
Click to expand...
Click to collapse
newer clockwork supports slcd... older clockwork only works on amoled and allows for 10pt multi-touch.. my backup only takes maybe 2-3 min tops but it is definitely longer than before
wpbear said:
Ok thanks. Is there any benefit of the newer builds that I will miss if I just keep using the older 2.5.0.5 instead of 2.5.1.2?
Click to expand...
Click to collapse
besides being able to actually backup and restore? lol no you can search for a topic called "clockwork mod...on crack" and it will give u the speed increase for scrolling with the trackball. im one of the 1st ppl here to post a problem with 2.5.1.1 so yea if u have an amoled don't use cwm higher than 2.5.0.5...it just messes **** up
Sent from my ADR6300 using XDA App
Thanks for this thread....I can't count how many times I've lost my current set up because I thought my phone froze when it said MD5sum............so I should just wait right, it'll eventually finish correct?
Sent from my ADR6300 using XDA App
BTW, how does one revert back to previous versions of ROM manager?
Sent from my ADR6300 using XDA App
Related
I have a problem, I am running FR007 and I can't get Clockwork to make a working backup. If I try to restore from the backup it gives MD5 error. I also tried using Rom Manager and it gives me the android with the triangle error. What do I need to do to get a working backup.
Try titanium backup or Astro File Manager.
tbone22 said:
I have a problem, I am running FR007 and I can't get Clockwork to make a working backup. If I try to restore from the backup it gives MD5 error. I also tried using Rom Manager and it gives me the android with the triangle error. What do I need to do to get a working backup.
Click to expand...
Click to collapse
Out of curiosity, when you turn off your phone or, restart it, whatever it is that you do to get into clockwork...do you have your phone plugged in with the usb cable?
Yeah I get into clockwork and do a android backup but if I try to restore I get an,error. MD5 something. Titanium and astrology don't do android do they.
Sent from my HTC Liberty using XDA App
tbone22 said:
Yeah I get into clockwork and do a android backup but if I try to restore I get an,error. MD5 something. Titanium and astrology don't do android do they.
Sent from my HTC Liberty using XDA App
Click to expand...
Click to collapse
lol @ astrology. damn auto correct lol. anyway, you didn't pay attention to my question. do you have your phone hooked up to usb when you are rebooting to go into clockwork?
Yeah auto correct gets me alot. And no I don't have anything hooked to the phone when I try to backup.
Sent from my HTC Liberty using XDA App
are you renaming the backup folder?
No. It won't sync with HTC sync either if that helps.
Sent from my HTC Liberty using XDA App
same thing happened to me for almost all of my backups, i think it was because i put in a custom kernel. I switched back and it started to work again.
I'm having a problem with nandroid restore where it gives me a md5 mismatch. I never renamed a file or anything. If I cant do nandroid restore then I don't feel safe flashing rc1. I see there is a md5 fix in these forums but don't want do it unless I know it will work with aria. Can somebody lead me the way please and help a buddy out. Thanks you guys are the best.
Sent from my Liberty using XDA App
tommyguns818 said:
I'm having a problem with nandroid restore where it gives me a md5 mismatch. I never renamed a file or anything. If I cant do nandroid restore then I don't feel safe flashing rc1. I see there is a md5 fix in these forums but don't want do it unless I know it will work with aria. Can somebody lead me the way please and help a buddy out. Thanks you guys are the best.
Sent from my Liberty using XDA App
Click to expand...
Click to collapse
Is it an old (i.e. done a while ago) back up? Take a new back up then try to restore it right away...see if it gives you the same error. Make sure, when you are booting into clockwork, that you don't have USB plugged in.
also make sure you are not connected to your charger when doing it, i had the same problem but when i took it off the charger it worked fine. see if that works for you.
ok same problem....
i did a recent back up (without phone being plugged into computer) and couldn't restore it. it gives me md5 mismatch. any takes at this mount!! nandroid is broken!!!!
So I think its my new eBay 32gb I got. Cause I put back the og 2gb and deleted abunch of crap, like pics and stuff that were already backed up. And backed up and finally restored.....yay. no md5 mismatch. But it did say something like there's no sd-ext skipping?
Sent from my Liberty using XDA App
no sd ext just means you didn't partition your sd card, so don't worry about that.
Sent from my Desire HD using XDA App
ive been rooted for quite some time, and never have had trouble with pulling backups form clockwork recovery. last night i made a backup of my CM7.0.3 that i was using for a while to try out virtuous unity. today on my lunch break at work i attempted to load the backup and i was getting that error message.
i did a "superwipe for g2" right before i tried to recover.
then i attempted to recover my stock rom i have had for months an i got the same error message. any ideas? the only thing i could think of is a few days ago i cleared out a HUGE cache in my clockwork from my SD to clear up my card. could that be it? any help would be appreciated.
bump.
someone please give me some help! i would really appreciate it.
i attempted this
http://forum.xda-developers.com/showpost.php?p=11768066&postcount=2965
but go no response and still had a md5 mismatch.
Had that issue before... The back up process didn't go right unfortunately. I would recommend you to download another Rom and transfer it to your SD card.
Sent from my HTC Vision using XDA Premium App
what do you mean by that?
PatrickHuey said:
what do you mean by that?
Click to expand...
Click to collapse
Well it rarely happens. I remember when I got the same error and told somebody in XDA they told me that during the back up process clockwork didn't back it up correctly which leads you not being able to restore your back up. Had virtuous 2.2 back then, good thing was I had 2 back ups just in case so I was able to restore a later version of my back up.
Sent from my HTC Vision using XDA Premium App
Did you by any chance change the name of the folder of the backup? I once 'annotated' the default date-time format that Clockworkmod uses with something more meaningful to me, but found that it breaks the MD5 check.
I'm just asking on the off-chance because changing the folder name back to what it was when the backup was made will fix it, if that's the case.
Good luck.
Yeah I did, but I hadn't had any problems with renaming it with it before. I attempted to change it back to a default name and that didn't work. Is there anyway to try and recover my backup, or just my data?
Sent from my HTC Vision using XDA Premium App
I also had this problem before when switching between cyanogen and a Sense ROM. The way I fixed it was I downloaded, wiped and installed a fresh new cyanogen ROM. After it was installed I was able to restore my old backup from CWM.
ill have to give that a try. thankyou sir.
I updated to EI22, stock w/OTA update. I then rooted and things were working great. Then about 1 week ago, I did a CWM backup and when I restarted the phone just kept automatically rebooting approx. every 3 -4 minutes. I could not stop it no matter what I did. Then I restored the backup and it worked fine. A few days later, I turned the power off to put in a my extra battery, and when I turned it on, the same thing happened. I had to restore twice fir it to stop this time. Then this morning, I did a reboot to see what would happen, and again it happened. Mind you it was working flawless before I restarted it. I have tried everything from removing programs, turning off the wifi, leaving the battery out for a half hour, but nothing. Sometimes after it reboots, I leave it alone for 15 minutes and then when I hit the power button, it just restarts.
Any ideas before I put back froyo??
Sounds like a bad flash. I would Odin all the way to Stock EC05 then root then flash a Gingerbread ROM. Your error is either in the kernel or recovery to happen immediately after boot. It could even be a flaky partition table.
Sent from my SPH-D700 using XDA App
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
mszach said:
OK. Funny, I flashed backed to a stock EC05 and did the OTA update so as to possible avoid any problems like this.
Click to expand...
Click to collapse
I figured that but the problem may lie in the rooting which required you to flash a kernel or in your recovery module.
Sent from my SPH-D700 using XDA App
mszach said:
Any ideas before I put back froyo??
Click to expand...
Click to collapse
Your not alone on this issue. I am also considering going back to froyo
ADW was nice enough to bring up a crash report that I emailed myself. In the stack trace I see that android Package manager has died as a cause of the exception. I am not a java programmer so am at a loss here to what's happening.
See also this related post
So I flashed to the ACS ICS rom and so far no problems. What a great ROM!! Many thanks to Marcusant and ACS.
Sent from my SPH-D700 using XDA App
don't use the OTA.
just root ec05, flash CWM 5, flash modem update ec05 to EI22, flash a rom of your choosing. it's that simple. i don't see why people go the OTA route. it just causes problems with the recovery.
EDIT: also if you want Rom manager, check the kernel(or rom) for compatibility.
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
I'm lazy sometimes and like to use a GUI...
Sent from my SPH-D700 using XDA App
robmoney215 said:
Why use ROM MANAGER at all? All the same tasks can be done from Clockwork Mod directly?
Sent from my SAMSUNG-SGH-I777 using xda premium
Click to expand...
Click to collapse
It was not supported for the Epic before but with the new CWM5 it is. It is much faster to boot into recovery from ROM Manager rather than powering down and 3 fingering into it. Plus ROM Manager supports renaming your backups when you are doing them. Also ROM Manager will continuously update your CWM if new versions come out. There is also OTA updates available if the developer supports it on their ROM.
Anyone having trouble making nandroid backups using clockworkmod? I'm using the latest version of clockworkmod touch and stock 4.4. I run the backup, it appears to run fine, says it's finished, but when I reboot there is no backup files. This has happened multiple times, including getting burnt by modifying a system file and then finding out my backup is non-existent. I'm used to TWRP, but someone told me it doesn't work with 4.4 so I switched.
Sent from my Nexus 10 using xda app-developers app
gc84245 said:
Anyone having trouble making nandroid backups using clockworkmod? I'm using the latest version of clockworkmod touch and stock 4.4. I run the backup, it appears to run fine, says it's finished, but when I reboot there is no backup files. This has happened multiple times, including getting burnt by modifying a system file and then finding out my backup is non-existent. I'm used to TWRP, but someone told me it doesn't work with 4.4 so I switched.
Sent from my Nexus 10 using xda app-developers app
Click to expand...
Click to collapse
Maybe you are looking into the wrong directory.. mine is located at Device\Data\Media\Clockworkmod\Backup.
Hope that helps!
mfaisal98 said:
Maybe you are looking into the wrong directory.. mine is located at Device\Data\Media\Clockworkmod\Backup.
Hope that helps!
Click to expand...
Click to collapse
That was it, thanks!
I guess I'm used to TWRP where it is saved under /sdcard/TWRP, plus I was thrown off by the clockworkmod folder at /sdcard/clockworkmod
I just wasted a couple hours setting everything up because I couldn't find the backup