So last night, I copied a nandroid I had previously made from my computer onto my phone. When I tried to restore it, it aborted b/c the md5 sum didn't match. Strange. So I copied a different nandroid onto the phone, tried to restore that one, same thing- md5 mismatch.
What's going on there? Is the file being corrupted during the move to/from the phone? That seems like it'll make storing your old backups on your computer kind of useless.
STaria said:
So last night, I copied a nandroid I had previously made from my computer onto my phone. When I tried to restore it, it aborted b/c the md5 sum didn't match. Strange. So I copied a different nandroid onto the phone, tried to restore that one, same thing- md5 mismatch.
What's going on there? Is the file being corrupted during the move to/from the phone? That seems like it'll make storing your old backups on your computer kind of useless.
Click to expand...
Click to collapse
Make a new nandroid and immediately restore it. If it works move it to your computer and then back to your sd and attempt another restore to see if you get the same problem with a nandroid you KNOW was good before you moved it.
EDIT: you didn't still have your phone plugged to the computer when you tried to do the restore did you? If so try restoring it again unplugged. Its known to cause issues.
Sent from my cm7 Aria.
Yea I did end up doing that, I immediately restored the backup, it worked, so I went ahead and flashed a new ROM. When it came time to restore, it said something along the lines of "error writing boot image" and failed.
I ended up just using Titanium to restore everything, but it's worrying that my stored backups might not work.
EDIT: Oh, having it plugged in may have been the issue... I'll keep that in mind.
Did you rename the folder that the backup img files are in? They aren't supposed to be changed (i.e., "2010-11-27.21.30.28").
drumist said:
Did you rename the folder that the backup img files are in? They aren't supposed to be changed (i.e., "2010-11-27.21.30.28").
Click to expand...
Click to collapse
Nope, didn't touch them. Just copied to and from the computer.
Related
Just put my old SD into a new Eris and I'm trying to nandroid (I've rooted)
error: run 'nandroid-mobile.sh restore' via adb !
is the error I get.
Can someone help? I've tried a lot of things. The phone's fully charged and plugged in.
EDIT: I fixed this by deleting my nandroid folder after backing up my backups, doing a nandroid backup, deleting that backup, putting my old backup there and then restoring.
Thanks anyway.
I just tried to do this as well. Same thing happened to me. I'm guessing the backups are only good for the specific phone they were backed up on. If anyone knows a way around this, could you share? I have a few backups from my old phone and would hate to have to start over.
read the Edit: portion of the OP above
I've had this happen a couple times. Usually, I get it when the battery is low. Perhaps an internal protection? The other times, for some reason it won't create an MD5 file. The only way around that is to manually create one. I'm not sure what caused the initial problem here, but it's nice to see you got it fixed.
To clear this up, this can happen when the battery is low or possibly when trying to nand on a new phone/ newly flashed recovery.
I solved it by
-- saving everything inside the nand folder I wanted to restore.
-- Deleting the nandroid folder from my sd card
-- Booting into recovery and doing a nandroid backup
-- Deleting the contents of that nandroid backup and replacing them with my nandroid from the first step
Alright, so I have rooted my Captivate, and brought it up to 2.2 (no thanks to AT&T). My issues are the following. Before I started messing with the operating system at all, I did a full Nandroid backup. My special situation is that I had contacts not associated with my Gmail account, and not synched to my SIM card, because it was full. These contacts should be backed up with the nandroid backup, but is there a way to simply extract them and put them on my computer, or have them back on my phone, without overwriting all of the data on my phone again? I'm a little bit desperate, and haven't been able to figure this out. Thanks so much for any help.
Edit: Just to make things a little clearer, here's what specifically I'm looking to do. I would like to be able to take the data.img file, and extract the contacts from it to my computer. Also, is it possible in Nandroid to restore just the contacts to the phone?
Have you tried exporting your contacts to a vcard in the phone's settings? this would save a .vcf file to your phone's sd card, which you can then e-mail or send to your pc.
contacts > menu > Import/Export > Export to SD card
Vcard
Well, because I already made the software changes and went to 2.2, the contacts arent currently loaded, but instead stored in the Nandroid backup. Is it possible to do this with just my nandroid files?
I see. I'm not sure how you can do that. Do you have the nandroid backup on your pc? Can you try running it on an old android phone?
Unfortunately, I do not have an older android device to load this up with. Anyone have a suggestion for how I might be able to open up the data file and extract some of the information? I do have the nandroid folder with all of the parts of the backup on my windows machine.
i am actually trying to do the very same thing. its hard because i cant just restore the nandroid backup because the kernels do not match up and i have been having a hell of a time getting back to a 2.1 kernel and restoring. it keeps boot looping.
i am trying to track down where in nandroid the contacts are stored because you can do an advanced restore and choose from specific directories so it might work. but can not find it so far. good luck, ill be following this thread so if you figure it out, let us know.
Well I have a fascinate, so I cant give you specific files to use etc, but I have no problem flashing 2.1 .tar through odin while I am on 2.2
For example, if I run into a problem on an eb01(2.2) ROM, I can just odin my trusty dl09(2.1) .tar and I am back to stock, bloated dl09 kernel/baseband/rom. Perhaps you can look in your specific device forum for an equivalent odin image?
I do not know how the nandroid backup is built, but would it be possible to burn the image to an SD card and take the files off of there? Or maybe using WINRAR to extract the files? The problem is, again, I do not know how it is made. I will try this as soon as I can get to my computer.
Sent from my SAMSUNG-SGH-I897 using XDA App
so what i ended up doing to get this to work was flashing JI6 in odin and then restoring nandroid.
Well, I dont know where these backups are going, after backing up, if i go in nand manager, I see the file, but when clicked to explore, says this type file cannot be opened.
online nand says backup was successful, but there is nothing in the file. And it shows it as file size: 4kb.
cm 10.1RC4 captivate.
I'm on stock 2.1 with 2.1.1.A.0.6. and my phone's rooted. And I have never been able to use CWM to restore any backups.
Everytime I try, I'm told there's a MD5 sum mismatch. Even if I've made the backup a few seconds before and I'm still in CWM. I've gone into the backups and changed the checksums in nandroid.md5 with the correct ones (or at least I assume they're the correct ones, I use ES File Explorer to generate them). CWM then restores it..but I get thrown into a boot loop when I start the phone.
I do a lot of fiddling to get my phone just the way I want it and every time anything goes wrong (like a ROM not installing properly), I have to reflash the whole thing, re-root it, re-install my app's, re-remove the bloatware, re-set my settings, re-do my widgets, blah-blah-blah..
Anybody any idea what's going on? I'm using ClockworkMod v3.2.0.0-r5.
when you create a backup using clockworkmod NEVER rename the folder its saved all your backup, if you do then that will cause the MD5 to be invalid,
if thats not the issue then try downloading ROM manager from android market and use this app to backup and restore your .img files
Well, I don't rename the folder, I don't rename anything. I think I'm not wiping the right things first. At least, I hope it's something that simple. I'd hate to be the one poor soul on here whose phone doesn't like doing backups..
ROM Manager sounds like the sort of thing I need though, even if I do get CWM working properly.
Many thanks!
I'm running various ICS/CM9 ROMs, and have noticed a pretty consistent problem.
When I perform a backup through recovery, everything goes fine and the last stage creates the MD5 and says backup completed successfully.
I store my backups (based on the ROM) in their own respective folders on my external MicroSD.
I can almost guarantee that 80% of the time when I try to run a restore, I am informed that the MD5 is mismatched and of course the restore operation fails.
I've checked the integrity of my MicroSD, and it's rock solid. Every other file (including ROM installation files and APK's) install flawlessly time and time again - no issues whatsoever.
Can anyone offer guidance? Should I run restore through ROM Manager instead, is CWM recovery not good for backups?
Thanks.
Try making a nandroid, don't move/rename the folder, and then try to restore the nandroid and see if you get the same error.
Sent from my Sensation using Tapatalk 2
Ya like he said. Make sure no spaces in your renamed files either.
Another thing is to maybe restore the nandroid using the same kernel that it was created with. A while ago in ICS infancy there was a kernel problem with FIOPs that was preventing restores.
Also check to see if your nandroid has a boot.img in it. Might be causing some issues but maybe not.
So I ended up smoking my old phone the other day when using it as a signal generator to test some amps on the bench. The battery was getting low so i plugged the charger into the laptop that I also had the osilliscope plugged into. - bad idea. ground loop fry.
Anyways i have my new phone here, rooted with TWRP installed. Stock kit kat via .kdz.
The problem I am having is the phone will not allow me to choose the backup I have of my old phone.
Just for curiosity I made a fresh backup of the other halfs phone, loaded it to the SD card and I get the same results.
It seems TWRP will not restore any backups unless it was a backup of that particular phone. Iv never had this issue before, I have to be doing something wrong.
I made a backup of the stock OS, then flashed a MM rom to it, got everything working and backed that up also.
Both the backups I made I can choose to restore. I notice each phone will make a new folder on the sd. So i moved the other backups to the folder that was made for this phone, but no luck there.
Any ideas WTF is going on anybody?
No idea. The only thing I was going to say - moving the old backups to where the new ones are, is the only thing I've ever had to do.
larski156 said:
So I ended up smoking my old phone the other day when using it as a signal generator to test some amps on the bench. The battery was getting low so i plugged the charger into the laptop that I also had the osilliscope plugged into. - bad idea. ground loop fry.
Anyways i have my new phone here, rooted with TWRP installed. Stock kit kat via .kdz.
The problem I am having is the phone will not allow me to choose the backup I have of my old phone.
Just for curiosity I made a fresh backup of the other halfs phone, loaded it to the SD card and I get the same results.
It seems TWRP will not restore any backups unless it was a backup of that particular phone. Iv never had this issue before, I have to be doing something wrong.
I made a backup of the stock OS, then flashed a MM rom to it, got everything working and backed that up also.
Both the backups I made I can choose to restore. I notice each phone will make a new folder on the sd. So i moved the other backups to the folder that was made for this phone, but no luck there.
Any ideas WTF is going on anybody?
Click to expand...
Click to collapse
Look in the TWRP/Backups folder for your new backup. It should say VS985 then some numbers. Copy this folder name to the backup that you're trying to restore then TWRP should find it.