Database Info

USB Driver Issues

Has anyone else using XP had any issues installing the USB Driver for the Magic? I've tried every possible method to get it to work and it just will not install. A method that appears to work for some is in this link-
http://www.mail-archive.com/[email protected]/msg09692.html
Although this did not work for me. There was also a suggestion of copying the inf file and renaming certain strings by one digit. Any suggestions?

I used the latest SDK with the included driver. Set the environment paths. Nobody has any other suggestions?

renaming the inf file solve the prob for me.

radonsg said:
renaming the inf file solve the prob for me.
Click to expand...
Click to collapse
What did you rename it to? I renamed it to android_usb_Magic.inf like the linked post said.

Hi Gimpeh
This worked perfectly for me. The issue was once it installed the Windows drivers there was no way back. However, follow this
So you plugged your Android phone into your Windows machine having forgotten to switch on USB debugging…
Menu > Settings > Applications > Development > USB debugging
Then Windows detected your device as a USB-Mass storage device and won’t change the settings, regardless of how many times you uninstalled the device. Thread on it here.
This solution worked for me and didn’t require editing the registry settings (I don’t know if the reboot is unnecessary).
(1) Plugin phone
(2) Uninstall any drivers that mention “HTC Android Mobile USB Device”
(3) Unplug phone and restart
(4) Install and run USBDeview
http://www.nirsoft.net/utils/usb_devices_view.html
(5) Using USBDeview find the Android device (for some reason Windows hides uninstalled drivers instead of deleting them), right click on it and uninstall.
(6) Follow the official instructions to the letter this time.
http://developer.android.com/guide/developing/device.html
Click to expand...
Click to collapse
http://blog.zedray.com/2009/06/16/when-adb-won’t-detect-your-android-phone…/
Good luck!

This is pretty close to the instructions I followed earlier. No resolution. All HTC device drivers have been removed. Although there is a composite USB device installed (not labeled HTC). I know sometimes if windows does not recognize a device it will show it as a composite.

Install HTC Hotsync - http://www.htc.com/sea/SupportViewNews.aspx?dl_id=573&news_id=169
Have your phone plugged in first then install the app. You don't need the additional drivers it list. Just the Hotsync program.
That did the trick for me.

edit the inf file under the x86 folder inside the usb driver.
replace the vid_0bb4&pid_0c02 with vid_0bb4&pid_0c03
cos somehow my htc is recongnise as vid_0bb4&pid_0c03 instead of vid_0bb4&pid_0c02.

Hotsync didn't work and neither did replacing the string from 02 to 03. I got it to recognize at work on a Vista machine but since then it will not recognize on my home XP or any other Vista machine. When I select Have Disk and select the INF file it says something to the effect of There is no driver information for this device.
Additional Note: Although the device was recognized on that one vista machine, it would not recognize when it was in HBOOT mode.

try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.

radonsg said:
try to search your registery using the string "vid_0bb4&pid_0c0"
and c wat is your system detecting it as and edit the inf accordingly.
Click to expand...
Click to collapse
CTRL+F Put in that key and found nothing.

I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.

Cheesebaron said:
I also have the same problem, just with Vista. Happened after I plugged in the phone the first time without the USB dev debug enabled. I tried a lot of things such as the mentioned USBDeview software and so on. None of the methods have worked. So I am using my Linux laptop to do stuff on the phone.
I guess the only sollution is to reinstall the OS, Windows is very strange a lot of times.
Click to expand...
Click to collapse
How would you go about flashing the recovery.img in Ubuntu. I didn't see any drivers for linux.

Driver
http://developer.android.com/sdk/1.5_r2/index.html
Additional work for linux(add rules)
http://developer.android.com/guide/developing/device.html

I finally figured the damn thing out. For some reason windows recognized the ION as a Video device and installed it as such. I figured it out after I got irritated and just uninstalled everything that wasen't plugged in.

woa.
TT is strange. Which version of windows? vista or xp?

Its XP Home on a HP Mini. I'm glad I finally have it figured out. I've probably spent 20 hours on this issue alone. I even went to Ubuntu since Windows was being...well windows.

[Q] Device debugging with Eclipse

I'm very new to Android development (my first app), so please bear with me.
I'm using Eclipse with the android SDK. Using the Android SDK and AVD Manager, I've installed the Usb Driver package, rev 3.
To this point, I've been using the emulators to debug and develop. Now I need to debug on my device (bought a ViewSonic GTablet). Somewhere in my searching for solutions to how to get this going, I found that I need to get the drivers correctly installed. Those instructions directed me to:
- Modify the android_winusb.inf file in the usb_driver folder
- Install USBDeview program
- Removed all drivers associated with Andriod and NVIDIA Tegra 2 (I think there were 3 or 4)
- Connect the GTablet with USB and follow new found hardware wizard. Direct it to modified .inf file
The problem is, the "Found New Hardware Wizard" does its thing automatically without user intervention. I end up with 1 NVIDIA Tegra 2 USB Device driver. I think I'm supposed to have another driver called something like "Android Composite ADB Interface".
I tried using the Add Hardware wizard to install this, but it always results in saying "This device cannot start. (Code 10)".
Sorry for this lengthy explanation...can anyone please help?

Hi,
I struggled getting adb working until today. There's info for getting adb working with Gtab here:
http://forum.xda-developers.com/showthread.php?t=827209
The key for me was adding the 3 lines to the .inf. Make sure you have USB debugging enabled on the tab.
Then, in Win Device Manager uninstall the devices under Android.
Then unplug the USB, then reboot Windows.
After Windows starts, plug in USB, then when wizard pops up, browse to the USB driver dir.
Jim

Thank you jimcpl for the reply.
It's still a no-go.
I have done all the steps lined out in the link you provided--and thought your reboot step may be the key to making it work, but that didn't do it.
When I plug the GTab back in, I do get a "found new hardware" popup message, but no wizard is appearing. The result is, the system is installing:
(With the help of USBDeview window)
Device Name: NVIDIA Harmony
Description: NVIDIA Tegra 2 USB Device
Device Type: Mass Storage --> This one I can use to transfer files
...
I see no other devices associated with the GTab
What device type should the "Android Composite ADB Interface" be?
Also...Maybe this is a silly question, but isn't it the miniUSB connection I should be plugging in to?

More info on the problem
I found that when attempting to install the adb driver, the system is not using the .inf file I'm pointing it to. It is using one titled "oem24.inf". I found this by looking in Start->All programs->Accessories->System Tools->System Information. Then under Software Environment/Signed Drivers there is the "Android ADB Interface" listed.
I can see the referenced oem24.inf file (and associated .pnf files) under C:\Window\inf folder
BTW. I'm on Windows XP Pro SP3
In here I see at least 3 .ini files that have the three lines that we're using to modify the android_windusb.inf file with.
So the question now becomes...
How do I get the installation (or driver update) to use the .inf file I point it to?
Another recent thread suggested that window's supplied drivers will have to be removed. Are these what he may be referring to? If so how do I do that?
PLEASE -- I need a response from someone that knows something about this!

Memory doesn’t serve me too well in windows xp but go to device manager, click on action, add legacy hardware, Install the hardware that I manually select or something close to that then, have disk and point to the directory where the inf is located and install it. Make sure you modded the inf from the post above and you should be good to go.

Thanks...but, not the solution
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck

JRDev said:
I really appreciate the suggestion littleoldme!
In XP, Device Manager/Action menu only has the "Help" link which lauches the Microsoft Management Console. Doing a search for "Legacy" in the console results in no hits.
So I'm still stuck
Click to expand...
Click to collapse
I found your answer.. see URL below
tegradeveloper.nvidia.com/tegra/forum/after-installing-froyo-adb-cant-see-device

I want to thank all who responded with suggestions to this problem.
I've followed all advice given and carefully followed all directions given in suggested links.
Unfortunately, there seems to be some underlying condition on my pc that is preventing the successful installation of the necessary adb driver. No matter what I have done so far, Windows is choosing NOT to use the driver I point it to, and use what it wants instead. I don't even get the "New Hardware" wizard when following the directions. It installs automatically and I have to launch a separate "Install new Hardware" dialog.
Anyway...through persistence, I've been able so far to develop this first app without the debug connection to the device using the development emulators, then installing the signed .apk on the device for further testing (via the one USB mass storage connection I do get).
So, maybe one day I'll find the reason, but for now I'll be purging on to get the app ready to go.
Thanks again for all help received.

I just come across this thread. After insert the usb device, then you might might find the unknown device in device manager. unstall that unknown device. And then do a hardware scan again in device manager. After it find your device again, point back to your USB inf file. It might work this way.

One thing I forgot. Do not unplug your device between uninstall and hardware scanning.

AAAHHH! GTAB Eclipse ADB frustration!
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.

rlapela said:
Thanks for all the tips, everyone, but I've been trying for days to be able to connect my gtab to use as a device for installing/debugging my apps. I too am running Eclipse using the emulators to date.
I've tried the steps outlined in the link provided by jimcpl, as well as others that are slightly varied, but to no avail.
I am running Vista SP2. My Gtab has been rooted, running ClockworkMod, and TnTLite 2.2. I also updated the Google USB package, rev 4 via the SDK/AVD Manager after attempting to use the rev 3 usb package.
Should any of these be reason why I cannot connect my gtab to Eclipse via ADB?
I'm totally frustrated...If anyone has any other suggestions, please forward them on!
Thanks in advance.
Click to expand...
Click to collapse
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim

jimcpl said:
On the Gtab, is USB debugging enabled?
On the Windows machine, did you add the 3 lines for tetra?
Jim
Click to expand...
Click to collapse
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!

rlapela said:
Thanks Jim...Yes, and yes. I finally got connected. Old drivers were conflicting, and even though I'd repeatedly uninstall them in Device Manager, the ADB USB drivers would load, but not start the device. I finally got USBDeview to uninstall them successfully after many attempts and reboots, plugged in my GTab, and finally installed correctly, and it works like a champ!
Click to expand...
Click to collapse
Hi,
Ok, thanks. I'm glad it's working for you now.
FYI, I think that when you "uninstall" a device from Device Manager in Windows, it doesn't physically delete driver files, etc. from your hard drive. It just removes the references to the removed device drivers from the Windows configuration.
That's why if you reboot, or do a scan for devices again, and if Windows thinks that it detects the physical device, it'll try to use the same driver files, .inf, etc. In that case, you have to force the installation of the new/correct driver, by not letting Windows automatically find the drivers (because otherwise, Windows will find the same ones from before, the non-working ones).
It's kind of a pain sometimes ... I ran into the same thing when I tried to install the ADB USB drivers. I downloaded the USB driver files from Android dev website, but those are generic. They have stuff in the .inf for some phones/devices that Google has relationships with, but not the "proprietary" ones like for the Gtab. That's why you have to add the 3 lines, which match (I guess) the Gtab.
Jim

[Q] Nexus S Root-Windows requests 'Android 1.0' hardware driver (and other weirdness)

Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.

Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928

webplus said:
Hey man what you need to do is this.....I had the same problem with drivers. Once I figured that out things ran smooth.
PDAnet drivers
http://forum.xda-developers.com/showthread.php?p=9861928#post9861928
Click to expand...
Click to collapse
You're a scholar and a gentleman--and absolutely right.
Looks like the default drivers from Google are borked. Downloaded the ones from PdaNet and things went smooth like butter. Thanks for making my day!!

haha no problem took me 6 hours of trying everything to figure out what I was doing wrong. Glad everything worked. If not for these forums and some great minds on these boards many of us would still be sporting a locked phone......so KUDOS to them!

bluetrevian said:
Team XDA Developers,
It's been a long frustrating evening and I write to you in a desperate plea for help. First off--YOU ARE ALL GENIUSES. That being said let my scrubby noobermcnooberstein train of thought commence.
Found a lot of help from 'drexman8244' on the Nexus S 'fastboot help?' thread and although I've made it decently far... I've hit a wall that I cannot overcome.
First--the specs. Running Windows XP SP3 32-bit. The phone is a Samsung GT-i9020 (aka Nexus S).
Second--I've successfully installed the Java SDK, the Android SDK, downloaded USB drivers from Google, downloaded/installed a copy of ADB into the '/SDK/tools' directory, configured the PATH value in the Windows System Environment variables in Control Panel 'System', and basically set things up to rock and roll.
Third--I turn on my Nexus S, enable USB debugging, and attach the device to the workstation. The system detects the device and produces the following output (which appears to install the Android ADB driver and successfully establish a connection to Nexus S). Verified this step by entering 'adb devices' in a command prompt. Working great!
Fourth--In the command prompt I enter 'adb reboot bootloader'. The device reboots... but here's where things get strange. The device enters Fastboot (bootloader) mode and the Windows workstation request an additional 'Android 1.0' hardware device driver to continue. (I've searched far and wide and can't seem to find something that resembles this driver)
Fifth--Regardless of my efforts to direct the Hardware Installation Wizard to the 'C:\Program Files\Android\android-sdk-windows\google-usb_driver' location on my workstation... it just doesn't seem to accept that as a valid driver for the device in Fastboot (bootloader) mode. Blows my mind.
Sixth--??? What steps do you fellas think I should take next?! I've obviously tried uninstalling the device from the workstation, rebooting the Nexus S and the workstation, attempting to install the ADB driver before attaching the device and rebooting into Fastboot. Nothing I've tried seems to work.
Any input is especially appreciated and I hope that there's nothing left out. Warm regards--
The Kid
Edit: Posted an album on the Imgur account in case anyone wants to look at screenshots of the steps provided.
Click to expand...
Click to collapse
as far as the USB driver and such, dont point it directly at the USB-driver folder point it at the SDK folder and then click the box that searches the sub folders

The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.

jimmypopulous said:
The drivers from Google aren't borked. You install one driver - the "normal" Android USB interface - for when the phone is plugged in and fully booted, and another - the "Fastboot" interface - for when the phone is plugged in but in recovery. For the latter, you have to pick the driver manually and do a force install, as Windows won't recognize the device.
Both drivers are available in the usb-drivers directory in the Android SDK directory, provided you loaded the SDK manager and downloaded the USB drivers.
Click to expand...
Click to collapse
This is correct. Oddly, I had no problems searching with the driver with the wizard on my win7 x64 pc, but had to manually point it for the fastboot relevant driver on my laptop, running the same OS.
Basically, as jimmypopulous says, you need to manually select the usb driver when you're in fastboot, according to my experience.

I hear what folks are saying about the Google USB drivers working fine for most installs.
That being said... No matter how many times I manually provided the path to the Google Fastboot driver location the OS refused to accept them as valid. (Seems like there are others that experienced this problem from a quick glance at the forums.)
In either case it seems as though the alternative drivers resolved the problem and I appreciate all the feedback that was given!
The Kid

I had the same issue - my Nexus One always worked fine on my laptop but even after updating the SDK & drivers I couldn't get fastboot to work with my Nexus S.
ADB worked fine but my laptop didn't recognise my phone properly via fastboot.
After installing PDANet, fastboot works as well now - thanks very much for your help, my NS is now rooted!

Hi,
This is my first post so bear with me and let me know if I'm outta line in any way.
I'm trying to root my nexus s and I am running XP. I can get ADB devices to work but when it comes to fastboot my device is not recognised. I have been trying for a couple of days and still cannot get it to work! I have installed PDAnet and and tried force installing the drivers but I can' get them to install. When I click install driver from a list and browse to the drivers it says that the specified location does not have information about your hardware. Is there something I am doing wrong here? Is there another way I can force install the driver?
Also I am a MASSIVE NOOB so please try and be specific when giving me directions.
Thank you XDA Overlords!

Uninstall all references to the drivers. your phone should show up with a bang once done properly.
Then follow the excellent guides here to root your phone properly
Sent from my Nexus S

Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App

Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
;Nexus S
%CompositeAdbInterface% = USB_Install, USB\VID_18D1&PID_4E20&REV_0100
Click to expand...
Click to collapse
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"

When you say uninstall all references what do you mean? Again, I am a massive noob. Do you mean uninstall the device with USBDeview from all the previous times I have tried installing it? I've tried that multiple times and still can't get it to work

matt2053 said:
Also make sure you have the phone connected and in fastboot mode when you install PDAnet.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
In fastboot the ns just comes up as unknown device with hardware id of USB\UNKNOWN.
I tried just entering that id into the .inf file but that didn't help.
Anyone got any other ideas?
Thank you for these ideas I'm not gonna give up yet!

thejug02 said:
When I try install PDAnet with the ns in fast boot mode the installer says please connect your phone to complete the installation. Is there another way to install it where this won't happen?
Click to expand...
Click to collapse
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App

matt2053 said:
Maybe the installer has changed since I did it.
Try running PDA install, put phone in fastboot, then plug in when prompted.
Sent from my Nexus S using XDA App
Click to expand...
Click to collapse
Yea maybe it did change. When I run the installer it stops and requests that you connect the device and put it in debugging mode. When you connect the ns in fastboot it doesn't read it as the ns so just continues to ask you to connect the ns.
Thanks for the idea though! Keepem coming people!

I just uninstalled the drivers from my laptop and installed again using PDAnet method. It worked without a problem.
The only other thing I can think of is to boot phone and make sure USB Debugging is checked and try again.
Sent from my Nexus S using XDA App

lambda30 said:
Adding these 2 lines in the android_winusb.inf file from the google "usb_driver" folder helped me.
Detailed:
If your PC displays "Android 1.0" in Device Manager (when you try to connect the phone through fastboot), then go to Android 1.0, Properties, Details tab. Select Hardware ids.
USB\VID_18D1&PID_4E20&REV_0100 This part should be exactly the same with the one you add in "android_winusb.inf"
Click to expand...
Click to collapse
It helped me too! It must be added under the [Google.NTx86] box

Nexus 5 showing up as ACER ADB Interface Windows 8.1

Hi guys, I recently installed windows 8.1 and now my N5 shows up in device manager as ACER ADB Interface and I can't acces MTP , I didn't had this problem with windows 7 , it worked perfectly back than ( i have unlocked and rooted my N5 with windows 7 without any issues ) . What can I do to make it work with windows 8.1 ?

I had the same, you have to go into Device Manager and roll back the driver to the Google one. Proper PITA

I can't do it, the roll back option is grayed out

I have managed to make it work, nevermind .

SilentGTX said:
I have managed to make it work, nevermind .
Click to expand...
Click to collapse
Why not actually post what you did to fix it so it can benefit others in the future? Just a thought...

EddyOS said:
I had the same, you have to go into Device Manager and roll back the driver to the Google one. Proper PITA
Click to expand...
Click to collapse
I rolled the driver back, but it keeps updating to it. I've uninstalled and deleted the driver, yet it keeps reinstalling it. Somehow, my MTP connection started working again. Not sure how though. If I knew which KB update it was, I'd uninstall it from there.

wvcadle said:
I rolled the driver back, but it keeps updating to it. I've uninstalled and deleted the driver, yet it keeps reinstalling it. Somehow, my MTP connection started working again. Not sure how though. If I knew which KB update it was, I'd uninstall it from there.
Click to expand...
Click to collapse
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...

EddyOS said:
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...
Click to expand...
Click to collapse
I'm not sure how to do that, because, of course, if you try to update it, it will say that the Acer one installed is already the best driver. And after uninstalling it, upon plugging it back in, it updates to the Acer driver automatically again.

wvcadle said:
I'm not sure how to do that, because, of course, if you try to update it, it will say that the Acer one installed is already the best driver. And after uninstalling it, upon plugging it back in, it updates to the Acer driver automatically again.
Click to expand...
Click to collapse
You have to manually check and select 'choose from a list' and you'll see the MTP option as well as the Acer one. Select the MTP one and you're good to go

EddyOS said:
You have to manually check and select 'choose from a list' and you'll see the MTP option as well as the Acer one. Select the MTP one and you're good to go
Click to expand...
Click to collapse
Btw... thanks for your help.
I went through those steps, but on my system, the MTP driver wasn't listed as an option.

wvcadle said:
Btw... thanks for your help.
I went through those steps, but on my system, the MTP driver wasn't listed as an option.
Click to expand...
Click to collapse
Hmmm, I've only ever used the Google drivers from the SDK until this stupid ACER one appeared. Managed to get back to it now so it's all good. Perhaps download the Google driver and then point to it?
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip

Yeah , I forgot , sorry about that . I managed to make it work by downloading this drivers " https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip " . After i have extracted the driver i plugged my N5 to the PC, than I went to the Device Manager i right clicked the Acer ADB Interface and I have selected Update Drivers . After that I selected the folder where i have extracted the drivers , than i chose " Let me pick from a list ... " , I selected MTP USB Device and Voila , it works !
PS: You can also try to install the LG Driver " http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 "

EddyOS said:
The other option is to manually change the driver in Device Manager from the ACER one to the Google one. I think it's happened as M$ have the ACER driver digitally signed whereas the Google one isn't so it'll always choose the signed driver...
Click to expand...
Click to collapse
Thanks For your help. It worked.

SilentGTX said:
Yeah , I forgot , sorry about that . I managed to make it work by downloading this drivers " https://dl-ssl.google.com/android/repository/latest_usb_driver_windows.zip " . After i have extracted the driver i plugged my N5 to the PC, than I went to the Device Manager i right clicked the Acer ADB Interface and I have selected Update Drivers . After that I selected the folder where i have extracted the drivers , than i chose " Let me pick from a list ... " , I selected MTP USB Device and Voila , it works !
PS: You can also try to install the LG Driver " http://tool.xcdn.gdms.lge.com/dn/downloader.dev?fileKey=UW00120120425 "
Click to expand...
Click to collapse
LG driver helped me to resolve issue while installing LG driver got pop up message for the missing MTP package for windows 8.1, i followed link to download missing package and install after reboot it resolved issue in my Windows 8.1, Thanks for your help.:good:

I can never seem to get adb or fastboot to work I gave up and dual booted my computer with Linux Linux hasn't given me problems with adb or fastboot
Sent from my Nexus 5 using Tapatalk

This worked for me
Hi guys, I had the same problem. My phone was configured as MTP but when i connected to Win 7 it would appears in the Device Manager list as "ADB", this wouldn't allow me to transfer files so what worked for me was:
1- Connect your Mobile to the PC and it appears as ADB Driver (In the device manager screen), rignt click on ADB and select Browse my computer for driver software.
2- Choose let me pick a from list of devices on my computer and choose the option MTP instead of ADB.
3- Did that and problem solve, hope this helps for you !!

Delete this Acer ADB driver when you uninstall it
I have the same issue. Here is what I did and that resolved the issue. Go to "Device Manager" to uninstall the Acer driver. The uninstall window pops up asking you if you want to uninstall it. There is a check box that says "Delete the driver." Make sure you check that off and then go ahead and uninstall it. Once that's done, plug your Nexus 5 back in. The correct MTP driver will now be installed and your computer will recognize the phone normally. Hope this helps.

Experiencing the same on Windows 7...have tried everything suggested
Really hoping someone can help because I've just about had it with this. I'm running Windows 7 Home Premium 64-bit. I have a brand new Nexus 5 16GB. As others have indicated, when I plug my phone into my computer with debugging enabled, it creates an "Android Composite ADB Interface" device listed under "ACER Device" in Device Manager. See attachment.
I have tried every permutation of the 'uninstall driver, manually install Google USB driver' solution, to no avail. The best way I can describe what I'm seeing is that Windows is forcibly categorizing the device as an 'ACER Device' even though the driver files themselves are telling it otherwise.
If debugging is DISABLED, and EITHER MTP or PTP is ENABLED, everything is just fine - the default Windows drivers for those devices kick in, and no 'ACER Device' category is created.
If debugging is ENABLED, and MTP and PTP are DISABLED, when I tell Windows to use the Google USB driver, it says that the device could not be installed.
If debugging is ENABLED, and MTP is ENABLED, the 'ACER Device' issue rears its ugly head even when I tell Windows to use the Google USB driver.
I've already disabled Windows automatically fetching a driver online, so that's not to blame.
If this is the result of a Windows Update, does anyone know the number of the update so I might try uninstalling it? I can't seem to find it despite searching.
Hoping someone out there can help. Thanks!

[FIX] USB Tethering lags/freezes on windows 8.1

Everytime i tried to use USB Tethering with my Xperia U on my Windows 8.1 (Bing's single language Edition [Genuine Licence]) have always lags or even freeze the taskbar and some other tool settings on my operating system. After some testing and googling a little bit i found a solution for this Microsoft Issue: Update your NDIS 5 Driver to NDIS 6.x.
Verify if your device is using RNDIS 5 driver (1):
Open Device Manager from Control Panel and expand “Network Adapters.”
Plug in your device and enable USB Tethering so that the device is detected as Remote NDIS based device.
This should now create a Network Adapter named as “ [Your Device Name] Remote NDIS based [internet Sharing/network] Device.”
Right-click the Adapter and select Properties.
Select the Driver tab and then click Driver Details.
You can see the driver files if the files are named usb8023x.sys and rndismpx.sys you are using RNDIS 5 Driver.
Updating your driver:
Option 1: Update your driver NDIS driver manually by selecting the driver's list option on windows wizard driver's update. Unselect show all compatible hardware option, you will get a Microsoft's driver list. You should seek for a RNDIS 6 USB device and click next. This should work on 32bits or 64bits edition.
Option 2 (64 bits only)(2): Just Download and update your NDIS driver from the attachment below. On Driver's Wizard installation must go through selecting the driver from a list.
Sources:
http://support.microsoft.com/kb/2923775 (1)
http://www.driverscape.com/download/remote-ndis-compatible-device (2)
https://msdn.microsoft.com/en-us/library/windows/hardware/dn449742%28v=vs.85%29.aspx. Microsoft says NDIS 6.4 is included on Windows 8.1, don't know why windows chooses RNDIS 5 over RNDIS 6 on my laptop.

Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards

MHP2013 said:
Thanks for your great tutorial. I tried updating the drivers but stupid windows doesn't let me do it. If I try the first method to install and click the "RNDIS 6 Adapter" drivers in the "Microsoft" list, it shows an error that some "required line in the INF file could not be found" (translated from german).
Then if I try the manual method (downloading the zip), windows refuses to install and says "the latest drivers is already installed" (translated).
I also tried uninstalling the drivers but as soon as I plug in the device it installs the wrong drivers again manually. I cannot stop this also because of the extremely lag in the taskbar...
Thanks windows!
regards
Click to expand...
Click to collapse
Try this before installing the NDIS 6 driver:
http://www.tomshardware.com/faq/id-2165451/dont-windows-windows-automatically-download-device-drivers-icons.html
If above didn't work try to disable driver signature verification:
http://www.howtogeek.com/167723/how-to-disable-driver-signature-verification-on-64-bit-windows-8.1-so-that-you-can-install-unsigned-drivers/

Perfect, Thanks for this fix! Didn't need the driver as RNDIS6 driver is already included in Windows 8.1
NDIS Compatible works without huge driver lockups, but RNDIS6 USB Adapter also works like a charm. (Nexus 5)

Facing the same problem, here.
Tried both options, still facing the same problem..
Any ideas?

I am having the same issue in Windows 10 64-Bit.

Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.

Ano59 said:
Got this issue after upgrading Windows 10 (I was already on 10). This solved the problem perfectly. Thanks for fixing yet another fail from Microsoft.
Click to expand...
Click to collapse
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?

DubleJayJ said:
I keep trying to update it on Windows 10 but it keeps telling me it's the most up to date driver(it definitely isn't). How did you go about doing it?
Click to expand...
Click to collapse
As OP said, manually select the proper driver.

Windows 10 best solution: rename the RNDIS5 .inf file
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver

Something is not logical in this tutorial :
The content of the inf file in the attachment is rndiscmp.inf; but this file is already in Win8.1 system (C:\Windows\Inf). Hash are similar
This could explain why windows refuses to install it again and says "the last drivers is already installed"
Renaming extension of wceisvista.inf doesn't work for me in Win 8.1
Maybe you could tell us the name of driver files when using RNDIS 6 Driver ...

This thread is also important for resolving playability issues with the game XCOM 2, so thank you very much for the fix to a problem completely unrelated to Android You guys are awesome!

Thanks, worked for my Galaxy S6.

You can use one of the below drivers from that list. One of them may work, try them all:
USB RNDIS Adapter
USB RNDIS6 Adapter
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device > this was the one that worked for me

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank You :good:

Thx! Worked!! Windows 10 64 bit.

Hi guys, i get some issues here where it looks like i have only NDIS 5 on my windows 10.
I tried manually select driver, but i can only see this one : Remote NDIS based Internet Sharing Device
i tried inkaine's method, usb8023x.sys is still there but rndismpx.sys is missing. So i think i'm still using this annoying NDIS 5.
I don't understand why it's so hard to update this driver.. :silly:

inkaine said:
The issue drove me nuts on Windows 10 as well. Selecting another driver as suggested did not work for me as well, since Windows kept jumping back to the RNDIS5 driver all the time.
But I found the solution: Just rename the .inf-file containing the RNDIS5 driver. That way Windows will automatically use the RNDIS6 driver.
Go to C:\Windows\INF folder
Find file wceisvista.inf
Take ownership of that file and grant yourself permissions
Rename the file extension to anything but .inf (for me I used .in_)
Enjoy the RNDIS6 driver
Click to expand...
Click to collapse
Thank you so much. This issue has been bothering me for years and your solution along with OP's solution helped me. Thanks

Hey ive been having this issue for a while now and im using a htc one m8 to tether with but for me it wont let me manually update the drivers or modify the wceisvista.inf im using windows 10 pro as well.

Windows 10 fix - Worked for me
Hello all,
None of the steps worked for me, however i followed one more set on steps that i found on the net (unable to post links yet )
anyways, the steps are
Open Device Manager (right click on Computer > Manage > on the left side, under System Tools choose Device Manager)
Choose the problematic device in Network Adapters (for me it's called HTC Remote NDIS based device)
Right click on it and choose Update Driver Software...
Click Browse my computer for driver software
Click Let me pick from a list of device drivers
Uncheck the box Show compatible hardware
For the manufacturer, choose Microsoft Corporation
Now you will have two options:
Remote NDIS based Internet Sharing Device
Remote NDIS Compatible Device
I chose the second one and it solved the problem, but if it doesn't work you could try the other one. In my case, the driver that was being used was neither of these, but a special driver from Android SDK ADT bundle.
Pick one and click Next.
If a dialog comes up, confirm by clicking Yes.
Wait a few seconds for the connection to restart. If it doesn't work, try disabling and reenabling USB tethering on the phone, or reconnect the USB cable.
PS: Microsoft Corporation or Microsoft Inc. or Microsoft might be present in manufacturer. search among the three