Meizu Pro 5 (meizu-turbo): Difference between revisions
m infobox: remove "", that doesn't look good on the device overview page |
Add info about OpenRC not logging |
||
Line 62: | Line 62: | ||
The display is not working - blank black screen. If provoked to display an early splash (e.g. no rootfs), a black image is displayed | The display is not working - blank black screen. If provoked to display an early splash (e.g. no rootfs), a black image is displayed | ||
with white lines on the left and top borders, as if it is a part of zoomed in image. | with white lines on the left and top borders, as if it is a part of zoomed in image. | ||
Turning on OpenRC logging does not produce any log files in /var/log on sysroot partition, which suggests that either switch_root and call to /sbin/init fails, | |||
or OpenRC fails on very early stage. | |||
<!-- add more sections below as necessary, e.g. Wifi, photos, ... --> | <!-- add more sections below as necessary, e.g. Wifi, photos, ... --> |
Revision as of 20:10, 17 December 2018
Manufacturer | Meizu |
---|---|
Name | Pro 5 |
Codename | meizu-turbo |
Released | 2015 |
Hardware | |
Chipset | Samsung Exynos 7420 Octa |
CPU | Octa-core (4x2.1 GHz Cortex-A57 & 4x1.5 GHz Cortex-A53) |
GPU | Mali-T760MP8 |
Display | AMOLED, 16M colors |
Storage | 32GB/64GB |
Memory | 3GB/4GB |
Architecture | aarch64 |
Software | |
Original software | Android 5, Ubuntu Touch |
postmarketOS | |
Category | testing |
Pre-built images | no |
Flashing |
Partial |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Battery |
No data |
Screen |
Broken |
Touchscreen |
No data |
Multimedia | |
3D Acceleration |
No data |
Audio |
No data |
Camera |
No data |
Camera Flash |
No data |
Connectivity | |
WiFi |
No data |
Bluetooth |
No data |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
FDE |
No data |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
Accelerometer |
No data |
Magnetometer |
No data |
Ambient Light |
No data |
Proximity |
No data |
Hall Effect |
No data |
Haptics |
No data |
Barometer |
No data |
Contributors
elelel
Maintainer(s)
How to enter flash mode
The device has to be with unlocked bootloader. Android phone version has bootloader locked by default. Locked bootloader may be unlocked with a Beta FlymeOS image for the international phone version. International firmware can be flashed to Chinese phone if one changes phone's id (possible with a 5.1.x Chinese firmware, root and a hex editor).
Press volume down and power while turning on to get into fastboot mode.
Installation
Current pmbootstrap utility assumes that boot partition is always named 'boot' on fastboot devices. This device's boot partition has 'bootimg' label. Because of that boot partition must be either flashed directly with fastboot utility, or pmbootstrap config source code has to be fixed.
Status
Currently when turned on, the device enters reboot loop. USB networking workds, telnet debugging hook lets log in at early stage before the reboot. All steps from init.sh until switch_root when entered manually in telnet debug shell seem to work without problem. The display is not working - blank black screen. If provoked to display an early splash (e.g. no rootfs), a black image is displayed with white lines on the left and top borders, as if it is a part of zoomed in image. Turning on OpenRC logging does not produce any log files in /var/log on sysroot partition, which suggests that either switch_root and call to /sbin/init fails, or OpenRC fails on very early stage.