Linux packages
AppImages, tarballs and software install zips
Every Linux release ships the same application in four wrappers. This page says which file to take, how to run it, and how to rebuild any of the wrappers from an unpacked package or from the source tree.
Which file to take
Two processors are published: Intel and AMD (x86_64), and ARM64. Take the file that matches the machine you will flash from, not the player.
| File | Processor | What it is |
|---|---|---|
UpdaterCE.appimage | Intel / AMD | One file that runs on its own. Needs chmod +x. |
UpdaterCE-arm64.appimage | ARM64 | The same single file for ARM boards and ARM laptops. |
UpdaterCE-Linux-Portable.tar.gz | Intel / AMD | The application folder in a tarball. Unpack it and run the launcher inside. |
UpdaterCE-Linux-Portable-arm64.tar.gz | ARM64 | The ARM64 folder in a tarball. |
UpdaterCE-Linux-Portable.zip | Intel / AMD | The same folder as a zip, for machines where zip tools are more familiar. |
UpdaterCE-Linux-Portable-arm64.zip | ARM64 | The ARM64 folder as a zip. |
UpdaterCE-Lite.tar.gz | Any | The terminal-only payload, about 17 KB of Python. Flashing tools are fetched when a task needs one. |
All of the files above carry the terminal interface, so --tui opens the same application without a window.
Running what you downloaded
An AppImage is a single executable:
chmod +x UpdaterCE.appimage ./UpdaterCE.appimage
If it stops with a FUSE message, either install libfuse2 (libfuse2t64 on Ubuntu 24.04) or run it unpacked:
./UpdaterCE.appimage --appimage-extract-and-run
A tarball or a zip is a folder. Unpack it and run the launcher in it, keeping the folder together, because the application looks for its own files beside itself:
tar -xzf UpdaterCE-Linux-Portable.tar.gz cd InnioasisUpdater && ./Innioasis-Updater
For the terminal interface instead of a window, add --tui:
./UpdaterCE.appimage --tui
The launcher script does the same work without a manual download. Copy this into a terminal:
curl -fsSL https://innioasis.app/run_linux.sh | bash
It reads your processor, fetches the matching build, and offers install, a window session, or a terminal session. To skip the menu, pass the choice through: curl -fsSL https://innioasis.app/run_linux.sh | bash -s -- tui.
Building an AppImage from an unpacked package
An AppImage is an AppDir in a squashfs wrapper, so the way back to one is to unpack a working AppImage and pack it again.
- Unpack the AppImage you already have. It writes an AppDir named
squashfs-rootnext to you:./UpdaterCE.appimage --appimage-extract
- Make the changes you want inside
squashfs-root. The desktop entry and the icon live at the top of that folder, andAppRunis the entry point. - Pack the folder again with
appimagetool. The app repository'sbuild_appimage.shdownloads the tool when it is missing, so a copy may already be in your build cache:appimagetool squashfs-root UpdaterCE.AppImage
Pack for the architecture you are on. An AppImage built on an ARM64 machine runs on ARM64 machines, and an x86_64 build runs on Intel and AMD. To build the other one, run the same steps on that processor, or build from source as described below.
Building a tarball or a zip from the same folder
Both wrappers are the AppDir contents and nothing else. Keep the executable bit, which both tar and zip record, and keep the folder layout unchanged.
tar -C squashfs-root -czf UpdaterCE-Linux-Portable.tar.gz . cd squashfs-root && zip -r ../UpdaterCE-Linux-Portable.zip .
If a file arrives without its executable bit after unpacking, restore it by hand:
chmod +x Innioasis-Updater
Name the file after the processor it was built for, so nobody has to guess later. The published names are UpdaterCE-Linux-Portable.tar.gz and UpdaterCE-Linux-Portable-arm64.tar.gz, with the same pattern for the zips.
Building from the source tree
The releases are produced by scripts in the application repository, and the same scripts run on your machine. They need Python 3.10 or newer, and on Linux also curl, file and desktop-file-utils.
git clone https://github.com/y1-community/updater-ce-neo cd updater-ce-neo ./build_appimage.sh --brand updater_ce
The AppImage lands in dist/. The script downloads appimagetool itself when it is not already present, and it accepts --clean when you want the build cache thrown away first.
Other platforms and other payloads use their own scripts in the same repository:
| Script | Produces |
|---|---|
build_appimage.sh | The x86_64 AppImage, and the AppDir the tarball and zip are made from. |
build_macos.sh | A .app bundle and an optional .dmg, with --arch universal2 for both Mac processor families. |
build_windows.ps1 | The Windows executable, the portable folder, and an Inno Setup installer when Inno Setup 6 is installed. |
scripts/build_lite_payload.py | The terminal-only payload that UpdaterCE-Lite.tar.gz carries. |
scripts/verify_linux_runtime.py | A pass or fail on a bundle that would not run on older distributions. Run it before you publish anything. |
The verifier rejects a bundle that needs glibc newer than 2.35, bundles a Python newer than 3.12, is missing an xcb client library, or contains instructions (SSE4.2, POPCNT, AVX) that older processors do not have. A build that fails it may run on your machine and nowhere else.
Checking a download
Each file is published beside a .sha256 file with the same name plus the extension, and the value covers the archive itself:
curl -fsSLO https://github.com/y1-community/innioasis-updater/releases/latest/download/UpdaterCE-Linux-Portable.zip curl -fsSLO https://github.com/y1-community/innioasis-updater/releases/latest/download/UpdaterCE-Linux-Portable.zip.sha256 sha256sum -c UpdaterCE-Linux-Portable.zip.sha256
The .sha256 files name the archive they belong to, so sha256sum -c looks for it in the same folder.