Thank you guys.
I always thought that when a HKS is set to off, this means that the device was enabled (is working or switched on).
I was not shure if my reasening was correct.
Now I know
The intention is to keep the power consumption as low as possible in order to maximize chances of successful boot even with deeply depleted battery and under-powered USB source - so youâre supposed to put all hardware kill switches in off position (towards the bottom of the device) to disable the peripherals.
Of course itâs not strictly necessary. Usually everything will work just fine even if you donât do that. I never do
Or, if the expression âkill switchâ had never been used, and it was just a âswitchâ, then readers would not be confused by being told to switch the peripherals âoffâ before booting.
Iâll see about getting the description of that step clarified.
Since @dos is not responding for whatever reasons, I ask my question to the community.
There is an updated/patched version of JumpDrive (created by @dos) and can be found here.
I do not know what to do when following that link.
Where is the modified JumpDrive?
I only see a download for âartifactsâ, but that is not JumpDrive.
Any help is appreciated.
Back again and I need a bit more help with Jumdrive.
Iâm confused where to install the Jumdrive software.
Should it be installed on the L5 or on the laptop?
So far Iâve tried these steps.
I have installed (unzipped) the jumpdrive software in a folder on my L5.
Tried to run the script but it complained that it needed uuu (wich was not installed).
So I installed uuu on my L5 and started the script (boot-purism-librem5.sh) again.
All is done in Terminal.
Now it runs.
A text line appears: Success 0 Failure 0 Wait for...
At this stage I power down my L5,
Remove the battery,
Press volume up, insert the USB cable (blinking red led appears)
Insert the battery (red led constant on)
Release the volume up button.
My L5 remains dark, nothing to be seen on screen.
Checking my laptop (running Live USB with PureOS latest iso), but no new USB device(s) to be seen.
What am I doing wrong?
Confirm you are in flashing mode by turning on the Librem 5 while holding the volume up button. You may need udev rules, permissions in the plugdev group, and a restart of your host computer to have uuu detect the Librem 5:
OK, got Flashingmode and Jumpdrive running.
At the host Jumpdrive reports Success 1 Failure 0
At the L5 I have the screen as expected.
However, there is no luks pw prompt (where should it appear? Host or L5)
Also, the L5 is not visible at the host.
lsusb does not show the L5
disks does not show the L5 eMMC
I switched USB cables, despite they have been working fine.
What should happen after flashing Jumpdrive is that your Librem 5 is detected as a USB device on the host. I suggest retrying the flashing procedure and seeing if anything changes. You can also use this more thorough guide for further debugging/troubleshooting steps:
OK, did read bits and pieces, check some requirements and all seems to be available.
Booted again and entering succesfull into flasmode with Jumdrive.
But still no eMMC partition available.
dmesg -w shows
usb-storage 3-4:1.2: USB Mass Storage device detected
scsi hosts5: usb-storage 3-4:1.2
usb3-4: USB disconnect, device number xx
usb3-4: new SuperSpeed Gen 1 USB device yy using xhci_hcd
usb3-4: new USB device found, iVendor=1209, iProduct=4201, bcdDevice= 5.18
usb3-4: new USB device strings: Mfr=1, Product=2, Serialnumber=3
usb3-4: Product: Librem 5
usb3-4: Manufacturer: Purism
usb3-4: SerialNumber: Jumpdrive
usb3-4: Set SEL for device-initiated U2 failed.
usb3-4: Disable of device-initiated U1 failed.
usb3-4: Disable of device-initiated U2 failed.
rndis_host 3-4:1.0: RNDIS init failed, -19
usb3-4: Set SEL for device-initiated U1 failed.
usb3-4: Set SEL for device-initiated U2 failed.
rndis_wlan 3-4:1.0: RNDIS init failed, -19
usb3-4: Set SEL for device-initiated U1 failed.
usb3-4: Set SEL for device-initiated U2 failed.
These messages are looping all the time, where xx is an incrementing number and yy is xx+1.