Database Users

[Q] Can't install win usb drivers on XP. Tried everything

I've used different guides, searched to death, but cannot seem to get the driver installed on this XP computer. Some of the guides seem to be for Vista or Windows 7. Is there a good video for XP, or one that relates to the driver issue?

xp is a good choice for this because you don't have to care about the uac (user access control)
maybe this one helps:
http://forum.xda-developers.com/showpost.php?p=22342376&postcount=6

I was in the same boat as you but luckly i had a netbook with windows 7 starter that worked for me. I couldn't find any help for XP either.
Sent from my Kindle Fire using xda premium

Unfortunately, that did not work for me. I'm fairly computer savvy, but this has stumped me. I will keep looking.

I was getting rather upset because I could get the USB drivers installed, but ADB still wouldn't recognize my Fire.
Is this the problem you guys are having? Or can you just not get the drivers to install at all?
It turned out that my problem was a complete, "I'm an Idiot!" deal. Especially because I'm a System Engineer and should know better than to overlook the steps I did. But, in very few of the instructions of how to load the drivers, does it tell you where the adb_usb.ini file needs to be located. I was thrown off because with the Kindle Fire Utility (ver. 0.9.3 at least), it comes located in the drivers folder. Plus, just about every time this file was mentioned, it always had a big thing about adding the 0x1949 device ID, which caused me to miss the couple times I ran across instructions that said where it needs to be located.
The adb_usb.ini needs to be, in XP, located in the ".android" folder that is located in your username's folder. For example, if I am logged into my computer as PBFred, the path would be the following...
C:\Documents and Settings\PBFred\.android
I also ran into one other problem. When you manually select the path for the driver, android_winusb.inf, (which you can place where ever you want) XP shows you a list of compatible device drivers. The correct device driver, "Android Composite ADB Interface", isn't listed unless you uncheck the box that says "show compatible devices only". If you don't uncheck that box, it just lists "Android ADB Interface", which is not the right one.
Once I did that, I was good to go. The only issue I have now with the driver is for no apparent reason, it asks for the driver to be reinstalled about half the time I plug my Fire in, even though I haven't plugged any other devices in inbetween. But since the path to the driver is still saved, it only takes 2 seconds.
I hope this helps you guys out.

I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.

DukeSilver79 said:
I did these things that you've mentioned. I've gotten to the point of "rooting..."
And nothing happens...but I feel like I've gotten further than before. I will keep working at it.
I'm using the method from rootkindlefire.com
Any other suggestions to try?
And thanks for the suggestions.
Click to expand...
Click to collapse
I don't quite follow where you are stuck.
Does running the command "adb devices" list your device? If so, your USB drivers are installed correctly. Which means that the version of Windows you are running pretty much doesn't matter any more.

[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 ADB USB drivers?

After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?

beandog said:
After enabling USB debugging on my Nexus 7, I still can't get "adb devices" to list my Nexus 7. I also tried switching its USB connection type from "media" to "camera", to no effect. I have Windows 7; I see a "Nexus" device under Other Devices in my device manager, but when I try to install the Google USB drivers from the Android SDK, Windows refuses to take it.
This is going to make development difficult Anyone know where I can find working USB drivers for Windows 7?
Click to expand...
Click to collapse
If you have updated the drivers from the SDK, then your problem is probably coming from the cable.
PS: Try not to use an extension cable

When I have had this problem in the past I have found that installing PDA net solves it.
Sent from my Galaxy Nexus using Tapatalk 2

download a sync software,for example,chinese use 360 mobile assistant,it will help you to connected with PC
Sent from my SHW-M190S using xda premium

i got the problem too,just install 360 mobile assistant ,it worked.but i dont know ,any mobile assistant
used in your city？
Sent from my SHW-M190S using xda premium

You may try to use device manager to solve the issue.:
Firstly please connect your Nexus 7 to you computer using the USB cable
included in the box.
Then on the tablet,
choose "Settings" -> "Storage" -> open the menu -> choose "USB computer connection" -> choose "MTP" or "PTP".
On your computer,
1. Control Panel -> Hardare and Sound -> View devices and printers
2. Click on Nexus.
3. Click on "Hardware" tab
4. Click on "Properties"
5. Click on "Change settings"
6. Click on "Driver" tab
7. Click on "Update drivers".
I'd suggest that you repeat these steps for both "MTP" and "PTP" connection types mentioned above.
Then on your computer, run "adb devices", the Nexus 7 would be listed in the
output of the adb command.
Enjoy.

Works with PTP mode - MTP mode doesn't
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.

driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?

bytecollektr said:
driving me crazy too.
First, windows did not recognize the thing in AdB mode. I managed to get around that with PDA net. But in cmd mode running "fastboot oem unlock" it just sits there saying "waiting for device". Also switched to both usb modes under "storage" as well as tried all usb ports on my pc (running Win 7 64bit). Using original cable.
Any other clues on what to do next?
Click to expand...
Click to collapse
ADB and fastboot may have two different drivers, this is the case with most other devices.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.

Unlawful said:
ADB and fastboot have two different drivers.
Anywho here's a link to the all inclusive driver bundle. Drivers was one of the reasons I only use a linux distro these days.
Click to expand...
Click to collapse
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)

reddweb said:
just for future reference...
By default it uses the MTP mode for USB. ADB is not working in this mode, even after i follow all the steps in above post.
Change it to use PTP (Camera mode), and ADB works !! go figure.
Click to expand...
Click to collapse
This is how i got my ADB drivers to actuallly work right!! listen to this guy.

Nexcellent said:
This is how i got my ADB drivers to actuallly work right!! listen to this guy.
Click to expand...
Click to collapse
I have it in that mode, and it does not do anything, even with the new drivers.

bytecollektr said:
I have it in that mode, and it does not do anything, even with the new drivers.
Click to expand...
Click to collapse
Oh and fastboot is not available during normal operations and it has to be booted into the bootloader to use fastboot. Try using adb reboot bootloader and then when it restarts fastboot oem unlock.

I'm in the exact same situation
I'm having the same problem. I'm not exactly sure how to use the Naked Drivers pack. Can someone advise?

Easy as ADB...
Use the step by step instructions in the Nexus Root Toolkit found here;
http://forum.xda-developers.com/showthread.php?t=1766475
Hope that helps,
-CC

Set it to ptp mode, install updated sdk, and you will find proper adb driver in extras/google/usb-driver directory. After those steps adb started to work in my case' no need for third party downloads.
Sent from my Nexus 7 using xda app-developers app

I've been having the same issues with all of the new android devices I've tried to use adb on my computer for. I as able to make them work by manually installing the drivers in device manager. When you choose browse for drivers manually you can look through pre installed drivers and select adb interface and manually choose the drivers for adb and fast boot. Only issue I have is that it won't give adb root access and says rot is not available in production builds. Not sue if that's related or not.
Sent from my Nexus 7 using xda app-developers app

Windows 7 - Nexus 7 ADB Recognition
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.

ADB driver
Try to root toolkit from Wugfresh
http://forum.xda-developers.com/showthread.php?t=1766475
There is a very complete and usable guide to install ADB driver for most version of windows (XP->win 7).
You don't have to unlock or root; just use the interactive guide for driver install.
Good luck
bytecollektr said:
Still nothing. Deleted the drivers, and it obviously installed the new ones, since the name under the "device manager" changed. I go to the Android sdk and it still says waiting for device. Is there different versions of fastboot? Maybe its the wrong command? (fastboot oem unlock)
Click to expand...
Click to collapse

rootblock said:
For me, like others, choosing either MTP or PTP from the Nexus 7's USB computer connection options didn't solve the issue. Updated to the latest version of the Android SDK Tools within Eclipse [version 20.0.1], and even uninstalled and re-installed the Google USB Driver [Revision 6] within the Android SDK manager, but no luck.
What ended up clearing the issue for me was to go to Computer Management, find the Nexus device with the question mark next to it, update the driver by browsing a location on the computer, browse to the location on your computer where you saved the Android SDK [the one with the following directories: add-ons, docs, extras, platforms, platform-tools, etc], and choose that very folder containing those folders I mentioned. It should search for a while then ask you whether or not to install some Asus/Google driver.
After installing that driver, my N7 was recognized by the "adb devices" command.
NOTE: Turns out when I updated the driver, my N7 was in PTP mode, and when I switched it to MTP mode, it was no longer recognized under adb devices. adb kill-server then adb start-server should get it recognized again when you switch between MTP and PTP.
Hope this works for all of you out there, like me, who really didn't want to take the 3rd party software route to overcome this problem.
Cheers.
Click to expand...
Click to collapse
i'm having the issue with the mtp not being recognized in adb. can you be more specific in the adb kill-server and adb start-server.

[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!

No ADB mode, driver issue?

I'm Italian, sorry for my English.
A few days ago I unlocked the bootloader via Toolkit, rooted and flashed the TWRP recovery _.
But I had hard difficulty:
After driver installed, I unlocked bootloader, enable debugging and then NOTHING!
In practice, the N7 was recognized by windows 7 64bit only in FastReboot mode ..
I tried in every way possible, deleted and reinstalled the driver 50 times, restored windows to a previous point, installed the drivers manually tried without toolkit, but how ADB just do not want to know.
For hours I was still with the bootloader unlocked but without root, until came to my rescue a friend with another notebook but same windows 7 64. Load the Toolkit, install the drivers and everything goes perfectly, I do everything in 5 minutes.
On my laptop there is always the issue driver ADB, in the future I still need my PC recognized the N7 in ADB, how can I do?

One thing that I think is not well understood is that there is no "Generic Class Driver" for ADB nor for fastboot...
... even though the very driver that works for one mode (or phone/tablet device) may be perfectly fine with a different device. The wire protocol for both fastboot and adb are extremely simplistic.
So, what that means is that if the Hardware ID used by the USB device endpoint registers on the bus with a different VendorID/ProductID, Windows will (correctly) not use a previously-installed ADB driver, or previously installed fastboot driver - even though they would probably work just fine.
Here is an example. The Nexus 7 registers the following Hardware ID when ADB debugging is turned on in the OS:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
On the other hand, if you are using TWRP, it's adbd daemon shows up on the PC as:
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
This means that you might need to install a different driver for using the ADB with the OS, and a different driver for ADB under TWRP - even though it is exactly the same hardware on the other end of the cable! In the absence of a generic class driver for a given USB endpoint, Windows tries to match drivers in it's local (& internet) database based on this VID/PID pair.
If you have a look at the [ADB/FB/APX Driver] Universal Naked Driver 0.72 thread - and download it and have a look at it's included "android_winusb.inf" file - you will see literally hundred of different VID/PID pairs in the driver's android_winusb.inf file in the installer package, corresponding to many hundreds of phones/tablets. Same driver with hundreds of devices listed as compatible.
In the past I recall taking the Google (SDK) USB driver, and manually editing into place matching VID/PID pairs for a HTC phone into the .inf file. It worked perfectly; I probably flashed that phone hundreds if not thousands of times using the Google Driver (My PC is a Windows 7 Pro x64 machine btw).
Anyhow, I have pulled this stunt twice now - once editing the .inf file for the Google Driver, and I did it once with the Universal Naked driver too. You can choose which driver you want to start with.
If you want to give it a roll, you can start with any of those three drivers:
- Google (SDK) USB driver
- XDA "Universal Naked" driver
- Asus Nexus 7 USB Driver (Look under Download)
Note that since you are using W7 x64, make sure that you add each new entries to the .inf file twice - once in the ".NTx86" section, and duplicated again in the ".NTamd64" section. When editing .INF files, make sure to use an editor which preserves simple text file formatting - use "notepad", not "wordpad"
If you want a reference for what values to use, see the bottom end of this post. You should see exactly these same values in your Device Manager, however.
Note that if you see the device show up in the Device Manager as being correctly identified and marked as "working normally" - but it doesn't work - you should probably remove that driver and re-install from a different driver package.
This would certainly be the case for any drivers you saw associating with VID/PID pairs that look like:
VID_18D1&PID_4E40 bootloader/fastboot
VID_18D1&PID_4E41 single adb
VID_18D1&PID_4E42*&MI_01 composite adb
VID_0955&PID_7330 avx mode
VID_18D1&PID_D001 adb in TWRP (maybe CWM too, I didn't check)
That's a lot to throw at you, especially with Italian <=> English in the mix.
Feel free to ask questions.
bftb0

Hello,
I tried to follow your advice but I have not solved.
I'll explain what I did, so you can correct me.
-Uninstalled previous drivers (from device manager, control panel)
-Restart the PC
-Modified the inf file. Package Asus Nexus 7 USB driver (ntx86 and NTamd64 sections) attach screenshots
-Linked N7 (usb debugging actived)
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
I tried to change also too XDA "Universal Naked" driver by following the same procedure.
I tried to create another account on my pc, but no ADB!
View attachment 1734997

Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD

stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse
Use "Google USB drivers" you get after you install from here http://developer.android.com/sdk/index.html
Its drivers work with 4.2.2
I got 4.2.2. rooted with ADB working now via only this and no other method

No problem with adb in 4.2.2... I tested yesterday (no need psw too...)
stonebear said:
Did you update to 4.2.2?
The is something to do with adb in that update, needing a password or something. I am not sure but if you did update you might want to check that.
Sent from my Nexus 10 using Tapatalk HD
Click to expand...
Click to collapse

Marco16V said:
-Found portable device in device manager, update drivers manually from the Nexus 7 Asus USB drivers
Click to expand...
Click to collapse
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.

bftb0 said:
Is this the only device which shows up in the device manager? The "Portable Device" is either the MTP or PTP endpoint - not ADB. The latter (adb) should show up elsewhere in the device manager.
You should certainly NOT be trying to install fastboot/adb driver on MTP/PTP endpoints!
I think perhaps I am not understanding because I am guessing at certain details.
Q1) Do the drivers appear to install correctly?
Q2) When you have the N7 in the corresponding mode - whether or not you observe (device manager) "working normally" or "unknown device" - do you see the following Hardware IDs showing up in the device manager?
Bootloader Fastboot Mode:
USB\VID_18D1&PID_4E40&REV_0000
USB\VID_18D1&PID_4E40
OS adb:
USB\VID_18D1&PID_4E42&REV_9999&MI_01
USB\VID_18D1&PID_4E42&MI_01
TWRP adb (Possibly also CWM adb, I haven't checked it) :
USB\VID_18D1&PID_D001&REV_9999
USB\VID_18D1&PID_D001
Q3) I presume you went through the same install sequence on your PC that succeeded on the other laptop - in the event the problem is a hardware problem, did you try a different cable or USB port on your PC?
Q4) When you remove drivers, are you requesting that the drivers be removed from the PC?
The 4.2.2 authentication issue might be an issue (although I suspect this is a adb program version issue, not a driver version issue. In any event, it wouldn't effect the behavior of adb in TWRP/CWM.
Sorry for all the questions.
Click to expand...
Click to collapse
When the drivers are not installed and I connect to pc N7, is only recognized as a portable device, then later recognized as Google Nexus 7.
To install the drivers (modified as described) I click reinstall driver, then later recognized (if connected to pc in android mode, with usb debugging actived) as Android Device in another voice, ADB interface. But is not recognized by the toolkit under adb devices, and even when I try using cmd.
1-When I install the drivers. seem to be installed correctly.
2-Sorry, where can I find Hardware IDs in Device Manager? What is the difference between OS adb and TRWP adb?
3 - In other pc (with same N7, same cable, same driver, same toolkit) I had no problems. I tried to change only the USB port.
4-I uninstall the driver from device manager (uninstall voice) and ask to be also uninstalled software from the PC
In some Italian forum, I found people with the same problems.
Solved by formatting PC. I would not do that ...
Thanks for your help, sorry for my English and my limited skills

AW: No ADB mode, driver issue?
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app

AndDiSa said:
Try to download the latest Android SDK and try to connect with that adb version. Adb with version < 1.0.31 will not work correctly with Android 4.2.2.
Sent from my Nexus 7 using xda app-developers app
Click to expand...
Click to collapse
I tried sdk but I have not solved.
I use Android 4.2.1. I'm having problems with the update! I can not update OTA (N7 stuck under the impending reboot). I also tried to download the zip file to upgrade the memory and flash it from recovery but the installation is not completed (error 7 build.prop).
I also tried to flash the factory image 4.2.1 (keeping userdata) and start again. Nothing, same mistakes!
Too many problems!

Marco16V said:
2-Sorry, where can I find Hardware IDs in Device Manager?
Click to expand...
Click to collapse
(Note I attached some pictures below)
From the Device Manager:
- Select the Device in question by right-clicking. Choose "Properties"
- A window with three tabs will appear: General, Driver, and Details. Select Details
- The "Property" combo-box-selector has 20 or 30 items - the 2nd one in the list is Hardware Ids. I attached two pictures from Win7-Pro-x64 (below)
But note as I said before: You should NOT be seeing the ADB endpoint under "Portable Devices" - if ADB Debugging is turned on in the OS, you should see it under "Android Phone" or something similar. In any event, the hardware Ids will identify it exactly
Marco16V said:
What is the difference between OS adb and TRWP adb?
Click to expand...
Click to collapse
Well, as far as the behavior of the USB driver on the PC, almost nothing. Unfortunately - for better or for worse - both TeamWin (TWRP) and CWM authors put their ADB interface on the bus with the VID/PID pair of USB\VID_18D1&PID_D001, whereas the OS puts all its USB interfaces on 18D1/4Exx.
So, even if you get a driver installed for the OS "adb" mode (say by using the Google SDK USB driver or the Asus Nexus 7 driver), it won't work for the custom recovery... unless you fix up the driver installer package to have the matching VID/PID pairs (18D1/D001) in the .INF file for that driver.
I think folks find this confusing - they think, "wait, I have a ADB driver installed" - why does it not work?
OK, there are a couple more things to try (at least before I give up). Roughly they try to answer these questions:
Q1) Is this a toolkit issue, or a driver issue?
Q2) Is it a prior driver you installed that you are not observing that is causing the problem?
The first one (Q1) is easiest to diagnose: when your PC Device Manager indicates that a device is "working normally" - AND THE VID/PID ID MATCHES WHAT YOU SHOULD EXPECT FOR THE MODE THE TABLET IS IN (regular OS, recovery boot, fastboot mode), can you communicate with the device from the Windows command line? e.g.,
Code:
C:\foo> cd C:\blahblah\sdk-platform-tools-directory
C:\blahblah\sdk-platform-tools-directory> fastboot devices
or
C:\blahblah\sdk-platform-tools-directory> adb devices
If you can communicate with the tablet from the command line - your device ID will be printed by the above commands, then you don't have a driver problem at all - there is something screwy about the way your toolkit is installed.
OK, Q2 -
When Windows installs a driver, it caches it into a kind of database. I suppose it is possible that a prior driver installation might be causing trouble. You can observe - from the device manager - all the drivers that are installed - even for devices that are not currently connected to your computer.
This is done by setting the "devmgr_show_nonpresent_devices=1" environment variable. It can be done semi-permanently this way, or for a single invocation of the device manager this way..
See the third image attached (devmgr-all-devices.jpg ) - it is my computer in that "show all devices" mode. See all that rubbish in there? It's from other Android devices (HTC, Samsung, etc).
You can walk through each one of those - even the devices that are not currently attached - and inspect the VID/PID pair to see if they happen to match the values that you are expecting to see for the different operating modes on the Nexus 7. I'll leave it up to you whether you want to do this or not; it is a bit tedious. Just don't start deleting drivers willy-nilly if you don't know what they are associated with.
Marco16V said:
Thanks for your help, sorry for my English and my limited skills
Click to expand...
Click to collapse
I am understanding everything you are saying - and your english is far better than my italian
good luck!