recently my mom's phone lenovo a6000 was having some issues so i did a hard reset later it was stuck at lenovo logo after 2/3 hours of wait i decided to flash stock rom some how managed to get it into edl or download mode with and thn got some error with the flashtool i was usin (QFIL) and the phone completely died and was stuck in a black screen of dead some how it is showing in my device manager as qualcom 9008 something but it is un-useable and i cant flash anything nor i cant get out of 9008 mode
Can you get into download mode using volume down + power key? Does adb detect the phone? If yes, then flash this twrp recovery https://forum.xda-developers.com/android/general/recovery-lenovo-p70-t3296687 using adb and if that works, then simply download the stock zip (just search google Lenovo_A6000_S034_Q113507_20170301 zip ) and flash it in twrp recovery. It will take some time (10-30 minutes approx) to flash so be patient.
Reply back if you need clarification.
user0u said:
Can you get into download mode using volume down + power key? Does adb detect the phone? If yes, then flash this twrp recovery https://forum.xda-developers.com/android/general/recovery-lenovo-p70-t3296687 using adb and if that works, then simply download the stock zip (just search google Lenovo_A6000_S034_Q113507_20170301 zip ) and flash it in twrp recovery. It will take some time (10-30 minutes approx) to flash so be patient.
Reply back if you need clarification.
Click to expand...
Click to collapse
buddy firstly thanks alot for replying
my phone is completely dead it is some how stuck in 9008 it only gets detected in pc even when i take off the battery
and when i try to flash through qfil i get sahara and firehorse error thn the phone gets disconnected
guide me to get it out of 9008 mode tried everything but nothing is working is it possible to push it to adb from 9008 ?
thanks.
Sorry man, if my previous instructions didn't work and adb doesn't detect the phone then I can't help any further.
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?
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:
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
My A2017G did an OTA update on its own yesterday and after that it would only display the 'bootloader unlocked' warning and go straight to DFU mode. I managed to get into EDL mode and Windows also now recognises the phone as 9008. Is there any way that I could backup data before reflashing? The key combinations work normally and I can reboot into any mode
blendomatik said:
My A2017G did an OTA update on its own yesterday and after that it would only display the 'bootloader unlocked' warning and go straight to DFU mode. I managed to get into EDL mode and Windows also now recognises the phone as 9008. Is there any way that I could backup data before reflashing? The key combinations work normally and I can reboot into any mode
Click to expand...
Click to collapse
Did you have TWRP or anything else installed?
If you don't have TWRP, install it via EDL with EDL Tool, then enter it and get stuff out via usb. You were most probably encrypted, in that case I honestly don't recall which TWRP handled stock encryption, but I guess the official one on twrp.me (axon7) does.
any reason you're still on stock, though? Friendly advice, take a hard look at the new Pie device-specific ROMs
Choose an username... said:
Did you have TWRP or anything else installed?
If you don't have TWRP, install it via EDL with EDL Tool, then enter it and get stuff out via usb. You were most probably encrypted, in that case I honestly don't recall which TWRP handled stock encryption, but I guess the official one on twrp.me (axon7) does.
any reason you're still on stock, though? Friendly advice, take a hard look at the new Pie device-specific ROMs
Click to expand...
Click to collapse
I tried flashing various versions of TWRP using the EDL tool and it always showed a success message at the end, but when I booted to recovery via the bootloader menu, it just went to DFU mode instead.
Also, i tried custom roms before but i switched back to stock for the camera quality.