• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!

[Auto ToolKit][BL Unlock][Magisk&SuperSU][Xposed] Zenfone 2 ToolKit [Z00A/Z008/Z00X]

Search This thread

rummsbumms

Senior Member
May 19, 2015
150
135
Last update: 14.10.2017

Fantastic news
No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good::D

Next level reached
No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.

z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214


Introduction
This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.

I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...

Note:

This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.

Before you try any action in the menu, check that the device informations are shown.




Features

  • Supports ZE551ML, ZE550ML, ZX551ML
  • Device status and connection information
  • Automated actions
  • Bootloader unlock
  • Flash boot/recovery images (twrp, stock)
  • Fix wrong or missing image signatures!!
  • Root / unroot Magisk & SuperSU
  • Xposed for Magisk (install / uninstall)
  • Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
  • Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML



Currently integrated Tools


  • v14.0 (default) and v14.2
  • SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
  • TWRP 3.0.3-M4 / 3.1.1 (default)
  • Xposed for Magisk v87.3 / v88.0 (default)
  • Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
  • adb/fastboot 1.0.32 (optional: 1.0.36)



Installation instructions

Do a clean start:

  1. Download the latest base package
  2. Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
  3. (Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory

To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).



Usage instructions
Prerequisite:

  1. Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
  2. Ensure that you have one of the latest MM firmwares for your device installed.
  3. Ensure that you have enabled USB Debugging in Developer Options
  4. Even if only a few actions could be really harmful to your data: Get a backup!

Then:

  1. Run ze551ml_toolkit.bat
  2. Check device status information & see if toolkit really likes your device ;)
  3. If your bootloader is still locked: Unlock it first with menu B -> choice U
  4. (Optional) Choose your desired versions of the integrated tools in menu O.
  5. (Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
  6. Check all the other nice functions of the toolkit


Downloads


Main: Downloads tab (see above)

Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg

Mirror 2: https://goo.gl/xNhMvZ

File structure:

  • ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
  • z00a*.zip - contains all device specific files for Z00A (ZE551ML)
  • z008*.zip - contains all device specific files for Z008 (ZE550ML)
  • z00x*.zip - contains all device specific files for Z00X (ZX551ML)



Changelog
Code:
[B]v1.3[/B]
Current changelog: 14.10.2017
[added] xposed for magisk v88.0
[new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)

Code:
[B]v1.22[/B]
Current changelog: 08.10.2017
[added] magisk v14.2
[removed] magisk v13.3
[fixed] xposed for magisk v87.3
[new] Fix wrong or missing image signatures!!
[fixed] Better support for encrypted devices
Code:
[B]v1.1b9[/B]
Current changelog: 22.09.2017
[added] magisk v14.0
[removed] magisk <v13.3
[removed] twrp 3.0.2-M1
[updated] magisk uninstaller
Code:
[B]v1.1b8[/B]
Current changelog: 19.07.2017
[added] magisk v13.3
[updated] magisk uninstaller
[new] action to download latest mirror file which is used to get some stock files updates
Code:
[B]v1.1b6[/B]
Current changelog: 13.07.2017
[added] magisk v13.2
[removed] magisk v13.1
[fixed] twrp detection
[modified] magisk manager will now be extracted from zip and installation will be forced after sideload
Code:
[B]v1.1b5[/B]
Current changelog: 11.07.2017
[added] magisk v13.1
[removed] magisk v13 betas
[fixed] minor fixes in supersu actions
Code:
[B]v1.1b3[/B]
Current changelog: 02.07.2017
[added] 2 magisk v13 beta versions
[removed] magisk <v12
[updated] xposed installer
[added] 2 more twrp versions
[fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
[fixed] changed the way the toolkit downloads files
Code:
[B]v1.0b10[/B]
Current changelog: 04.04.2017
[added] magisk v12.0
[updated] fixed some help messages
Code:
[B]v1.0b8[/B]
Current changelog: 21.03.2017
[added] support for more devices: z00a, z00d, z00x
[added] automatic download for device files if needed
[added] magisk v11.6
[added] twrp 3.0.3-M4 (for encrypted devices or android n installations
[added] backup efs function
[added] integrity check
[modified] menu structure
[updated] changed some help messages
Code:
[B]v1.0b2[/B]
Current changelog: 14.02.2017
[modified] menu order
[disabled] usage of system installed platform tools, internal are forced now
[fixed] boot2recovery could have been failed in some cases
[fixed] timing problems in wipe routine 
[added] validations added to each boot states
[removed] twrp 3.0.3.2
[adjusted] code / function names
Code:
[B]v0.9[/B]
Current changelog: 07.02.2017
[added] new twrp 3.0.3.2
[added] new magisk v11.1 
[disabled] second disclaimer
[disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
[removed] magisk v10.2
[removed] twrp 3.0.3-N
Code:
[B]v0.7[/B]
Current changelog: 02.02.2017
[added] boot to safe mode
[added] wipe menu
[added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
Code:
[B]v0.5[/B]
Current changelog: 31.01.2017
[added] each action shows some information about what's going to happen now
[changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
Code:
[B]v0.3p1[/B]
Changelog: 28.01.2017
[fixed] added missing magisk manager to installation procedure


Thanks to/Credits
Code:
::   > shakalaca
::   > chainfire
::   > topjohnwu
::   > twrp
::   > social-design-concepts
::   > phhusson
::   > say99
::   > Deathschythe33
::   > ggrandou
::   > gerasiov

You'll find more credits inside the source code. 

I hope i didn't forget anyone. If so please report.

XDA:DevDB Information
Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2

Contributors
rummsbumms

Version Information
Status: Stable
Current Beta Version: 1.3
Beta Release Date: 2017-10-14

Created 2017-01-28
Last Updated 2018-07-31
 

Attachments

  • disclaimer.png
    disclaimer.png
    12.3 KB · Views: 51,494
  • mainmenu.png
    mainmenu.png
    16 KB · Views: 47,563
Last edited:

fred_gaou

Senior Member
Jul 25, 2014
341
154
Here and there
@rummsbumms
Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
====
To avoid having to get always the same questions like
  • How to root for the 1st time or safely upgrade firmware and root again…?
  • How to get back to a clean stock device?
  • What does this menu entry really do?
  • etc.
I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
====
FEATURES REQUEST

# Add FACTORY RESET DEVICE menu entry. This will imply:
Code:
fastboot erase userdata
fastboot erase cache
# Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
Code:
fastboot erase system (I guess it will work only if bootloader have been unlocked)
fastboot erase userdata
fastboot erase cache
or a complete wipe that will format the partitions too
Code:
fastboot -w
# Add a way to Back up and restore EFS, see this thread.
# And +1 to the post below about ifwi.
====
I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
====
I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
====
And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
====

Great Work ! :good:

I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.

Regards
 
Last edited:

timbernot

Senior Member
Sep 20, 2013
1,239
397
N/W UK
What would be ideal , if possible to add ;)
Is ..
An ifwi version detector ;)
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
 
Last edited:
  • Like
Reactions: rummsbumms

rummsbumms

Senior Member
May 19, 2015
150
135
@fred_gaou
You gave some nice questions&suggestions!
About your questions:
  1. You don't need the batch to run as admin as I don't use any function that needs admin rights.
  2. Yes, I've tested all root functions and switched between single supersu, magisk with phh and magisk with supersu, but of course always with running the unroot task first. my personal favorite is magisk with phh b/c of the magisk hide. that's what i need for some banking apps :angel:
  3. Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
  4. The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.

The other points:
  • Giving more guidelines/hints in this thread&toolkit is a good point. I'll try to add this as soon as possible. :good:
  • Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
  • I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
 

rummsbumms

Senior Member
May 19, 2015
150
135
What would be ideal , if possible to add ;)
Is ..
An ifwi version detector ;)
Because , there are a lot of people who flashed their phones who haven't a clue they have M version with LP bootloader.
They think they have M BL and brick their phones
If any help...
IFWI versions on 551 or Z00A
0094.0177 is locked LP bootloader
0094.0173 is unlocked.
0094.0183 is M BL
If your tool kit could detect these , it could flash back original stock recoveries and help many unaware people restore and upgrade stock LP to M
Then they could again use your tool to unlock once upgraded to stock M.
Where they then could make back ups of stock again before flashing custom ROMs
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
 
  • Like
Reactions: timbernot
Hi,

I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?

I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM :(
 

fred_gaou

Senior Member
Jul 25, 2014
341
154
Here and there
  • Not yet. I don't think i'm going to try that soon as I want to stay at stock rom atm. If you have any idea to implement that to this toolkit, i would be pleased to know.
Well, I'm still on stock LP so I would not be a good adviser. I trust the experienced users that switch and update ROM weekly so they will give useful feedback soon. Since some guys on LineageOS used Giovix modder to unlock bootloader and install ROM via TWRP, I guess it's currently the way to go.

  • The idea of the auto packages is to combine some single actions like unroot & root. So there is actually just one package, which I used the most time to get back to my favorite root solution.
I get it now. It could be a useful section in future to run sequential commands at once.

  • Putting factory reset & backup on my todo list :good: Are there any installation procedure for roms that recommend to erase /system first? I've done that by mistake a few months ago and started to sweat. As this is a very dangerous command, I would only implement this if there is a need.
Yes it is wise. I just provided the command because it was implemented in Giovix Modder and often reported as a way to clean up before flash all stock in other device. Don't know for 551.

  • I know about the newer 1.0.36 version. That was the reason for the action "force internal platform toolkit" in the troubleshoot menu. But I had a LOT of problems running the new version on 2 different machines. The daemon didn't start with an error telling that the adb.log couldn't be opened. I'll put it on my todo list too, but with low priority.
Detail is good to know. What OS do you use: 7, 8.1 or 10? If 1.0.32 works fine on every version, there is no point to risk to break anything using 1.0.36.

Thanks for your answers.
 

timbernot

Senior Member
Sep 20, 2013
1,239
397
N/W UK
Haven't thought about that scenario. Can you give me some more details? Users with bricked phones can only boot fastboot and nothing else?
I currently don't know a method to detect the ifwi version in fastboot state, so i would probably need twrp or a running system (almost certainly with root permission) to get ifwi information.
Thinking about it now a bit more , it maybe tail end for this problem .
The actual problem people were having was they thought they had cm13 with M BL , actually they had the LP bootloader cm13 . They would be in a working system then flash 14.1 / 7.1 builds then , brick their devices .
They forget they never upgraded bootloader and with having 6.0.1 M in build information in settings, presumed they had upgraded bootloader at some point but didn't .
Maybe , to prevent the tail enders from performing such tasks again , maybe a simple addition like a warning , like build date which in cm 13 , to check.. if before July 2016 and have IFWI version 0094.0173 unlocked . Then you could direct them to say a return to stock option , flashing back boot and recovery for say on 551 LP 2 20 40 .196 Version , then possibly install the full ROM from say a link or something like ...Then info to upgrade to stock M before returning back to tool to unlock updated to the latest M.
But like mentioned , we maybe at the tail end of this problem.
Probably related to 95% of the bricking threads here for zenfone.
Anyway thanks for taking interest ;)
 

rummsbumms

Senior Member
May 19, 2015
150
135
Hi,

I just want to verify. I have the ASUS Zenfone 2 Deluxe Special Edition that I have upgraded from the stock 5.0.0 Android Lollipop (I forgot the ASUS Firmware version number) to the the Official ASUS 6.0.1 Marshmallow (Version WW-4.21.40.223(andriod M)) I can use this?

I regret upgrading from the Official LP to the Official MM with all the bloatwares. I am looking for a way to get root just like with my Sony Xperia phones but I am learning that getting root on ASUS Zenfones on MM is difficult. Almost all solutions I am reading is advising to downgrade from MM to LP, root, then manually upgrade to MM :(
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.

Is your bootloader still locked?
 
Last edited:

rummsbumms

Senior Member
May 19, 2015
150
135
v0.7 is out
@fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
@holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
@timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.
 
Last edited:
As far as i can see from the asus page, the zf2 deluxe special edition uses the same firmware files and you already have the newest firmware (.223) installed, so i think it should work.

Is your bootloader still locked?

Hello @rummsbumms,

Thank you for taking your time to respond. Yup, my phone's bootloader is still locked. Everything in this phone is "official" including the freaking official bloatwares. I love the HW specs of this phone, but the bloatwares are F***ing crazy!
 

Top Liked Posts

  • There are no posts matching your filters.
  • 51
    Last update: 14.10.2017

    Fantastic news
    No more waiting for manually signed magisk, supersu or twrp versions from now on. Just install any new version and use the image signature fix action in the troubleshoot menu of the toolkit. :good::D

    Next level reached
    No more waiting for special zenfone 2 patched xposed for magisk. Got my own zip to do some hex patching. You can either use one of the (already patched) xposed versions from the toolkit or download xposed for magisk and use the xposed patcher in the troubleshoot menu.

    z00x users please read this post https://forum.xda-developers.com/showpost.php?p=72298931&postcount=214


    Introduction
    This is a windows batch toolkit for automated actions like bl unlock, flash, root, xposed, sideload tasks, ... for your ze551ml/ze550ml/zx551ml.

    I hope you find it useful. Check the tabs above for more screenshots, downloads, review ...

    Note:

    This tookit works well for a lot of situations, but I need feedback especially for the new supported devices ze550ml and zx551ml. Please go on and try the toolkit, then leave a message on this thread, do a review or just vote.

    Before you try any action in the menu, check that the device informations are shown.




    Features

    • Supports ZE551ML, ZE550ML, ZX551ML
    • Device status and connection information
    • Automated actions
    • Bootloader unlock
    • Flash boot/recovery images (twrp, stock)
    • Fix wrong or missing image signatures!!
    • Root / unroot Magisk & SuperSU
    • Xposed for Magisk (install / uninstall)
    • Patching xposed for magisk for zenfone 2 (if installed the unpatched xposed for magisk by mistake)
    • Compatible with most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML



    Currently integrated Tools


    • v14.0 (default) and v14.2
    • SuperSU 2.79SR3 / 2.82 (default) / 2.82SR5
    • TWRP 3.0.3-M4 / 3.1.1 (default)
    • Xposed for Magisk v87.3 / v88.0 (default)
    • Stock boot/recovery support of most current MM firmware versions from devices ZE551ML, ZE550ML, ZX551ML
    • adb/fastboot 1.0.32 (optional: 1.0.36)



    Installation instructions

    Do a clean start:

    1. Download the latest base package
    2. Extract to your desired location. It will extract a "ze551ml toolkit" directory with all files.
    3. (Optional / If the automatic download of the device specific files fails) Download the device specific packages and extract it directly to the "ressources" directory

    To run the toolkit just execute "ze551ml toolkit.bat" (no admin rights are needed).



    Usage instructions
    Prerequisite:

    1. Ensure that you have installed device usb drivers (e. g. see: https://www.asus.com/Phone/ZenFone_2_ZE551ML/HelpDesk_Download/ )
    2. Ensure that you have one of the latest MM firmwares for your device installed.
    3. Ensure that you have enabled USB Debugging in Developer Options
    4. Even if only a few actions could be really harmful to your data: Get a backup!

    Then:

    1. Run ze551ml_toolkit.bat
    2. Check device status information & see if toolkit really likes your device ;)
    3. If your bootloader is still locked: Unlock it first with menu B -> choice U
    4. (Optional) Choose your desired versions of the integrated tools in menu O.
    5. (Recommended) Flash twrp with menu F -> choice T. If you want to try a newer twrp version, change it first in menu O
    6. Check all the other nice functions of the toolkit


    Downloads


    Main: Downloads tab (see above)

    Mirror 1: https://mega.nz/#F!u8JhhY7T!9PryiRdjVSFf-O4erijDWg

    Mirror 2: https://goo.gl/xNhMvZ

    File structure:

    • ze551ml-toolkit-<VERSION>-base.zip - contains the base toolkit package without any device specific files
    • z00a*.zip - contains all device specific files for Z00A (ZE551ML)
    • z008*.zip - contains all device specific files for Z008 (ZE550ML)
    • z00x*.zip - contains all device specific files for Z00X (ZX551ML)



    Changelog
    Code:
    [B]v1.3[/B]
    Current changelog: 14.10.2017
    [added] xposed for magisk v88.0
    [new] Patching xposed for magisk for zenfone 2 (if installed the unpatched version by mistake)

    Code:
    [B]v1.22[/B]
    Current changelog: 08.10.2017
    [added] magisk v14.2
    [removed] magisk v13.3
    [fixed] xposed for magisk v87.3
    [new] Fix wrong or missing image signatures!!
    [fixed] Better support for encrypted devices
    Code:
    [B]v1.1b9[/B]
    Current changelog: 22.09.2017
    [added] magisk v14.0
    [removed] magisk <v13.3
    [removed] twrp 3.0.2-M1
    [updated] magisk uninstaller
    Code:
    [B]v1.1b8[/B]
    Current changelog: 19.07.2017
    [added] magisk v13.3
    [updated] magisk uninstaller
    [new] action to download latest mirror file which is used to get some stock files updates
    Code:
    [B]v1.1b6[/B]
    Current changelog: 13.07.2017
    [added] magisk v13.2
    [removed] magisk v13.1
    [fixed] twrp detection
    [modified] magisk manager will now be extracted from zip and installation will be forced after sideload
    Code:
    [B]v1.1b5[/B]
    Current changelog: 11.07.2017
    [added] magisk v13.1
    [removed] magisk v13 betas
    [fixed] minor fixes in supersu actions
    Code:
    [B]v1.1b3[/B]
    Current changelog: 02.07.2017
    [added] 2 magisk v13 beta versions
    [removed] magisk <v12
    [updated] xposed installer
    [added] 2 more twrp versions
    [fixed] hardened detection of installed twrp version (still needs root or already booted twrp for that)
    [fixed] changed the way the toolkit downloads files
    Code:
    [B]v1.0b10[/B]
    Current changelog: 04.04.2017
    [added] magisk v12.0
    [updated] fixed some help messages
    Code:
    [B]v1.0b8[/B]
    Current changelog: 21.03.2017
    [added] support for more devices: z00a, z00d, z00x
    [added] automatic download for device files if needed
    [added] magisk v11.6
    [added] twrp 3.0.3-M4 (for encrypted devices or android n installations
    [added] backup efs function
    [added] integrity check
    [modified] menu structure
    [updated] changed some help messages
    Code:
    [B]v1.0b2[/B]
    Current changelog: 14.02.2017
    [modified] menu order
    [disabled] usage of system installed platform tools, internal are forced now
    [fixed] boot2recovery could have been failed in some cases
    [fixed] timing problems in wipe routine 
    [added] validations added to each boot states
    [removed] twrp 3.0.3.2
    [adjusted] code / function names
    Code:
    [B]v0.9[/B]
    Current changelog: 07.02.2017
    [added] new twrp 3.0.3.2
    [added] new magisk v11.1 
    [disabled] second disclaimer
    [disabled] bootloader status in device overview at the top as I haven't found a secure way to detect a locked/unlocked bootloader yet.
    [removed] magisk v10.2
    [removed] twrp 3.0.3-N
    Code:
    [B]v0.7[/B]
    Current changelog: 02.02.2017
    [added] boot to safe mode
    [added] wipe menu
    [added] new twrp 3.0.3-N and platform tools 1.0.3.6 (no default yet. versions can be switched in troubleshoot menu for testing)
    Code:
    [B]v0.5[/B]
    Current changelog: 31.01.2017
    [added] each action shows some information about what's going to happen now
    [changed] each action must be confirmed to be executed. if you don't need that, enable auto-yes in troubleshoot menu
    Code:
    [B]v0.3p1[/B]
    Changelog: 28.01.2017
    [fixed] added missing magisk manager to installation procedure


    Thanks to/Credits
    Code:
    ::   > shakalaca
    ::   > chainfire
    ::   > topjohnwu
    ::   > twrp
    ::   > social-design-concepts
    ::   > phhusson
    ::   > say99
    ::   > Deathschythe33
    ::   > ggrandou
    ::   > gerasiov
    
    You'll find more credits inside the source code. 
    
    I hope i didn't forget anyone. If so please report.

    XDA:DevDB Information
    Zenfone 2 ToolKit [Z00A/Z008/Z00X], Tool/Utility for the Asus ZenFone 2

    Contributors
    rummsbumms

    Version Information
    Status: Stable
    Current Beta Version: 1.3
    Beta Release Date: 2017-10-14

    Created 2017-01-28
    Last Updated 2018-07-31
    5
    @rummsbumms
    Question 1: would you suggest to run ze551ml_toolkit.bat as admin or not?
    Question 2: did you personally test all root method provided by toolkit: SuperSU, Magisk+SuperSU, Magisk+phh superuser? Did you succeed to properly unroot all of them? Will you suggest one method rather than another?
    Question 3: did you test custom ROM install via TWRP such as last LineageOS after unlock bootloader and install TWRP with your toolkit?
    Question 4: What is "Auto Packages" supposed to mean? What does it do? According to script code, it seems to unroot and restore stock bootloader. That's why I don't understand the Auto Packages term.
    ====
    To avoid having to get always the same questions like
    • How to root for the 1st time or safely upgrade firmware and root again…?
    • How to get back to a clean stock device?
    • What does this menu entry really do?
    • etc.
    I would suggest some guide lines to help users in the 1st post as well as in a "how to.txt" file along the toolkit or in the batch itself as a menu entry named "Help" or "FAQ" or else.
    ====
    FEATURES REQUEST

    # Add FACTORY RESET DEVICE menu entry. This will imply:
    Code:
    fastboot erase userdata
    fastboot erase cache
    # Add Erase /system, /data and /cache menu entry, may be useful before installing a ROM. This will imply:
    Code:
    fastboot erase system (I guess it will work only if bootloader have been unlocked)
    fastboot erase userdata
    fastboot erase cache
    or a complete wipe that will format the partitions too
    Code:
    fastboot -w
    # Add a way to Back up and restore EFS, see this thread.
    # And +1 to the post below about ifwi.
    ====
    I would suggest also in the 1st post as well as in a "how to.txt" that the functions be more detailed. Example:
    I see you chose to use adb/fastboot 1.0.32 version. Just to let you know that Minimal ADB and Fastboot v1.42 provide a more up to date adb and fastboot (the last 1.0.36). Why do you use this old 1.0.32 version?
    ====
    I didn't test ZE55xML_Modder by Giovix92 or this toolkit yet, but just by reading the batch file, I can tell your code is way more elegant and skilled and should avoid the magisk root bug that ZE55xML_Modder users encounter.
    ====
    And why checking if ADB is installed as system-wide since your toolkit already provides local adb/fasboot ? What's the point to add this "unnecessary" step ?
    ====

    Great Work ! :good:

    I will test your toolkit very soon and give feedback. I hope to get answers from you in the meantime.

    Regards
    3
    I hope this will help...

    Code:
    #include <std_disclaimer.h>
    
    /*
     * Your warranty is now void.
     *
     * We are not responsible for bricked devices, dead SD cards,
     * thermonuclear war, or you getting fired because the alarm app failed. Please
     * do some research if you have any concerns about features included in this ROM
     * before flashing it! YOU are choosing to make these modifications, and if
     * you point the finger at us for messing up your device, we will laugh at you.
     *
     */

    Pre-requisites:
    1. ASUS Android USB Drivers - get it from the ASUS Support page
    2. 15 seconds ADB Installer v1.4.3 - get it from here: https://forum.xda-developers.com/showthread.php?t=2588979
    3. ASUS Zenfone 2 with Firmware version XXXXXX - @rummsbumms please advise on this
    4. Enable Developer Options How to enable Developer Options? Go to Settings > About > Software Information, and tap on 'Build Number' Seven (7) times
    5. Enable Developer Options > USB Debugging
    6. Enable Security Options > Unknown sources
    7. Download the ze551ml-toolkit-v0.9-full.zip OR ze551ml-toolkit-v0.9-base.zip - get it here https://forum.xda-developers.com/devdb/project/?id=19121#downloads
    8. Back-up your data!
    9. Back-up your data!
    10. Back-up your data!
    11. Back-up your data!
    12. Back-up your data!
    13. Back-up your data!

    Steps:
    • Download and extract the ze551ml-toolkit-v0.9-full.zip (or the ze551ml-toolkit-v0.9-base.zip) to your desired location
    • Turn your phone on normally
    • Plug your phone to your computer via a USB Cable. Note: It is not advisable to use a USB Hub. Please connect your phone directly to your Computer.
    • Run the ze551ml_toolkit.bat file
    • Follow the initial prompt and type ACCEPT, and press enter
    • Type Y, and press enter
    • The toolkit should be able to pull your phone's information and show it on the upper part
    • Then following these steps...
      1.) unlock bootloader (choice U) in menu B
      2.) install twrp recovery (choice T) in menu F
      3.) install magisk (choice M) in menu R

    3
    New version v1.0b8..

    ..is out and ready to download. Did a lot of code work, but i'm too lazy to add changelog or update main page atm.

    Some enhancements: magisk v11.6, device support for z00a/z008(untested)/z00x(untested) & twrp3.0.3M4 (for encrypted devices or android n roms)

    Base v1.0b8 package doesn't contain any device specific files! Toolkit will automatically ask to download them for you if an action needs them, otherwise download & extract the device package (z00a/z008/z00x) on your own to the ressource directory.
    3
    v0.7 is out
    @fred_gaou: I've tested with win10. 1.0.3.2 works fine and will be default, but I've added 1.0.3.6 too. perhaps someone could test on other machines as i still have problems using it and don't know whats the problem.
    @holymoz: I've made a additional "full" package which contains all files. the "base" version still only contains the latest mm firmware files.
    @timbernot: Still thinking about it. Maybe some kind of decision tree asking for the problem could lead the user to an action that could cure the problem. I'll keep it on my todo list.