Please enable / Bitte aktiviere JavaScript!
Veuillez activer / Por favor activa el Javascript!

[update#4] Updating Meizu Pro6 ChinaMainland (A or Q) to G (Global) SW? [Method1] or [2,3,4 failed]

Hi, All.
I’ve tried to update my 5.4.1.1Q [original version in china mainland] to Global Version.

downloaded and try to updates from link https://forum.meizufans.eu/topic/2599/guide-how-to-install-i-international-firmware-on-your-chinese-mainland-meizu

[Updated #4] Finally I’ve failed to change A.Q version to 5.2.4.0G (Global Version) and Reverted to 5.2.4.1A .

You can my progress by Update # 1, 2, 3 with update method 2 way. And Also needs to update above article
Method 2 or 3 way , converting updates images utilities.

Conclusion :
Meizu Pro6 A version and G version has different device information and Device IMEI information tables.
So, I’ve forceley changed/updated to G version , Can’t Identify IMEI and Phone Call LTE/GSM informations.
And, then Just use as wifi pad. not a smart phone.

Another Question is changing it to A or Q version install Google Service? thru unlocking china region bound.

[Updates #1]
Method 2, 3 failed : can’t converting the new system images.
Pro6 , 5.2.4.0G file has Zero (0) values.
convert programs break on Zero (0) .

system.transfer.list

3
515011
0
0
new 80,0,32770,32929,32931,33439,65535,65536,65538,66046,98303,98304,98306,98465,98467,98975,131071,131072,131074,131582,163839,163840,163842,164001,164003,164511,196607,196608,196610,197118,229375,229376,229378,229537,229539,230047,262143,262144,262146,262654,294911,294912,294914,295073,295075,295583,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,490704,491520,491522,524288,524290,557056,557058,589824,589826,622592,622594,623102,650190,650191,655320
zero 86,32770,32929,32931,33439,65535,65536,65538,66046,98303,98304,98306,98465,98467,98975,131071,131072,131074,131582,163839,163840,163842,164001,164003,164511,196607,196608,196610,197118,229375,229376,229378,229537,229539,230047,262143,262144,262146,262654,294911,294912,294914,295073,295075,295583,327679,327680,327682,328190,360447,360448,360450,360958,393215,393216,393218,393726,425983,425984,425986,426494,458751,458752,458754,459262,490704,491520,491522,492034,523776,524288,524290,524802,556544,557056,557058,557570,589312,589824,589826,590338,622080,622592,622594,623102,650190,650191
erase 8,492034,523776,524802,556544,557570,589312,590338,622080 

Method 4 with 5.4.2.0G has always failed “Firmware Corrupt” messages shown.

I want to use Global version and Google Apps.
Is there Method1 or Method2 way?

[Updates #2]
I’ve found Converter programs in github https://github.com/trustfarm/sdat2img
add sdat2img.py to bin/ folder

caution You needs to install python 2.7 for windows and python.exe is on PATH

inside of System-conVERTER.cmd

bin\sdat2img -> bin\sdat2img.py

Then It makes Out\system.img

copy system.img to M570C (Pro6) internal Download/ folder.

using putty with conneted sshDroid (pro6)

dd if=/storage/emulated/0/Download/system.img of=/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name/system 

5~10 minutes blank , but ssh putty terminal acks when enter.

[Updates #3]

-_- :disappointed: Half of Success. sim information and some things are not compatible with previous things.

It may be default system library must updates with given update.zip [5.2.4.0G]

Anyway I’m install google play service.

Booting!
1_1480335331429_booting.jpg

Phone Information - missing SIM info
4_1480335331431_phoneinfo.jpg

Installing Google service managaer
3_1480335331430_installgsm.jpg

TO BE CONTINUED

I’ve dumped related pro6 images structure information. it’s 5.2.4.1A version snapshot.

[email protected]:/proc # cat partitions
major minor  #blocks  name

   7        0      12166 loop0
 179        0   30535680 mmcblk0
 179        1      30720 mmcblk0p1
 179        2        512 mmcblk0p2            --  

00020000  45 4e 56 5f 76 31 00 00  6f 66 66 2d 6d 6f 64 65  |ENV_v1..off-mode|
00020010  2d 63 68 61 72 67 65 3d  31 00 00 00 00 00 00 00  |-charge=1.......|
00020020  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00023ff0  00 00 00 00 45 4e 56 5f  76 31 00 00 12 06 00 00  |....ENV_v1......|
00024000  00 00 00 00 00 00 00 00  00 00 00 00 00 00 00 00  |................|
*
00040000  ef 55 44 ff 00 00 00 00  00 00 00 00 00 00 00 00  |.UD.............|
00040010  ef 55 44 ff 00 00 00 00  00 00 00 00 ef 55 44 ff  |.UD..........UD.|
00040020  00 00 00 00 00 00 00 00  00 00 00 00 ef 55 44 ff  |.............UD.|

 179        3     524288 mmcblk0p3
 179        4        256 mmcblk0p4             --   

00000200  30 78 35 37 30 36 31 30  30 31 0a 00 00 00 00 00  |0x57061001......|

 179        5      20480 mmcblk0p5
 179        6      10240 mmcblk0p6
 179        7       1024 mmcblk0p7
 179        8       8192 mmcblk0p8
 179        9      32768 mmcblk0p9
 179       10      32768 mmcblk0p10
 179       11       8192 mmcblk0p11
 179       12      10464 mmcblk0p12
 179       13       8192 mmcblk0p13
 179       14       2048 mmcblk0p14
 179       15       7168 mmcblk0p15
 179       16      24576 mmcblk0p16
 179       17       4096 mmcblk0p17
 179       18       3072 mmcblk0p18
 179       19       5120 mmcblk0p19
 179       20       1024 mmcblk0p20
 179       21       1024 mmcblk0p21
 179       22       5120 mmcblk0p22
 179       23        512 mmcblk0p23
 179       24        512 mmcblk0p24
 179       25      16384 mmcblk0p25
 179       26       8192 mmcblk0p26
 179       27       5120 mmcblk0p27
 179       28       5120 mmcblk0p28
 179       29       9216 mmcblk0p29
 179       30    2621440 mmcblk0p30
 179       31     442368 mmcblk0p31
 259        0   26669024 mmcblk0p32
 259        1      16384 mmcblk0p33
 179       96       4096 mmcblk0rpmb
 179       64       4096 mmcblk0boot1
 179       32       4096 mmcblk0boot0

And named partition and path are followings:

[email protected]:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name # ls -l
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 cache -> /dev/block/mmcblk0p31
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 custom -> /dev/block/mmcblk0p3
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 devinfo -> /dev/block/mmcblk0p4
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 expdb -> /dev/block/mmcblk0p6
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 flashinfo -> /dev/block/mmcblk0p33
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 frp -> /dev/block/mmcblk0p7
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 keystore -> /dev/block/mmcblk0p29
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 lk -> /dev/block/mmcblk0p23
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 lk2 -> /dev/block/mmcblk0p24
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 logo -> /dev/block/mmcblk0p26
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 md1arm7 -> /dev/block/mmcblk0p18
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 md1dsp -> /dev/block/mmcblk0p17
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 md1img -> /dev/block/mmcblk0p16
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 md3img -> /dev/block/mmcblk0p19
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 metadata -> /dev/block/mmcblk0p10
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 nvcfg -> /dev/block/mmcblk0p8
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 nvdata -> /dev/block/mmcblk0p9
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 nvram -> /dev/block/mmcblk0p22
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 oemkeystore -> /dev/block/mmcblk0p14
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 para -> /dev/block/mmcblk0p2
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 proinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 protect1 -> /dev/block/mmcblk0p11
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 protect2 -> /dev/block/mmcblk0p12
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 recovery -> /dev/block/mmcblk0p1
lrwxrwxrwx    1 root     root            20 Nov 28 08:23 rstinfo -> /dev/block/mmcblk0p5
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 scp1 -> /dev/block/mmcblk0p20
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 scp2 -> /dev/block/mmcblk0p21
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 seccfg -> /dev/block/mmcblk0p13
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 system -> /dev/block/mmcblk0p30
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 tee1 -> /dev/block/mmcblk0p27
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 tee2 -> /dev/block/mmcblk0p28
lrwxrwxrwx    1 root     root            21 Nov 28 08:23 userdata -> /dev/block/mmcblk0p32
[email protected]:/dev/block/platform/mtk-msdc.0/11230000.msdc0/by-name #


please give a more advanced solutions.

last edited by trustfarm
Admin

I would try to flash the device to an A version firmware (best would be the oldest one, instead of the newest). This makes sure you have a “solid” base (known to work).

Ok, Good advises. thanks.
But, I’ve tried new one. I’ll try to make all works well.

Looks like your connection to [update#4] Updating Meizu Pro6 ChinaMainland (A or Q) to G (Global) SW? [Method1] or [2 was lost, please wait while we try to reconnect.]