Database Users

[USB Drivers] Galaxy S GT-I9000 (Working on ICS)

Hello.
And bacon and spam:
I've recently upgraded my SGS to ICS (ICSSGS ROM) and started to develop a simple application.
So, now i've got to the point that the emulator starts to show its limitations, so i need to debug directly on the real device.
Well, i've been trying to make ADB recognize my phone, tried several usb drivers from several sites, none of them worked.
After several hours spanking windows, it's finally working (yes! almost 6 AM in the morning!).
What matters:
So, to anybody who have the same problem as i had, do the following:
0. Uninstall any drivers that you've tried before.
1. Extract the zip file that i've uploaded to anywhere you like.
2. Enable debugging on your phone and connect it to PC throught the USB cable
(Just connect it, don't mount)
3. On your computer, click Start -> Right click on "Computer" -> Manage
This will open the "Computer Management" window (it might take some seconds to load).
4. Click "Device Manager". Now you should find your device in the list. It must be really easy to find. It's called something like "GT-I9000" or "GalaxyS" and it has a yellow warning sign next to it.
5. Right click on it and choose "Update Driver Software". In the window that appears, choose "Browse my computer for driver software". It then asks you where is the driver.
6. Click the "Browse" button and choose the folder you extracted from my zip file.
(If you didn't change it, it must be called "Android Composite ADB Interface")
7. Click "Next" and cross your fingers. If you're lucky, it may work for you.
Final notes:
1. I'm not responsible for ANYTHING. Whatever you do, it's your own choise to do it. I guarantee absolutely nothing.
2. This is was tested on Windows 7 - 64 bits with Team ICSSGS RC4.2 ROM and Semaphore ICS 0.9.1 Kernel.
3. Have fun.
4. If you try this, please answer the topic and tell everybody if it's working for you (mentioning your Windows version and what ROM you use).
Driver file:
-> http://www.mediafire.com/?t8ekrd9ly3mwwbk

Missing file when installing driver on windows 7 x64
Hi,
I have recently installed the most recent Dark Knight ICS 4.0.4 build to my Samsung Galaxy S. The ROM seems very good but I'm an android app developer and need to be able to debug my applications on the device via USB.
I have tried the driver provided in the thread which won't install due to a missing file according to the Windows 7 x64 driver install wizard. The exact message is displayed after step 7 and says:
"Windows found driver software for your device but encountered an error while attempting to install it."
"Android Composite ADB interface"
"The system cannot find the file specified".
Is there a file missing in the package? Has anybody managed to get this driver working?
Cheers,
Ben

Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2

What's wrong with the Nexus S drivers available with Android SDK?
Google USB driver, R4 developer.android.com/sdk/win-usb.html
The SGS will present it self like that when it is running ICS/CM7/CM9.
Sent from my GT-I9000

METEMEDO said:
Does it say that it doesn't find a controller or that is there a missing file?
Anyway, please try this installer and let me know if it works for you:
http://www.mediafire.com/?v70501cxbzzdvc2
Click to expand...
Click to collapse
Dont work for me.
System: Windows 7 x64
Android 4.04 Dark Knight
Nevertheless thanks for your approach. I'll test if it works with the SDK Updater.

I'm going to test in my desktop this weekend to check if it works with it.

I have the same problem, but with WIndows 7 32 bit. Drivers from discusion doesn't work. Don't you have some for 32 bit?
I found SDK Components on developer.android.com, where is Android driver which suppose to work, but unfortunately ODIN still do not see phone.

I also have the same problem but mine is worse because my phone is completely down after I tried to restore from a GB ndriod backup failure , phone won't boot , cannot boot into recovery only in download mode but no way my 4 x computers would detect the phone now ....tried using heimdall in linux as well as sdb, no go....so sad...help...
Sent from my Dell Streak using XDA

Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf

I got my i9000 recognized using the latest drives from the Google sdk

That‘s great

http://ics.samsung-updates.com/addons/usb_driver.zip

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
I tried last night didn't work for me.... (r18)
Sent from my Dell Streak using XDA

oxidising said:
I got my i9000 recognized using the latest drives from the Google sdk
Click to expand...
Click to collapse
Daha açık anlatabilir misiniz?

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
... this driver actually worked for me...!
(Tiramisu ICS)

USB option has been lost in my galaxy s
RazorNova said:
Using Google USB drivers finally worked for me. They can be optionally installed with Android SDK using SDK manager (extras). After installation drivers can be found in <sdk>\extras\google\usb_driver.
Just follow the instructions in the first post to find your device from device manager with exclamation mark. Need at least one reboot to work and I also redirected the driver installation process to Google usb driver directory but now ADB finally recognizes my SGS (MyICS, Android 4.0.3).
Edit: Operating system Vista 64-bit
[Currently stuck in "error: device not found" while trying adb push -command. I will update if I find a workaround. Probably something to do with inf-file.]
For alternate .inf -file (optional):
Google "usb-drivers-not-working-after-flash-latest-rom-ota" and see post #12 to see alternative inf-file. Some have managed to make adb recognize the device with that file, but I have at least this far been unsuccessful.
Edit: Problem above was caused by me being stupid and trying to use push in shell, which caused phone unable to locate host system folders. I don't know if that inf file has anything to do with drivers working now, but go ahead and try it if doesn't work with the original .inf
Click to expand...
Click to collapse
What should i do after instaling SDK

IWillExplain said:
http://ics.samsung-updates.com/addons/usb_driver.zip
Click to expand...
Click to collapse
This worked for me

The very important thing is that newest Google USB driver is in
Code:
[B]<android-sdk>/extras/google/usb_driver/[/B]
location, not in
Code:
<android-sdk>/usb_driver
It really makes the difference !

these drivers only worked once...
all the other times killing and starting over adb i was getting error messages like "device not found" and "protocol fault" even though adb devices was listing the device online.
apparently i connected the phone to another USB3 port on my pc (front panel) and that was it!! it now works every time i type adb shell or adb devices.i no longer get any error messages.rather weird
anyway..i also wanted to be up to date with everything so i uninstalled all related software like the older java 6 jdk, Android SDK and the drivers mentioned above.
i followed the procedure below and installed all the latest packages:
latest java 7u5 JDK, the latest Android SDK (nstaller_r20.0.1-windows.exe) then ran sdk-manager and loaded http://developer.android.com/tools/extras/oem-usb.html#InstallingDriver google USB drivers rev 6. then installed these drives so i got the ADB composite interface on my device manager and it all works fine now.

I recenelty installed latest ICS , and SDK recognizes my phone as ACER ADB , when I'm pretty sure its a Samsung I9000 . I tried uninstalling the ACER ADB and install the one that the guy posted in the first post , and it didn't work , it said this driver is not compatible , oddly it reinstalled ACER ADB though. I can't even uninstall it at all , I removed all my Samsung drivers , and everything else I installed for Samsung , and its still there , I even tried removing the GOOGLE USB drivers , still there.
Neendless to say that the phone doesnt connect to the PC at all even though it says everything is alright. For example i got ths gPAD app , which uses the USB with Debugging to turn the phone into a mouse , but it says its not connected even though it is.

[Q] Windows 7 fails to install MTP driver

I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?

mseebass said:
I recieved my N4 yesterday.
When I try to connect it to my notebook (running Windows 7 Professional), the installation of the MTP driver fails. The error message says something like "driver could not be found". ADB however works without problems. (I allready debugged some apps on the phone.)
I tried installing the drivers from the toolkit, but it didn't work.
On my brothers netbook the MTP drivers were installed successfully. But I can't get it working on my notebook.
Can anyone help me?
Click to expand...
Click to collapse
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.

bigcrav said:
I was just having this problem but I fixed mine by changing the USB port. Not sure if itll help but worth a try.
Click to expand...
Click to collapse
Thanks for your help. I allready tried an other usb port. It did'nt work.

I wanted to avoid it but I reinstalled windows. Now it works. Thanks again.

Hmm, messed with this problem for ages yesterday, mtp installed fine in normal mode but refused when in 'usb debugging' mode
simple fix, find your wpdmtp.inf file in windows/inf
edit it like shown, look for the [Generic.NTx86] and [Generic.NTamd64] entries near the top of the file........
[Generic.NTx86]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
[Generic.NTamd64]
%GenericMTP.DeviceDesc%=MTP, USB\MS_COMP_MTP
%GenericMTP.DeviceDesc%=MTP, USB\VID_18D1&PID_4EE2&MI_00
...then update the driver in device manager, use automatic search
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode

I did a clean install of windows and that solved the issue for me. Thanksfor your help anyway.

I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.

meangreenie said:
just make sure the 'VID_18D1&PID_4EE2&MI_00' matches your device id, check in device manager.. but i'm guessing all nexus 4 are the same.. usb debugging mode
Click to expand...
Click to collapse
Just FYI, just got a Nexus 4 from T-Mobile yesterday and the device ID is slightly different:
VID_18D1&PID_4EE2&MI_01
01 at the end instead of 00
---------- Post added at 09:11 AM ---------- Previous post was at 08:53 AM ----------
Fitchman said:
I usually see what drivers do install, like adb or whatever, and then remove/uninstall them AND delete them
Then installed this pack
http://forum.xda-developers.com/showthread.php?t=1998650
then connect to a different USB port and try again with the new drivers
Also, some USB hubs can be under-powered and cause problems.
Click to expand...
Click to collapse
How/where do you install those files/drivers? There are no instructions.

lannister80 said:
How/where do you install those files/drivers? There are no instructions.
Click to expand...
Click to collapse
When Windows asks where the drivers are you point to the folder with the ones you want to use...

EddyOS said:
When Windows asks where the drivers are you point to the folder with the ones you want to use...
Click to expand...
Click to collapse
It doesn't ask. I plug in the phone, and Windows says it can't install the MTP driver.
If I go into Device Manager and find the phone (with the yellow triangle and !) and select Update Driver Software, then navigate to the i386 folder from the Universal Naked Driver (on an i5 system), it tells me that "The best driver for your device is already installed" or something similar.
Of course, if I uninstall the device from device manager (and presumably the bad MTP driver as well), it disappears, so I have nothing to point to to install the drivers.

Earlier today I reinstalled the drivers for my N4 on my work PC (Vista Business) and I had to reboot before it recognised the N4 as an MTP Device - prior to that it only saw it as an 'MTP Device'. Now it sees at 'Nexus 4'

I have a similar problem I have a kindle fire
I have install the ADB driver but am having extreme difficulties getting the MTP drivers to work
I have tried everything (every solution on Google)
and nothing works
I've tried the "Media Transfer Protocol Porting Kit"
I tried to get Microsoft help they gave me the run around and confused me even more
here is the conversation
Microsoft: "Thank you for that information
Nathaniel I was checking your product key and it is blocked that is why you can not connect these devices to your computer, you may be a victim of counterfeit software so in this case since it is an OEM computer which means that the manufacture of the computer installed Windows 7 on your computer I recommend you to contact the manufacture of your computer to see if they have an option in order to resolve this issue you are having."
me: when i contact them what do I ask for?
Microsoft: You need to ask for a new product key
me: I am confused what does this mean? that the manufacturer put windows 7 OS on here illegally? but all PC's come with windows OS so every PC in the world is suspect to counterfeiting
them: No, this could be because someone still some information of your computer and use the product key to try to activate Windows until the product key got blocked
No, the name is not involved in this case it is jut the product key
what do I do?
is there an alternative to MTP drivers?

Solved
Hi, i had the same problem described in previous posts and I managed to solve thanks to what is written by meangreenie.
In practice, in the windows\inf of my Windows 7 the file wpdmtp.inf was no longer present but there is only the "compiled" version (wpdmtp.pnf).
I retrieved the file from an earlier version founded in he folder Winsys and so the LG driver are installed without further problems.

Jon McDougal said...
You might be using the wrong driver (Android ADB) instead of the MTP driver. This happened to me the other day!
If you're in Debug Mode, you've already done the first step I was going to suggest.
Here's the second step that worked for me: Open Device Manager -> Click Android Device (top of my list) which exposes "Android Composite ADB Interface" -> Right click that device -> Update Driver Software -> Browse My computer for driver software -> Let me pick from a list of device drivers on my computer -> then choose "MTP USB Device" -> Next
Mine installed the MTP driver and then the N4 opened normally.
Click to expand...
Click to collapse
That works for me with USB Debug ticked and in MTP Mode but not in PTP Mode (on CM10.2-nightly-20130817). I absolutely can't see my pics in no way... (I suppose this is a bug from Google to be fixed in further updates). ADB and FB are correctly working as tested with NexusRootToolkit 1.7.1 Drivers Test.
May it help to delete original DCIM folder and start from a new one??
edit: Shame on me... I forgot that I've formatted my SDcard, so I've no picture in DCIM folder.... Sorry! So I can say that McDougal trick totally worked for me!

try to check the device manager to check the missing drivers with ! mark

Maybe I'm not completely getting the problem, but just doing this worked fine for me:
danielms22 said:
Enable USB debbuging in your phone. Go to Settings -> about phone -> tap about 10 times on build number item until USB debbuging is unlocked.
Also, on your computer go to the device manager, look for your phone, if you find it, right click on it, then update Driver Software, browse computer, Let me pick from a list of device drivers on my computer, USB composite device
That should do it.
Click to expand...
Click to collapse
No need for additional driver download or anything...

Finally a working solution
Finally I found a solution.
Visit answers.microsoft.com/en-us/windows/forum/windows_xp-hardware/mtp-usb-device-drivers-will-not-install-correctly/0ee71b7c-4ae7-403f-abbb-63c7ed9a79f9?rtAction=1387606800207 and search for the "Bret B"'s answer which has also been marked as the most helpful answer. It works perfectly. He simply says..
Go to the Registry Editor (Start –> Run –>type in, “regedit” (without the quotes) then click OK.
Search the following key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Contro l\Class\
Go upto Edit>Find, type in or copy/paste Portable Devices
In the right hand pane you will see the (Default) value “Portable Devices” on the string
Once found, you see a string value called UpperFilters –> delete it!
Reconnect the device. Finished!

I think I soft bricked the KFHD 7', help pls.

So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.

procter said:
So I was following pesano's KFHD tweak thread and found out that my int.d was probably not working, so I decided to re-do the process. I wasn't thinking straight and deleted the install-recovery.sh (this is the only one that has an original file) without copying over the new file, and rebooted. Now my kindle is bricked, I think, I can see the kindle fire logo and then the screen goes blank (still has power). When I plugged it in PC, it can be detected as Kindle, but the driver is not taking effect (yellow exclaimation in device manager), and could not connect as usb device either. Is there any easy way to get it back without fastreboot cable?
Thanks a lot.
Click to expand...
Click to collapse
No.. and really you shouldn't be doing these things without a fastboot cable.. What do you mean by the driver does not take effect? It sounds like you need to fix the bootloader. I would head over to the Kindle Fire First Aide thread and talk to Chris and see if he can help you out. Is adb working or have you checked? If adb is working then you will be able to enter fastboot without the cable..

I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2

procter said:
I meant I had the drivers installed before but now the device is not using them although it was showing up in Windows 7 device manager as "Kindle". The adb is not working, showing "device not found".
Sent from my SPH-L710 using Tapatalk 2
Click to expand...
Click to collapse
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?

lacoursiere18 said:
Ok so uninstall drivers, click delete driver software, unplug kindle and reinstall drivers.. and then see if adb works.. It should work..Did you have adb working previously?
Click to expand...
Click to collapse
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.

procter said:
I hardly remember if I used adb commands for rooting this device. I followed the guide here, which runs a series of bat files.
I tried re-installing the kindle drivers (without deleting them first, so it's an overwriting process), and then reboot the PC. Still the same symptoms: "kindle" was listed in device manager of windows 7 but with the yellow exclaimation mark, tried "update driver" pointing to the kindle driver folder but was told that system could not find/install driver in that location.
Click to expand...
Click to collapse
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well

lacoursiere18 said:
You have to update it manually. Do not let the computer find it, you have to find it where you downloaded it too. Follow this guide:http://forum.xda-developers.com/showthread.php?t=1552547 the ADB section is towards the middle of the original post.. By the way this a great guide if you hav other questions as well
Click to expand...
Click to collapse
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.

procter said:
Yes I was referring to manually point to the folder I downloaded the kindle fire usb driver when "updating the driver" in device manager. The automatic search driver never worked. But still, even if I pinpointed the directory where the driver sits, windows still told me could not install the driver.
And btw, the guide you linked to is for Kindle Fire, not kindle fire hd,, does it matter then? Thx.
Click to expand...
Click to collapse
A lot of it is the same I am sure some aspects of the GUIDE do not work but as far as installing ADB drivers it is good. Did you uninstall it and also hit delete all software with driver?

did u recover
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:

KFHD 7 Stuck at splash screen
techdeisel said:
Did u get your he back up I did something simaler and got mine back sounds like I could help u:good:
Click to expand...
Click to collapse
Hey. I am having a terrible time getting my KFHD 7 back to stock. I used KFFirstAide to root it and when I went to restore it back to factory settings it ended up with the holo launcher lock screen and the android start screen. Has no notifier bar at top or menu bar at bottom. Lock screen let's me go online, to the camera, or just unlock. Don't know what happened! It's not recognized in ADB but shows up on computer as Kindle. I just want it back to stock so I can use it again! PLEASE HELP!!

In my situation, when trying to update the "Kindle" driver from Windows device manager, use the option to let you choose install driver from a list of devices instead of pointing to the directory where you have the adb driver (it will always tell you can't install even if u point it to the right directory).
In my case, I had all the drivers installed already, so when I use the option to install from the list of known devices, I can choose so"Android adb" or sth similar in that list. And after that you will be able to restore the adb connection.
Sent from my SPH-L710 using Tapatalk 2

the the reason your kindle cannot communicate properly with your computer is because it is soft-bricked, only way to recover from a soft-brick is with the use of a fastboot cable, if you are partially soft bricked...ie boot is intact and functional but system filesystem is corrupt you may be able to access fastboot with the use of a fastboot command

Like I tell everyone, go here to solve your problem.
Sent from my KFHD using xda premium

Drivers no longer working

trying to get some help for my ZE551ML 4gb - unrooted and with the latest update
I have never had an issue plugging my phone into my pc and transferring files. I bought my daughter a BLU R1HD and that wont wont show up on any pc when plugged into USB...yes dev and debug is enabled.....installed a bunch of different drivers to try to get that phone to work and it wont....
but worse is now my phone wont show up.
I went to the main thread here and located drivers and installed, and nothing....went to asus support and dl drivers and nothing...
does anyone know why or how i can get the drivers installed on my W10 PC so I can plug phone into usb and transfer files?

In the pc's device manager, is the device listed there? And is there a yellow mark on the device name? Maybe the drivers didn't install properly, you can right click on the device and click update driver, then choose automatically, you must be connect to the internet for it to find the required driver and install automatically.

I had same issue. Makw sure phone is not. Plugged into the pc. Load up windows into safe mode with networking. Once there open device manager. From the pulldown menu choose show hidden devices then find the Asus drivers and uninstall and if available tick the box that says delete the driver.. reboot, reinstall.... Done.
This will work for most usb devices that are having issues.

Frankenberrie said:
I had same issue. Makw sure phone is not. Plugged into the pc. Load up windows into safe mode with networking. Once there open device manager. From the pulldown menu choose show hidden devices then find the Asus drivers and uninstall and if available tick the box that says delete the driver.. reboot, reinstall.... Done.
This will work for most usb devices that are having issues.
Click to expand...
Click to collapse
sadly this did not work. I grabbed the drivers from the ZF2 resource thread here at XDA
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
for the BLU R1HD I was told to install these
https://androidmtk.com/download-mtk-usb-all-drivers
whih i did and also uninstalled and resinstalled along with the intel drivers.
I did exactly as explained above and the device will not show up.
I have the Z00AD -- ZE551ML -- 4GB/2.3GHz 64gb version running Stock OS with NO ROOT - an its up to date (v 40.194)
I attached screen shot to show what I have going on - thanks

come on

Are you using the same cord for both phones with the computer? If so, try a different cord
Sent from my ASUS_Z00A using Tapatalk

Reboot the pc with the "disable driver signature verification" option and then reinstall the drivers.

This may or may not have some relevance to your problem. Try downloading a program called USB Device Viewer, run it as an administrator and uninstall all the phone drivers that are listed. Reboot your computer, plug your ZE551ML in and let it install the drivers. Hope this is of some help.

i finally fixed this bs problem. simply a matter of device manager >>>> portable devices >>>>> right click >>> update drive>>> browse my computer >>> Let me pick>>>
for me i had
Model
MTP Device
MTP USB Device
select MTP USB DEVICE >>> Click Next and done
how stupid is this? the simple solution after 2 weeks of pain in the ass is what makes this so stupid.

Nexus 6P won't install on any system

My dad has a Nexus 6P.
When he connects it to my Windows 10 PC or his own Windows 10 laptop, nothing appears in Computer (any USB mode on the phone).
Device Manager shows a yellow exclamation mark next to the device.
Trying to reinstall shows that an error occurs whilst installing 'MTP Device' (service installation section in INF invalid).
I have tried installing the standard Android USB drivers, no luck.
I've tried with and without USB debugging mode enabled.
Any ideas?

Is the device having any issues? Like is it boot looping or just dead?
If not, it definitely sounds like a driver issue. Open up your device manager and delete any Google / Android drivers and then reboot the PC. That part is pretty important. PCs can be a little wonky with drivers. After that install them via the method posted in Heisenberg's guide. Reboot the PC again and then try.
Guide Here.

RoyJ said:
Is the device having any issues? Like is it boot looping or just dead?
If not, it definitely sounds like a driver issue. Open up your device manager and delete any Google / Android drivers and then reboot the PC. That part is pretty important. PCs can be a little wonky with drivers. After that install them via the method posted in Heisenberg's guide. Reboot the PC again and then try.
Guide Here.
Click to expand...
Click to collapse
There are no drivers to uninstall in Device Manager. If I right-click on the (exclamation mark) device in question, I simply get 'Remove', which 100% doesn't uninstall drivers, presumably because no drivers are installed.
Also, the instructions there require a load of stuff (CMD, platform tools, Android debug bridge and all that rubbish), just to install the drivers. I doubt it's that complicated.

King Mustard said:
There are no drivers to uninstall in Device Manager. If I right-click on the (exclamation mark) device in question, I simply get 'Remove', which 100% doesn't uninstall drivers, presumably because no drivers are installed.
Also, the instructions there require a load of stuff (CMD, platform tools, Android debug bridge and all that rubbish), just to install the drivers. I doubt it's that complicated.
Click to expand...
Click to collapse
I've given you the tools to get it up and running, whether you choose to use them is up to you. If you read the guide, you'd see that you don't need to install the entire SDK. It's one of the first things mentioned in the drivers section. Good luck.
Edit: Read your post again. Seems you're a little confused. CMD is a program already on your Windows PC. You must use it in order to use fastboot. Fastboot and ADB are literally the drivers you need to install. Not "rubbish." Read that guide and take it to heart. There's a lot of learning ahead for you, no offense.

King Mustard said:
There are no drivers to uninstall in Device Manager. If I right-click on the (exclamation mark) device in question, I simply get 'Remove', which 100% doesn't uninstall drivers, presumably because no drivers are installed. Also, the instructions there require a load of stuff (CMD, platform tools, Android debug bridge and all that rubbish), just to install the drivers. I doubt it's that complicated.
Click to expand...
Click to collapse
Even if you don't wan't or need ADB/Fastboot, a link to the standalone USB drivers is provided in the guide. If you still have issues, an existing driver installation is likely causing the problem. There is a free tool called USBDeview you can use to get rid of the conflicting drivers.

King Mustard said:
My dad has a Nexus 6P.
When he connects it to my Windows 10 PC or his own Windows 10 laptop, nothing appears in Computer (any USB mode on the phone).
Device Manager shows a yellow exclamation mark next to the device.
Trying to reinstall shows that an error occurs whilst installing 'MTP Device' (service installation section in INF invalid).
I have tried installing the standard Android USB drivers, no luck.
I've tried with and without USB debugging mode enabled.
Any ideas?
Click to expand...
Click to collapse
If you just want to be able to transfer files back and forth between computer and phone you can try installing Huawei's Windows software which should download necessary drivers. I didn't personally find the software all that useful but it's another option if you aren't looking to do anything complicated with your phone.
http://consumer.huawei.com/minisite/HiSuite_en/index.html