obi202 stuck in firmware upgrade loop
SteveInWA:
Quote from: ProfTech on January 18, 2018, 12:25:10 pm
To Wayne.obi I have never used the procedure, but the Obi help describes a method to recover a bricked unit. Use the link sent by gpz1100 to get the 5775EX firmware. Then try setting your PC for a static IP and connecting to the Obi using a crossover cable then use the manual update and see if it will "Take". Good luck
The OP reported a flashing red LED. This means the unit is dead. The only state wherein you can update the firmware via the direct connection method is an alternating red/green LED.
grtessman:
See this link: https://www.obitalk.com/forum/index.php?topic=13344.0 maybe make sure Auto-Update is turned off since OBI can't seem to keep their auto update links up to date. It may update but revert back to the old crap with old certs, due to auto update.
SteveInWA:
Quote from: grtessman on April 05, 2018, 06:45:50 pm
See this link: https://www.obitalk.com/forum/index.php?topic=13344.0 maybe make sure Auto-Update is turned off since OBI can't seem to keep their auto update links up to date. It may update but revert back to the old crap with old certs, due to auto update.
No, it's a brick. Bricks can't receive firmware updates. Period. "He's dead, Jim".
roadshow69:
I experienced the same issue. I thought my Obi200 might be bricked. Every time I upgraded the firmware, it would reboot and after a minute would flash red/green. I tried rebooting modem, router and Obi multiple times. It didn't help.
Through the whole process, I was always able to type the Obi IP address in my browser and get to the internal page that allows you to update it's firmware. From past experience, any devices that I have ever owned that became bricked, would not connect to to my network, the fact that the Obi's firmware update page was accessible gave me some hope that it might be fixable.
My netgear router set to reserve a specific IP address for the Obi based on it's MAC address. Thinking my Obi was likely dead, I removed the reservation from my router, and rebooted the router. I plugged the Obi back in to see if it would still show up on my network. It did show up with a different IP address as I expected. I tried one more time to upgrade the firmware, and after it rebooted, the Obi started working again. All lights green, and able to make and receive calls.
I am not sure why it started working after removing it's DHCP reservation. The Obi was obviously communicating with my network with it's DHCP reserved address, or I would never have been able to see the firmware page.
I'm confused, but happy to have my Obi back in action.
SteveInWA:
Quote from: roadshow69 on April 20, 2018, 06:59:54 am
I am not sure why it started working after removing it's DHCP reservation. The Obi was obviously communicating with my network with it's DHCP reserved address, or I would never have been able to see the firmware page.
I'm confused, but happy to have my Obi back in action.
Probably because the router and the OBi were trying to obtain an IP address while the router already had assigned a different IP address due to your settings. Your experience is different than the original poster's.
Navigation
[0] Message Index
[#] Next page
[*] Previous page