I followed the basic instructions for doing screen captures with the SDK since the other capture apps are not working. My g-tab does not show up in the list when i run ddms. what drivers do i need to install to get this working. USB Debugging is enabled.
Ok i found this information.. but i do not have a usb_driver folder.
Nevermind... Im an idiot. Still recovering from thanksgiving.
Related
Hello
I have a stock Vodaphone Magic and I'm looking to root it, but to do this I need to get adb to see it, which I'm having problems with.
When I plugged it in first to charge it used window's default drivers for the SD card etc. Trying to update the drivers with the ones included in the SDK dosn't seem to work as Windows says that they're less recent.
Also, I can't see any sort of "ADB" section in the device manager, even with USB debugging turned on in the phone.
Any help? I'd really like to root my phone so I can use WPA Enterprise!
Edit: Already read the wiki page, no help.
I remember having this problem when I first set up the Android SDK.
However in my device manager I did have a device, it wasn't called Android or Magic or anything similar. From what I remember it was a bunch of random letters and numbers.
From there I right clicked it, went to Properties, Update Driver and then pointed it to the directory with the drivers.
Thats how I did it in Windows 7, if that doesn't work for you then I'm not sure sorry.
Hi,
I recently had the same problem as you. The first time you plug in your phone sometimes Windows will assign USB drivers to the device instead of the ADB interface. To correct this, I uninstalled the drivers and pointed the computer to the ADB files as the new drivers. After those install it should be labelled correctly and work.
How in the heck do I do it?
It has no problems recognizing my Dream, but N1 is non-existent to it. I can get Fastboot to recognize it. Help!
I have the latest SDK installed and everything.
Any ideas?
USB debugging is enabled.
first of all you need to download the 3rd release of ADB usb driver. Just download the android SDK and run the androidsdk.exe and update everything to latest version.
Next go to device manager, select your nexus one, press update driver. direct it to where your android sdk usb_driver is (example C:/AndroidSDK/usb_driver), make sure include subfolder box is checked, and update!
Just posted that.
http://forum.xda-developers.com/showthread.php?t=613054
Thanks, guys!
I finally decided I'm going to root my nexus. Everything seems very simple, except one small problem. I don't have the USB drivers installed. No biggie, I downloaded the 2.1 SDK that supposedly had the USB drivers in it. But for the life of me I can't freaking find them.
As I understand it they should be located at :
C:\AndroidSDK\USB driver\
Unfortunately, inside AndroidSDK there is no USB Driver folder. In fact, no where in the subfolders is there one either. Now perhaps I'm just a total idiot and am missing something, but I've been trying to figure this out for the last 40 minutes and cannot find the damn drivers.
Can anyone tell me how dumb I am? Please?
The USB drivers are a separate download. It's way down the list of things you tick when choosing what to install.
Heh... as above, run the SDK setup and tick the USB drivers.
Then they'll be in \SDK\USB driver\
worth noting if you're on windows 7 x64 you'll need to dl both 32 and 64 bit versions of java jdk to get the actual sdk to run to download the drivers.
then make sure usb debugging is on, and you're away from there
Best way to get the ADB drivers installed correctly is to just install the PDAnet client for your computer. It'll install the correct drivers per your OS.
http://www.junefabrics.com/android/index.php
Thanks guys, you're awesome!
I just downloaded DroidExplorer, and it installed everything I needed for the SDK/ADB. Saved me alot of precious time..
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
I honestly didn't expect this to work, but since I didn't have any better ideas, I might as well try it. Man was I wrong.
The reason I did not think this would work is that I had downloaded the Moto Drivers (just the drivers, not the full MotoConnect software) from the Moto website. I did not expect there to be any difference.
Evidently the software on the phone does have more drivers than the downloadable package from Moto.
Thanks for the help.
I've tried doing this...turning off Dev mode, and turning on USB Mass Storage mode, but still no motoconnect setup screen comes up. Any other way to get those drivers installed?
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
Like Zaphod, I very much appreciate the help and did not expect this to work lol. Thanks much.
Yesterday at work I couldn't get into adb either because the devices drivers no longer loaded. I had to edit the driver inf file. It seems like the usb diver id changed.I'm on my phoebe right now and works rcd wasn't working anyway. You can get the new id if you open up device manager sand open the properties for the phone.the last tab has device details and the first or second has the new id. Just add that in the inf. Should look like the other entries. Just try adding rfd drivers with that new inf.
media sync mode gets you adb.
might say driver not installed when you click on it but adb will startup and work properly.
least on mine it does. win7 64bit
anthonygill13 said:
Hello,
If you put your phone into mass storage mode without development mode you will get a cdrom with motoconnect setup. Run that and fully install and then unplug out into dev and change to pc mode. Adb is all yours.
-tony
Click to expand...
Click to collapse
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this
drewlamo1 said:
while i got adb using the method i described above, this is still a nice find lol
i would of nvr saw this cause im always in debugging mode .
thanx for this
Click to expand...
Click to collapse
cant get it to work, ive tried all the above? keep getting error: device not found
Zaphod-Beeblebrox said:
I managed to get my Froyo on and still keep root.
However, when in debug mode, my computer will not recognize/install driver for the X. I've uninstalled and re-installed the drivers a couple of times, and even tried to manually force it to see the Moto Composite ADB interface.
If I turn off debug, the drivers load just fine (but of course no ADB that way).
I'm on Win7 x64.
Any suggestions?
-Z
Click to expand...
Click to collapse
change from pc mode to media sync mode in the notification window
If turning on and off USB Debug mode doesn't work, then do this, it will almost certainly work:
http://alldroid.org/default.aspx?g=posts&m=7662#post7662
teenfaces said:
change from pc mode to media sync mode in the notification window
Click to expand...
Click to collapse
Exactly as this is the fastest and simplest way to fix it. I freaked about about a week ago when my X would not work threw ADB anymore and that is the trick that took care of it. And it is proven to work it has been posted hundreds of times on many other site/forums.
I have a Kindle Fire which I would like to connect to via ADB, but the settings menu does not even have a box for USB debugging. Amazon also does not have ADB drivers, though I'd guess that using drivers for the TI OMAP 4430 might work, but I can't even try without USB debugging enabled.
Is there some secret way to enable USB debugging or an app which allows you to set it, even if the OS does not?
+1 for developers!
+2, been looking myself. Got some apps that aren't running right and there's no way to figure out why exactly.
+3 has anyone found any ADB drivers that work for Win7? I tried a few but no luck
Found it. It's pretty easy. http://blog.actlocalmedia.com/2011/11/developing-on-kindle-fire.html
Steps to get ADB to show your Kindle Fire
Hi everyone,
1. First, go into your KF Settings > Device and enable "Allow Installation of Applications "
2. Edit your adb_usb.ini and add 0x1949 to it.
Now it should show up on ADB and let you deploy APKs to it.
Thanks guys this works.
For Windows users the file is at:
C:\Users\[YOUR USER NAME]\.android\adb_usb.ini
Post removed
For windows users if you need the driver, I posted a solution here:
http://forum.xda-developers.com/showpost.php?p=19391164&postcount=4
AdmiralUD said:
For windows users if you need the driver, I posted a solution here:
http://forum.xda-developers.com/showpost.php?p=19391164&postcount=4
Click to expand...
Click to collapse
That's odd, I didn't need to do any of that, just modify my INI in Win7 here.
I wasn't able to make this work based on the just the info here. Luckily Amazon actually posted official instructions, and they worked for me: http://g-ecx.images-amazon.com/images/G/01/sdk/Connecting_your_Kindle_Fire_to_ADB.pdf
It's weird actually having real support from the vendor.
Edit: ROFL, the links in the PDF are just blue text and not real links. Here's the whole dev FAQ including a link to the Win7 driver: https://developer.amazon.com/help/faq.html#KindleFire
Still having trouble myself using both the Amazon provided instructions and the ones in dev thread.
Still getting no devices listed doing an adb devices. Have used the provided drivers for windows from Amazon and also am sure have modified correctly the drivers in the .android folder. My adb is working as it sees my captivate no problem.
Any thoughts? Is there a way to completely remove drivers and try installing them again? Any help would be appreciated.
In win xp, it didn't work for me when I specified the driver file explicitly, but did work when I just told it what folder to look in for the driver.
To uninstall just right click the device in device manager and click remove.
Good luck.
Sent from my Kindle Fire using Tapatalk