You connect your phone to a computer with a USB cable. The battery icon shows that charging has started, yet the phone does not appear as a place where you can browse files. It is tempting to conclude that the cable and port must be working because power is clearly getting through.

Charging proves only part of the connection. USB can carry electrical power and data, but those functions are related rather than identical. A phone can receive power even when the data path is unavailable, disabled, or set to a mode that does not expose files.

The useful mental model is to treat a USB connection as two jobs happening through the same physical connector: supplying power and establishing communication. Successful charging confirms the first job. File transfer also needs the second.

Power and data are separate parts of the connection

A USB cable can provide power from a computer, charger, hub, or other source to a connected phone. That is enough for the phone to show a charging indicator.

Transferring files requires more. The cable and ports must support a data connection, the phone must choose an appropriate USB function, and the computer must recognise that function and have software that can communicate with it.

This explains a common situation: a cable charges a phone perfectly but never makes its files appear on a computer. Some cables are intended only for charging and do not provide the data connections needed for communication. A damaged cable can also lose reliable data connectivity while still carrying power.

The same distinction applies to adapters, hubs, and ports. A connection path that delivers power is not automatically proof that every required data connection is working.

The phone decides what the USB connection is for

Even with a data-capable cable, a phone does not necessarily expose its files as soon as it is plugged in.

Modern phones can use USB for several purposes. Depending on the device, these may include charging, transferring files, transferring photos, sharing a mobile internet connection, connecting to audio or musical equipment, or other functions. The exact choices and labels vary by operating system and manufacturer.

Many phones default to a charging-focused or no-data mode. In that state, the physical USB data connection may exist, but the phone is not offering file access to the computer.

On phones that provide a USB mode selector, choosing a file-transfer option tells the phone to present an appropriate data service to the computer. The menu may appear in a notification, a connection prompt, or the device’s USB settings. Its wording and location can change between phone models and software versions.

This is why reconnecting the same cable can produce two different results depending on the selected USB mode.

Why Android phones often use MTP instead of appearing as a normal drive

Many Android phones transfer files using Media Transfer Protocol, usually shortened to MTP. MTP lets a computer browse and manage files that the phone chooses to make available.

This is different from attaching a USB flash drive as ordinary block storage. With a flash drive, the computer typically works directly with the drive’s filesystem. With MTP, the phone remains in control of its storage and responds to requests from the computer for files and folders.

That distinction matters in everyday use. An Android phone connected for file transfer may appear as a portable device rather than as a conventional disk with a drive letter. The computer is communicating with the phone through a file-transfer protocol instead of taking direct ownership of the phone’s internal storage.

MTP also means that successful file browsing depends on software at both ends. The phone must provide the service, and the computer must support it correctly.

Some devices also offer PTP, or Picture Transfer Protocol, a mode intended mainly for transferring photos. If a phone is using a photo-oriented mode, the computer may expose images differently or show less of the phone’s storage than it would in a general file-transfer mode.

Why unlocking the phone can matter

A phone may require you to unlock it before it exposes files over USB. This is a deliberate access-control decision: physical possession of a connected cable should not necessarily give a computer immediate access to everything the phone makes available through file transfer.

As a result, you can have a valid data cable, a working USB port, and a recognised phone but still see no browsable files while the device is locked. After unlocking the phone, you may also need to approve the connection or select file transfer.

The exact behaviour varies. Some phones remember parts of a previous choice, while others return to a more restricted USB mode when reconnected. Managed devices can also have policies that limit USB data functions.

The practical lesson is simple: when diagnosing file transfer, do not treat a charging indicator as the final test. Check the phone’s unlocked state and its current USB mode as well.

Why the computer may recognise the phone but still not show files

USB communication happens in stages. A computer can detect that a device has been attached without necessarily being ready to browse its storage.

For file transfer to work, the operating system needs suitable support for the protocol or device function the phone is presenting. On some systems this support is built in. In other situations, additional software, a driver, or a vendor-supported application may be required.

This creates several possible symptoms. The phone may appear somewhere in the operating system but not in the file browser. It may appear with no accessible files. It may connect and disconnect repeatedly. Or a photo-import tool may see it while a general file browser does not.

Those symptoms are useful because they show that the problem is not necessarily at the same layer. If the computer detects nothing at all, the cable, port, adapter, or physical connection deserves attention. If the computer detects the phone but cannot browse files, the selected USB mode and the computer’s protocol support become more likely places to investigate.

A data-capable cable is necessary, but it is not the whole answer

USB connectors can look identical while the cables behind them have different capabilities. This is especially easy to miss with USB-C because the connector shape alone does not tell you every feature a particular cable supports.

A cable supplied with a simple charging accessory, for example, may not be suitable for file transfer. Even among data-capable cables, supported data rates and other features can differ.

For troubleshooting, you do not need to identify every USB specification first. A more useful test is to try a cable that is known to transfer data successfully with another compatible device. If file transfer suddenly works, the original cable was part of the problem even though it charged normally.

If changing the cable does not help, try another suitable USB port on the computer and remove unnecessary hubs or adapters from the path. This reduces the number of components that could interfere with the data connection.

Use the symptom to narrow down the problem

When a phone charges but file transfer fails, checking the connection in a logical order is more effective than changing many settings at once.

First, unlock the phone and look for its current USB connection mode. If the phone offers a file-transfer option, select it. Do not rely on an exact menu path from another device because manufacturers and software versions use different labels and locations.

Next, confirm that the cable supports data. A known-good data cable is a stronger test than a cable that is merely known to charge.

Then try another appropriate USB port, preferably with the phone connected directly rather than through an unneeded hub or adapter. If the computer now detects the phone differently, the previous connection path may have been the limiting factor.

If the computer recognises the phone but still cannot browse files, check what software the phone manufacturer and computer operating system support for that type of connection. The required handling can differ between platforms.

Finally, test the two sides separately if possible. Connecting the phone to another computer, or connecting another known-working data device to the same computer and cable path, can help reveal whether the problem follows the phone or stays with the computer setup.

This approach works because each test answers a specific question rather than simply repeating the connection attempt.

Charging speed does not tell you whether file transfer should work

Another easy mistake is to use charging performance as evidence about data capability.

A phone may charge quickly through one connection and slowly through another because USB power delivery depends on the capabilities and negotiation of the phone, power source, cable, and relevant charging technology. Data transfer has its own requirements.

A connection can therefore be good at charging and unsuitable for data, or capable of data while providing only modest charging power. The two functions share hardware, but one is not a reliable measurement of the other.

Similarly, replacing a cable with one advertised for a high charging wattage does not by itself guarantee the data features you need. Cable capability should be evaluated for the intended job, not inferred from a single specification.

The important distinction is connection versus permission to exchange files

When a phone charges over USB, something useful has already been established: electrical power is reaching the device. But file transfer asks several additional questions.

Can the cable and connection path carry data? Has the phone enabled a data function? Is the phone unlocked or has access been approved? Does the computer understand the protocol the phone is offering?

Thinking through those questions turns a vague “USB is not working” problem into a small set of separate checks.

A charging icon is therefore not evidence that the entire USB connection is healthy. It tells you that power works. File transfer begins only when the data path, phone mode, access state, and computer support also line up.