• After 15+ years, we've made a big change: Android Forums is now Early Bird Club. Learn more here.

Root Command Prompt : Adb Devices error

i have a mytouch 3g first edition and i type adb devices in cmd and it only says list of "available devices" does not show my phone. any ideas?

thanks
 
hiee guys
i own micromax a60
i have installed adb drivers of it
when i use
adb deices
i get a error
-------------------
list of devices attached
? devices
--------------------
why is it soooo
 
Hi nikhil -

This is the Droid X forum, so we won't be a lot of help to you.

What I can tell you is that you need two things to get ADB to recognize your device:

- The manufacturer-provided drivers for your device
- And turn on USB debugging on your device (go to Settings > Applications > Development, check off USB Debugging)
 
Hi all,

All the above advice have been terrific; however, I've run into the problem of my command prompt in Windows 7 x64 not being able to recognize "adb" but ok with "adb.exe". Any insight? Thanks in advance for your help.

Drew
 
droo said:
Hi all,

All the above advice have been terrific; however, I've run into the problem of my command prompt in Windows 7 x64 not being able to recognize "adb" but ok with "adb.exe". Any insight? Thanks in advance for your help.

Drew
Click to expand...

Drew, welcome to the AndroidForums.

Sounds like either Windows has strangely lost its association of programs with a .exe extension or perhaps you have another file in your directory named "adb" that was mistakenly created (which would explain why an explicity reference to adb.exe works).

If you type a "dir adb*" command, do you see more than one item displayed?

Also, are you trying to run the adb command from the same directory in which it lives or do have its path added to the PATH environment variable?

Anyway, some things to check...good luck!

Cheers!
 
Hi scary alien =)

Thanks for the response. My problem appears to be not only with adb, but any .exe file. Example - "java" is not recognized, but "java.exe" is. I'm trying to root my phone and hence I'm concerned that there is something more fundamental wrong and didn't want to proceed with the possibility of bricking my phone.
The Path is ok; I can call up "adb.exe" from any directory. The "dir adb*" doesn't seem to work; it appears to only search for adb files in the directory I'm immediately in.
Again, thanks for your help!
Drew
 
droo said:
Hi scary alien =)

Thanks for the response. My problem appears to be not only with adb, but any .exe file. Example - "java" is not recognized, but "java.exe" is. I'm trying to root my phone and hence I'm concerned that there is something more fundamental wrong and didn't want to proceed with the possibility of bricking my phone.
The Path is ok; I can call up "adb.exe" from any directory. The "dir adb*" doesn't seem to work; it appears to only search for adb files in the directory I'm immediately in.
Again, thanks for your help!
Drew
Click to expand...

Drew, hey no problem...I wish I could have been more help...

I did a quick Google search of "windows lost exe file association" and found more stuff (and scary stuff) than you probably want to see. Try this search and see all the results you get...you'll have to sift through the stuff that seems to match your circumstances (I would hate to hazard a guess here...remote debugging is such a pain, LOL).

Good luck with your rooting efforts!

By the way, you know this is the Droid X forum, right? ;) I'm guessing you have a different device (which is cool, but we should probably try to throw in a DX reference to keep the Guides (LOL=me ;)) or Mods (:eek:) happy:

"Hey, the Droid X is a pretty sweet device, eh" -- mission accomplished :)

Cheers!
 
When you install the sdk file, the adb is no longer in the "adroid-sdk/tools" folder. There is a text document in the android-sdk folder saying it moved to "android-sdk/platform-tools". My "android-sdk" folder is in my "program files" in a folder I named "android."

so, for example: cd c:\program files\android\android-sdk\platform-tools\

I had the same issue today, then i found that note in the android-sdk folder about the adb stuff moving. So, you must use "platform-tools" folder.
If you do not have Android-SDK", search for it on google. It will show up. I hope this helps.
 
GiMortal5 said:
When you install the sdk file, the adb is no longer in the "adroid-sdk/tools" folder. There is a text document in the android-sdk folder saying it moved to "android-sdk/platform-tools". My "android-sdk" folder is in my "program files" in a folder I named "android."

so, for example: cd c:\program files\android\android-sdk\platform-tools\

I had the same issue today, then i found that note in the android-sdk folder about the adb stuff moving. So, you must use "platform-tools" folder.
If you do not have Android-SDK", search for it on google. It will show up. I hope this helps.
Click to expand...

Welcome to the AndroidForums, GiMortal5.

Yeah, subsequent to the above post, I whipped-up some notes about how to get the adb utility installed:

http://androidforums.com/faqs/443072-adb-guide-updated-12-05-2011-a.html

This might be easier for folks (also, the middle section has a downloadable .zip file that has the adb and fastboot utilities for Windows, Mac, and Linux platforms).

Cheers!
 
You must log in or register to reply here.
Back
Top Bottom