i use xrecovery 0.3-releasde to backup my current system and data,and when i'm going to restore,it says the MD5 mismatch
who can tell me why?
You may have changed something with your build after you backed up your current system. Try removing anything you recently changed before you backed up your system.
thx for answer~
i just got why it happened
the xre itself calculated the md5 incorrectly
i calculate the md5 of the three .img myself and change the md5 in the nandriod.md5
then i can use the restore~
Related
When trying to restore backup from CWM-recovery I get MD5 checksum error in 2 of 3 restores. The backups doesn't report any errors but restores stops because of MD5 error.
Every time I do a backup I have to check by restoring to verify that the backup is ok. Otherwise I can't trust the backup to be restorable.
This happens with backups/restores from either sdcard or ext_sd, no difference.
Anyone else experiencing this, and are there any solutions to solve it, or at least check the state of the backup without needing to restore it to check if it's restorable?
nilste said:
When trying to restore backup from CWM-recovery I get MD5 checksum error in 2 of 3 restores. The backups doesn't report any errors but restores stops because of MD5 error.
Every time I do a backup I have to check by restoring to verify that the backup is ok. Otherwise I can't trust the backup to be restorable.
This happens with backups/restores from either sdcard or ext_sd, no difference.
Anyone else experiencing this, and are there any solutions to solve it, or at least check the state of the backup without needing to restore it to check if it's restorable?
Click to expand...
Click to collapse
In adb shell or in a terminal emulator, navigate to your backup folder
Code:
cd /sdcard/clockworkmod/backup/name-of-your-backup/
md5sum *img > nandroid.md5
This code resolves md5 checksum errors. Now try to restore.
In case this fails,use advanced restore to restore each .img one by one
so i did a nandroid then renamed the file (didn't touch contents) and apparently that broke the md5 check, now it won't allow me to restore and i don't recall the original file name to change back to. Any way to resolve?.
Delete intervals in the name of the backup.
tenkkata said:
Delete intervals in the name of the backup.
Click to expand...
Click to collapse
I did, didn't work. I just deleted and recreated the md5 file in ADB, worked fine. Thanks!
i have renamed my CWM backup without using ROM MANAGER and when i tried to restore it says
md5 mismatch
i dont remember the actual name of backup. Is there anyway i can rename my backup to its actual name?
Can't restore in cwm , it say 'MD5 mismatch', before I have install the acid 6.0, but finished the install , the device just reboot again and again , just can see the desktop, and 3sec will reboot, I try to restore , but say mismatch MD5, what can I do now, in case I can restore to a long time backup, how can addon the md5 to the my last backup file?
Thanks you so much
Sent from my Sony Tablet S
Did you change the folder of the restored files or modify anything in the restore folder?? Then only MD5 miss match occur.
Sent from my LT22i using Tapatalk 2
Once happened to me as well...rebooted my phone and tried restoring again..and it worked...
Hi, thanks in advance for (hopefully) helping me!
I have a halfly bricked phone, and I can still get into recovery mode. I have a ClockWork Mod backup, made when the phone still worked.
CWM Recovery keeps having errors while restoring 'data'. So I want to make an MD5 file to flash the backup (only the data files, which are three files, if that's possible) using Odin.
Is this possible? And if yes, how?
I have a Samsung Galaxy Young GT-S6310N
I tried flashing the stock firmware (using Odin), but the trouble seems to be in the data files, since there weren't any in the stock firmware md5 file.
Thanks!
Bring the backups to pc.
Search google for md5 calculator.
Calculate the md5 value for the data files and replace the generated value in md5 file.
But a strict word of caution. Since there has been md5 mismatch, chances are that the data backup has got corrupt.
Using the above method will save you from restoration errors but you may have a corrupt phone in the end.
Extent of corruption may vary.