If I didn’t get nerd7473 wrong he’s using his second device. So I guess there is no important file that needs to be saved.
However, wouldn’t it be better to flash it to crimson instead of updating? At least for people who want a “production-ready” experience with stable crimson builds later. Or am I wrong?
By cleaner, I mean, for example, that everyone installing crimson from scratch has an initially identical system.
As a data point, when a new LTS version of Ubuntu is released, they don’t even offer the upgrade from the previous LTS version until the first point release update to the new LTS version comes out. So the only way to run the LTS version immediately is to install from scratch (unless you really want to be on the bleeding edge and force the update before it is offered and are prepared to deal with whatever mess ensues).
After you download it, extract the file and put it in the root directory of librem5-flash-image. Also get the DAS U-Boot image (u-boot-librem5.imx) and place it in the same directory.
Well, since December 27th, 2018, whenever anyone followed the instructions to reflash the Librem 5, the plain variant was used as the default. It was only recently changed to LUKS in June 23rd, 2023, which my actions may have been a catalyst for: I mentioned about it to Purism support just before I decided to make a forum account on June 26th, 2023.
@FranklyFlawless
Thanks for the instructions. I can reflash the L5 with byzantium no problem, but the git scripts mentioned above are for flashing byzantium, not crimson AFAICT. I am getting ‘image not found’ errors when executing any of the flash-image scripts. The script needs modification for crimson but I have no idea how to change it.
Yes, now the script progresses. When I plug in the phone, it begins the flash but dies before the process completes. The messages are as follows:
1:3 3/ 5 [===========> 32% ] FB: flash -raw2sparse all
Traceback (most recent call last):
File “/home/pureos/librem5-flash-image/./scripts/librem5-flash-image”, line 538, in
sys.exit(main())
File “/home/pureos/librem5-flash-image/./scripts/librem5-flash-image”, line 521, in main
flash_image(uuu_target, args.debug)
File “/home/pureos/librem5-flash-image/./scripts/librem5-flash-image”, line 351, in flash_image
subprocess.check_call([‘uuu’, uuu_target])
File “/usr/lib/python3.9/subprocess.py”, line 373, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘[‘uuu’, ‘./flash_librem5r4.lst’]’ died with <Signals.SIGBUS: 7>.
Those last few messages are referring to uuu. If you have not done so already, you need to install uuu and the udev rules for serial access permissions to the Librem 5.
I ran through the install steps up to the udev rules install. uuu is installed and the udev rules are there in /etc/udev/rules.d/70-librem5-flash-image.rules but the script keeps dying at the same spot.
This may be hard to believe but after leaving the L5 sit all night with no battery, I re-ran the script again this morning from my Debian Trixie PC (yesterday I had been using my KDE Neon install) and, yep, you guessed it. Worked like a charm! I appreciate all your help.