OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53 Fails to Load

OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53 Fails to Load

OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53 Fails to Load
OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53 Fails to Load
22 hours ago - last edited 22 hours ago
Model: OC200  
Hardware Version: V1
Firmware Version: OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53

I have been running "OC200v1_OC200v1_2_un_1.37.11_20251201_rel43290_common_up_2025-12-01_12.02.18"  successfully for a few weeks.  Yesterday, my OC200 notified me of a new firmware version available, "OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53". I selected the upgrade from the pop-up and let it install the new version.  When it was completed, the OC200 rebooted but only got to 65% before rebooting itself.  I allowed the OC200 to try several more reboots with the same result.  I then used Recovery Mode and installed a downloaded copy of the same new firmware version (from https://support.omadanetworks.com/us/product/oc200/v1/?resourceType=download).  This resulted in the same results with this downloaded file - except that the reboot progress only got to 56% each time. I ran Recovery Mode again, but this time, I installed the earlier 1.37.11 firmware that I was running previously. The OC200 then rebooted successfully, and I am now back up and running as before on 1.37.11.

Any ideas regarding what the issue is?  Has anyone else had similar results?

(1) TL-R605 v2.20 Router/Gateway (1) OC200 v1.0 Controller (1) TL-SG2210P v3.20 POE Switch (2) TL-SG2218 v1.2 POE Switch (3) EAP650 v1.0 Access Point (2) EAP225-Outdoor v1.0 / V3 Access Point
  0      
  0      
#1
Options
1 Reply
Re:OC200v1_OC200v1_2_un_1.38.10_20260117_rel60495_common_up_2026-01-17_16.48.53 Fails to Load
7 hours ago

Hi  @lflorack 

 

Thanks for posting here.

 

How do you access the OC200 when updating the firmware, locally or via cloud access?

 

Will the reboot get stuck at 65% or 56% every time?

 

To rule out browser reasons, please try the following:


Troubleshooting Guide for Web-Based Management Interface Anomalies

 

For your case, please proceed with steps 3, 4, 5, and 6.

 

 

  0  
  0  
#2
Options