GitHubWhat they did
The poster, u/Personal-Conflict952, bought a no-name DQ10 Android TV stick and asked Claude Code to reflash it with clean firmware and make it safe. Claude Code ran on Windows with Git Bash, a Kali WSL2 distro and usbipd-win passing the stick's USB through. The main Opus session planned and ran every hardware command, a Sonnet subagent built the U-Boot config, device tree, image and scripts, and a separate Opus subagent audited each plan on a fresh context. Nothing was written to the stick until an audit passed and the poster said go. The poster only plugged cables, held the button and read the TV. Every decision was logged to an Obsidian vault, and the scripts, runbook, audits and malware indicators were published on GitHub.
How it went
Claude got root through unauthenticated ADB, isolated the stick behind a firewall and backed up the eMMC. The backup held a vendor remote-command system and a packed Go binary with reverse-tunnel code running as root, so Android was replaced outright. The stick now boots mainline U-Boot and Armbian from its own eMMC with Wi-Fi and key-only SSH. Four audits caught brick-level mistakes, including a power-cycle instruction mid-write and a bootloader that only started 1 time in 6. With no serial console, Claude debugged with LED blink patterns and reset timing. Some guesses were wrong and corrected by data.
Worth knowing
The poster hit the 5-hour and once the weekly usage limit, and subagents died mid-task; resuming the same agent kept its context. The 50-minute flash ran detached inside WSL so it did not depend on the session surviving. Several commenters dismissed the post as AI-written. It is the poster's own device; the same method on hardware you do not own is off limits.