Install PortMaster in KNULLI and Add One Ready-to-Run Port

by

Owner testing: No — this is a documentation-led procedure
Example: 2048, conditionally, only when that exact title appears under Ready To Run Ports on your device
Source and catalog check: 2026-10-26

KNULLI provides a PortMaster installer, but PortMaster is not necessarily installed already. The installer location depends on your KNULLI release. After you install PortMaster, its live catalog is filtered for ports eligible for the handheld; that filtering is a useful gate, not a promise that a listed port will launch or work perfectly.

This guide uses 2048 for one deliberately narrow setup check. Continue only if the exact title 2048 appears under Ready To Run Ports. If it does not, stop. Do not use All Ports, choose 2048 Plus, or substitute another game.

Scope and eligibility

This procedure is for an RG CubeXX/H700 running one of these known KNULLI branches:

  • Firefly 20241204
  • Gladiator II 20250813
  • Scarab 20260511
  • a later build whose visible menu hierarchy still matches the current KNULLI documentation

Before continuing, all of the following must be true:

  1. You know the exact installed KNULLI release.
  2. KNULLI boots normally into EmulationStation.
  3. The release-appropriate PortMaster installer entry is visible.
  4. The device has working Internet.
  5. After installation, PortMaster appears in Ports.
  6. PortMaster can finish its launch update activity and open Ready To Run Ports.
  7. The exact title 2048 is visible in that list.

Stop if the release is unknown, the expected menu entry is missing, the menus materially differ from those below, or an on-screen action would have to be guessed. This guide does not cover a manual installer, file transfer, sideloading, shell access, permissions, storage formatting, or substitute port.

Short answer

Identify your KNULLI release, connect to working Internet, then use the correct installer:

  • Firefly 20241204 or Gladiator II 20250813: Ports → Install.PortMaster
  • Scarab 20260511 or a matching current build: Start → Device Settings → Install Portmaster

After EmulationStation restarts or reloads, confirm PortMaster appears in Ports. Open Ports → PortMaster, let its documented launch update activity finish, then open Ready To Run Ports. Install 2048 only if that exact title is present. Exit PortMaster from its main menu, let EmulationStation restart and rescan, and check Ports → 2048.

A successful check ends when one launch reaches a stable, recognizable 2048 game screen. It does not certify controls, saves, audio, performance, long-session stability, every KNULLI release, or every PortMaster port.

Choose the correct release route

Installed KNULLI release Exact installer route Expected completion behavior Rule for 2048
Firefly 20241204 Ports → Install.PortMaster The bundled installer runs, EmulationStation restarts automatically, and PortMaster replaces the installer in Ports. Continue only if the live Ready To Run Ports list shows exact title 2048. Current Knulli-specific 2048 handling postdates this release, so do not infer old-release success.
Gladiator II 20250813 Ports → Install.PortMaster The bundled installer runs, EmulationStation restarts automatically, and PortMaster replaces the installer in Ports. Apply the same live-list gate. Current Knulli-specific 2048 handling postdates this release.
Scarab 20260511 Start → Device Settings → Install Portmaster On completion, EmulationStation reloads and PortMaster appears in Ports. Current Knulli handling predates Scarab, but the exact live listing is still mandatory.
Later build matching current documentation Start → Device Settings → Install Portmaster, only while that visible route matches the documentation EmulationStation reloads and PortMaster appears in Ports. Treat the 2026-10-26 package evidence as mutable. Require the live listing.
Unknown release or menu mismatch None Stop. Do not infer eligibility or choose another route.

The punctuation and capitalization matter: the older entry is Install.PortMaster, while Scarab/current documentation uses Install Portmaster.

Internet is required before you begin

Connect KNULLI to working Internet before starting. KNULLI requires Internet to install and update ports, and PortMaster checks for its own updates when opened. This guide does not claim that every KNULLI release obtains the initial PortMaster application through the same download mechanism; the older route uses a bundled installer.

If Internet itself is unavailable or failing, stop and use KNULLI Wi-Fi Not Connecting or Keeps Disconnecting. Do not continue until Internet works.

If Internet works but the PortMaster catalog does not load or complete normally, stop and try again when the catalog service is available. Do not assume that this is a Wi-Fi fault.

The normal procedure uses direct outbound Internet access. It does not require an account, API token, local IP address, SMB, SSH, SFTP, Windows client, or network share.

Install PortMaster

Firefly 20241204 and Gladiator II 20250813

  1. Open Ports.
  2. Select Install.PortMaster.
  3. Follow the documented on-screen installation flow. Do not guess any button or status wording if the screen differs materially.
  4. Let the bundled installer finish and allow EmulationStation to restart automatically.
  5. Open Ports and confirm that PortMaster has replaced the installer.

Scarab 20260511 and matching current builds

  1. Open Start → Device Settings.
  2. Select Install Portmaster.
  3. Follow the on-screen installation flow without inventing confirmation or progress labels.
  4. Let installation finish and allow EmulationStation to reload.
  5. Open Ports and confirm PortMaster is present.

If the expected installer entry is missing, or PortMaster does not appear after the documented restart/reload, stop. The old manual download-and-transfer fallback is intentionally excluded. A separately chosen transfer workflow belongs to Transfer Games to KNULLI from Windows over SMB or SFTP, but it is not a prerequisite or repair procedure for this guide.

Open the live catalog and apply the 2048 gate

  1. Open Ports → PortMaster.
  2. Let PortMaster finish its documented launch update activity. Do not interrupt it, and do not claim that a particular update occurred unless the interface reports one.
  3. From the PortMaster main menu, open Ready To Run Ports.
  4. Look for the exact title 2048.

The catalog is filtered for ports compatible with the handheld. Seeing 2048 there establishes eligibility for this procedure at that moment. It does not guarantee launch, controls, saves, audio, performance, storage behavior, or future availability.

If 2048 is absent

Stop. Do not:

  • open All Ports to bypass the gate;
  • install 2048 Plus or a similarly named title;
  • substitute another port;
  • sideload a package;
  • add copied game data, patches, runtimes, or files; or
  • infer why the listing is absent.

There is no substitute example in this article.

If 2048 is present

Select 2048 and follow the current on-screen installation prompts. Do not add user-supplied proprietary game data, copy files manually, install a runtime manually, or edit a launch script.

Why 2048 is a conditional example

The official PortMaster source checked on 2026-10-26 recorded the following current metadata for 2048:

  • rtr: true;
  • install text Ready to run.;
  • runtime: null;
  • reqs: [];
  • architectures aarch64 and armhf; and
  • package items 2048.sh and 2048/.

The current launch script also contains explicit Knulli handling added in an official commit on 2026-04-10. These dated facts support using 2048 as a conditional example. They do not guarantee that it is present in a future catalog, certify it on every RG CubeXX or old release, or prove that it has no implementation dependencies. No runtime or additional requirement is declared in the current metadata, and this procedure requests no user-supplied proprietary game data.

Exit PortMaster and discover the port

After installation:

  1. Return to the PortMaster main menu.
  2. Exit PortMaster from its main menu.
  3. Let EmulationStation perform the documented restart and rescan.
  4. Open Ports and look for 2048.

Do not force-close PortMaster or restart the handheld as a substitute for this main-menu exit.

If 2048 does not appear in Ports

Use this bounded recovery ladder once:

  1. Run Start → Game settings → Update gamelists exactly once.
  2. Check Ports again.
  3. If 2048 is still absent, open PortMaster → Manage Ports.
  4. Continue only if 2048 is visibly listed and the reinstall action is visibly available.
  5. Use Manage Ports → 2048 → reinstall once and follow the on-screen prompts.
  6. Return to the PortMaster main menu, exit normally, allow EmulationStation to restart, and check Ports once more.

If the 2048 Manage Ports entry or reinstall action is unavailable, or if 2048 remains absent after that one refresh and one reinstall, stop. Do not repeat the loop, edit gamelist.xml, rename or move files, change permissions, or delete folders.

If 2048 is still absent after this bounded recovery ladder, use KNULLI Games Not Showing Up for the next library-discovery check.

Launch once and verify only the visible result

When Ports → 2048 is visible:

  1. Launch it once.
  2. Pass this check only when a stable, recognizable 2048 game screen appears.
  3. Leave using the normal exit method already documented or configured for your exact KNULLI release.

Do not require a score, move, input test, audio check, save, performance run, or minimum duration. This article does not name a universal exit chord.

If 2048 errors, immediately returns, hangs, stays black, or otherwise fails to reach the stable recognizable screen, stop and use KNULLI Visible Game Launch Failure: Emulator, BIOS, and Content Handoff. Do not edit the port, diagnose controls, or force power off as part of this procedure.

If the game reaches the stable screen but you cannot leave through the normal documented/configured method, stop. That result is outside this article’s proof boundary.

What the check proves—and what it does not

The check supports only these session-local observations

  • The release-specific installation route completed far enough for PortMaster to appear in Ports.
  • The live, filtered catalog exposed exact title 2048 on this device at that time.
  • PortMaster installed the package far enough for EmulationStation to discover its launcher.
  • This package reached a stable, recognizable game screen on this device, release, and session.

The check does not prove

  • all controls work or one exit chord applies everywhere;
  • save creation, save location, persistence, backup coverage, or uninstall treatment;
  • audio behavior, frame pacing, battery impact, performance, or long-session stability;
  • broad exFAT compatibility;
  • the identity of every internal runtime or dependency;
  • every RG CubeXX, H700 device, KNULLI release, or PortMaster port behaves the same;
  • future catalog availability, package identity, or automatic port updates; or
  • another port has the same readiness, compatibility, safety, or licensing.

Screenshots are not owner-test proof. A screenshot records only the visible state at capture time.

Update, repair, reinstall, and removal

PortMaster updates

PortMaster checks for and applies PortMaster’s own updates when it launches. Let that documented activity finish. Do not report a specific update unless the interface shows one.

This does not mean 2048 or every installed port updates automatically. For an installed port, use the current action offered under Manage Ports and follow the on-screen prompts. Do not invent submenu labels or claim background updates.

Repair PortMaster

If PortMaster later goes missing or stops working, repeat the same release-appropriate installer route only if that route is still visibly available:

  • Firefly/Gladiator II: Ports → Install.PortMaster
  • Scarab/current documented equivalent: Start → Device Settings → Install Portmaster

If the expected route is missing, stop. Do not use the excluded manual installer fallback.

Reinstall 2048

Use PortMaster → Manage Ports → 2048 → reinstall only when the installed port is visibly listed and that action is available. Follow the current prompts. Reinstallation is not permission to inspect, move, edit, or delete package files.

Remove 2048

Use PortMaster → Manage Ports → 2048 → uninstall and follow the on-screen prompts. Whether uninstall preserves or removes save data is unconfirmed, so do not rely on either outcome. Do not manually delete package folders or save files.

A complete PortMaster-uninstall procedure is not established by the reviewed evidence and is not provided here.

Storage boundary

PortMaster installs the port into KNULLI’s active logical /userdata/roms/ports area. Which physical card backs /userdata depends on KNULLI’s selected storage. Do not move or edit the installed files for this guide.

This article does not identify TF1 or TF2 as the backing device, recommend a filesystem, advise formatting or conversion, or prescribe symlink or bind-mount repairs. It also does not publish an internal PortMaster data path or a save path.

Privacy, media, and licensing

The normal flow does not require an account or private network details. Do not share or capture SSIDs, IP or MAC addresses, hostnames, account identifiers, unrelated library titles, recent-game lists, personal filenames, logs, tokens, credentials, QR codes, or private-name paths.

If this article uses media, prefer a tightly cropped menu label or a newly created release-path diagram. Remove unrelated/private content and label diagrams or mockups as illustrative. Before reusing a 2048 package or gameplay image, verify that exact asset’s reuse permission and provide the required credit.

PortMaster marks 2048 Ready to run and packages the files used by this port. The official package README credits the original 2048 creator, Gabriel Cirulli, and the Libretro port/core. That does not establish one license for the game, core, metadata, binaries, screenshots, or every packaged component, and it does not establish unrestricted reuse rights for all assets.

STOP and handoff guide

Situation Action
KNULLI release is unknown, or the expected installer menu is absent Stop. Do not guess a route or use a manual fallback.
Internet itself is unavailable or failing Stop and use Article #7.
Internet works but PortMaster’s catalog cannot load normally Stop; do not label it a Wi-Fi problem without evidence.
PortMaster is absent after the documented install and restart/reload Stop. Do not download or transfer installer files manually.
Exact title 2048 is absent under Ready To Run Ports Stop. Do not use All Ports or a substitute.
Installation interface differs enough that an action must be guessed Stop.
2048 is absent after normal exit, one gamelist update, and one visibly available reinstall Stop and use KNULLI Games Not Showing Up.
2048 is visible but cannot reach a stable recognizable screen Stop and use Article #19.
Manual transfer is separately chosen for an excluded recovery workflow Keep it outside this guide; Article #13 owns transfer mechanics.

At a stop point, do not factory-reset, reflash, format storage, expose SMB/SSH, weaken network security, delete folders, or substitute another port.

For broader RG CubeXX setup and troubleshooting routes, see the KNULLI on RG CubeXX troubleshooting and setup hub.

FAQ

Is PortMaster preinstalled in KNULLI?

Do not assume so. KNULLI provides a PortMaster installer. After the release-appropriate installation and EmulationStation restart/reload, PortMaster should appear in Ports.

Which installer path should I use?

Firefly 20241204 and Gladiator II 20250813 use Ports → Install.PortMaster. Scarab 20260511 and a later build that visibly matches current documentation use Start → Device Settings → Install Portmaster. If your release is unknown or the expected route is missing, stop.

Why must 2048 appear under Ready To Run Ports first?

The live list is filtered for the handheld and is the eligibility gate for this guide. Current metadata supports 2048 as the example, but metadata does not override what your device actually lists and does not guarantee a successful launch.

Can I choose another port if 2048 is absent?

Not in this procedure. Do not use All Ports, 2048 Plus, or another title as a substitute. Stop without changing the example.

Do I need to supply game files?

This procedure requests no user-supplied proprietary game data. Install only through the visible PortMaster entry and its on-screen prompts. Do not turn that bounded statement into a broader claim about implementation dependencies or into one shared-license claim for every component.

Does a stable 2048 screen prove everything works?

No. It proves only that this package reached a recognizable screen on this device/release/session. It does not verify controls, safe exit, saves, audio, performance, long-session stability, all ports, or future compatibility.

Where are the port files installed?

Use only the logical location /userdata/roms/ports. The physical card behind /userdata depends on the active KNULLI storage choice. No manual file operation is required or supported in this guide.

How do I update or remove 2048?

Use the action offered for 2048 under PortMaster → Manage Ports. For removal, use 2048 → uninstall and follow the prompts. Save treatment is unconfirmed. Do not delete folders manually.

Can I completely uninstall PortMaster with this guide?

No. The reviewed evidence does not establish a complete PortMaster-uninstall procedure. This guide covers reinstalling PortMaster through the same visible release-specific route and managing the example port through Manage Ports.

Do I need SMB or SSH first?

No. PortMaster uses direct outbound Internet access. SMB and SSH are not prerequisites, and this procedure does not ask you to enable either service.

Evidence labels used in this article

  • FACT: Directly stated in the reviewed official documentation or current official package metadata.
  • SOURCE-CONFIRMED: A bounded conclusion supported by the reviewed official sources, such as using live catalog visibility as this article’s eligibility gate or naming the logical storage area.
  • COMMUNITY REPORT: No community report is used as procedural evidence in this article.
  • UNCONFIRMED: Save path and persistence, uninstall treatment of saves, complete PortMaster removal, universal device compatibility, broad exFAT behavior, and future catalog availability remain unconfirmed here.

Sources and date note

Official sources reviewed for this documentation-led guide:

The current 2048 catalog/package evidence was checked on 2026-10-26. Catalog entries, package metadata, and menu behavior can change. The live Ready To Run Ports → 2048 listing and the release-matched menu path remain controlling at the time you follow the guide.