-
Notifications
You must be signed in to change notification settings - Fork 0
Installation
Draft — some per-device steps still need on-hardware confirmation. Verified flows are marked ✅; unconfirmed ones are marked
⚠️ .
LodorOS ships as one zip that boots every supported device — each device reads its own platform folder at boot. How you get that zip onto a card differs by device boot class.
-
The card must be FAT32. LodorOS mounts the data card as
vfat. An exFAT card (macOS's default for cards ≥ 32 GB) will silently fail to mount and the device falls back to its stock OS. If your card is exFAT, reformat it as MS-DOS (FAT) / FAT32 first. -
Extract the contents of the zip to the card root, including hidden folders. The zip contains
.system/,.tmp_update/,.userdata/and more. Use a real unzip (unzip -o), not a Finder/Explorer drag — a drag can silently skip the dot-folders and the device won't boot.
macOS note: after extracting, run
dot_cleanon the card to strip._junk, and eject cleanly (diskutil eject). Do not force-unmount — a forced unmount can leave the FAT32 with orphaned clusters, which stops the device mounting it. If a previously-working card suddenly won't boot, rundiskutil repairVolumeon it.
The volume label does not matter — name the card anything.
Miyoo Mini Plus (miyoomini), Miyoo A30 (my282), Miyoo Flip V2 (my355)
These boot from internal flash and read the SD card only for data. LodorOS installs by a stock-firmware boot hook.
- Format the SD card as FAT32.
- Extract the LodorOS zip onto it (contents at the card root, hidden folders included).
- Insert it into the device and power on. The stock firmware detects the card and launches LodorOS.
RG35XX Plus / H, RG34XX, RG28XX, RGcubeXX, RG40XX
The H700 boots its OS from the SD card, so it uses a two-card arrangement (the same one MinUI uses on these devices):
-
TF1 (slot 1) — your stock Anbernic card. You reuse the card that came with the device; you do not flash or reformat it. You only add one file: copy
rg35xxplus/dmenu.bin(from the LodorOS zip) to the root of its main FAT32 partition (the "NO NAME" partition that holds theanbernicfolder). Thatdmenu.binis what boots LodorOS from the second slot — it mounts slot 2 by device (/dev/mmcblk1p1) and launches.system/<platform>/paks/MinUI.pak/launch.shfrom it.⚠️ Never reformat the stock TF1 card — its Allwinner boot layer lives in the card's raw sectors and can't be recreated by copying files. Reformatting it bricks the device to a black screen. - TF2 (slot 2) — the LodorOS data card. A plain card formatted FAT32, with the LodorOS zip extracted onto it (contents at root, hidden folders included). Label irrelevant.
To install:
- Format a card FAT32, extract the LodorOS zip onto it → this is TF2. Put it in slot 2.
- On your stock Anbernic card, copy
rg35xxplus/dmenu.binto the root of its main partition → this is TF1. Put it in slot 1. - Power on with both inserted. It boots LodorOS.
(This mirrors MinUI's own rg35xxplus two-card install — if you already run MinUI on the H700, your existing boot card already works as TF1.)
Rockchip RK3566. Like the H700 it boots from SD, so it's a two-card setup — but here the OS card must be flashed with a bootable image, not format-and-extract.
-
OS card (left / TF-OS slot): download Moss (
.img.gz) from shauninman/Moss releases — a pared-down JELOS fork that boots MinUI-family systems on RK3566 — and write the image to the card with an imaging tool (balenaEtcher, Raspberry Pi Imager, ordd). Do not just copy files. - Game/data card (right / TFGAME slot): a card formatted FAT32 with the LodorOS zip extracted onto it.
To install:
- Flash Moss to the OS card with balenaEtcher → left slot.
- Format a card FAT32, extract the LodorOS zip onto it → right slot.
- Power on; first boot runs a one-time init (~a minute).
Moss is non-functional on its own — it needs the LodorOS/MinUI data card alongside it.
Head to Reaching your RomM server to connect the device to your library.