R36H SD Card Setup: Back Up, Verify and Replace
A new microSD card can help if the current card is faulty, too small or you want a separate copy for experimenting with firmware. The included card is not proven to fail on a particular schedule, and a black screen or missing game does not by itself diagnose card failure. Keep the original working card untouched while you prepare and test a replacement.
1. Record What Is Working
Before removing a card, note which slot it came from, the firmware shown in settings, and the exact motherboard or board revision if you can identify it. R36H-branded units are not all interchangeable: a firmware project's device list and installation steps need to match your particular revision. If you cannot verify a match, keep the existing setup and ask the project's maintainers or seller for the correct image.
2. Back Up the Original Card
Power the handheld off before removing a card. Copy personal saves, settings and other files you are entitled to keep to your computer. If you may need to restore the complete bootable setup, also make a full-device image of each original card with a reputable disk-imaging tool; a file copy alone may omit boot and hidden partitions. Label the image with its slot and board revision, then check that the image file exists and can be opened by the imaging tool. Do not format or overwrite the only working card.
3. Choose and Verify the Replacement
Choose capacity for the firmware image and your own storage needs, subject to compatibility stated by your device or firmware project. No single brand, 64–128 GB range or 256 GB cutoff is established as best for every R36H revision. Buy from a seller you trust and test the actual card you receive. Our R36H accessories page lists the cards and the card reader we point owners to. The SD Association's A1/A2 ratings describe specified card performance, but they do not guarantee a particular emulator's speed or compatibility with this handheld.
On a new, empty card, F3's f3write followed by f3read writes test files across available space and reads them back to check capacity and data integrity. Select the mounted replacement volume carefully; the test fills its free space, so leave your backup and original card disconnected. Review any errors before using the card. The project's raw-device f3probe --destructive mode erases data and is not required for this workflow.
Keep a rollback path
Verify the replacement before writing firmware, retain your original card and its backup, and do the first boot with the original still available. Testing a card does not prove that a firmware image matches your board.
4. Install Only an Image That Matches Your Board
Use the current instructions from the firmware project you selected, including its download source, supported board list, checksum if provided, imaging method and first-boot procedure. For example, dArkOSRE's installation guide lists board-specific paths and separate second-card steps; its list is not blanket support for every R36H-labelled device. Write to the new card only, and follow that project's partition and second-card directions rather than assuming a universal TF1/TF2 layout.
If the new card does not boot, switch off, reinsert the untouched original and check the exact board ID, image and any project checksum before changing other files. A card read test alone cannot distinguish a wrong firmware image, display configuration, reader issue or hardware fault. Our screen diagnosis guide covers the display-specific checks.