Results 1 to 10 of 10
  1. Thread Author  Thread Author    #1  

    Default Daemon not running. ADB server didn't ACK

    SO i have the HTC inspire. which as you all know doesn't have the "Unknown Sources" button ata ll. so i downloaded the Sideload Wonder mAchine which would be awesome to use if i could get my phone to work with it. when i run the USB driver status it says
    daemon not running. starting it now
    ADB server didn't ACK
    failed to start daemon
    error: cannot connect to daemon

    i also downloaded HTC sync and my device can not be found on that either.
    please help i am VERy new to this process so any and ALL ideas will be great. and if the answer seems obvious please let me know i literally just plugged my phone in for the first time to my computer and tried using the Sideload wonder machine
  2. #2  
    DroidXcon's Avatar

    Posts
    11,645 Posts
    Global Posts
    11,775 Global Posts
    ROM
    Stock for now

    Default

    Quote Originally Posted by newbiehacker View Post
    SO i have the HTC inspire. which as you all know doesn't have the "Unknown Sources" button ata ll. so i downloaded the Sideload Wonder mAchine which would be awesome to use if i could get my phone to work with it. when i run the USB driver status it says
    daemon not running. starting it now
    ADB server didn't ACK
    failed to start daemon
    error: cannot connect to daemon

    i also downloaded HTC sync and my device can not be found on that either.
    please help i am VERy new to this process so any and ALL ideas will be great. and if the answer seems obvious please let me know i literally just plugged my phone in for the first time to my computer and tried using the Sideload wonder machine
    open up the computers task manager, find adb process and kill it, then try again
    If i've made life easier buy me a Macchiato
    Thanked by 2:
  3. Thread Author  Thread Author    #3  

    Default

    my process do not have that even listed
  4. #4  
    DroidXcon's Avatar

    Posts
    11,645 Posts
    Global Posts
    11,775 Global Posts
    ROM
    Stock for now

    Default

    Quote Originally Posted by newbiehacker View Post
    my process do not have that even listed
    Try rebooting the computer
    If i've made life easier buy me a Macchiato
  5. Thread Author  Thread Author    #5  

    Default

    Quote Originally Posted by DroidXcon View Post
    open up the computers task manager, find adb process and kill it, then try again
    it had that listed earlier when i tried connecting to HTC sense so i killed it and it hasn't reopened yet
  6. Thread Author  Thread Author    #6  

    Default

    damn. never thought it would be that simple. Alright. thanks so much you save alot of grief for me
  7. #7  

    Default

    Your PC won't allow ADB to use port 5037. DroidXcon has listed the right steps to take.

    If they don't work, you're going to have to see why your computer can't/wont allow ADB to use port 5037.

    It's a local connection, so your firewall shouldn't come in to play, but check it anyway.

    EDIT: Ignore this, looks like you have it sorted
    ಠ_ಠ
    제리
  8. #8  

    Default Re: Daemon not running. ADB server didn't ACK

    Run over to sysinternals.com and pick up TCPVIEW and PROCESS EXPLORER, if you don't have them installed already.

    For some reason, the ADB daemon is terminating before the close socket exchange is complete. If you run (from the command prompt) "NETSTAT -o", you will see the socket (generally 5037) in CLOSE_WAIT state and the owning process number. Process Explorer won't show that process ID (the daemon terminated), and the process called adb.exe (which opened the socket) will be gone. (If adb.exe if found, try killing the task and see if things get cleaned up.)

    Using TCPVIEW, locate the hung socket. The process name column will show the associated process can not be found. Right click, and select "Close Connection". The socket is now closed, and the adb daemon should be able to start.
  9. #9  

    Default Re: Daemon not running. ADB server didn't ACK

    I tried everything, got frustrated and re-installed Eclipse + Android SDK .. still nothing.

    I then got a feeling it was my Firewall, and even though I had marked adb.exe as a trusted file, I shut the Firewall down (or so I thought) ..... still nothing.
    Only when I (after 2 frustrating days) uninstalled my Firewall and rebooted would I again be able to run my apps on the AVD.

    P.S. I used the Comodo Firewall
  10. #10  
    twburger's Avatar

    Posts
    1 Posts
    Global Posts
    4 Global Posts

    Exclamation Re: Daemon not running. ADB server didn't ACK

    Note to all: The Comodo firewall seems to have many issues with Android development tools.

Tags for this Thread

Posting Permissions

B