Hey guys, ive read every solution to Error: run ' nandroid-mobile.sh restore ' via adb! hero, eris etc whatever phone that has this problem and no solutions work. ive run the restore through adb and restores just fine. but that is a pain in the ass. i wanna restore via recovery. sometimes ill be running a rom and need to switch to run gps or 4g etc. ive partitioned the sd card. ive made a new restore of current rom and flashed a different rom and restored and works just fine. but what about all of my other nandroid back ups i put them back on and get that error. even my original before i started rom flashing. should i unroot and flash it to stock etc and start fresh? sorry if its just ramblings and not really questions but dont now what to ask. i just want my backups to work. ps have over 7 gb free and battery is full and plugged in when tring to restore. ive flashed restores with alot less
crzy619 said:
Hey guys, ive read every solution to Error: run ' nandroid-mobile.sh restore ' via adb! hero, eris etc whatever phone that has this problem and no solutions work. ive run the restore through adb and restores just fine. but that is a pain in the ass. i wanna restore via recovery. sometimes ill be running a rom and need to switch to run gps or 4g etc. ive partitioned the sd card. ive made a new restore of current rom and flashed a different rom and restored and works just fine. but what about all of my other nandroid back ups i put them back on and get that error. even my original before i started rom flashing. should i unroot and flash it to stock etc and start fresh? sorry if its just ramblings and not really questions but dont now what to ask. i just want my backups to work. ps have over 7 gb free and battery is full and plugged in when tring to restore. ive flashed restores with alot less
Click to expand...
Click to collapse
I usually got that issue when one of two things happened. The nandroid backup I did was corrupted, or never backed up right. Or two, when I changes the name, and added spaces or certain symbols it borked it.
If you haven't changed it, it may just not have nandroid backedup correctly. If you are able to restore via ADB then do so and renandroid.
Did you use illegal characters in your file name? Did you try to restore a clockwork backup with amon ra or vice versa?
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
crzy619 said:
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
Click to expand...
Click to collapse
Did you make any changes to system files? The files may be corrupted.
crzy619 said:
ive only used amon ra from the very beginning. i will try clock just cuz i can. and nope all the backups ive tried are original names. i have renamed some in the past and they have restored fine before. but ones im trying are original. i cant even flash the first nandroid i made and ive gone to that one bunch times?! idk cuz this randomly started happening.
Click to expand...
Click to collapse
what version of Amon-Ra are you using? If your not using 2.3 go flash it immediately and try again.
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.
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
crater said:
So got my G2 today, rooted, installed Hboot, started up the phone, logged into all my accounts, got stuff how I wanted. Made a backup via Clockwork.
Then I tried out CM7 Nightlies, decided its pretty good but I wanted to go back to my backup. Loaded into Clockwork hit recover, picked my backup. The phone then just sits on the HTC screen. Never going to the G2 screen or getting back into the OS. I can't get a logcat from it either to see if it is crashing. I can get back into recovery, and flash another rom, but why isn't my backup of my original image working? There are no errors when restoring, I've tried a few times.
Click to expand...
Click to collapse
If you are using CM7, does this mean you upgraded to one of the CWM3 recoveries? Not sure if this has changed, but backups made with the older CWM2 recoveries are not compatible with CWM3. You will need to reflash back to the older recovery before restoring your backup (pretty sure there are lots of warnings about this in the CWM3/CM7 threads, so you should probably check those out to see if this is no longer the case).
I used CWM3 to make the backup, i assumed that would work to restore it.
EDIT: Okay. so CWM3 can't handle ANY Froyo, regardless of if the backup was made with it. Misunderstood that part. Flashed to CWM32 and it worked. Thanks.
Hello everyone,
I have been running cyanogen 7 nightlies for the past week. Today I decided to give a couple sense based roms spin. I decided that I preferred cyanogen and attempted to restore to my backup. No matter what I tried, I could not restore the rom, it kept saying there was an error and go check the log files. I tried several different cyanogen backups I had made. So I reflashed cyanogen, after restoring a previous backup of a sense rom. So after flashing and resetting up my phone on cyanogen, I performed a backup and attempted to flash back to the same sense rom that had worked for me earlier on in the day, because I wanted to update my prl. Now I can't flash from my cyanogen rom to the sense rom due to an error again. Obviously this is a problem if my backups wont work. I have tried flashing from RA to clockwork and back to RA 2.3, but that did not fix the problem. What is going on?
Thanks
hate to say it but you could be one of those Rare cases where the nandroid/clockword backup is bad. i would suggst nandroid another rom to see and if you can go back to that one from nandroid you will know the other backup is bad.
Also i would upload the log files here cuz im sure plenty of people can ready your log files(i cant..lol).
Also i read when i was on the HTC HERO that sometimes when you flash to a different rom it does something to the flash portion of the backup(or watever). One time i flashed to a sense rom on my hero to try it out and then flashed back to CM6 and i couldnt flash ANY zip, or backup file. i had to do a adb line on my phone in order to enable to flashing/backups to work again. cant remember the line tho.
By any chance were you naming them, on clockwork from rom manager, and on pc for amon_ra? If so and they had spaces, you need to re-name them, just no spaces. Hyphens, underscores, and periods are okay though.
teh roxxorz said:
By any chance were you naming them, on clockwork from rom manager, and on pc for amon_ra? If so and they had spaces, you need to re-name them, just no spaces. Hyphens, underscores, and periods are okay though.
Click to expand...
Click to collapse
Really? I did just recenty start naming the backup via my pc, where I did include spaces (file manager won't allow this). Ill rename and let you know what happens.
That fixed it. Thanks a lot.
-Tosses scarf like Homer- And that's the end of that chapter.
So tonight I was trying to show off my phone to a friend that didn't understand the concept of rooting. I made a nandroid of my current rom, so I could flash a past nandroid. As I started flashing, it was able to flash the boot and the system, but it could not flash the data for some odd reason. I am using clockwork mod 2.5.0.7, and have been using it before, but have never ran into this problem. I even tried flashing the nandroid that I had made tonight, but the same problem occurred. Any ideas?
Ps. My roms were MIUI 1.8.5(nandroid tonight) and Synergy RC 1(past nandroid).
Cmorris8848 said:
So tonight I was trying to show off my phone to a friend that didn't understand the concept of rooting. I made a nandroid of my current rom, so I could flash a past nandroid. As I started flashing, it was able to flash the boot and the system, but it could not flash the data for some odd reason. I am using clockwork mod 2.5.0.7, and have been using it before, but have never ran into this problem. I even tried flashing the nandroid that I had made tonight, but the same problem occurred. Any ideas?
Ps. My roms were MIUI 1.8.5(nandroid tonight) and Synergy RC 1(past nandroid).
Click to expand...
Click to collapse
Was your battery level low?
from my EVO 4G
dougjamal said:
Was your battery level low?
from my EVO 4G
Click to expand...
Click to collapse
It was at 60%. All I've read is that 30% is the minimum you can flash stuff at so the phone won't die.
Did you have ample space on your sd card when the backup was made? Cuz if not that portion could have been corrupted and not flashing.
+1 for a corrupted nand. Was there any transfers of the nand between pc and phone? Sometimes they can get corrupted like that. Also I suggest using amon ra 2.3 for recovery.
Sent from my PC36100 using XDA App
I have plenty of space on my sdcard (1.74 GB), and I had not messed with it on my computer. After trying the synergy backup and it not working, I tried to restore the backup I had just made that night, and it came up with the same problem. And I switched to Amon a few months back, but it is not as convenient as Clockwork to make nand backups. I have been contemplating switching to Amon, but the convenience of Clockwork is overwhelming with rom manager.
Recently have been having the worst luck.
I haven't ever been able to get CM to work on my SG3.
I've tried downloading stables and nightly. They always seem to be bad no matter how many times I down load them.
Recently everything went bad **** crazy where CWM thought my back up folders were empty.
After I rerooted the phone with odin, I tried to do a restore.
At which point CWM told me all of my original backup were had mismatched MD5s.
So does anyone know what happened here? How I can prevent it from happening again?
Icon000 said:
Recently have been having the worst luck.
I haven't ever been able to get CM to work on my SG3.
I've tried downloading stables and nightly. They always seem to be bad no matter how many times I down load them.
Recently everything went bad **** crazy where CWM thought my back up folders were empty.
After I rerooted the phone with odin, I tried to do a restore.
At which point CWM told me all of my original backup were had mismatched MD5s.
So does anyone know what happened here? How I can prevent it from happening again?
Click to expand...
Click to collapse
I have been having issues with CWM telling me my backup folders are empty.. like i never did a Nandroid backup.. Very strange. So i always keep a few ROMS that work well stored on my SD card.
Make sure your CWM is up to date. Download ROM manager, and flash over the most recent CWM from there. Also from ROM manager you can download and flash over some of the CM's to your phone and ROM manager will install for you.
DustinD1986 said:
I have been having issues with CWM telling me my backup folders are empty.. like i never did a Nandroid backup.. Very strange. So i always keep a few ROMS that work well stored on my SD card.
Make sure your CWM is up to date. Download ROM manager, and flash over the most recent CWM from there. Also from ROM manager you can download and flash over some of the CM's to your phone and ROM manager will install for you.
Click to expand...
Click to collapse
The install would even fail when I was installing CM 10 stable from Rom Manager.
I'm at a loss of what else to do.
Icon000 said:
Recently have been having the worst luck.
I haven't ever been able to get CM to work on my SG3.
I've tried downloading stables and nightly. They always seem to be bad no matter how many times I down load them.
Recently everything went bad **** crazy where CWM thought my back up folders were empty.
After I rerooted the phone with odin, I tried to do a restore.
At which point CWM told me all of my original backup were had mismatched MD5s.
So does anyone know what happened here? How I can prevent it from happening again?
Click to expand...
Click to collapse
Rename your back ups and remove any spaces in the name. The back ups can be named anything you want, just make sure there aren't any other spaces. I had the md5 checksum error and this was the fix, I removed the spaces and voila it worked
Sent from my SAMSUNG-SGH-I747 using xda app-developers app