I’ve pulled my Evergreen back out of the box after a little while and wanted to reflash with the latest firmware to start from scratch as I was never able to get my phone connected to wifi previously.
I found this blog post:
but when inspecting the linked repo, the relevant script has been moved out.
Sidenote: It sounds like a nice approach to have it independent. Would be great to have the deb package available in the Purism apt repository too. I’m assuming this is the plan and it just hasn’t gotten to the top of the priority pile yet.
Got all my fingers and toes crossed that I’m following the right process atm, but just flagging the documentation mismatches. It’s the classic documentation dilemma - outdated almost the moment its published!
I fished out the original librem cable too. No change.
The LED does the same pattern if I plug in the cord without holding volume up.
If holding volume up the phone also does a short vibration every ~second.
It does this if I hold volume up then plug it in, or if I plug it in and then hold volume up. Same behaviour.
The reflashing script is still sitting waiting to detect a device.
For context I’m on a Librem 15v2 running PureOS 10.
uuu was installed using apt without error, however I haven’t yet tried re-inserting the battery in the phone because the LED is not displaying the expected behaviour and I’d rather not brick it.
@amosbatto do you remember if the LED on yours flashed any other colours? Or just the red as is suggested in the docs?
Another suggestion is: Forget about trying to flash (forget about uuu) and just plug your phone into your desktop/laptop via USB and confirm that the phone shows up at all. (If you don’t do the magic stuff on the phone but you do connect it via USB then it should at minimum show up on the host as a network connection and will probably also show up on the host as a small disk.)
Once you are confident about the USB port at each end and the USB cable and the USB cable orientation … you would retry but this time doing the magic stuff to put the phone into boot mode.
I’ve successfully put my phone into boot mode but I don’t have a USB-C port on my host - so I am using a USB-C to USB-A adapter and plugging in to USB-A port on the host (or alternatively a USB-C to USB-A cable). Which of the three are you attempting to do?
Regarding cable orientation, the “beauty” of USB-C is that there are 4 possible orientations if you use a USB-C cable (but only 2 orientations if you use a USB-C to USB-A cable).
I believe that lsusb output on the host should reveal the difference between a Librem 5 that is in boot mode and one that is not. If it’s not getting into boot mode then I don’t think you can do much damage either way i.e. can’t brick but also can’t reflash.
I’m now using the USB-C to USB-C cable from the Librem 5 connected to the single USB-C slot on the original Librem 15. lsusb shows it as:
Bus 001 Device 101: ID 1d6b:0104 Linux Foundation Multifunction Composite Gadget
and you’re right it’s showing as a network connection.
After doing this, I gave the reflash another try and the device went into boot mode! Got the flashing red so dropped the battery in and it flashed a few colours then went green (not the red described in the docs). Still the script was proceeding and it’s come up wiped and with all the new applications so
, and therefore is