Database Users

MiFlash - 'cannot receive hello packet' in EDL Mode. No Fasboot

Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards

nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
disassemble again, force EDL and flash the corresponding rom

bornlivedie said:
disassemble again, force EDL and flash the corresponding rom
Click to expand...
Click to collapse
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash
Click to expand...
Click to collapse
In Windows 10, does the device manager detect the phone as Qualcomm 9008 inside the ports section? It is the way Windows detects a phone in EDL mode. You may have also some driver issue in Windows. If it is detected as BULK then you only need to install the latest Qualcomm drivers. You can find the details in this guide.

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
I had the no hello package message in Win10 with a A2017U, for me the solution was to setup to run MiFlash in Administrator mode (look for the check box under the compatibility tab), and then replugin the USB cable and restart EDL fresh.
There seem to be all kinds of cases of this occurring for various phones on the internet with various solutions, but this one worked for me this time.
It seems to be a YMMV thing.
BTW if you have an unlocked bootloader flashing the Recovery with the suitable version of Nfound's TWRP Exclusive allows a choice of rebooting into EDL(9800).
This makes getting back into EDL relatively convenient.

nukem007 said:
Hi all,
what happens until here?
A week ago i have bricked my Axon 7 (2017G). Complete dead, only red LED flashing. Search the Forum and found the instructions to disassemble the phone, shorten the Service Point and set the device into edl mode. Great, Works. Flashing the full EDL Rom via MiFlash and phone boots into Android. But then i was realizing that i have flashed the wrong linked Rom. ZTE_A2017V2.0.0B13. At this time i was not Aware that i Need 2017G Rom. Phone works, but wrong Rom.
When i tried to flash anew rom i get from miflash the message 'cannot receive hello packet. try to reset...'
I'm using Win10, several USB Ports and several MiFlash versions. When i Press Power + Vol Down i get into FTM Mode. When i press Power + Vol Up i come into 'Revoery Mode?'. Ist in Chinese.
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.
What can id do, any Idea?
Regards
Click to expand...
Click to collapse
I have now used the Axon7Toolkit with Option 11 (Restore to stock) and after this flashed the 2017G with MiFlash. And it works. Don't know why.
But the Topic with the Bootloader is still open. So I'm not able to root and istall TWRP:
Message from Fastboot:
'Your device Software cant be checked for corruption. Please lock the bootloader'.

nukem007 said:
Already done, same Story. I've disassemble again and tryed like the first time. But MiFlash says no hello package. Laptop was meanwhile rebooted to ensure that no Background processes are blocking MiFlash.
I can also force EDL Mode by 'adb reboot edl'. The Axon is then shown as 'Qualcomm HS-USB QD Loader 9008)' in the device manager. Or is there a difference?
Click to expand...
Click to collapse
that's a bad connection, you must have let go of the contact too son
make sure it gets detected in your pc, hold it a couple of seconds more and then let go

Use the ADB command "adb reboot edl" instead as its the most sure fire way to ensure you are actually in EDL mode. The button combination method sometimes doesn't work as I've experienced this myself on more than one occasion.

I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.

> 4: Then i again lock the boatloader using fastboot oem lock.
This is the fatal step that bricked your phone in EDL mode. Reason: To relock bootloader, your phone must be full stock first:
stock ROM, stock recovery. But you was with TWRP = custom recovery!
Fortunately, the Axon 7 is "unbrickable". And your phone is still in EDL mode, this is not the worst brick status (DFU mode).
Note: if ever your were in DFU mode, there is still DFU tool to unbrick your phone (search appropriate topic in forum).
To unbrick in EDL mode, try to EDL flash entire stock ROM corresponding to your model (A2017, A217U or A2017G), Nougat recommanded (not Oreo: not supported by many tools; not Marshmallow: too old).
Recommended tool to flash:
Axon 7 EDL tool (it has link to full stock ROM for different models)
https://forum.xda-developers.com/axon-7/development/axon-7-edl-tool-flash-backup-restore-t3750759
Note: I never get "No hello packet received error" when using Axon 7 EDL tool. Miflash is not necessary nor recommended for me (overkill, various versions).
Some advices:
- always launch Windows Device manager and monitor it to check phone connection status (COM HD-USB QDLoader 9008, or DFU, or Android device).
- try using latest stable Qualcomm HD-USB QDLoader Driver, if possible signed version. E.g. version 2.1.1.2.
- of course charge the phone fully if possible before flashing.
- check and use good USB connection cable.
- you may need to set Windows in "test mode" first (disable driver signing) to avoid "No hello packet received error"
https://answers.microsoft.com/en-us...est-mode/27b555ca-852a-44c7-b42f-c84b8eec06f2

I have a really similar issue. After updating to Oreo ROM B03, I tried to enter EDL to flash twrp (but I didn't get to this).
I couldn't boot to bootloader using the recovery options (the system was just normally starting). I tried with vol+, vol- and power at one time. After the red led blinks I released all buttons. I guess I got to EDL, but I can't quit it now.
The QDLoader 9008 (driver version is exactly 2.1.1.2) is visible COM4, but I can't do nothing with it. Same error with Miflash, Axon 7 EDL tool stopped on "Loading the programmer". I tried all combinations vol+, vol-, power to boot to the system again, but without luck. Black screen and no reaction.
After night, when I hold power the red led blinks and that's all. When I connect cable to laptop the red led starts blinking, no QDLoader 9008 visible now.
Anyone has an idea what to can I do?

I have the same issue. I cant flash using MiFlash. My phone stuck on black screen and no LED flash. This is what i tried to do:
1: I unlocked bootloader using MiFlash and fastboot.
2: Installed TWRP recovery.
3: Tried to install custom ROM and it installed but phone was not booting to system and it always went to fastboot mod.
4: Then i again lock the boatloader using fastboot oem lock.
5: Just after that the phone went to black screen and no LED and adb devices dont show phone listed and fastboot not working.
6: Tried Vol up and power for a minute but no LED and no logo just black screen. Tried Vol down and power plus vol up/down and power for a minute but nothing.
7: If i connect phone with PC its appearing in Device Manager as Qualcom HS-USB QDLoader 9008 (COM10)
8: adb and fastboot dont detect it. MiFlash detets but not flashing and gives No hello packet received error.
Anybody can help? Should i try flashing stock rom using MyFlash if it works for some reason? Other files are not flashing like recovery or unlock etc.
Click to expand...
Click to collapse
Hi,
same issue here. Using the Axon7_EDL_Tool doesn't work for me: While flashing A2017G_B03_OREO_FULL_EDL via "Flash FULL EDL" it stops with the output: Loading the programmer: prog_ufs_firehose_8996_ddr.elf
Does someone know the solution?

same thing happening today, anyone found the solution yet?

[SOLVED]Advice on Soft brick

Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.

Xadro said:
Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
Nope, i did +- same mistake with you. You need to make an edl cable. I made it in 2 mins and flashed full edl. No need fancy buttons etc. Just short green and black cable when you have to by pressing with your fingers.

Xadro said:
Hi guys,
i ****ed up and need some advice.
I soft-bricked my axon 7.
Situation was as follows.
I had installed AEX Oreo Rom (build from May somewhen) along with the according B10+B32 bootstack and exclusive TWRP 3.2.1.7.
This configuration ran fine. However, i decided that i wanted to upgrade and started to Flash B32 bootstack and TWRP 3.2.1.8 (with treble).
I recognized that this configuration wasnt able to boot the current rom, so i reverted to B10+B32 bootstack and TWRP 3.2.1.7 and make a full backup of current config.
After that, i wanted to Flash newer bootstack and twrp again and continue installing the newest AEX with treble.
HOWEVER i had the greatly stupid idea to Flash DrakenFX's universal Bootloader and modem. The BL states that my device is corrupt and wont boot into either recovery or System.
I still can boot into fastboot and EDL Registers as "Handset Diagnostic Interface(DFU)"....
Is there a way that i can flash the correct bootstack via fastboot? I have made a complete backup earlier using axon7tool.
Any help would be greatly appreciated.
Click to expand...
Click to collapse
that's not a brick dude, that's a normal warning when using draken's bootstack
press power a couple of times and everything will be okay
to remove it, visit the los15.1 thread (second or third post)
and it registers as DFU because you're not entering EDL the correct way but instead you're entering into DFU mode.

Modding the cable by shorting the wires gives a deep edl flash ...
An edl flash can be done without modding the cable ...
Use the Miflash app ...
Edl mode is ...
Turn phone off ...
Press and hold ....volup + voldn + pwr buttons for 10 to 15 seconds ..
You will be stuck on a black screen ...led flash red ..
Open Miflash ...
Plug your phone into the cable ....
Miflash should detect ....if not hit refresh ...
Then flash an edl package to suit your phone ....there are several packages on XDA ....
I hope this helps in the future ...
BTW this is how I rescued mine after a bad flash

Voenix said:
I had the same problem a few days ago. When I booted to EDL Mode the red led was instantly on but the PC recognized it somthing like ZTE Handset Device Mode.
1. You can download TWRP Treble by NFound and flash it via your TWRP. Then reboot to recovery again and under the reboot tab its possible to boot to EDL/9008 Mode.
2. You build a EDL Cable to get the device from the red light to EDL mode. Just open some usb cable and connect the green and black (all four) together, plug it in the device and press the power button
until the red light is gone and hold on two additional seconds. Then remove the cable and plug another working cable in and the PC recognize it as Qualcomm in EDL mode.
This is literally how I unbricked my device.
Click to expand...
Click to collapse
Hope it helps

Thanks you guys on the advice!
I have made an EDL cable and was able to put the phone back into deep EDL.
I then restored my backups i took with axon7tool. Phone is in working order again!
Thanks again for pointing in the right direction to all of you! :good:

A2017G only EDL mode available, need help with brick

Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks

Drunkenmazter said:
Hello
Long story short, i digged out my axon 7 to use it with some music apps.
I wanted to return the phone to stock firmware, it had unlocked bootloader and running a custom nougat rom (AEX i think).
I followed this thread: https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413 and flashed full EDL package.
Now when i try to turn on the phone, or enter recovery i see the boot logo and quick flash of the commandpromt with a broken droid and the phone turn off again.
I can still enter EDL mode and flash the phone.
Any ideas how i get it up and ruunning gain ? preferably on stock firmware
Thanks
Click to expand...
Click to collapse
Use one of the less archaic methods:
Download "EDL Tool" from the ROMs, kernels, development section, along with an EDL package that goes with your phone model. Put your phone in EDL and just flash it with that tool. after that, if it still doesn't boot you have to format data, because you might have conflicting data. If you can't do it from EDL Tool (i think you can, don't remember) just enter the recovery with Vol+ and Power and make a factory reset

My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?

From some other threads, I believe you could try to EDL flash Nougat instead of Oreo, it would work better.
https://forum.xda-developers.com/axon-7/help/help-edl-factory-restore-stuck-device-t4031619

I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.

xperiaatic said:
I did that already but no luck, i still end up with the same error.
Is there some way to reformat or clean up internal storage completely in EDL mode? It seems that some garbage left behind by trying to unlock bootloader is surviving even EDL ROM flash and breaking OS boot.
Click to expand...
Click to collapse
According to other threads, the problem could be due to "sparse" structure while flashing.
I suggest the following:
- Use Axon 7 EDL toolkit to flash latest official TWRP recovery (for Oreo a specific TWRP would be requied).
- Inside TWRP then wipe data/factory reset and at the utmost Format data. Then retry to boot.
- If not OK, reflash with EDL full ROM and try again.

Already done that for several times with O ja N EDL rom's but no luck. Can't get to recovery nor make system to boot.

Did you successful unlocked bootloader?
If not, I would recommended Axon 7 EDL Tool by djkuz, flashing nougat edl package and unlock it through the options.
Can you get into stock recovery after flashing EDL package? It supposed to have a format option for userdata and cache.
Did you try to get into fastboot mode? Power + Vol up buttons if i'm not wrong.
If so, you could try to format these partitions.
fastboot erase /cache
fastboot erase /data

I have experienced the same problem but I have resolved flashing, with Xiaomi MiFlash (sometimes I use this program because occasionally flashing EDL packages with AxonEDLTool, it gives me problems like this) this package Axon7_RR-O_B32-B10_TREBLE-Ready_Oki20180803_FULL_EDL.
With this EDL, if the flash is successful, you will find NFound recovery 3.2.1-7 installed with which you can make a complete wipe and / or format them with the file system you prefer.
Afterwards, using MiFlash or EDLTool at your discretion, you can flash the EDL of the original system if you prefer.
I'm not an expert but this has solved my problem.
To unlock the bootloader, if the unlocking with EDLTool does not go well (it happened to me just yesterday while I was installing a Rom on another Axon 7), you can use Axon7ToolKit 1.2.1, it always worked well for me.
I hope it can help :fingers-crossed:.

xperiaatic said:
My story is very similar and now i'm stuck in EDL mode. I was able to flash stock Oreo B02 EDL package successfully and boot into OS. But after i was trying to unlock bootloader and reboot to recovery, ZTE logo appears for a second or two and then following error message starts looping:
(broken droid logo)
No command
Supported API: 3
E:failed to mount /cache: Invalid argument
E:Can't mount /cache/recovery/last_locale
EDL mode works but if i flash EDL package or boot/recovery again nothing changes, i still get the same error. Can't boot to OS any more and recovery does not work - screen just stays black.
So what are my options now to get it to work again?
Click to expand...
Click to collapse
Hi, just want to let here my solution for the same problem, it may help others.
I tried to flash A2017G_B10_NOUGAT_FULL_EDL and A2017G_B02_OREO_FULL_EDL but always getting the Can't mount /cache/recovery/last_locale error, phone completely bricked.
So I flashed A2017_B13_FULL_EDL_UNBRICK_DFU using MiFlash through EDL, you can find this here: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 (if your EDL mode works fine there is no need to disassemble the phone as shown in that tutorial)
Now the phone is completely working, recovery and system, but everything in chinese.
Then I flashed A2017G_B02_OREO_FULL_EDL using MiFlash through EDL, and now everything is working and in english

Thanks a lot for the tip! A2017_B13_FULL_EDL_UNBRICK_DFU did the trick and unbrick the phone.
What i did:
1. used MiFlash to flash A2017_B13_FULL_EDL_UNBRICK_DFU
2. after that A2017G_B03_OREO_FULL_EDL
3. reboot to recovery and performed factory reset
First time I did not perform the factory reset and got stuck on the boot picture without the reset function (power button did not work). Drained the battery and performed factory reset and got the phone working again.
update:
Phone is not stable on B03, some apps crashing from time to time for no apparent reason and also soft reboots happening randomly.
Now I got stuck on the Axon boot screen again after rebooting the phone manually and waiting for the battery to drain ...
i did not install or perform any custom action to the system, just regular use and apps, but it is still acting up badly.
I was planning to use this phone as a secondary handset because it is actually a very nice piece of hardware but now i am starting to have second thoughts about that.

A2017G Bricked Oreo

Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state

dalebaxter01 said:
Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3).
How i got here.
used a update.zip to go to oreo b3
using the EDL tool i backed up the OREO (A2017B03) recovery
using the EDL tool i flashed oki's trwp and rebooted
nothing...
Tried flashing EDL packages with the EDL tool and MIFlash.
> EDL tool hangs on `loading the programmer`
> MiFlash "cannot retrieve hello packet" , "try to reset status" ,"write time out maybe device was disconnected"
Tried other USB2 and USB3 slots
Tried other USBC cables
prediction, it seems i have broken EDL mode as the device is in the state but does not do anything after that.
device does not boot or reboot into edl. stuck in this state
Click to expand...
Click to collapse
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything

Predatorhaze said:
Why do you backup the recovery? its already included in the zip file,just grab it.And OKIs twrp does not support stock oreo.
If you can boot in twrp,do it and flash a twrp for oreo from nfound and wipe everything
Click to expand...
Click to collapse
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL

dalebaxter01 said:
i backed up the stock recovery just incase i was going to go back to it, but seeing what has happened it seems like even tho i flashed a custom recovery and didn't boot into it i am just plain stuck in a EDL state. i can't boot into recovery or fastboot as i'm seemingly stuck in EDL
Click to expand...
Click to collapse
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware

Predatorhaze said:
i was stuck in edl sometime ago too because i was flashing edl firmware and my laptop shutdown because empty battery.Can you enter FTM mode? hold vol down + power button.
If yes do it.Now close axon7toolkit EDL TOOL.After that open axon7toolkit and follow instructions.It will boot in edl again and try to flash firmware
Click to expand...
Click to collapse
holding for 2 min unplugged and another 2 min plugged and nothing

FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom

dalebaxter01 said:
FIXED
- Waited for battery to drop to 0% and the EDL loop was ended
- plugged into PC and used the buttom combo
- EDL'd ZTE Oreo Rom
Click to expand...
Click to collapse
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?

yarecco said:
Refreshing subject because same **** happened to me
My question is how long did you wait to empty the battery? I was about 57% when phone stucked in EDL... does it drains battery when being dead-like?
Click to expand...
Click to collapse
I don't have my Axon 7 on me, but I would give it about a day or 2 for it to die out on its own because its standby time can be insane if you have a custom kernel.

Lg v20 stuck into bootloop no download mode only recovery | please help

HI I PUT MY PHONE ON CHARGE SO IT SHOWED THAT I AM USING AN HANDSFREE SO I RESTARTED MY PHONE BUT NEVER TURNED ON AGAIN ITS STUCK INTO A BOOTLOOP
IF I TRY TO GET INTO DOWNLOAD MODE IT SHOWS DOWNLOAD MODE FOR 5 SECS THEN RESTARTS AGAIN
IT DOEST NOT BOOT INTO FASTBOOT ALSO AND MY PHONE WAS ON OFFICIAL STOCK ITS AN F800L MODEL ON OREO 8.0.1
I CAN ONLY GET INTO FACTORY MODE BUT IF I RESET MY PHONE IT STUCKS ON BOOTLOOP AGAIN, PLEASE HELP ME...
ANYONE??? PLEASEEEEEE :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:

hamzarawal said:
HI I PUT MY PHONE ON CHARGE SO IT SHOWED THAT I AM USING AN HANDSFREE SO I RESTARTED MY PHONE BUT NEVER TURNED ON AGAIN ITS STUCK INTO A BOOTLOOP
IF I TRY TO GET INTO DOWNLOAD MODE IT SHOWS DOWNLOAD MODE FOR 5 SECS THEN RESTARTS AGAIN
IT DOEST NOT BOOT INTO FASTBOOT ALSO AND MY PHONE WAS ON OFFICIAL STOCK ITS AN F800L MODEL ON OREO 8.0.1
I CAN ONLY GET INTO FACTORY MODE BUT IF I RESET MY PHONE IT STUCKS ON BOOTLOOP AGAIN, PLEASE HELP ME...
ANYONE??? PLEASEEEEEE :crying::crying::crying::crying::crying::crying::crying::crying::crying::crying:
Click to expand...
Click to collapse
I'm sorry for your loss. To me it sounds like something may be physically damaged.

To elaborate a bit further, fastboot doesn't usefully exist without root, stock recovery can only wipe your userdata, and you've already said download mode reboots way too early to try anything. There is no safe way to try anything with the firmware, if it even somehow is a firmware issue. There's the leaked firehose, if you force it into 9008 mode, but that's risky and I have no personal experience with it to give more details.
Basically don't expect it to be coming back.

Phoenix591 said:
To elaborate a bit further, fastboot doesn't usefully exist without root, stock recovery can only wipe your userdata, and you've already said download mode reboots way too early to try anything. There is no safe way to try anything with the firmware, if it even somehow is a firmware issue. There's the leaked firehose, if you force it into 9008 mode, but that's risky and I have no personal experience with it to give more details.
Basically don't expect it to be coming back.
Click to expand...
Click to collapse
SO THAT MEANS IM NEVER BUYING AN LG AGAIN:crying:

boot in fastboot flash twrp and reinstall laf partition

Lussardi said:
boot in fastboot flash twrp and reinstall laf partition
Click to expand...
Click to collapse
Without it already being rooted and the dirtysanta bootloader installed there is no fastboot mode on anything (which you would have seen if you had read the OP) but the h918 (which still can't flash with it) and us996, and you still need a working phone to actually set the options in Android to allow unlocking the bootloader.
And I'd put it at like an 80% chance it's hardware failure anyway, since it's boot looping in download mode too.

Try holding down volume down and plugging in USB.......

Same issue herewith...
LG V20 boot loop , restarting again and again , also when USB cable method is applied to enter into the Download Mode , it also restarts after sometime after showing download mode icon etc........