R36H Troubleshooting Guide
Having issues with your R36H? This guide covers the most common problems and their solutions.
Black Screen on Boot
Cause: Display panel DTB mismatch with custom firmware.
Fix: See our screen fix guide for panel identification and correct DTB files.
SD Card Corruption
Cause: Low-quality stock SD card failure.
Fix: Replace with a SanDisk Ultra or Samsung EVO Select card. See our SD card guide.
Games Not Loading
Cause: Wrong ROM format or corrupted files.
Fix: Ensure ROMs are in the correct format for each emulator. Use verified ROM sources.
No Audio
Cause: Audio settings misconfiguration in RetroArch.
Fix: In RetroArch, set Audio Output Rate to 48000 and adjust Audio Latency.
Battery Draining Fast
Cause: High brightness or demanding emulators.
Fix: Lower screen brightness, close background processes, use lighter emulators for less demanding platforms.
Start With The Card
Before working through symptoms individually, it is worth knowing that a large share of problems on these handhelds — missing games, lost saves, failures to boot, apparently random crashes — trace back to a failing or counterfeit microSD card rather than to firmware or emulator settings. If you are still using the card that came in the box and something is behaving strangely, replacing it resolves the issue more often than any amount of configuration.
Common Symptoms
| Symptom | Usual cause | First thing to try |
|---|---|---|
| Black screen after flashing firmware | Display panel mismatch | Swap the device tree file |
| Games disappear between boots | Card failing or counterfeit | Verify the card, then replace |
| Saves do not persist | Card write failure, or exiting without saving | Use the exit hotkey properly |
| Hotkeys do nothing | Device type set incorrectly | Set the profile to R36H |
| A single game will not start | Wrong folder, format, or missing BIOS | Check all three in order |
| Audio crackles | Emulator audio rate mismatch | Set the output rate to 48000 |
| Battery drains unusually fast | Demanding system, or high brightness | Compare against a light system |
When Only One Game Misbehaves
This narrows things down considerably, because the device and firmware are evidently fine. The cause is nearly always one of three things: the file sits in the wrong platform folder, its format is not one the emulator for that system accepts, or the system requires a BIOS file that is not present. Neo Geo, Sega CD, Dreamcast and Famicom Disk System titles all fall into that last category, and the error messages they produce rarely mention the BIOS directly.
Returning To A Known State
Because the operating system lives entirely on a removable card, recovery on this device is unusually painless. Putting the original card back returns you to exactly the factory condition, with nothing on the hardware itself to undo. Any experiment you make on a second card is therefore reversible in seconds, which is worth remembering before assuming something is broken.
Change one thing at a time
When several settings are adjusted at once and the problem persists, it becomes impossible to tell which change helped. Reverting to defaults and moving in single steps is slower but reaches an answer sooner.