Cool. Fix the update that just bricked a percentage of decks.
If you updated recently, AND your wifi was toggled off on the next reboot the deck can’t restart into SteamOS. There is a handful of workaround that can fix it in some cases but essentially the Deck requires you to have internet access to verify the installation and if it doesn’t it will just get stuck on this step indefinitely.
Workaround solutions involve tricking it into thinking it is on a known network, ethernet into the dock, etc. Then loading the previous image.
The actual solution is for Steam to skip this verification step unless wifi is on and connected. It has happened in the past and with this being portable device if you happen to be using your deck in a normal way, bringing it with you traveling for example you’re fucked until you get home.
People keep downvoting users reporting issues because people think Valve is above criticism but every forum is the issue is being reported for the past several days.
And this is happening on the BETA channel. If you’re running beta, and you expect no issues, you’re an idiot. If you’re running beta, and you’re unable to investigate those issues and resolve them (Which, as you’ve such a clear, lucid understanding of what’s going on you clearly are able to), then you’re an idiot. If you’ve enabled developer options without understanding tech, and how to fix things yourself, you’re an idiot.
There’s no protecting against idiots, they’re on their own.
The vast majority of people will not see this issue because you have to go out of your way to see this bug.
Bricked as in it’s actual meaning of “it’s fundamentally broken and can only be replaced”? Or bricked in the incorrect sense that it works slightly less good?
They installed the BETA branch of steam os and are expecting a flawless experience.
They are complaining about a bug causing the deck to boot loop on verifying install. This can be fixed by simply plugging in an ethernet cord Or reinstalling steam os stable.
