Welcome to the Android Central Forums Create Your Account or Ask a Question Answers in 5 minutes - no registration required!
Results 1 to 18 of 18
  1. Thread Author  Thread Author    #1  

    Default ADB device not found

    Need a little (lot) of help, I searched and still wasn't able to find a solution. I rooted using unrevoked 3, installed the SDK and was able to remove quite a bit of the bloatware successfully from my EVO. However I missed like 2 programs I wanted to remove. Now when I boot in to recovery I get a "error: device not found" message. I have not changed anything since I was able to successfully remove the other bloatware, I have USB debugging enabled, the SDK is installed and I have ADB setup in my environment variables. I am in the correct folder when I am using the command prompt. I tried removing and reinstalling the drivers, reinstalling HTC Sync, and all no go. I switched USB ports, and I verified that the port is working because it will let me go in to disk drive mode when on. (BTW I am on windows 7 32 bit) I also get an error when I try to use HTC sync (not that I actually wanted to use it, just trying to test alternatives) and it remains "disconnected". Can't figure out what to try next...any assistance would be greatly appreciated!!!!
  2. #2  
    trooper54's Avatar

    Posts
    1,411 Posts
    Carrier
    ACS Jelly Bean RC1, Stock

    Default

    You want to run the adb devices command in ./andorid-sdk/tools

    Just make sure thats right. I had a similar occurrence trying to run it in shell.
    jcole01272 likes this.
  3. Thread Author  Thread Author    #3  

    Default

    Quote Originally Posted by liquidjesus View Post
    You want to run the adb devices command in ./andorid-sdk/tools

    Just make sure thats right. I had a similar occurrence trying to run it in shell.
    Hmm, tried that, still having the issue. Did cd /android-sdk/tools and tried adb devices, but my EVO is not listed. Tried adb shell again and same device not found error message...
  4. #4  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    Quote Originally Posted by jcole01272 View Post
    Hmm, tried that, still having the issue. Did cd /android-sdk/tools and tried adb devices, but my EVO is not listed. Tried adb shell again and same device not found error message...


    its

    cd c:\Android-sdk/tools


    thats if you put it on the c:\


    Oh to add...

    do this ADB command...

    adb kill-server

    adb start-server

    adb devices

    you should see it connected
    jcole01272 likes this.
  5. Thread Author  Thread Author    #5  

    Default

    yep, for me it was actually cd c:\android\android-sdk\tools but no go...:-(
  6. #6  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    Quote Originally Posted by jcole01272 View Post
    yep, for me it was actually cd c:\android\android-sdk\tools but no go...:-(
    your slashes are wrong...

    cd c:\android/android-sdk/tools

    Try that...
    jcole01272 likes this.
  7. Thread Author  Thread Author    #7  

    Default

    Quote Originally Posted by d3xn2o View Post
    your slashes are wrong...

    cd c:\android/android-sdk/tools

    Try that...
    Totally worked...Thanks!!!!!
  8. #8  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    No prob dude...
    jcole01272 likes this.
  9. #9  
    trooper54's Avatar

    Posts
    1,411 Posts
    Carrier
    ACS Jelly Bean RC1, Stock

    Default

    lol, all a matter of getting into the proper directory

    Oh and ps.

    In win7

    when i type cd c:/andooid-sdk/tools it auto corrects to c:\android-sdk/tools
    XD
    jcole01272 likes this.
  10. #10  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    Quote Originally Posted by liquidjesus View Post
    lol, all a matter of getting into the proper directory

    Oh and ps.

    In win7

    when i type cd c:/andooid-sdk/tools it auto corrects to c:\android-sdk/tools
    XD


    Yea me too...

    I used to work for Canon

    You learn quick that / \ these symbols are very important...

    I was a Network Specialist for Canon Copiers BTW...
    jcole01272 likes this.
  11. #11  
    gksmithlcw's Avatar
    Software Engineer

    Posts
    457 Posts
    Global Posts
    1,889 Global Posts

    Default

    Quote Originally Posted by d3xn2o View Post
    your slashes are wrong...

    cd c:\android/android-sdk/tools

    Try that...
    Since when does Windows accept slashes in cmd in place of backslashes?

  12. #12  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    It matters if ur not on Windows 7
  13. #13  
    gksmithlcw's Avatar
    Software Engineer

    Posts
    457 Posts
    Global Posts
    1,889 Global Posts

    Default

    Quote Originally Posted by d3xn2o View Post
    It matters if ur not on Windows 7
    I've run Windows for a long time and it has ALWAYS used (much to my annoyance, I might add) backslashes in its file paths unlike every other OS which uses slashes.
  14. #14  
    12MaNy's Avatar
    Regional Leg Breaker

    Posts
    229 Posts
    Global Posts
    7,596 Global Posts
    Carrier
    Chroma - [N6p] [6.0.1]

    Default

    Make sure the sdk folder is on the root of your C drive and try this...
    Code:
    cd C:\android-sdk-windows\tools
  15. #15  
    gksmithlcw's Avatar
    Software Engineer

    Posts
    457 Posts
    Global Posts
    1,889 Global Posts

    Default

    Quote Originally Posted by 12MaNy View Post
    Make sure the sdk folder is on the root of your C drive and try this...
    Code:
    cd C:\android-sdk-windows\tools
    Yes, exactly. Backslashes...
  16. #16  
    trooper54's Avatar

    Posts
    1,411 Posts
    Carrier
    ACS Jelly Bean RC1, Stock

    Default Re: ADB device not found

    I'm telling you dude. In win7 I type it wither way and it auto corrects

    Sent from my PC36100 using Tapatalk
  17. #17  
    d3xn2o's Avatar

    Posts
    2,252 Posts
    Carrier
    4.1.1

    Default

    Quote Originally Posted by liquidjesus View Post
    I'm telling you dude. In win7 I type it wither way and it auto corrects

    Sent from my PC36100 using Tapatalk
    I believe you...

    Im just accustom to writing it correctly with both forward and back slashes...
  18. #18  
    gksmithlcw's Avatar
    Software Engineer

    Posts
    457 Posts
    Global Posts
    1,889 Global Posts

    Default

    Quote Originally Posted by d3xn2o View Post
    I believe you...

    Im just accustom to writing it correctly with both forward and back slashes...
    But there are no slashes in Windows directory syntax. They are all backslashes. It's really annoying because EVERY OTHER OS I've used uses slashes.

    So, again...

    Quote Originally Posted by gksmithlcw View Post
    Since when does Windows accept slashes in cmd in place of backslashes?
    I just want to know when this change occurred...

Posting Permissions