Database Users

Installing twrp with locked bootloader

I found a way to install twrp on my mi max with locked bootloader using EDL mode.
NB! This will reformat the phone so you should take a backup if you got something you want to keep on the phone.
NB! DO THIS ON YOUR OWN RISK!!!
To get into EDL mode I followed thi guide:
http://xiaomitips.com/guide/how-to-put-mi-max-into-edl-mode/
I turned off the phone and pushed vol+and- and connected the usb to the PC.
Then I installed the qualcom drivers I found here:
http://xiaomitips.com/download/qualcomm-qdloader-usb-drivers/
In device manger update the drivers that has name QHSUSB_BULK when the phone is in EDL-mode with the quallcomm-drivers
The driver should be installed and you can see added in Ports as Qualcomm HS-USB
I downloaded a fastbootimage
http://bigota.d.miui.com/6.6.23/hydrogen_images_6.6.23_20160523.0000.23_6.0_cn_5ab5ac0aba.tgz
I also downladed twrp:
http://forum.xda-developers.com/mi-max/development/recovery-twrp-3-0-2-0-touch-recovery-t3388073
I used 7zip to unpack fastbootimage.
Inside I found the folder with images and a recovery.img file. I renamed twrp file to recovery.img and replaced the one in images.
I then used miflasher and flashed the fastbootimage using clean option.
The flasher I used: can be found here:
http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
On flasher program the device should be recognized as COMXX when the Qualcomm drivers.
If the device id is a hexnumber and not COM10 the flashing in EDL mode will not work.
After flashing I diconnected the phone from pc and rebooted into recovery "power and vol+"
Now I had TWRP and could wipe and install ROMS etc.
I installed the ROM I found here
https://xiaomi.eu/community/threads/6-6-23.32335/
This was a much better ROM than the china-rom

Nice... Did your bootloader get unlocked after you flashed the eu global ROM?

nijel8 said:
Nice... Did your bootloader get unlocked after you flashed the eu global ROM?
Click to expand...
Click to collapse
Its still locked, but as you got twrp it really doesn't matter

I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!

Survivor1990 said:
I've got a little problem. At the moment I'm in a bootloop. No access to ROM and bootloader is still locked.
Could you describe how exactly you flashed the ROM? After you replaced the recovery, did you pack in again? And whats the "clean option"? By MiSuite or by MiFlasher?
Because in my case MiFlasher does not work saying "critical partition flashing is not allowed"...bootloader locked.
Do you think I can install Cyanogenmod for Max by your method?
Thank you very much in advance!!
Click to expand...
Click to collapse
You use the Miflasher when telephone is in EDL-mode. I used http://xiaomitips.com/download/new-miflash-beta-one-click-install-miui-fastboot-rom/
I didn't pack the ROM again. I had to browse into the catalog with the flasher which has files like flash.all
I see no reason why a Cyanogenmod for max shouldn't work as long at you flash it with twrp

Okay I did not know about this third Tool. I will try it when I am at home in the evening. Thank you very much!!

My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working

tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)

same for me!

g_BonE said:
tried this, did not work for me ;( - Max Helium 3gb/64gb
After booting to recovery from the off-button menu i just got that regular old recovery screen (a phone with a plug connecting)
Click to expand...
Click to collapse
Did the flashing give you the developer version of miui?
I don't know if it has something to say. I had the oem unlock option set in developer section on settings.
Are you sure the phone stayed in EDL mode and not in Fastboot? A black screen with a little mi icon
Or that the recovery.img was really swapped with the twrp?
It worked on 2 phones I tried.

Survivor1990 said:
My flashing starts and stops after 1 second saying success. But it did not change anything. My phone is detected and I've done everything you said. I don't get it working
Click to expand...
Click to collapse
Doesn't look like it flash with EDL and qualcom drivers. Does it says device is a com port in the flasher utility?
I found this that might help. I had enabled usb debugging:
Be sure to Enable USB Debugging:-
Go to About phone > tap MIUI version at least 7 times to activate the Developer options. Go to Additional settings > Developer options > USB debugging > Enable it.
Before proceeding: Disable Driver Signature Enforcement in Windows 7/8/10 64-Bit
USB Data cable from your set.
Battery is charged at least 50%.

Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.

Survivor1990 said:
Could you send me the link to the correct drivers? I use Universal ADB Drivers and in ADB I can see my device as "sideload ...."
But in the XiamiFlash Tool I can not see it in EDL, only in Fastbootmode.
_____
in fastboot mode it's recognized and starts flashing, and it says success. But the ROM is not changed.
Do you really mean
-launch XiaoMiFlash (Beta)
-Then connect Max in EDL Mode (Phone with usb plug on display)
-then it should be recognized?? (because in my case it's not...)
_______
I don't have access to my ROM after an update...it's just ridiculous.
Click to expand...
Click to collapse
You need the qualcomm drivers
https://goo.gl/CPa5jd
To install the drivers follow this guide when connected in edl-mode:
http://en.miui.com/thread-235865-1-1.html
Follow point 5 and in point 6 use the drivers you have downloaded

There is no need to flash the entire partition set to install TWRP. It is enough to flash a single "recovery" partition using edited rawprogram0.xml, removing all partitions except "recovery" and either specifying TWRP image file name in "filename=" or renaming TWRP image file to "recovery.img".
patch0.xml must be edited too to remove all "<patch>" tags.
Additionally, flashing a modified "boot" image may be required.

I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!

Survivor1990 said:
I managed to flash it with the new XiaomiFlasher Beta. My phone is running fine on CM 13 now! Thank you!
Click to expand...
Click to collapse
Thanks for det update, I added an URL to the flasher on the first post

After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB

alexecus said:
After I flash using EDL, for some reason, free space reported is only 8 GB, instead of 24 GB
Click to expand...
Click to collapse
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk

iJohnny said:
I had the same problem with 64gb version.
In twrp go to wipe
Click option to delete data partition
It will tell you all data will be deleted and encryption disabled.
After data partition gets deleted twrp will report proper internal space, and ROM will also report proper internal space.
Be sure to backup everything before.
Sent from my MI MAX using Tapatalk
Click to expand...
Click to collapse
Thanks, it worked. I thought the partitioning got corrupted after I flashed using EDL. Glad TWRP was able to provide a quick fix

I got this working on my Helium 64gb Mi Max.
Please note that the instructions above is for the 32gb Hydrogen Mi Max. What I did differently is to get the recovery.img out of a Helium image.

[Help] I bricked my Axon. Need help.

So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Edit: I solved my issue by downloader the stock B08 system on my S5 and then i placed it in the external sd. Then i put the SD back into the Axon and installed the system. After i had installed the system and booted into the OS i could enter adb with my device being recognized and after that i flashed twrp by using ADB.
I have a new problem though and that is that i can't install the 3.1.0.0. twrp. it only boots into black screen when i enter recovery. I can use the 3.0.4.0. version though.

You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?

senny22 said:
So i've gone through every thread here without success. I have a unlocked bootloader but no OS nor custom recovery and i cant get into fastboot mode to install twrp. When i use ADB it wont find my device unless i go into Stock recovery -> update through ADB and even then it only recognized my device as sideload. What can i do? When i tried to use the MiFlash tool i cant seem to get the correct qualcomm drivers installed. what can i do?
Click to expand...
Click to collapse
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?

nonamesl said:
You can't enter fastboot mode on your phone. Correct?
I also assume that you installed a ROM from recovery and that's what caused the brick, right?
What happens when you try to enter recovery?
Click to expand...
Click to collapse
Correct. It simply reboots.
Yup, i tried installing the B29 stock system on my G model and so i suppose i had the wrong bootstack becasue this is where my problems started.
I get to the stock android recovery.

raystef66 said:
Go into My Computer, manage, devices and try to uninstall all drivers that are possibly related to your device.
Unplug your phone and let the drivers reinstall by itself.
Go into ADB and see if ADB Devices works.
If possible go into ADB reboot edl and try to reflash custom recovery : "axon7tool -w recovery"
When recounting unplug your phone and see if you can reboot, shutdown and enter into TWRP.
ps : i hope you have a backup ?
Click to expand...
Click to collapse
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.

senny22 said:
It still wont recognize my device. Which driver am i supposed to have in the Device manager? Do you think i can use my old S5 to transfer a Stock system to the sd card and then update my phone manually through the stock recovery and then when i have an OS installed maybe i can connect to ADB. I read somewhere that ADB commands only works in recovery and in the OS.
I have a twrp backup of my system on my SD card so no worries there.
Click to expand...
Click to collapse
You should see your phone as QUSB_BULK. Installed the ZADIG drivers ? That may cure the problem.
After that, imo, it is important you can reboot edl and flash TWRP recovery again AND when it recounts, you pull usb.
Normally you will have replaced recovery , reboot ok and you can enter TWRP and fastboot also.
ps : sometimes it is also advisable to go to ADB RECOVERY directly and do the processes.
ps2 : when TWRP backup, you can always put it on SD via other phone and in TWRP restore. Normaly you're good to go then...

Try the Marshall London Bootloader Interface driver maybe?

nonamesl said:
Try the Marshall London Bootloader Interface driver maybe?
Click to expand...
Click to collapse
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?

senny22 said:
Ok, should i be able to find my device with "adb devices" if i uninstall all the other drivers and install this driver?
Click to expand...
Click to collapse
Installing the driver and using it for the phone (device manager -> change driver manually (or something of the sort)) worked for me, but it could differ. Let me know. You don't have to uninstall other drivers just use that specific one for your phone by switching the driver manually via device manager.

A2017g can't reboot to bootloader

So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?

ItsNewDroid said:
So I've just received my axon 7 a2017g. It came with b06 installed. I'm trying to unlock boot loader without success. Can't get to edl mode. In cmd the device is unauthorized though I've enabled oem unlock and sub debugging. Installed the drivers from sub debugging. I have Windows 10 64 bit. I get to recovery with volume up plus power I select to reboot to bootloader with no success. It only restarts. Tried also with b10 and b08.
Any suggestions ?
Click to expand...
Click to collapse
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though

Choose an username... said:
Why bootloader? Isn't there a way to do it via EDL (from system, do adb reboot edl)? On Controllerboy's guide maybe? Maybe you think that the device doesn't get to EDL because it seems like it's totally powered off. Just try again.
As of fastboot, it was removed on Nougat, not sure if they removed it before though
Click to expand...
Click to collapse
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts

ItsNewDroid said:
Did not understand you. Where in system to do and reboot?
The phone is turned onand connected the the pc and I've enabled oem unlock and usb debugging.
The device won't boot to edl after I enter adb reboot edl. So I tried in recovery screen to get to the bootloader menu but pressing reboot loader it just restarts
Click to expand...
Click to collapse
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)

Choose an username... said:
You have to have adb and fastboot installed. Run "adb reboot edl" from your computer while the phone is on, it should ask you if you want ADB to be allowed to do stuff, then poof. Go to the Device manager and check that there's a Qualcomm HS-USB QDLoader 9008 under Ports (COM&LPT)
Click to expand...
Click to collapse
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly

ItsNewDroid said:
Can you direct me where to get the adb and fastboot? I've rooted a lot of phones but this one seems unfriendly
Click to expand...
Click to collapse
You rooted a lot of phones and don't have ADB lol
Search for 15 seconds adb installer

I already have it installed. It says unauthorized when I run adb devices

ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Unplug the phone, turn it off. Hold only the 2 volume buttons (DON'T TOUCH POWER) and insert the USB-C (plugged to the PC in the other end ofc) while holding the two volume buttons. then check device manager
This should get you to EDL
---------- Post added at 12:44 AM ---------- Previous post was at 12:40 AM ----------
ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Okay after you do that last thing you should get to EDL. Download Zadig, uninstall the Qualcomm QDLoader drivers and tick Delete driver software too. Then go to Zadig and install the driver. After that hold the 3 buttons (pwr, vol) until the led flashes or your PC makes a sound, wait 5 seconds, and you'll be able to run axon7tool.exe -r gpt boot recovery

In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found

ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
That's extremely weird...
Well I guess there's no harm trying to downgrade to marshmallow B03. Download that ancient ROM from raysteff's download center. I did the whole process there. Maybe you'll get fastboot too
---------- Post added at 01:13 AM ---------- Previous post was at 01:10 AM ----------
ItsNewDroid said:
In zadig's post he says they G models should edl only by the command. But I did as you said with the volume buttons. I run axon7tool in command But it says no device found
Click to expand...
Click to collapse
Thinking about it it's not that weird, I think you're not getting the Zadig part. Did you install the driver through Zadig? How's the device reported aa when on EDL? If you installed the driver properly it should be listed as QUSB_BULK under USB something

Sure I'm not doing something right.
First I did not have Qualcomm drivers installed
I'm in edl with volume buttons and sub. open zadig and install wcid.
From here I did not get it. Hold all buttons vol÷power?

ItsNewDroid said:
I already have it installed. It says unauthorized when I run adb devices
Click to expand...
Click to collapse
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"

dnlilas said:
Like this ?
"adb devices" command:
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx unauthorized
When enabling USB debugging then with USB cable connected, there is a popup in your phone, asking to authorize
your phone (with digital signature etc..). You need then to authorize it. Afterwards, your phone will be recognized
with 'adb devices" output as :
List of devices attached
* daemon not running. starting it now at tcp:5037 *
* daemon started successfully *
xxxxx device
xxxxx is your device id. You must have status "device" and not "unauthorized"
Click to expand...
Click to collapse
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one

ItsNewDroid said:
Yes I know that a message should popup but it doesn't. What can I do?
I have oconnection options like charging, mpt etc.
Should I choose something perticular?
And why it doesn't reboot to bootloader from recovery menu?
I really think something is wrong with the device.
Where can I find a2017g b03? In every post the link to zte's website that only have b11 and nougat.
Sorry for all the questions as I said this device gives me a hard time.
I've had opo op3 lg g5 le max 2. Non of theme gave me hard time like this one
Click to expand...
Click to collapse
Please check periodically USB debugging option. I encountered similar problem as your, and before the popup that confirms USB debugging
for the phone, the option is set back to disabled. So maybe you have to check again this option, unplug and replug the phone, choose option MTP,
this should help to have the confirmation popup. Anyhow you must have to reach status "device" which means your phone is able to connect using ADB.
For A2017G B03, it is not necessary, B11 is OK for unlock, TWRP or root using the current guide.
However if you really need it (A2017G B03, B06, B09):
https://forum.xda-developers.com/showpost.php?p=68873485&postcount=3

I suspect that my laptop is causing me trouble as also my g5 will not prompt me with authorization.
I'm gonna use a different laptop without any drivers installed. Can someone tell me all the drivers needed for the a2017g in chronological order so there won't be any conflicts?
In other tutorials they don't mention Qualcomm's driver but in othrrs they are needed.
This phone makes me so frustrated.
So please a step by step from new how to connect to adb on a total new pc. From there I hope I'll manage.
Thanks to all who replied. It's much appreciated.

Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!

the_cyberspace said:
Here the same problem with an A2017G model. Phone worked with the latest LineageOS, was rooted and got an unlocked bootloader, and with flashing to the the new B04 update phones ends up in a loop.
I can get into the stock recovery and when i choose "reboot system now" i get a screen wich tells you to lock your bootloader.
In recovery a can also choose "apply update from adb" or "apply update from sd card". With the first option i can flash a rom but at 25-30% adb ends up with an error.
With the second option i get a message "Sorry, can`t sdcard upgrade", and tryed several sd cards.
Phone will NOT boot into Android so i can`t change USB debgugging or something.
I can get in EDL mode and after "axon7tool -r gpt boot recovery" in adb the phone reboots with no errors and gets in a loop again. Grrrrr..... Very frustrating with a non working phone!
Click to expand...
Click to collapse
The command "axon7tool -r gpt boot recovery" only backups your boot and recovery (-r = read, so of course only files *-backup.bin are created inside your PC directory, no change to the phone).
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?

dnlilas said:
Since you have stock recovery, did you apply the full ROM A2017G-N-B04 (australian) from here:
https://forum.xda-developers.com/axon-7/how-to/download-center-factory-images-ota-t3606547 ?
Click to expand...
Click to collapse
Yes but get an error in adb: cannot read 'rom.zip'

the_cyberspace said:
Yes but get an error in adb: cannot read 'rom.zip'
Click to expand...
Click to collapse
Did you try installing the ROM zip from inside the stock recovery?

dnlilas said:
Did you try installing the ROM zip from inside the stock recovery?
Click to expand...
Click to collapse
I can choose "apply update from ADB" and "apply update from SD card". When i choose the option from SD card i get a error: "sorry, can`t sdcard upgrade" and when i`m flash the rom in adb: "cannot read 'rom.zip' ".

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

[HELP] LG G6(H870) block to boot

Hello,
I tried to install a new ROM on my phone (for the first time).
I unlock it with (unlock.bin) and checked with adb command if it is unlocked.
I installed TWRP. I boot myphone in factory mode, and TWRP started. But I failed install to ROM...
So now I have a problem :
If I try to access to TWRP : I boot in factory mode, select "yes" twice, and my phone boot a second time again and lock on the screen "LG".
I told me I can reinstall it with adb, but adb can't see phone connected on my computer (because no os)
Do you have a solution ?

https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924

Android# said:
https://forum.xda-developers.com/lg-g6/how-to/lg-g6-unbrick-method-t3935924
Click to expand...
Click to collapse
Thank you for the link. I don't understand step 2 :
Step 2) Install QDLoader Driver (Select the driver for your system, 32 or 64-bit)
Use The new Signed driver.
in the archive(download in google drive) I don't found the exe, so I download and install QDLoader driver from internet.
But what does that mean "use the new signed driver" ? edit: how I use (NEW)(Signed)9008 Drivers.rar ?
edit: In my driver management I didn't see Qualcom HS-USB

GameKoyColor said:
Thank you for the link. I don't understand step 2 :
Step 2) Install QDLoader Driver (Select the driver for your system, 32 or 64-bit)
Use The new Signed driver.
in the archive(download in google drive) I don't found the exe, so I download and install QDLoader driver from internet.
But what does that mean "use the new signed driver" ? edit: how I use (NEW)(Signed)9008 Drivers.rar ?
edit: In my driver management I didn't see Qualcom HS-USB
Click to expand...
Click to collapse
Sorry for late reply. If I remember correctly, phone has to be connected to the computer in EDL mode for you to see the Qualcom HS-USB. Also, you just unzip the .rar file and driver is there. Sorry, I did this long time ago and I think once I connected the phone in EDL mode with the PC, it showed up in device manager and I installed the driver to it.