dArkOS vs ArkOS, ROCKNIX: which system for your R36S in 2026?

ArkOS has been discontinued: its creator, Christian Haitian, replaced it with dArkOS at the end of 2025. On a genuine R36S, the systems still maintained as of 3 October 2026 are the dArkOS derivatives (dArkOSen, dArkOSRE) and ROCKNIX. On a clone, you need a dedicated image: ArkOS4Clone, dArkOSRE or the ROCKNIX B image.

A common trap: there is no official dArkOS image for the R36S. Here is who does what, what is still being updated, and how to switch systems without losing the card that already works.

ArkOS: discontinued since December 2025

The ArkOS GitHub repository is archived. Since 30 December 2025, its wiki has said so at the very top: dArkOS has replaced ArkOS, which is no longer maintained and stays online for the record. The last official release, v2.0, dates from 1 August 2025.

ArkOS never had an official "R36S" image in the first place. Its wiki points to ArkOS R3XS, the community image by AeolusUX for the R33S, R35S, R36S and R36H. Its latest release, V2.0 from 7 November 2025, is archived as well.

The same goes for ArkOS K36, the AeolusUX image for the K36, the R36 Max and other clones: discontinued on 25 August 2025 and handed over to ArkOS4Clone.

dArkOS vs ArkOS: the successor, with no official R36S image

dArkOS comes from the same author, Christian Haitian. It is built on Debian (Trixie at the time of writing) and presents itself as the continuation of ArkOS, designed so that others can pick it up. The first public release came out on 23 December 2025; the most recent, v08272026, was published on 30 August 2026.

What it promises: more than 64,000 installable Debian packages, online updates without reflashing the card, more than 90 emulated systems, more than 800 ports through PortMaster, and game management from a web browser.

The catch for you: the August 2026 release ships images for ten devices (RG351MP, RGB30, G350, A10 Mini and others), none of them for the R36S. Two community projects adapt it.

dArkOSen-R36: for genuine R36 consoles

Built by djparentx from the dArkOS image for the RG351MP, it covers "genuine" R36 consoles (R36S, R36S Plus, R36H, R36H Pro Max, R45H, R46H, R40S), not clones, G80CA and "Soy Sauce" boards included. Latest release as of 3 October 2026: 29 September.

Two settings catch people out on first boot: the A and B buttons are swapped by default, and an overclock is offered (1,296 MHz by default, 1,512 MHz at most). To write the card, the project only supports Rufus.

dArkOSRE-R36: for some R36S units and some clones

A version of dArkOS adapted by southoz "for some R36S and clones". Latest release as of 3 October 2026: the one from 10 March 2026. Its strength is a table giving a status for each motherboard: R36S-V12 2023-08-18, R36S-Y02 or R36XX-V21 as "done", R36S-V21 and R36S-V30 as "beta".

The R36 Max and the R36 Ultra are in beta there, the R36H is in progress. Read the line for your board before flashing.

For clones: ArkOS4Clone

The project by lcdyk0517 brings (d)ArkOS to devices not supported elsewhere: the original R36S (screens 0 to 4), five types of R36S clones, "Soy Sauce" boards, the R36 Max, R36 Ultra, R36T, K36 and others. Latest release as of 3 October 2026: 30 September.

A word of warning: on some clones with a V20 board, an ArkOS4Clone bug can overdrive the speaker and damage it permanently.

ROCKNIX: the other maintained route

ROCKNIX has a dedicated page for the R35S and the R36S, with its "RK3326" image, running a mainline Linux kernel and the EmulationStation interface.

Two release tracks: a stable release every month (the latest from 1 October 2026) and nightly builds in a separate repository (the latest from 3 October 2026). For a genuine R36S, go with the monthly stable.

R36S units from 2024 have new screens that need one extra step: pick the right screen file (mipi-panel.dtbo.r36s-panel…) and place it in the overlays/ folder of the boot partition, or generate it from the original .dtb file.

For clones in the K36 family (K36, R36 Max, R36 Pro…), support is experimental: the "B" image, from the 10 November 2025 nightly or newer.

AmberELEC: yes, with the RG351MP image

AmberELEC lists the R35S and the R36S, on one condition: use the RG351MP pre-release image, not the stable release. The last stable dates from 3 February 2023, but pre-releases keep coming: the most recent is from 3 October 2026.

AmberELEC detects the screen on its own: do not replace or rename the .dtb files after flashing. EmuELEC clones are not compatible.

The table to help you choose, as of 3 October 2026

System	Status	Genuine R36S	Clones (K36 family)	Good to know
Official ArkOS	Discontinued, archived. v2.0 from 1 August 2025	Never had an R36S image	No	Replaced by dArkOS
ArkOS R3XS	Archived. V2.0 from 7 November 2025	Yes	No	Screen chosen at power-on (R1 + direction)
Official dArkOS	Maintained. v08272026 from 30 August 2026	No image	No image	Base for the derivatives
dArkOSen-R36	Maintained. 29 September 2026	Yes	No	Write with Rufus
dArkOSRE-R36	Maintained. 10 March 2026	Depends on the motherboard	Some boards	Status per motherboard
ArkOS4Clone	Maintained. 30 September 2026	Screens 0 to 4 listed	Yes	Bug reported on some V20 clones
ROCKNIX stable	Monthly. 1 October 2026	Yes, RK3326 image	See nightly	Screen file to add on 2024 models
ROCKNIX nightly	Latest from 3 October 2026	Prefer the stable	Experimental, B image	Nightly from 10 November 2025 or newer
AmberELEC	Stable from 2023, pre-releases up to date	Yes, RG351MP pre-release	No	Leave the .dtb files alone

Before flashing: five precautions

1. Keep the original card untouched. Flashing a system wipes the card you flash. Work on a second, branded card: 8 GB minimum, 16 GB or more recommended by dArkOS. The R36S stock cards have a poor reputation anyway.
2. Make a full copy of it. Win32DiskImager on Windows, ApplePi-Baker on Mac. At the very least, keep the .dtb files from its BOOT partition: on a clone, without them, you end up trying a lot of screen files.
3. Identify your motherboard and your screen. The number is printed on the board, visible under the battery or through a transparent shell. Then run the .dtb files from the original card through the dtbIdentify tool by AeolusUX or dtbTools by lcdyk0517.
4. Write the card with a tool the projects confirm. Rufus on Windows (the only one supported by dArkOSen), Win32 Disk Imager or Raspberry Pi Imager, ApplePi-Baker on Mac. dArkOS and dArkOSRE explicitly advise against another very widespread tool.
5. Let the first boot run its course. ArkOS R3XS can take up to 10 minutes to set itself up: do not start the screen selection during that time. dArkOS asks you not to expand the EASYROMS partition by hand beforehand.

What the motherboard number tells you

The genuine R36S comes in at least six screen versions; the wrong image gives you a black screen. The board number points you in the right direction:

• R36S-V12 2023-08-18: usually the original screen ("screen 0").
• R36S-V21 2024-12-18: screen 4, green LED, slot for a Wi-Fi module; this board is also used in the R36XX.
• R36S-V22 (2024-12-18 and 2025-09-22): screen 4.
• R36S-V30 (2025-10-18 and 2025-11-18): new revision, screen 4.
• "Soy Sauce" Y3506 boards: a family of their own, supported by dArkOSRE and ArkOS4Clone.

Be careful: some clones also carry the V12 number. The number alone does not prove a console is genuine. Our guide to telling an original R36S from a clone covers the other signs.

Black screen after flashing: two causes

Black screen: the screen file does not match your version. Flashing red LED: a standard R36S image was installed on a clone, and you need a clone image.

In both cases, reflashing the card is usually all it takes. One caveat: ROCKNIX warns that flashing the internal memory (eMMC) of some clones can render them unusable. The genuine R36S has no internal memory: everything happens on the microSD card.

What about muOS, MinUI and Knulli?

None of the three lists the R36S as of 3 October 2026. muOS only names Anbernic and TrimUI devices. MinUI is archived and its device list contains no R36S. Knulli covers Allwinner H700 and A133 chips, a few RK3566 devices and Retroid handhelds, not the RK3326 in the R36S.

For the details of each system, our guide to R36S systems is still useful; to know what actually runs today, rely on the table above, up to date as of 3 October 2026.

Do you really need to change systems?

Not necessarily. The R36S, from 69,99 €, works as it is with its original card. Changing systems is a choice, not an obligation.

To stay on your current system, see our article on how to update the R36S, keeping the rules on this page in mind: copy the card first, then use one of the writing tools listed above.

Frequently asked questions

dArkOS or ArkOS: which one should you install in 2026?

ArkOS has been discontinued since the end of 2025. On a genuine R36S, go for a dArkOS derivative (dArkOSen, dArkOSRE) or ROCKNIX, all of them maintained. ArkOS R3XS can still be downloaded, but it is archived.

How do you know which image to use?

Read the motherboard number, then analyse the .dtb files from the original card with the AeolusUX tool or the one by lcdyk0517, which also gives you the steps to follow for a clone.

Why does the screen stay black after flashing?

Most of the time, the screen file does not match your version. On a clone, a flashing red LED means a standard R36S image was installed: you need a clone image.

ROCKNIX stable or nightly?

The monthly stable for a genuine R36S. K36 and R36 Max clones need a recent nightly (from 10 November 2025 or newer) and the B image, with experimental support.

Does changing systems erase my games?

Flashing erases the card you flash. Keep the original untouched, copy it and work on a second card.