Tutorial · Retro handhelds
R36S variants and clones: identify your hardware before flashing
Keep the original card and compare BOOT files and hardware markings with the official matrix; an unresolved result means stopping before flashing.
At a glance
TimeDepends on the checks required
DifficultyIntermediate (LODEX estimate)
ConsoleR36S and variants sold under that name
SystemdArkOSRE-R36 as reference; retain the original system if the profile is uncertain
Compatible devices
Compatible consoles
R36S, variants and clones sold under that name, for identification only. No firmware is confirmed for an undocumented profile.
What you need
- Required — The original microSD card kept intact.
- Required — A computer and reader able to access BOOT.
- Required — Motherboard markings only if a controlled inspection becomes necessary.
Why identify the variant?
The R36S trade name covers several motherboards and panels. Two nearly identical devices can need different boot files. The goal is not a “real or fake” label, but a documented profile before choosing firmware.
Keep the original card and copy accessible .dtb and boot.ini files before making changes.
Dated table of profiles marked completed
Snapshot of the dArkOSRE repository consulted on 2 October 2026. This is not a permanent list: check the repository when installing.
| Family | Identifiers marked completed in the snapshot |
|---|---|
| R36S | R36S-V12 2023-08-18 Panel 0; R36S-V12 2023-08-18 Panel 4; R36S-Y02 2024-12-18; R36XX-V21 2024-12-18 |
| Clone | G80CA-MB V1.2-20250422 Panel 8; G80CA-MB V1.2-20250423 Panel 8; G80CA-MB V1.3-20251212 Panel 8; R36S-V12 2023-08-18 Variant 2 Panel 1; Variant 3 Panel A; Variant 3 Panel 3 |
| SoySauce | Y3506_V03_20241104; Y3506_v03_20241210; Y3506_V03_20250317; Y3506_V04_20250529 2533, 2537 and 2548 |
Software clues
Cross-check BOOT partition files, original DTB name, boot.ini and motherboard identifier. Back up original files before testing. A community tool may help read a DTB, but its result remains a clue until confirmed against the matrix and release files.
The ArkOS-R3XS repository is archived: it provides historical context, not current support validation.
Cautious hardware clues
If choosing to open the console, switch it off, remove cards and proceed only if competent at disassembly. Record motherboard markings, revision, visible chips and ribbon cables without extrapolating. Opening can damage clips and affect warranty coverage.
Shell colour, general button layout or a seller’s label cannot identify the board on their own.
What proves nothing by itself
- A shell identical to a reference photo.
- A black screen after flashing.
- “R36S” in a listing.
- A panel number inferred only from an old tool.
- Booting an image intended for another variant.
Next action based on the result
| Result | Safe action |
|---|---|
| Exact match with completed status | Choose the matching profile in the stable release, then follow the installation guide. |
| Beta or untested match | Do not present compatibility as established; use only the official beta protocol if you accept the risk. |
| Profile absent | Keep the original system and send the project the requested identifier, .dtb and boot.ini files. |
| Conflicting clues | Stop before flashing and document the observations. |
Unresolved case
An unresolved case is a valid conclusion. Do not try multiple DTBs in sequence based only on resemblance. For an unlisted device, dArkOSRE requests the motherboard identifier and .dtb and boot.ini files from the original card.
Sources
- dArkOSRE-R36 — official repository — https://github.com/southoz/dArkOSRE-R36
- ArkOS-R3XS — historical archive — https://github.com/AeolusUX/ArkOS-R3XS
Leave a Reply