If you want to add roms r36s the right way, the trick is not the copy itself, it is understanding which card your handheld is reading from and letting ArkOS build the folder structure before you start. The R36S usually boots from the TF1 system card, while a dual-card setup uses TF2 as the main game card after you switch storage in the Advanced menu.
This is where a lot of new owners get tripped up. One ArkOS image may show an accessible games partition called GAMES, while other setups expose a partition called Easyroms, so the label can vary even though the job is the same. I have lost more time to invisible partitions than to actual ROM transfers, especially on Windows when the card is fine but the games partition has not shown up properly yet.
This guide covers transferring files you already own or have legally backed up. If you searched for terms like retroarch roms download or retroarch roms pack, the practical part you actually need here is how to organize your own library so ArkOS and RetroArch can see it cleanly.
KEY TAKEAWAYS
- The cleanest R36S workflow is to decide first whether you are using TF1 only or a dual-card TF1 plus TF2 setup.
- ArkOS should create the ROM folder structure for you before you start dragging files around.
- ROM files go into system-specific folders, while BIOS files belong in the
biosfolder on the games partition. - A proper shutdown, a decent card reader, and a branded microSD card prevent most of the pain.
- If you are copying from the stock card, back it up before you touch a single file.
How to add roms r36s without breaking your setup
The safest R36S method is to let ArkOS define the storage map first, then copy files into the folders it creates. In a dual-card setup, the system can populate the second card with the proper ROM directories when you go to Options > Advanced > Switch to SD2 for ROMs.
That menu step matters more than it looks. ArkOS uses it to prepare the second card for a ROM library, and after the switch both cards are typically needed for booting in that configuration. If you skip this and just dump files onto a random blank card, you are basically volunteering for an avoidable troubleshooting session.
One quiet failure point is that the second card can look blank or unusable if the handheld did not mount it properly the first time. I always check the card again on the device before blaming the files, because a bad mount, a weird format choice, or a flaky card wastes more evenings than the ROM copy itself.
If your handheld is still fresh out of the box, this practical first-boot setup walkthrough that explains the menu path, slot layout, and prep work before file transfers will make the next fifteen minutes much smoother.
Choose your storage method first
The first decision is whether you want a single-card setup or a dual-card setup. ArkOS supports both, but the dual-card method is usually cleaner because TF1 handles the operating system while TF2 handles the game library. That separation also makes future OS changes less messy, because your games are not living on the same card as the system files.
A single-card setup still works. In that case, you add ROMs and BIOS files to the accessible games partition on the OS card itself, which may appear as GAMES or Easyroms depending on the image and version you are using. This approach is fine for smaller libraries, but it gives you less breathing room if you later want a bigger card or a cleaner reflash.
Card quality is not a boring side note here, it is part of the setup. The bundled generic cards that ship with many handhelds are famous for acting fine right up until they ruin your mood. Before a long copy session, I would much rather swap in a decent branded card than trust the mystery card that arrived in the box.
Before a big copy job, this storage upgrade guide that compares better microSD options for the R36S is worth a quick look.
What you need before copying anything
A reliable microSD card reader makes the whole job easier. Better readers improve transfer speeds and reduce corruption headaches during flashing and large file moves. If you already own one that behaves properly, great, use it and move on.
A backup of the stock card is the other non-negotiable. A common migration workflow is to copy the stock card’s visible games content to a folder on your PC, boot the fresh ArkOS card once so it finishes its initial setup, and then move that saved content onto the new card’s accessible ROM partition. That is the grown-up version of this process, and it saves a lot of swearing later.
A proper shutdown also matters. ArkOS devices behave more like little Linux computers than plug-and-play toys, so you should shut the handheld down from the menu before pulling a card. It feels fussy at first, but it is cheaper than file-system repair.
If you are still deciding whether the handheld deserves the effort, this hands-on R36S review that covers the device’s tradeoffs, strengths, and who it suits best gives the wider context.
Step-by-step transfer method
The first step is to back up the original card or cards in full. If your R36S came with a stock library, copy the visible games partition contents to a folder on your computer before you experiment with anything else.
The second step is to prepare your target setup. If you are using a fresh ArkOS install on TF1, flash the card, insert it into the TF1 slot, boot the handheld, and let ArkOS complete its first-run partition resize and initialization. Do not rush this part, because the system is still arranging itself.
The third step depends on whether you are using TF2. If you want a dual-card layout, insert a blank second card into TF2, open Options > Advanced, and select Switch to SD2 for ROMs so ArkOS creates the correct folders on the second card. Once that finishes, shut the handheld down properly before removing the card.
The fourth step is the actual file transfer. Put the target card into your computer, open the accessible games partition, and copy each ROM into the matching system folder rather than dumping everything in one place. This is the point where being tidy saves you from browsing chaos later.
The fifth step is BIOS placement. ArkOS expects BIOS files inside the bios folder on the games partition, and some systems will not boot properly or will behave oddly without the correct files in that location. If a console mysteriously refuses to launch while others work, the BIOS folder is one of the first places I check.
The sixth step is to reinsert the card and boot the device again. After that, your systems should populate in the menu based on the folders and files ArkOS can see. If the library looks incomplete, it is usually a folder-name issue, a file-format mismatch, or a BIOS problem rather than some magical curse.
| Checkpoint | What you should see | What usually went wrong if you do not |
|---|---|---|
| TF1 after first boot | ArkOS boots normally and finishes setup | The flash was bad, the card is weak, or the system was powered off too early |
| TF2 after switching ROM storage | New system folders appear on the second card | The card was not mounted properly, the format was not accepted, or the storage switch did not finish |
| Games partition on PC | A visible GAMES or Easyroms style partition | Windows has not assigned it properly yet, or the reader is being awkward |
| BIOS folder | A clear bios directory on the games partition | You are looking at the wrong partition or ArkOS did not finish creating the structure |
| After reinserting the card | Consoles appear in the menu with your library | ROMs are in the wrong folders, the system names do not match, or the BIOS files are missing |
Method 1, dual-card setup
The dual-card method is the best default for most people. TF1 stays focused on ArkOS, and TF2 becomes the main home for your ROM collection once you switch to SD2 in the menu.
This is also the least annoying route for future maintenance. If you reflash TF1 later, your ROM card can remain separate, and ArkOS also includes an option to read from SD1 and SD2 in Advanced settings if you want to use storage across both cards. That flexibility is handy when your library starts small, then suddenly contains every PlayStation game you loved in 1999.
A small but nasty friction point shows up when TF2 is smaller than the card you started with. Some storage-switch workflows try to copy existing ROM content across, so a too-small second card can fail halfway through or leave you thinking the slot is broken. I only made that mistake once, and it was enough to make me check free space before every migration after that.
A smart internal link belongs here because storage choices affect everything else. This capacity and card-quality guide for the R36S, especially useful if you are picking a TF2 card for larger PS1 and Dreamcast libraries fits naturally at this point.
Method 2, single-card setup
The single-card method is simpler in hardware terms, because you only manage one card. In that workflow, you use the accessible games partition on the OS card itself and place ROMs and BIOS files in the folders ArkOS provides there.
The catch is visibility. Some Windows systems will not show the games partition cleanly until it has been mounted properly, and that creates the illusion that ArkOS never made the folders. I have seen people reflash a perfectly good card because the partition looked missing, when the real problem was simply that the PC had not exposed it in a useful way.
Where ROMs and BIOS files actually go
ROM placement is system-folder based, not free-form. ArkOS exposes folders for each platform on the accessible games partition, and you should place each game file in the folder for its console instead of inventing your own structure. That sounds obvious until you see a root directory full of loose files and realize someone got optimistic.
BIOS placement is more specific. The BIOS files belong inside the bios folder, and some systems also expect particular filenames to work correctly. In practice, if your ROM appears in the menu but the emulator fails on launch, BIOS is often the missing piece.
Partition names can differ, so do not get hung up on the label. Some workflows refer to Easyroms, while others describe the accessible partition as GAMES, and both point to the user-facing storage area where your ROM folders live.
RetroArch is part of the bigger picture too. ArkOS uses RetroArch for many systems, which is why ROM placement, BIOS files, and supported file formats all matter together rather than as separate chores. A handheld library is not just a pile of files, it is a relationship between storage, frontend, and emulator expectations.
Common mistakes that waste an evening
The most common mistake is copying files before ArkOS has created the folders for the target card. The safer workflow is always to let the handheld initialize first, then use the menu option to prepare TF2 if that is your setup. It is the difference between following the map and drawing one in the dark.
The second common mistake is trusting the stock card too much. Bundled generic cards are frequently the weakest part of the whole setup, so cloning or backing them up early is just common sense. If you are mid-transfer and the card starts throwing weird behavior, assume the card before you assume your sanity.
The third common mistake is bad housekeeping after a Mac transfer. macOS often creates ._ metadata files alongside your ROMs, and those extra files can clutter menus or create duplicate-looking entries on Linux-based handhelds. I now check for those first whenever a freshly copied library looks messier on the device than it did on the computer.
The fourth common mistake is assuming the second card will be read automatically with no configuration. ArkOS specifically uses the Advanced menu options for switching ROM storage, and some setups behave better after a restart or an interface refresh. Menu path matters here, which is not glamorous, but it is real.
Conclusion
The clean way to add roms r36s is simple once you stop treating the handheld like a mystery box: decide on single-card or dual-card storage, let ArkOS create the expected folders, copy ROMs into the correct system directories, and place BIOS files in bios. If you back up the stock media first, use a reputable card, and shut down properly before removing anything, the process is much more boring, and boring is exactly what you want from file management.
