I was flashing the MIUI 8 Stable after formatting system from TWRP and my phone is now bricked. Can't turn it on, can't get into TWRP and the LED isn't even lighting up while charging it.
Is there a way I can fix this or do I have to take it to the service center now?
Flash full ROM in EDL mode from MIflash tool
Harsh khatri said:
Flash full ROM in EDL mode from MIflash tool
Click to expand...
Click to collapse
How do I get into EDL mode? The device isn't responding to any button combination.
Related
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 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:
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.
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.
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.