Database Info

CWM Recovery - MD5 mismatch

Hey there,
since a few time I can't restore my recently made backups..
Everytimes I want to restore the CWM Recovery says
"Checking MD5 sums
MD5 mismatch" ..
I've already searched the forum and couldn't find a thread in here..
Also the solutions I found on google didn't help me..
Any tips?
Thanks in advance..
EDIT: Recoverysystem is 5.0.2.0

I've had this happen once when I went in and changed name of my backup from cwm's default date and time naming to something else. Other than that not sure why you'd be getting mismatch error except for a maybe a bad sdcard.
You could try reflashing the recovery to rule out a bad flash of the recovery
Sent from my LG-VM670 using XDA App

Well, I didn't change the name..
Reflashed the recovery, still got the Problem.. :/
Sent from my LG-P500 using Tapatalk

Could be a bug in the recovery. I'd try flashing another recovery and see if that helps. Lots of different recoveries out there so just make sure the one you try supports your phone.
Sent from my LG-VM670 using XDA App

Of course it supports my phone. I've installed it from ClockWorkMod and chose LGE Optimus One. And it worked a few time before without problems.. :/
Sent from my LG-P500 using Tapatalk

Found this you might try to rebuild your md5smd5s
http://forum.xda-developers.com/showthread.php?t=714114

Hi,
I also got the same problem some time ago. But for me this is because i deleted the ext partition on my phone after the backup has been taken. So i think any hardware changes may result this.

So this might be because I've changed SD-card for flashing another ROM in between?
@kwkbnk : Thanks, but I've already tried this before...

kwkbnk said:
Found this you might try to rebuild your md5smd5s
Click to expand...
Click to collapse
I had this problem on one of my phones. I had deleted one of the files. (an extra sd-ext backup file that I did not need). The first thing that recovery does is check the MD5 sum of all the files. If it can't find one, it just says MD5 does not match and stops. It tries to check all files even if you tell recovery you only want one restored. I fixed it by modifying the nandroid.MD5 file. It is a text file with one line for each file, listing each file's name and its MD5 sum. I just edited the file and removed the line for the missing file and all was well, I was able to restore all the other files with no errors. I also noted that I could remove all the entries so it was an empty file and recovery restored all files without checking MD5s at all. That's not a good idea in case there is a file error, but there may be times when it's necessary.

Where do I find the nandroid.MD5?
Couldn't find it anywhere..

unicycler said:
Where do I find the nandroid.MD5?
Couldn't find it anywhere..
Click to expand...
Click to collapse
Mine was in the same folder that had the img files. Clockworkmod/backup on your SD card. There is a folder inside that for each backup you have made.
EDIT: I just looked at that referenced post above and that script first removes the nandroid.md5 file and then rebuilds a new one. If you got an error and the script did not finish, then there would be no nandroid.md5 file. If you feel brave, you can create an empty nandroid.md5 text file and I believe recovery will skip the md5 check. At least it did for me. That's no worse than building a new one from the files you have with the script. If there was a bad file, recovery would try to install the file anyway since the new md5 sums match.

For me it happen when my memory card storage is low I did a backup.
Sent from my LG-P500 using Tapatalk

I built an empty nandroid.md5 with editor, then it worked again, thanks!!
Sent from my LG-P500 using Tapatalk

Same prob here help?
Sent from my LG Optimus One P500 using XDA App

WhatTheFlash said:
Same prob here help?
Sent from my LG Optimus One P500 using XDA App
Click to expand...
Click to collapse
Just go back and read my last few posts here. It tells you everything you need to know.

WhatTheFlash said:
Same prob here help?
Sent from my LG Optimus One P500 using XDA App
Click to expand...
Click to collapse
You can find the solution a view posts before, as already said.
I've uploaded an empty nandroid.md5 which causes the md5 sum is not checked.
Just copy it into your backup on SD (for example /clockworkmod/backups/2011-12-01.13.55.09).
You can find the MD5 here (xda-attechments don't support .md5-files).
Remember it could crash if your error is not caused by an missing nandroid.md5 .

OMG, helps alot
my eternal thanks

Thx unicycler! Saved me a lot of hours of frustration -I was just about ready to reinstall minicm7 on my X8 when I saw this thread! Your uploaded file fixed it all.
Thank you!!!

Leapinlar, please, can you reupload the MD5? The download link is broken

I will do this evening. Just forgot to do..
Sent from my LG-P500 using Tapatalk

[Q] Generic Imei number

Hi,
for some reason i lost my Imei number. Im not sure when or how, but i would guess it was due to flashing.
Now i do have a backup of my efs folder, but somehow putting that one back doesnt work.
I get the following error in my nv.log:
Backup NV restored.
"MD5 fail. Original MD5 '17f88xxxx etc'
Computed MD5 'fbe9xxxxx etc'
Anybody with a solution to this?
I was thinking it might be because with ICS my radio was changed to the new one, so it makes a different MD5 checksum. Does this make any sence at all?
[edit]
ok this is really weird. Apperently ICS causes this. When i restore a nandroid back to GB and restore my backed up imei files, they stick and i have my imei back. As soon as i go back to ICS the problem is back.

Lowroad said:
Hi,
for some reason i lost my Imei number. Im not sure when or how, but i would guess it was due to flashing.
Now i do have a backup of my efs folder, but somehow putting that one back doesnt work.
I get the following error in my nv.log:
Backup NV restored.
"MD5 fail. Original MD5 '17f88xxxx etc'
Computed MD5 'fbe9xxxxx etc'
Anybody with a solution to this?
I was thinking it might be because with ICS my radio was changed to the new one, so it makes a different MD5 checksum. Does this make any sence at all?
[edit]
ok this is really weird. Apperently ICS causes this. When i restore a nandroid back to GB and restore my backed up imei files, they stick and i have my imei back. As soon as i go back to ICS the problem is back.
Click to expand...
Click to collapse
If you're rooted, use Root Explorer & navigate to efs folder, then delete your nv_data.bin file, then rename your nv_data.bak file to nv_data.bin, therfore changing it from a bak file to a bin file, then reboot & see if this helps! If this fails try this technique here: http://www.youtube.com/watch?v=JqLK_2I-SBM Works with nexus s!

CrackDaddy said:
If you're rooted, use Root Explorer & navigate to efs folder, then delete your nv_data.bin file, then rename your nv_data.bak file to nv_data.bin, therfore changing it from a bak file to a bin file, then reboot & see if this helps! If this fails try this technique here: http://www.youtube.com/watch?v=JqLK_2I-SBM Works with nexus s!
Click to expand...
Click to collapse
thanks for the ideas!
However, i dont have any bak files. I dont think i need them, since i do have the original .bin file.
The original does work, but in ICS it doesnt stick. As soon as i reboot its back to 00049 again.
In GB it does stick, but obviously i prefer to stay on ICS
Very weird problem.. cant be the only one having this issue?

Lowroad said:
thanks for the ideas!
However, i dont have any bak files. I dont think i need them, since i do have the original .bin file.
The original does work, but in ICS it doesnt stick. As soon as i reboot its back to 00049 again.
In GB it does stick, but obviously i prefer to stay on ICS
Very weird problem.. cant be the only one having this issue?
Click to expand...
Click to collapse
You should have bak files!? bak files are for recorded changes! You say you have a backup of your cfs folder? if you do, open that & do as I mentioned, then try repacing that folder with the one on your device, reboot & see if that helps!

CrackDaddy said:
You should have bak files!? bak files are for recorded changes! You say you have a backup of your cfs folder? if you do, open that & do as I mentioned, then try repacing that folder with the one on your device, reboot & see if that helps!
Click to expand...
Click to collapse
Well as I said, i have done that and it does work in ics... Until i reboot. Then its back to 0049...
In gb it does stick after rebooting, which seems strange to me.

not an ideal solution but why not just script the file copy. so when you reboot you dont need to do it manualy...

MD5Sum mismatch

I dl'd the CWM Image of v21e GB off the Android development page, but when I restore it, I get MD5Sum mismatch.
help?

Have you tried to redownload it? Might be bad download.
I have mirrors here if you meant the v21e nandroid
V21E
Also what version of CWM are you using? I've had the least amount of issues with 5.0.2.0
Sent from my LG-P999

nitrogen618 said:
I dl'd the CWM Image of v21e GB off the Android development page, but when I restore it, I get MD5Sum mismatch.
help?
Click to expand...
Click to collapse
Don't rename directories or files, Nandroid MD5 has to match filepaths too.

I was messing with my keyboard layout bininaries the other day. I made a backup with cwm before hand. I went to restore and received this same message while restoring.
I did not mess with any file names, etc.
Sent from my LG-P999 using xda premium

Try the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=976453

Whyzor said:
Try the solution in this thread:
http://forum.xda-developers.com/showthread.php?t=976453
Click to expand...
Click to collapse
Sure it'll flash now, but if there's a reason for the hash's mismatch then you could have a corrupted backup. No harm trying though.

Jufjufjuf said:
Sure it'll flash now, but if there's a reason for the hash's mismatch then you could have a corrupted backup. No harm trying though.
Click to expand...
Click to collapse
Could make a copy of the original backup dir, remove the .md5 checksum in the copy so it generates a new one and restore from there. If it doesn't work, you still have the untouched original dir.

Nandroid Backups?

Coming from the HTC Rezound, I'm having some Nandroid issues on my VZW SGS3 (and questions):
1. On the Rezound, Nandroid backups were like four or five image files. However, on the SGS3, there's a \\Cynogenmod\backup folder with some image files and a \\cyanogenmod\blobs folder with a whole bunch of subfolders and smaller files. What is the difference? What does the blobs folder contain? Is it different because of the Cyanogenmod recovery or because it's the SGS3?
2. I had three backups from three different ROM flashes and when I try to restore any of them, they all fail with either an MD5 Checksum mismatch or some "unable to access" error. I tried the workaround of using the CMD line to rebuild the MD5 file, but no luck. I should also mention I renamed the backup folders because Nandroid puts them in folders dated in the year 1970 and I can't remember what backups were of what. Anyone else having this issue?
Thanks in advance.

wmaudio said:
Coming from the HTC Rezound, I'm having some Nandroid issues on my VZW SGS3 (and questions):
1. On the Rezound, Nandroid backups were like four or five image files. However, on the SGS3, there's a \\Cynogenmod\backup folder with some image files and a \\cyanogenmod\blobs folder with a whole bunch of subfolders and smaller files. What is the difference? What does the blobs folder contain? Is it different because of the Cyanogenmod recovery or because it's the SGS3?
2. I had three backups from three different ROM flashes and when I try to restore any of them, they all fail with either an MD5 Checksum mismatch or some "unable to access" error. I tried the workaround of using the CMD line to rebuild the MD5 file, but no luck. I should also mention I renamed the backup folders because Nandroid puts them in folders dated in the year 1970 and I can't remember what backups were of what. Anyone else having this issue?
Thanks in advance.
Click to expand...
Click to collapse
wmaudio what program are you using to create your nandroid backups? I've been using CWM 6.0.1.0 and noticed the 1970 files as well. I've been using the Clockwork Mod Recovery app so I can name the nandroid backups.

Bran.Bouchard said:
wmaudio what program are you using to create your nandroid backups? I've been using CWM 6.0.1.0 and noticed the 1970 files as well. I've been using the Clockwork Mod Recovery app so I can name the nandroid backups.
Click to expand...
Click to collapse
Awesome response. Thank you very much. I forgot that you could initiate the ROM backup process from ROM Manager. The only downside is that it backs up to the internal sdcard rather than the external one. I'll check options to see if I can change that. I wonder if moving the backup to the external card will cause me to encounter the same issues. Thanks again.

I just checked my clockworkmod/blobs folder and it is full of I'm guessing hashed folders, which contain a hashed file name. I checked the date in a astro file manager and they were all modified 2/6/1970 as well.
Does anyone know the use of these files? Can they be deleted?
Sent from my SCH-I535 using xda app-developers app

ENDonDESIGN said:
I just checked my clockworkmod/blobs folder and it is full of I'm guessing hashed folders, which contain a hashed file name. I checked the date in a astro file manager and they were all modified 2/6/1970 as well. Does anyone know the use of these files? Can they be deleted?
Click to expand...
Click to collapse
Most ROMs for the S3 are at least 550MB in size and can be over a 1GB. I checked the size of the dated folder and it's under 100MB, and the blobs folder is almost 2GB in size. Add settings files and other content created from general use of the phone, and that could theoretically bring a backed-up ROM to 2GB or more, so deduction tells me that I would recommend that you don't delete the blobs folder.

ENDonDESIGN said:
I just checked my clockworkmod/blobs folder and it is full of I'm guessing hashed folders, which contain a hashed file name. I checked the date in a astro file manager and they were all modified 2/6/1970 as well.
Does anyone know the use of these files? Can they be deleted?
Sent from my SCH-I535 using xda app-developers app
Click to expand...
Click to collapse
DO NOT DELETE THEM this is how cwm6 does backups now, just delete the main dated one from the backup folder and when you make your next backup cwm will automatically remove the ones from the blobs folder when it says "Freeing Space"
This is how Koush explained it:
New ClockworkMod Backup Format
TL;DR:
Don't delete /sdcard/clockworkmod/blobs
I've gotten a few questions about how this works, so I figured I'd make a post on it.
Basically, here's what happens:
The files being backed up are hashed (sha256, not that it matters). Then it checks for a file with the name of the hash in
/sdcard/clockworkmod/blobs
So, if the hash of the file was c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed, it looks for /sdcard/clockworkmod/blobs/c5273884b90d490134e7737b29a65405cea0f7bb786ca82c63 37ceb24de6f5ed
If the hash file is found, it continues on to the next file. Otherwise, it copies the file to the blobs directory with the file name being the hash.
ROMs and user data, for the most part, do not change too much between builds and backups. So, your APKs, system files, etc, are generally only stored once. This saves a ton of space. Especially between incremental backups.
Some of you may be thinking "well, how do I delete a backup?".
First, never delete the blobs directory. This would actually delete all your backups by rendering them unusable.
Simply delete the usual backup directory, and the next time you run a backup, all the unused hash files will be automatically delete (a process known as garbage collection). The recovery will show "Freeing space..." while this is happening.
Click to expand...
Click to collapse

Help please! phone won't boot

So I think I made a stupid mistake.
I was trying to reset google wallet and It hung at 97% and wasn't able to reset. I used the google wallet installer to basically change my build prop to the nexus build prop. I figured it would just overwrite my original wallet app anyway, and once my build prop was changed to the nexus build prop I could simply reset the app from there.
Anyways, phone rebooted and it's stuck in a bootloop and isn't getting passed the boot animation screen. I can get into recovery mode and download mode just fine. I tried restoring a backup I had with CWM and it says "md5 mismatch error". I really have no idea what to do at this point, and would rather not go completely to stock since I know my data is still there. Also I'm concerned to even restore a backup because i'm pretty sure my build prop was changed. I'm also wondering if it would be possible to simply factory reset and flash a new rom on top of it.
Any help would be greatly appreciated.

which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error

Khizar Amin said:
which rom are you using?
extract its build.prop and flash manually (if you know how to create a flashable zip)
if you are using a cm based rom, just reflash the rom without deleting anything..
and avoid using space while renaming backups... it gives md5 mismatch error
Click to expand...
Click to collapse
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.

BadUsername said:
No idea how to create the flashable zip. However I did notice a tutorial, I guess now would be a good time to learn.
I'm using darthstalker X1, it's a touchwiz based rom so I can't simply flash the rom again.
I saved all of my backups on my external SD card, can I just simply hook it up to my computer and change the backup names? And is my build.prop included in the backup I made?
Thank you for responding.
Click to expand...
Click to collapse
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4

Khizar Amin said:
renaming the backups again might not fix
i believe to have seen a script for sgy which fixes md5 mismatch error. but you need to give commands from terminal emulator.
if you have more than one backup of the rom, try to restore system only
if any one of them works your phone will boot up again
Edit: your backups contain the build.prop file in system.(partition type).tar
just extract this
and partition type may be rfs or ext4
Click to expand...
Click to collapse
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.

BadUsername said:
No idea how that is even done. I think I need windows and ADB in order to extract the build.prop, I have a mac.
I found a restore that worked, I just forgot to rename it and it wasn't too old thankfully.
I really appreciate you helping. And now I know of this mismatch error so I can name my backups correctly.
Click to expand...
Click to collapse
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time

Khizar Amin said:
to extract backups u need a tar extractor
if the backup format is something like .tar.a or .tar.md5 rename it to .tar first
and restoring the system only of your working backup would have booted your phone (in advance restore in recovery)
anyway this was an experience too for you.. so you would be carefull next time
Click to expand...
Click to collapse
Restoring my system partition only from advanced restore worked perfectly. All my apps stayed how they were and I didn't have to update all of my apps after I restored. Way better than doing a full restore in this case.
Thank you for this advice, this will be a very helpful method to me if I make any mistakes while messing with anything in my system folder. And yes, it was certainly an experience for me.
Sent from my SCH-I535 using Tapatalk 2