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.
Just a quick question that's puzzling me.
I installed the latest OTA update, re-rooted, and wiped my phone. (It's stock besides root.) Everything is functioning fine on the device. However, when I connect to my Windows 7 PC, the phone will connect for a brief moment, and then disconnect. I tried different cables and none make a difference, but when I disabled USB debugging, the phone stays connected without any issues. I do have the latest Motorola USB drivers/device manager installed.
Any idea what could be causing this? Thanks.
I am having a similar issue. I get the same problem when in Linux (my primary OS). However, I was surprised to find out the issue does not exist when booted into Win8.
I would like to find a solution though. Kind of a drag to boot up into windows just for a couple ADB commands.
Sent from my XT907 using xda premium
Since my Moto X already received its KitKat OTA, I finally got impatient tonight (and had a little free time) so I decided to sideload KK onto my stock/unrooted Nexus 10. Unfortunately, this has not turned out well for me.
Since I received the previous OTAs so quickly, I never setup ABD/Drivers/etc. for the N10. After fumbling through that (missing hardware ID in .inf file, etc.) I'm finally to the point where everything looks like it should work. ADB recognizes my device in recovery mode, various ADB commands seem to work without issue, and so on. However, when I fire off the adb sideload KitKat.zip command, all I see on my PC is:
sending: 'KitKat.zip' 1%
On my N10, nothing changes. All I see is the normal:
Now send the package you want to apply
to the device with "adb sideload <filename>" ...
I've rebooted both my PC and my N10 at least a dozen times. I've tried switching back and forth between the Google USB drivers and Koush's universal drivers, but the behavior is always the same.
I've done a bit of googling on this issue without any luck. Anybody have any pointers beyond just being patient for the OTA?
This may sound crazy, but try another USB cable. I had the same exact problem. And since adb recognized it and it charged fine when plugged into my PC, I thought it couldn't be the cable. I tried everything including koush's universal adb drivers as well as 2 other PC's with no luck. But I tried a different USB cable and it worked fine.
Same problem...
I have exactly the same problem here with a Samsung Galaxy SII. It's just stuck at 1%. Tried with another USB cable with no luck. Have you sorted out what the problem was? Tnx!
TWRP or CWM? Also, you could try the adb push command and push it to the internal storage and install it from there.
Sent from my Nexus 10 using XDA Premium 4 mobile app
Alternative to sideload...
anthony2424 said:
TWRP or CWM? Also, you could try the adb push command and push it to the internal storage and install it from there.
Click to expand...
Click to collapse
Solved!
Tried everything to get this sideload to work, without success. In the end, I flashed it through Heimdall. Not one of my favorite ways to flash but hey, phone works like a charm again :good:
For some reason, I can no longer get any computer to recognize my Nexus 4 when connected by USB. I can charge but cannot get the phone recognized.
A couple weeks ago, everything was working fine. I was running Cataclysm (November build based on 4.3). I upgraded to the Nexus 5 and decided to give the Nexus 4 to my daughter. I was able to connect the Nexus 4 to the computer and move all my photos and music etc off of the phone. After moving my files off and doing a Titanium backup and Nandroid just in case, I did a complete wipe on CMW (6.0.3.5). Everything fired up fine and I had no reason at the time to test the USB.
However, last week, my daughter was complaining about bad battery life and I decided to take a look and go ahead and update the phone to the latest (Dec. 12) Cataclysm build based on 4.4.2. Before flashing the new build, I connected the phone to the computer by USB but could not get the computer to recognize the phone. The phone charges, but is not recognized in device manager and does not connect.
I've done everything I can think of to troubleshoot the issue - all without luck - including:
Turned USB debugging on and off. No luck.
Changed the USB storage mode from MTP to PTP and back. No luck.
Confirmed fast charging isn't somehow enabled. It isn't.
Tried several different USB cables. No luck.
Tried a different Nexus 4 and my Nexus 5 on the same computer. They work.
Tried the subject phone on a different computer running Windows. No luck.
Tried the subject phone on a computer running Mac OS. No luck.
I did go ahead and flash the latest Cataclsym build (I did a full wipe again) but sill no change. I don't see any evidence of physical damage to the micro USB port but I took a small toothrush and gently cleaned the contacts with rubbing alcohol.
At this point, I believe the problem is either the a) the port is bad or b) somehow, the phone software/ROM is screwed up.
Is there any way to determine whether the physical port is bad? Any other ideas. I'm kind of at the end of my capability here.
can adb recognize it?
Code:
adb devices
Riro Zizo said:
can adb recognize it?
Code:
adb devices
Click to expand...
Click to collapse
I don't think so. I'll have to check tonight when I get home. I tried to get Wug's toolkit to recognize the phone with no luck but haven't tried that command on its own.
Riro Zizo said:
can adb recognize it?
Code:
adb devices
Click to expand...
Click to collapse
No luck. I attached the Nexus 4 to the computer, entered a command prompt to navigate to the platform tools director that has the adb files and entered the "adb devices" command. The response was "List of devices attached" with no phone (or anything else) listed.
I have that issue too. I´m on windows 8 and to root and being able to recognize by the pc I changed it to PTP. It only works in PTP and I have to pass all the data to the camera folder to send info
Gildegan said:
I have that issue too. I´m on windows 8 and to root and being able to recognize by the pc I changed it to PTP. It only works in PTP and I have to pass all the data to the camera folder to send info
Click to expand...
Click to collapse
I don't think I've got the same issue. I cannot get any computer to recognize the phone under any mode (storage, photo, debugging on, debugging off). Nada. At this point, I'm pretty sure it's the port gone bad. I just wiped the phone again and clean flashed the stock 4.4.2 ROM, radio and bootloader. Still no connection.
Argh.
SHPhone said:
I don't think I've got the same issue. I cannot get any computer to recognize the phone under any mode (storage, photo, debugging on, debugging off). Nada. At this point, I'm pretty sure it's the port gone bad. I just wiped the phone again and clean flashed the stock 4.4.2 ROM, radio and bootloader. Still no connection.
Argh.
Click to expand...
Click to collapse
can you try going to recovery, then type adb devices?
Sent from my Nexus 4
I had this problem and i found away to fix it. Plugin your phone to a computer. Start > right click on my computer > properties > device manager. Look for Samsung > expanded it you will find Nexus 4. Right click on it and choose uninstall and check uninstall driver. Unplug your phone and restart the computer. Re-plug the phone and wait for the drivers to install.
Sent from my Nexus 4 using Tapatalk
Guys just bought a new phone and started debugging on the phone. I'm facing this issue.
While I'm trying to debug the apps on my device. My device is showing as offline after sometime. Then I again have to Toggle off USB Debugging and switch it on. I even checked adb devices it shows the device as online and then offline after sometime. Anyone facing similar issues or knows the solution please help me with the same.
Thanks
I solved this by changing the usb cable and updating the usb drivers of my phone, give it a try
dont think so.
Hey thanks for the reply. The USB cable is brand new and of very good quality. Also ADB drivers are installed properly. It works once I toggle the USB Debugging in the phone so I dont think it would be related to the data cable.
mohamedrashad said:
I solved this by changing the usb cable and updating the usb drivers of my phone, give it a try
Click to expand...
Click to collapse
Maybe the rom if you are using a custom one
The debug bridge will never go "offline" as long as it is connected to the device, and as long as you have USB-debugging "on" in your device and the correct drivers are installed. The point being that ADB isn't the issue, I assume that you are debugging/logging through LogCat , "and that piece of shi* really sucks," if LogCat stops logging or says it is disconnected try to rearm it by manually launching the app you're debugging, or Run the app from your IDE. That will work most of the times, alternatively you can use the old Android logcat which is fully functioning but not as good as LogCat.
If all fails start debugging through ADB in the console.
same problem here, ..
showing adb device offline :?