When you create a backup using Clockworkmod 0.8, it puts the backup files in a directory on /sdcard/clockworkmod/backup/date_time. Can I rename that final directory to give it a more meaningful name (say, something like "Calkulin_110323"), or will that prevent Clockworkmod from doing a restore?
Thanks!
Ron
You sure can. Just don't use spaces in the name and it should be just fine.
Related
I went to restore a backup using Rom Manager, when in CWM I selected the one I wanted and I receive error message MD5 miss matched. How could this be from a backup made on the phone. Would renaming the folder have something to do with because I did rename folder, but others I have renamed do work.
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
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
Hi, I have an N8000 rooted with Stock 4.0.4 Rom
I installed the CWM 6.0.1.1 and everything was ok.
Yesterday I tried to install Rom Manager and it freezed so I pressed the power button until it reboots.
Now I noticed when I try to create a Nandroid backup with CWM the backup size is only 17Mb.
CWM did not show any error when backing up and it says Backup Complete!
I am afraid because I don't trust the backup.
I have an old backup and the size is 2,43 GB.
In that backup there are these files:
boot.img
cache.ext4.tar
cache.ext4.tar.a
data.ext4.tar
data.ext4.tar.a
data.ext4.tar.b
nandroid.md5
recovery.img
system.ext4.tar
system.ext4.tar.a
system.ext4.tar.b
In the 17.3Mb backup I have these files:
boot.img
cache.ext4.dup
data.ext4.dup
nandroid.md5
recovery.img
system.ext4.dup
Anyone knows what I can do to fix this?
Thank you
Do you also have a file in CWM backup file called "Blobs"? If so, this is where all the main data is backed up.
When you reflash a new rom how often do you seriously change your apps? This just copies the files that are different and checks against the other info to see if anything else needs backing up. I know I use the same apps no matter what base rom I'm using...
Check the properties on the blob file, it will be 1 - 2 gb...
The folder is almost 2gb. You are right. Thankyou
Sent from my GT-N8000 using xda app-developers app
What i cannot understand is how i can save a nandbackup on my PC.
There was a time when i could easily copy and paste the folder on my pc; now that files are split into two folders, how can i save them on my pc?
I have 4 nandbackups on my external sd. This means that i have 4 folders and the blob folder, that is full of smaller folders. I can't see how i can move just one or two of those backups on my pc when the blobs folder is shared among them.
Apparently i could do it thourgh ROM manager from the play store, premium version only.
I still think that that the old method (a very simple copy&paste) was the simplest way.
Normally, to restore SMS or MMS from an old backup, one can just restore the nandroid backup, use a third party SMS backup program to backup the data to sdcard or gmail, restore or install new rom, then restore the SMS from the third party backup software.
However, in my case, I had a nandroid with data on it that I wanted to keep but that wouldn't boot.
So I did some searching and others have had this problem before but I figured I'd put it here for others that may have the same problem. I am not taking credit for this I just found various pieces of info around the web and xda.
Requirement:
1. Winrar.
2. CWM backup
3. Windows
4. Brain
Here's the process:
To restore SMS/MMS from a CWM backup using MS Windows:
1. Install Winrar on your system
2. Open CWM backup folder
3. Now extract data.ext4 on your system
4. The contents of the data.img will be extracted to this folder. Wait for extraction to complete
5. Browse to data\data\com.android.providers.telephony\databases in the extracted folders
6. copy mmssms.db, mmssms.db-journal, to sdcard
7. use root explorer to copy these three files to \data\data\com.android.providers.telephony\databases
To restore contacts/call log from a CWM backup:
Repeat above process for \data\com.android.providers.contacts\databases
contacts2.db, contacts2.db-journal
Note: Be aware that replacing the existing files with those extracted from the backup will remove the existing data so if you're not 100% sure what you're doing, change the names to mmssms_OLD.db or otherwise back them up before pasting the files from the backup.
NOTE : You can also use Nandroid Browser , Nandroid Manager
Sorry to say.....not worked for me....
good work
Thank you, it works on my Samsung Galaxy S2 Gt-I9100,
you are my Hero.
I had no luck with this as the app versions seemed to differ. But there's this awesome python tool on github -- github.com - t413 - SMS-Tools -- which let's you export the db file's content into an xml file which can then be restored with "SMS Backup & Restore". That worked!