I made 2 different CWM backups (Cleanrom 3.0 and CM9 roms). Neither of them are able to be restored to the phone, due to an MD5 mismatch. What exactly does this mean? Is it because I edited the name of the backup folder? I've done this before with my Galaxy SII, and those still restored fine.
did you put spaces in the names of the backups? I had the same problem and it was because I put spaces in the name.
Yes I did... I will try it without the spaces and see if that works. Thanks!
That's probably it. CWM will not restore if the file has any spaces in the file name.
OK it works now, that fixed it. What a n00b mistake, thanks all.
Related
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.
I have been palying around with various Zoom configuration. As I get one close I do a nandroid backup with CWM Recovery. I would like to be able to rename them with discriptive names so that I can find a specific backup when needed. Every time I try I get an MD5 sum error.
Does anyone know how to rename a backup and fix the MD5 sum?
REHolt218 said:
I have been palying around with various Zoom configuration. As I get one close I do a nandroid backup with CWM Recovery. I would like to be able to rename them with discriptive names so that I can find a specific backup when needed. Every time I try I get an MD5 sum error.
Does anyone know how to rename a backup and fix the MD5 sum?
Click to expand...
Click to collapse
You will need a file manager, such as Astro or what I use, Super Manager. Your nandroid back ups will be under folder "external 1" , clockworkmod, backup.
It's all in the file manager
I use root explorer. One thing to remember is that you can't use certain characters. I don't know exactly what they are, but if you only use what are in the original as far as punctuation you should be all set.
REHolt218 said:
I have been palying around with various Zoom configuration. As I get one close I do a nandroid backup with CWM Recovery. I would like to be able to rename them with discriptive names so that I can find a specific backup when needed. Every time I try I get an MD5 sum error.
Does anyone know how to rename a backup and fix the MD5 sum?
Click to expand...
Click to collapse
Use a md5 checker and check the whole folder, find the md5 file and open a text editor and add the md5 you just got in place of the old one
And if you put any special characters in the name or spaces you will get a md5 sum error
Sent from my ADR6400L using Tapatalk
the easiest way is use root explorer and stick to numbers and alphabet characters as much as possible. it will handle the md5 for you. just renaming the files with a file manager will ruin the backup.. DONT DO IT. I found out the hard way unfortunately.
As a test, I copied a CWM backup folder from my phone to my Windows PC. I renamed the folder without spaces or special characters and then copied the entire folder back to the phone. Upon restoring using CWM 5.0.2.7, it successfully passed md5 test and restored. I then rebooted with no problem.
I also compared the md5 sums in the nandroid.md5 files from the original folder (before renaming) and after renaming and they are identical.
The key is to avoid spaces or special characters; use underscore "_" instead of spaces in the folder_name.
I hope this helps!
you can use - instead of space
md5 fail with space, if rename again it will re-work, data is NOT ruined if you rename
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...
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
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