[bug] Steamdeck don't boot in 3.5.19 (stuck on logo / stuck on verifying installation). 3.5.17 is ok.

[judbd]

Your system information

• Steam client version: ?
• SteamOS version: 3.5.19-20240422
• Opted into Steam client beta?: No
• Opted into SteamOS beta?: No
• Have you checked for updates in Settings > System?: Yes

Please describe your issue in as much detail as possible:

I updated the steamdeck from 3.5.17 to 3.5.19 as prompted, it was OK, then I updated the softwares that needed updates in destkop mode, updated decky script, all was OK, I was able to play for some days.

Then ~2 days ago the Steamdeck is stuck on Steamdeck logo. When I hold power button down to force power off and then restart it, it's stuck on the logo + "verifying installation". If I replay this sequence when connected to ethernet with a dock or with my phone in tethering connection, the verification is successful and the OS boots up. But I don't always have the dock so it's not a long term solution.

I did not install new games or updates or anything before this bug, all was normal 3 days ago with 3.5.19 installed.

Booting in 3.5.17 works fine (holding … + power but I don't know how to keep it, and what will happen if I update from this, I don't want to have 2 3.5.19 partitions an no more rollback options. If I install a version from the beta chanel, I fear that the old version becomes 3.5.19 and that I can't rollback if the beta have the same issue.

I tried to boot in boot mode again to do more tests, but now the d-pad and buttons are not responding and I can't select the B/3.5.17 version anymore.

Steps for reproducing this issue:

1. Update from 3.5.17 to 3.5.19 (OLED 1To)
2. Try to boot
3. It fails (logo stay displayed)
4. Hold power down
5. It's rebooting and get stuck on logo + progress bar "verifying installation"

[BrunoTheMad]

I am experiencing this as well, and it continues to occur after resetting the bios and re-imaging the steam deck + updating to the current stable branch. Also noticed the boot hang does not occur on 3.5.17, only after re-imaging and updating to 3.5.19.

There are several reddit threads that mentioned this occurring after the last stable branch update as well.

[Okttenda]

I have the same Issue even after 3.5.19. Noting I am indeed on the Beta Channel and it seemed at least from now that it's only occuring on the Beta Channel. I only use the Beta Channel for Family Sharing Beta and it seems there is no standalone beta for that on the Steam deck.

[jfrconley]

I am also getting this issue now, the published workaround of using home wifi or Ethernet are not working. Neither of my installed versions are working (3.6.12 and 3.6.9)