Yeppers. It’s in “scripts”
pure1@pure-pc:~/librem5-flash-image$ dir scripts
librem5-devkit-flash-image librem5r2-flash-image Makefile
librem5-flash-image librem5r3-flash-image
librem5_flash_image.py librem5r4-flash-image
pure1@pure-pc:~/librem5-flash-image$
BTW. I just follow orders and cut & paste.
What happens when you just run:
./scripts/librem5-flash-image
Info:
I’m gonna get some sleep now, it’s near midnight.
pure1@pure-pc:~/librem5-flash-image$ ./scripts/librem5-flash-image
2024-04-29 13:52:49 INFO Looking for librem5r4 luks byzantium image
2024-04-29 13:52:58 ERROR No matching image found
Weird huh! Have good rest.
~s
Are you aware that
Google layoffs: Sundar Pichai-led company fires entire Python team for ‘cheaper labour’
~s
OK I think both commands are wrong. (I’ve added that to my list of things to edit.) However most of the time, you can ignore that command anyway. I have never done it (because I have assumed that I have everything that is needed already installed, which admittedly may not pan out as an assumption).
On this point you are better off following post 16 above which just directs you to install some hard-coded dependencies in step 1. I think you have probably already got past that step.
Reiterating … I suggest you add --stable as an argument when you run the shell script to flash the phone.
That would be in addition to your choice of variant (encrypted or unencrypted) - but at the end of the day, if you can complete the flash process at all, you will be in a good position to flash with the variant that you actually want.
luks builds are failing, see Image Build [Image Builds] [Jenkins]
looking into the build logs of these builds show
ERROR: command failed: ['cryptsetup', 'luksClose', '/dev/mapper/crypt_root']
Device /dev/mapper/crypt_root is still in use.
Creating disk image
Creating partitions
Using bootoffset: 5mib 5242880 bytes
Using bootsize 493mib: 512000000 bytes
EEEK! Something bad happened...
command failed: ['cryptsetup', 'luksOpen', '--key-file', 'passphrase.txt', u'/dev/mapper/loop37p2', 'crypt_root']
Device crypt_root already exists.
.
.
.
By default librem5-flash-image script downloads the luks variant, so try the plain variant.
This time it at least had a happy ending. t’s not the same since last up-grade/date - change where there is a icon with a dinosaur, and other additions I can’t remember. Still cannot get rid of the orange square with a small ! in it the square over the mobile bars, top left. Meaning, still can’t send text w/. image (small image - the one below)
But this time around #7 I think, resulted in:
I gather there are a lot of update/grades to get down.
I did what @irvinewade and @amarok and @shopping4purism and yourself suggested. Together, it installed this time.
Now to bring it up to snuff. sudo apt update says there are 131 “packages” update…
Wow, I updated and upgraded (I think) without asking how. Like a spitball, some things still stick in my head.
You can remove the exclamation mark by toggling mobile data off and on.
Great news!
I dear not mention it, but perhaps now is a good time to create a backup image of your phone by using jumpdrive.
With such image it is far more easy to restore the state of your L5 compared to flashing the L5.
@irvinewade @amarok @shopping4purism
At first just toggle Data on and off didn’t not work. So I disabled data, restart device, enable - fixed.
Too, it really didn’t install upgrade or update the OS because the last OS had more program icons, and various screens didn’t overlap to the right. I didn’t add them. A very recent upgrade or update was a cosmetic and icon improvement. I think this exercise resulted in a very old install of much earlier versions of the OS.
I missed the celebration of life for Chat. R.I.P. Chat. Will hunt for a good chat program, stalker or not. Don’t care any more so long as it works. I try to send 1 text w/ pic and I see 6 of the same sent at the same time, but pics w/ images, or the smiley don’t go anywhere - just multiply like rabbits. There is no telling if it goes or not. Just sits there looking smart. Confirmed with other people that they receive a text, but not if there is a pic in it. Maybe I need to upgrade Chat for the Pro ver$ion.
Display is set to 720 x ??? and 200 x ??? (???) is offside. Zoom is 200%
Almost forgot to mention that the Pure OS Store is anorexic now that it’s back to the snail-pace load of the screen (don’t dare mention it might be my ISP) it take several minutes to show ONE available app. Leaving that page using < or swipe does nothing but lock the screen. Press Power button, log back in and then close Store and re-open to expect the same service!
BEFORE resorting to a week of flashing, the store loaded fast, pages like Create were very different than the existing Twilight zoned imitation of a store. It literally takes 2-4 minutes for the category to end up displaying a white page.
I did the Upgrades and Updates and it says to do. Can’t even install apps that don’t show up in the Store (polite word for nowhere land.)
All that flash trial and error for nothing. 
In my experience, sometimes it takes a minute or two for a SIM to acquire the mobile network. I don’t ever toggle on and off.
Right. What flashing does is install a “baseline” image with a select few programs. It wipes out anything you had before. That’s why it’s recommended to back up your list of installed applications before flashing, to make it easier to find and reinstall them.
lsb_release -c
If it returns byzantium, then it’s just a question of applying any available updates to bring everything up to date. If it returns amber, then that’s a problem; it would mean that somehow the script downloaded the wrong version.
I’m not sure how to fix Chats issues. Did you re-add the Koodo MMS settings, by the way? (Don’t forget you will also need bm818-tools for VoLTE.)
Hmm. That shouldn’t happen. The default is 720 x 1440 and 200%. Try reducing it, then enlarging it again.
Also remember to reinstall phosh-mobile-settings, which allows auto-compositing selected apps to fit the screen.
A known issue, unfortunately. Sometimes it performs reasonably well, sometimes not.
By the way, sudo apt update updates native apps, but not flatpaks, so if there are any installed, you also need to do flatpak update for those.
Both Koodo and Volte are set properly - same as before the multi-flashing. Checked and tipple checked w/ Koodo site. Volte is enabled CBS not checked.
lsb_version -c shows “codename byzantium”
“phosh-mobile-settings is already the newest version” so says sudo apt install phosh-mobile-settings
That is new to me. The last upgrade/date (a few days ago before last sort-of-successful pre-flash that added several new icons, changed others (like the screencap app) and added a in-between screens background. It’s why I think this is waiting for that update. Yet, upgrade and update show everything is updated/upgraded.
I’ve been reading a large novel at flatpak web site how-to’s.
As for Puri store, the one that came w/ last up-something showed what appeared to be a faster very different layout.
Thanks amarok for trudging through this with me. I’m learning.
The store updates them along with native packages, however in terminal, you have to run that command separately to update them.
Probably not needed, unless you’re just interested.
Since you did not know about flatpak I guess you don’t have any installed.
If you want to check if you do have installed one ore more flatpak apps,
you just need to type into terminal:
flatpak list
This command shows all installed flatpaks.
I thought it might help me get it device to where it was when Puri put the last update/grade and to find some
wares in a list of some good apps Programs.
Have Warp and “… …latform 44” whatever that is.
sudo apt upgrade
sudo apt update
Commands should be in the opposite order.
Sometimes you need to use
The why and when using 2) is not clear to me, but when I experience upgrade issue’s
I use the ‘full-upgrade’ method.
