Related
Hi,
I know that there are already several threads where this is being discussed on this forum, just wanted to add this one so that people could share how they overcame it, As some let their battery die and then Vol down+Power into EDL, whereas some dismantle the phone and short the testing point, whereas some even got lucky with the Deep Flash Cable.. therefore it would be of benefit to all if all such solutions are shared under once single thread so that anyone suffering from it can look into one single list of options that he or she has!
As someone who is still figuring out how to escape this death trap, this would be great!
It's not a death trap for me ?? I can't even get it to that point. It's an amazing phone and I want to keep using it. I can't tell you how many different combinations I've tried in the last 24 hours and I have yet to get miflash to see my phone. All while adb and Qualcomm things are working exactly how they're supposed to. It's so frustrating that I can't even get my device into a state that needs recovering, especially with soooo many amazing ROMs for it!!
A2017U working on Verizon network with no problem.
Bone stock
Please help
@ CASEY_K Have you tried different USB ports or a different computer?
RUNNERX said:
@ CASEY_K Have you tried different USB ports or a different computer?
Click to expand...
Click to collapse
I have tried both ports on this laptop multiple times. That's my next guess. Only downfall is I only have this one and don't know many other people that have one.
I'm getting the error, "parameter length can't be less than zero"
Had to disassemble the phone and follow the 4th category brick guide for me. I tried everything else, but that's the one that actually worked.
A2017G
Can anyone share on how to get to the FTM mode from DFU ??? how did they achieve it!?
SBFarooq said:
Can anyone share on how to get to the FTM mode from DFU ??? how did they achieve it!?
Click to expand...
Click to collapse
Supposedly fiddle enough with the buttons until it works, for example: https://forum.xda-developers.com/ax...estigation-t3511191/post74092981#post74092981
Some drain the battery first.
My ZTE is put into FTM mode by holding volume + and plugging in a USB cable that is connected to a computer. On some phones FTM mode will have ADB enabled. From ADB the command "adb reboot edl" will put the phone into edl mode without a deep flash cable.
If the phone contains a Qualcomm chip and you have Qualcomm drivers installed EDL mode will cause the phone to register in the device manager as a com port labeled Qualcomm 9008. Miflash recognizes the Qualcomm 9008 mode.
Sent from my SM-G935V using Tapatalk
TysonBeall said:
My ZTE is put into FTM mode by holding volume + and plugging in a USB cable that is connected to a computer. On some phones FTM mode will have ADB enabled. From ADB the command "adb reboot edl" will put the phone into edl mode without a deep flash cable.
If the phone contains a Qualcomm chip and you have Qualcomm drivers installed EDL mode will cause the phone to register in the device manager as a com port labeled Qualcomm 9008. Miflash recognizes the Qualcomm 9008 mode.
Click to expand...
Click to collapse
Don't bump completely dead threads, please??
Also you would be right if this didn't pertain to DFU. FTM almost never works when your phone is DFU bricked
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Waancho said:
Last time i checked, edl mode was volume up and down and power button together. Then wait till light flashes three times and you're in edl mode.
Click to expand...
Click to collapse
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
ibphantom said:
I tried that, and I can hear it disconnect and reconnect again, but still can't get windows to see it in adb. Device manager shows it as Qualcomm HS-USB QDLoader 9008(COM6)
Click to expand...
Click to collapse
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Waancho said:
If I'm not mistaken, that in fact means you're in edl mode. Edl and adb are two different modes.
Click to expand...
Click to collapse
Okay, well even from there it's not showing up in XiaoMiFlash's device list
ibphantom said:
Okay, well even from there it's not showing up in XiaoMiFlash's device list
Click to expand...
Click to collapse
Did you try the edl tool AND different cables? I always test cables just to be sure.
Waancho said:
Did you try the edl tool AND different cables? I always test cables just to be sure.
Click to expand...
Click to collapse
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
ibphantom said:
I've tried 3 different cables. I'm stuck at the Axon7Toolkit option "#11 : RESTORE TO STOCK/RECOVER FROM HARDBRICK (EDL)"
I am able to select stock firmware, but then it tries to pass the flash off to XiaoMiFlash and that program cannot see my phone for some reason.
Click to expand...
Click to collapse
Did you try flashing a full edl image for your phone?
Waancho said:
Did you try flashing a full edl image for your phone?
Click to expand...
Click to collapse
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
ibphantom said:
I've been trying to, but XiaoMiFlash tool doesn't see my device in edl
Click to expand...
Click to collapse
Have you tried using the EDL Tool?
ibphantom said:
I was flashing a zip file to an SD for my raspberry pi using an app downloaded from the app store. Once I targeted the SD and hit flash, the status bar started going across the screen to show how much data has been written, and then the phone started acting really slow, froze and started playing the bootlogo for AEX-ROM. After that the screen went black. I tried plugging the phone into 3 different chargers but nothing would turn it on, not even the status light. I plugged the phone into my computer to see if I could fix it through ADB, but the phone is not showing. I get the sound from windows of the device being recognized. Does anyone know the special key combo to put the phone into EDL mode? Or the trick to get the phone to boot again?
Click to expand...
Click to collapse
Stupid question, did you take the SD card out?
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
Hey there guys, so as the title suggests, i'm having a bootloop problem on my m30s sm-307f, i can't access recovery mode, and i'm unable to start the flashing process because i can't even install the usb driver, i've tried several drivers, using several cables, on several systems (windows 7 / windows 10 / windows 11), and i always get that infamous yellow triangle on the SAMSUNG Mobile USB CDC Composite Device in the Universal Serial Bus Controllers section in the device manager, the phone was operating normally one day, and the next day when i try to power it on, i get this, i'm absolutely certain that i did nothing to the phone, not even an update, and it most definitely didn't fall to the ground, please respond, i have really important data there, and it would devastating to lose it, and thanks a lot.
Can you access Download Mode?
UniX1803 said:
Can you access Download Mode?
Click to expand...
Click to collapse
Yes i can.
Ok. Can Odin detect your phone?
UniX1803 said:
Ok. Can Odin detect your phone?
Click to expand...
Click to collapse
No, unfortunately it can't, which is to be expected since windows itself can't detect it.
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
UniX1803 said:
Is your USB Cable connected when you try to boot to Recovery Mode? when the screen goes black, press Vol+ & Power until Samsung Logo appears, Release Power, hold Vol+ until Recovery Mode appears.
Click to expand...
Click to collapse
I do know how to get to download mode, i did of course try, and although it does appear on the phone that it's working, the computer doesn't detect the latter as i explained, and as such, odin doesn't detect it as well.
I was talking about Recovery Mode.
UniX1803 said:
I was talking about Recovery Mode.
Click to expand...
Click to collapse
Sorry, i didn't notice that, i'm unable to access recovery mode either because the phone just keeps rebooting.
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
UniX1803 said:
I had the same problem but following the mentioned steps did worked for me. It's that short moment when the screen turns black, where you have to push that buttons. USB Cable needs to be plugged in!
If this solution is not working for you, try searching the web. I found more than one potential solution. Good luck.
Click to expand...
Click to collapse
Thanks a lot for the help, i really appreciate it, some people are saying that it's a motherboard problem, what do you think ?
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
UniX1803 said:
Could be, but i'm not sure. I would try to find a software solution, until you are sure it's not to get fixed on this way.
Click to expand...
Click to collapse
You're right, again, thanks a lot for your help.
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
treety said:
Try uninstalling the device in device manager and try those before plugging it in again.
Samsung Android USB Driver | Samsung Developers
You need the driver only if you are developing on Windows and want to connect a Samsung Android device to your development environment over USB.
developer.samsung.com
Click to expand...
Click to collapse
I've already tried them, they didn't work as intended unfortunately, thanks for the reply though.
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
stoag said:
Were you ever able to solve this? Is it a hardware issue? I think that may be the correct determination. I'm going to take this one apart and see if I find anything that would corroborate.
Click to expand...
Click to collapse
Unfortunately, i wasn't able to, but i think it's most likely hardware related.
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.