Related
Hello,
My computer is running windows 7 32bit and these days i am continually trying to install Nexus S drivers. I have tried PDAnet, SDK manager, Samsung drivers and others but i still can not connect my nexus s with my computer. In others posts, i realised that i must see my nexus s in device manager but i can not see it too. Please help me! Thank you!
christoscy said:
Hello,
My computer is running windows 7 32bit and these days i am continually trying to install Nexus S drivers. I have tried PDAnet, SDK manager, Samsung drivers and others but i still can not connect my nexus s with my computer. In others posts, i realised that i must see my nexus s in device manager but i can not see it too. Please help me! Thank you!
Click to expand...
Click to collapse
hello
eventullay you have a hardware problem cable or usb hub.... because even your drivers are not installed correctly the
device manager on your pc make instead of the phone named: android device 1.0 a yellow sign with eclamation mark if you don't have this, there is an hardware or a bigger ROM error.
S.R.
.
christoscy said:
Hello,
My computer is running windows 7 32bit and these days i am continually trying to install Nexus S drivers. I have tried PDAnet, SDK manager, Samsung drivers and others but i still can not connect my nexus s with my computer. In others posts, i realised that i must see my nexus s in device manager but i can not see it too. Please help me! Thank you!
Click to expand...
Click to collapse
i had this problem too. but this worked for me, i hope it works for you too.
Open My Computer
Right Click on it and select Properties
Select Device Manager
Right click Android. Click Update Driver Software
Manually locate the drivers and update.
I hope that works
if you can't find "android" maybe it's under USB, or something like that. it should be there.
shivasrage said:
hello
eventullay you have a hardware problem cable or usb hub.... because even your drivers are not installed correctly the
device manager on your pc make instead of the phone named: android device 1.0 a yellow sign with eclamation mark if you don't have this, there is an hardware or a bigger ROM error.
S.R.
Click to expand...
Click to collapse
nainna said:
i had this problem too. but this worked for me, i hope it works for you too.
Open My Computer
Right Click on it and select Properties
Select Device Manager
Right click Android. Click Update Driver Software
Manually locate the drivers and update.
I hope that works
if you can't find "android" maybe it's under USB, or something like that. it should be there.
Click to expand...
Click to collapse
I will check another usb cable and i hope it will be working!
PdaNetA350x32
bajong said:
PdaNetA350x32
Click to expand...
Click to collapse
Have you got a download link?
I have scoured the internet and xda and have not found a solution. I am trying to unlock my bootloader, so I can install ROMs and whatnot, on my HTC One S. However, the device is not recognized by adb, even though the normal drivers are installed through HTC sync. I cannot install any additional driver through any other way.
Basically, I just need to know if anyone has a solution to getting the HTC One S to recognize with adb on Windows 8, or any alternate way to get a token.
I have done this many times before on windows 7, and even used adb for other devices on Windows 8, but cannot get the One S to read.
..and unfortunately my Windows 7 machine is in need of repair.
Any suggestions would be appreciated.
Adb still worked after I went from 7 to 8. Uninstall drivers and install android sdk which has required drivers. I've never used HTC sync due to its suckness. You can also google the download for just the drivers without any extra software. There are multiple devices that have adb drivers for download here on xda aswell.
Good hunting
But as far as driver compatibility nothing has changed since the update
Sent from my HTC VLE_U using xda app-developers app
the drivers wont work until htc/Microsoft updates them. doesn't work on my windows 8 pro, I had to installed a virtual machine to get it to work with windows 7.
Definitely nofun that the htc drivers seem to be the big issues. Whendid not have trouble with the kindle orsamsung. Did update as much through the sdk, and tried manually installing the win 7 drivers, and more andno luck. So guess Ill be waiting.
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Spastic909 said:
Works for me on windows 8 pro....don't know what you are talking about
Sent from my HTC VLE_U using xda app-developers app
Click to expand...
Click to collapse
Thats good to hear that there is a way to get it working. What drivers did you install?
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
mbh87 said:
Are you looking for a driver that will work for when you are in bootloader? I used a Samsung driver and it worked fine.
Click to expand...
Click to collapse
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
mikeyinid said:
I just installed the latest htc sync and all the drivers were good
Sent from my HTC VLE_U using xda premium
Click to expand...
Click to collapse
Did this allow detect in adb? not just for windows recognizing the device?
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
Already tried Used both windows 7 and windows vista drivers.
Oh well.
I installed the SDK and some hacked HBOOT drivers. Doesn't work. I'll have to try new methods
phoenixbennu said:
Ive come to find that adb will recognize the device, but not in fastboot mode. Which is the killer, cause thats the only mode I really need it to be recognized in.
Click to expand...
Click to collapse
I've found in some pages that HTC has already uploaded their HTC Sync and that is now compatible with Windows 8. However, still not working for me in 8 Pro.
---------- Post added at 02:02 AM ---------- Previous post was at 01:55 AM ----------
Ruwin said:
I use both ADB and Fastboot on my W8, and never had a problem. Worst case scenario, if you install the drivers but you still have an exclamation mark next to the device in device manager, try and install the Android USB drivers on a W7 machine and copy the files on your W8. Then go to device manager and update the driver, and point to the folder you just copied. This should do.
Click to expand...
Click to collapse
I've uploaded from W7 to W8 pro and my now I'm not able to find a driver that fits my computer. It's a very strange situation.
I have tried pretty much everything lol, its not worth it if you are installing a RUU then windows 8 suddenly stopped detecting your phone then you have a brick. I would just wait till htc releases drivers for windows 8. or installed windows 7 through VMware, like I did.
Just have the device for 1 day and had some issues. Is there any working solution for this? I've spend some time searching and reading, I tried alot of drivers (HTC, from android-sdk and so on)...with all the same issue. Windows 8 recognizes the device as My HTC BUT...adb doesn't. When issuing "adb devices" command, returned list is blank.
Finally I've installed recovery and unlocked on a Windows 7 machine but I don't want to do that each time I flash a ROM (and I flash alot).
Also short question... I didn't saw anywhere clearly stated but from what I've read, I understood there's no S-Off for One S right? I'm comming from Desire S and everything there was flawless.
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
dexi00 said:
It is working on my Windows 8 Pro without an issue. I installed the driver which comes together with the android sdk.
1. Open device manager
2. Select the android device with yellow sign
3. right click and select "Update Driver Software ..."
4. select browse my computer for driver software
5. select "Let me pick from a list of device drivers on my computer"
6. select have disc and browse for the "android_winusb.inf" in the android sdk folder
7. select Android ADB Interface and press next
8. select yes, ...
-> adb driver is installed and device should now work with adb.
Best regards,
dexi
Click to expand...
Click to collapse
wbut i can't find android-winusb.inf in my sdk,
can you mention the folder's path?
I'm having same issue but on Win7 also tried many installs and uninstall of HTC drivers, still not recognized plus have my own thread which 2 members tried all they know also tried on my Dad's Vista with a no go? I found my computer recognized my device if u do this, power down ur device than restart ur computer while booting up plug in ur device and sometimes it recognizes it but not always staying connected
Sent from my HTC One S using xda premium
I have Windows 8 Pro Media Center, install drive from htc sync manager from htc site, flashing fastboot, oem lock, etc seem to work in cmd. But odd was if i do adb devices, it just say something like "list device" i don't see my device number.. or i should use fastboot devices instead
Try this:
[Solution]Windows 8 - ADB/fastboot driver problem solved!!
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
UPDATE :
Use flashtool drivers to install adb/fastboot/flashboot drivers. This is the most simplest and easiest method I have come across lately.
Simply download flashtool
http://www.flashtool.net/index.php
Go to folder where you have downloaded it. Usually C:/flashtool/drivers.
Select the drivers for your particular device. I use universal for all three types of drivers. It is helpful to boot into fastboot/Flashtool before installing the drivers but not necessarily.
Good Luck
Reserved
This is great Hnk1 thanks a bunch
joel113- said:
This is great Hnk1 thanks a bunch
Click to expand...
Click to collapse
I am glad I could be of help
Good work
Hnk1 said:
Hi there
I have seen some posts where users are having difficulty connecting Xperia L to their PC or ADB. Therefore, I am writing this guide to help you all.
The guide was prepared using Windows 7 Ultimate but should work with Windows XP and Windows 8.
Firstly, Sony uses a different driver for their Xperia devices and therefore, sometimes you are unable to install drivers for your devices especially for ADB commands.
IF YOU ARE LUCKY
There are few ways to get around to install drivers for your device. The most convenient and easy is you plug in your device and wait for automatic detection of your device. Make sure you have USB connected as MTP in MY XPERIA in SETTINGS of your phone. The device drivers would be automatically installed by Windows update.
METHOD
If suppose you can not install your drivers, connect your xperia and then on your PC, go to My computer > Properties>Device Manager.
You should see an undetected hardware with a yellow exclamation mark over it. Open it and click on update my drivers. Then choose GOOGLE DRIVERS by choosing hard-drive. This should install the drivers for you. If this doesnot work. Try the attachment with the post where the drivers are modified to work with Sony Xperia Devices.
Follow the same steps but this time choose the attachment folder to search for drivers. It might say, the drivers are not verified. Just Ignore it and carry on installing them. You will need to unzip these files.
IF suppose you do not see any exclamation mark while you connect your xperia. Just go to control panel and add new hardware. Select, I will choose my device and then install from hard-disk. Select the folder where you have unzipped the files and you are good to go. The name of new hardware is not important as windows will read the drivers files and install drivers for Xperia.
This will install all drivers for your device. If there are two or more drivers while installing them. Redo the steps and install all of them individually.
Suppose your ADB still doesnot work, then
FOR ADB DRIVERS :
Download the ADB Universal Drivers and connect your device. Then hit install. The ADB drivers will be automatically detected and installed.
Further, if these tricks fail, you can delete the unknown driver from your control panel and then try finding it again by using refresh button(scan for new hardware changes) in device manager.
Another trick is to click on unknown drivers and delete them. Connect your phone and restart your phone. Then scan for new hardware in device manager. The drivers should be installed for your device.
If still there are some problems, I will try to help you out.
DOWNLOAD LINKS
DOWNLOAD GOOGLE DRIVERS FOR MTP/ PC ETC
https://dl-ssl.google.com//android/repository/latest_usb_driver_windows.zip
DOWNLOAD UNIVERSAL ADB DRIVERS HERE :
http://adbdriver.com/upload/AdbDriverInstaller.exe
UPLOADED FILE : Sony Xperia Drivers for ADB.
Click to expand...
Click to collapse
:good: Good work
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
ReSkid said:
Installing these drivers didn't work, But after a factory reset and installing the Sony companion, the drivers installed and now gets detected in the ADB.
Thanks
Click to expand...
Click to collapse
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
you can use ADB Wireless
https://play.google.com/store/apps/details?id=com.sherdle.adbwireless&hl=en
Hnk1 said:
Did you try the attached drivers ?
I am just wondering you might hadnot turned USB debugging or disabled MTP mode or something you might have done to your kernel/ROM that might have changed the environment of your phone which factory reset reverted back. These drivers are NOT the drivers for connecting your device to your PC. These are used when you are unlocking your bootloader or working with ADB/fastboot commands.
Thanks for your contribution about how it worked for you and it might help others who might have a problem!
Click to expand...
Click to collapse
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
ReSkid said:
I had tried every possible driver haha! Also had everything like USB Debugging etc turned ON, I guess it might have been some app I had installed. Anyways now I have rooted it successfully.
Thanks a lot for your help.
Click to expand...
Click to collapse
I am here for anything that I can help you with. It's great that your problem is fixed now !
AATrooperz said:
I am still having this problem for days now. still no connection to pc/flashtool whenever i try to reboot into flashmode/flashboot. i've been google'ing around. and i've tried this method but it's seems doesnt work. i've already got tons of these unknown devices, and the driver doesnt work(or maybe im too noobish to install them).please help
Click to expand...
Click to collapse
For a second when I looked at your images, I was just baffled. THOSE MANY UNKNOWN DEVICES! That can't be right you know.
There must be only ONE unknown device that ought to be installed as mentioned above in my post.
Do you see these devices when you connect your phone to your PC or those unknown devices are already there?
Have you tried windows update to fix it?
Tell me more about why you see so many devices.
If suppose, they are already there, just see which device comes up when you connect your phone and try installing drivers for that particular device.
Also, i suggest just go for add a new device and then select hard disk and then install drivers which are attached. I hope that fixes your problem.
REMEMBER your device must be connected when you are trying to install the drivers
right.i'm gonna give it a try,wish me luck. thanks!
I still need your help!!
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Hnk1 said:
I am glad I could be of help
Click to expand...
Click to collapse
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
FPThatea said:
I could not install or might be dont know how to install the attached xperia drivers which are in .dll files. Can u explain in detail how can I install it. I've lost root access after upgrade to 4.2.2 . I do really need your help to get back root access and install a valid driver for my device. From C2104
Click to expand...
Click to collapse
Hi
well first thing you need to understand is there are three drivers you need to install to make everything work including fastboot , flashboot, and Xperia L storage and SD card.
To install each type of drivers, you must have the phone in that particular state. To install normal drivers (for mass storage and PC companion), if suppose not detected automatically, you need to turn on your phone and then unlock it. Then see if drivers are found or not!
If the windows give you the error like undetectable device attached, go to my computers and then properties and the device manager and look for any device with an exclamation mark (yellow).
click on it and then select update drivers and use drivers that have been attached in the first post. (Remember to extract the attachment in a folder)
Then click on select drivers from hard drive (click manual installation of drivers )
and locate the folder where you have extracted drivers. This will install drivers!
if you want drivers for flashmode/fastboot, turn off phone and boot into flashmode and then install drivers as I mentioned above.
I'm quite certain they wouldn't trouble you at all. If you still need help, do not hesitate to ask !
Good luck
P.S: You will need to enable developers option and select USB debugging to root your device. I hope you are doing that right !
Joel16 said:
Dude someone needs your help ^
I just quoted your post so you'd get notified about it.
Click to expand...
Click to collapse
Thank you so much ! I only check my notifications so I really appreciate it
uremytoy said:
@up ur post is a simple spam, if u dont know how to help just dont write anything. n one needs notifications for replying
just go to device manager, connect phone and find ur not recognized device; then right click on it and press update/install drivers. From the window that will appear choose socond option (it should be something like manualy find drivers or something like that), then navigate to that downloaded folder. This way it should install them
But XL doesnt need any external drivers. If u install fasboot an flashmode drivers from flashtool folder they should work; they are working for me and for anyone i know. U may also install SEUS and then connect phone. This way u dont need that drivers, but ofc what i have mentioned earlier should work.
Click to expand...
Click to collapse
Actually why don't you have a look at what the OP said,
"Thankyou so much, I only check my notifications so I really appreciate it"
I know what I'm doing here, if you don't have anything nice to say about it then DON'T say anything
Thanks..but still need you
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
FPThatea said:
Hi..Thank you so much for getting me back very soon.. I've successfully installed the driver with your your help. But, When I tried to root by using metachopper 1.3 my device did not reboot and start. Now, it just dead and really sad for this. I don't know what shall I do to get my phone back. Yes, I have 4.2.2 update in .ftf file with a flashtool. But, it does not work for me now.. Do you any experience to help me to solve my unwanted problem..Please..
Click to expand...
Click to collapse
you must boot your phone in fast boot mode. turn off your phone and hold down volume down when you connect it to the PC!
Use flashtool to flash ftf file. you'll need to place ftf file in C:/flashtool/firmwares
then select the right file for xperia L and just flash ftf.
in flash tool , select flash n then fastboot and then I'll ask you to put your phone in fast boot (use method mentioned above)
good luck !
I have tried all your methods
but I keep getting this error message "An error occurred during the installation of the device"
I am using windows xp sp3
please help
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 was giving a surface pro x.it will not install any of the phone drivers.if I open device manager when in bootloader mode it shows Android with a yellow triangle.i try to update the driver but I always get it can't find a driver or no driver is installed for your device.ive searched for 2 days and cannot find a solution.any help would be greatly appreciated.
gillim74 said:
I was giving a surface pro x.it will not install any of the phone drivers.if I open device manager when in bootloader mode it shows Android with a yellow triangle.i try to update the driver but I always get it can't find a driver or no driver is installed for your device.ive searched for 2 days and cannot find a solution.any help would be greatly appreciated.
Click to expand...
Click to collapse
Please search for the appropriate drivers for your phone and manually install them. Then try connecting your phone.
TNSMANI said:
Please search for the appropriate drivers for your phone and manually install them. Then try connecting your phone.
Click to expand...
Click to collapse
I tried they won't manually install either
gillim74 said:
I tried they won't manually install either
Click to expand...
Click to collapse
Download the correct drivers and after connecting the phone to the PC/Laptop, go to Device Manager and right-click the entry with the yellow triangle, then Update Driver, Browse My Computer For Drivers, then Let Me Pick From A List of Available Drivers On My Computer and then choose the drivers you downloaded and install.
If still facing issues, driver signing may be an issue, so search the internet on how to install drivers after turning off driver signing on the PC/Laptop.
TNSMANI said:
Download the correct drivers and after connecting the phone to the PC/Laptop, go to Device Manager and right-click the entry with the yellow triangle, then Browse My Computer For Drivers, then Let Me Pick From A List of Available Drivers On My Computer and then choose the drivers you downloaded and install.
If still facing issues, driver signing may be an issue, so search the internet on how to install drivers after turning off driver signing on the PC/Laptop.
Click to expand...
Click to collapse
Ive done that.i think its because microsoft uses there own processor in it.the microsoft sq1 instead of intel or amd.every time i try to manually install it says theres no drivers installed and doesnt even show adb interface.
gillim74 said:
Ive done that.i think its because microsoft uses there own processor in it.the microsoft sq1 instead of intel or amd.every time i try to manually install it says theres no drivers installed and doesnt even show adb interface.
Click to expand...
Click to collapse
If it is a processor issue, I have no ideas.
TNSMANI said:
If it is a processor issue, I have no ideas.
Click to expand...
Click to collapse
Not sure if thats it but only thing i can think of.
Well after a few day i finally got platform tools to recognize adb device.now i gotta figure out fastboot