How To's

How to Unlock Bootloader on MEIZU Pro 7 Plus

Unlock Bootloader on MEIZU Pro 7 Plus

A Bootloader is a code which runs when we turn on your device. This code initiates some hardware and the kernel and ramdisk and gets the boot procedure going. So this procedure is known as Bootloader. A similar method applies to all the Laptop, PC, Smartphones and any such gadget. Each Android OEM producers bolt the bootloader despite the fact that it is an Open Source. So, you cannot install any custom ROM without unlocking the bootloader. So the smartphone manufacturer created a policy that Unlocked Bootloader device will void the warranty. They need you to stay with the Stock ROM.

Many users like to customise their phone to make it more interesting. Almost all the MEIZU devices come with bootloader locked, so if you want to install any custom ROM or custom recovery you need to Unlock Bootloader on MEIZU Pro 7 Plus.

If you consider the fact that this device is relatively new, you can get the idea of how much time will be needed by the developers to craft new ROMs for this device. However, you can still unlock your device and then try to root it. Unlocking the bootloader of your device is the first step towards successfully rooting a device. It allows you to customise the functions, unbrick the device and gain more control of your device. Unlock Bootloader on MEIZU Pro 7 Plus.

Unlock bootloader on MEIZU Pro 7 Plus


  • Follow this guide carefully or else it may lead to brick your device.
  • Unlocking Bootloader may wipe your data. Better take a full backup.
  • Maintain at least 50-60% of charging to prevent accidental shutdown.


ADB Drivers for Windows / Mac

Steps to Unlock bootloader on MEIZU Pro 7 Plus

  1. Download and Install ADB drivers on your PC.
  2. In your device, Enable the USB debugging on your device after enabling ‘Developer Options’ by going to ‘About phone’ and tapping build number 7 times.
    Usb debugging
  3. In PC, Open the ADB folder in C: Drive
  4. In ADB Folder, press “Shift + Right mouse key” and tap on “Open command window here.”
  5. Now connect your device to the PC using a USB data cable.
  6. Boot your device into “Fastboot” mode and give the following command
    Windows: adb reboot bootloader
    Mac: ./adb reboot bootloader
  7. Execute the following command to unlock the bootloader.
    Windows: fastboot oem unlock
    Mac: ./fastboot oem unlock
  8. Done. You device bootloader is unlocked.

Hope this article is helpful. Comment down below if you have any doubts.


Teja Pagidimarri

I am a Tech Content writer and full-time blogger. Started my career as Engineer in Larsen and Toubro LTD. with 3 years of experience in Hyderabad Metro Rail Project. I have been doing blogging since 2015, started with zero experience and now I am the well-recognized blogger. I like learning new things and believe that there can never be an end to learning. You can shoot an e-mail at

Related Articles


  1. Hi, I need help. I can’t unlock the bootloader on my Pro 7 Plus.
    There always comes the error: device ‘(null)’ not found. The point “allows unlock the bootloader” does not exist on my developer setups.everything else I did like described. Please help me

  2. Hi friend,
    this is not work on my pro 7 plus.
    when i input “adb reboot bootloader”,just comes the error:adb server is out of date. killing……. *daemon started successfully* error:device not found
    when i input “fastboot oem unlock-go” just comes the error: failed(remote:argument error!) finished. total time:0.000s
    can you help me? this is my

    1. Hi Jerry,
      After I get into the fastboot mode, the two unlock commands does not seem to work for me.
      I got errors as below
      C:\adb>fastboot devices
      793QBDR62286K fastboot

      C:\adb>fastboot oem unlock

      FAILED (remote: argument error!)
      finished. total time: 0.020s
      C:\adb>fastboot oem unlock-go

      FAILED (remote: argument error!)
      finished. total time: 0.010s

      do you happen to know why?

      Thanks for your help in advance.

  3. Yes,the ADB and fastboot drivers are installed.compute shows Android phone-Android Bootloader interface are ok

  4. Hi,in you guide,have not writed that i need to Execute the command ” adb fastboot devices ”
    i will try it soon

  5. hi friend,
    here is all informations,can you help me to solve this problem?
    Have you deleted my message at here before? because i can not see some historical records

    C:\adb>adb reboot bootloader
    * daemon not running. starting it now on port 5037 *
    * daemon started successfully *
    error: device ‘(null)’ not found

    C:\adb>adb reboot bootloader
    error: device ‘(null)’ not found

    C:\adb>fastboot devices
    793QBDR822A32 fastboot

    C:\adb>fastboot oem unlock

    FAILED (remote: argument error!)
    finished. total time: 0.004s

    C:\adb>adb fastboot devices
    Android Debug Bridge version 1.0.32
    Revision eac51f2bb6a8-android

    -a – directs adb to listen on all interfaces for a c
    -d – directs command to the only connected USB devic
    returns an error if more than one USB device is
    -e – directs command to the only running emulator.
    returns an error if more than one emulator is r
    -s – directs command to the device or emulator with
    the given
    serial number or qualifier. Overrides ANDROID_S
    environment variable.
    -p – simple product name like ‘sooner’, or
    a relative/absolute path to a product
    out directory like ‘out/target/product/sooner’.

    If -p is not specified, the ANDROID_PRODUCT_OUT

    environment variable is used, which must
    be an absolute path.
    -H – Name of adb server host (default: localhost)
    -P – Port of adb server (default: 5037)
    devices [-l] – list all connected devices
    (‘-l’ will also list device qualifiers)
    connect [:] – connect to a device via TCP/IP
    Port 5555 is used by default if no port number
    is specified.
    disconnect [[:]] – disconnect from a TCP/IP device.
    Port 5555 is used by default if no port number
    is specified.
    Using this command with no additional arguments

    will disconnect from all connected TCP/IP devic

    device commands:
    adb push [-p]
    – copy file/dir to device
    (‘-p’ to display the transfer progress)
    adb pull [-p] [-a] []
    – copy file/dir from device
    (‘-p’ to display the transfer progress)
    (‘-a’ means copy timestamp and mode)
    adb sync [ ] – copy host->device only if changed
    (-l means list but don’t copy)
    (see ‘adb help all’)
    adb shell – run remote shell interactively
    adb shell – run remote shell command
    adb emu – run emulator console command
    adb logcat [ ] – View device log
    adb forward –list – list all forward socket connections.
    the format is a list of lines with the followin
    g format:
    ” ” ” ” “\n”
    adb forward – forward socket connections
    forward specs are one of:
    jdwp: (remote only)
    adb forward –no-rebind
    – same as ‘adb forward ‘ but fail
    if is already forwarded
    adb forward –remove – remove a specific forward socket connection
    adb forward –remove-all – remove all forward socket connections
    adb reverse –list – list all reverse socket connections from device

    adb reverse – reverse socket connections
    reverse specs are one of:
    adb reverse –norebind
    – same as ‘adb reverse ‘ but fail
    if is already reversed.
    adb reverse –remove
    – remove a specific reversed socket connection
    adb reverse –remove-all – remove all reversed socket connections from dev
    adb jdwp – list PIDs of processes hosting a JDWP transport

    adb install [-lrtsdg]
    – push this package file to the device and instal
    l it
    (-l: forward lock application)
    (-r: replace existing application)
    (-t: allow test packages)
    (-s: install application on sdcard)
    (-d: allow version code downgrade)
    (-g: grant all runtime permissions)
    adb install-multiple [-lrtsdpg]
    – push this package file to the device and instal
    l it
    (-l: forward lock application)
    (-r: replace existing application)
    (-t: allow test packages)
    (-s: install application on sdcard)
    (-d: allow version code downgrade)
    (-p: partial application install)
    (-g: grant all runtime permissions)
    adb uninstall [-k] – remove this app package from the device
    (‘-k’ means keep the data and cache directories
    adb bugreport – return all information from the device
    that should be included in a bug report.

    adb backup [-f ] [-apk|-noapk] [-obb|-noobb] [-shared|-noshared] [-all]
    [-system|-nosystem] []
    – write an archive of the device’s data to
    If no -f option is supplied then the data is wr
    to “backup.ab” in the current directory.
    (-apk|-noapk enable/disable backup of the .apks
    in the archive; the default is noapk.)
    (-obb|-noobb enable/disable backup of any insta
    lled apk expansion
    (aka .obb) files associated with each applic
    ation; the default
    is noobb.)
    (-shared|-noshared enable/disable backup of the
    shared storage / SD card contents; the defau
    lt is noshared.)
    (-all means to back up all installed applicatio
    (-system|-nosystem toggles whether -all automat
    ically includes
    system applications; the default is to inclu
    de system apps)
    ( is the list of applications to b
    e backed up. If
    the -all or -shared flags are passed, then t
    he package
    list is optional. Applications explicitly g
    iven on the
    command line will be included even if -nosys
    tem would
    ordinarily cause them to be omitted.)

    adb restore – restore device contents from the backup

    adb disable-verity – disable dm-verity checking on USERDEBUG builds
    adb enable-verity – re-enable dm-verity checking on USERDEBUG build
    adb keygen – generate adb public/private key. The private ke
    y is stored in ,
    and the public key is stored in .pub. Any
    existing files
    are overwritten.
    adb help – show this help message
    adb version – show version num

    adb wait-for-device – block until device is online
    adb start-server – ensure that there is a server running
    adb kill-server – kill the server if it is running
    adb get-state – prints: offline | bootloader | device
    adb get-serialno – prints:
    adb get-devpath – prints:
    adb remount – remounts the /system, /vendor (if present) and
    /oem (if present) partitions on the device read-write
    adb reboot [bootloader|recovery]
    – reboots the device, optionally into the bootloa
    der or recovery program.
    adb reboot sideload – reboots the device into the sideload mode in re
    covery program (adb root required).
    adb reboot sideload-auto-reboot
    – reboots into the sideload mode, then reboots au
    tomatically after the sideload regardless of the result.
    adb reboot-bootloader – reboots the device into the bootloader
    adb root – restarts the adbd daemon with root permissions
    adb unroot – restarts the adbd daemon without root permissio
    adb usb – restarts the adbd daemon listening on USB
    adb tcpip – restarts the adbd daemon listening on TCP on th
    e specified port
    adb ppp [parameters] – Run PPP over USB.
    Note: you should not automatically start a PPP connection.
    refers to the tty for PPP stream. Eg. dev:/dev/omap_csmi_tty1
    [parameters] – Eg. defaultroute debug dump local notty usepeerdns

    adb sync notes: adb sync [ ]
    can be interpreted in several ways:

    – If is not specified, /system, /vendor (if present), /oem (if pre
    sent) and /data partitions will be updated.

    – If it is “system”, “vendor”, “oem” or “data”, only the corresponding partiti
    is updated.

    environmental variables:
    ADB_TRACE – Print debug information. A comma separated list
    of the following values
    1 or all, adb, sockets, packets, rwx, usb, sync
    , sysdeps, transport, jdwp
    ANDROID_SERIAL – The serial number to connect to. -s takes prior
    ity over this if given.
    ANDROID_LOG_TAGS – When used with the logcat option, only these de
    bug tags are printed.


Leave a Reply

Your email address will not be published. Required fields are marked *