A Xiaomi phone that charges but won’t connect to a PC often needs one of a few fixes: use a data-capable USB cable, switch the phone to File Transfer/MTP, or reinstall the Windows MTP/Android driver. If you skip the wrong step, Windows keeps seeing only power, so file transfer, backups, and device syncing fail. This guide walks you through the symptom path, charging-only, no MTP device, or driver conflict, so you can fix the exact break.
What the charging-only symptom means
If the phone charges but Windows cannot see files, the USB link is carrying power but not the data lines that MTP needs. The fastest first check is a known good data cable, then the Xiaomi USB mode on the phone, then the Windows driver.
What MTP does on Xiaomi and Redmi phones
MTP, or Media Transfer Protocol, is the Windows file-transfer path for photos and other files over USB. It depends on both sides: the phone must expose file transfer, and Windows must load the right portable-device driver. If either side falls back to charging only, Explorer often stays empty.
Say your Redmi phone shows a charging icon as soon as you plug it in, but File Explorer never adds a device. That usually points to a cable, mode, or driver problem rather than a dead port, because power is getting through while data is not.
When the problem is likely hardware instead of settings
Hardware rises to the top when the phone charges on one cable but not another, when a rear PC port works better than a front port, or when a hub is involved. Connector wear matters too. A loose fit can charge while data drops out under light movement.
Likely causes
Most often, the fault is a cable or phone setting. Less commonly, Windows loads the wrong device entry, or a PC port, hub, or connector is unstable. Use the symptom that matches your case, then follow that branch instead of changing every setting at once.
| Symptom | Most likely cause | Exact check | Next fix |
|---|---|---|---|
| Phone charges but no transfer | Charge-only cable or USB mode set to charging only | Try another data-capable USB cable and open the USB notification on the phone | Switch to File transfer/MTP, then test again |
| Phone appears as unknown device | Windows driver conflict or bad enumeration | Open Device Manager and look for Unknown device or Portable Devices | Remove the device entry, reconnect, and refresh the MTP driver |
| Phone appears then disconnects | Flaky cable, loose connector fit, hub, or unstable port | Move to a rear PC port and remove any hub or adapter | Replace the cable or stop using the hub |
| PC sees the phone but Explorer shows nothing | MTP permission or mode mismatch | Check the phone’s USB preference and look for the file-transfer prompt | Change to File transfer/MTP; if that fails, reinstall the Windows MTP driver |
Xiaomi USB settings to check
On Xiaomi and Redmi phones, the USB choice on the phone matters. Charging only blocks file copy. File transfer is the normal MTP path. Photo transfer, or PTP, is narrower and may help when file transfer does not appear. USB debugging is separate and only matters for ADB tasks.
- Plug the phone into the PC and open it.
- Pull down the notification shade and tap the USB notification, then choose File transfer or Transfer files.
- If that option is missing, try Photo transfer (PTP) once to see whether Windows detects the device differently.
- Open Settings > Additional settings > Developer options only if you need ADB or Fastboot, then check USB debugging.
- If MIUI or HyperOS shows a permission prompt, allow the connection for file access.
A common first-timer mistake is turning on USB debugging and expecting ordinary file copy to start working. USB debugging can help with ADB tools and some recovery tasks, but It does not replace MTP for drag-and-drop file transfer in Explorer.
USB cable and port checks
A charge-only cable can power the phone while blocking data. That is why a replacement cable fixed the forum case, and the poster said the supplied cable was the problem. Start there before changing drivers. Use an original or certified replacement if possible.
- Swap to a USB cable that is known to pass data, not just charge.
- Check the connector fit at both ends. A loose Type-C plug can sit far enough in to charge and still fail on data.
- Move the cable from a front-panel port, hub, or adapter to a rear motherboard port.
- Try a USB 2.0 port if USB 3.x behaves badly, or test the opposite if the PC’s controller is picky.
- Use another computer once to separate a cable fault from a phone fault.
Suppose the phone charges from a front-case port but disconnects every time you open Explorer. That points to an unstable path rather than a dead phone. A rear port often gives a cleaner connection because it skips front-panel wiring and weak adapters.
Windows MTP driver fix
If Windows can power the phone but does not load a portable-device entry, the MTP driver is the next target. Windows should usually show the phone under Portable Devices when the link is healthy. An Unknown device entry often means Windows needs to refresh the driver.
- Right-click Start and open Device Manager.
- Expand Portable Devices, Other devices, and Universal Serial Bus controllers.
- If you see Unknown device, right-click it and choose Uninstall device.
- Disconnect the cable, reconnect the phone, and wait for Windows to reinstall the MTP driver.
- If the phone still fails, right-click the USB controller entries and choose Scan for hardware changes.
The forum case matched this pattern in part: the phone charged, the PC would not detect it, and the device did not appear in Windows Explorer. One reply said Android needs drivers on the computer, and another suggested downloading phone drivers on the PC. In that case, the replacement cable fixed the connection, which shows why cable and driver checks should stay separate.
Unknown device or disconnecting
When Windows sees the phone briefly and then drops it, the fault is often in the data path itself. That can be a weak cable, a wobbly port, a hub, or a Windows-side driver fight. A second PC helps tell the difference.
- Disconnect any USB hub, dock, or extension lead.
- Plug straight into a rear port on the PC.
- Open Device Manager and watch whether the entry flickers between connected and disconnected.
- If the phone shows up on one PC but not another, focus on the failing PC’s driver stack.
- If it fails everywhere, replace the cable first, then test the phone port and connector fit.
Can a bad USB cable stop Xiaomi from connecting to PC? Yes. A cable can still supply power while failing on data, and that creates the exact “charges but no files” symptom. If the phone works on a second cable but not the first, stop troubleshooting the phone and replace the cable.
USB transfer decision table
Use the table below to match the symptom to the next check. It separates charging-only failures from Windows driver problems, so you do not waste time on settings that cannot fix a dead data path.
| Symptom | Most likely cause | Exact check | Next fix |
|---|---|---|---|
| Phone charges but no transfer | Charge-only cable or charging-only USB mode | Try a different data-capable cable, then open the USB notification and choose File transfer | Replace the cable if a known-good data cable works |
| Phone appears as unknown device | Windows MTP driver or USB controller issue | Check Device Manager for Unknown device or Portable Devices | Uninstall the entry, reconnect, and refresh the driver |
| Phone appears then disconnects | Flaky cable, loose connector, hub, or port wear | Test a rear port without a hub or adapter | Stop using the hub and replace the cable if the dropouts continue |
| PC sees the phone but Explorer shows nothing | Wrong USB mode or missing MTP permission | Check for File transfer, then try PTP once | Switch the phone to File transfer and reconnect |
Still not working?
If the basic checks fail, move one level deeper. Try another Windows 10 or 11 PC, then reinstall the USB and MTP device entries in Device Manager. If ADB or Fastboot is part of your workflow, install only the Android platform tools and the separate ADB/Fastboot drivers, because those are different from the MTP driver used for file copy.
- Test the phone on a different PC with a different cable.
- On the failing PC, open Device Manager and remove the phone entry plus any Unknown device tied to it.
- Restart both the phone and the PC, reconnect the phone, and confirm the USB mode on the handset.
- If recovery or development tools are needed, install the ADB/Fastboot package separately; do not expect it to fix normal Explorer transfers.
- As a last resort, reset the phone’s connection settings or perform a factory reset only after the cable, port, and driver paths have been ruled out.
Keep one known-good data cable for file transfers and avoid front-panel ports and hubs when a stable rear port is available. That cuts down repeat failures from loose connectors and weak adapters.
Frequently asked questions
What Windows driver do I need for Xiaomi USB connection?
For ordinary file transfer, Windows needs the MTP driver, not ADB or Fastboot. In Device Manager, the phone should appear under Portable Devices or as a refreshed MTP entry. ADB drivers are separate and only matter for development or recovery tasks.
Why does my Xiaomi phone charge but not transfer files?
That usually means the cable is power-only, the phone is set to charging only, or Windows did not load the MTP driver. Start with a different data cable, then change the USB mode to File transfer, then refresh the device in Device Manager.
How do I enable file transfer on Xiaomi when USB is connected?
Plug in the cable, open the phone, and open the USB notification in the shade. Choose File transfer. If that option is missing, try Photo transfer (PTP) once. USB debugging is separate and does not replace the file-transfer mode.
Can a bad USB cable stop Xiaomi from connecting to PC?
Yes. A bad or charge-only cable can still deliver power while blocking data, so the phone charges but Windows cannot see files. If a different cable makes the phone appear in File Explorer, replace the original cable and stop troubleshooting the phone side.