Universal Naked Driver 0.72
** HTC One Added (HTC phones are pretty much future proof with my driver)
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Just FYI, you don't need HTC Sync to get the drivers, you can download the drivers by themselves.
designgears said:
Just FYI, you don't need HTC Sync to get the drivers, you can download the drivers by themselves.
Click to expand...
Click to collapse
Ah they may have changed this but this will still work with all your devices and tablets.
Thanks for making this but after about 30 min of research you can learn how to modify the google ini file to work with ANY android ran device as long at it doesn't have a proprietary connection interface. Once you plug in the phone just go to device manager and properties. Find the hardware ID and Vendor ID and plug them into the generic google.ini setup and label it with your phone. Then you can just install google drivers to run your interface.
I work with linux too and its even EASIER to create generic google drivers you just need vendor id and port.
I've installed this driver and I still have the MTP device problem. My phone connects as an android tablet and I can't mount my storage card. Pls help
Related
Ok hopefully this helps someone. After flashing the amazing AOKP ROM (literally best ROM I've ever flashed...Holy stable batman) I noticed that on Win7 x86 or x64 that USB file transfer to/from SD card worked fine...as did Odin but Windows could not find a driver for my phone anymore. This creeped me out because this meant adb would not be able to connect. Running the adb devices command would not show anything.
I tried 3 different Win 7 machines and a WinXP machine all of them used to work but now they didn't I read the FAQ, I goggle searched xda and droid forums and tried everything, cables, switching USB ports, phone settings, dev settings, new usb drivers but, I could no longer get adb to connect.
So I started looking closely at the Samsung USB drivers I have on my machines which worked fine on stock ROMs, and a few other custom ROMs (not blaming AOKP no disrespect) and I found that the hardware id for my device changed and the device string wasn't referenced in any of the USB drivers files. So I forced the correct driver to install and it worked! So if that is all you need to know cool, if you some of you need the steps here they are:
I'm assuming you already have Samsung USB drivers and adb from the SDK installed (if not there's tons of info on this site to get both)
I'm also assuming you installed the USB drivers so they are in the default location, if you extracted a zip file or something you will need the path to the USB drivers
Last assumption... I tried 3 different versions of Samsung USB drivers and for each one the ssadadb2.inf that has the ADB driver was in the USB Drivers\16_Shrewsbury folder...If you don't find it there do a search in the USB Drivers folder and reference that location for step 13
Click Start button, then right-click Computer, then click Manage
Click Device Manager
Expand Other devices, you should see SCH-I500 with the yellow exclaimation point
Right-click it then click Update Driver Software
Click Browse my computer for driver software
Click Let me pick from a list of drivers
Scroll up, highlight Show All Devices, click Next
Click Have Disk
Click Browse
Browse to C:\Program Files\SAMSUNG\USB Drivers\16_Shrewsbury
Double-click ssadadb2.inf, click Open, Click OK
Highlight SAMSUNG Android Composite ADB Interface, click Next
You will get an "Update Driver Warning" saying cannot verify compatibility with your hardware, click Yes
You should see Windows has successfully updated your driver software, click Close
Back in device manager under ADB Interface you should see the driver name you just added....the entry under Other devices should be gone
Connect your data USB cable (not a charging only cable...if you can't tell the difference just be sure you used this cable for data before)
Open a cmd prompt (start>run>cmd enter if you didn't know)
browse to where you installed adb and type "adb devices"
You should see your device and a serial number again....back in business
Like I said no disrespect to AOKP I rock my B31 (soon to be 32) Pink Unicorn proudly This hopefully applies to anyone who had a hardware id change from any ROM.
Universal Naked Driver 0.72
** Google Nexus 4 Added
** Google Nexus 10 Added
** Google Nexus Q Added
** Google Nexus S Added
32 & 64 Bit Windows 8 / 7 / Vista / XP - Attached to this post!
MD5: 30D25BC073F010CA01178CD6E2C5E4FA
I am happy to release my Universal Naked Driver. This is to allow ADB, Fastboot & APX interfaces to work without installing any package much less multiples packages for users with multiple devices. Yes you can just install them and uninstall right away but why bother?
I was annoyed that I couldnt use my Transformer Prime and Galaxy Nexus without having versions and packages trip over each other. My previous post for the Sensation & Galaxy Nexus was helpful so I thought I would bring to XDA the newest Android driver available from source (which they call 4.0) and make it start talking.
Warning: Uninstall any previous driver package's you may have installed and also manually remove drivers by attaching your phone and going to Windows device manager and right click the entry for your phone and select "Uninstall" on the next prompt make sure to select "Delete the driver software for this device" then hit OK and reboot before installing these drivers
Code:
Google Nexus Devices ADB & Fastboot
Samsung Devices ADB & Fastboot
Asus Devices ADB, Fastboot & APX
HTC Devices ADB & Fastboot
Code:
[B]Windows 8 Instructions[/B]
How to Disable Driver Signature Enforcement in Windows 8:
From the Metro Start Screen, open Settings (move your mouse to the bottom-right-corner of the screen and wait for the pop-out bar to appear, then click the Gear icon).
Click ‘More PC Settings’.
Click ‘General’.
Scroll down, and click ‘Restart now’ under ‘Advanced startup’.
Wait a bit.
Click ‘Troubleshoot’.
Click ‘Advanced Options’
Click ‘Windows Startup Settings’
Click Restart.
Enjoy!
Ha I have a Mac
AshtonTS said:
Ha I have a Mac
Click to expand...
Click to collapse
/VeryUsefulComment
Great work mate
Mark.
If this driver are not signed (and I think so), you should inform the Windows 8 User that most likely they need to Activate the "Install unsigned driver" option.
More here:
http://www.tips-trick.com/use-access-windows-8-boot-loader-advanced-boot-options/
@OP: Can you make this work for Nexus S?
DJBhardwaj said:
@OP: Can you make this work for Nexus S?
Click to expand...
Click to collapse
**EDIT**
DONE! Check OP
mskip said:
Great work mate
Mark.
Click to expand...
Click to collapse
I slapped your Windows 8 instructions to the front page as many people would not use Google Thanks!
Martin_Ro said:
If this driver are not signed (and I think so), you should inform the Windows 8 User that most likely they need to Activate the "Install unsigned driver" option.
More here:
http://www.tips-trick.com/use-access-windows-8-boot-loader-advanced-boot-options/
Click to expand...
Click to collapse
Added a little something, thanks
Will try this when I get home. Thanks!
Beamed via Nexus 4
these don't work for me...i pointed to the folder with the drivers and it says "windows could not find driver software for your device"
n7of9 said:
these don't work for me...i pointed to the folder with the drivers and it says "windows could not find driver software for your device"
Click to expand...
Click to collapse
Did you point to the folder during ADB or fastboot? Did you have ADB enabled as well?
You should not have any issues with these, let me know about the above.
i was having 'tried too many different things now everthing is messed up' issues
i deleted any and all Google/Samsung/adb etc drivers, and managed to get everything working with PDAnet drivers
n7'd from my n7
n7of9 said:
i was having 'tried too many different things now everthing is messed up' issues
i deleted any and all Google/Samsung/adb etc drivers, and managed to get everything working with PDAnet drivers
n7'd from my n7
Click to expand...
Click to collapse
yea you have to uninstall everything before using my driver as well, usually users have 2-5 packages installed sometimes.
Pardon the noobish question fits but is it this that you use to fast boot kernels?
Sent from my Nexus 4 using Tapatalk 2
barondebxl said:
Pardon the noobish question fits but is it this that you use to fast boot kernels?
Sent from my Nexus 4 using Tapatalk 2
Click to expand...
Click to collapse
The driver pack includes adb and fastboot drivers.
Mark.
mskip said:
The driver pack includes adb and fastboot drivers.
Mark.
Click to expand...
Click to collapse
Thanks, downloading now!
Sent from my Nexus 4 using Tapatalk 2
Just Tried on my Nexus Q on Windows 8
#justsaying no need to disable signed driver, it works !!!
Win8 pre-load laptop, maybe its different than self-installed version?!
I was excited when I read the XDA News headline, but then reading on figured it doesn't support the Nexus 7 yet.
Any chance of you supporting the Nexus 7 (3G) as well?
Thanks!
Many thanks for this useful driver pack, I have an HTC One X and in a few weeks a Nexus 4 + Nexus 7. Very good for my daily life with these devices
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller.
Note 2: You will need to have a USB 3.0 and a USB 2.0 ports for this to work. USB 3.0 for the fix and the 2.0 to install the S1Fastboot Driver.
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
EDIT: If the file is corrupted, here's the Mediafire link. Click!
kyzn said:
This is a working fix for the Xperia P Flashmode/Fastboot on Windows 8.1.
Disclaimer: I'm not the original author of this fix. Use it at your own risk.
All credit goes to Samyak Ranjan over at Droid Now. LINK
Note: Please double check in Device Manager if you have Intel eXtensible Host Controller under the Universal Serial Bus Controllers. It's listed as Intel(R) USB 3.0 eXtensible Host Controller
Here are the steps:
1. Install the XP default drivers included in the Flashtool. It's in the FLASHTOOL\DRIVERS folder in wherever you installed it.
2. Download the attachment I have included in this post. It's the official Intel Drivers for USB 3.0 Driver: Intel® USB 3.0 eXtensible Host Controller Driver for Intel® 7 Series/C216 Chipset Family. I've already included the modded files that works for Windows 8 and 8.1.
3. Disable Signing Reinforcement in Windows. Hit WINDOWS + C, go to SETTINGS ---> PC Settings ---> Click the Search button ---> Type in "advanced startup options ---> Click "Change advanced startup options" ---> Click the button that says "Restart".
4. After it reboots, choose Troubleshoot ---> Advanced options ---> Startup settings ---> Click Restart ---> Hit 7 on your keyboard (Disable driver signature enforcement). Your computer will Reboot again, log in as normal.
5. Open Device Manager.
6. Go to Universal Serial busses at the end and double click “Intel USB 3.0 eXtensible controller”. Click on Drivers in the New window which opens.You should see that the Drivers are provided by Microsoft.
7. Now click “Update Driver” and then select “Browse my computer for driver software”. Next choose “Let me pick from a list of device drivers on my computer” and select “Have Disk”.
8. In the Window that pops up titled “Install From Disk” choose “Browse” and navigate to the location where we replace the attachment.
("...\Intel(R)_USB_3.0_eXtensible_Host_Controller_Driver\Driver_Installer\Drivers\Win7\x64\") Select iusb3xhc.inf and click ok.
9. Ignore all warnings and install the drivers. After installing, Reboot the computer with the same procedure as Step 3 & 4.
Note: At this stage any devices you have connected to USB 3.0 hub will cease function. So fair warning. They will be fixed after you finish.
10. On opening the device manager, you should see an Unknown device. If you already had one before, you need to cross-check every unknown device to find the one we need. Double click each such device and go to the 3rd tab “Details”. Find the Value “VID_8086″. If you only have one listed unknow device it's that one even if it does not have "VID_8086".
11. After finding the correct device, choose “Update Driver” then click “Browse my computer”, Windows will ask you to identify the type of device, scroll down and select “Universal Serial Bus Devices”.
12. Click next, choose “Have Disk”, “Browse” and select the modified iusb3hub.inf that we placed in the same folder earlier. Ignore all warnings and install the drivers.
13. Restart the computer normally and look at the driver tab for the “Intel(R) USB 3.0 eXtensible Host Controller” and the “Intel(R) USB 3.0 Root Hub” to confirm that you are now running the Intel drivers instead of the Microsoft ones.
___________________________________________________________________________________________________________________
Now plug in your XP while holding down, the S1Boot Fastboot Driver should now install. I've double checked it via Sony Update Service and Flashtool 64. Both now register my XP.
Click to expand...
Click to collapse
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
What if I only have USB 2.0 on my computer?
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
can you re-upload the drivers its corrupted, thanks
nagarjuna93 said:
can u provide for usb 2.0 because my phone dosent connect in usb 2.0 also and also after i connect my phone it dosent show up as S1Boot Fastboot instead it show that "driver enumeration failed".
Click to expand...
Click to collapse
nanoleet said:
What if I only have USB 2.0 on my computer?
Click to expand...
Click to collapse
Sorry, but currently the fix I found was for UBS 3.0 only. Did you already try the other fixes here in XDA? Some of them worked for USB 2.0.
In my case it was a combination of this fix, and installing the S1Fastboot driver via USB 2.0.
nosmaster said:
Just disable driver signing as per instructions above nothing special for USB 2.0 I have covered windows 8 drivers many times on this forum I also asked for it to be sticky but no1 will make it so every1 on windows 8/8.1 will have the same problem
Sent from my Xperia Go using xda app-developers app
Click to expand...
Click to collapse
That did not work for me. ADB drivers installed but not the Fastboot, so I thought I'd share the way that did.
hrashdan said:
can you re-upload the drivers its corrupted, thanks
Click to expand...
Click to collapse
Done.
Work for me!!! Thanks
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
manudo said:
Only USB 3.0, right?
Sent from my Xperia Sola using xda premium
Click to expand...
Click to collapse
Yes.
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
For those with intel 8/c220 usb series you may have a look to
http://plugable.com/2012/12/01/windo...#comment-19066
Andrew (thanks) submitted there, in his comment, modified drivers in December 2013 for the Intel 8&7/c series
Be sure to use the right one because it could be a big mess (my experience)
see my post here (i tried to use 7c series drivers given in that link above,and 8 series one with the trick given a the begining by the initial writer
) big mess, only the Andrew modified ones for my 8Cseries worked :
http://forum.xda-developers.com/showthread.php?p=49426792
bountygiver said:
Installing the hub driver causes BSOD with MEMORY_MANAGEMENT error
Device: surface pro 1
Click to expand...
Click to collapse
Those are the modded drivers specifically made to support Intel 7 USB 3.0 ports. Do you even have the specific hardware those drivers were made for?
Thanks.. was trying to flash my old pro after a long time and tried everything.. this was the only thing that worked..
This worked for me on Windows 8.1 x64.
However, I had originally "Renesas eXtensible Host Controller" installed in my device manager so I downloaded the latest Renesas USB 3.0 drivers in stead of the Intel drivers but it worked perfectly afterwards!
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
molnartibor said:
after installing the driver all my usb devices stopped working. i cannot use my mouse and keyboard and cannot login to windows... ay help how i could fix it?
Click to expand...
Click to collapse
go to your Bios USB settings and disable xHCI, that worked for me & I was able to do a system restore
Any info of working fastboot driver for Windows 10? Those posted in OP not accepted.
I found a fix for VZW LG G3 Bluetooth drivers work around that works
1 - Download the 'Windows Mobile Device Center' (current version is 6.1) which you can download it here for 32-bit OS or here for 64-bit OS. This works for both Vista and Windows 7. I've tried it on both.
2 - Install the downloaded software but it may not look like it worked on Windows 7 PCs. Vista automatically configured the settings on the Bluetooth devices but for those who have Windows 7, here are the things you should do:
3 - Go to 'Device Manager' from 'Control Panel' -Or- just right-click on Computer Icon and choose 'Properties' and then click on 'Device Manager'.
4 - You'll see an 'Unknown Device' named 'Bluetooth Peripheral Device'
5 - Right-Click it and click on "Update Driver Software" -Or- anyway you find it easy to bring up the Update driver window.
Click "Browse My Computer Image for Driver Software" button.
Click "Let Me Pick from a List of Device Drivers on my computer".
Select 'Bluetooth Radio' from the list if it asked you to select and then in the next window, it will show a list of drivers with Company Names in one list and Drivers in another. In the Company List choose 'Microsoft Corporation', not only Microsoft.
From the drivers list there may be one or more drivers with the name "Windows Mobile-Based Device Support" with different driver versions. Select one or the latest.
Ignore any warnings and keep pressing next and then Finish at last. If all goes well, the last screen will show the message that device driver is successfully installed.
After doing this and pairing my PC and phone again, I was able to send files between them through Bluetooth.
I hope this helps
Hi, I'm new to the N9, have had the tablet about a week. I have tried connecting it to my windows 7 Pc and the N9 isn't recognized. I have tried all the basics, all drivers are current, set tablet to mtp, and not found. I have connected to a friend's Windows 10 PC and the N9 is found immediately. My N9 is a wifi only device, non rooted. I have 2 other Android devices that my W7 PC finds with no issue. Anyone else experience this, and or have any suggestions on how to fix this issue ? Not looking to root at this point. Any help and guidance would be greatly appreciated
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
In some cases, you need to enable ADB on your N9 before plugging it into your PC (Settings -> Developer Options -> Android Debugging).
peterk-1 said:
I think there are many threads about this problem. Nexus Root Toolkit has a driver installation feature.
If you were starting from scratch I'd delete any unknown "tablet/usb" devices in Device Manager - look for the also delete drivers option.
Google's W7 installation instructions are here http://developer.android.com/tools/extras/oem-usb.html#Win7
On this page http://developer.android.com/sdk/win-usb.html is a link to download a zip file of the drivers (not the full SDK package) Click here to download the latest Google USB Driver ZIP file.
This software http://www.nirsoft.net/utils/usb_devices_view.html is possibly better than device manager in deleting drivers
Click to expand...
Click to collapse
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
eckharttim said:
Thank you for your help, I had already tried all of this, but tried once more in case a step was missed. Every other Android device I have, or had never gave me an issue like this. The 2 android phones I have connect to pc without a problem, I am at a loss, lol.
When deleting drivers, should I have deleted all drivers for all devices, or just the ones installed from N9 ? Thanks again for your help
Click to expand...
Click to collapse
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
peterk-1 said:
I've not got access to a Windows 7 PC. Does this page help http://www.topnotchtablets.com/FixUSBproblems
A basic one. I don't think it's relevant until you have a connection. Do you know that the N9 USB connection defaults to "charging only" and you need to pull down the notification menu to enable MTP to see the device contents
In USBDeview
Expand the window there are a lot more columns
There is a "connected" y/n column. I'm not certain that this works as expected, I can connect a tablet and despite an F5 refresh or a restart of the program it will stay a "No"
Look at the VendorId column AFAIK everything Google Nexus related has an ID of "18D1"
Have tried to establish what, if anything pops up in Device Manager when you plug in the N9 so you can disable it? Nirsoft have a program http://www.nirsoft.net/utils/device_manager_view.html that gives a table view of all devices - no clicking to expand trees
Click to expand...
Click to collapse
Thank you for your help I greatly appreciated it. After trying pretty much everything, I decided to see if the ruu's for my two phones would run on W10. They did, so I then proceeded to update my W7 to W10. N9 communicates perfectly now with my PC. Thank you