Recovering a Borked Sideload on Android TV That Failed Boot

Updated 2026-10-30

The problem: what happens when an Android TV sideload fails at boot

You tried installing an app or a bundle before a power cycle, but the install never finished cleanly. You power on the device, and the TV shows a boot loop, a black screen, or a generic “App not installed” error. In the worst cases, the system partition looks corrupted and you’re stuck staring at a loading spinner. This is one of the most frustrating failure modes for Android TV owners who rely on third-party packages like Kodi, Plex, or custom launchers. The sideload process itself didn’t crash the install—it just stopped cleanly in a state the OS doesn’t know how to recover from without a factory reset.

If you need to fix this without wiping the device, the key is understanding the two layers that can break: the package manager that handled the APK unpack, and the system state files left behind on the failing side. Most modern Android TV builds store sideloaded packages in /data/local/tmp/com.android.packageauthor, and a half-install can leave orphaned metadata that blocks future installs until you clear it manually.

Tools you’ll need for a safe recovery

Before you touch anything, gather the right tools. Your primary method is ADB on a computer connected to the TV via USB over Ethernet or Wi‑Fi (screen-to-screen screen mirroring works too if you can get ADB running).

First, confirm ADB is working on your workstation. You need adb version to see a recent release. On the TV itself, go to Settings > About > Device Info > ADB, and make sure it reports a usable ADB connection. If it doesn’t, you may need to enable Developer Options on the TV (Settings > System > Developer options, enable ADB and USB debugging).

The essential commands for a failed sideload are:

• adb shell pm list packages – shows which packages are currently installed
• adb shell pm uninstall --user 0 <package> – removes a package and its data
• adb shell pm clear com.android.packageauthor – clears the package author cache
• adb shell rm -rf /data/local/tmp/com.android.packageauthor/* – removes leftover package files
• adb reboot – restarts the device once the cleanup is done

A second option for heavier fixes is a factory reset from Settings > System > Reset options. You must back up any account-only data first, because a reset wipes everything except the factory image. For production devices running Google TV or the standard Android TV firmware, the factory reset method is the guaranteed fallback. The recovery path I’m detailing here avoids a wipe whenever the package manager state allows it.

Step-by-step: clearing partial installs that cause boot failure

Start with the least destructive action: trying to complete the failed install before doing anything else. Because the boot failed, your regular app list probably can’t be displayed, but you can still test whether the install metadata is intact. Run adb shell pm list packages from the command line. If the list is empty or truncated, the install metadata was interrupted and the package either wasn’t unpacked or was partially unpacked.

If the list shows a partial entry, or if you see duplicate entries for the same app (some users have reported seeing a “duplicate” warning during recovery), proceed to remove it:

adb shell pm uninstall --user 0 <app.package.name>

Replace <app.package.name> with the name of the offending package. If you don’t know it offhand, grep through the output with adb shell pm list packages | grep -i kodi (or the package name you expected to install). After the uninstall command finishes, run adb shell pm clear com.android.packageauthor. Then check the package list again. If the bad package is gone and nothing else is missing, try a cold boot by holding the power button and selecting restart.

If the boot still fails after removing the partial package, you’ll need to clear the leftover files explicitly. The directory /data/local/tmp/com.android.packageauthor holds the author markers for sideloaded packages. An empty chroot-like view of that directory often reveals the orphaned entries from the broken install. Remove everything inside it:

adb shell rm -rf /data/local/tmp/com.android.packageauthor/*

Then reboot. Some TV models also cache per-package state in /data/local/.adb or in the system partition’s /data/recovery. If those exist and are unusually large, consider deleting them, but back up the recovery partition contents first—many setups don’t have easy access to those, so tread carefully.

What usually goes wrong and how to avoid it next time

The most common mistake is assuming a sideload completes atomically. It rarely does. When a package is large or contains native libraries, the unpack stage can be killed partway through by a power blip, OS timeout, or a temporary storage drop on the TV’s internal flash. The incomplete state leaves the package’s app binary and its metadata pointing to a non-existent installation record, which manifests as a boot hang.

Never sideload while the TV is plugged into an unstable power source, and prefer Wi‑Fi over Ethernet if both are available—some older Android TV boxes throttled network during sideload downloads. Another rule: install one package at a time. Do not try to push a full media suite as a single bundle. Each bundle contains dozens of shared dependencies, and if one piece fails to resolve due to a transient network hiccup, the whole thing can abort mid-way.

If you must install a large bundle, do it from a wired Ethernet connection with the TV’s micro-USB port powered from a stable device. Test the TV with a small package first—like a simple utility app from the Play Store—to verify the package manager plumbing is healthy before attempting a heavy install.

When recovery isn’t enough: choosing between repair and reset

If you’ve cleared the package author cache and removed the bad package, but the boot still lands on a black screen or on the “Apps not installed” prompt, the remaining state is almost always the system partition’s app cache. That’s harder to reach without developer mode and fastboot, but on many Nvidia Shield TV, Xfinity Flex, and similar Android TV hardware, you can enter recovery mode and choose “wipe cache partition.” A cache partition wipe is safer than a full factory reset because the system image, user data, and account settings remain intact.

Only perform a factory reset when the boot fails repeatedly with the same error, or when the TV no longer shows any UI at all. Back up your Netflix login, your Google account, and the Plex media server credentials before resetting. Factory reset is the last resort, and it’s irreversible from the TV’s perspective.

In practice, the cleanest way to recover a borked sideload on Android TV today is to clear the package author cache, remove the partial package, and reboot. If that still doesn’t bring back the UI, a factory reset followed by a recan of the install from the Play Store (or a trusted APK host) is the reliable path. Avoid factory resets when possible—these devices are built to be reused years, and every reset erases user content. You can almost always reinstall the exact same package from the store, and the boot failure is usually a single bad install that we can undo without taking the whole box to the shop.

Related reading: more Android TV notes