[TUTORIAL] BOOTLOADER UNLOCKING FOR MX4/M1 Note

Search This thread

slowsunset

Member
Sep 7, 2015
40
24
Hello xda, here's guide for bootloader unlocking for Meizu MX4 and Meizu M1 Note.


All your actions with the phone is at your own risk. The authors are not liable. This is just your choice.


PLEASE read full instructions before you start.
RECOMMENDED ONLY FOR EXPERIENCED USERS.
This was tested ONLY on MX4 and M1 Note (MX4 PRO - NOT WORKING)


Archives contains:

  • custom-recovery_mx4_philz - custom recovery philz touch 6 for MX4
  • custom-recovery_m1note_philz - custom recovery philz touch 6 for M1 Note
  • gscript - folder with unlocking script
  • patched-stock-recovery_mx4 - patched stock recovery for MX4 (who wants to flash International (index I) firmware to chinese MX4 (index A), or flash stock-customs (deleted chinese soft, game center etc.))
  • patched-stock-recovery_m1note - patched stock recovery for M1 Note (same as MX4)
    *********************************** (deleted digital signature checker and checking version of your MX4 / M1 Note (chinese/international))
  • patcher - loader patcher
  • terminal emulator - easy terminal emulator




UNLOCKING PROCESS:

  1. Flash clean stock firmware, do this only on android version: 4.4.2 firmware on MX4 (4.2.8.2A) / 4.4.4 firmware on M1 Note (4.2.0.5A) VERY IMPORTANT!!!
    **************************************************************** (Android 5.0/5.1 firmwares uboot not patch)

  2. Get ROOT by standard method (flyme account). SuperSu NO NEEDED
  3. Unpack on your disc (on PC) archive with firmware which you used to flash on your MX4 (4.2.8.2A) / M1 Note (4.2.0.5A) VERY IMPORTANT!!!
    • Place in a folder with unpacked archive (p.3) file "Meizu_Patch.exe" from folder "patcher" of your downloaded archive and open this with administrator rights.
      -Theoretically, antiviruses can alarm to packer which patcher was compilated (but Dr.Web is fine) / but antiviruses recommended to be closed.
      -If you are afraid about viruses and trojans, skip this step....and all the following.
    • If all goes well - we see a flashing green "SusseccFully Patched" in the patcher round window - continue.
    • If no and you see inscription "Patching Failed!", RED - STOP - something goes wrong and if you continue - BRICK!!!

  4. Delete from this folder 2 files: "Meizu_Patch.exe" and "uboot.img.bak".
    • Create a folder with name "UNLOCK" in phone root directory (SD card)(DCIM folders, Picture, Music, data etc.) and copy in already patched loader file "uboot.img" from firmware folder from PC (where we started our patching (unpacked firmware)).
    • Pack this firmware (on PC) back in archive (using 7-zip/winrar) with name "update.zip" (default flyme firmwares) - could be useful.

    • Copy a folder "gscript" together with the contents in phone root directory (SD card).
    • Install "terminal emulator" on your phone from "gscript" folder.
    • Open terminal and write
      su
      sh /sdcard/gscript/unlock.sh
      *Important!!* Wait 3 minutes for script action
    • Reboot your phone by command reboot . If it succesfully boot - congratulations, all right.



Further:

*WARNING!!!* All operations of modules flashing (recovery.img, boot.img etc.) doing ONLY BY STANDARD METHODS, by FASTBOOT command "fastboot flash"!! NOTHING ELSE!!

  1. You can flash modified stock recovery from folder "patched-recovery" for MX4/M1 Note (your needs) by command: "fastboot flash recovery patched_recovery.img" and restrict the international version of firmware (in update.zip you can do all changes you want - signature will not check).
    • *CARE!!* If you flash index I firmware with patched recovery, USE Titanium or others to delete/freeze "System Update" from firmware. OTA UPDATE WILL BRICK YOUR DEVICE!!!
    • *CARE!!* Patched recovery will be rewritten on the usual stock recovery by first full android load, then after command "fastboot flash patched_recovery.img" turn off your phone and hold button "volume up" (+) and "power" before the phone starts (or delete "recovery-from-boot" as alternative).
  2. You can flash custom recovery - and use it for your needs.
    • *CARE!!* DON'T try to flash stock meizu firmwares from any custom recovery, we have patched stock recovery for that.
    • ALWAYS DO A BACKUP!!


VERY IMPORTANT Notes:

  1. Not allowed "strange" combinations (for example flashing not patched loader and custom recovery). If system goes to bootloop - exit from "half-brick" could be very hard, if it all possible.
  2. Loader patch and reverse packing stock firmwares should be done everywhere - it will save your time and nerves. You should avoid version mismatch of preloader - uboot - boot.img in smartphone firmware. Effects, bugs, lags can be very different.
    • *IMPORTANT!!* Then, if we flash "custom firmware", it should NOT CONTAINS "uboot.img" and "preloader.bin". All this can be flashed only in stock (modified) firmware, ONLY FROM STOCK or PATCHED STOCK recovery.
  3. "uboot.img" CAN'T BE flashed by fastboot!! Also not allowed doing experiments with "preloader.bin". BRICK probability is very high!!






Original source:

Authors:
kirill8000 -
kkk4 -

Some thanks:
Paypal - [email protected]
 
Last edited by a moderator:

Naphtha

Senior Member
Jan 2, 2015
886
409
Crotone
Hi guys,
first of all thx... I want test it but i have missed 2 points:
-After unpacking and patching the firmware, i need to move the "gscript with the unpacked firmware" on root folder? Or create a new folder ?
 
  • Like
Reactions: iicc

koaaN

Senior Member
Jan 3, 2011
382
602
Lesjöfors
www.facebook.com
Hi guys,
first of all thx... I want test it but i have missed 2 points:
-After unpacking and patching the firmware, i need to move the "gscript with the unpacked firmware" on root folder? Or create a new folder ?

New folder's in root of your phone. (a folder called "gscript" with the files "unlock" and "gscript.apk in" AND a folder called "UNLOCK" with the uboot.img you patched :)
 
Last edited:

Naphtha

Senior Member
Jan 2, 2015
886
409
Crotone
"Copy a folder "gscript" together with the contents in phone root directory" we aren't able to install the apk from root directory...only from sd
 

Naphtha

Senior Member
Jan 2, 2015
886
409
Crotone
Look
 

Attachments

  • S50915-192153.jpg
    S50915-192153.jpg
    142.4 KB · Views: 5,368
  • S50915-192157.jpg
    S50915-192157.jpg
    152.5 KB · Views: 4,632
  • S50915-192206.jpg
    S50915-192206.jpg
    67 KB · Views: 4,391
  • S50915-192216.jpg
    S50915-192216.jpg
    77.1 KB · Views: 4,313
  • S50915-192401.jpg
    S50915-192401.jpg
    93.4 KB · Views: 4,631
  • Like
Reactions: triasafrudin

Naphtha

Senior Member
Jan 2, 2015
886
409
Crotone
when i execute "unlock.sh" :
The phone afther this boot well but no "Program should show 2 window with root access for gscript, Agree! Wait for one-two minutes for script action (until the yellow lines in the gscript window)."
 

Attachments

  • S50915-192942.jpg
    S50915-192942.jpg
    87.8 KB · Views: 2,670
  • S50915-192946.jpg
    S50915-192946.jpg
    70.1 KB · Views: 2,534
  • S50915-192949.jpg
    S50915-192949.jpg
    84.2 KB · Views: 2,579

slowsunset

Member
Sep 7, 2015
40
24
sure it must be on sd card, i just translated the root directory like sd because we physically haven't it. Logic? nope.
so folder "UNLOCK" should be on SD card and should contains "uboot.img" from patched firmware
folder "gscript" (with .apk and unlock.sh script) should be there too (on SD card)

fixed now and replaced steps.
 
Last edited:

Naphtha

Senior Member
Jan 2, 2015
886
409
Crotone
The recovery work well and i care i can install the rom from ubuntu desktop...
if all go to hell, i can reinstall the recovery patched from fastboot and back to the firmware modified from recovery.... :')
 

iicc

Senior Member
Apr 10, 2015
370
141
I think the problem is related with Lollipop, that is why we only can do with mx4 and m1 note, because they have Kitkat Flyme roms.
 

iicc

Senior Member
Apr 10, 2015
370
141
You guys are wonderful. So many months waiting for it, and so many months trying to unlock it.

Now is real
0o78psgh.jpg


Hope you can do it for Lollipop, the rest of Meizu phones. I know you can.
Thanks again

---------- Post added at 03:12 AM ---------- Previous post was at 02:34 AM ----------

Maybe with bootloader unlocked my TWRP works, if anybody wants to try it... https://drive.google.com/file/d/0B1WZs_VfDdzYYjRlTGZFR2w3eUU/view?usp=sharing

For MX4!
 
Last edited:
  • Like
Reactions: ach4m0

zspudsz

Member
Apr 15, 2012
5
0
help

How can I unlock the bootloader of a bricked MX4? cant access anything than fastboot. please help
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Hello xda, here's guide for bootloader unlocking for Meizu MX4 and Meizu M1 Note.


    All your actions with the phone is at your own risk. The authors are not liable. This is just your choice.


    PLEASE read full instructions before you start.
    RECOMMENDED ONLY FOR EXPERIENCED USERS.
    This was tested ONLY on MX4 and M1 Note (MX4 PRO - NOT WORKING)


    Archives contains:

    • custom-recovery_mx4_philz - custom recovery philz touch 6 for MX4
    • custom-recovery_m1note_philz - custom recovery philz touch 6 for M1 Note
    • gscript - folder with unlocking script
    • patched-stock-recovery_mx4 - patched stock recovery for MX4 (who wants to flash International (index I) firmware to chinese MX4 (index A), or flash stock-customs (deleted chinese soft, game center etc.))
    • patched-stock-recovery_m1note - patched stock recovery for M1 Note (same as MX4)
      *********************************** (deleted digital signature checker and checking version of your MX4 / M1 Note (chinese/international))
    • patcher - loader patcher
    • terminal emulator - easy terminal emulator




    UNLOCKING PROCESS:

    1. Flash clean stock firmware, do this only on android version: 4.4.2 firmware on MX4 (4.2.8.2A) / 4.4.4 firmware on M1 Note (4.2.0.5A) VERY IMPORTANT!!!
      **************************************************************** (Android 5.0/5.1 firmwares uboot not patch)

    2. Get ROOT by standard method (flyme account). SuperSu NO NEEDED
    3. Unpack on your disc (on PC) archive with firmware which you used to flash on your MX4 (4.2.8.2A) / M1 Note (4.2.0.5A) VERY IMPORTANT!!!
      • Place in a folder with unpacked archive (p.3) file "Meizu_Patch.exe" from folder "patcher" of your downloaded archive and open this with administrator rights.
        -Theoretically, antiviruses can alarm to packer which patcher was compilated (but Dr.Web is fine) / but antiviruses recommended to be closed.
        -If you are afraid about viruses and trojans, skip this step....and all the following.
      • If all goes well - we see a flashing green "SusseccFully Patched" in the patcher round window - continue.
      • If no and you see inscription "Patching Failed!", RED - STOP - something goes wrong and if you continue - BRICK!!!

    4. Delete from this folder 2 files: "Meizu_Patch.exe" and "uboot.img.bak".
      • Create a folder with name "UNLOCK" in phone root directory (SD card)(DCIM folders, Picture, Music, data etc.) and copy in already patched loader file "uboot.img" from firmware folder from PC (where we started our patching (unpacked firmware)).
      • Pack this firmware (on PC) back in archive (using 7-zip/winrar) with name "update.zip" (default flyme firmwares) - could be useful.

      • Copy a folder "gscript" together with the contents in phone root directory (SD card).
      • Install "terminal emulator" on your phone from "gscript" folder.
      • Open terminal and write
        su
        sh /sdcard/gscript/unlock.sh
        *Important!!* Wait 3 minutes for script action
      • Reboot your phone by command reboot . If it succesfully boot - congratulations, all right.



    Further:

    *WARNING!!!* All operations of modules flashing (recovery.img, boot.img etc.) doing ONLY BY STANDARD METHODS, by FASTBOOT command "fastboot flash"!! NOTHING ELSE!!

    1. You can flash modified stock recovery from folder "patched-recovery" for MX4/M1 Note (your needs) by command: "fastboot flash recovery patched_recovery.img" and restrict the international version of firmware (in update.zip you can do all changes you want - signature will not check).
      • *CARE!!* If you flash index I firmware with patched recovery, USE Titanium or others to delete/freeze "System Update" from firmware. OTA UPDATE WILL BRICK YOUR DEVICE!!!
      • *CARE!!* Patched recovery will be rewritten on the usual stock recovery by first full android load, then after command "fastboot flash patched_recovery.img" turn off your phone and hold button "volume up" (+) and "power" before the phone starts (or delete "recovery-from-boot" as alternative).
    2. You can flash custom recovery - and use it for your needs.
      • *CARE!!* DON'T try to flash stock meizu firmwares from any custom recovery, we have patched stock recovery for that.
      • ALWAYS DO A BACKUP!!


    VERY IMPORTANT Notes:

    1. Not allowed "strange" combinations (for example flashing not patched loader and custom recovery). If system goes to bootloop - exit from "half-brick" could be very hard, if it all possible.
    2. Loader patch and reverse packing stock firmwares should be done everywhere - it will save your time and nerves. You should avoid version mismatch of preloader - uboot - boot.img in smartphone firmware. Effects, bugs, lags can be very different.
      • *IMPORTANT!!* Then, if we flash "custom firmware", it should NOT CONTAINS "uboot.img" and "preloader.bin". All this can be flashed only in stock (modified) firmware, ONLY FROM STOCK or PATCHED STOCK recovery.
    3. "uboot.img" CAN'T BE flashed by fastboot!! Also not allowed doing experiments with "preloader.bin". BRICK probability is very high!!






    Original source:

    Authors:
    kirill8000 -
    kkk4 -

    Some thanks:
    Paypal - [email protected]
    2

    Apparently, the chinese community has developed a functional cm12 for the MX4, I'm downloading it and I'll test it

    http://blog.xen0n.name/2015/09/21/meizu-mx4-cm-12.1-userdebug-1/

    EDIT: It works !

    http://i.imgur.com/p8LZNoN.jpg
    2
    "Can't install this package on top of incompatible data. Please try another package or run a factory reset."

    I'm downloading the omnirom version

    And... No :(
    Ok.. Thanks for test it. I will continue trying [emoji6]
    2
    Philz Touch 6

    Sound is ok
    Wifi is ok
    Call works but "com.android.phone" crashes randomly when a sim is inserted
    Vibration not ok

    I continue my test
    2
    I have a spare board, I will need to downgrade this to KK and DD the uboot.img, then ill test with MTK tools mate.

    ---------- Post added at 10:53 AM ---------- Previous post was at 10:34 AM ----------

    I also managed to get this recovery working fine on Lollipop! but not the uboot.img

    ---------- Post added at 11:14 AM ---------- Previous post was at 10:53 AM ----------

    I have now successfully patched the uboot img of Lollipop and successfully flashed.

    This has allowed flashing a custom recovery using "fastboot flash recovery customrecovery.img"

    What it has not allowed is
    preloader mode
    and extended fastboot options like "fastboot getvar all"

    So this does not completely "unlock" the bootloader... but wondering if a Ubuntu user DD'ed there uboot.img if this would result in a brick when flashed.

    I am interested in this, I have a spare board to take the risk!


    My experience with MTK tools is limited, however with my past experience the phone is in preloader mode when completely powered off, I am unsure if this is the case with the ubuntu edition mx4 and doubt we can replicate that.