View Single Post
Old March 29th, 2011, 02:49 PM   #35 (permalink)
Senior Member
Join Date: Nov 2009
Posts: 1,644
Carrier: Not Provided

Thanks: 50
Thanked 758 Times in 377 Posts

Originally Posted by crz6662 View Post
Ah ha. A bulb just lite up. Even a single empty space will change my checksum. I think it finally clicked guys.

Won't be renaming. Period.
I looked at the 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).

Please don't send me PMs - post your questions so others may benefit from any answers given.
erisuser1 is offline  
Reply With Quote
The Following User Says Thank You to erisuser1 For This Useful Post:
crz6662 (March 29th, 2011)