I attempted to upgrade a WAP AC LTE6 to 7.11.2 yesterday, but it never came back.
To recover the device I have attempted netinstall on Linux, and the process proceeds as follows:
$ sudo ./netinstall-cli -a 192.168.88.3 -r routeros-7.11.2-arm.npk
Version: 7.11.2(2023-08-31 14:41:16)
Will reset to default config
Interface Mask: 255.255.255.0
Using Client IP: 192.168.88.3
Using Server IP: 192.168.88.2
Starting PXE server
Waiting for RouterBOARD...
client: 18:FD:74:B3:6C:4A
Sending image: arm
sendFile 3469772
So the device seems to be found, but the process never proceeds from “sendFile”, not even when left overnight.
As a troubleshooting attempt of the process I did the same with a HAP lite, and this runs as expected, so the overall system and process should be correct:
$ sudo ./netinstall-cli -a 192.168.88.3 -r routeros-smips-6.49.8.npk
Version: 7.11.2(2023-08-31 14:41:16)
Will reset to default config
Interface Mask: 255.255.255.0
Using Client IP: 192.168.88.3
Using Server IP: 192.168.88.2
Starting PXE server
Waiting for RouterBOARD...
client: B8:69:F4:A6:4D:8A
Sending image: mips
sendFile 4896892
Discovered RouterBOARD...
Formatting...
Sending package routeros-smips-6.49.8.npk ...
Ready for reboot...
Sent reboot command
As further troubleshooting attempts I have tried to remove the LTE modem and the SIM card, but this made no difference.
Any ideas on further recovery steps, or should I consider the device dead?
Try to netinstall your device to some late ROS v6 … to rule out potential problems with routerboot. I seem to remember debates on this forum saying that v7 requires pretty recent routerboot installed and if one doesn’t keep routerboot in sync with ROS then routerboot version can become too old. AFAIK netinstall doesn’t upgrade routerboot …
So if you manage to successfully netinstall your wAP ac to v6, you’ll know it’s probably not hardware.
@mkx is right. I ran into similar with cAPac, which roughly same as wAPac… Using an V6 netinstall-cli fixed it. You can try it with the V7 package with V6 netinstall … but likely should install V6 with V6 netinstall, then upgrade from there.
Now the original upgrade may have failed since these devices have very little flash… If you were using extra-packages (like lora or iot), that might cause problems. Or other files stored on the wAPac’s flash? Normally the upgrade should just fail, not brick the router.
Curious what version you started with BEFORE upgrading the wAPac? Or was it fresh out of box and/or you never upgraded the RouterBOOT (e.g. /system/routerboard/upgrade)?
Netinstall 6.49.3 did the job. I first tried 6.47.8 but it resulted in “key was rejected”.
I was upgrading from 7.11 to 7.11.2 so it should not have been an issue however, I was also installing the IOT package at the same time, so I might not upgrade and install packages simultaneously another time.
Glad that worked. Annoying you had a double-whammy of problems.
Thanks for the info re versions/packages. I suspected the IOT package was involved. Guessing MT merged IOT and LORA packages to save space on stuff like wAPac with limited flash
*) lora - moved LoRa service to IoT package;
BUT that seem have caused a LOT of upgrade issues. And, those were done in 7.11.0… so why a 7.11.0 to 7.11.2 upgrade had issues is a mystery to me…
NOW upgrading RouterBOOT in /system/routerboard to match the RouterOS version after each upgrade is likely a good idea too.
