OC200 V1 bricked after failed firmware update and RMA path is unclear

OC200 V1 bricked after failed firmware update and RMA path is unclear

OC200 V1 bricked after failed firmware update and RMA path is unclear
OC200 V1 bricked after failed firmware update and RMA path is unclear
Thursday - last edited Thursday
Model: OC200  
Hardware Version: V1
Firmware Version: 1.35.7 Build 20250514 Rel.51837

Hello,

 

TL;DR:

My OC200 V1 appears to be bricked after a failed firmware update. It no longer connects to Omada Cloud, is not reachable from the LAN, and the official reset/recovery procedure does not trigger the expected LED behavior.

At the same time, the RMA process in Italy is not providing a workable path for an end customer. The official TP-Link Italy warranty/replacement page points to a support/RMA process based on proof of purchase, but by email I was asked for internal distributor-to-reseller documents that a final customer cannot realistically provide. The reseller has been helpful and has tried to assist, but the case remains blocked despite multiple follow-ups.

 

Long version:

 

I am writing here because I am currently stuck with both a technical issue and the related support/RMA process in Italy.

I own a TP-Link Omada OC200 V1 purchased in Italy from an Italian reseller on 08/11/2022.

 

Technical issue

On 14/04/2026, the OC200 stopped working after a failed firmware update process.

The firmware version involved was: 1.35.7 Build 20250514 Rel.51837

Since the failed update, the controller is no longer usable.

 

Current behavior:

  • the OC200 no longer connects to Omada Cloud;
  • it is not reachable from my LAN;
  • I cannot access the local controller interface;
  • the device does not seem to complete any normal boot or recovery process;
  • only the Ethernet port LED remains on;
  • the Cloud LED and the Ethernet/port LED never start blinking as expected during the recovery/reset procedure.

 

Troubleshooting already performed

I tried to follow the official Omada reset/recovery procedure described here: https://support.omadanetworks.com/it/document/13063/

 

In particular, I tried the procedure involving:

  1. disconnecting power from the OC200;
  2. pressing and holding the reset button;
  3. powering the device back on while keeping the reset button pressed;
  4. waiting for the expected LED behavior.

 

The Cloud LED and the Ethernet/port LED never blink as described in the procedure. The only visible behavior is that the Ethernet port LED remains on.

As a result, I cannot restore the device, I cannot reach it from the network, and I cannot re-adopt or recover it in any practical way.

From a technical point of view, the unit appears to be bricked after the failed firmware update.

 

Support and RMA timeline

I first contacted TP-Link Italy support on 15/04/2026, asking whether an RMA/replacement could be arranged.

The request was sent using the support contact information published on the official TP-Link Italy warranty/replacement page https://www.tp-link.com/it/support/replacement-warranty/

That page appears to describe the replacement/warranty process for TP-Link products in Italy and refers to proof of purchase documentation such as invoice, receipt or fiscal document as the basis for checking warranty eligibility.

However, the instructions I later received by email do not seem fully consistent with the public information on that page.

Timeline so far:

  • 15/04/2026: first support/RMA request sent to smb.support.it@tp-link.com, including proof of purchase;
  • 16/04/2026: I called first-level support and was told that the case had been escalated;
  • 20/04/2026: I called again and was told that another reminder/escalation had been made;
  • 28/04/2026: I called again and was told that first-level support had sent another reminder;
    • on the same date, TP-Link support internally acknowledged that I had already been waiting for more than 15 days and had already called several times;
    • later, I was told that the SMB support channel is reserved for resellers, distributors, installers and TP-Link Omada partners, and that I should contact rma.it@tp-link.com instead;
    • after that, I was told that the RMA request should normally come from the reseller;
    • alternatively, I was told that, if I wanted to bypass the reseller, I would need to provide not only my purchase invoice from the reseller, but also the delivery note from the distributor to the reseller.

 

This is the part I am trying to understand.

I am the final customer. I can provide my purchase invoice/receipt from the seller, but I obviously cannot provide internal supply-chain documents such as a delivery note from the distributor to the reseller.

Those documents can only be provided by the reseller or distributor.

I contacted the reseller, and I would like to thank them for their availability and cooperation. They contacted both the distributor and TP-Link Italy, sent multiple reminders, and also sent a formal and legal communication. However, according to what I have been told, they also have not received any effective operational response so far.

 

So at this stage:

  • I, as the final customer, cannot provide the distributor-to-reseller delivery note;
  • the reseller has been cooperative and has tried to help;
  • the reseller has contacted the distributor and TP-Link Italy;
  • TP-Link Italy has not provided a clear operational solution;
  • the public warranty/RMA information on TP-Link Italy’s website appears to describe one process, while the email instructions seem to require a different process;
  • the case keeps being redirected between support channels instead of being clearly handled.

 

In practice, this leaves the final customer with no clear and practical way to complete the RMA process.

 

What I am asking for

I would appreciate help with both the technical and support/RMA side.

 

Technically

  1. Is there any additional recovery method for an OC200 V1 that appears bricked after a failed firmware update?
  2. Is there a documented low-level recovery procedure other than the reset procedure already tried?
  3. Is there any way to force recovery if the expected LED blinking sequence never starts?
  4. Is this a known failure mode after a firmware update failure on OC200 V1?

 

Commercially / support-wise

  1. What is the correct RMA path in Italy for an end customer with an Omada OC200 purchased from an Italian reseller?
  2. If TP-Link requires distributor-to-reseller documentation, should TP-Link Italy request it directly from the reseller/distributor instead of asking the final customer?
  3. How can this case be escalated properly, considering that both the final customer and the reseller have already tried to get the case handled?
  4. Can someone from TP-Link clarify which procedure actually applies in this case?
  5. Can TP-Link clarify why the public warranty/replacement page seems to indicate one process, while the email instructions require documents that a final customer cannot realistically provide?

 

Any help from TP-Link staff or the Omada community would be greatly appreciated.

Thank you.

 

  0      
0
#1
Options
4 Reply
Re:OC200 V1 bricked after failed firmware update and RMA path is unclear
Friday

Hi  @usefulnoise 

 

Sorry to hear about the poor experience with RMA.

Based on your description, this OC200 appears to be faulty and needs to be replaced.

Could you please provide me with the case ID from your contact with our support team? I will forward your request to the responsible team with high priority. Thanks.

  0  
0
#2
Options
Re:OC200 V1 bricked after failed firmware update and RMA path is unclear
Friday

 

Vincent-TP wrote

Hi  @usefulnoise 

 

Sorry to hear about the poor experience with RMA.

Based on your description, this OC200 appears to be faulty and needs to be replaced.

Could you please provide me with the case ID from your contact with our support team? I will forward your request to the responsible team with high priority. Thanks.

Hi @Vincent-TP,

thanks for getting back to me!

 

I believe the case ID is TKID260506495

 

Appreciate your help on this!

Have a nice day :)

 

  0  
0
#3
Options
Re:OC200 V1 bricked after failed firmware update and RMA path is unclear
Friday

Hi  @usefulnoise 

 

Thanks for the info. It's forwarded. Someone will contact you. 

  0  
0
#4
Options
Re:OC200 V1 bricked after failed firmware update and RMA path is unclear
15 hours ago

Hi @Vincent-TP, so far no one has got back to me.

To be honest, one of the reasons I chose Omada was the promise of reliable business-grade support and warranty coverage. However, this experience is making me seriously reconsider that choice.

Since mid-April, I have been unable to properly manage or modify the networks I am responsible for because the OC200 is no longer working.

Is opening an RMA case usually this difficult with Omada, or is this a specific issue with the TP-Link Italy support/RMA process?

Thanks

 

  0  
0
#5
Options