The Roku Community thread, posted in June 2023, documents a new TCL 65R655 (model J102X) going through first-time setup. The TV automatically checked for updates, downloaded one, and displayed a message confirming it would restart to finish installation. It restarted. It never came back on.

The owner disconnected power, waited 15 minutes, and tried again, per the thread. The TV returned to the initial setup screen, connected to the internet, fetched the same update, attempted the same restart, and went dark again. That sequence repeated six times without variation. The device shipped running firmware version 10.5.0 build 3168-DK, according to the thread.

The key fact: manual restarts worked normally. Both the physical reset button on the back of the TV and a restart initiated through the settings menu completed without issue. The TV couldn't execute the post-update automatic restart that Roku's installation process required that specific path failed, not the hardware as a whole. That's the thread author's observation, not a hardware diagnostic, but it's a meaningful distinction.

"Bricked" gets used loosely in consumer electronics. It covers everything from an unresponsive remote to circuit-level destruction. This case sits between those extremes: completely unusable by any consumer standard, impervious to every standard fix, but with manual restarts still functioning. The practical outcome was the same as total failure. The TV didn't work and couldn't be made to work.

The thread lists every recovery method attempted: leaving the TV unplugged for 24 hours before retrying; skipping internet setup and running a factory reset first; pressing the physical reset button; working through Roku's USB firmware recovery process at tvupdate.roku.com. None of it worked. TCL's support team advised enabling Fast TV Start, draining residual power, and running setup again. That didn't work either.

The thread doesn't document what came after: whether TCL acknowledged a defect, whether a replacement unit behaved the same way, or whether the failure appeared in other units from the same production run.

Accounts circulating online describe a legal action naming both TCL and Roku as defendants. The core allegation, as those accounts frame it: mandatory software updates caused failures that consumers couldn't fix, and both companies failed to prevent or remedy the problem. Rather than treating affected units as isolated defects, the framing assigns product-level responsibility to both parties.

None of that could be verified. Which models are named, which court received a filing, what legal theories are alleged, what damages are sought all unconfirmed. No primary document is available.

That absence doesn't prove a lawsuit doesn't exist. It means the specific claims can't be confirmed from any source available at publication, and reporting them as established fact would not be accurate. Headlines about TCL and Roku being sued over bricked TVs are circulating. The publicly documented evidence behind those headlines is, right now, a single forum post about one unit from nearly three years ago.

The Roku Community thread establishes something concrete: this failure mode can occur. The combination of a mandatory first-setup update, an automatic restart, and this specific hardware produced a loop that no consumer-level fix resolved, on one model (the 65R655), one firmware build (10.5.0 / 3168-DK), documented in June 2023.

What it can't establish is that more than one unit was affected, that the failure extended to other TCL models or firmware versions, or that either company had any reason to anticipate the failure before the update deployed. One precisely described, repeatable case is not a pattern. A pattern is what a class action typically requires to move forward.

The sharpest legal question in any potential litigation would likely be causal: did the firmware update cause the failure, or did it expose a hardware defect already present in specific units? Those are different arguments with different burdens of proof. The thread doesn't answer that. Establishing that either company knew about the failure before deploying the update would require evidence that isn't in the public record.

If a TCL Roku TV fails to power on after an automatic software update during first-time setup, the failure pattern in the thread is a useful reference: the TV returns to the setup screen on power cycle, connects to the internet, pulls the same update, attempts the same restart, and fails again. Factory reset, USB recovery via tvupdate.roku.com, and direct TCL support guidance all failed to resolve it in the documented case.

Anyone dealing with this should note the firmware version displayed before connecting to the internet that build number may matter if the issue needs escalating. Keep written records of every support interaction, including the specific steps recommended. Hold onto proof of purchase. If the device is still within the retailer's return window, that's the most direct path to resolution.

For prospective buyers: the available evidence describes a failure tied to one specific model and one firmware transition from nearly three years ago. No public record connects it to other models or to units sold since. The documented case doesn't support a broad indictment of TCL Roku TVs.

What the case does illustrate is a structural exposure that applies to any smart TV requiring a software update to complete initial setup. One failed first-boot update, triggered automatically with no consumer override, can leave a new device unusable before it displays a single frame. How courts might weigh that as a product liability matter depends on documents that aren't yet public.