ArkOS R36S Download & Complete Setup Guide
There's no official ArkOS image for the R36S. R36S owners use community builds based on ArkOS, mainly ArkOS-R3XS and ArkOS4Clone, which add the device files (DTB files) for R36 boards and screens. You write the image to the TF1 card with a raw image writer such as Rufus, USB Image Tool or ApplePi-Baker, not balenaEtcher, and the first boot sets up the EASYROMS games partition by itself.
ArkOS is no longer maintained. The ArkOS wiki, written by its developer christianhaitian, says dArkOS has replaced it and that the repository is kept for historical purposes only. ArkOS keeps working, but it won't get updates. For the maintained successor, see dArkOS on the R36S.
Bought a rebranded clone instead of an R36S-labelled unit? See ArkOS on clone handhelds. Weighing ArkOS against ROCKNIX or stock firmware? See the R36S custom firmware comparison.
What is ArkOS?
ArkOS, short for "Another Rockchip Operating System", is a Linux-based firmware for Rockchip handhelds. According to its wiki:
- It started as a fork of The Retro Arena and is based on Ubuntu 19.10.
- It emulates over 90 systems and supports over 800 ports through PortMaster.
- Its menu is EmulationStation-FCAMOD, with RetroArch running most emulators.
- Games and BIOS files sit on an exFAT partition called EASYROMS, which Windows, macOS and Linux can open without extra software.
Most R36S units already ship with an ArkOS-based card. A fresh install is worth it when the stock card fails, when you want a clean menu, or when you move to a better card.
Which ArkOS image works on the R36S?
The download list on the ArkOS wiki covers devices such as the RG351MP and RG351V, not the R36S. Its R35S entry points to a community image, ArkOS-R3XS, as the more up-to-date option. Don't flash an image made for another handheld: the R36S needs device files that match its own board and screen, and the official images don't include them.
| Image | Maintainer | Made for (per its README) | Status |
|---|---|---|---|
| ArkOS-R3XS | AeolusUX | R33S, R35S, R36S and R36H in one multi-panel image, plus a separate R36S Plus image | Listed as archived versions, labelled ArkOS 2.0 |
| ArkOS4Clone | lcdyk0517 | R36S units and other clone handhelds | Community project, also offered as dArkOS4Clone |
| dArkOSRE-R36 | southoz | Genuine R36S boards and several clones, based on dArkOS | Maintained; see our dArkOS guide |
The ArkOS-R3XS README now points R36S owners to ArkOS4Clone for an updated ArkOS and to dArkOSRE-R36 for dArkOS. All three are on GitHub: ArkOS-R3XS, ArkOS4Clone and dArkOSRE-R36. Read the project's notes and check that your board is listed before you flash. The R36 Max, R36S Ultra and R36 Pro aren't in the ArkOS-R3XS list.
What about "ArkOS 2.0"? That's the version label on the archived ArkOS-R3XS images, not a new official ArkOS release.
What do you need before you start?
- A microSD card for the system. The ArkOS wiki asks for at least 8 GB and highly recommends 16 GB or more. It warns that low-quality and no-name cards tend to fail quickly or refuse to boot, so use a name brand such as SanDisk, Samsung or PNY.
- A card reader and a computer running Windows, macOS or Linux.
- 7-Zip or another extractor for the compressed image.
- A raw image writer. The ArkOS wiki recommends USB Image Tool on Windows (Win32 Disk Imager also works), ApplePi-Baker or dd on macOS, and the Disks app or dd on Linux. The dArkOS wiki recommends Rufus on Windows.
- A backup of your original card. It holds the DTB files for your exact board and screen. The R36S SD card guide shows how to image it.
Both the ArkOS and dArkOS wikis say do not use balenaEtcher with these images, citing strange issues and inconsistent performance.
How do you flash ArkOS to the SD card?
1. Download the image for your device from the project's release page, and check its hash if the page publishes one.
2. Extract the .img file with 7-Zip.
3. Open your image writer, select the microSD card (double-check the drive letter) and write the image. This erases the card.
4. If Windows then offers to format the card, click Cancel. Formatting wipes the install.
5. Don't resize the EASYROMS partition yourself. The ArkOS wiki says expanding it before the first boot makes the boot hang.
What happens on the first boot?
1. Insert the flashed card in TF1, the system slot, and leave TF2 empty until setup is done.
2. Power on. ArkOS expands the games partition to fill the card, converts it to exFAT and reboots, usually twice. The ArkOS-R3XS README says this first setup can take up to 10 minutes. Don't power off early.
3. Setup is finished when the EmulationStation menu appears.
4. On the ArkOS-R3XS multi-panel image, a wrong or blank picture usually means the screen panel doesn't match. Once the first setup has finished, power on while holding R1 and a D-pad direction (or R1 and A for the stock panel) to pick another one, as its README describes.
Our troubleshooting guide covers other black-screen and boot-logo causes.
Where do BIOS files go on ArkOS?
BIOS files go in the lowercase bios folder on the EASYROMS partition, which the device sees as /roms/bios. If you move your games to a second card with Switch to SD2 for Roms, the ArkOS emulator list says all BIOS files go in the bios folder on that second card (/roms2/bios). Dreamcast files go one level down, in bios/dc.
| System | Need | File name | Folder |
|---|---|---|---|
| PlayStation 1 | Recommended | scph1001.bin (or scph5501.bin, scph7001.bin, scph101.bin) | bios |
| Sega CD | Required | bios_CD_U.bin, bios_CD_E.bin or bios_CD_J.bin, by game region | bios |
| PC Engine CD | Required | syscard3.pce | bios |
| Neo Geo | Required | neogeo.zip, kept zipped | bios and neogeo |
| Dreamcast | Recommended | dc_boot.bin (ArkOS also lists dc_flash.bin) | bios/dc |
| PSP, N64, NES, SNES, Mega Drive | None | โ | โ |
ArkOS runs on Linux, so names are case-sensitive: copy them exactly. This site doesn't host, link to or say where to find BIOS files; dump them from consoles you own. The R36S BIOS files guide has the full list, plus MD5 checksums to verify your dumps.
How do you add games after installing ArkOS?
- One card: shut down with Start โ Quit โ Shutdown, put the TF1 card in your computer and open the EASYROMS drive. If Windows shows only a small BOOT drive, give EASYROMS a drive letter in Disk Management.
- Two cards: format the games card as exFAT with its own label (not EASYROMS) and insert it in TF2 with the device off. Then open Options โ Advanced โ Switch to SD2 for Roms. ArkOS creates the folders but doesn't copy your games across, and from then on it needs both cards in place to boot.
- Folder names are short and lowercase:
psxfor PS1, thenn64,snes,gba,megadrive,arcadeand so on. Don't delete folders that look empty; some hold files the PSP and DS emulators need. - Use games you own. Copy your own dumps into the matching folder, then reboot so EmulationStation picks them up.
The SD card guide lists every folder and file type, and how to add games to the R36S walks through the copying.
What are the ArkOS controls?
These are the ArkOS defaults for games that run in RetroArch. ArkOS-R3XS points R36S owners to the ArkOS FAQ for the RG351MP for them.
| Action | Buttons |
|---|---|
| Open the RetroArch menu | Select + X |
| Save state | Select + R1 |
| Load state | Select + L1 |
| Exit to the game list | Select + Start |
| Reset the game | Select + B (unsaved progress is lost) |
| Brightness | R3 + D-pad Up / Down |
| Safe shutdown | R3 + Power, or Start โ Quit โ Shutdown |
In the game list, Start opens the main menu, and Select opens options for the highlighted game, including which emulator it uses. The dArkOS R36S builds use a different layout; see R36S controls and hotkeys.
How do you get the best performance on ArkOS?
- N64: the ArkOS wiki says standalone Mupen64Plus usually performs best. If one game misbehaves, switch just that game to a RetroArch core such as parallel-n64 or mupen64plus_next.
- PSP: PPSSPP runs lighter and 2D games best; try frame skipping in its graphics settings for heavier ones.
- PS1: PCSX-ReARMed runs nearly the whole library at full speed. Use a real BIOS, and keep rewind and fast forward off, as the ArkOS wiki advises.
- Everything else: leave the CPU governor on performance (Start โ Advanced Settings) and turn off shaders and overlays.
The limits are the same on every R36 model, from the R36S to the R36S Ultra, because all of them use the RK3326 with 1 GB of RAM. Check single games in the game list and the R36S emulator list, compare models on the comparison page, or start with the best R36S games.
What if something goes wrong?
- Games don't appear: usually the wrong folder or file extension. Reboot, then check the SD card guide's tables.
- A game won't start: often a missing BIOS or an arcade ROM set made for another emulator version.
- Stuck at the logo or a black screen: give the first boot 10 minutes, then reflash with one of the recommended writers and make sure the image matches your board.
The R36S troubleshooting guide goes through each fix.
Sources: ArkOS wiki, ArkOS FAQ for the RG351MP, ArkOS emulators and ports list, ArkOS-R3XS README, dArkOS wiki
Related topics: