Android Phone Not Recognized by Windows: 10 Fixes

Windows failing to recognize an Android device is one of the most common frustrations when setting up ADB, using ODIN, or simply transferring files. These 10 fixes address the specific causes in order of likelihood, so you can stop as soon as the device appears.

Fix 1: Check the USB Connection Mode on the Phone

The most common reason a phone is not detected is that the phone itself is set to "Charging only" mode after being connected. Swipe down the notification shade and look for a USB connection notification. Tap it and change the mode to "File Transfer" (MTP) or "USB Tethering." Some Samsung devices require "MTP" to be selected explicitly before the driver can bind.

On Android 9 and above, you can also find this setting under Settings > Connected devices > USB preferences.

Fix 2: Try a Different USB Cable

Charge-only cables lack the data wires needed for ADB or MTP communication. If you are using a cable that came with a cheap wall charger, it may be data-capable on the charger side but wired only for power. Test with a known-good data cable, ideally the one that shipped with the phone.

Even data-capable cables can develop intermittent failures at the connector. Try wiggling the cable at both ends while the device is plugged in. If Device Manager briefly shows then hides the device, the cable has a physical fault.

Fix 3: Try a Different USB Port

USB ports on a PC can fail individually. USB 3.0 ports (usually the blue ones) sometimes have compatibility issues with certain Android devices during initial enumeration. Try a USB 2.0 port first. On a laptop, also try plugging directly into the chassis rather than through a USB hub, as hubs introduce additional power and signal issues.

Fix 4: Install or Reinstall the USB Driver

Open Device Manager (Win + X > Device Manager). Look for any entry under "Other devices" or "Universal Serial Bus devices" with a yellow warning triangle. This indicates Windows loaded a generic or incorrect driver. Right-click the entry, select "Update driver," then "Search automatically." If that fails, download the manufacturer-specific driver:

• Samsung: Samsung USB Driver for Mobile Phones (Samsung developer portal)
• Google Pixel: Google USB Driver (Android Studio SDK Manager > SDK Tools)
• All other brands: Google's universal USB driver often works; alternatively check the manufacturer's official support downloads

Fix 5: Restart the ADB Server

If the phone appears in Device Manager but ADB still shows no devices or an "offline" state, the ADB host daemon may be in a bad state. Fix this by restarting it:

adb kill-server
adb start-server
adb devices

This kills and restarts the background daemon that manages the ADB connection. It is harmless and only takes a few seconds.

Fix 6: Revoke and Re-authorize USB Debugging

If you previously connected the phone to a different computer, or if the authorization key has somehow become corrupted, revoke all trusted computers and re-authorize. Go to Settings > Developer Options > Revoke USB debugging authorizations. Then reconnect the phone and tap Allow when the authorization dialog appears on screen.

Fix 7: Check Developer Options and USB Debugging

USB debugging is disabled by default and resets on some devices after a factory reset or major OS update. Verify it is still enabled: Settings > Developer Options > USB Debugging should be toggled on. On Samsung devices, also check that "USB Debugging (Security settings)" is not blocking the connection if you are on a corporate-enrolled device.

Fix 8: Uninstall Conflicting Drivers

Third-party "phone manager" applications such as older versions of MobileGo, Phone Manager, or Kies sometimes install their own USB filter drivers that conflict with direct ADB access. Uninstall these applications via Add or Remove Programs, then use Device Manager to uninstall any remaining device entries for the phone. Reconnect and let Windows use the correct driver.

Fix 9: Update or Roll Back Windows USB Drivers

A Windows Update can occasionally push a USB hub or controller driver update that breaks device enumeration. In Device Manager, expand "Universal Serial Bus controllers" and check the dates on the USB root hub and USB host controller entries. If they changed recently and coincide with when the problem started, right-click each one and select "Update driver" or try "Roll back driver" to the previous version.

Fix 10: Test on Another Computer

If none of the above fixes work, connect the phone to a different Windows PC or to a Linux machine. If it is recognized there, the problem is specific to your Windows installation. Common causes at this point include corrupted USB driver stack entries in the Windows registry or a disabled USB selective suspend policy. If the phone is not recognized anywhere, the USB port on the phone itself may be damaged and the phone may need hardware service.