R36H Troubleshooting: Start With Reversible Checks
A black screen, missing games or crackling audio is a symptom, not a confirmed diagnosis. R36H-labelled handhelds and firmware projects vary. Record the exact board revision, installed firmware and when the problem began before changing files or settings.
First: Preserve a Known Working Setup
Power off before removing a card. Note which card belongs in which slot and keep any working original card unchanged. Back up saves and settings; if you may need the bootable setup later, make a full-device image as described in our SD card setup guide. Test one change at a time on a separate card. If neither the original nor the new card works, do not assume the new image is the only cause.
Black Screen or Stuck on a Logo
Did the symptom start immediately after flashing a new image? First compare with the untouched original card. Then verify the downloaded image and any published checksum, the firmware project's supported-device list and the exact motherboard marking. A display configuration mismatch is one possible explanation, but a card, image, power or hardware issue can look similar. Do not swap random DTB files across boards. Follow the current instructions for your specific project and revision; our screen diagnosis guide gives a fuller sequence.
Games or Saves Missing
Check whether the affected game or save is on the system card or a second card, and whether that card is mounted in the firmware's expected location. Check available space and whether other files can still be read. If you suspect a replacement card is misreporting capacity, test the empty replacement with F3's write/read method before copying data. Do not run a write test over your only copy of saves. One missing game can also be caused by that core's supported formats, folder layout or required firmware files; consult the core and firmware project's documentation for the exact combination. Use only game and BIOS files you have the right to use.
Hotkeys or Controls Do Not Work
Check whether the issue occurs in the main menu, one emulator or every emulator. Revert any recent controller remapping before choosing another device profile. The dArkOSRE project notes identify R36H-specific control mapping as an area requiring care; that does not make a generic “R36H” profile the right setting for every image. Use the mapping instructions for the exact firmware release you installed.
No Sound or Crackling Audio
First check the device volume, mute state and whether the symptom occurs in the menu, one core or all cores. If it started after a configuration change, restore the previous setting and compare. Libretro's troubleshooting guide notes that video and audio synchronization can contribute to crackling; it does not prescribe 48 kHz as a universal R36H fix. Change audio settings only with a recorded baseline and the relevant firmware/core guidance.
Power or Battery Behavior
Record whether the unit fails to power on, shuts down under load or simply runs for less time than expected. Compare the same game, brightness and charge state before drawing a conclusion. A shorter session alone does not identify a failing battery. If the unit becomes unusually hot, the battery is swollen or charging behaves abnormally, stop using and charging it and seek qualified device support rather than continuing software tests.
When to stop troubleshooting
If the board revision is unknown, the firmware project does not list it, or the original card also fails, preserve your backups and ask the seller or project maintainer for model-specific guidance. A successful card test does not certify firmware compatibility.