It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Stryder5 said:
How did you get install the drivers? If you haven't done so, you can just grab the drivers from here: http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
Yes, that's where I got the drivers (and that's how I got fastboot working).
I've taken the drastic step now of uninstalling the entire SDK thing and am currently re-installing it. We'll see how that goes.
EDIT: yeah, "adb devices" still gives nothing at all.
You need to turn it on first but Developer Options are hidden in Settings. Go into About phone and tap the build version. After 7 times you will have access and you can turn on USB Debugging
chinly43 said:
It seems like I go through this every damn time I get a new Android device, so you'd think I'd have figured it out by now, but I haven't.
How the heck to I get ADB working for this device? It's not being recognized by the "adb devices" command right now. As far as I know, I've got the drivers installed (at least, I could communicate via fastboot). I don't know what else I need to do, and would appreciate any help.
Click to expand...
Click to collapse
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
0.0 said:
do you have usb debugging on? its under development under settings. to make it appear, you need to press the about phone 7 times or so. http://www.androidcentral.com/how-enable-developer-settings-android-42
^^what the user said above. he beat me to it
Click to expand...
Click to collapse
While this was, admittedly, once my problem back in the early days of android, it's not the problem this time. USB debugging is on.
EDIT: I've also reconfirmed that fastboot is still working after the whole re-installation thing.
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
chinly43 said:
Anyone have any other ideas? Is it correct that when I plug the phone in, it's detected add an MTP device?
Click to expand...
Click to collapse
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
0.0 said:
thats very odd...perhaps run the android sdk and check for any updates for the drivers and whatever else is needed
Click to expand...
Click to collapse
That's all I can suggest as well, although I can't see what the issue could be
Yer try installing the SDK and downloading the "Google USB Drivers" from there to see if it helps.
Sent from my Nexus 4 using Tapatalk 2
Here try this. It's from the sdk. I just zipped it. https://www.box.com/shared/7sutkummukh4pup0rwoi
Sent from my Nexus 7 using Tapatalk 2
You can just get the windows executable from Google, r21
http://dl.google.com/android/installer_r21-windows.exe
Thanks, everyone who's been reading/trying to help. Unfortunately, it's still not working.
People suggesting the .exe installer - that's how I've installed it each time. Twice now I've uninstalled/reinstalled the SDK. When installing, I choose the SDK tools, SDK platform tools, the 4.2 API (which is probably unnecessary, right?), and the Google USB driver. Each time, ADB has worked *in general*, but will not recognize this device (via the "adb devices" command).
Here's how things are going right now. When I first plug the phone in (with debugging on), if it's not currently installed as a device then it automatically self-installs and shows up as an "mtp" device. I try ADB, doesn't work. I then go in and manually install the drivers found in various places around this board. When I do this, it no longer appears as MTP. This is weird, though, and I didn't notice this last night - when I look at the list of devices in Device Manager in Windows, the category it falls into is "ASUS Android Devices", under which it's listed as "Android Composite ADB Interface", and it still doesn't work.
Something seems wrong about it being listed as ASUS, though. I wonder if all these current difficulties are a result of the problems I had getting my Transformer Prime to work with ADB? If anyone sees anything above that looks like I'm doing something wrong, let me know; I think the next thing I'm going to try is doing this whole process on a fresh computer here at work that's never been exposed to android at all, see how that goes. I'll check back in after I do that.
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
EddyOS said:
Have you tried these drivers?...
http://forum.xda-developers.com/showthread.php?t=1992345
Click to expand...
Click to collapse
I have, and it still doesn't work on my laptop. However...
It's working! On a shared computed at work that had never had *anything* android-related installed before. Went through the same procedure I did on my own computer, so the problem is with my laptop, I guess. Which I'm more okay with than it being a problem with the phone. I guess I need to more thoroughly remove everything from the laptop, maybe?
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
chinly43 said:
An update:
I DO. NOT. UNDERSTAND. why this worked; I haven't changed the drivers or anything on the laptop itself. On a whim, I changed the device type on the N4 from "media device" to "PTP device" and suddenly ADB is recognizing it on the computer where it's never worked. Should I have expected that?
Click to expand...
Click to collapse
I have to do that to my Nexus 7 before ADB will recognize it, so you're not alone there.
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
I had the same problem, here's what you need to do. When you plug it in, change the settings from MTP to Camera for USB settings. I don't know why, but you need to do it.
dcarpenter85 said:
Just curious, what brand phone did you have before? If it was a samsung and you had all the samsung drivers and what not installed still, this could be causing the problem. My cousin couldn't get adb to recognize his device and we finally discovered the samsung software was conflicting in someway. He uninstalled it all and adb worked like a charm.
Click to expand...
Click to collapse
I've got four other android devices that all worked (simultaneously, at that): T-Mobile/HTC G1, Nook Color, T-Mobile/HTC G2, and an Asus Transformer Prime.
Hi, been lurking around here for a good while now....fantastic website website and I've learned so much but now I have an issue.
For what ever reason my nexus 7 will not boot, I can get into fastboot and have been following the guides to do a full factory restore through fastboot. Everything goes fine until is comes to "Sending System" then just.....stops. I have used the nexus toolkit and also the official sdk drivers and fastboot contained there. I only have an old laptop as my main pc for some reason does not recognise the nexus.
I have tried alternative USB cable too.
Does anyone have any other advice.
Also the device is complete stock no custom rom has been installed so no custom recovery available.
I really appreciate any help.
Cheers!
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Try a search, shouldn't be hard to find what others have done with Windows 8 difficulties...
singlemanriot said:
Okay well ive managed to get it back alive!
used a new laptop and usb cable and it all seems to be fine now!
Now back to my original issue...windows 8 is pissing me around and wont recognise the bloody thing!
Any ideas?
Click to expand...
Click to collapse
Go to Device Manager, show hidden devices and uninstall any Android or ADB related devices that you have. Disable USB debugging on your Nexus, then plug it into your PC and see if it's recognized. If it is, then re- enable USB debugging, then go to Device Manager and reinstall the Google USB drivers to get ADB support back.
Thanks for the advice, first thing I did was try searching....I have tried countless methods suggested but nothing works its like windows cant find the drivers. In the device manger its recognised but no diver installs no matter what I do. If I force the manual driver install it fails!? I have tried the Naked drivers, the SDK even making sure the media components of windows are installed properly
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
asylumxl said:
Hi guys.
Firstly, apologies if this is in the wrong section. If it is I'd appreciate if the moderators could move it to the correct place. Also apologies for the essay of a post.
Now, I recently purchased a Nexus 6P, which I think is an absolutely brilliant device. Despite this I would like to mess around with it behind the scenes (root, different ROMs etc). Firstly I'd like to edit build.prop.
As such as I have installed the Android SDK, installed the relevant things needed such as the USB drivers and platform tools. I've enabled USB debugging in the Developer Settings and ADB works fine when the phone is in normal mode. Booting in to fastboot mode also works.
Unfortunately, when I enter Recovery mode the phone disappears from ADB devices and from Device Manager on Windows. Strangely selecting the sideload option means the device shows up in both places, but I can't use the commands I want.
I've tried various official drivers, unofficial drivers and even edited the official drivers to add my hardware ID with no luck. Any help with this would be greatly appreciated. I'm somewhat new to modern Android so I may be missing something obvious.
Cheers for any help in advance!
Click to expand...
Click to collapse
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Gizmoe said:
So what is it exactly you are trying to do? Unlock the bootloader, or have you already done that and flashed custom recovery?
Click to expand...
Click to collapse
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
asylumxl said:
I've done that, I've been following various information from these forums. I just can't seem to do anything in recovery mode using ADB. Everything else works, but the phone disappears if I try and use ADB to do anything.
Click to expand...
Click to collapse
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Gizmoe said:
Try and updating USB drivers for your PC from manufacturer or mb company. I had problems with newer versions of Android on my pc and had to update my usb3.0 drivers. I got mine from a different company from the board i use but the same chipset. My 6p works in recovery with twrp using adb. But I use a usb3.0 port. The only driver for the phone I use is the one from the Android sdk. The Google driver.
Click to expand...
Click to collapse
I'll give that a go, that's the only thing I haven't tried so far. It's just bizarre it shows in every other mode. The device is there in the Device Manager under hidden, but doesn't actually show up as connected. Thanks .
Hi all,
I am trying to root my phone, following this guide: http://forum.xda-developers.com/nexus-6p/general/guides-how-to-guides-beginners-t3206928
However, I am stuck at entering 'fastboot devices' into the command prompt. It will not return my device's serial number. I know this is supposed to be becuase I don't have the correct drivers installed - but I'm pretty sure I do! I've spent hours scouring the internet for solutions and I can't find anything to help. So now I turn to you, please help me
I'm running windows 10.
I've double checked the google usb driver is installed.
I've manually installed the android bootloader interface driver.
The bootloader screen says on my phone says 'Connect USB data cable'. It is already connected and I have tried connecting it to all the ports on my laptop. I'm using the original cable that came with the phone.
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Eric214 said:
Well did you enable USB debugging? I'm assuming you did but you didn't list that in the process you said you did.
Click to expand...
Click to collapse
I did indeed. And I also fixed it! I just needed to do some more tinkering. I set the fastboot.exe to recommended defaults. Not sure why it was not already but there you go. You can lock or delete this thread now, thanks!
I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
jeffrimerman said:
I'm sure it's been asked a bunch. I read the discussion for Jan 15 but none of those helped. Anyone have this problem lately? Maybe something updated in the last few months so I need a different driver? It must be a simple driver issue. If someone has the right driver maybe I can specifically install it. I just want to turn the headphone volume up. The volume on most phones sucks out of the box.
Click to expand...
Click to collapse
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Scott said:
It usually is a driver issue. I assume you are on Windows 8.x or 10. If so go to Device Manager and find the QCOM device. I dont recall the full name of the device off my head. Once you find that go to the driver tab and then hit update drivers.
I do beleive that windows will pull down the latest drivers automagically.
Click to expand...
Click to collapse
What funny is just now I used the power button to go into bootloader then I plugged it into the computer to see what it's called in device manager and it recognized it. It wasn't QCOM device or anything phone related so not sure what it was called. I then unlocked the bootloader, but now when I'm back in the bootloader it does not recognize it again and the name is "unknown usb device(device description request failed)". So maybe it's not a driver issue if it recognized it. I had just updated the phone to the new 9.016 or something. Maybe I should reboot the phone and try again. I'll try to update the driver again but that's what I've done quite a few times.
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
jeffrimerman said:
Update:
I decided to boot right into bootloader again with the power butter option by enabling it in Developer Options and then plug into the pc and check with powershell and fastboot devices worked. The only thing different is that I can think of is I enabled developer options just before but not sure if that did anything. It worked either way so I loaded twrp and magisk and I'm rooted. I just want to change the headphone volume but still get updates later. I'll google to see if an unlocked bootloader will allow updates or maybe root will prevent it. If I unroot and relock as long as my headphones are loud then that's cool. Thank for the help guys.
Click to expand...
Click to collapse
You also have to enable usb debugging and OEM unlocking, if you want to unlock your bootloader.
Yes, sorry I didn't mention that because I've done it many times. I was just trying to think of what was different this time why the bootloader was recognized in case someone reads this in the future and is trying everything. Maybe it was the factory reset, maybe it was enabling developer options immediately before who knows. I did nothing different with the computer or the usb debugging and oem unlocking. The first time bootloader was recognized I literally didn't do a darn thing. I used to have a phone that I could only use the wifi hotspot if I rebooted the phone and immediately signed on with my laptop. A few seconds too long and it wouldn't work.