what exactly is md5? Ive noticed alot of the devs are posting the md5 with their roms now. Just wondering what it is. Also I was running calks rom and then flashed miui and cm7 then tried to restore back to calks and i get a md5 mismatch error..how do i correct that? do i just delete them from my sd card and make new nandroid backups? thanks
Redownload it. Md5s basically validate if the file was downloaded without problems
MD5 is an algorythym that will take any data (file) and spit out a (supposedly) unique hash. It is possible for 2 different files to have the same MD5 hash, but it's so rare that it doesn't matter.
So if a dev gives you an MD5 hash for their file, you can download a utility called md5sum and use that to check your downloaded file to see if it matches. If it doesn't then you got a bad download.
With your particular problem, something changed in your backupset to cause the mismatch. Did you delete any files from your backup folder, like the cache image? There should be a file called nandriod.md5 that contains one line for each image file along with it's md5 hash. Check each image file with "md5sum <filename>" and compare it to the nandroid.md5 file. If a file is listed in the nandroid.md5 file, but you don't have that file (ie. a deleted cache file), then just remove that line from the nandroid.md5 (i believe that will work).
I haven't tried it, but i think, if you rename the nandroid.md5 to something else like nandroid.md5.old, then it may just skip checking the md5's. Or you may need a blank nandroid.md5. Things to try if you feel like it.
please, allow me:
http://bit.ly/w33grw
Its the roms social security number...
Sent from my SPH-D710 using XDA App
cnstarz said:
please, allow me:
http://bit.ly/w33grw
Click to expand...
Click to collapse
Haha hohoho LMFAO. THAT IS CLASSIC.
Search. The most unused button ever...
If you noticed, he wasn't JUST asking what md5 was.. he was also having an md5 mismatch issue with a nandroid restore and was asking how to fix it. Would the google search on "md5" tell him that?
Although, this thread SHOULD be in the Q&A section.. shame on you OP
---- Edit ----
I have to admit though, the first time i saw LMGTFY, i nearly died laughing.
cnstarz said:
please, allow me:
http://bit.ly/w33grw
Click to expand...
Click to collapse
Related
i already checked similar threads but they refer to the evo and I want to make sure of our epics...
Im currently on CM7 (amazing rom)....i have a previous backup of a froyo rom that i was using before...im on cm7 and i make backups everyday since im playing around with apps and features from the main CM7 threads in xda...what is the name convention for nandroid backups...can I simple name it "srf froyo latest"?? with no spaces...
Make a random back up and see if it works. best way to see if its possible right? Worse thing that will happen is it won't load the back up.
Sent from my CM7.1/*Apocalypse-Talon* v3.2.1 NS4G
Yes, but no spaces
sent from my cm7-ified epic
Unless something has changed, I know that renaming your backups will cause an md5 mismatch. It won't work after that.
I believe there was a tool available to correct the mismatch after renaming, though I cannot recall exactly what it was or where. A Google search should provide something useful.
Sent from a secret underground bunker
I use a file that i put a description of each backup, I tried the rename and got the md5 mismatch error
jdelano said:
I use a file that i put a description of each backup, I tried the rename and got the md5 mismatch error
Click to expand...
Click to collapse
Same here. I name folders, and put the backups in those folders. If I have to use a backup, it has to first be moved back to it's original location though otherwise md5 mismatch.
Sent from a secret underground bunker
I've already stated how to get md5 mismatches to rematch again on another thread, but in the future, use an app such as Rom Manager to rename your nandroid backups.
I'll quote my other thread, gimme a sec.
P.S. I highly recommend you rename your backups to something simple with no spaces before you attempt to rematch via commands.
(Ex: 2.1Eclair)
This can also be done from Terminal Emulator on your phone while its on without the use of a pc. just be sure you add 'su' first for root permission.
# su
# cd /sdcard/clockworkmod/backup/whatyourenamedyourbackupto
# rm nandroid.md5
# md5sum *img > nandroid.md5
I hope this helps, and gets stickied, it's very important for anyone who gets MD5 mismatches on Clockworkmod for whatever reason.
Click to expand...
Click to collapse
On external_sd\clockworkmod\backup there are folders named by date/time they were created. Can I rename these backup folders so I know what I am restoring before I restore it?
agentfazexx said:
On external_sd\clockworkmod\backup there are folders named by date/time they were created. Can I rename these backup folders so I know what I am restoring before I restore it?
Click to expand...
Click to collapse
Yep, you absolutely can. I rename mine like 'Starburst198r_2010-10-14-11-15-03'. Can't remember the exact date format that cwm uses, but you get the idea. Just don't rename any of the files within that folder. That would mess up the md5 check.
I renamed my backups when I had my evo and none of them would restore
Euclid's Brother said:
Yep, you absolutely can. I rename mine like 'Starburst198r_2010-10-14-11-15-03'. Can't remember the exact date format that cwm uses, but you get the idea. Just don't rename any of the files within that folder. That would mess up the md5 check.
Click to expand...
Click to collapse
Gotcha, so appending the ROM name (for example) to the front of the folder name is fine. Good to know.
Other question...why is the time stamp so far ahead from my time?
just no spaces
Vegasrich said:
just no spaces
Click to expand...
Click to collapse
Cool. Good to know. Thanks.
Are u sure they will work? I would think it would mess up the md5
Sent From My Evo Killer!!!
musclehead84 said:
Are u sure they will work? I would think it would mess up the md5
Sent From My Evo Killer!!!
Click to expand...
Click to collapse
Where's the md5 generated from?
musclehead84 said:
Are u sure they will work? I would think it would mess up the md5
Click to expand...
Click to collapse
nandroid.md5 doesn't contain the directory name.
I back up with rom manager. It lets you rename the back up before it reboot into recovery and backs up,
Sent from my GT-P7510 using xda premium
You can definitely rename the files. I do it and have restored from them on multiple occasions. As mentioned above, you just can't have spaces in the name or the md5 check fails. If it starts failing when you rename, it's probably just a naming issue. May not want to try too many symbols (though I've used hyphens and underscores I think).
On a related note, anyone know if you can change the actual folder CWM backs up to? I haven't even looked, so I'm sorry if it's something super obvious.
With trying new roms, daily now it seems, is it possible to rename nandroid backups to something that makes more sense then just a date/time stamp like the name of rom/kernel?
Usually it doesn't matter as long as there's no special characters but I've tried it before and always get an md5 sum mismatch I just write down the date and the name of the rom
Sent from my SPH-D700 using xda premium
You need to use ROM Manager for this, then it will work with or without ROM Manager in CWM 5.0.2.7.
I usually put the backups in folders with meaningful names. I have to move them back to the proper location before restoring.
Never tried rom manager to do this though.
sent from my secret underground bunker
I was able to rename my backups with es file explorer just renamed it something like CM7_33 and it restored just fine
K3VlN said:
I was able to rename my backups with es file explorer just renamed it something like CM7_33 and it restored just fine
Click to expand...
Click to collapse
Sometimes that will work for me also... most of the time I will get an md5 sum error when I rename them though... like biggoron said the easiest way is to write them down somewhere... or as (insert name here) said you can put them in a seperate folder with the name and then move them back before restoring them....
Sent from my SPH-D700 using Tapatalk
hmmm strange error to have happen but good to know guess id better make another back up and delete the changed one
I had the md5 mismatch too. It seems you can rename as long as you don't put any spaces. I have been renaming mine CM7N##beforeCM9blahblah and it still works. If I put spaces in, then md5 mismatch
kennyglass123 said:
You need to use ROM Manager for this, then it will work with or without ROM Manager in CWM 5.0.2.7.
Click to expand...
Click to collapse
Thanks, I renamed some of them using ROM manager and the one I tried worked.
I tried twice to do it manually, no spaces and always got the md5 error. My backups are too important so I only use ROM manager as it makes sure the MD5 is correct.
kennyglass123 said:
I tried twice to do it manually, no spaces and always got the md5 error. My backups are too important so I only use ROM manager as it makes sure the MD5 is correct.
Click to expand...
Click to collapse
Yup, this is the main reason I use rom manager, to name my backups to keep track of them easier. The nightlies for cm7 in rom manager don't hurt either..
I was actually trying to restore a backup which had an altered name and the recovery kept prompting error.
I had to rename the prefix back to BCDEARS in order for it to restore.
I think the prefix is important because it's a code to the kind of content that was actually backed up.
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
As long as you only add to the beginning without changing the rest if the name you should be ok.
Although I might recommend another option. When I need to categorize them I just create a new folder, name the new folder whatever i want and move them into it. If I need to restore a specific nandroid I just move it back into the original CWM backup folder and restore it.
iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
I've heard as long as you don't have any spaces, it should be fine. Such as "Blend.ICS" or something. I had the same issue long ago, I put the name of a ROM (with spaces) instead of the date then had the same issue. I simply fixed it by replacing the name back to a random date without spaces.
I never rename anything but I have heard you can change the beginning portion and I try to limit the amount of nandroids only three stock, daily driver, and one test build I update my daily every few days and delete the old one
Sent from my SPH-D710 using XDA
I always change the name because it only shows the timestamps. I modify the name with rom version and status good or final ....
I check the md5 checksum after the name change and it's always successful. Even I restored with name changed nandroid backup multiple times and never had any problem.
Only the problem with nandroid backup was I made it thru rom manager or rom toolbox. It's causing md5 mismatch on ics rom. So ifyou use rom toolbox or rom manager on ics, you need to extremely careful.
Sent from my SPH-D710 using xda premium
Yeah I have an ICS ROM and I tend to avoid using apps like ROM Manager and just do it myself in Recovery. But thanks everyone for the responses. I think I'm just gonna create a folder for them like rwilco said or just edit the beginning.
One of the good habit is verifying the md5 checksum using the tool something like afv. I'm always check the md5 checksum against the nandroid backup. This tools is free and very useful...
MD5 Checksum
How do you do the md5 check? Is there a special command you need to type at a command prompt?
bronski813 said:
How do you do the md5 check? Is there a special command you need to type at a command prompt?
Click to expand...
Click to collapse
There are many ways but I use afv.
For example - (serious of screenshots)
1. You can change the directory name of nandroid backup (it's not related to md5 checksum at all. But don't change the individual file's name inside of the directory. If you do that, then you have to change the md5 checksum file and checksum data also.
2. Open afv and select file
3. move to the directory and long click on nandroid.md5 file
4. select verify nondroid backup
5. check the result.
If you want to check the individual backup's md5 checksum, select the file and do the 'calc md-5 checksum' and compare the result with nandroid.md5 file.
Lots of fun (lof)!
kobridge said:
There are many ways but I use afv.
For example - (serious of screenshots)
1. You can change the directory name of nandroid backup (it's not related to md5 checksum at all. But don't change the individual file's name inside of the directory. If you do that, then you have to change the md5 checksum file and checksum data also.
2. Open afv and select file
3. move to the directory and long click on nandroid.md5 file
4. select verify nondroid backup
5. check the result.
If you want to check the individual backup's md5 checksum, select the file and do the 'calc md-5 checksum' and compare the result with nandroid.md5 file.
Lots of fun (lof)!
Click to expand...
Click to collapse
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?
samsmalls said:
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?
Click to expand...
Click to collapse
If nandroid backup md5 file mismatch, then calculate individual files md5 checksum and compare with nandroid.md5 data. Modify the checksum data from nandroid.md5 file. It does not automatically match the md5. AFV only provides verification and calculation.
To fix the md5 mismatch automatically, you can use another tool something like 'Root Toobox'. This tool fixs the md5 error but does not show the fixing result. So, this tool is not recommended to fix the md5. There are many other tools in the market, please try to search.
Update - do not use root toolbox. It breaks the md5 file.
samsmalls said:
How do you correct the md5? im not sure what i did but every nandroid i make refuses to restore saying that "md5 mismatch"...
Can afv match the md5?
Click to expand...
Click to collapse
If you have a mismatch with md5 - see my signature. You can type the command from terminal on your phone. Then everything is right again.
Oops, forgot I deleted it from my signature. Here it is:
http://forum.xda-developers.com/showthread.php?t=714114
iniz94 said:
Some of my Nandroid backups have been getting md5 mismatched lately. I just realized that the reason may be because I change their names to something like "Blend ICS" or "Blazer", etc. Anyone know if this is the problem? And is there any way to rename them without causing a mismatch? Someone said to just add some like "blazer" without spaces right before the auto-named CWM folder (so basically the date). This won't cause problems will it?
Click to expand...
Click to collapse
If you have this problem, use rom manager or romtoolbox to rename the backups , and itll work
This thread is 4 months old...
Sent from my SPH-D710 using xda app-developers app
Indeed it is
Sent from my SPH-D710 using xda app-developers app
krishneelg3 said:
If you have this problem, use rom manager or romtoolbox to rename the backups , and itll work
Click to expand...
Click to collapse
So one person says Rom Manager / Rom Toolbox will not work for renaming nandroids, you say it does. Which is it?
I recently had some backups that didn't work because I renamed them completely. I got md5 mismatches. I dont use CWM though. Strictly 4EXT. I dont believe Rom Manger will do much for you if your recovery is not CWM. Still, renaming seems to be problematic but you have to do something to keep them organized/separate. Dates dont mean much a few weeks later.
It doesn't matter what you name the backup. Just don't add spaces instead if where the space is put dots "." And it'll work.
Hey guys
I've gone through all the steps as instructed, but can't install HD RSL15 successfully. I downloaded the installation file from a mac which then automatically unzips the folder. Zipped it back up with 7zip and threw it on the phone. I went through all the prescribed steps using TWRP 2.6 and AndroidUnite's video on youtube (How To Install TWRP Recovery And Flash Custom ROM) as example. This is the 2nd time Ive downloaded the file and I switched over from CWM based on advice in these threads.
When it comes to installing the ROM the window ends up looking like this:
Checking for MD5 file...
Skipping MD5 check: no MD5 file found.
Error flashing zip...
Updating partition files...
FAILED
Have I done something wrong during the previous steps (flashing, installing recovery) or does it have something to do with the method of zipping the files (tried fastest and store as compression options, doing store makes the file unreadable by the phone during recovery mode)?
I've read there is supposed to be an md5 file in the installation files, but mine didn't have any. Can someone let me know about the contents of the zip file so that I can zip it up as intended or something. Please help
PS. I know this is a copy of another reply i posted, but i cannot delete those and i haven't received any help in the other threads
I'm having a similar issue, only I run the checksum before I flash and the md5 is never the same. Has anyone fixed this?
Sent from my SGH-I747 using xda app-developers app
KissyLynn said:
I'm having a similar issue, only I run the checksum before I flash and the md5 is never the same. Has anyone fixed this?
Sent from my SGH-I747 using xda app-developers app
Click to expand...
Click to collapse
KissyLynn, can u send me a screen shot of ur zip file's contents please
Don't let your Mac unzip the file. There is probably a problem when unzipping or rezipping. Just leave the file the way it is, don't unzip it.
Sent from my Nexus 7
stelv said:
Don't let your Mac unzip the file. There is probably a problem when unzipping or rezipping. Just leave the file the way it is, don't unzip it.
Sent from my Nexus 7
Click to expand...
Click to collapse
No choice in the matter. Can u let me know what the zip contents should look like so i can try and solve the problem
Rhetorical said:
No choice in the matter. Can u let me know what the zip contents should look like so i can try and solve the problem
Click to expand...
Click to collapse
Here is a screenshot of the contents, I really don't think it is going to work if you unzip and zip the file. You usually can't just rezip a rom file. The md5 will be different and it will give you an error. Not sure what you are using on your mac to download, but maybe try with chrome. The file should not automatically unzip, and if it does there should be a zip file intact still somewhere on your mac. You need to flash the original zip file.
stelv said:
Here is a screenshot of the contents, I really don't think it is going to work if you unzip and zip the file. You usually can't just rezip a rom file. The md5 will be different and it will give you an error. Not sure what you are using on your mac to download, but maybe try with chrome. The file should not automatically unzip, and if it does there should be a zip file intact still somewhere on your mac. You need to flash the original zip file.
Click to expand...
Click to collapse
Hey Stelv, i did a screen share and am busy copying what i hope is the original zip file (hyperdrive rsl15 universal s3.zip.download), but we'll have to see, files are still being copied over individually so not sure it's right. I don't see an md5 file in that main directory, where is it situated??
Md5 is achieved by opening terminal on your mac and typing Md5 and then a space and then drag and drop your zip file into terminal and hit enter. If it doesn't match the md5 number in the hyperdrive thread its not going to install correctly. There are also md5 checker apps on the market.
Sent from my SAMSUNG-SGH-I747
redownloaded and it works like a charm, thanx for the assist