If I downloaded PureOS 10 to a disc then ran it and installed uuu , would it be installed on the mint hardrive?
No, it is just temporary environment on your laptop or PC. There is no change to your currently installed OS there. After you are done with your session related to the Librem 5 recovery, you would just log out from the PureOS Live environment (make
shutdown without any changes to your Mint permanent installations, nothing will be saved there).
After few of my thoughts related to avoid (in advance) some potential issues with the https://tracker.pureos.net/w/installation_guide/ on your hardware, like those that might popup after: “Make sure you followed the procedure to create a bootable USB drive”, you might want to use some other Debian based distro (that includes …), for example you should actually use one of this Live
.iso images: https://cdimage.debian.org/cdimage/unofficial/non-free/cd-including-firmware/current-live/amd64/iso-hybrid/. Everything else related to usage of
uuu stays the same as you are here instructed from
support@ Team to proceed (as thoroughly described within related post). This way you are about (just follow this path/direction) to solve your Linux phone booting issue there, for sure.
This looks like a battery that’s almost drained.
Here’s how I deal with it:
- Get the phone into a state where it vibrates/blinks every 15sec.
- Connect to your computer over USB
- Hold the volume up button until it stops vibrating/color stays the same
- Wait about 15s
- Run lsusb on your computer.
6a. If lsusb shows the phone, it’s alive! But leave it alone for a couple hours to charge.
6b. Otherwise, leave it alone for a couple hours
6b1. Hold power button for 20s, go to 1.
He charged the battery in another librem 5. @joao.azevedo suggested the thing with uuu.
TL:DR, I suspect that the
/boot partition is full, which was why I was asking for jumpridrive to have a look at the
/boot partition. To confirm it. If that is the case it can be fixed without having to reflash the device.
Good point. Then my advice would not work. TBH reflashing is the right solution for 90% of the users anyway.
Jumpdrive might be useful to copy out data, but it’s still hard to use.
Just another variation: Librem 5 is switched off, every HKS down, battery needs to be removed. @j8m2p6f, now hold Volume-up and plug-in the USB-C cable (red light blinks, no green light), reinsert BPP-L503 battery (constant red LED light is on) and make “free of pressure” Volume-upper-side button. Please proceed as already guided here:
Thanks to @dcz you’ll sattle down even before you decide about your next step. Running
lsusb | grep 8M on your computer (within above setup) is indeed needed, as very important step there (as perhaps this Librem 5 still waits for help, for your help).
The package isn’t called
This stuff is way beyong my abilities. I need to find somebody in the US that I can ship the phone to and have them reflash the phone and I will pay them.
I am a total non computer literate person who likes privacy and security but am just not very tech savvy.
You folks here on this forum give me a lot of hope though.
@j8m2p6f, when above command output works for you as it should (when your Librem 5 connected … as described), please rethink (take your time) and implement what your host computer needs for successful
reflash of …. At least take a look at following approach: External battery charger for Librem5 or take another recommended one, yet preparation of your own Linux host computer, for any upcoming task (ensuring preinstalled packages support your intended work) is everything (although even WindowsOS, for example,
uuu approach should work too).
EDIT: Below links might be of some help there:
ls -ahl to tell me this:
ml@lib14:/media/ml/283a4739-85fc-44b7-8ee0-e0e4c328ab42$ ls -alh total 395M drwxr-xr-x 5 root root 2.0K Jan 25 16:40 . drwxr-x---+ 3 root root 4.0K Feb 1 11:35 .. -rw-r--r-- 1 root root 2.3K Jan 25 16:39 boot.scr -rw-r--r-- 1 root root 2.3K Dec 4 16:36 boot.scr.bak -rw-r--r-- 1 root root 185K Apr 13 2022 config-5.16.0-1-librem5 -rw-r--r-- 1 root root 187K May 24 2022 config-5.17.0-1-librem5 -rw-r--r-- 1 root root 190K Jul 14 2022 config-5.18.0-1-librem5 -rw-r--r-- 1 root root 194K Nov 15 16:16 config-6.0.0-1-librem5 -rw-r--r-- 1 root root 196K Jan 10 14:21 config-6.1.0-1-librem5 lrwxrwxrwx 1 root root 52 Jan 25 16:39 dtb -> dtbs/6.1.0-1-librem5/freescale/imx8mq-librem5-r4.dtb lrwxrwxrwx 1 root root 53 Apr 25 2022 dtb-5.16.0-1-librem5 -> dtbs/5.16.0-1-librem5/freescale/imx8mq-librem5-r4.dtb lrwxrwxrwx 1 root root 53 Jun 1 2022 dtb-5.17.0-1-librem5 -> dtbs/5.17.0-1-librem5/freescale/imx8mq-librem5-r4.dtb lrwxrwxrwx 1 root root 53 Sep 18 15:19 dtb-5.18.0-1-librem5 -> dtbs/5.18.0-1-librem5/freescale/imx8mq-librem5-r4.dtb lrwxrwxrwx 1 root root 52 Dec 4 16:36 dtb-6.0.0-1-librem5 -> dtbs/6.0.0-1-librem5/freescale/imx8mq-librem5-r4.dtb lrwxrwxrwx 1 root root 52 Jan 25 16:39 dtb-6.1.0-1-librem5 -> dtbs/6.1.0-1-librem5/freescale/imx8mq-librem5-r4.dtb drwxr-xr-x 9 root root 1.0K Jan 14 17:21 dtbs drwxr-xr-x 2 root root 1.0K Jul 13 2021 grub -rw-r--r-- 1 root root 63M Apr 25 2022 initrd.img-5.16.0-1-librem5 -rw-r--r-- 1 root root 63M Jun 1 2022 initrd.img-5.17.0-1-librem5 -rw-r--r-- 1 root root 63M Sep 18 15:19 initrd.img-5.18.0-1-librem5 -rw-r--r-- 1 root root 63M Dec 4 16:36 initrd.img-6.0.0-1-librem5 drwx------ 2 root root 12K Sep 11 2021 lost+found -rw-r--r-- 1 root root 4.8M Apr 13 2022 System.map-5.16.0-1-librem5 -rw-r--r-- 1 root root 4.8M May 24 2022 System.map-5.17.0-1-librem5 -rw-r--r-- 1 root root 4.8M Jul 14 2022 System.map-5.18.0-1-librem5 -rw-r--r-- 1 root root 4.9M Nov 15 16:16 System.map-6.0.0-1-librem5 -rw-r--r-- 1 root root 3.9M Jan 10 14:21 System.map-6.1.0-1-librem5 -rw-r--r-- 1 root root 24M Apr 13 2022 vmlinuz-5.16.0-1-librem5 -rw-r--r-- 1 root root 24M May 24 2022 vmlinuz-5.17.0-1-librem5 -rw-r--r-- 1 root root 24M Jul 14 2022 vmlinuz-5.18.0-1-librem5 -rw-r--r-- 1 root root 25M Nov 15 16:16 vmlinuz-6.0.0-1-librem5 -rw-r--r-- 1 root root 24M Jan 10 14:21 vmlinuz-6.1.0-1-librem5 ml@lib14:/media/ml/283a4739-85fc-44b7-8ee0-e0e4c328ab42$
It seems that the initrd for image 6.1.0-1 is missing, which would explain that my phone does not boot.
df -h shows me this:
ml@lib14:/media/ml/283a4739-85fc-44b7-8ee0-e0e4c328ab42$ df -h Filesystem Size Used Avail Use% Mounted on udev 16G 0 16G 0% /dev tmpfs 3.2G 2.7M 3.2G 1% /run /dev/nvme0n1p1 458G 183G 252G 43% / tmpfs 16G 572M 16G 4% /dev/shm tmpfs 5.0M 12K 5.0M 1% /run/lock encfs 458G 183G 252G 43% /home/ml/work encfs 458G 183G 252G 43% /home/ml/devel encfs 458G 183G 252G 43% /home/ml/personal encfs 458G 183G 252G 43% /home/ml/.ssh/priv firstname.lastname@example.org: 288G 18G 256G 7% /home/ml/mnt/a330r/ml email@example.com: 908G 42G 821G 5% /home/ml/mnt/i7r/ml ml@i7: 908G 42G 821G 5% /home/ml/mnt/i7l/ml ml@a330: 288G 18G 256G 7% /home/ml/mnt/a330l/ml tmpfs 3.2G 4.9M 3.2G 1% /run/user/1000 /dev/sdb1 449M 396M 30M 94% /media/ml/283a4739-85fc-44b7-8ee0-e0e4c328ab42 ml@lib14:/media/ml/283a4739-85fc-44b7-8ee0-e0e4c328ab42$ ls -alh
There is 30 MB left on the boot partition, and given that an initrd takes up 63 MB, this explains why the latest initrd was not installed.
So, to quote Marillion (Clutching at Straws, White Russian): “Where do we go from here?”
Can I manipulate some file to get it to boot 6.0.0-1, so that I can clean out old images to make room on the boot partition?
It might be best to contact support directly and they can walk you through the exact procedure. Otherwise you aren’t the first person to have this specific problem so maybe someone has listed the exact procedure in another topic.
I followed this one, linking to initrd.img and vmlinuz for 6.0.0 and it booted. Now I can clean out old images and update. Hurrah!
The package manager does not purge outdated kernel images, the initrds of which crop up in /boot. And it does not prevent trying to install a new image, failing to install the initrd, thus leaving the phone in an unbootable state. Remember to regularly purge old images! This can not be done from the PureOS Store, only from the commandline. (This may be an issue for ordinary lusers.)
I always run before
sudo apt full-upgrade and after it the check
df -kh /boot
which shows around 240 Mbytes.
so this issue is solved for you?
Yes. No problem after that. apt purged the old images, then full-ugraded, and back in business.
did you ever reflashed your librem 5 since you received it? And if you did, when was that, more or less?
No, never reflashed.