So i renamed my backup folder. To something that makes sense to me. But when i went to restore it, it gave md5 mismatch.
I have tried
# md5sum *img > nandroid.md5
# md5sum *dup >> nandroid.md5
but it still gives md5 mismatch.
A file not having an entry in the .md5 probably gets flagged as a mismatch. May I ask why you would use dup? Incremental backups are messy with a good system, and CWM is quite possibly the sloppiest I have ever seen. Then there is the corruption problem. Is it necessary to keep more than a couple backups? I keep a current one on my phone, and a slightly older one on the computer.
Aerowinder said:
A file not having an entry in the .md5 probably gets flagged as a mismatch. May I ask why you would use dup? Incremental backups are messy with a good system, and CWM is quite possibly the sloppiest I have ever seen. Then there is the corruption problem. Is it necessary to keep more than a couple backups? I keep a current one on my phone, and a slightly older one on the computer.
Click to expand...
Click to collapse
It's all default through cwm. Cwm is not the issue. Me touching it is the issue.. and it was my cm10 backup. And I'm certain all files are added to the nandroid file.
Sent from my SGH-T999 using Tapatalk 2
Default of what version of CWM? Newer versions swapped to tar as default backup mode. Was the backup created with the same version of CWM you are attempting to restore it with?
Perhaps it's the folder name that is the problem. Are there any spaces in it, or anything? I always rename mine to CM10-MMDDYY and never had issues with restoring.
Aerowinder said:
Default of what version of CWM? Newer versions swapped to tar as default backup mode. Was the backup created with the same version of CWM you are attempting to restore it with?
Perhaps it's the folder name that is the problem. Are there any spaces in it, or anything? I always rename mine to CM10-MMDDYY and never had issues with restoring.
Click to expand...
Click to collapse
Yes there is a space... and I can't remember which version of clockwork I used. I'll try removing the space.
Sent from my SGH-T999 using Tapatalk 2
Removing the space fixed it. Thanks for the brainstorming!
Sent from my SGH-T999 using Tapatalk 2
Related
So heres the situation. I made a backup of my phone using rom manager because I wanted to try out the new cyanogen. I got done playing with it and I went to revert back to my restore I had just created. During the restore I got an md5 mismatch error.
I used the instructions here to repair the restore
http://www.droidforums.net/forum/droid-hacks/40428-checking-md5-sum.html#post430944
su
cd /sdcard/clockworkmod/backup/*rom name (date and time usually)/
md5sum *img > nandroid.md5
reboot recovery
The procedure worked in the sense that I was able to restore the image. The problem is after the restore I am stuck at the white "HTC Incredible" screen. I tried wiping caches and running the restore again but I am unable to get the phone to reboot.
I was able to restore to a much older restore that I had previously created but it lacks alot of updates and changes that I have made since then. Not to mention my Angry Birds saved game.
Looking at the restore files it looks like the folder for the restore contains a hand full IMG files. What i'm wondering is since it appears that the boot process is damaged I'm wondering if I could make a backup of the phone as it is now then take lets say the data.img file (or whatever file i need to recover installed apps and saved games) and overwrite the img files for the restore i just created. I could then use the same procedure I just performed to recreate the md5 hash and run the restore. My home is that will allow me to get my data back and still allow the phone to boot.
What do you guys think? Is it doable or am I going to be in a world of hurt if I start messing with this?
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
s197 said:
Did you put spaces or special characters when you named your backup? This can cause MD5 mismatch errors.
Click to expand...
Click to collapse
NO, I didn't. I used the default setting. I think it was 2010-12-29.01.34.10 or something like that.
setexascustoms said:
Something else you might try is to restore the latest backup, then do an advanced restore of just the boot partition from your older backup. It's worth a shot I'd think.
Click to expand...
Click to collapse
Thanks man, This worked perfectly. Restoring the boot.img didn't fix the problem but restoring the system.img did. I have all my data back and my phone is fully functional again. Thanks again.
I ran in to an issue today.... I used CWM (Touch recovery 5.8.0.2) to backup my system then flashed the latest CM9 nightly. I was getting some force close issues so I tried to revert back to my backup. I got an "error restoring /data" and the restore stopped.
After looking in to it I think the issue may be the /data backup is over 2 gigs. CWM (or busybox?) has an issue with this and cannot restore (or maybe the way the tar archive is created gives the problem). I've read some people trying things like:
Split the data.ext4.tar file into half so they are less than 2GB.
Push both to the device using adb.
Execute "tar xvf data.ext4.tar -C /" for each part.
Click to expand...
Click to collapse
I tried this but got the error:
Code:
/data/media # tar xvf data.ext4.tar.001 -C /
tar xvf data.ext4.tar.001 -C /
tar: invalid tar magic
Help! How can I restore my backup?
I even tried some earlier backups but they all had the same error with /data.
Thanks!
I have heard bad things about touch recovery. have you tried restoring your backups with regular CWM?
WiredPirate said:
I have heard bad things about touch recovery. have you tried restoring your backups with regular CWM?
Click to expand...
Click to collapse
Yeah, I gave that a try and no luck... I think the tar used in both touch and non-touch have the same 2gig limit.
Would it be possible in adb to delete the /data then push the untared /data from my computer to the phone? The file untars fine on my desktop system.
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Jubakuba said:
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Click to expand...
Click to collapse
Yeah, I'm leaning that direction. I'm just really annoyed that they nandroids are sitting there but I'm being confounded by the tar functionality. I'll be switching to TWRP myself.
When you want to install or send some data to your new rom, you can use "nandroid browser" from the store
https://play.google.com/store/apps/...dvZGRjaGVuLmFuZHJvaWQubmFuZHJvaWRicm93c2VyIl0.
Jubakuba said:
And this is why I switched to TWRP recovery.
Compression allows the backup to be less than 2 gigs...and it works.
Personally, I'd skip all that...
Just wipe all data.
Install the rom you're trying to restore data for...
And use titanium to restore app data from the nandroid.
Click to expand...
Click to collapse
With TWRP can you restore backups that were made in CWMR?
I'm almost thinking this is not something to blame on CWM. If CWM makes a call to tar (in busybox) then it's the busybox version of tar that has the issue.
I was able to get my CWM /data backup back on my phone. I made two copies of /data. I opened them up in 7zip and split them in to two archives (deleting the first half of one and second half of the other). I then restored by doing:
tar xvf data.ext4-1.tar -C /
tar xvf data.ext4-2.tar -C /
(I had tried this earlier but I think I corrupted my tar archive which is why it was giving me the error).
Using the busybox (from CM9) and trying the same thing on the full 2.6GB tar archive I'd get an error stating "Value too large for defined data type". From what I've read this may be a result of how tar (in busybox) was compiled.
The funny thing is I'm getting the exact same problem in TWRP if I don't use the compression option and the /data backup is greater than 2GB! Using compression I'm at 1.6GB and everything is fine.
Pls help.
I recently backup my Gnex using Touch CWM before flashing custom kernel. The backup process is successful, but when I tried to restore it, it said MD5sum missmatch. What does it mean and any idea how to solve it?
Thanks in advance.
here's another thread about the matter: http://forum.xda-developers.com/showthread.php?t=1835914
in short, if you have nandroid.md5 then the backup image is corrupt. if, however, you don't, the error you see is due to CWM not being able to find nandroid.md5, then you have to create it yourself as mentioned in the thread.
Woah. I had this problem too, but I didn't have to do any of that to resolve it.
One reason for MD5 mismatch is renaming of the backup folder - apparently you are allowed to append letters at the end of the folder name, but special characters, like space for instance, aren't allowed. (I might be wrong about exactly how you can modify - it depends on the CWM Touch version you're using).
I just removed the changes I'd made to the folder name (the format is yyyy-mm-dd.hh.mm.ss ), and rebooted - presto, CWM restore worked without any hitches
I did a backup in ROM manager, I went to restore and it said "This does not seem to be a valid backup. The MD5 file is missing." Is there anyway to fix? I'd hate to lose the data .
do another back up in recovery,
I think the problem with doing another backup is he's already wiped.... Maybe.
sent from Incredible ViperDIX
Assuming you're using CWM or a compatible recovery, you can calculate a new md5 by running this command in a terminal emulator from the directory holding your backup files:
md5sum *img > nandroid.md5
Keep in mind, though, if the files were corrupted since the original backup, this will allow them to be flashed, since it's creating the verification md5 based on what's there now, not what was there originally. But it's pretty rare to have files become corrupted just sitting on your sd card. I've done this many times without issue.
Jizzylax said:
I think the problem with doing another backup is he's already wiped.... Maybe.
sent from Incredible ViperDIX
Click to expand...
Click to collapse
ChrisDDD said:
Assuming you're using CWM or a compatible recovery, you can calculate a new md5 by running this command in a terminal emulator from the directory holding your backup files:
md5sum *img > nandroid.md5
Keep in mind, though, if the files were corrupted since the original backup, this will allow them to be flashed, since it's creating the verification md5 based on what's there now, not what was there originally. But it's pretty rare to have files become corrupted just sitting on your sd card. I've done this many times without issue.
Click to expand...
Click to collapse
Sorry guys, I got busy irl. Forgot i posted this.
The file i looked at it on my comp, it was missing half of the files that a complete back up was. I assume it's corrupt. I already have most things back to the way they were, i'll be sure to make a back up in recovery next time.
Hello,
I having been having some major problems the last 2 weeks with any and all backups i create of my phone. I have tried to make backups of various Roms using both Rom Manager and also directly by flashing into recovery (CWM touch). Each time the backup is successfully made, but then when i try to flash the backup i get errors saying "file not found". I lost my stock rooted backup, a backup of CM10, a backup of Liquid Smooth, and a backup of JellyBam. Does anyone have any idea why my backups don't seem to work? This is incredibly frustrating as I lose all of data and have no security blanket should something go wrong. Every time i flash a new Rom i wipe Dalvik, Cache, and factory reset/wipe.
Anyone have any idea what's going on with the backups?
what versions of android have you been flashing and are you sure your on the latest recovery?
psycho2k9 said:
what versions of android have you been flashing and are you sure your on the latest recovery?
Click to expand...
Click to collapse
Thanks for the reply. believe liquid smooth was version 4.2 and the jellbam was 4.1.2. My stock was either 4.1.1 or 4.1.2, whichever the last update went to. As far as CWM, I am on 6.0.2.3.
westmenu Marquette
Not sure if this is relevant in all this, but my Titanium Backup wasn't working on it's own either when I flashed any new Rom. It would not see any backups and I would have to go into the Preferences and scan for the folder that had backups in it as it did not automatically detect backups in whatever folder it defaults to. This is also a recent development.
Something Creative said:
Hello,
I having been having some major problems the last 2 weeks with any and all backups i create of my phone. I have tried to make backups of various Roms using both Rom Manager and also directly by flashing into recovery (CWM touch). Each time the backup is successfully made, but then when i try to flash the backup i get errors saying "file not found". I lost my stock rooted backup, a backup of CM10, a backup of Liquid Smooth, and a backup of JellyBam. Does anyone have any idea why my backups don't seem to work? This is incredibly frustrating as I lose all of data and have no security blanket should something go wrong. Every time i flash a new Rom i wipe Dalvik, Cache, and factory reset/wipe.
Anyone have any idea what's going on with the backups?
Click to expand...
Click to collapse
I started several threads on this very issue....my backups also are not working - "file not found" You aren't alone, once more people start experiencing this I'm sure we will see an answer
jackryan57 said:
I started several threads on this very issue....my backups also are not working - "file not found" You aren't alone, once more people start experiencing this I'm sure we will see an answer
Click to expand...
Click to collapse
I've tried searching and nothing relevant came up. Do you also have several folders that appear the same when you reboot into recovery? For example, I have a folder titled "0" that popped up around when the issue started. I have a CWM folder as a subfolder under "0" that appears to be identical to the CWM folder that is not in a subfolder. That's why i brought up the issue i am having with titanium backup, wondering if that has anything to do with anything.
I've tried flashing the backups from both the subfolder and the non-subfolder, and nothing seems to work. The only thing i can successfully do is do a complete wipe and reset and flash a new Rom from scratch off the zip.
If your flashing anything 4.2 related its highly recommended that you use twrp as your recovery because of how the files get condensed into that "0" folder.. Your probably going to have to hunt down your backups I'm sure they are somewhere in that 0 folder
Sent from my SAMSUNG-SGH-I747 using xda premium
psycho2k9 said:
If your flashing anything 4.2 related its highly recommended that you use twrp as your recovery because of how the files get condensed into that "0" folder.. Your probably going to have to hunt down your backups I'm sure they are somewhere in that 0 folder
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I thought it might have to do with the folder issue, but i have tried flashing from the CWM, backup, and various other folders in both the "0" subfolder and the main folder. In both cases i get an error that say's file not found. That said, do you really think twrp would make a difference? I'm pretty new to android, so i'm not really familiar with it beyond knowing it's a recovery like cwm. I'd be willing to try it out if it wont jack up the little amount of cwm i do actually know and am familiar with. At least now i can flash a new Rom and start over with a titanium backup of files if shizz hits the fan.
The only thing I can think of is to copy and paste the clockworkmod folder from the 0 folder to the root folder and try the restore process from the root folder instead of the 0 sub folder. If that doesn't work I dunno bro
Sent from my SAMSUNG-SGH-I747 using xda premium
psycho2k9 said:
The only thing I can think of is to copy and paste the clockworkmod folder from the 0 folder to the root folder and try the restore process from the root folder instead of the 0 sub folder. If that doesn't work I dunno bro
Sent from my SAMSUNG-SGH-I747 using xda premium
Click to expand...
Click to collapse
I'll give it a shot even though I've tried loading from the folder directly already.
How would i move it? I've actually tried using file manager and it doesnt let me. It says it can't move the file, or any file actually, from the "0" subfolder.
so i made some serious progress. I used ES file explorer instead of file explorer and it let me move the file for CWM from the "0" subfolder to the main folder. It said that it was going to overwrite everything in the main folder with the subfolder stuff. I accepted and then i dirty flashed a backup of the same Rom (in case the file would not be found again) that had previously not worked.
It actually ended up working. I am afraid to try to flash a backup after completely wiping b/c i dont want to go through the crap of setting everything up again tonight, but i will give it a go tomorrow and report back. So for some reason, backups can't be flashed from CWM from the "0" subfolder, and they can't be flashed from the main folder, unless you move the files from the "0" subfolder to the main folder.
Hope that makes sense to anyone that may have this problem.
If you have the time and are by a computer you can also just move everything out of the 0 folder into the root folder and just get rid of the 0 folder altogether and start from scratch. I think it has something to do with cwm and how they recognize the file system. Like I said you should give twrp a try its very good.
Sent from my SAMSUNG-SGH-I747 using xda premium