Hi,
I tried to nandroid backup from Amon_RA 1.7.0 and it failed after 3 dots:
"run 'nandroid-mobile.sh restore' via adb!"
I swear I searched.
But the only links are for G1 and I did not understand a thing about that script.
It refers to /sbin/sh
sh is located in /system/bin/sh on my device....
Help...
thx
I have seen this error when people try to run nadroid + ext when they lack an ext partition, but never just after 3 dots.
I got this same response when I tried to restore a nandroid+ext but when I tried it through adb I got different errors. I never got it to work
Is your battery low? I get that error if I try to do a restore and the battery is low.
Make sure the battery is above 30% and you will not get that error.
hyperlite1604 said:
Is your battery low? I get that error if I try to do a restore and the battery is low.
Click to expand...
Click to collapse
It might be that.
Thank you very much!
I'll report back.
i'm having the same issue. i rooted my nexus, created 3 nand backups, and try to restore them and get this error:
error: run 'nandroid-mobile.sh restore' via adb
so i've never once been able to restore a nand, but successfully can create them. i'm pretty lost here and have searched google so many times now.
and my battery is at 100% and i have 2 gb free space on my sd card, and it fat32.
So I dont know if it was really because of my battery level...
But the day after I tried again with more battery and it worked...
?
Good
Good for you but not for me cause my battery is 100 %.
Related
I feel that I am running on borrowed time. Every time I upgrade to a new version of cyanogenmod, I do a full Nandroid backup. I've done this several times without any problems.... until now. Here's what is going on.
1) Boot into recovery mode, run Nandroid Backup and it performs backup, adding dots, ENDLESSLY. I allowed it to run for 20 minutes straight and no change.
2) When I boot the phone normally and check the nandroid folder on the SD Card, I find that it started by creating a file and FILLING THE REMAINDER OF MY CARD! (2.2 gig).
3) After running fix_permissions, and FSCK on both the EXT3 and FAT partitions, is get the same result.
4) I went ahead and did the newest cyanogenmod update anyway and the update took without a problem, but the backup issue still is present.
This seems to be similar to this thread. Anyone here with some possible solutions?
EDIT- SOLUTION:
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
It feels so much better to have a good backup completed.
I know cliq users have that problem if they try to run nand with the phone plugged into USB. Was your phone plugged into USB by any chance?
borodin1 said:
I know cliq users have that problem if they try to run nand with the phone plugged into USB. Was your phone plugged into USB by any chance?
Click to expand...
Click to collapse
Yes. Every time a do anything firmware related, I connect to USB for that redundant power. I'll try without and let you know what I find.
Thanks!
Just tried again without the cable and waited till the screen was completely filled with dots (over 14 minutes) and it was still going. Had to pull the battery to restart it.
BTW... is there a more graceful way to terminate this without pulling the battery?
Did the Cliq users have to do anything after they encountered this problem besides unplugging?
Any log files I should check?
What recovery image are you using? Thought about upgrading it or just reapplying the image?
evilkorn said:
What recovery image are you using? Thought about upgrading it or just reapplying the image?
Click to expand...
Click to collapse
Just updated the recovery to RA-dream-v1.5.2 and it did the same thing. Also tried with a different SD card. No change.
Actually I just found out that the backup doesn't fill the card, it stops at the FAT32 2gb filesize barrier.
EDIT: Additional info: It is the data.img portion of the backup that grows to an insane size.
BART backup ended up failing also.
I've never mounted an .IMG file before. Could someone help me do that perhaps to see what file inside the data.img is exploding?
Try dropping to the console, enter umount /sdcard. Then run nandroid from the console.
Did I do what you wanted?
Booted to recovery, to console, umount /sdcard (wasn't mounted), /sbin/nandroid-mobile.sh -b
It went through and hung on data.img.
PROBLEM SOLVED!!!! Thanks all who helped out.
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
It feels so much better to have a good backup completed.
Congratulations!
fields_g said:
PROBLEM SOLVED!!!! Thanks all who helped out.
I went into Manage Applications and cleared out all the various caches. I noticed that "Browser" was reporting a very large NEGATIVE size for its data and total size. I'm guessing that that was the problem.
Click to expand...
Click to collapse
Hi,
I had *exactly* the same problem today. While searching for a solution, I tried similar things to solve the the never ending backup problem.
I read your solution a few minutes ago, checked my entries under "Manage Applications" and found the K-9 mail application with a size showing a large negative number. Deleting the cache was not possible, I had to uninstall the whole application.
After that, the nandroid backup works (and I think faster than ever... only about 2 lines of dots on screen).
Thanks for your solution!!!!!
Martin
This used to only happen from time to time, now it happens about 90% of the time.
Using RA-Recovery 1.6.2, I do a nandroid +ext backup, it will get half way through, and drop the error "Error, run nandroid-mobile.sh from console".
I can do this no problem, it's just very inconvenient. I'd like to know why the command doesn't work properly. I have PLENTY of space on my sd card, because running it from console works perfectly.
It's just a pain because there are no back lights on the keyboard, so unless I'm out in the daylight, it's hard to see the keyboard and use console.
Any ideas?
tehseano said:
This used to only happen from time to time, now it happens about 90% of the time.
Using RA-Recovery 1.6.2, I do a nandroid +ext backup, it will get half way through, and drop the error "Error, run nandroid-mobile.sh from console".
I can do this no problem, it's just very inconvenient. I'd like to know why the command doesn't work properly. I have PLENTY of space on my sd card, because running it from console works perfectly.
It's just a pain because there are no back lights on the keyboard, so unless I'm out in the daylight, it's hard to see the keyboard and use console.
Any ideas?
Click to expand...
Click to collapse
Just a theory on my part, but I think that it has something to do with the fact that there isn't a /system/sd directory anymore for CM5 builds, thus no ext partition to backup according to nandroid. A workaround is simple. Just create a /system/sd directory.
adb remount
adb shell mkdir /system/sd
then your nandroid + ext backup should work as long as you have a sufficient battery charge.
Thanks for the reply mate, I had figured that too, but then when it worked correctly via console, I dismissed it. I guess since I'm not the only one to think it, I'll give it a shot, see what happens.
I'm going crazy with this error and been doing Google search with no luck. I recently rooted, created a few nand backups and finally wanted to do some restores. I get that error. My battery is 100 % and my memory card has 2 gb free space on it. I'm at a loss what to do.
Even when I create a brand new backup and immediately try to restore, I get that error. Anyone have a solution? Thanks.
Everytime i try to restore i get the error: run 'nandroid-mobile.sh restore' via adb!
I have no clue what the hell to do :-(
Any help would be great.
I usually get that if my battery is too low.
ok got an adb shell running, done the process noted, but im still getting error. -
error:m5sum mismatch aborting. None of my previous backups work either?
Your battery is too low. It's a well documented issue.
If that doesn't fix it then you have the same issue I did. I get that same error and using a different memory card was the only way to fix it.
try running a repair on the sd card, with disk utility on a mac, or a similar disk scanning program on linux/pc. it's definitely an issue with the SD card BUT i've seen this error 3 times before and every time i get it a simple 15 second error scan fixes the problem.
Did you rename your Nandroid backup with a space? There should be no spaces.
x986123 said:
Did you rename your Nandroid backup with a space? There should be no spaces.
Click to expand...
Click to collapse
Could be the problem, i rename them all. Thanks for the advice guys
Can some one please help me my phone will create a nandroid but wen I go to restore it I get an error no matter wat I do
Sent from my HERO200 using XDA App
Two things usually cause this, either the folder is renamed and has a space in the name, or you are low on battery and need to charge your phone (greater than 50% is best)
Also have a close to full SDCard will cause it.
damn forgot that one. lol Don't think about it, never an issue for me
danaff37 said:
damn forgot that one. lol Don't think about it, never an issue for me
Click to expand...
Click to collapse
Those of us with <4GB cards have to deal with it on occasion
Thank you I'm gonna check the name n get back to you
Sent from my HERO200 using XDA App
Nope no spaces in the names of the folder or the folder in it and my battery is full n it won't restore ill send the exact error message
Sent from my HERO200 using XDA App
ok heres what i get when i try to restore my nandroid
Restore BCDMRS-20100712-1825 ?
Press HOME to confirm.
any other key to abort.
Restoring : .................
Error : run 'nandroid-mobile.sh
restore' via adb!
bycoo222 said:
ok heres what i get when i try to restore my nandroid
Restore BCDMRS-20100712-1825 ?
Press HOME to confirm.
any other key to abort.
Restoring : .................
Error : run 'nandroid-mobile.sh
restore' via adb!
Click to expand...
Click to collapse
How full is your SDCard?
abcdfv said:
How full is your SDCard?
Click to expand...
Click to collapse
i have over half of it free
try another nandroid to restore? that one may be corrupt
danaff37 said:
try another nandroid to restore? that one may be corrupt
Click to expand...
Click to collapse
Will do right now get back with the results in a minute
Sent from my HERO200 using XDA App
well it restored this time but after 3 hours on the htc screen i pulled the battery
I have this same issue.
I just created a new backup (97% battery, over 1/2 of SD card mem free). Here's a list of the files that it created:
boot.img
misc.img
recovery.img
system.img
When I look at one of the 2 backups that will actually restore, it shows these files:
boot.img
cache.img
data.img
misc.img
nandroid.md5
recovery.img
system.img
Any idea why this is happening?
No one has any thoughts on this?
What recovery are you running?
I'm running 1.5.2
You might want to try and use a newer version of recovery. There is 1.6.2 and also darch has one that he OC'd.
I had this problem before when I copied my sdcard to my computer and reformatted my card to fat32 only. When I tried to restore a backup it was trying to write files to the sdcard but there was not an ext file system on it so it would abandon the process.
unCoRrUpTeD said:
You might want to try and use a newer version of recovery. There is 1.6.2 and also darch has one that he OC'd.
I had this problem before when I copied my sdcard to my computer and reformatted my card to fat32 only. When I tried to restore a backup it was trying to write files to the sdcard but there was not an ext file system on it so it would abandon the process.
Click to expand...
Click to collapse
did you repartition your sd and it worked?
I flashed 1.6.2, and I still can't get a good backup.
The upside is I still have one that works, the downside is that it's from 6/1.
I would greatly appreciate any thoughts on other things to try.