What is installed on the console when it arrives
The R36 Max runs an open-source Linux system with an EmulationStation-style menu that sorts your games by console. Units leave the factory with a Linux image supplied by the manufacturer, and some batches arrive with ArkOS already installed. The system lives on the microSD card in the TF1 slot, on the right-hand side. The card in the TF2 slot, on the left, holds the games. Changing the firmware therefore simply means rewriting what is on the TF1 card. That is reassuring: a microSD card can be copied in full on a computer and restored exactly as it was if needed.
Before you change anything, work out what you have. The boot screen and the look of the menu usually tell you whether it is the factory image or ArkOS. Also make a note of what works well on your unit: buttons, sticks, triggers, sound, brightness. This short checklist becomes your reference after a change, so you can confirm in a few minutes that nothing has gone missing along the way.
Why some owners switch systems
The reasons vary. Some people want newer emulator versions or finer per-console settings. Others want a different menu, new themes, or support for a USB Wi-Fi dongle plugged into the OTG port. That dongle is sold separately and whether it works depends on the firmware, as the console has no built-in Wi-Fi or Bluetooth. Community projects also release fixes from time to time. None of this is guaranteed: each project moves at its own pace, and a newer system is not necessarily a better fit for your console.
There is also a good reason to leave things as they are. If the factory image or ArkOS runs well for you, there is no need to flash anything. A new system does not change the hardware: the Rockchip RK3326 processor and its 1 GB of memory stay exactly the same. 8-bit and 16-bit consoles, arcade classics and plenty of PS1 games run well. N64, PSP and Dreamcast games, on the other hand, depend heavily on the title and the settings. PS2 remains out of reach.
| Option | What it is | Worth knowing |
|---|---|---|
| Factory Linux image | The system installed by the manufacturer on the TF1 card | Your starting point: back it up as an image before changing anything |
| Pre-installed ArkOS | ArkOS already on the card in some batches at delivery | Depends on the batch: identify it before looking for an update |
| ArkOS for R36 Max (AeolusUX K36) | ArkOS builds prepared for the R36 Max by a community project | Project archived since August 2025, no new releases expected |
| dArkOS4Clone | A spin-off of dArkOS for clone consoles | Lists the R36Max, with no guarantee: read the notes and known issues |
| Your backup image | A full copy of your TF1 card in .img format | Lets you go back to exactly how things were before |
The best-known community options
Two community projects come up regularly for this console. The first is ArkOS for R36 Max, from the AeolusUX K36 project. The project has been archived since August 2025. That generally means no new releases or fixes are expected, although the published files may remain available. It suits anyone happy with a frozen version, not someone who wants a system that keeps developing. Read the release notes and reported issues before deciding.
The second is dArkOS4Clone, a spin-off of dArkOS designed for clone consoles, which includes the R36Max among its listed devices. Being listed does not guarantee that every feature works on every batch. Check the device list, the instructions and the known issues on the project page, and only download from that source. These are community projects: they come with no warranty of any kind.
The golden rule: copy your data, then make a full image
Your games and save files live on the cards. So start by putting the TF2 card into a computer and copying everything on it to a dated folder. Depending on the system and emulator, saves are stored either alongside the games or on the system card, so copy the readable folders on TF1 as well. Be aware that the system card contains several partitions, some of which Windows cannot read. If your computer offers to format the card, decline: that message does not mean the card is damaged.
Next, make a full image of TF1 with a standard imaging program that can read the whole card to a .img file. Store that file on your computer and in a second place, such as an external drive. Better still, install the new system on a second card and keep the original card untouched in a drawer. Going back is then as simple as putting the old card back in.
- Switch the console off and remove TF1 (right) and TF2 (left).
- Copy everything on TF2 and the readable folders on TF1.
- Read the whole of TF1 to an image file named with the date.
- Check that the file size matches the capacity of the card.
- Keep this image in two different places.
Choosing an image made for the 720 × 720 screen
The R36 Max uses a square 4-inch IPS screen at 720 × 720 pixels. An image built for a different screen, such as the 640 × 480 panel on the R36S or the 1024 × 768 panel on the R36 Max2, may not be able to drive this display. The possible result: the console appears to boot, but the screen stays black. Choose an image that explicitly names the R36 Max. Watch out for similar names: the R36 Max2, R36 Ultra and R36H Pro Max are different devices, even when the advertised screen looks the same.
Before writing the image, check its checksum if the project publishes one, and read the installation instructions all the way through. Write it to the system card or to a good-quality spare card, using the same kind of program. Charge the console before the first boot, which can take longer than usual. Finally, how 4:3 games are displayed, with bars at the top and bottom, depends on the system and emulator you choose.
If something goes wrong: restore your backup
Black screen, boot loops, buttons not recognised properly: don't panic, this is exactly what your image is for. Switch the console off, remove the TF1 card and put it into the computer. Using the imaging program, write your .img file to the card. The target card must be at least as large as the original, because an image will not fit on a smaller card. Put the card back in the right-hand slot, restart, then copy your games and saves back to TF2 if you had moved them.
Bear in mind that changing the firmware is done at the owner's own risk. We do not supply or support community firmware for the R36 Max sold here, the original square-screen model released in November 2024, so look for images made for this exact model. If in doubt, sticking with a system that works is a perfectly sensible choice.
Frequently asked questions
Can I update the R36 Max without a computer?
The console has no built-in Wi-Fi or Bluetooth. Some systems include update tools in their menu, which may work with a USB Wi-Fi dongle plugged into the OTG port, sold separately and depending on the firmware. To back up the card as an image or install a completely different system, you still need a computer with a microSD card reader.
Can a different firmware improve battery life?
For the 4000 mAh Li-Po battery, runtime is up to 6 h announced by the manufacturer. Real-world battery life depends mainly on brightness, volume, the emulator and the game. A different system may use different default settings, but there is no guarantee of any improvement. For a fair comparison, play the same game at the same brightness and volume.
Which card should I use for games after switching?
The console accepts cards up to 128 GB. Capacity changes how many games fit, not performance, and the usable space after formatting is less than the stated capacity. Follow the card format recommended by your chosen project, as not every system organises its folders in the same way. Only copy games you have the right to use.
The console shows no sign of life after flashing. What should I do?
If even the small LED between Select and Start stays off, check the battery first. Charge it through the USB-C port marked DC, using a 5 V adapter rated at 1.5 A or more (not included). Then try booting with the original card or your restored image. If nothing changes, the system may not be the cause.
Sources
Our guides are based on the supplier's product sheets and publicly available documentation. We don't claim any hands-on testing.