Librem 5 flashing process fail (LED turn green

Hardware Librem 5
29

Thank you for the fast response! :smiley:

I try your advice but still have the same problem.

To make the situation clear why we flashing the phone and maybe give you a possible indicator of the problem we have here the the story with the phone:
After receiving the brand new phone he charge the phone than turn it on, it works without any problems.
The next day the battery was empty but the phone was in standby mode the hole night.
After he recharged the battery the phone did not start anymore to be precise led lights but the screen stays black, and it was not only the backlight of the display that turnt not on it is the full screen because i try to see something on the screen because there were a similar problem what i found in the internet but it was not the case with this phone.

What i also realised is when i plug in the phone for flashing into the laptop the screen on the top side gets warm, only warm not hot. The battery on the other hand stays cold much longer.
Maybe the situation i describe and your experience with the phone can tell you something about the problem.

Thank you in advance and sorry for my not so perfekt english. :sweat_smile:

30

As I recall at this moment: There is NO NEED for this (disconnect => connect again action).

Therefore (explaining this up to my understanding, rewriting what already correctly written): “Remove battery” together with “Hold volume-up” means that after next step: plug into your Librem 5 USB-C connector of your USB-C to USB-A cable (that is already connected to your computer/laptop) blinking red LED light will turn instantly into steady red, right after you released volume-up button (will start to charge Librem 5 with around 0.45A in this flashing mode, which logically recommends having pre-charged Librem 5 battery to at least 70%, as this battery will start to actually discharge, at least slightly … during here related process).

As @dos kindly recommended please use preferably (shorter USB-C to USB-A cable):

What is here important is that after battery inserted (red LED light steady) please do not move here mentioned Librem 5 phone around any more (not even 1 mm left or right, up or down, as perhaps previous flashing process interrupted this way already, leave phone steadily connected few minutes even after 100% of … as shown on your host screen).

After above (no need to disconnect this Librem 5 any more, please, this will be confirmed/observed from your side as correct) you will be ready to proceed (if selected USB-C to USB-A cable of adequate quality):

$ apt list uuu
Listing... Done
uuu/stable,now 1.4.193-1+b1 amd64 [installed,automatic]

$ lsusb | grep 8M

It is your turn now (good luck to both of you, quality USB2.0 cable will serve this purpose as well).

32

@dos

Hi! I bought new 50cm USB 2.0 USB-A to USB-C cable and still same result.
Trying to get some info from purism support, had written them 3 e-mails since friday but still no anwer :confused:

I am now already tired of this phone and would like to send it somewhere to get it fixed

33

Please use OEM USB-C2USB-A cable and GNU OS to recovery the L5 otherwise u will stumble.

34

Status quo:

I had now some very expirienced help from @Quarnero who tried to flash my phone as well with the following result (Thank you very much again):

apt list librem5-flash-image
Listing… Done
librem5-flash-image/now 0.0.4-1 all [installed,local]
/Documents/Librem5_Florian/purism-librem5# uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips – lib1.4.193

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
2:1 MX8MQ SDP: 0x1FC9 0x012B 0x0001
/Documents/Librem5_Florian/purism-librem5# librem5-flash-image --board librem5r4
2023-07-22 09:17:03 INFO Looking for librem5r4 plain byzantium image
2023-07-22 09:17:06 INFO Found disk image Build 14748 ‘plain librem5r4 byzantium image’ from Sat Jul 22 01:30:59 2023
2023-07-22 09:17:07 INFO Found uboot Build 85 from Thu Aug 25 15:22:41 2022
2023-07-22 09:17:07 INFO Downloading to ./tmp_librem5-flash-image_he_tyk5h
2023-07-22 09:17:07 INFO Downloading image from https://arm01.puri.sm/job/Images/job/Image%20Build/14748/artifact/librem5r4.img.xz
2023-07-22 09:20:44 INFO Calculating sha256sum of ./tmp_librem5-flash-image_he_tyk5h/librem5r4.img
2023-07-22 09:21:25 INFO Downloading uboot from https://arm01.puri.sm/job/u-boot_builds/job/uboot_librem5_build/85/artifact/output/uboot-librem5/u-boot-librem5.imx
uuu (Universal Update Utility) for nxp imx chips – lib1.4.193

Success 0 Failure 0

2023-07-22 09:26:33 ERROR CTRL-C pressed.============] SDP: boot -f u-boot-librem5.imx
2023-07-22 09:26:33 INFO Cleaning up.
@Flo127, around 11h00 I’ve sent your Librem 5 back to you:
https://www.dhl.de/de/privatkunden/dhl-sendungsverfolgung.html?piececode=CR863053908DE

Now, this Jumpdrive outputs (especially third one below: ‘HID(W):LIBUSB_ERROR_TIMEOUT’, that works while used Jumpdrive own Linux Kernel) are important (I think) to be sent to Purism Support Team:

/Documents/Librem5_Florian/purism-librem5# ./boot-purism-librem5.sh
uuu (Universal Update Utility) for nxp imx chips – lib1.4.193

Success 0 Failure 0

2:1 1/ 1 [=================100%=================] SDP: boot -f u-boot-librem5.bin
/Documents/Librem5_Florian/purism-librem5# uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips – lib1.4.193

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
2:1 MX8MQ SDP: 0x1FC9 0x012B 0x0001
/Documents/Librem5_Florian/purism-librem5# ./boot-purism-librem5.sh
uuu (Universal Update Utility) for nxp imx chips – lib1.4.193

Success 0 Failure 1

2:1 1/ 1 [HID(W):LIBUSB_ERROR_TIMEOUT ] SDP: boot -f u-boot-librem5.bin
I still think it is about USB communication issue not communicating toward eMMC yet this still does not mean that eMMC is “dead”, I still believe it is about flash procedure (software that I’m not familiar with) approach that is missing this, sort of initial, communication toward this Librem 5 eMMC.

P.S. I gave up on my thought to boot this Librem 5 from microSD card as this would not help anyone (and might be interpreted as misuse of this phone).

35

If you are trying to reflash the Librem 5 with new images, use these instructions. Next time, do not press CTRL + C to cancel the flashing process.

36

@FranklyFlawless

Thanks for advise…it’s not working due to the phone…Already 3 different people tried.

It’s now the turn from purism support to solve this problem! It was a new phone and it should work out of the box. I have alreaedy spent too much time to get it working and have already 3 batteries for a not working phone because i always got told it’s problem with battery.

37

Well I regularly reflash my Librem 5 USA so I already know the procedure very well, but if you do not want my help, go ahead and contact Purism support then.

Hopefully you do not get a fourth battery this time.

38

I really appreciate your your intentions and would try it 6 months ago.

If you are sure to get it running I have a brand new Librem5 with 3 batteries for sale :stuck_out_tongue_winking_eye:!

I am already tired of it and have lot of other things to do where I get actually some results.

39

I am certain I can solve it, but I have no interest in purchasing a Librem 5 when I already have a Librem 5 USA. I simply do not need two.

I just like cleaning/wiping devices, because I always feel inspired with a clean slate.

40

It is not about getting “clan state”, it is about not getting LIBUSB_ERROR_TIMEOUT error.

41

Hi,

I believe I am having similar problems. I attempted to upgrade via the system upgrade, but it failed (froze and never unfroze).

I rebooted, but there was no response except green LED and blank screen.

I have tried with 3 different computers and about 6 different high-quality USB cables in all configurations, but all I ever get is the following:

./scripts/librem5-flash-image --dir .
2023-07-27 16:52:13 INFO Looking for librem5r4 luks byzantium image
2023-07-27 16:52:14 INFO Found disk image Build 14786 ‘luks librem5r4 byzantium image’ from Wed Jul 26 22:54:25 2023
2023-07-27 16:52:14 INFO Found uboot Build 85 from Thu Aug 25 09:22:41 2022
2023-07-27 16:52:14 INFO Downloading to .
2023-07-27 16:52:14 INFO Calculating sha256sum of ./librem5r4.img
2023-07-27 16:52:30 INFO Image already up to date - no download needed.
2023-07-27 16:52:30 INFO Downloading uboot from https://arm01.puri.sm/job/u-boot_builds/job/uboot_librem5_build/85/artifact/output/uboot-librem5/u-boot-librem5.imx

        Enter the flashing mode by holding volume-up button while turning the phone on.

        If it's not detected, follow these steps:
        - Ensure that the phone is powered off
        - Turn all Hardware-Kill-Switches off
        - Unplug the USB cable if connected
        - Remove battery
        - Hold volume-up button
        - Insert the USB-C cable (red light blinks, no green light)
        - Reinsert the battery (red and green lights constantly on, the script will continue)
        - Release volume-up button

Searching…
uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.21-0-g1f42172

Success 0 Failure 0

1:2 1/ 1 [=================100%=================] SDP: boot -f u-boot-librem5.imx

After this nothing happens and the light turns solid green. Then both red and green are on.

And that’s it. The script does not continue.

Have tried this with Debian, PureOS, Arch linux, and Debian on Arm64. Same outcome.

uuu -lsusb give:

uuu (Universal Update Utility) for nxp imx chips – libuuu_1.5.21-0-g1f42172

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:2 MX8MQ SDP: 0x1FC9 0x012B 0x0001

Cannot load using jumpdrive.

Anyone have a suggestion on what to try next? I have about 15 years of experience with flashing ROMs and Linux, but this one has me stumped.

2 Likes
42

Looks like Purism had to restore to an earlier backup snapshot of their forums, so if your Discourse settings are the default configuration, use my last reply sent by Discourse to your email for the reflashing procedure. Otherwise, I will need to relist all of the steps again.

43

Yeah, WTD is happening. I feel as if a number of my posts have disappeared. Has Purism actually posted any comment to the effect of the above?

44

No, but I do not follow any of their social media platforms and/or accounts. The most I did was read blog posts from @Kyle_Rankin, but that has stopped now too.

46

Sorry for bumping this topic but searching the forum has not revealed a solution to the flash and jumpdrive boot failures (Led turns solid green + hang) on my L5USA.

I have successfully flashed my Oct '21 L5USA about a dozen times and have used jumpdrive probably a dozen times as well - no problems.

A few weeks ago the L5 started randomly hanging. I decided to roll back to a previous image suspecting the random hangs might be related to an update. I was able to boot and use the system after the flash a few times but another random hang occurred and that was it. Since then the phone cannot be booted or placed in flash or jumpdrive mode.

  • Checked battery voltages - AOK, monitored charging via inline USB VOM - AOK.
  • Tried several USB-A/USB-C cables. My Dell, Thinkpad and RPi 400 (all Debian) respond with same failure.
  • Flash & jumpdrive software had been working perfectly up to this point.

UUU properly recognizes the NXP chip. For both the flash-image and jumpdrive scripts, the phone is placed in flash mode i.e. turn off switches, remove battery, insert USB-C, insert battery - constant red LED, invoke script.
Below are terminal sessions for the flash and jumpdrive boot attempts:

============
Flash Image Attempt

============
$ sudo ./scripts/librem5-flash-image --skip-cleanup --skip-download --dir ./Images --stable
2024-04-07 19:54:10,841 INFO Looking for librem5r4 luks byzantium image
2024-04-07 19:54:11,540 INFO Found disk image Build “stable” ‘Last stable librem5r4 build’ from Fri Jun 23 22:21:40 2023
2024-04-07 19:54:13,142 INFO Found uboot Build 85 from Thu Aug 25 09:22:41 2022
2024-04-07 19:54:13,142 INFO Downloading to ./Images
2024-04-07 19:54:13,142 INFO Skipping download and using local image ‘./Images/librem5r4.img’

        Enter the flashing mode by holding volume-up button while turning the phone on.

        If it's not detected, follow these steps:
        - Ensure that the phone is powered off
        - Turn all Hardware-Kill-Switches off
        - Unplug the USB cable if connected
        - Remove battery
        - Hold volume-up button
        - Insert the USB-C cable (red light blinks, no green light)
        - Reinsert the battery (red and green lights constantly on, the script will continue)
        - Release volume-up button

Searching…
uuu (Universal Update Utility) for nxp imx chips – lib1.4.77

Build in config:
Pctl Chip Vid Pid BcdVersion
==================================================
SDPS: MX8QXP 0x1fc9 0x012f [0x0002…0xffff]
SDPS: MX8QM 0x1fc9 0x0129 [0x0002…0xffff]
SDPS: MX8DXL 0x1fc9 0x0147
SDPS: MX28 0x15a2 0x004f
SDPS: MX815 0x1fc9 0x013e
SDPS: MX865 0x1fc9 0x0146
SDPS: MX8ULP 0x1fc9 0x014a
SDPS: MX8ULP 0x1fc9 0x014b
SDP: MX7D 0x15a2 0x0076
SDP: MX6Q 0x15a2 0x0054
SDP: MX6D 0x15a2 0x0061
SDP: MX6SL 0x15a2 0x0063
SDP: MX6SX 0x15a2 0x0071
SDP: MX6UL 0x15a2 0x007d
SDP: MX6ULL 0x15a2 0x0080
SDP: MX6SLL 0x1fc9 0x0128
SDP: MX7ULP 0x1fc9 0x0126
SDP: MXRT106X 0x1fc9 0x0135
SDP: MX8MM 0x1fc9 0x0134
SDP: MX8MQ 0x1fc9 0x012b
SDPU: SPL 0x0525 0xb4a4 [0x0000…0x04ff]
SDPV: SPL1 0x0525 0xb4a4 [0x0500…0x9998]
SDPU: SPL 0x0525 0xb4a4 [0x9999…0x9999]
SDPU: SPL 0x3016 0x1001 [0x0000…0x04ff]
SDPV: SPL1 0x3016 0x1001 [0x0500…0x9998]
FBK: 0x066f 0x9afe
FBK: 0x066f 0x9bff
FB: 0x0525 0xa4a5
FB: 0x18d1 0x0d02
FB: 0x3016 0x0001
Wait for Known USB Device Appear…

Start Cmd:CFG: SDP: -chip MX8MQ -compatible MX8MQ -vid 0x316d -pid 0x4c05
Okay (0s)
New USB Device Attached at 1:12
1:12>Start Cmd:SDP: boot -f u-boot-librem5.imx
6400%1:12>Okay (3.059s)

LED turns solid green
After 35 secs LED turns yellow (NO alternating green-red etc)

Nothing else happens L5 frozen

============
jumpdrive Attempt

============

+++ uuu finds the NXP chip +++

spacex:$ uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips – lib1.4.77

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:12 MX8MQ SDP: 0x1FC9 0x012B 0x0001

+++ invoke jumpdrive boot script+++

spacex:$ ./boot-purism-librem5.sh
uuu (Universal Update Utility) for nxp imx chips – lib1.4.77

Success 0 Failure 0

1:12 1/ 1 [=================100%=================] SDP: boot -f u-boot-librem5.bin

+++ jumpdrive boot stops - LED solid green, ~35 secs later LED solid yellow +++

+++ Script terminated using ctrl-C +++

+++ uuu still detects NXP chip… +++

spacex:$ uuu -lsusb
uuu (Universal Update Utility) for nxp imx chips – lib1.4.77

Connected Known USB Devices
Path Chip Pro Vid Pid BcdVersion
==================================================
1:12 MX8MQ SDP: 0x1FC9 0x012B 0x0001

+++ however NXP chip no longer responds to boot script +++

1 Like
47

Install the udev rules so you do not require sudo.

sudo ./scripts/librem5-flash-image --udev

Then use commands without it and display their output.

48

Udev has always been installed on my three flash script install hosts.
The ‘librem5-flash-image’ utility has always worked with OR without sudo.

+++ librem-flash-image without sudo +++

Note 1: test result is the same as when using sudo

Note 2: The repository is currently inaccessible except for a single librem5r2.img file so I temporarily renamed the r4 image in my flash-image ‘Images’ folder to 'librem5r2.img to ‘trick’ the script to proceed to the boot phase:

fraila@spacex:~/librem5-flash-image $ ./scripts/librem5-flash-image --skip-cleanup --skip-download --board=librem5r2 --dir ./Images
2024-04-08 12:50:16,393 INFO Looking for librem5r2 luks byzantium image
2024-04-08 12:50:28,609 INFO Found disk image Build 16667 ‘luks librem5r2 byzantium image’ from Tue Apr 2 00:17:23 2024
2024-04-08 12:50:30,294 INFO Found uboot Build 85 from Thu Aug 25 09:22:41 2022
2024-04-08 12:50:30,295 INFO Downloading to ./Images
2024-04-08 12:50:30,295 INFO Skipping download and using local image ‘./Images/librem5r2.img’
uuu (Universal Update Utility) for nxp imx chips – lib1.4.77

Build in config:
Pctl Chip Vid Pid BcdVersion
==================================================
SDPS: MX8QXP 0x1fc9 0x012f [0x0002…0xffff]
SDPS: MX8QM 0x1fc9 0x0129 [0x0002…0xffff]
SDPS: MX8DXL 0x1fc9 0x0147
SDPS: MX28 0x15a2 0x004f
SDPS: MX815 0x1fc9 0x013e
SDPS: MX865 0x1fc9 0x0146
SDPS: MX8ULP 0x1fc9 0x014a
SDPS: MX8ULP 0x1fc9 0x014b
SDP: MX7D 0x15a2 0x0076
SDP: MX6Q 0x15a2 0x0054
SDP: MX6D 0x15a2 0x0061
SDP: MX6SL 0x15a2 0x0063
SDP: MX6SX 0x15a2 0x0071
SDP: MX6UL 0x15a2 0x007d
SDP: MX6ULL 0x15a2 0x0080
SDP: MX6SLL 0x1fc9 0x0128
SDP: MX7ULP 0x1fc9 0x0126
SDP: MXRT106X 0x1fc9 0x0135
SDP: MX8MM 0x1fc9 0x0134
SDP: MX8MQ 0x1fc9 0x012b
SDPU: SPL 0x0525 0xb4a4 [0x0000…0x04ff]
SDPV: SPL1 0x0525 0xb4a4 [0x0500…0x9998]
SDPU: SPL 0x0525 0xb4a4 [0x9999…0x9999]
SDPU: SPL 0x3016 0x1001 [0x0000…0x04ff]
SDPV: SPL1 0x3016 0x1001 [0x0500…0x9998]
FBK: 0x066f 0x9afe
FBK: 0x066f 0x9bff
FB: 0x0525 0xa4a5
FB: 0x18d1 0x0d02
FB: 0x3016 0x0001
Wait for Known USB Device Appear…
New USB Device Attached at 1:12
1:12>Start Cmd:SDP: boot -f u-boot-librem5.imx
6400%1:12>Okay (3.06s)

LED turns solid green
After 35 secs LED turns yellow

Nothing else happens L5 frozen - same result as script invoked with sudo.

FYI

1 Like
49

Okay, contact Purism support.

50

It’s a continuing challenge to convince folks that my flash and jumpdrive problems have nothing to do with the librem5-flash-image and jumpdrive scripts or running them - both had been working perfectly for more than two years.

For further enlightenment here is a look at where the problem seems to be.
The image shows the jumpdrive script is active, the phone is in flash mode and uuu attempts to load file u-boot-librem5.bin.
FYI

jumpdrive
jumpdrive781×783 49.7 KB

3 Likes