[A2017U - B29] "Fastboot Flashing Unlock" returns "Unknown Command" in ADB
Hi !
Quick info: I am not a novice when it comes to rooting / unlocking bootloader / installing TWRP or CWM / installing Xposed Frameworks, etc
I will make this short and sweet.
My Info :
- Axon 7 Gold - A2107U (US variant) with Update B29 installed (A2017UV1.0.0B29)
- Minimal ADB and Fastboot
- Windows 7 x64 Home premium
Here are the steps I have done:
1-
I installed the ADB drivers and Qualcomm WWAN drivers on my computer.
2-
Under Developers settings, I have enabled "OEM Unlocking".
3-
Using Axon7backup.exe, I created 2 backup files: "stock_recovery_backup.img" and "stock_boot_backup.img"
4-
Rebooted in bootloader using "adb reboot bootloader", (my device was listed). I first tried "fastboot oem unlock" then tried "fastboot flashing unlock", both returning "Unknown Command".
HERE IS WHERE I AM CONFUSED:
Normally, anyone would Unlock to bootloader THEN install TWRP, but from what I've seen with Axon7, some people say that Installing TWRP is "required" to unlock the bootloader.
I've seen some say that they have successfully rooted / unlocked bootloader with the B29 update, but I don't see any zip files or threads for the B29.
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you !
Could anyone enlighten me on the steps that I (and many others) have to do in order to Unlock the Bootloader and be able to install TWRP and Xposed Framework (and root).
Thank you ![/QUOTE]
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) I am assuming you already have the tool downloaded since you used it to create the backup files so just follow the same instructions to boot into edl mode, then open a command window where the tool is located. Then execute:
Code:
axon7backup.exe
to start the tool and then
Code:
axon7root.exe -p # -r
where # is your COM Port # in Device Manager. The tool will flash the signed version of TWRP with ZTE's signature from the leaked firehose onto your Axon 7.
2)Hold down volume up and power to exit download mode and boot into recovery which should now be TWRP.
3) Download the bootloader unlock zip from @DrakenFX: https://www.androidfilehost.com/?fid=529152257862665656. Flashing the zip will replace your fastboot image with the one from B20_boot.
4) After you have flashed the zip, reboot to bootloader and just execute
Code:
fastboot oem unlock
and you are good to go!
^^The stock fastboot does not support the unlocking command. There's another fastboot image in the bootloader unlock thread that gets flashed first. *THEN* you can issue the unlock command.
I've been messing with android at least since late 2009 and have seen many variants of unlocking processes. This one is new for me too.
bkores said:
Ok so the long story short is that the bootloader is not unlockable out of the box. When ZTE released the bootloader unlock, they released a separate ota for it called B20_boot from B20 which modified the fastboot image. It didn't make sense for a lot of people for ZTE to release a separate OTA since it would not allow them to recieve future otas (such as B29) so they are working on a new bootloader unlock. So since you are on B29 and the bootloader is not unlockable out of the box and you cannot update to B20_boot since you are not on B20 this is what you do:
1) Go to this thread: http://forum.xda-developers.com/axon-7/development/wip-axon-7-root-bootloader-unlokced-t3441204. Download @tenfar's tool for A2017U B20(axon7root.exe not axon7backup.exe). There is no tool for B27 or B29 because the OP is no longer active but it will still work(I have tested.)
Click to expand...
Click to collapse
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
EDIT: Should I do following command ?: reboot disemmcwp (to remove protect write, or it's no longer necessary? )
Boutchoo said:
I see that the release a "axon7root-us-b27.zip" here: http://d-h.st/kRgq
"Uploaded By: tenfar
Uploaded On: 2016-09-19 23:10:07"
Should I use the B27 or follow the B20 method ?
Click to expand...
Click to collapse
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool. And yes you should do "reboot disemmcwp" if you want to be able to make changes to /system
bkores said:
I edited my original answer. Since you already have axon7backup.exe you don't have to download the tool.
Click to expand...
Click to collapse
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password *NEVER MIND- FORMATED CELL, NOW WORKS*
Edit3: Do I need to flash SuperSU or is it pre-packaged ?
Boutchoo said:
Nice ! TWRP is now installed !
I was wondering, if I backup my DATA only using TWRP and restore them after doing "fastboot oem unlock", will I be able to get my apps back without breaking my system ?
EDIT: After doing "Fastboot oem unlock", TWRP gives me "Mount: Decrypt Data: Enter Password:"...
EDIT2: Ok now Android is locked... it's asking me to enter a password
Click to expand...
Click to collapse
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened. For some reason ZTE screwed up encryption to the point where if you backup data in TWRP with a pin/password/pattern enabled and then restore from it you will get a data decryption prompt where no password would work, not even your own. If you get this you have no choice but to wipe your data and then do either a Google restore during setup or use Titanium Backup(after you flash SuperSU) if you have it. In the future if you want to backup your data and until ZTE fixes it, you have to disable your pin/password/pattern first.
bkores said:
Did you just flash TWRP using -r or flashed the boot image as well using -b? Because if you just flashed TWRP the data decryption thing should not have happened.
Click to expand...
Click to collapse
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Boutchoo said:
I copy pasted your line "axon7root.exe -p 8 -r" only, did nothing else.
Also, do I need to flash SuperSU for the root or is it pre-packaged ?
Click to expand...
Click to collapse
Flash SuperSU
bkores said:
Flash SuperSU
Click to expand...
Click to collapse
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
bkores said:
You need SuperSU v2.65 as any other version will crash TWRP(no one knows why)
Click to expand...
Click to collapse
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Boutchoo said:
Ah, I see. It's weird !
Also, what does flashing the boot (-b) does with the Axon 7 ? It's weird that only recovery (-r) is necessary.
Click to expand...
Click to collapse
The modified boot image allows people without an unlocked bootloader to have root however if your bootloader is unlocked you should not do it as you will have the data decryption issue.
Boutchoo said:
When I flash SuperSU-v2.78-201609011115.zip from my SD Card, it crashes TWRP.
Click to expand...
Click to collapse
Try 2.65
Related
I've been trying for the last couple of days to root my MM G4 H815 v20e but all the guides I've tried to follow have either wanted TWRP installed before rooting, or root being required before installing TWRP. No matter which TWRP I tried, none would install. Yeah, the install would succeed ok, but when I tried rebooting into recovery all I got was the dead robot. Then I came across a method for running TWRP as a boot img and installing root from there. And it worked 100%, first time. So I'm putting this method on here so anyone else having the same problems as I had, can root their phone.
This is non-destructive but, as usual, I take no responsibility for you wandering from the path and breaking something. You will need an unlocked bootloader, instructions here, and your warranty will most definitely be invalidated after this. The original instructions were in Turkish, so many thanks to the original poster, and to Google Translate for at least making it understandable.
So I take it we're all sure what we're doing with adb, fastboot etc? This is serious stuff so if you don't think you're up to it, don't try it until you are. I'm just posting the method for rooting, the other stuff can be easily found. Plus it helps you understand the system of searching.
So when you're ready, connect your phone to your pc by USB cable, ensure USB Debugging is enabled, and off we go:
Step 1 - Visit https://dl.twrp.me/h815/ and download twrp-3.0.2-0-h815.img to your sdk/platform-tools folder. Rename it to "twrp.img". Copy this file to either the root of your internal memory or external sd card.
Step 2 - download SU zip from here https://download.chainfire.eu/921/SuperSU/UPDATE-SuperSU-v2.65-20151226141550.zip and rename it to "su.zip". Copy it to either the root of your phone's internal memory or sd card
Step 3 - switch to your sdk/platform-tools folder, shift and right-click on a white space and select "Open command window here"
Step 4 - type "adb reboot bootloader" [ENTER] then type "fastboot boot twrp.img" [ENTER]
TWRP will now run in memory
Step 5 - As TWRP isn't actually installed, you'll need to swipe the switch at the bottom to allow it to modify your phone
Step 6 - Tap Install and select su.zip. Select "Zip signature verification".
Step 7 - Swipe the switch at the bottom to flash the zip.
Step 8 - It would be a good idea at this point to also flash the TWRP. go back to the install screen. As it is an img file and not a zip you want to flash, tap the "Install Image" button at the bottom right, choose the twrp.img file you copied to the phone, and swipe to flash.
When complete, tap the Reboot button, choose Recovery and your phone should now boot into TWRP. Now choose to reboot to System and allow your phone to restart (it may take a while longer than normal and may reboot , mine did once).
And that's your phone rooted. Install Root Checker from the Play Store and run it to confirm your phone has been rooted.
Unlocked bootloader, I guess, yes?
cesedy said:
Unlocked bootloader, I guess, yes?
Click to expand...
Click to collapse
Without unlocking the bootloader he wouldn't be even able to boot the twrp img, since its unsigned by LG!
This is common sense
If I unlock the bootloader I´ll also fire up the twrp (not boot but simply flash twrp)
Root is just optional there
U rock man!!!
100% working!!!! i've been looking for this for so long and all tutorials were complicated and hard to follow and you came with this simple tutotial xD i have the same lg g4 h815 20e. You are the real MVP!!!:highfive:
But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).
dontpannic said:
But why? Why wouldn't you just install TWRP seeing as you've unlocked the bootloader, might as well make your life easier in the long run...
adb reboot bootloader
fastboot boot twrp.img
copy twrp.img to internal storage
in twrp -> install -> images -> twrp.img -> select recovery and swipe to install
Can't install TWRP via fastboot (fastboot flash recovery twrp.img doesn't work properly, have to flash the twrp.img inside TWRP itself).
Click to expand...
Click to collapse
Exactly, makes no sense
Sent from my LG-H815 using Tapatalk
Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...
snail22 said:
Will it work on LG G4 H815 V10d ? anyone tried it ? I hate it not having root, thats the first phone i have so many problems rooting it...
already unlocked my bootloader...
thanks...
Click to expand...
Click to collapse
Since you have unlocked bootloader anything will work
you can simply boot the twrp (like the op shows) and flash supersu
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root
bender_007 said:
or rather -> copy twrp img to the internal, boot twrp (look op) and flash the twrp img (tap first the zip/img checkbox) --it will ask where to flash -> select recovery, don´t tap boot...
Then you might also flash the supersu
and now you have twrp and root
Click to expand...
Click to collapse
Great, This looks like what I want, will try in the evening, if this work, I will be able to use TASKER AGAIN !! hooray :laugh:
The problem with the boot loop is only in the devices that are bootloader unlocked ? My H815 (506) is locked...and i was thinking at unlock the bootloader, but, i am "afraid" of the boot loop.
No, it's random
Sent from my LG-H815 using Tapatalk
Its because of a hardware problem, isnt?
Sent from my LG-H815 using XDA-Developers mobile app
Exactly, we have a poll about it but I see sone 505, 506 users wanted to re-vote because their phones died. :/
Sent from my LG-H815 using Tapatalk
Did work h815 TWN ? I need to root or unlock bootloader. Help me pl0x
Hey,
I have H815 6.0 with locked bootloader v20e
will this work for me? or i have to unlock the bootloader first? i just want root
can i use this method for v20d? thx.
After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached
xyster13 said:
After typing "adb reboot bootloader" phone restarts to bootloader. And thats it. Typing "fastboot boot twrp.img" does nothing but writes <...> is not recognized as and internal or external command, operable program or batch file. Whats going on? Also if i type adb devices there is empty list of devices attached
Click to expand...
Click to collapse
You don't have fastboot installed, or you're typing the command wrong.
c:> adb reboot bootloader
c:> fastboot boot twrp.img
What happens if I want to go back to stock, will the device remain as it was before rooting and will receive OTAs and allow device encryption and all?
I'd like to know if there's a way to remove the 5 second "Your device has been unlocker and can't be trusted" message that started coming up every time I boot when I unlocked the bootloader on my A2017U.
If I understand correctly, this was added in B29 and I just need to flash the B27 boot sequence and then unlock it. Just not sure exactly how to do that, and what specific files I need.
Thanks
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
DrakenFX said:
I'll just get used to that Boot Message, for the whole reason of if you want BL unlock when N hits, you are going to have that message unless ZTE changed the way it boots.
Otherwise you can flash B20 aboot.img to remove such thing.
Click to expand...
Click to collapse
Hi,
I unlocked my A2017G using controllerboy's method. I didn't get this message then. But after flashing the B11 full rom from ZTE's webstite (using the update.zip from my SDCard) I now also have this message. Since I'm on a A2017G I can't flash the B20 boot.img i guess. Can I flash the boot.img from controllerboys thread or will that brick my device because of the B11 ROM?
Side note: I didn't get offered the update to Nougat (even without root) now I'm on B11. Not sure if I want to switch no Nougat yet without xposed, but if I wanted, how would I proceed?
Many thanks in advance,
Cheers,
/Cacti
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Can you provide a quick tutorial for flashing aboot.img? Tried with fastboot flash and it failed.
Thanks!
Bomberus said:
The Boot message is not in the Boot.img. You habe to flash the old aboot to get rid of the message. I already did it and it is working fine.
Click to expand...
Click to collapse
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
le_cactus said:
Thanks! That worked flawlessly!!!
@shifuharris: Take a look here: https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
You need step 1,6 and 13 of the B) Unlock the bootloader part
Worked for me.
Cheers,
/Cacti
Click to expand...
Click to collapse
Thanks for the help. However, I get a permission denied error when I try to execute step 13. Not sure why. Device is rooted. Any suggestions?
Thanks!
I had the same. I opened a terminal window, gave the su command and then did the dd commmand. Hope I make sense.
Cheers,
/Cacti
Sent from my ZTE A2017G using XDA-Developers Legacy app
Installation Procedure
To summarize the procedure:
First use adb to copy aboot and fbop (if you want to use the fastboot features) to your sdcard)
Then flash the aboot and fastboot(only needed if you want the fastboot lock/unlock options) images
Enjoy your unlocked phone
See B : https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
Code:
#copy necessary files to internal sd card
adb push aboot.img /sdcard/
adb push fastboot_unlock.img /sdcard/
#make a backup to your internal sd of the partitions we are going to modify
adb shell dd if=/dev/block/bootdevice/by-name/fbop of=/sdcard/fbop_lock.img
adb shell dd if=/dev/block/bootdevice/by-name/aboot of=/sdcard/aboot_lock.img
#copy them to your pc
adb pull /sdcard/fbop_lock.img
adb pull /sdcard/aboot_lock.img
#flash the proper fastboot and aboot file
adb shell dd if=/sdcard/fastboot_unlock.img of=/dev/block/bootdevice/by-name/fbop
adb shell dd if=/sdcard/aboot.img of=/dev/block/bootdevice/by-name/aboot
I also added the old aboot and fastboot_unlock image. For me as a european user the fastboot unlock options was initally not available.
The bootloader message actually saved me from softbricks so I don't mind it being there
On my ZF3, I'm on Nougat with the bootloader unlocked and I've confirmed that.
Followed instructions on the XDA ZF3 ROOTING GUIDE thread & ZF3 Toolkit, I can't seem to flash TWRP due to an error.
"
sending 'recovery' (26636 KB)...
OKAY [ 0.912s]
writing 'recovery'...
FAILED (status read failed (Too many links))
finished. total time: 1.075s
"
I've enabled USB debugging and even restarted, redownloaded drivers, changed USB ports and re did again but still the same error.
Any tips and solution?
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
sensi277 said:
Try booting TWRP first, then flashing from within TWRP.
The command is "fastboot boot <path to TWRP image>".
Click to expand...
Click to collapse
Just tried right now, did the command but its stuck at booting. My zf3 didn't boot the .img
Prev was too blurry
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
wang1chung said:
Have you been able to flash anything via fastboot from that computer?
Which OS are you using, windows? Firewall disabled? Do you have another computer you can try it on? From what I've read, it's a driver issue causing this and since you've tried reinstalling them, I'd try downloading the USB bootable version of Linux and try again. The commands are the same.
You may be able to flash it through an adb shell too, but I'd try the Linux USB first. On the ze552kl, the recovery partition is #59, so the command would be "dd if=/sdcard/TWRP.bin of=/dev/block/mmcblk0p59".
Edit: I see you posted in the other section you tried other computers so i guess try the DD command. Only thing is, you should back up your original partition first just in case because something is definitely bizarre. Run "dd if=/dev/block/mmcblk0p59 of=/sdcard/recoverybak.bin" first so you can revert if it goes awry.
Click to expand...
Click to collapse
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
TiTAN-O-One said:
How do you restore that ".bin" if anything fails? And if it does fail, what's the "problem" that I'll be having to fix?
Click to expand...
Click to collapse
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
wang1chung said:
You restore it with the same DD command you used to flash the TWRP recovery bin (dd if=/sdcard/recovery.bin of=/dev/block/mmcblk0p59)
No access to recovery is the problem you'll have.
edit: wait, do you get the warning screen on bootup now since unlocking? The one where you hit the volume keys to get to recovery/bootloader mode?
Click to expand...
Click to collapse
I unlocked my ZF3 via the "0.unlock_ze522kl.bat" way. Some people complained that the official way of unlocking frm the Asus website broke their devices or smth.
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
TiTAN-O-One said:
Got me a "No such file or directory" when I dd. "Failed to open /sdcard/TWRP.bin"
No warning screen as far as ik. I unlock unofficially. Am I right to say that under the Asus bootloader, a barcode will be seen when it is unlocked?
Im on Nougat officially.
Click to expand...
Click to collapse
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
wang1chung said:
Not sure about the unofficial way but with the official way you get that bootup menu I mentioned along with a warning screen that your phone isn't secure or something. I believe the unofficial way only works on marshmallow, did you use it on nougat?
You have to take the TWRP bin and place it in the root of your sdcard and then try the command.
Click to expand...
Click to collapse
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
TiTAN-O-One said:
Okay i can confirm the "Bootup and device is insecure" screen is the official way to Unlock your bootloader. I didn't do via that way cos I'm on Nougat. I did the unofficial way cos that's meant for nougat.
As for the TWRP flash, i did everything and still the same. TWRP.bin is at the chosen directory. Just to confirm, its all done under ADB right? And then simply use the dd command right?
Click to expand...
Click to collapse
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
wang1chung said:
We're talking internal sdcard, right? While in the adb shell, cd to /sdcard and do an ls and verify you can see your TWRP.bin there.....I think it's case sensitive too.
Also, remember I said to back your original one up just in case, so try to do that and verify everything is working.
I was under the impression the unofficial unlock didn't work on nougat and the official did? I thought it was some people doing the unofficial unlock that bricked their phones, which is why I chose the official, lol.
Click to expand...
Click to collapse
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Found a thread here and a user says
"The ASUS Zenfone 3 comes shipped encrypted by default. This is required by Google's Play Services agreement for phone OEMs. You cannot remove decryption on the Zenfone 3 without using a custom ROM"
I had this annoying "reboot and type my pin password" whenever I restart my phone.
Any idea how to remove or decrypt this? I believe this is the issue to all the failed and permission denied errors i guess.
TiTAN-O-One said:
Right guess what m8. I realised that I didnt and now couldn't unlock my bootloader. Here's what I did for the Unofficial Nougat way of unlocking ZF3 bootloader
Download this Zip file containing a folder called RootZenfone3-master.
Inside this folder contains 4 .bat files that is automated and named orderly so users can easily unlock and root their ZF3.
1st bat file being UnlockzeXXX.bat
2nd bat FlashRecovery.bat
3rd bat GetRoot.bat
Now 1st bat is obvly the bat file to unlock bootloader, ran it, followed the instructions to boot to bootloader etc and waited, only to know that unlocking the bootloader was unsuccessful.
Neermind that, if the bat file wasnt working, you can manually "Fastboot flash all" a file called unlock_ze552kl.raw that i believe contains a partition to unlock the bootloader.
So yes I ran the command but now i have an error that says
"FAILED (remote: Partition flashing is not allowed)"
Same error for both my Linux and Windows machine.
Click to expand...
Click to collapse
That "FAILED (remote: Partition flashing is not allowed)" error means you're bootloader isn't unlocked. I believe that is the root cause of your issue.
Use the official unlock, works every time.
The pin at the beginning bootup is a security setting. I believe there was a thread where someone said to disable security lock and then reenable it but chose "no" when it asks to use pin to start device. Give that a shot first and see.
For the official bootloader unlock, is it compatible with Nougat?
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
TiTAN-O-One said:
Good news, it IS compatible with Nougat. Now my bootloader is unlocked and TWRP is installed successfully. However, i don't seem to get any root access despite flashing the latest supersu.zip nunerous of times. Any ideas why?
Click to expand...
Click to collapse
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
wang1chung said:
Do you see the SuperSU icon in your app drawer?
Did you follow this guide and install all four zips?
I had an issue and needed to update busybox, but that was easily done from the playstore.
Click to expand...
Click to collapse
Great! Everything is settled and Im unlocked and rooted successfully too. Thanks for the help.
Glad you got it sorted, now make a TWRP backup of all your partitions and go crazy flashing lol
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
Guys, no one to help or assist?
Mr147 said:
Guys, no one to help or assist?
Click to expand...
Click to collapse
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
X10MINISTER said:
Did u try running the command at the adb folder?shift+right click in adb folder?
Is Usb debugging enabled in developer options?
Click to expand...
Click to collapse
Yes, everything done.
Still no success.
Mr147 said:
Yes, everything done.
Still no success.
Click to expand...
Click to collapse
Did ur unlocking bootloader succeed?
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
X10MINISTER said:
Did ur unlocking bootloader succeed?
Click to expand...
Click to collapse
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Tyakrish said:
Did you try relocking the bootloader ?
1) Try relocking the bootloader using the methods described here :
https://forum.xda-developers.com/max-pro-m2/how-to/unroot-relock-bootloader-max-pro-m2-t3885870
See if it successfully relocks...
If it does, then next time unlock using the unofficial method only...
2) If not then maybe try contacting ASUS... Tweet them on Twitter... Companies usually respond very fast on Twitter, since their reputations are at stake...
3) All else fails then try rooting it using something like Kingroot... Once rooted, flash TWRP Recovery using Flashify... then flash any custom ROM u want...
I hope your problem gets solved... Next time be a little more cautious when taking such a risky step... See what are all the options you have before jumping into something...
Click to expand...
Click to collapse
Tried everything except 2, none worked. I'll drop them a query over twitter like you say, let's see what their reply is.
I am on stock recovery, non working bootloader but unlocked, and stock rom unrooted.
I think Pie update may give some insight on fixing this.
Mr147 said:
I guess it did because when I reboot it I get that bootloader unlocked splash screen.
Click to expand...
Click to collapse
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
X10MINISTER said:
I see.. did u've try using another laptop/pc? Sometimes antivirus blocking the tools that are needed for unlocking bootloader..
Click to expand...
Click to collapse
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Mr147 said:
I unlocked using official bootloader apk provided by asus. Now I have encrypted phone which isn't decrypting and can't flash twrp.
Click to expand...
Click to collapse
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Note:
- This method is highly experimental... There are 50% chances of bootloop. I would not have recommended this method, but situation seems to demand it.
- Your data will most probably be formatted, so keep a backup.
- If it falls in a bootloop, then you need to flash original stock firmware to restore your phone.
Credits: @#ArtFuL
Who came up with this method, but removed it from the main guide, because of being experimental... (I guess)
Click to expand...
Click to collapse
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
#ArtFuL said:
After going through the errors, I strongly believe that the problem is with your drivers. If reinstalling doesn't works, try a different pc. If your pc detects your device on MTP or your are able to perform adb operations without any hassle, it's not the problem with your phone.
You can decrypt the device only after flashing custom recovery.
---------- Post added at 09:35 PM ---------- Previous post was at 09:31 PM ----------
Yes this method is highly experimental. Also in this situation, he cannot use any fastboot commands. So this method won't work
Click to expand...
Click to collapse
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
So is it done?
Mr147 said:
This method didn't work, as fastboot isn't accepting any command. I tried giving command before connecting phone and then connecting, it gives me error of "File size is more than max allowed".
Click to expand...
Click to collapse
See I recommend please use Linux (Manjaro or Ubuntu) , Windows will have driver issues forever and ever
had same issue after fota update UL-ASUS_X01BD-WW-15.2016
Tyakrish said:
Hey you said phone is encrypted ? Maybe this might work :
1) Download and install the latest Magisk Manager apk
2) Extract boot.img from stock firmware
3) Put boot.img in your internal storage and open magisk app.
4) Click on install and select patch boot Image.
5) Select stock boot.img file placed in phone memory.
6) Magisk will automatically patch the stock Image and this patched image can be installed using fastboot using this command:
fastboot flash boot patched_boot.img
This will root your phone. After that you can install Flashify to flash TWRP or PBRP
Thanks , this method work me. had same issue after fota update UL-ASUS_X01BD-WW-15.2016.1902.192-user
Click to expand...
Click to collapse
I've the same problem too. Let me know if you've configure it out. Thanks.
Okay @Mr147, I've fix this. I checked Windows Update and there was a pending ASUS driver update. I downloaded it and now I can use the fastboot commands.
Anyone that can fix this problem? I also experience this.
Mr147 said:
Hi guys,
I am using Zenfone Max Pro M2. I wanted to install a custom rom and I tried to unlock bootloader but I unlocked it through official unlocktool. Now I can't flash anything or send any command through fastboot, whenever I do then it restarts the device.
When I try to keep the fastboot command running and then connect phone - it throws errors like "Fail - Too many links", "Fail - Write to device fail (No such file or directory)" or "Fail- Unknown command".
I tried unlocking bootloader with the unofficial way provided in https://forum.xda-developers.com/max-pro-m2/how-to/unlook-bootloader-root-asus-zenfone-max-t3885457
but it isn't working either, any fastboot command is rebooting the device although bootloader is unlocked.
How do I fix this?
EDIT: Things I have tried:
- Changing USB Cable and Port
- Reinstalling ADB and device driver
- Reunlocking bootloader from UnlockTool (don't know why I did that again)
- Unofficial way to unlock bootloader
None of it helped.
Thanks
Click to expand...
Click to collapse
I suggest to Unlock with unofficial step, or read the post https://www.blocknesia.com/2019/04/unlock-bootloader-dan-install-twrp-asus-zenfone-max-pro-m2.html
With the huawei support down, could anyone please help me to unlock huawei nova 2i RNE-L22 bootloader and to root it?
DC. UNLOCKER?
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
bootloader unlock codes forbidden
Chisetdel31260 said:
DC. UNLOCKER?
It says
> If your phone runs Android 8 or later with latest security patch - then this service won't work!
I have the latest security patch(March 1, 2019), I've been searching for the past 3 days for a working method to root my mate 10 lite, found nothing.
Huawei stopped providing oem unlock codes, All the services that provided unlock codes for money are now obsolete too.
I'm trying to find a way to root this phone on my own, but I'm not sure where to go from here.
I've read this book today "XDA Developers' Android Hacker's Toolkit", but it teaches how to use rooting methods that are already out there and not how to create your own way to root a device.
Can you provide guidance on where to go from here to learn how to find vulnerabilities in android?
Click to expand...
Click to collapse
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite .
it works
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
(4€/4$).
Service ROMs you can find here :
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
m10_lite said:
Thanks, it worked!
I got my bootloader unlocker, now I'm installing a custom rom, but there's no much custom roms for mate 10 lite.
Click to expand...
Click to collapse
Best Custom ROM is Stock ROM & root .
bozka1 said:
Best Custom ROM is Stock ROM & root .
Click to expand...
Click to collapse
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
He did already
bozka1 said:
"If your phone runs Android 8 or later with latest security patch - then this service won't work! " it's true , you must downgrade to Nougat via HiSuite ane than using Service ROM flash FW with security patch max. april 2018. After you can get bootloader unlock code here
https://www.dc-unlocker.com/how-to-read-huawei-bootloader-unlock-code
(4€/4$).
Service ROMs you can find here :
https://androidhost.ru/search.html
Type RNE- or Rhone or Mate 10 lite. Gl!
Click to expand...
Click to collapse
ante0 said:
He did already
Click to expand...
Click to collapse
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
davideakc said:
Sorry, I've not explained clearly what i want to do...
I'm already with bootloader unlocked, I need a guide for root the phone
Click to expand...
Click to collapse
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
ante0 said:
Sorry, I misread. xD
Well, you can either flash TWRP for Oreo. Not sure which is "best" though, take one with decryption support if available for RNE on Oreo. Then you flash Magisk zip in twrp.
Or you can take your stock ramdisk and patch it in Magisk Manager, then flash the patched ramdisk from fastboot.
I would provably go with TWRP and Magisk zip though, as you would need a stock ramdisk from an update.app of your build. So saves some downloading
Basically flash TWRP using fastboot: fastboot flash recovery_ramdisk twrp.img
Reboot to recovery which will end up in TWRP. Flash latest Magisk using the Install button in twrp.
Click to expand...
Click to collapse
Don't worry, thanks for the fast reply!
davideakc said:
Don't worry, thanks for the fast reply!
Click to expand...
Click to collapse
I can't find any TWRP with decryption. This one might work, it's from the MorfuZ thread: https://mega.nz/#!uD4FlCqL!ERBzP4ZWa2sR8f_wnn15F_cOFCdYVKgfYETjiehQkkQ
So it may or may not have working decryption. But if you have an external SD it doesn't really matter as you'd only transfer magisk to that.
Magisk from here: https://forum.xda-developers.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
Download latest stable.
Flash twrp using fastboot.
Reboot to recovery.
Transfer magisk zip to external SD.
Flash Magisk zip using the Install button
You will probably have to browse to /external_sd manually as it will default to /sdcard in the install browser.
If it fails to install using TWRP:
Open terminal in TWRP from the Advanced button then enter this command:
dd if=/dev/block/bootdevice/by-name/ramdisk of=/external_sd/ramdisk.img
This will dump your stock ramdisk to external sd, which you then can patch in Magisk Manager and flash the output file to 'ramdisk' using fastboot. You will have to install Magisk Manager apk first though, it can be found in the Magisk thread.
davideakc said:
Do you have the guide for rooting RNE-L21, stock ROM, Android and EMUI version 8.0?
Click to expand...
Click to collapse
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!Fgd0xa4R!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
bozka1 said:
Only EMUI 8.x !!!
Your device must have an*unlocked bootloader.
Huawei HiSuite installed on your computer because it will install all the USB drivers
Download and install*Minimal ADB and fastboot Tool*on your computer. The folder location should be C:\Program Files(x86)\Minimal ADB and fastboot.
https://www.the***********.com/minimal-adb-and-fastboot-tool-for-windows/
Download*TWRP-oreo-smart.img*file
https://mega.nz/#!ot8TGIIa!1o5ejzDnkLJLG2tAZG-STtlJ4nnNCHfwwZdOlmOkrVw
Copy the downloaded* TWRP file to the*Minimal ADB and fastboot folder.
Enable OEM unlocking on your phone (developer options) and USB debugging mode.
Now launch MAF32.exe (or cmd-here) file from the Minimal ADB and fastboot folder, a command window will open up.
Turn off your phone and connect to your PC. Reboot to fastboot mode using button combination Power and Volume down.
In the command window, enter the following commands one by one
- fastboot devices - this command will verify connection in fastbot mode (you will see your serial number)
-fastboot flash recovery_ramdisk TWRP-oreo-smart.img
-fastboot reboot - the device will reboot
Now you can boot into TWRP mode using button combination Power and Volume Up or command*
adb reboot recovery
Download and copy to SD card latest Magisk.zip.
Boot your phone into TWRP,* in TWRP main menu tap 'Install', then navigate to the*Magisk.zip , tap it, then ‘Swipe to confirm Flash’.*
When the process is complete, tap Reboot System.
Enjoy !*
Click to expand...
Click to collapse
If I do this, I lost all apps and data or not?
davideakc said:
If I do this, I lost all apps and data or not?
Click to expand...
Click to collapse
No you won't, but you should always backup your data.
AztekSoul said:
No you won't, but you should always backup your data.
Click to expand...
Click to collapse
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Yes you can, although you have to download updates through firmware finder and update with HuRUpdater in twrp.
davideakc said:
And after flashing that TWRP can I still install Huawei updates like security patches etc... even if I don't have stock recovery?
Click to expand...
Click to collapse
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
bozka1 said:
Then there is another solution - install TWRP over eRecovery (my own experience) :
- copy to SD card TWRP-oreo-smart.img
- in main TWRP menu tap Install image, then navigate
to the TWRP-oreo-smart, select
eRecovery_ramdisk and confirm Flash . System
reboot.
- Download and copy to the Minimal ADB and fastboot folder RECOVERY_RAMDISK330.img
https://mega.nz/#!I511VK4b!9cGodiCORHOvXndOCHyqcezpHmUk2zeTslqpbZe8pk4
Connect your phone to PC in fastboot mode and install recovery_ramdisk using command
- fastboot flash recovery_ramdisk RECOVERY_RAMDISK330.img
- fastboot reboot
How to boot into TWRP: reboot your phone and press Volume Up key up to 3 seconds to enter TWRP.
Click to expand...
Click to collapse
After that, how can I restore factory eRecovery?
davideakc said:
After that, how can I restore factory eRecovery?
Click to expand...
Click to collapse
Okay, one can install Magisk without TWRP. There are plenty of guides on how to do these things in the Mate 10 forums. Of course, TWRP makes things easier ....