Installing the Server

This chapter explains how to install the FIRERPA server, which is the most crucial component and the fundamental underlying service. You can choose to install it via the AUTORUN APP (supports auto-start on boot), as a Magisk module (supports auto-start on boot), or manually. The installation difficulty corresponds to the order in which they are listed.

Important

By default, FIRERPA is installed without any authentication enabled, allowing anyone to access any content on the device. Please refer to the section on enabling service certificates to selectively enable them. If you do not enable them, be sure to use FIRERPA only on a trusted network.

Attention

For security reasons, we do not recommend placing any related files, such as the server or configuration files, in the `/data/local` directory.

Installation via APP

We will introduce the simplest method first. This installation method is the easiest and doesn't require any extra steps. You just need to install our automatic installation and auto-start APK. However, you still need to ensure that your phone has root permissions (su). On some phone models, the default auto-start behavior for APKs may be disabled. In this case, you may need to find the relevant settings and allow our APK to auto-start.

Click to download our FIRERPA auto-start application lamda-autorun.apk. After installation, open the app, grant root permissions, enable the auto-start switch, wait for the installation to complete, and then restart your device. If you have completed this successfully, you do not need to continue with the rest of this chapter.

Get Device Architecture

Because FIRERPA supports multiple CPU architectures, downloading the wrong server version will prevent it from running correctly. Therefore, before installation, you need to get your device's architecture. You can execute the following command to get it.

getprop ro.product.cpu.abi

Typically, for modern physical phones, this command outputs arm64-v8a. For emulators like LDPlayer, you choose a 32-bit or 64-bit version of Android when creating a new instance. A 32-bit emulator system corresponds to x86, and a 64-bit one corresponds to x86_64. Some older Xiaomi models are armeabi-v7a. Please remember this output value for now.

Startup Configuration File

Please refer to the properties.local Configuration chapter for information on how to write the startup configuration. This will also be covered in the sections for various features.

Installation via Magisk

If your device uses Magisk, you can complete the installation using the simplest method, and FIRERPA can auto-start on boot. Ensure your Magisk version is >= 20.4 and that you install it only through the Magisk App.

Now, download lamda-magisk-module.zip from the lamda/releases page, push it to /sdcard, open the Magisk App, tap Modules -> Install from storage, select lamda-magisk-module.zip, and wait for a moment.

Tip

If you encounter any ERROR during the process and the installation fails, it might be because our module zip file is too large. Use an archive manager to open the zip file and delete the server files for the architectures you don't need from the `server` directory, then try installing again. Do not extract and re-compress; perform the operation directly within the archive manager.

After flashing successfully, please restart your device. After rebooting, FIRERPA should start automatically on boot. However, to avoid potential crashes, lamda will start after a 30-second delay instead of immediately, giving you enough time to disable the FIRERPA module if needed (please wait 2 minutes after booting before connecting to FIRERPA).

You can also use a custom configuration. For example, if you want all FIRERPA instances installed with this Magisk module to have API service certificates enabled, or if you want these devices to automatically connect to a proxy on startup, you just need to write a properties.local file or generate a PEM certificate and rename it to lamda.pem (please see the usage instructions for the tools in tools/). Then, use an archive manager to open lamda-magisk-module.zip and drag your configuration files (lamda.pem or properties.local) into the common folder. This will apply the configuration automatically on startup.

Attention

Do not extract and re-compress. Perform the drag-and-drop operation directly in the archive manager, otherwise the module will not function correctly.

After the installation is complete, you can skip the following section on manual installation.

Manual Installation

Since some older devices may not be able to extract .tar.gz files using the system's tar command, we provide busybox as a supplement. You may need to download the provided busybox as well. Assuming the device architecture is known to be arm64-v8a, connect the device to your computer and ensure that ADB is authorized and you can switch to root.

From the lamda/releases page, download lamda-server-arm64-v8a.tar.gz and busybox-arm64-v8a, and push the files to the temporary directory /data/local/tmp.

Tip

This section only covers how to manually unpack and install the server. The startup process is described in another chapter.
adb push lamda-server-arm64-v8a.tar.gz /data/local/tmp
adb push busybox-arm64-v8a /data/local/tmp

Once done, enter adb shell, run su to switch to the root user, and then 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 have been executed correctly, the installation is complete. Please proceed to the Starting the Server chapter to learn how to start the service.