yashsingh1/xdaforums huggingface dataset:
[Meizu MX] maxegawa:
Yes, done that Windows Driver Signature thingy already. BTW, I use W8.1.

Just tried to do it like you've said, pressing the download button after connecting the phone The SPFL gave me this error:

BROM ERROR: S_COM_PORT_OPEN_FAIL (1013)

[COM] Failed to open COM port.

[HINT]:

:(
[Meizu MX] realjavajim:
Can't boot into TWRP recovery

I can't get in the TWRP recovery:(

I am always booting into the "normal" Flyme recovery. Any solutions?

Edit: I re-flashed the recovery:) That was the solution
[Meizu MX] Moyster:
I'm pretty sure it's meant that way, if you have flashtool opened and ready to flash, press "download" and plug the phone

open flashtool => phone unplugged => config FT and press download => plug the phone

It seems (and it's my opinion only) that since that mode needs the phone to be shut down and powered up, then it would make sense that it only stay a few seconds only before booting normally (too many people would cry their phones can't reboot if they are plugged on usb, since it would stay on the bootloader mode)

Anyway, I wasn't careless to run flashtool under wine, so that's how I did under Windows 10 (64bits) without disabling any driver signatures whatsoever.

Pretty sure that's not needed ;)

don't plug your phone, turn it off (shutdown), press vol up slightly before pressing power, wait for the vibration and release. You're not doing the combo properly ;)
[Meizu MX] maxegawa:
Thanks, Moyster, it really worked. It was my mistake for not following the tutorial thoroughly.

Just installed Cyanogenmod right now, we'll see how everything goes! :)

A big thanks to everyone who made this happen! -Max, from Spain.
[Meizu MX] rokas66:
does anyone might why my phone doesn't appear in the device manager as an unknown device?
[Meizu MX] dinkan01:
Latest build 12... Used 10 lately... It got many bugs...

Build 12 ( second one on the dwld list )

Thanks
[Meizu MX] zerogeex:
Boot loop?

Hi,

I followed all the steps up until the flashing of the cm rom everything seems fine, but when i flash the rom it stuck forever on "Patching system image unconditionally..."

After this I press the power button until it reboots. Then it shows the meizu logo with normal boot and after this it reboots back into twrp recovery.

The same happens when i select boot to system.

Pls help me out:crying:;)
[Meizu MX] LBA97:
First you should reinstall your TWRP. You can use SPFlahstools if you can't access to the OS.

If that doesn't work mabe you could try installing the new CM release. Maybe it was an incorrect download. I hope it helps, tell us if it does, and good luck :)
[Meizu MX] zerogeex:
After downloading all the possible ROM's and transfering them with the TWRP disk mount feature to my phone I tried the older RC version 12 and this one booted.

Wasn't really worried since I could still enter the TWRP but it is curious though since I'm not too sure what I did right or not or if it was the newer ROM.

I also didn't reinstall TWRP so I don't know, I did fidle a bit with not wiping cache and stuff trying stuff I found all over in other topics :P

Ultimately I think it was not mounting the system cause whenever I went to mount menu it wasn't ticked as mounted...will have to look more into this :D

SO: After redownloading the stable 1 I flashed it succesfully XD So all good :D
[Meizu MX] MvPGEO:
Any news about mx5? This is a better phone how come not so many ppl interested?
[Meizu MX] hardKNOXbz:
also note sp flashtool no longer detects my device
[Meizu MX] numpea:
Make sure the drivers are installed correctly to flash the firmware via sp flashtool you need to flash first "temp_unlock_secro.img" as unlocking bootloader then flash the firmware :good:
[Meizu MX] hardKNOXbz:
I believe indeed something's up with the drivers.

I can only get it to connect as below. But not with the preloader driver.

I've uninstalled and removed multiple times with usbdeview and used the drivers from this instruction as well as from other sources. :crying:
[Meizu MX] numpea:
Is the device turning on ? Can you access recovery or fastboot mode ?
[Meizu MX] hardKNOXbz:
No buddy, unable to turn on or access any recovery or fast boot....

I'm done for huh?
[Meizu MX] numpea:
it's still can be back to life the unbrick firmware you will find it at https://mega.nz/#!2d4kwJAR!4u5ZxXM_m6v3zf6mxWb9rGied6Uqm2FcbVhI-r3yoqY

with sp flash tool make sure you select temp_unlock_secro.img and hit download before connecting usb cable after you are done with temp_secro.......

disconnect usb cable and load the firmware with sp flash tool and select format all+download (you will loose your imei but you can get it back) hit download and connect usb cable
[Meizu MX] hardKNOXbz:
Ok this is funny, my dad who has absolutely no experience in phone flashing has restored my phone. I have had fairly good experience of flashing mods and Roms for years and am in shock. He pushed the home button and power button for 30 seconds and the phone booted right up. Holy crap.!!!!

In desperation yesterday I thought I pressed and held all combination of buttons including this one with no result.

Anyways another good thing that happened is that my dad had already given me his Huawei p8 that he was not using. Hehe. Not sure if I will attempt to do this again. I will give this phone to my wife, Perhaps I will try the "in device" method if I do. Thanks guys.
[Meizu MX] hardKNOXbz:
Probably final update, flashed recovery with flashify and installed cm and this is amazing... You guys are great... The best thing to happen to this device was getting rid of flyme.... Amazing work people.
[Meizu MX] hellenicsun:
What could I have possibly done wrong so that to end up with Meizu's recovery and not TWRP? I mean, boot-loader unlocking went fine (little message to the left end of the screen) and when I flashed recovery.img through SP Flash, again all went OK based on the PC on-screen message. But still, I didn't end up with custom recovery. Should I repeat the recovery.img flash process?

Ah, never mind. Just repeated the process.
[Meizu MX] zoranstojanovic967:
When I connect my phone (which is OFF) to PC, it shows as VCOM driver in Device Manager for 1 sec. After that, phone starts charging (with a short vibrating and battery animation on display) and driver disappear from Device Manager. Is that normal behavior? Not seems to me.
[Meizu MX] LBA97:
It is. If you want to unlock the bootloader, click the download button of SP Flashtools before you connect the device to your pc. Remember keeping the volume down button pressed.
[Meizu MX] emilkawa:
what about model M571U? Can I use this solution?

Emilkawa
[Meizu MX] LBA97:
Some users have already unlocked the bootloader of some M571U. Good luck! :)
[Meizu MX] :
I'm sorry! Didn't see the tutorial properly! ?

Btw, this is working completely fine! Love ? you all! Thank you
[Meizu MX] rokas66:
anyone?
[Meizu MX] LBA97:
It does appear as unknown or it doesn't? Does it appear in any other way? Have you installed the drivers properly?
[Meizu MX] iqqdd:
Thank you developer!

Thank you developer, that's a quite good job!!!

I'm going to use it as my permanent rom but I have to tell you about an issue and I want to talk about the m-button.

Well, I only found a bug: when I want to unlock the phone the lock screen doesn't appear, it goes straight to the home screen or the app I've been using. In the other hand we have de m-button configuration, I suppose that it comes from a hardware limitation or something like that but, it is possible to launch the app switcher by a long pressure over the capacitive button instead of the physical one?
[Meizu MX] LBA97:
I wish I were a developer xD

You should report that bug at Moyster's Github. You can find it in the main post of his ROM

About accessing to recent apps through long press of capacitive button, try xposed additions, I think it has that feature.
[Meizu MX] haliltae:
M571H

Hi can i install this rom to my m2 note m571h , and can i use this bootloader unlocking methot on my m571h
[Meizu MX] LBA97:
Yes, you can.
[Meizu MX] haliltae:
Flyme version

Thanks, is it important flyme version 4 or 5
[Meizu MX] LBA97:
Not actually. Good luck and happy unlocking :)
[Meizu MX] SomeYoungGuy:
Hi,

I need help. Trying to flash a Flyme rom (5.1.12.0G).

TWRP flashes CM based roms quick and correctly, but when i try any Flyme Rom, it just stays stuck on "Patching system image unconditionally", the progress bar on the bottom is full, but even after leaving it in the whole night, it just stays stuck there.

It wasn't like this last week, i could flash Flyme and CM back and forth quickly.
[Meizu MX] LBA97:
Have you deleted the preloader files? Maybe you're flashing the wrong zip
[Meizu MX] SomeYoungGuy:
hmmm i haven't deleted them yet. Gonna try it out later.

I flashed the resurrection remix rom, worked well at first, but noticed that i wan't getting any signal even if the sim is recognizrd.
[Meizu MX] SomeYoungGuy:
i deleted the 3 preload files. still getting the error...

the zip i got was from here:

https://forum.meizufans.eu/topic/7167/flyme-os-5-1-12-0-stable-m2-note
[Meizu MX] LBA97:
Why don't you try downloading it from the original web?

http://www.flymeos.com/firmwarelist?modelId=3&type=1

Don't forget deleting the preloader files or you'll get a bootloop.
[Meizu MX] LBA97:
I've just updated the info in the main post with some useful guides more. Hope it helps!
[Meizu MX] SomeYoungGuy:
Downloaded... still getting the error.

Assert failed: package_extract_file("preloader_no.img", "/tmp/preloader.img")

Updater process ended with ERROR: 7

Error installing zip file '/extSdCard/update.zip'

Update:

Saw the update you made to the 1st post.

Ignored the error, boot logo now the Flyme Balloon. fingers crossed, hope this works.

Booted properly. Phone is back on Flyme again...but still not getting any signal, even if the IMEIs are intact.

The carrier shows, but it keeps saying that there is no signal and cannot be chosen in the settings.

Ok, found out, that the sim was the problem. lol
[Meizu MX] LBA97:
Quite interesting xD

I'm happy you found that solution! :D
[Meizu MX] SomeYoungGuy:
thanks. Haha

After so many flashes, i though of trying out the sim to check.

Put it in my Zenfone 3, no signal. Gonna go out tomorrow to get a new sim. I gave this M2 Note to my kid for christmas.
[Meizu MX] Bggrof:
IMEI

I followed the procedure, no issues during the process but unfortunately imei is empty, and of course phone does not detect sim card. 571H Please guys help!!! :( I flashed cm 13 build 4
[Meizu MX] numpea:
CM13 build 4 has a bug try build 3 aka beta 3 aka "GestAbit"

[MENTION=6003981]LBA97[/MENTION] please update the link to the unbricking firmware in the OP

Firmware
[Meizu MX] LBA97:
numpea is right, the latest beta has that error. Flashing the previous beta will solve the problem.

Updated, thanks :)
[Meizu MX] dongle.ebrywer:
Can't charge while powered off

Every time I powered off my phone and then plug a charger it does the usual thing, it powers the screen with the battery in the center of the screen and a "Powered Off Charging Mode" text at the bottom left but then proceeds to normal boot. In addition, when I unplugged the charger is suddenly powers off the device. I don't know if this is caused by TWRP,CM12.1 or its a bug of somewhat, if so can you tell me.
[Meizu MX] goodoane:
It was a kernel problem last year, you have to flash a new updated boot.img(or only kernel) or to change your rom. To update your ROM, use cm13 (lineageos 13) or other ROM.
[Meizu MX] kamango:
One quick question. Tutorial says for flashing recovery via flashify:

""+ Tap Recovery Image

+ Choose a file

+ Find TWRP zip and flash it

I cant select zip when choosing recovery image. Should i unzip it and flash recovery.img, or should i flash twrp.zip with zip file flashing?
[Meizu MX] numpea:
Unzip and flash recovery.img with flashify
[Meizu MX] LBA97:
Just corrected it. I didn't notice I hadn't explained it right. Thanks and happy flashing.

Thanks to [MENTION=6520775]numpea[/MENTION] again, who seems running the thread much better than I :P
[Meizu MX] tursey:
But this way bricks the phone...

Flashing stock recovery in flashify + installing stock Flyme by stock recovery ---> Always bricked... Am I doing anything wrong? Thanks!
[Meizu MX] goodoane:
All of this need to be flashed from recovery. From TWR flash stock recovery, then reboot in stock recovery, then connect to PC upload stock update.zip under recovery partition showed on your PC and flash from phone.
[Meizu MX] dongle.ebrywer:
Do we have here/you have the updated boot.img which is can be flash via recovery for cm12? I'm still divided to flash or not lineageos13 because it is not yet a stable build.
[Meizu MX] tursey:
NO, tried again and brick again... This way DOES NOT RUN.
[Meizu MX] LBA97:
I don't know how to help you. This method works for everybody. Are you flashing a modified zip instead of the original one?

If even flashing the zip from the stock recovery bricks your phone, install a modified zip from twrp and keep the bootloader unlocked.
[Meizu MX] yiannisoooo:
I had the same problem and i found out at 4pda forum that i have to flash 4.5.4.2i. I did and the phone turned on and the bootloader was locked again. the problem is that the phone was in bootloop this time (i didnt check clear data). i got in stock recovery connected to pc and load latest g version in recovery partition, upgrade and everything ok. Bootloader locked.
[Meizu MX] maestro_787:
SIM (IMEI) issue

Hi,

first of all thanks for the great guide. It let me to easily install lineage OS on my Meizu M2 note!

Unfortunately I'm having some trouble with SIM card.

I'm getting two different behaviors:

1. With CM13 the SIM card is not recognized at all

2. With CM12 the SIM card is recognized but it cannot register on network.

I suspect the issue is related to a wrong IMEI: it's currently showing me an alphanumeric string with also special characters.

For sure the problem is not the SIM because I tried:

1. My SIM on other devices

2. Other SIMs with my device

Could someone help me?

Thanks,

Armando.
[Meizu MX] LBA97:
Hi Armando. You have to know that the latest cm13 builds have a sim issue. There are two solutions:

1. Flashing the first cm13 beta, booting, rebooting to recovery and flashing the latest cm13 beta

2. Flashing the brand new and fantastic cm14 beta from Moyster from here:

https://xdaforums.com/meizu-mx/orig-development/rom-lineageos-14-1-meizu-m2-note-t3551287
[Meizu MX] harold.goldensky:
Bricked

i accidentally bricked my phone and my computer can't install any drivers even the sp flash tool can't detect it. any idea?
[Meizu MX] LBA97:
I don't know any other way to unbrick it. Go to a library, ask a relative, but you need a pc.
[Meizu MX] numpea:
you have to disable driver signature verification to install drivers search on google how to install Mediatek preloader drivers

then continue with the Tutorial
[Meizu MX] harold.goldensky:
it's now back to normal. thanks

---------- Post added at 11:41 PM ---------- Previous post was at 11:31 PM ----------

i'm having a problem with my flyme update, when im trying to update my flyme os with new update, it always need to flash the stock recovery but i already lock the bootloader. any idea about this one?
[Meizu MX] geri96:
hi,

can I unlock my bootloader if my phone originally was an A version but I made it to an I?
[Meizu MX] LBA97:
I think that if you were able to change the version that means you don't own a C version, but I'm not sure. Try looking in the page you bought it from or at its box.
[Meizu MX] geri96:
I looked it up on it's box and was an U version....since then I installed TWRP and flashed the rom. Thanks for your advice.
[Meizu MX] LBA97:
You're welcome, have fun! :)
[Meizu MX] Baijoosharma:
any idea if not showing anything only a blank screen no logo no fast boot
[Meizu MX] numpea:
You device is bricked, you have to flashe unbrick firmware with flashtool
[Meizu MX] Baijoosharma:
i think dead not turning on :D
[Meizu MX] numpea:
Yes it's bricked the PC detects it but it doesn't turn on
[Meizu MX] Baijoosharma:
no PC also mot detecting when charging its heating normally :D
[Meizu MX] DrGrozozo:
My device is from China, info on device saying only m2note, software is android 5.1 flyme 4.5.3U, which M571 is that and can I use this method? I really want to change this rom since it is full with bloatware that cannot be uninstalled or disabled. Thanx in advance.

Sent from Sony M5
[Meizu MX] LBA97:
You should look in the box. M571 is the model number and cannot be seen from the device,but it should appear in the bill, the order or in the phone's box. Good luck!
[Meizu MX] Alucard:
Please HELP,I BRICKED MY DEVICE,I format all and then tried to flsh twrp recovery and it says dram missed or failed,PLEASE HELP.
[Meizu MX] Ashutosh Sundresh:
thanks!
[Meizu MX] srjkumar96:
Unable to unlock the Bootloader !

I'm not able to unlock the bootloader. It always gets stuck on this screen !

I have HP laptop with Windows 10.
[Meizu MX] Ashutosh Sundresh:
Connect your phone.
[Meizu MX] srjkumar96:
You're joking right ?

Did you really reply that ? I mean c'mon. You've got to be kidding me ?

Dude. I have connected my phone and then done that. It's not happening.

I tried in all three modes :

1. Power On Mode

2. Power Off Mode

3. Fastboot Mode

Still not happening.

Btw, my phone is on Flyme 6.1.
[Meizu MX] Ashutosh Sundresh:
Sarcasm
[Meizu MX] LBA97:
Did you do it right like in the tutorial? It should work flawlessly. Have in mind that you should keep pushing the vol- button with the device powered off before connecting it to the pc, and that before connecting it to the pc you should hit the download button. That way it will work for sure.

Make sure you have all the drivers connected to the pc too.
[Meizu MX] Ashutosh Sundresh:
Try downgrading to Flyme 5 or 4
[Meizu MX] srjkumar96:
An unexpected bug !

I was finally able to unlock the bootloader and installed CM13. But unfortunately,it is not recognizing my SimCard. What should I do now ?

Update : Found the solution !
[Meizu MX] Alucard:
Mine says error when trying to flash,how did you solved it?

Says error when trying to flash temp secro,drivers are installed.
[Meizu MX] srjkumar96:
What kind of error are you getting ?

Post a screenshot if possible !
[Meizu MX] Alucard:
Security secure usb dl image signature verify fail 6046 ,msp error code 0x00.
[Meizu MX] denzelque:
Asking

May i know if i can still install other firmware using its internal memory because i lost my sim tray thats why im afraid to do it without micro sd inserted on my phone?
[Meizu MX] ksraghavendra:
Pls help! I'm getting the same error. M2 Note running Flyme 6.1.0.0G and using Windows 10 (driver signature enforcement disabled, tried without disabling as well).

Screenshot - [IMG="Error 6046"]https://i.imgur.com/jGg09IL.jpg[/IMG]
[Meizu MX] Alucard:
I believe i solved it by not flashing temp secro first but going to step 2 and after that flashing through sp flash tool twrp,but its been sometime but im 90% sure thats what i did.Tell if that worked for you.
[Meizu MX] ksraghavendra:
I tried that as well. Didn't work.

I got the "normal boot" "fastboot" small text on my boot screen but every time I try to do a recovery boot it goes to flyme bootloader and not twrp.
[Meizu MX] Alucard:
Flash twrp recovery imeddiatelly and wipe everything at first twrp boot.And then flash rom.
[Meizu MX] ksraghavendra:
Managed to flash Lineage atlast! What worked for me, used adb/twrp commandline installation given here - https://www.xda-developers.com/how-to-install-twrp/ Thanks!
[Meizu MX] aaawqw:
Well, if you don't select format all+ download, your IMEI, etc,will not just disappear. And as for the product sn, if you've lost it, use dd if of **** to backup proinfo out, take a working one as an example, and compare them in Beyond Compare. You'll see the SN in there.
[Meizu MX] xiaowei666:
I want to know if I unlock bootload,my phone'data will be wipe?:crying:

---------- Post added at 06:44 PM ---------- Previous post was at 06:43 PM ----------

And if I want to unlock bootload,must be have root?:D
[Meizu MX] ChinaHeart:
please

don't download mega.nz file......

chinese great wall.!!!
[Meizu MX] x X x:
So I fuked up my Meizu M2 Note. Trying to unlock bootloader, I flash "secro.img" instead of "temp_unlock_secro.img" as first file, got some errors, and now my phone is not recognized by Windows - "Unknown USB Device (Device Descriptor Request Failed)", I cannot start it in normal/fastboot/recovery mode. What should I do now?

Edit:

OK I fixed my phone using this tuttorial:

https://www.youtube.com/watch?v=S1kFRfKzk6U

Btw. when device manager says that unknown USB device is conneceted, while connected to usb press and hold menu+power button - device should be correctly reconnected.
[Meizu MX] salvmason:
Hi, is it possible to repost links for bootloader unlocking? Thanks.
[Meizu MX] aaawqw:
Hi,

just updated the link in my post as well:

https://xdaforums.com/meizu-mx/orig-development/tutorial-meizu-m2-note-bootloader-t3429843
[Meizu MX] salvmason:
Thank you very very much!
[Meizu MX] Olofaiolo:
Hi guys, Can I just unlock the bootloader, install twrp and flash magisk to gain root without use a custom rom? I mean staying on flyme official, or do I risk to get bootloop? Thanks
[Meizu MX] aaawqw:
I won't recommend that since this is a relatively old phone that many users reported new versions of Magisk has compatibility issues in the past. If you only need root, Meizu allows you to root the phone once you login with a Flyme account and there's no need for BLU/TWRP. If you really need Magisk modules, and the new versions doesn't work, maybe try older versions (e.g. 17.x/19.x). You can do BLU, flash TWRP and still use the Flyme stock rom, the main issue is Magisk's compatibility with such an old phone. I don't have the phone anymore and that's all I can tell you :)
[Meizu MX] Lieta:
The link doesn't work.

I found TWRP-3.0.2-3-Meizu M2 Note.zip, flashed it, tren tried flashing LineageOS-14.1 Build 25 (Stable 9 "PrettyLate"), but it failed with error "unsupported command "Log"" or something. Is there a working TWRP for m2 note?
[G3 Q&A, Help & Troubleshooting] varu:
I have a D852 bootlooping at the "Optimizing" stage, this happened after they pushed an OTA update. I'm not concerned about the data on it (keeping good backups ftw!). Here's what I've tried so far:

Tools: LGUP, LGFlashTool 1.8.1, LG Flash Tool 2014

KDZs: the one provided by LG for the specific IMEI of the phone, Rogers D85230b.kdz

TOTs: LGD852AT-01-V10b-302-720-JUL-15-2014+0.tot

Regardless of what I flash, it bootloops at the "Optimizing app" stage. The stage does complete, followed by "starting apps..", a brief screen blanking (backlight remains lit), and a restart of the boot logo animation, followed by a repeat of the "Optimizing" stage. Have tried Normal, CSE, Refurbish, Upgrade modes in the various tools, all produce the same result. What am I doing wrong? Is this thing a perma-brick?

EDIT: A few extra details:

When flashing a KDZ or TOT, immediately after flashing through download mode it runs through a process where it sits at the bootloader for a few minutes, then the "open-hood" Android shows up (recovery from what I've experienced with other phones). This process lasts *very* little, 2 seconds at most. I have of course tried the phone's own "recovery" process which is supposed to clear data (booting with holding power & volume down), with no difference in results. I have tried the LG PC Suite as well, same results.