I tried running from Ubuntu stable on a live USB, it blew up with some exception about a timeout as soon as I ran the command.
Trying with Rhino Linux which says its more up to date than Ubuntu, as I searched the exception, and spotted something about Python Requests and a bug with an old version. Could be wild goose chase of course …
You can use Debian 12 ‘Bookworm’ instead, which is upstream of Ubuntu.
I manged to try on Bookworm. I now wonder if all these distros are too new with some Python package. But I’m guessing.
user@debian:~/librem5-flash-image$ ./scripts/librem5-flash-image --stable
2024-10-28 22:44:54 INFO Looking for librem5r4 luks byzantium image
2024-10-28 22:44:55 INFO Found disk image Build “stable” ‘Last stable librem5r4 build’ from Fri Jun 23 22:21:40 2023
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 462, in get_job_info
response = self.jenkins_open(requests.Request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 564, in jenkins_open
return self.jenkins_request(req, add_crumb, resolve_auth).text
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 580, in jenkins_request
self.maybe_add_crumb(req)
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 369, in maybe_add_crumb
response = self.jenkins_open(requests.Request(
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 564, in jenkins_open
return self.jenkins_request(req, add_crumb, resolve_auth).text
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 583, in jenkins_request
self._request(req))
^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 557, in _request
return self._session.send(r, **_settings)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/requests/sessions.py”, line 703, in send
r = adapter.send(request, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/requests/adapters.py”, line 664, in send
timeout = TimeoutSauce(connect=timeout, read=timeout)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/urllib3/util/timeout.py”, line 119, in init
self._connect = self._validate_timeout(connect, “connect”)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/urllib3/util/timeout.py”, line 156, in _validate_timeout
raise ValueError(
ValueError: Timeout value connect was <object object at 0x7f6b449784c0>, but it must be an int, float or None.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File “/home/user/librem5-flash-image/./scripts/librem5-flash-image”, line 538, in
sys.exit(main())
^^^^^^
File “/home/user/librem5-flash-image/./scripts/librem5-flash-image”, line 478, in main
uboot_ref = find_uboot(UBOOT_JOB_NAME.format(uboot_board))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/home/user/librem5-flash-image/./scripts/librem5-flash-image”, line 282, in find_uboot
info = server.get_job_info(jobname)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/jenkins/init.py”, line 475, in get_job_info
raise JenkinsException(
jenkins.JenkinsException: Could not parse JSON info for job[u-boot_builds/uboot_librem5_build]
Looks like Jenkins is broken again, but this time for uboot, so manually download it instead:
https://arm01.puri.sm/job/u-boot_builds/job/uboot_librem5_mainline_build/lastSuccessfulBuild/artifact/output/uboot-librem5/u-boot-librem5.imx
Since the steps are manual now, download the Evergreen Byzantium LUKS image as well:
https://storage.puri.sm/librem5/images/byzantium/2024.04/librem5r4/luks/artifact/librem5r4.img.xz
Extract it to ~/librem5-flash-image, move u-boot-librem5.imx to that directory, then execute this command within the directory instead:
./scripts/librem5-flash-image --stable --skip-download --dir ./
Thanks for the help everyone. Still struggling though sadly. What a faff.
Post there, somebody seems to be saying they had the same issue, and worked around it somehow or other. Need to read that lot and try and make sense of it.
That post specifically refers to missing Python dependencies, but if you already used the sudo apt build-dep . command in the ~/librem5-flash-image directory, then you do not need to read it.
Yeah I did use that command, so okay, maybe its just because the build is broken then. Not sure why my manually copying the files in didn’t fix it though.
Sigh.
There needs to be these two files within the ~/librem5-flash-image directory for the last command to work:
librem5r4.imgu-boot-librem5.imxIf you want to share more verbose, add the --debug argument to the command.
It may be too late now but have you ever successfully flashed your phone in the past?
I chose to keep the disk image and other needed files on my host computer so that I can at least reflash back to that exact state, regardless of whether I can download the latest disk image (or for that matter restore a backup image).
If you have all the right files already downloaded and processed and sitting on your host computer then you can reflash just by cd to the correct directory and then sudo uuu flash_librem5r4.lst but that is definitely going to be trickier if you are trying to do this from a Live Boot environment.
Thanks mate, good thinking, bad sadly no, the phone has happily run and never needed it. Also as above, you can’t run this “uuu” thing on Fedora or seems.
That’s why you would be doing it from a Live Boot environment. Or, alternatively, grab a flash drive and actually install Ubuntu, or other Debian-family distro, on the flash drive and then use that to boot from when you need to do host computer management tasks on your phone (like backup, restore or reflash). (In that scenario, you might want e.g. a 32 GB flash drive, to allow enough space for Ubuntu slash whatever itself, plus the unexpanded disk image, plus the expanded disk image, plus margin.)