How to Fix adb Device Offline Without Replugging the Phone Ten Times and Pretending That Is a Workflow

Why this keeps returning: adb device offline is usually not one dramatic Android failure. It is the host and device losing trust, transport stability, or a clean server session.

You run:

adb devices

and see:

abcdef123456    offline

Step 1: restart the adb server cleanly

adb kill-server
adb start-server
adb devices

This clears a surprising number of transient states.

Step 2: reset USB debugging authorization on the phone

On Android:

1. open Developer options
2. tap Revoke USB debugging authorizations
3. disconnect and reconnect the device
4. accept the host fingerprint again

If you never get the trust prompt again, the issue is not solved yet.

Step 3: check USB mode and cable quality

Charging-only mode and low-quality cables cause nonsense errors that look like adb problems.

Prefer:

1. file transfer or similar data mode
2. a cable known to carry data
3. a direct port instead of a flaky hub

Step 4: inspect the device state again

adb devices -l

If the device still shows offline, remove stale adb keys on the host:

rm -f ~/.android/adbkey ~/.android/adbkey.pub
adb kill-server
adb start-server
adb devices

Then reconnect and accept the trust dialog again.

Wireless debugging note

If you are using adb over TCP/IP, stale pairing or network changes can produce the same symptom. Re-pair if needed rather than assuming USB-only fixes apply.

Verification checklist

adb devices -l
adb shell getprop ro.product.model

You want the device listed as device, not offline, and a shell command that returns normally.

Bottom line

adb device offline is usually a broken trust or transport session, not a mysterious Android curse. Restart the server, reset authorization, and make sure the cable and USB mode are not undermining you before touching more exotic fixes.

Sources

• Android Debug Bridge documentation
• Android developer options documentation