4 weeks ago
Hi Google Community,
We are managing 1,500 units of Chrome cast with Google TV (Gen 4), and we're facing a major issue: several devices are stuck on the Google TV boot logo and do not proceed further.
The only known workaround so far is performing a factory reset, but we are looking for alternative solutions to avoid data/configuration loss across so many devices.
Key Questions:
Is there any way to access the system, logs, or remote ADB while the device is stuck on the GTV logo?
Can the issue be resolved without a factory reset (e.g., firmware recovery, USB update, special key combination, or remote access)?
Has anyone experienced a similar mass deployment issue with boot freeze?
We appreciate any guidance or official escalation path for enterprise-level troubleshooting. Looking for a sustainable solution, not just a reset.
Thanks in advance,
Samcyril S
Answered! Go to the Recommended Answer.
3 weeks ago
Hi @Samcyril,
Thanks for reaching out to the community. I'm sorry to hear your Chromecasts with Google TV 4k are not working as expected and several devices are stuck on the Google TV boot logo, but there's no need to worry; I'm happy to help you right now.
To get a better understanding of the situation, please help me out by answering the following questions:
Any additional details you can provide will be helpful.
Best regards,
Gabriela
3 weeks ago
Hi @Samcyril,
Thanks for reaching out to the community. I'm sorry to hear your Chromecasts with Google TV 4k are not working as expected and several devices are stuck on the Google TV boot logo, but there's no need to worry; I'm happy to help you right now.
To get a better understanding of the situation, please help me out by answering the following questions:
Any additional details you can provide will be helpful.
Best regards,
Gabriela
2 weeks ago
We have a critical issue – 1,000 Chrome cast with Google TV Gen 4 devices are stuck on the Google TV logo screen. This is a major problem for our deployment.
We are looking for any solution other than factory reset due to the number of devices involved.
Please reply urgently if anyone has faced this before or knows a workaround. Any immediate help would be highly appreciated.
Thanks in advance!