Database Users

[TOTAL NOOB GUIDE][Back to Stock][VibeK5Plus][Snapdragon][MORE]FLASH LENOVO TO STOCK

Hi everyone,
This guide is intended for only snapdragon version of Lenovo devices which supports QFIL (Qualcomm Flashing Tool). For MediaTek Devices, you need different tools.
However, please understand that the device which I had to test in length was LENOVO K5 PLUS and thus, recovery, stock images and development is for K5 plus. As long as you have stock rom, custom recovery or custom rom of your specific device which you own, you can follow this guide for any snapdragon device but booting your device into DIAG mode might need different commands.
TABLE OF CONTENT
Recover Your Device
EFS
Driver Guide
TWRP
Root
Backup device
Stock and Custom Roms
Future Issues
FAQ
Credits​
(Don't know what is brick or ANDROID BASICS, click here to quickly go through them) HIGHLY RECOMMENDED
Code:
This guide is for those who understand the risk of their actions.
I have fully tested this guide and I found no issues, however,
I am not responsible for world wars, broken phones,
flying machines, dead SD cards, [B]girlfriend breakups[/B]
or any damage by your actions and only join in the forum
with [B]popcorn[/B] to enjoy myself at your suffering in case you
didn't follow the instructions and later blamed me for it.
IMPORTANT :
I suggest you start this guide by directly going to POST 5 BACKUP FULL DEVICE before you intend to do any experiments with your device. Make a FULL BACKUP WHICH IS HIGHLY RECOMMENDED OR YOU WOULD NOT BE ABLE TO USE OTAs LATER) Requires no root
DRIVERS ARE MUST HERE
You can simply download all the drivers from post three and install them all. In case you have troubles, you can refer HERE for more details.
WHAT YOU NEED
1. DRIVERS
2. USB DEBUGGING
3. ADB
4. TOOLS & STUFF (all in attachments)
5. Little Common Sense
6. Zero Skills
USB DEBUGGING ON
1.Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Done
SETUP A WORKING ADB
Download platform tools from here in attachment
Extract them to any location.
Navigate to the location where you have extracted platform.zip
Hold crtl+shift on keyboard and then use your mouse to right click on an empty area of the folder.
Select open command prompt here
An cmd window will open
You are ready to go
Alternatively,
if that does not work for you. Simply download the platform.zip and extract it to C:/platform-tools.
Rename platform tools folder to adb
Go to cmd from start menu
Type in these commands until you see C:\> in cmd.
You will need to type twice most probably.
Code:
cd..
cd..
then type the following once you are at C:\>
Code:
cd adb
You will be in ADB folder, which will be now like C:\adb>
Now you have a working adb
RECOVER YOUR BRICKED DEVICE
There are actually 3 methods in theory to recover your phone. However,I also found that sometimes you can not flash your device using download mode and in this case, fastboot mode is the only route which means you will need to use TWRP or find a method to go into EDL from fastboot. So after you brick your device, your device can present in the following states.
No recovery or download mode but fastboot mode
Download mode
Recovery mode
Phone goes into download mode on its own
Possible Solutions
TWRP Method if you have a custom recovery or only fastboot(tested and works)
QFIL (tested and works) if you can boot into download mode
Lenovo Updater (untested)
ONLY FASTBOOT ACCESSIBLE NO DOWNLOAD/ RECOVERY.
Phone goes directly into download mode but QFIL unable to flash at all. Need to find a way to boot into EDL. Currently under working. Check this here Gold for those who need to boot to edl from fastboot
Fail with status when trying to flash using QFIL
Code:
Download Fail:System.Exception: Failed to Switch to Emergency Download mode
at QC.QMSLPhone.Phone.QPHONEMS_SwitchToEDL()
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
Download Fail:Switch To EDL FailSystem.Exception: FireHose Fail
at QC.SwDownloadDLL.SwDownload.SwitchToEDL()
at QFIL.Tech.DownloadTech.SwitchToEDL()
Finish Download
Two ways possible. Flashed TWRP and it worked by restoring previous backup. Works like a charm
Fastboot to edl needs some work. If that could be achieved. It will be brick proof.
TWRP METHOD
Pre Requisites
Fully working TWRP with root (preferable)
backup of your device (highly recommended) or download stock flashable roms HERE
STEPS
Boot into fastboot mode (bootloader) by switching off your phone and then press volume - and power
Flash TWRP recovery using fastboot commands HERE
Flash your previously made backup using RESTORE function in TWRP
To flash recovery partition, you will need to select flash IMG instead of preset ZIP when you navigate to INSTALL. You will find it on lower left side
DOWNLOAD STOCK RECOVERY FOR YOUR DEVICE HERE
You will need to unroot your device as well from supersu settings if you want to return to FULL STOCK
In case you only have fast boot mode and no recovery AND no download mode
Pre Requisites
You must have a fully working TWRP and possibly rooted
flashable zips of your stock roms or any previously made backup
STEPS
Simply place your update.zip in your sd card if you are using stock images
Or you can copy your previously made TWRP backup in sd card
Restore using TWRP if you have a backup
or flash via TWRP if you are flashing stock Images
Done
I highly suggest you wipe your device in TWRP including system
QFIL METHOD
Download stock image for your device. Make sure you choose the correct file for your device or you can hardbrick your device
Install QPST and QFIL software from attachments.
You may need to install Microsoft Tools which are provided in attachment for QPST to work
I assume that you have already proper drivers installed
Extract your device stock images in any given location of your choice but prefer it like D:/stock images etc
Open QFIL from start menu
Refer to image attachments 1,4,5,6,7 for the next steps
Browser Programmer Path and navigate to where you have extracted stock images.
Select the file with the given extention .(firehose)
Next load XML file and select the image.
It will ask for another file which you will be able to locate in the same folder\
Connect your device and see if the port is detected as QD LOADER
Select DOWNLOAD under LOAD XML
Sit back and enjoy. It should take 5-10 minutes
NOTES FOR QFIL
Bootloader Method does not seem to work. Even after changing drivers and replacing them.
Works with keys too. Hold Volume + and power after switching off device and select download!
Requires EDL method
Lenovo Serial driver required
Adb reboot edl
Then install drivers for Qualcomm port
Flash as instructions
Erase Misc after flash
Wait for device to turn on
STATUS : COMPLETE
Last updated 26.08.16

EFS
Pre Requisites
Installed drivers. ( See Next posts for detailed guide.)
Enable USB debugging. See first post
Working ADB (Download from attachment)
You will need to move to the location where you have extracted adb.zip
Hold crtl+shift + mouse right click and select open command prompt here and then you can give commands.
Root
[*] Recovery
TWRP BACKUP
I find this method most superior to all others.
Download recovery from this forum. All credits to the developer to make it possible
DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
After downloading the recovery, using a working adb. Enter commands
Does not require root
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
You will boot into recovery with Russian translation. Change translation to your local language as shown in attachments TWRP 1 and TWRP 2.
Make EFS and all other backup and keep it safe.
I suggest you copy this to your PC before you plan to do something else with your device.
Done
Enable DIAG MODE on your device using adb.
Code:
adb shell
su
setprop sys.usb.config diag,adb
Once your phone is in DIAG mode, you can utilise these methods for QCN.
QCN is a file that holds all your data regarding your signals, bluetooth, wifi, imei etc
If you lose it without a back, it may be very hard to fix your phone.
For first two methods, you need to be in DIAG mode. For the last two, you can make a backup on your mobile. All four methods require root.
QCN EXTRACTION BY QFIL
Simply open QFIL on your PC.
You will see
QPST>Tools> QCN backup and Restore.
Select Backup in your desired location
Done
QCN backup by QPST other tools.
1.First time you are trying to make a backup of your QCN using this method, you will need to add DIAG port which you enabled via adb commands in QPST.
For that , go to QPST>BIN>QPSTConfig. You might need to go to show all ports before you are able to add it.
2.Next go to, QPST > Bin> QPSTServer.exe
3.A globe would appear in taskbar. Click on it and select software download from the tab
4.Select port of your diagnostic mode in backup tab of software download.
5. Once in software download, backup your current QCN
4. Done
Backup by blocks
This is a better method to make a backup. You can either use adb commands or simply download PARTITION BACKUP APP from play store. This will automatically backup your partitions.
PARTITION BACKUP TOOL PLAYSTORE LINK
XDA FORUM LINK FOR ANY QUERIES
These are ways to check your device for partitions manually. You can make backup of these yourself as well.
Detailed guide is given here
Code:
adb shell
cat /proc/partitions
[B]OR[/B]
adb shell
ls -al /dev/block/platform/dw_mmc/by-name
make sure you replace dw_mmc with your device partiton. (I have not checked it yet)
[B]OR[/B]
adb shell
cat /proc/partitions
adb remount
adb shell "su" "" "mount -o remount,rw /system"
adb push parted /system/bin/parted
adb shell
chmod 0755 /system/bin/parted
parted /dev/block/mmcblk0
print
Backup by tar.gz and Img
For this method you will need to download EFS BACKUP from playstore and then you can make a backup. I recommend make backup in all three formats.
EFS BACKUP PLAYSTORE
XDA FORUM LINK FOR THE APP
That's all you need for a good EFS Backup. Good Luck!

DRIVERS GUIDE
On Windows, it will automatically detect all drivers.
Make sure your device is attached to PC, before you install these drivers.
You may need to download drivers for ADB and QDLOADER which are all provided in Lenovo Usb driver.
So Installing these driver will be enough for you and you may need to manually select drivers for rest from lenovo folder
For ADB drivers use LENOVOUSB DRIVER 1.1.16 if your device is not detected by Windows.
For QHUB drivers use these in attachment named QDLOADER HS USB DRIVER.
Simply Install them and you are good to go.
INCASE YOUR DEVICE IS NOT DETECTED
All drivers are contained in these folder C:\Program Files (x86)\LenovoUsbDriver on your PC.
Go to My computer> Properties? Device Manager and see if you have any unknown devices like shown in attachment.
If you have, then I suggest you install manually.
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
ADB contains all ADB and Bootloader drivers
Use ADB folder if you are installing drivers for adb / fastboot/ bootloader.
Make sure you have usb debugging and device connected when you are installing these drivers. You have to be in normal mode for adb drivers
.
You can check if you have working adb by typing
Code:
adb devices
To download fastboot / bootloader drivers, simply first boot your device into fastboot.
Turn off device
hold power and volume down
Now try to install fastboot drivers
Serial Contains EDL drivers (Download mode drivers)
Select unknown device and go in its properties.
Next go to drivers tab and select update drivers
Select Browse my computer for drivers
Let me pick from the list of devices
Select have disk
Move to folder C:\Program Files (x86)\LenovoUsbDriver
You will see that there are many folders.
Use Serial if you are in download mode / EDL mode.
Working adb is required for this
You can go into EDL mode directly from adb commands by
Code:
adb reboot edl
OR
You can power off device
hold power and volume up
Select download mode and you are in EDL/ Download mode.
Now you can install drivers from above method
Make sure you select QDLOADER 9008 while installing EDL drivers.
How to enable QHUB drivers if no unknown/ undetected device is seen
Sometimes, your device is not detected in QFIL and you have all drivers installed and there is no unknown device in my computers> device manager.
For this, you will need to attach your device first.
Go to Device Manager by going into my computer properties
Look for ADB Interface drivers in device manager.
Update drivers for ADB interface and replace it with QDLoader HS USB driver.
If it asks for any permission, allow it.
In case your windows do not allow you to install these drivers , you need to turn off Digital Signature Verification in windows
run cmd as run as administrator
Type in these commands
Code:
bcdedit.exe -set loadoptions DDISABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING ON
Restart
Then try again to reinstall drivers
To re-enable device verification on Windows
Code:
bcdedit.exe -set loadoptions ENABLE_INTEGRITY_CHECKS
bcdedit.exe -set TESTSIGNING OFF
Good luck

ROOT AND TWRP
HOW TO ACTIVATE USB DEBUGGING
1. Activate the Developer options (Settings> About phone> Device Information> to tap 7 times in Build number)
2. Enable USB debugging (Settings> Developer> USB Debugging)
3. Enable OEM unlock (Settings> Developer> Unlock OEM)
4. Connect the phone with the USB cable to the computer
5. Install the drivers that come on the CD cell partition.
TWRP:
Download TWRP from HERE or TWRP WITH EFS BACKUP AND MORE
Copy it to the folder where abd is installed.
On working adb, type in these commands
Code:
adb reboot bootloader
fastboot flash recovery LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot flash recovery TWRP-k5-3.0.2-r2_shreps.img
This will permenantly flash twrp instead of Stock recovery.
If you just want to boot it once. check backup guide by using this command instead
Code:
fastboot boot <file name>
ROOT
Download the ZIP file SuperSU v2.76 and save it in the micro SD card.
Restart the phone in recovery mode:
Turn off the phone, then turn it on while pressing the volume up button. a screen appears with various options and choose "recovery".
You can even boot by adb commands using
Code:
adb reboot recovery
[*]
When opening the recovery, select Install and locate the file you downloaded just now.
Confirm execution flashing, restart the phone and voila!
ORIGINAL POST HERE
Editing the post with permission

BACKUP GUIDE
I HIGHLY RECOMMEND TO BACKUP YOUR DEVICE BEFORE YOU NEED TO EVEN ROOT YOUR DEVICE OR FLASH TWRP . IF YOU FAIL TO DO THIS, YOU WILL HAVE TROUBLE UPDATING YOUR PHONE VIA OTA ESPECIALLY IF YOU ROOT YOUR DEVICE
THIS IS MUST AS YOU CAN ALWAYS EASILY REVERT BACK TO YOUR ORIGINAL STOCK STATE IN CASE YOU NEED IT.
Download TWRP from HERE or Download recovery from this forum. All credits to the developer to make it possible DOWNLOAD IT FROM HERE. TWRP WITH EFS BACKUP AND MORE
YOU DO NOT NEED ROOT
I suggest you use the second TWRP as it supports more partitions than the first one.
Open working adb
TYPE IN
Code:
adb devices
adb reboot bootloader
fastboot boot LenovoA6020_TWRP-3.0.2-r3_7M.img
OR
fastboot boot TWRP-k5-3.0.2-r2_shreps.img
You will be booted into recovery.
Select Read only mode
Go to backup
Backup all partitions by selecting all of them
Swipe to confirm.
Make sure you have about 6GB for a full backup
You can skip user data if you do not want user apps backup
Nothing will be changed unless you enable system modification. So on first boot, simply do not enable system modification and go to backup and then backup all partitions. Keep these safe in case you need them.
Keep it in a safe place
HOW to restore back to your stock using TWRP. HERE
EFS Professional
doesnot work for me. Anyone can check by updating their busybox ? I couldnot on supersu 2.76 without updating busybox

CUSTOM ROMS
PACMAN
CYANOGENMOD 13
SOME HERE ON A RUSSIAN FORUM
STOCK ROMS
SOME HERE ON A RUSSIAN FORUM
Shreps said:
Stock Firmwares:
Firmware collection Thanks to @vache
Firmware collection, 2nd Mirror by @Shreps
TWRP Backups of Stock ROM:
A6020a40 - S027_160519_ROW
A6020l36 - S032_160401_LAS
Click to expand...
Click to collapse
Stock Rom guide to know which is your device by region
[*]American Models
Lenovo K5 Plus dual sim 6020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
[*]European Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
[*]Asia Models
Lenovo K5 Plus 6020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
[*]Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616

Some problems of the future. World war? Mobile mind control
OTA FAIL
ERROR 101 System doesnot allow change of carriers
download lenovo smart assistant
Install it and try to update it using this. If it does not update, find update package in lenovo tool folder
C:\Program Files (x86)\LenovoSmartAssistant\LenovoSmartAssistant\plugins\75fc9be6-29e6-495f-8c0a-93f9e1971133
Extract it and find system.zip and your country ota (both) in the sequence
Country.ota.zip (image taken from QPST)
Country2Default.ota.zip (image taken from QPST)
System.zip (image taken from FullOTA)
Does not flash with no error but system not updates and shows update again
Must flash system using QFIL
I used Indian firmware as I couldnot find for my region and thus I always had the error. Can not switch carriers.
I went to recovery and then 0>OTA> Flashed India OTA
Checked for system updates and this time it worked fully.
You can check which is supported by ####6020# in dialer
THIS IS GOLD. DO NOT MISS IT AT ALL
http://lenovo-forums.ru/forum/624-lenovo-k5-plus/

Credits
@Shreps for TWRP/ Custom roms and all his development efforts @samuro625 for TWRP and Rooting instructions @scritch007 cyanogenmod 13
@ more coming soon
@ anyone i left ? PM me and I will be happy to add your name!
 @dongordo @axal Stock Firmware information
JUST WANT YOUR NAME FOR NO REASON ? PM and I will add it under this heading

Nice thread ?
Envoyé de mon Moto G (4)

Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?

Hnk1 said:
Custom roms
PACMAN
CYANOGENMOD 13
Orignal Sock Roms
Stock Rom guide to know which is your device by region
American Models
Lenovo K5 Plus dual sim 7020l36 MSM8939v2 SD 616
Lenovo K5 Plus single sim 7020l37 MSM8939v2 SD 616
European Models
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo K5 7020a40 MSM8939 SD 415
Asia Models
Lenovo K5 7020a40 MSM8939 SD 415
Lenovo K5 Plus 7020a46 MSM8939v2 SD 616
Lenovo Lemon 3 K32C36 MSM8939v2 SD 616
Lenovo K5 note K52t38 Mediatek MT6755 Helio P10
Latin America ( Brazil, Chili )
Lenovo K5 dual sim A6020l36 MSM8939v2 SD 616
Click to expand...
Click to collapse
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)

Phylum said:
Where on the Qualcomm site can one find the QIFL / QPST? Is it part of the Hexagon SDK?
Click to expand...
Click to collapse
It is a took which was leaked and it is not officially available to you unless you manufacturer devices like samsung, lenovo etc
Download it from the first post. I have attached it in two posts!

Shreps said:
Wrong info. A7020 is K5 Note with MTK SoC.
Envoyé de mon Moto G (4)
Click to expand...
Click to collapse
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg

rafaellancas said:
Just to remember you guys, these methods DON'T WORK on A6020l36. Don't try this on your phone if it's this model, but if you did (like me), here is how to unbrick your phone.
https://www.youtube.com/watch?v=6pF2nT2SsHg
Click to expand...
Click to collapse
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.

Hnk1 said:
I think you are mistaken. I have QFIL method in my guide which is used by the user in the video.
Click to expand...
Click to collapse
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).

rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app

Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???

Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone

rafaellancas said:
Sorry man! Haven't seen it! I thought you were only talking about the TWRP method (which doesn't work on a6020l36).
Click to expand...
Click to collapse
It should work flawlessly. I do not see why! Did you do as instructed ?
JoZ3 said:
Really?
Sent from my Lenovo A6020a46 using XDA-Developers mobile app
Click to expand...
Click to collapse
nguyenlucky said:
Is this software almost the same as XIAOMI MIFLASH (it has EDL flashing mode) ???
Click to expand...
Click to collapse
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
minigreen said:
Lenovo K5 Plus single sim 6020l37 MSM8939v2 SD 616
Click to expand...
Click to collapse
Do you want me to add it to the guide ? Which region is your device from ?
kkn_13 said:
Any hope for Vibe X3 etc? getting it dirt cheap and I need a new phone
Click to expand...
Click to collapse
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.

Hnk1 said:
It should work flawlessly. I do not see why! Did you do as instructed ?
Well, I have not tested this with a XIOAMI device with QFIL. In theory it should work, but I have always preferred MIFLASH as it is designed specifically for Xiaomi devices. Most of snapdragon devices has an emergency download mode.
Do you want me to add it to the guide ? Which region is your device from ?
What do you mean ? QFIL should work on all lenovo devices (snapdragon) provided you have proper stock images which are specific to your device. Google is your friend ? TWRP and development is not currently my aim for any device yet. As i did all my experiments using a K5 plus so I could write in length about it specifically.
Click to expand...
Click to collapse
Thank you for your time man! Twrp does not work with my phone (I mean, I can install it, and root/flash some stuff, but it definatelly does not work for flashing any of the images uploaded here, including the backups or the pac/cyanogenmod roms, they all give the same compatibility erros as the roms were not made for this phone). I followed the instructions, wiped system/data/dalvik, tried to flash, compatibility erros. There is no way of backup too, since it crashes at the ending. I'm starting to think that my phone is not the a6020l36 (even though it says that on a label under my battery, on my phone's setup and also on the box), but some variant made for my country only. And I know that are brazillians that claim to make it work on their phones, but since there's no way to guarantee that we really have the same phone, I don't now what to do. The QFIL stock rom (that I got from another place too, the ones uploaded here don't work either (another reason to think that my a6020l36 is different from the ones people claim to work here)). Thank you again for your time.

A2017g bricked after bootloader relock

Hello everyone,
So I've read that I can re-lock the bootloadder and tried to do it.
First I have flashed b10 and flashed the su so I wont loose TWRP. I entered fastboot with adb and then I typed fasstboot oem lock, I got a message on the pc with ok.
Since then I cannot boot to the phone.
The phone shows the zte logo for 0.5 seconds but not booting and with constant red led.
Tried power + vol up, power + vol down, all three buttons, vol up + vol down and then connect to pc - nothing at all. The phone wont get past this 0.5 second zte logo.
In all connections I have listed above the phone shows in device manager as QUSB_BULK. At first it was with yellow acclamation mark and then I installed the zadig driver. Now it is connected "normally".
What can I do?
Please refer me to the right tutorial or guide me.
Thanks

I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)

dnlilas said:
I heard that it is not recommended to relock (although possible) unless strict necessity (RMA, sale...) due to risks.
This said, I suggest two methods:
Method A)
Revert back to bootloader unlocked so you will be back as before.
Your current situation with recognized QUSB_BULK driver is good.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot bootloader" command: anything changed on screen or Device manager sound?
Then try "fastboot devices" command: if you get answer, then OK you are in fastboot mode.
And in fastboot mode you can now issue the command "fastboot oem unlock" to unload the bootloader again.
Then the phone should be back operational again as before.
Method B)
Try to get to recovery (either stock or TWRP preferably). When the phone can boot to recovery
(TWRP if possible), you are saved since with TWRP you can reflash everything.
Your current situation with recognized QUSB_BULK driver is good for (re)flashing recovery in EDL mode.
Always have Device Manager running to monitor.
- try "adb devices" command. If device recognized: good.
- try "adb reboot recovery": does it boot to recovery?
If not, then my guess is that since the bootloader is locked, unsigned TWRP (as the one you used since normally nobody should use tenfar's signed
TWRP for daily operation) is not accepted.
- so you need to reflash tenfar's signed TWRP mentioned in this guide:
https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379
using EDL mode ("adb reboot edl", then "axon7tool -w recovery" etc..., with file recovery.bin = tenfar recovery).
tenfar's signed recovery is accepted even if the bootloader is locked.
- after that you should be able to boot TWRP (tenfar), by using 'adb reboot recovery', or with Power + Volume-Up: your phone is now under your control!
(reunlock, upgrade TWRP, flash ROM, root...)
Click to expand...
Click to collapse
I'll try to do it but yesterday tried to go to edl or recovery in cmd no device found. Tried to flash recovery but it hangs on "waiting for device" so I don't thing I can get to these edl, recovery, fastboot status.

@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169

dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
I'll try all these guides and update with results

dnlilas said:
@ItsNewDroid
Bootloader relock could also be done with Axon 7 Toolkit https://forum.xda-developers.com/axon-7/development/tool-axon7toolkit-t3573108
Other topic:
https://forum.xda-developers.com/axon-7/how-to/guide-lock-bootloader-axon-7-a2017g-b9-t3589169
Click to expand...
Click to collapse
So for sure I'm doing something wrong. Can you please guide me with this tool?
Ironically you helped me unlock the bootloader and I need your assistance relocking it.
Edit: I have the 3 files backed up from the unlocking procedure they should help no?
The phone is not recognized in any adb status edl or fastboot

I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?

QuantumFluxx said:
I don't think you can have a modified recovery partition and a locked bootloader. As I understood it, fastboot oem lock will fail or result in brick if you try to flash anything other than authorized files. Can anyone confirm that they have successfully locked their bootloader and retained TWRP?
Click to expand...
Click to collapse
I don't want to keep twrp or anything. I want to sell the phone so all I want.t is to go back to locked stock phone.
I cannot boot to recovery or fastboot or edl. If I could I would use miflash and flash b10 and be done with it

I think that the initial problem arose when you flashed SU and tried to relock the bootloader with TWRP installed
What does Windows Device Manager show when you connect the phone to your PC?
Update: sorry bud. I totally missed that bit in your OP. DOH! Will update.
Update:
Have you seen this?
https://forum.xda-developers.com/axon-7/help/a2017g-totally-bricked-t3537990
https://forum.xda-developers.com/showpost.php?p=70948893&postcount=28
Sorry that I can't be of more help...

I think what went wrong with my device is that after flashing stock b10 I flashed su so I won't lose twrp. Now when I tried to lock the boot loader made a conflict as I could not have locked bootloader and this version of twrp (for unlocked device). Now I just need to find a way to flash stock recovery (I have a backup from the unlocking procedure) without edl or fastboot as I cannot seem to find a way to enter these states (cause I have no recovery) I'm hoping it makes sense (pretty early in the morning)

So no one can help?
I can't believe the phone is beyond repair

@ItsNewDroid
Sorry I do not have solution, just some idea.
It "seems" that you cannot boot to either system, recovery, bootloader, EDL! adb/fastboot commands are not recognized.
There is still hope since your phone is still recognized somehow as QUSB_BULK (not unknown device) with Zadig driver under USB device.
So you can try to uninstall Zadig WinUSB driver and use Qualcomm bulk drivers so that the phone appears under COM port as Qualcomm HS-USB QDLoader 9008.
If you get 9008 then you are in EDL mode, and MiFlash could be used to flash.
Qualcomm bulk drivers, MiFlash... are available from Download center:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547
The problem is to find available "EDL packages" recognized by MiFlash to flash.
These packages could be stock recovery, signed TWRP, or full ROM (any version, MM, or Nougat).
This would allow booting to either recovery or system.
The problem is that I did not see many such packages for A2017G, but only for A2017U.
You may have to ask other members how to build such "EDL packages" (for ROM, sometimes it is called "fastboot ROM").

@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again

@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Edit 2: So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?

ItsNewDroid said:
@dnlilas
First, let me thank you for your help. It is much appreciated.
I've uninstalled the zadig driver and installed Qualcomm driver. Now the phone shows in device manager under ports - (DFU) (COM 4) not as Qualcomm HS-USB QDLoader 9008.
Do you know the steps to enter Qualcomm HS-USB QDLoader 9008?
Thanks again
Edit:
Miflash is not recognized in any key combination.
Click to expand...
Click to collapse
Oh no, you unfortunately got the dreaded DFU (device firmware mode).
Looks like it a serious brick. Some topics and articles:
https://forum.xda-developers.com/axon-7/help/2017g-dfu-mode-investigation-t3511191
https://community.zteusa.com/thread/14699
https://www.reddit.com/r/Axon7/comments/5oqgfj/a2017g_bricked_cannot_get_past_dfu_mode/
https://www.youtube.com/watch?v=nqF3nr3y-Eg

@dnlilas
Man there are changes!
So somehow I booted to fastboot. My boot loader is LOCKED!! What to do now?

Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Edit: the screen capture you took is the bootloader menu (equivalent to come into with "adb reboot bootloader").
When in bootloader, I believe you can use Volume-Up and Volume-Down to navigate (to go to recovery, system, bootloader or other mode). Validate with Power button. It is important to remember how to get to this bootloader menu.

dnlilas said:
Excellent! Try to remember how you get to this menu.
Does "adb devices" command recognized? Status "xxx recovery"?
Of does "fastboot devices" recognized? If yes => you are in fastboot mode. Then you can try to unlock (reverse lock operation) with:
"fastboot oem unlock"
It should ask on phone to erase data (like factory reset). Then say yes.
Click to expand...
Click to collapse
I held the 3 buttons not connected to power or pc. As soon as I felt the vibration before zte logo I let go of the vol up button and it booted to fastboot.
I dont want to unlock the bootloader I want to sell the phone ( this is the reason I came to this situation) I tried to boot to recovery from this menu but it could not.
My guess is that I have twrp recovery and as the bootloader is locked it can not boot.
I need either a twrp for LOCKED bootloader or a stock recovery.
I'm searching the forum but could not find.
You are a wizard! Every time you reply I have good news :good::laugh:

@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!

dnlilas said:
@ItsNewDroid
Download tenfar's signed TWRP here:
TWRP 3.0.2.2 (tenfar) : https://www.androidfilehost.com/?fid=529152257862720446 (download center https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547)
Important: check md5 6eeb1a9d02470a840bc68019184d9a72
A2017G-TWRPrecovery3.0.2.2tenfar.img
to insure correct download.
Note: tenfar's signed TWRP can be flashed even with locked bootloader, using fastboot in EDL mode (bootloader mode).
Important: I believe you need to switch back to Zadig driver first so that axon7tool used below could work.
The most important thing is that "fastboot devices" command must be recognized while you are in EDL (bootloader) mode.
In the directory where resides axon7tool (axon7tool-1.5-win64.exe https://forum.xda-developers.com/axon-7/how-to/guide-install-twrp-unlock-bl-flash-t3517379),
make a copy of it with the name recovery.bin:
copy A2017G-TWRPrecovery3.0.2.2tenfar.img recovery.bin
Put your phone in bootloader mode (EDL mode) as before, then verify that "fastboot devices" command is answered correctly with your device id.
If OK, then issue the command:
axon7tool-1.5-win64.exe -w recovery
If everything is OK, this will write tenfar's TWRP signed recovery and phone reboots (I believe so).
Immediately Use "Power and Volume-Up" until ZTE logo: it should then boot in recovery (TWRP, tenfar version 3.0.2-2).
Good luck to you!
Click to expand...
Click to collapse
So this is the new situation: adb devices phone is not recognized. Fastboot devices device IS recognized. Issuing axon7tool - w recovery I get device not connected failed to connect. Any idea?

your device is corrupted and cannot be trusted and may not work properly

Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command

amus76 said:
Hi all, I ended up with this:
"your device is corrupted and cannot be trusted and may not work properly"
I can access Fastboot mode but can't flash any TWRP
Any help?
I tried to install LOS with Universal Bootstack...and Axon 7 Tool open a window just for one second so I can't access the command
Click to expand...
Click to collapse
All right, do this:
-Put the phone in Fastboot
-Open command prompt
-Run "fastboot erase userdata"
If it doesn't work, do this:
-Set up a TWRP on your fastboot folder (rename it to "recovery.img" [BE SURE THAT YOUR PC SHOWS FILE NAME EXTENSIONS] and put it on the folder where fastboot is located)
-Open command prompt in the folder where Fastboot is located
-Run this command:
fastboot boot recovery.img
Your phone should enter TWRP. It's not installed, it just boots it once.
Then try to format data from TWRP. Right after that, use "adb push recovery.img /sdcard" to push the recovery img to your internal storage. Then go (on your twrp) to "Install" - hit "Install image", then select the recovery.img, and select "recovery" and swipe to confirm.
After it is done, install LOS again. If it is 15.1 or 16 you have to have a Vendor compatible TWRP, such as Ordenkrieger's TWRP (From LOS16 thread). Follow the instructions precisely

As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?

amus76 said:
As soon as TWRP is flashed, i get the warning screen with : "your device is corrupted and cannot be trusted and may not work properly"
And no recovery then after reboot
No FTM mode and I can't enter EDL
And I have to say my device is recgnised as DFU by the PC so maybe trying the EDL cable?
Click to expand...
Click to collapse
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done

If you still have access the fastboot
Enter, reboot dm-verity enforcing
Check here
https://forum.xda-developers.com/axon-7/development/unofficial-lineageos-15-1-zte-axon-7-t3800214

Choose an username... said:
yes, an edl cable might work. Otherwise I think you can get some fastboot images and attempt to install them to the right locations
Did you do "fastboot boot recovery.img"? It shouldn't reboot the phone. TWRP should appear right after the transfer is done
Click to expand...
Click to collapse
I did the fastboot boot recovery.img the phone reboot, i get the warning screen for unlocked bootloader and straight after "your device is corrupted and cannot be trusted and may not work properly" with the same style as the bootloader warninr screen.
So without a recovery I can't flash fastboot images

For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.

Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?

Syberclone said:
Did you get access to Edl mode, via button combo or through adb?
If not can you get to the FTM screen?
I know you couldn't access these earlier, has that changed?
Also what apps do you have?
Edl tool?
Axon 7 tool kit (you did mention this)
Miflash?
Qualcomm drivers and Zadig drivers?
Click to expand...
Click to collapse
I didn't get access to EDL mode even through ADB, nor FTM screen. So MiFlash is useless
With Axon 7 tool, I tried to flash TWRP with no success, my phone was on DFU
Then I managed to dm-verity encrypted through ADB but the phone was not rebooting on recovery, still fastboot but the phone was not recognize by the PC
I have Qualcomm Drivers installed
Right now with Lineage, I can't acces FTM screen
I just pushed the button twice when I was with the red warninr screen and get access to TWRP (or Lineage boot screen)

Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted

Syberclone said:
Try installing the Zadig drivers and the bulk USB drivers for the axon to help detect the correct device.
Then see if the Axon tool kit will work properly.
DFU mode shows for a number of reasons.
In your windows device manager it needs to show
"Qualcomm HS-USB QDLoader 9008" if all drivers are setup properly.
When I soft bricked mine I was trying to install Los 15.1
I had the corrupt device message you are getting.
I used all 3 apps to eventually get mine running.
I made sure all drivers were installed and up to date, I switched between the Axon tool kit, edl tool and Miflash to get my laptop to recognise.
I ran the Axon tool kit to setup adb (a few attempts before it worked)
I then ran Edl tool to get some form of Edl
Then ran Miflash (latest version) I had to try this several times too (constant error messages) it finally started the flash process but would fail (I was using the turkdev edl)
I swapped it for the B12 Edl on Raystefs page and it worked, I then had to reflash with the correct modem though.
Anyway I truly hope you get it sorted
Click to expand...
Click to collapse
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time

amus76 said:
Thanks a lot, I have it sorted!
But what strange is a lot of people is facing this problem recently in a short time
Click to expand...
Click to collapse
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.

Syberclone said:
Can I ask how you got it fixed? I would be handy to know for others that end up in this position.
Click to expand...
Click to collapse
Just with "dm-verity enforcing" with ADB
Then: press button power when on the red warning, a pinguin will appear and again press the power button, it will reboot on TWRP or Lineage
My fasbtoot was inefficient a part for the dm-verity enforcing, no FTM also

amus76 said:
For those in my case:
When you get the warning screen with the red message, just push once the button power, a Linux logo will appear, and another push on the button will boot you in TWRP
I didn't manage to get the command to work : adb reboot "dm-verity enforcing", I tried Terminal in TWRP but with no luck.
Click to expand...
Click to collapse
I know this is an old reply, but I arrive from a google search. Sir, thanks a lot for this reply. I was stuck in your same situation and pressing the power button with the linux icon allowed me to go to TWRP. THANKS!

I get the pinguin, but if i press Power again, nothing happened. I have to wait for a while it reboots to System. I tried to hold Power while it is rebooting, but it always reboots to System. No chance to enter twrp...

Need some help after messing up my Lineage OS installation on A2017U

My phone has no OS. Factory reset is unavailable to my knowledge (attempted volume up and power).
I can go into fastboot and TWRP, but I can't seem to install the stock OS nor Lineage OS. In fastbootmode, I see the following
Product name - AILSA_II
Variant - MTP eMMC
Bootloader version -
Baseband Version -
Serial Number 9e28c2da
Secure Boot - enabled
Device State - unlocked
Click to expand...
Click to collapse
I cannot use ADB commands. My phone isn't listed under ADB devices. EDL does not work. However in Fastboot mode, MiFlash recognizes a device 9e28c2da. Whenever I try to flash a full EDL however, miflash brings up errors saying it cannot find script and it cannot find file.
When attempting to install in TWRP, I get the respective errors "Invalid zip file format!" for "A2017U_B19-NOUGAT_FULL-EDL.zip" when I try to install the stock. When I try to install Lineage, I get "E3004L This package is for device: ailsa_ii,axon7; this device is ."
I am able to successful install A7LOSv1_UniversalBootStack.zip as well as the UniversalBootstack by DrakenFX. I then install OreoModem.zip after that, but the phone won't let me install any OS afterwards.
Am I trying to install the wrong arrangement of files? What can I do to get an OS back on my phone?

Firstly it sounds like the drivers need an update.
Try updating the USB drivers and try Zadig drivers as well.
Your PC/laptop should see your phone as ...
"Qualcomm HS-USB QDLoader 9008"
In the device manager on Windows. If you are using Miflash it should see it as Com 4 or similar.
Make sure you have the correct Edl package for your phone eg: A2017G, A2017U or A2017.
Extract the Edl package using WinZip or Winrar and take note of the folder name and location.
Boot your phone into Edl mode, via button, adb command or using the Edl tool by @djkuz
Open Miflash tap refresh, if it sees com4 or similar you are good to go.
Tap the browse button and pick the Edl package location on your PC/laptop and then tap flash.
The flash will take a few minutes and when done you will get a green flash success.
Unplug your phone and press and hold the power button till it boots.
Hope this helps
If you get stuck,
I have an Edl help page here >
https://forum.xda-developers.com/axon-7/help/bad-flash-help-page-axon-7-t3839700
There are many others on XDA too

Phone doesn't get recognised in Download mode (bootloader)

Hi Guys
So my current goal is to root my galaxy S10+ (SM-G975F) running exynos with android 11. I've seen many methods that are supposed to work for android 11, some more complicated than the others.
The method I chose to stick with, is to enter bootloader through adb using cmd on my computer and to flash twrp that way. (Bootloader is unlocked already)
After that I should be able to install magisk via twrp to complete the root access.
My inital thought was to flash twrp via odin, because odin did recognize my phone after entering bootloader. The problem was that after flashing twrp with odin and performing vol down + power then bixby + vol up + power which normally makes you enter twrp, I got stuck in a bootloop. After that I had to flash the stock ROM via Odin to "repair" my phone.
From what I've read this is due to the vbmeta protection mechanism, that you need to deactivate to avoid bootlooping.
So I heard that you can extract the boot.img file from the official firmware and edit the file with HxD Binary editor to replace a bitcode's value with a series of 0's. Unfortunately I couldn't find that specific code in boot.img.
So the remaining option was to manually flash vbmeta.img and to disable verity verification via cmd.
This is where the big problem lies, my PC does not recognize the device as soon as I enter Download mode. I tried every possible fix I could find online, they all revolve around installing certain drivers and applying them to the device in the device manager. Apparently the device needs to appear in the device manager under "other devices" with a yellow triangle then you can manually select a driver to install. Unfortunately as soon as I enter Download mode (Via cmd command or manually) my device totally disappears from the pc. Only Odin still recognises it somehow.
I installed official android device drivers, specific drivers for bootloader etc.
Every online guide about solving this problem needs you to locate the device and to apply certain drivers to it, but nothing appears for me.
I hope somebody can help me

Format data?

What your twrp version ? your twrp version must be version support 11.

You cant flash Magisk via TWRP. It doesn't work, Install the magisk App

Wrong place to ask this stuff