R36S Not Working? 12 Common Problems and How to Fix Them

The R36S is a Linux handheld running a community firmware (usually an ArkOS-style build) from a microSD card, and that card is the single point of failure behind most of what goes wrong. Reseating or replacing it resolves the majority of faults; almost everything else is a setting rather than a broken console.

Below are the 12 problems owners hit most often, fix first. Menu names and button combinations vary between firmware versions, so treat the paths here as a guide and check the menu on your own unit.

1. The R36S will not turn on or charge — what now?

Plug it in and leave it 15–30 minutes before concluding anything. A completely flat lithium battery does not respond to the power button straight away, and the charge LED does not light on every firmware version, so an unlit console is not proof it is dead.

If it still does nothing, swap the cable and plug: community guides consistently report that some units charge reliably only from a standard USB-A to USB-C cable in an ordinary 5V phone plug. Check the port too — where there are two USB-C ports, one is OTG only and they look identical. If it is frozen rather than flat, hold power for 10+ seconds, then restart.

2. Why is my R36S stuck on the boot logo or showing a black screen?

Nine times out of ten it is the microSD card. Switch off, push the card in until it clicks and boot again — a card that has worked loose in a pocket or in transit is the most common cause of a dark screen.

If it still hangs, check whether the backlight is on: a lit but blank screen usually means the firmware is failing to start, which points at a corrupt card. If you have just written a new image, be patient — it expands itself to fill the card on first boot and can sit dark for several minutes. Never power off during that step.

Re-flashing means writing a fresh image from a computer with Rufus, Win32DiskImager or Raspberry Pi Imager, decompressing it first if it arrives as a .xz file. One R36S quirk is worth knowing: production batches use different screen panels, so a build made for another panel can boot black on a healthy console. Community ArkOS builds usually include a panel picker for this.

3. Why are my games not showing up after adding ROMs?

Check the folder first: a game only appears if it sits in the folder for its own system, so a SNES ROM in the nes folder will not show up. Then check the file type — .rar and .7z archives never work, and arcade ROMs must stay zipped while most other systems prefer unzipped files.

If both are right, force a rescan: open the settings with Start and look for Update Game Lists or Gamelist Refresh. If your firmware has no such option, a reboot scans anyway. Our walkthrough of adding games to the R36S lists every folder name and file type.

4. Why is there no sound?

Start with the obvious: volume up, nothing in the headphone socket, and sound present in the menu as well as in games. If the menu has audio but a game does not, the problem is that emulator, not the console.

In a RetroArch-based emulator, check Settings → Audio: audio must be enabled and the driver set to ALSA rather than null. Crackling rather than silence is usually cured by raising the audio latency. Some firmware builds have known headphone-jack quirks, so if the speaker works but headphones do not, look for an update to your build.

5. The buttons or controls are not responding — how do I fix it?

Work out whether it affects every game or just one. If it is one game, that emulator's mapping is wrong: open the in-game menu and check the input bindings. If it is everything, including the menu, run the controller calibration in the system settings.

A single dead button is usually dirt rather than failure — clean around it with a cotton bud lightly dampened with isopropyl alcohol and let it dry fully. If it stays unresponsive after that and a reboot, treat it as a hardware fault and contact GameBro support.

6. Where have my save files gone?

Almost always because the console was switched off mid-game. Save data is written when a game closes cleanly, so exit through the in-game menu (the hotkey shown on screen, commonly Function + Start) rather than flicking the power switch.

Two habits prevent a repeat: use the game's own save system as well as save states, and watch which save-state slot you are on. If saves vanish even after clean exits, suspect the card — a failing or counterfeit microSD silently loses writes.

7. Why is the battery draining so fast?

Screen brightness is the biggest single drain, and heavier systems cost more: a PSP or Dreamcast title works the chip far harder than a Game Boy Advance game. The 3500mAh battery is rated at 6+ hours, assuming moderate brightness on mid-weight systems.

Check you are switching it off rather than leaving it asleep, since sleep still draws power over days. A wildly jumping battery percentage is a separate, well-documented annoyance on ArkOS-based handhelds — usually a reporting bug, so judge the battery by how long it actually lasts.

8. How do I fix screen tearing?

Turn vertical sync on in the emulator's video settings (Settings → Video → Sync/VSync in RetroArch-based cores). If it continues, switch threaded video off in the same menu and restart the game. Tearing in the menus rather than in games is firmware-level, and a newer build is the fix — and it is worth trying the scaling and aspect-ratio options too, since an odd scaling mode can look like tearing when it is really uneven pixel scaling.

9. What do I do about SD card errors and corruption?

Stop using the card until you have backed it up: put it in a computer, copy everything readable, then write a fresh image. Never let Windows reformat an R36S card with the standard format tool — the card carries Linux partitions that Windows offers to "fix", and accepting destroys the system.

If corruption keeps returning, replace the card — counterfeit microSDs advertising a capacity they do not have are rife and fail exactly this way. Our guide to the best SD cards for retro handhelds covers what to buy.

10. How do I fix analogue stick drift?

Run the calibration tool in the system settings first — drift on a new unit is frequently a calibration issue rather than a worn stick. If a little remains, raise the analogue deadzone in the emulator's input settings; 0.15 to 0.20 is the commonly recommended starting point. Persistent drift after both steps points at the stick module, which is replaceable — but if the console is a GameBro purchase inside its 12-month warranty, contact support rather than opening it up.

11. Why does it freeze in PSP and Dreamcast games?

Because you have reached the hardware's limit, which is expected rather than a fault. The R36S is built around a modest Rockchip RK3326 chip: everything up to PS1, plus many N64 titles and a selection of Dreamcast and PSP games, runs well — the heavier 3D titles on those two systems do not, and no setting will change that.

Before giving up on one game, try frameskip in that emulator's menu, a lighter core if one is offered, and a lower internal resolution. If it still stutters, it is outside what this class of handheld does — the 16-bit and 32-bit libraries are where the R36S is at its best, as our 50 best games to play on your R36S shows.

12. How do I factory reset the R36S?

There are two levels. The gentle one is the reset option in the system settings menu, which restores the firmware's settings without touching your games. The path varies by firmware but usually sits under Start → System Settings.

The complete reset is re-flashing the card, which wipes whatever you write to. Copy your roms, saves and bios folders to a computer first, write the image with proper imaging software, and let the first boot finish. Then set it up as if new — our R36S setup guide covers the first charge, the hotkeys and the save system.

When is it a hardware fault?

If it will not charge from a known-good cable and plug, the screen stays dark with a freshly flashed card, a button or stick fails after cleaning and calibration, or the battery drops from full in under an hour, you are past what software can fix.

Every console GameBro sells ships from UK stock, is tested before dispatch, and carries a 12-month warranty against defects plus 30-day returns. Contact us through the GameBro support page with your order number and what you have already tried. If you are still shopping, the R36S is £34.39 and arrives configured and tested, not as a blank import.

The short version

Reseat the card, charge it properly, exit games through the menu, and keep a spare microSD. Those four habits prevent almost every problem in this guide.

Nearly everything that goes wrong with an R36S is a card or a setting, and both are recoverable. For anything genuinely hardware, that is what the warranty is for — get in touch through support.