AndronixOrigin: the shell scripts that install Linux on Android through Termux and PRoot

What AndronixOrigin actually contains, and who it is for

This repository is the back end of the Andronix app, not the app. The README describes it as the place where "you can know all the scripts you're installing," and the directory listing backs that up: Rootfs, Installer, WM, Bootstrap, APT, Pacman, XBPS, Fedora, Uninstall, Assets. Those names map onto the moving parts of a Linux-on-Android install. Rootfs and Bootstrap hold the base filesystem material, the package-manager directories (APT, Pacman, XBPS) hold per-distro setup, WM holds window manager and desktop environment scripts, and Installer and Uninstall drive the whole thing.

The audience is narrow and specific. First, people who already use the Andronix app and want to see what runs on their device before they trust it with a rootfs. Second, anyone building their own Termux-based Linux installer who wants a working reference for how a distro is unpacked, patched and wired to a VNC server. Third, contributors: the README has a Development Docs section, though it admits "We are working on it," so the scripts themselves are the documentation for now.

What it is not: a standalone product. There is no build system, no test suite and no CLI entry point described in the README. You cannot clone this and get a Linux desktop. The scripts assume the surrounding app or a Termux session with the right packages already present.

PRoot is the mechanism, and it explains both the reach and the limits

Andronix runs distributions without root and without a custom kernel. The README is explicit: "Andronix uses PRoot to run your favourite Linux distribution on your Android devices." It then quotes the PRoot project's own description, that PRoot is a user-space implementation of "chroot, mount --bind, and binfmt_misc," letting an unprivileged user treat an arbitrary directory as the new root filesystem and execute binaries built for another CPU architecture through QEMU user-mode.

That single design decision cascades. Because there is no root and no kernel modules, the distro is a directory tree, not a partition. You can keep several side by side, and the README claims "12 OS at once given that you have the storage for it." Uninstalling is deleting a directory, which is why the Uninstall directory exists as a peer of Installer rather than a footnote.

The cost is equally direct. The README lists the constraints plainly: "the lack of the full Linux kernel, the SELinux policies of your Android versions, your CPU architecture and your device's hardware." Anything that needs kernel features, kernel modules, systemd as PID 1, or privileged networking will not behave as it does on a laptop. The README's own guidance is that web browsing, coding and other light work are fine, and it points to a separate page for "what you can't do on Andronix systems." That page is where the real compatibility list lives, and the README does not reproduce it.

Installing a free distro: from the app to a running shell

The README does not give a command-line install sequence for AndronixOrigin. It gives the product route. The badges at the top point to Google Play (package id studio.com.techriz.andronix) and to GitHub Releases, and the installation documentation lives at docs.andronix.app/installations/non-modded-os. If you want the supported path, that is it: install the app, pick a distro, and the app runs the scripts from this repository.

For the manual route, Termux is the prerequisite the README names: "We use Termux to provide the command line and the packages that are especially compiled for Termux implemented inside Andronix." The repository ships a helper at the root, repo-fix.sh, which the naming suggests repairs package repositories inside a Termux-based install. The README does not document its flags, so treat it as something to read before running rather than a command to paste blind.

What a first real use looks like once a distro is installed is a VNC session. The repository root carries tigervnc-1.10.1-1-aarch64.pkg.tar.xz and its .sig file, an aarch64 Arch package for TigerVNC, and WM holds the desktop environment and window manager scripts. The README lists LXDE, LXQT and XFCE as desktop environments and Awesome, Openbox and i3 as window managers. So the intended first run is: install a distro, install a desktop or window manager from WM, start the VNC server, connect a viewer. The repository layout supports that reading; the README itself does not spell out the commands.

A reader who wants to see what a script does before it runs can inspect the tree directly:

git clone https://github.com/AndronixApp/AndronixOrigin
cd AndronixOrigin
ls Rootfs Installer WM

The listing should show the distro rootfs material, the install and uninstall scripts, and the desktop environment scripts. If a distro you want is not under Rootfs, it is not offered as a free un-modded OS.

The free and paid split is the limitation that matters most

The README answers the open-source question with unusual candour: "Yes but no." The free distro tar files and the shell scripts are on GitHub. The Android app and everything concerning Andronix Modded OS are closed source. That is a real boundary, not a licensing technicality. If your interest is the Modded OS images (Ubuntu XFCE, Debian XFCE, Ubuntu KDE, Manjaro XFCE), this repository will not show you how they are assembled. You get the un-modded eight: Ubuntu, Debian, Manjaro, Fedora, Kali, Void, Alpine, Arch.

The second limitation is documentation depth. The README links to docs.andronix.app for installations, software and development, and the Development Docs section is marked as still being written. For a repository whose value is its scripts, the absence of a documented script interface means you are reading shell to learn the contract. There is no stated versioning scheme for the scripts themselves; the releases listed are app releases (v7.0, v5.2) plus one rootfs tarball release for Kali arm64, so a script change and an app change are not clearly separable from the outside.

Third, the README's own framing of what you can do is honest but broad: "Pretty much anything you like to do" is immediately qualified by kernel, SELinux, architecture and hardware limits. Treat that as marketing followed by an accurate caveat, and read the caveat.

How it compares with UserLAnd, AnLinux and plain Termux

The alternatives people search for alongside Andronix are Termux, UserLAnd, AnLinux and UserLAnd vs Andronix. The differences are architectural, not cosmetic.

Plain Termux is a terminal emulator and package ecosystem for Android. It gives you a shell and Termux-compiled packages, and Andronix depends on it. What Termux does not do by itself is hand you a Debian or Arch root filesystem with a desktop environment. AndronixOrigin's scripts are the layer that adds that. If you only need a shell, Python and git on your phone, Termux alone is the smaller commitment.

UserLAnd takes a different route to the same goal: it is a full app that manages distributions and sessions for you, rather than a set of scripts you can read and run yourself. The practical difference is transparency and control. AndronixOrigin lets you inspect the install scripts and the rootfs tarballs because they are in the repository. UserLAnd's internals are not laid out this way. The trade-off runs the other way too: UserLAnd is a single installable app, whereas the script route assumes you are comfortable in Termux.

AnLinux follows the Andronix model closely, distributing scripts that set up a distro inside Termux. The meaningful distinction here is the desktop environment and window manager coverage in WM and the Modded OS tier, which is the paid, optimized path the README describes as "a lifetime purchase with unlimited installs on unlimited devices." If you want a maintained, pre-tuned desktop image rather than a script you assemble yourself, that tier is the product, and it is outside this repository.

Maintenance, licence and what an upgrade costs you

The repository is not archived, and the last push to master was on 2026-09-27, so the free script side is being touched. The release history tells a different story: v7.0 (Andronix 7.0.1 Stable) is dated 2023-01-19, the Kali arm64 tarball release 2021-05-28, and v5.2 2020-08-07. Script commits and tagged releases are not moving at the same cadence, so do not read a recent push as a recent stable release.

The repository root contains a LICENSE file and the project metadata lists MIT. The README, however, describes a split: free distro tar files and shell scripts are open, the app and Modded OS files are not. The MIT label on the repository and the licensing of the bundled tarballs are two separate questions, and the README does not resolve the second. If you plan to redistribute a rootfs, read LICENSE and the individual files rather than inferring from the repository-level label. That is a factual gap to close, not legal advice.

Upgrade cost is mostly re-provisioning. Because a distro is a directory tree under PRoot, moving to a new script version generally means reinstalling the rootfs rather than patching in place; the Uninstall directory exists precisely because removal is a supported operation. The repository does not document an in-place upgrade path, and the README does not document rollback. Budget for backing up anything inside the rootfs before you reinstall.

Editorial conclusion

Adopt AndronixOrigin if you want to read or modify the scripts that install Ubuntu, Debian, Arch and the other free distros into Termux, or if you are packaging your own rootfs. Do not adopt it expecting the Android app: the app, the Modded OS images and the desktop environment packages are not in this repository, and the README states they are closed source. Before committing, check the Rootfs, Installer and WM directories to confirm your target distro and desktop are actually scripted here, and read the LICENSE file in the repository root rather than assuming the MIT label covers the tarballs. The last push to master was on 2026-09-27, and the newest tagged release, v7.0, dates from 2023-01-19.

Frequently asked questions

Official sources

1. AndronixApp/AndronixOrigin on GitHub
2. License: MIT
3. Project website
4. README
5. Releases