R36S Troubleshooting: Fixes for Games Not Loading, Missing Games and Black Screens

Most R36S problems start on the microSD cards, not in the hardware. Games that don't show up are usually in the wrong folder or have an unsupported extension. Games that won't start usually lack a BIOS or, for arcade, use the wrong ROM set. A black screen at power-on usually points to the TF1 system card: missing, failing, or flashed with a device file that doesn't match the screen.

Find your symptom below. Menu names are from ArkOS and dArkOS; other builds may differ.

R36S problems and fixes at a glance

Why are games not showing in the list?

1. Check the folder. Each system has its own folder, and the names depend on your firmware. The R36S SD card guide lists them.

2. Check the extension. A file the system doesn't accept is skipped. The ArkOS emulator list gives every system's extensions.

3. Unhide systems. Press Start, open UI Settings → Visible Systems and select all.

4. Turn off "Parse gamelists only" under Start → Advanced Settings, as the ArkOS FAQ advises.

5. Reboot. EmulationStation hides systems with empty folders and picks up new games when it restarts.

6. Using two cards? After Switch to SD2 for Roms, the menu reads games from the TF2 card, so games left on TF1 won't show.

7. Copied from a Mac? Delete hidden ._ files; the ArkOS wiki notes Macs can also add extra characters to files.

Why won't a game start?

• Missing BIOS. Check the R36S BIOS files guide.
• Damaged copy. Copy it again from your own backup and eject the card safely.
• Wrong format. A .cue file must sit next to the .bin files it names. ArkOS's Dreamcast cores don't read .7z.
• Wrong emulator for this game. For a whole system, press Start → Emulator Settings. For one game, highlight it, press Select, choose Edit This Game's Metadata and change the emulator or core.
• A demanding game. Look it up in the game list before assuming a fault.

Why won't an arcade ROM start?

Arcade ROM sets are tied to an emulator version. On ArkOS, the folder decides the default emulator:

• Match the set to the core. The libretro FBNeo docs say romsets change as FBNeo is updated. Sources disagree on the older cores: the ArkOS list quotes FB Alpha 0.2.97.44 sets for its arcade folders, while libretro says FB Alpha 2012 matches 0.2.97.29 sets. The DAT file for your exact core version settles it. If your set was built for an alternative core, switch to it for that game.
• Keep parent sets. In split sets, a clone game needs its parent zip in the same folder.
• No coins? The ArkOS FAQ says Select doesn't insert coins in some MAME and CPS games; map coin to R2 or L2.

Why do Neo Geo, Sega CD or PC Engine CD games fail?

These systems won't start games without their BIOS:

• Neo Geo: neogeo.zip, still zipped, in both bios and neogeo.
• Sega CD: the BIOS for the game's region, such as bios_CD_U.bin for US games.
• PC Engine CD: syscard3.pce. Super CD-ROM² games won't boot with the older system cards.
• Neo Geo CD: the BIOS goes in bios/neocd.

On a two-card setup, these belong in the bios folder on the TF2 card. The BIOS guide has exact names and checksums; the Neo Geo and arcade pages list the games.

What causes a black screen on boot?

1. Charge it. The ArkOS FAQ lists a flat or worn battery among the reasons a unit won't boot.

2. Reseat the TF1 card. The system card must be in TF1, fully clicked in.

3. Insert both cards if you set up a games card with Switch to SD2 for Roms; ArkOS then won't boot without it.

4. Just flashed new firmware? A blank or white flickering screen usually means the device file (DTB) doesn't match your screen panel. Run the build's model selector, or copy your original DTB files back to the BOOT partition. dArkOSRE-R36 says a blank first boot usually means a Panel 9 device.

5. Suspect the card. Boot your backup of the original card, or reflash onto a name-brand card.

Why is the R36S stuck at the boot logo?

• The first boot is slow. The official dArkOS wiki says provisioning can take up to a minute to start and the device may reboot twice. The ArkOS-R3XS image for the R36S says its first setup can take up to 10 minutes. Give it 10 minutes.
• Don't expand EASYROMS yourself before the first boot. The ArkOS wiki says that makes the boot hang.
• Clicked Format in Windows after flashing? Flash the image again.
• Check your flashing tool. The ArkOS and dArkOS wikis say not to use balenaEtcher. dArkOSen supports only Rufus and says reflashing with Rufus fixes most odd behaviour.
• Charger on or off? Builds disagree: dArkOSRE-R36 says unplug it for the first boot, ArkOS4Clone says plug it in. Follow your build.
• Still stuck after a careful reflash? Replace the card.

Why is there no sound?

1. Turn the volume up with the volume buttons.

2. On the dArkOS R36S builds, Hotkey + L3 toggles mute. Press it again.

3. Unplug headphones and test the speaker.

4. If only one game is silent, check that core's audio options or try another core.

5. After flashing a clone, no sound plus wrong buttons usually means the DTB doesn't match. Run the model selector again.

Why are the controls wrong or the sticks drifting?

• A and B swapped: dArkOSen swaps them by default and includes a Button Mapper to undo it. ArkOS-based cards offer Switch A/B under Start → Advanced Settings.
• Wrong in one game only: a RetroArch remap file is probably active. Reset or remove it in Quick Menu → Controls.
• DS, PSP or N64 controls odd: those standalone emulators have their own controls; see R36S controls and hotkeys.
• Sticks inverted on a clone: the DTB is wrong. ArkOS4Clone's DTB tool can remap joystick axes.
• Drift: we found no stick calibration tool in the ArkOS or dArkOS documentation. Raise the analog deadzone in RetroArch's input settings; dArkOSen adds a Joystick Deadzone setting under Advanced Settings, noting that stock devices use a very small deadzone. If drift shows everywhere, the stick itself is worn. The R36 Pro uses Hall-effect sticks.

Why are N64 and PSP games slow?

Some games are too heavy for the RK3326. Check the community R36S compatibility lists and the Nintendo 64 and PSP pages, then:

• N64: the ArkOS wiki says standalone Mupen64Plus usually performs best. If a game misbehaves, try a RetroArch core (parallel-n64 or mupen64plus_next) for that game.
• PSP: in PPSSPP, try frame skipping in the graphics settings. Lighter and 2D games run best.
• PS1: the ArkOS wiki says to keep rewind and fast forward off.
• CPU governor: ArkOS defaults to performance; check it isn't set to powersave under Start → Advanced Settings.
• Shaders and overlays cost speed; turn them off.

Where did my saves go?

On ArkOS-family firmware, saves and save states sit next to the game in its system folder (GBA .srm and .state files in gba, for example). So:

• They follow the card. Switched to or from a TF2 games card? Your saves are on the other card.
• Names must match. A save is tied to the game's file name, so renaming the game loses the link. DS saves are .dsv files in nds/backup.
• Some emulators keep their own folders. PPSSPP stores PSP saves in psp/ppsspp/PSP/SAVEDATA; Dreamcast saves made through retrorun go in bios/dc.

See how to save on the R36S for backing them up.

Why isn't my SD card detected?

• On a computer: if only a small BOOT drive appears, give the EASYROMS partition a drive letter in Windows Disk Management. Windows can't read the Linux system partition, so never format it when asked.
• On the R36S: a new games card must be formatted first (exFAT is the safe choice), labelled something other than EASYROMS and inserted with the device off. Then use Options → Advanced → Switch to SD2 for Roms.
• Still nothing: test the card in a computer. Fake and failing cards are common; use a name-brand one.

To start fresh, the dArkOS install guide covers reflashing.

Sources: ArkOS FAQ (RG351MP, the base for R36S ArkOS), ArkOS emulators and ports list, dArkOSRE-R36 firmware installation, libretro FBNeo