If a USB-C connection charges but carries no data, the power conductors are working well enough to deliver some power; that does not prove the cable has working data conductors, the port supports the requested data mode, or the device has successfully enumerated. Diagnose the chain in a fixed order: identify the missing function, connect directly, substitute one known-good component at a time, and check the operating system only after the physical path is controlled.
Start with the exact missing function
“No data” can describe several different failures. A phone may charge but never appear in a file browser. An external drive may enumerate but negotiate a slower link than expected. A dock may pass keyboard data while its display output stays dark. Those symptoms do not share one automatic cause, so the first useful step is to name what works and what does not.
| What you observe | What it establishes | Best next comparison |
|---|---|---|
| The device charges, but never appears to the host | A usable power path exists; USB enumeration has not been confirmed | Use a known-good data cable and a second host port with the same device |
| The device appears, but transfers only at a low data rate | Basic data works; the intended high-speed path has not been established | Keep the endpoints fixed and compare a cable declared for the required USB data mode |
| File transfer works, but a display does not | USB data support does not prove DisplayPort Alternate Mode or video support | Check the exact host port, cable and display path for the same video feature |
| The connection changes when one plug is reversed | The symptom follows orientation or one connector interface | Cleanly retest both ends; inspect for damage or debris and stop using a damaged plug |
| The cable works with one device but not another | The cable is not automatically cleared or condemned | Compare the required feature set of both endpoint combinations |
The matrix is a routing tool, not a verdict. It keeps a charging icon from becoming false proof that every USB-C function is present. It also prevents an unsuccessful video test from being treated as a generic data-cable failure when the actual gap may be Alternate Mode support in the host port or cable.
Why charging can work when data does not
USB-C combines several functions in one reversible connector. VBUS and ground carry power. Configuration-channel contacts help the ports detect attachment and roles. USB 2.0 data uses its own conductors, while higher-speed USB and optional display modes rely on additional signal pairs and compatible electronics throughout the link. These paths cooperate, but they are not interchangeable.
A cable built for charging can therefore omit high-speed capability, and a damaged or poorly terminated data path can fail while power remains available. The reverse is also possible: data may operate while charging is limited by the source, cable current capability, device policy or negotiated power. Connector shape is only the starting point.
Signal construction matters more as the requested data rate rises. Shielding, pair geometry, connector termination and cable length all influence signal integrity. The USB-C cable shielding explainer shows why a cable that looks normal from the outside can behave differently at higher data rates. Shielding alone is not a certification, but it is part of the physical design that charging-only comparisons miss.
Use a direct, controlled substitution test
Remove docks, extension leads and adapters unless one of them is the item being tested. Connect the device directly to the host. Record the exact port, cable and device, because “the USB-C port” may hide different capabilities on the same computer. Then change only one variable per test.
- Confirm the device: use the same device and its normal data mode. Unlock a phone and select file transfer if the device requires that choice.
- Confirm the reference cable: use a short, known-good cable that has already transferred data between known-good endpoints. A cable that has only charged a device is not a data reference.
- Confirm the port: keep the device and reference cable fixed and try another port that is documented for USB data.
- Confirm the host: if practical, test the same device and reference cable on another computer or controller.
- Return to the suspect cable: once both endpoints have passed, replace only the reference cable with the suspect one.
This sequence creates evidence. If the failure follows one cable across two working endpoint combinations, the cable becomes the leading suspect. If every cable fails on one port, investigate the port and host. If one device fails everywhere, investigate that device and its settings.
Classify the failure before choosing a fix
No device appears at all
Look first for a charging-only cable, a data-disabled accessory, contamination, connector damage or a device mode that blocks data. On phones and cameras, the device may require unlocking or an explicit transfer mode. On computers, the operating system may report an unrecognized USB device when enumeration begins but cannot complete.
USB 2.0 works, but the expected high-speed transfer does not
Basic enumeration proves that some data conductors and software layers work; it does not prove the SuperSpeed lanes are present or healthy. Verify the declared data capability of the cable and both endpoints. Compare like-for-like files and storage devices, because drive performance and caching can hide the actual link rate.
Data works, but video does not
Ordinary USB data and display output are separate feature claims. The host port must support the required display mode, the cable must carry the necessary high-speed signals, and every dock or adapter must support the intended resolution and refresh combination. Test a direct display path at a conservative supported mode before adding a dock.
The symptom depends on plug orientation
A reversible connector should provide its supported function in either orientation. Orientation-dependent behavior can point to contamination, wear, damage, a connector or cable fault, or an endpoint implementation problem. Inspect without inserting tools into a powered port. Retire a cable with a deformed shell, loose plug, exposed conductors or abnormal heat.
Do not confuse charging wattage with data capability
Power and data labels answer different questions. A cable advertised for a high charging wattage may be designed mainly for power and USB 2.0 data. A high-speed data cable may support less charging current than another cable. A Thunderbolt, USB4, DisplayPort or other logo is meaningful only when it is authentic and applies to the exact product.
For a useful comparison, write four requirements separately: connector arrangement, charging power or current, USB data mode, and any display or tunnelling feature. Add cable length and target devices. That short requirement prevents the familiar mistake of buying by wattage and discovering later that the intended data function was never specified.
When software and device settings become the main suspect
Move to software only after the physical comparison path is known. Check whether the operating system sees an unknown or disabled device, whether a driver or system update is pending, and whether security policy blocks removable storage. Restarting can clear a transient state, but it is not evidence that the cable was good or bad.
On Windows, connection notifications and Device Manager can help distinguish “nothing attached” from “enumeration attempted but failed.” On other platforms, use the equivalent system information tool. If the device appears there but not in an application, the USB link may already be working and the remaining problem may be a filesystem, permission, driver or application issue.
When to replace the cable
Replace or quarantine the cable when the failure repeatedly follows it between known-good ports and devices, when its declared specification does not include the required function, or when the connector is damaged or becomes unusually hot. Do not open a molded cable or probe powered contacts as a consumer troubleshooting step.
If the failure is intermittent, record the exact motion or orientation that triggers it and stop flexing the assembly once damage is suspected. Intermittent conductors can create repeated disconnects and corrupted transfers even though a charging icon remains visible.
A better USB-C cable requirement
- Connector type and gender at both ends
- Required charging power, current and USB Power Delivery range
- Required USB data mode and minimum verified transfer function
- Required display or other Alternate Mode, if any
- Cable length, flexibility, shielding and environmental constraints
- Target host, dock and device combinations
- Evidence expected for the declared capability, including applicable certification or test documentation
After those requirements are fixed, compare exact models in ChargeKeku’s USB-C to USB-C cable category. The category is a starting route, not a claim that every listed cable supports the same power, data or display features.