Meizu MX4 magic-device-tool - I think I've done something wrong ... I'm stuck in a loop

happyzenith · 25 Feb 2018, 10:46

I think I've just finished using the magic-device-tool to install ubports on my Meizu MX4. The last few lines from the terminal are:

Move to your device to finish the setup.
Cleaning up..
Exiting magic-device-tool. Bye Bye

I've just turned my phone off using the power button, then turned it back on and seem to be stuck in a loop where I've got the regular Meizu powered by Ubuntu screen with => Normal Boot at the bottom for about 3 seconds, then it turns off for about three seconds on repeat.

I think I've probably done something wrong

Stefano · 25 Feb 2018, 14:30

@happyzenith why not use the terminal instead?

Reboot to recovery (power + volume up)

Type in:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable

If you want to completely wipe it, then add --wipe

at the end of the command.

hummlbach · 25 Feb 2018, 22:37

When I had similiar problems flashing ubports on my pro5, the --wipe option did the trick...

happyzenith · 26 Feb 2018, 22:25

@stefano Thanks for that tip!

The first time I got the following:
2018/02/25 15:35:46 Device is |arale|
2018/02/25 15:35:49 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
2018/02/25 15:35:49 Start pushing /home/nb/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2018/02/25 15:35:50 Done pushing /home/nb/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2018/02/25 15:35:50 Start pushing /home/nb/.cache/ubuntuimages/ubports-touch/15.04/stable/arale/version-3.tar.xz to device
2018/02/25 15:35:50 Done pushing /home/nb/.cache/ubuntuimages/ubports-touch/15.04/stable/arale/version-3.tar.xz to device
977 B / 337.07 MB [] 0.00 % 4.57 MB/s 1m13s2018/02/25 15:35:51 Start pushing /home/nb/.cache/ubuntuimages/gpg/image-master.tar.xz to device
2018/02/25 15:35:51 Done pushing /home/nb/.cache/ubuntuimages/gpg/image-master.tar.xz to device
978 B / 105.59 MB [] 0.00 % 6.38 MB/s 16s2018/02/25 15:35:51 Start pushing /home/nb/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2.36 KB / 105.59 MB [_________________________________________________________________] 0.00 % 11.79 KB/s 2h32m51s2018/02/25 15:35:51 Done pushing /home/nb/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
159.86 KB / 105.59 MB [213.30 KB / 105.59 MB [2223.14 K22242225237382.05 KB / 105.59 MB [] 0.35 % 13.35 KB/s 2h14m3102.98 MB / 105.59 MB [============================================================================>] 97.53 % 13.03 KB/s 3m24s
2018/02/25 17:50:41 read tcp 192.168.1.5:51482->104.18.45.123:80: read: connection reset by peer

I decided therefore to do exactly the same again.

This time I got:
nb@Tigger:~$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable
[sudo] password for nb:
2018/02/26 14:04:38 Device is |arale|
2018/02/26 14:04:38 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
2018/02/26 14:04:38 Target device cannot be reached over adb
nb@Tigger:~$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable
2018/02/26 14:04:57 Device is |arale|
2018/02/26 14:04:59 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
2018/02/26 14:04:59 Target device cannot be reached over adb
nb@Tigger:~$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable
2018/02/26 14:05:03 Device is |arale|
2018/02/26 14:05:04 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
2018/02/26 14:05:04 Target device cannot be reached over adb
nb@Tigger:~$
nb@Tigger:~$ sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable
2018/02/26 14:05:10 Device is |arale|
2018/02/26 14:05:11 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
2018/02/26 14:05:11 Start pushing /home/nb/.cache/ubuntuimages/ubports-touch/15.04/stable/arale/version-3.tar.xz to device
2018/02/26 14:05:11 Start pushing /home/nb/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
978 B / 105.59 MB [] 0.00 % 6.12 MB/s 17s2018/02/26 14:05:11 Done pushing /home/nb/.cache/ubuntuimages/pool/keyring-4c4e7ef380ebcfa2c31084efa199138e93bfed8fc58aa3eb06bdf75a78af9b57.tar.xz to device
2018/02/26 14:05:11 Done pushing /home/nb/.cache/ubuntuimages/ubports-touch/15.04/stable/arale/version-3.tar.xz to device
977 B / 337.07 MB [] 0.00 % 5.01 MB/s 1m6s2018/02/26 14:05:12 Start pushing /home/nb/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
2018/02/26 14:05:12 Done pushing /home/nb/.cache/ubuntuimages/gpg/image-signing.tar.xz to device
3.77 KB / 337.07 MB [] 0.00 % 2.09 KB/s 45h51m18s2018/02/26 14:05:13 Start pushing /home/nb/.cache/ubuntuimages/gpg/image-master.tar.xz to device
20.79 KB / 105.59 MB [_] 0.02 % 8.65 KB/s 3h28m11s2018/02/26 14:05:14 Done pushing /home/nb/.cache/ubuntuimages/gpg/image-master.tar.xz to device
105.59 MB / 105.59 MB [===================================================================================] 100.00 % 13.37 KB/s
2018/02/26 16:20:00 Start pushing /home/nb/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
105.87 MB / 337.07 MB [======================>_____________________________________________________] 31.41 % 13.35 KB/s 4h55m38s2018/02/26 16:20:34 Done pushing /home/nb/.cache/ubuntuimages/pool/device-c746103f205781974a7b89aff29cdf3dd450879f119f672d3a6f62b67ed783c5.tar.xz to device
337.07 MB / 337.07 MB [===================================================================================] 100.00 % 19.88 KB/s
2018/02/26 18:54:34 Start pushing /home/nb/.cache/ubuntuimages/pool/ubports-e5cf0885f061c9615931cf863a43f65d8590aa71027315ad71999252ce118868.tar.xz to device
2018/02/26 18:56:24 Done pushing /home/nb/.cache/ubuntuimages/pool/ubports-e5cf0885f061c9615931cf863a43f65d8590aa71027315ad71999252ce118868.tar.xz to device
2018/02/26 18:56:24 Created ubuntu_command: /home/nb/.cache/ubuntuimages/ubuntu_commands746454033
2018/02/26 18:56:24 Rebooting into recovery to flash

Now my phone shows a purple background with a ubuntu logo, with a progress bar exactly half through complete. It doesn't seem to have done anything for about four hours. I can turn the phone off and I have the same problem of restarting as before, or I can turn it back on in recovery mode and see the purple background. I've left it like that overnight ... but should I do anything else? Perhaps I'll try wiping it in the morning if it still hasn't made any more progress.

Stefano · 27 Feb 2018, 04:49

@happyzenith ok, try this then:
Reboot to bootloader/fastboot mode (power + volume down)

In terminal type:

sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable --bootstrap --wipe

But to warn you, you'll loose all the data on your phone, so I hope you made a backup before.

It should work. If not, there is even new Ubports installer you can try:

https://ubports.com/ubuntu-touch/get-ut

Download it and run, follow the on-screen instruction.
Let me know if succeeded.

happyzenith · 27 Feb 2018, 12:33

@Stefano I've tried your first suggestion and it gave me the following:

sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable --bootstrap --wipe
2018/02/27 11:30:20 Device is |arale|
2018/02/27 11:30:20 Flashing version 3 from 15.04/stable channel and server http://system-image.ubports.com to device arale
can't flash recovery image

I tried it in recovery (power + volume down) as well (just to see!) and I'm back stuck in the loop again.

When I try the installer instead (it fails to download about 5 times, then I realise I've got the installer on another computer!), I have to choose my phone from the menu - it doesn't seem to be connecting via USB. I get as far as the screen that says "Please reboot to bootloader" but no further. I've tried the whole process a couple of times ... with no success.

Marathon2422 · 27 Feb 2018, 12:39

@happyzenith try putting sudo ubports-installer,in terminal, I tried this ,the only time it has worked for me

happyzenith · 27 Feb 2018, 17:11

This post is deleted!

Stefano · 27 Feb 2018, 18:10

@happyzenith ok,
try to flash the MX4 recovery first and then try again same as previously.
To flash the recovery, do this;
Download the recovery from here: (https://drive.google.com/open?id=1gW9KEdm6C_yjiBdgbEf9feOGX3jwpuYn)
save it to your Home directory on your pc.
Reboot your phone to bootloader/fastboot mode
Type in terminal: sudo fastboot flash recovery recovery.img

Then reboot to recovery and try again with command:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=arale --channel=15.04/stable --wipe

happyzenith · 27 Feb 2018, 22:13

Thanks @Stefano !

The recovery seems to have worked. I now have a background with a UBports logo on

I've left the phone flashing for a couple of hours so far and I haven't had any feedback from the terminal or change on the phone. Is that normal? I've just left it to run overnight ...

happyzenith · 27 Feb 2018, 22:19

@Marathon2422 Thanks for that. I tried it and the last few lines from the terminal were:

info: Downloading file, 8% left
info: Download checking file
info: checked: ubports-e5cf0885f061c9615931cf863a43f65d8590aa71027315ad71999252ce118868.tar.xz
error: Devices: Download error Checksum did not match on file ubports-e5cf0885f061c9615931cf863a43f65d8590aa71027315ad71999252ce118868.tar.xz

I did this a couple of times, both times leaving it for a few hours each time, but it didn't finish,

Stefano · 28 Feb 2018, 01:20

@happyzenith
Reboot to recovery and type in terminal:
adb shell
rm -rf /cache/recovery/.xz /cache/recovery/.xz.asc

It will probably ask you for your password of the phone, just type it in(you won't see the text on terminal, just like when typing password in terminal on your PC)
It should delete the old files in Recovery.

Then try to flash again.

Lakotaubp · 3 Jan 2018, 13:29

@stefano Please carry on with the advice you are getting and I hope you get there in the end. Just in case, you said at the start you used the magic device tool to start with. If you haven't already and all else fails try the magic device tool --dev version. I used the snap if this to install on my mx 4.

happyzenith · 28 Feb 2018, 15:25

@stefano thanks!

I've tired adb shell and got error: device offline

Stefano · 1 Mar 2018, 12:51

@happyzenith Try to reflash the Recovery again and then try to clear the cache

happyzenith · 1 Mar 2018, 12:51

@stefano Thanks!

I accidentally did it in fastboot mode, which gave me:

sending 'recovery' (10760 KB)...
OKAY [ 0.566s]
writing 'recovery'...
OKAY [ 0.543s]
finished. total time: 1.109s

When I try to reflash the recovery section, using the downloaded code, in recovery mode, I get < waiting for device >

I've waited for about 15 minutes, then tried again with a different USB port and cable, but it gives me the same message

Lakotaubp · 1 Mar 2018, 13:32

@happyzenith Sorry posted this to the wrong person yesterday

Please carry on with the advice you are getting and I hope you get there in the end. Just in case, you said at the start you used the magic device tool to start with. If you haven't already and all else fails try the magic device tool --dev version. I used the snap if this to install on my mx 4.

Good luck with your quest

happyzenith · 1 Mar 2018, 14:12

@lakota Is that different from the magic-device-tool? How can I download that to try? I've had a look and couldn't find it. I'm probably using the wrong search terms ...

Lakotaubp · 1 Mar 2018, 16:06

@happyzenith Yes its a slightly different version. I used Linux mint and had to install snapd first which allows you to install snap packaged apps. Then search for Magic-device-tool --devmode and you should get the right version.
The normal MDT didn't work for me but this did and was very straight forward.
I've only done this once so I would look up how to install snapd and snaps from the net or theres info in the Ubports Doc app in the open app store. Wouldn't want to miss out anything by trying to remember what I did, but it was quite straight forward and I'm not at all techy.
There is also a MDT telegram group who will help you out. All the best

happyzenith · 1 Mar 2018, 16:33

Fab - all done! With lots of help from the lovely people on the UBports supergroup on Telegram

Firstly I downloaded to my computer the recovery image file for Meizu MX4 from: https://wiki.ubuntu.com/Touch/Devices#Working_with_ubuntu-device-flash

I needed to do this because it is a retail phone that shipped with Ubuntu installed already (and is currently running Ubuntu).

I rebooted into FASTBOOT (the bootloader) by pressing down on the volume button and power button at the same time and holding it until I could see =>FASTBOOT on the phone screen.

In the terminal on my computer I typed in: ubuntu-device-flash --server https://system-image.ubports.com touch --recovery-image recovery.img --channel ubports-touch/15.04/stable --bootstrap. If you have a different file name for the recovery image file you would need to put in a different file name where I've put recovery.img

On my phone I could then see a purple background and ubuntu logo. In the terminal window I could see a terminal output showing that it is pushing files.

Eventually the terminal output read "Rebooting into recovery to flash". The phone then reflashed and installed ... with me watching