Back up missing MD5 file - Verizon Droid Incredible 2

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.

Related

[Q] My recent Nandroid issues - any thoughts ?

Hi,
I recently decided to install the N1 partition table, it ended up going very smoothly apart from being able to restore the most recent nandroid backup, MD5 error (or words to that effect).
Not worying too much I just reinstalled CM6.1 from scratch, again all went smoothly.
I then did a nandroid backup and then rebooted then restored the nandroid backup, everything worked perfectly.
I then installed a cooked zip file from http://circle.glx.nl/.
That failed to boot after installing, no prob I thought, just recover from the nandroid backup.
I got another MD5 error from the one that I previously restored from.
So another reinstall, nandroid backup and recovery later it's all ok again.
Unfortunately I'm losing confidence in nandroid now.
Any thoughts ??
Colin
Md5 is a checksum, it makes sure the images your trying to restore are the same as when backed up! Maybe theres a problem with your recovery, flash it again from fastboot, only takes a second
Sent from my HTC Desire using Tapatalk
Aye I know what MD5 is, I just couldn't remember the exact words when the MD5 check failed.
The thing is though that I'd already tested the nandroid image by recovering it, all OK. Then made a change to the ROM tried to restore the same (previously working nandroid backup) which failed with the checksum error.
gol_n_dal said:
Aye I know what MD5 is, I just couldn't remember the exact words when the MD5 check failed.
The thing is though that I'd already tested the nandroid image by recovering it, all OK. Then made a change to the ROM tried to restore the same (previously working nandroid backup) which failed with the checksum error.
Click to expand...
Click to collapse
It can also happen of your Sdcard is failing and the files on it are getting corrupted. Since MD5 is a checksum, a change in even a few bytes could cause issues
I too have faced MD5 checksum issues.
1.copy the files to the sd card via the phone mounted as Disk drive mode
2.Safe remove the device from windows
3.Once you unplug, the device will shortly show "Preparing SD card" in the notification bar. Wait for a full minute
4.Switch off device to boot in recovery.
For me, if i dont wait a minute after unplugging the device, clockworkmod will report the files as corrupt. Maybe the device is updating the inode tables and switching the device off immediately after copying and unplugging causes it to corrupt filesystem tables.

nandroid img files restore question

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.

[Q] Really bad problem with CWM :(

I've made two backups on ClockworkMod, yet EVERY time I try to reinstall data, it restarts midway, and when I start my phone up the bootanimation becomes an flashing android logo, what am I doing wrong? Please help!
kamranh3 said:
I've made two backups on ClockworkMod, yet EVERY time I try to reinstall data, it restarts midway, and when I start my phone up the bootanimation becomes an flashing android logo, what am I doing wrong? Please help!
Click to expand...
Click to collapse
Hmm..that's a strange problem.
Did you try to reinstall the CWM??
Edit: I pushed the Thanks Button unfortunately -.-
Every little helps
And I've tried, no such luck, so I'll try an older version and see what happens
EDIT: There's a thanks back!
Okay I've tried a different recovery, no luck
What have I done wrong? I seem unable to make any recovery.
I think the problem may have originated when I installed CWM 3.0.0.5, everything was fine before that
This is just a long shot, but have you tried checking your SD card for errors from your PC? The backup file could be corrupted, and that might fix it.
It would probably be a good idea to copy the /clockworkmod/backup folder from your SD card to your PC before you run the check. If it doesn't help or makes matters worse, you can copy it back.
Also, which version of CWM did you use to make the backup?
preacher65 said:
This is just a long shot, but have you tried checking your SD card for errors from your PC? The backup file could be corrupted, and that might fix it.
It would probably be a good idea to copy the /clockworkmod/backup folder from your SD card to your PC before you run the check. If it doesn't help or makes matters worse, you can copy it back.
Also, which version of CWM did you use to make the backup?
Click to expand...
Click to collapse
I used 2.5.1.3 in both cases, went down to 2.5.1.2 to see if it was linked to the recovery itself, it wasn't
kamranh3 said:
I used 2.5.1.3 in both cases, went down to 2.5.1.2 to see if it was linked to the recovery itself, it wasn't
Click to expand...
Click to collapse
If you look in the /clockworkmod/backups folder on your card, in the folder for the relevant backups, what size is the data.img file? Have you got any earlier working backups you can compare it to? I'm wondering if the backup failed part way through.
I take it you're trying to restore data only using Advanced Restore?
I can't think what else could cause it apart from a damaged sd card or corrupt file, but I'm not a CWM expert.
preacher65 said:
If you look in the /clockworkmod/backups folder on your card, in the folder for the relevant backups, what size is the data.img file? Have you got any earlier working backups you can compare it to? I'm wondering if the backup failed part way through.
I take it you're trying to restore data only using Advanced Restore?
I can't think what else could cause it apart from a damaged sd card or corrupt file, but I'm not a CWM expert.
Click to expand...
Click to collapse
I have looked at the backup is around 1.11GB which is the expected file size, the data.img being around 730mb, it's done this twice, and I've always checked that I've had plenty of space before attempting nandroid, and nothing's ever happened to the sd, i've never moved it or anything
kamranh3 said:
I have looked at the backup is around 1.11GB which is the expected file size, the data.img being around 730mb, it's done this twice, and I've always checked that I've had plenty of space before attempting nandroid, and nothing's ever happened to the sd, i've never moved it or anything
Click to expand...
Click to collapse
I'm not sure what else to suggest besides checking the sd card for errors. There have been some bugs with the HTC 1.72 stock ROM, which affect all custom ROMs based on it, that occasionally cause sd card errors. This is most likely to happen if you connect to your PC with a USB cable, mount the SD card as a drive in your PC, and disconnect the cable without using "eject" in Windows. It might happen at other times as well, I'm not certain.
This is usually fixed by checking the card for errors through your PC. Some people recommend defrag'ing the card, but I think a check for errors should be all that's needed. I'd copy all contents of the card to a folder on your PC first, just so you have a backup.
Otherwise I've run out of ideas, sorry. Hope you get it working.
What I'll do is transfer my backup to my brother's SD card, and then attempting a nandroid then, if that doesn't work then I don't know what will, but I'm 99% sure it's probably due to a problem on my SD card.
Sent from my Desire HD using XDA App
Hope it works, let us know how you get on.
preacher65 said:
Hope it works, let us know how you get on.
Click to expand...
Click to collapse
Well it doesn't seem like option, brother's too stubborn, so I guess I'll have to stick with what I got for now until I can fix this problem, it's really bugging me
kamranh3 said:
Well it doesn't seem like option, brother's too stubborn, so I guess I'll have to stick with what I got for now until I can fix this problem, it's really bugging me
Click to expand...
Click to collapse
You didn't say whether you tried checking the card for errors from your PC, did you try that yet?
CWM created an MD5 checksum for the backup, so it's not very probable r/w errors are the cause of the problem. If the data was corrupted CWM would notice before attempting to restore the data.
But if in doubt you can verify the checksums manually. In the backup directory there's a file called nandroid.md5 it's a text file that contains the hashes for each backup file. Compare those values to the actual checksums. If you need a tool use Hash My Files.
CWM 3 backups aren't backward compatible with CWM 2? Then you could try restoring with CWM 2 and see if that works. Then you'd at least know if it's you phone or a software problem.
This may sound silly but did you upgrade clockwork to 3.0.0.6?
equlizer said:
This may sound silly but did you upgrade clockwork to 3.0.0.6?
Click to expand...
Click to collapse
I tried upgrading to see if it would solve the issue, it didn't.
And as for md5 checksums, it all checks out fine, everything starts to restore fine, and on two of the latest occasions it will not fully restore data, but will restart CWM between restoring. I really don't know what the cause is :/

[SOLVED] Restoring nandroid.md5

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

Can't get any backups to work

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

Categories

Resources