Hello,
I don't manage to install plasma mobile on a nexus 5X with USB debogging activated, and also developer status. I've a TWRP installed (v 3.0.2-2).
I start the script. When the password is asked, it quit fastboot and log to TWRP and at the end it repeat always the same thing as seen below.
If someone has an idea about a solution…
Thanks

Code: Select all

./pm-flash
+ 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.007s
++ 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
+ '[' -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=20171220-160911
+ wget -c http://images.plasma-mobile.org/rootfs/pm-rootfs-20171220-160911.tar.gz -P rootfs
--2018-01-14 08:17:38--  http://images.plasma-mobile.org/rootfs/pm-rootfs-20171220-160911.tar.gz
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ ln -sf rootfs/pm-rootfs-20171220-160911.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=20171214-111413
+ wget -c http://images.plasma-mobile.org/halium/bullhead/recovery.img -P bullhead
--2018-01-14 08:17:38--  http://images.plasma-mobile.org/halium/bullhead/recovery.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171214-111413/system.img -P bullhead/20171214-111413
--2018-01-14 08:17:39--  http://images.plasma-mobile.org/halium/bullhead/20171214-111413/system.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171214-111413/boot.img -P bullhead/20171214-111413
--2018-01-14 08:17:39--  http://images.plasma-mobile.org/halium/bullhead/20171214-111413/boot.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ rm -f bullhead/latest
+ ln -sf 20171214-111413 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.466s]
booting...
OKAY [  0.550s]
finished. total time: 1.016s
+ 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 ''
+ echo -n .
.+ sleep 3
++ 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 ''
+ echo -n .
.+ sleep 3
++ adb shell echo 1
+ test -z ''
+ echo -n .
.+ sleep 3


I manage to install (but some failed appeared as seen below), I think but it remains on google logo. I think I should downgrade to android 6 as seen here https://forum.kde.org/viewtopic.php?f=297&t=139325

Code: Select all

./pm-flash
+ 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.000s
++ 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
+ '[' -z '' ']'
+ download bullhead neon
+ '[' 2 -eq 0 ']'
+ mkdir -p cache/
+ pushd cache/
~/Téléchargements/pm-flashtool/cache ~/Téléchargements/pm-flashtool
+ echo 'Downloading latest rootfs ... '
Downloading latest rootfs ...
+ '[' neon == neon ']'
++ curl http://images.plasma-mobile.org/rootfs_stamp
+ ROOTFS_VERSION=20171220-160911
+ wget -c http://images.plasma-mobile.org/rootfs/pm-rootfs-20171220-160911.tar.gz -P rootfs
--2018-01-15 23:03:56--  http://images.plasma-mobile.org/rootfs/pm-rootfs-20171220-160911.tar.gz
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ ln -sf rootfs/pm-rootfs-20171220-160911.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=20171214-111413
+ wget -c http://images.plasma-mobile.org/halium/bullhead/recovery.img -P bullhead
--2018-01-15 23:03:57--  http://images.plasma-mobile.org/halium/bullhead/recovery.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171214-111413/system.img -P bullhead/20171214-111413
--2018-01-15 23:03:57--  http://images.plasma-mobile.org/halium/bullhead/20171214-111413/system.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ wget -c http://images.plasma-mobile.org/halium/bullhead/20171214-111413/boot.img -P bullhead/20171214-111413
--2018-01-15 23:03:57--  http://images.plasma-mobile.org/halium/bullhead/20171214-111413/boot.img
Résolution de images.plasma-mobile.org (images.plasma-mobile.org)… 207.154.251.179
Connexion à images.plasma-mobile.org (images.plasma-mobile.org)|207.154.251.179|:80… connecté.
requête HTTP transmise, en attente de la réponse… 416 Requested Range Not Satisfiable

    Le fichier a déjà été complètement récupéré ; rien à faire.

+ rm -f bullhead/latest
+ ln -sf 20171214-111413 bullhead/latest
+ echo '[done]'
[done]
+ popd
~/Téléchargements/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.456s]
booting...
OKAY [  0.544s]
finished. total time: 1.000s
+ 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/go/Téléchargements/pm-flashtool/cache/rootfs/pm-rootfs-20171220-160911.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 ... [done]
preparing system-image on device ... [done]
unpacking rootfs tarball to system-image ... [done]
adding android system image to installation ... [done]
Setting up default password for phablet user to 1234 ... [done]
cleaning up on device ... [done]
Increasing the rootfs size to 4G ... e2fsck 1.42.9 (28-Dec-2013)
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information

/data/rootfs.img: ***** FILE SYSTEM WAS MODIFIED *****
/data/rootfs.img: 68412/128000 files (4.7% non-contiguous), 419360/512000 blocks
resize2fs 1.42.9 (28-Dec-2013)
Resizing the filesystem on /data/rootfs.img to 1024000 (4k) blocks.
The filesystem on /data/rootfs.img is now 1024000 blocks long.

[done]
[100%] /data/time/timekeep
[done]
rebooting into bootloader mode and flashing boot.img ... [done]


So I tried to install lineageos instead for the moment, but I have the same problem, it stays on "google".

Hello, I finally managed to install plasma mobile, but it didn't boot (stays on the boot screen with "google"). So I reinstalled Factory images for Android 6.0.1, and it works !

goalgauth wrote:Hello, I finally managed to install plasma mobile, but it didn't boot (stays on the boot screen with "google"). So I reinstalled Factory images for Android 6.0.1, and it works !

Hello, thanks for the info. But nobody mentions which 6.0.1 factory image to flash. Could you tell me which factory image you flashed (https://developers.google.com/android/images#bullhead) before using the pm-flashtool?
Thanks!

lazlo wrote:

goalgauth wrote:Hello, I finally managed to install plasma mobile, but it didn't boot (stays on the boot screen with "google"). So I reinstalled Factory images for Android 6.0.1, and it works !

Hello, thanks for the info. But nobody mentions which 6.0.1 factory image to flash. Could you tell me which factory image you flashed (https://developers.google.com/android/images#bullhead) before using the pm-flashtool?
Thanks!

Not android 6.0.1, but android 7.0.1,

You can use the flash-vendor script in the pm-flashtool repository, which downloads pre-extracted vendor image and flashes it to /vendor partition.

Thanks