414
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 29 Sep 2026
414 points (98.8% liked)
memes
22781 readers
2414 users here now
Community rules
1. Be civil
No trolling, bigotry or other insulting / annoying behaviour
2. No politics
This is non-politics community. For political memes please go to !politicalmemes@lemmy.world
3. No recent reposts
Check for reposts when posting a meme, you can only repost after 1 month
4. No bots
No bots without the express approval of the mods or the admins
5. No Spam/Ads/AI Slop
No advertisements or spam. This is an instance rule and the only way to live. We also consider AI slop to be spam in this community and is subject to removal.
A collection of some classic Lemmy memes for your enjoyment
Sister communities
- !tenforward@lemmy.world : Star Trek memes, chat and shitposts
- !lemmyshitpost@lemmy.world : Lemmy Shitposts, anything and everything goes.
- !linuxmemes@lemmy.world : Linux themed memes
- !comicstrips@lemmy.world : for those who love comic stories.
founded 3 years ago
MODERATORS
I've had three boards that advertised that/recovery bios that I needed the feature for, and none of them have worked. Also even if the features does work, it's a one-shot safety net; what are you going to do, abort your plan to update? If you did everything right the first time, you'll just end up with two bad flashes, so you're right back to nail-biting anxiety.
You'd think that a board would auto-revert from a failed flash, or - just spitballing here - make their fucking firmware for their fucking hardware not fucking fail spectacularly from basic testing and quality control. But I guess failed flashes drive sales so fuck fixing the problem, I guess.
Ugh. Actually angry about this, phones have had this issue solved for 15 years now but motherboards that have been around for like 50+ years, nah, too complex to fix. Sales go up ooga booga.
Wait, that is such a good point. Why aren't motherboard firmware updates atomic?
Hmm, my motherboard (Asus) just has a reset button that flashes the contents of the secondary ROM to the primary ROM. If there's any problem getting the primary to POST, you just push the button and it reflashes the primary from the secondary, so you're back in the original state. It's not a one-shot, because the contents of the secondary don't change. You can use it as many times as you need to.
Once you get a good POST from the primary, it updates the secondary. I've never had an issue with this system.
Phone mainboards are very different, which is a big part of why maintaining third-party phone OSes is such difficult work, and why GrapheneOS constrains itself to specific devices.