Installation

Installation

Beta (0.9.1) — the install is a plain unzip. Onboarding (including Tailscale QR sign-in), pairing, download-on-launch, and save sync have all had a hardware pass on tg5040.

Lodor-NextUI is not a firmware. It is a Tool pak (plus the Game Manager's library entry) that drops onto an SD card that already runs stock NextUI. You install NextUI the normal way first, then add Lodor on top.

Prerequisites

1. A TrimUI Brick / Smart Pro (tg5040) or TrimUI Smart Pro S (tg5050) already running stock NextUI. If you don't have NextUI yet, install it from the NextUI releases first.
2. A RomM server, version 4.8.0 or newer, reachable from the device — see Reaching your RomM server.

Install

1. Download Lodor-NextUI-0.9.1-beta.zip.
2. Unzip it to the root of your NextUI SD card, merging the zip's Tools/, Emus/, and Roms/ folders with the ones already on the card. The zip contains:

   Tools/tg5040/Lodor.pak/          Tools/tg5050/Lodor.pak/
   Emus/tg5040/LODORGM.pak/         Emus/tg5050/LODORGM.pak/
   Roms/0) Game Manager (LODORGM)/
   version.txt   README.txt
   

   Each device reads only its own platform folder; shipping both is harmless. The Emus/ + Roms/ pieces are the Game Manager's entry at the top of your games list — a launcher affordance, not a game, and still zero NextUI modification.
3. Reinsert the card and boot NextUI.
4. On the device, open the Tools menu. You should see one new entry: Lodor. Your games list gains a Game Manager entry at the top.

Use a real unzip, not a Finder/Explorer drag — the paks contain executable bits and (in Lodor.pak/hooks/) the launch hooks that a naive drag can mangle. On macOS, unzip -o Lodor-NextUI-0.9.1-beta.zip -d /Volumes/<card> and then diskutil eject. Don't force-unmount the card.

The card stays whatever filesystem NextUI already uses; Lodor adds no filesystem requirement of its own.

What lands where

• The pak lives under Tools/<platform>/Lodor.pak. There is one pak — the onboarding wizard is built in (older betas shipped a separate "Lodor Setup" pak; it's gone, folded into Lodor.pak).
• On first open of the Lodor pak, it self-installs its launch hooks into NextUI's hook directory (<SDCARD>/.userdata/<platform>/.hooks/{pre-launch,post-launch,boot}.d/) and starts the background sync daemon. This wiring is idempotent and self-healing — re-running the pak re-verifies it, and the Game Manager library entry is re-created if it goes missing.
• Your connection config is written to NextUI's shared userdata at <SDCARD>/.userdata/shared/Lodor/config.json (survives a pak reinstall; shared across NextUI profiles). You never edit it by hand for a normal setup — the onboarding wizard writes it.
• Where games go: by default, RomM games merge into your existing Roms/ folders, tracked by a safety manifest — your own files are never modified. Cards that previously used an older beta's separate-folders layout get a one-time "Where should RomM games go?" prompt on first open; fresh cards are never asked.
• Uninstalling: Tools → Lodor → Remove Lodor from this card removes exactly what Lodor's manifest owns (stubs, its covers/collections, hooks, the Game Manager/Continue entries) — downloaded games are kept unless you choose otherwise, and saves are never touched. It then tells you the one folder left to delete by hand.

Next

Open Tools → Lodor — the first open runs onboarding. See First-run onboarding.