Develop Bugs

[Q] Error: run ' nandroid-mobile.sh restore ' via adb!

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.

Data fail on restore....

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

[Q] TWRP help

The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.

Not much help here, and at the risk of sounding like a Negative Nelly, I gave up on image-based backups several devices ago. The only device that I could get reliable nandroids was my HTC EVO 4G running AmonRA recovery. Since then, I've owned/rooted 4 or 5 other Android devices, and every single one of them have been completely unreliable with nandroid restores to the point that I just gave up, use Titanium Backup, and then just flash the ROM again. That's been with CWM and TWRP, all versions (and I've probably tried them all) on all of my devices.
I would love it if someone could enlighten the both of us on how to be successful with nandroid backups/restores. Again, sorry I'm not of much help, but consider me a confirmation of what you're encountering (a "yeah, what he said").

dante32278 said:
The other day I was restoring a backup in TWRP 2.6.0 on my Sprint Galaxy S3. The ROM I was on was AOSP based and the one I was restoring was AOSP based. During the restore, the phone rebooted during the data restore and then started a boot loop on the device, where it appeared I was starting TWRP again, only to have the device reboot at the TWRP splash screen.
I eventually finagled the device into getting TWRP to load by starting DL mode and then booting into recovery where I proceeded to do a full wipe and install a ROM from fresh. Anyone know why this would occur? It was very scary to think I was about to brick my device over something as simple as restoring what was a successful backup. I have not tried to restore any backups since out of fear of this issue occurring again. I also read on the TWRP page about a defect of reboot during restores if not enough data is available, but I have plenty of storage room available on my internal (26.26) and external (29.93) SD cards.
Click to expand...
Click to collapse
What I have found out the hard way is that every device is different. Some prefer CWM Recovery, some TWRP Recovery. If TWRP is not working for you, try CWM. A stable Custom Recovery is a must have.
TEAM MiK
MikROMs Since 3/13/11

[Q] Can't restore /data after 4.3 update

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).

twrp consistently crashes while restoring backups

I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
I will be travelling and i wont have access to odin for a little while, so i'm less inclined to go breaking things till i get back home. I thought maybe someone here has run into this or knows how to fix this.
Thanks for the help
Dom

wascalwabbit said:
I was playing around with some ROMs yesterday, since i was not happy with CM11 anymore. after installing a couple of different ROMs i decided to stick with slimkat. so i made a nandriod of slimkat and tried to go back to CM11 to get my apps all figured out for the switch. This is where the trouble started. when trying to restore CM11 I would get to "writing data" and at some point (always a different percentage) the phone would crash and reboot and get stuck in a boot loop. it would then do the same thing when trying to restore the slim ROM, always crashing before the restore finished. I always wiped data/sys/cache, i tried to fix permissions, install different version of twrp (2.6.x.x vs 2.8.6.0). I've since restored the phone back to factory and installed twrp again. I'm at my wits end as to what the problem could be. one thing that's odd is I get a splash screen before the twrp splash which still shows the little cyanogenmod guy at the bottom, even though there should be no remnants of CM on my s3 at this point.
I have slimkat installed at the moment and it's running fine. i'd still like to boot back into my old CM11. if i can't it's no tragic loss.
Click to expand...
Click to collapse
Was the original CM11 nandroid made with the same recovery make and version which would not install it? I am pretty sure TWRP will not install a CWM or Philz nandroid. I don't know if there are issues installing a 2.6.x.x TWRP nandroid with the 2.8.x.x version of TWRP.

Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz

wascalwabbit said:
Thanks for you're reply. The backup was made with twrp, I'm not sure which version it was, so I downgraded to see if it would help, then I installed the latest version again. There was no difference in the results no matter the twpr version. Twrp nandroids are in fact incompatible with CWM, not sure about philz
Click to expand...
Click to collapse
Since Philz was originally based on CWM I wouldn't expect it to work with TWRP nandroids either.
Have you tried installing only specific partitions of the nandroid, such as the /data/data partition where the user installed apps are stored. As opposed to restoring the entire nandroid. I have heard mention of this, but in your case it may be problematic since your nandroid is of CM11 and the ROM you are running is SlimKat.

Oh that's a great idea, thanks, that may work. I i'll just flash CM and then restore data. I'm literally heading into the jungle right now, so in not sure if I'll be able to try this out for few days, but I will as soon as I get a chance.
Thanks for tour help