Hi, today my Axon 7 got stuck in EDL mode for the second time. And I would like to know why...
I was about to flash TWRP in order to try LOS 16.0 and when I turned the phone off and plugged the cable with the button combo it entered into EDL Mode sucessfully (PC recognises it normally, COM3) but EDL Tool got stuck at "Loading the programmer: prog_ufs_firehose_8996_ddr.elf".
The only way to fix this problem as far as I know is by restarting the phone into EDL again but mine is somehow getting stuck and I can't restart/turn off
As I said before this is the second time it's happening, and the last time the only way i got it fixed was by waiting until the battery runs out and then try again.
Does anybody know what causes this? Is there any fix? Thanks in advance
Sorry for my english
joaocandeias said:
Hi, today my Axon 7 got stuck in EDL mode for the second time. And I would like to know why...
I was about to flash TWRP in order to try LOS 16.0 and when I turned the phone off and plugged the cable with the button combo it entered into EDL Mode sucessfully (PC recognises it normally, COM3) but EDL Tool got stuck at "Loading the programmer: prog_ufs_firehose_8996_ddr.elf".
The only way to fix this problem as far as I know is by restarting the phone into EDL again but mine is somehow getting stuck and I can't restart/turn off
As I said before this is the second time it's happening, and the last time the only way i got it fixed was by waiting until the battery runs out and then try again.
Does anybody know what causes this? Is there any fix? Thanks in advance
Sorry for my english
Click to expand...
Click to collapse
Only way out of EDL Mode (asides from flashing a file) is to let the battery drain completely.
If your phone gets stuck loading the .elf file whilst using the Axon 7 EDL Tool, you can try a couple things: -
- Change which USB port you are plugging into
- Change your wire
- Use MiFlash instead, simply just put the twrp into a folder and rename the twrp to recovery.img and select that folder in MiFlash.
- Make sure your Axon 7 EDL Tool is extracted properly to C:/ Axon 7 EDL Tool
- Go into EDL mode via ADB and try again, or go into EDL mode via just plugging in your device whilst it's on the home screen and launching the EDL Tool. The EDL Tool will automatically take you to EDL mode.
Hey there,
just wanted to add that I had the very same issue. In my case I solved it by letting my battery drain just like you described and get into EDL Mode once more but this time with another USB slot.
More precisely I tried it with USB 2.0 instead of 3.0. I don't know if that was the resolving change in the end but then it suddenly worked out for my. In my case it was full flashing nougat 7.1.1 when I had Oreo b03 before.
2 solutions:
- try rebooting to EDL, using Axon 7 EDL Tool flash a custom recovery. It will then ask you to reboot.
- you can also flash a full EDL stock ROM, but you will certainly lose data.
- if you can't use Axon 7 EDL Tool because EDL mode isn't working correcly, let the battery drain totally then boot to EDL.
Related
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
I'm right there with you. Literally did the exact same thing. I'm stuck in DFU mode on my 2017U.
UnsecWifi said:
I tried to go from 7.0 to 7.1.1. I had root, unlocked bootloader and twrp. I somehow managed to hose everything and now when I try to turn on the phone I get the AXON screen and it stays there.
If I try to "power and up" it blanks out and at least shows up as com 5 in the com list.
Tenfar's tool goes through the motions but no change, Tenear's tool doesnt see the device.
Am I hosed or is there someway I can unscrew this up.
Click to expand...
Click to collapse
Use this thead https://forum.xda-developers.com/axon-7/development/edl-emergency-dl-mode-twrp-unlock-t3553514
And remember NOT USE ZADIG DRIVER FOR MIFLASH, use the driver from the thead.
Tell me if it work
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
use another computer have windows 7 32 bit(try use windows 10 32 bit)
UnsecWifi said:
"cannot receive hello packet", I think its hosed. I dont even know if its really in EDL mode, its a black screen and it shows up as a COM port but nothing seems to see it.
Click to expand...
Click to collapse
If it sees it you should be alright, just close the MiFlash, or even better reboot your computer. Then try to reset ur axon by holding power button and then when it fails enter EDL again using the combo.
The MiFlash works best on a freshly booted EDL where u did not attempt and fail to flash stuff before. So always reboot the EDL fresh before using the tool.
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory::laugh::victory: Awesome. Thanks to everyone.
UnsecWifi said:
I went back and forth between my laptop(win10) and my desktop(win7) and never could get anything to work through MiFlash. Then all of a sudden it worked (I have no idea why). I wound up flashing the B15 new_full.
After it finished it did nothing. No splash screen nothing. Only flashing led. I plugged it back in and the battery was dead. I charged it up and it worked!!!!:victory:[emoji23]:victory: Awesome. Thanks to everyone.
Click to expand...
Click to collapse
Did it work on win 10 or 7?
Also what drivers did you have installed? I'm afraid mine is a lost cause
Did it on my desktop with Win7. Used qualcom bulk drivers. And the only file to work for me was B15-NEW_FULL (Nougat). Unpack it and select the A2017U_B15-New_twrp_edl folder, refresh so you see your COM port and flash it.
If it doesnt work try going back into EDL mode, closing and reopening the MiFlash utility, switch USB ports etc. And use the cable that came with your phone. Make sure to charge it first with the original charger.
Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
There's this tool for the Redmi Note 4 that can get your phone recognized by MiFlash if you can get into Fastboot. Is there something like this for the Axon 7? I couldn't find anything.
https://forum.xda-developers.com/re...ool-redmi-note-4-edl-mode-o-removing-t3684024
Penoro123 said:
Hi, today I tried to update my phone to LOS 15.1. I got a tad lazy, because I've flashed many roms in different phones so many times that maybe I skipped a step. Have in mind that I was on NFound's 3.2.1-7 recovery and AOSIP 8.1 rom with B32 Bootstack.
This is what I did:
1. I flashed the Bootstack and Modem that was on the official thread.
2. Went to Fastboot to flash the newest Recovery (3.2.3.0).
Then when I tried to get into recovery to flash the rom, I knew I ****ed up :cyclops:; It reboots instantly as soon as I try to get into recovery mode . I can boot into Fastboot and launch commands from my PC just fine, tried flashing many recoveries to see if I could get in, but I can't.
Tried getting into EDL, but the phone shows in the Device Manager as ZTE Diagnostic Interface (DFU).
Is there something I can do without opening the phone? Maybe there's a way to flash my old bootstack through Fastboot? Maybe it's because I'm on Windows 10 that it shows as UDF in the Device Manager? Any ideas?
Click to expand...
Click to collapse
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Oki said:
The problem is the bootstack. The universal bootstack linked in the OP of the LOS15.1 doesn't support EDL mode. I recommend NFound or mine to avoid these kind of issues. With these other bootstacks there is always the EDL mode available by using the key combo or the EDL cable, so there is no risk of brick your device in DFU mode.
Click to expand...
Click to collapse
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
I'll try this and I'll try using a deep flash cable.
There's a guy that went through the very same thing and was able to get it working again using an homemade cable.
https://www.reddit.com/r/Axon7/comments/9hc9gu/your_device_is_corrupt_it_cant_be_trusted_and_may/
Penoro123 said:
If it didn't support EDL mode, would there be anything I could do? It seems that I need to put the phone on EDL to be able to flash and unbrick it. If I press vol+ and vol- while booting the phone I can get to EDL mode, but the phone shows as DFU in the Device Manager., so it isn't recognized in MiFlash.
Click to expand...
Click to collapse
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
Thank you, Oki. I'll surely try tomorrow and post again if that one or any method works for me.
You can try enter the FTM mode: https://forum.xda-developers.com/showpost.php?p=69604257&postcount=7
It worked for me when I did the same like you. I also had the universal bootstack linked in the OP of the LOS15.1 and flashed a wrong recovery.
tdm said:
Have you tried this?
http://en.miui.com/thread-310325-1-1.html
Note that you should unplug the device to remove the wire in step 10 to avoid any possibility of damage. The device will remain in EDL mode until rebooted.
That should work for all qcom devices.
Click to expand...
Click to collapse
Oki said:
You can follow the UNBRICK link in my signature on how to use the EDL/QDL/deep flash cable. You can also try to turn your phone completely off and then plug it while pressing VolUp+VolDn
Click to expand...
Click to collapse
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Penoro123 said:
I got the phone to be recognized in MiFlash. I even flashed the B19 EDL package, but now the phone boots into recovery for a second (I can see the splash screen), then shuts down. I'll try downloading another EDL package.
Click to expand...
Click to collapse
Nice. So just to confirm, you have a G model and the wire trick worked?
tdm said:
Nice. So just to confirm, you have a G model and the wire trick worked?
Click to expand...
Click to collapse
Yeah, it did, but now I can't even get into fastboot to shut down the phone or let it discharge. It boots into MiFlavor, then the screen goes black but it's still on.
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Penoro123 said:
I finally got the phone working again. Jesus Christ, I was about to go out and spend $600 to just buy another phone.
I"m in a rush, so if I sound vague in any part, you can just ask.
This is what I did:
1. I discharged my phone completely by leaving it overnight in the Fastboot screen.
2. I cut a black ground cable from a mouse cable I had lying around.
3. I used one of those things to cut fingernails to expose the copper cable / remove the insulation plastic.
4. I bent it to form an "u".
5. I put it inside the usb port touching the 2nd "electric track" (that's how they are called here, at least).
6. I connected the cable to the PC (the phone didn't boot nor started charging).
7. I removed the cable from the usb port and connected the phone to the pc again.
8. It was recognized in MiFlash 2016.08.30, then I proceeded to flash the B19 Nougat room.
After I flashed the phone, It always booted into recovery mode for a second, then the screen went black. I couldn't even boot into Fastboot to discharge the phone or flash a new recovery, but after many tries, I could. I instantly deleted cache and userdata from Fastboot, flashed TWRP 3.2.3.0 recovery and was able to get in. Then I flashed AOSIP again, as I got error 6 trying to install LOS bootstack.
I think if I had deleted the Cache and Userdata the first time I wouldn't have had to go through all of this, so try that first before flashing another recovery, if you are able to boot into fastboot.
An important thing to note, before trying it with a deepflash cable or if you are lazy like me, by putting a copper ground cable into the usb port, is to DISCHARGE your phone completely, otherwise your phone will just charge if you try to unbrick it using one of those 2 methods.
I'll upload pics later, if anyone wants. It's pretty simple, just cut a black ground cable, expose the copper cable / remove the insulation plastic, and put it inside the usb port lining it up with the second metallic track.
Click to expand...
Click to collapse
Bro please put the all the details briefly here so that everyone can learn and save their device from brick
Hello guys, how are you today ?
I will do my best to write properly (french, sad)
So, i unlocked my phone with no problem. I tried to install a working TWRP. The ADB command to install was easy, but impossible to boot in twrp with the boot command on ADB.
I understood that i just needed to press up and power to open TWRP.
I putted on my OTG USB KEY the xiaomi.eu weekly ROM for my phone.
I formated only DATA, and i began the installation.
I had an error, and after my OTG was not recognize.
I just putted up and power to reboot the phone and try again.
But i dont know what happened, black screen, impossible to boot on something, i tryed to hold power 15 sec and nothing work, impossible to go to fastboot mode.
The phone is recognized on windows but nothing more.
I searched on the net and my phone is bricked. I need to open it to press ELD.
I found someone who has ELD permission for 12$.
Now i just want to know if someone can explain me how to open without damage the phone and how to be in ELD mode.
Thanks you and have a nice day.
I guess you could try to buy an EDL cable instead.
How you see phone in device manager?
newhope81 said:
Hello guys, how are you today ?
I will do my best to write properly (french, sad)
So, i unlocked my phone with no problem. I tried to install a working TWRP. The ADB command to install was easy, but impossible to boot in twrp with the boot command on ADB.
I understood that i just needed to press up and power to open TWRP.
I putted on my OTG USB KEY the xiaomi.eu weekly ROM for my phone.
I formated only DATA, and i began the installation.
I had an error, and after my OTG was not recognize.
I just putted up and power to reboot the phone and try again.
But i dont know what happened, black screen, impossible to boot on something, i tryed to hold power 15 sec and nothing work, impossible to go to fastboot mode.
The phone is recognized on windows but nothing more.
I searched on the net and my phone is bricked. I need to open it to press ELD.
I found someone who has ELD permission for 12$.
Now i just want to know if someone can explain me how to open without damage the phone and how to be in ELD mode.
Thanks you and have a nice day.
Click to expand...
Click to collapse
Can you get into fastboot
My phone was completely stuck in black screen impossible to go on fastboot mode.
Luckely, i dont know how but my phone was recognized like if i was in EDL mode.
I contacted an asian man on WhatsApp, he putted his logs on miflash to allowed EDL flash.
My phone is Alive now!
Where Can i buy an EDL cable if i need it ? It replace the open of the phone?
Good evening! I hope you can help me.
I flashed LineageOS 14.1, but I wanted to go back to EMUI. I made all the wipes and tried to flash different stock firmwares through a forced update (volume buttons + power button), but it never worked. At that point, I read about a guy in this forum who suggested to create a flashable zip with Huawei Update Extractor: I followed the suggestion and tried to flash it with TWRP. No error was given, but when I tried to restart, TWRP told me I had no OS installed. I thought it was strange, so I tried to restart anyway. That's when I got in rescue mode. I can't get into the recovery and I can't use fastboot. What rescue mode shows me is:
RESCUE MODE
Attention!
Please update system again
Update User Guide:
*link*
*android avatar*
Error!
Func NO: 10 (boot image)
Error NO: 2 (load failed!)
Pressing the three buttons, I'm able to force an update. The problem is I can't find a firmware that doesn't get rejected. With Lollipop firmwares, it starts to install, but it fails at 12%. With Marshmallow ones, the installation process doesn't even start.
What can I do to make it work again? I'm very sad because this phone was gifted to me a couple of days ago and I already messed it up. I don't even know how to turn it off.
What can I do to get in fastboot mode? At that point, what should I do to flash the stock firmware? Or maybe do I need to find the first stock firmware ever installed into this phone to make the forced update work?
Please, I need help. Thank you in advance!
P.S. The phone's model is ALE-L21. I live in Italy, so I assume it's a European version.
Did you managed to fix this?
Jhon_Locke said:
Did you managed to fix this?
Click to expand...
Click to collapse
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
ErikChimello said:
Not yet, but I'm working on it. I found out that the device is recognized by my PC if I follow these steps:
1. Connect the phone to the PC and wait for it to go in rescue mode;
2. Wait until the notification LED stops to blink;
3. Disconnect the USB cable;
4. Press volume - and power button;
5. Reconnect the cable.
At that point, the screen turns black and the phone is recognized as "㌲㔴㜶㤸". I installed the drivers and now it's recognized as "HUAWEI USB COM 1.0". I should be able to reflash the partitions and make my phone work again, but I'm still trying to understand how to do it correctly.
Any help is appreciated!
Click to expand...
Click to collapse
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Jhon_Locke said:
fastboot detects your device when you plug it into your computer?
I mean, if you run "fastboot devices" it shows your phone?
I've had this same problem but with an P8 Lite 2017, after flashing some ROM that supposedly was the stock one and trying to flash recovery I ended up with my phone bootlooping into rescue mode, I was able to "bypass" this thing rebooting my phone like crazy, seriously like after 20 reboot it finally booted into the damn ROM and I never touched the phone again. Sometimes when the phone ran out of battery and tried to power it on the phone booted into rescue mode and again after some reboots it booted to Android but now I want to install a custom ROM or at the very least root this damn phone so that's why I'm asking you if you have solved this, if you do then probably if I follow the same steps I would be able to fix that screen, hopefully.
If you are able to flash something start with flashing all recoveries your update.app has, maybe that's the problem (at least in my phone it is).
Click to expand...
Click to collapse
No, it doesn't show anything if I write that command...
I guess mine won't ever boot into the rom because it seems like there's no system installed. I made some researches and found out there are some softwares that let you reflash the partitions IF the phone is recognized as "HUAWEI USB COM 1.0". I'm still trying to figure out how to do it correctly though. I feel like if I do something wrong, then my phone won't probably turn on again.
In your case, you should be able to flash a custom rom without any issue. You just have to be very careful and inform you as much as you can: I don't want your phone to end up like mine?. Anyway, it seems pretty hard to go back to the stock rom, so think about it before you flash a custom rom. Also, make a Nandroid Backup is very important.
I have some previous threads on my Redmi 7A dead... but no one responded, some did but said I can't fix it, buy a new phone. I am not in a financial condition to buy a new phone. All I can do is fix this phone and continue using it till I get a new phone. But since 3 weeks I am not able to use my Redmi 7A. I was hopeless that this phone could be repaired or could be used again but I went through a few videos on YouTube and saw a ray of hope but still I was helpless I tried booting it into EDL mode using the test point method but nothing worked out. Please I NEED HELP to fix this phone. I have a brief description below of the timeline about how it
crashed, how it was in the service center, what happened after it.
Alright so,
At March 13, It was on AOD (I know it is not supported keep reading), running nusantra os latest version for (Mi-439 aka Redmi 7A, 8) which was last updated on Dec 4, 2022. So when It was on AOD I tried to unlock the phone and it froze. So I rebooted it abnormally. After it was booting it stuck on the Redmi logo but it wasn't going ahead, not showing the boot animation. So I tried to boot it in recovery mode, when it was booting in recovery mode the phone was just shutting down and trying to reboot itself again but it couldn't. So I tried to wipe everything using fastboot commands and the command which I used was -w. So after that instead of waiting at the redmi logo it was stuck in a bootloop, in fact booting in the bootloader (fastboot mode). So after that I lost hope and gave it to the nearby service center. Please note that the phone was turning on before giving it to the service center. After like one day I went there to check if it was done, they say that it's a hardware problem, they are not able to fix it, When I came home the phone didn't boot neither in the fastboot mode nor It was turning on. So I thought it's not charged so I charged it for 1.5 hours but still there was no sign of life. I asked them about the phone not turning on they told me that it's a hardware issue and hung up the phone, said I am in a hurry I will call you later. Till this day I received no call. So Now I am posting this because I see some hope of EDL mode. I even tried to boot it in the EDL mode but still it was neither booting in the EDL mode nor my computer is detecting my phone (I have all the drivers installed). Please help ASAP.
Gibbron1 said:
there was no sign of life
Click to expand...
Click to collapse
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
mYXiao said:
1. does the led light up when you charge it?
2. what does you pc device manager show when you plug it in? (do you hear the windows sound?)
try every button combination that is possible. i mean two buttons at the same time, three buttons, all buttons... and for about even up to 1 minute (because this brought my 7A back from just led light when charging to pc detected a usb device)
i can't reproduce your brick but i managed to debrick via edl mode once on a "complete dead" (only led lights up when charging) so i think you can do that too.
also as long as you work with the EDL Tool, deactivate your Firewall (and don't forget to activate it again) just so be sure.
3. are you trying to enter edl mode via adb terminal? i would say you have to open the back cover and enter edl mode via hardware bridge from edl point to ground.
and as far as i can remember you have to be really quick between "starting" (booting) edl mode on the phone and make the phone "accept" edl mode. i think i first made the hardware bridge and then pluged the usb in.
i will dig deeper again in the next few days so i can give you better info's
Click to expand...
Click to collapse
I bought another phone, but thanks for the reply and help you gave me. My new Phone is Mi A1.