Meizu Pro5 fastboot mode locked
-
Hi guys, it's still me
I was reading this bug post on GH for Cooler:
https://github.com/ubports/ubuntu-touch/issues/76It's quite the same issue I'm experiencing with my Pro5 and it seems that the @Marathon2422 comment on the NVRAM was right, even if on Flyme I didn't see any strange NVRAM-ERROR WIFI.
Nonetheless, I will re-install Flyme to better check the matter but in the meantime I'd like to raise some questions: why on Flyme the wi-fi password is retained, while once installed UT it is not retained anymore? Doesn't the NVRAM, in case of failure, act in the same way for every OS installed on the same phone? -
@matteo
There are plenty of youtube videos,about. MT and NVRAM err x 10,what it is and how to fix, usually,caused by the flash tool and the wrong setting.
not sure if it efffects pro5 the same way,if the file could be identified,and swapped for a working copy ?My M10fhd has this error, i sent it back to BQ,to get fixed, but it came back 3 months later,not repaired,it just sat in a mail room,and then was returned.
Kind of reluctant to send it again. -
@marathon2422 Thanks. I need to investigate the matter searching on youtube and better acknoledge the issue.
-
Sorry for hijacking this thread but as there are some Pro5 users here, can someone with a running device type this on the Terminal
df -h /android/cache/and paste the "size" output here https://papad.org/p/ubp-devices-cache-space?Thank you!
-
@advocatux Updated: Pro5/turbo: (64Gb version UbPorts OTA-3): 496M (32Gb version Canonical OTA-15): 679M
-
@tera thank you!
-
@advocatux said in Meizu Pro5 fastboot mode locked:
df -h /android/cache/
mine is at 913m for cache after using the one Stefano put up
-
@matteo
The NVRAM error does not show on BQ version 1.0.0, or 1.3.0, only from 2.1.0 and newer, FYI
On m10fhd -
@advocatux
on this post,how to increase cache size.Support
problems flashing UBports on meizu pro5.
I printed it, to follow it very carefully. -
@marathon2422 interesting. I was checking right now since I reinstalled Flyme 5.6.1.19 and I didn't see such an error among all the wi-fi access points. So you say that it could be there this NVRAM error but maybe I'm not able to see it on this Flyme version. However, I don't understand why rebooting the phone with Flyme the wi-fi credentials are retained but with UT they are not.
-
@advocatux 701M (resized already for Xenial)
-
@Stefano I'm still trying to investigate what's wrong with my pro5 as I feel there is something weird that prevents my phone to properly work. The problem seems related to APPARMOR in some ways. I attach here some of the logs I find mostly representative of my phone "illness":
Dbus.log
Ubuntu-location-service-trust-stored
application.click.sensorstatus
ubuntu-location-service-trust-storedI don't have the deep knowledge to understand what's going on...I hope somebody can identify the reason why this is happening helping me eventually to resolve the problem.
Thank you.
Matteo
-
@matteo I wish I could help, but I'm not a developer, nor can code. Maybe someone will have a look? Have you filled a bug report on Github Ubports website?
-
@stefano thanks anyways. I didn't open a bug report on GH yet because I'm not sure if this is related to the Ubuntu Touch OS itself or if this is peculiar of my phone only. I have the evidence that other people with fresh UT installation on pro5 don't suffer for the bugs I'm experiencing.
-
@matteo A lot of people with Pro 5 experience the data connection problem, signal drops, but not wifi. Strange, cos on Flyme is rather stable, so don't really know what's wrong and where.