My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Used Twrp to flash Custom ROM, EDL still not fixed
sauerkraut17 said:
use ADB
Enable ADB in developer options
use command "adb reboot edl"
Click to expand...
Click to collapse
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
levittc5280 said:
I had no OS installed, only twrp recovery and I was able to unlock my boot loader. I tried to flash Lineage-OS ROM in twrp and didn't have much luck because i would get an error code saying it wasn't compatible with my phone and had to go into the ROM files and edit the updater-script file to remove the compatibility check.
In the end I have a working phone with a custom ROM but EDL mode is still not responsive and seems to freeze my phone as soon as I press the 3 buttons to get into EDL. the notification light blink remains on so ill take it as an indicator that something is wrong with the firmware that it uses. i still want to fix it so EDL can be used but unsure how to fix it. I did some researching and was wondering if using a deep flash Engineering cable would work to fix the EDL mode and any other problems that could be there.
Click to expand...
Click to collapse
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
sauerkraut17 said:
EDL using the volume/power button has issues with the newer bootstack (which it sounds like you're on). However, since you have an OS now do as I recommended. It will 'reset' the EDL and once done via ADB command it will work with the volume/power buttons like it did before moving forward.
Click to expand...
Click to collapse
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
Have the same issue as you do after installing the bootstack. but even with the adb reboot edl command my phone just restarts normally.. But my OS is working fine, is there any way?
Try to use volume up and volume down only and plugging in USB cable........
stinka318 said:
Try to use volume up and volume down only and plugging in USB cable........
Click to expand...
Click to collapse
Tried everything already. Can only get to DFU mode..
So, I have a similar problem: after flashing a new version of TWRP, now Recovery doesn't start. The problem is that I haven't any OS installed and the last chance to save the phone should be reflash stock by EDL... BUT EDL mode doesn't start if I press vol UP + vol DOWN during power on... (it became black with a red light, but if I digit "ADB devices" on ADB, no devices seems connected, and in the same way it's impossible to use Axon7Toolkit). So: no Recovery, no EDL mode, no OS installed, my phone is a paperweight.
Is there a method to save my Axon 7?
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
levittc5280 said:
My Axon 7 is the A2017U, i had the B32 Nougat running on it and wanted to try the new lineageos 15.1, but had to unlock my bootloader first i used the toolkit like I've done in the past and was able to unlock it and flash twrp, when i try to boot it back on it goes to factory testing mode, i was able to get into twrp and i wiped everything and it stopped the problem of booting directly to FTM but after that i tried to go into EDL mode and it seemed to try to enter the mode but the red led indicator light stays on rather than doing a quick blink. its no longer picked up as a COM port, when i enter fastboot mode adb doesn't seem to work and I'm unsure what to do or if I'm out of luck. Thank you for your time and the advice and help you guys are able to provide.
Click to expand...
Click to collapse
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.
Syberclone said:
Here is something to try ...
Enter edl via button combo (volup + voldn + pwr)
You should have a black screen ...
Now plug your phone into the cable on your PC/laptop ..
If your PC / laptop doesn't recognise your phone via Miflash or app you are using ...
Try tapping the power button once ...this seems to open/close the port ...
I noticed this when I was using edl mode to flash a ROM
I hope this helps
Click to expand...
Click to collapse
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
Did you resolve problem?
spasacamen said:
Thanks, I tried but this doesn't solve my problem. The strange thing is that connecting my phone in EDL mode, the phone appears in device manager as COM port, but is not seen launching an "ADB devices" command and is not seen in MiFlash too. I tried to change drivers from "ZTE device (something)..." to "Qualcomm HS-USB QDLoader 9008" and in this way, although ADB doesn't detect nothing yet, MiFlash detects a COM port, but flashing an EDL image still fails with a "cannot receive hello packet" error.
Now I ordered a deep flash cable, hope this can solve... next week I'll know if it works.
Click to expand...
Click to collapse
No need to order that cable... If you still can cancel it i'd tell you to do that. You made a mistake by changing the drivers, you had the "ZTE Handset Diagnostic Interface (DFU)" driver, and replaced it with the EDL driver.
This of course does not work because your phone is in DFU MODE instead of EDL. What you have to do is uninstall the device via device manager and also tick "Uninstall driver software for this device", then turn the phone off and enter DFU again, and then use MultiDL from this forum to enter EDL. After that, use MiFlash or EDL Tool, and try flashing a FULL EDL file
By the way ADB will only work on FTM mode or the recovery or on a working system. You won't get ADB on edl mode or dfu mode because they simply don't have adb working, it's normal
i never use xda but this quote thing is what i have aswell
levittc5280 said:
Using the ADB command i was able to get into EDL mode and it was able to get a COM port. using the volume + power buttons had the same problem. Would using an older bootstack fix it?
Click to expand...
Click to collapse
all i see is the red light in edl, whatever i try it Always just goes to a red light and a black screen. this happened after trying to unlock the bootloader. i was in android 8 and tried to lock it, it messed it up as my Phone could not boot anymore, i flashed the stock android 6.0 or something that came with the axon 7 toolkit and it did work but when trying to unlock the bootloader as the device state suddenly was locked it broke the whole thing and i oped edl could save me but even that is broken just like what the person in the quote has
Well the only fix to get EDL mode is through test point, there's a thread of unbricking Axon 7 using test point, find it, you'll need to open your back cover to do this
This in case nothing works to get into EDL mode.
Related
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
both volume buttons + plug the wire doesn't work?
senny22 said:
hi!
So i've messed up my phone. I was formatting my data and as twrp was stuck for 15 minutes at done i forced rebooted my phone. after that i can only boot into twrp (not even edl mode) no matter which button combos i use. But the thing is, twrp is stuck at the loading screen. the phone is recognized in adb but it is recognized in recovery and trying to use the command "adb reboot edl" doesn't work, nothing happens.
What can i do? I was thinking about using some commands where the phone is recognized in adb as in recovery but i have no idea what to do.
Click to expand...
Click to collapse
I have exactly the same problem, could you solve it? I'm very worried about my phone
ale0796 said:
I have exactly the same problem, could you solve it? I'm very worried about my phone
Click to expand...
Click to collapse
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
senny22 said:
Hi! When I held both volume buttons and the power I dunno in what mode I was in but while my phone was on this mode and plugged in to my PC it was recognized in device manager as ADB something (I don't remember). I was shocked when I saw that my PC would recognize the phone because no LEDs was lit (not even the red LED you get in edl mode) and also my phone would start instantly with pressing the power button, (in edl it takes about 10 to restart the phone). Anyway so I tried zadig, Qualcomm drivers and even a different pc but it would still connect as ADB something. Lastly I disabled automatic driver updates in windows and installed the qualcomm axon 7 firmware driver (Google it). After that I rebooted and my phone was now recognized as "qualcomm hs loader" something and so I could use Miflash to flash a stock firmware. Miflash would work right away though but after maybe 15 tries and lots of reboots it then worked for some reason I don't know. After that I had a stock recovery back and it was all going smooth again from there.
Click to expand...
Click to collapse
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
ale0796 said:
THANK YOU SO MUCH, after 30 more attempts, I get the xiaomi miflash flashed my device, the last thing I tried was to disconnect the phone, keep the power button for 10 seconds and then connect it. The device was recognized as "Qualcomm HS-USB QDLoader 9008" download this rom https://build.nethunter.com/misc/axon7/A2017U_B15-NEW_FULL_EDL.zip unzip it and select the folder with miflash and flash it. Miflash did not send me the "can not get hello package" message anymore. I really appreciate it a lot, without your message I would probably have kept my phone in a box and forget it. I hope all people can read this comment and solve this problem. THANK YOU
Click to expand...
Click to collapse
Really glad I could help
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Choose an username... said:
I assume you're not on Windows 10 x64? If you aren't, either get a PC with Win10 x64, or do this:
Connect the phone, get into EDL mode. Now go to the Device Manager, and tell me where it appears.
It can appear as:
-"Qualcomm HS-USB QDLoader 9008" under Ports (COM & LPT);
-"ZTE DFU Interface, under Ports too; or
-"QUSB_BULK" under Universal Serial Bus devices or unknown devices.
If it appears as the DFU stuff, you'll have to follow the 4th category brick repair guide. If it appears as QDLoader, right click on it, then Properties, then go to Bits per second and put the number at 115200 or 128000 if it's not there. Then hold the 3 buttons (vol and power) until Windows beeps and the device manager spazzes and the phone flashes the red led, then try MiFlash again.
If it appears as QUSB_BULK, uninstall the driver (tick delete driver software too) and restart edl.
Click to expand...
Click to collapse
I'm on win10 64bit
daevion0 said:
I'm on win10 64bit
Click to expand...
Click to collapse
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Choose an username... said:
Then do everything I described above or just try another PC. It always happens that one PC can be decided not to let you unbrick your phone for some reason
Click to expand...
Click to collapse
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
daevion0 said:
Is there no other option? is there no other way to at least get fast boot mode back on my phone?
Click to expand...
Click to collapse
Lol nope, not if EDL is not working for you. You still didn't tell me whether you have a DFU brick or not. If you do have a DFU brick the only surefire way is to disassemble your phone and short a testpad, so don't complain.
Try what I told you above. It may be that it's set at 9600 baud
daevion0 said:
Okay so long story short: I unlocked my bootloader, flashed twrp and things like that and tried to flash lineage. This was all using the Axon 7 tool. I did something wrong and now I can't get into any other mode but EDL mode. The phone shows up in Miflash but I always get some "cant read hello packet error" and it tries to "reset" and end it eventually just stops and gives me an error. Plz help.
Click to expand...
Click to collapse
1. You must use "Qualcomm HS-USB QDLoader 9008" driver (there is another one call zidag but it's not work here)
2. As soos as you enter EDL mode, you must press "Flash" as quick as possible
i'm in a similar situation... i did "fastboot oem lock" and now i'm in a loop trying to boot the phone, after the 3time it enters edl (i see the red light).
My model is de G model (2017G) can i use miFlash just to restore the recovery and fastboot?
i had installed lineageOS, when connecting my phone it says that is the U model (2017U) but i think is only a label tag from the rom...
Thansks for the help!!
A 64 bit computer is not really necessary, however it is adviced.
I used a 32bit laptop running Win 10 to rescue mine.
Drivers seem to be a major problem, having the correct up to date drivers is a must.
Also try using Edl Tool and the Axon7 tool kit to access flashing.
Zadig drivers can help in some instances.
With the error you are receiving, have you tried another Edl package?
I was using an Edl package that would not finish flashing either, try a different package and make sure its correct for your phone.
I hope you get it sorted
The hello read package does occur when the phone is not really EDL mode anymore. You always have to restart the phone and boot manually into EDL mode with + - Power and you have to reboot everytime you did or if the hello error happens.
Look under device manager if it says Qualcomm instead of ZTE Device Handset. If that is the case you can build your own EDL cable.
"First I opened the cable and cut the Black and green open, then I connected all the black and green one together and pressed the power button until the red led was gone and 2 additional seconds.
After that I disconnected the modded cable and connected the Phone to the PC with the orginal cable and it showed up as Qualcomm HS-USB QDLoader 9008. "
You can install the qualcomm drivers under the MiFlash tab in the latest version.
i finally solve my issue following the guide: https://forum.xda-developers.com/axon-7/how-to/a2017-4th-category-brick-repair-manual-t3585898 there is also a resume on https://forum.xda-developers.com/axon-7/how-to/guide-dfu-unbrick-guide-disassembly-t3731152
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
crank_girl said:
I'm returning my 2017G as the internal gyro sensor is wonky and it's not playing well with my VR headset.
I was following a guide (I don't think it's important to state which) to return to stock. Seemed to go well until my phone started asking for a password (there wasn't one active). I put in lots of passwords thinking it would just eventually factory reset itself. Instead of resetting, it accepted a password and I then got the decryption unsuccessful screen. "The password you have entered is correct but unfortunately your data is corrupt". It gives me the option to reset my phone but nothing happens. It looks like it's going into EDL mode (black screen with red led). I can see the phone in dev manager and it lists as QUSB etc when put into EDL mode. My problem is that it isn't listed as an adb device so I cant't flash anything further.
I have removed and installed drivers using zadig. I've removed and reinstalled the QUSB drivers. I've run the minimal adb thingy. Bear in mind that I've been flashing recoveries and roms with no issue up until now. I can also access FTM.
Any words of wisdom gratefully received.
Click to expand...
Click to collapse
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
p.s. can you actually flash something with adb??
Lots of people seem to confuse adb with fastboot. Is that what you want to use?
Thanks both for responding. I think I've gotten myself a bit confused over what is supposed to be working at any given time.
I can get the phone into EDL mode and fastboot. Fastboot devices finds my phone. MiFlash doesn't find my phone despite having the QHSUSB driver installed.
What's the easiest way to return my phone to stock? I have MiFlash and Axon7toolkit installed.
Cheers!
Choose an username... said:
Why did you try to get ADB while you were in EDL though? You only get the EDL connection there.
Look, two things:
-When you get the password thing you just have to format data (NOT wipe, but FORMAT). just remember that for the future.
Click to expand...
Click to collapse
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
-Since you didn't say what happened with the driver, let's see that first. Connect it, get into EDL (you can enter by key combination or by FTM then "adb reboot edl"), and when you're in EDL find the driver. If it is the Zadig driver uninstall it and "delete driver software too". After that hold all 3 keys (power and vol+-) until device manager refreshes and the phone flashes the led. After that the qualcomm driver should install itself. If it is "Qualcomm HS-USB QDLoader 9008" use MiFlash or djkuz's EDL Tool to flash a stock system.
Click to expand...
Click to collapse
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
You have the wrong drivers.
crank_girl said:
It doesn't work. I only get the option to reset phone and if I press that the screen goes black with just a red led to indicate that it's not switched off. It hangs like that.
That's the other thing, my laptop doesn't communicate with the phone at all via adb.
These images might help - USBDeview showing the drivers in operation in various phone states.
First is FTM, then in fastboot, then in EDL, then when it's booted normally. Green denotes drivers that are functioning OK and pink is where it might be problematic. Can you spot any issues and have ideas on how I can put it right?
Cheers!
Click to expand...
Click to collapse
I tried to post yesterday and for some reason the XDA app didn't post the answer... Basically this:
-Forget ADB and that program that you're using to see the devices. EDL uses COM protocol, has nothing to do with adb at all.
-Go to Device manager and find where QUSB_BULK is. If it is in Unknown devices, either right click on it and try to install the driver automatically, or search for "Qualcomm HS-USB QDLoader 9008 drivers", download, install and try to install it on QUSB_BULK. If it is in an "USB devices" tab or on Ports "COM & LPT" simply right click, Uninstall device, Delete driver software for this device
I've done that several times over but miflash still isn't detecting it.
crank_girl said:
I've done that several times over but miflash still isn't detecting it.
Click to expand...
Click to collapse
all right. Try EDL Tool by djkuz. I don't know if the same packages work but just download another edl package
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
crank_girl said:
It's weird. Doesn't matter what mode the phone is in fastboot, edl, ftm, it's not detected by my laptop .
I'll try the tool you suggest.
Tbh I'm reaching the point where I'm tempted to return as is. Bootloader is locked, it just looks like a phone fault.
Click to expand...
Click to collapse
How come? The right driver literally appears on the last photo...
Choose an username... said:
How come? The right driver literally appears on the last photo...
Click to expand...
Click to collapse
I know, right? It's a mystery. Never had this happen before.
crank_girl said:
I know, right? It's a mystery. Never had this happen before.
Click to expand...
Click to collapse
If it doesn't work try MiFlash on another PC, it sometimes happens that it won't detect it by any means
no OS, no recovery, edl not working...
hey
i'm new here
so hello everyone
i write this post because i have no idea what can i do else....
i try every method i found on xda (without dissamble) and my axon 7 still have no os...
long story short
some time ago i flash lineage 14.1 using Axon7_EDL_Tool
everything was ok
but one day lineage updater tell me there is update to lineage os 15,1
but you have to use twrp
so i download update
put it to sd card
reboot to twrp
Wipe system,data and cache
everything like i read instruction
then i flash lineage 15.1 in twrp
but it stop - saying error 7
i did not uprade TWRP - maybe it is a problem....
now i have no os, no twrp
and axon stop on "your device will boot in 5 second"
bootloader unlocked
usb debbuging on
i have win10 64b, win7 32b, win7 64b
I installed drivers for axon 7,
i bought deep flash cable
nothing helps.....
what happens if you connect the charger to your phone while its off? not to pc, to wall charger
also, does the LED flashes once and then turns off while trying to access EDL? or does it stays on all the time? or maybe never lights up at all?
Always, if you update ROM to higher Android version, then you have to check TWRP version. 1st attempt - try to install TWRP.
I think error 7 means that you didn't flash the Oreo bootstack. If you can get into bootloader/fastboot mode then you can follow this to flash TWRP. Or give this a try, I haven't tried it myself though.
you need los15 bootstack lol.Go to los15 thread,download universal bootstack v2,flash in twrp,then flash rom (oreo rom)
Keep pressing power , volume + and volume - and this will force into EDL.
Then flash universal orea bootloader then recovery. Then u should be good to go
I can't flash anything...windows can't see my AXON7 - this is main problem...
I tried the tools you wrote but they can't connect my phone
I don't know what else can I do to communicate between phone and computer
Change the cable.
O tried 4 USB and 2 deep flash...
Pressing power , volume + and volume - will turn the led notification red right?
Then you connect the phone to the PC.
You have to check the device manager, what you see there?
Can you get into FTM?
Vol down and power button.
Try installing Zadig drivers and see if that helps
In the device manager in windows you need to see
Qualcomm HS-USB QDLoader 9008
If all drivers are setup correctly
Try installing twrp via fastboot.
Hope this helps
Nothhhing appears im device manager...
Still nothing..
what happened when you press both volume button and button together? for Oreo it will just show black screen or it will show FTM mode on the screen if you on older bootloader. Keep pressing the 3 button until it show black screen then plug in to your computer... make sure you windows firewall and security is all turn off.
Can you check on Windows' Device Manager if the Axon 7 is recognised as DFU, after you try to enter EDL mode? (Also, usually, the notification light is red and stays on).
Similar situation
Hi,
I'm in a similar situation. I'm guessing my recovery was corrupted. I even disassembled the unit to try to get it into EDL mode, which may be working but the device is just not recognized by my computer, though it does charge. My next step is to try replacing the usb connector, or just move on.
Good luck!
Ed
Hello,
I was in the same situation and this tuto saved my phone
https://forum.xda-developers.com/axon-7/how-to/guide-axon-7-universal-unbrick-t3814413
Hope this works for you !
So I wanted to flash evolution X, which flashed ok but would only boot into fastboot mode. I then went to flash stock 11 rom using the fastboot rom. It flashed ok but when it came to rebooting, the screen just went black. I cannot enter fastboot, recovery or EDL mode. Regardless of the method to get into EDL mode, the computer wont recognise the phone. Device manager doesnt show anything being plugged in and MSMdownload tool doesnt recognise it either. I have the drivers already installed so the computer should recognise it.
What i did one time was:
Start MSM Tool and press start.
Connected the phone with a third party cable and to a usb hub.
Held vol up, vol down and power button for like a minute or longer.
xtcislove said:
What i did one time was:
Start MSM Tool and press start.
Connected the phone with a third party cable and to a usb hub.
Held vol up, vol down and power button for like a minute or longer.
Click to expand...
Click to collapse
nope. didn't work. phone doesn't get recognised by the computer at all.
Roamed around a bit and solved the issue by following this.
Brick Saved!! OnePlus 8 Pro Oxygen OS 12 to Android 11 downgrade brick saved. Methods I used and pitfalls.
Background: OnePlus 8 Pro IN2020 Original OS version is OxygenOS 12 Android 12 How my phone turned into brick: Try flashboot unsupported TWRP and other third party recoveries. After a few tries, eventually causing my phone turning into a brick...
forum.xda-developers.com
You likely just haven't installed the proper drivers. You need those Qualcomm ones so your PC recognizes the phone. Also try different USB cables.