ZD551KL/ZE550KL/ZE551KL/ZE600KL/ZE601KL official bootloader unlock

Search This thread

wickedpygmy

Senior Member
Mar 17, 2012
67
34
Released on asus website 14/12/2015:
Marshmallow:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip

Lollipop:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip

The APKs for each are binary identical, so it is not really important which unlock utility you download.

Frequently asked questions:
Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
A: we do not think so, but we do not know if anyone has tried it.

Q: can I relock bootloader?
A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.

Q: can I restore my warranty by re-locking the bootloader?
A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.

Q: can I still receive OTA updates?
A: we do not know, because no updates have been released since the unlock utility was released.

Q: can I still update firmware manually?
A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).



Download notes from the site:

Unlock Device App: Unlock boot loader
Notice:
1. Update your software image to V1.15.40.771 or latest version
2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.

You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
 
Last edited:

wickedpygmy

Senior Member
Mar 17, 2012
67
34
Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)

I updated my ZE550KL to firmware v1.15.40.771:
http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip

then ran the ZE600KL unlock utility.

Unlock utility runs without errors, phone reboots, no errors, everything still working fine.

Confirmed unlock successful

Code:
C:\adb>fastboot oem device-info
...
(bootloader)    Device unlocked: true
(bootloader)    Charger screen enabled: false
(bootloader)    Display panel:
OKAY [  0.010s]
finished. total time: 0.010s
 
Last edited:

wickedpygmy

Senior Member
Mar 17, 2012
67
34
Yeh i did, in the source code they seem to be built with identical makefiles so i just figured i would experiment

Sent from my GT-I9195 using Tapatalk
 

destilant

Senior Member
Jan 14, 2010
108
9
Kaiserslautern
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name

I already compiled a cm recovery, but i am not sure about the block names...
 

wickedpygmy

Senior Member
Mar 17, 2012
67
34
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"

Code:
C:\adb>adb devices
List of devices attached
F8AZCY01P722    device


C:\adb>adb reboot bootloader

C:\adb>fastboot oem device-info
...
(bootloader)    Device unlocked: true
(bootloader)    Charger screen enabled: false
(bootloader)    Display panel:
OKAY [  0.010s]
finished. total time: 0.010s

C:\adb>
 
  • Like
Reactions: destilant

SkandaH

XDA Portal Supporter
Jun 8, 2013
968
2,561
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name

I already compiled a cm recovery, but i am not sure about the block names...

Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
 

wickedpygmy

Senior Member
Mar 17, 2012
67
34
You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"

fair enough. How do it look? The 600KL is a 6" phone and the 5500KL a 5.5". Does it appear to overlap or anything?

looks normal, both have same resolution. I think both phones use the same firmware since the kernel is identical and Asus don't release Z00m firmware but use Z00L for both models.
 

wickedpygmy

Senior Member
Mar 17, 2012
67
34
Moreover, can somebody please upload raw backups of the 'aboot' (& 'abootbak' if present) partition before & after unlocking the bootloader? You need root access & can use something like this one.
@Titokhan must be too late for me to do this, since I already unlocked and have no way to get back?

attached is aboot and abootbak after unlocking, maybe @heywheelie can upload the before?
 
Last edited:

heywheelie

Senior Member
Feb 12, 2013
681
97
Brisbane
  • Like
Reactions: Xcaliber

wickedpygmy

Senior Member
Mar 17, 2012
67
34
Can someone please paste the output on a rooted ZE550KL in adb shell:
Code:
ls -al /dev/block/platform/dw_mmc/by-name

I already compiled a cm recovery, but i am not sure about the block names...

This any use?

Code:
[email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
lrwxrwxrwx root     root              1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
lrwxrwxrwx root     root              1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
lrwxrwxrwx root     root              1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
lrwxrwxrwx root     root              1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
lrwxrwxrwx root     root              1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
lrwxrwxrwx root     root              1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
lrwxrwxrwx root     root              1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
lrwxrwxrwx root     root              1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
lrwxrwxrwx root     root              1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
lrwxrwxrwx root     root              1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
lrwxrwxrwx root     root              1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
lrwxrwxrwx root     root              1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
lrwxrwxrwx root     root              1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
lrwxrwxrwx root     root              1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
lrwxrwxrwx root     root              1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
lrwxrwxrwx root     root              1970-05-15 01:49 config -> /dev/block/mmcblk0p32
lrwxrwxrwx root     root              1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
lrwxrwxrwx root     root              1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
lrwxrwxrwx root     root              1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
lrwxrwxrwx root     root              1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
lrwxrwxrwx root     root              1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
lrwxrwxrwx root     root              1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
lrwxrwxrwx root     root              1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
lrwxrwxrwx root     root              1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
lrwxrwxrwx root     root              1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
lrwxrwxrwx root     root              1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
lrwxrwxrwx root     root              1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
lrwxrwxrwx root     root              1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
lrwxrwxrwx root     root              1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
lrwxrwxrwx root     root              1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
lrwxrwxrwx root     root              1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
lrwxrwxrwx root     root              1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
lrwxrwxrwx root     root              1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
lrwxrwxrwx root     root              1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
lrwxrwxrwx root     root              1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
lrwxrwxrwx root     root              1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
lrwxrwxrwx root     root              1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
lrwxrwxrwx root     root              1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
lrwxrwxrwx root     root              1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
lrwxrwxrwx root     root              1970-05-15 01:49 system -> /dev/block/mmcblk0p45
lrwxrwxrwx root     root              1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
lrwxrwxrwx root     root              1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
lrwxrwxrwx root     root              1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
[email protected]_Z00L_93:/ #
 

Top Liked Posts

  • There are no posts matching your filters.
  • 11
    Released on asus website 14/12/2015:
    Marshmallow:
    http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE551KL/UnlockTool_ASUS_AndroidM20160928_Singed.zip

    Lollipop:
    http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/ZE600KL_UnlockApp.zip

    The APKs for each are binary identical, so it is not really important which unlock utility you download.

    Frequently asked questions:
    Q: will this work on ZE500KG / ZE500KL / ASUS_Z00RD / ASUS_Z00RD_5 / ASUS_Z00RD_7 / ASUS_Z00ED / ASUS_Z00EDB / ASUS_Z00E_1 / ASUS_Z00E_2 / ASUS_Z00E_3
    A: we do not think so, but we do not know if anyone has tried it.

    Q: can I relock bootloader?
    A: we do not have a way of re-locking bootloader right now. Hopefully it will be possible using a backup of some partition to restore original bootloader, but we have not found it yet.

    Q: can I restore my warranty by re-locking the bootloader?
    A: we believe that ASUS records the serial number of the device through the unlock utility, so it will not be possible to make a warranty claim even if you do manage to re-lock the bootloader.

    Q: can I still receive OTA updates?
    A: we do not know, because no updates have been released since the unlock utility was released.

    Q: can I still update firmware manually?
    A: yes, definitely. fetch the new firmware zip from ASUS website and flash in stock recovery or transfer to root of sd-card and boot the phone normally (it will find the update zip file and prompt you).



    Download notes from the site:

    Unlock Device App: Unlock boot loader
    Notice:
    1. Update your software image to V1.15.40.771 or latest version
    2. Before you download, install, and use the Unlock Device App you acknowledge and assume complete risk to the quality and performance of this App, including but not limited to the following: once you activate the App you will not be able to recover your ASUS product (“Original Product”) back to original locked conditions; the Original Product with the activated App will not be deemed the Original Product; the Revised Product will no longer be covered under the warranty of the Original Product; the software of Revised Product will no longer be deemed the software of the Original Product and can no longer receive ASUS software updates; your purchased digital content may also be affected.

    You also acknowledge ASUS does not guarantee service satisfaction to any Revised Product, including events involving paid service requested by you to be performed to the Revised Product.
    Furthermore, such repaired Revised Product will not be covered under the warranty of the Original Product; the software of the repaired Revised Product will not be deemed the software of the Original Product and will not receive ASUS software updates.
    It is strongly advised that you avoid activating this App unless you fully understand and accept the risks that may arise.
    3
    Please note, I have ZE550KL-1A025TW version, Snapdragon 615, 2GB RAM (ASUS_Z00LD / ASUS_Z00L_93)

    I updated my ZE550KL to firmware v1.15.40.771:
    http://dlcdnet.asus.com/pub/ASUS/ZenFone/ZE600KL/UL-Z00L-WW-1.15.40.771-user.zip

    then ran the ZE600KL unlock utility.

    Unlock utility runs without errors, phone reboots, no errors, everything still working fine.

    Confirmed unlock successful

    Code:
    C:\adb>fastboot oem device-info
    ...
    (bootloader)    Device unlocked: true
    (bootloader)    Charger screen enabled: false
    (bootloader)    Display panel:
    OKAY [  0.010s]
    finished. total time: 0.010s
    3
    Rooted locked?

    Okay, from root (#) command prompt:
    Code:
    dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo

    Then reboot and see if it unlocked it.
    @Titokhan and osm0sis
    OMG OMG OMG IT WORKED!!!!!!!!!!!!!!!!!!!!!!!!!
    I had to do one more thing before your byte flip
    "Adb enable" should be set to 1. But by default, we don't see "adb enable" line after exec "fastboot oem device-info"
    When I executed the following, only then i could see "adb enable : 0" in device-info
    Code:
    fastboot oem abd_enable
    Then exec above command again, will set "adb enable" to 1
    And then your magical code
    Code:
    dd obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo

    Here's the imp terminal output (attached complte output)
    Code:
    [email protected]:/home/sziraqui# adb shell
    [email protected]_Z00L_63:/ $ su
    obs=1 count=1 seek=16 of=/dev/block/bootdevice/by-name/devinfo                <
    
    0+1 records in
    1+0 records out
    1 bytes transferred in 4.035 secs (0 bytes/sec)
    [email protected]_Z00L_63:/ # exit
    [email protected]_Z00L_63:/ $ exit
    [email protected]:/home/sziraqui# adb reboot bootloader
    [email protected]:/home/sziraqui# fastboot oem device-info...
    (bootloader) 	Device unlocked: true
    (bootloader) 	Charger screen enabled: false
    (bootloader) 	Display panel: 
    (bootloader) 	Adb Enable: 0
    OKAY [  0.004s]
    finished. total time: 0.005s
    [email protected]:/home/sziraqui# fastboot boot '/home/sziraqui/Downloads/twrp-3.0.2-3-Z00L.img' 
    downloading 'boot.img'...
    OKAY [  1.076s]
    booting...
    OKAY [  0.038s]
    finished. total time: 1.114s
    [email protected]:/home/sziraqui# fastboot oem device-info< waiting for device >
    
    #rebooted to system then to bootloader
    [email protected]:/home/sziraqui# adb reboot bootloade[email protected]:/home/sziraqui# fastboot oem device-info
    ...
    (bootloader) 	Device unlocked: true
    (bootloader) 	Charger screen enabled: false
    (bootloader) 	Display panel: 
    (bootloader) 	Adb Enable: 0
    OKAY [  0.016s]
    finished. total time: 0.016s
    [email protected]:/home/sziraqui# fastboot flash recovery '/home/sziraqui/Downloads/twrp-3.0.2-3-Z00L.img' 
    target reported max download size of 268435456 bytes
    sending 'recovery' (29956 KB)...
    OKAY [  1.090s]
    writing 'recovery'...
    OKAY [  0.681s]
    finished. total time: 1.771s
    [email protected]:/home/sziraqui#

    i have installed twrp, no issues so far
    Also note tthat after unlocking "adb enable" was automatically set to 0

    Lastly, IF YOU DONT MIND, CAN I WRITE A GUIDE FOR UNLOCKING BOOTLOADER USING ABOVE STEPS? Or is it too early?
    3
    Can someone please paste the output on a rooted ZE550KL in adb shell:
    Code:
    ls -al /dev/block/platform/dw_mmc/by-name

    I already compiled a cm recovery, but i am not sure about the block names...

    This any use?

    Code:
    [email protected]_Z00L_93:/ # ls -al /dev/block/platform/7824900.sdhci/by-name
    lrwxrwxrwx root     root              1970-05-15 01:49 ADF -> /dev/block/mmcblk0p42
    lrwxrwxrwx root     root              1970-05-15 01:49 APD -> /dev/block/mmcblk0p43
    lrwxrwxrwx root     root              1970-05-15 01:49 DDR -> /dev/block/mmcblk0p9
    lrwxrwxrwx root     root              1970-05-15 01:49 aboot -> /dev/block/mmcblk0p12
    lrwxrwxrwx root     root              1970-05-15 01:49 abootbak -> /dev/block/mmcblk0p13
    lrwxrwxrwx root     root              1970-05-15 01:49 abootdebug -> /dev/block/mmcblk0p34
    lrwxrwxrwx root     root              1970-05-15 01:49 asdf -> /dev/block/mmcblk0p33
    lrwxrwxrwx root     root              1970-05-15 01:49 asusfw -> /dev/block/mmcblk0p40
    lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt -> /dev/block/mmcblk0p27
    lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt1 -> /dev/block/mmcblk0p28
    lrwxrwxrwx root     root              1970-05-15 01:49 asusgpt2 -> /dev/block/mmcblk0p29
    lrwxrwxrwx root     root              1970-05-15 01:49 asuskey -> /dev/block/mmcblk0p22
    lrwxrwxrwx root     root              1970-05-15 01:49 asuskey2 -> /dev/block/mmcblk0p23
    lrwxrwxrwx root     root              1970-05-15 01:49 asuskey3 -> /dev/block/mmcblk0p24
    lrwxrwxrwx root     root              1970-05-15 01:49 asuskey4 -> /dev/block/mmcblk0p25
    lrwxrwxrwx root     root              1970-05-15 01:49 asuskey5 -> /dev/block/mmcblk0p26
    lrwxrwxrwx root     root              1970-05-15 01:49 boot -> /dev/block/mmcblk0p37
    lrwxrwxrwx root     root              1970-05-15 01:49 cache -> /dev/block/mmcblk0p44
    lrwxrwxrwx root     root              1970-05-15 01:49 config -> /dev/block/mmcblk0p32
    lrwxrwxrwx root     root              1970-05-15 01:49 devinfo -> /dev/block/mmcblk0p15
    lrwxrwxrwx root     root              1970-05-15 01:49 factory -> /dev/block/mmcblk0p20
    lrwxrwxrwx root     root              1970-05-15 01:49 factorybak -> /dev/block/mmcblk0p21
    lrwxrwxrwx root     root              1970-05-15 01:49 fsc -> /dev/block/mmcblk0p17
    lrwxrwxrwx root     root              1970-05-15 01:49 fsg -> /dev/block/mmcblk0p16
    lrwxrwxrwx root     root              1970-05-15 01:49 hyp -> /dev/block/mmcblk0p7
    lrwxrwxrwx root     root              1970-05-15 01:49 hypbak -> /dev/block/mmcblk0p8
    lrwxrwxrwx root     root              1970-05-15 01:49 keystore -> /dev/block/mmcblk0p31
    lrwxrwxrwx root     root              1970-05-15 01:49 misc -> /dev/block/mmcblk0p30
    lrwxrwxrwx root     root              1970-05-15 01:49 modem -> /dev/block/mmcblk0p41
    lrwxrwxrwx root     root              1970-05-15 01:49 modemst1 -> /dev/block/mmcblk0p18
    lrwxrwxrwx root     root              1970-05-15 01:49 modemst2 -> /dev/block/mmcblk0p19
    lrwxrwxrwx root     root              1970-05-15 01:49 oem -> /dev/block/mmcblk0p36
    lrwxrwxrwx root     root              1970-05-15 01:49 persist -> /dev/block/mmcblk0p39
    lrwxrwxrwx root     root              1970-05-15 01:49 persistent -> /dev/block/mmcblk0p35
    lrwxrwxrwx root     root              1970-05-15 01:49 recovery -> /dev/block/mmcblk0p38
    lrwxrwxrwx root     root              1970-05-15 01:49 rpm -> /dev/block/mmcblk0p3
    lrwxrwxrwx root     root              1970-05-15 01:49 rpmbak -> /dev/block/mmcblk0p4
    lrwxrwxrwx root     root              1970-05-15 01:49 sbl1 -> /dev/block/mmcblk0p1
    lrwxrwxrwx root     root              1970-05-15 01:49 sbl1bak -> /dev/block/mmcblk0p2
    lrwxrwxrwx root     root              1970-05-15 01:49 sec -> /dev/block/mmcblk0p11
    lrwxrwxrwx root     root              1970-05-15 01:49 splash -> /dev/block/mmcblk0p14
    lrwxrwxrwx root     root              1970-05-15 01:49 ssd -> /dev/block/mmcblk0p10
    lrwxrwxrwx root     root              1970-05-15 01:49 system -> /dev/block/mmcblk0p45
    lrwxrwxrwx root     root              1970-05-15 01:49 tz -> /dev/block/mmcblk0p5
    lrwxrwxrwx root     root              1970-05-15 01:49 tzbak -> /dev/block/mmcblk0p6
    lrwxrwxrwx root     root              1970-05-15 01:49 userdata -> /dev/block/mmcblk0p46
    [email protected]_Z00L_93:/ #
    2
    You can test your bootloader status, if you type in fastboot mode "fastboot oem device-info"
Our Apps
Get our official app!
The best way to access XDA on your phone
Nav Gestures
Add swipe gestures to any Android
One Handed Mode
Eases uses one hand with your phone