My problem is very similar to this thread https://forum.kde.org/viewtopic.php?f=297&t=139325&sid=01283d076c7a06400f926cdb4c1a9e7c, and I've used some solutions proposed. Still I'm having problems. What did I do? I followed the installation instructions from https://www.plasma-mobile.org/nexus-5/. Got this error twice

Code: Select all

error: no devices/emulators found

As I had Android 8.1 on my device, I used this thread https://forum.kde.org/viewtopic.php?f=297&t=139325&start=15&sid=01283d076c7a06400f926cdb4c1a9e7c
to install Android 6.0.1 using instructions from https://forum.xda-developers.com/nexus-5x/general/guides-how-to-guides-beginners-t3206930 and Android runs fine. Then I start into bootloader:

Code: Select all

adb reboot bootloader

unlock it:

Code: Select all

fastboot oem unlock

or (doesn't matter which one I choose, the result is the same):

Code: Select all

fastboot flashing unlock

Then

Code: Select all

fastboot format cache
fastboot format userdata


Then I go to the directory where pm-flashtool is installed and:

Code: Select all

sudo ./pm-flash

output:

Code: Select all

+ CACHEDIR=cache
+ echo 'Waiting for device to be in the fastboot mode'
Waiting for device to be in the fastboot mode
+ fastboot getvar product
product: bullhead
finished. total time: 0.008s
++ fastboot getvar product
++ head -1
++ awk '-F: ' '{print $2}'
+ DEVICE_NAME=bullhead
+ confirm 'Connected device is bullhead, is that correct? [y/N]'
+ read -r -p 'Connected device is bullhead, is that correct? [y/N] ' response
Connected device is bullhead, is that correct? [y/N] y
+ case $response in
+ true
+ PLATFORM=neon
+ echo 'Continuing ...'
Continuing ...
+ getopts cp: opt
+ case $opt in
+ PLATFORM=neon
+ getopts cp: opt
+ '[' -z '' ']'
+ download bullhead neon
+ '[' 2 -eq 0 ']'
+ mkdir -p cache/
+ pushd cache/
~/pm-flashtool/cache ~/pm-flashtool
+ echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
+ '[' neon == neon ']'
++ curl http://images.plasma-mobile.org/rootfs_stamp
+ ROOTFS_VERSION=20180209-155413
+ wget -c http://images.plasma-mobile.org/rootfs/pm-rootfs-20180209-155413.tar.gz -P rootfs
--2018-03-05 22:00:54--  http://images.plasma-mobile.org/rootfs/pm-rootfs-20180209-155413.tar.gz
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

    The file is already fully retrieved; nothing to do.

+ ln -sf rootfs/pm-rootfs-20180209-155413.tar.gz pm-rootfs-latest.tar.gz
+ '[' neon == arch ']'
+ '[' neon == edge ']'
+ echo '[done]'
[done]
+ echo 'Downloading the latest boot, recovery, and system images  ... '
Downloading the latest boot, recovery, and system images  ...
++ curl http://images.plasma-mobile.org/halium/bullhead/halium_stamp
+ HALIUM_VERSION=20180209-134208
+ wget -c http://images.plasma-mobile.org/halium/bullhead/recovery.img -P bullhead
--2018-03-05 22:00:54--  http://images.plasma-mobile.org/halium/bullhead/recovery.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

    The file is already fully retrieved; nothing to do.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20180209-134208/system.img -P bullhead/20180209-134208
--2018-03-05 22:00:54--  http://images.plasma-mobile.org/halium/bullhead/20180209-134208/system.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

    The file is already fully retrieved; nothing to do.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20180209-134208/boot.img -P bullhead/20180209-134208
--2018-03-05 22:00:54--  http://images.plasma-mobile.org/halium/bullhead/20180209-134208/boot.img
Resolving images.plasma-mobile.org (images.plasma-mobile.org)... 207.154.251.179
Connecting to images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80... connected.
HTTP request sent, awaiting response... 416 Requested Range Not Satisfiable

    The file is already fully retrieved; nothing to do.

+ rm -f bullhead/latest
+ ln -sf 20180209-134208 bullhead/latest
+ echo '[done]'
[done]
+ popd
~/pm-flashtool
+ flash-phone bullhead
+ '[' 1 -eq 0 ']'
+ echo -n 'Flashing recovery image ... '
Flashing recovery image ... + fastboot flash recovery cache/bullhead/recovery.img
+ echo -n '[done]'
[done]+ fastboot boot cache/bullhead/recovery.img
downloading 'boot.img'...
OKAY [  0.861s]
booting...
OKAY [  0.540s]
finished. total time: 1.402s
+ wait_for_device
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z $'1\r'
+ echo

++ readlink -f cache/pm-rootfs-latest.tar.gz
+ ./rootstock-touch-install /home/marcel/pm-flashtool/cache/rootfs/pm-rootfs-20180209-155413.tar.gz cache/bullhead/latest/system.img cache/bullhead/latest/boot.img
mount: mounting /dev/block/mmcblk0p40 on /cache failed: Invalid argument
mount: can't find /data in /etc/fstab
transfering rootfs tarball ... [done]
preparing system-image on device ... [done]
unpacking rootfs tarball to system-image ... Killed
[done]
adding android system image to installation ... error: no devices/emulators found


When transferring "transfering rootfs tarball", the TWRP tool appears in the device's screen. Here I can either:

• leave it at password request

• cancel password and enable system changes

It does not matter, the result is the same: The device shuts itself off after a while. "Killed" appears on the konsole... followed by the last messages.
whether I do nothing or try to "keep the device alive" by keeping my finger moving on screen has no influence on the outcome.

The whole procedure repeated various times either using "sudo" or "sudo su". Although using "sudo su" gives a slightly different output near the end:

Code: Select all

++ readlink -f cache/pm-rootfs-latest.tar.gz
+ ./rootstock-touch-install /home/marcel/WIENS/Support/IT/hardware/Mobile-phone/2018-03-02-Nexus-5X/PM/pm-flashtool2/pm-flashtool/cache/rootfs/pm-rootfs-20180306-104507.tar.gz cache/bullhead/latest/system.img cache/bullhead/latest/boot.img
mount: mounting /dev/block/mmcblk0p40 on /cache failed: Device or resource busy
mount: mounting /dev/block/mmcblk0p45 on /data failed: Device or resource busy
transfering rootfs tarball ... error: no devices/emulators found


In that case, The last screen on phone in the TWRP tool reads:

Code: Select all

updating partition details...
...done
Full SElinux support is present
wiping data without wiping /data/media ...
Done.
Formatting Cache using ?????_ext4fs...
Done processing script file
Renamed stock recovery file in /system to prevent
the stock ROM from replacing TEMP.


I'm not sure about the ??

software versions: fastboot version 1:7.0.0+r33-2 adb: Android Debug Bridge version 1.0.36 Revision 1:7.0.0+r33-2

Any advise is appreciated, Thanks

Update: most likely, my device is damaged, as the situation described here: https://forum.xda-developers.com/google-nexus-5/help/fastboot-oem-unlock-goes-to-lock-reboot-t2903581 looks very familiar...

You should be able to reactivate a Nexcus %x with an old factory image.

Are you using Linux or macOS for the Installation?

I'm using Linux... Kubuntu 17:10
Yes indeed, I could reactivate a factory image, but not using the standard provided "flash-all.sh" script. For flashing Version 6.0.1 MTC20K, I unzipped the bullhead-n2g48c-factory-45d442a2.zip and went into the directory bullhead-n2g48c, then, start bootloader on the nexus 5x (volume down, power on):

Code: Select all

fastboot flashing unlock

confirm on the nexus 5x, using volume and power buttons
(If I would reboot now, power off and return to bootloader, the device would be locked again, that is what is broken), Nevertheless, I could:

Code: Select all

fastboot flash bootloader bootloader-bullhead-bhz10r.img
fastboot reboot-bootloader
fastboot flashing unlock


confirm on the nexus 5x, using volume and power buttons

Code: Select all

fastboot flash radio radio-bullhead-m8994f-2.6.32.1.13.img
fastboot reboot-bootloader
fastboot flashing unlock


confirm on the nexus 5x, using volume and power buttons

Code: Select all

fastboot -w update image-bullhead-mtc20k.zip
fastboot reboot


And the android would be installed perfectly on the nexus 5x.

However, for flashing plasma-mobile, the nexus 5x needs to remain unlocked during the whole process and when TWRP is started, the device locks (automatically)... during the "./rootstock-touch-install ..." the device shuts off, notified as "killed"... and does not continue the installation... and as written above, I can get back to Android stock... but not flashing linux...

On the other forum https://forum.xda-developers.com/google-nexus-5/help/fastboot-oem-unlock-goes-to-lock-reboot-t2903581, theesotericone writes

Sounds like a nand failure. The boot loader staying locked is a key indicator of that. There's not really much more you can do.

I could still return the phone to the online shop and request a replacement... so hopefully next week ....