I can't for the life of me connect to my TP2 running XDANDROID via ADB.
Here's what I've tried
-Connect via Linux in a VM(Ubuntu)
-Connect via Linux (for real, also Ubuntu)
-Connect via Windows.
The problem is the connection to the phone. In Linux, the USB0 network connection does show up, but when I try to connect to it, it fails everytime without any specific error message.
On Windows, I managed to install the Android SDK USB driver, but once again ADB can't seem to connect.
The error message is the same on both platforms btw. When I try to run adb shell, it starts the Daemon and then quits saying that there is no device to be found.
The phone itself indicates it's in USB debugging mode and the USB cable is connected.
What could I be doing wrong?
Whoops, wrong subforum. Could a mod please move this to 'Software and Hacking General'?
Related
I've had ADB working successfully in the past, but now nothing is listed after an "adb devices" command, and a "device not found" error for other commands. I was on Royal Ginger 2, and just updated to the latest CM7 nightly - then wanted to use ADB to tweak a few things and found out something was wrong. What else do I need to do to get adb to recognize my device?
I haven't changed anything on my laptop, which is Win7 64bit, and I've updated everything in SDK Manager. Device Manager on the laptop shows T-Mobile myTouch4g USB Device under Disk drives on the Device Manager, and I believe I have the latest mt4g drivers installed. I'm connecting via USB with debugging turned on, and without turning on USB storage.
Any ideas?
I was finally able to get adb to recognize my device again. FYI, I tried a few different things, but I think what finally got it working was tweaking the *.inf file in the usb_driver folder in SDK, the uninstalling/reinstalling the drivers - as outlined here:
http://forum.xda-developers.com/archive/index.php/t-881324.html
I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
lablunk said:
I have searched extensively to no end. When I ./adb devices in terminal, it lists my phone but says 'unauthorized.'
I do not get a prompt on my phone to authorize its connection to osx.
I have rest phone to factory spec. Still nothing.
Thoughts?
Click to expand...
Click to collapse
I had this issue on a stock rom with ADB in Windows and in Linux. This apparently is a known "issue" with the stock rom when the USB mode is set to MTP.
The "fix" is to make sure you are in Network mode (either Internet or Modem is fine). You might have to disconnect and re-connect the USB cable a couple times (and re-select the Nework mode) before it will actually connect with ADB. If it pops up with the ADB Verify Server Fingerprint window on the phone, you have sucessfully made an ADB connection.
Hello,
Im trying to connect my G5 Plus over ADB interface driver to my Windows computer for use with PDAnet. When I enable USB debugging and connect the phone to the laptop via USB cable, the driver fails to install. It says "Moto G5 Plus" with an exclamation mark next to it.
I have tried manually installing Google's universal ADB driver and this does not work as well. The phone then shows up as "Android ADB Interface" but it fails to work with the application on the computer. PDAnet says "Wrong Winusb pipes found" when I try to start the internet connection.
How can I get the phone talking to my computer over the ADB interface? Is there a driver out there I am missing?
Thanks!
I cant tell what im doing wrong, ive never had this much of a headache using ADB.
For the life of me i cannot connect to my device to run commands.
I can see the device and the serial, but its forcing me to connect over tcpip, and every time I put in the correct IP and port 5037 and it refuses to connect.
Device will authorize my PC, but that is it, and ADB will not run in USB mode and keeps asking me for the IP, which I can ping, but it wont connect.
Please help
What commands are you wanting to run?
And you are using the most recent USB drivers?
It sounds like the correct comm port is being used, as you get basic recognition, but I'd check anyway. Try a different USB port, maybe different PC.
Let us know.
Did you try adb kill-server then adb start-server?
I had an app I was trying to give privileges to, figured I couldn't but wanted to try anyway. That part kinda doesn't matter though because I cant get far enough.
I do have the latest drivers installed, tried 3 different ports but not a different pc.
I killed and restarted the server in USB mode, but then it says no devices connected and the phone disconnects and reconnects each time, and adb restarts in tcp/IP when it doesn't detect the phone
I had previously connected my Asus X00TD to my laptop for transferring files. The phone doesn't connect to PC from yesterday. Only charging happens after connection, and device doesn't show up on the device manager(no change on list of devices after connection), and no notification sound of device being connected either. There is no notification in my phone as well. Here are the following workarounds I have tried, but failed:
Changing USB cable
Changing PC/laptop
Installing ADB and Qualcomm drivers and again uninstalling them(error code 10 on ADB Driver)
enabling and disabling USB debugging
changing connection mode(nothing works)
Going into safe mode
restarting and connecting multiple times
Kindly help me if possible, and your help will be kindly appreciated
I had a similar problem recently. What ended up working for me was to install some generic Android driver published by Google. I already had the ADB package installed, but without the generic Android driver published by Google, my phone could charge and transfer files, but I could not issue ADB commands through the Windows command prompt.
The package I needed was called "usb_driver_r13-windows.zip"