My own notes from using Netinstall, from experience forged in the white heat of frustration. I used Netinstall under Linux, which is commend line only, so if you are using a GUI Netinstall under Another Operating System, you will need to interpret, but when it comes to interaction with the target machine, I expect it to be just like this. [ETA this was done on a L009UiGS] Hope this helps
1 Netinstall
A video explaining Netinstall for the use case of upgrading to arm64 packages from arm32 is here https://www.youtube.com/watch?v=pnktg6SD6T8 .
1.1 Preparation
Netinstall formats the device disk and it might be advisable to take a backup.
To run Netinstall, it is necessary to prepare the target device to accept changes. In a terminal
/system/device-mode print # check existing settings
set routerboard=yes
It is also necessary to set the device to boot from the Netinstall utility. [System → Routerboard → Settings]
Boot Device = try-ethernet-once-then-nand
Other preparatory steps may be required, according to the reason for using Netinstall, for example changing from arm32 packages to arm64 requires the following in a terminal:
/system/routerboard/settings # check existing settings
set preferred-architecture=arm64
1.2 Applying Netinstall
The Netinstall utility is only available as a command line utility for Linux and should be run as root. All the previous action has been via a connection to any port on the target device apart from ether1. Once Netinstall is to be run, the connection must be via ether1 on the target device. The invocation [assumed from the directory containing the utility] is
./netinstall-cli
-i # optional eg eth0
-r # reinstall with default configuration
-v # verbose
-mac # mac address of ether1 on target device
Netinstall acts as a server and waits for a target device, which should have the expected mac address. Once Netinstall is invoked, the target device must be rebooted, with the reset button depressed until Netinstall shows that the device has connected.
1.3 Netinstall failure
If Netinstall fails, after identifying the problem, it will be necessary to prepare the target device again to boot from the Netinstall server as given above, changing the connection to the target device to achieve this and back again to ether1 to complete the Netinstall operation.