Related
Hi guys,
I just have received a i9023 from a friend to repair. I put fastboot on and the device is unlocked, then I copied over Matr1x kernel via USB to the SD card and flashed CMW to recovery.
From here things went bad.
When trying to update the kernel to Matr1x, it showed that the file wasn't on the SD card anymore, so I tried to mount the SD card to copy it back, but it my computer wouldn't see it. Since then I tried many things to get the USB working - updating drivers etc... after awhile I decided to format SD card, which didn't help, so I formatted all the partitions on the phone.
Now, every time the phone comes on, it boots straight to fastboot, but also the PC will still not recognise the phone via USB.
I've tried getting into Download mode and using ODIN to flash a new kernel & ROM, but this wont work without USB working.
Can anyone help?
PS. I have read many other guides and posts, but nothing has helped.
Many thanks.
*Bump*
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
bedalus said:
Are you running Ubuntu or similar? You need to be root to use fastboot and edit the right config files
wait, did you go to the mount menu in cwm? You can mount as usb storage in that menu... Are you saying it doesn't show up on your computer? Are you running windows?
Click to expand...
Click to collapse
Yes, I tried to mount as USB Storage in the Recovery Menu - didn't work, but now, I've only got fastboot - Booting up the phone normally jumps straight to fastboot, trying to boot into recovery doesn't work (just the fallen over Android pic with the red "!" on his chest).
I'm using Windows 7 and computer will not recognise the phone at all (it was working before this & the MicroUSB port is not damaged).
My GT-i9100 works perfectly via USB.
Piemo said:
I've a friend in the same situation.
We managed to make the phone recognizable using pda.net driver for nexus S, but weren't abel to find a single tar file to use on Odin.
Seems that all stocks rom were deleted from any storage.
Click to expand...
Click to collapse
If I can get it to connect to my PC so I can throw a stock ROM on there via ODIN I should be right (Pretty sure SAMFIRMWARE has some).
I've found often that the sdcard only gets mounted when you "choose zip from sdcard" in recovery. I panicked once with a galaxy s when I had forgot to put any rom on the sdcard and couldn't mount it subsequently. Ended up using heimdall with success. Also make sure you have latest version of fastboot, from platform tools 4.0.3.
Yeah, try Odin
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
twadda218 said:
If you can download sdk with the google drivers and install the drivers through device manager, you should be able to get your usb to connect again to fastboot. There is a bootloader driver inside the kit!
Click to expand...
Click to collapse
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Can you try Ubuntu? Any luck with Odin?
KLoNe1 said:
Yeah, it is definitely not connecting via fastboot. Windows 7 just comes up with UNKNOWN DEVICE., as does my WinPX machine. It's very strange.
Click to expand...
Click to collapse
Does it say unknown device in device manager?
Sent from my ice cream powered Nexus S
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
KLoNe1 said:
I don't have a machine with Ubuntu on it unfortunately.
Yes, Unknown Device in Device Manager - it won't accept it when I point the new driver to the modified Google USB .inf file
Click to expand...
Click to collapse
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
DarkhShadow said:
Did you click the "Have disk" option, point it at the file then click one of the options? That's what I had to do
Sent from my ice cream powered Nexus S
Click to expand...
Click to collapse
Yes, I did - it said that this inf (driver) doesn't contain information about the device in question.
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Many thanks for all your help everyone; unfortunately I still have yet to figure out how to get this working. Please keep throwing out your ideas
bedalus said:
I think I came across a USB driver problem once that was rectified by deleting the relevant keys from the registry. Could be worth looking into.
EDIT: Found it!
Open regedit and navigate to
HKEY_LOCAL_MACHINE > SYSTEM > CurrentControlSet > Enum > USBSTOR
and look for any devices that could be your nexus s.
I think they might be these:
Disk&Ven_Android&Prod_UMS_Composite&Rev_0001
Disk&Ven_Google&Prod_File-CD_Gadget&Rev_0000
You should be able to delete them (if not, change the permissions).
Then reboot and hopefully next time you plug in your phone, the drivers will reload.
Click to expand...
Click to collapse
I gave this a go as it sounded like a great idea, but unfortunately it still isn't working.
I ended up deleting the drivers it was installing which wouldn't work & now it will only show up as 2x Unknown device under 'Portable Devices' heading.
I think you should try installing ubuntu, and the android sdk so you have access to fastboot again.
I can not figure out what the hell I am doing wrong here.
I downloaded the naked driver pack on the guide page labeled 'Drivers TF700: Windows (Patched Universal Naked Driver)'. I unzipped the folder and plugged my TF700 into my computer. I then opened up the Device Manager and clicked on 'Asus Android Devices', then right clicked on 'Asus Android Composite ADB Interface' and pressed uninstall. I checked the 'delete the driver software for this device' and pressed OK.
The drivers uninstalled successfully and I turned off my WiFi card. I then unplugged and re-plugged my TF700 and navigated to 'Other Devices' in the Device Manager. I right clicked on 'Asus Android Composite ADB Interface' and clicked 'update driver software...' and then on 'browse my computer for driver software'.
I then navigated to the folder that I unzipped the driver pack to and tried to install them (clicking the 'include sub-folders' option). No go, I got the error message 'Windows was unable to find the driver software for your device' or something very similar. I then tried specifically pointing to both the i386 and amd64 sub-folders just to see if that wouldn't work somehow but I got the same error message.
What am I doing wrong? I am using a Lenovo G550 (I think) 32-bit laptop running Windows 7. My TF700 is rooted and unlocked but not much else has been done to it.
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
diablodow said:
Put the device in apx mode then try that process. It should show up as an APX device and that's what you apply the nvflash drivers to.
Click to expand...
Click to collapse
That step isn't till later
@OP - let it update the drivers form Windows. That should be fine. As long as you can see the device and it has no errors or warnings around it. you only need the specific drivers when you get to the APX mode, then it will find them.
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
MartyHulskemper said:
I had pretty much the same problem, but it turned out it went a lot smoother with reboot in between. Try that, and disable Windows' desperate searching for drivers on Windows Update -- I got some funky drivers and device designations from the WHQL drivers... Please report back in with any progress or lack thereof, and we'll try and get you back on track.
Click to expand...
Click to collapse
This.
I had big time problems as well with installing these correctly. You need to reboot after uninstalling all old drivers. 1) Hook up Infinity in Android Debug mode 2) uninstall/delete old drivers like you did 3) reboot PC 4) Plug in Infinity again in Android Debug mode 5) install drivers manually through hardware wizard (use have disk option)
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
SOTK said:
Repeat this process for fastboot mode. Note: you will get a warning that you are installing drivers that have not passed WHQL. Disregard. Install anyways.
Its a pain in the butt process but you have to reboot after uninstalling each old driver. You should probably reboot and remove Infinity USB connection after each successful install of new drivers. This is how I got everything to work. I also tried a different USB port.
Sent from my SCH-I535 using Tapatalk 2
Click to expand...
Click to collapse
Can you clarify this? What do you mean by 'repeat this for fastboot mode'?
Sent from my unlocked Transformer Infinity
Still no luck. I uninstalled 'ASUS ABD Interface', unplugged the TF700, restarted the computer, plugged the tablet back in, and tried to uninstall. Told me the same thing, that Windows could not find the driver software.
Any other ideas? I have no clue what to do now...
Sent from my unlocked Transformer Infinity
I_EAT_BABIES said:
If anyone can help me get these installed I would really appreciate it. I assume I can probably set up NvFlash with the standard Asus drivers but I would rather set it up exactly the way it is recommended to ensure success.
Massive thanks in advance!
Blake
Click to expand...
Click to collapse
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Eddie Hicks said:
I am having the same exact issue. And strangely I get the same results on both my laptop and desk top systems. I search the forums for solutions and found the same answers that were suggested here but nothing works for me. I just can't figure out what I am doing wrong since so many others seem to be able to install the drivers without problems. Did you ever resolve your driver issue? Are you certain that the standard ASUS drivers will work?
Click to expand...
Click to collapse
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Pretoriano80 said:
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
Click to expand...
Click to collapse
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Eddie Hicks said:
Thank you very, very much but I just figured that out and came back to this thread to tell it. I wasn't doing the "Have Disk" thing. I was just browsing to the driver's folder. I just successfully installed NVflash. I installed the ADB drivers at first but during the Nvflash installation process I had to go back and install the APX drivers. Thanks again. Now time for Jelly Bean.
Click to expand...
Click to collapse
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
buhohitr said:
Haha, nice! but still be very careful, 98% of the brick situation on tf700, NVflash didn't help at all.
Click to expand...
Click to collapse
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Pretoriano80 said:
Guys you need to install those drivers manually,it's not that hard.Here's how you should do it:
1) Put your device in Fastboot or APX mode (depend on the driver you want to install) and connect it to your PC
2) Open Device Manager and select the device
3) Right Click and select " Update Driver Software " and choose " Browse My Computer for driver software"
4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK "
5) BROWSE to the folder where naked drivers are located and select "android_winusb.inf " if you are trying to install the FastBoot driver or choose " android_apxusb.inf " if you are trying to install the APX drivers.
6) After the installation is done reboot your PC
If Windows give you a big red warning about the driver not beeing signed just ignore it and go ahead installing the driver.
Also you should disable UAC if it's enabled.
Click to expand...
Click to collapse
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Pretoriano80 said:
Is the other way around, NvFlash will help you in 98% of bricks situation, if you don't believe try to investigate more, you can even try to wipe your bootloader if you want to check that percentage.
Click to expand...
Click to collapse
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
buhohitr said:
I'm talking about nvflash for the tf700 only. 98% of ppl in the tf700 experienced this type of issue where nvflash is uselessmost I believe cause by install custom recovery), where your pc failed to see your device. Below is another sample.
http://forum.xda-developers.com/showthread.php?t=1778353
Click to expand...
Click to collapse
So I see you are trolling this thread too... 98%??? Really??? Can you give a source for that or is that a number you just made up?
NVFlash is useless if you have not already made the backups. But you are completely incorrect if you are suggesting that it is useless even if you have made the backups.
Best not to troll when you clearly do not understand what you are talking about
I_EAT_BABIES said:
I'm still not getting it I guess. I am assuming when doing it this way you do not uninstall the original drivers first or else the computer would not recognize the device correctly, please correct me if I am wrong.
I keep seeing this supposed "have disk" option talked about but I don't see it anywhere. Could someone please screenshot it for me?
Thanks for all the help guys, I (hope) I am close to getting it.
Sent from my unlocked Transformer Infinity
Click to expand...
Click to collapse
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Damn,i can't believe this....When you get to this step " 4) Now click on " Let me pick from a list of device driver " and select " HAVE DISK ... " look on the right bottom of that menu,do you see a "Have Disk" button?.
I_EAT_BABIES said:
Anyone?
Sent from my DROID SPYDER using Tapatalk 2
Click to expand...
Click to collapse
Here is a screen capture from my system. Look in the lower right for the HAVE DISK button. Following the directions giving earlier should get you to this point. Just click HAVE DISK and guide to where you have the drivers on your system. You may not see the list of drivers as on the screen capture the first time you do it. Since I have already installed the drivers the system remembered where to look so the drivers are visible. Also make sure to connect your tablet to your computer in order for the device to be visible in device manager. The device in device manager should say android ABD Interface or something of that sort. It took me awhile to get it too
****edit***
Apparently the link opens another page.Once on that page click the little box for the image.
https://www.dropbox.com/s/ykuv2ac6zxdln7i/driver_update.JPG
As of the time of this reply I have got the Fasboot drivers installed, but I still saw now "have disk" option. After turning UAC off (don't know how that got back on) I was still just selecting a folder as shown in my previous screenshot.
About to try APX, will post results.
Got it! Thank you guys so much, I really appreciate it. This was seriously driving me crazy, but I still don't understand how we are looking at different menus.
When I plug my phone in I have no way to transfer files to and from the Nexus 5. Nothing comes up. Tried updating the drivers, but nothing works. Please help.
I haven't been able to do this either, anyone wanna help?
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Sent from my Nexus 5 using xda app-developers app
n7of9 said:
connect phone to pc via usb
go to Device Manager
right click anything that looks like the phone and uninstall drivers
unplug phone
restart pc
connect phone to pc via usb
let it install drivers automatically
fixed?
Click to expand...
Click to collapse
Nope, still nothing. My Razr HD comes up fine, but not the Nexus 5. Think it's a conflict in drivers?
Tweaken said:
Think it's a conflict in drivers?
Click to expand...
Click to collapse
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Tweaken said:
Sweet, that did it. Uninstalled Motorola drivers, uninstalled Google ADB driver, restarted, plugged in phone, voila!
Click to expand...
Click to collapse
n7of9 said:
definitely...the only time i ever had Nexus driver issues was when i changed from HTC to Nexus
the best i can offer is how i fixed it...get a copy of Wug's Nexus Root Toolkit and follow his instructions from deleting all other drivers and installing new ones...he offers (i think) 4 different options and you just work your way through them until one stick (the RAW drivers always work for me)
and note that the Toolkit doesn't work on 4.4 yet, so only use it to clear and update drivers
http://forum.xda-developers.com/showthread.php?t=1766475
Click to expand...
Click to collapse
Thank you n7of9 the link you provided worked for me.
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
This worked and also fixed another popular issue
Not only does this fix the MTP connection issue to move folders to root folder. But it also now allows me to see the preview thumbnails of my media! This was a huge problem on my other phones and many many people including me were never able to fix that. All the ideas to get around or create USB Mass Storage instead of MTP after 4.1 were fails.
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Cosmicevo said:
Another solution...
Plug the phone into your computer. Go to "Device Manager" and find the Nexus <x> device where-ever it's listed (may not be called "Nexus...", though on my machine with the real drivers it was).
Right click, choose "update driver software"
Select "browse my computer"
Select "let me pick..."
Choose the option. "usb composite device"
Apply and close all windows.
Disconnect and reconnect the phone to the computer.
The phone will now allow you to move files to it properly. Something weird with proper phone drivers. I believe you need to reverse this if you need to use ADB again in the future.
Click to expand...
Click to collapse
Worked perfect, thanks
what worked for me
In windows 8.1
I plugged in my nexus and browsed to device manager in control panel
I uninstalled the device (and deleted the driver)
I unplugged the nexus 5
I plugged it back in
Windows recognized it as a proper MTP device
I think the problem was something to do with windows recognizing it as an ADB device (I had installed the toolkit before etc)
This fixed it for me
openlatedotorg said:
Worked perfect, thanks
Click to expand...
Click to collapse
Hi,
I did all the steps mentioned, and ran the driver test - everything works fine, success.
However, I still cant see my device in "This PC"...
What is even more weird, that it only disappeared couple of days ago, and I didnt do anything to my computer at all....
Any other way to get devices to show? (Nexus 10 or Nexus 4 stopped showing too).....
Maybe problem is that it is being shows as ACER ADB Interface? But i cant change that to MTP anyway..
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.