Tutorials · Retro handhelds
Android handheld: how to transfer files from a Windows PC over USB
To copy files from a Windows PC to an Android handheld, use a data cable and select File transfer mode if it is offered. First check the operating system that is running, the port used and the requirements below: a console charging does not yet confirm a data connection.
At a glance
TimeVaries with the amount of data and the network
DifficultyBeginner (LODEX estimate)
ConsoleAndroid handhelds documented below
SystemAndroid, depending on the installed firmware
Compatible devices
Compatible consoles
The Android configurations below are documented by the cited sources. This method applies only if the port, cable and firmware support file transfer to Windows. A USB-C connector, charging, video output or OTG support alone does not prove that this mode works. LODEX has not tested physical transfers on these models.
- Anbernic running Android 11: RG353V, RG353M and RG353P. Boot their Android session: this guide does not cover Linux. RG353VS and RG353PS are not covered.
- Anbernic running Android 12: RG405M and RG405V.
- Anbernic running Android 13: RG406H, RG406V, RG Cube, RG556, RG Slide and RG476H. RG Cube XX is a different model and is not covered.
- Anbernic running Android 14: RG557 and RG477M.
- Powkiddy: X28 running Android 11.
- Retroid: Pocket 4 running Android 11 and Pocket 4 Pro running Android 13; Pocket 5 and Pocket Flip 2 Snapdragon 865 running Android 13; Pocket Classic running Android 14; Pocket 6 and Pocket Nova running Android 13. The Flip 2 D1100 variant is not verified by the SD865 product page consulted.
- AYN: Odin 2 Base/Pro/Max, Odin 2 Mini and Odin 2 Portal Base/Pro/Max running Android 13. These specifications do not automatically apply to the original Odin.
The listed versions are those of the documented configurations. Check the installed version and which port is intended for data. Current Google help notes that some screens apply to Android 14 or later; older systems and manufacturer interfaces may use different labels.
Retroid Pocket 3+, original AYN Odin and Kinhank K56: compatibility still to confirm. The primary sources found do not establish their exact prerequisites here. Identify the model and variant, then check that it runs Android. Locate the data port in its manual and check that File transfer mode is offered. This qualification does not mean these consoles are incompatible.
What you need
Required items are listed below; optional diagnostic or backup equipment is marked as recommended.
- A console booted into Android and unlocked, with a port and firmware that support file transfer; consider the qualifications above.
- A Windows computer and data-capable cable matching the connectors used. A cable described only as a charging cable is not evidence of data support.
- The personal files to copy and an identified destination folder; keep the originals until verification.

1. Unlock the Android console
Turn on the console and unlock Android before connecting it to the computer. The official Android procedure requires the device to be unlocked to allow file-transfer access.
Keep the home screen or normal console interface visible: do not leave it on the lock screen when connecting.
2. Connect the console using a USB data cable
Connect the console directly to the computer using a USB cable that supports data. Not every USB cable allows file transfer: some are charge-only.
The console may initially show only charging. That does not mean file transfer is enabled: change the USB mode through the Android notification.
3. Open the USB notification
- Wait a few seconds after connecting.
- Swipe down the notification panel on the console.
- Look for a notification such as “Charging this device via USB” or its translated equivalent.
- Tap the notification to display USB connection modes.
The exact text may differ with the Android version and manufacturer. Look for the notification saying that the device is connected by USB or charging.
4. Select File transfer
- Open the options offered by the USB notification.
- Select “File transfer” or the equivalent label displayed by your console.
- Wait a few seconds for the computer to respond.
- Open the computer’s file browser and look for the console among connected devices.
If Windows displays the console and lets you open the storage it exposes, file access is available for this configuration. Next verify an actual copy: the device merely appearing does not guarantee access to all folders or a successful transfer.
5. Copy the files
In Windows, open the console’s accessible storage and copy the files from the PC to your chosen folder. Wait for the copy to finish and check the file on the console. Keep the original on the PC until that check is complete, then end the connection as described in step 7 before removing the cable.
Start with a small transfer to avoid a mistake that is difficult to spot. Then check that the file appears in the console’s storage before starting a larger copy.
6. If the console remains in charging mode
If no File transfer option appears, first check that the console is unlocked and the USB notification is open. If the connection still only charges, try another USB cable, another computer port or another computer.
These checks isolate the cause without changing the console’s system. Android documentation notes that a different cable, port or computer may be needed when detection or transfer does not work.
7. Verify that copying has finished
- Wait for copying to finish in Windows.
- Check the file in the destination folder and, where possible, open it with the intended app.
- Use Windows’ eject command when it is offered for this device.
- Unplug only after all operations have finished and, if you requested ejection, after it is confirmed.
If transfer fails with a known data cable, another port or another computer, these comparisons guide diagnosis without establishing which component or software is responsible. Record the exact model, Android version and displayed USB options, then consult manufacturer support. The absence of File transfer mode is not a reason to apply another console’s firmware or settings.
If the console only charges, disappears from Windows or interrupts copying, continue with the USB-transfer diagnostic guide to compare cables, ports and computers without prematurely concluding that something is faulty.
Sources and scope of the procedure
The Windows method is based on Google help. Console specifications and manuals identify documented Android configurations and interfaces; they do not validate transfer for every model, cable and firmware. The same result is not promised for an undocumented configuration.
- Google — transfer files between Windows and Android, then disconnect. Some steps apply to Android 14 or later.
- Anbernic manufacturer specifications — listed Android configuration and interface: RG353V; RG353M; RG353P; RG405M; RG405V; RG406H; RG406V; RG Cube; RG556; RG557; RG Slide; RG477M; RG476H.
- Manufacturer specifications: X28.
- Retroid manufacturer specifications — listed Android configuration and interface: Retroid Pocket 4; Retroid Pocket 4 Pro; Retroid Pocket 5; Retroid Pocket Classic; Retroid Pocket Flip 2; Retroid Pocket 6; Retroid Pocket Nova.
- AYN manuals: AYN Odin 2; AYN Odin 2 Mini; AYN Odin 2 Portal. For Odin 2, the table from the manual is reproduced as text; AYN’s product page confirms Android 13. These sources describe prerequisites without guaranteeing USB transfer on every firmware.
If the console charges without allowing copying, see the USB-transfer diagnostic guide.

Leave a Reply