Database Users

Stuck at twrp loading screen, no other boot options is working.

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

Axon 7 EDL Mode Not Working/ can't boot to EDL

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.

Phone not recognized in Fastboot / Download

Three days ago, my phone went off by itself and I had a hard time starting again, it was just loading the bootanimation, I tried to reinstall the ROM, but it did not go into TWRP, although the message Recovery appears on the screen, I insisted and after several attempts, I got into the recovery, formatted everything and I installed the AICP ROM again, and I had to restart,my phone freezes in the LeEco bootloader, then again I insisted until the ROM finally started, but soon realized that it was taking too long to start (30 minutes waiting and nothing).
So I rebooted again, and from then on, I can not go into any mode anymore, trying to access the TWRP, the phone only stays on the Recovery screen until reboot after 2 minutes, when letting the phone try to start the ROM, it only stays on the LeEco screen and restart after 2 minutes, when entering Fastboot, it enters the screen in Fastboot mode, but is not recognized by the computer, not even as unknown device, the same for Download mode.
Is there anything I can try?

Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.

tsongming said:
Doesn't seem like a a fried motherboard. In my experience, If you fried the CPU, you would still be able to access Fastboot, if you fried the GPU part of the chip, or if the LCD has failed you would feel vibrations..
Do you thin it is possible that you accidentally put the phone into EDL mode? It can sometimes be hard to get out of, and it will give you similar issues.
To leave EDL press and hold volume down and power for 1 minute or longer.
Try this
Install the All in One tool and use it to update your android and fastboot drivers. Afterwards see if the computer recognises the phone port connection by going to Control Panel>System> Device Manager* ( Even though, you may not see the drive, you will maybe still see unknown device or te port)
Maybe a Brick?
If it does not see the phone or show a unknown USB device with port 9008
Try placing the phone into EDL mode by pressing and holding the Vol Up (+) and Vol Down (-) together while simultaneously connecting the phone by USB cable to the computer. Do you see the port or phone now? If you see port 9008 you possibly are bricked, follow the steps on my unbricking thread., if you can not get back to TWRP, or fastboot,and the phone keeps a charge. Then I would think that you are definitely bricked.
Other possible issues
The issue could be the battery. Have you tried using other USB C Cables? If you can use a different usb cable let it charge for a couple of hours then see if you can get into TWRP again . If you can enter fastboot mode try reflashing TWRP, you can use the All in One tool for this.
Click to expand...
Click to collapse
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.

kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode.sl Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Well that sucks, if you feel like sending to the phone to China for repair, you can find several shops that are offering to repair any damaged Leeco for $10 and an average cost of $30 for resoldering. On the TaoBao website, use Chrome for translation. Some of their ads mention overseas repair
If it's memory it would be an easy fix for them.
If you don't want to fix it, I highly recommend the Mi8 if it's within your budget, its a perfect phone and you can find them for close to $300. My brother has a Redmi note 6 Pro which is also really nice. He paid $190.
Good Luck.
Sent from my Xiaomi MI 8 using XDA Labs

kakobr said:
Thanks for answering. I've tried everything.
But I can not see the smartphone when connected. USB drivers are properly installed (I used to recover other LeEco x651, x526 and x520 devices)
I left it restarting for more than hours holding the power button and volume down, no results.
The device does not appear in the Windows device manager in any way, not even as Unknown or 9008 port.
I tried several usb cables.
There is no communication with TWRP or ROM installed and neither with the computer, even though I enter into fastboot / 9008 mode. Only LeEco / recovery logo and Fastboot screen.
I think my main memory is damaged or something.
Click to expand...
Click to collapse
Check out this possible do it yourself fix : https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71

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
What my error looks like:​
Not able to boot into system
Showing "the current image(boot/recovery) have been destroyed"
Can access fastboot and detect by system
​Method:​
Follow the steps in How to UNBRICK OnePlus 8 or 8 Pro! by Max Lee (Thank you my man, Max, for this video)
​Pitfalls in 2022 (IMPORTANT before UNBRICK!):​A USB 2.0 and Third-party USB cable are highly recommended​I was unable to boot into Quadcomm EDL mode while using the stock cable and USB 3.0 connector. Pressing the correct Volumn Up & Volumn Down and Power Button will boot the phone to fastboot in no time.
I successfully got into the EDL mode and finished flashing the phone using my iPad Pro Type-C charging cable which is an USB 2.0 one.
Use a newer version of the Qualcomm driver if you find the device not correctly detected​Use Qualcomm HS-USB QDLoader 9008 driver.
A new Quadcomm driver will help you flash your device correctly the first time!!!
Windows 11 won't let you install unsigned driver by default, but there's a way round​
Press Shift key while click Reboot in start menu to enter Advanced Options
Click Trouble shoot in Advanced Options
Click Advanced options, click Startup Settings then click Restart
After restart press 7 when required
If your computer won't restart, just unplug your phone temporarily
after this your device will detect by your computer correctly.
Pressing buttons requires special timing and preconditions and a few more tries​
To fully power off your phone, press Volume up and Power button for 10 seconds. Release immediately after the screen turns black.
Your phone is in the state of powered off even your screen displaying error message or charging animation, just make sure it's not in fastboot, recovery or booting animations.
Connect your phone to your computer before press Volume up and down and Power Button all at the same time to enter EDL mode.
Prepare yourself with Device Manager and MSM tool open and configured correctly before your phone enter EDL mode. There's a about 10 second window for you to start flashing.
Fail amid your MSM flash process:​Don't panic if you see error message saying you didn't finish flashing​
You can flash it anytime just make sure checking all the things above and enter EDL mode
Check these things：​
Check your Windows can install the unsigned driver correctly
Check Device Manger in Control Panel if your device is correctly detected as a COM device as Qualcomm HS-USB QDLoader 9008 or something like this
Use administrator privilege to open the MSM software
Check your cable connection is stable or not.
Finally, thanks Dr.E (Max Lee) for your help. Without your video instructions, I won't revive my phone. It spares my pain to ask my dad for money for a new phone I don't actually need.
Hope everyone could find some helpful information in this post and flash your phone like a champ.

A even better way to enter EDL mode is power off and unplug your device, and after hold volume up and down at the same time, plug in the USB 2.0 cable to the computer. It works every time!!

i cant join rdl mode always restarting fastboot mode

HELP PLZ, phone hard bricked cannot enter EDL OR FASTBOOT MODE

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.