Story: SteamDeck stuck at TTY Login Fix after SSD Upgrade
I had 6 hours of trouble last night and thought I'd share this information with you as many people will be doing the same. So here's the story:
My girlfriend bought a SteamDeck in the summer sale and I told her to get the cheapest one and upgrade the ssd as soon as it arrived.
For 2 days everything worked fine. Swapping from 64GB to 512GB worked perfectly and installing SteamOS on the new drive was no problem at all.
While I was at work, she texted me that the deck was getting very laggy in games and in the UI itself, so I asked her if she had already rebooted or set any kind of tdp or performance limit (which she denied).
So she rebooted her machine from the laggy ui and it got stuck with the boot logo. After a few minutes it went black, the backlight was still on and the fan stopped.
When I got home, I reinstalled steamos for her from the usb stick we made a few days ago (went for the reimage). I tried to boot, but the same problem occurred. After a few minutes it went to the TTY login screen and asked for a user, but the cursor froze immediately. I also tried to switch TTY sessions with ctrl - alt - f4-f6 - but that did not work either.
So I flashed the USB stick again, but nothing changed. Then I deleted all partitions manually and nothing changed. I booted my windows sd card which worked fine. So I thought maybe the SSD was broken, so I went into recovery live boot with "smartctl -a /dev/nvme0n1" to check, but everything seemed fine.
I also filled the whole SSD with zeros and tried again. Nothing.
Same problem. It's weird, but it was solved by putting the battery in power saving mode:
Enter the BIOS at power up (Power + Vol+) with the PSU disconnected.
Inside the BIOS, use the D-pad to navigate and the A-button to select.
Navigate to Setup Utility.
Navigate to the Power menu.
Select Battery Backup Mode.
Select Yes to confirm.
Your Steam Deck should now enter storage mode.
Then plug in the power supply and switch on the deck.
In my case, it booted correctly.
I know it's weird, but it actually worked.
Good luck with that!
And my fucking God, that thing fixed it. I have no idea why that would fix it and I'm happy for anyone who can explain it to me. I'm fucking curious :D
And my fucking God, that thing fixed it. I have no idea why that would fix it and I'm happy for anyone who can explain it to me. I'm fucking curious :D
so, you put it in storage mode (or shipping mode) to fix it? that’s definitely weird. maybe it’s doing something to reset some hardware configuration? like, it’s expecting to be serviced so it resets what it knows on its own hardware? it would be weird though, I don’t get what could change hardware wise that it’s not already managed by a normal firmware/bios.
Yeah, I couldn't make sense of it either, but this worked like a charm and has worked for others. A friend of mine was having touch issues and was also told to put it in battery backup mode and that fixed it too.
Funnily enough, I had it the other way around! I copied my old drive contents into the new one with dd, but after one successful boot into the new SSD it ran into the same issue as you. I tried entering battery backup mode a few times but it didn't fix it. Only after I reimaged completely and then did a battery backup did it start working. Been good for months now though!
I'm about to replace the SSD on my Steamdeck myself in the next days. So, perfect timing.
If I understand correctly, battery storage mode is disabled by plugging in the charger. So there is no downside to this fix?
Did you activate battery storage mode before replacing the SSD? I think, the iFixit guide recommendeds activating it.
I did not put the SteamDeck in BSM before installing the SSD. I think this should avoid the problems I had. The BSM is disabled when you plug in a charger or switch the deck on again, so there is no downside to this.
When you installed the drive, did you first put the Deck into storage mode or disconnect the battery before disconnecting the drive? I know it's recommended to do that. Could possibly be the cause as it's obvious that the hardware is fine.