Portable Retro Emulation: The SD-Card and Firmware Reality

Every review of a sub-£100 retro handheld — including our own Anbernic-versus-the-field roundup — spends most of its word count on the shell: the screen, the D-pad feel, the button travel. That’s the wrong place to spend the attention, because the shell is the part these devices get right almost without exception now. What actually determines whether a £45 handheld feels like a magic box or a frustrating one is a £6 microSD card and a firmware choice that most buyers never think about until something goes wrong. The handheld market solved the hardware problem years ago. The card and the software are where the promise printed on the listing and the thing that actually turns on still have the biggest gap.

Why the SD card is not a commodity purchase here

Nearly every budget retro handheld — the Miyoo Mini Plus, the whole Anbernic RG-series line, the various clones built on the same reference boards — boots its entire operating system from the SD card rather than from onboard storage, and treats that same card as the drive holding every ROM, save state and configuration file. That’s a fundamentally different job than the one an SD card does in a camera, where a slow or dying card costs you a photo. Here, a card that’s slow, worn out or (very commonly, on marketplace listings) simply counterfeit can produce corrupted save states, random freezes mid-session, or a device that won’t boot at all — and because the symptom looks identical to a firmware bug or a hardware fault, it’s the single most common reason these handhelds get returned or written off as broken when the actual fault is a six-pound card.

Counterfeit and remarked SD cards are a well-documented problem on marketplace listings specifically in this price bracket: a card printed to claim 128GB or 256GB that actually contains a much smaller flash chip with firmware rigged to report the fake capacity, silently overwriting old data once the real capacity is exceeded. The reliable defence is buying only from a retailer that will honour a return, checking the card with a capacity-verification tool (H2testw or f3 are the standard free tools) before loading it with anything irreplaceable, and treating a price that’s dramatically below the going rate for a given capacity as the warning sign it is rather than a bargain.

What actually matters in a card spec sheet

For this specific job — booting an OS and randomly reading thousands of small ROM and save files — raw sequential read speed matters less than the random-access performance the class ratings partially capture. A card rated A1 or A2 (the “Application Performance” ratings, which specify a minimum random read/write IOPS figure rather than just sequential throughput) will noticeably outperform a same-capacity card that only carries a U3 or V30 sequential rating, because those older ratings were designed around continuous video recording, not launching thousands of small files. In practice this means a genuine SanDisk or Samsung card carrying an A2 rating, even at a modest 64GB or 128GB capacity, will deliver faster load times and smoother firmware navigation than a larger but A1-or-unrated card from a less established brand — capacity is not the spec to optimise for here.

Stock firmware versus custom firmware

Every handheld in this category ships with a manufacturer stock firmware, and every one of them also has an active custom-firmware scene replacing it. Anbernic’s stock software is functional but plain: a basic menu, inconsistent emulator cores across systems, and — a genuinely common complaint in owner reviews — occasional bugs in save-state handling that custom firmware has already fixed. The two custom firmware projects that matter most right now are muOS, which targets a wide range of Allwinner and Rockchip-based handhelds with a fast, minimal interface and strong per-core configuration, and GarlicOS (and its close relative, ArkOS), which is the default recommendation specifically for the RG35XX line and focuses on a cleaner box-art-driven front end. Miyoo Mini owners have their own long-established option in OnionOS, which is mature enough at this point that a meaningful share of Miyoo buyers install it before they’ve finished setting up the stock software.

What the firmware swap actually changes

The honest case for custom firmware isn’t that stock firmware is broken — most current-generation stock firmware boots and plays games without drama. It’s that custom firmware consistently ships better-tuned emulator cores for demanding systems (PS1 and Sega Saturn emulation in particular benefit from cores that stock firmware often doesn’t include or configure well), better save-state reliability, and a front end that’s noticeably faster to navigate once a ROM library grows past a couple of hundred titles. The trade-off is real too: installing custom firmware means re-flashing the SD card from scratch, which erases anything on it, and it means giving up the manufacturer’s official support path if something goes wrong afterwards — most sellers won’t warranty a device running firmware they didn’t ship, even though the fault that prompted a support call is rarely caused by the firmware itself.

Building a card that survives a reflash

Because the OS lives on the card and the ROM library lives on the same card, the sane approach for anyone planning to try more than one firmware is two cards rather than one: a small, cheap card (16–32GB) dedicated to testing firmware builds, and a second, larger card holding the actual game library, kept untouched while different firmware options get tried on the first. Most current custom firmware supports pointing at an external ROM path or a second card slot on handhelds that have one, which avoids re-copying a multi-gigabyte ROM collection every time a firmware version changes. It’s a small extra purchase — a second 64GB A2 card is routinely under £10 — that turns firmware experimentation from a stressful all-or-nothing gamble into something that can be undone in five minutes.

Write endurance and the slow death of a well-used card

A card running an OS, writing frequent save states and swapping firmware configuration files takes a genuinely different wear pattern to a card used for photos or video, which is written once and mostly read afterwards. Consumer microSD cards are rated in total bytes written (TBW) rather than a figure most buyers ever see quoted on the packaging, and a card used heavily for save-state cycling over a couple of years is a realistic candidate for developing bad sectors well before its capacity would suggest it should. The practical symptom is usually a save file that silently fails to write correctly rather than a dramatic card failure — which is exactly why regularly copying the save-state folder off the device to a laptop or cloud folder matters more here than it would for almost any other gadget category: the card is a wear part, not a permanent home for the only copy of a hundred hours of progress.

Why the same firmware runs on handhelds from different brands

Look at the compatibility list for muOS or GarlicOS and the same pattern shows up that shows up in the cheap USB-C hub market: a handful of reference designs from a small number of Chinese SoC and board vendors get relabelled by dozens of storefronts. Most sub-£60 handhelds in this category are built around one of a small number of Allwinner H700-family or older Rockchip RK3326-family boards, with the shell, screen and button layout the only things a given brand actually designed themselves. That’s precisely why a single custom firmware build can support what looks like a bewildering range of brand names — the silicon underneath is shared, and firmware developers target the chip and board reference, not the marketing name printed on the box. It also explains why buying “the cheapest one that looks right” from an unfamiliar storefront is less risky in this category than it would be for, say, a smartphone: the odds are good it’s running hardware already supported by the same firmware projects covering the well-known names, even if the badge on the shell has never been reviewed anywhere.

The legal note worth being straight about

Emulator software itself is legal in effectively every jurisdiction that matters here — it’s a program that interprets instructions, no different in principle to any other software. The legality question is entirely about where the ROM files come from: dumping cartridges or discs you already own onto a card for your own handheld sits on solid legal ground in most reasonable readings of the law, while downloading ROMs for games never owned does not, regardless of how freely available the files are or how old the original hardware is. The handheld and firmware scene doesn’t distribute ROMs itself for exactly this reason — that part of the process is left to the buyer, and it’s worth being clear-eyed about which side of that line a given ROM library actually sits on.

The picks

For a first retro handheld, buy a genuine, name-brand A2-rated card of 64GB or 128GB rather than chasing the largest capacity a marketplace listing offers, and verify it with a capacity-check tool before loading anything onto it — this single step avoids the most common and most frustrating failure mode in the whole category. Start on stock firmware to confirm the hardware itself works, then move to muOS, GarlicOS/ArkOS or OnionOS depending on which handheld it is, once the ROM library is large enough that the stock front end’s limits start to show. And keep a second, small card around for testing firmware changes — it’s the cheapest insurance available against losing a carefully built save-state library to an experiment gone wrong. None of this is specific to one handheld: it applies as much to a Miyoo Mini Plus as to any Anbernic model it’s up against, because the handheld was never really the hard part.