Thanks but I think, that I am the wrong guy for the job. It still doesn’t work because, there is no header.
Maybe I can do it with --header /dev/loop1p1 while encryption is on /dev/loop1p2, but it was not going anywhere.
I tried to directly encrypt via jumpdrive:
sudo cryptsetup reencrypt --encrypt /dev/sdb2 --header /dev/sdb1
one hour later:
This doesn’t work.
Hi ein_dude,
if you aware of loosing all data and flash the phone with crimson. You may want to use the tresore/backup app to create a backup on USB or Cloud or MSD Space.
Edit-Paragraph: I may have you misunderstood. I have also some not encrypted MSD but a Lukes encrypted Crimson L5 installed Flash Pureos Setup. You flash pureos and add a LUKES encryption with a different pass later.
Then you could more easy flash crimson by using a Linux Laptop (or a Windows one -PureOS Crimson Development Report: June 2025 – Purism) like suggested in the wiki:
https://docs.puri.sm/Hardware/Librem_5/Maintenance/Reflashing.html
With the change of source in the downloaded and flashing part:
./librem5-flash-image --stable --variant luks --dist crimson
Then you will have a L5 phone with crimson.
But have a Backup and later you like to install up to date Apps. gilally have some overlay - but i just installed some preferred flatpaks and it was fine to use.
Regards
Christal
Hi Christal,
thank you for that! I wasn’t able to just install crimson beforehand. Now this was fresh and easy. 
The thing is that I was greeted with the “low disc space notification” and therefore I won’t use the luks variant. Maybe this issue will resolve in future crimson luks variants, but I am okay by staying in plain file system. 
Maybe it is possible to resize via ssh connection or jumpdrive, but I am good with the solution I have now. Just wanted to test the luks variant.
I am only a user and I can only use what these great developers achieve. Thank you all!
Regards,
Alex
Actually, you should have all disk space, the warning is probably the result of a race condition, see: First boot gives low disk space warning (#51) · Issues · PureOS / Tasking · GitLab
crimson alpha images are now available.
librem5-flash-image --dist crimson
I used librem5-flash-image from sid (trixie also has the latest version).
crimson alpha images are now available.
librem5-flash-image --dist crimson
That may need to be librem5-flash-image --dist crimson --stable as for some reason it didn’t find any image to download otherwise. I think it then downloaded the latest Aug 28 r4 image (it’s hard to tell as the alpha seems to be pretty much as the previous images and the software is still the old versions - as could be expected, although not as hoped).
What does
lsb_release -c
output?
That there are no lsb modules and codename is crimson - nothing more specific.
It does not matter much. The real crimson will be the one with all the updated packages - those will determine (to users) how up to date the system overall will be (comparisons to old byz and also to what’s in use elsewhere, and all that).
That’s OK. It was just to confirm that you did download and flash crimson, as premature as it may be at this stage.
Ah. I was more hoping cat /etc/*-release would have been more informative.
