Related
So I got a phone with cryogen7 or whatever from my friend. I want to make it completely stock again. I dont have his sd card. so I just have mine from another phone. I downloaded the stock g2x gingerbread file, but when I try to restore it, i get a md5 mismatch or something. I saw a thread on that but I dont know how to write code. just hoping someone could help me out. thank you.
Download it again, also try another browsee
Sent from my LG-P999 using Tapatalk
Download the V21E nandroid from this thread:
http://forum.xda-developers.com/showthread.php?t=1196019
Then use your computer to extract the folder from the zip file you download. Copy that folder to the sdcard on your phone, and place it in the ./clockworkmod/backup directory. Then boot into clockworkmod recovery and select backup/restore > restore and then choose the backup folder you just copied to your sdcard. Make sure to do a full wipe/factory reset from within clockworkmod before you reboot or you might get a bootloop.
If you want stock recovery then use tga gunmanns one click app in the development section to restore stock recovery. Then you'll be 100% unrooted stock again.
IF the name of the zip has spaces in it it wont flash
Mister Hat said:
IF the name of the zip has spaces in it it wont flash
Click to expand...
Click to collapse
Nandroid backups aren't flashable zips. With the files from the thread i linked to, you have to extract the backup folder from the zip before you restore it. But yes, you are correct that spaces in the name of the backup create issues.
Did you figure it out yet?
Sent from my LG-P999 using XDA App
it freezes on "checking md5 sums"... don't know what to do
Are you using your computer to extract the V21E folder from the zip file? Ive used my phone before to extract it before and gotten the md5 mismatch error, and then used my computer to do it and it worked fine.
are you sure the rom your using is for your phone?
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
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Not sure if it's available in the Free Version but Titanium Backup allows you to extract from a Nandroid backup.
I just checked and it gave me a listing of all the apps I have installed and there was one listed as Messages, I can only assume that it's my texts.
Yes I do have the paid version. I tried restoring both Go SMS and the Messages app from TiBu using my TWRP backup, but they basically just reinstall the app. I still have no messages in either app :/
I didn't realise TiBu was Titanium - how retarded of me... haha
Any chance of backing this one up restoring the other nandroid and then backing up the txt's from within the stock messaging app then restoring?
Unless someone else knows how open .win files
I did think of that, but I don't want to run the risk of a corrupted restore. I've had it happen s bunch of times, unfortunately.
Sent from my HTC One X using xda premium
silentecho13 said:
So, I just flashed CleanROM 4.5. Everything went smoothly, except I've lost all my sms/mms messages from both Go SMS and the default Messaging app.
I have a TWRP backup here on the computer, as well as a TiBu backup of all user apps.
I can't seem to find the SMS database in the TiBu backup at all, and I can't figure out how to browse the TWRP backup to find it.
Nandroid Explorer doesn't read TWRP backups either...
Anyone have a solution?
Click to expand...
Click to collapse
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
TheNightHawk223 said:
Yep, it's fully possible. Just get the nandroid backup file, and make a copy and change the extension to .zip After that just unzip, and volia. A bit of searching (should be in the apps file, I forgot the details).
Sent from my HTC One XL using xda premium
Click to expand...
Click to collapse
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
silentecho13 said:
....so I saw this too late.
I went and restored my backup, grabbed the files, and restored the new backup hoping that neither were corrupted.
It all went smoothly, but I'll definitely remember this for the next time I mess up...haha.
Thanks!
Click to expand...
Click to collapse
Glad I could help, almost everything that uses the term "compressed" seems to be able to be turned into a .zip
Sent from my HTC One XL using xda premium
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
eldamobo said:
Sorry I'm not following this. I made a twrp backup using 2.5.0.0 and I got a bunch of .WIM files.
7-Zip recognizes those and opens them to have a .ext4 file. However every ext browser and mounter (in windows) I've tried can't seem to browse them. I tried renaming them zip, but I'm guessing I'm doing something wrong.
With old CWM releases, my backups were tars which were easily browsable.
Am I missing something?
Thanks!
Click to expand...
Click to collapse
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
uberamd said:
I know this is an old post, but it's the first Google result.
What you want to do is rename the .wim file to .tar.gz, then extract the file (command line is tar -xvzf filename.tar.gz). If you look at the TWRP logs it indicates that it uses tar to create the archive file.
Click to expand...
Click to collapse
Thanks uberamd. I'll give this a shot. I guess I should have checked the logs. Tar would be great!
hi there.. i made backup too.. now i want to bring back the boot.img and recovery.img..
most of guys said to me the " boot.emmc.win " is the stock boot.img.. but this one is 16 MB and other boot.img i saw till now are 6 MB..
and how can i restore the stock recovery? does the backup contain the recovery?
any idea?
N5 TWRP Backups
I made a backup with TWRP, and copied the .WIN files to my PC. Tried renaming those to .ZIP or .tar.gz, but 7zip could not open either of those!?
Are you guys sure the backups are actual zip or tar/gz files?
EDIT: Nevermind, I renamed to .tar and it opened. I suppose compression is not enabled by default
Except the data.ext4 is splitted in two files: data.ext4.win000 and data.ext4.win001 and renaming either of those to .tar, .zip or .tar.gz doesn't help
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
eldamobo said:
Just a guess here but what if you concatenated the files together?
If you can post the details from the twrp log that would also probably help.
Click to expand...
Click to collapse
Yes concatenating can help however all those .WIN files are either .tar files or .tar.gz (if compression is enabled). That's quite simple in the end, except that 7zip doesn't always recognize the format properly. If I open the system.win file, it only shows about 60MB of files, whereas the whole .win file is 600MB uncompressed, hence I was confused about the format.
I've been able to update my app to read those .tar, .tar.gz and extract any file from it now Pretty cool!
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
VIPLightning said:
Be advised though, for some reason when I rename the backup to .tar or .tar.gz for twrp 2.6.3.1, it doesn't want to open or extract. I don't know if it's only happening only for t-mobile sgs3 or the developer removed the ability for us to do it. But I did revert it back 2.6.3.0 and it's working fine for me. Thought I want to just throw it out there.
-VIPLightning
Click to expand...
Click to collapse
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
3c said:
That's interesting. Which app are you using to open those TWRP backups? Asking because I found out that many extractor are unable to open those in the first place! 7zip for example showed me a 80MB content while the file was 600MB! And I'm using a very old 2.6.0.0 TWRP, so I got to try this last version out
Would you mind trying Android Tuner Free, last update allows opening those .tar and .tar.gz files, but got to rename the TWRP backup to either of those first. It won't open the tar inside the gz file, but you should be able to extract it and then open it If you don't have the time, I can understand, but hopefully you still have a 2.6.3.1 backup file around?
Click to expand...
Click to collapse
I should have no problem giving it a try. Yeah I deleted my backup. I'll go ahead and update the recovery when I get a chance to later on. Then I'll make another backup And the program I used for extracting and opening was WinRAR. Everytime I tried to, the 2.6.3.1 backup would always come up as corrupted or damaged.
EDIT: So I tried out your app. Indeed the explorer does work. Thanks so much. Even though first it took some time, I was able to get to my stuff. But it was worth it. I've never seen an app that can actually do so much. Thanks again.
-VIPLightning
What are WIN files?
Along with win and md5 files TWRP creates recovery.log file. If you look inside this file, you can see the full log of what TWRP has done. There you can notice that win file with the boot partition is in fact a result of the dd command, so that's a bit-to-bit copy of the boot partition, sometimes named as .img file.
Other partition win files are tar files. If you used compression, you got .tar.gz files.
So .win files are raw partition data, .tar, or .tar.gz files. See recovery.log
If you use compression in TWRP, just rename the .win to .tar.gz
i.e data.ext4.win to data.ext4.tar.gz , then use tar -xvzf , extracts perfectly fine.
I used this to extract my apps from a TWRP backup just now.
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