Android charges over USB but cannot transfer files to Windows
Check USB mode and a known-good data cable. Cross-tests distinguish cable, PC port, and phone without installing unknown MTP driver packages.
Try this first
1 quick checks · ~5 min
Find your situation
See all the clues. Choose the one that matches what you observe.
The USB notification appears
Select file transfer and check whether files become accessible.
It only charges or the option is missing
Try a cable known to transfer data.
Another port or PC works
The difference directs investigation to the first computer’s connection path.
Different cables and computers also fail
The phone’s configuration or USB connection becomes more relevant.
Diagnostic signals
- ObservationNormal charging, missing files
- Google notes that some cables cannot transfer files; power does not test the data connection.
Step-by-step solutions
Unlock Android and choose File Transfer
A charging-only mode can be the entire blocker when a data connection is available.
Connect the unlocked phone to a trusted PC. Tap the Charging this device via USB notification and select File Transfer. Wording may vary by manufacturer; do not look for this in USB debugging.
If Windows shows the files, the selected mode was the observable blocker: first make a test copy without moving or deleting originals. If the option is absent or files remain unavailable, continue with the cable.
Compare a cable already known to transfer data
The first cable charging the phone does not prove it supports files.
Keep the same phone and port, and try a compatible cable known to transfer data. Connect directly without a hub where safe, and select File Transfer again. Do not force a loose or damaged connector.
If it now works with other conditions unchanged, the first cable is the main suspect. If you also removed a hub, the result points to the previous path rather than identifying only the cable. If it still fails, continue with port/computer tests.
Change one end of the connection at a time
Useful comparisons keep the cable and mode known to avoid mixing causes.
Try another direct port on the same PC with the data cable. If one works and another does not, narrow investigation to the failing port or path. Then, if needed and authorized, compare the same phone and cable on another PC.
If it works on another computer, try a known data device on the first port. Several devices failing there strengthen the PC/port hypothesis. If Windows shows USB not recognized, Code 28, or Code 43, use the matching guide with the actual code rather than third-party MTP packages.
If the phone fails on several PCs with known data cables, stop reinstalling Windows: use the phone branch. You do not need many machines; an available controlled comparison is more useful than simultaneous changes.
Investigate the phone when comparisons point to it
The evidence focuses support but still does not prove a physically broken port.
Save work and restart Android normally. Check supported updates and compare again with the known cable. Restarting the PC can be useful if the failure was limited to that computer, not as a repeated step on every computer already tested.
If the phone still offers no data across connections, give the manufacturer its model, version, visible USB options, and results. Do not enable developer options, USB debugging, or a factory reset for normal file transfer. If it stops charging, use the charging guide, which has a different scope.
Still not working?
Known data cables and several computers without improvement justify manufacturer USB support. A PC-specific failure justifies checking its port/device state. Do not wipe the phone or install unknown drivers without a specific cause.
Sources
Documentation behind this guide. Editorial recommendations are identified separately.
Source review: . A documentation review, not a physical hardware test.
Related problems
USB device not recognized in Windows
Windows displays a USB device recognition warning. Start with the connection and read device status: the warning does not automatically mean Code 43 or a drive that needs formatting.
View solutionAndroid phone won't charge
The phone is not taking charge or showing a charging indication. Check the cable, adapter and connection before assuming battery failure.
View solutionWindows Code 28: drivers not installed
Identify the device missing its driver and obtain the appropriate official package before removing its entry.
View solutionWindows Code 43 error
Windows stopped a device after a driver reported a problem. Code 43 describes that state, not a specific failed part, and can affect different device classes.
View solution