Last week, when I tried to restore a Nandroid backup in Ra_hero 1.6.2 recovery, the process failed. After checking the recovery log, I found that the system stopped the restore process because the data.img md5 checksum is mismatched.
I then cross-checked the md5 of that data.img with the one in the nandroid.md5 in my PC and found them to be different. I then created another nandroid backup and the md5 is also mismatched.
There's no error message during the backup process. Anyone knows what's the problem?
(I'm currently using VillainROM 5.5)
Have the same problem here with Wildfire.Guess it's the problem because I made a backup from SD to HD ?
StratOS_HTC said:
Have the same problem here with Wildfire.Guess it's the problem because I made a backup from SD to HD ?
Click to expand...
Click to collapse
Actually, I've no idea of the cause of this problem. But I remember after upgrading to another VillainROM version, the MD5 checksums are correct again and it's been no problem ever since.
Are you using a custom ROM too?
Related
Hi,
I recently decided to install the N1 partition table, it ended up going very smoothly apart from being able to restore the most recent nandroid backup, MD5 error (or words to that effect).
Not worying too much I just reinstalled CM6.1 from scratch, again all went smoothly.
I then did a nandroid backup and then rebooted then restored the nandroid backup, everything worked perfectly.
I then installed a cooked zip file from http://circle.glx.nl/.
That failed to boot after installing, no prob I thought, just recover from the nandroid backup.
I got another MD5 error from the one that I previously restored from.
So another reinstall, nandroid backup and recovery later it's all ok again.
Unfortunately I'm losing confidence in nandroid now.
Any thoughts ??
Colin
Md5 is a checksum, it makes sure the images your trying to restore are the same as when backed up! Maybe theres a problem with your recovery, flash it again from fastboot, only takes a second
Sent from my HTC Desire using Tapatalk
Aye I know what MD5 is, I just couldn't remember the exact words when the MD5 check failed.
The thing is though that I'd already tested the nandroid image by recovering it, all OK. Then made a change to the ROM tried to restore the same (previously working nandroid backup) which failed with the checksum error.
gol_n_dal said:
Aye I know what MD5 is, I just couldn't remember the exact words when the MD5 check failed.
The thing is though that I'd already tested the nandroid image by recovering it, all OK. Then made a change to the ROM tried to restore the same (previously working nandroid backup) which failed with the checksum error.
Click to expand...
Click to collapse
It can also happen of your Sdcard is failing and the files on it are getting corrupted. Since MD5 is a checksum, a change in even a few bytes could cause issues
I too have faced MD5 checksum issues.
1.copy the files to the sd card via the phone mounted as Disk drive mode
2.Safe remove the device from windows
3.Once you unplug, the device will shortly show "Preparing SD card" in the notification bar. Wait for a full minute
4.Switch off device to boot in recovery.
For me, if i dont wait a minute after unplugging the device, clockworkmod will report the files as corrupt. Maybe the device is updating the inode tables and switching the device off immediately after copying and unplugging causes it to corrupt filesystem tables.
So heres the situation. I made a backup of my phone using rom manager because I wanted to try out the new cyanogen. I got done playing with it and I went to revert back to my restore I had just created. During the restore I got an md5 mismatch error.
I used the instructions here to repair the restore
http://www.droidforums.net/forum/droid-hacks/40428-checking-md5-sum.html#post430944
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
The procedure worked in the sense that I was able to restore the image. The problem is after the restore I am stuck at the white "HTC Incredible" screen. I tried wiping caches and running the restore again but I am unable to get the phone to reboot.
I was able to restore to a much older restore that I had previously created but it lacks alot of updates and changes that I have made since then. Not to mention my Angry Birds saved game.
Looking at the restore files it looks like the folder for the restore contains a hand full IMG files. What i'm wondering is since it appears that the boot process is damaged I'm wondering if I could make a backup of the phone as it is now then take lets say the data.img file (or whatever file i need to recover installed apps and saved games) and overwrite the img files for the restore i just created. I could then use the same procedure I just performed to recreate the md5 hash and run the restore. My home is that will allow me to get my data back and still allow the phone to boot.
What do you guys think? Is it doable or am I going to be in a world of hurt if I start messing with this?
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
s197 said:
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
Click to expand...
Click to collapse
NO, I didn't. I used the default setting. I think it was 2010-12-29.01.34.10 or something like that.
setexascustoms said:
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Click to expand...
Click to collapse
Thanks man, This worked perfectly. Restoring the boot.img didn't fix the problem but restoring the system.img did. I have all my data back and my phone is fully functional again. Thanks again.
hi...............
when i want restore my backup i see error md5 mismatch WHY????
http://forum.xda-developers.com/showthread.php?t=714114
Might help.
Edit your thread title please to include a brief description of your problem.
It's a problem that happens to a few people and I believe he did describe it. When in recovery and selecting a backup to restore, it just says md5 mismatch. It's caused by the backup actually being corrupt or if you've gone in after the backup was taken and renamed the folder..usually if you put a space in the file name.
I have tried to restore some Nandroid Backups that I made via Clock Work mod. I get an error
Checking MD5 Sums...
MD5 Mismatch!
Why does it not work? I had copied it to my PC then back to my phones internal SDCARD. I did rename the Directory. Are these things not allowed?
I decided to see if I can bring back 1 I never touched. I made a backup then restored it and it worked so Clock work mod seems to be fine but perhaps its because I changed to folder path?
No clue perhaps someone can educate me on Nandroid backups do's and don'ts. Please note I have the 5X version of CWM.
dudejb said:
I have tried to restore some Nandroid Backups that I made via Clock Work mod. I get an error
Checking MD5 Sums...
MD5 Mismatch!
Why does it not work? I had copied it to my PC then back to my phones internal SDCARD. I did rename the Directory. Are these things not allowed?
I decided to see if I can bring back 1 I never touched. I made a backup then restored it and it worked so Clock work mod seems to be fine but perhaps its because I changed to folder path?
No clue perhaps someone can educate me on Nandroid backups do's and don'ts. Please note I have the 5X version of CWM.
Click to expand...
Click to collapse
Placed the files exactly as they were backed up and it worked. No renaming of directories and no placing in another folder. Apparently this is all taken into account with Nandroid backup.
I'm using Nandroid and ROM Manager to perform backups, but when I boot into CWM, and choose any backup created by these apps, I get the "MD5 Mismatch error". I've seen plenty of threads how to fix one back-up file, but why does this keep happening? Is there a permanent fix?
Thanks