[1.7.0] Official ZimaCube (F8NAB / N5 PRO) stuck on "Searching for network address..." after OTA from 1.6.1; recovered on 1.6.1

[hussainexpocci]

Summary

After upgrading from ZimaOS 1.6.1 to ZimaOS 1.7.0, my official ZimaCube no longer obtains/displays a network address and remains stuck on the local splash:

Searching for network address...
If this persists, please check your network connection.

This is the same failure mode I previously reported on 1.6.2 in #538. Rolling back / returning to 1.6.1 restored networking and access again.

Environment

• Hardware: Official ZimaCube (MODEL=ZimaCube, DMI N5 PRO, product SKU F8NAB / MGF8NAB)
• Broken version: ZimaOS 1.7.0 (release)
• Working version: ZimaOS 1.6.1 (Build: 2026/04/21, kernel 6.12.25)
• Connection: Ethernet on LAN 1 (eth0)
• Physical link: Link appears up during the failure (same pattern as [1.6.2] Official Zima hardware stuck on "Searching for network address..." after OTA; recovered by rolling back to 1.6.1 #538)
• Related issue: [1.6.2] Official Zima hardware stuck on "Searching for network address..." after OTA; recovered by rolling back to 1.6.1 #538 (identical symptom on 1.6.2)

Steps to reproduce

1. Device running ZimaOS 1.6.1 with working Ethernet/DHCP and normal Web UI / SSH access.
2. Apply OTA update to ZimaOS 1.7.0.
3. Reboot into the updated slot.
4. Observe local display stuck on “Searching for network address...”.

Expected behavior

Device acquires (or continues to use) a network address, shows it on the local display, and remains reachable on the LAN / Web UI, as it does on 1.6.1.

Actual behavior

• Boot reaches the network-search splash and does not progress.
• Device is effectively unreachable on the LAN until the previous working slot / 1.6.1 is used again.
• Returning to 1.6.1 restores normal networking and access.
• User data on storage appears unaffected after recovery.

Recovery used

1. Connected keyboard + monitor (or used GRUB / previous RAUC slot selection).
2. Booted the previous working slot (1.6.1).
3. Network and Web UI / SSH access returned.

Current confirmed working state after recovery:

• VERSION=v1.6.1
• kernel 6.12.25
• eth0 UP with LAN address again

Notes / possible relevance

• This now happened on two consecutive OTA targets after 1.6.1: 1.6.2 ([1.6.2] Official Zima hardware stuck on "Searching for network address..." after OTA; recovered by rolling back to 1.6.1 #538) and 1.7.0 (this report).
• Failure begins immediately after the OTA reboot (not a gradual cabling/router issue). Cabling and router port were verified previously for [1.6.2] Official Zima hardware stuck on "Searching for network address..." after OTA; recovered by rolling back to 1.6.1 #538 and remain unchanged.
• This is official Zima hardware, not a DIY/unsupported-NIC install.
• Secondary observation: the failed/interrupted OTA path also reset /mnt/boot/cmdline.txt, wiping custom boot parameters that were present on 1.6.1. Even if unrelated to the splash screen, it suggests boot/OTA handling may be rewriting boot config during these failed upgrades.

Request

Please confirm whether this is a known regression spanning 1.6.2 / 1.7.0 on official ZimaCube hardware, and advise:

1. Whether users should remain on 1.6.1 until a fixed build is released.
2. Whether a hotfix is planned for the “Searching for network address...” hang after OTA.
3. Any recommended diagnostic logs to collect if we temporarily boot 1.7.0 again (e.g. ip a, nmcli, journalctl -u NetworkManager, rauc status, uname -r).

Thank you.