When I type "adb start-server", it shows "Daemon not running. Starting it on port 5037" and then after a few minutes shows "Daemon started successfully". After then, when I type "adb devices", it again shows "Daemon not running. Starting it on port 5037". After that, it either crashes, or shows the "ADB server didn't ACK" crap. I tried using "ABD cleaner" from these forums, checked the port, killed the task manually, nothing works.
Can somebody please explain what's going on?
I updated my Windows to 8.1 and the problem's over.
Sent from my XT1022 using XDA Free mobile app
Related
ok so i downloaded the SDK and the windows drivers. i downgraded the phone to rc29 and have just enabled adb on the phone using the command <enter>setprop persist.service.adb.enable 1<enter> and <enter>telnetd<enter>. i opened up CMD in windows and changed the directory where i needed and tried to run adb and it gave me this error: "* daemon not running. starting it now *
* daemon started successfully *
error: device not found"
why did it give me this error? and alo im stuck at the part where im supposed to "copy a busybox binary" using adb push. i dont know exactly what im supposed to do to do that step. i am a noob at this stuff so please be kind and use noob terms and steps.
Thanks
PS: i did connect the phone to the pc with the data cable and the add new hardware thing popped up and i installed the drivers like i was supposed to. it said something about they were installed correctly but may not be working properly, whatever that means.
Try this....
Unplug the phone.
Reboot the computer.
When fully rebooted, plug the phone back in and see what the computer does.
Did it say, "Found new hardware" or some such message?
Did it say that it couldn't find a driver?
Okay - after the OTA updates, I'm now having the same problem! Ouch!
Plugging in, running DOS Command...
c:\> adb devices
Reports that there are no devices attached!
BUG!!!!!!!!!!!!!!!
So I've been playing around with the Beta VI build of Gingeritis and was going to change out the bootanimation to go back to the stock one, and adb isn't functioning for me all of the sudden. USB Debugging is flipped on on the device so I'm not sure what's up.... anyone else having this problem?
Flashing a rom won't bork your adb. Use cmd prompt to get into your adb directory & type "adb start-server" (without quotes), connect phone to computer, then type "adb devices". What does it say
Sent from my ADR6400L using XDA App
That's what I thought, however it seems there's something not quite right here:
G:\temp>adb kill-server
G:\temp>adb devices
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
List of devices attached
G:\temp>adb devices
List of devices attached
G:\temp>
Go to settings > wireless & networking, enable internet passthrough mode
Sent from my ADR6400L using XDA App
Yup that's what I was missing - installed the driver and adb picked back up again. Weird that the drivers between the kernels changed, wonder if it's just because that gingersense kernel is based off another device and not the T-Bolt.....
hi all. for some reason, my adb is glitching.
nothing is hooked up, but it says
"list of devices attached 0123456789abcdef offline"
sooo, i cannot connect anything. i have files from where i was running virtualbox, could that be causing the problems?
Does this persist even after a reboot? I had some funky problems with my drivers... What OS is your desktop on?
Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app
Already check your cable?maybe your cable does not support to transfer data beetween your phone and PC.
Make sure you have connect as a 'MTP' or Try to connect as a 'USB Mass Storage'
If you have tried all the ways,the last way is to backup your phone and do factory reset,or it will be BETTER if you bring your phone to serviceperson,because maybe there is an issues on your hardware.
jasonmerc said:
Not sure what happened, but all of a sudden whenever I plug in my Blu Studio X+ into either one of my computers with USB Debugging enabled I get a pop up saying the USB device is not recognized, and it shows up in the Device Manager as an Unknown Device. I've tried updating the driver manually, but every time I navigate to an INF file in the driver installation dialog it tells me the specified file contains no information on the device. Doing an "adb devices" command returns nothing, and "adb shell" returns "error: device 'null' not found".
Sent from my STUDIO X PLUS using XDA-Developers mobile app
Click to expand...
Click to collapse
You seem to have a lot of driver problems considering the number of threads you made
Go to device manager with your phone plugged in and uninstall every driver that has to do anything with your phone.
Unplug phone.
Reboot your PC.
Now plug phone back in and wait for the automatic driver installation to complete (doesn't matter if it succeeds or not).
Click here to download the latest driver (download it even if you have already).
Disable USB debugging and enable it again and wait for the automatic driver updater if it opens.
Open device manager and manually select the .inf file for your device.
If you don't know which device is your phone, unplug the phone and plug it back in and watch which devices disappear and then reappear again.
Also updating to Ubuntu, as your profile picture suggests, should ease the ADB driver installation and reduce ADB problems
Got it figured out. Wiped all ADB drivers and reinstalled, then downgraded my system-wide ADB from 1.4.2 to 1.3.
Sent from my LG-D415 using XDA-Developers mobile app
Hi,
I'm currently trying to use adb to pull some data from my phone but i always get "error: closed". Im running it from cmd.
When I use the command "adb devices" to see if my phone is connected, I get something different from the others is i am getting
List of devices attached
XXXXXX sideload
instead of what most other people got
List of devices attached
XXXXXX device
Is this a problem? What am i missing? Thanks a lot for ur time in reading this