Lenovo pulled the bad Legion Go BIOS. It still won't say who pays for the bricks.

The distribution route is doing quiet work in Lenovo's statement. V42 never went out through Windows Update or Legion Space ^[2], so the only machines carrying it belong to owners of the original Legion Go 8APU1 who went to the support site and fetched N3CN42WW by hand during the roughly two months it was posted ^[6]. Removing the file shuts the door for anyone who has not already walked through it. It does nothing for units already flashed, and because the file was never pushed, there is no update channel to work back from and no automatic path to reach the people holding it ^[13].

Then there is the instruction. Lenovo tells users who hit a blank screen to hold the power button for about ten seconds, wait about a minute, and power on again, and to contact support if that fails ^[3]. The Verge's reviewer flashed V42 onto a review Legion Go and sat through roughly six minutes of black screens and progress bars before it booted normally and started taking PIN entry from the gamepad ^[10]. A working install and a dead one look alike for several minutes, and Lenovo's guidance does not say how long a screen has to stay blank before the ten-second hold is a rescue rather than an interruption ^[14].

On money, the official statement ends at "contact Lenovo Support" ^[3]. The free-repair language comes from somewhere else entirely: a forums account called Daniel_Legion, who wrote that in-warranty devices should be repaired free of charge and that out-of-warranty devices should be too, "but please check local laws" ^[7]. That last clause moves a firmware defect into the category of things whose answer depends on which country you bought the handheld in. The account has no other visible posts, and The Verge has asked Lenovo to confirm both the words and whether it will extend warranty coverage to bad BIOS bricks ^[8].

That unanswered question is the whole story for an owner. The Verge's comparison point is Framework, which offered fixes after its own device-bricking BIOS update, and its writer's position is that a vendor should say "if we did it, we will fix it, even outside of warranty" before the root cause is nailed down ^[11][12]. Lenovo has instead published a keypress, a phone number, and a promise to keep validating future BIOS releases ^[3]. For anyone buying a device whose firmware the vendor controls and distributes, the useful reading of this episode is not the defect rate. It is how quickly the manufacturer took the repair bill off the table, and here it has not.