Related
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
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
pmazz850 said:
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
Click to expand...
Click to collapse
If you are in fastboot it will not show up under adb... you need to install htc sync for the drivers then uninstall htc sync the program. Make sure you are using adb version 1.031 and that usb debugging is on.
pmazz850 said:
First off,
i am rooted with weaksauce, power saver enabled, supersu installed, usb debugging checked. PC is windows 7 x64. I wanted to do the firewater s off but adb is not listing my device. I have previously had adb connecting to my device( while trying htcDev Unlock before weaksauce root). Under device manager with phone booted to os, I get no android device listed. If i boot the phone to fastboot, it will list an android device in device manager, but still not listed on adb devices. Leads me to think its a driver issue. Removed and reinstalled all htc drivers but still no love. I do not have htc sync installed. I am kinda at a loss right now as to what to do. I also tried uninstalling weaksauce root and supersu but it was the same with or without. anyone have any ideas?
from what i read its a driver thing but this didn't seem to fix it for me.
Click to expand...
Click to collapse
what driver did you use?
http://forum.xda-developers.com/showthread.php?t=2217396
123421342 said:
If you are in fastboot it will not show up under adb... you need to install htc sync for the drivers then uninstall htc sync the program. Make sure you are using adb version 1.031 and that usb debugging is on.
Click to expand...
Click to collapse
where do i find my adb version?
i just went in and updated android sdk to latest version.
i tried installing htc sync manager and uninstalling earlier. i assume sync manager is the same as htc sync??
Thanks.
pmazz850 said:
where do i find my adb version?
i just went in and updated android sdk to latest version.
i tried installing htc sync manager and uninstalling earlier. i assume sync manager is the same as htc sync??
Thanks.
Click to expand...
Click to collapse
Adb version in cmd prompt
Htc sync should have the drivers you can try Google to find a stand alone installer. Also switch usb ports.
Sent from my HTC6525LVW using Tapatalk
Karl said:
what driver did you use?
http://forum.xda-developers.com/showthread.php?t=2217396
Click to expand...
Click to collapse
thats the thread i got the driver from. bot i got the 4.1.... version. gonna try 4.2..
what about htc bmp drivers? are they supposed to be installed? I just seen that in my program list.
pmazz850 said:
thats the thread i got the driver from. bot i got the 4.1.... version. gonna try 4.2..
what about htc bmp drivers? are they supposed to be installed? I just seen that in my program list.
Click to expand...
Click to collapse
Having same issue with 4.2.. drivers...
pmazz850 said:
Having same issue with 4.2.. drivers...
Click to expand...
Click to collapse
so its still not showng in windows deviice manager?
and it still doesnt show in adb when you type ( adb devices)
you tried this right
Go to 'Device Manager', right click "Other Devices->HTC" and select 'Update Driver Software - HTC'
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Select 'Android USB Devices' & select 'Next'
Select 'Have Disk' and select the folder you unpacked the HTC Driver
Karl said:
so its still not showng in windows deviice manager?
and it still doesnt show in adb when you type ( adb devices)
you tried this right
Go to 'Device Manager', right click "Other Devices->HTC" and select 'Update Driver Software - HTC'
Select 'Browse my computer for driver software'
Select 'Let me pick from a list of device drivers on my computer'
Select 'Android USB Devices' & select 'Next'
Select 'Have Disk' and select the folder you unpacked the HTC Driver
Click to expand...
Click to collapse
My htc shows under portable devices. Under other devices it only says Broadcom USH. Also when i plug my phone into usb it says htc installed correctly, ready to use. but also "unknown device not installed "
I have never in all my years of rooting and roming had this issue and it's a pain in my ass!!
pmazz850 said:
My htc shows under portable devices. Under other devices it only says Broadcom USH. Also when i plug my phone into usb it says htc installed correctly, ready to use. but also "unknown device not installed "
Click to expand...
Click to collapse
go to unknown and add driver manually
Karl said:
go to unknown and add driver manually
Click to expand...
Click to collapse
Having trouble trying to update driver. When asked to direct to the driver, i cant find it. Its looking for an .inf file but the driver is in an exe file. Dont know where it supposidly installed to.
i used this to pull mine http://sourceforge.net/projects/drvback/
you can use the inf's or try to use the restore its your call
windows 7 64bit
If you're trying to S-OFF, the instructions state HTC Sync Manager isn't supposed to be installed. So if it still is, uninstall that (you can uninstall it separately from the HTC drivers). Also, make sure USB Debugging is enabled. Plus, when you connect the first time after enabling USB debugging make sure you hit the checkbox that says something like "always allow". I didn't, and it didn't prompt me on subsequent connections. I had to disable USB debugging and re-enable it to allow adb commands to communicate again.
good point i dont think that was tried go to debug and revoke authorizations
sfreemanoh said:
If you're trying to S-OFF, the instructions state HTC Sync Manager isn't supposed to be installed. So if it still is, uninstall that (you can uninstall it separately from the HTC drivers). Also, make sure USB Debugging is enabled. Plus, when you connect the first time after enabling USB debugging make sure you hit the checkbox that says something like "always allow". I didn't, and it didn't prompt me on subsequent connections. I had to disable USB debugging and re-enable it to allow adb commands to communicate again.
Click to expand...
Click to collapse
the only reason i installed htc sync was to get the drivers and after install i removed it. and debugging is checked. if i uncheck usb debugging and re-check, i don't get an option for a checkbox. just asks me to ok or cancel usb debugging.
Tried revoking authorizations....same deal....no device listed.
pmazz850 said:
the only reason i installed htc sync was to get the drivers and after install i removed it. and debugging is checked. if i uncheck usb debugging and re-check, i don't get an option for a checkbox. just asks me to ok or cancel usb debugging.
Tried revoking authorizations....same deal....no device listed.
Click to expand...
Click to collapse
did you try them drivers
Karl said:
did you try them drivers
Click to expand...
Click to collapse
Ya i click on htc in device manager, click update driver, and direct to the file and it says driver updated, but i'm not convinced its actually updating. still trying something now....gettin pissed now....picked up some malware along the way today that ****ed me up for a little while! I appreciate your help and will post back in a little while.
pmazz850 said:
Ya i click on htc in device manager, click update driver, and direct to the file and it says driver updated, but i'm not convinced its actually updating. still trying something now....gettin pissed now....picked up some malware along the way today that ****ed me up for a little while! I appreciate your help and will post back in a little while.
Click to expand...
Click to collapse
i meant the ones from my puter
Karl said:
i meant the ones from my puter
Click to expand...
Click to collapse
ya, thats what i used to update them.
Let me ask you something, when i click on my htc in device manager list, do i choose mot device or usb composite device? And which driver should i use to update it?
pmazz850 said:
ya, thats what i used to update them.
Let me ask you something, when i click on my htc in device manager list, do i choose mot device or usb composite device? And which driver should i use to update it?
Click to expand...
Click to collapse
usb, did you try to use all 3? or use the ones you dont see on your end
Hi, I've been trying to connect my rooted Nexus 5 to my laptop for a few hours now with no luck. It works for my desktop but it doesn't for my work laptop. Both machines recognize it as Google ADB interface in device manager but I can't see the folder on my laptop. I tried with and without USB debugging, MTP/PTP and I also installed SDK tools but none of them worked. When I try to uninstall the drivers, so I can reinstall them, it does the uninstall, I plug in the usb again and the device is there like the drivers were never uninstalled. I've attached a screenshot with the driver and the date. Any thoughts on what's causing the issue?
geolykos said:
Hi, I've been trying to connect my rooted Nexus 5 to my laptop for a few hours now with no luck. It works for my desktop but it doesn't for my work laptop. Both machines recognize it as Google ADB interface in device manager but I can't see the folder on my laptop. I tried with and without USB debugging, MTP/PTP and I also installed SDK tools but none of them worked. When I try to uninstall the drivers, so I can reinstall them, it does the uninstall, I plug in the usb again and the device is there like the drivers were never uninstalled. I've attached a screenshot with the driver and the date. Any thoughts on what's causing the issue?
Click to expand...
Click to collapse
Uninstall all drivers for android devices (and make sure you choose the option to remove the files), reboot then plug it in, what does it do? Try the universal drivers?
Also try turning off USB debugging if you have it on.
If you look through the first link in my signature there's a thread on troubleshooting driver issues
Lethargy said:
Uninstall all drivers for android devices (and make sure you choose the option to remove the files), reboot then plug it in, what does it do? Try the universal drivers?
Also try turning off USB debugging if you have it on.
If you look through the first link in my signature there's a thread on troubleshooting driver issues
Click to expand...
Click to collapse
I've checked that guide already as it is first to pop on google search. I uninstalled and removed software as you said and it installed Android ABD Interface drivers now. Which I imagine are the same but not device specific. Still not response from my phone though. I can see it under Devices and Printers as well but no folder pops. It works on Windows 7 at home and I tried it on a machine with Windows XP as well and it works fine.
geolykos said:
I've checked that guide already as it is first to pop on google search. I uninstalled and removed software as you said and it installed Android ABD Interface drivers now. Which I imagine are the same but not device specific. Still not response from my phone though. I can see it under Devices and Printers as well but no folder pops. It works on Windows 7 at home and I tried it on a machine with Windows XP as well and it works fine.
Click to expand...
Click to collapse
Not sure then. Try this: http://forum.xda-developers.com/showpost.php?p=47165389&postcount=3
If not then try asking in the driver thread.
Enable USB debugging mode if its not on. I usually turn on and off and then connect it to your PC.
badboy47 said:
Enable USB debugging mode if its not on. I usually turn on and off and then connect it to your PC.
Click to expand...
Click to collapse
OP wants to connect in MTP, not for adb I think lol. No need to turn it on, and on some devices I've had in the past it won't show up if you have it on :/
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!
I have a Nexus 5 that I have had about a month now and I had the USB on it working before about a week ago. I plugged it in today and neither my desktop or laptop could recognize it anymore. Both computers are running Windows 8.1.1 and the issues seems to be new as I can neither get USB storage or ADB to find it. The closest I can get it to working is to switch the USB mode to PTP and it reads that but I don't want to pull photos off. When I have it in MTP, it makes the sound of it plugging in and my phone shows it is plugged into a computer but Explorer shows nothing and it says it is working normally in device manager. I've tried everything from enabling and disabling debugging, restarted both my phone and computer tried reinstalling the drivers (both by the computer automatically finding them and manually installing them) but nothing seems to work. Is it possible that Windows Update could of broke the drivers since my computer installed updates yesterday? I also have Linux on my laptop and it appears to read fine with Linux.
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
OK thanks. I'll give it a try because it was showing up as ACER ADB Device under device manager
EDIT: I updated the drivers and used the USB composit drivers instead and it got MTP working again. When I set it to USB composit, it installed Google's ADB drivers and the Nexus 5's USB drivers so everything is working again. Thanks for your help
EddyOS said:
That's the exact issue. If you check in Device Manager you'll see it listed as 'ACER ADB Device' (or something like that). You have right-click on it, select update driver, manually check and go through the list option and choose the MTP driver and it'll work again (and with USB Debugging enabled if you don't usually have it on like me)
I theorise that it's happened cause the Acer driver is digitally signed and the Google ones aren't but I could be wrong. Either way, it's a PITA
Click to expand...
Click to collapse
I can´t manually update driver because of this:
when i update the acer adb it says the driver is up to date and everything is all same. what to do?
Thanks! Thought I was going to go crazy. Worked for me...
i set the driver to MTP as mentioned above and the phone started to show up on the explorer but now i couldnt copy any files from my laptop to the
phone. It displays like that and if clicked yes then the copy wouldnt happen.what is the problem.
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
wangdaning said:
Uninstall driver, plug in device, tell windows to not auto install driver (or disconnect from internet), click to update or install driver, point to folder with drivers, install, all is done.
Click to expand...
Click to collapse
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Big tree said:
actually i did all the process above(when the phone was not appearing) and then i got to display the thing on the explorer. and shall i do it still what you say.
Click to expand...
Click to collapse
That msg comes when you're in PTP mode I think...Only certain formats are supported.
Check under storage, expansion menu and make sure you are set to the first option...not PTP.
Above guy mentioned to have phone in USB debugging mode when setting up drivers.
If the device is showing then you need to point to the drivers for it (download them from google). I reinstalled windows a few days ago and had the acer issue (device first shows up in device manager as nexus 5 then switches to acer), windows wants it to be an acer device. Stop windows and then install the correct drivers,
For me I had to click the auto install in windows tray and tell it to stop. After a few times it worked.
No I'm connecting in MTP mode. Ahh its gettn irritating.