Step-by-Step Guide to Updating ArkOS on Your R36S

You finally get twenty quiet minutes after the house goes to sleep, you flash the newest ArkOS build for its latest fixes and hotkey tweaks, and your R36S answers with a blue LED and a black screen. Don't panic, your console isn't bricked. The usual culprit is a pair of tiny screen files that got replaced during the flash, and this guide shows you how to back them up, write a clean ArkOS 2.0 image, and put them back in one evening.

Table of contents

1. 1. Why does the Update R36S ArkOS process frequently fail?
2. 2. How do I accurately identify which display panel my R36S uses?
3. 3. What is the precise Flashing Process using Rufus?
4. 4. How do I correctly copy the DTB files?
5. 5. Is there an easier solution? (2Bluebox Pre-Install)
6. Frequently Asked Questions (FAQ)
7. Conclusion

1. Why does the Update R36S ArkOS process frequently fail?

Most failed ArkOS 2.0 updates trace back to three things: a worn-out unbranded MicroSD card, a mismatched .dtb screen file, or a single-RAM EmuELEC clone board. Back up your BOOT partition first, or skip the risk with the 2Bluebox R36S Handheld ($79.99).

Firmware on the R36S doesn't behave like a phone update where one installer fits every device. The screen panel changed several times across production runs, and third-party factories also sold single-RAM clone boards inside the same-looking shell.

Before you touch a disk formatting tool, check the four essential update rules in the quick reference below:

R36S ArkOS 2.0 Update · 4-Check Safety Cheat Sheet

BOOT BACKUP	Save Stock .dtb Files First: Copy rk3326-r35s-linux.dtb and rg351mp-kernel.dtb from your factory BOOT partition to your PC before flashing anything.
A1 / A2 SD CARD	Never Overwrite the Stock Card: Keep your original factory card in a drawer and flash ArkOS 2.0 onto a fresh SanDisk or Samsung (64GB/128GB) card.
7-ZIP+RUFUS	Extract & Write in DD Mode: Extract the .img.xz archive with 7-Zip first, then write the raw .img file using Rufus on Windows.
START+SHUTDOWN	Safe First-Boot Expansion: Let the first boot in TF1-OS run for a few minutes to expand EASYROMS, then shut down via START -> QUIT -> SHUTDOWN SYSTEM.

Compare the three failure points below before you wipe or format any card:

"Tested on our unit" means we checked it on a device we own. "Manufacturer spec" means the maker states it and we haven't verified it ourselves. "Community reports" means players report it, and results can vary.

Get these four tools ready on your desk before you start:

1. A Branded MicroSD Card (64GB or 128GB)

   Keep your original factory card untouched as a physical backup, and flash the new OS onto a genuine SanDisk or Samsung UHS-I U3 A1/A2 card. Under the SD Association Application Performance Class specification, an A1 card is rated for at least 1500 IOPS random read, 500 IOPS random write, and 10MB/s sustained write, which suits the small, constant reads and writes of a Linux handheld OS.

2. A Dedicated USB 3.0 MicroSD Card Reader

   Cheap thumb-drive style adapters can drop the connection during long writes and leave you with a half-written card.

3. 7-Zip File Archiver

   Community ArkOS images usually ship as compressed .img.xz or .7z archives of a few gigabytes that expand into a much larger raw .img file.

4. Rufus (Windows) or ApplePi-Baker (macOS)

   Raw image writers that copy the Linux BOOT (FAT32), rootfs (ext4), and EASYROMS partition layout sector by sector.

The Hardware Fragmentation Problem

The R36S doesn't come from one tightly controlled factory line. As suppliers switched to new 3.5-inch 640x480 IPS panel revisions, the timing values inside the Device Tree Blob (.dtb) files on the BOOT partition changed with them, which is why one image can light up one unit and leave another dark.

At the same time, bargain marketplace listings began shipping clones built on a single RAM chip running EmuELEC. Community guides point to two quick checks: a genuine Dual-RAM R36S shows two separate RAM chips beside the Rockchip RK3326 processor once the back shell is open, and a clone often still boots into its own menu with both TF1-OS and TF2-GAME slots empty. If yours fails either check, a standard ArkOS 2.0 image probably won't run on it.

2. How do I accurately identify which display panel my R36S uses?

The fastest way to identify your R36S screen revision is copying the .dtb files from your working stock BOOT partition and checking them in the community Panel Detector. Or skip manual matching with the pre-configured 2Bluebox R36S Handheld ($79.99).

If you flash a fresh ArkOS 2.0 image and power on without matching your screen file, the console often shows a lit LED, a faint backlight glow, or even menu music from the speaker while the display stays black. If your console is already stuck there and your original card is gone, jump to our R36S black screen fix and DTB recovery guide.

Understanding DTB Files (rk3326-r35s-linux.dtb)

On an RK3326 Linux handheld, the kernel can't ask the built-in LCD what it is the way a desktop monitor reports itself over EDID. Instead, the bootloader reads boot.ini and loads a compiled hardware map called a Device Tree Blob (.dtb) from the root of the BOOT (FAT32) partition. On the R36S, the files that matter are usually rk3326-r35s-linux.dtb (or rk3326-rg351mp-linux.dtb) and rg351mp-kernel.dtb.

Use the matrix below to see how the known R36S screen revisions map to the folders in a recent AeolusUX BOOT partition:

Some newer units use screen revisions beyond Panel 4. If none of these folders lights up your display, check the latest AeolusUX release notes for updated screen files before you assume the hardware is dead.

Three Reliable Ways to Identify and Save Your Panel Version

Follow these steps before you remove or format your working factory MicroSD card so you never have to guess your screen version:

1. Method A — Back Up Your Working BOOT Partition (Most Reliable)

   Power off your R36S, take the original MicroSD card out of the right-hand TF1-OS slot, and insert it into your Windows PC. Open the drive labeled BOOT (FAT32), create a folder on your desktop named R36S_Stock_Boot_Backup, and copy every .dtb, .ini, and .bmp file (especially rk3326-r35s-linux.dtb, rg351mp-kernel.dtb, and boot.ini) to your computer.

2. Method B — Check Your .dtb in the Community Panel Detector

   To learn the exact panel number before downloading an image, drag your backed-up rk3326-r35s-linux.dtb file into the AeolusUX R36S Screen Panel Detector tool on GitHub. It compares your file against known panel files and tells you which revision it matches.

3. Method C — Trial and Error with ScreenFiles Folders (If Your Original Card Died)

   If your stock card is unreadable and Windows can't open the BOOT partition, flash the AeolusUX ArkOS image first. Inside the new BOOT partition (or the companion ScreenFiles archive), try the Panel 4, Panel 3, Panel 2, Panel 1, and Original folders one at a time, copying each folder's contents into the root of BOOT until your display lights up cleanly.

If your marketplace unit turns out to be a single-RAM EmuELEC clone that won't run any ArkOS image, or your factory card died before you could back up the 15,000+ ROMs on it, the bench-verified Dual-RAM 2Bluebox R36S Handheld ($79.99) below is the shortcut:

3. What is the precise Flashing Process using Rufus?

Extract the downloaded AeolusUX ArkOS .img.xz archive with 7-Zip into a raw .img file, then write it to a branded MicroSD card using Rufus. Prefer to skip PC disk flashing? The 2Bluebox R36S Handheld ($79.99) arrives pre-flashed and ready to play.

Once your stock .dtb files are safe in a folder on your desktop (and you've copied any favorite ROMs and .srm or .state save files off the old EASYROMS partition), you're ready to install ArkOS on the new card. Backup first, tinker second.

Choosing the Right ArkOS Image (AeolusUX Community Build)

For the R36S and R35S, most owners use the ArkOS R3XS (AeolusUX) community image rather than a generic RG351MP build. The official AeolusUX ArkOS R3XS GitHub Wiki lists the supported devices, the hotkeys, and the screen-file folders that ship inside the BOOT partition, so read the notes for the release you download before you flash it.

Why Rufus Beats BalenaEtcher for R36S Cards

If I were setting up a fresh R36S today, I'd reach for Rufus first. Plenty of owners report BalenaEtcher stalling at the validation step or throwing permission errors on Windows 10 and Windows 11 when it writes multi-partition Linux images (FAT32 + ext4).

Rufus is a small, free, open-source Windows utility that runs without installation and writes raw .img files straight to the card.

Step-by-Step: Extracting with 7-Zip and Flashing with Rufus

Follow these five steps on a Windows PC to write a clean ArkOS 2.0 image:

1. Download the Latest Release: Download the latest ArkOS_R35S-R36S_v2.0_...img.xz (or .7z) archive from the official AeolusUX release page to your PC.
2. Extract the Raw .img File with 7-Zip: Right-click the downloaded archive and select 7-Zip -> Extract Here. Wait for decompression to finish and confirm you now have an uncompressed .img file several times larger than the download. (Rufus can open some compressed images directly, but extracting first proves the download is complete, and some archive formats must be extracted either way.)
3. Insert Your Branded MicroSD Card and Launch Rufus: Plug your 64GB or 128GB SanDisk or Samsung card into your USB 3.0 card reader and open Rufus. Under Device, confirm the drive letter and capacity match your MicroSD card so you never overwrite an external hard drive.
4. Select the Extracted .img File: Click SELECT in Rufus, browse to your extracted ArkOS_R35S-R36S...img file, and click Open. Rufus recognizes it as a raw disk image and writes it in DD mode.
5. Write the Image and Wait for READY: Click START, confirm the warning that existing partitions on the card will be destroyed, and wait while Rufus writes the partition table and file systems. Don't close Rufus until the green progress bar says READY.

(Note: Right after Rufus finishes, Windows may pop up "You need to format the disk in drive E: before you can use it." Click CANCEL every time. That popup is just Windows reacting to the Linux ext4 partition it can't read.)

4. How do I correctly copy the DTB files?

Before inserting the newly flashed card into your R36S, open the BOOT (FAT32) drive on your PC and replace the default .dtb files with the ones that match your panel. For zero file-swapping hassle, choose the 2Bluebox R36S Handheld ($79.99).

Once Rufus shows READY, hold off on putting the card in your console until the BOOT partition has the right display files.

Overwriting the Root BOOT Partition Files

If Windows doesn't show the BOOT drive in File Explorer after Rufus closes, unplug your card reader for three seconds and plug it back in. When the BOOT (FAT32) drive opens, pick the option that fits your situation:

• Option 1 — The Build's Default Already Matches Your Panel: If the release notes say the default screen file matches your panel (often Panel 4 on recent builds), you can leave the default files in place.
• Option 2 — You Backed Up Working Stock .dtb Files: Open your R36S_Stock_Boot_Backup folder, copy your original .dtb files, and paste-and-overwrite them into the root of the BOOT drive. Keep the new image's boot.ini unless the AeolusUX release notes tell you to replace it, because an older boot.ini can point to kernel files that aren't on the new card.
• Option 3 — Selecting From the Built-In ScreenFiles Folders: Inside the newly flashed AeolusUX BOOT partition, you'll see sub-folders for each panel revision. Open the folder that matches the panel you found in Section 2, copy every file inside it, go back to the root of BOOT, and choose Replace the files in the destination.

First Boot in TF1-OS and Expanding the EASYROMS Partition

Right after flashing, the EASYROMS game partition hasn't been expanded to fill the card yet. Follow this sequence so ArkOS 2.0 builds your game folders cleanly:

1. Safely eject the card reader from Windows and insert the MicroSD card into the TF1-OS slot (the right-hand slot on the R36S).
2. Press and hold the Power button for two seconds. You'll see the ArkOS 2.0 splash screen, then a scrolling terminal message saying the system is expanding the EASYROMS partition and creating dozens of console ROM folders (psx, n64, psp, gba, snes, bios, and more).
3. Wait a few minutes without touching the power or reset buttons. The console reboots once during this script and then loads the main EmulationStation menu.
4. When the main menu appears, press START -> QUIT -> SHUTDOWN SYSTEM instead of holding the power button.
5. Put the MicroSD card back in your PC. The expanded EASYROMS (exFAT) drive should now show up in File Explorer, and you can copy your backed-up bios/ folder and ROM folders back onto it. For a folder-by-folder walkthrough of file extensions and BIOS placement, read our step-by-step guide on how to add games to the R36S.

(Pro Tip for Dual-Card TF1 + TF2 Setups: If you keep ArkOS on a 16GB or 32GB card in TF1-OS and store your games on a second 128GB card in the left-hand TF2-GAME slot, boot into the fresh ArkOS menu first, insert your TF2 card, go to OPTIONS -> Advanced -> Switch to SD2 for ROMs, and let the system link the second card.)

5. Is there an easier solution? (2Bluebox Pre-Install)

If your old card died without a backup or your bargain unit is a locked EmuELEC clone, the 2Bluebox R36S Handheld ($79.99) arrives with ArkOS 2.0 on a verified Dual-RAM RK3326 board, 15,768 preloaded games listed publicly, and a 30-day replacement guarantee.

Downloading multi-gigabyte archives, extracting disk images with 7-Zip, flashing raw partitions in Rufus, and hunting down the right .dtb file is fun when you enjoy tinkering. It's a lot less fun when you only wanted twenty minutes of Pokemon Emerald, Crash Bandicoot, or Castlevania: Symphony of the Night after work.

Worse, some owners only find out halfway through an update that the budget console they bought from a random marketplace seller came on a failing unbranded card with no bios/ backup, or on a single-RAM clone board that can't run ArkOS 2.0 at all.

What We Pre-Configure on Every 2Bluebox R36S ($79.99)

At 2Bluebox LLC, we take the screen-file guesswork and the clone risk out of the box before your handheld ships. When I pulled the microSD card out of our R36S unit to export the full game list, I filtered out duplicate and broken files before publishing the 12,805 playable titles you can search at /pages/r36s-games-list. Our in-depth R36S retro handheld hardware review covers how the controls and 3.5-inch IPS screen feel in real play.

Use the matrix below to compare the 2Bluebox R36S with unverified marketplace listings, and to see where our living-room TV stick and PC Batocera drive fit instead:

Whether you want a ready-to-play Dual-RAM 2Bluebox R36S Handheld ($79.99) with ArkOS 2.0 pre-installed, a two-player 2Bluebox Retro Game Stick 4K Pro ($59.98) for your living-room TV, or the 2Bluebox Portable HDD Super Console 500GB ($64.99) for 3D PS2 and GameCube classics on your PC, compare all three below:

Frequently Asked Questions (FAQ)

Q1: Why is my R36S showing a black screen with a glowing LED after updating ArkOS?

A lit power LED with a dark backlit screen (or menu audio with no picture) usually means the ArkOS 2.0 kernel booted, but the BOOT (FAT32) partition holds a .dtb display file that doesn't match your LCD panel revision. Power off the console, put the MicroSD card in your computer, and copy your backed-up stock rk3326-r35s-linux.dtb and rg351mp-kernel.dtb files (or the matching panel folder from ScreenFiles) into the root of the BOOT partition.

Q2: Can I update ArkOS on my R36S over Wi-Fi (OTA) instead of flashing a new MicroSD card?

Sometimes, if your R36S already runs a genuine AeolusUX ArkOS 2.0 build on a branded MicroSD card. The R36S has no built-in Wi-Fi, so you'll need a compatible USB Wi-Fi dongle on a USB-C OTG adapter in the OTG port. Connect under OPTIONS -> WiFi, then run OPTIONS -> Update. Back up your BOOT files and saves first, and avoid running updates on the unbranded factory card, which is the card most likely to fail under heavy writes.

Q3: Why can't I see the EASYROMS partition in Windows after flashing ArkOS with Rufus?

Right after Rufus finishes, the EASYROMS partition hasn't been expanded yet, so usually only the small BOOT (FAT32) partition mounts in Windows. Eject the card, insert it into the right-hand TF1-OS slot on your R36S, and let the console run for a few minutes so ArkOS can expand and format EASYROMS (exFAT). If EASYROMS still doesn't appear on your PC afterward, press Win+X, open Disk Management, right-click the EASYROMS partition, select Change Drive Letter and Paths -> Add, and assign an open letter like E: or F:.

Q4: Will updating ArkOS fix a cheap R36S clone that came with EmuELEC?

Usually not. Clones that boot into EmuELEC (especially units that still start with both MicroSD slots empty, or boards with only one RAM chip) use different hardware that the standard AeolusUX ArkOS 2.0 R3XS image doesn't support. If you want real ArkOS 2.0 with PortMaster, standalone PSP and N64 emulators, and a matched screen file, choose the bench-verified Dual-RAM 2Bluebox R36S Handheld ($79.99).

Q5: Should I use a single-card (TF1) or dual-card (TF1 + TF2) setup when updating ArkOS?

Both work well on branded SanDisk or Samsung A1/A2 cards. A single-card setup (64GB or 128GB in TF1-OS) is the simplest option and matches how the 2Bluebox R36S Handheld ($79.99) ships, on one 64GB card with 15,768 preloaded games. A dual-card setup (16GB or 32GB OS card in TF1-OS plus a 128GB ROM card in TF2-GAME) suits heavy tinkerers, because you can re-flash TF1-OS later without touching the ROM library on TF2-GAME.

Conclusion

A clean ArkOS update on the R36S comes down to three rules: never overwrite your original factory card, always copy your stock .dtb and boot.ini files from the BOOT partition to your PC before flashing, and use 7-Zip plus Rufus to write the AeolusUX ArkOS 2.0 image onto a branded A1/A2 MicroSD card. Give the console a few full minutes on its first boot in TF1-OS to expand EASYROMS, or skip the flashing bench altogether with the pre-configured Dual-RAM 2Bluebox R36S Handheld ($79.99).

Back up your stock .dtb files first, flash onto a branded card, and Press Start. - Liam Parker

Further Reading & Resources

• AeolusUX Community Firmware Repository: ArkOS R3XS (R35S / R36S) Official GitHub Wiki & Releases - Primary documentation for community ArkOS 2.0 builds, hotkeys, emulator cores, and .dtb screen files.
• AeolusUX DTB Identification Utility: Online R36S Screen Panel Version Detector - Browser-based checker that matches your stock rk3326-r35s-linux.dtb file to a known LCD panel revision.
• Rufus Official Documentation: Rufus USB & Raw Disk Image Formatting Utility - Open-source Windows tool for writing raw .img files to MicroSD cards.
• SD Association Technical Standards: Application Performance Class (A1 / A2) Specification - Official minimums (A1: 1500 IOPS random read, 500 IOPS random write, 10MB/s sustained) for cards that run apps and operating systems.