How to Install ArkOS on R36H

ArkOS is the most popular custom firmware for the R36H. Follow our complete firmware setup guide for detailed step-by-step instructions on downloading, flashing, and configuring ArkOS on your R36H.

Quick Steps

1. Download ArkOS image for RG351MP/R36H from GitHub
2. Flash to a quality microSD card using Balena Etcher
3. Insert into R36H TF1 slot and power on
4. Wait for initial setup (2-5 minutes)
5. Configure device type as R36H in settings

Before You Begin

You need a microSD card from a brand you trust, a card reader, and a computer. Do not use the card that came with the device for this — keep that one untouched as your route back to the factory state. A 64GB card is enough for the operating system and a substantial library; going larger only matters if you intend to store disc-based systems.

Step By Step

1. Download the correct image. ArkOS releases are published per device family on the project's GitHub. The R36H uses the RG351MP-class image. Downloading the wrong variant is the single most common mistake, and it produces a device that either will not boot or boots with a broken screen.
2. Write it to the card. Balena Etcher is the usual tool because it verifies the write afterwards. Extract the archive first if the image is compressed, then select image, select card, and flash. Expect this to take several minutes.
3. Insert into TF1. The first slot is the system slot. The card must go here — in the second slot it will be treated as storage and ignored at boot.
4. First boot. Power on and wait. The initial startup expands the filesystem and builds its databases, which can take several minutes and may look like it has hung. Do not power off during this.
5. Set the device type. In the settings, tell ArkOS it is running on an R36H. This sets the correct button layout and, importantly, makes Select work as the hotkey modifier — without it, the hotkey combinations will not behave as documented.

If The Screen Stays Black

This is expected often enough that it should not worry you. It almost always means the display panel in your unit differs from the one the image assumes, and it is corrected by replacing the device tree file on the card's boot partition with the variant that matches your panel. The screen troubleshooting guide walks through identifying which one you have.