How to Add Games to R36S: Backups, Card Readers and Folder Checks
Use a compatible microSD card reader and the game-storage location confirmed for your supplied setup. Save and shut down normally before removing a card, back up accessible files, and test one supported file before copying a large batch. A USB-C socket alone does not establish USB mass-storage access. Folder paths, accepted formats and menu refresh steps depend on the Linux-based retro gaming OS and emulator configuration; this guide does not promise a fixed completion time or universal game compatibility.
Save, shut down and identify the game card
Save your progress, use the supplied system’s normal shutdown command, and wait until shutdown is complete before removing any card. Identify the actual game-storage card and slot from your supplied instructions; do not assume every unit uses the same one-card or two-card layout. Use a compatible microSD reader for the computer. Do not assume a charging cable or USB-C port exposes the console as storage.
Open the readable game storage and back up files
Insert the identified card into the reader. Back up accessible game files, saves and configuration before editing. A file copy is not necessarily a restorable image of a bootable card. If the computer asks to format, initialize or repair an unfamiliar partition, cancel rather than accepting automatically. If the expected storage is unreadable or missing, stop and obtain setup-specific help; do not overwrite the working system to make it appear.
Match the existing system directory and emulator
Inspect the game location already configured on your card. A label such as ROMS is only an example, not a required root on every build. Names such as gba, snes and psx may differ from menu labels or the old PS1 example. Match actual spelling, case and configured path; do not rename working directories or create a parallel tree solely to match this guide.
Copy one supported file without overwriting saves
Check your emulator’s accepted format and any required companion files first. For example, a supported .gba file belongs in the actual configured GBA location; a supported disc set may need a matching .cue and its referenced tracks together. Copy one permitted file, avoid overwriting existing games or saves, and retain originals. An extension alone does not prove a valid file, required dependencies, inclusion or playable performance.
Eject, reinsert while powered off and test
Wait until copying finishes, then safely eject the card reader or mounted card through the computer. Reinsert the card in its original slot while the handheld is powered off, then start normally. Use only the game-list refresh or rescan procedure documented for your supplied menu if the entry does not appear. Test the added title and a new save before copying more. If an entry is missing or fails, check configured path, format and companion files; repeated forced restarts or reflashing are not the default remedy.
| System | Example only: check configured path and case | Common extensions: emulator support required |
|---|---|---|
| Game Boy Advance | Example only: ROMS/GBA/ | .gba |
| Super Nintendo (SNES) | Example only: ROMS/SNES/ | .sfc, .smc |
| NES | Example only: ROMS/NES/ | .nes |
| Sega Genesis | Example only: ROMS/MD/ or ROMS/GENESIS/ | .md, .bin |
| Game Boy | Example only: ROMS/GB/ | .gb |
| Game Boy Color | Example only: ROMS/GBC/ | .gbc |
| PlayStation 1 | Example only: ROMS/PS1/ or ROMS/PSX/ | .bin + .cue, .pbp, .chd |
| Nintendo 64 | Example only: ROMS/N64/ | .z64, .n64, .v64 |
| PSP | Example only: ROMS/PSP/ | .iso, .cso |
| Sega Master System | Example only: ROMS/SMS/ | .sms |
| Atari 2600 | Example only: ROMS/ATARI2600/ | .a26, .bin |
.bin + .cue pairs. Keep both files together in the same folder. The .cue file tells the emulator how to read the .bin file. Do not separate them.
Some configured PS1 emulators accept .chd, but support and conversion requirements must be checked for the supplied build. Compression savings depend on the source and are not a fixed 700MB-to-200MB result. Preserve original disc files and check that track references remain valid. N64 formats such as .z64 are examples, not a guarantee of better compatibility. Recognizing a file is separate from running the exact game acceptably; N64 and PSP remain title-dependent in this listing direction. Do not format, replace firmware or migrate the system card merely to add a title.
R36S — Choose the Actual Capacity and Confirm Your Game Needs
Selected 64GB $79.99 / 128GB $89.99 · Advertised 15,000+ / 20,000+ counts · Confirm essential titles and first-use requirements.
→ Shop R36S — $79.99 R36S Setup Guide📖 See also: R36S Setup Guide · R36S Games List · 64GB vs 128GB
