[Help] F4-212-2G bootloader crashed [SOLVED]

[SCARABAY]

Hello. A serious problem arose after resetting my TerraMaster F4-212-2G to TOS version 6.0.585. Standard recovery methods do not work, and I need expert help.

The essence of the problem:
After resetting the system to factory settings (via the web interface), the TOS web interface disappeared. Only the background image loads in the browser, without fields for entering a login and password. At the same time, access to the device via SSH (dropbear) has been preserved, which indicates that the system is partially functional.

What has already been done:

The standard procedure for reinstalling TOS with disk removal, described in detail in your knowledge base. The TNAS PC utility did not detect the device after removing the disks, and the message “No hard drive detected” did not appear. The procedure did not lead to the TOS installation window.

A flash drive formatted in fat32 and downloaded file RTK1619b_bootloader_V5.1.53.img to restore boot at startup did not produce results.

Diagnostics via SSH. It was confirmed that web services (nginx, twsd, tnas_web) are not in the list of processes and are not installed in the /etc/init.d/ directory. Commands executed:

find / -type f -name “*nginx*” -o -name “*twsd*” -o -name “*ttnas*” -o -name “*web*” 2>/dev/null | grep -v /proc — no results.

ls -la /etc/init.d/ — no files related to the web interface are present.

The ps output shows that the OpenWrt-based system is running dropbear, avahi-daemon, and udhcpc, but without a web server.

Please help me resolve the bootloader recovery issue.

[CursaYang]

Based on your description, there may be an anomaly with the current guidance system. When you access the initialization page, does it only display a blue background? If that is the case, please go to the official website's live chat to schedule an engineer for remote troubleshooting.

[SCARABAY]

Yes, a blue background and nothing else. I'll try to schedule a session on the website.

[TMnight]

We have completed the processing for you through remote assistance, and the system has now returned to normal. Thank you for your cooperation and patience.
For the 212 model, during the upgrade from TOS 5 to TOS 6, a very small number of devices may encounter unexpected issues halfway through the upgrade process. This issue is not a common occurrence, and we are aware of the situation. We will provide an operation guide on the forum in the future, and following the steps in the guide will restore the system to a normal state.
It should also be noted that TOS 6 for the ARM architecture is no longer considered a long-term maintenance version. After completing system recovery, we recommend waiting for the official release of TOS 7 for ARM before upgrading to ensure a more stable and reliable user experience.
If you encounter any issues during subsequent use, please feel free to contact our technical support team at any time. We will continue to provide you with assistance

[SCARABAY]

Thank you so much! I finally updated to TOS 6. I use NAS as my media source (music, movies), I need NTFS and EXT4, I don't need RAID, and the system is installed on the first HDD. I successfully reinstalled TOS 6 by formatting the system drive, and initialization proceeded normally. However, just before the crash, I went into the system menu and performed a factory reset. TOS 6 6.0.585 is a beta, and this caused a critical error.
Thank you again for your technical support, and I wish you good luck in developing wonderful technical products.