Oddly enough, my phone puked (i.e. didn’t respond to touch at encryption log-in) after a recent update too, so I went through the easier process through jumpdrive again. However, I did notice the files were a bit different than they used to be. Now every file, new and old, has its version number. e.g., there’s no vmlinuz nor vmlinuz.bak. There are however four files in the fashion, vmlinuz-6.6.0-1-librem5 and vmlinuz-6.5.0-1-librem5. I couldn’t find a quick way to have the boot sequence point to the older version, so I just copied the four 6.5.0-1’s over the 6.6.0-1’s, and it seemed to do the trick. Maybe someone has a more clever way of just pointing to the vintage file?
Sad side note - when I ran the update again (after I copied over and got it to boot fully), the reboot did the same thing - no touch response at the encryption login screen. But the copy-over worked just fine again. Guess I’ll just wait awhile before I update the phone again, and hope an updated update comes out that doesn’t have the same issue on my phone.
It’s different from most big computers that I have seen where those names will exist without version numbers as symbolic links to the names with the chosen version number (so theoretically it could be easy to revert) - although the previous version may be .old rather than .bak.
Strangely though I am running 6.6.0-1 and I am not experiencing the problem entering the encryption passphrase.
I did delete most of them, but I still had the same issue on the upgrade reattempt. Now I figure I’ll just wait until there’s two versions up, and hopefully jumping the current one will work?
