Hello, I may have caused a bit of an oopsy-soft-brick. I tried to update to Crimson by editing the /etc/apt/sources.list (I included crimson-proposed, probably should not have) because I needed a new version of something. I did a apt upgrade and apt full-upgrade.
The update itself did get interrupted, there was a point where text encodings seemed to break and I couldn’t sign in with my pin and was not even sure the update was making progress, so I restarted. But apt gave me instructions for what to do after trying apt upgrade again.
Something seemed to go wrong and triggers failed to process for tpm-udev, I just updated again but didn’t examine the result all that closely.
I restarted and I started to have issues, I didnt see the prompt/keyboard to type in my LUKS key, I see the Librem 5 splash screen in between console log messages, this is what I see:
“Nothing to read on input”
“cryptsetup: ERROR: crypt_root: cryptsetup failed, bad password or options?”
“cryptsetup: ERROR: crypt_root: maximum number of tries exceeded”
Each message is repeated multiple times, first a number of the first one, then in cycles several of the second and one of the third.
It seems to be an issue with I/O.
I know some people have had similar issues after trying to update their L5:
- Can't enter disk encryption password after update
- Can't use L5 after update! - #14 by mladen
- Last update phone stopped working - #21 by FranklyFlawless
I researched the “Nothing to read on input” error in particular and found that people on laptops resolve it by just typing in the password unprompted and it seems to work.
I don’t have an on screen keyboard and I tried connecting 2/3 external keyboards, but they don’t even seem to be getting power. If I press caps lock, the indicator light does not turn on. The L5 doesent seem to be responding to inputs either (could it be usbguard? or too early in the boot?) At least one keyboard I tried was PS/2 and the other(s) were USB.
I would like to avoid flashing the phone, and it may be a bit paranoid but I honestly would like to avoid connecting it an external computer (or really anything else external),
Summary
(it might be a bit paranoid but it was expensive and I would like to avoid giving certain/untrusted hardware direct memory access, and I would like to continue to know an issues with other hardware have not made it onto there or had the chance to exploit vulnerabilities, not everything is FLOSS/easily auditable all the way down :()
I have also contacted support. Any help would be greatly appreciated.
A possibility: somehow writing a file to disk with the decryption key (then changing it later on perhaps):
- centos - Automatic LUKS unlock using keyfile on boot partition - Unix & Linux Stack Exchange)
- boot - What is the correct way to use key file LUKS authorization? - Ask Ubuntu
Also the LUKs prompt itself disabling I/O?: No keyboard input at LUKS passphrase prompt - #2 by linux-aarhus - Support - Manjaro Linux Forum