This isn't like some of the other nandroid fail threads i've encountered.
I had a full nandroid backup of my tmobile g2 (eng hboot) and I lost that device. I got an exact replacement, rooted it (no eng hboot), installed rom manager only and flashed clockwork. I then copied my nandroid backup to the clockwork/backups directory and did a restore.
The phone booted successfully with cyanogen 7 nightly 22 flashed but the only problem is that it seems to have done a fresh install...as in there are no apps, no data, just cyanogen 7 nightly 22. It appears it didn't restore anything except the rom itself. Any ideas? thanks in advance.
ps. ive done multiple data wipes, and tried 2 different nandroid backup files on the new phone.
Did you have darktremors a2sd installed on the old ROM? CWM3 seems to have an issue for some with seeing the sd-ext partition and won't back it up. So when you select 'restore' in CWM it *successfully* completes the nandroid restore correct, no errors? It would be odd for it to give you a 'restore complete' message if it ran into any errors.
pretty sure I don't have a2sd installed on the old rom. first time i'm hearing of it. I don't recall getting any errors after restoring the backup but I will try again and double check. I also have much older backups that I can try to restore and see if those go through
Well I think this needs more attention if it's really not restoring the nandroids fully. Seems like it's restoring the system.img and whatnot just not the data.img. Maybe try it with ADB and see if it works. I've never had to do it that way but I know it can be done, you may have to run it in a shell.
I tried restoring a nandroid backup from February, which I believe was backed up with an older version of clockwork, and it was completely successful. This tells me that either the new clockwork is not backing up correctly or it's getting corrupted.
I then tried restoring 3 different backups and they did not give me any errors but failed to restore my data. hmmm
Related
I am getting this error when ever I try to do a nand restore : Error: run ' nandroid-mobile.sh restore ' via adb!
I am running amon ra 1.8, I have the latest sprint lovers installed running 3.70, new radios, pri 1.90. Hboot 79. I've succesfully backed up and restored nands in the past but now I get this error. I've tried to backup and then immediately try to restore the backup and I get the same error so its not a corrupt backup. I have more than 6gb available on my sd card and am fully charged. I've looked in other threads and haven't found an answer. Any help is appreciated since I'm flying without a net when I flash if I can't restore my nand.
Run the command from adb shell, and it'll tell you what's wrong. Duh.
In other words, do what it tells you to do. Is it really so hard to follow instructions?
Hey man had the same problem. I was on miui and I went back to sense to update profile and flashed the new radio combo so I made a nandroid of miui first and then when I tried to restore that same back up I got the same error that you got. I'm not positive but I think that it has something to do with flashing the new radio and then switching to aosp rom. I ended up having to reflash miui and then every thing went back to working normally.
Sent from my PC36100 using XDA App
nandroid won't work if battery is low, I think if it's less than 30% charged, might want to try charging it before restoring to see if it helps...
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Nefariouss said:
I've had this happen with a full battery. The couple of times I had it happen I just wiped cache and dalvik. Rebooted back up, then gone back into recovery and then was able to restore the nand backup. Might give that a shot.
Click to expand...
Click to collapse
I had the same problem and what nefariouss is saying might work. Also, once i wiped several times and then completely turned the phone off and booted back into recovery and then it would restore. Another time i reflashed the rom that i was trying to restore and once it booted i went back to recovery, wiped all and then it would restore. Hope that helps. Just keep messing with it. I know its a pain but eventually it will restore.
Sent from my PC36100 using XDA App
if your sd card didnt partion properly this will happen.
save everything on your sd.
reboot into recovery
repartition sd card.
read that a few people running clockwork recovery have this issue frequently.
Delete Spaces!
If you are trying to flash a file in recovery that has spaces in it, it will not flash and will give you that error. so 'Fresh Evo.zip' won't work, but FreshEvo.zip will work.
FML, ignore this post please. I was a bit stupid.
Sorry for bumping, I have the same problem on my Optimus One p500
Sorry for bumping but I'm really worried about my phone. I have the same problem on my Optimus One and I've tried stuff mentioned above with NO success. Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
antiother said:
.... Is there maybe another way to restore stock Froyo or to get this working?? I'm a total noob by the way..
Click to expand...
Click to collapse
Download and flash this. It is a rooted stock rom (Froyo) that has NOT been deodexed. In other words, it is THE stock HTC sense rom (3.70) that will allow you to maintain root privileges. While in recovery, wipe EVERYTHING in the wipe menu EXCEPT the SD card BEFORE flashing.
posting & replying via the XDA Premium app.
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
wampuscat said:
This happened to me and I tried everything listed. Reformatted my SD card. Copied everything back and nand restore finished first time. Polly unrelated but the only thing different was I had upgraded my RA recovery after I had made the backup.
Click to expand...
Click to collapse
Same thing happened to me after I updated Amon Ra recovery after doing a nandroid backup. Desire wouldn't boot and got stuck on white screen. Tried to do the backup using ADB but each time I got to the last step it failed. So I tried clearing Dalvik cache etc and finally wiped my card using recovery. After a couple of attempts, I was able to restore the last nandroid backup. Big relief.
i need help!!! i have the same problem of the whole error run nandroid-mobile.sh.. via adb. ive scoured the internet and havent solved my problem. i tried doing the cmd prompt thing and i found the latest backup, put into the cmd prompt but this is what i got.
error: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411/nandroid.md5 not found,
nnot verify backup data
/ # /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sdcard/nandroid/mem=477M/BCDEAS-20120130-0411
/sbin/sh: /sdcard/nandroid/mem=477M/BCDEAS-20120130-0411: Permission denied
/ #
and i rebooted and have no idea what to do. someone help. i have the nandroid backup saved to my computer as well in case something like this would happen, and if i could restore, things would be fine!!! i dont understand this, i created a nanroid backup and its not corrupt but i can restore it! wth, im lost and confused and i have lots of data on that nandroid backup. someone please help. i partitioned my sd card and lost everything so all i have is the nandroid backup and my original rom, Cyangon MOD 7 is running right now bc i lost all my data, so im at the beginning. PLEASE HELP!
Delete spaces
I was facing similar problem but thanks to @hecklbrg, It did the trick. Cheers.
Hi,
Made a complete nandroid backup, with all options selected in amon ra 2.2.1. Flashed MIUI to try it out and decided to go back to Myn's.
Upon selecting nandroid restore, I get nothing but the splashscreen and it hangs there. I left it on for over 30 mins in case it was working and I couldn't tell, but unfortunately it just hung.
I had a2sd installed, is it possible that because the ext partition was blown away that this is causing issues ???
Edit: DISREGARD ..... SOLVED ON SECOND NANDROID ATTEMPT
-Protos said:
Hi,
Made a complete nandroid backup, with all options selected in amon ra 2.2.1. Flashed MIUI to try it out and decided to go back to Myn's.
Upon selecting nandroid restore, I get nothing but the splashscreen and it hangs there. I left it on for over 30 mins in case it was working and I couldn't tell, but unfortunately it just hung.
I had a2sd installed, is it possible that because the ext partition was blown away that this is causing issues ???
Edit: DISREGARD ..... SOLVED ON SECOND NANDROID ATTEMPT
Click to expand...
Click to collapse
I had a similar problem only I made a backup on one phone, then when i got a new phone (same 0004 hardware version), I tried restoring the backup and it failed 2 or 3 times. not sure what was going on.
How long would you say it takes to restore the nandroid backup?
I understand you solved the problem, but I wanted to mention this: If you are using ROM Manager it is a good idea to make a CWM backup as well as an Amon RA nandroid. If one doesn't work, the other may! And, if you are not using ROM manager, you might want to think about it. Also, if you are not making multiple backups, you might want to think about that as well.
I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
ChadH42 said:
I know that I have seen this question asked before but I can't find the post. I broke my evo (let's call it #1) and I am trying to restore evo#1 CWM backup onto evo #2 the new phone that I just got. I have put the sdcard from evo#1 with its latest backup into evo#2 and have booted into recovery.
I remember seeing that you can't do a full restore but rather to use Advance Restore but I don't remember which components to restore and which not. I think that I restore all but WIMAX bacause WIMAX is different for each phone.
Anyone know ??
Click to expand...
Click to collapse
Generally, I don't believe it's recommended to restore a backup from one phone to another. However, I've seen reports that it it can be done. As you assumed, you are correct by NOT restoring the wimax. If you were to do that, it would restore the RSA keys of your old phone, overwriting your NEW RSA keys. You don't want to do that. So remove the wimax.img from your nandroid backup before you restore.
Also, I'm not positive on this, but I do believe that if your old backup was made on a certain hboot version, that you need to be on the same hboot version when restoring that backup. (lets say you when you created the backup, your hboot version was 2.10, then when you restore your backup, be sure the hboot version on the new phone is also 2.10). The reason I believe taht to be true, is because I had always had hboot .93 on my phone, and all backups I had ever made were when I was running .93 hboot. I then downgraded to the ENG .76 hboot, (to use fastboot), and I tried to restore a backup that had been created when I was on .93 hboot, and it did not go well. After the backup restored and I rebooted, it booted straight to fastboot, and that was the only place I could get. None of my old backups would restore. I then switched back to hboot .93, and my backups restore perfectly fine. So that is what led me to my conclusion. Good luck with your quest. ( i personally recommend just starting fresh, and not restoring an old backup, just to be safe)
k2buckley got you covered, but restoring a backup from an old phone to a new one WILL cause you problems, and the easiest way to avoid it is to not do it.
The best you can do is backup your apps via titanium backup and your launcher settings, transfer those folders to your new phone. When restoring the apps, do only app and data, NOT system settings.
Thank you both for the reply. Based upon your feedback I decided to do a clean install of everything.
You're welcome; just trying to make it smooth as possible.
I've been running stock rooted MD4 with TWRP 2.5.0 and have done backup and restore several times just to try out new roms. Yesterday I decided to try Hyperdrive, did another backup, and gave it a shot. I decided it was much more than I needed so changed back to stock. I have a total of 3 backups, 2 of which I know are good because I've used them before. Now when I do restore I get "failed" on data restore. I've done the triple wipe of everything and even downgraded TWRP to 2.4.1 to no avail. I can get data to restore by restoring everything else, rebooting, then going back to recovery and restoring data. I'm open to suggestions guys. Am I missing something? Help would be very much appreciated.....
Sent from my SPH-L710 using XDA
I've had this same exact issue...the only way I fixed it was with what you found too, or by flashing the rom, booting up and then back into recovery and restoring data
I honestly have no idea why it does this, everything I've read said that this was an issue on older recovery versions when restoring files bigger than 2 GB,.but that's since been fixed.
BTW: CWM had this issue to for me
Hello!
I'm in a bit of panic. Since Google pushes their stuff over OTA and my custom rom PAC somehow didn't deal with that correctly, it caused to use all my data, so I wanted to give stock 4.3 a try.
Rebooted into CWM, made a backup of my current ROM, free unused backup data, did a factory reset like always and flashed the 4.3 image. Wasn't happy at all with stock 4.3 so I wanted to go back. To my horror, restoring that image failed. Error while restoring /data!. I tried booting up anyway, maybe only a few settings were lost, but it started like the first time I flashed the ROM with the gapps log-in thing and all my apps are gone.
I tried getting back in CWM, manually restored /data, but that didn't work either. It starts restoring /data but then halfway through it stops with the error.
Previous backups (AOKP/CM/PAC) didn't restore /data either.
Installing Nandroid Manager to restore individual apps to a fresh ROM fails too. It sees all apps but it can't restore anything at all.
I have come to the discovery that apps won't even install. Apps manually extracted from the backups are 0kb and I can't seem to install some apps from the Play Store either. Unknown error code during application install: "-24"
Does 4.3 change anything about where the /data partition is? Or what happened?
What's the problem and can I even restore the data? Or do I have to start over?
RainbowSwag said:
Hello!
I'm in a bit of panic. Since Google pushes their stuff over OTA and my custom rom PAC somehow didn't deal with that correctly, it caused to use all my data, so I wanted to give stock 4.3 a try.
Rebooted into CWM, made a backup of my current ROM, free unused backup data, did a factory reset like always and flashed the 4.3 image. Wasn't happy at all with stock 4.3 so I wanted to go back. To my horror, restoring that image failed. Error while restoring /data!. I tried booting up anyway, maybe only a few settings were lost, but it started like the first time I flashed the ROM with the gapps log-in thing and all my apps are gone.
I tried getting back in CWM, manually restored /data, but that didn't work either. It starts restoring /data but then halfway through it stops with the error.
Previous backups (AOKP/CM/PAC) didn't restore /data either.
Installing Nandroid Manager to restore individual apps to a fresh ROM fails too. It sees all apps but it can't restore anything at all.
I have come to the discovery that apps won't even install. Apps manually extracted from the backups are 0kb and I can't seem to install some apps from the Play Store either. Unknown error code during application install: "-24"
Does 4.3 change anything about where the /data partition is? Or what happened?
What's the problem and can I even restore the data? Or do I have to start over?
Click to expand...
Click to collapse
have the same story with galaxy note 2..
Flash backwards first
not an expert here, but isnt the general protocol to try to flash back to the same version of the os first (i.e 4.2.2), and then try the CWM restore?
Are you able to try to track down the same os version you had before?
Have the same issue with my i717
nimbin2k said:
not an expert here, but isnt the general protocol to try to flash back to the same version of the os first (i.e 4.2.2), and then try the CWM restore?
Are you able to try to track down the same os version you had before?
Click to expand...
Click to collapse
I flashed back to 4.2.2 and then tried restore, but no luck. It gave me the same error (Error while restoring /data).