I discovered a little problem when using RA-1.8 Recovery's Nandroid Restore, I've been since it was released but few times when I wanted to do nandroid restore, it reported an error and let me manually do it using ADB, but unfortunately when I did it using ADB, it gave an error saying unable to mount SD card.
I did some search about this problem and there seems no answer.
Later I discovered, just fastboot flash recovery again, and nandroid restore will work fine.
Don't know what is cause of this problem...
if your battery is under 40% it would not let you nan restore
Sent from my Nexus One
I didn't notice that limitation..
Yesterday in morning my battery had 9% left and I did nandroid backup.
Then immediately tried nandroid restore, reported error.
Then I plugged usb cable in, fastboot flash recovery and then unplug cable, nandroid restore completed successfully..
Related
Im running fresh 0.5.3 and have the latest amon recovery, i can do a ext+nandroid backup fine but when i try to restore after i reboot, it gets hung on the
htc screen and will not load. Ive tried several backups and it will not work when restoring. Any ideas?
Make sure you're wiping the data, cache and dalvic before restoring the backup.
Are you sure the backup is getting created?
I know SteelH was posting yesterday about the NAND + EXT backup not even working with amon recovery.
I personally don't even know what it does, but all my backups are just "NAND backups and seem to work fine.
I'm assuming you used Amon_ra to create the backup and you're using Amon_ra to restore?
I created a backup with amon_ra and tried to restore with Clockworkmod and the backup doesn't even show up and vice versa. I found out by trial and error that backups created by clockworkmod have to be restore with clockworkmod and backups created by amon_ra have to be restored with amon_ra.
I don't know if that's the case for everyone, but it sure is for me. I'm running whitslack's 1.47 and Evolution V9.
Back to the Nand+Ext, maybe SteelH has figured it out, maybe send him a pm or search for his posts in the Q&A forum from yesterday.
make sure your batt has enough power
I am fully charged when i nandroid. It creates the backup and restores it but when i reboot it freezes on the htc screen. So this is a bug with the amon recovery image then? It would be nice to be able to backup & restore my ext apps because i use apps2sd. I could use titanium backup but nandroid is faster.
So I decided to try and flash Ubuntu last night... I booted into recovery made a backup 15min and 2.5 GB later it was done... wiped flashed no go would not boot... so back to recovery I choose my restore file... system says it was successful but when restoring the data it fails... I'm on twrp 2.5 ...then I tried to just restore the system when booting up I get that static image you see on cm flash every 5 sec but never boot nor goes inyo the boot animation...is there anyway to use this restore file... I just need the data part.. I have messages that i need to show my lawyer and numbers that I need... TiB won't restore my messages either....
Sent from my XT907 using xda app-developers app
You will need TWRP 2.6.3 / PhilZ / or a newer CWM that supports adb in recovery (not sure is 2.5 does)
First off, all of your pictures and other stuff are stored at "/data/media" or "/data/media/0" and are not "wiped" unless picked. These are both accessible in recovery, and you could do an "adb pull ....." to get those files to a PC. At this point you should have your pictures.
Sounds like Ubuntu messed some things up, and when you restored "/system" only it won't boot because of missing data. I once had a problem like this bouncing back and forth between 4.3 and 4.2. Assuming you were on a custom ROM, maybe try wiping completely including "/data/media" DO NOT WIPE "/DATA/MEDIA" IF YOU HAVEN"T BEEN ABLE TO PULL THE FILES VIA ADB IN RECOVERY!!! YOUR PHOTOS WILL BE GONE!!! Sorry for the bold caps, I just didn't want you to miss it. Next install your custom ROM, boot, and do enough setup to get to the home screen. Now go back to recovery and your backup should restore. From here you could "adb push ..." your files back.
Updating TWRP is one way to solve this in the future, like JB already posted. However, to remedy on 2.5, do a clean wipe prior to restore, mounting system prior. Then, restore only the boot.img from the ROM you want and then restore the full ROM you want. This is how I was able resolve this same issue. Hopefully, it will work for you.
I was on stock deodexed debloated prior to all this... after a few tries at the restore I just flashed that same ROM and used TiB to restore what I had on last back up... tonight I'll try and restore that twrp backup ... but either way I guess I'll be updating my recovery... I'm not worried about all my pics n what not I keep all that on the external SD card now...
Sent from my XT907 using xda app-developers app
I used to backup/restore without any problems using CMW Recovery v6.0.3.2. I had to retry flashing the last Omega Rom a few times because it wouldn't boot, but at last it worked after the factory wipe. Now I can't restore previous backups as it says simply "Error while flashing boot image!". I know I cans till recover the system+data, but I'd like to be able to restore boot as well.
What can I do to fix this? Is it a wrong/corrupt partition table?
Thanks
My Nexsus 4 was at 5.0.1 updated OTA, I rooted and installed recovery and created a nandriod backup on the internal SD card. The phone was working fine for the most part except it was having issues with the screen going black when making a call and would not come out of that state. I wanted to revert back prior backup so I did a nandriod restore with CWM v6.0.4.7 and now my phone is in a bootloop. I've tried wipe data/factory reset, also tried wipe cache partition, but still stuck in bootloop. I'm not sure what else I can do to get out of this bootloop state/ Any suggestions would be greatly appreciated.
Fixed it by using Nexus Root Tool Kit to flash stock image. Not sure what happened but I'm switching to TWRP. First time using CWM and things didn't work out well for me using it.
Long story short, I tried to install MultiROM on my Nexus 6P, and it failed. So I tried to restore my backup using TWRP 3.0.2.0, and it keeps failing at exactly 7800MB with the error E:extractTarFork() process ended with ERROR=255. I have seen posts talking about checking the log when this happens, but I'm not sure exactly how to do that.
What exactly do I need to do to restore my backup?
I guess I should add some detail. I first tried booting to recovery and restoring the backup. The phone rebooted into a boot loop part of the way through the restore process every time I tried that. Then, I tried flashing the phone completely back to the stock image, and then restoring. I got the error 255 above. Then, I tried flashing back to stock completely, wiping Dalvik/cache, and restoring the backup. I still get the same error message. I tried restoring everything except userdata, and the phone reboots part of the way through the restore.
I could easily reroot, reinstall Xposed, and reflash TWRP if for some reason my system backup partition is corrupted. However, I don't want to lose my data partition at all. That was the whole reason I made the backup in the first place.