[Q] Mac won't detect my Nexus 6 (or other devices) - Nexus 6 Q&A, Help & Troubleshooting

Since Google recently released the second preview of Android M, I've been trying to sideload the OTA through adb. The problem is that my Mac won't recognize my Nexus 6 whenever I plug it in. I have debugging on and change the USB mode to MTP, but still no luck. However, when I change the USB mode to MTP, Android File Transfer recognizes my Nexus 6 and I can go through my device's file system. I've also connected my dad's droid razor m to see if the problem only occurs on my device, but the same thing happens to his phone, too. Since I had no luck on my Mac, I tried to sideload the OTA on my Windows 7 desktop. adb only recognizes my nexus 6 when I have it booted up regularly, but when I put it in recovery mode, my desktop makes the sound that signals it can't connect to my device and it won't show up in adb, either. Any suggestions? I believe adb is set up correctly on both my mac and desktop since I can execute other commands such as "adb version" and "adb help". Thanks in advance!
And here is the device information of my nexus 6 and my dad's droid razor m:
Nexus 6
32GB
not rooted
stock recovery
stock rom - Android M Preview 1
Droid Razr M
8GB
rooted
custom recovery (TWRP)
custom rom - Cyanogenmod 12 Android 5.0.2 nightly build

elvintopalov said:
Since Google recently released the second preview of Android M, I've been trying to sideload the OTA through adb. The problem is that my Mac won't recognize my Nexus 6 whenever I plug it in. I have debugging on and change the USB mode to MTP, but still no luck. However, when I change the USB mode to MTP, Android File Transfer recognizes my Nexus 6 and I can go through my device's file system. I've also connected my dad's droid razor m to see if the problem only occurs on my device, but the same thing happens to his phone, too. Since I had no luck on my Mac, I tried to sideload the OTA on my Windows 7 desktop. adb only recognizes my nexus 6 when I have it booted up regularly, but when I put it in recovery mode, my desktop makes the sound that signals it can't connect to my device and it won't show up in adb, either. Any suggestions? I believe adb is set up correctly on both my mac and desktop since I can execute other commands such as "adb version" and "adb help". Thanks in advance!
And here is the device information of my nexus 6 and my dad's droid razor m:
Nexus 6
32GB
not rooted
stock recovery
stock rom - Android M Preview 1
Droid Razr M
8GB
rooted
custom recovery (TWRP)
custom rom - Cyanogenmod 12 Android 5.0.2 nightly build
Click to expand...
Click to collapse
On Windows, when entering recovery, unplug the USB then reconnect it.

Evolution_Tech said:
On Windows, when entering recovery, unplug the USB then reconnect it.
Click to expand...
Click to collapse
I've tried that, too.

elvintopalov said:
I've tried that, too.
Click to expand...
Click to collapse
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979

Evolution_Tech said:
On Windows, when entering recovery, unplug the USB then reconnect it.
Click to expand...
Click to collapse
Evolution_Tech said:
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Thanks, I'll see if it works when I get home.

Evolution_Tech said:
Try this instead:
http://forum.xda-developers.com/showthread.php?t=2588979
Click to expand...
Click to collapse
Just tried this out with no luck. Any other suggestions?

I've never used a Mac, so I can't help you there (but from my understanding, it should recognize your device as soon as you plug it in).
As for Windows, you need to install the Google USB driver found here.
Now, this can be a bit of a pain, but it is doable: Depending on how you are connecting to your device, the driver may need to be installed multiple times.
For example:
If you are connected with your device booted into Android, you need to install the driver;
If you are connected with your device booted into the bootloader, you need to install the driver again,
If you are connected with your device booted into the stock recovery, you need to install the driver again,
If you are connected with your device booted into the stock recovery and you select ADB Sideload from the menu, you need to install the driver again;
If you are connected with your device booted into a custom recovery, you need to install the driver again.
Always make sure that you manually install the driver, i.e., right click on the android device in Device Manager in Windows and select Update driver". Then do NOT select "automatically search for the best driver.. blah, blah" or whatever the option is called. Select the second option (something like "let me choose from a list") and then click the "have disk" button, and install it that way.

efrant said:
As for Windows, you need to install the Google USB driver found here.
Now, this can be a bit of a pain, but it is doable: Depending on how you are connecting to your device, the driver may need to be installed multiple times.
For example:
If you are connected with your device booted into Android, you need to install the driver;
If you are connected with your device booted into the bootloader, you need to install the driver again,
If you are connected with your device booted into the stock recovery, you need to install the driver again,
If you are connected with your device booted into the stock recovery and you select ADB Sideload from the menu, you need to install the driver again;
If you are connected with your device booted into a custom recovery, you need to install the driver again.
Always make sure that you manually install the driver, i.e., right click on the android device in Device Manager in Windows and select Update driver". Then do NOT select "automatically search for the best driver.. blah, blah" or whatever the option is called. Select the second option (something like "let me choose from a list") and then click the "have disk" button, and install it that way.
Click to expand...
Click to collapse
AKA: "Windows driver dance"

Related

Usb Driver Problems

Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
magma9495 said:
Ok. Right now I'm trying to root my nexus. I'm stuck at installing the usb driver. I tried following this tutorial /showthread.php?t=613217 but every time i choose the driver and it searches it tells me it "couldn't find a better match for my hardware" and the driver doesn't install. I've tried 2 different computers, a macbook pro dual booted with Win XP media center Sp 2 and a dell XP media center Sp 3. No luck with either of them. Anyone tell me what I'm doing wrong please? its getting really anoying
Click to expand...
Click to collapse
I'm having the same issue myself i think.
Look under N1 Q&A and find the topic "N1 Bricked"
Glad to know im not the only one
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
I have a tutorial called ADB 4 Dummies that will walk you through installing the android sdk 2.2(froyo) and setting up your environments. Step by step for every system.
First thing, unplug your Phone from computer, uninstall ALL drivers and try from scratch.
Also, if you're using windows, when you're done and you plug in your phone, don't choose to "automatically find drivers" instead manually point it to the drivers folder in the SDK.
Don't worry, it's not bricked. lol.
mrandroid said:
I have a iMac and I never even had to worry about drivers.
Just download/install/setup the Android SDK and the rest is automatic.
Click to expand...
Click to collapse
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
magma9495 said:
Followed your tutorial, got adb and everything to work, adb will recognize my Motorola Cliq, but for some reason my nexus doesn't show up. When i do adb devices no devices come up
Click to expand...
Click to collapse
Hmmmm....
There are 2 modes to the bootloader HBOOT and Fastboot.
Make sure you're phone is in fastboot mode... it should say FASTBOOT USB highlighted in red on top. If it doesn't, use the volume down key, select Fastboot and hit the power button once to switch the phone to fastboot.
Remember, "adb devices" works while your phone is turned on regular. If your phone is in Fastboot mode use "fastboot devices"
Ok, are you using windows? If you are;
Turn off your phone and boot it back up in Bootloader mode. (trackball+pwr, or volume down+pwr)
Once it's on bootloader, plug it in to the computer.
See if the computer asks for any drivers, etc. If it does point it to the Drivers folder in the SDK. If it doesn't... go into your Device Manager. (Right click on MY COMPUTER, click on MANAGE and when computer management opens up, go to Device manager from the list on the left). Look to see if there are any icons with an Exclamation mark and yellow background. If there is, right click on it, select update driver and point it to the drivers folder in the sdk.
Basically there should be a menu on top that says "Android Phone" and when you expand that selection you'll see "Android Bootloader Interface".
nope, no luck with that either, I tried it both on windows XP and windows 7. same error each time. Could it be a problem with my device? because Snow Leopard doesn't recognize the nexus as a storage device or anything
Damn. I think i'm out of options. Last thing to try:
- Turn on phone regular.
- Plug in through USB to computer (try a different USB cable, even if that one worked with the CLIQ, try a different USB port also.)
- On Phone: GO to settings, Application Settings, Development, USB Debugging, (if it's checked on, check it off then on again) make sure it's ON.
Go into your Android SDK folder, go into the TOOLS folder. Now click on DDMS. See if it lists your device...
Last thing would be to go back through the Device Manager, and click on SCAN HARDWARE while your phone is plugged in... It has to be on that list somewhere, whether it's a bad driver, etc, it should still appear in your device manager somehow.
alright that didnt work, but, i got it, i just kept unplugging and plugging back in my phone until adb recognized it. then i got fastboot to run and now i have superuser . But now im stuck at another point. I'm trying to do the recovery.img file. I tried in mobile terminal "flash_image recovery /sdcard/recovery.img" but it told me something like "flash_image not found" I saw that i could do this via fast boot but i dont know how to do that. how would i do fastboot on Mac?
http://www.myhangoutonline.com/tutorials/nexus-one/6-upgrade-nexus-one-recovery
when i try to do the fastboot command i get "-bash: fastboot: command not found" i dont think i have fastboot set up right
have you tried typing in "./" before the command? I found that that was one of my mistakes I did when I first rooted my phone
tried that, entered "./fastboot-mac flash recovery recovery.img" and i just get "waiting for device"
I believe you can also try "./fastboot-mac flash recovery ./recovery.img"
Alright I flashed a clockwork recovery through the app manager in the market. Is there any way I can apply the other recovery with an update.zip?
Also, thanks so much for all the help guys!!!!!!!!!!
you can do it through terminal emulator, if you go to amonra's recovery thread he tells you how.
this is the link http://forum.xda-developers.com/showthread.php?t=611829
fastboot somtimes doesn't come in the SDK... download the version for your system from here: http://www.myhangoutonline.com/tutorials/nexus-one/5-unlock-nexus-one-bootloader
place it in your androidsdk/tools folder

Having a problem getting in Fastboot!

Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
ikutoisahobo said:
Ok, I get into Fastboot on my DELL S7 it just keeps on saying "Starting Fastboot USB download protocol" and other stuff in red text above, besides that I need to install the driver on my computer for Fastboot but Windows 7 says "Windows was unable to install your Fastboot" I guided windows to the driver folder in Fastboot+ADB which I got from the Clockwork Mod 5.0 RECOVERY Flash thread.
I really want to flash this clockwork mod http://forum.xda-developers.com/showthread.php?t=1334487
EDIT: Fastboot working, ok I have another problem I flashed the CWM 5.0 IMG file thru fastboot, but how to go into CW recovery? isn't it Power + Up Volume, but that takes me to the Dell update system.
EDIT 2 : I got everything working, used my brain instead of working blindly. Thanks anyways.
Click to expand...
Click to collapse
Where did you find the driver during the fastboot screen? I'm having the same problem and any help would be definitely appreciated. What stock android did you have before installing CWR?
Ok, I had ADB drivers for a Motorola CLIQ and it worked, just select choose from list of installed drivers and selct Android Interface or ADB interface or whatever wityh ADB or android in it. Tyhen run cmd and ttpe fastboot.exe or fastboot
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
PfcKirk said:
I see a few posts where folks cant get their computer to install the fastboot driver from the FASTBOOT+ADB.ZIP but then they say they got it working, but nobody has said how! I have XP sp3 and cant get the computer to install a fastboot driver. The ANDROID PHONE device is empty as well as the ANDROID USB DEVICE. I get adb interface when I plug in my Epic but I even tried uninstalling it and seeing if the steak would install but no go. Any suggestions?
Click to expand...
Click to collapse
Yeah, that's right.
This is how it is download ADB which is basically downloading the SDK.
And if you have an Android phone or something just install the drivers for it, usually downloads adb drivers for it too, or if that doesn't work try downloading MOTOROLA CLIQ USB or ADB drivers....as I had them installed when I plugged in the phone.
Put device in fastboot mode
Connect device
Open up Device Manager
Click on "Fastboot" or whatever it says
Click on "Update driver"
Click on "Browse my computer for driver"
Click on "Let me pick from a list of device drivers on my computer"
Click on "Have Disk"
Find your fastboot drivers

[Q] Phone won't connect via ADB

Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
nikpmr said:
Hi all.
I'm trying to S-Off my HTC first, but I can't get the phone to connect to ADB while in debug mode. It connects to ADB fine while in recovery mode, but apparently it needs to be in debug mode for moonshine to work. The phone is unlocked and rooted and I installed the HTC drivers. In the device manager it comes up as an Android device in recovery mode, but as a portable storage device in debug mode.
Can anyone tell me what I'm doing wrong?
Click to expand...
Click to collapse
Does it show up when typing adb devices in the command prompt?
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
nikpmr said:
Thanks for the reply.
No, not unless the phone is in recovery mode. Fastboot works as well. However when the phone is on and in debug mode I get nothing.
Click to expand...
Click to collapse
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Try to force ADB to redetect with adb kill-server.
abrahammmmmmm_ said:
Hmmm sounds like what happened to me once it was a frustrating situation but all that was needed was an update to the ADB drivers for the device. Sadly I'm away from my computer right now so it'll be a while until I can actually whip something up to help you, sorry
Click to expand...
Click to collapse
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
nikpmr said:
Okay, let me know when you have some time. Thanks again!
I tried the kill-server command to no avail. The computer just plain doesn't recognize it as an Android device. I will try on my Linux computer and see if that makes any difference.
Click to expand...
Click to collapse
Is your computer windows 7, 8 x32 or x64bit? I can probably do it today if you've got a windows 7 x64bit computer since I wont have to do much looking
I'm running win 7 64 bit. Thanks again for your help!
nikpmr said:
I'm running win 7 64 bit. Thanks again for your help!
Click to expand...
Click to collapse
NOTE THAT YOUR PHONE SHOULD NOT BE CONNECTED DURING THIS PROCESS
I already searched & set up the update folder so you don't have to do all the dirty work d:\
Ok Well I'm just going to make this quick and not really got through the basics like how to unzip things because if you don't know how to do that you probably shouldn't be trying to get s-off on your phone anyway so I'll just assume you already know how.
Step 1. open control panel select hardware and sound and open Device Manager with the administrative logo one the side.
Step 2. Near the top or somewhere on this list there's supposed to be a drop down that reads "adb devices, adb android, adb, android, adb drivers etc. Mine shows Android USB Devices it actually just varies based on computer I can't really go to the specifics of it but I'm sure you can find it.
Step 3. Select that dropdown menu and right click whatever shows (there should only be one thing) and then select Update Driver Software and choose the option that says Browse my computer for driver software and locate the htc drivers folder which should already be unzipped, select the whole folder and have the option to include subfolders checked. click next or whatever it says to finish
Step 3 Now you must remove your device from the Portable Devices dropdown menu to ensure all drivers are detected for the phone, to do this right click on HTC First and just select remove, wait until it's done. and now just reconnect your device and let all the drivers install and it should now be done!
Make sure you look at the screenshots I attached to make sure you don't accidentally remove or update something else also because that's where the drivers folder is an i'm pretty sure you'll need that
A reboot of the computer is recommended btw
Ask questions if you have any
View attachment 2459140
View attachment HTC_drivers_Win7_x64.zip
View attachment 2459141
Wow, that's quite explanatory, thank you! Unfortunately I only see the category ADB Devices when the phone is connected and in recovery mode, and I only see the category Portable Devices when the phone is connected, booted, and in debug mode. (Neither of these categories are visible when the phone is disconnected from the computer.) I did however try installing the drivers you gave me with the phone connected and in recovery mode, but to no avail; after the phone boots ADB Devices disappears and Portable Devices appears. Uninstalling Portable Devices doesn't help either; it just reinstalls when I reconnect the phone.
I am trying to get the category ADB Devices to appear in the Device manager when the phone is turned on and in debug mode so that I can use ADB while the phone is booted.
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
nikpmr said:
Got it working. I had to go to device manager > portable devices > HTC First and replace the driver with Generic USB Composite Device Driver.
Boom. Everything working. Weird.
Click to expand...
Click to collapse
How exactly did you replace the HTC First driver with the Generic USB Composite Device Driver?

MTP & "Nexus 6" drivers won't install...help?

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.

Cannot Get Drivers Installed for Windows 8.1 - Manual Installation or SDK

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.

Categories

Resources