How to Connect the R36S to a PC (and Transfer Games Safely)

Let's clear up the thing that sends most people looking for this guide in the first place: plugging the R36S into your computer with its USB-C cable does not make it show up as a drive. That port is for charging. Nothing is broken, and you haven't done anything wrong — the console simply doesn't present itself as USB mass storage out of the box.

There are four ways to actually move files, and which one suits you depends on whether your console has WiFi and how much you enjoy tinkering.

Method 1: the card reader (start here)

Unglamorous, and still the right answer most of the time. It's the fastest by a wide margin and it works identically on every firmware and every model.

1. Power the console fully off. Not sleep — off. Pulling the card while the OS is writing is how filesystems get corrupted.
2. Remove the microSD card and put it in a reader connected to your computer.
3. Open the card. You'll usually see one readable partition; that's where roms (or games) lives.
4. Copy your files into the matching system folder — roms/snes, roms/psx, roms/psp and so on. A game in the wrong folder won't appear in the menu.
5. Eject safely, reinsert, power on, and rescan or reboot so the OS indexes the new files.

On a Mac

macOS shows the readable partition and ignores the Linux ones, which is fine. Two things to watch: macOS scatters hidden ._ files and .DS_Store across the card, which some firmware displays as phantom games. A quick clean-up from Terminal fixes it:

dot_clean /Volumes/YOUR_CARD_NAME

And always eject properly — macOS caches writes aggressively, so pulling the card early really can lose a file that looked copied.

Method 2: WiFi transfer over Samba

If you have the HN-R36S-WiFi, this is the one that makes the card reader feel obsolete for day-to-day use. The console appears as a shared folder on your network.

1. Get WiFi connected first — our R36S WiFi setup guide covers this end to end.
2. Enable network file sharing in your firmware. On ArkOS it's under Options → Network → Enable Samba. DarkOS has its own toggle in network settings.
3. Note the console's IP address — the same network menu displays it, usually something like 192.168.1.x.
4. On Windows, open File Explorer and type \\192.168.1.x into the address bar. On Mac, use Finder → Go → Connect to Server and enter smb://192.168.1.x.
5. The console's folders open like any network drive. Drag files straight in.

Two practical notes. Wireless transfer is much slower than a card reader — fine for a few GBA ROMs, genuinely tedious for a 1.5GB PSP ISO. And keep the console awake during transfers; if it sleeps, the share drops mid-copy.

Method 3: FTP

When Samba is being temperamental — and on some Windows builds it is — FTP is the more reliable wireless path. Most R36S firmware ships an FTP server alongside Samba.

1. Enable FTP in your firmware's network menu.
2. Install FileZilla on your computer.
3. Connect to the console's IP on port 21, with the credentials your firmware shows (ArkOS commonly uses ark / ark; check your own network menu rather than assuming).
4. Drag files across. FileZilla queues transfers and resumes interrupted ones, which is exactly what you want over WiFi.

Method 4: USB networking

For a non-WiFi R36S, some firmware builds can expose a network connection over the USB-C cable — so the console appears as a network device to your computer even though it never appears as a drive.

This one is firmware-dependent, fiddly, and genuinely not worth it for most people. If your console has no WiFi, a ₹300 card reader will save you an evening. We mention it only because people ask whether the USB port can do anything at all — it can, just not the obvious thing.

Troubleshooting

Nothing happens when I plug in the USB cable. Expected. The port charges. Use a card reader or WiFi.

Games copied but don't appear in the menu. Almost always one of: wrong folder, an archive format the emulator can't read (some cores want the file unzipped), a missing BIOS for that system, or the OS hasn't rescanned. Reboot before you assume the file is bad.

Windows can't see the console on the network. Check both are on the same network — not one on 2.4GHz guest and the other on 5GHz main. Then try the raw IP (\\192.168.1.x) rather than the hostname; Windows name resolution for these devices is unreliable. If it still fails, use FTP.

Transfers stall or fail halfway. The console went to sleep, or the card is failing. Disable sleep during transfers; if it persists across cards, suspect the microSD. Counterfeit cards are the most common hardware cause of mystery problems on these consoles.

The card shows as unformatted or the wrong size. That's Windows failing to read Linux partitions, not a dead card. Don't format it. If you genuinely need to start over, reflash properly — see our firmware flashing guide.

Which method should you actually use?

Honest recommendation: use a card reader for anything large, and WiFi for everything else. Set up your library once over the reader — PSP, PS1, the big stuff — then use Samba for the ongoing trickle of "I want to try this one game." That combination means you almost never open the console again, without ever waiting twenty minutes for an ISO to crawl across your WiFi.