Start the Server¶
FIRERPA installed via Magisk or through an auto-start app will automatically launch upon device boot. After the initial installation, you only need to restart your device and can skip this section. However, if you performed a manual installation, please continue reading this section to manually start the server.
Hint
On first startup, there is a chance that the remote desktop remains in a loading state. If this occurs, first try restarting your device and then restart the FIRERPA service. If it still does not function properly after waiting for a long time, please report this issue to us.
Execute the Startup Command¶
Now, re-enter the adb shell and switch to the su root user, then execute the following command. Wait quietly for the process to complete. If you see the output llllaamDaa started, the server has successfully started and entered background mode. You may now exit the adb shell normally. Otherwise, refer to the error messages below to troubleshoot the issue.
sh /data/server/bin/launch.sh
Troubleshooting Error Messages¶
During the startup of FIRERPA, you might encounter the following error messages. Use the descriptions below to diagnose and resolve the issues. Under normal circumstances, successful startup will display llllaamDaa started on screen, indicating that the service has properly entered background mode (not exited). You can then close the terminal and proceed with other tasks. If any of the errors listed below appear, the startup has failed—refer to the corresponding solutions.
| Error Output | Description |
|---|---|
| already running | The service is already running |
| invalid TZ area | System timezone is not set or is incorrect |
| not run as root | Please run with root privileges |
| unsupported sdk | This Android version is not supported |
| abi not match | Incorrect architecture tar.gz package used |
| file broken | Files are corrupted; please reinstall |