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.

Nandroid backup rebboting after udating to clockwork recovery 3?

Hello,
I just got back my desire from repair and have rooted it again using unrevoked, my main rom i flashed was cyanogen 7, i made a backup and then i thought i would s-off and update to clockwork recovery 3....everything was successful.
But when i try out other roms then decide to restore my nandroid back up of cyanogen 7 messeges pop up quickly saying all the apps and stuff have stopped unexpectedly and then the phone reboots again and again.
Can some one help please.
Cheers.

Just do a full wipe and fresh install then backup again.
Sent from CM7

Meaple said:
Just do a full wipe and fresh install then backup again.
Sent from CM7
Click to expand...
Click to collapse
Hi,
I have done this 3 times and the nandroid backup still reboots, only way to fix it is to install cyanogen on top of it and it fixes it.
I think i will need to try with a sense rom and see if it happens too.
Thanks.

Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7

And if you did some fancy formatting to your SD card. Well, Might think about that also....

Meaple said:
Your tryings to restore the same backup? I said wipe, install fresh then backup that rom, not restore the old one.
Sent from CM7
Click to expand...
Click to collapse
I have deleted the old backup and made new one's each time after a full wipe, the card is formatted correctly and working fine, i have only had this problem after i updated clockwork mod and s-off.

Backup problems with DInc 2 and CMR

I have s-off and am permanently rooted. I am able to flash and run such roms as CM7.1 and RMK Gingersense from the original .zip file without a problem. However I have been unable to restore a single backup made with ClockworkMod Recovery.
For example, once I flash Gingersense I am unable to restore a backup to CM7.1. If I flash CM7.1 I am unable to restore a backup to Gingersense. In fact, I can't even successfully restore a previous backup of the same rom. I have reloaded CMR several times.
Every time I try to restore a backup, when I reboot I freeze on the white HTC screen. I have tried wiping everything before restoring, but that doesn't help.
It's a pain not being able to play with new roms and variations without being able to painlessly restore from a backup.
Any ideas?

bsteenson said:
I have s-off and am permanently rooted. I am able to flash and run such roms as CM7.1 and RMK Gingersense from the original .zip file without a problem. However I have been unable to restore a single backup made with ClockworkMod Recovery.
For example, once I flash Gingersense I am unable to restore a backup to CM7.1. If I flash CM7.1 I am unable to restore a backup to Gingersense. In fact, I can't even successfully restore a previous backup of the same rom. I have reloaded CMR several times.
Every time I try to restore a backup, when I reboot I freeze on the white HTC screen. I have tried wiping everything before restoring, but that doesn't help.
It's a pain not being able to play with new roms and variations without being able to painlessly restore from a backup.
Any ideas?
Click to expand...
Click to collapse
Here are a couple of thoughts.
1 - Is your SD Card full? I had been flashing ROMs and doing back ups a lot recently. As I flashed a ROM to give it a try, I noticed that my back up went very quick. I thought nothing of it, but when I restored that back up, it did not work and caused problems. Looking into things, their was not enough room on the SD Card for the back up to complete all partitions, so it did what it could and finished. You may have several back ups that are incomplete.
2 - You are not waiting long enough for the phone to boot. I have had my phone stuck on the HTC screen for a minute or more before it finally starts the boot animation. If the HTC animation keeps starting over, you have a boot loop, but if it is just on the screen, it may just be taking longer to boot.
I hope this helps.

I had some similar issues at one point. I would try deleting the entire clockwork folder from your SD card and let it recreate when you go back into cwr. That's what worked for me. I believe it was due to some older files that were left behind from prior versions of cwr.
Sent from my ADR6350

Sounds like the same problem I had. Which was a bad SD card format. You can try to format your SD card via Windows and start all over. One thing to note is when you hook your phone up to your computer and mount it that you must use the safely remove device icon in the system tray. This will cause many problems for you if you don't. Trust me, I learned the hard way!

Thanks for suggestions, but I don't think we've got it yet.
Plenty of room for backups (more than 7 GB) on SD card. Have looked at backup files and am pretty sure they are complete. Backups take the usual amount of time, but I notice the failed restores go more quickly than full new installs.
Always use safely disconnect to disconnect from computer (rarely mount to computer anyway - files are usually sent to phone through Dropbox).
Suppose I can reformat SD card, but what a hassle to copy/paste everything back on.
Will try deleting CMR folder, but don't think there could be vestiges from previous versions since this is the first/only version installed since root.
Any other ideas from the incredibly bright and helpful people on this forum?

Have you tried reflashing recovery?
Sent from my Droid Incredible 2

ruvort said:
Have you tried reflashing recovery?
Sent from my Droid Incredible 2
Click to expand...
Click to collapse
Yeah, even tried using an earlier version. No joy.

bsteenson said:
Suppose I can reformat SD card, but what a hassle to copy/paste everything back on.
Any other ideas from the incredibly bright and helpful people on this forum?
Click to expand...
Click to collapse
This is your best solution. If it doesn't work then you might have a bad SD card. It is a hassle to format the card but if you want it to work then it's the best solution.

Just a follow-up for anyone who lands on this thread because they have a similar problem.
Following the advice of spizzo03, I completely deleted ClockworkMod Recovery -- the app, the paid license app and the folder on the SD card. I then reinstalled just the free app of CMR from the Market.
Testing by trying to restore one of my backups ... IT NOW WORKS. Goes through the entire restore process -- system, data, cache, etc. -- whereas before it used to stop while restoring system.
Thanks to all who offered suggestions.

bsteenson said:
Just a follow-up for anyone who lands on this thread because they have a similar problem.
Following the advice of spizzo03, I completely deleted ClockworkMod Recovery -- the app, the paid license app and the folder on the SD card. I then reinstalled just the free app of CMR from the Market.
Testing by trying to restore one of my backups ... IT NOW WORKS. Goes through the entire restore process -- system, data, cache, etc. -- whereas before it used to stop while restoring system.
Thanks to all who offered suggestions.
Click to expand...
Click to collapse
Another one here. I was having issues as well restoring backups and simply wiping the sdcard's clockworkmod folder was enough for me.

[Q] Force closes long lag times, other problems so un-root/re-root or something else?

So, I have been having some major problems with my phone. Tons of force closes, major lag times and things like that. I have tried a handful of different ROMs, including CM7, the nightlys, Miui and a few others. I hear great stories about people and rooting and I want to be one of them. I am tired of all the hassles. So, when talking to someone in the office who has had no issues with his Droid 2, he suggested, and said he has read, the best thing to do is go back to stock, unroot, as they will remove all possible conflicting files that could be causing problems. Then, re-root, and install whatever.
Any thoughts on that? Generally, my process for installing a new ROM, I boot into recovery manually, clean cache, clean Dalvik, then install ROM. Then, I restore apps and data from Titanium and restore the Nandroid from Rom Manager. The past couple times, I have done the factory reset, but eventually, a day or 2, it goes back to the same problems. Maybe, I should just try it without the restoring the Nandroid (even though it is a backup from when there was no problems) and the app data from Titanium. I assume, you know what happens when you assume, that both the Nandroid and Titanium backups are clean as I backed up when I was having no issues.
So, any thoughts here? Unroot, then re-root or is there something else I should try to wipe everything clean to solve the problems? Currently, on the original Droid Incredible (got it on the release day, so the first screen), running 2.2 when I rooted, currently on Miui 1.9.16, but just installed it 10 minutes ago and was running the Cyanogen nightly's before hand..
Thanks in advance

When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Try not restoring apps and data from Titanium, as restoring the app is okay, but restoring data can cause unwanted things to happen more times than not.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that...
If you flash the RUU to return to stock and re-root, make sure you use the 2.2 RUU. If you use the 2.3, you need to be s-off to get rooted again. If you use the 2.3 RUU and you're s-on, no root for you...come back one year.

The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.

loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
As for Titanium, I restore apps with data all the time, but system data should almost never be restored as it's OS and app version specific. Basically, if it's green, it's safe. If it's red, don't mess with it. If it's white, like a user app, app and data are usually safe to restore.
ROM Manager is a bigger pain in the ass than it's worth and is useless for anything more than flashing a new recovery. If my recovery is working reliably, I never install ROM manager. Most devs will tell you to never flash with ROM manager anyways. Any function that ROM Manager performs can be performed in recovery in a safer, more reliable fashion.
Click to expand...
Click to collapse
Thanks for the correction, I forgot to put system in there...restoring system data is not good.
+1 on ROM Manager issues, always get a zip file of the ROM, and flash through recovery.

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
When you say restore nandroid from ROM Manager, what do you mean here? A nandroid is backing up your ROM via ROM Manager, which gets stored to your clockworkmod/backups folder...you shouldn't be pulling anything from that....
Click to expand...
Click to collapse
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
loonatik78 said:
The ONLY time you want to restore a nandroid backup is if you've wiped your device clean and want to return to a previously backed up setup. You should never restore a nandroid backup over a ROM you've just installed. If that's what you're doing, that's your problem. You're effectively replacing whatever ROM you just flashed in it's entirety.
Click to expand...
Click to collapse
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks

MikeDaub said:
That is pretty much what I do, except for the Mounts and Storage parts.
For the Nandroid part, maybe I have my terminology mixed up. I do a restore from Rom Manager...which I thought was called the Nandroid backup. It seems to me, that it makes sure the launcher and things are set up right.
I rarely use the ROM Manager to do anything, just restore (what I thought was called the Nandroid) to make the launcher the way things were..
But it seems like that is my problem. I am installed the new ROM, then just restoring a back up of all the problems. DUH.. Guess I should try it all without restoring anything from the ROM Manager and see how it all works. That will be my project tonight..
Thanks
Click to expand...
Click to collapse
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.

loonatik78 said:
If you want to restore your launcher, try it through Titanium Backup. If that doesn't do it, and I can't promise you it will work correctly, you're probably SOL on restoring a launcher unless some other backup app does the job better.
Click to expand...
Click to collapse
I am fine with not restoring it, I just thought "that is what you should do".
I don't venture too far from the regular settings, so it isn't a pain to do, just thought I should...

RMarkwald said:
When flashing a new ROM you should always do the following before flashing, especially if you're flashing completely different ROMs:
Wipe user data/factory reset
Mounts and Storage - format /system, format /boot, format /data, format /cache
Advanced - Wipe Dalvik, Wipe Battery Stats
Then flash the ROM zip.
Click to expand...
Click to collapse
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..

MikeDaub said:
One more quick question since I am thinking of it....is this same process if doing nightly updates from Cyanogen, or just is I change from say, Cyanogen to Miui or something??
Thanks again for all the help..
Click to expand...
Click to collapse
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.

loonatik78 said:
Generally, CM nightlies can be flashed over top of each other without a wipe since the vast majority of the code is identical. However, if an issue crops up, a wipe and flash might be a good thing to try. Probably won't help though, since nightlies, by definition, are experimental.
Always wipe and flash when moving from one ROM type to another.
Click to expand...
Click to collapse
That's kinda what I figured, but I thought it was worth asking so I don't completely wipe the whole thing every time I install an update. The nightly I am on now seems to be working, so the new plan is keep whats working until it doesn't work anymore, or some major update comes along..
Thanks again for the help. I really appreciate it.

If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.

jackbtha1 said:
If the issue continues you can try copying everything off of your SD card to your PC and reformatting your SD card. Remember to use FAT32 format. Then copy everything back to your SD card. I've read threads were this helped the force close issues for many people - Just a thought.
Click to expand...
Click to collapse
Certainly worth a thought. The card that is in it now came from a different phone. I am pretty sure I formatted it when I first plugged it in, but it can't hurt to try...
Thanks

Can't restore backup and network problems

dud3me said:
Phone reboots every time I turn on mobile data. Had this issue after using 3gturbocharger but got 2g working after that. Then I chose the network from settings and now it's rebooting every time I turn mobile data on. I think I'm on 3g atm and I'm on nightly 236. Will try a fresh install and see if it helps!
Click to expand...
Click to collapse
dud3me said:
Ok so did that and it's still rebooting every time i try to turn it on -.-
Click to expand...
Click to collapse
dud3me said:
I don't think it was about the script cause I "unsuperduperturbo charged it" the problem started when I chose network again. I took the same carrier that I was on atm (don't remember the reason why I did that).
Also when trying to restore a backup I get "error while restoring sdcard/android/.secure" or something like that.
Click to expand...
Click to collapse
When I try to restore back up I get this "error while restoring sdcard/android/.secure" or something like that. I'm on cwm 5.0.2.0 and you can see the reason why I need to restore from the quotes.

Happened to me a few times, even on some backups I know previously worked. I just put it down to unpredictable software and start again. If there's things you need from the backup try advanced restore in clockwork recovery or app extractor from the market, a free app which lets you pull apps and data from nandroid .imgs.
Sent from my HTC Wildfire using xda premium

Ok so figured the backup problem but the mobile network still isn't working

Do a fresh install (Remember to format /system in mounts and storage, just doing wipe data / factory reset is not sufficient). Then, reflash the radio and try again.

3xeno said:
Do a fresh install (Remember to format /system in mounts and storage, just doing wipe data / factory reset is not sufficient). Then, reflash the radio and try again.
Click to expand...
Click to collapse
That should disable all the scripts? Cause I tried that and then restored nandroid but I'm not sure If I was running the script when I made the nandroid. And how can I reflash the radio because when you start cm7 for the first time It has data on so it just reboots before you can turn it off and I can't flash cm7 and radio with same cwm so should I do a fresh install of cm7 and then fastboot flash cwm 2.5 and flash the radio?

Keep this zip file on your sdcard, its the same as ROM Manager (ie Temp 2.5.0.7). Flash in your existing Clockworkmod 3/4/5 after fresh installing CM7 to get temporary 2.5.0.7 and then flash the radio. You need not boot into the ROM to do this.
http://forum.xda-developers.com/attachment.php?attachmentid=662193&d=1311319218
I don't know whether it will solve all your issues or not, but I think its worth to try it. (Again, remember to format everything under the Mounts and Storage Menu, especially /system)

Actually the 3g is now working on senseonfire I guess the reboot was just a coincidence. I'm gona go back to cm7 now and I'll fast the new radio just to be sure.
Edit: Seems to be working fine

Error restoring .secure
HI
As opposed to other items, "android_secure" is stored on the SD card instead of internal flash. So, your "error while restoring sdcard/android/.secure" is likely to happen if your sd card is full. (it happened to me for that reason !!)
I would suggest to mount the sdcard from usb - you can do it from the recovery menu - then try to free enough space for this restoration. Or maybe also try repairing the sdcard filesystem.

jjacinto said:
HI
As opposed to other items, "android_secure" is stored on the SD card instead of internal flash. So, your "error while restoring sdcard/android/.secure" is likely to happen if your sd card is full. (it happened to me for that reason !!)
I would suggest to mount the sdcard from usb - you can do it from the recovery menu - then try to free enough space for this restoration. Or maybe also try repairing the sdcard filesystem.
Click to expand...
Click to collapse
Wow......... Talk about waking the dead lol.
Sent from my Nexus 4

Well I had this issue and couldn't find any solution on the forums... But I ended up on this similar thread and had to resolve it by myself, so I thought this little contribution might help someone else in the future.
slymobi said:
Wow......... Talk about waking the dead lol.
Sent from my Nexus 4
Click to expand...
Click to collapse