Before starting

Installation completely erases the selected target microSD. Keep the original intact, copy accessible files first and work on a quality new card. Selecting the wrong device in the flashing tool can destroy another drive’s data.

This guide targets variants marked “completed” in the dArkOSRE matrix consulted on 4 October 2026. A “beta testing”, “untested” or absent profile is not treated as compatible. R36H, R36 Plus, R36 Max, R36 Ultra and V20 are therefore not included by analogy.

• A reliable new microSD and card reader.
• The original card protected from writes.
• A Windows, macOS or Linux computer.
• The official Releases page and Firmware Installation guide open.

Identify the supported variant

Record motherboard markings or boot information preserved on the original card, then compare with the official repository table. Do not choose a profile solely from shell colour or the box’s product name.

As of 2 October 2026, the stable matrix includes R36S-V12 2023-08-18 Panel 0 and Panel 4, R36S-Y02 2024-12-18 and R36XX-V21 2024-12-18. Clone and SoySauce variants are also marked completed, but each must exactly match its identifier. If the identifier is absent, stop and preserve original .dtb and boot.ini files.

Download and verify the release

Download the image from the official repository’s Releases page, never an unidentified mirror. Record the release name and published checksum. The stable release observed during writing was dArkOSRE-R36 03082026, with a SHA1 checksum; a future release may use another algorithm.

After extracting the .img, calculate the checksum of the file specified by the release using its published algorithm. On Windows, Get-FileHash accepts -Algorithm. Compare the entire value character by character against the same release. If it differs, discard the download and restart from the official source.

Flash on Windows, macOS or Linux

Close applications using the card. In USB Image Tool, Raspberry Pi Imager, Rufus or an equivalent image writer, select the .img, then double-check the target’s capacity and drive letter or name. The dArkOS wiki recommends avoiding Balena Etcher for this image because of reported problems.

Start writing, wait for completion and use the tool’s verification function if available. Cancel Windows prompts to format a Linux partition: do not reformat a partition created by the image.

• Insert only the new microSD.
• Select the verified .img file.
• Check the target drive’s identity.
• Write and verify the image.
• Safely eject the card before further file operations.

Choose the model and DTB

On Windows, open SELECT MODEL on BOOT and choose only the number matching the exact matrix identifier; confirm when prompted.

On macOS or Linux, follow the wiki’s branch: remove .dtb files from the BOOT root, then copy files from the versioned folder matching the exact motherboard and panel. Never mix two profiles’ files.

First boot and checks

Temporarily remove the second SD card. Insert only the system card, do not connect the charger during first boot and let initialisation finish. The official guide shows roughly two to three minutes for first boot; do not interrupt too soon.

Success means reaching EmulationStation with consistent display, controls and audio. Record the displayed version, shut down cleanly and reinsert the second card only after this check.

• Visible, stable picture.
• Main controls recognised.
• Clean shutdown available.
• Version and profile recorded in the maintenance log.

Failure: diagnose without repeated reflashing

If the screen stays black, stop repeated writes. First check the flashed target, checksum, profile identifier and DTB files. The wiki mentions Panel 9 as a possibility; a black screen alone does not establish that hardware identity.

If the card becomes unreadable or I/O errors appear, use the microSD diagnostic guide. If the profile is uncertain, use the identification page. Reflashing becomes relevant only after correcting a documented cause.

FAQ

Can one guide cover Windows, macOS and Linux? Yes: the goal and image are shared; only model-file selection differs.

Can I try a beta profile? Not in this stable procedure. A beta needs its own test protocol and must not be presented as compatible.

Is a file copy a disk image? No. A logical copy preserves accessible files; flashing or imaging operates on the whole medium.