Join the discussion

Write your take first — we'll ask for email only when you're ready to publish.

  • Hacker News
  • I really like what Framework is trying to do but this story is very hard to ignore. If a failed BIOS update can brick the machine, and the official solution is a CA$500+ motherboard (that's about $350+ USD I belieive), there's still a pretty big gap between being modular and being truly repairable

    Not to mention there are no "alternatives" that you can look into to purchase these replacements. You are essentially just locked to purchasing from Framework only

  • I really don't understand how in 2025 a competent company can't implement a trival A/B flash update. Do they depend on some obscure contractor for the firmware and have no power here?
  • Good story, and surprising that there was so little assistance from the OEM. As an aside, I got to test out Asus crash free BIOS a couple of weeks ago. A strong thunderstorm hit and before I could get to my office a rapid series of deep voltage drops occurred. I shut down my systems and waited out the storm. When I powered my Asus tower back on it failed to POST, automatically restarted, recovered the BIOS (CMOS settings I assume), restarted again and booted Windows. Pretty slick, and instantly removed that cold lump of lead that had formed in my gut.
  • > Framework chose to not provide a header for flashing the BIOS, which, when combined with issue #3, forced the use of pogo pins.

    Op probably missed https://github.com/FrameworkComputer/FrameworkDebugger#jspi. Though, the connector is not populated for cost reasons.

    Otherwise, I agree with the author, this is a pain.

  • I agree with their conclusion.

    I somewhat regret buying my framework laptop at this stage, because the answer to every fault is "buy a new component, from framework".

    I'm not sure I blame them for this really, but there is no competitive market of parts (or really any market at all), which means that the reality is that you're just locking your money to them. They also often have stock issues, so woe betide you if your component fails at the wrong time.

    It's very hard to predict costs here, but framework laptops do seem to fail more than other brands, and their laptops do tend to be more expensive. In comparison to MacBooks I've used over the years, which other than screen delaminating, have been faultless, at least.

    by SCdF
  • A bit off-topic, but kind of relevant. I firmly believe that if installing custom firmware voids the warranty of a device, installing official updates should extend the warranty.

    I'm tired of sloppy updates or change of behavior that mess with how I use MY device.

    At this point, I'm convinced Google is doing this on purpose. My Google TV has become slow since the Gemini update, which I wasn't asked if I wanted it. My pixel battery life gets worse with every update, etc.

  • I had the same thing happen to me with my Thinkpad Nano, and researching how to fix this made me realize pc manufacturer really don't care. PC bricked from BIOS update are still ultra common.

    I uploaded a dump of the flash [1] in the bad state and they somehow analyzed it and made a fix. Great for others I guess, but I'm still mindblown that the regular path would have been that this perfectly working laptop to this day become ewaste.

    Being an embedded dev, I don't understand why there isn't a special USB-C protocol to recover bios over SDU/CC pins. Or some DFU mode you can boot into.

    [1] https://github.com/fwupd/firmware-lenovo/issues/484

  • I think cases like this should be brought before a small claims court. It seems unfair. The company (Framework Computer) provided the software, but the software is faulty and broke ("bricked") the laptop. Can you imagine if a GPU driver caused the card to get bricked? Even if out of warranty, surely the manuf would be legally liable in many jurisdictions for this faulty driver.

    The author's LinkedIn profile[1] tells me that this person lives/works in Toronto, Ontario, Canada. While the issue is already fixed, for others affected with the same issue, I would suggest the small claims route. Make sure to talk with an LLM to follow the correct steps to gather and prepare evidence for your claim. If you are lucky enough to win, then you should "go nuclear" on social media (and their own forums) to share the win and the exact details about how you did it. Framework Computer will surely (1) cave and provide replacements or (2) be flooded with small claims about this issue.

    [1] https://www.linkedin.com/in/guanzhong-chen/

Explore Birbla archives