[How To] Fix md5 mismatch nandroid restore

Ryanscool

Senior Member
Aug 30, 2011
1,151
194
0
Denver
Another problem,

Hello when I was doing this command you said I had it all the way until rm nandroid.md5. It says rm failed and some other jibberish. What do I do now? Oh shoot nevermind the stuff inside was in a sub folder 11. I have no idea how that got in there lol.
 
Last edited:

ThinksAmoral

Senior Member
Aug 22, 2011
103
24
0
I had a problem with the whole "md5 mismatch" before.

I tried this method, and it created a nandroid.md5 file with 0 bytes of memory. My other backups contained a nandroid.md5 with 222 bytes. That can't be right, can it?
 
  • Like
Reactions: tiny4579

Holmes108

Senior Member
Sep 29, 2010
674
76
48
Toronto
Just want to add an extra issue I had to overcome, in case it helps someone.... Not sure if it was mentioned, but:

I had the MD5 mismatch... the steps here fixed it, I then got errors for each step of the restore, saying (for example) "error, system.img not found."

I knew I had image files in the directory. I checked and 2 or 3 files were names something along the lines of system.yaffs2.img. I deleted the "yaffs2" section of each file that had it, I then had to redo the MD5 fix, and the restore worked beautifully.
 
  • Like
Reactions: ithrewitontheground

emoandy

Senior Member
Feb 14, 2006
70
1
0
It seems like I've tried everything here, plugged in the phone with usb debugging enabled, opened adb shell from the platform-tools folder, entered the given commands with my correct backup name (no space, created by nandroid) and everytime I get on the last step:

*.img no such file or directory...
(and tried just *img)
 

ksantoshh

Senior Member
Nov 27, 2011
200
62
0
Singapore
It seems like I've tried everything here, plugged in the phone with usb debugging enabled, opened adb shell from the platform-tools folder, entered the given commands with my correct backup name (no space, created by nandroid) and everytime I get on the last step:

*.img no such file or directory...
(and tried just *img)
You may not have the img file in the backup folder.sometimes the extention are ext4.Best workaround is create a blank nandroid.md5 file and place it in backfolder, it works :)
 
  • Like
Reactions: mcw3118

billabong272

Member
Dec 21, 2011
27
3
0
Davao City
Dude thanks for posting this thread! It really is a lifesaver.
Before I didn't have any problems doing backups on my ROM. Then after flashing a new Kernel, ROM and updating SuperUser and ROM Manager, CWM cannot generate MD5 Checksum file. At the end of backing up my ROM. CWM states generating MD5 sum error. etc..
At recovery log, it states:
Generating md5 sum...
sh: nandroid-md5.sh: Permission denied
Error while generating md5 sum!
result was NULL, message is: assert failed: backup_rom

Then I found this thread. First I copied a nandroid.md5 from my previous back up. Then I applied the code using Terminal Emulator. Then I reboot to recovery, then I tried to recover cache, voila! It works!:D