yashsingh1/xdaforums huggingface dataset:
[Upgrading, Modifying and Unlocking] slavke1976:
I cant fix them, as connector on motherboard is break ( they break in meizu service france). I am sure all was ok before i send them my phone . When they returned they lose 1 back screw and this connector of volume keys is break.
[Upgrading, Modifying and Unlocking] iicc:
A friend with a bricked MX4 has been tryng with the flashtools and appears this mensaje: "user: this is a secure Base-band Chip! Please select the auhentification file first"
[Upgrading, Modifying and Unlocking] giox969:
Thank you for this thread. I bricked my MX4 just by overwriting the recovery partition, doing a "dd" from inside flymeOS. Now I'm attempting to unbrick it. I used SP Flash Tool 5.1512, your recovery.img and your 1st scatter file, but I get the same message of the previous post :crying:

What should I do now ?
[Upgrading, Modifying and Unlocking] iicc:
Ouch..

Good question... I think that we have to modify the scatter.

Im very busy this days, if you want you can look at the thread about making a cwm for zopo999 to see if they faced this problem.

Other thing, meizu has published the source code of MX4 Ubuntu edition, the hardware is the same so It may helps. I dont know. https://github.com/meizuosc
[Upgrading, Modifying and Unlocking] ahmetkings:
I'd like you shoot a video about the construction.

My phone was soft brick, and I do not know what I have to do for my fix again :(

Edit : My phone meizu MX4
[Upgrading, Modifying and Unlocking] iicc:
Softbrick? If you still have the recovery there is no problem. Just reflash the update.zip again
[Upgrading, Modifying and Unlocking] ruilapa:
Ubuntu MX4 has a /android with

/android/cache/blobs/preloader_m75.bin

/android/cache/blobs/file_contexts

/android/cache/blobs/MT6595_Android_scatter.txt

/android/cache/blobs/secro.img

/android/cache/blobs/logo.bin

/android/cache/blobs/custom.img

/android/cache/blobs/lk.bin

/android/system/boot/android-ramdisk.img

/android/system/etc/firmware/modem_1_ltg_n.img

/android/system/etc/firmware/modem_1_lwg_n.img
[Upgrading, Modifying and Unlocking] iicc:
Could you please make me a favour? Could you upload this? At least the scatter

Many thanks

EDIT: Dont worry, I have it
[Upgrading, Modifying and Unlocking] ruilapa:
You can get the ubuntu image with

ubuntu-device-flash --download-only --channel=ubuntu-touch/devel-proposed/meizu.en --device arale

They are inside one of the downloaded file named "device-*.tar.xz".

I've uploaded latest to

https: //mega.co.nz/#!nIhwUbAL!osl-njsNrsdXExT3sSqrIIDcSeXJEpCiG8eaywyzux0
[Upgrading, Modifying and Unlocking] kkamil:
[MENTION=6582191]iicc[/MENTION]

thx for img files.

I bought MX4 Ubuntu Edition but I wanted to check FlyMe OS. I have download your files:

- recovery.img

- boot.img

- system.img

And flash phone through fastboot.

Let's say Flyme is working but I have observed some strange issues:

- web browser crashes on every/any page loading (its totaly unusable)

- if I add gmail account to e-mail client it's synchronizing (but I can't open any massage - application crashes)

- if I tried to downgrade/upgrade Flyme OS (update.zip from meizufans_eu or flyme_cn), really many versions and many series (A,U,I) and I always get bootloop.

Do you have any ideas what I'm doing wrong ?
[Upgrading, Modifying and Unlocking] iicc:
Glad it helped!

These are Flyme bugs of this rom, I'd recomend to flash a newer version of flyme, 4.5.4 Stable for example.

It is very strange you cant upgrade... in lollipop, the instalation of the rom is very long and it may look as a bootloop. Have you waited a lot of time?
[Upgrading, Modifying and Unlocking] kkamil:
[MENTION=6582191]iicc[/MENTION]

Yes, I have flashed it few times and I wait more than 30 minutes... and nothing.

I think i have tried all options ;)

I have also download few times the update.zip archive in case of lost packages.

Maybe there is a flash tool for MX4 of something ? I don't know if now I can do it by myself ...

Maybe I should flash by fastboot all files you attaches ?

---edit---

One time I tried to flash from recovery (update.zip 4.5.2A)the same version as I had from Your image - and the same thing happen - bootloop...
[Upgrading, Modifying and Unlocking] Naphtha:
go in bootloop because the MBR aren't the same of 4.2.8 A/I and Ubuntu Touch. Don't flash Lollipop.
[Upgrading, Modifying and Unlocking] kkamil:
[MENTION=6296892]Naphtha[/MENTION]

If i flash it by fastboot Lollipop is working. I just can't update it from 4.5.2A to 4.5.4A - I don't think it's MBR problem...
[Upgrading, Modifying and Unlocking] Naphtha:
But go in bootloop(?)
[Upgrading, Modifying and Unlocking] kkamil:
Yes, it goes in bootloop after upgrade.
[Upgrading, Modifying and Unlocking] Naphtha:
mmmmm :confused:
[Upgrading, Modifying and Unlocking] kkamil:
After flashig from [MENTION=6582191]iicc[/MENTION] system.img - I've got version as below.

Numer modelu:MX4

Numer seryjny:75HABKFGTSD2

IMEI:***

Wersja systemu Android:5.0.1 DID]

Numer kompilacji:Flyme OS 4.5.2A (验版) << I've check it it means 'test version' :)

Baseband:MOLY.LR9.W1421.MD.LWTG.

MPV18.P1, 2015/05/17 14:43
[Upgrading, Modifying and Unlocking] Naphtha:
From SP Tool you can flash it?
[Upgrading, Modifying and Unlocking] kkamil:
I don't know if it's makes a difference - flashing by fastboot and by SP Tool ?

As far as I know (but maybe i'm wrong) SP Tool is more risky and I'm not sure if all *.img's and *.bin's files attached in this discussion are correct.

---------- Post added at 09:43 PM ---------- Previous post was at 09:16 PM ----------

Maybe I can compare it with someone:

kamil3@kamil3-CR42-2M-GE40-2OC ~/Pobrane $ fastboot getvar all
(bootloader)	partition-size:userdata: 32000000
(bootloader)	partition-type:userdata: ext4
(bootloader)	partition-size:cache: 2c000000
(bootloader)	partition-type:cache: ext4
(bootloader)	partition-size:system: 81000000
(bootloader)	partition-type:system: ext4
(bootloader)	partition-size:expdb: a60000
(bootloader)	partition-type:expdb: raw data
(bootloader)	partition-size:custom: a00000
(bootloader)	partition-type:custom: ext4
(bootloader)	partition-size:logo: 800000
(bootloader)	partition-type:logo: raw data
(bootloader)	partition-size:para: 80000
(bootloader)	partition-type:para: raw data
(bootloader)	partition-size:secro: 600000
(bootloader)	partition-type:secro: ext4
(bootloader)	partition-size:recovery: 1000000
(bootloader)	partition-type:recovery: raw data
(bootloader)	partition-size:boot: 1000000
(bootloader)	partition-type:boot: raw data
(bootloader)	partition-size:lk: 60000
(bootloader)	partition-type:lk: raw data
(bootloader)	partition-size:seccfg: 40000
(bootloader)	partition-type:seccfg: raw data
(bootloader)	partition-size:protect2: a00000
(bootloader)	partition-type:protect2: ext4
(bootloader)	partition-size:protect1: a00000
(bootloader)	partition-type:protect1: ext4
(bootloader)	partition-size:nvram: 500000
(bootloader)	partition-type:nvram: raw data
(bootloader)	partition-size:proinfo: 300000
(bootloader)	partition-type:proinfo: raw data
(bootloader)	partition-size:preloader: 40000
(bootloader)	partition-type:preloader: raw data
(bootloader)	kernel: lk
(bootloader)	product: M75
(bootloader)	version: 0.5
all: Done!!
finished. total time: 0.019s
[Upgrading, Modifying and Unlocking] Naphtha:
Can you go back from the recovery to the Ubuntu Touch version and repack the rom ? With scatter and other parts? I will flash it on my meizu mx4 android version.
[Upgrading, Modifying and Unlocking] kkamil:
Sure I can go back and recover Ubuntu Touch.

I don't know how to make dumps from partition and how to make scatter ( if you tell me how, I can do it).

... but what with my actual problem? Any ideas ?
[Upgrading, Modifying and Unlocking] iicc:
I have dumped the rom doing this:

adb shell mkdir -p /storage/sdcard0/SPFT

adb shell su -c "dd if=/dev/block/mmcblk0boot0 of=/storage/sdcard0/SPFT/preloader.bin bs=512 count=512 skip=4"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/boot of=/storage/sdcard0/SPFT/boot.img"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/cache of=/storage/sdcard0/SPFT/cache.img"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/lk of=/storage/sdcard0/SPFT/lk.bin"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/logo of=/storage/sdcard0/SPFT/logo.bin"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/recovery of=/storage/sdcard0/SPFT/recovery.img"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/secro of=/storage/sdcard0/SPFT/secro.img"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/system of=/storage/sdcard0/SPFT/system.img"

adb shell su -c "dd if=/dev/block/platform/mtk-msdc.0/by-name/userdata of=/storage/sdcard0/SPFT/userdata.img"

You can try to make the scatter from the firmware.info with MTK DT.
[Upgrading, Modifying and Unlocking] kkamil:
[MENTION=6582191]iicc[/MENTION]

I have installed Ubuntu Touch again (rc5 - from 05.08.2015).

I started making dumps.... I'm on the first one - how long would it take ... ?

---------- Post added at 11:59 PM ---------- Previous post was at 11:38 PM ----------

I'm not sure which block should be dumped to which file ...

lrwxrwxrwx 1 root root 7 Aug 5 21:13 1:0 -> ../ram0
lrwxrwxrwx 1 root root 10 Aug 5 21:13 179:0 -> ../mmcblk0
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:1 -> ../mmcblk0p1
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:10 -> ../mmcblk0p10
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:11 -> ../mmcblk0p11
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:12 -> ../mmcblk0p12
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:13 -> ../mmcblk0p13
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:14 -> ../mmcblk0p14
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:15 -> ../mmcblk0p15
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:16 -> ../mmcblk0p16
lrwxrwxrwx 1 root root 13 Aug 5 21:13 179:17 -> ../mmcblk0p17
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:2 -> ../mmcblk0p2
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:3 -> ../mmcblk0p3
lrwxrwxrwx 1 root root 15 Aug 5 21:13 179:32 -> ../mmcblk0boot0
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:4 -> ../mmcblk0p4
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:5 -> ../mmcblk0p5
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:6 -> ../mmcblk0p6
lrwxrwxrwx 1 root root 15 Aug 5 21:13 179:64 -> ../mmcblk0boot1
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:7 -> ../mmcblk0p7
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:8 -> ../mmcblk0p8
lrwxrwxrwx 1 root root 12 Aug 5 21:13 179:9 -> ../mmcblk0p9
lrwxrwxrwx 1 root root 14 Aug 5 21:13 179:96 -> ../mmcblk0rpmb
lrwxrwxrwx 1 root root 8 Aug 5 21:13 253:0 -> ../zram0
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:0 -> ../loop0
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:1 -> ../loop1
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:2 -> ../loop2
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:3 -> ../loop3
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:4 -> ../loop4
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:5 -> ../loop5
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:6 -> ../loop6
lrwxrwxrwx 1 root root 8 Aug 5 21:13 7:7 -> ../loop7
[Upgrading, Modifying and Unlocking] lj26ft!:
With these files could someone reenable LTE bands on the MX4. Install a new operating system and get rid of flyme? Quote below on the capabilities of the integrated mtk 6595 LTE modem.

"The new MT6595 includes an integrated 4G LTE multi-mode modem with support for category 4 FDD and TDD LTE. The modem also supports 2G and 3G networks and according to MediaTek the device will work with over 30 3GPP RF bands meaning it will support the various LTE bands from around the world."
[Upgrading, Modifying and Unlocking] lj26ft!:
newb- mx4 owner

I have a mx4 in the US it works really well on At&t 3G and HSPA+. Has this thread been successful in creating a custom recovery? Get rid of flyme OS at some point? even with a locked bootloader. I saw the thread about adding lte bands to qualcomm based phones. Looking up information on the MT 6595 the octo core chip has a integrated multi band LTE modem that supports 30 bands.

"The new MT6595 includes an integrated 4G LTE multi-mode modem with support for category 4 FDD and TDD LTE. The modem also supports 2G and 3G networks and according to MediaTek the device will work with over 30 3GPP RF bands meaning it will support the various LTE bands from around the world."

Does this mean with a custom recovery , access to the kernal and experienced developer someone could add band 4,5,17. ??? Totally clueless interested in learning though.

If I could do this i certainly would.
[Upgrading, Modifying and Unlocking] iicc:
Yes, some needs a lot of time (1, 1/2 h) and others are instantaneous.

http://xdaforums.com/showpost.php?p=57891694&postcount=4

lrwxrwxrwx root root 2014-12-16 18:25 boot -> /dev/block/mmcblk0p7

lrwxrwxrwx root root 2014-12-16 18:25 cache -> /dev/block/mmcblk0p14

lrwxrwxrwx root root 2014-12-16 18:25 expdb -> /dev/block/mmcblk0p12

lrwxrwxrwx root root 2014-12-16 18:25 flashinfo -> /dev/block/mmcblk0p16

lrwxrwxrwx root root 2014-12-16 18:25 lk -> /dev/block/mmcblk0p6

lrwxrwxrwx root root 2014-12-16 18:25 logo -> /dev/block/mmcblk0p11

lrwxrwxrwx root root 2014-12-16 18:25 nvram -> /dev/block/mmcblk0p2

lrwxrwxrwx root root 2014-12-16 18:25 para -> /dev/block/mmcblk0p10

lrwxrwxrwx root root 2014-12-16 18:25 proinfo -> /dev/block/mmcblk0p1

lrwxrwxrwx root root 2014-12-16 18:25 protect1 -> /dev/block/mmcblk0p3

lrwxrwxrwx root root 2014-12-16 18:25 protect2 -> /dev/block/mmcblk0p4

lrwxrwxrwx root root 2014-12-16 18:25 recovery -> /dev/block/mmcblk0p8

lrwxrwxrwx root root 2014-12-16 18:25 seccfg -> /dev/block/mmcblk0p5

lrwxrwxrwx root root 2014-12-16 18:25 secro -> /dev/block/mmcblk0p9

lrwxrwxrwx root root 2014-12-16 18:25 system -> /dev/block/mmcblk0p13

lrwxrwxrwx root root 2014-12-16 18:25 userdata -> /dev/block/mmcblk0p15
[Upgrading, Modifying and Unlocking] kkamil:
[MENTION=6582191]iicc[/MENTION]

Dumps from UBUNTU TOUCH 15.04 (rc 15.04 - from 05.08.2015).

After flashing password: 1234

Files under link below, there's no flashinfo.img (it's bigger than partition i'm dumping it):

https://drive.google.com/folderview...BWWVdUZUMxal9jbHZUaTRsdXhGZDVuNmM&usp=sharing

dd if=/dev/mmcblk0boot0 of=/home/phablet/SPFT/preloader.bin bs=512 count=512 skip=4
dd if=/dev/mmcblk0p7 of=/home/phablet/SPFT/boot.img
dd if=/dev/mmcblk0p14 of=/home/phablet/SPFT/cache.img
dd if=/dev/mmcblk0p12 of=/home/phablet/SPFT/expdb.img
/*Can't export*/ dd if=/dev/mmcblk0p16 of=/home/phablet/SPFT/flashinfo.img
dd if=/dev/mmcblk0p6 of=/home/phablet/SPFT/lk.img;
dd if=/dev/mmcblk0p11 of=/home/phablet/SPFT/logo.img;
dd if=/dev/mmcblk0p2 of=/home/phablet/SPFT/nvram.img;
dd if=/dev/mmcblk0p10 of=/home/phablet/SPFT/para.img;
dd if=/dev/mmcblk0p1 of=/home/phablet/SPFT/proinfo.img;
dd if=/dev/mmcblk0p3 of=/home/phablet/SPFT/protect1.img;
dd if=/dev/mmcblk0p4 of=/home/phablet/SPFT/protect2.img;
dd if=/dev/mmcblk0p8 of=/home/phablet/SPFT/recovery.img;
dd if=/dev/mmcblk0p5 of=/home/phablet/SPFT/seccfg.img;
dd if=/dev/mmcblk0p9 of=/home/phablet/SPFT/secro.img;
dd if=/dev/mmcblk0p13 of=/home/phablet/SPFT/system.img;
dd if=/dev/mmcblk0p15 of=/home/phablet/SPFT/userdata.img;
[Upgrading, Modifying and Unlocking] iicc:
Nice!

Could you make an scatter with the MTK Droid Tools?
[Upgrading, Modifying and Unlocking] dazerolui:
Recovery.img

Hey how can i extract the recovery. img from the update.zip file? Vers. Flyme 4.1.1a

i have a mx4 ubuntu edition .. i can not copy the update.zip to my root only to download or Dokuments.. dev mode is on!!!

and in my recovery mode i only see the ubuntu logo with no options!!

can anyone help? sorry form my bad english
[Upgrading, Modifying and Unlocking] iicc:
I think you cant directly from the update.zip, somebody have to have the rom installed to give you the img

I dont know, I dont own an ubuntu mx4
[Upgrading, Modifying and Unlocking] artlov:
Partition /dev/mmcblk0p16 is mounted to many folders, including /home, so dumping to it isn't possible.

You can try to dump it over network to the another location, like this:

sudo dd if=/dev/mmcblk0p16 | ssh user@another.host.com dd of=/home/user/flashinfo.img
[Upgrading, Modifying and Unlocking] kkamil:
Hi,

you have to flash recovery by fastboot if You wish to upload recovery from FLYME use [MENTION=6582191]iicc[/MENTION] files:

recovery.img: https://drive.google.com/file/d/0B1W...ew?usp=sharing

If you wish to upload UBUNTU recovery use:

https://drive.google.com/folderview...BWWVdUZUMxal9jbHZUaTRsdXhGZDVuNmM&usp=sharing

To enter fastboot mode you have to turn off the phone and press POWER+VOL_DOWN

command to run:

fastboot flash recovery recovery.img

Do you want to reinstall ubuntu or try FlyMe OS ?
[Upgrading, Modifying and Unlocking] artlov:
Deleted
[Upgrading, Modifying and Unlocking] kkamil:
https://drive.google.com/open?id=0B...BLTTFyMGFZTFBWWVdUZUMxal9jbHZUaTRsdXhGZDVuNmM

After you upload ubuntu recovery.img from fastboot, You have to boot to recovery, and run:

ubuntu-device-flash touch --device arale --channel ubuntu-touch/rc/meizu.en

10 minutes and You have up and running ubuntu phone :)

It's rc channel - you have updates almoust every week.
[Upgrading, Modifying and Unlocking] artlov:
So, it means that I have to have Ubuntu PC?

I currently have only Slackware and Windows10
[Upgrading, Modifying and Unlocking] kkamil:
Yes, I have ubuntu PC. I have Windows XP in VirtualBox ... probably that's why I can't make scatter file for [MENTION=6582191]iicc[/MENTION] - there are some problems with USB porting.

------------edit

Or maybe USB porting to VB is ok, but I can only connect to adb from Ubuntu...
[Upgrading, Modifying and Unlocking] artlov:
I can't make scatter file as well - "Create scatter file" button is grayed out.

But may be you can try "MediaTek Flash Tool for Linux" on your Ubuntu. Download from this page.
[Upgrading, Modifying and Unlocking] kkamil:
Thx for this tool (I didn't know about it). But there's no option to create scatter.
[Upgrading, Modifying and Unlocking] artlov:
So sad. Then only possibilty to create scatter file manually:

http://xdaforums.com/showthread.php?t=2540400

From my MX4 Ubuntu I have the following starting information (adb pull /proc/partinfo):

Name Start	Size
pgpt 0x0000000000000000	0x0000000000080000
proinfo 0x0000000000080000	0x0000000000300000
nvram 0x0000000000380000	0x0000000000500000
protect1 0x0000000000880000	0x0000000000a00000
protect2 0x0000000001280000	0x0000000000a00000
seccfg 0x0000000001c80000	0x0000000000040000
lk 0x0000000001cc0000	0x0000000000060000
boot 0x0000000001d20000	0x0000000001000000
recovery 0x0000000002d20000	0x0000000001000000
secro 0x0000000003d20000	0x0000000000600000
para 0x0000000004320000	0x0000000000080000
logo 0x00000000043a0000	0x0000000000800000
custom 0x0000000004ba0000	0x0000000000a00000
expdb 0x00000000055a0000	0x0000000000a60000
system 0x0000000006000000	0x0000000081000000
cache 0x0000000087000000	0x000000002c000000
userdata 0x00000000b3000000	0x00000002f7380000
flashinfo 0x00000003aa380000	0x0000000001000000
sgpt 0x00000003ab380000	0x0000000000080000
[Upgrading, Modifying and Unlocking] iicc:
TWRP Touch recovery for MX4!

https://drive.google.com/file/d/0B1WZs_VfDdzYLV80QkFmd3hkT1U/view?usp=sharing

I'm installing it, hope It works :D
[Upgrading, Modifying and Unlocking] iicc:
Nothing, only black screen :(
[Upgrading, Modifying and Unlocking] artlov:
I understand that this is for MX4 PRO only.
[Upgrading, Modifying and Unlocking] iicc:
Only for Meizu MX4 mt6595, but as I said, I only get a black screen when I enter to twrp
[Upgrading, Modifying and Unlocking] Pikard72:
Storage NAND?

Is correct?​
[Upgrading, Modifying and Unlocking] z00k3r:
So what is needed for flashing Ubuntu to the International MX4 ??
[Upgrading, Modifying and Unlocking] kkamil:
I think it depends from phone if you can flash it to Internation (I) FlyMe.

I have flashed my ubuntu phone to FlyMe (A).

Under this link you have directory (Ubuntu 2 FlyMe):

https://drive.google.com/folderview...BLTTFyMGFZTFBWWVdUZUMxal9jbHZUaTRsdXhGZDVuNmM

You have there manual, recovery and firmware.

Aftrer instalation you have to make OTA upgrade.
[Upgrading, Modifying and Unlocking] z00k3r:
But i want to put Ubuntu on the normal international MX4
[Upgrading, Modifying and Unlocking] kkamil:
So you have to change recovery at first:

https://drive.google.com/folderview...BLTTFyMGFZTFBWWVdUZUMxal9jbHZUaTRsdXhGZDVuNmM

After you upload ubuntu recovery.img from fastboot, You have to boot to recovery, and run (from Ubuntu PC)

ubuntu-device-flash touch --device arale --channel ubuntu-touch/rc/meizu.en
[Upgrading, Modifying and Unlocking] z00k3r:
but if i change recovery phone will brick .. ppl from meizufans tested it with backups made by Flashify
[Upgrading, Modifying and Unlocking] jbseal:
Update

Just a correction on your manual you say to rename zip to update.zip but you have to rename to update only, tks for the manual and files:good:
[Upgrading, Modifying and Unlocking] z00k3r:
It depends on how your Systsem is set..

On Windows theres an option where you can Show and Hide the Extensions of files (.zip, .txt, .exe....... For example) if you have the Hide option enabled the part .zip will not show an will not be changed so you have to write "update" only
[Upgrading, Modifying and Unlocking] kkamil:
Why would flashing recovery from fastboot brick the phone ?

Recovery is like other independent system on your phone (you run recovery or you run FlyMe; other case: You run recovery or you run Ubuntu).

You can have recovery from UBUNTU and run normalny FlyMe.

----edit

I heard that some Meizu phone had locked bootloaders., then you have to make one more command before changing recovery:

fastboot-windows oem unlock
[Upgrading, Modifying and Unlocking] z00k3r:
Yes and thats the problem on the MX4 with has Flyme as Stock has locked oder not fully existing fastboot so we're not able to flash smthing with it... Correct me if i'm worng
[Upgrading, Modifying and Unlocking] kkamil:
OK, I have read some threads about it - so if you have locked bootloader don't try to change system.
[Upgrading, Modifying and Unlocking] jbseal:
:good:
[Upgrading, Modifying and Unlocking] jbseal:
Recovery image

Does any one have a flyme recovery image of international version? So i can flash it by fastboot. I'm having problems with sync of google services in chinese version of the rom, and i cant go from A version to I version on this recovery. (The recovery image provided [MENTION=6582191]iicc[/MENTION] its from A version (chinese)
[Upgrading, Modifying and Unlocking] z00k3r:
Here you are .. Its from my own phone backup'd

But i'm on KK only for info

https://www.dropbox.com/s/3dgrtgx04bi7l35/Stock Recovery?dl=0
[Upgrading, Modifying and Unlocking] jbseal:
Tks a lot mate. :good:

Didn't work, i believe file is to small usually flyme recovery has 16 mb, maybe something missing.
[Upgrading, Modifying and Unlocking] z00k3r:
Screenshot of flashify

https://www.dropbox.com/s/49zuxdjm17yzch1/fkash.jpg?dl=0

Made a new backup with lollipop

https://www.dropbox.com/s/i5zey8hv5ok8tg2/Stock Recoveryv2?dl=0
[Upgrading, Modifying and Unlocking] jbseal:
Going to try this one then, tks mate :good:

Doesn't work to, i think the problem is my mx4 being Ubuntu touch i can only flash the recovery provided by [MENTION=6582191]iicc[/MENTION] A version of flyme Kitkat, lolipop doesn't flash, when i reboot to recovery the phone jumps from Meizu logo to Flyme (normal reboot).
[Upgrading, Modifying and Unlocking] z00k3r:
This phone is crazy .. No working flashing tools

No roms

No kernels

Nothing

And meizu isn't able to create a flyme rom that works good and without bugs

I bought when it came out because everyone said its a great phone and battery time is top..... Nothing is working good on this device
[Upgrading, Modifying and Unlocking] jbseal:
I just bought this phone because of Ubuntu, its a nice piece of hardware but a poor Android experience, and Ubuntu its far from being ready for daily driver, so Meizu its not going to see my money again that's a fact.
[Upgrading, Modifying and Unlocking] artlov:
Agree. It's the reason why I flashed FlymeOS Android over Ubuntu.
[Upgrading, Modifying and Unlocking] thyrth:
Artov (Procedure?)

Artov, Me too want to install the Android ROM for now. Can you give some more tips or what procedure you did follow?

Regards :angel: