checking MD5 sum

[hookerdj]

Ok so i made a backup last night. A little bit ago i went to restore it and my phone went through the usual. I saw it stopped at error md5 sum incorrect or doesnt match...Anyone have a clue what this means? thank you

[bomber889]

It means that you can't restore it lol.

[hookerdj]

uh duhhhhhhhhhhhhhh lol jk

[bomber889]

Something went wrong when generating the md5 sum when making a backup so you can not restore it. It happened to me during the earlier days of clockwork mod but hasn't happened in a while for me.

[cupfulloflol]

Ok so i made a backup last night. A little bit ago i went to restore it and my phone went through the usual. I saw it stopped at error md5 sum incorrect or doesnt match...Anyone have a clue what this means? thank you

You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/

See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.

Next step to open adb shell or terminal emulator and type:

su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery

Give it a bit of time, before you reboot into recovery, if I remember it takes it a little while to perform it. Maybe it will sort your problem though.

[dlwhtrose]

That happened to me last week when I did a manual backup through ROM Manager. My update aborted so I tried to restore back to my backup and got the MD5 mismatch warning. So I restored to an earlier backup then deleted that manual backup. I also updated ROM Manager and have not had that warning again.

RoLaDroid was helping me at the time and we could not figure out what caused it. He said that this had been an issue before and thought it was fixed.

[cupfulloflol]

That happened to me last week when I did a manual backup through ROM Manager. My update aborted so I tried to restore back to my backup and got the MD5 mismatch warning. So I restored to an earlier backup then deleted that manual backup. I also updated ROM Manager and have not had that warning again.

RoLaDroid was helping me at the time and we could not figure out what caused it. He said that this had been an issue before and thought it was fixed.

Yeah I had this issue multiple times back in the day, which is how I figured out how to do that. Kind of a pain in the butt to do, but it isn't that hard. My instructions only work if the backup was truly complete, just missing the md5sum, or have an error with it. I haven't seen it recently with clockwork recovery, but I guess it could still happen for whatever reason.

[bzdon]

You can actually manually do it, and maybe get that backup fixed. Go to the backup folder /sdcard/clockworkmod/backup/*rom name (date and time usually)/

See if there is a nandroid.md5 file in there. If so, delete it, you can back it up if you want but it is busted so no point.

Next step to open adb shell or terminal emulator and type:
Code:
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery

trying to solve my problem on this page http://www.droidforums.net/forum/dro...oot-image.html. i put in the commands in the emulator and it responded by saying "cannot create nandroid.md5: read-only file system"

what do you think about that?

thanks for any help you have to offer

[debdado]

I am being plagued by the MD5 mismatch from clockwork mod. I was able to get one backup to work, yippee. So I now have a functioning Droid again. Suggestions on how to clear those other backups and start all over again from "bugless breast" that I am currently using. Thanks in advance.

[SlyHusky]

Basically I renamed three of the backups, and none of them worked. I added spaces in the new rename. I finally used my initial backup (not renamed), mounted the USB and changed back the names but instead of spaces I added "-" marks. I't booting up for me fine now.

Good luck everyone...