Related
I am doing some testing and writing scripts in GScript and was wondering if there is a power off or shutdown command (as opposed to reboot). I want a command that will literally just turn the phone off but it needs to be a command line command, not an app.
Thanks
Code:
C:\>adb shell
* daemon not running. starting it now *
* daemon started successfully *
# which shutdown
which shutdown
/system/bin/shutdown
http://www.computerhope.com/unix/ushutdow.htm
lol i tried "shutdown -k" and it shutdown my phone!
Code:
# shutdown -k wait
shutdown -k wait
mount: mounting tmpfs on /dev failed: Device or resource busy
mount: mounting sysfs on /sys failed: Device or resource busy
mount: mounting none on /dev/cpuctl failed: Device or resource busy
C:\>
When I try shutdown from terminal it just locks the phone up completely
+1
I too am trying to achieve phone power down using a script. But like you when I issue the shutdown command the phone immediately powers off and won't switch on again without a battery pull.
Same for reboot command.
I am using gscript lite and have s-off with a stock Froyo sense ROM.
"poweroff" generally works in linux systems. I haven't tried this in Android though.
"reboot -p"
GldRush98 said:
"poweroff" generally works in linux systems. I haven't tried this in Android though.
Click to expand...
Click to collapse
Poweroff works if run using busybox, however, the command needs parameters to run.
#poweroff (doesn't work)
#busybox poweroff (also doesn't work)
#busybox poweroff -d 8 -f (works!!)
The -d 8 delays by 8 seconds to give system a chance to stop processes and unmount filesystems, whilst the -f forces poweroff.
Works a treat using Gscript. Not sure if it harms the system as the busybox poweroff command does not use init. That may be a bad thing. I just don't know enough about Android/Linux to know that. Maybe someone else does???
"reboot -p" works.
"busybox poweroff -d 8 -f" works too.
"busybox poweroff -f" works.
If I use the power button to shut down it takes a bit of time, goes through a process. If I shut down using terminal, by the command reboot -p, the shut down is instant. Is there any harm in that, or is that ok to shut down like that?
I like to find ways to reduce the use of the power button, as some have reported it fails after time, but if it's not good for the system then I'll just shut down normally using the power button...
YES! "reboot -p" works for me
duskymagus said:
"reboot -p" works.
"busybox poweroff -d 8 -f" works too.
"busybox poweroff -f" works.
Click to expand...
Click to collapse
YES! "reboot -p" works for me
"reboot -p" has a possibility of harming the phone.
What if none of these commands work for my device?
reboot does work.
reboot -p does not, just returns to command prompt.
shutdown does not work (no such file)
poweroff does not work (no such file)
busybox is installed, but these applets are not installed
Is there any other way?
"adb shell shutdown"
AngelOfGrief said:
What if none of these commands work for my device?
reboot does work.
reboot -p does not, just returns to command prompt.
shutdown does not work (no such file)
poweroff does not work (no such file)
busybox is installed, but these applets are not installed
Is there any other way?
Click to expand...
Click to collapse
If you use adb:
"adb shell shutdown" - performs immediate shutdown
poweroff under su always worked for me.
Nothing works but reboot -p for abrupt shutdown on my phone..
It may cause harm
Bryce2010 said:
If I use the power button to shut down it takes a bit of time, goes through a process. If I shut down using terminal, by the command reboot -p, the shut down is instant. Is there any harm in that, or is that ok to shut down like that?
I like to find ways to reduce the use of the power button, as some have reported it fails after time, but if it's not good for the system then I'll just shut down normally using the power button...
Click to expand...
Click to collapse
Sometimes there are problems when you use reboot -p too often, like failure in file systems because they are not unmounted safely. I do not use this command very often. I only use reboot recovery for flashing roms. Just try not to use this command very often to prevent harm okay?
Current Phone/ROM:
Samsung Galaxy Ace GT-S5830/Cyanogenmod 10.1 RC1 by bieltv3
Recovery:
CWM v5.0.2.6
ROMs used in the past: CM9 RC2 by Maclaw, SGS2 v9 ROM, AOSP ICS ROM by Maclaw, PAC ROM(very disappointed with this, no play store included.)
reboot -p actually does a reboot
Hi there,
on my device
Code:
reboot -p
does shut down the device, but after a few seconds (like 2 or 3 seconds) it boots again. So actually it behaves like doing a normal reboot. Any ideas how I can fix this issue?
Thank you and kind regards,
ToBe_HH
Hello gyus,
is there any Android application to perform power off?
Thank you
The followin shut down my CM13 using the Cerberus shell. Very slick.
su -c 'am broadcast android.intent.action.ACTION_SHUTDOWN && sleep 5 && reboot -p'
from:
android stackexchange com/questions/73001/how-to-shutdown-android-via-ssh-command
gorlox said:
The followin shut down my CM13 using the Cerberus shell. Very slick.
su -c 'am broadcast android.intent.action.ACTION_SHUTDOWN && sleep 5 && reboot -p'
from:
android stackexchange com/questions/73001/how-to-shutdown-android-via-ssh-command
Click to expand...
Click to collapse
works perfectly, also with 'reboot' and 'reboot recovery'
I was messing around with the ONE-click-lag-fix thingy on this thread
http://forum.xda-developers.com/showthread.php?p=8353541#post8353541
someone posted a "fix"
""you can fix the jpk issue by doing this:
after the failure, reboot the phone.
then with root explorer delete the file linux.ex2 in folder /data/ext2 this will give you back the space
open terminal emulator on phone and type:
su
busybox mount -o remount,rw /system
press home button and reapply the lagfix.
wait...
profit!"
So I went into my phone in /data and found linux.ex2 (although it wasn't in /ext2 it was just in /data) and I deleted it
and used the terminal commands etc.
I reset my phone and it books into the logo then turns black and turns off
I don't have the 3 button recovery mode enabled... I have ADB and stuff though
WHAT do I do ?
Please oh please tell me I didn't brick my phone
Please tell me how to fix this and I will give you $50 or $100 paypal right away
If it is bricked, what do I do to go about getting it replaced ?
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
kalpik said:
Try: adb reboot recovery
And try a factory reset
Otherwise, you can boot into download mode by: adb reboot download and flash via Odin.
Click to expand...
Click to collapse
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
frankencat said:
You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix.
Click to expand...
Click to collapse
What do you mean? can you please explain this further?
what's mke2fs ?
Funkadelick said:
Where do I get ADB again (im at work) is there a tutorial ?
btw if this works Ill need your paypal info
Click to expand...
Click to collapse
ADB tutorial: http://forum.xda-developers.com/showpost.php?p=7239659&postcount=3
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I'm fairly new -- this is the problem
What do you mean "look" for it ? I can't even open up my phone -- it goes black on the boot screen (i shouldn't have deleted linux.ex2)
So I would assume this would be done through ADB ? I'm downloading it now
frankencat said:
WAIT!!!!!!!: Before you do anything else!!! Look for /sdcard/linux.ex2 and see if it exists. This should be a backup that can be restored. Copy this back to data and you should be good to go. Might take a while to copy but it should work.
Click to expand...
Click to collapse
I would need to know the commands to type to "restore" this file basically once I get ADB running
and if it works, please PM me your paypal info
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Funkadelick said:
I downloaded the android development SDK -- but when I ran it i got this: "Failed to fetch URL http://dl-ssl.google.com/android/repository/repository.xml, reason: dl-ssl.google.com"
Is this b/c I'm at work ? (firewall)
do I need to connect in order to use ADB ?
Click to expand...
Click to collapse
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
Jesus christ how did you know all this stuff ? gonna try it out ill let you know how it goes -- brb
frankencat said:
You don't need to run anything. Just download it and unzip the files to a directory on your computer like C:\android-sdk-windows
Then add the tools directory to you PATH setting
C:\android-sdk-windows\tools
Let me know if you don;t know how to do that and I will walk you through it.
Click to expand...
Click to collapse
I got adb up and running
but please explain (in detail) your solution you mentioned in the previous page --
"You can use mke2fs to re-create linux.ex2
Ex. mke2fs /data/linux.ex2
This could get you booted up again. Then you could uninstall/reinstall the lagfix."
Please in details explain what you mean and show commands. Thanks
frankencat said:
You said you have ADB so do this...hook up your phone and fire up a command window on you pc.
type in "adb shell"
this should get you into adb shell (duh).
next type "su"
Now enter the following one at a time on order. The last line will reboot your phone.
/data/lagfixtemp/busybox rm -rf /data/data;
/data/lagfixtemp/busybox rm -rf /data/system;
/data/lagfixtemp/busybox rm -rf /data/dalvik-cache;
/data/lagfixtemp/busybox rm -rf /data/app;
/data/lagfixtemp/busybox rm -rf /data/app-private;
/data/lagfixtemp/busybox mv /data/bak/data /data/;
/data/lagfixtemp/busybox mv /data/bak/system /data/;
/data/lagfixtemp/busybox mv /data/bak/dalvik-cache /data/;
/data/lagfixtemp/busybox mv /data/bak/app/app-private /data/;
/data/lagfixtemp/busybox mv /data/bak/app /data/;
/data/lagfixtemp/busybox mv /system/bin/playlogosnow /system/bin/playlogos1;
reboot
Click to expand...
Click to collapse
when I type adb shell I get
error: device not found
am I doing something wrong ?
I rebooted my phone (galaxy S logo / start up screen) then it goes black as usual -- then I connected the cable and ran ADB from CMD.exe and typed ADB shell and got that error
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
frankencat said:
Add C:\android-sdk-windows\tools to you computer's PATH...
- Open System Properties by right-clicking on My Computer
- Click on Advanced tab
- Click on Environment Variables
- Find PATH in System Varibles (bottom window) and open it for editing by either double-clicking or selecting it and clickin Edit button
- Scroll all the way to the end of the PATH string and enter a semi-colon ; at the end
- Paste the path to the sdk tools directory right after the semi-colon (C:\android-sdk-windows\tools)
- Click OK, OK, OK all the way out.
Now type "PATH" (without the quotes) in the command window and you should see the new path in the window. If not then close the window and open a new one. The tools dir should now be in the path and you are ready to use ADB.
Click to expand...
Click to collapse
I did all of this - i type in PATH and I see the new path etc.
But when i type adb shell it still says "device not found"
frankencat said:
You probably do not have have USB debugging enabled. Do you know if you eneabled that before or not? Also, did you make an nandroid backup before you started this?
And yes, it is because of Jesus Christ that I know this stuff.
<><
Click to expand...
Click to collapse
I don't think I enabled it -- as this happened spontaneously -- is there any way to fix this ? or am I seriously screwed ?
Not screwed, there is always a way.
Try this, pull your battery to power down your phone and then put the battery back in but DONT power it back up.
Now you have to do this all at the same time...hold down the up and down volume buttons and press down the power button. Hold all three buttons until you see the black Vibrant screen. KEEP HOLDING the up and down volume buttons until you see the yellow diags screen and then the green recovery screen.
Using the up/down volume keys to move, select "Reinstall Packages" and press the power button to select.
Tell me what you see...
Can anyone tell me the differences btn using reboot -p command and classic way by pressing power button?
reboot -p turns off the phone very quickly, I'm afraid that it's not good for the system
My Galaxy Ace, won't get on after I am execute command reboot -p through adb.
Thats still my big question, how to safely shutdown android through adb shell.
Rooted my kindle fire HD a few days ago using the QemuRoot method. Was working fine, and installed Google Play, etc. Everything was working well until this morning, when I get a blank screen upon startup. The words "kindle Fire" will be displayed and then it goes blank. I am suspecting that it was the apks I installed last night - It is probably the LCD Density Modifier, the Home Manager or the Go Launcher. At a loss what to do now - the reset using the power button doesn't work. Appreciate any help here.
Thanks!
Arithon said:
Rooted my kindle fire HD a few days ago using the QemuRoot method. Was working fine, and installed Google Play, etc. Everything was working well until this morning, when I get a blank screen upon startup. The words "kindle Fire" will be displayed and then it goes blank. I am suspecting that it was the apks I installed last night - It is probably the LCD Density Modifier, the Home Manager or the Go Launcher. At a loss what to do now - the reset using the power button doesn't work. Appreciate any help here.
Thanks!
Click to expand...
Click to collapse
Does your device show up in adb? If it does you can remove those apps(especially the first two) using adb:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up the name of the apk:
cd /system/app
ls *.apk
http://www.careace.net/2010/05/12/ho...s-through-adb/
Which file ?
Thanks for your input. yes, the device show up in ADB. trouble is the list of apks does not right a bell. My fear is the LCD density app changed the display format - and that's why it is a blank now. Is there any way to reset it to factory defaults using ADB??
Trying to output a list of the apps if I use ls *.apk - how I copy the list out of command shell (windows)? Sorry, last time I touched unix seriously was back in 92.......:silly:
onemeila said:
Does your device show up in adb? If it does you can remove those apps(especially the first two) using adb:
adb shell
su
mount -o remount,rw -t rfs /dev/stl5 /system
rm -r /system/app/[AppName].apk
mount -o remount,ro -t rfs /dev/stl5 /system
If you need to look up the name of the apk:
cd /system/app
ls *.apk
Click to expand...
Click to collapse
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Try to clear dalvik cache, so that it gets rebuilt. Then try again. If you don't have CWM installed, you might as well be able to do it manually, but unfortunately I don't know the commands for that atm.
luuk.vandeven said:
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Click to expand...
Click to collapse
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Allright, it all sound really complicated to me. I will do my very best! But how exactly do I boot my phone in stock recovery mode, volume up and power button at the same time?
Bogeyof said:
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Click to expand...
Click to collapse
luuk.vandeven said:
Allright, it all sound really complicated to me. I will do my very best! But how exactly do I boot my phone in stock recovery mode, volume up and power button at the same time?
Click to expand...
Click to collapse
Vol- & Power. Vol+ & Power will bring you to "Emergency mode", this might work as well. Just make sure you have adb access.
Hello
Thanks for the guidance' the only thing is that "adb push busybox /sdcard/" is not recognized so I pushed the file into /temp I created and then continued accordingly
yishay said:
Hello
Thanks for the guidance' the only thing is that "adb push busybox /sdcard/" is not recognized so I pushed the file into /temp I created and then continued accordingly
Click to expand...
Click to collapse
Normally u can push directly through /data/local without the /sdcard step. But its ok to push it to any other local tem-folder before moving it to /system/xbin...
Search for total commander the pc version and the adb plugin then you can access the phone file system, il post what next to do,
* total commander - http://www.ghisler.com/ - officall free version
adb plugin -- http://www.totalcmd.net/plugring/android_adb.html
---------- Post added at 03:53 PM ---------- Previous post was at 03:43 PM ----------
basically what you need to do is said in this extract from a previous post i had done
open total commander and then click configuration and then click options then next click the plugins tab followed by the the WFX button,
then point it at the installed adb plugin,
Once you have done that click the Drive tab in total commander it will be set a drive C:/ and change to Network Neighbourhood, now go to your phone and plug in your usb lead while powering it up and holding the power key and volume up and not releasing until it starts.
Now in total commander click adb in the explorer part and it access you into your phones file system so click on the root folder then click the system folder and then click the Xbin folder i replace the busybox inside with the busybox file which is in o4xr
Please
Hello,
Thanks for the support, but I don't understand anything from your post. I'm not a real geek, and know how all this stuff works, so my phone is still dead. Lg won't take it back for repair, and other phone companies can't manage to fix my phone. So can you please give me some more specific instructions, sorry that i'm a noob, but I miss my phone .
I only understood the 'download the onxr4 file and extract it', after that I lost it:silly:.
Bogeyof said:
I had the same problem. You can start the P880 in stock recovery and connect it to pc. After the drivers are installed, you have access via adb. Because you installed busybox, i think your device is rooted. So you cann access your P880 with "adb shell", in the shell "su", then you have to mount system and you can push another busybox (e.q. from root, the o4xr directory contains a functionally busybox) to your phone (/system/xbin)
Just download o4xr.zip from the "How to Root" thread.
Then do the following:
- extract o4xr.zip and switch to that folder
- adb shell "su -c 'mount -o remount,rw -t ext4 /dev/block/mmcblk0p33 /system'"
- adb push busybox /sdcard/
- adb shell "su -c 'cat /sdcard/busybox > /data/local/busybox'"
- adb shell "su -c 'chmod 777 /data/local/busybox'"
- adb shell "su -c 'cat /sdcard/busybox > /system/xbin/busybox'"
- adb shell "su -c 'chmod 777 /system/xbin/busybox'"
- At this point the device will reboot itself automatically (Don't know why?), if not: adb shell 'su -c reboot'
- Delete /sdcard/busybox
- Done
I´ve done all this and its booting again with no problems....
Click to expand...
Click to collapse
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Kdz flash
luuk.vandeven said:
Hello,
I downloaded the latest version of busybox on my o4x, after I downloaded that, I turned off my device. When I tried to turn it back on, it got stuck on the 'loading apps' page, so I can't basicly do nothing with the phone. I let it load apps for like 10 hours (while on the charger) but that didn't work, and I let my phone run out of battery and after a couple of hours turn it back on, that also didn't work.
Does anyone know how to fix it, or can at least tell me what the problem is?!
Thanks,
Luuk
Click to expand...
Click to collapse
do the kdz flash. Easiest and safest. Worked for me with the same prob like you.
Did that
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
OS_Hacking said:
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Click to expand...
Click to collapse
luuk.vandeven said:
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
Click to expand...
Click to collapse
Why don't you just send it to LG for repair. They'll fix it for you and you'll get it back as good as new. And after you have done that, stop messing around with busybox.
luuk.vandeven said:
I already did that al long time ago, didn't work though. I'm considering to buy a new phone, I've been having these prpblems for several weeks now.
Click to expand...
Click to collapse
What doy exactly mean? You tried that but didn't work or you are unable to do a kdz flash? Please be clear.
!!
OS_Hacking said:
Try reflash the *.KDZ .
See this thread :-
http://forum.xda-developers.com/showthread.php?t=2069723
Then boot into recovery [ (power on) + (vol-) ] .
Then wipe cache ,, and do factory resert . This will delete all your apps .
Good Luck .
Sent From LG-P880
Try Use THANKS Button If I Helped
Click to expand...
Click to collapse
Dude...
You are my man! I've got the problem solved, so thank you!!