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
Related
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'?
I have installed android sdk but I cant get it to recognize my nook touch. Thought it was a usb driver problem,but device manager shows that the driver is up to date. Any suggestions?
I am ultimately trying to remove the cell standby that is using up so much battery
connect with wifi. Just use the Ip for your nook on the network and connect that way.
adb connect 192.168.x.x
then you can push pull shell etc...
klong81506 said:
I have installed android sdk but I cant get it to recognize my nook touch. Thought it was a usb driver problem,but device manager shows that the driver is up to date. Any suggestions?
I am ultimately trying to remove the cell standby that is using up so much battery
Click to expand...
Click to collapse
Well I don't think anyone has posted on here how to ADB through USB, but with WiFi I connected after installing adb. Then I went "adb connect <your.ip.address.right.here>:5555"
How do you get rid of the cell standby service through adb?
Edit: Also, if you plan on removing, renaming "Phone.apk" and "TelephonyProvider.apk" nothing will happen, according to majority in this thread:
http://forum.xda-developers.com/showthread.php?t=888216
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.
I can't for the life of get adb to see my g2 on my mac. I've had adb detect other phones in the past. I have USB Debugging on. I connect the phone through 'Ethernet' It starts the daemon and then says List of devices and it's blank. It must be something so little that I'm missing. I've rooted via adb before on my mac with other phones so I'm pretty sure it works. Anybody have any suggestions?
not to sure about mac but on my pc only 2 out of 5 ports have adb. try a different port. not sure if that will work with mac
Hi all,
so i have got android installed on my switch but cannot seem to get the usb to work at all for ADB and MTP.
the switch does not show anything when it is connected by usb and it does not appear in device manager or adb on the host machine.
i have enabled developer mode and debug over USB.
i have tried to connect to ADB via the network but this lead to the authentication failing
does anyone have any ideas of what could be the issue?
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Laurin Neff said:
I looked at lsusb on my Linux machine and it shows as a USB serial device, so I looked at the serial terminal and it doesn't print anything, so I guess you won't get USB to work, but you might be able to get WiFi adb to work but I haven't
Click to expand...
Click to collapse
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Roy8765 said:
Thank you that is greatly important stuff to know.
The issues I am having with ADB over network is that it requires the device to be trusted which first needs to be done over USB.
It could be done using root but I can not seem to enable root on this version of Android.
Click to expand...
Click to collapse
Just flash magisk, it's what I did and now I have root.