TCL 65R625 Reboots each time turning on then requires pulling the plug to fix
Have a TCL 65R625 Roku TV (Roku TV A108X) that has been pretty good up till about 4 days ago. Now each time the TV is turned on, we can use it for about 30 seconds and then it reboots itself with the TCL/Roku logo. Then it returns and tries to connect to the default source but freezes. The TV makes a noise when I press a button on the remote, but nothing happens. Can't turn the TV off/change the source etc. Have to pull the plug on the TV in order to power it down and restart it. It then restarts and 9 times out of 10 we can start using it without an issue (otherwise we have to do it again).
I'm running software version 9.4.0 Build 4187-88 and according to the TV it last updated the firmware on 11/5 at around 1:30 in the afternoon.
So I'd say there's a bug in this version of the software for the TV???
Can you please provide us with the following information: -Roku TV brand and model -serial number -device ID -software OS/version (these can all be found in Settings > System > About) -summary of the issue you are experiencing -when did you start seeing this issue occur
Once we have this information we will be able to pass it along to the appropriate team to investigate further.
Re: TCL 65R625 Reboots each time turning on then requires pulling the plug to fix
Well, we have a new twist - I am now 9.4.0 Build 4190-88 (was 4187-88) and the software was last updated on 13-NOV-2020 at 17:11 (approx). TV has booted fine over the weekend and tonight.. But when we switched from watching the FIOS box on HDMI1 to try to pull up Amazon PrimeVideo or Netflix, the TV reboots. In the case of PrimeVideo, it successfully rebooted as the app was launching and it went back to HDMI1. In the case of Netflix, it rebooted, got the red TCL-Roku splash screen and then it went black.
Didn't respond to the remote. had to pull the physical plug (as there isn't a power button on the TV) and then after that reboot PrimeVideo worked.
So someone updated the OS but moved the issue from power up (or wake from sleep) and moved it into launching apps...