If you have windows, you will need these drivers to use ADB or Fastboot with your Nexus 4. The long method of getting this is downloading the SDK and running it. I have extracted the drivers and put it into a rar file for easy use.
Follow these steps if you haven't plugged your phone into your computer before.
1. Download the file.
2. Extra the files into a folder.
3. Plug your phone in.
4. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
5. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
If you already installed other drivers and they don't work for you. Download the drivers below and follow these steps:
1. Enable USB Debugging on your phone.
2. Plug your phone into your computer.
3. Go to Device Manager on your computer and locate your device. It will either be under "Android Devices" or "Other Devices" depending whether drivers have been installed or not.
4. Right click on your phone and select "Uninstall."
5. In the box that appears, check the option to "Delete the driver software for this device" then proceed.
6. When that is done, go back to Device Manager and refresh.
7. Locate your phone and right click to select "Update Driver Software."
8. When prompted, select "Let me pick from a list of device drivers on my computer", NOT "browse for driver software on your computer".
9. Then you have to select "have disk" and then point to where you extracted the drivers (the usb_driver folder) to install the drivers.
10. Unplug your phone and restart your computer.
11. Plug it back in and everything should work.
Download link:
http://www.mediafire.com/?8xb50uktar8096i
Thanks to efrant for clarifying exactly how to manually select your drivers.
I would suggest everyone download Android SDK.
You have a Nexus device right?
http://developer.android.com/sdk/index.html
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
ijip said:
OK... I DL the SDK I'm on win and it says it can't find java even after I DL from java. Any ideas?
Sent from my SGH-I777 using Tapatalk 2
Click to expand...
Click to collapse
This thread is for Nexus 4 drivers, not the SDK.
Ask your question in the Q&A section.
theexel said:
Some people may not want that, or want to have the drivers on their other computer. I for one like having the drivers, I only download the platform-tools folder instead of the whole sdk.
So, thanks OP.
Click to expand...
Click to collapse
Yep, I never needed the whole SDK before. I only download the platform tools too.
Have any other ADB drivers installed? Because then you need to uninstall those:
Go into command prompt and write:
set devmgr_show_nonpresent_devices=1
start devmgmt.msc
Delete all devices including driver software in the "Android Device" section.
Then reinstall the Nexus 4 drivers.
If that still doesn't work, update the driver when connected with usb debugging on and manually add by rightclicking the device, click update driver software, then the "Browse my computer for driver software", then "Let me pick from a list..." then "Show all devices" and then Have disk.
Then you simply point to the driver and select the "Android ADB Interface" (Or something like that) it also has driver for bootloader and composite, bootloader is for fastboot, can't remember what composite is for, but you shouldn't use those.
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
qvert said:
the stuff from Fisker didn't did it for me
the driver is installed and the device is in debug mode,
but i can't see in adb devices,
any idea?
Click to expand...
Click to collapse
Go to Device Manager on your PC. If debug mode is enabled, you should see your device listed as an Android phone or something of the sort. If it has a yellow exclamation mark or some sort of symbol next to it, then that means the drivers aren't properly installed. Assuming that is the case, follow FISKER_Q's directions:
Right clicking the device, click update driver software, then the "Browse my computer for driver software." Select the usb_driver folder that you extracted and you should be good to go.
Subbed to refer to later when i have the N4
Sent from my Nexus S
jark99 said:
Subbed to refer to later when i have the N4
Sent from my Nexus S
Click to expand...
Click to collapse
This thread is also in the Misc section of the reference guide in case you can't find it later
I did the same thing and I cant get adb to see my device however fastboot will =/
Shambala001 said:
I did the same thing and I cant get adb to see my device however fastboot will =/
Click to expand...
Click to collapse
Did you enable debugging on your phone yet?
If not, go to Settings > About phone, then tap on "Build Number" 7 times. Go back to settings and you will see developer options. Go in there to enable USB debugging.
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Nitemare3219 said:
Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB.
Click to expand...
Click to collapse
Glad you got it figured out. :good:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Try leaving the phone plug in. Go to Device Manager. Find the ADB drivers and uninstall it. While in Device Manager, have it scan for new changes. You should see your phone appear. Right click it and manually install the drivers.
Letitflow said:
I have exactly the same problem and its driving me nuts! I can't get adb to work. Any suggestions? Did you restart during the whole process?
Of course i tried this:
"Having the same issue. Fastboot works fine, however I am unable to use ADB (device not listed, however is recognized in device manager without any issues). I have tried uninstalling the drivers, but it re-installs them automatically when I plug the phone back in. Debug mode is enabled.
Edit: Fixed by uninstalling the drivers through the SDK manager, then uninstalling and checking the box to delete the driver software in device manager. Re-installed using instructions and now it works in ADB."
Fastboot does not work either.
Click to expand...
Click to collapse
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
IAMLordspeed said:
Same here. I'm running windows 7 and it doesn't matter what drivers I try, ADB doesn't list any devices first time I've ever had this issue.
Click to expand...
Click to collapse
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Stryder5 said:
Make sure USB Debugging is enabled through Developer Options on your phone. Once done, plug the phone into your computer. Go to Device Manager on your computer. You should either see something listed under Android Devices or Other Devices. If you see something under Android Devices, uninstall it. If you see it under Other Devices, right click it and browse to manually install the drivers. Select the folder that has the drivers in my original post.
Click to expand...
Click to collapse
I had to put a check in the box next to "Delete the driver software for this device" to get this to work. Otherwise Device Manager will keep detecting the old drivers.
Related
Hey everyone,
I have been happily using android on nand for quite sometime, and everything has been going well. However, I must have the wrong adb driver installed on my windows 7 computer and can't seem to remove it fully or install the proper one ever. Every time I remove it from device manager, and plug it back in, windows finds it as an HTC composite device, and adb through command line can't find any devices, ever! I would really like to be able to use this feature for things like tethering and what not.
Also, if anyone has any information on how to tether using any OS, windows, mac or linux, I would greatly appreciate it, along with any applications that might be helpful! I have done proxoid in the past and it worked well, pdaNet looks like it might work, but again I don't have a connection to my windows computer!
Thanks in advance for all of the help!
I am using the android SDK usb driver for ADB, you just have to edit a file and add the vendor ID. I can do things like adb logcat, adb shell gives me odd characters in directory listings,I get a ? from adb devices, not sure what that is about.
C:\Documents and Settings\Administrator\.android\adb_usb.ini
Code:
# ANDROID 3RD PARTY USB VENDOR ID LIST -- DO NOT EDIT.
# USE 'android update adb' TO GENERATE.
# 1 USB VENDOR ID PER LINE.
0x0e79
0x0bb4
The 0e79 is for my Archos tablet, works fine there. 0bb4 is what showed up in device manager when I plugged in the phone.
I tried to install that driver for my Polaris and it doesn't work.
It shows "Installing Android Phone" while I have my device plugged in. It takes forever and seems that the USB connection hangs the driver install process, but as soon as I disconnect my device, Windows shows me an error message.
Instructions for Vista\Windows 7
For WinVista/Win7
These OS will install Android as a mass storage device. You must uninstall the driver and update to the android driver model.
Instructions:
1) Unplug all removable devices(thumb drive, sdcards, etc) beside the Android phone.
2) Locate "Device Manager", usually under "control panel"
3) Select "Universal Serial Bus Controllers"
4) Select USB Mass Storage Device.
Note: to check if you have the correct device, click on the details tab and select "compatible ids" under properties. There should be three items listed under value.
5) Select uninstall driver
6) Close the window. Now in device manager a new "Android Phone USB device" with a yellow! will appear... If not, Unplug your android device or select Action -> Scan.
Note: view optional steps below if you still have problem with the your windows automatically installing drivers.
7) Click on the "Android Phone USB device"
8) Select "browse my computer to driver software"
9) Under "search this location for driver", Browse for the location that you have unzip the android_usb_windows and select the corresponding folder for your system(AMD64 for 64bit systems or x86 for 32bit systems. Right click -> properties on "My Computer" to check which system you have)
The driver is now installed and is ready to use.r
***Optional.
1. Go to System under Control Pandel.
2. Click on Hardware Tab and Under "Device Installation" select “Never search windows update for drivers”, then OK.
3. Go to Enable debugging on your phone. (Settings->Applications->Development->USB debugging).
4. Run USBDeview and remove all instances of Android Phone
5. Unplug your phone, and plug it in again.
7. Continue on step 7) above.
To turn off search windows update in windows 7, use this link below
http://www.addictivetips.com/windows-tips/disable-windows-update-device-driver-search-prompt/
To turn off automatic driver installation in windows 7, use the link below
http://www.addictivetips.com/window...tomatic-driver-installation-in-windows-vista/
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
SuperJMN said:
Unfortunately, it doesn't work for my Polaris. The whole driver installation process hangs while my device is connected. As soon as i disconnect it, it continues, but it then complaints about it being disconnected.
Click to expand...
Click to collapse
mine hung as well, what i ended up doing was turnng off the automatic installation. Then uninstalled the adb interface driver that was already installed. Then turning back on automatic installation. Then plugging phone back in and as it was installing automatically, manually installing the adb interface driver at the same time. Eventally the automatic install would error out and the manual install would work. It took like 15 or 20 minutes for it to finish.
when i uninstalled the adb interface, it turned into ''android phone'' in device manager. That was the driver i manually installed while the phone was automatically installing. I know it dont make much sense but it worked for me.
It looks like that will be my fate as well. It also says, that when I do the manual install of the ADB drivers that I already have the most current version installed!!! OH well, keep trying!
Same behavior on my pc with windows 7 32-bits.
When I have lucky the adb driver is connected (working correctly) for a few minutes and then it's disconnected.
i've tried various things to install adb driver, since last night but i've got nothing. i can't install adb driver for my xperia arc.
i installed sdk manager and usb driver. but when i try to install or update driver, i always see this message like "you're using the latest version". So i can't install it.
and also i've tried to uninstall driver and unplugged / plugged my device. then w7 automatically install driver. so i can't install adb driver again.
i want to root my phone, using this way at this link http://forum.xda-developers.com/showthread.php?p=18805560#post18805560
so i must install adb driver, please help me.
thanks everybody
edit: i've windows 7 home premium, 64-bits
SO recently got a nexus one and for some reason i cant get it to be recognized by adb, i have tried everything, updating drivers, reinstalling adb, trying diferent usb cables, different usb ports, but for some reason no matter what i try adb doesnt recognize any device. it recognizes my atrix just fine, but not the nexus. and the nexus is also rooted and has cwm but somehow the bootloader says ship s-on. it all seems prtty wierd. any ideas?
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
baseballfanz said:
I had the same problem once. ADB recognized other devices I had but not the N1.
The driver from this thread got it working for me.
http://forum.xda-developers.com/showthread.php?t=613217
Click to expand...
Click to collapse
already tried that driver and same thing
Theshawty said:
Unlocking the bootloader doesn't control whether the secuflag is on or off. If you Nexus One cannot be found by adb, check if you really have working abd drivers. Use this tool to see what usb drivers are installed and delete everything related to the Nexus One and let them reinstall:
http://download.cnet.com/USBDeview/3000-2094_4-10614190.html
If that doesn't work, plug your N1 to your pc for the last time, then press Windows key + r so the "run" box shows up. Type in devmgmt.msc (device management) and press enter. See if something called "android phone" has a yellow triangle. Download and unzip the attached archive. Right click this "android phone" and choose to update its drivers. Locate to the folder you just unzipped and then let the drivers install.
Now it should work just fine. Cheers.
Click to expand...
Click to collapse
still nothing with reinstalling
gunna try restoring stock firmware and see what happens
not even going back and flashing stck firmware will let it connect to adb
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Aceyo said:
USB debugging is ON, right...?
but thats probably not the problem.
driver issue, most likely. try installing sdk here
"The Google USB driver is a downloadable component for the Android SDK, available from the SDK Manager"
Click to expand...
Click to collapse
as i told the other 2, it is not a driver issue, it turns out the guy i got it from had work done on it before it was shipped, thinking something internal is the issue
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
I'm having similar issues, laptop running win 7 can't see Nexus 6, DL'd drivers, even tried Motorola for drivers but although showing in device manager as installed no connection
At least they installed for you. The drivers don't even recognize my device. I still get a yellow Nexus 6 in device manager with no usable connection. Ugh...
Sent from my Nexus 6 using Tapatalk
Seems to be a lot of this going around. I'm on win 8.1. I couldn't get the drivers to work via the sdk. Then I tried the Google and Motorola drivers. After deleting the devices on device manager I finally got the N6 to connect via mtp. However, I can't the computer won't connect via mtp if USB debugging is on. On top of that I can't get adb to even see the phone. I would suspect it's more of a Windows problem at this point. I need to do some more testing from another pc.
Sent from my Nexus 6 using XDA Free mobile app
Have any of you tried using Wug's Toolkit?
http://forum.xda-developers.com/showthread.php?t=2947452
Managed to connect via PTP eventually by uninstalling and reinstalling drivers, seems to work with PTP and USB debug on, but not with MTP
wfujay said:
Hey guys, weird stuff going on here.
Downloaded the latest Android USB drivers as well as the SDK. When updating the device from the device manager, ADB drivers loaded fine, but MTP drivers and "Nexus 6" (camera mode) drivers will not install no matter what I try. USB debugging mode or not, no dice.
What I did find odd, is that when opening the android_winusb.inf file that was packaged in the latest usb drivers, there is no mention of a Nexus 6 phone inside - which explains why the drivers won't install See screenshots below.
http://i.imgur.com/qmgxwsd.png
http://i.imgur.com/9NGYxsR.png
I'm not sure if I feel comfortable "hacking" the inf file in order flash my phone, but maybe it would be ok Is this a screw up on Google's part or am I way off base here?
Click to expand...
Click to collapse
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Use the universal naked drivers. I have multiple devices and the drivers don't cooperate with each other but since I installed the naked drivers I have had any issues.
http://www.xda-developers.com/andro...r-solves-your-adb-driver-problems-on-windows/
---------- Post added at 05:46 PM ---------- Previous post was at 05:45 PM ----------
http://forum.xda-developers.com/goo...nt/adb-fb-apx-driver-universal-naked-t2513339
I fixed it! Wug's toolkit didn't work, although I'm about to use it to unroot, lock, and return my phone to factory state since it has to be taken back to the AT&T store to be replaced due to a screen defect. Hope they don't freak out about the death star being scratched off, lol.
Anyway, oddly enough the problem is because I'm using Windows 8.1 N, which doesn't come with Windows Media Player or any of the media features. Installing the Media Feature Pack for N and KN versions of Windows 8.1 sorted it out. Installed, rebooted, done. I can now access the device in any mode and the device driver errors are gone.
So if anyone is having the same issue with Windows 8.1 N, download and install this: http://www.microsoft.com/en-us/download/details.aspx?id=42503
Reboot and enjoy!
thanks
EvanVanVan said:
This may not apply to you at all, but with the mess of Android drivers I have to install over time I've finally figure out a solution when something is not installing correctly. Did you try right clicking on the Nexus 6 (I'm assuming that has a yellow exclamation point) going to:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Same thing was going on with my nexus 6 and I tried what you said and updated everything. Now the MTP works. thanks
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
Click to expand...
Click to collapse
Thank you so much ! MTP Works now. Hail to the king
EvanVanVan said:
Update Driver Software > Browse my computer... > Let me pick from a list > Portable Devices > and find a compatible MTP driver in there
I'm saying Portable Devices specifically because that's how my Nexus 6 shows up as (as an MTP device) in the device manager.
Click to expand...
Click to collapse
Ran into the same issue initially when I was trying to root my Nexus 6. Wug's didn't work, and neither did the naked universal drivers. Added the Nexus 6 ID to the inf and still didn't work.
Had to install the Motorola driver kit, and then go through the drivers as above to find a Motorola that finally worked; while the Motorola driver is just a wrapper for some Microsoft driver that normally comes built into Windows since Windows 7.
Nexus 6 Driver (ADB, Fastboot and MTP) for Windows and MAC
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.
Same here. Nexus 6 stock lollipop 5.1.1 with unlocked bootloader. I thought it was my personel windows 7 pc. But no its any pc I try to connect to. Found that out because I work at a big business full of windows pc's. I remember at one point not having this problem at all. Don't know if it was before one of the lollipop updates but I remember I used to connect my phone at work on any pc the pc would automatically open MTP asking me what I wanted to do. That was without adb turned on. I've tried everything searched everywhere, installed,uninstalled drivers from Google, Motorola etc. Even tried wugfresh's instructions. My pc does not recognize my phone at all. Mtp, Adb, Fastboot, nothing. Weird thing is I also have a nexus 5 and as soon as I connect it its recognized. Don't know if it maybe the cable that's the only thing I haven't tried since my cables are not Motorola cables, or nexus 6 original cable as that is the way I bought it. But it used to connect. Now I'm stuck, at a loss. Don't get it, called Motorola, Google, T-Mobile. I think they know nothing about phones as when I tell them the problem they look at me like I'm talking Chinese. If anyone knows what the problem is and have been able to fix it please hit me up @ [email protected] Just about to give up. I just don't understand what the problem maybe. Running stock lollipop 5.1.1 with unlocked bootloader never rooted. Thanks and hope someone can help.
I had the same issue. I installed the latest google drivers from the Android SDK and my computer would not recognize my Nexus 6. I couldn't use fastboot or anything. I was able to fix this though. With my Nexus 6 hooked up to my computer, I opened device manager. There was the "unknown device" which was my Nexus 6 obviously. I right clicked on it and attempted to install the driver, the automatic driver installation method could not find it. I had to point it directly to the file. The file is located in the android-sdk files. I had to point it to c:/android-sdk/extras/google Obviously location will vary depending on where you installed the android-sdk. Just make sure to only point it to extras/google. I wen't further in the first attempt and it didn't work. I hope this helps. I suck at explaing stuff.
Long Island NOOBIE said:
http://www.theandroidsoul.com/nexus-6-driver-adb-fastboot-mtp-windows-mac-68355/
I discovered the following troubleshooting tip listed below (amongst others) at the website above. It worked flawlessly with my brand new unlocked stock Motorola NEXUS-6 (XT-1103) and Windows-7 PC. Thank you and big props to the developer(s) who posted it!
1.Connect your Nexus 6 to computer with a USB cable and open Device manager on your computer.
2.Look for ‘Android Composite ADB Interface‘ entry, right-click and select uninstall from the context menu.
3.In the uninstall pop-up that appears, tick ‘Delete the driver software for this device’ checkbox and press the “Ok” button.
4.Disconnect your phone from your computer.
5.Disable USB debugging on your Nexus 6 from Settings » Developer options » un-tick ‘USB debugging’ checkbox.
6.Put your Nexus 6 in MTP mode (It should be in MTP by default unless you selected the Camera (PTP) mode).
7.Connect your Nexus 6 to the computer again, and let the computer re-install drivers automatically. If it doesn’t re-installs driver, try toggling the ‘USB debugging’ option on your device.
Click to expand...
Click to collapse
This didn't work the first or second time. I did steps 2 through 7 3 times and then it worked. I must have had a lot of drivers installed.
So if it doesn't work the first time, keep uninstalling the drivers and try again and again. Worse case scenario, you have to install the drivers again. hope this helps.
I want to add my own tale to his thread with the hope that it will help someone. I could not see the Nexus 6 when I set MTP mode or MIDI mode. The phone showed up on the PC when I selected PTP (camera) mode. In my case, I had four external USB3 hard drives connected. I finally turned off the hard drives and then MTP mode would be visible, both as a Portable Device, named Nexus 6, in the Device Manger, and as the same under My Computer in Windows Explorer. After Imy PC recognized the Phone in MT mode, I tuned on the external drives and all were visible.
I cannot possibly figure out what the heck is causing my Windows 8.1 Installation to not detect my Nexus 6. Google comes up with TONS of results for this issue, but all troubleshooting points to what I have already done.
Plug it in, comes up as "Nexus 6" under "Other Devices" in Device Manager. With the little Yellow ! mark.
Downloaded the USB drivers from here - http://developer.android.com/sdk/win-usb.html attempted to install them and I get an error message. After selecting the folder that contains the driver.
"Windows was unable to install your Nexus 6: Windows could not find the driver software for your device. If you know the manufacturer of your device, you can visit its website and check the support section for driver software"
What I have Tried:
- Installing Drivers with USB Debugging ON and OFF
- Installing Drivers with Connection set to MTP and PTP on the phone
- Disabled Driver Signature Enforcement and attempted to install.
- Downloading Drivers a second time to ensure no corruption was in the file.
- Attempted to install via Android SDK (This appears to work per SDK software, but Device Manager shows no change, and the nexus isnt showing up in Explorer.)
- Tested Nexus on another Device. (Running Windows 7. Literally Plug and play No manual Installation needed. Worked)
I'm at total Loss here, Any other Ideas?
@morbid_bean,
Did you try the Motorola Device Manager >https://motorola-global-portal.custhelp.com/app/answers/detail/a_id/88481
Thanks for the reply. Unfortunately that seems to have done nothing
I'd go w/ uninstall all other drivers first, change cables and see what happens.
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
morbid_bean said:
Thanks for the reply. Unfortunately that seems to have done nothing
Click to expand...
Click to collapse
This is a long shot, but you did install the Java JDK, right?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
You do not need the JDK to install the drivers...
efrant said:
You do not need the JDK to install the drivers...
Click to expand...
Click to collapse
I understand. OP has diagnosed his problem as drivers, but if his problem is ADB not connecting to his N6, it could be the problem. As I said, it's a long shot.
OP Here with a status update.
Continued to try some other suggestions. Such as another Cable, another USB port, reboots. Hell I seriously went as far as a whole Windows 8.1 Re-install. I had some feeling that possibility because I am rooted its causing issues; so I even went as far as taking my old Nexus 4 and reverted it to 100% stock to attempt to install the drivers and then trying the nexus 6. But I got same results.
efrant said:
Try this:
1) Download the driver from the link in your post, and unzip the files to any location;
2) Open Device Manager on your PC and turn on the option to "Show hidden devices" from the View menu;
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.);
4) With USB Debugging set to OFF, plug your device into your PC. Windows should automatically install the MTP driver and It should be recognized;
5) Now turn USB Debugging ON;
6) Go back into Device Manager, right click on your device and select "Update driver software";
7) Select "Browse my computer...", NOT "Search automatically...";
8) Click "Browse", and locate the driver you downloaded in step 1.
EDIT: I don't think you have to disable Driver Signature Enforcement, but if it gives you issues, try disabling it.
Click to expand...
Click to collapse
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
cam30era said:
This is a long shot, but you did install the Java JDK, right?
Click to expand...
Click to collapse
When I installed Android SDK, it told me I needed JDK before proceeding with the installation. So I'm pretty sure I did this.
morbid_bean said:
When I follow these steps I was successfully able to install drivers for something called "Android Composite ADB Interface"; "MTP" or "Nexus 6" was still failing. Even after switching debugging on. I still unfortunately do not see anything in Explorer that I can access the Nexus 6's files. Maybe this is an indicator that I am getting closer?
Click to expand...
Click to collapse
I just realized that the last part on my step 3 was cut off. It should read:
3) Right click on EVERY item that could potentially relate to your device (e.g., adb interface, composite interface, motorola, nexus, etc.) and uninstall, including deleting the driver.
As far as your issue, I'm pretty sure that Windos recognizes the N6 as an MTP device (assuming you have it on MTP) without any additional drivers, so I'm not sure what the problem is. My steps were to get the ADB driver installed, which seems to have worked. (ADB allows you access to your files via command line...)
Sent from my Nexus 6 using Tapatalk
FIXED IT!
I am running a version of Windows 8.1 known as Windows 8.1 Pro N Essentially this is a slightly stripped down version and does not include "Windows Media Player or other Windows Media-related technologies, such as Windows Media Center and Windows DVD Maker" I managed to get this copy really cheap.
More Info Here
So essentially I needed to download THIS Pack/Update which gave me these special features. Including the resolution of my Driver Problem. Rebooted the computer plugged in my phone and it was detected and installed drivers automatically.
Special Credit to THIS thread for helping me with the answer. I hope this can be added to any Driver Installation Guide or Sticky to assist others that may come across this problem.
Glad you got it resolved. I've never heard of Pro N. Another wrinkle in the Windows 8.1 driver issues, it seams.
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Pneuma1985 said:
Recently I have been deving on a friends nexus 6 with 5.1.1 on it all drivers are installed properly device shows in adb i even get adb root successful but it refuses to adb remount for testing purposes even on roms that have modified boot.img's with init.d in them and ro.secure=0 set and adb persistance is also set so there is no reason for it not to mount. I imagine there could be a problem with it mounting system on boot but I am new to aosp 5.1.1 roms and this solution did not work for me it tells me the windows 8.1 version I'm running is not applicable for this update? So if anyone can lend some assistance it would be much appreciated.
The Nexus 6 is VZW unlocked bootloader and rooted twrp recovery all the latest
currently any rom i try i cant mount through adb so testing for themes is impossible?
Click to expand...
Click to collapse
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Evolution_Freak said:
Have you tried this:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Pneuma1985 said:
My question is: Why would old google universal adb drivers work when everyone else says to use the new google usb drivers in tandem with the Motorola drivers for vzw? Thats the only reason i didnt use the tool is b/c its outdated?
Click to expand...
Click to collapse
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Evolution_Freak said:
But alas! It does work, I've tested it myself. Also, you can install the most recent drivers optionally.
Click to expand...
Click to collapse
I just tested it and it does not work i still get permissions denied when i try to remount it.
Pneuma1985 said:
I just tested it and it does not work i still get permissions denied when i try to remount it.
Click to expand...
Click to collapse
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Evolution_Freak said:
I don't usually recommend toolkits but you could try this:
http://forum.xda-developers.com/showthread.php?t=2947452
Click to expand...
Click to collapse
Yup that didnt work either. I get su in adbshell it shows me # so there is su i just dont get why it wont mount at all or pull or push obviously cant do that if it won't mount. And no tutorial I've followed nor solution has worked thus far. As stated above that solution worked for him with windows media center or whatever but that doesnt apply to me. I've done this hundreds of times with many many many devices on windows 7 I've even done it with 3 devices on 8.1 so far no problems this is the only one to give me issues like this.
It's always a bit of messing around with it to get it to work but this is different i have spent hours going back and forth removing all drivers installing new ones using tools etc.
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
LuminousOne said:
After doing lots of reading and trying many things I cannot connect in fastboot mode. I tried on two computers, holding volume down and plugging in usb cable. In CMD I run fastboot status and it just stays on <waiting for device>. I have connected other Android phones so maybe that is somehow messing up the device drivers, but I reinstalled them. Also when I run adb reboot fastboot from CMD, the phone restarts normally and not to fastboot but the volume down at least shows blank screen.
My goal is to get root, so whatever is easiest.
Click to expand...
Click to collapse
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Didgesteve said:
If you have used that computer for other phones previously, that might be the problem, Winodws is asigning the wrong driver. In your picture you have devices with warning triangles (no drivers). Try manually assigning the Sony driver. Depends on what you're doing, but you need a different driver for when you want to use ADB, so start the phone into recovery, connect it to your PC and look again in the device manager and manually add the Google USB driver.
If you are using windows10 and trying to install drivers, it doesn't tell you that the install failed. Restart the machine in safemode and look for 'driver signing disabled'
Click to expand...
Click to collapse
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I'm not sure what you're trying to do. If you want to flash a rom, you want flashmode, volume down (-) then plug in the USB. If you want fastboot it's volume up (+) then plug in the USB..
MTP driver is wrong, you need to uninstall it and re-install the sony driver. Windows chooses the wrong driver by default and you have to manually add it yourself to make it work.
Having said that you mentioned that you are getting ADB commands to work, so I'm confused, perhaps the google driver is in place, but the Sony one is not.
You need both, when the phone is in fastboot it's presented as a different device than when connected via ADB.
Hope that helps explain a bit.
But if you're having issues with the drivers, should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
LuminousOne said:
It's unclear to me which driver should be added to which device. For example should the Sony or Google driver be added to the section Android Devices, Portable Devices, or Sony?
Click to expand...
Click to collapse
I had this problem before. My fault before was install drivers in usb-debugging mode, then a change to fastbook/flash, and then the phone is not recognized or connection properly - despite me thinking I had correctly installed the drivers.
Took me months to figure it out. Boot into windows, then connect your phone in all modes, flash mode, fastbook mode, standard, and usb debugging - and for each mode - install the Sony driver again.
The result will be, that for every mode - when you go to device manager - you won't see an exclamation mark. If you ever see an exclamation mark again - install the driver. You get the idea.
Regards,
I finally found the f**kin problem the invalid driver was hiding under "other devices" only when the phone was in fastboot mode. Basically I followed the instructions of user2021355 from here.
Start Windows in test mode (instructions)
download driver from https://developer.sony.com/develop/drivers/
in admin command prompt run adb reboot bootloader
if the above step failed, you have a problem with adb and the solution is something different
open device manager and carefully search for any errors. I found mine hidden under "other devices"
right click on the errored driver and choose update
choose browse my computer
select the driver you downloaded from step 2
verify if working by running fastboot devices and you should get a serial number
Didgesteve said:
should you really be going down the unlocking road? It doesn't get you many advantages and breaks a whole heap of sh*t.
Click to expand...
Click to collapse
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
LuminousOne said:
I thought the only thing it broke was the camera and there's a DMR fix for that. Does it mess up something else?
Click to expand...
Click to collapse
Some banking and games apps don't like rooted phones.
Not sure about android pay.
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
same is when pointing to the drivers from here: https://developer.android.com/studio/run/win-usb
I ve the G8441
sheedy1900 said:
Hi
I ve the yellow exclamation mark in device manager -> other devices -> "Android"
When I point to the Xperia_XZ1_Compact_driver/ folder (from https://developer.sony.com/file/download/xperia-xz1-compact-driver// ), windows cant find a driver.
I ve the G8441
Click to expand...
Click to collapse
Add the driver manually.
Didgesteve said:
Add the driver manually.
Click to expand...
Click to collapse
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
LuminousOne said:
At least for me it wasn't enough to add the driver manually (I think because the invalid driver would still be there). So you need to right click on it, update, then browse to the downloaded driver.
Click to expand...
Click to collapse
I think we have different ideas of what adding the driver manually is
sheedy1900 said:
OK I got it working with installing the driver, win10 bootet with disabled Driver Signature enforcement
Click to expand...
Click to collapse
i have the problem as you and I'm also on win10. can you share how you installed the fastboot driver?
the adb and mtp drivers work fine for me, just fastboot is not working
unsigned driver under W10
try this one
https://www.maketecheasier.com/install-unsigned-drivers-windows10/
Gesendet von meinem viennalte mit Tapatalk
I have the same problem with my Sony XZ1 Compact G8441.
'adb devices' shows my phone, after 'adb reboot bootloader' phone goes into fastboot mode (I think), the one with blue LED, but 'fastboot devices' does not show any connected devices. Same when pressing Volume Up or Volume Down while plugging the phone in.
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Tried installing through device manager, right-click on faulty 'Android' under 'Other Devices', update driver, browse to download location.
With 'Sony XZ1 Compact driver' it found no installable drivers.
With 'Sony Fastboot Driver' it found an installable driver but had an error. Error said something like 'Did not find "Android ADB Interface", installation failed'.
I tried figuring out what you guys meant by 'installing driver manually' but I don't understand. Is it what I tried above, or something else?
My goal is to be able to install TWRP, which needs an unlocked Bootloader first. I followed the instructions on the official Sony Website for that.
Sorry. Delete this.
Gnorv said:
After some reading I figured it was a driver issue, so I tried installing drivers from Sony XZ1 Compact driver and Sony Fastboot Driver.
Click to expand...
Click to collapse
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Didgesteve said:
If you're using Windows 10 you'll have thought that you'd have installed the drivers, but W10 fails on driver install and doesn't tell you.
Start the pc in 'safe mode' (hold shift while restarting), then choose 'driver signing disabled', install the drivers agiain. This time it should work.
Click to expand...
Click to collapse
No, that did not help. The same problem remains. Phone is recognized when powered on by 'adb devices' but not recognized after typing 'adb reboot bootloader' and 'fastboot devices'.
Thanks for your suggestion though.
I got the problem that no matter what i do i can't install the driver.
Booting windows 10 with driver check disabled does not solve my problem.
Once i selected the driver to install i end up with a questionmark in the device manager above the android device. Taking a closer look reveals that there seems to be no driver installed.....
Any advice?
I tried:
1. Booting with driver signature check disabled
2. Switching windows 10 into test Mode
I booted ubuntu from a live usb stick and went from there. That works like a charm without the need of installing any drivers
Both solutions do not work....