I have successfully used Nandroid to backup my phone. I wanted to know if it was possible to extracts the files and data out of the data.img that Nandroid gives? I read about the unyaffs tool, but was not able to get it working when I gave it data.img. Is this possible with unyaffs or any other method? Thanks.
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
Original:
Thank you Mikey1022 for a nice warm threat of banning me for my first post ever. Really makes a newcomer feel welcome around here. My bad for thinking something to do with CyanogenMod and Nandroid was development-related.
Anyway, as was said in my thread that was locked:
The last few times I've updated to a new CM ROM, my phone boots to the android screen, goes black, stays there indefinitely. Have to pull battery.
OF COURSE I always do a Nandroid backup before flashing a new ROM. So I think "well, I'll just revert to my backup." Right?!? No. Whenever I try to restore a Nandroid backup, I get "Error performing restore! Try running nandroid-mobile.sh restore from shell". When I run said command in adb, it tells me:
Verifying backup images...
boot.img: OK
cache.img: FAILED
data.img: FAILED
misc.img: OK
recovery.img: OK
system.img: OK
md5sum: WARNING: 2 of 6 computed checksums did NOT match
Error: md5sum mismatch, aborting
How does my cache and data images "fail?"
So I end up wiping, then re-flashing the CM update, and all is well. Except I have a wiped phone, with none of my apps or settings. I know, I know, I should wipe anyway, right? Bull****. I spend a lot of time customizing my phone, getting it just the way I like. I have tons of apps installed, set up how I like. To wipe every two weeks when CM releases a new update is absurd. I don't have to wipe my computer every time Microsoft issues a security update.
So my two questions are: Many other people report flashing the new CM ROMS without having to wipe, so why doesn't it work for me?
And why can't I restore a friggin Nandroid backup? Really, what is the point of making a backup if there's no way to restore it?
Notes: I have a brown T-mo G1 unlocked on AT&T. I just did this whole process today going from CM 4.2.3.1 to CM 4.2.4. I have CM's Recovery 1.4 installed. I have a 2GB SD card formatted as ~1.4GB fat32, ~500MB ext4, 64MB linux-swap. And I have an anxiety problem. I'm eating Xanax like candy.
I am completely with you that it is inconvenient to wipe and flash and have to put all your settings back together. I've also been lurking for a little while and learned that most people are dickbags about posting in the right forum, rather than just helping someone out. Don't take it personally.
The best thing I have found to do is get Backup for Root. I'd recommend MyBackup Pro as well, to be safe. Backup with both before wiping and flashing a new rom, and usually Backup for Root will restore your desktop and settings. Reboot a couple times if things don't come back instantly.
If I were you, I would just take some time out, copy the files on the SD to a hard drive, reformat the card, wipe the device, and reload everything fresh. But that's just me. Good luck
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
B-man007 said:
You can flash the restore through fastboot....
take the data.img and
fastboot flash userdata data.img
though if the md5 is messed up...its probably not a good idea, though at the worst you can wipe
Click to expand...
Click to collapse
What he said. Put all your .img files in the tools of the sdk. In order, the fastboot commands would be:
fastboot flash boot boot.img
fastboot flash userdata data.img
fastboot flash recovery recovery.img
fastboot flash system system.img
Click to expand...
Click to collapse
Cache and misc don't really matter that much. This will manually restore your nandroid backup.
Thank you very much, FaJu. That is exactly what I needed to know. I will try that next time if I can't get Nandroid to restore.
I also started backing up with Backup for Root, as drspanklebum suggested, so hopefully one way or another I'll make damn sure I can restore my apps and settings if need be!
UPDATE: I've discovered all of my problems seemed to be due to a FUBAR SD card. I wiped, went back to factory, did the stock-to-CM process all over again. Phone STILL either wouldn't boot or would boot but nothing would work with my 2GB card in it. So I formatted a 1GB card I had laying around with 32MB swap, 200MB ext4, and about ~770MB fat32.
Phone now works better than it ever has on any firmware since the day I bought it! It's a lot faster than it's ever been, too. This also explains why I couldn't restore my Nandroid backups. Nandroid and Backup for Root both work great now (and are lifesavers!).
I no longer have any complaints about CM!
If I have to switch file systems but I don't wanna lose data will recovering backups restore the filesystem of the backup too?
-sandro- said:
If I have to switch file systems but I don't wanna lose data will recovering backups restore the filesystem of the backup too?
Click to expand...
Click to collapse
In theory the latest CWM (5.0.2.0 as of this moment) should be able to restore the filesystem as well as the data. In practice however this doesn't work yet. (At least not for me if trying to restore an ext3-backup on an ext4-phone.)
That's not really a concern though, because you can revert from ext4 to ext3 by running/installing "r1_backtoext3-2x-unsigned.zip" (search for it) before restoring the backup, or install another .zip which will convert ext3 to ext4 without data-loss if going the other way. (Cannot remember the filename right now, never used it myself.) I think Rusty packaged that one.
CMW can backup the whole rom /system included. I always change into CM7 and the Leaked GB via the backup/restore.
Hello,
I'm using CM7 and i want to make a nandroid backup of the ROM but for the first time it's not working. It doesn't give an error message but in the end I get data.ext4 and system.ext4 of 0KB :| I'm suing CWM 6
Solution was to change backup format to tar
Something on my phone got screwed up and i'm glad i made a nandroid with safestrap a couple of weeks ago. Now I'm wondering if its possible to some how create auto nandroid backups? I have titanium backup auto-run everyday but a having a up-to-date nandroid would be good too.
thanks
It might be possible to write a script that nightly reboots into recovery and starts a nandroid backup process. But I'm unsure if it would reboot after that automatically.
I just boot to SS any time I make any major change and make a new backup. Only takes a few seconds of my time (and a few minutes of the phone's time).