@stefano Hi, I have just typed this command ubuntu-device-flash --server=https://system-image.ubports.com touch --device=turbo --channel=ubports-touch/16.04/stable thinking that my phone is not connected to a laptop... but it was. I have flashed UBPorts OTA-4 on my Meizu Pro 5. Thanks a lot!

Is this something interesting for UBports?

https://www.indiegogo.com/projects/cosmo-communicator/#/

Since they promise to be able to run Debian on it, it should be possible to port UBports onto...?

I see the command I entered is not complete.
I have flashed a new recovery on fastboot mode.
Then I followed with complete command:

$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable --bootstrap --recovery-image=./recovery-turbo.img
2017/12/06 16:13:15 Device is |turbo|
2017/12/06 16:13:15 Flashing version 2 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
2017/12/06 16:13:19 Waiting for device to enter recovery mode ...
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 16:13:50 Done pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 16:14:23 Done pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 16:14:23 Created ubuntu_command: /home/andrzej/.cache/ubuntuimages/ubuntu_commands002121213
2017/12/06 16:14:23 Rebooting into recovery to flash

And it's back to life.
Unfortunately I have wiped it with this. But it's good to wipe it from time to time

Is this something interesting for UBports?

https://www.indiegogo.com/projects/cosmo-communicator/#/

Since they promise to be able to run Debian on it, it should be possible to port UBports onto...?

You saved my day! Thanks a lot! It works!

https://gitlab.com/bhdouglass/rockwork/issues/4

Hi,

I have just installed OTA-5 on Meizu Pro 5 and RockWork doesn't start anymore. I can see a blue circle with arrows going round and it never goes to main screen.

Connecting to Pebble from bluetooth page seems to work ok.

Anybody hass an ide what to do with this?

@stefano Hi, I have just typed this command ubuntu-device-flash --server=https://system-image.ubports.com touch --device=turbo --channel=ubports-touch/16.04/stable thinking that my phone is not connected to a laptop... but it was. I have flashed UBPorts OTA-4 on my Meizu Pro 5. Thanks a lot!

After several unsuccessful tries I have installed TWRP. Wiped the device. Then installed "recovery-turbo" again.
At the end I have installed RC channel with this command:

$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/rc
2017/12/07 13:35:44 Device is |turbo|
2017/12/07 13:35:44 Flashing version 12 from 15.04/rc channel and server http://system-image.ubports.com to device turbo
2017/12/07 13:35:45 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/07 13:35:47 Start pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/07 13:35:47 Start pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/07 13:35:47 Start pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/rc/turbo/version-12.tar.xz to device
2017/12/07 13:35:47 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/07 13:35:47 Start pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-ab3bba2c6973569f7df80a7d9fe67bccbeec8edc58cf34e8c4a04f27293837b4.tar.xz to device
2017/12/07 13:35:48 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/07 13:35:48 Done pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/07 13:35:48 Done pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/rc/turbo/version-12.tar.xz to device
2017/12/07 13:35:48 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/07 13:36:10 Done pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/07 13:36:45 Done pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-ab3bba2c6973569f7df80a7d9fe67bccbeec8edc58cf34e8c4a04f27293837b4.tar.xz to device
2017/12/07 13:36:45 Created ubuntu_command: /home/andrzej/.cache/ubuntuimages/ubuntu_commands881164790
2017/12/07 13:36:46 Rebooting into recovery to flash

I have read on another topic that I should not use "" --bootstrap " option. Anybody knows why? Why it is there in the documentation?

(sorry for answering myself, but I think somebody else might learn from my experience while installing UBPorts on Meizu Pro 5)

I tried several times installing rc or stable channel from scratch but continuously failing with ""Failed to enter Recovery"

$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/rc --bootstrap --recovery-image=./recovery-turbo.img
2017/12/07 13:11:27 Device is |turbo|
2017/12/07 13:11:27 Flashing version 12 from 15.04/rc channel and server http://system-image.ubports.com to device turbo
2017/12/07 13:11:31 Waiting for device to enter recovery mode ...
Failed to enter Recovery

Hi struggled again with this today.
I wanted to switch to RC channel. The switch on the phone settings doesn't seem to have any effect. It switches back itself to stable.
So looking into the wiki page (https://wiki.ubports.com/wiki/Release-Channels), I tried this command:

sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --channel=15.04/rc
2017/12/07 11:25:26 Expecting the device to expose an adb interface...
2017/12/07 11:25:26 Device is |turbo|
2017/12/07 11:25:26 Flashing version 12 from 15.04/rc channel and server http://system-image.ubports.com to device turbo
10.34 KB / 320.96 MB [] 0.00 % 34.41 MB/s 9s2017/12/07 11:25:28 Start pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/rc/turbo/version-12.tar.xz to device
2017/12/07 11:25:28 Start pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/07 11:25:28 Start pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/07 11:25:28 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/07 11:25:28 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
177.54 KB / 320.96 MB [] 0.05 % 885.74 KB/s 6m10s2017/12/07 11:25:28 Done pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/07 11:25:28 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/07 11:25:28 Done pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/rc/turbo/version-12.tar.xz to device
2017/12/07 11:25:28 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
28.80 MB / 320.96 MB [==========>_______________________________________________________________________________________________________________] 8.97 % 1.71 MB/s 2m50s2017/12/07 11:25:45 Done pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
320.96 MB / 320.96 MB [=================================================================================================================================] 100.00 % 1.54 MB/s
2017/12/07 11:28:56 Start pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-ab3bba2c6973569f7df80a7d9fe67bccbeec8edc58cf34e8c4a04f27293837b4.tar.xz to device
2017/12/07 11:29:45 Done pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-ab3bba2c6973569f7df80a7d9fe67bccbeec8edc58cf34e8c4a04f27293837b4.tar.xz to device
2017/12/07 11:29:45 Created ubuntu_command: /home/andrzej/.cache/ubuntuimages/ubuntu_commands513972988
2017/12/07 11:29:45 Rebooting into recovery to flash
Failed to enter Recovery

And it failed! I was left again with not booting phone. Only fastboot was responding.

I see the command I entered is not complete.
I have flashed a new recovery on fastboot mode.
Then I followed with complete command:

$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable --bootstrap --recovery-image=./recovery-turbo.img
2017/12/06 16:13:15 Device is |turbo|
2017/12/06 16:13:15 Flashing version 2 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
2017/12/06 16:13:19 Waiting for device to enter recovery mode ...
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 16:13:29 Start pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 16:13:29 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 16:13:50 Done pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 16:14:23 Done pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 16:14:23 Created ubuntu_command: /home/andrzej/.cache/ubuntuimages/ubuntu_commands002121213
2017/12/06 16:14:23 Rebooting into recovery to flash

And it's back to life.
Unfortunately I have wiped it with this. But it's good to wipe it from time to time

Hi I have just tried to flash latest stable to my Meizu Pro 5 using this command:

$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=15.04/stable
2017/12/06 15:26:15 Device is |turbo|
2017/12/06 15:26:15 Flashing version 2 from 15.04/stable channel and server http://system-image.ubports.com to device turbo
2017/12/06 15:26:15 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 15:26:15 Start pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 15:26:15 Start pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 15:26:15 Start pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 15:26:18 Start pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 15:26:18 Done pushing /home/andrzej/.cache/ubuntuimages/ubports-touch/15.04/stable/turbo/version-2.tar.xz to device
2017/12/06 15:26:18 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2017/12/06 15:26:18 Done pushing /home/andrzej/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2017/12/06 15:26:18 Done pushing /home/andrzej/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2017/12/06 15:26:18 Start pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 15:26:37 Done pushing /home/andrzej/.cache/ubuntuimages/pool/device-60f53a5768e9340729d3a5ef9263bd3a9726792e7d0dbf830e5b124938dd419a.tar.xz to device
2017/12/06 15:27:03 Done pushing /home/andrzej/.cache/ubuntuimages/pool/ubports-03a48725ab23059f103ccbb3cfa913f1ebcd314aaa0742e9ff724ee4fef19d78.tar.xz to device
2017/12/06 15:27:03 Created ubuntu_command: /home/andrzej/.cache/ubuntuimages/ubuntu_commands211794806
2017/12/06 15:27:03 Rebooting into recovery to flash
Failed to enter Recovery

As it can be seen it resulted with a screen with error saying ""Flashing failed. Contact Support" in few different languages.
As a result I can boot to fastboot, but normal restart stops at screen with "MEIZU powered by ubuntu".
Can I somehow recover it?