Legion Go controller firmware is separate from the handheld’s Windows installation, AMD graphics driver, and system BIOS. On the original Legion Go 8APU1 (Type 83E1), firmware versions for the left and right TrueStrike controllers matter when buttons, pairing, calibration, or motion controls behave incorrectly. The safest first step is to identify the exact controller version in Legion Space before attempting any update or reset. Before starting, reconnect both controllers, keep the handheld powered, and note which side is failing. Those details help distinguish an update issue from a pairing or hardware fault.
Check the correct hardware and firmware version
This guide covers the original Windows Legion Go 8APU1, not Legion Go S, Legion Go 2, or the 2025 revised hardware. On the handheld, open Legion Space > Settings > Controller > Current Controller Version, where the installed version information is exposed in supported versions of Lenovo’s application. Lenovo’s calibration guidance distinguishes controller firmware 0231226B or above from older firmware, which is why directions copied from an early launch-day video may no longer work.
A version screen may distinguish core firmware, receiver, left-controller, and right-controller information. Record a screenshot or write down each visible component rather than assuming that the BIOS release number represents the controller version. Also note Legion Space’s installed app version, Windows build, whether the controllers are attached, and whether each one works in Windows’ game-controller test panel.
What firmware updates can change
Firmware controls low-level input processing, wireless pairing, calibration handling, and communication with the main device. Legion Space exposes higher-level joystick dead zones, gyro behavior, and button settings; changing those options is not the same as flashing firmware. Installing a new BIOS without a demonstrated controller-firmware requirement may introduce extra variables rather than fix an isolated trigger problem.
Firmware also does not repair physical defects such as a broken switch, loose rail contact, worn joystick or battery. A controller that vanishes from Windows entirely requires a power, attachment, or connection check before any software flashing.
Update safely through Lenovo’s supported path
- Attach both controllers to the handheld and charge the handheld using its supplied or equivalent 65 W USB-C PD power adapter. Confirm that Windows recognizes both sides. Save open work and close games.
- In Legion Space, inspect Settings for available updates. Lenovo’s 8APU1 guide documents Settings > Disks and Drives > Check for Updates for drivers and BIOS; controller-specific firmware controls can appear elsewhere depending on installed Legion Space version. Follow a controller-firmware update only when Lenovo actually offers it for this machine.
- If the app provides no controller package, open the official Lenovo Legion Go 8APU1 support downloads page and filter for the correct machine type. Never substitute a Go S or second-generation executable because its number looks newer.
- Run an explicitly applicable update with the controllers connected and sufficient charge. Do not detach a controller, switch FPS mode, unplug the charger, put Windows to sleep, or launch a game during a firmware flash.
- Let the process finish and reconnect controllers if instructed. Reopen the controller-version screen and check that the indicated component actually changed. Test analog inputs and all buttons in a known-working game.
A temporarily dark LED is not proof of a dead controller during an update. But a flash that errors repeatedly, loops without finishing, or reports an unexpected hardware ID is a reason to stop and contact Lenovo support instead of forcing another manufacturer’s firmware tool.
If calibration changes after the update
Lenovo documents different calibration gestures for firmware 0231226B+ and earlier builds. For recent firmware, holding LT + LS or RT + RS for roughly seven seconds enters a calibration procedure, followed by moving the stick, trigger actions, and gyro settling according to Lenovo’s full instructions. Older firmware used a shorter button sequence. Use the version-specific support article rather than experimenting with undocumented key combinations.
If dead-zone changes feel wrong, open Legion Space > Controllers > Joystick Settings and return to a reasonable default before recalibrating. Lenovo cautions that a dead zone below 5% may expose small unwanted movements. Calibration cannot cure an erratic or mechanically damaged sensor.
Recovery when a controller stops responding
First attach the affected controller and allow it to charge. A controller may power off after inactivity or a failed wireless reconnection; that is not automatically corrupted firmware. Restart Windows and Legion Space, detach and reattach once, and test the other side separately. Lenovo documents a small reset opening near the slide rail and a factory reset shortcut for last-resort use. A reset clears stored controller data, so record bindings and try ordinary reconnection first.
Avoid disabling Windows driver-signature protection, downloading unsigned firmware bundles, or flashing over an unstable Bluetooth connection. If the issue began immediately after an officially installed firmware update, collect the firmware versions and error message for Lenovo; a public rollback package is not guaranteed.
Firmware-specific calibration procedures are different
Lenovo’s support article HT516008 was revised in September 2026 and explicitly separates controllers with firmware 0231226B or later from older firmware. For newer versions, calibration begins by holding the relevant trigger and stick together for about seven seconds, followed by stick rotations and the indicated trigger/gyro sequence; older versions use a different three-second trigger-plus-stick initiation. Check Legion Space > Settings > Controller > Current Controller Version before giving someone a key combination. Controller firmware and BIOS versions are separate. Do not interrupt firmware installation and do not assume a mismatch between left and right controller numbers proves damage.
Keep controller firmware separate from general display drivers
Lenovo identifies the original Legion Go as Legion Go 8APU1, Type 83E1. Its October 2026 support instructions say Legion Space can check for applicable driver updates in Settings, under the drive/update section, and display available packages; this is not proof that every controller has a controller-firmware update waiting. Record the detected controller firmware version and change log separately. For context, Lenovo lists an AMD VGA driver package 25.30.44 dated September 10, 2026, but that GPU driver is not a replacement for controller firmware. If the controller version remains unchanged after a general update, inspect the controller-specific update path before attempting recovery.
Controller firmware, calibration firmware and the base are different targets
On the original Legion Go 8APU1, Lenovo documents that controller firmware is updated with the controllers attached to the tablet, while the controller base firmware can be updated through USB. These are different components; a version number displayed for RX, L or R is not a BIOS version and must not be applied to the wrong device. Lenovo also documents different joystick calibration methods on either side of controller firmware 0231226B, so check Legion Space > Settings > Controller > Current Controller Version before following any shortcut seen in a video. An update may enable a different calibration workflow without fixing a faulty stick sensor. If an update fails, reconnect and power the controllers normally and use Lenovo model-specific support rather than a generic controller flasher.
Separate a firmware update from a controller connection fault
Record whether the left controller, right controller or both fail, and whether each works while attached to the Legion Go 8APU1. An attached-only success is evidence to investigate the detached link or charge state before repeating firmware installation. Controller firmware may be installed while attached, whereas Lenovo documents distinct procedures for controller reset and for the base firmware; they are not one generic graphics-driver update.
After a supported update, detach and reattach each controller and test a recognizable input in Windows and Legion Space. Document installed firmware versions if shown and the result for each side. If one controller fails before and after a verified update, stop repeating flashes and move to Lenovo’s reset or service procedure for the affected unit.
When to stop troubleshooting
A version screen that looks different after a Legion Space update is not itself a defect. If both controllers work and the firmware updater offers nothing, no update is necessary. If a controller still fails a basic button and axis test after charging, rebooting and a supported reset, treat it as a service case—not an invitation to cross-flash unrelated firmware.
