Meizu Pro5 fastboot mode locked
/dev/disk/by-partlabel/cache 496M 2,8M 483M 1% /android/cache
And, after installing the ubuntu-device-flash the following command worked:
sudo ubuntu-device-flash --server=http://system-image.ubports.com touch --device=turbo --channel=ubports-touch/16.04/devel --bootstrap --wipe
But it stalled after rebooting into the Ubuntu recovery, like you said in that post. I would like to proceed with the mihael procedure to resize the cache but it is not very straightforward... I'm not sure for example where to type the lines listed at the very beginning:
mount /dev/block/sda41 /system
mount -t proc proc /system/proc
mount -t sysfs sys /system/sys
mount -o bind /dev /system/dev
chroot /system /bin/bash
@stefano uuuuuuuu thanks, will do! I completely missed that!
Marathon2422 last edited by
very stressful for a retired truck driver like me .
nearly tripped up on the name for 43 , got there in the end ,now i need a drink.
maybe i need to buy you a drink Thanks Stefano.
/dev/block/sda32 45568 50687 5120 20M Microsoft basic data
/dev/block/sda33 50688 55807 5120 20M Microsoft basic data
/dev/block/sda41 65536 720895 655360 2.5G Microsoft basic data
/dev/block/sda42 720896 790000 69105 270M Microsoft basic data
/dev/block/sda43 790016 1031167 241152 942M Microsoft basic data
/dev/block/sda44 1031168 7633914 6602747 25.2G Microsoft basic data
@stefano UPDATE: I wiped the phone completely and the situation of my Pro5 partitions is the following:
Now I'm stuck at the first step:
mount /dev/block/sda41 /system -----------> OK!
mount -t proc proc /system/proc -------------> ERROR!
mount -t sysfs sys /system/sys -------------> ERROR!
mount -o bind /dev /system/dev -------------> ERROR!
BTW how to get rid of the tmpfs partitions, if possible? And why there are 2 partitions named sda44?
@matteo If you wiped the phone completely, you lost a tool to change the partitions. You'll need Gparted or flash back Ubuntu Touch and follow the guide. Ubuntu Touch itself is Linux distro and has a tool to do it within the system (fdisk)
The partition you see are Android partitions as you formated with TWRP ( I presume)
No need to remove tmpfs, actually I wouldn't touch it at all. Same for partition 44.
@stefano Right Stefano, I just realized....Actually I had to wipe it with TWRP because I tried to go back to 15.04 Stable channel but I got a big error at the end of the update and my phone just didn't boot anymore. I noticed I had some issue with the 15.04, for example the wi-fi lost the password at every boot.
Stefano last edited by Stefano
If there is trouble to have your phone recognize with adb, then reboot the phone to Ubuntu Touch and unplug it from PC. In terminal (on PC) type:
sudo adb kill-server
sudo adb start-server
Plug in the phone, on the screen should appear a small window to allow adb usb debuggingusb, click on to allow.
Your phone (curent installation of Ubuntu Touch will remeber your PC and will allow the adb usb debugging)
Reboot again to recovery and try Ubports installer or ubuntu-device-flash
@stefano I did it Stefano! I followed step by step your guide to resize the cache partition and now I have the 16.04 UT installed! Thank you so much, you were very helpful! I would like only to take the advantage of this open thread to share some thoughts about the newly installed OS:
- I tried to install back the Ubuntu recovery by typing "sudo fastboot flash recovery-turbo.img" but now, inaspectedly respect to when I did the same for the 15.04 working flawlessly, now I got this error:
Just to be clear, the file is in the $home folder, the name of it is "recovery-turbo.img" and I enabled the developer mode.
However, is there a reason why I should install the Ubuntu recovery? Doesn't make any sense to stick with the TWRP recovery, in order to be ready in case of any problem and restore for instance the backup?
Both with the 15.04 and now with the 16.04 I noted that my home wi-fi session is not keeping the password, which I have to reinstate every time I reboot the phone; I searched for a known bug on the UBports github and on this forum but unluckily I didn't find a thing about it. Do you know how to fix this problem on my Pro5?
I think I can reply to myself for point 2: if I try to update the OS and I download and install the OS update, the phone tries to boot to the Ubuntu recovery but instead boots to TWRP and there it just stuck and doesn't continue anymore the updating process.
That's why I need the Ubuntu recovery, but up to now I'm not able to flash it again for some reasons it seems....
reinstall the recovery by this command:
sudo fastboot flash recovery recovery-turbo.img
Yes it makes sense to have Ubuntu recovery installed for OS updates. If you just want to test it, then no.
The wifi problem I never experienced on Pro 5, only on Nexus 5.
I would probably wipe the phone completely, install Flyme 5......daily (the one for unlocking bootloader)
And try again with Ubuntu aftrwards. Your partitions should stay untouched, ready for 16.04.
I don't think that anyone mentioned that wifi bug on Pro 5, so probably just a glitch.
@stefano ahahaaha so I missed the command 'recovery' there.....yes, it works now
For the wifi then you are suggesting to install Flyme again ....ok I'll try that also, if I see the wifi problem persisting even after the latest update.
Big thanks to all you guys who helped me so much! This community is awesome!
@matteo No problemo, I got helped, so I do help others.
Marathon2422 last edited by
@matteo regarding the wifi
,my bqm10fhd has this problem
Caused by the flash tool,and my error.
If you go back to android it will show NVRAM error x10.
But it will remember passwords ,on android.
I do not have this on my pro5
Unfortunately I flashed Flyme and then back to UT 16.04 but nothing, the wi-fi doesn't keep the password and at every reboot I have to reinstate that: it is so annoying. In Flyme it worked as expected, by the way. I suspect that also the GPS doesn't work because before, when I flashed for the first time the UT 15.04, both the wi-fi and GPS didn't worked as expected (I left the GPS looking for my position for 10 minutes or so and then I gave up). But here in 16.04 I found out I cannot install the uNav app yet, so I cannot check it.
@Marathon2422 When I flashed the Flyme OS I didn't see such an error you are mentioning, so I don't really know what's going on with my Pro5. Am I the only one to have experienced that? Really weird...
advocatux last edited by
@matteo I have uNav installed on my xenial device and also sensorsstatus. Both are versions for vivid, that's true, but they seem to work and at least those apps don't crash. Enough for me until there's a proper xenial version.
For your wifi password you should file a bug report if it isn't filed already https://github.com/ubports/ubuntu-touch/issues (use the Label button to look for issues specific of your phone).
Stefano last edited by Stefano
@matteo Maybe download latest Flyme (International,Global ) unzip the update.zip file, remove bootloader file from there, create a new update.zip( without bootloader file as this way you won't need to unlock it again) , flash it with Meizu Original recovery,( Wipe as well) enable Developer options, usb debugging, flash TWRP recovery, wipe it and try it again.
Otherwise I'm out ideas what to do to make the wifi works.
@stefano Stefano thanks but it's not only the wifi. I just tried the sim card and it doesn't work as well. It's only 10 minutes I'm playing around with the 16.04 version and I stepped into several issues, for instance: the browser doesn't load a newspaper page throwing an error; if I select the printer option the system settings window freezes; transparency of the keyboard doesn't seem to properly work. I know that most of them are related to the status of the OS so I don't bother at all. It's the connectivity which bothers me and seems completely broken. However, I'll try to follow your hint and to keep flashing back to Flyme and forth to UT.
@advocatux how could you do that? I don't see in the list of OpenStore neither uNav nor sensorstatus...By the chance, do you have the click files?
For sure I'll file tickets on Github, once I'm sure my problems are not related to maybe some mistakes I made during the flashing process as Marathon was suggesting...the reason why I wanted to go with the 16.04 OS was also to help improving it in some ways...