I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
gospodinwizard said:
I have found that I can't perform either a Bart or nandroid backup from recovery. Any ideas? Do I perhaps need to update Among RA? My version is 1.6.2.
Sent from my FroyoEris using XDA App
Click to expand...
Click to collapse
Does it just get like 1 or 2 dots into it and then says it can't?
Sometimes it has to do with it properly mounting your SD card.
Try plugging USB into a computer, turning on USB-MS toggle for a second, then turning off USB-MS Toggle. SOmetimes that works.
Otherwise, turn off the phone, pull out the SD Card, put it back in, then boot back into Recovery.
This happens to me occasionally. You can't Flash from Zip either, when this happens. It's annoying but it'll work eventually.
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
gospodinwizard said:
I haven't tried removing the SD Card, but I will try that. Flashing from zip still works fine. And I can still use nandroid-mobile.sh via adb to make backups with no issues. Restoring from recovery works fine as well. It seems to get about half way through the backup process before it craps out and tells me to use nandroid-mobile.sh. And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
http://forum.xda-developers.com/showpost.php?p=7661952&postcount=1
Your SD card possibly needs to be re-formatted.
Don't forget to back it up first.
Once I formatted my card with normal FAT and had very strange behavior as such.
And even if you already did as FAT32, sometimes recovery (and android) only likes it if you use home > menu > settings > Sd card and storage > format to format it.
Once, I had to format it fat32, then go into android and format it again.
Odd, I think. But something about how it writes blocks of data, and it can't seem to write it the way it wants in recovery, even though windows can with nandroid-mobile.sh.
I don't know how well this works for our phone, but this might be worth a shot:
http://erlern.wordpress.com/2010/06/03/error-run-nandroid-mobile-sh-via-console/
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
dragon1018 said:
I had this problem last nite. Possibly your battery may be low or something with the SD card. For me was as easy as letting the phone charge for like 20 minutes then try again
Sent from my Eris using XDA App
Click to expand...
Click to collapse
I was thinking the same thing, but he said:
And this all happens even if the battery is at 100% or plugged into the wall charger.
Click to expand...
Click to collapse
OK just to top this all off and make it even weirder, nandroid backup from recovery just started working again. I have no concrete idea why, but I did notice something a bit odd. I was poking around in the terminal emulator to see what I could decipher. I entered "whoami" and got the response "app54". So I typed "su" and a message popped on the screen that "Titanium Backup has been granted root access". Another "whoami" returned "root". I uninstalled TB and booted into recovery but the backup still didn't work. Rebooted, reinstalled TB, and went back to recovery at which point nandroid backup decided it was time to work. I can't imagine what, if any, the connection is with my backup problems but nonetheless this is what transpired. I was left wondering if TB had done something with/to busybox that caused the problem.
Related
So I just tried to go back to a previous nandroid backup I had on my phone, specifically CyanogenTazz because I didn't like the current ROM I was on... So I wiped my dalvik cache and did a factory reset wipe and then went to restore and it gave me this error "error : run 'nandroid-mobile.sh restore' via adb!" What is the exact command in command prompt to do that? And what caused this error? I'm pretty confused
Does your battery have plenty of charge left? If not, plug the phone in and try again. Nandroid will refuse to do a backup or restore unless it knows it has plenty of power.
Sent from my Eris using Tapatalk
plug your phone into a charger and try again
My battery is at 100% And I also had the charger plugged in when I tried to do it.
thisisreallygay said:
My battery is at 100% And I also had the charger plugged in when I tried to do it.
Click to expand...
Click to collapse
I've had this happen to me. Your backup name might be to long or contain characters that aren't kosher. Can you restore an older backup? If you can, restore to an older backup and change the name if that's possible.
I can't restore any backup, I have 3, one is named CyanogenTazz V5 the other is just the like random characters that Nandroid gives it, and then the other one I've used multiple times before and it has worked... I started having this problem right after flashing the Aloysius V12 Purehero port or something like that. The ROM works.. Just nandroid doesn't.
Okay I heard you need to have USB Debugging on when doing it and I had that option on.. but when I would turn off my phone it would disable USB Debugging I think because it just wouldn't work.. So I plugged it into my computer so that it would activate USB debugging and then I turned it off while plugged it and it worked now... So I don't know if that was it or what.. but I didn't do anything different other than that. But its working now so thanks
I had this problem. My recommendation. Make a new backup. Take an old backup and rename this folder the name assigned to the new backup. Then try restoring that backup. I had success with this method.
You can try renaming the backup. I had the same issue and that took care of it. Basic rule of thumb. Keep the new name short and only include alpha numeric characters.
The default naming for new backups works pretty like a time stamp. Bds-yyyyddmm-tttt. If you have multiple backups rename them to what you'll remember easily.
Oh and has anyone tried a BART backup or know what that is?
Sent from my Eris using XDA App
When you get that error message "... run nandroid-mobile.sh...", the cause of the problem is ALWAYS logged in the recovery log; you can discover what the problem is simply by looking at that log file - either using Root Explorer, or by pulling the log file to your PC with ADB, as in:
C:\foobar> adb pull /cache/recovery/log log.txt
C:\foobar> wordpad log.txt
(You can do these steps without ever leaving Amon_RA, as "adbd" is running when Amon_RA is booted)
Turns out to be a lot faster than playing 20 questions with random dudes on the Internet
I'm going to guess NAND backup names can't include special characters as well. I'd also think it'd probably be best not to include spaces in the name either. I'm not positive about such things in Linux but I do know that in some versions of unix-based OS's anything after the space would essentially be ignored. So if the name of the backup is passed as a parameter to a function, "CyanogenTazz v6" would be evaluated as "CyanogenTazz" and thus the backup wouldn't work.
Ever since i rooted my phone. I have not been able to run any of the backup options in the recovery menu. Is there anything specific i should do? I have tried rerooting and a couple other hocus pocus fixes but nothing ever works and i do not want to run these backups from adb shell.
Seannoxious said:
Ever since i rooted my phone. I have not been able to run any of the backup options in the recovery menu. Is there anything specific i should do? I have tried rerooting and a couple other hocus pocus fixes but nothing ever works and i do not want to run these backups from adb shell.
Click to expand...
Click to collapse
Why exactly can you not use the recovery menu (i.e., is it a trackball issue)?
If so, check out this post: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Cheers!
scary alien said:
Why exactly can you not use the recovery menu (i.e., is it a trackball issue)?
If so, check out this post: http://forum.xda-developers.com/showpost.php?p=9124095&postcount=83
Cheers!
Click to expand...
Click to collapse
Sorry no it's not a trackball issue. It just says Error: run in adb. I have seen a lot of fixes but none of them seem to ever work. It wont ever allow me to bart or nand backup always errors out. I can external backup but that really isn't any sweat off my nuts.
Seannoxious said:
Sorry no it's not a trackball issue. It just says Error: run in adb. I have seen a lot of fixes but none of them seem to ever work. It wont ever allow me to bart or nand backup always errors out. I can external backup but that really isn't any sweat off my nuts.
Click to expand...
Click to collapse
Argh, I really wish I could remember what the solution was for that. I'm afraid someone else is going to have to answer because I haven't had that happen in many months.
One workaround, download the free ROM Manager off the market. It won't replace Amon RA, if that's what you're using, but it'll allow you to load ClockworkMod Recovery from Amon RA, and then perform backups and restores from there. You can also use the ROM Manager app to tell it what to do and then it'll reboot and automatically do whatever you tell it and reboot after.
I don't know for sure that this will alleviate this problem, but it won't do anything permanent to your phone and it's cheap to try. Come to think of it, maybe one of the reasons I haven't had this problem in many months is I've been using ROM Manager for over four months.
Let me know if it helps if you try it.
Can you post your exact error message? I scanned Amon_RA's recovery source as well as the nandroid-mobile.sh script and found similar things, but the exact error message would help tremendously.
1. Make sure you have enough space on your /sdcard. The nandroid-mobile.sh script will check to make sure that you have at least 130MB or more of free space before allowing a backup to be performed.
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
A couple of months back, I examined the nandroid-mobile.sh script for circumstances under which it would return a non-zero return status. This post over on AF details that analysis: http://androidforums.com/eris-all-things-root/142379-help-please-cant-nandroid-restore.html#post1604509
As you can see, there are several scenarios that could lead to the backup refusing to work (including a wonky /sdcard). So, if you have another card you could try, that might help.
Cheers!
Too late to run through this tomorrow but will observe all this new found data and report back. Thanks guys always appreciated.
scary alien said:
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
Click to expand...
Click to collapse
Good point! Now that you reminded me, I think this was the main culprit when I was having a problem, and it just so happens that my phone is nearly always charged pretty full for the past several months since I USB tether for my computer internet.
roirraW "edor" ehT said:
Good point! Now that you reminded me, I think this was the main culprit when I was having a problem, and it just so happens that my phone is nearly always charged pretty full for the past several months since I USB tether for my computer internet.
Click to expand...
Click to collapse
A low battery was the issue the couple of times I ever had it as well.
scary alien said:
Can you post your exact error message? I scanned Amon_RA's recovery source as well as the nandroid-mobile.sh script and found similar things, but the exact error message would help tremendously.
1. Make sure you have enough space on your /sdcard. The nandroid-mobile.sh script will check to make sure that you have at least 130MB or more of free space before allowing a backup to be performed.
2. Be sure to have enough battery charge (best bet is to always be topped-off and plugged-in...just to be sure). The nandroid-mobile.sh script will check to make sure that you have at least 30% or more battery charge before he'll allow a backup to take place.
A couple of months back, I examined the nandroid-mobile.sh script for circumstances under which it would return a non-zero return status. This post over on AF details that analysis: http://androidforums.com/eris-all-things-root/142379-help-please-cant-nandroid-restore.html#post1604509
As you can see, there are several scenarios that could lead to the backup refusing to work (including a wonky /sdcard). So, if you have another card you could try, that might help.
Cheers!
Click to expand...
Click to collapse
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Seannoxious said:
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Click to expand...
Click to collapse
Yeah, I've never run anything other than a Nandroid backup and restore--never have done a BART backup or + ext...
Good luck!
Seannoxious said:
I got it to run just the NANdroid backup without error for the first time ever. Whenever i try to do NANdroid + ext or BART backup it says Error:Run X in adb shell. I have enough battery but will try charging to 100% and being plugged in in a second. Will try an alternate SD and report back. I have an 8gig micro sd hc. Transcend. Not sure if that matters.
Click to expand...
Click to collapse
This is weird because I downloaded the rom manager which is quite awesome might i add. It looks at my SD notices it has enough space to backup the NAND but refuses to do the external backup because it says No sd-ext found. Going to try titanium backup + nand + ext backup (from my pc) see if that covers all bases
Seannoxious said:
This is weird because I downloaded the rom manager which is quite awesome might i add. It looks at my SD notices it has enough space to backup the NAND but refuses to do the external backup because it says No sd-ext found. Going to try titanium backup + nand + ext backup (from my pc) see if that covers all bases
Click to expand...
Click to collapse
Did you ever partition your /sdcard (i.e., for apps2sd)? If not, you won't (or shouldn't have) any ext2 or ext3 partitions (I believe...).
Just wanted to make sure you weren't chasing your tail...
scary alien said:
Did you ever partition your /sdcard (i.e., for apps2sd)? If not, you won't (or shouldn't have) any ext2 or ext3 partitions (I believe...).
Just wanted to make sure you weren't chasing your tail...
Click to expand...
Click to collapse
I never did but thought that nandroid+backup did the backup of the sd in general not necessarily the partitions.
Also just installed froshedyp 9 after a full wipe did the nandroid backup and it put xtr back on the phone? I thought nandroid backup was to backup your **** so when you installed a new rom you didn't have to reset everything up (apps and settings and the such)
First, SD-Ext is referring to a Ext2/3/4 partition on the SD card, which you would've had to put there for old style (before Froyo) Apps2SD function, as Scary Alien said. So a failure to backup SD-Ext doesn't mean the backup itself fails, it just skips the SD-Ext backup if it doesn't exist, which it sounds like it doesn't.
Also, no, a Nandroid is to backup your ROM exactly the way you have it configured including the ROM itself. That's why it has to be done outside of the ROM, in recovery. Titanium Backup and other backup apps are for doing what you're talking about, backup up your Apps and your Apps settings.
Note that it's a risky thing to use any backup program to backup the system settings. Not actually risky to back them up, but you should never restore them to a completely different ROM (even if they're both based on CM6.x or whatever, or both based on Stock), so it's really only applicable between minor version upgrades of the same ROM (CelbFroyo 3.9 to CelbFroyo 4.0). Even then this is risky and sometimes breaks things, so don't expect to be able to do it too often if you change ROMs again.
roirraW "edor" ehT said:
First, SD-Ext is referring to a Ext2/3/4 partition on the SD card, which you would've had to put there for old style (before Froyo) Apps2SD function, as Scary Alien said. So a failure to backup SD-Ext doesn't mean the backup itself fails, it just skips the SD-Ext backup if it doesn't exist, which it sounds like it doesn't.
Also, no, a Nandroid is to backup your ROM exactly the way you have it configured including the ROM itself. That's why it has to be done outside of the ROM, in recovery. Titanium Backup and other backup apps are for doing what you're talking about, backup up your Apps and your Apps settings.
Note that it's a risky thing to use any backup program to backup the system settings. Not actually risky to back them up, but you should never restore them to a completely different ROM (even if they're both based on CM6.x or whatever, or both based on Stock), so it's really only applicable between minor version upgrades of the same ROM (CelbFroyo 3.9 to CelbFroyo 4.0). Even then this is risky and sometimes breaks things, so don't expect to be able to do it too often if you change ROMs again.
Click to expand...
Click to collapse
Sweet thanks for clearing everything up man.
Hello, I have to let you know that my knowledge over android is limited.
My (rooted) p500 was working flawlessly.
One day the music app just stopped working. I tried to uninstall it with an unistaller, and try to install it again. It wouldnt install for no reason. Just keeps "installing" and never ends.
Next step was performing full backup with the titanium backup. After that i restored the phone to the factory settings.
And here comes the major problem. Any app i try to intall Just keeps "installing" and never ends. Even from the market or just by running the apk.
I performed several restores to factory setting and it didnt help. I cleared the updates the cashe and the data from the Market app. Didnt help.
Is there any way to bring my phone back to normal?
use AppMonster to do your installs/uninstalls or Astro File Manager. I've experienced this issue with the latest version of titanium backup.
Well at this time my phone is useless. I can't install anything.
Is there a way back?
sspyross said:
Well at this time my phone is useless. I can't install anything.
Is there a way back?
Click to expand...
Click to collapse
have you tried resetting to factory mode? HOME+VOL DOWN+POWER
I'll do it right now.
Well i thing holding down those keys is the same as doing it from the settings.
So yes i did it once again and nothing happened. Still cannot intall a s#!t!
oh boy... it sounds like it's time for an LG Stock ROM flash.
http://forum.xda-developers.com/showthread.php?t=883314
here is the stock ROM:
csmg.lgmobile.com:9002/swdata/WEBSW/LGP509BK/ATMOBK/V10l_00/V10L_00.kdz
edited for latest stock rom.
I'll try it also! Thank you!
If its not too late, it might be better to use a lower version ROM as that is V10L. Which I believe is NOT ROOTABLE.
AzNxJoHnNy said:
If its not too late, it might be better to use a lower version ROM as that is V10L. Which I believe is NOT ROOTABLE.
Click to expand...
Click to collapse
I tried to do the trick but i could make it through the drivers setup. I put the phone in the emergency mode. After that, and seeing that i couldn't got it working. I restarted the phone, did a reset to factory settings. My phone at this time WAS working.
I started installing apps, but after installing 13 of them, it stuck again. From now on it's in the same situation as before, i cannot install any more.
Should i try the trick again?
Try a different sd card.
Do you have custom recovery? If not, install it. And then you can install any custom rom.
Sent from my LG-P500 using Tapatalk.
What else have you done with your phone?
My phone did something like this before when I tried to force it to directly install everything new to my memory card which was Class 2. I used some command prompt stuff I found on the internet to instruct my phone to shift to SD card.\ storage.
It would be able to install some files and I even remember Angry Birds would install to SD card even before the mod. Then it would stop and hang at the installing screen after a while.
The solution (after a week at the service center) was to get a faster memory card. That's what the guy said. My temporary fix was to install everything to the Internal Memory like it is supposed to, and move them to the SD card using Titanium Backup. But this made some apps move too slowly...
lekhwani said:
Do you have custom recovery? If not, install it. And then you can install any custom rom.
Sent from my LG-P500 using Tapatalk.
Click to expand...
Click to collapse
Would be nice if i could istall anything.
raylgo said:
What else have you done with your phone?
My phone did something like this before when I tried to force it to directly install everything new to my memory card which was Class 2. I used some command prompt stuff I found on the internet to instruct my phone to shift to SD card.\ storage.
It would be able to install some files and I even remember Angry Birds would install to SD card even before the mod. Then it would stop and hang at the installing screen after a while.
The solution (after a week at the service center) was to get a faster memory card. That's what the guy said. My temporary fix was to install everything to the Internal Memory like it is supposed to, and move them to the SD card using Titanium Backup. But this made some apps move too slowly...
Click to expand...
Click to collapse
I used an unistaller to unistall the preinstalled music app because it stopped working. When i tried to install it again that was it, it hangs at the installing screen forever.
According to the sd the only thing i used the move2sd, but i didn't use it.
My sd is class 6.
Is it normal that the superuser (root) remains after recovering to the factory settings?
Should i try to reinstall the software by myself or let the lg technicians do it?
Mind-blowing (for me) update.
While using the device without the sd, the apps get installed normally!
WTF?
PS: Should i use the FAT or the FAT32 file system on my sd card?
I used another sd and it seems to work till now.
Finally.
I formatted the sd card (fat32 just as it was before) and now everything works perfect.
The only minor issue is that i cannot install the music.apk
It always fails. I like when it fails, at least it doesnt freeze.
Do you now any way i could install it, or should i get over it and use an other music app?
sspyross said:
Finally.
I formatted the sd card (fat32 just as it was before) and now everything works perfect.
The only minor issue is that i cannot install the music.apk
It always fails. I like when it fails, at least it doesnt freeze.
Do you now any way i could install it, or should i get over it and use an other music app?
Click to expand...
Click to collapse
use Winamp from the Android Market.
sspyross said:
Finally.
I formatted the sd card (fat32 just as it was before) and now everything works perfect.
The only minor issue is that i cannot install the music.apk
It always fails. I like when it fails, at least it doesnt freeze.
Do you now any way i could install it, or should i get over it and use an other music app?
Click to expand...
Click to collapse
Yes, you could get over it and try some other app. There's plenty of them on the market. I settled for doubleTwist.
AzNxJoHnNy said:
If its not too late, it might be better to use a lower version ROM as that is V10L. Which I believe is NOT ROOTABLE.
Click to expand...
Click to collapse
I have rooted V10L no problem with z4root
I recently received a new phone (sent the other one back because it wouldn't boot/charge anymore). Anyways, I am not sure if this is something that was occurring on my previous phone or not, but if I install MOTODX2_Bootstrap_signed.apk (which is a package I have had forever... maybe there is a newer version or something?) everything works fine until I reboot. I can get into recovery and create/restore a backup, install .zip files, etc. However, after I reboot the phone the icon for System Recovery is no longer in my app drawer. I can re-run the .apk from my external SD card and everything works fine again... until I reboot. Anyone seen this?
BTW Stock 2.3.5 1.3.418
I had that happen before, my solution was move it to system apps, worked at the time
I've SBFed since, and it's working fine
Xeno62277 said:
I recently received a new phone (sent the other one back because it wouldn't boot/charge anymore). Anyways, I am not sure if this is something that was occurring on my previous phone or not, but if I install MOTODX2_Bootstrap_signed.apk (which is a package I have had forever... maybe there is a newer version or something?) everything works fine until I reboot. I can get into recovery and create/restore a backup, install .zip files, etc. However, after I reboot the phone the icon for System Recovery is no longer in my app drawer. I can re-run the .apk from my external SD card and everything works fine again... until I reboot. Anyone seen this?
BTW Stock 2.3.5 1.3.418
Click to expand...
Click to collapse
moving the app to your phone
DROID DOES, Apple did...like I forgot when
Pixelation said:
moving the app to your phone
DROID DOES, Apple did...like I forgot when
Click to expand...
Click to collapse
I guess I didn't clarify... I am not running it from my external sd card. That is where I have the installer... I have to reinstall it after every reboot.
sd_shadow said:
I had that happen before, my solution was move it to system apps, worked at the time
I've SBFed since, and it's working fine
Click to expand...
Click to collapse
That fixed it... though I don't know what changed. I remember before just hitting the .apk on my external sd card, it installed, and I was fat and happy after that... go figure.
Thanks!
I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
rsdown said:
I am trying to upgrade from CM7 to CM10 using this guide: http://forum.xda-developers.com/showthread.php?p=35669871#post35669871
Got everything in place, get into recovery, start the backup, and that's as far as I can get because the backup hangs. If I use CWM, it gets to a point where it says "Baseline.par" and hangs, if I use TWRP it gets system backed up, gets to "Generating MD5 system.ext4.win" and hangs. I tried with an 2gb card & an 16gb card. Same results. I've let it sit for a good 45 minutes and nothing.
Not sure if this matters with it, but after I re-booted I forgot to swap out the cards & still had the one with all the files on it in the nook. The nook was not plugged in to USB. As it came back up, it gave a message that I had a "bad boot file (in memory)". Is this because I didn't have the USB cord attached? I've never gotten that message before.
I posted all this in the thread itself, so I apologize for a bit of a double post but I'm hoping someone might notice the problem if it's in it's own thread & I don't really think it has to do with loading CM10, anyway.
Suggestions? Thanks!
Click to expand...
Click to collapse
Use Titanium Backup to backup all your files. Or manually save them all on your computer then put them in the right spots when you update.