1

adb sometimes won't connect. I get this behaviour. What's going on?

$> adb kill-server
[ user@host ] ~
$> adb connect 192.168.3.160:5556
* daemon not running. starting it now on port 5037 *
* daemon started successfully *
connected to 192.168.3.160:5556
[ user@host ] ~
$> adb shell
error: device offline
[ user@host ] ~
$> adb connect 192.168.3.160:5556
already connected to 192.168.3.160:5556
[ user@host ] ~
$> adb shell
error: device offline

(Note: It also occurs with adb using port 5555)

1 Answer 1

2

I would write this as a comment but I can't. It may be because of the cable. I had this problem with an old cable that kept disconnecting my phone. Even cables that look fine may do this. The problem went away after I bought a new cable.

2
  • This was my problem. It's very strange, because the cable that doesn't work can still charge the phone just fine.
    – Teekin
    Mar 26, 2019 at 15:24
  • I don't think it's my problem though because I have the same problem with many different cables.
    – JohnyTex
    Apr 1, 2019 at 9:34

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .