Hi @dos
Thanks for explaining.
I guess you missed my other question:
Can you help me with this?
Hi @dos
Thanks for explaining.
I guess you missed my other question:
Can you help me with this?
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.
Extract the downloaded file (artifacts.zip
), then extract the resulting purism-librem5.tar.xz
, then follow these instructions:
Thank You, got it.
It never crossed my mind to check inside that zip file.
Hi all.
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.
I’m stuck.
Any ideas?
Did you execute the boot-purism-librem5.sh
script using the host computer?
Yep and it reported back with success = 1
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, I’m going to follow the steps from Lliure.
I will report back and thanx.
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.
That is unusual, and there are no similar issues. Are you using sudo dmesg -w
for your command?
Indeed I do. Typo corrected in my message.
EDIT:
I am using jumpdrive on my brand new L5.
Okay, disconnect and reconnect the cable to the same USB port on the host, then if it does not work, try the other ones.
Done that an I have now a diff. situation.
demsg -w shows now less errors (now complaining about no support for DPO or FUA).
Also telnet does work now.
But eMMC is still not available as storage.
Is LUKS preventing this?
Perhaps important info:
I simply switched over the USB cable to another port.
Jumpdrive kept running and did not complain about the interruption.
Okay, then from here, you should be able to use step 16 and up of @Lliure’s guide to access the encrypted partition.
Some problems dissapear while waiting .
I was looking on the host for some mount utilities and tadaa a popup appeared asking for my Luks key.
Entered it and “voila”, now I have access to eMMC.
Thank you for helping and solving my issue(s).
No. Jumpdrive is just exporting a block device (or two block devices, if you have a uSD card inserted in your phone). There need be no file system at all. It’s up to the host computer to interpret the data. (So, yes, the exact commands to do on the host computer will depend on whether LUKS is in use on the eMMC drive. Regardless though the /boot
partition is not encrypted and should work even if LUKS is giving you grief.)
Thanks for explaining.
As you have seen, I managed to overcome my issues.
Once you know how to do it, it’s a piece of cake to backup and restore an image.
My second L5 is now a complete identical copy of my orriginal one.
As I wanted to have a ‘factory default image’ I made an image from the third (new) L5 before going through the very first start up procedure of the L5.
Restoring this ‘default’ image is less time consuming measured against flashing the L5
One worrying aspect I had was about the old L5 having a Redpine module while the new L5’s have a Sparklan module.
But this is a non-issue.
The OS picks this up without a hassle.
I do have another question about using Jumpdrive, but I will create a new thread for it.