The source shows three separate first-boot issues on an older factory image: the new ZimaBoard 2 shipped with ZimaOS 1.4.3, the expected 1.5.3 update prompt was missing, and the App Store showed far fewer applications than expected—including no Immich.
A community workaround enabled Join the Beta experience, after which the user immediately saw the update and a much larger app catalog, and Immich installed successfully. The OTA itself later stalled at 0%, so the user downloaded the 1.5.3 package and completed an offline update. That sequence is historically useful, but current users should not assume enabling Beta is required for every stable release. Current ZimaOS is 1.7.1 and IceWhale maintains a dedicated offline-update workflow for systems whose OTA path does not work.
A New Device Can Ship with an Older Factory Image
A board manufactured, boxed, and stocked before the latest software release may arrive several versions behind. That is not unusual for appliance hardware.
The correct first step is to check the installed ZimaOS version against the current stable release before diagnosing missing apps as hardware incompatibility.
The App Store Expanded After the Old Version Was Addressed
The source initially saw only about 83 apps from a store that listed many more upstream. After the workaround, the App Store showed 369 apps and Immich became available.
The exact app count is not a permanent benchmark—catalog contents, compatibility metadata, third-party stores, architecture, and ZimaOS versions all change.
Immich Was Not Permanently Unsupported
Once the catalog refreshed, the user installed Immich without issue. Current IceWhale documentation still provides a ZimaOS Immich installation/phone-photo workflow.
Use the current ZimaOS Immich workflow.
Treat the Beta Toggle as a Historical Workaround, Not a Current Stable-Update Rule
The claim that a fresh install must enable Beta even for stable updates came from a community reply, not an IceWhale staff statement in this thread. The source user did confirm that it exposed 1.5.3 on their 1.4.3 system.
For a current device, first use the normal Settings update flow and current release documentation. Enable beta releases only if you intentionally want beta software or current IceWhale guidance specifically requires it.
The Source OTA Later Stalled at 0%
After the update appeared, the progress bar stayed at 0%. The user tested DNS, DHCP, router firewall, cable, ports, and ping. The thread never identified the exact online-update root cause.
Do not reduce that failure to “Google DNS fixes it” or “the router firewall caused it.” Neither was source-confirmed.
Offline Update Was the Source-Confirmed Recovery Path
The user downloaded the 1.5.3 update bundle, placed it in the appropriate OTA/offline path, and reported that the offline update worked. The Plus marker also appeared after upgrading.
Current IceWhale documentation explicitly notes that the offline update directory changed starting with v1.4.1, so use the current offline-update instructions instead of copying an old folder from memory.
Current Official Zima Hardware Has Its Own Plus Entitlement Rules
The source was confused because the old image did not show Plus immediately. Current ZimaOS licensing has changed since the 1.5 transition period, and official Zima hardware has device-based Plus entitlement according to the current pricing/activation model.
After Updating, Verify Version, App Catalog, and Critical Apps
Confirm the new version in Settings, reopen the App Store, verify Immich and other required applications appear, and test installed apps before copying large amounts of data to the new system.
New ZimaBoard 2 Update FAQ
Did Immich appear for the source user after the catalog/update workaround?
Yes. The user said the App Store expanded and Immich installed successfully.
Did the normal OTA update complete?
No. It stalled at 0%; the user later completed the upgrade using an offline package.
Should every current user enable Beta to receive stable updates?
The source does not establish that as a current official rule. Use the normal stable update path first.
