yashsingh1/xdaforums huggingface dataset:
[Droid Incredible General] DonJuan692006:
The only thing I have to add is that you don't need Java if your only going to be using ADB, but that's honestly just me being particular.

Secondly, since I didn't see this get brought up in the past posts, the final folder from the ADB commands isn't necessarily going to be labeled the same as the OP. The actual backup folder name is based on the current date/time when the backup was made, so I would suggest doing the following:

adb shell
cd /sdcard/clockworkmod/backup
ls -l (which will list all your backup's)
cd *backup folder you're trying to use*
rm nandroid.md5
md5sum *.img > nandroid.md5
[Droid Incredible General] juice willis:
Success!

Just wanted to say it worked, and thanks a lot!

Seems that none of the backups I made have the md5, not sure why, freshly rooted and cwm recovery flashed...hmmm...
[Droid Incredible General] BigMrB:
Dude thanks a bunch!!! You saved me from wasting a few hours of my life
[Droid Incredible General] ezeuba:
I get an md5sum not found error

I have this problem with restoring my backup. I tried the fix as was detailed, even had to download md5sum.exe because I am working on a Windows 7 machine, but I always get "md5sum: not found" error. Can anyone please guide me on what I can do to get this working. I copied md5sum.exe to C:\Windows\System32 and also to the sdk\platform-tools folder, still getting the error.

Thanks all.

EDIT: I found that I had to go into recovery first to run the fix. Only then did the md5sum command work and created a fresh new nandroid.md5, and got my backup restored. Thanks to all who made this possible. My sincerest thanks.
[Droid Incredible General] dwreck420:
hey im getting the same error. what do you mean you went into recovery first to run the fix first?
[Droid Incredible General] dwreck420:
lol like you, just kidding!

put md5.exe in sys32, boot to clockwork mod, connected usb, open cmd shell in win7, execute commands: md5 success, backup restored.
[Droid Incredible General] nolimitzz:
nice post, helped me alot, thanks!
[Droid Incredible General] elvis56:
Just ran into this problem as well. I think it has something to do with the Hboot version.

Anyway, people using windows based tools probably have to manually edit the nandroid.md5 file. The checksum HAS TO BE in lowercase character(as someone else pointed out before as well) , there HAVE to be 2 spaces after the checksum and you do not need a checksum of .android_secure.img.

And, maybe most important of all, if the filesize of nandroid.md5 is anything other than 267 bytes the file will not work. As described in the documents from the thread below it's best to start from an existing nandroid.md5 file and copy/paste the correct checksums.

The files linked in this thread will probably help windows based users. http://www.droidforums.net/forum/hacking-help/33355-help-clockwork-md5-mismatch-recovery-2.html
[Droid Incredible General] potcryan:
Just in case anyone runs into the same problem I did when trying to restore- do NOT name your backup with a "/" in it. I named mine with the date ie 5/2 and it created a folder named 2 which is where everything saved. Finally figured out that's why I couldn't restore, heh.
[Droid Incredible General] D!T:
I am probably wrong here, but there is a disturbing pattern in that the last backup made by ClockworkMod (3.0.0.5) has lately failed every single time with the md5sum error.

Stepping through the instructions, I saw that nandroid.md5 didn't even exist in the directory (and therefore could not be deleted).

Furthermore, I ran a second backup before making any changes and miraculously the former (broken) backup suddenly worked again.
[Droid Incredible General] major_works:
I wanted to restore a backup today. It was the first time I'd tried it. I immediately ran into this "MD5 mismatch" thing. I had no idea that I shouldn't have put spaces in my backup file names. I edited out the spaces, tried it again, and it worked for me.
[Droid Incredible General] NJMoreno22:
This was my problem too. Renamed with no spaces and restore completed successfully. Thanks man :D
[Droid Incredible General] Araf:
big thank you!!

EDIT:

After follow all the procedure, here's the result in my clockworkmod recovery (v3.0.2.8):

1. Checking MD5 sums is OK

2. Restoring system is OK

3. Restoring data is not OK, there is message: ".android_secure.img not found. Skipping restore /sdcard/.android secure.

4. Restoring cache is OK

5. Backup complete

Then after reboot, all my data is not restore as expected. I am afraid my data is gone :-(

Can someone help me?
[Droid Incredible General] ACD168:
clockworkmod recovery (v3.0.2.8): is this for the incredible?
[Droid Incredible General] morgan39:
Thankfully

I had renamed the backup to know that rom but there were spaces left; I returned to rename without spaces and following adb commands, voilà: I was able to restore it without problems.

I've saved so much time with headache ¡¡¡¡¡¡¡¡¡¡

Thanks for sharing .............
[Droid Incredible General] GirLuvsDroid:
Thank you DonJuan and ihtfp69 for this fix. I found this thread by searching after I got an MD5 mismatch on my Nook Color. I ran DonJuan's script from Terminal Emulator on the Nook Color and it worked like a charm. My backup is restored and I'm up and running again. You guys are lifesavers!!!!!
[Droid Incredible General] xTFGx:
Thanks so much!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
[Droid Incredible General] Dacoco:
Simple but great! Thank you very much :-)
[Droid Incredible General] woodpeckerlo:
Rename your backup folder how ever u like

just don`t put any spaces in name

!!!!!!!!!!!!!!!! It work`s like a charm!!!!!!!!!!!!!!!
[Droid Incredible General] Neo:
+1 that. I never had a problem with the spaces until after flashing this one particular rom and when it had issues, could not restore from any of my backups from 8 different roms. Turns out I had spaces in the folders that I kept each individual rom in. Take the spaces out and you should be good to go!
[Droid Incredible General] neil_swann80:
Ignore... wrong thread.
[Droid Incredible General] pacut:
well well...I renamed my ROM image and put some spaces, and when I need it I got MD5 check error. It is clear: non spaces into string name of the backup file.

Question is: has it the be identical name to original backup from CWM, or could it be anything I want just with no spaces ?

Thanks
[Droid Incredible General] omer1112:
I had a md5 sumcheck error as well. I tried the adb shell commands. It didnt do anything. i explored my backup folder and two of my backups that aren't working actually only have two files in the folder. boot.img and recovery.img.

Any idea why my nandroid backups got screwed like this? What can I do to prevent this? Never ran into this problem before and i've done atleast 50+ nandroids throughout different phones.
[Droid Incredible General] im.nick.hello:
ok so i've been having some problems with not booting past the splash and so on... so i made a backup then ran a ruu

when i tried to restore my backup after flashing the ruu and re rooting i got a md5 mismatch, i think my backup is probubly corrupt.

what will happen if i restore it anyway with this method?
[Droid Incredible General] Ryanscool:
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.
[Droid Incredible General] dirtsky:
I'd hit the thank you button but there is no thank you button but yes this did fix my md5 problems. Thank You.
[Droid Incredible General] ThinksAmoral:
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?
[Droid Incredible General] zoomy942:
I always make 2 backups just in case.
[Droid Incredible General] menghour2010:
Thank you very much.... for your post... :D
[Droid Incredible General] Jpac175:
Thanks so much! this just worked perfectly :)
[Droid Incredible General] SpaceRanger69:
THANK YOU!!! Thought I hosed my G2X Stock Backup when I renamed the folder putting spaces in, and wasn't able to restore it. *wipes brow*
[Droid Incredible General] Holmes108:
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.
[Droid Incredible General] Krisbo:
I would click thanks but the thanks button appears to be gone o_O
[Droid Incredible General] bharattp:
Big thanx......
[Droid Incredible General] yudaniel:
Very Thankfull, after few days of googleing. This was the only halpfull information.

Thanks
[Droid Incredible General] WarEduar:
Thx a lot bro, this one was the solution after fuc&%&# my phone whit funbox.
[Droid Incredible General] michaelko999:
thanks pal !!!! re-rename recovery without space work !!!
[Droid Incredible General] emoandy:
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)
[Droid Incredible General] ksantoshh:
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 :)
[Droid Incredible General] evanbowers:
whew

This thread was a lifesaver, thanks a ton.
[Droid Incredible General] billabong272:
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
[Droid Incredible General] askpcguy:
My thanks as well. When I am not sleepy, have a beer or lunch on me.
[Droid Incredible General] PMGRANDS:
Is there anyway to Fix the MD5 issue Without the use of ADB?
[Droid Incredible General] askpcguy:
Only if you can run a terminal emulator on the phone.
[Droid Incredible General] vladimirhtg:
excellent instructions
[Droid Incredible General] Roshi69:
This is awesome. thanks!
[Droid Incredible General] :
(:

all i did was change my folder that help all my backed up files that were in Folder named Stockrom to 2010-06-29.20.22.53 just that setup like when u first do a backup.. im sure u could change the numbers a bit but it passed md5 check right away and worked!!! hope this helps. If this helps please thanks me!! im glad to help anyone

---------- Post added at 09:20 PM ---------- Previous post was at 09:16 PM ----------

And no you dont have to fix the md5 through ADB... u can do it just by hooking ur phone up..!!
[Droid Incredible General] Mix3d:
Thanks a TON~

Turns out I also had the issue with spaces... (boot manager lite broke my rom by backing up a corrupt boot.img, and then I ran into this problem)

I made a backup of the nandroid.md5, rather than just deleting it, so I could compare and see which file was not matching, and oddly enough, the md5sums were the same, so I dove further into the thread, and lo and behold, I WAS USING SPACES IN THE FOLDER NAME!

hooray!

CWM should fix that, imo.
[Droid Incredible General] simple man:
Thanks for such a useful guide, it works great! :)
[Droid Incredible General] xpanmanx:
In my situation, I'd renamed the backup folder using CWR to something like this: "Calkulin_2.9.2._2012-03-11" All I had to do was rename the folder to "2012-03-11".
[Droid Incredible General] BohArie:
where to put the code on terminal emulator on our phone or using android sdk on windows 7 cmd? im using winndows 7 and already put android sdk...
[Droid Incredible General] simple man:
I use Terminal Emulator.
[Droid Incredible General] BohArie:
how to do on terminal emulator?
[Droid Incredible General] simple man:
I just type su ,(to get superuser rights)then the return key, then copy and paste the commands in the OP , leaving out the # in front of each line. But you need to change the backup name to your exact backup name, date, etc..,then return key. Then use a file explorer to make sure you have a md5 checksum file in the backup folder.
[Droid Incredible General] paulo13pdm:
I renamed the folder of the backup and it worked.
[Droid Incredible General] KodeRiter722:
Just to elaborate on this, if folks are also seeing this same error (md5sum: not found) when they get to the last step in the guide, just repeat the process, but this time on the last step, use the command:

# busybox md5sum *img > nandroid.md5

this worked for me
[Droid Incredible General] whitetigerdk:
Just to let you know.. didn't work for me.. however.. when doing an advanced restore and making checksum file image by image it worked.. it took some more time - but it worked.. wife got her phone back.. my life is saved :) THANX A LOT!!!
[Droid Incredible General] crz6662:
Wondering if moving from an internal to an external SD card would affect the backup? Rooted/Flashed TMO SGS2. Moved from internal 16GB to external 32GB card and couldn't flash the backup. MD5 mismatch. As I recall I attempted to switch back to internal and it still wouldn't work. Never changed the name, and was able to locate the backup via ClockWorkMod on the external card.
[Droid Incredible General] KodeRiter722:
I have had issues moving backups between internal and external storage. Once you move it back to your internal sd, try this process again, and it should work.
[Droid Incredible General] hassi4042:
you save my F***ing life man...!
[Droid Incredible General] prudviraj:
OP instructions worked like a charm for my galaxy Note

OP instructions worked like a charm for my galaxy Note... keep up the good work guys.. XDA is awesome.. :)
[Droid Incredible General] EliTSamsunG:
INFO: Need Boot.img on the folder or THIS DONT WORK.
[Droid Incredible General] Cacha21:
I think i love you, ihtfp69 :) thank you so much!
[Droid Incredible General] LegionCmndr:
started adb shell and navigated to the folder where the backup was stored

md5sum *img > nandroid.md5

created a successfull md5, and no less then 3 days after i tried this she somehow got the phone to go into a boot loop. i booted it into recovery and restored the phone and all was well

directions worked for my daughters samsung vibrant

MIUI with CWM 5.0.?.?
[Droid Incredible General] Ryan_28:
Hahaha you saved my ass on that one, such a simple solution, easily over looked. Thanks!
[Droid Incredible General] wazer22:
Hi

I was wandering if you can help me. i tried running the code but it tells me no such file or directory at the end. i am a noob in it some help will be much appreciated
[Droid Incredible General] JZ SmartMort:
THANK YOU @kentoe!!! I'm glad your post was second otherwise this gold would have been missed. The OP should be updated with some of these notions.

Thanks to the OP as well as that was another key component although I needed the data file so had to do this: md5sum *img *tar > nandroid.md5

All the best!
[Droid Incredible General] vvulture:
You're a legend my friend !! Worked for me too ! :good:
[Droid Incredible General] sxi200:
Lifesaver. Backup on my tab got corrupted when copying to pc then back after a format. The system file was the only one corrupted. After doing this in terminal, tab wouldn't boot so I then restored system from an old backup and all is good again. All data is back again. Thank you so much.
[Droid Incredible General] Ulukita:
I did the same thing!

I had renamed my folders o I just did renamed them by years 1982-05-13RomNameetc worked perfectly!
[Droid Incredible General] sekhar13515:
The explaning is good, but noobs can't get how to ..

so, plz explain with detailed screenshots or video...

---------- Post added at 04:05 PM ---------- Previous post was at 03:59 PM ----------

Applied commands as stated..

Nothing happened
[Droid Incredible General] shishircoolin:
A million thanks:D to you! Cheers:good:
[Droid Incredible General] BigMrB:
If noobs can't figure out those commands than that noob needs to go off and do so more reading... the answers aren't always spoon fed.. even though on this occasion it has been
[Droid Incredible General] sekhar13515:
At first you are also a noob,

Noobs can try and follow, but they have fear that they brick the phone
[Droid Incredible General] bhake:
Worked like a champ, thanks! Hat tip to google for putting this as the first search result when trying to find out how to fix this!
[Droid Incredible General] shishircoolin:
For those having a 'No such file or directory found' error you need to use emmc in place of sd card:good:! i.e.

cd /emmc/clockworkmod/backup/2010-06-29.20.22.53
[Droid Incredible General] ImjuzCY:
I've checked the files inside the nandroid folder with the md5. It shows that it's all matched. But clockworkmod says md5 mismatch

Edit: My case solved. Need full wipe before restoring, if not it will show md5 mismatch right after you confirm to restore.
[Droid Incredible General] spexwood:
I was Googling for a solution to the CWM MD5 mismatch issue for my Galaxy S2 and came across this thread. I followed all the instructions and managed to get my backup to install (well, it's actually installing as I type).

I dont think my BU is corrupted though. I copied all the backups from my phone to my PC, but I renamed the backup folders and I think that messed CWM up. I would rename them back to default, except that I do not remember the exact names of the folders!

RESULTS:

Yup, the backup worked!

It must have been the folder renaming!

I guess, the lesson here is to not rename CWM's backup folders!
[Droid Incredible General] bornlivedie:
Saved me a couple of hours, lol.

Thanks a lot.
[Droid Incredible General] diamond_4g64:
Can i do this by terminal?
[Droid Incredible General] A Lex and Er:
Of course we all thank IHTFP for this great info.

In these instances I leave in place the CWM name and put my file name at the end. Suppose I could put mine at the beginning? But whatever works for you.
[Droid Incredible General] tietganFTW:
Saved me the hassle to reinstall all my apps :)

:good:THANKS YOU DESERVE A THUMBS UP
[Droid Incredible General] olokos:
Hopefully working. I thought it might not work as i didn't even have nandroid.md5 in my folder for some reason (i haven't changed anything). I got no file or directory (ofc) but i created md5 file... Crawled through web seeking for another way and i didnt really belived that it'd work in the newer CWM but... Works great ;) Thanks a lot dude :)
[Droid Incredible General] sxi200:
Yes. That's what I used.
[Droid Incredible General] shishircoolin:
Here's a trick , While in recovery select on "install a zip from sdcard/internal sdcard" and then browse to the folder where your backup is stored once you get there check the backup path on top left,. It should be the path you need to type in the command prompt window. If it still gives an error then try the same thing without root command(su), that should definitely work.:good:
[Droid Incredible General] my3fox:
I just remove the extra letters which I add to the name of the original backup file. I tried again and ..... YES.... it worked again and restore successfully from the back-up file.

try to return the file to its original name.
[Droid Incredible General] maucenaiks:
How can I found the firmware version, in my backup folder?, I haw Galaxy s3 i9300, and 6 files in backup folder. Nothing from this post worked for me. Please help
[Droid Incredible General] maranello69:
why do you need the firmware version?
[Droid Incredible General] rahulsuneja:
The best solution for such a problem, if I ever happen to face one is:

1. Create an empty text document on your desktop.

2. Rename it to "nandroid.md5"

3. Place this renamed empty text document (nandroid.md5) in your clockworkmod backup folder.

4. Try restoring again. It should work.

PS:

What basically has been done here is that the CWM has been made to skip MD5 checking by placing an empty md5 in the backup folder. This is the only solution I adopt whenever a md5 error is seen. CWM keeps omitting the nandroid.md5 file while creating backups!

PPS:

A humble thanks is very much appreciated if I have been of any help to anyone! :D
[Droid Incredible General] sekhar13515:
can't we create that empty text document in phone?
[Droid Incredible General] benny3:
Great find ! Worked perfect Thank You
[Droid Incredible General] :
Worked perfect, thank you :good:
[Droid Incredible General] DLM2583:
i`ve tried this method but i cant find the md5 file in my es explorer for some reason.......please can someone verify this method if the have root explorer i dont want to purchase it unless need thanks https://www.youtube.com/watch?v=yaeqRaRV7Xk
[Droid Incredible General] GhostCanon:
Great Thanks Man. ;) :good:
[Droid Incredible General] :
Doesn't work

I followed all the steps exactly without error, but then when I attempt to restore, it still says MD5 mismatch.

If it's any help, I'm on 4.2 and the CWM directory defaults to data/media/
[Droid Incredible General] Alexkidd85:
+1 same here!
[Droid Incredible General] SnarfSnarf:
Thanks!

Worked for me following your steps, (1st post) and also had to rename my backup file to something shorter.
[Droid Incredible General] rsjet:
Since I upgraded to 4.2 (and my sdcard got moved to /0) but wanted to go back to my old nandroid, I had to use "/data/media/" like this:

cd data/media/clockworkmod/backup/2013-03-05.19.25.09

Thank you for this fix.
[Droid Incredible General] Blue3125:
THANKS , WORKED LIKE CHARM

BTW, i still don't get why dose recovery says md5 mismatch even if do nothing worng

i created a backup and after an hour or so, decided to restore it and it said md5 mismatch , now i have the solution but still just curious to know what is really causing it,

regards
[Droid Incredible General] Blue3125:
Any alive Human being left to answer this Simple question ?

Or everybody is dumb as hell ?

Via HTC Sense
[Droid Incredible General] BleedingIris:
Yup.. everybody is dumb as hell. You got that right!

LâTêS†↭ⓛⓘⓝⓚⓢ™CM10 HTC A310E.

If I haven't given you link, it's above. Just click it
[Droid Incredible General] Pons:
Yep, not a clue what I'm doing. Been trying to get this to work on my landline all day, and can't even get it to boot into recovery.
[Droid Incredible General] areeb47:
Life Saving Post, and also time saving :laugh:
[Droid Incredible General] Beastben13:
error

It says that its a read-only file system so it can't create a nandroid.md5 file.
[Droid Incredible General] CyberdyneSystems:
so in the end to fix this md5 mismatch you have several ways

1. using the adb shell

2.using the app, 4EXT Recovery Control v2.4.4 ROOTED DEVICES ONLY

( it will attempt to scan and see what phone you have, me (SG2-boost) i chose, HTC Touch)

3. the simple one, delete the nandroid.md5 file

reboot into recovery then restore, creates a new md5 and restores...successfully ( ive done this several times)

about my device:

Samsung Galaxy s2 (Boost mobile)

REcovery: AGAT (uses CWM parts) "agat_recovery tREC_v0.3.4"

kernel: SXTP_Agat_GC01-v0.5.0

success/fails: 8/0
[Droid Incredible General] Abhy-Boy:
Error : Permision denied

Check file in your /system/bin/, in my device I can't find md5sum, but I find md5. So last command should be

md5 *img > nandroid.md5

not md5sum *img > nandroid.md5