Start from what the TV is doing
| What you see | Most likely cause | Go to |
|---|---|---|
| Everything works but you want the stock TV back | Most likely causeNothing broken | Go toRestore the whole list |
| A feature broke: casting, an input, the mic or the phone remote | Most likely causeOne package the feature needed | Go toRe-enable one package |
| Black screen, a setup or “Recovery” screen, or the launcher chooser at Home | Most likely causeThe stock launcher is off, or the setup package took Home | Go toGet Home back first |
| The TV forgot its Wi-Fi | Most likely causeThe network belonged to the Google TV setup package | Go toGet back on the network |
| Restarts in a loop, or stuck on the logo, and ADB never connects | Most likely causeA system or TV middleware package is off | Go toFactory reset from recovery |
Restore the whole list
If you used CleanYourTV’s scripts, they saved a recovery record in ~/.cleanyourtv/ before disabling anything: each package’s previous state and which app owned Home. The restore script replays it, so packages that were already off from the factory stay off.
# Google TV (stock launcher as the fallback)
TV_HOST=<tv-ip> tools/restore.sh examples/<your-tv>/debloat.txt com.google.android.apps.tv.launcherx
# Android TV
TV_HOST=<tv-ip> tools/restore.sh examples/<your-tv>/debloat.txt
# Fire TV
TV_HOST=<tv-ip> tools/restore.sh examples/<your-tv>/debloat.txt com.amazon.tv.launcher
# Windows
powershell -ExecutionPolicy Bypass -File tools\restore.ps1 -TvHost <tv-ip> examples\<your-tv>\debloat.txtUse the same TV address as the clean-up: the record is filed under it. Without a record, the script falls back to enabling every package in the list, which can also switch on apps the factory left off. The new launcher stays installed; remove it in Settings > Apps if you want it gone. On Fire TV the restore prints one harmless “Cannot disable a protected package” error for Amazon’s launcher.
If Claude Code worked without those scripts, ask it for the file it saved before the first change, or list what is disabled now and compare it with what you remember changing:
adb connect <tv-ip>:5555
adb shell pm list packages -d # everything currently disabled
adb shell pm enable <package.name> # one at a timeRe-enable one package for one broken feature
| Broken feature | Package to check first |
|---|---|
| Phone remote connects but nothing happens, or the remote’s mic is dead (Google TV) | Package to check firstcom.google.android.tv.remote.service |
| Phone remote stops responding on NVIDIA SHIELD | Package to check firstcom.google.android.tvrecommendations |
| Casting fails with Untrusted device (Chromecast, Google TV Streamer) | Package to check firstcom.google.android.tungsten.setupwraith |
| Xiaomi Settings freezes or crashes | Package to check firstmitv.service |
| Inputs, Live TV or the Sources key stopped working | Package to check firstThe TV maker’s input or Live TV app, such as com.tcl.tv on TCL |
No computer? On the TV, open Settings > Apps > See all apps > Show system apps, choose the disabled app and select Enable. On Fire TV the path is Settings > Applications > Manage Installed Applications.
Get Home back first
Connect over ADB and turn the stock launcher back on: `adb shell pm enable com.google.android.apps.tv.launcherx` on Google TV, or `com.google.android.tvlauncher` on Android TV.
Pressing Home shows the stock home screen, or a chooser that lists it.
If `adb` cannot connect, debugging may have been switched off by the restart; see the boot-loop section.
If Home lands on a screen from the setup wizard, check which app holds focus with `adb shell dumpsys window | grep mFocusedApp`.
If it names `setupwraith/.RecoveryActivity`, the Google TV setup package has taken Home; the stock launcher you just enabled should take it back.
Do not reboot while that screen is showing. One Xiaomi owner reported that a reboot on it factory-reset the TV.
Restart only once Home works, then run the full restore if you want everything back.
The TV boots to the stock home screen.
If Home goes black again after a power cut, some firmware re-enables the setup package at every cold boot. Keep the stock launcher enabled.
Get back on the network
On Google TV, a Wi-Fi network saved during first-time setup can belong to the setup package. Disable that package and the network disappears with it, taking network ADB along. Re-join from the TV with the physical remote or a USB keyboard: forget the network first, then connect again, which makes the system own it. A wired Ethernet connection also works. Then switch network or Wireless debugging back on and continue the restore.
When a factory reset is the only way back
If the TV restarts in a loop or stays on the logo and never stays up long enough for ADB, start it into its recovery menu and choose a factory reset. The way in varies by model, often holding a button on the TV itself while plugging it in, so check the manufacturer’s instructions for yours. Everything the clean-up changed lives in the user data the reset wipes, so every disabled app returns and the new launcher is gone, along with your own apps, accounts and settings.
Owner reports trace boot loops to core Android or TV middleware packages, such as MediaTek’s TV service packages. Current CleanYourTV scripts refuse to disable those, but a free-form Claude Code session has no such guard, so tell it never to touch packages named android, com.android.systemui, com.android.tv.settings or the TV’s middleware.
Keep a second way to control the TV
A recovery is easier when you can still move around the TV’s menus. A phone remote on the same Wi-Fi works as long as the TV’s remote service is enabled, and on Fire TV TV Remotely connects through ADB debugging, so leave it on until you finish. If the phone remote is the thing that broke, the first row of the package table above is usually why.
Sources for these instructions
- CleanYourTV restore guide: recovery record, restore commands and fallback — checked 2026-11-18
- CleanYourTV FAQ: bricking, factory reset from recovery — checked 2026-11-18
- CleanYourTV troubleshooting: boot loops, black Home, setupwraith Wi-Fi and RecoveryActivity — checked 2026-11-18
- Android Developers: adb and the package manager — checked 2026-11-18
Frequently asked questions
- Did Claude Code brick my TV?
- Almost always not permanently. Disabled packages stay installed, so re-enabling them or a factory reset brings the TV back. Owner reports of TVs that still looped after a reset point to hardware faults.
- Will a factory reset undo the clean-up?
- Yes. Everything the clean-up changed lives in the user data the reset erases, so every disabled app comes back. Your own apps, sign-ins and settings are erased too.
- I lost the list Claude Code used. Can I still undo it?
- Yes. `adb shell pm list packages -d` shows what is disabled now. Re-enable the ones you recognise from the session, starting with the launcher and any package tied to a broken feature.
Use TV Remotely with a compatible TV
Install on iPhone or Android, then follow the pairing steps for your TV. The TV must already be reachable on your local network; the app cannot bypass setup or an approval prompt.
