GUYS first i installed Twrp 2.7 than after getting into recovery mode i flashed TWRP 3.0.2 but after that phone is dead.Not even lenovo logo
when i connect it to PC it shows as "Qualcomm hs-usb qdloader 9008m" (but not detecting as fastboot mode) and many many windows gets opens and tell me to fomate drive but cant formate it shows that disk is read only
when i tried to Flash stock rom using QPST it shows "failed to switch to EDL mode". any key combination isnt working.I cant go to EDL mode maunally as phone is not detecting as fastboot or adb mode
is my motherboard is broken????
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?
It seems i have bricked my device by flashing a custom recovery.
USB Debugging is enabled but OEM Unlocking is not
Can't seem to get any interaction with the buttons, but it is seen in windows as Qualcome HS-USB QDLoader 9008 (COM3)., holding buttons seems to do nothing aswell as the phone has no LED indicator or vibration.
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
Hello everyone, there is Lenovo K6 Power, which when turned on hangs on the Lenovo splash screen and the fastboot mode is written on top.
1. you can turn it off and hold both volumes to connect to the PC and it will be visible as Qualcomm / Lenovo HS-USB QDLoader 9008,
1.2 but with firmware via qfil - Download Fail: Switch To EDL FailFailed to Switch to Emergency Download mode. (although the body is essentially already in mode)
2. The fastboot devices command is defined in the fastboot. through the fastboot oem command, reboot-edl- switches to the mode, but when trying to flash it repeats p1.2
3. enters the native recovery, tried to make wipes - it does everything, and after rebooting the mode enters the fastboot again.
*
On a third-party resource, they prompted that we should try to update update.zip with 231 firmware from the native recovery. Does anyone have this file?
sorry for my english, I translated google translator)
imprestness said:
Hello everyone, there is Lenovo K6 Power, which when turned on hangs on the Lenovo splash screen and the fastboot mode is written on top.
1. you can turn it off and hold both volumes to connect to the PC and it will be visible as Qualcomm / Lenovo HS-USB QDLoader 9008,
1.2 but with firmware via qfil - Download Fail: Switch To EDL FailFailed to Switch to Emergency Download mode. (although the body is essentially already in mode)
2. The fastboot devices command is defined in the fastboot. through the fastboot oem command, reboot-edl- switches to the mode, but when trying to flash it repeats p1.2
3. enters the native recovery, tried to make wipes - it does everything, and after rebooting the mode enters the fastboot again.
*
On a third-party resource, they prompted that we should try to update update.zip with 231 firmware from the native recovery. Does anyone have this file?
sorry for my english, I translated google translator)
Click to expand...
Click to collapse
What is the exact firmware version that you are trying to download into the eMMC?
I'd suggest you to find a full package for K6 Power (I have the package for K6 Note) and try to download it with QFIL. You can find these on a lot of YouTube videos.
And for entering into the EDL mode, better install a custom recovery (you can find the procedure on XDA) and enter EDL mode from TWRP recovery. This is a better option as you will barely know if you device is in EDL mode as the screen is always off.
Don't worry you will get the stock recovery back when you download the stock firmware into the eMMC.
Thanks,
tfr.
My phone was rooted nad has an unlocked bootloader
today, i got prompted to update magisk. I had done this previously with no problem, but something must have changed with magisk, because after rebooting the phone got stuck in fastboot mode.
I tried the "hold power and volume down until the phone reboots 6 times in a row", but it didn't work. I plugged the phone to the pc and it entered download mode
is there a way to fix it myself? is download mode the same as 9008 mode?
the phone is a AWM model cross flashed to ulm, running android 9
nevermind, got the phone to 9008 mode too (detected by pc as Qualcomm HS...)
I have same problem, i get download mode but when i open lgup there is no option to choose kdz or select refurbeshed
So how did you fix it?