R36S Firmware Download and Flashing Guide (2026): Every Image, Step by Step
Share
Most people searching for "R36S firmware download" want one of three very different things: a fresh custom OS, a way to fix a console that won't boot, or the stock image back. This guide covers all three — with the actual download sources, the flashing steps, and the mistakes that cost people their save files.
What you need
- A microSD card. A genuine A1-rated card from SanDisk, Samsung or Kingston, 64GB or larger. This is the single most important component and the most common source of problems — counterfeit cards are everywhere and they fail in ways that look exactly like firmware bugs.
- A card reader. USB-A or USB-C. The R36S itself cannot be flashed over its own cable — the card has to come out.
- A flashing tool. balenaEtcher (Windows, Mac, Linux) or Raspberry Pi Imager. Both are free.
-
7-Zip or equivalent, because firmware images ship compressed as
.7z,.xzor.zip. - Time. Budget 30–45 minutes for your first flash. The write itself takes 10–20 minutes depending on your card.
Which image should you download?
| You want | Flash this | Why |
|---|---|---|
| The best all-round experience | ArkOS | Mature, well supported, per-system settings, the safest first custom firmware. |
| Something minimal and fast | MinUI | Boots in seconds, no menus to get lost in, excellent battery life. |
| WiFi, a browser, streaming | DarkOS | The most featureful option on the WiFi model, at the cost of complexity. |
| A real Linux desktop to tinker with | Arch-R | Full Arch Linux. For people who want the project, not just the games. |
| To undo everything | Stock image | Returns the console to how it shipped. See the recovery section below. |
Where to download each one safely
This matters more than people realise. R36S firmware is community-built, and search results are full of reuploaded images on file-locker sites carrying who-knows-what. Always download from the project's own release page — never from a mirror, a Telegram link or a YouTube description.
- ArkOS — the official releases live on the project's GitHub. Pick the image built for RK3326 / R36S. Do not take an RG351 image; it will not boot.
- MinUI — GitHub releases, in the R36S variant. Our MinUI install guide walks through it.
- DarkOS — distributed by its developer; our DarkOS and Chrome guide covers both the source and the setup.
- Arch-R — see our Arch-R installation walkthrough.
If you bought your R36S from us and can't find a safe source for the image you want, message us on WhatsApp — we'll point you at the current official release rather than let you download something dubious.
Step 1: back up the card you already have
Skip this and you will lose your saves. It takes ten minutes.
- Power the console fully off and remove the microSD card.
- Put it in your card reader and open it on your computer. On Windows you'll typically see only one of its partitions — that's normal and fine.
- Copy the whole
romsfolder (orgames, depending on your firmware) to your computer. - Copy your saves and save states. On ArkOS these live under
roms/<system>/or in asavesfolder; on MinUI look in.userdata. When in doubt, copy everything that isn't the OS itself. - Copy your BIOS folder if you have one set up. Re-collecting BIOS files is the most annoying part of a rebuild.
If you'd rather image the entire card so you can restore it byte-for-byte, balenaEtcher's "Clone drive" and Win32DiskImager both do this. It's slower and produces a large file, but it's the only backup that captures absolutely everything.
Step 2: flash the new image
-
Extract the download. You want the raw
.imgfile. Etcher can read.img.xzand.7zdirectly in most cases, but extracting first removes a failure mode. -
Open balenaEtcher and choose Flash from file, then select the
.img. - Select your microSD card as the target. Check the drive letter twice. Etcher tries hard to hide your system drive, but this is the step where people destroy a USB backup disk.
- Flash, and wait. 10–20 minutes is normal. Let the verification pass finish — it catches bad cards before they waste an evening of your time.
- Ignore Windows when it asks to format the drive. After flashing, Windows sees the Linux partitions it can't read and offers to "fix" them. Click Cancel. Every time. Formatting here undoes the whole flash.
- Eject safely, put the card back in the console, and power on.
First boot takes noticeably longer than normal — the OS resizes its partition to fill your card and builds its game database. Two or three minutes with a seemingly frozen screen is expected. Don't pull the power.
Step 3: put your games back
Once you're at the main menu, power down, put the card back in your computer, and copy your roms folder back into place. Match the folder names the new firmware expects — ArkOS and MinUI use slightly different conventions, and a game in the wrong folder simply won't appear.
Then rescan or reboot so the OS picks them up. For PSP specifically, our guide to adding PSP games covers the folder structure and the ISO formats that work best.
If your console has WiFi, you can skip the card shuffle entirely for future transfers — see the WiFi setup guide for wireless file transfer.
Recovery: when the console won't boot
A black screen after flashing is almost never a dead console. In order of likelihood:
- Wrong image. An RG351 or R36S Plus image on a standard R36S will not boot. Re-download the RK3326 / R36S build.
- Bad or counterfeit microSD card. By far the most common cause. Try a different card from a different brand before you try anything else. A card that passes Etcher's verification can still fail under real use.
- Incomplete write. Reflash, and let verification finish this time.
- Card not seated. Push until it clicks. It's worth ruling out.
- Counterfeit console. If three good cards with three correct images all fail, check whether the unit is genuine.
Because the entire operating system lives on the removable card, you cannot permanently brick an R36S by flashing firmware. A fresh card and a correct image always brings it back. That's a genuinely nice property of this hardware and worth remembering when a flash goes sideways at midnight.
Updating firmware you already have
You don't always need a full reflash. ArkOS ships incremental updates you can apply from its own menu, and on the WiFi model those can come over the air. A full reflash is only necessary when you're changing OS, jumping several versions, or recovering from a broken install.
When you do reflash, the backup step above is what makes it a 20-minute job instead of a lost weekend.
Common questions
Does flashing firmware void the warranty? Not with us. The card is user-replaceable by design and flashing it is the expected use of the device. Physical damage is a different matter.
Can I flash firmware without a computer? No. You need a card reader and a desktop or laptop. There's no on-device flashing path.
Do I need to format the card first? No. Etcher overwrites the entire card including its partition table. Pre-formatting changes nothing.
What size card should I buy? 64GB is comfortable for everything up to PS1. Go to 128GB or 256GB if you want a large PSP library — PSP ISOs are big. Buy from a seller you trust; fake high-capacity cards are the single most common cause of "my R36S keeps corrupting."
Can I use two cards? Yes, and it's the nicest way to experiment. Keep your working setup on one card and try new firmware on a second. Swapping takes seconds and your main setup is never at risk.