How to Save Games on the R36S (And Why Your Saves Disappear After Reboot)

Below is the shortcut table for both FN and Select builds, the RAM-flush rule that keeps in-game saves from vanishing, and step-by-step fixes for Sega Dreamcast VMU and read-only SD card errors.

Quick Cheat Sheet: R36S Save & Load Shortcuts (ArkOS Stock vs. Updated FN Key)

Press FN + R1 or Select + R1 to freeze any RetroArch game into a save state slot on your 2Bluebox (2bluebox.com) R36S handheld.

When looking into how to save game in R36S or setting up an R36S save game routine, players run into a surprise. There is no dedicated physical Save button on the console shell. On top of that, the modifier key changes depending on your ArkOS firmware build.

As the official ArkOS global event keys documentation explains, community ArkOS 2.0 builds map the center FN button as the primary Hotkey Enabler. In contrast, older factory cards and generic EmuELEC clones assign hotkeys to Select. On clone boards, the center button is often labeled M or left completely disconnected.

Use these six core button combinations inside any RetroArch emulator (NES, SNES, Game Boy, GBA, Sega Genesis, PS1, and Arcade):

The R36S provides two distinct save architectures. Mixing them up is the number-one reason retro fans lose hours of RPG progress.

Understanding the difference between In-Game Battery Saves (.srm) and RetroArch Save States (.state) is essential:

Table 1: In-Game Battery Saves (.srm) vs. RetroArch Save States (.state) on 2Bluebox R36S. "Tested on our unit" means we checked it on a device we own. "Manufacturer spec" means the maker states it and we haven't verified it ourselves. "Community reports" means players report it, and results can vary.

For a complete layout of brightness, audio volume, and fast-forward toggles across the device, bookmark our R36S shortcuts and ArkOS hotkeys cheat sheet.

Why Your In-Game Saves Disappear: The "Select + Start" RAM Flush Rule

In-game .srm saves stay trapped in volatile RAM until you exit cleanly with FN + Start or enable a ten-second SaveRAM Autosave interval in RetroArch.

Here is the exact issue we inspect weekly on our hardware bench. A player spends three hours catching rare creatures in Pokemon Emerald or clearing castles in Super Mario World. They save inside the game menu, see the confirmation text, and immediately hold down the physical Power button on the left edge of the R36S. When they power the unit back on, their save file is gone.

According to the official Libretro documentation on SaveRAM and overrides, RetroArch emulates a cartridge's original battery-backed SRAM chip inside volatile system memory (RAM). This design prevents constant small writes from wearing out flash memory on your microSD card. By default, RetroArch flushes that .srm file to your EASYROMS partition only when the emulator closes cleanly.

If you cut power with the physical side button or press the recessed Reset pin, system RAM clears instantly. The save data never reaches your card. Follow this four-step Save Dual-Lock and Autosave routine to safeguard your progress:

1. Save Inside the Game Menu First: Open the game's standard save prompt (such as a Final Fantasy inn or the Pokemon pause screen). Wait for the in-game saving animation to finish completely.
2. Drop a Backup Save State (FN + R1 or Select + R1): Before exiting, tap FN + D-Pad Right to select an empty slot (like Slot 1 or Slot 2). Press FN + R1 to create an instant R36S save state. A yellow status notification will confirm the write at the bottom of the screen.
3. Quit to EmulationStation (FN + Start or Select + Start Twice): Press FN + Start (or Select + Start twice on factory firmware). This clean exit command instructs RetroArch to write your cached .srm file directly to the microSD card.
4. Turn On 10-Second SaveRAM Autosave (Permanent Protection): Open any RetroArch game. Press FN + X (or Select + X), then press B to enter the RetroArch Main Menu. Navigate to Settings -> Saving -> SaveRAM Autosave and set the timer to 10 seconds. Next, browse to Configuration File -> Save Current Config. RetroArch will now sync your .srm data to disk every ten seconds automatically while you play.

How to Fix R36S Dreamcast Save Errors (Formatting the Virtual VMU in Flycast)

Fix R36S Dreamcast save errors by booting into the Dreamcast BIOS inside the Flycast core options and formatting the virtual VMU memory card once.

Over a thousand retro enthusiasts every month search for an R36S Dreamcast save solution. Popular arcade titles like Sonic Adventure, Crazy Taxi, and Soulcalibur display "Not enough free blocks" or "Memory card is unformatted" upon booting. This message does not indicate defective R36S hardware.

As documented in the Flycast Libretro core guide, the Sega Dreamcast stored saves on a removable Visual Memory Unit (VMU). In 1998, original VMUs featured an LCD screen and 128KB of flash storage holding 200 memory blocks. When you launch a Dreamcast title for the first time on the R36S, Flycast creates a raw virtual card file (vmu_save_A1.bin in your bios/dc/ or /roms/bios/dc/ folder).

However, arcade ports like Crazy Taxi (which requires 10 blocks) and Sonic Adventure refuse to write to a blank card until the Dreamcast BIOS initializes the file system. Use this four-step procedure to format the virtual Dreamcast VMU on your R36S:

1. Use FN + R1 Save States for Immediate Play: If you want to jump straight into arcade action without formatting menus, press FN + R1 (or Select + R1) at any point. RetroArch save states bypass the virtual VMU entirely and record your exact spot.
2. Enable Boot to BIOS in the Flycast Core Options: To fix in-game VMU saves permanently, launch any Dreamcast title that runs through RetroArch (Flycast). Press FN + X (or Select + X) to open the Quick Menu. Select Core Options -> System, and toggle Boot to BIOS to ON.
3. Format Memory Card A1 Inside the Dreamcast BIOS: Close the Quick Menu and restart the core (or relaunch the game). The classic white Sega Dreamcast swirl will load into the four-icon system dashboard. Choose the File icon (the VMU graphic), select the memory card in Slot 1, choose All -> Delete All (Format Memory Card), and pick a custom icon color. The screen will confirm 200 blocks free.
4. Disable Boot to BIOS and Exit Cleanly: Press FN + X, return to Core Options -> System, toggle Boot to BIOS back to OFF, and press FN + Start to quit. ArkOS will save the newly formatted vmu_save_A1.bin file to your storage card, eliminating future Dreamcast save warnings.

If your R36S refuses to save even after you press FN + R1 and quit with FN + Start, the culprit is almost always an unbranded factory microSD card or a single-RAM clone board. Our 2Bluebox R36S Handheld ($79.99) eliminates both headaches: every unit is inspected by 2Bluebox LLC before shipping to verify genuine Dual-RAM RK3326 hardware, ArkOS 2.0 hotkey mappings, and a working game partition with 15,768 preloaded games.

Fixing R36S & R36 Max Save ROM Issues (Read-Only Stock SD Card & Pokemon Saves)

When an R36S or R36 Max stops saving ROM progress entirely, the unbranded stock microSD card has usually locked itself into read-only failure mode.

We regularly diagnose the R36 Max save ROM issue along with identical complaints on budget marketplace handhelds. The console displays "State saved to slot 0" or "Failed to save state," yet all progress vanishes after rebooting. The Handhelds Wiki R36S troubleshooting guide confirms that generic factory cards degrade quickly. Their flash controller locks into read-only mode right before total memory failure.

Investigate these three primary causes whenever your R36S or R36 Max fails to store new saves:

• Cause 1 (Stock MicroSD Card Locked in Read-Only Mode): Power down the handheld, insert the card into a computer card reader, open the EASYROMS drive, and create a new folder named TEST_SAVE. Safely eject the card, re-insert it, and verify whether TEST_SAVE remains. If the folder vanished or your operating system throws an I/O write error, the card's NAND flash controller has permanently locked itself. Back up your screen .dtb files immediately and upgrade to a reputable card following our R36S SD card replacement and TF1/TF2 compatibility guide.
• Cause 2 (The Pokemon Save State vs. .srm Overwrite Trap): In Pokemon FireRed, Emerald, and Crystal, beating the Elite Four triggers an automated .srm save. The game then resets to the title screen. If you subsequently press FN + L1 to load an older Save State (.state), RetroArch overwrites console RAM with earlier memory data. This wipes out your newer Hall of Fame battery save. After major in-game milestones, always boot your adventure from the title screen (Continue) instead of reloading older states.
• Cause 3 (Depleted EASYROMS Storage or Core Configuration): Uncompressed PS1 and arcade save states consume multiple megabytes per slot. When your card hits 0 MB of free space, RetroArch fails to write new states. Clear out old .state files to free up space. You can also assign GBA titles to the mGBA core by pressing Select on the title in EmulationStation -> Edit This Game's Metadata -> Emulator: RetroArch and Core: mgba.

To review how genuine R36S hardware handles demanding emulation libraries, read our hands-on R36S review and buying guide.

Standalone Emulator Save Keys (PPSSPP, DraStic NDS & N64)

Standalone emulators for Nintendo DS, Sony PSP, and Nintendo 64 bypass RetroArch and use dedicated L3, R3, or Select menu buttons for saving states.

Why does pressing FN + R1 produce no response when you play Mario Kart DS or God of War: Chains of Olympus? To maximize frame rates on the Rockchip RK3326 processor, ArkOS 2.0 launches Nintendo DS (DraStic), Sony PSP (PPSSPP), and certain Nintendo 64 titles as standalone emulators outside RetroArch.

Because these standalone engines bypass global RetroArch hotkeys, use the dedicated mappings outlined in Table 2:

Table 2: Standalone Emulator Save & Exit Shortcuts on R36S (DraStic NDS, PPSSPP & N64). "Tested on our unit" means we checked it on a device we own. "Manufacturer spec" means the maker states it and we haven't verified it ourselves. "Community reports" means players report it, and results can vary.

If your emulator overlays appear misconfigured or FN combinations behave erratically, consult our step-by-step guide to updating ArkOS 2.0 on the R36S. Keep our R36S black screen fix guide bookmarked as well before modifying system files.

Matching your hardware to your playstyle makes all the difference. You might want pocket RPGs with instant save states on the R36S, two-player TV arcade action, or sixth-gen PS2 and GameCube games on PC. Explore all three bench-tested 2Bluebox systems below:

Frequently Asked Questions (FAQ)

Conclusion

Mastering how to save game on R36S consoles comes down to the Save Dual-Lock routine. Save inside the game, drop a backup state with FN + R1, and exit cleanly with FN + Start before shutting down. With that habit in place, you never have to worry about losing a 40-hour Pokemon or Final Fantasy campaign again. Format your virtual Dreamcast VMU once in Flycast, enable the 10-second SaveRAM Autosave Interval in RetroArch, and replace unbranded stock cards before they lock into read-only mode.

Lock in your save state, exit cleanly to the menu, and Press Start. - Liam Parker, Head of Retro Gaming & Hardware Testing at 2Bluebox

Further Reading & Resources

• Global ArkOS hotkeys: ArkOS Frequently Asked Questions: General Questions & Global Event Keys (ArkOS GitHub Wiki)
• SaveRAM & Save State mechanics: Libretro Guides: Overrides, SaveRAM (.srm) & Autosave Interval (Libretro Documentation)
• Dreamcast VMU configuration: Flycast Libretro Core Documentation: BIOS & VMU Files (Libretro Documentation)
• Stock SD card troubleshooting: R36S Problems and Troubleshooting Guide (Handhelds Wiki)