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.
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
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.
I'm curious about this. Maybe someone can enlighten me.
Lets say that I'm on stock 2.2, rooted. I do a nandroid backup. Then I allow the upgrade for 2.2.2. Of course I lose root.
Will a nandroid restore, restore root, or will I have to root again?
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
maltloaf said:
A full nandroid restore will restore everything - the system and data - and you will be right back where you were, on 2.2 and rooted.
Click to expand...
Click to collapse
Ahh, okay.
So to confirm that I understand you correctly...
...the 2.2.2 update won't hold after the nandroid restore? I'll be back to 2.2, as it was before the (2.2.2) update?
If you just wanna backup and restore your apps, use Titanium Backup (it's free on the Market).
Nandroid backs up your entire phone. When you restore a nandroid backup your phone will be exactly like it was when you made the backup. Restoring a nandroid backup is used to recover from a crash or to revert to a previous ROM.
After a ROM change I will set up my accounts, root if needed and do any other basic setup stuff and then, before installing any apps, do a nandroid backup. I can then go back to a "fresh install" if I want to. I also do a nandroid each weekly to capture the state of my phone.
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
I have not tried backing up my apps to Google, which you can do in later versions of Android. Go to Privacy in the setting menu and then to Backup and restore. There are boxes for data backup and automatic restore you can check. maybe someone who has used this can comment on how well it works.
If your nandroid backups hang up at "backing up firstboot" get the latest version of StreakMod Recovery.
marvin02 said:
Backing up apps and restoring them across different ROMs may or may not work for you. When I have tried this with Titanium Backup I had many force closes and ended up reinstalling everything from the market. Others have had success. I have read the MyBackup pro does better, but most suggest that you just backup and restore data not the app itself.
Click to expand...
Click to collapse
After installing a fresh ROM and rooting my device, the first thing I do is install Busybox. Then, with Titanium Backup I do Restore Apps Only, then reboot my device. I never get any FC's with this restore process.
Thanks!
Thank you everyone. I appreciate the info.
I've used Titanium BU, and have busybox installed too.
It was just a matter of if after an update (OTA), and restore with Nandroid, would root still be in place.
I totally understand what you guys are saying now.
I've also been using MyBackup to see how it compares to Titanium. So far so good.
~X
I prefer mybackup root to titanium. It's far more user friendly and more automated (in the free version). As for nandroids, I always take a backup before doing any system changes (hacks or rom updates) so I can roll back to a known good system if needs be.
BTW - it is a good idea to copy your ROM backups to another device, just in case your SD card dies. I copy mine to one of my desktop computers and to a USB drive. I usually back up my entire SD card, except my music folders, every couple of weeks.
Where does Nandroid put the backups so I can rename them and save off phone?
mine (from Streakmod recovery) are in /sdcard/rom_backup
StreakMod recovery puts the backups on the SD Card in a folder named rom_backup.
Each backup is in a sub-folder of it's own and uses a date-time format for the folder name. I rename the folders with a meaningful name by just pre-pending to the name. So my last backup is named BB351-2011-06-18-02.41.04. The following files are created:
.android_secure.img
boot.img
cache.img
data.img
firstboot.img
recovery.img
system.img
nandroid.md5
the md5 file is a text file that contains the md5 sums for the other files. This file is used to verify the other files when they are restored.
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!
Hi all, first of all, I apologize if I've posted in the wrong place.
I was never an "expert" with Android but I have used the EVO 4G for the past two years and just upgraded to the Galaxy S3. I rooted it this morning and have been playing with it. I wanted to flash different ROMs and try them out but I ran into some problems when trying to create a nandroid backup.
First I tried the usual method via ROM Manager. When I rebooted into Recovery, instead of backing up it just loaded the main CWM screen and at the bottom a message said it wasn't able to load the ROM Manager script and to make sure I have ROM Manager 4.4.0.0 or above (which I do). Then I tried to make a backup from CWM itself and after it was done, the date was all messed up as it thought it was 1970. Also when I booted back and loaded ROM Manager, it wasn't able to see the backup I made. I did try to make a backup in both my internal and external SD Card but didn't make a difference.
Please advise, thanks!
Don't use ROM Manager, no real need to use it for backups. Boot into recovery and manually backup (like you did). The date issue is a known CWM issue and will be resolved by them sometime soon I'm sure. The backup you did should be fine. I've backed up a few times (with the same date issue), but never tried restoring yet. Net Net, when you ran the backup manually (even with the borked date) you are good.
PS. I only use ROM Manager to rename the backups, as if I tried to manually change the name via a file explorer the file became invalid. If I changed the name via ROM Manager the backup was perfect.
I have also had issues with creating a nandroid. I have the verizon version so it probably has to do with it.
I have v 5.8.4.8 and installed it through ROM Manager.
I tried a nandroid and it errored with
Error while backing up boot image.
I'm guessing that it is known and has to do with the locked bootloader. But was just seeing if I anyone else had the issue.
johnhazelwood said:
Don't use ROM Manager, no real need to use it for backups. Boot into recovery and manually backup (like you did). The date issue is a known CWM issue and will be resolved by them sometime soon I'm sure. The backup you did should be fine. I've backed up a few times (with the same date issue), but never tried restoring yet. Net Net, when you ran the backup manually (even with the borked date) you are good.
PS. I only use ROM Manager to rename the backups, as if I tried to manually change the name via a file explorer the file became invalid. If I changed the name via ROM Manager the backup was perfect.
Click to expand...
Click to collapse
I used to use ROM Manager to backup before mostly because as you have stated I could name the backup
Thanks for letting me know that even though the date is broke it's still good. I get a bit cautious when it comes to backing up