Related
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
Did you ever find this out, I'm having the same problem.
Just install the SDK and it should work?
Sent from my HTC Desire HD using Tapatalk
yes the drivers are included in the android SDK from google website
I installed the pdanet software to get it recognized in the fastboot mode.
thecurran said:
I'm a developer, but can't get my Galaxy Nexus working with ADB. I've noticed that in Device Manager "Galaxy Nexus" is correctly installed under a Portable Devices, but there is an unknown device called "Galaxy" which it can't automatically find the drivers for.
I saw this thread but that seems to be talking about drivers for fastboot; I want the ones which enable USB debugging of my apps. Are they one and the same?
Thanks!
Click to expand...
Click to collapse
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
You sir, are my hero!
Thanks alot
Easiest way is through installing PDAnet, that's what I did.
Sent from my Galaxy Nexus using XDA App
On Windows 7 you go to device manager and select
Updated driver > Browse my computer... > Let me select... > Show all > Have disk
And then browse to the inf file in the android-sdk-windows\extras\google\usb_driver folder.
It's a pain but it works perfectly.
or get a mac
appelflap said:
or get a mac
Click to expand...
Click to collapse
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Eoinoc said:
If Google and simply included an install section in the INF file people could have double clicked it and everything would work fine and dandy.
This is not an OS wars case, it's a (minor) 3rd party issue.
Click to expand...
Click to collapse
Agree, although developing on a unix based machine (mac or linux) is so much faster.
gambiting said:
I had the same thing - just go to properties, select to update the driver manually,and then select to choose from a list of known devices(this is really important, don't select to choose your own driver file). Second or third from the top should be an Android ADB interface device. Just select that and it should work just fine ;-)
Click to expand...
Click to collapse
Worked perfectly, thank you!
Can somebody help me. I have everything installed but it won't recognize my device
Sent from my Galaxy Nexus using xda premium
I'm new and not allowed to post links
Go to the Samsung Homepage of your Country/Language, go to support -> download center, enter galaxy and use the autocompletion for galaxy nexus, then download the usb driver
was not working for me so I force the use of google usb driver from Android SDK by:
- opening windows device manager
- right click -> update driver on the Other devices : Galaxy(exclamation mark)
- Browse my computer option
- Let me pick from my computer option
- click next on the Show All Devices upper selection
- click Have Disk and browse toward your android-sdk\extras\google\usb_driver
- select Android ADB Interface, Next and finish with the Yes
adb devices command reply correctly
I've done the same and flash succesfully my Gnex in fastboot (once you're in bootloader the driver to update in device manager is Android 1.0).
Adding new lines in the android_winusb.inf file from the extras\google\usb_driver leads exactly to the same result.
As it's not a conventional method there might be some issues
mskip said:
If the adb drivers from the sdk kit dont work for you (which they should) then just install the Samsung adb drivers *HERE* and you will be able to select the Samsung driver in the device manager.
Mark.
Click to expand...
Click to collapse
Just wanted to say thank you as this has resolved my issue. I had installed Android SDK which didnt help.
Edit: I had to install the driver to DeskNotifier application would work with my Galaxy Nexus. After installing, it did connect fine. Strangely though, as soon as I sent a test msg from my phone to the PC, my computer became extremely sluggish. I am now rebooting
USB driver still won't install
Neither the USB driver from Samsung nor Google will work on my Win7 machine with my Galaxy Nexus. I have the device plugged in and in recovery mode. The device shows up as a Galaxy Nexus on the device manager, but is unable to install either one.
Thanks for your help.
http://forum.xda-developers.com/showthread.php?t=1626895, part A. It seems the device should be booted normally to install the adb drivers.
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
mojo1633 said:
Let me start by first saying I'm brand new to the forum and have never rooted, unlocked, or flashed anything, so I'm a total novice. Any help is therefore greatly appreciated! I have a VZW Galaxy Nexus, and I've decided to manually install a Jelly Bean Rom, rather than waiting for Verizon's slow ass. I'm trying to use Wug Fresh's Nexus Root Toolkit to do so, but I can't even get started because I can't get Windows to recognize the device when connected via USB. I know there are many other threads about this, but I can't seem to get a straightforward answer for my exact situation. I've installed all the drivers I can find - the official Samsung drivers, the drivers included in the toolkit, and some naked drivers found here on XDA. Nothing seems to work. I've tried it on three different machines - XP, Visa, and W7. The message I get when I try to manually configure/select the drivers is something to the effect that the most current software/driver is already installed, despite the fact Windows says there's no driver and doesn't recognize the device. Oh, and one last thing, I've now tried this on two different GNex's - Verizon just replaced mine for signal loss issues, and the new one has the new build number IMM76Q. I'm at a complete loss and extremely frustrated. Help!!!
Click to expand...
Click to collapse
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
eksasol said:
The Universal Naked Driver is the one you want, it include the ADB FastBoot drivers required to do flashings (link in my sig). The Samsung driver from Samsung Kies is a different driver so the computer could recognize the phone storage.
Make sure you use the official USB cable or a quality one to get good connection. Uninstall all unncessary Android drivers from other devices and the Nexus too, reboot, connect the Nexus, when it ask for a driver poing it to the Universal Naked Driver folder. If the installation still fail, try a different computer.
Sometimws the Nexus might be attached to the wrong ADB driver, when you connect it, you can go to Device Manager and uninstall the ADB driver, but also selecting the option to delete the driver from the system.
Click to expand...
Click to collapse
Thanks both of you for your help so far. I tried installing these naked drivers but no still luck. I don't have any preexisting Android drivers on the computer, but how would I uninstall drivers on the Nexus? The message I get when I try to update the drivers to these is that Windows could not find a better match for the hardware than you currently have installed. I checked the Driver Details and the driver it has listed is C:\WINDOWS\system32\DRIVERS\klfltdev.sys. I've tried numerous times "uninstalling" the driver, rebooting the computer, and starting the process over again but still no luck. I'm unable to actually remove this system file from my computer. I've been trying to do this on a work computer running XP, but I tried the naked drivers on a Vista machine as well, and I still get a similar message about the software already being the best match when I try to point Windows to these drivers (again, no other drivers installed on that machine). I'm so frustrated...
PoorCollegeGuy said:
Lol just be forewarned, a lot of douchebags may come in here and make fun of you. Ignore them, they don't represent XDA
I'm getting the Galaxy Nexus in a few days (mine's the Sprint one), but I'm going to be using mskip's GNex Toolkit. No worries, he has one for the Galaxy Nexus on Verizon too:
http://forum.xda-developers.com/showthread.php?t=1400871
I would download that and use it to install the drivers. If that doesn't work, mskip has a pretty extensive FAQ and I believe drivers on Windows is answered in the 1st solution in post 3...so follow the link, download THAT toolkit, see if the drivers install properly and if not, go to post 3 and follow the instructions for "fastboot drivers".
Next time, try to use the search bar please. It is a rule around here to do so because it's XDA, which means every question has been asked and answered a million times lol no big deal, just be more weary in the future!
**edit**
first post, huh? Welcome to XDA
Click to expand...
Click to collapse
I have done all of this, including following the complete instructions and trying all options at http://theunlockr.com/2009/10/06/how-to-set-up-adb-usb-drivers-for-android-devices/
Still nothing seems to work. I am at a complete and total loss, and am entirely discouraged. For the life of me, I can't believe it's so utterly difficult just to properly install device drivers on a developer phone.
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
ifly4vamerica said:
Ok I am sure you have done this but thought I would check. USB debugging needs to be enabled so settings developer options then enable usb debugging.
Click to expand...
Click to collapse
Yes, I turned debugging on. Never hurts to check, though. I'd love for the solution to be something so simple that I just overlooked.
http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735
First of all, DO NOT USE TOOLKITS!
I know it is easier for you, since you are new to this rooting stuff, but trust me on this, 2/3 people who said their phone's bricked used toolkit instead of adb and fastboot method
Now with that out of the way, you can check if you got any other drivers installed by going to Control Panel->Hardware and Sound->Device Manager
From there, connect your phone via USB and see driver pop up. If it's something like "Android 1.0", uninstall that, and then install naked driver. If you don't see any driver pop up after connecting, just install naked driver (for me, when I checked USB debugging, Windows automatically installed Samsung ADB driver that works well for me.). If you see something like "Samsung ADB Interface Driver", you should be able to use adb commands and such.
If you don't have fastboot and adb files, make sure you do this step!: After that, you should download adb files, fastboot files (adb and fastboot files can be found from Efrant's attachment from this thread: http://forum.xda-developers.com/showthread.php?t=1626895), and Android SDK (If you already have SDK for some reason, just download adb file and fastboot file ). After downloading Android SDK, put the folder in somewhere easy to find. (C:\ directory should do it). Now, put adb and fastboot files inside the platforms file (that can be found from SDK folder)
Now you got files set, go to the directory where you put adb and fastboot files, shift+right click and then click Open Command Prompt Here
Type "adb devices" and if you see one device from the cmd, you are good to go
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
lol nice.
mojo1633 said:
FINALLY! I got it to work. I turns out the problem was just the GD USB cord I was using. I had been using the OEM Samsung that came with the device the entire time, so I obviously had no reason to believe the problem was the cord, especially considering the device would still charge when plugged into the computer or the AC outlet. I just happened to purchase a cheapy Chinese charging station that came with a USB cord and that did the trick. I guess I just got a lemon of a cord the first time. I could've been saved so much aggravation, but oh well! I'm no running the latest BAMF Paradigm Jelly Bean ROM, and it's sweet! Thanks to everyone for the help and suggestions!
Click to expand...
Click to collapse
That's great! Make sure you give the guy who helped you Thanks
I have browsed up and down both these forums and google. I am not a dev, but I am by no means a newb at this stuff.
Here is what is happening and what I have tried.
The Nexus will only recognize on the PC as INFT2 device and will try to install as a modem. I am not rooted. The problem with this seems to be that the only recurring theory that seems to be popping up is that I have Fastcharge enabled. Unless I am grossly mistaken, if I am using a stock kernel that not possible. And all signs (unless I'm just completely oblivious in looking this stuff up) point to my kernel being stock. Just for fun if anyone wants to direct me to a terminal emulator way to disable fast charge if my kernel is magically not stock, I'm all ears.
What I have attempted so far.
-Using the toolkit 7.8 installer
-Using the PDANET installer.
-Manually using the link provided in toolkit 7.8 to get it to recognize the device properly.
-Switching USB ports on my computer.
-Three different USB cables.
-Trying to force the device to recognize in Device manager (but since it isn't recognized as a usb device I don't know how that's possible.
For your dissection this is the kernel I have on my new phone.
3.0.8-00007-g785b3cc
[email protected] #1
SMP Preempt
Any help is greatly appreciated at this point.
When you connected the very first time your phone to PC, did it say your drivers could not be found? I presume you started after that the hole drivers saga. If I'm correct, Fastcharge would require a custom kernel and you are on stock, right? So why using it from the start... I own a GSM model from Google Play and my kernel is at 3.0.31 version.
Few rules for people running on Windows software: use the Windows Update drivers and original Google drivers for ADB, if you do not want to end with a pile of crap. I would start by removing all the crazy driver collection you have there and make sure they are gone. Run a cmd as Administrator and type:
Code:
set devmgr_show_nonpresent_devices=1
Then, in Device Manager enable the hidden devices (View > Show Hidden Devices) and hunt down all the drivers you installed, they will be grayed. You are in for a nice long workout... might as well re-install Windows.
Read this guide also: http://forum.xda-developers.com/showthread.php?t=1830108
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
mikoal said:
What type of drivers are there for the S3?
I understand that you need drivers installed on the computer for it to reecognize the S3
How many driver are there?
Are there any more aside from this?
Where can i download these drivers?
I think ADB has a driver for thisas well?
Thanks!
Click to expand...
Click to collapse
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
themadproducer said:
Here is the link to the Driver package for i747 and i747m (AT&T/Bell/Rogers/Telus) With this, you don't need Keis...unless you want to use Keis. Also, TRY a WINDOWS UPDATE after installing this driver package.
I found their to be side issues on my Win7 and XP pc's....too long a story. If you have issues, I will send you a link.
Click to expand...
Click to collapse
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
mikoal said:
Thanks mad producer. Is this driver package all the drivers I'll need?
I noticed these drivers are from the samsung site.
Are there any custom drivers or drivers for rooted phone, on custom roms etc?
Are there different kinds/type, I recall reading about ADB drivers or ADB connections.
Can you also send me the link to the issues with the drivers?
Thanks a bunch!
Click to expand...
Click to collapse
If/when you need ADB (I don't use it) then just look around for ADB. I don't have a link for that.
When I first connected my S3 to my Win7, XP, 2nd XP machine, each one had an issue with the MTP protocol. This is what's used to transfer files to and from phone internal and external storage. I did my homework and massive experimenting and solved the issues. (pretty pathetic really) I just don't have a turn key absolute solution but here are some tips. Try one or all of these till it works...and it WILL!
(Backup your PC before attempting and use at your own risk)
XP
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in XP for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if not, download this and install
- if it's still not working, (which I doubt) then update windows. After the Samsung drivers are installed on some windows machines, windows updates provides a specific update that helps. I watched it happen/work on 2 machines.
- still not working, get ready....sounds crazy...but install Windows Media Player 11. It is tied into the MTP framework somehow. This is the version I used
Win7
- plug your Ss in via usb
- install the samsung drivers
- after any/each of these steps, unplug/replug usb S3 to PC
- check Device Manager in Win7 for any Yellow exclamation marks. If there are none, then go see if you can transfer large files (eg mp3) to your S3 and back via USB
- if you can then your done
- if it's still not working, (which I doubt) then update windows. (remember to unplug/replug usb after.
- install wmp11 or higher
- if it's still not working, try this file (sorry...can't elaborate on it)
- STILL NOT WORKING...doubt it...but last chance, download this file and place it into c/windows/inf directory and reboot.
I have a couple of very basic questions about drivers needed for the Galaxy Nexus. I am using Windows 7 with a Galaxy Nexus GSM.
Part 1:
I have the impression that there are 4 drivers required:
-- USB driver (needed for normal mode)
-- ADB driver (needed for normal mode)
-- MTP driver (needed for normal mode)
-- Bootloader driver (needed for fastboot mode)
Question: Is the above correct?
Part 2:
The first time I had a successful connection, I copied down some of the driver information from Device Manager:
-- USB - Samsung, version 2.9.507.0
-- ADB - Samsung, version 2.9.507.0
-- MTP - Samsung, version 2.9.319.511
When I look at Device Manager now, the MTP driver is now something from Microsoft, not Samsung. I tried finding the Samsung version in the files downloaded from an XDA thread:
-- Samsung_USB_Driver_for_Mobile_Phones_v1.5.29.0.exe
-- Samsung_Android_ADB_Interface_Driver_v2.9.510.0.cab
It seems like both of these files contain USB and ADB drivers, but not the MTP driver.
Question: How do I get and install a Samsung MTP driver?
Part 3:
Question: How do I get and install a Samsung bootloader driver?
Thanks.
KarateKick said:
I have a couple of very basic questions about drivers needed for the Galaxy Nexus. I am using Windows 7 with a Galaxy Nexus GSM.
Part 1:
I have the impression that there are 4 drivers required:
-- USB driver (needed for normal mode)
-- ADB driver (needed for normal mode)
-- MTP driver (needed for normal mode)
-- Bootloader driver (needed for fastboot mode)
Question: Is the above correct?
Part 2:
The first time I had a successful connection, I copied down some of the driver information from Device Manager:
-- USB - Samsung, version 2.9.507.0
-- ADB - Samsung, version 2.9.507.0
-- MTP - Samsung, version 2.9.319.511
When I look at Device Manager now, the MTP driver is now something from Microsoft, not Samsung. I tried finding the Samsung version in the files downloaded from an XDA thread:
-- Samsung_USB_Driver_for_Mobile_Phones_v1.5.29.0.exe
-- Samsung_Android_ADB_Interface_Driver_v2.9.510.0.cab
It seems like both of these files contain USB and ADB drivers, but not the MTP driver.
Question: How do I get and install a Samsung MTP driver?
Part 3:
Question: How do I get and install a Samsung bootloader driver?
Thanks.
Click to expand...
Click to collapse
For ADB stuff, use the Google USB driver. The MTP driver shouldn't matter a whole lot.
You can always uninstall the driver from the device manager and then reinstall the Samsung drivers from the Samsung website but I don't remember ever needing a Samsung MTP driver.
So in answer to Part 1, the only driver you will probably need is the Google USB driver if you ever flash from ADB.
Why are you looking for a Samsung MTP driver? I think the one provided by Microsoft should be fine. Matter of fact I'd be surprised if different vendors had drivers for their MTP devices.
Use Universal Naked Driver, have been using it for a long time with zero issues. Works with ADB, MTP, Bootloader, and USB tethering without any issues.