Related
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
This helped me... http://www.droidforums.net/forum/dr...b-windows-7-64bit-should-also-work-32bit.html
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
me144 said:
I don't know if the motorola driver will work with htc, but i understand what you're saying. I'll find the standard google driver and try to install that the way the link mentioned. I just need to figure out how to do it in xp, as I am not a windows 7 user.
Thank you.
Click to expand...
Click to collapse
I have an incredible and it worked for me...good luck.
me144 said:
It's probably something simple, but I would much rather ask a stupid question than be the enraged owner of an Incredibly expensive paperweight. I've been following the How 2 thread, and I've ran into a little issue.
I'm running the official Froyo 2.2 OTA on the Droid Incredible, but am looking to root my device with unrevoked 3.3. I've read through the procedures and searched through support topics, but with no success.
I downloaded the recovery tool, the Android SDK, and the usb drivers from revoked, unzipped them all and installed the recovery tool and the sdk.
I put the phone into HBOOT and installed the driver like the unrevoked guide said, removed the device and reconnected it to ensure that the driver was associated with the device and it is.
Here's the problem.
I reboot into the Android OS and reconnect the device to my pc. Now the driver is listed as 'ADB' in the device manager, which is not the same driver. The driver isn't installed correctly as there is a yellow exclamation point attached to the icon. I opened cmd, changed the directory to appropriate Android SDK directory, ran ADB and the command 'adb devices' to insure that my device was recognized. It is not.
So how do I repair/reinstall the ADB driver so that I don't brick my Incredible? Any and all help is tremendously appreciated
Click to expand...
Click to collapse
Go here and follow her steps exactly....
http://www.droidforums.net/forum/dr...ow-root-stock-2-2-using-unrevoked-3-32-a.html
Sent from my Incredible using XDA App
I get through all the steps, adb setup recognizes my device is connected. When i try to unlock the bootloader <fastboot oem unlock> command line locks up at <waiting for device>.
can someone advise?
Verizon if that matters
What happens when you type in "fastboot devices"
Nothing happens. Tried it both before and after typing in adb reboot bootloader
You sure your pc is detecting the phone when it is in fastboot mode? To me it seems like your computer isn't detecting the phone or the drivers didn't get installed properly.
<deleted>
answered my own question
I had the same issue. Assuming you're using Windows, you need to find where the latest Samsung drivers for the GN were copied to when you installed them (you have installed them, right?) The next time you plug in your phone, it will probably ask you to setup a new device. Tell it you will install the drivers from a location you choose, navigate to the folder where the drivers are, let it install them, restart if it asks, and then try the process over.
FWIW, I used the directions and links from this tutorial and eventually got it working. They include alternate drivers here in case the one from samsung.com doesn't work.
im having the SAME PROBLEM AND HAVE TRIED TWO DIFFERENT COMPUTERS.TRING ADB METHOD
What's the ADB method? Why don't you just just hold the volume up, volume down and power to get into fastboot mode? When you plug it in, windows should see a new device that needs drivers. You need to make sure the drivers are installed before fastboot will work.
i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device
robitron929 said:
i am in fastboot "little android with chest opened". and i do have the driver installed but in fastboot windows thinks its a different device
Click to expand...
Click to collapse
Is it saying that it couldn't install the drivers for Android 1.0 or something like that? What step are you at? Which tutorial are you using?
Read the driver installation part of this tutorial.
http://forum.xda-developers.com/showthread.php?t=1392310
i got it. it was this
TO GET DRIVER WORKING IN BOOTLOADER YOU MIGHT HAVE TO DO THIS, THIS TOOK ME FOREVER TO FIND!!!!!!!!!!!
I TAKE NO CREDIT!
READ CAREFULLY
THANKS TO KELLEX FROM DROIDLIFE
Tips:
-We know that many of you are running into a “waiting for device” issue when apply the fastboot oem unlock command. This is a driver issue and one that a reader has a suggestion for:
1. Open device manager on your PC.
2. Right click on Android 1.0 with the yellow ! mark on it.
3. Choose update driver.
4. Choose browse my computer.
5. Choose Let me pick from a list.
6. Scroll down and find the Samsung driver with newest date. Should be the driver you downloaded above. (Possibly dated 11/25/2011 ).
7. It will give you a warning about installing the driver, just click yes.
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
After installation, plug in your phone, look at your system tray for the USB icon, click it. It should show a status of installing more drivers. This can take awhile, and for a lot of people it seems to fail the last step, Android 1.0 drivers. Open control panel, system, device manager. Look for a yellow error icon. Click that, choose to install drivers manually and locally. Then select 'choose from list', find Samsung.
That should get you back on track
Sent from my Galaxy Nexus Bugless Beast 4.0.3 lte +franco#5
Were you able to unlock the bootloader? If you didn't do this, don't go installing any driver... be very careful. If you install the wrong driver in device manager, you'll screw it up. I installed the wrong driver on my main computer and I couldn't get the device manager to even recognize the phone :| I couldn't locate the right driver either because once I installed the driver, it renamed it. It was a huge pain and the only way I got this to work was by using a different PC with the correct drivers.
I have found this to be the best instructions for unlocking the bootloader. Most importantly, it includes directions on how to gain access to adb on your phone properly. Take your time and follow the instructions exactly...
Dutchy18 said:
hey.
i followed the guide for rooting my galaxy nexus.
driver installation was alright, and then i switched to fastboot mode (green android) and then the device manager didn't recognize my gn (unknown device).
tried uninstalling and then reinstalling, tried "updating" it with various rar files i found on this forum and ofcourse i tries pdanet.
none of them worked. it was always unknown device.
then i had no choice and i removed the battery to boot it normal.
suggestions? thnaks
Click to expand...
Click to collapse
I had the same issue, install pdanet and your phone will be recognized when in fastboot
Sent from my Galaxy Nexus using xda premium
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Dutchy18 said:
i followed one of the main guides on this forum.
it says to install the pdanet drivers and then boot to fastmode via the volume buttons.
once i got into fastboot, the device was unrecognizable.
when i was still in normal boot, the device was recognized and it was all right. and yeah i turned usb debugging on.
how can i unlock the bootloader without installing drivers?
thanks
Click to expand...
Click to collapse
silly question, but after booting to fastboot, you are using the fastboot.exe, and not adb? if you type "fastboot devices" does anything show up?
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Dutchy18 said:
no, nothing shows up.
and thats clearly because the driver is not installed correctly.. i see a yellow sign in device manager.
what am i doing wrong? only thing i was different from the guide is that instead of typing adb reboot bootloader, i got into fastboot by pressing the volume buttons.
Click to expand...
Click to collapse
click open that yellow unrecognized device...manually choose drivers (don't do auto), and select from the list, you'll see samsung, choose the driver
that should install android 1.0...alot of people have gotten this error.
edit: another thing to keep in mind is, after installing the drivers, and fixing the device in device manager, it can still take a little bit to initialize. in your system tray there should be a usb icon, open that to see when the drivers are done
I am in the same boat. I tried for hours on 2 different Windows 7 laptops (both 64bit). I am trying to get Yakju from one of the derivitives (without unlocking the device).
Steps taken:
- Dloaded Samsung USB driver 1.4.6 & Installed: Did not recongnize in explorer or Odin (even Odin did not show a thing)
- Dladed PDA Net A302x64: Did not recognize in explorer or Odin.
Both times the GN is in Device/Printers and listed as having Android 1.0 driver. I try to manually update, but cannot seem to find driver in list (as it just has Android 1.0 driver listed). Any suggestions?
i didnt even see the "Android 1.0".. just "unknown device" all along..
i also tried on a different computer.. same issue.
about manually installing the driver.. i tried pointing him to a manual driver package i got from this forum.. it said its the same driver..
when im searching for "samsung" on the list, i dont see a relevant driver.
Well, i've saw someone else on here who was having driver issues, who also had installed both samsung & pda drivers...
uninstall both.
fresh install ONLY the naked drivers directly off samsungs website (http://www.samsung.com/us/support/downloads/verizon-wireless/SCH-I515MSAVZW -- if you're verizon, if not, you can search there). Do the install. Plug the phone in, it will start to install its usual crap. this is the long part. then, it will fail like you saw before. in device manager, you'll see the unrecognized device. Open, it will ask you to find drivers, choose "Browse", "Let Me Pick From a List", "Samsung", and then pick the driver with the date 11/25/2011
check to see if there are any other unrecognized devices in device manager, just to be sure you got em all. at this point, plugging in your phone should show the USB connected icon in the system tray. do you see this? If you click it does it say "Eject MTP"?
Hello!!
Well, hey guys. I thought I tell you the story, on why I posted this thread.
It started as I was installing Windows 8, on my laptop, and had the same problem, as some others. I just could not install the drivers, for my Droid, so I had a looksee and found that Windows 8 didn't yet have the capability, to download unsigned drivers, unlike Windows 7. So, I found a way of "tricking" Windows, into thinking, that these drivers are legit and it isn't forbidden to use, which is exactly what this tutorial tells Windows, in a way.
So, get going and use the full potential of your Android device!
Tutorial:
I have found a solution, to the following problem;
After installing Windows 8, you cannot install fastboot drivers, but it recognizes the ADB drivers...
Solution:
Open the dev-manager, by typing following, in a command prompt window, or the run dialog. Whichever you prefer... : devmgmt.msc
Now, the dive manager, should pop up.
Install ADB drivers, (If you do not have them present, download them here/
To prevent confusion: When I say install, it can mean unpack, or instal... Quick tip: An installer does nothing, apart from unpacking files, to allocated space, on your computer
Download USB drivers, from here. (Link fixed)
Should you NOT have drivers installed:
Install the USB drivers, and download ADB/fastboot drivers.
Installation of ADB/fastboot drivers:
Open the device manager, and look for "Samsung Mobile Device", or "Unidentified Device". You can make your search easier, by unplugging the phone, whilst in device manager, then plug it back in, and see what's changed...
Once you have found your phone, Perform a right-click, on the device. Select : "Update device drivers", once the dialog has poped up, choose "Browse my computer" and goto your dsktop, where you have installed the files to.
Open just the "drivers" folder, nothing else...
Select OK, then wait for installation to finish.
Once that has been done, you need to reboot your device, into bootloader mode; do this by typing
Code:
path=%userprofile%\Desktop\ADB\adb reboot-bootloader
adb reboot-bootloader
into the command prompt (download & install this, if you want to do it the cmd-way...)
Or, turn off your phone, and reboot i it manually into bootloader-mode, by pressing
Code:
VOL UP +DWM & PWR
together, untill phone vibrates...
Once the phone is in bootloader, go back to the device manager, and look for a device named "android 1.0". Perform a right-click on this and select "Update device drivers". Again, selct "Browse my computer", but, instead of clicking on "Browse" and selecting the folder, again, select "Let me pick, from a list of drivers." Once the menu has popped up, select "Samsung Android ADB interface". Click OK, and wait for the drivers to install . Then, you're done. You have then successfully installed the ADB + fastboot drivers correctly, to test this, open a cmd window, and type following:
Code:
path=%userprofile%\Desktop\ADB\
fastboot devices.
If your device shows up, then you have done it!!
Now type:
Code:
fastboot reboot
adb wait-for-device
adb kill-server
Note: while the phone is booting (If you typed "adb wait-for-device") A cursor will blink, wait for that, to stop blinking, then type the next command
I hope you learned, from this tutorial!! Check my root helper out, if you have enough time
Should you have problems, in recovery, open your dev. manager, and look for following device:
Code:
Full
Select, right-click. Update driver (blah, blah, witter, droan)
Browse my computer -> Let me pick -> Samsung ADB -> Done. You have enabled the ADB drivers, on your SAMUNG GALAXY NEXUS!"!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Addition: You can only reboot into bootloader, if you are using a motorola, Google or HTC branded Android device! This will NOT work with Samsung models (i.e. Galaxy S II/III) due to the fact, that they use Odin mode. Should the drivers need updating, for some devices, please let me know!
Motorola Razr
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Click to expand...
Click to collapse
Download MotoHelper. Right click the file and run in compatibility mode. It should install the drivers. I used this to run fastboot with my xoom.
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
thejakenixon said:
It still hangs while running as admin under compatability mode for 7, I'll try as XP momentarily.
Edit: XP compatability didn't work either.
Click to expand...
Click to collapse
Bummer, I just remembered there was a setting to skip os version check in compatibility mode. Did you try that? If that won't work unfortunately I don't know what else to try. Sorry.
Sent from my Xoom using XDA Premium HD app
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
First of all, thanks, for letting me know about the link It's uploading again ^^
Yes, you can do the same for your Motorola. But only with the ADB drivers. Just do the same as with the Samsung. Select your device, form the devman. and right click. Update device drivers -> Browse -> Let me choose from a list... -> Samsnung ADB interface.
They are all provided by Google, inc. so, they are compatible, with every Android device. I've even used my Samsung ADB drivers, for a Sony Ericsson Xperia X8. So I can actually say, for myself, that they work. You then can work, using fastboot... ^^
Have fun fastbooting!
LG familyguy59/Beatsleigher
Well, I'm definitly glad, to see I'm actually helping some people, and they're appreciating it!!
I don't remember mentioning it, but if you Need help, PM me. I'll help you via Team Viewer ^^
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
iconicpaul said:
will this work on Windows 8 Release Preview also ? are those compatible with x64 version of W8?
Click to expand...
Click to collapse
Yes, it works on both x86 and x64 bit architectures of Windows 8, works withRC and with pre-release...
Sent from my GT-I9300 using xda app-developers app
confirmed, it works, thank you...very fast and easy
thejakenixon said:
Hello, I was wondering if this would work for the Motorola drivers. I've been trying to install them so that I can fastboot my Razr, but it quits right after it recognizes that I'm on Windows 8.
I guess I might as well just try it in the meantime!
-Jake
Edit: In the ADB drivers link you posted, there's nothing to install. Just .sys files, .dlls, two .cat files, and some .infs. How exactly does one do anything with these files? Also, your second link for USB drivers was removed by mediafire.
Click to expand...
Click to collapse
To your edit. You have extracted the files. This is also called "installing" because you have extracted NEEDED files. Even when you extract a .zip/.rar/.tar/.tar.gz and so on, because you need files out of them, you are installing, but not to the system, but to yourself
Sorry for bringing up an old post, but this method is not working for me on Windows 8 Consumer Preview. When I'm trying to install the ADB drivers, it says the drivers cannot be installed because it's not digitally signed.
UPDATE: I got it to work by disabling the Digital Signature Enforcement on Windows 8. Steps: Restart Windows > Boot loader Menu > Other Options > Advance Options > *Computer Automatically Restarts* > Press F7 to Disable Digital Signature Enforcement
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
2phonejones said:
I cant get odin to work on win8 with my epic touch could this be my solution? Ive tried everything
Sent from my SPH-D710 using xda app-developers app
Click to expand...
Click to collapse
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
iconicpaul said:
confirmed, it works, thank you...very fast and easy
Click to expand...
Click to collapse
No worries, dude That's what I posted this thread for.
familyguy59 said:
Yes, it should work with all Android-modification applications. I have never really had problems, with Odin, with any version of Windows, mainly because this is the first thing I do, on any of my Windows machines, but it is always worth a try Tell us, what you have found out!
If necessary, I'll try to find a solution myself
Sent from some GS III in some country, to a server somewhere in the US...
Click to expand...
Click to collapse
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Could someone pls. create a video tutorial, nad post this on Youtube, for me?
My laptop broke a couple of days ago, and my PC is only capable of running 98 - Vista, so, running on XP with 1GB of RAM.
I would appreciate this very much!
If you could do so and send me the link, via PM, I would be glad to pay 5€, via PayPal!
2phonejones said:
thanks bro i didnt think anyone would repsond lol. Trying now, report back with results i want to flash so bad.:good:
Click to expand...
Click to collapse
Ok, dude! Have fun!
Didn't work for me.
jorgefcbastos said:
Didn't work for me.
Click to expand...
Click to collapse
Did you follow the tutorial COMPLETELY, or did you leave stuff out? If you left something out, it's obviously not going to work
You may have to disable device driver signing, I've had quite a few people notify me about this.
But I'll sign the drivers, ASAP, so you won't have this problem
LG familyguy59/Beatsleigher
Edit: I forgot to mention, you need to tell me what exactly didn't work, otherwise I can't really help you
Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here: http://forum.xda-developers.com/showpost.php?p=21266325&postcount=239
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here:http://forum.xda-developers.com/showpost.php?p=29044502&postcount=735 , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
paul-g said:
Hi everyone,
I'm currently trying to upgrade my phone from Yakjudv to Takju/JB. Unfortunately I've run into some issues, and as they are quite different from the questions in my original thread, I thought it best to start a new one. I do apologise if this was the wrong thing to do! I just thought that an answer to this may be helpful for others, as my searching for an answer is coming up blank.
Before I found XDA forums, I had downloaded and installed Wug's toolkit, and used it to manually install drivers for my phone. This led me to being able to find my phone's serial number when I load toolkits or run adb devices tools.
I then tried to backup my ROM using the method here:
Unfortunately, I got an error saying 'can't mount SD Card' (presumably because the GNex doesn't have an SD Card). Being worried about this, I thought it might be a driver based issue, so I tried to uninstall my drivers by:
1. uninstalling them from device manager (including deleting the driver software);
2. disabling downloads of drivers in windows; and
3. uninstalling all entries related to Galaxy Nexus, Google and Samsung in UDBview
I restarted, plugged my phone in, and the phone suddenly reinstalled, finding drivers on its own. It showed Galaxy Nexus and Samsung ADB device as being installed. When I tried to manually install universal drivers from here: , I was told by my PC that up to date drivers were already installed.
I don't seem to be able to uninstall the drivers, no matter what I do. I have even tried to uninstall the drivers using Galaxy Nexus Toolkit (I'm trying to avoid using this, but thought it might do the job).
Is this a problem?
If so, is there anything I can do to uninstall the drivers properly?
Thank you so much in advance, everyone!
Click to expand...
Click to collapse
Drivers
cyanogenmod wiki said:
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
lowandbehold said:
Google USBDeview, and download the application. When you run the program, make sure to right click and "run as administrator". This will show you all of the drivers installed on your computer. Delete anything that says "Samsung" "Galaxy" or "Nexus". This will give you a clean slate to start with.
Click to expand...
Click to collapse
Thanks for the advice. I have tried to do this, and uninstalled all of the Google/Samsung/Galaxy/Nexus options, but the minute I plug my phone in, it all just reinstalls!
Originally Posted by cyanogenmod wiki
Open the Device Manager.
Right-click on My Computer (Windows XP) or Computer (Windows Vista/7).
Click on Manage.
Click on Device Manager on the left.
You will probably see Unknown Device with ADB listed under it with a yellow exclamation mark.
Right-click on ADB.
Click on "Update Driver Software".
Click on "Browse my computer for driver software".
Click on "Let me pick from a list of device drivers on my computer".
Click on "Have Disk".
Click on "Browse".
Select "android_winusb.inf
Click to expand...
Click to collapse
Thanks for this. I have used it to install the drivers for when in fastboot mode, and I forced installation for the Samsung ADB Device that showed up in my Device Manager.
Do I need to do anything for the driver for the "Galaxy Nexus" device?
Thanks so much!
Paul