USB-C cable charges but will not transfer Android files: what to check

Featured image: IKEA SITTBRUNN USB-C cable shown as an illustrative example, not a Buy2Fix listing or a promise of compatibility. Photo: Dinkun Chen / CC BY-SA 4.0 (via Wikimedia Commons). Resized; featured version arranged with editorial text and colour accents. Photograph source; CC BY-SA 4.0. The adapted featured artwork is also licensed under CC BY-SA 4.0.

Quick answer

If an Android phone charges through USB-C but will not copy files, do not assume its charging port needs replacing. Check three separate things: the cable supports data, the phone is unlocked and set to File Transfer, and the computer can recognise the connection. Charging alone does not settle those questions.

This guide covers ordinary file copying between an Android phone and a Windows computer or Chromebook. It is not a phone-to-phone migration guide, a way to bypass a locked device, or a socket-repair procedure. Menu names vary by phone and Android version; use your manufacturer's instructions when they differ.

Separate charging from data

Google's Android guidance notes that some USB cables cannot transfer files. USB-IF also distinguishes the connector from performance: a USB-C cable may support USB 2.0 data rather than faster USB operation. A slower data specification is not the same as no data support. Look for a stated data capability instead of relying on the connector shape, a charging-wattage claim or the cable's appearance. Google's file-transfer guidance and USB-IF's terminology guidance explain these distinctions.

Write down what actually works. “The battery icon appears, but the computer shows no phone” is more useful than “USB is broken”. A successful charge is an observation, not proof that the complete file-transfer path is working.

Choose the ordinary file-transfer mode

For a trusted computer you are authorised to use, Google's starting sequence is to unlock the phone, connect the cable, open the USB charging notification and choose File Transfer under the USB-use options. Windows should then offer a file-transfer window; on a Chromebook, use the Files app. Google warns that some instructions require Android 14 or later. Follow the phone's own support page if its labels differ.

For example, Xiaomi's Mi 11 guidance calls the option “File transfer/Android Auto”. That is a model-specific label, not a promise that every Android phone uses it. Xiaomi's Mi 11 USB-transfer instructions.

Start with a small, non-sensitive file that you can recognise at the destination. Copy rather than remove your only original, then open the copy before deciding that the transfer succeeded. This is a checking method, not a claim that copying one file verifies every folder or application backup.

Use a one-change-at-a-time connection check

Google recommends trying another cable, another computer for the phone, and another device for the computer. Xiaomi also recommends another computer USB port. Keep the phone mode and test file consistent while changing one connection element. Record the outcome before moving on; otherwise a successful result will not tell you which change mattered.

The worksheet is an original way to organise observations, not a laboratory diagnostic test. It narrows the support conversation without pretending to identify an internal component.

Recognise policy and security boundaries

A work-managed phone may intentionally restrict USB file copying. Google Workspace documents an administrator setting for USB file transfer on supported managed Android devices. If the option is unavailable on an organisation-owned phone, ask its administrator rather than trying to work around the restriction. Google Workspace Android policy documentation.

This workflow does not require instructions for disabling security software, bypassing a screen lock or enabling developer debugging. Do not install an unknown “USB repair” utility to complete it. If ordinary supported transfer remains unavailable, use the manufacturer's support route or an authorised alternative transfer method.

What to ask before buying another cable

• Does the listing explicitly support data transfer, and at what stated standard?
• Do both connector ends match the actual phone and computer ports?
• Is the claim tied to an identifiable cable model rather than a generic photograph?
• Can the supplier explain the return route if the documented compatibility does not match your equipment?

No particular cable is recommended here: a relevant-looking product photograph is not verification of its capabilities. Keep any charging requirement separate from the file-transfer requirement when asking a supplier.

Finish with a verified copy or a useful support record

When the copy works, confirm the destination file opens. Use Windows' eject step before disconnecting, as Google advises. If it still fails, record the phone model, Android version, computer/OS, cable identification, selected USB mode, exact message and the comparisons attempted. Share only the information support needs, not private file contents.

Stop experimenting with a visibly damaged connector or a setup that cannot be connected normally without force. This article does not instruct you to scrape contacts, open the phone or replace its port. The useful outcome may be a working copy—or evidence that prevents buying the wrong repair part.

Compare relevant listings only when needed

If your comparison points to the cable, check a replacement’s stated data specification as well as its connectors. For example, the Toocki USB-C-to-USB-C cable listing specifies USB 2.0 data transfer up to 480Mbps. That is a listing specification, not a diagnosis of your phone; confirm that both your phone and computer have the required USB-C connection.