I’m stuck when trying to upgrade my RUTx50 above RUTX_R_00.07.04.5. I have seen many posts and solutions regarding this, but I’m stuck. Any ideas?
I have tried:
Webgui
Different firmware version (both a small step to RUTX_R_00.07.06.10 and directly to the latest
With or without Keep settings
Bootloader-way
Tested RUTX_R_00.07.06.10_WEBUI.bin and RUTX_R_00.07.16.6_WEBUI.bin. The whole process look ok with upload and reboot, but I end up with the old version
SSH
Tried RUTX_R_00.07.05 and the latest on.
Looks ok during process but the old RUTX_R_00.07.04.5 with all settings are there after reboot.
Additional information after further investigation:
I have investigated the filesystem and logs on the router, using support from ChatGPT, and found some potential issues:
The df -h output shows partitions are not full and mounted read-write as expected, so lack of space should not be the problem.
However, logread and dmesg show UBI errors like block: can't add 'rootfs' volume, err=-17 indicating problems with the NAND flash or root filesystem volumes.
There are repeated errors in system logs saying “failed to step through query” and “unable to open database file”, which strongly suggests filesystem corruption or flash wear issues.
These errors could according to ChatGPT explain why the firmware upgrade process completes without error but does not actually flash the new version. The internal flash or rootfs volume might be damaged or locked in a way that prevents modification.
At this stage, ChatGPT suspects that the problem is not with the upgrade method itself or firmware files, but a lower-level flash memory or filesystem issue.
Has anyone else experienced this UBI rootfs volume error on a RUTX50 and managed to resolve it? Could this be fixed by a deep factory reset, a special repair tool, or is this a hardware failure requiring RMA?
Since you managed to update the firmware to 07.05, that should rule out any hardware issue with the device’s Flash memory.
I would suggest trying to perform an update using Bootloader again, but this time making sure that you are using a private/incognito web browser window. The most common reason why the Bootloader update might fail is if a standard web browser window is used.
I think you meant ‘firstboot’ ; y to accept erase; then ‘reboot’ – right?
root@Teltonika-RUTX50:~# firstboot
This will erase all settings and remove any installed packages. Are you sure? [N/y]
y
/dev/mtdblock5 is mounted as /overlay, only erasing files
root@Teltonika-RUTX50:~# reboot
Could you please confirm whether performing a firstboot (as suggested by randyrick) and then attempting to upload or install a higher firmware via WebUI, SSH, or bootloader provides any positive result?
Additionally, another approach you could try is mounting an external USB flash drive with the firmware image and attempting to update the device via SSH.
Lastly, just to confirm, is the device being powered with the proper 18 W PSU?
Thank you for the details. I’ve noted that it somehow allowed the installation of 7.05, which is indeed unusual. Could you please confirm whether the device’s system and memory information is displayed correctly when logged into the WebUI and navigating to Status → System? Please ensure not to share SN or MAC addresses.
Based on your previously provided logs, this might suggest an issue with the rootfs partitions. Were there any interruptions during firmware upgrades previously? Does the device allow downgrading the firmware via bootloader?
Additionally, could you run the hexdump -C /dev/mtd1 command via CLI and provide its output here. Thank you.
Thank you for your update and positive experience throughout the remote session.
As I understand, the device will be sent for RMA inspection and further analysis. For any further details after the device has been inspected, please kindly refer to your HelpDesk ticket.
