ADB not finding my device.. Used to?

Discussion in 'Android Support' started by n0m0n, Nov 12, 2010.

  1. n0m0n

    n0m0n Member

    Nov 5, 2009
    Likes Received:
    Trophy Points:
    Starting ADB Server...
    *daemon not running. stating it now on port 5037*
    *daemon started successfully*


    Waiting for device

    And waiting...
    Something must be wrong becuase I have not gotten past waiting.
    I do have USB debugging connected...

    What might be wrong?

    OK I just opened a CMD prompt and typed adb devices
    This is what I got in return.

    C:\user\n0m0n>adb devices
    List of devices attached


    Does that mean ??? adb is working or isn't becuase I have my Droid2 and gTablet plugged in?

    Now I have re-flashed my Droid2 with RSD Lite and the stock SBF already so I don't know why I can't get the PC to see or find the serial # of my device that is plugged in.

    Can anyone advise?

  2. teddyearp

    teddyearp Senior Member

    Jan 13, 2010
    Likes Received:
    Trophy Points:
    Pinetop, AZ
    Current Phone Model:
    Motorola XT1103 (Nexus 6)
    Are you the one who posted a while back with the same thing as I have italicized? And the part of your message that I bolded above makes me wonder as well. I have never seen adb specify a port while connecting to my phone.

    I guess first off is to make sure of your drivers. I am sure you have them installed, but sometimes actually opening up the driver in your start menu and then selecting "clean and re-install" followed by a re-boot of your computer can fix some of these types of issues.

    Also, try NOT having the gtablet plugged in at the same time. Maybe try a different USB port. The Droid is pretty fogiving, but sometimes we have to resort to the same types of tactics as with the old razr to get stuff to work properly.

    good luck
Search tags for this page
* daemon not running. starting it now on port 5037 * * daemo
adb devices daemon not running
adb wait for device

adb waiting for device

daemon not running starting it now on port 5037
daemon not running starting on port 5037

daemon not running. starting it now on port 5037

daemon not running. starting it now on port 5037 *
daemon not running. starting it now on port 5037 daemon star
starting it now on port 5037