I put in windows powershell the command: adb connect [myj3ip]:5555 and it answers
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
unable to connect to 192.168.1.4:5555
Why?? Debug usb is enabled, so why?
Related
First off i apologise for any newbie questions. I have just acquired an xperia play (first smartphone ) and i have been trying to use sdk to setInstallLocation 2. I have installed sdk the .zip version (unziped to desktop) and installed the sdk platform tools revision 3 plus enabled the google usb driver package. I conect my phone to the pc (in debugging mode) and mount my sd card (so pc companion sees my phone) (also tried unmounted)
My problem is when i try to adb devices in cmd (as admin) the following error appers
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
so i have followed a few tips i have seen when googling the error. So i start the task manager and end the adb.exe process and then when i try again with adb devices now it says
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not runningerror: cannot connect to daemon
but when i installed sdk platform tools revision 3 i noticed when it asked to restart adb that deamon tools was loaded in sdk successfully. Any ideas/help would be greatly appreciated?
Moz
Could you post a screenshot of cmd?
Yeah i tried removing http:// and put spaces every where but it stil realised it was an outside link lol. Anyways i can post it now. So here it is.
After the first fail. I did as i said before ended the task in the task manager and then tried again but got the second error. Even if i run cmd not as admin its still the same
You could post only part of the URL, if you leave out the beginning with "http://www." you should be able to post it. And your next post will be number 8 so you can always edit the post afterwards.
Just picked up a Fire today...
Can't seem to get ADB to recognize it on Mac 10.7.
Installed the SDK, running adb from directly inside platform-tools.
I have adb_usb.ini in ~/.android with the correct id line inside.
If I try to do ./adb devices while the Fire is connected, I get:
Code:
* daemon not running. starting it now on port 5037 *
ADB server didn't ACK
* failed to start daemon *
error: cannot connect to daemon
That's after doing ./adb kill-server and ps ax | grep adb to make sure it's not still running.
Any ideas? It runs correctly (no SERVER DIDN'T ACK message) when I run ADB without the Fire connected, but it still doesn't come up in the device list.
Edit: I got hold of a windows computer and was able to use the Kindle Fire Utility without issue. Not sure what's going on with Lion.
.
I have been trying to get adb working on my Win10 machine for a long time and just can not figure out what is wrong.
I have adb installed in c:\adb and my USB drivers are working. I can browse the phone from the PC.
But no matter what I try when I try to adb, I get this:
.
C:\adb>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
** daemon still not running
error: cannot connect to daemon: No error
error: cannot connect to daemon: No error
C:\adb>
Click to expand...
Click to collapse
(Yes I do have USB debugging ON and OEM ON)
It is weird because it says daemon is nOT running then it tries to start
it and says daemon started Successfully ... then it says daemon still
nOT running. That makes no sense to me ?
Please any thoughts on this ???
Thanks
.
.
hello, i have a problem with sideloading android apps to my moto 360. i used the guide from google to connect it with bluetooth, but i get this output:
Code:
C:\Windows\system32>adb devices
List of devices attached
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
01daca4ec2a31f39 device
C:\Windows\system32>adb forward tcp:4444 127.0.0.1:/adb-hub
C:\Windows\system32>adb connect 127.0.0.1:4444
connected to 127.0.0.1:4444
C:\Windows\system32>adb devices
List of devices attached
01daca4ec2a31f39 device
C:\Windows\system32>
the device i use to plug into my computer is a nexus 5x with O developer preview (rooted).
thanks for any help! im really excited about playing hill climb racing on my watch
i follow this guide on my non-rooted phone but not working>> http://stackoverflow.com/questions/2604727/how-can-i-connect-to-android-with-adb-over-tcp
Here is my Output
[stark]:~|$ adb kill-server
[stark]:~|$ adb tcpip 5555
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
[stark]:~|$ adb connect 192.168.43.1:5555
connected to 192.168.43.1:5555
[stark]:~|$ THEN I REMOVE USB^C
[stark]:~|$ adb shell
**error: device not found**
Click to expand...
Click to collapse
I tried many times but always getting error that device not Found
I have Android N, Current OS: Ubuntu, ADB version: 1.0.31
*when i had MM (no root) this method works fine, but after upgrading to N, not working