Yep, the rom (bullhead-20170209-173909.zip) is identical (everything is with the obvious exception that I went with -p arch )

With an Arch install when I use lxc-start -n system -F I am able to login to the phone using phablet and default password. However on the phone screen is still stuck on Google logo.

Can confirm, that indeed works! Do you know of a place with some documentation to look at?

gibru wrote:Can confirm, that indeed works! Do you know of a place with some documentation to look at?

I have been using
https://community.kde.org/Plasma/Mobile/Flashing
https://plasma-mobile.org/nexus-5/

Let me know if you find a better place to refer to.

Ok AMunshi, got it to work!

Talked to Bhushan and turns out silviof already posted the solution. He was just a bit too "elliptic" when posting the solution

Long story short: Bhushan is working on fixing the issue.

The reason it didn't work for us is because our phones already came pre-installed with Android 7 and this probably caused some issues with the flashing process. So what you have to do if you want to get it to work is to go get a factory image for the NX 5 of Android 6. Here's the link: https://developers.google.com/android/images. I chose 6.0.1 (MTC20K) (sha256: 4a950470af6c1e0111cfa8efbd77422928b88d01800dd2fadc6f8eeeae1b97a9).

Just download the zip. unpack and run the sh as instructed. After that, just the usual: enable ADB in the developer's options on Android, quick adb reboot bootloader and you're set. At this point, just ./pm-flash -p neon

Go grab a coffee and wait for the magic to happen. I ran it before lunch and when I got back I had a N5X running Plasma

Cheers

gibru wrote:Ok AMunshi, got it to work!

Talked to Bhushan and turns out silviof already posted the solution. He was just a bit too "elliptic" when posting the solution

Long story short: Bhushan is working on fixing the issue.

The reason it didn't work for us is because our phones already came pre-installed with Android 7 and this probably caused some issues with the flashing process. So what you have to do if you want to get it to work is to go get a factory image for the NX 5 of Android 6. Here's the link: https://developers.google.com/android/images. I chose 6.0.1 (MTC20K) (sha256: 4a950470af6c1e0111cfa8efbd77422928b88d01800dd2fadc6f8eeeae1b97a9).

Just download the zip. unpack and run the sh as instructed. After that, just the usual: enable ADB in the developer's options on Android, quick adb reboot bootloader and you're set. At this point, just ./pm-flash -p neon

Go grab a coffee and wait for the magic to happen. I ran it before lunch and when I got back I had a N5X running Plasma

Cheers

This worked perfectly. Thanks for all the help to get me started with Plasma Mobile.

gibru wrote:Ok AMunshi, got it to work!

Talked to Bhushan and turns out silviof already posted the solution. He was just a bit too "elliptic" when posting the solution

Long story short: Bhushan is working on fixing the issue.

The reason it didn't work for us is because our phones already came pre-installed with Android 7 and this probably caused some issues with the flashing process. So what you have to do if you want to get it to work is to go get a factory image for the NX 5 of Android 6. Here's the link: https://developers.google.com/android/images. I chose 6.0.1 (MTC20K) (sha256: 4a950470af6c1e0111cfa8efbd77422928b88d01800dd2fadc6f8eeeae1b97a9).

Just download the zip. unpack and run the sh as instructed. After that, just the usual: enable ADB in the developer's options on Android, quick adb reboot bootloader and you're set. At this point, just ./pm-flash -p neon

Go grab a coffee and wait for the magic to happen. I ran it before lunch and when I got back I had a N5X running Plasma

Cheers

If you don't mind me asking, which 6.0.1 image did you get? I just grabbed the MMB29K because it was first, and now when I Plasma on top of that it seems to hang up on an adb wait-for-device while the screen shows an Android logo.

If you don't mind me asking, which 6.0.1 image did you get? I just grabbed the MMB29K because it was first, and now when I Plasma on top of that it seems to hang up on an adb wait-for-device while the screen shows an Android logo.

I used MTC20K. Waiting for device may happen because the new boot loader has a slider that needs to swiped when it appears. The boot loader asks for user to authorize the modifications.

AMunshi wrote:I used MTC20K. Waiting for device may happen because the new boot loader has a slider that needs to swiped when it appears. The boot loader asks for user to authorize the modifications.

Yep, looks like that was the issue. Another N5X is now running Plasma.

AMunshi wrote:Are you using pm-flash -p neon or arch?

Does anyone know if the `-p` flag has been removed? While flashing I tried the `-p neon` parameter (as shown in the Nexus 5X flashing instructions) and the script stopped with an "invalid option" error. Looking at the pm-flash script it does appear that the only valid flag is now `-c`. Am I missing something or are the instructions a little out of date?

i just went through all the steps (I think) I ended up downgrading to 6.0.1 (MTC20K) and then running the flash for neon. I am currently stuck, not at the Google logo screen, but rather at an "android" logo boot screen. Any advice?

So in the pm script after the function flash-phone there was some sort of issue between my phone and adb (I'm guessing). I ended up manually running all the steps from flash-phone and plasmafy in pm-flash script and my device is now up and running.

NexusSleuth wrote:
Does anyone know if the `-p` flag has been removed?

For halium-flash branch (which is recommended) yes -p flag is removed for now. just use ./pm-flash .

Unfortunately I can’t install Plasma Mobile successfully. I realised an update of the installation instruction and tried the installation today.

First I did a reset of my Nexus 5X with the factory image MTC20K by following the instructions of Google. Afterwards my 5X startet without problems and I could set it up and send an SMS and start a call.

Then I followed the updated instruction on https://plasma-mobile.org/nexus-5/. After the script has finished, my 5X restarted not with Plasma Mobile but with the previous installed Android 6.0.1.

The last console output is the following:

Code: Select all

+ ln -s 20170703-141145 bullhead/latest
+ echo '[done]'
[done]
+ popd
~/PlasmaMobile/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.437s]
booting...
OKAY [  0.536s]
finished. total time: 0.972s
+ 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
readlink: illegal option -- f
usage: readlink [-n] [file ...]
+ ./rootstock-touch-install cache/bullhead/latest/system.img cache/bullhead/latest/boot.img
Need valid rootfs tarball gzip type
usage: rootstock-touch-install <path to rootfs tarball> <path to android system.img> [options]

   options:
   -h|--help      this message

Has someone an idea, to keep Plasma Mobile running?

joergw wrote: Has someone an idea, to keep Plasma Mobile running?

Which operating system you are using?

Code: Select all

++ readlink -f cache/pm-rootfs-latest.tar.gz
readlink: illegal option -- f


Above seems to be error.