Meizu Pro 5 (meizu-turbo): Difference between revisions
Created page with "Category:Not booting {{Infobox device | manufacturer = Meizu | name = Pro 5 | codename = meizu-turbo | image = | imagecaption = Meizu 5 Pro | releaseyear = 2015 | origina..." |
No edit summary |
||
Line 64: | Line 64: | ||
== See also == | == See also == | ||
{{MR|106}} Initial merge request | |||
<!-- | <!-- | ||
Link to related gitlab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234): | Link to related gitlab issues or merge requests like the following (replace CHANGEME with the ID, e.g. 1234): |
Revision as of 23:28, 15 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 |
Mainline | "" |
Flashing |
Partial |
---|---|
USB Networking |
Works |
Internal storage |
No data |
SD card |
No data |
Multimedia | |
Camera Flash |
No data |
Connectivity | |
GPS |
No data |
NFC |
No data |
Modem | |
Calls |
No data |
SMS |
No data |
Mobile data |
No data |
Miscellaneous | |
USB OTG |
No data |
HDMI/DP |
No data |
Sensors | |
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.
At the time of writing the device boots, but is unable to insert subpartitions from 'system' partition into kernel. kpartx -avs /dev/sda41 sees the partition table, but each subpartition inside appears to be corrupt. USB networking workds, telnet debugging hook lets log in at early stage before root is mounted.
See also
!106 Initial merge request