A dead or unresponsive remote is usually blamed on batteries or a faulty IR sensor, but on GX6605S boards the firmware itself is often the actual culprit. Here’s what fixed it across several test units.
The first thing worth checking is whether the remote works fine in the boot/recovery menu but fails once the main firmware loads — if so, that points squarely at a software-level input driver issue rather than hardware. Reflashing with a clean, matching dump resolved this in most of the cases I tested.
Some firmware versions also let you reassign or recalibrate the IR profile from a hidden engineering menu, which fixed intermittent button lag on a couple of boards without needing a full reflash.
If the remote still misbehaves after a clean flash, it’s worth ruling out interference from other IR-based devices nearby, since some GX6605S firmware builds are oddly sensitive to ambient IR noise.
Verdict: Before replacing a remote or sensor, try a clean firmware reflash first — it solved the issue far more often than expected.
Discussion