@Alkolombra 

Exactly the same with my C320WS camera.

I'm requesting the firmware and manual update instructions too.

Thank you.

  @Hilbert-TP 

Thanks for your reply.

I was pointed to that thread by email assistance too.

But I still haven't received an answer to an important question, maybe you know: will the fix work for V2 camera too?

V1 camera only, according to instructions, that's why I'm asking.

My main concern is the firmware available to download, I don't know if it works on V2 camera too, given the instructions and the file name

Tapo_C320WSv1_en_1.3.9_Build_231024_Rel.59054n_up_boot-signed.zip 

Case 3

Applicable Models: 
Tapo C320WS V1

  @Alkolombra 

I tried the suggested LAN recovery procedure (static PC address), but the camera is completely invisible (I tried to find it with a ip scanner too), so I can't upload anything to it.

I tried the SD recovery too (not listed as doable, just as last resort), no luck.

I guess the firmware update bricked the camera for good (or maybe only V1 cameras are recoverable using the LAN procedure).

Please let me know if you find a solution, I'm out of options.

Same issue as this thread — Tapo C320WS V2 (EU, HW 2.0) bricked by a failed OTA firmware update. It was running firmware 1.5.3 Build 260304 Rel.25729n when the update left it in an infinite bootloop (red LED ~3s then resets), no factory reset, and invisible on the network. MAC: 98:BA:5F:7D:F0:30.

I am technical and already tried every documented recovery method, all failed:

• Web/LAN Emergency Mode (PC set to 192.168.0.123, browser to http://192.168.0.10): the camera never brings up the emergency server — no HTTP, no ping, not even an ARP entry (no network stack at all).
• microSD recovery (factory_up_boot.bin on FAT32): the bootloader cannot initialize the SD reader ("MMC interface configure failed").
• UART console (115200): U-Boot loads fine but crashes while loading a corrupt internal image (exactly the stage that would host the recovery), causing the infinite bootloop.

This was caused by TP-Link's own firmware update, not user error, and it affects multiple users in this thread, still unresolved. Could the moderators (@Hilbert-TP) please provide the working C320WS V2 emergency recovery firmware and the "Case 2" instructions, or a warranty replacement? Serial number and proof of purchase available on request. Thank you.

  @Hilbert-TP 

I beg your pardon, but Case 2 ("Wait for around 10 minutes, the camera will automatically connect to the previous Wi-Fi and re-upgrade the firmware.") is not a solution as the camera is not functional.

The device is bricked and it's 100% TP-Link responsibility, what should we do now?

Throw the camera in the trash because of a faulty firmware we are not responsible of?

Thanks @Hilbert-TP. I have to be clear: Case 2 cannot work for this failure. It relies on the camera powering on, reconnecting to Wi-Fi and auto-re-downloading the firmware — but mine never boots that far. I confirmed via UART serial console that it is stuck in a U-Boot bootloop (it crashes while loading a corrupt internal image and resets every ~3 seconds) and never starts the OS or Wi-Fi, so it cannot auto-reconnect or re-upgrade. Moving it closer to the router changes nothing — there is no Wi-Fi stage at all. There is also no working SD-card or web-emergency recovery for the V2 (I tried all of them).

So, as you indicated, the only path left is a warranty replacement, which I would like to proceed with — this was caused entirely by your own OTA firmware update (the camera was on 1.5.3 Build 260304 Rel.25729n), not by user error. What are the exact steps to start the RMA?

Device details — Model: Tapo C320WS V2 (EU, HW 2.0) · MAC: 98:BA:5F:7D:F0:30 · Serial number and proof of purchase: available on request. Thank you.