Database Info

MD5 Mismatch

I have the 155 SBF on my Defy, then i made an Nandroid Backup.
Wipe my whole Phone reflash the 155 SBF and then i want to restore my nandroid backup, but i get a MD5 Mismatch
Is there any opinion to restore it?

I think it is not going to be restorable now
Sent from Barebones-Defy using tapatalk.

Try remove spaces from nandroid backup folder's name.
Sent from my MB525 using XDA App

besides the having no spaces in the name as mentioned above, make sure the nandroid is at the backup folder and there are no more folders inside as well, like below
...backup/ (backup folder name)/nandroid
having this
...backup/ (backup folder name)/ (another folder)/nandroid will have md5 mismatch

probably something went wrong while calculating the md5 sum.
Copy the img file to your PC and calculate a new md5 sum. Place both in a folder in your backupfolder.
Remember that its possible that you end up with a not running system and you have to reflash the SBF

Hi,
dont install 2ndInit.
install directly Defy Recovery, After Rooting ur phone.

psicodelico said:
try remove spaces from nandroid backup folder's name.
Sent from my mb525 using xda app
Click to expand...
Click to collapse
a lot of thanks, man!

[Q] Can you rename Rom backup folders?

noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated

great question i also would like to know never had the balls to try cuz it says something about messing it up i know in rom manager u can under manage and restore (i think) also rom manager doesnt see ur cwm backups i usually go through ando zip but yea id def like to kno

Suprah said:
noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated
Click to expand...
Click to collapse
I don't know if you can rename the folders themselves, but you CAN rename the backup file itself. I use Root Explorer to do this. Just make sure you don't put any spaces in the new file name. You can use dashes and underscores to separate words and numbers, though.

Someone in the past said you can download mand5 to generate a new md5 sum, but I haven't tried it.

@visedmonk do u think andro zip will work it says it will let me rename then i click on that and it says change to file extension can make file unusable and i dont space any letters for instance il put cm for (cyanogenmod) rite next to the numbers havent had the balls to try it

sarni84 said:
@visedmonk do u think andro zip will work it says it will let me rename then i click on that and it says change to file extension can make file unusable and i dont space any letters for instance il put cm for (cyanogenmod) rite next to the numbers havent had the balls to try it
Click to expand...
Click to collapse
I dunno. I've never used andro zip. Only one way to find out...
But seriously, it should work. To be safe, though, make a copy of the file you want to rename and place the copy with the unaltered name on your computer or sd card or whatever. Then you can rename the file and see if it works. If it does, great. If it doesn't, you still have the backup you need.

Suprah said:
noob question i know however just a quick one,
can you rename nandroid backup folders with messing up md5sum ?
i load a ton of roms on the regular [a junkie i know] basis and get flustered when i have tons of backups but they are all dated
Click to expand...
Click to collapse
Don't know if you're using "nandroid" generically to refer to both the true nandroid as well as CWM but I rename CWM backup folders all the time and have never had trouble restoring them. I've done it from ROM Manager, via a file manager and also via ADB.

short/y said:
Don't know if you're using "nandroid" generically to refer to both the true nandroid as well as CWM but I rename CWM backup folders all the time and have never had trouble restoring them. I've done it from ROM Manager, via a file manager and also via ADB.
Click to expand...
Click to collapse
im talking about the folder not the actual files in the folder.
i just want to organize my roms so i can always jump between each

@suprah name it like this ex, 2011-06-16.05.57.13.....
you want...2011-06-16.05.57.13gingerbread ? rite well when i try that in andro zip it sayin it will make file unusable.... n i guess i will have to try and i always used to use rom manager and just go to manage and restore backups but its different with this phone especially cuz rom mana doesnt see cwm i guess?

Suprah said:
im talking about the folder not the actual files in the folder.
i just want to organize my roms so i can always jump between each
Click to expand...
Click to collapse
Yup, that's exactly what I'm talking about. I rename the folders all the time and have no problems restoring.

short/y said:
Yup, that's exactly what I'm talking about. I rename the folders all the time and have no problems restoring.
Click to expand...
Click to collapse
alright welp as long as you rename the folder without any spaces, then there would be no problem with restoring nandroid backups

nice nice will try soon cuz yea i have like 6 backups on here n was writing the date down with a name lmao

I renamed the folder once and couldn't restore. It was making a reference to the md5 file.
What I did to fix the backup is rename the folder again but this time without spaces and then it let me restore without any problems.
Now my Nandrioids are all organized
Hope that helped
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App

the stock rooted nandroid restore that's posted in the dev section is renamed to LG-P999-V10f. it's not the typical date format. and alot of people have used it. so the answer is ....yes.

crazythunder said:
the stock rooted nandroid restore that's posted in the dev section is renamed to LG-P999-V10f. it's not the typical date format. and alot of people have used it. so the answer is ....yes.
Click to expand...
Click to collapse
jus making sure, im not a dev so i assumed that was possible with some code editing

moshe22 said:
I renamed the folder once and couldn't restore. It was making a reference to the md5 file.
What I did to fix the backup is rename the folder again but this time without spaces and then it let me restore without any problems.
Now my Nandrioids are all organized
Hope that helped
Sent from my Bionix 2 - A TeamWhiskey Production using XDA App
Click to expand...
Click to collapse
Could be there's a coding error in the recovery code and stops parsing the directory name when it hits a space. The md5 file only references the individual files not the directory.
In general it's better to stay away from spaces in file and directory names. Back in the early days of *nix spaces were verboten and there are still some vestigial issues lurking either in the code or in the coding habits of some people. It's rare but it does happen. Hyphens, underscores, periods are all OK though.
Sent from my Xoom using Tapatalk

If after you rename the folder you get an md5 error. This http://forum.xda-developers.com/showthread.php?t=714114 can help you fix it.
BE SURE AND READ THAT POST COMPLETELY
It's imperative that one not generate an md5 sum for a nandroid that is actually corrupted. That will wreak all kinds of havoc on your system.
ONLY PERFORM THE ABOVE IF YOU KNOW ITS NOT RESTORING DUE TO A NAME CHANGE
EDIT: For the record, the above commands can be performed from terminal emulator if you know what bits to leave out. Saved me a few steps.

I rename all of my nandroid backups. They are easy to get confused otherwise. The only thing I change is the year in the date, and leave the month/day alone.
Sent from my LG-P999 using XDA Premium App

Yea I downloaded the Stock Nandroid and loaded it. I renamed the folder and got a MD5 error. Now I'm not sure it if was because of the rename or because it was a bad download to begin with.
I think I still have the file on my pc and possibly find the MD5 checksum before copying it over this time.

player911 said:
Yea I downloaded the Stock Nandroid and loaded it. I renamed the folder and got a MD5 error. Now I'm not sure it if was because of the rename or because it was a bad download to begin with.
I think I still have the file on my pc and possibly find the MD5 checksum before copying it over this time.
Click to expand...
Click to collapse
Most likely because you renamed it
Sent from my LG-P999 using XDA App

[Q] Change Nandroid Backup Name

I finally rooted TF and flashed Revolution HD. I understand that ROM Manager does not work with the TF. I want to be able to change backup names w/o messing up md5. Is there method or app for this?

go into file manager and change the name of the .zip

What zip? I have the CWM backup folder with sub folders for each backup and the 4 nandroid files in each.

mrevankyle said:
go into file manager and change the name of the .zip
Click to expand...
Click to collapse
Actually it looks like I can change the folder name for the Nan back without problem.

I thought that changing the names of the Nandroid backups would cause a restore to fail....unless the name was reverted back to it's original name.

HuskerWebhead said:
I thought that changing the names of the Nandroid backups would cause a restore to fail....unless the name was reverted back to it's original name.
Click to expand...
Click to collapse
That's what I feared. Evidently it's OK to change the directory name that contains the files. I tried a restore after and it went fine. Makes sense that the file md5 sum is not affected by chance nging folder name.

Hi, I changed the name of the folder and BAM!!.. the restore failed! I had two backups of two different ROM's and could not restore either of them after name changing! I managed to put back the old names and now both work. But I still need a way to identify so was wondering if there was any way to change the name and yet keep the md5 sum intact!!

MysticPhantom said:
Hi, I changed the name of the folder and BAM!!.. the restore failed! I had two backups of two different ROM's and could not restore either of them after name changing! I managed to put back the old names and now both work. But I still need a way to identify so was wondering if there was any way to change the name and yet keep the md5 sum intact!!
Click to expand...
Click to collapse
Usually a simple name change should still work. If you use symbols and stuffs in the name it might not work.
The latest version of TWRP let you name you nandroid backup.

clockwork-recovery MD5 mismatch FIX!

HEY GUYS I JUST FOUND THE KEY TO THE PROBLEM---clockwork-recovery MD5 mismatch IS VERY SIMPLE...
1.OPEN SD CARD IN WINDOWS.
2.DOWNLOAD 2 SOFTWARES ( MD5 CALCULATOR AND NOTEPAD++) JUS GOOGLE THEM AND INSTALL.
3.OPEN CLOCKWORK FOLDER IN SD VIA COMPUTER->BACKUP->(YOUR BACK).
4.NOW RIGHT CLICK ON NANDROID.MD5 AND EDIT WITH NOTEPAD++
5.GREEN HIGHLIGHTED PHRASE IS A KEY.
6.RIGHT CLICK ON REST EVERY FILE IN BACKUP FOLDER INDIVIDUALLY->MD5 CALCULATOR
7.MATCH THE KEY TO THAT OF NOTEDPAD++ FILE
8.IF THEY DONT MATCH COPY KEY FROM MD5 CALCULATOR AND PASTE IN NOTEPAD
9.SAVE AND EXIT.
10.NOW TRY RECOVERY IT;LL WORK.

MD5 is there for a reason...
Sent from my GT-S5670 using XDA App

Aspire said:
MD5 is there for a reason...
Sent from my GT-S5670 using XDA App
Click to expand...
Click to collapse
what reason??
can you share??
(and why did you change the name?)

Wikipedia said:
MD5 digests have been widely used in the software world to provide some assurance that a transferred file has arrived intact. For example, file servers often provide a pre-computed MD5 (known as Md5sum) checksum for the files, so that a user can compare the checksum of the downloaded file to it. Unix-based operating systems include MD5 sum utilities in their distribution packages, whereas Windows users use third-party applications.
Click to expand...
Click to collapse
Successful verification of the md5 file shows that the files are the same as at the time of packing and "not corrupted".
Consider this,
You flash a ROM which did not have a correct md5 checksum.
It may mean that the ROM was corrupted due to some reason and you may end up with a bricked phone.
though the chances of this happening are pretty low with a backup.. but better safe than sorry.
and i changed my username cause i liked it

arhant said:
HEY GUYS I JUST FOUND THE KEY TO THE PROBLEM---clockwork-recovery MD5 mismatch IS VERY SIMPLE...
1.OPEN SD CARD IN WINDOWS.
2.DOWNLOAD 2 SOFTWARES ( MD5 CALCULATOR AND NOTEPAD++) JUS GOOGLE THEM AND INSTALL.
3.OPEN CLOCKWORK FOLDER IN SD VIA COMPUTER->BACKUP->(YOUR BACK).
4.NOW RIGHT CLICK ON NANDROID.MD5 AND EDIT WITH NOTEPAD++
5.GREEN HIGHLIGHTED PHRASE IS A KEY.
6.RIGHT CLICK ON REST EVERY FILE IN BACKUP FOLDER INDIVIDUALLY->MD5 CALCULATOR
7.MATCH THE KEY TO THAT OF NOTEDPAD++ FILE
8.IF THEY DONT MATCH COPY KEY FROM MD5 CALCULATOR AND PASTE IN NOTEPAD
9.SAVE AND EXIT.
10.NOW TRY RECOVERY IT;LL WORK.
Click to expand...
Click to collapse
Or you can simply use the app root toolbox available in the market.
Sent from my Galaxy Fit @ 801Mhz- RazoDroid

Aspire said:
Successful verification of the md5 file shows that the files are the same as at the time of packing and "not corrupted".
Consider this,
You flash a ROM which did not have a correct md5 checksum.
It may mean that the ROM was corrupted due to some reason and you may end up with a bricked phone.
though the chances of this happening are pretty low with a backup.. but better safe than sorry.
and i changed my username cause i liked it
Click to expand...
Click to collapse
what's your real name, btw?? :curious:
and buddy, why don't you join us on fb? see my sig vvvv

Congratulations arihant you made FIT to appear on XDA Portal !!

invincible authority said:
congratulations arihant you made fit to appear on xda portal !! :d
Click to expand...
Click to collapse
thnx even i didnt knew that..thnx for telling..

You are GENIUS THX!!!

Aspire said:
MD5 is there for a reason...
Sent from my GT-S5670 using XDA App
Click to expand...
Click to collapse
Well yeah, MD5 is a great thing when it comes to checking consistency of a file, but for example, it bothers me because i have about 5-6 rom backups and they are all difrent roms, so i need to change the name of folder from date-time stamp to name of the rom, but when i do that i cant restore it any more because MD5 checksum apperantly checks the folders name also so i have to rename it again to date stamp... but sometimes it can be useful... just sayin'

I don't think cwm checks the backup names. I've got a couple of backups renamed to the ROM names and they work well.

well i dont know then, when i change their name back to the time stamp like 2012-03-15 11.12.32 then the restore will work, but when i leave a name like CM 7.2 rc5.5, when i chose restore, it prints out md5 checksum mismatched...

Same thing happens with me too..renaming the cwm backup file leads to the same mds mismatch error but sometimes it works..strange eh??

That never happens for me...
Sent from my GT-S5670 using XDA

Well I am an experienced hacker so ill explain. I do not have a brief knowleage about md5 but the md5 is calculated by the alphablet that it has lets say the name is ABHY then the md5 will be 1670 (This is an expamle) the other name is ZXDR the md5 will be 7304 now if you change the name the md5 does not change hence the error arises
Sent from my GT-S5670 using xda premium

yeah i know that, but i thought that he makes MD5 checksum of backup files, one by one, and not the whole folder...

slobo14 said:
yeah i know that, but i thought that he makes MD5 checksum of backup files, one by one, and not the whole folder...
Click to expand...
Click to collapse
Its assigned to the whole file
Sent from my GT-S5670 using xda premium

It looks like this is the case, I havejust spent the last hour trying to "repair" the Md5 checksums as described above only to find there was no problem with them, the problem was i had renamed the backup file. on checking in details when the file was created i renamed the file accordingly and voila the backup worked. I have renamed many backup files before and never had this problem but i did this time strange.

Informative post...
but MD5 checksum verification is useful...

I got md5 checksum error and it was caused by space in renamed folder name. After i remove space, restore worked.

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