Installing the Server¶

This chapter describes how to install the FIRERPA server. The FIRERPA server is the most critical component and the most fundamental underlying service. You can choose to install it via the provided APP (which supports auto‑start on boot), a Magisk module (also supports auto‑start on boot), or manually. The installation complexity increases in that order.

Installing via the App¶

First, let's introduce the simplest installation method. This method requires no extra steps – you just need to install our auto‑install and auto‑start APK. For detailed installation steps, please refer to the Quick Start chapter.

Getting the Device Architecture¶

Because FIRERPA supports multiple CPU architectures, downloading the wrong version of the server will prevent it from running. Therefore, you need to determine the device architecture before installation. Run the following command:

getprop ro.product.cpu.abi

For modern physical phones, the output is usually arm64-v8a; for emulators (such as LDPlayer), you can choose a 32‑bit or 64‑bit Android system when creating the emulator – 32‑bit corresponds to x86, 64‑bit to x86_64; some older Xiaomi models may output armeabi-v7a. Please remember this output value.

Service Configuration¶

Refer to the Service Configuration chapter to learn how to configure service startup options; each feature introduction may also contain relevant information.

Installing via Magisk¶

If your device uses Magisk, you can complete the installation in the simplest way, and FIRERPA can auto‑start on boot. Magisk version must be ≥ 20.4, and installation is only supported within the Magisk App.

Download lamda-magisk-module.zip from the lamda/releases page and push it to /sdcard. Open the Magisk App, tap "Modules" → "Install from storage", select lamda-magisk-module.zip, and wait a moment.

If you want the service to automatically set a proxy or connect to FRP forwarding at startup, please write the corresponding configuration in standard ini format, rename it to properties, and place it inside the common folder within the lamda-magisk-module.zip module ZIP. If you need to pre‑install a server certificate together with the Magisk module, generate a PEM certificate as described in the Server Certificate chapter, rename it to lamda.pem, and also drag it into the common folder of the module. If you want to authorize the built‑in ADB by default, write the content of your local adbkey.pub file into a file named adb_keys and drag it into the common folder.

Manual Installation¶

Some older devices may not be able to use the system’s built‑in tar command to decompress .tar.gz files, so a busybox is provided as a supplement; you may need to download it as well. Assuming the device architecture is arm64-v8a, connect the device to your computer and make sure ADB is authorized.

Download lamda-server-arm64-v8a.tar.gz and busybox-arm64-v8a from the lamda/releases page, and push both files to /data/local/tmp.

adb push lamda-server-arm64-v8a.tar.gz /data/local/tmp
adb push busybox-arm64-v8a /data/local/tmp

Once done, enter adb shell. If the device has root privileges, first run su to switch to the root identity; otherwise, use the current shell identity to execute the following commands:

chmod 755 /data/local/tmp/busybox-arm64-v8a

/data/local/tmp/busybox-arm64-v8a tar -C /data -xzf /data/local/tmp/lamda-server-arm64-v8a.tar.gz

rm /data/local/tmp/lamda-server-arm64-v8a.tar.gz
rm /data/local/tmp/busybox-arm64-v8a

After all commands execute successfully, the installation is complete.

Manual Start¶

Enter adb shell, and choose to run the following command as shell or root depending on the device’s actual situation. After running the command, wait for it to return. If the output shows llllaamDaa started, the service has started successfully and entered background mode; you can safely exit adb shell and access the FIRERPA service. Otherwise, refer to the error messages below for troubleshooting.

sh /data/server/bin/launch.sh

Uninstalling the Service¶

FIRERPA manages its own data in a very orderly manner and will never scatter files randomly on your system. Magisk installation users can simply remove the module, and APP installation users can use the uninstall function inside the APP.

Before uninstalling, first exit the service and wait at least 30 seconds to ensure the service exits normally.

rm -rf /data/server /data/usr # /data/local/tmp/usr

This will completely remove FIRERPA from your device. It is recommended to reboot the device afterwards.