Originally Posted by erisuser1
I looked at the nandroid-mobile.sh script - it would fault out BEFORE any md5sum checks were performed (and give you a different error message) if the "nandroid.md5" file could not be found (for instance, if the backup folder name had some spaces in it).
I rename nandroid backups all the time - I just avoid the use of anything but letters, digits, dashes, underscores, and the dot (".") character.
The "nandroid.md5" file only contains the names "boot.img", "system.img", "data.img", et cetera - the only way that you would get a "MD5 mismatch" error if you changed the names of THOSE files (not the folder that contained them).
It should be easy enough for you to figure out which of those image files is giving you fits - use AFV to examine each of them, and then compare the MD5 checksums one by one to the values reported in the "nandroid.md5" file (it is a simple text file).
I still think that an errant space in the Nandroid backup directory name will manifest itself as the "MD5 mismatch" condition, but only from having read reports on AF and over at XDA that this ended-up being the case. I thought I had actually tested this myself late last summer, but I don't have that feeling of having first-hand experienced / tested it (possibly since its been so long).
I've looked at the script before trying to make sense of how this could be and I do certainly hesitate (with very good reason) in disagreeing with you
(but I've eaten crow before...
I will make a point to re-test this when I get home in a little while (just to make sure
Also, the AFV's "Verify Nandroid Backup" function invoked via long-pressing the nandroid.md5 file will check each file and report which one does not match, so you don't have to manually do this for each file listed.
edit: time for me to eat a little crow: I actually did test this way back in September
MD5 Sum Mismatch
and I got an "Error : run 'nandroid-mobile.sh restore' via adb!' error instead. Perhaps the version of ClockworkMod's nandroid-mobile.sh script is different than that of the Eris and will yield this result? Dunno. As you can see, the above thread is from the Droid X forums and involved ClockworkMod and not Amon_RA recovery.
I'll still re-test this tonight