Hi everyone,
I’ve successfully flashed my librem 5 before, but this time I’m getting a connection error.
Command used: sudo ./scripts/librem5-flash-image --dir ./img --skip-cleanup --variant plain --debug
Output, relevant to error:
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:5
1:5>Start Cmd:SDP: boot -f u-boot-librem5.imx
100%1:5>Okay (0.888s)
New USB Device Attached at 1:5
1:5>Start Cmd:SDPV: delay 1000
1:5>Okay (1s)
1:5>Start Cmd:SDPV: write -f u-boot-librem5.imx -skipspl
100%1:5>Okay (0.77s)
1:5>Start Cmd:SDPV: jump
100%1:5>Okay (0.156s)
New USB Device Attached at 1:5
1:5>Start Cmd:FB: ucmd setenv fastboot_dev mmc
1:5>Okay (0.15s)
1:5>Start Cmd:FB: ucmd setenv mmcdev 0
1:5>Okay (0.009s)
1:5>Start Cmd:FB: flash -raw2sparse all librem5r4.img
0x400000000x2001:5>Fail Bulk(W):LIBUSB_ERROR_TIMEOUT(34.6s)
Flashing complete.
Let me know what you think. I’m also reaching out to support email for Purism as well, and will update any finding here for the benefit of the community!
Thanks, and have a great day people!
Try removing all USB connections, then use a different USB port.
Sorry, no change in behavior. Also, the following is relevant and established:
>Start Cmd:CFG: SDP: -chip MX8MQ -compatible MX8MQ -vid 0x316d -pid 0x4c05
>Okay (0s)
I do see the device and identify what type of device it is. So I’m inclined to think that its not a USB port issue, but I’m open to any and all suggestions. Thank you!
1 Like
Anecdotally, using a USB 2.0 port may be more reliable.
The starting point for troubleshooting is always: lsusb
Do you see
Bus 999 Device 999: ID 1fc9:012b NXP Semiconductors i.MX 8M Dual/8M QuadLite/8M Quad Serial Downloader
where the bus and device number won’t match? It’s the part after the colon that is important.
Other things to contemplate:
- Did you verify that the download succeeded? (multi-gigabyte?)
- Are you using the Purism original USB-C cable? (recommended)
- Have you tried all available cable orientations? (4)
- What distro and version is your host computer running? (Want to make sure you have a current version of
uuu
)
- Did you do a recent
git clone
so that you have an up to date flash script and associated files?
- Dare I ask whether you have an Evergreen phone or a phone from an earlier batch? (I ask because Discourse says we haven’t seen you for “2 years”.)
I assume that you are intentionally flashing the “plain” variant, rather than the “luks” variant.
1 Like
@irvinewade Thanks! That was the solution. Specifically, it was the cable I was using. I’m now marking that cable as the one that works, as it no longer errors out doing the flash stage of the script. BTW, I haven’t been on this forum so much, as things with my other Purism device (Librem 14) work excellent with Qubes OS 4.2 The phone was shelved, due to issues with battery life and I’m now testing again.
Thanks so much, we can mark this as closed and a good example of things to check when troubleshooting. I REALLY appreciate the help my friend!
2 Likes
Technically speaking, you are supposed to mark a post as “Solution”. Given that I made so many different suggestions, it may be best to mark your own post as “Solution” (since it is the one that specifically identifies what the solution was).
3 Likes