How to Fix "ADB Device Offline" Error on Windows

There is a specific frustration reserved for when adb devices shows your phone in the list — so it is definitely detected — but the status column reads offline instead of device. Commands fail, installs fail, and nothing seems to work. This guide explains exactly why it happens and how to fix it.

The offline status is distinct from both unauthorized and no device at all. It means ADB is aware of the physical device but the communication transport is in a broken state. This is typically a temporary condition that can be resolved without rebooting your phone in most cases.

Understanding the Offline State

ADB maintains a persistent connection to each device through its server process. When that connection breaks mid-session — due to a USB interruption, a system sleep/wake cycle, a driver reset, or an ADB server crash — the device can remain listed in the device registry with an offline status. The entry is essentially a stale record from a previously active connection.

Fix 1: Restart the ADB Server

This is the first thing to try and resolves the offline state in the majority of cases. Killing and restarting the ADB server clears all stale device records and forces a fresh discovery cycle:

adb kill-server && adb start-server

After running this, disconnect the USB cable, wait a few seconds, then reconnect it. Run adb devices again. In many cases the device will now show as device (possibly after accepting an authorization prompt if the server restart invalidated the session).

Fix 2: Reconnect the USB Cable

Simply disconnecting and reconnecting the cable — without restarting the ADB server — can sometimes resolve the offline state on its own. This is worth trying before the more involved steps:

1. Unplug the USB cable from your PC (not from the phone).
2. Wait 5–10 seconds.
3. Plug it back into a different USB port if possible, especially a USB 3.0 port directly on the motherboard.
4. Make sure your phone screen is unlocked when you reconnect.
5. Run adb devices.

Fix 3: Restart the Android Device

If the ADB server restart and cable reconnect do not fix the offline status, the issue may be on the device side — specifically, the ADB daemon (adbd) running on Android may have crashed or entered a bad state.

If you have just enough ADB connectivity to run a command (sometimes offline devices still accept basic commands), you can try restarting adbd on the device without a full reboot:

adb reconnect

Or attempt to restart the device's ADB daemon directly:

adb shell stop adbd
adb shell start adbd

If those commands fail due to the offline state, a full device reboot is needed:

1. Reboot your Android device normally (hold power button > Restart).
2. Once it fully boots and you have unlocked it, reconnect the USB cable.
3. Accept the USB debugging authorization dialog if it appears.
4. Run adb devices.

Fix 4: Disable and Re-enable USB Debugging

Toggling USB Debugging off and on again forces the Android ADB daemon to reinitialize, which can resolve a stuck offline state caused by daemon-level issues:

1. On your Android device, go to Settings > System > Developer Options.
2. Toggle USB Debugging off.
3. Wait 5 seconds, then toggle it back on.
4. Disconnect and reconnect the USB cable.
5. Accept the authorization dialog if it appears.

Fix 5: Update or Reinstall USB Drivers

Outdated or corrupted USB drivers can cause instability that manifests as intermittent offline states, especially after Windows updates. The device may connect fine initially but drop to offline after a few minutes or after the PC wakes from sleep.

1. Open Device Manager (right-click Start > Device Manager).
2. Expand Android Device or Portable Devices.
3. Right-click your phone and select Uninstall Device. Check the box to delete the driver software if it appears.
4. Disconnect the USB cable.
5. Download the latest USB driver for your phone's manufacturer:
   • Samsung: via Samsung Smart Switch
   • Google Pixel: Google USB Driver from developer.android.com
   • Xiaomi: Mi PC Suite USB driver
   • OnePlus: OnePlus USB Driver
6. Install the driver, then reconnect your phone.

Fix 6: Try a Different USB Port or Cable

USB hubs, front-panel ports, and low-quality cables can all cause intermittent connection drops that produce the offline state. This is especially common when the connection is made through a USB-C to USB-A adapter or a longer cable:

• Try connecting directly to a USB port on your motherboard (usually on the back of a desktop).
• Avoid USB 3.0 hubs — some of them cause ADB instability on certain devices.
• Use the original cable that came with your phone. Third-party cables vary significantly in quality.
• If using USB-C, try both orientations of the connector.

Fix 7: Check for ADB Version Conflicts

If you have multiple ADB versions installed (Android Studio, standalone platform-tools, and third-party apps all bundle their own ADB), they can conflict and cause offline states as each tries to talk to the same device through different server instances:

# Find all adb binaries on your system
where adb

# Check the version in use
adb version

If where adb returns more than one path, consolidate to a single ADB installation. Set the PATH to point only to the one you want to use and kill any running ADB processes before starting fresh.

Wireless ADB Offline

If you are using wireless ADB (ADB over TCP/IP) and the device shows as offline, the cause is almost always a changed IP address or a dropped network connection. Reconnect explicitly:

# First disconnect the stale entry
adb disconnect 192.168.1.100:5555

# Then reconnect with the current IP
adb connect 192.168.1.100:5555

If you do not know your device's current IP, connect via USB, run adb shell ip route, note the IP, then switch to wireless mode.

Conclusion

The ADB offline state is almost always temporary and fixable without a full device reboot. The fastest resolution is adb kill-server && adb start-server followed by a cable reconnect. If that does not work, check your USB driver, try a different port or cable, and disable/re-enable USB Debugging. For persistent offline issues, a driver reinstall or checking for conflicting ADB installations is usually the final answer.

If you want reliable Android device management without babysitting ADB, Andora handles connection state automatically and reconnects cleanly when devices drop. See also our guide on fixing ADB device not found if your device is not showing up at all.