Why half your USB cables are 'charge-only' (and how to prove it in 10 seconds)

Heads up: some links in this article are affiliate links. If you buy through them I may earn a small commission at no extra cost to you. As an Amazon Associate I earn from qualifying purchases. I only recommend gear I'd run myself.

You plug a device in to flash firmware, or mount it, or pull data off it — and nothing happens. It charges. The light comes on. But the computer never sees it. You swap ports, reinstall drivers, reboot, and lose forty minutes. The cable was the problem the whole time, and it wasn’t even faulty. It was charge-only — built with the data lines missing on purpose.

Once you know this exists, you stop losing those forty minutes. Here’s the why and the how.

A USB cable has four wires, and cheap ones skip two

A basic USB 2.0 cable carries four conductors:

  • VBUS — +5V power
  • GND — ground
  • D+ and D− — the differential pair that carries data

Charging needs only VBUS and GND. Data needs D+ and D−. So a manufacturer shipping a cable in a product box — the one that comes with a battery pack, a fan, a set of headphones — can save a fraction of a cent by simply not connecting the two data wires. It still charges perfectly. It will never sync anything. It looks identical to a good cable from the outside, and it ends up in your drawer next to the real ones.

This isn’t rare or malicious. It’s most of the freebie cables ever made. USB-C muddies it further: a cable can carry data but not enough power for fast charging, or power but only USB 2.0 data speeds, or be a full high-speed cable — all in the same connector shell, with nothing printed on it.

How to prove it — three ways, cheapest first

1. The device-manager test (free, 10 seconds). Plug the cable into a device that should enumerate — a phone, an Arduino, a flash drive. If it charges but never appears in your OS’s device list, and a known-good cable makes it appear, the cable is charge-only. This catches the common case instantly.

2. The multimeter continuity test (a couple of minutes). With a breakout or a steady hand on the pins, check continuity from D+ to D+ and D− to D− end to end. No beep means the data lines aren’t connected. A multimeter is the single most useful tool on a homelab bench for exactly this kind of “is this thing actually connected” question.

Auto-ranging, true-RMS, with a continuity beep — the tool I reach for first when a cable is suspect.

The multimeter I use (FNIRSI DMT-99) ↗

3. A dedicated cable tester (instant, no thinking). If you deal with cables often, a tester with an LED per conductor tells you at a glance which wires are live — charge-only cables light two LEDs, data cables light four. I built one from a cheap kit and it now lives next to the cable drawer. It also catches the other silent killer: a cable that has all four wires but one is broken near the connector, so it works until you move it.

Tests USB-A/C, Micro, Mini, Lightning and RJ45 — one LED per conductor.

The 9-in-1 USB cable tester kit ↗

The habit that saves the hours

Sort the drawer once. Test every cable, and physically separate the charge-only ones — a dab of paint on the connector, a different bin, whatever you’ll remember. From then on, when a device won’t enumerate, the cable is no longer a variable, because every cable you own is known-good and known-labeled.

It’s a small thing. It’s also the difference between “my board is bricked” and “oh, wrong cable” — a diagnosis that should take ten seconds and, without a tested drawer, routinely eats an afternoon.