An All-In-One toolchain build environment suite for use with the PAX S920 payment terminals running the ProlinOS Linux-based operating systen. Beware that, by using this toolchain, you are already more than well aware of all required pre-requisites like the root process or other dependencies.
either download the repo from this link and unpack it or just git clone if you already have git installed.
Android (Termux), Debian, Ubuntu, Fedora, Alpine, Nura (postmarketOS), Arch, Sailfish OS, openSUSE, FreeBSD and macOS
our toolchain script includes all necessary checks to make sure you have all things needed, just run
./setup_toolchain.shNixOS wants to be special, so let's let it be so. Just run
nix-shell
./setup_toolchain.shbuild environment on Windows is supported, but highly experimental!
to get working directly on Windows, just open the windows.bat batch script file. The same applies for opening the build environment later on as well.
Beware that you will have to run it multiple times, but it essentially combines everything the other systems need in an all in one solution.
make sure you have gcc, python3, python3-venv, git, swig, openssl + devel, qemu-user-static installed and or their equivalents. Beware, that you are on your own as other platforms do not get any higher level of support.
./setup_toolchain.shcontinue (or start on your next session) with
. ./env.shin case you plugged your terminal over USB or the IP/hostname changed, run this command to change the XCB settings
paxreconfigureyou will be once again asked to either write the whole /dev/ path of the PAX or the IP/hostname with the :5555 port
a handy command to install your public keys from ~/.ssh or from a specified file path
paxdeployssh
# or if you want to specify a file as well
paxdeployssh ~/.ssh/id_ed25519.pubcommand for pushing files or directories from your host computer to the terminal
- supports tab autocompletion where available
paxpush <local source 1> <local source 2> .. <pax destination>
#eg. paxpush osal_test.c /data/app/MAINAPP/libosal.socommmand for pulling files or directories from your terminal to your host computer
- supports tab autocompletion where available
paxpull <pax source> [optional: local destination]
#eg. paxpull /usr/lib/libcbinder.so libcbinder.solists files on your payment terminal
- supports tab autocompletion where available
paxls <pax directory>
#eg. paxls /data/app/MAINAPPcommand for dumping the contents of your terminal
paxdump <dump name> [optional: device path to dump]
#eg. paxdump mydumpThe resulting dump will be stored in dumps/<dump name> inside the working directory.
this is usually the more advanced part for those who really want to build their own software,
for others there's the official way of distributing packages using the handy app package manager download using the homebrew downloader (coming soon until the end of the year 2026)
traverse into the homebrew folder, pick your desired port and run ./build.sh, you should eventually end up with a built out unsigned apk file.
you can either push out these packages to the device and install them with eg. apk add paxDOOM_1.0.0.apk, by making your repo with software
or by upstreaming your homebrew with a pull request to our repo and we will include it in our homebrew repos for you
the recommended way usually is to push the folder with the same name into the apps folder on the desired place (internal storage or SD) of the terminal
eg. paxpush MilkyTrackerPAX /data/app/MAINAPP/apps/
see pax-docs