Related
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!
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
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
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.
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.