dArkOS on the R36S: What Changed From ArkOS and How to Install It

dArkOS is the Debian-based successor to ArkOS, from the same developer, christianhaitian. ArkOS's own repository now says dArkOS has replaced it and that ArkOS is kept for historical purposes only. For an R36S owner, dArkOS keeps the familiar parts: the EmulationStation menu, RetroArch, the EASYROMS games partition and the same system and BIOS folders.

There's one catch. The official dArkOS releases don't include an R36S image. R36S owners install a community build based on dArkOS, then pick their board's device file (DTB) so the screen, buttons and sound work. This guide covers what changes, which build fits which unit, and how to install it without losing your games.

What is dArkOS?

The name is short for "Debian-based Another Rockchip Operating System". According to the dArkOS wiki:

• It's currently based on Debian Trixie, with both 64-bit and 32-bit software. ArkOS was based on Ubuntu 19.10.
• It emulates over 90 systems and supports over 800 ports through PortMaster.
• It uses the same menu as ArkOS, EmulationStation-FCAMOD, with RetroArch running most emulators.
• Games and BIOS files sit on an exFAT partition named EASYROMS, which Windows, macOS and Linux can open.
• It can update online without reflashing, unless a release makes major structural changes.

The goals shift slightly. ArkOS listed "ease of use"; dArkOS lists "enthusiast focused", and it's built so others can fork and modify it. That's why R36S builds exist at all.

Does dArkOS support the R36S?

Not directly. The newest official release on the dArkOS GitHub page at the time of writing, tagged v08272026, has images for the A10 Mini, G350, Miniloong, RG351MP, RG353M, RG353V, RG503, RGB10, RGB20 Pro, RGB30 and RK2023. None is an R36-series handheld.

R36S owners use community builds instead. Each starts from dArkOS and adds R36 device files:

These are independent community projects, not official dArkOS releases: dArkOSRE-R36, dArkOSen-R36 and ArkOS4Clone. Read the project's wiki before you flash, and check that your exact board is listed.

The clone caveat

Many handhelds sold as an R36S are clones with different mainboards and screens. The same image can show a blank screen on one unit and work on another once the right DTB is chosen. dArkOSen says plainly that it isn't compatible with clones, including the G80CA and Soy Sauce models. If your board isn't listed, dArkOSRE-R36 asks for the motherboard ID plus the .dtb files and boot.ini from your original card. Our guides to spotting a fake R36S and ArkOS on clone handhelds help you work out what you have.

dArkOS is built for Rockchip RK3326 and RK3566 chips, which covers every R36 model in our records. The few R36S Plus batches reported with an Allwinner chip fall outside it.

What changes when you move from ArkOS to dArkOS?

What that means in practice:

• Your games folders carry over. The folder names are the same, so a games card set up for ArkOS works once the new firmware is switched to it. The ArkOS wiki notes that the switch doesn't overwrite existing folders, games or BIOS files on that card.
• In-game saves carry over; save states may not. Saves sit next to the games. A save state made with an older emulator version may not load in a newer one, so make an in-game save before you switch.
• Hotkeys change. On the dArkOS R36S builds, Select + B saves a state; on ArkOS it resets the game. See R36S controls and hotkeys.
• Wi-Fi still needs hardware. The dArkOS FAQ says devices without built-in Wi-Fi need a compatible USB Wi-Fi adapter. In the R36 family, only the R36S Ultra and some R36S Plus batches have it built in.
• Same chip, same limits. Firmware doesn't change what the RK3326 can run. N64, PSP and DS stay game by game; the R36S emulator list explains why.

How do you install dArkOS on an R36S?

Before you start

1. Back up the card your R36S came with: a full image, plus the BOOT partition's .dtb files and boot.ini. The R36S SD card guide shows how.

2. Copy your saves off the games card.

3. Use a name-brand card for the new install. dArkOS needs at least 8 GB and recommends 16 GB or more.

Install steps

1. Identify your board and choose the build that lists it.

2. Get the image for your device from that project's GitHub release page. Official dArkOS images come as split 7-Zip files: extract only the .001 part, and 7-Zip joins the rest. dArkOSRE-R36 recommends checking the image's hash against its release page.

3. Flash it with a raw image writer. The official dArkOS wiki recommends Rufus or USB Image Tool on Windows, ApplePi-Baker on macOS, and Disks or dd on Linux, and says not to use balenaEtcher. dArkOSRE-R36 lists USB Image Tool, Raspberry Pi Imager and Rufus as working. dArkOSen supports Rufus only.

4. Click Cancel if Windows offers to format the card afterwards.

5. Select your model with the build's selector tool. On macOS or Linux, copy your board's DTB files to the BOOT partition by hand, as each wiki describes.

6. Boot with TF1 only. dArkOSRE-R36 asks you to remove the second card until installation finishes. Insert the new card in TF1 and power on.

7. Wait. The first boot unpacks files, expands the games partition and may reboot twice. dArkOSRE-R36's walkthrough video shows it taking about 2 to 3 minutes. Don't power off early, and don't resize the partition yourself.

8. Add your games card back. Power off, insert it in TF2, boot, then use Options → Advanced → Switch to SD2 for Roms. On dArkOSen, use Enable SD2 in its Storage Settings.

Can you keep your existing games card?

Usually, yes. dArkOS uses ArkOS's folder names, and switching to the second card doesn't overwrite what's already on it. Three things help:

• Give the card its own label, such as ROMS. dArkOSRE-R36 warns that a second card also named EASYROMS can cause boot problems such as missing themes.
• Rename seller-card folders. If your card used names such as FC or MD, move those games into the ArkOS-style folders.
• Keep BIOS files in the card's bios folder. In a two-card setup, the BIOS goes on the games card. See the R36S BIOS files guide.

What are the known caveats?

• Beta support. Many boards in dArkOSRE-R36's support table are marked beta or untested.
• Blank screen on first boot. dArkOSRE-R36 says this usually means a Panel 9 device: let the install finish, or reflash and select the right model.
• Flashing tool sensitivity. dArkOSen reports installs made with other tools showing missing themes, broken hotkeys and lockups, which reflashing with Rufus fixed.
• Charging during the first boot. Builds disagree. dArkOSRE-R36 says unplug the charger, while ArkOS4Clone says connect it and, on original devices, make sure the battery is above 3.3 V. Follow the build you install.
• Defaults differ by build. dArkOSen swaps A and B globally and ships an overclocked kernel; its README explains the overclock and its risks.

If something goes wrong, the R36S troubleshooting guide covers black screens and boot hangs.

Should you switch from ArkOS?

If your current card works and you're happy with it, there's no rush. ArkOS keeps working; it just won't get updates. Switch if you want current emulator updates and fixes, or a feature a build adds. Either way, try it on a spare card first and keep your original untouched. Our custom firmware comparison and ArkOS guide cover the alternatives, and the model comparison shows which R36 models share the chip.

Sources: dArkOS wiki, dArkOS releases, dArkOSRE-R36 README, dArkOSen-R36 README