Hi!
I have a problem - when I start ADB it's work, but when I unlock my phone ADB crashes. I have android 4.0.3 and ADB on phone 1.0.29, ADB on PC is 1.0.31. I tried to update PC drivers and ADB, but it didn't help me. Before all of this ADB showed that my device is offline.
What can I do?
Hello XDA-Developers,
I have a problem
I have an android phone Jelly Bean 4.1.2
I already installed the drivers of my phone to my computer, when i plugged the cable i enable USB DEBUGGING.
after that i checked device manager and my phone is listed under Android Phone
After that i go the console and type adb devices it starts the server and returns an empty list
i tried everything
i also try kill-server and start-server still the same
PLEASE HELP
then
Maybe try a different usb slot. One directly on the motherboard, it sometimes helps.
Alright, I've tried installing the drivers from Verizion and also using the drivers from the Android SDK and either way I have the same problem. ADB devices shows my phone, however whenever I try to push, pull, or reboot (the only commands I have any use for atm) the command prompt hangs like it's trying to access the device but no matter how long I leave it the device will not reboot, nor will any files appear in the correct folders on either the device or my computer.
I'm trying to root my phone and this is a pretty major roadblock.
Note:
USB Debugging enabled
ADB drivers installed
Phone shows up on "adb devices"
There is no error or any other output in the console. The best way to describe this problem is that ADB hangs.
I'm running Windows 8.1 and my phone is running Android 4.1.2
Also, I don't know if this is normal but, In order to get the notification that "USB debugging connecting" I have to use the internet connection option on the phone. When using MTP, Charge only and PTP that message doesn't appear and I don't see an ADB device show up in device man.
Things I've Tried
Uninstalling all Android drivers and redownloading/installing them after restart
Restarting my phone multiple times
Running adb kill-server / adb start-server
Changing USB ports7
Thanks!
Try installing drivers from LG. This seems the right one but double check:
http://www.lg.com/us/support-mobile/lg-LGVS930
I recently installed Remix OS for PC onto a PC and am using an ethernet port to try to adb into the device ('adb connect 192.168.1.xx:5555'). It times out and does not connect. I have run 'setprop service.adb.tcp.port 5555' and it still times out. Any thoughts on how to get adb to work?
Hello everyone. I had my Stratos stuck in the "solar system" start up (just after the Amazfit Symbol).
I tryed some of the solutions presented here, but after the achived of FastBoot mode in the watch, i can't conect to PC due to am lack of Android 1.0 driver.
I connect the watch, the Windows 10 Home edition system "catch" the conection, but apears an Android 1.0 and Unknown USB device. Can someone help me to solve the problem please?
Thanks
Tugaspitfier said:
Hello everyone. I had my Stratos stuck in the "solar system" start up (just after the Amazfit Symbol).
I tryed some of the solutions presented here, but after the achived of FastBoot mode in the watch, i can't conect to PC due to am lack of Android 1.0 driver.
I connect the watch, the Windows 10 Home edition system "catch" the conection, but apears an Android 1.0 and Unknown USB device. Can someone help me to solve the problem please?
Thanks
Click to expand...
Click to collapse
Boot the watch as usual and try a factory reset with
Code:
adb reboot wipe
Saratoga79 said:
Boot the watch as usual and try a factory reset with
Code:
adb reboot wipe
Click to expand...
Click to collapse
Hello Saratoga79.
Thanks for your reply.
The problem is Windows don't conect to Startos.
In Windows System, (when i connect the stratos in Fastboot), apears the USB with an yellow exclamation mark in Android 1.0 driver.
What i can understand is, in fastboot the watch tryed to connect to Windows, but Windows donĀ“t have the correct driver to acept the conection.
I already tried to instal several USB drivers, but the final result is the same.
When i run adb he stops in "Waiting for Conection" step.
The solution you present works even in that situation (windows with the exclamation sign on Android 1.0 USB driver)?
Thanks in advace.
when in fastboot, you need to install "adb testing device" or "adb fastboot device" for the android 1.0 device.
If your watch got detected by "android adb device" and now it goes for "android 1.0" device, just manually install the drivers.
Saratoga79 said:
Boot the watch as usual and try a factory reset with
Code:
adb reboot wipe
Click to expand...
Click to collapse
Hello Again Saratoga79
I follow your advice and needed to do just one more step.
adb -d shell (and then adb reboot wipe)
After that i have a brand new watch
Thank You for your assistance
Best Regards and Happy Xmas