R36S Handheld User Guide (Setup, ArkOS, Games, & More)

You’ve got an R36S in your hands, maybe a pile of SD cards on your desk, and a bunch of questions you don’t want to learn the hard way. This r36s handheld guide style walkthrough is meant to take you from first charge to a stable ArkOS setup, then into the daily stuff: adding games and BIOS, using RetroArch without getting lost, learning Quick Menu basics, and fixing the classic white or black screen boot problems when they show up.

It’s beginner-friendly on purpose. No Linux deep-dives. No “just compile this script” nonsense.

I’ve spent dozens of hours in community discords and subreddits, and the consensus is clear: the R36S is a beast, but it’s a ‘fiddler’s console.’ Don’t be discouraged if you have to tweak a setting twice to get it perfect, that’s just part of the hobby.

Quick safety note before you start: back up your saves, avoid bargain-bin microSD cards, and never interrupt firmware updates mid-process. Stock cards are famous for corruption and weird boot behavior, so treat them like temporary transport, not long-term storage.

Table of Contents

Quick Summary: How to set up R36S

If you just pulled your device out of the box and want the “fast-track” version of how to set up r36s, follow these five essential steps:

Charge the Device: Use a standard 5V/1A or 5V/2A phone brick (avoid fast chargers).
Replace the SD Card: The stock card is unreliable. Buy a branded 64GB or 128GB MicroSD card.
Flash the Firmware: Download the latest R36S ArkOS image and use a tool like Rufus to “burn” it to your new card.
Insert and Boot: Place the card in the TF1 slot and turn the device on; let it run its initial “resizing” process (takes ~5 minutes).
Add Your Games: Pop the SD card into your PC and move your ROMs into the corresponding system folders in the EASYROMS partition.

For a detailed, step-by-step walkthrough of each of these points, keep reading below.

R36S Basics (What You Bought)

First, a tiny mental model that’ll save you hours later.

On the R36S, you’re usually dealing with three layers:

Frontend: the “console menu” you browse systems and games in (themes vary)
Emulator layer: often RetroArch (a universal emulator hub)
Cores: the actual emulators RetroArch loads per system (NES, SNES, PS1, etc.)

Now the file types, in plain English:

ROMs: the game files themselves (cartridge dumps, disc images, archives)
BIOS: small firmware files some systems need to boot or run correctly (common with PS1 and certain arcade setups)
Saves: the in-game save files made when you use the game’s own save option
Save states: “freeze point” snapshots made by the emulator (amazing, but not a replacement for real saves)

One more thing people don’t expect: button combos and menu names can differ depending on firmware, RetroArch version, and even the theme you’re using. So you’re not crazy if your friend’s shortcut doesn’t match yours.

How to set up R36S: What You Need Before Starting

A smooth setup is mostly about avoiding cheap accessories and rushed decisions.

Recommended basics:

A quality microSD card (or two): name brands matter here
A decent SD card reader: the throw-in readers are often unreliable and can corrupt transfers
A basic charger setup: more on this in the charging section, because yes, it’s picky on many units
Optional for online features: a compatible Wi‑Fi dongle plus a USB‑C adapter (OTG), since most R36S units don’t have built-in Wi‑Fi

One-card vs two-card decision (high-level):

One card: simplest, fewer moving parts, easiest for beginners
Two cards: more flexible, safer for ROM management, and you can re-flash the OS without touching your library

If you’re still deciding whether the R36S is the right budget handheld, see the R36S review and retro handheld guide here:
R36S review and retro handheld guide

Charging and First Boot

Do this first: charge it up before you start flashing firmware or moving files around. You don’t want a low battery shutting down mid-setup.

Steps:

Charge fully before long setup work
Expect the first boot to take longer than later boots, especially after a fresh flash or first-time configuration

Charging can be surprisingly specific on these devices. Some units won’t charge from modern USB‑C to USB‑C fast chargers, and a basic USB‑A to USB‑C cable plus a simple 5V brick is often the reliable combo.

If you want the safest charging basics (including which port to use), use this:
how to charge the R36S

SD Cards (The #1 Reliability Upgrade)

If you do only one upgrade, do this one.

The stock microSD cards that ship with many R36S units are widely considered failure-prone, and they’re a common cause of boot loops, freezes, and “it worked yesterday” headaches. A new, reputable card fixes a shocking percentage of issues before they even happen.

Sizing guidance (keep it practical):

One-card setup: pick a size that fits both the OS and your library (often 64GB to 256GB depending on how much PS1/ports you want)
Two-card setup: smaller OS card is fine (16GB to 32GB is usually enough for ArkOS), then size SD2 based on your ROM collection

Backup mindset (seriously):

Keep a clean “freshly working” image/backup before experimenting
Back up saves regularly, especially before updates or major settings changes

Common mistakes (that cause real pain):

Not ejecting the SD card safely before pulling it from your PC
Copying ROMs into the wrong system folder
Mixing OS files and ROM files across cards, then wondering why nothing boots

Firmware Overview (Stock vs ArkOS)

Stock firmware can be fine if your device is stable and you genuinely don’t want to tinker. If it boots, plays what you want, and you’re not chasing features, staying stock is a valid choice.

ArkOS is popular because it tends to bring a more mature “handheld Linux” experience: better performance tuning, more features, and a clearer maintenance path, especially when paired with a good SD card.

If you want the dedicated walkthrough, use this internal guide:
install ArkOS on R36S

ArkOS Install (Step-by-Step)

You want a boring, repeatable process. That’s the goal.

High-level sequence:

Download the ArkOS image you plan to use (many people use stable community-maintained builds for the R36S)
Extract the archive using an archive tool (7zip-style utilities are common)
Flash the image to your microSD card using an imaging tool (common options include Rufus or Win32DiskImager)
Insert the flashed card into the correct slot (your OS slot)
First boot, let it do its initial setup

When you first turn it on after flashing, you’re going to see a wall of white text scrolling faster than you can read. It looks like you’ve broken something or entered a developer mode. Relax. It’s just the system resizing your SD card partitions so you can actually fit your games on there. Grab a coffee; it’ll be done in about 5 minutes.

Important: flashing is not drag-and-drop. The imaging tool creates bootable partitions (commonly a BOOT partition and an EASYROMS-style partition) that your computer can recognize correctly.

Stop here and verify:

It boots to the ArkOS menu
Controls respond (D-pad, buttons, sticks)
The EASYROMS (or equivalent) partition appears on PC when inserted

If any of those fail, pause before you start copying ROMs. Fix the base first.

Boot Fixes (White Screen / Black Screen)

These two problems are so common they deserve their own section.

The short version: R36S hardware can ship with different screen panels, and if your OS image doesn’t match your panel configuration, you can get a white screen or a black screen even though the device is “on”.

White screen fix (DTB/boot files workflow)

Symptom: the device boots, but the display is white, washed-out, or clearly wrong right from startup.

Why it happens: the display configuration doesn’t match what your firmware expects, commonly tied to DTB (device tree blob) or related boot files. The DTB helps the OS understand the hardware configuration, including the screen.

Steps (generic workflow you can follow):

Power off, remove the OS SD card, insert it into your computer
Open the BOOT partition
Locate the DTB-related files (they often end in .dtb, and names may include rk3326 variants)
Replace the relevant DTB/boot files with the set intended for your screen panel, following any rename requirement (some sets must be renamed to the “active” filename)
Eject safely, put the card back, boot again

Take your time here. Most “I broke it” moments are really “I didn’t eject properly” moments.

Black screen fix (alternate DTB sets)

Symptom: the screen is black, but the LED indicates the unit is powered (often a blue light), and you might even hear audio.

Solution approach: try the alternate or “new panel” DTB sets until one works. This is normal, because manufacturers swap screen panels without warning, and the correct DTB is what makes the screen output appear.

If still stuck:

Re-flash the ArkOS image to the SD card (bad flash happens)
Try a different SD card (stock cards are a repeat offender)
Verify you’re using the correct slot for the OS card (easy to mix up when you’re frustrated)

One SD vs Two SD Setup (Choose Your Path)

This is where most new owners get confused, because the device has two slots, and ArkOS can use either for ROM storage.

One-card setup

Where ROMs/BIOS go: on the same card as the OS, using the EASYROMS folder structure (or similarly named ROM partition).

Pros:

Simplest to understand
Fewer settings to toggle

Tradeoff: if you ever need to re-flash the OS card, you’re juggling OS and ROMs together, which raises the “oops” risk.

Two-card setup

This is the cleaner long-term setup for a lot of people.

Workflow:

Keep ArkOS on SD1 (OS slot)
Format SD2 as exFAT, then tell ArkOS to use SD2 for ROM storage
ArkOS typically has a menu option that populates SD2 with the correct folders (often found under Options > Advanced with wording like “Switch to SD2 for ROMs”)

Pros:

ROM management is easier
Less risk to your OS card
If ArkOS breaks, your library stays untouched

Add Games, BIOS, and Verify They Show Up

This is the fun part. It’s also where “nothing shows up” panic tends to happen.

Basics that prevent 90% of issues:

Put ROMs in the correct system folder (nes, snes, gba, psx, etc.)
Put BIOS files in the BIOS folder your setup expects (often a bios directory under the ROM partition)
Keep filenames clean when you can, scraping tools and some emulators behave better

If games don’t appear immediately, you usually need to refresh the lists. Many setups have a menu option like “Update Games Lists” or “Refresh Roms”. There’s also a setting that can hide new files if it’s enabled, often called something like “Parse Gamelists Only”. Turning that off will show your files even before scraping metadata.

Use these internal guides for the full walkthrough and a compatibility sanity check:

Optional but useful: curated sets (like Tiny Best Set) can be a great shortcut, just pick a size that fits your SD card and don’t overload yourself with 20,000 games you’ll never touch.

Menu Tour (So You Don’t Get Lost)

Spend two minutes learning the layout and you’ll enjoy the device way more.

Most frontends have:

A systems list (choose a console, then choose a game)
Favorites (your real library, let’s be honest)
Recently played (fast way back to your current obsession)

Library organization tip that works: favorite first, browse per-system second. You’ll actually play more, and you’ll spend less time scrolling through junk you added “just in case”.

RetroArch Fundamentals (You’ll Use This Daily)

RetroArch is the control center. Once you get it, the R36S stops feeling mysterious.

A “core” is basically the emulator RetroArch loads. Same system can have multiple cores, and they can behave differently (speed, accuracy, compatibility). This is why “my friend’s PS1 runs fine” doesn’t always help, you might be on different cores.

Settings are layered:

Global settings: apply everywhere
Per-core options: apply only to that emulator core
Per-game overrides: apply only to one title

Save states vs in-game saves:

Save states are perfect for quick checkpoints, tough platforming, and testing settings
In-game saves are safer for long-term progress, RPGs, and anything that tracks internal game flags

Do this once:

Set a hotkey button (Select is commonly used as the hotkey enable in many setups)
Make sure settings persist by saving configuration (the wording varies, but the concept is “save config” so your hotkeys don’t vanish next boot)

How To Exit Game

Exiting the wrong way is one of the fastest routes to corrupted saves, especially on sketchy SD cards. So here’s the safe approach, then the faster approach.

Safe exit (recommended):

Open the Quick Menu (method depends on your mapping)
Choose Quit/Close Content (wording varies by core)
Wait a second, return to the frontend

Fast exit:

Use a hotkey combo, but don’t guess. Go into RetroArch settings and confirm the exact mapping on your device first, because firmware images and controller profiles differ.

If exit hangs:

Give it a moment
Try the menu again
Reboot only if you have to (forced power-offs are hard on file systems)

Warning: save in-game before you exit when possible, especially after long sessions. Stock cards fail often, and save states aren’t a perfect substitute.

How To Access Quick Menu R36s

Quick Menu is where the good stuff lives: save/load states, controls, shaders, core options, and quitting content safely.

Typical access routes:

A dedicated menu/function button (if your image mapped one)
Hotkey + button (common pattern is Hotkey Enable + X/Y/Start, but confirm in your settings)

If Quick Menu won’t open:

Check RetroArch hotkey settings (Hotkeys section)
Confirm your input device is mapped correctly (some builds ship with odd defaults)
If one core behaves differently, it may be using a different RetroArch instance or core-specific input profile

Once you learn this, everything else (fast-forward, shaders, remaps) becomes much easier.

Can You Fast Forward On R36s?

You can, as long as the emulator/core supports it and you map the control.

How to enable it (the repeatable way):

Open RetroArch settings
Find Input, then Hotkeys
Assign Fast-Forward Toggle or Fast-Forward Hold (hold is easier to control)
Save configuration so it sticks

Tips that matter in real life:

Prefer hold fast-forward. It prevents “oops I left it on” chaos.
If speed is unstable, reduce shaders or heavy filters, they can tank performance.
Some systems (like PS1) can fast-forward well, others depend heavily on core choice and settings.

Many setups don’t ship with a fast-forward mapping by default, so don’t assume it exists. Map it once, then you’re set.

Display & Comfort Settings

These are the tweaks you’ll use every day, not the fancy stuff.

Look for:

Brightness and volume controls
Sleep behavior (some firmwares do better with full shutdown than sleep, especially if your SD card is questionable)
Aspect ratio/scaling: keep it simple at first. If a game looks stretched, try “Core Provided” or “4:3” for older consoles

If you change a setting and it keeps resetting after reboot, that’s usually a “config didn’t save” situation, sometimes tied to SD card problems or permissions issues.

How To Adjust Brightness On R36s

You’ll typically have two ways to do this, depending on firmware and theme.

Method A (recommended): system settings path

Open your frontend’s main menu (often Start)
Find Settings (or System Settings)
Look for Brightness, then adjust and back out, making sure it saves

Method B (shortcut): only if your firmware supports it

Some builds map brightness to a button combo
Phrase to remember: if it works, great. If it doesn’t, don’t waste an hour hunting ghosts, just use the settings path

Troubleshooting:

Brightness resets after reboot: your configuration might not be saving, or your SD card may be acting up
If you’re still on the stock SD card, treat weird “settings not sticking” behavior as an early warning sign

Wi‑Fi Setup (If You’re Using a Dongle)

Most R36S units need a Wi‑Fi dongle for connectivity.

What you need:

A compatible Wi‑Fi dongle
A USB‑C adapter that supports OTG

Basic process:

Plug the dongle into the correct USB-C port (often labeled OTG on many units)
Boot ArkOS
Find Network/Wi‑Fi settings in the ArkOS menus
Select your network and enter your password

If it doesn’t detect the dongle, try a different adapter first. The adapter is often the weak link.

Updating ArkOS (Do It Safely)

Updates are useful. They can also be the moment things go sideways if you rush.

Rules that keep you out of trouble:

Update via the built-in updater after Wi‑Fi is configured
Don’t interrupt the process
Reboot after the update, then verify key systems still launch

One real-world gotcha: OTA updates can sometimes reintroduce screen DTB problems depending on how the update handles boot files, so if you’ve had a black screen issue before, keep your working DTB files backed up.

Scraping Box Art and Metadata

Scraping is optional, but it makes the device feel finished.

Common expectations:

You’ll usually need a ScreenScraper account
You’ll pick a box-art style (2D box art is a popular choice)

Tips to improve scrape accuracy:

Clean ROM naming helps
Scrape per system first instead of “scrape everything overnight”, it’s easier to spot mistakes early
If games aren’t appearing, fix that before scraping (scraping won’t solve folder/path issues)

RetroAchievements (Optional)

If you care about achievements, this can be a fun rabbit hole.

Basic idea:

Create a RetroAchievements account
Enable achievements in RetroArch settings

One quirk: some setups require you to configure this in each RetroArch instance (for example, if different systems launch different RetroArch builds). If achievements work in one system but not another, that’s usually why.

PortMaster (Optional Ports)

PortMaster is where “ports” come in, meaning fan-made or officially packaged versions of games that run natively on the device (not emulated the usual way).

What to expect:

Not every port works on every firmware image
Some ports require extra files (game data) that you legally provide from a PC install

Keep your first attempt simple: install, launch, confirm controls, then expand. If you want deeper PortMaster coverage later, it’s a great candidate for a dedicated post.

How To Factory Reset R36s

“Factory reset” means different things on handhelds like this, so let’s clarify the levels.

Soft reset (first-line fix):

Reset RetroArch or emulator settings back to default, especially if controls or video settings got weird

Medium reset:

Reset ArkOS UI settings, then reconfigure hotkeys and any frontend options you changed

True “factory reset” (the real one):

Re-flash the OS SD card with a fresh ArkOS image, then restore ROMs/saves from your backup. This is better described as reinstalling firmware, because the OS lives on the SD card.

Back up first:

In-game saves folder(s)
Save states folder(s)
Any scraped media folders
Your config overrides (if you’ve customized heavily)

If you don’t back these up, your “reset” becomes a “start over”, and that’s rarely what you wanted.

Troubleshooting (Most Common Issues)

This is the section you’ll come back to later. Bookmark it mentally.

Won’t boot (black/white screen) recap:

Black screen with blue light often points to DTB mismatch with your screen panel
White screen often points to display config mismatch, also commonly DTB/boot file related
Jump back to the DTB workflow above and take it slow

Games not showing up:

Confirm folder and extension match the system/core
Confirm ROMs are on SD2 if you switched to SD2 for ROM storage
Refresh/update game lists, and check any “parse gamelists only” setting that can hide new files

Can’t save games:

Bad SD card is a prime suspect, especially stock cards
Wrong folder paths or permissions can also block writes
Test with a different card if saves fail across multiple systems

Controls wrong in one emulator:

This is often a core remap vs global remap issue
Fix at the narrowest level possible (per-core or per-game) so you don’t break controls everywhere else

If you notice your character moving on their own (ghost inputs), it’s usually not a software bug. Because these are budget sticks, sometimes a tiny bit of dust gets in there. Try rotating the sticks firmly in a circle for 30 seconds while the power is off, it sounds silly, but it often clears the contact without needing to open the shell.

Performance issues:

Try a different core for that system
Reduce shaders and fancy filters
Use frameskip as a last resort, not the first move

Why is my battery dead when I charged it last night?:

One thing that trips up new owners: the power button. A quick tap puts it in ‘Sleep,’ but on these budget chips, sleep mode still drains the battery faster than you’d expect. If you’re putting it away for the night, always use the Menu > Quit > Shutdown method. Your battery (and your save files) will thank you.

For a deeper “fix it now” list (including charging and LED behavior), use the internal R36S troubleshooting guide:
R36S troubleshooting guide

Quick Reference Cheat Sheet

Keep this section handy. It’s the stuff you’ll actually use.

Exit game (safe): Quick Menu → Quit/Close Content (wording varies)
Exit game (fast): use your hotkey combo, confirm mapping in RetroArch first
Open Quick Menu: menu/function button if mapped, or Hotkey Enable + mapped button
Save state / Load state: Quick Menu → Save States
Fast forward: map Fast-Forward Hold or Toggle in RetroArch Hotkeys, save config
Brightness path: frontend menu → Settings/System Settings → Brightness
If it won’t boot:
- White screen: treat as boot/display config mismatch, swap correct DTB/boot files
- Black screen + LED on: try alternate/new-panel DTB sets until one works

Final Thoughts

If you do three things after reading this: replace the stock SD card, flash a stable ArkOS image, and learn Quick Menu plus Quit Content. Those alone remove most day-to-day frustration on the R36S.

When you’re ready for the next step, use the internal deep dives you’ll actually need:

install ArkOS on R36S
add new games to your R36S
Check your titles against the R36S compatible games list

That’s the whole point of this r36s handheld guide approach: get you stable first, then help you level up one feature at a time.

Once you’ve got your box art scraped and your favorite childhood game running at a smooth 60fps, take a moment to just look at it. You’ve just built a library of thousands of games for the price of a dinner out. That’s the magic of the R36S.