OC200 Update appears to have bricked the controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.OC200 Update appears to have bricked the controller
This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
I checked my OC200 controller today for an upgrade and saw it was available from the controller gui. I backed up the settings and had it do the upgrade. After the reboot it just seems to have died. Can't reach the IP anymore and it doesn't show up with the TP-Link discovery tool either. I did a factory reset and still same issue. I can't connect to it at all. I had to reinstall the controller software on my PC and factory reset everything to adopt them to into the the software controller. My network is back up but the OC200 has become a paper weight it seems.
Anyone else have this issue with the recent upgrade?
- Copy Link
- Subscribe
- Bookmark
- Report Inappropriate Content
- Copy Link
- Report Inappropriate Content
Dear @Moyshka,
Moyshka wrote
YES indeed I was waiting about an hour before starting the recovery procedure
Thank you for the information.
One more thing to confirm, have you tried uploading the latest firmware v5.0.30 to start the recovery procedure?
If not, could you please give it a try and verify if the upgrade works for your OC200?
- Copy Link
- Report Inappropriate Content
YES I did and got the same results, the OC200 become OFFLINE and I had to use the recovery procedure
- Copy Link
- Report Inappropriate Content
My OC200 Omada Controller upgrade failed twice
The 1st upgrade from 4.4.4 to 4.4.6 and the 2nd upgrade from 4.4.4 to 5.0.30
In both upgrade I got the Downloading window and after that the Rebooting window, when the rebooting finished the Omada Controller was OFFLINE.
I was able to recover the Omada Controller in both cases with the following procedure going back to firmware version 4.4.4
https://www.tp-link.com/us/support/faq/3114/
- Copy Link
- Report Inappropriate Content
Dear @Moyshka,
Moyshka wrote
I was able to recover the Omada Controller in both cases with the following procedure going back to firmware version 4.4.4
https://www.tp-link.com/us/support/faq/3114/
Sorry for the confusion. Could you please follow the FAQ3114 above to recover your Controller again? When you recover your Controller, please upload the latest firmware v5.0.30 instead of your current firmware 4.4.4 to start the recovery procedure. It should work in normal case.
- Copy Link
- Report Inappropriate Content
@Fae Few minutes back I have e-mailed Hugh from TPLINK for the tricks works for my experience of always corrupted or bricked Main (LIVE with adopted EAP's in production) controller OC200 v1. Might this is a good opportunity for community users or members to try the added steps I shared.
- Copy Link
- Report Inappropriate Content
As I reply before I did try the new firmware version 5.0.30 after the recovery and got the same results, the OC200 become OFFLINE. I was waiting for an hour and started the recovery procedure going back to version 4.4.4
NOW I am waiting for an expert from TP-Link to resolve this issue.
- Copy Link
- Report Inappropriate Content
Dear @Moyshka,
Moyshka wrote
As I reply before I did try the new firmware version 5.0.30 after the recovery and got the same results, the OC200 become OFFLINE. I was waiting for an hour and started the recovery procedure going back to version 4.4.4
NOW I am waiting for an expert from TP-Link to resolve this issue.
I've escalated your case to the TP-Link support team for further investigation.
They will reach you via your registered email address shortly, please pay attention to your email box later.
Thank you so much for your cooperation and patience!
- Copy Link
- Report Inappropriate Content
Hello
I am happy to inform you all that the firmware upgrade to version 5.0.30 was successful and here are the steps that I took.
- I have disconnected the OC200 from any Omada device and use a laptop to connect directly via the OC200 IP.
- I downloaded the firmware file and took a backup.
- I choose manually backup and browse to the BIN firmware file and clicked UPGRADE.
- After the OC200 finished downloading it went to rebooting mode, this process took several minutes.
- I connected the OC200 back to the network and several minutes later I was able to connect and see all devices.
I still don’t understand why it failed when the OC200 was connected to the network, I hope this info is helpful.
- Copy Link
- Report Inappropriate Content
Hello all,
I have the same problem with the failed update last year.
My additional problem is that the RESET BUTTON was disabled in the controller software.
Is there any hope for me?
- Copy Link
- Report Inappropriate Content
Information
Helpful: 3
Views: 4435
Replies: 20
Voters 2
