How to Flash ArkOS 2.0 on R36S Using Rufus: Panel .dtb Fix & Windows 11 EASYROMS Guide

Quick Answer: To flash ArkOS on the R36S with Rufus, back up your stock BOOT .dtb files, extract the .img.xz to .img with 7-Zip, write it in Rufus, and click Cancel on every Windows format popup. Then let the first TF1-OS boot run up to 10 minutes, match your screen panel, and give EASYROMS a drive letter.

A new Samsung or SanDisk card won't boot the R36S if you just drag files onto it with Ctrl + C and Ctrl + V. ArkOS 2.0 is a full Linux system spread across three partitions, so it has to be written as a disk image. Below is the Windows 11 order we follow when we set up or rescue an R36S card: backup, extract, flash, first boot, panel match, and drive letter.

1. Why Rufus Beats balenaEtcher on Windows 11 & Step 0: Back Up Your Stock BOOT .dtb Files

For R36S cards on Windows 11, use Rufus with an image you've already extracted; the Handhelds Wiki and the R36S UK guide both flag balenaEtcher as prone to problems. Before flashing, copy the stock card's BOOT and bios folders to your PC.

When you plug a working R36S card into a Windows 11 PC, it actually holds three partitions: a small BOOT (FAT32) partition, a Linux ext4 root partition Windows can't read, and the EASYROMS (exFAT) game partition. As detailed in our complete R36S Wiki and Day-1 setup manual, BOOT stores the device tree blob (rk3326-r35s-linux.dtb), a small file that tells the RK3326 chip how to drive your exact 640x480 IPS panel, plus the boot.ini that loads it.

That file is why the backup matters. The AeolusUX ArkOS-R3XS project behind the R36S multi-panel image was archived on June 9, 2026, and its page now points R36S owners to the actively maintained dArkOSRE-R36 build. Whichever image you flash, copying the stock BOOT folder and EASYROMS/bios/ to your desktop takes a couple of minutes. I treat a stock card the same way I treat an old SNES cartridge: pop it open and check the board before trusting the label. Backup first, tinker second. You can also see how we inspect these components in our hands-on 2Bluebox R36S hardware review.

Still have the stock card? AeolusUX's free dtbIdentify tool reads its .dtb and tells you which panel your screen uses, which takes the guesswork out of Section 3.

“Tested on our unit” means we checked the partition layout and .dtb behavior on our own 2Bluebox R36S Handheld ($79.99) (and, for Game Stick cells, our own 2Bluebox Retro Game Stick 4K Pro); “Manufacturer spec” means published documentation from Rufus, 7-Zip, the ArkOS image maintainers, or 2Bluebox store policy; “Community reports” means documented troubleshooting from the Handhelds Wiki, Joey's Retro Handhelds, the R36S UK guide, and r/R36S.

2. Step-by-Step: Extract ArkOS with 7-Zip, Flash It in Rufus, and Dodge the Windows “Format Disk” Trap

Extract the ArkOS_R35S-R36S_...img.xz download to a plain .img with 7-Zip, write that file to your microSD card in Rufus, and click Cancel on every “You need to format the disk” popup Windows 11 shows when Rufus finishes.

Rufus can open some compressed images by itself, but the Handhelds Wiki's black-screen guide is blunt: flash the decompressed image, and if your file still ends in .xz, unpack it with 7-Zip first. That extra step pays off twice. 7-Zip stops with an error if the download is damaged, before you touch the card, and the unpacked .img (about 8 GB, per the R36S UK guide) stays on your PC for the next card you flash.

Follow these 6 steps to write a clean ArkOS 2.0 image on Windows 11:

1. Step 1: Download Rufus, 7-Zip, and the ArkOS Image. Grab the portable Rufus executable from rufus.ie, install 7-Zip from 7-zip.org, and download the R36S image: the final AeolusUX multi-panel file (ArkOS_R35S-R36S_v2.0_..._MultiPanel.img.xz) from the archived project page, or the current dArkOSRE-R36 build. The panel steps in Section 3 follow the AeolusUX image, so check the dArkOSRE-R36 page for its own instructions if you go that route.
2. Step 2: Extract .img.xz to .img With 7-Zip. Right-click the download in File Explorer, click Show more options → 7-Zip → Extract Here, and wait until a single uncompressed .img file appears in the folder.
3. Step 3: Select Your microSD Card and .img File in Rufus. Insert a branded card (32GB to 256GB) into a USB card reader and open Rufus. Under Device, confirm the listed capacity matches your microSD card, click SELECT, pick the extracted .img, and leave the other settings alone.
4. Step 4: Click START to Write the Image. Click START, then OK on the warning that everything on the card will be erased. The write takes several minutes, depending on your card and reader.
5. Step 5: Click Cancel on the Windows 11 “Format Disk” Popup. When the Rufus bar turns green and reads READY, Windows 11 spots the Linux partition it can't read and asks: “You need to format the disk in drive E: before you can use it.” Click Cancel on every one of those popups.
6. Step 6: Check the BOOT Partition Before Ejecting. Open File Explorer (Win + E) and confirm a small BOOT drive shows boot.ini, rk3326-r35s-linux.dtb, and the image's Screenfiles folder. If BOOT doesn't appear, give it a letter in Disk Management (same steps as Section 4); if that option is greyed out, Joey's Retro Handhelds uses the free MiniTool Partition Wizard to unhide it.

If your stock card keeps failing or your unit turns out to be a clone, the 2Bluebox R36S Handheld ($79.99) ships on a verified Dual-RAM RK3326 board with ArkOS 2.0, a panel-matched .dtb, and 15,768 pre-loaded games (12,805 unique playable titles). Skip it if you need HDMI TV output or PS2/GameCube emulation:

3. Fixing the Post-Flash Black Screen: Matching Your R36S Panel .dtb File

A black screen with the blue LED on after flashing usually means the .dtb screen file in BOOT doesn't match your LCD panel. Fix it with the AeolusUX Panel Picker (R1 + a button at power-on) or by copying your stock .dtb into BOOT.

Before you blame the panel, give the first boot its full 10 minutes. The Handhelds Wiki's step-by-step fix warns that the screen can stay black while ArkOS expands the card, and that switching off early corrupts the install. If the screen is still dark after that, the panel file is the next suspect: the wiki counts at least five different screen versions across R36S production runs, and each needs its own .dtb timing file.

When the active file belongs to a different panel, the backlight may glow faintly and you may even hear menu sounds, yet the picture never appears. As the Handhelds Wiki R36S troubleshooting page documents, several post-flash symptoms look alike, and only one of them is a .dtb mismatch. For a broader look at how ArkOS handles hardware profiles compared with other handheld systems, read our OnionOS vs. ArkOS 2.0 vs. CrossMix-OS handheld firmware comparison.

If you flashed the AeolusUX multi-panel image, you don't have to pull the card to switch panels. The project README says not to enter Panel Picker Mode until the first-boot setup has finished. After that, power off, hold R1 plus the button for your panel from Table 3 as you power on, and wait: the console applies the panel and shuts itself off. Power it on normally and the boot logo should appear.

Prefer to fix it on the PC? Following the Handhelds Wiki, delete the .dtb and boot.ini files in the root of BOOT, then paste the .dtb files and boot.ini from your Step 0 backup. No backup? The image's Screenfiles folder and the AeolusUX R36S-DTB repository hold one set of files per panel; try them one panel at a time, starting with the newest panel and working backward.

4. First-Boot Expansion & Fixing “EASYROMS Not Showing” in Windows 11 Disk Management

Put the flashed card in TF1-OS, power on, and leave the R36S alone for up to 10 minutes while ArkOS expands EASYROMS (exFAT) across the card. If EASYROMS stays hidden in Windows 11 afterward, assign it a drive letter in Disk Management.

Don't copy ROMs or BIOS files onto the card right after Rufus finishes. The EASYROMS game partition only fills the card after the first boot in the right-hand TF1-OS slot, and Joey's Retro Handhelds R36S setup guide adds that the TF2-GAME slot should stay empty during that boot. Slide the card in, press Power, and wait. The AeolusUX README allows up to 10 minutes for this setup, Joey notes the console reboots twice along the way, and the R36S UK ArkOS flashing guide covers the dual-card switch if you plan to keep games on TF2-GAME.

Once the EmulationStation menu appears, shut down via START → Quit → Shutdown System, wait for the LED to go off, and put the card back in your Windows 11 PC. If Windows skips the drive letter for EASYROMS, only BOOT (or nothing at all) shows up in File Explorer. Follow these 3 steps in Disk Management (diskmgmt.msc) to reveal EASYROMS:

1. Step 1: Open Windows 11 Disk Management. Right-click the Windows Start button (or press Win + X) and click Disk Management. Scroll the bottom disk map to your removable microSD card (Disk 1 or Disk 2), which now shows three partitions: BOOT (FAT32), an unlettered Linux partition, and a large EASYROMS (exFAT) partition filling the rest of the card.
2. Step 2: Open Drive Letter Settings on EASYROMS. Right-click the large EASYROMS (exFAT) box on the right side of the disk bar and select Change Drive Letter and Paths.... Leave the unlettered Linux partition untouched.
3. Step 3: Assign an Open Drive Letter (G: or H:). Click Add..., keep Assign the following drive letter checked with a free letter like G: or H:, and click OK. File Explorer will open your EASYROMS drive with every console folder ready for your backed-up bios/ files (see our master RetroArch and Batocera BIOS reference guide) and your own games, including patched GBA cartridges from our step-by-step Pokemon ROM patcher and R36S guide.

Clicking Cancel on every Format Disk popup, matching your panel's .dtb in BOOT, and giving EASYROMS a drive letter in Disk Management clears the three Windows-side traps in this guide without re-downloading your ArkOS image.

5. Pre-Configured Handheld & TV Hardware: 2Bluebox vs. Marketplace Clones & a DIY Reflash

Unlike most marketplace clones, 2Bluebox (2bluebox.com) publishes game lists and verifies boards. Pick the 2Bluebox R36S Handheld ($79.99) for pocket play, the 2Bluebox Retro Game Stick 4K Pro ($59.98) for TV co-op, or the 2Bluebox Portable HDD ($64.99) for PS2.

Before you decide whether to spend an evening flashing disk images or pick up a pre-configured system, you can browse every included handheld title on our 15,768 R36S pre-loaded games directory (12,805 unique playable titles). Table 4 compares unverified marketplace sellers, a DIY Windows 11 reflash, and 2Bluebox (2bluebox.com) on board checks, screen setup, public game lists, stock and shipping, and warranty support.

Once your R36S is running, the two things it can't do are the living-room TV and the 3D era. For weekend 2-player games on the TV, the 2Bluebox Retro Game Stick 4K Pro ($59.98) plugs into HDMI with two wireless controllers. For PS2, GameCube, and Wii, the 2Bluebox Portable HDD Super Console 500GB ($64.99) boots Batocera Linux from a Windows PC over USB 3.0. Compare the ready-to-play options below:

Frequently Asked Questions

Conclusion

Flashing a fresh ArkOS 2.0 card on Windows 11 comes down to a short routine at your desk: back up the factory BOOT .dtb files, extract .img.xz to .img with 7-Zip, write it with Rufus, click Cancel on every Windows “Format disk” popup, give the first boot its full 10 minutes, match your panel, and assign EASYROMS a drive letter in Disk Management. Follow that order on a genuine R36S with a branded card, and it should boot straight into EmulationStation.

Back up your stock BOOT folder, click Cancel when Windows offers to format the card, give the first boot its full ten minutes, and enjoy your fresh ArkOS 2.0 handheld.