Database Users

Unbrick RN3 from HS USB 900E with EDL cable %100 working methode

If your RN3 Pro brick ,no download, no recovery mode ...
only 900E mode ...
http://i.hizliresim.com/NkW24O.jpg
Press power button 10 sec. while EDL button pressing.
Then release power button.
After then 8 sec. release EDL button.
Your RN3 turn from 900E to 9008
http://unbrick-snapdragon.blogspot.com.tr/2016/07/mi-snapdragon-telefonlar-icin-9008.html
Now you can flash with miflash fastboot rom.
http://unbrick-snapdragon.blogspot.com.tr/2016/05/snapdragon-islemcili-xiaomi.html
Making home made EDL cable ;
http://i.hizliresim.com/Y4JEl6.jpg
http://i.hizliresim.com/aX0NDz.jpg
https://www.youtube.com/watch?v=DJZ6Ka7mrIA
thanx to @manaswb

interesting to know, thanks
it might save people from having to use the test points which requires disassembly of the phone

Saludos amigo, me puedes ayudar, tengo el problema en este momento, el detalle es que al parecer no tengo carga en la batería, ¿Como cargo la batería de mi teléfono? o ¿como se que se esta cargando? si no enciende para nada.
En su momento (hace 1 mes) me reconocio siempre en 900E Diagnostic, pero ahora no ya que no me reconoce para nada (seguro porque no tiene batería)
"Ya tengo el cable hecho"
Me pueden ayudar @manaswb
Gracias amigos

same as MI5 edl flash cable

you saved my ass! after an unofficial bootloader unlock on kate, my phone went black. Couldn't do anything. Only 900E mode in windows device manager... it worked!

GNVM said:
same as MI5 edl flash cable
Click to expand...
Click to collapse
Hi GNVM,
Where did you got that information?
I need it since my friend is want to flash from china stable to global stable but still locked bootloader and now it can't be getting into EDL mode.
Could you please advise about it?
Please advise.
Thank you.
Regards,
Karkand

karkand said:
Hi GNVM,
Where did you got that information?
I need it since my friend is want to flash from china stable to global stable but still locked bootloader and now it can't be getting into EDL mode.
Could you please advise about it?
Please advise.
Thank you.
Regards,
Karkand
Click to expand...
Click to collapse
Follow the below Links.It will help you to make the flash cable.Good Luck.
http://en.miui.com/forum.php?mod=viewthread&tid=310325&highlight=mi5+flash+cable
http://en.miui.com/forum.php?mod=viewthread&tid=324300&highlight=mi5+flash+cable

https://www.youtube.com/watch?v=DJZ6Ka7mrIA

This worked to get an Orbic Wonder back into EDL model from 900E however I cannot get QPST nor UNI Antroid Tools or other flashers to work with it.

micro77 said:
If your RN3 Pro brick ,no download, no recovery mode ...
only 900E mode ...
http://i.hizliresim.com/NkW24O.jpg
Press power button 10 sec. while EDL button pressing.
Then release power button.
After then 8 sec. release EDL button.
Your RN3 turn from 900E to 9008
http://unbrick-snapdragon.blogspot.com.tr/2016/07/mi-snapdragon-telefonlar-icin-9008.html
Now you can flash with miflash fastboot rom.
http://unbrick-snapdragon.blogspot.com.tr/2016/05/snapdragon-islemcili-xiaomi.html
Making home made EDL cable ;
http://i.hizliresim.com/Y4JEl6.jpg
Click to expand...
Click to collapse
cableon picture is micro USB male and USB A female ??
thanx K.

krabat said:
cableon picture is micro USB male and USB A female ??
thanx K.
Click to expand...
Click to collapse
Because its posible connect microUSB cable, microC too etc.

BRICK QUSB_BULK device manager

Hello everyone was rotting when installing all successful and starting the device does not advance from the screen of the zte logo can be even hours with the logo until the battery is dead i have testered all the combinations of possible buttons ... The axon tools does not detect adb or fastboot mode and i can also reach it edl mode.
The only one that i get is then once when i have to uninstallthe driver to get the state in the device manager of windows qusb_bulk like universal usb. I do not know what to do if you can recover the phone please some link or guide to this problem
thanks

VIFTOKSKY said:
Hello everyone was rotting when installing all successful and starting the device does not advance from the screen of the zte logo can be even hours with the logo until the battery is dead i have testered all the combinations of possible buttons ... The axon tools does not detect adb or fastboot mode and i can also reach it edl mode.
The only one that i get is then once when i have to uninstallthe driver to get the state in the device manager of windows qusb_bulk like universal usb. I do not know what to do if you can recover the phone please some link or guide to this problem
thanks
Click to expand...
Click to collapse
You're not letting lots of things clear.
When you got into EDL, was the driver
-Qualcomm HS-USB QDLoader 9008
or
-ZTE something something DFU interface?
If you uninstall the Qualcomm HS-USB driver you won't be able to use MiFlash, which is the only thing that will help you at this point.
If you have the DFU thing, you can try letting the battery discharge completely and trying volume down + power many times, maybe while charging... Try some things, and if you get into FTM mode, you might be saved. If not you'll have to take apart your phone and follow the 4th category brick repair manual.
What's the model of your phone? (look in the back)

Choose an username... said:
You're not letting lots of things clear.
When you got into EDL, was the driver
-Qualcomm HS-USB QDLoader 9008
or
-ZTE something something DFU interface?
If you uninstall the Qualcomm HS-USB driver you won't be able to use MiFlash, which is the only thing that will help you at this point.
If you have the DFU thing, you can try letting the battery discharge completely and trying volume down + power many times, maybe while charging... Try some things, and if you get into FTM mode, you might be saved. If not you'll have to take apart your phone and follow the 4th category brick repair manual.
What's the model of your phone? (look in the back)
Click to expand...
Click to collapse
I'm going to start with the start
with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys volumen+/- + power at a time and just after that combo, it is left the black cell and appears in the device manager of windows the images that I attached, now has passed from qusb_bulk to qualcom 900 because i uninstall the drivers and then manually install the Drivers and chose that particular from the list of drivers
now
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I can not enter the edl mode as the attached image because when I press the volume- + power combination the device manager of windows does not detect the mobile phone.
Only detects the phone the device manager windows when I press the combination of all the buttons and then it is the current situation that I have although I put port 10 the adb does not detect the phone
Axon tool kits in this state also does not detect it ,and my flash is left empty list does not appear the phone
mi model of phone is ztea2017 (version china)
That is my current situation. so you recommend to me using the 4 category to repair a brick?
Or recommend me other steps

VIFTOKSKY said:
I'm going to start with the start
with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys volumen+/- + power at a time and just after that combo, it is left the black cell and appears in the device manager of windows the images that I attached, now has passed from qusb_bulk to qualcom 900 because i uninstall the drivers and then manually install the Drivers and chose that particular from the list of drivers
now
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I'm going to start with the start with the command axon7root.exe -p com3 -b -r (before the error was port 3 now appears as 10) but restarting the mobile stayed in the permanent zte logo I can only leave the Logo pressing the combo of the three keys at a time and just after that combo, it is left the black cell appears in the device manager the images that I attached has passed from qusb_bulk to qualcom 900 because 1disntale the drivers and then manually install the Drivers and chose that particular from the list of drivers
I can not enter the edl mode as the attached image because when I press the volume- + power combination the device manager of windows does not detect the mobile phone.
Only detects the phone the device manager windows when I press the combination of all the buttons and then it is the current situation that I have although I put port 10 the adb does not detect the phone
Axon tool kits in this state also does not detect it ,and my flash is left empty list does not appear the phone
mi model of phone is ztea2017 (version china)
That is my current situation. so you recommend to me using the 4 category to repair a brick?
Or recommend me other steps
Click to expand...
Click to collapse
Para hacertela mas facil: Necesitas usar la guia '4th category brick repair manual' (googleala, esta en XDA) pero empezando desde la parte que entran en modo EDL. Necesitas tener los drivers de Qualcomm para eso, asi que no los desinstales.

Choose an username... said:
Para hacertela mas facil: Necesitas usar la guia '4th category brick repair manual' (googleala, esta en XDA) pero empezando desde la parte que entran en modo EDL. Necesitas tener los drivers de Qualcomm para eso, asi que no los desinstales.
Click to expand...
Click to collapse
muchas gracias, si ya tenia esa pagina en favoritos, pero la tenia en plan ultimo recurso, no quería abrir si no era estrictamente necesario. tampoco quería hablar en español por si no se podia o alguien mas esta en este punto de error y respecto a mi ingles le tengo un poco oxidado y todo lo que escribo lo compruebo con el google translator por eso se copio dos veces.
una duda que me dejas con tu ultimo comentario lo voy a poner en ingles también para ayudar a gente que le pase igual.por eso lo leeras dos veces. cuando te refieres que empiece desde la parte de entrar en modo edl no te entiendo, porque segun el tutorial hay que abrir conectar el cable.... IN ENGLISH DOWN
1. Connect original USB Type-C cable to the phone.
2. Circtuit Test-point on the housing (there is sim-cards slot body nearby).
3. Connect USB cable to PC USB-port (preferably USB 2.0 version).
4. You will hear the USB device connection sound from PC (but you will not notice any vibration of the phone or red diode indicator blinking).
estos puntos ninguno pone mode edl no ? os me estoy saltando algun paso que no veo.
ENGLISH
A doubt that you leave me with your last comment I 'm going to put in English also to help people that happens to him equal. When you mean start from the part of entering edl mode I don't understand you, because according to the tutorial you have to open connect the cable not entering edl mode i'm forgetting some step ??

On your second pic, that is already in edl mode.
Try to enter that mode again by pressing all the buttons and make to the computer detect it as 9008. Once it is already in 9008, here's what you do:
1. Open the folder where you have the axon7root.exe.
2. Delete/rename or move the files "boot.img and recovery.img".
3. Rename the files "stock_boot_backup.img" to "boot.img". Do the same for recovery.img
4. Issue this command: "axon7root.exe -p COM10 -b -r"
Be sure it's COM10 in device manager. Else, try puting it in another usb slot and enter what port it is there.
That will restore your original boot and recovery.
If you still can't recover from that, install Teamviewer on your PC and let me access it remotely. That is if we can find a time convenient for us since we're not in the same timezone.
---------- Post added at 01:12 AM ---------- Previous post was at 12:30 AM ----------
Try also this method to restore.
https://forum.xda-developers.com/showpost.php?p=73449127&postcount=1

otaconremo said:
On your second pic, that is already in edl mode.
Try to enter that mode again by pressing all the buttons and make to the computer detect it as 9008. Once it is already in 9008, here's what you do:
1. Open the folder where you have the axon7root.exe.
2. Delete/rename or move the files "boot.img and recovery.img".
3. Rename the files "stock_boot_backup.img" to "boot.img". Do the same for recovery.img
4. Issue this command: "axon7root.exe -p COM10 -b -r"
Be sure it's COM10 in device manager. Else, try puting it in another usb slot and enter what port it is there.
That will restore your original boot and recovery.
If you still can't recover from that, install Teamviewer on your PC and let me access it remotely. That is if we can find a time convenient for us since we're not in the same timezone.
---------- Post added at 01:12 AM ---------- Previous post was at 12:30 AM ----------
Try also this method to restore.
https://forum.xda-developers.com/showpost.php?p=73449127&postcount=1
Click to expand...
Click to collapse
yes in the second pictures looks like alreday
If but the same explain me wrong in the second image seems to be in edl mode but does not detect it (install the drivers manually from the disk choosing that option ... ponia qusb_bulk and I manually update the driver series to that particular Prque knew it was the right one so now I dial that when I connect it stays on black screen after pressing the 3 buttons at a time and quickly connect the usb cable (if I do not this does not appear so when I enter the command screen Of amb and put the third image does not detect devices and does not recognize it even putting port 10 attached screenshot of the test ...
I suppose that only left to make option category brick 4

VIFTOKSKY said:
yes in the second pictures looks like alreday
If but the same explain me wrong in the second image seems to be in edl mode but does not detect it (install the drivers manually from the disk choosing that option ... ponia qusb_bulk and I manually update the driver series to that particular Prque knew it was the right one so now I dial that when I connect it stays on black screen after pressing the 3 buttons at a time and quickly connect the usb cable (if I do not this does not appear so when I enter the command screen Of amb and put the third image does not detect devices and does not recognize it even putting port 10 attached screenshot of the test ...
I suppose that only left to make option category brick 4
Click to expand...
Click to collapse
En la guia el celular esta brickeado de una manera que no se puede entrar al modo EDL. Se supone que podes entrar al modo si mantenes apretadas las dos teclas de volumen, y metes el cable USB-C al celular (tiene que estar conectado a la computadora). Desde ahi tenes EDL si no tiene un DFU brick (tendrias que desarmarlo). En la guia haces corto en un pad de cobre para entrar en EDL, pero podes meterte al EDL de manera que te salga el driver de Qualcomm en la PC y seguir con la guia despues de lo que copiaste. Lo de despues debe ser seleccionar la carpeta y flashear con MiFlash me imagino

[SOLVED] Need help with fixing unknown model in LGUP

I flashed the Fulmics ROM on my G6 and could not go back to stock using LGUP. Under Model and Port it shows "Unknown" and "Com 5, Fulmics" preventing me from proceeding.
I, however, managed to flash the stock rom from a zip provided in one of the threads. Still when I connect the phone to computer, LGUP says "Unknown" and "Com 5, Fulmics".
How can I fix this so that I can use LGUP again? (I also tried the Flashtool with no success)
Thanks

Go to
Code:
C:\Program Files (x86)\LG Electronics\LGUP\model\common
paste this file there https://drive.google.com/open?id=0B8K3M8fXJmgzX1hMNTBkZ3p2M1E

Did that before. Didn't make a difference.

backslashV said:
Did that before. Didn't make a difference.
Click to expand...
Click to collapse
Did you install the drivers properly and have you tried using a different USB?

Mavelos said:
Did you install the drivers properly and have you tried using a different USB?
Click to expand...
Click to collapse
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.

backslashV said:
Yes. I even tried another computer. It appears that something about this Fulmics rom is hard coded into the phone. The developer of the rom isn't responding so I don't know what else to do.
Click to expand...
Click to collapse
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.

Mavelos said:
Well, I use Fulmics also and i can say nothing is hardcoded. When you connect your G6, check the device manager on your PC to be sure your phone is detected.
Click to expand...
Click to collapse
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?

backslashV said:
It is detected. I even tried changing the com port but nothing happened. So when you connect your phone to pc in download mode LGUP recognizes it?
Click to expand...
Click to collapse
yes it does. Have you used LGUP before?

Yes I have. I used it to go back to stock from lineage os.

Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508

backslashV said:
Good news. I found this guide and it did the trick:
https://forum.xda-developers.com/showthread.php?t=3565508
Click to expand...
Click to collapse
Hi, how do you solve this issue?
i face same problem.
i even cannot tun off the G6 and cannot enter download mode
when i connect my G6 to PC via uppercut, it says unkonown model and i cannot go on the process.
in the link you put above. we have to enter download mode. how do you do that?
thanks

Just hold volume down and power button at same time to power off.
Sent from my LG-H870 using Tapatalk

i have a same problem with my LG Aristo 2
necesito el dll para flashear Lg Aristo 2 (LM-X210MA)

@ade_k012 I have exactly the same problem you just described. Were you able to resolve?

Yes i have solved it and i can update my g6 to the firmware i want. But sorry, i forgot the steps. It was quite long time ago..

Hola yo lo resolvi usando este tutorial
en el ultimo paso donde tienen que crear el common ddl, no lo hagan, solo descarguen el archivo ddl que proporcionan al principio de este post y lo pegan en la ruta especificada. Lo probe en mi lg h873 y funciono perfecto pude flashear y desbriquear mi telefono que se quedaba en el logo de lg

My MI A1 hard bricked..any solutions?

Recently my Mi A1 was completely bricked trying to restore stock rom from a custom 8.1,now doesn't power on (screen stay black),doesn't enter recovery or fastboot with buttons combination. Only vibrate. The phone can connect with pc only with pin out in edl mode (but no led blinking). The phone appear completely dead,instead of vibration. Anyone can help me or have a solution?

cdtech said:
Recently my Mi A1 was completely bricked trying to restore stock rom from a custom 8.1,now doesn't power on (screen stay black),doesn't enter recovery or fastboot with buttons combination. Only vibrate. The phone can connect with pc only with pin out in edl mode (but no led blinking). The phone appear completely dead,instead of vibration. Anyone can help me or have a solution?
Click to expand...
Click to collapse
try with MI Flash
Sent from my Mi A1 using Tapatalk

With Mi Flash always error.

cdtech said:
Recently my Mi A1 was completely bricked trying to restore stock rom from a custom 8.1,now doesn't power on (screen stay black),doesn't enter recovery or fastboot with buttons combination. Only vibrate. The phone can connect with pc only with pin out in edl mode (but no led blinking). The phone appear completely dead,instead of vibration. Anyone can help me or have a solution?
Click to expand...
Click to collapse
Only one option go to Xiaomi service centre
If your a1 is in warranty

IjazCI said:
Use this thread
https://forum.xda-developers.com/showpost.php?p=75750138&postcount=5
Same thing happened to me.
Click to expand...
Click to collapse
In device manager the device is recognized,after pinout edl mode, as Qualcomm HS-USB QDLoader 9008 (COM20).
When I trying to flash the stock rom on MiFlash appear an error like this ( Object reference not set to an instance of an object).
What*s wrong? Please help me.

Sahil132 said:
Only one option go to Xiaomi service centre
If your a1 is in warranty
Click to expand...
Click to collapse
My Mi A1 is in warranty,but I*m in Italy and here Xiaomi haven*t any service centre,because not officially in my country.
I got the phone on an online store,but I think that my warranty void because of pinout method that I tried.

cdtech said:
My Mi A1 is in warranty,but I*m in Italy and here Xiaomi haven*t any service centre,because not officially in my country.
I got the phone on an online store,but I think that my warranty void because of pinout method that I tried.
Click to expand...
Click to collapse
Then take it to any repair centre

IjazCI said:
Hi, did you changed the driver as shown in the video. After changing the driver to Qloader ( don't remember exactly). Mi flash tool give an error ( sahara something). And it took awhile to get fastboot mode. Like i tried several times and finally device booted to fastboot mode.
You need to try the key combination several times
Click to expand...
Click to collapse
any solutions? same Issue, I found 1 rom that was flashable, got fastboot and twrp, but cant get OS working says This system has been destroyed, cant take to service center

Lertu said:
any solutions? same Issue, I found 1 rom that was flashable, got fastboot and twrp, but cant get OS working says This system has been destroyed, cant take to service center
Click to expand...
Click to collapse
Im sorry, which rom was the one that was flashable?

boshell said:
Im sorry, which rom was the one that was flashable?
Click to expand...
Click to collapse
The first one 7.8.23
Fastboot works, so I can get twrp too,
but normal system boot says system is destoyed, tried installing lineageos, still says system destroyed

Do step by step
Before you do anything Install Qualcomm Diagnostic Driver
1. Connect your data cable in pc without connect your phone
2. Open Mi Flash tool
3. Then connect your phone by pressing volume down + power button
4. Try flashing fastboot rom

Meaning that fastboot is up, rite?
Miflash recognises it, yet unsuccessfully flash, rite?
Twrp booted ok?
Failed to install ROM, if so you better check twrp version and OP of the ROM.

Un millón de gracias!!!!!!!! :'d
Suraj Dutta said:
Do step by step
Before you do anything Install Qualcomm Diagnostic Driver
1. Connect your data cable in pc without connect your phone
2. Open Mi Flash tool
3. Then connect your phone by pressing volume down + power button
4. Try flashing fastboot rom
Click to expand...
Click to collapse
MUCHÍSIMAS GRACIAS POR TU APORTACIÓN! de verdad que ya estaba desesperada y llorando, ya que mi teléfono sufrió un Hard Brick podríamos decir (iniciaba literal un milésima de segundo y se apagaba (no entraba en bucle)) el usb reconocía que un dispositivo había sido conectado, sin embargo no figuraba dentro del equipo, ni tan quiera dentro del administrador de dispositivos (por lo que no había forma de poder acceder a él).

Le Pro 3 X720 Stuck in bootloop

Hello ,
Yesterday my phone was at 5% so I wanted tot charge it and it did but only not with the original Leeco charger and cable but with a normal charger micro usb with a mico usb to USB C adapter and it was showing that it was charging . But when I came back 10 minutes or so my phone was stuck in a bootloop and I never had a problem with the phone and I was running a LineageOS 15.1 rom.
My Le Pro 3 X720 is stuck in a loop and I can only get to Fastboot mode.
When i try to go to recovery mode (TWRP) it shows Recovery but after a few seconds it is trying to boot but then it restarts again.
What i tried is to flash a new version of TWRP but after that it is still in a loop and not going to twrp.
I know of the QFIL MODE but I don't want to lose my data.
Can someone please help me ?
Thanks in advance.

thebestgames said:
Hello ,
Yesterday my phone was at 5% so I wanted tot charge it and it did but only not with the original Leeco charger and cable but with a normal charger micro usb with a mico usb to USB C adapter and it was showing that it was charging . But when I came back 10 minutes or so my phone was stuck in a bootloop and I never had a problem with the phone and I was running a LineageOS 15.1 rom.
My Le Pro 3 X720 is stuck in a loop and I can only get to Fastboot mode.
When i try to go to recovery mode (TWRP) it shows Recovery but after a few seconds it is trying to boot but then it restarts again.
What i tried is to flash a new version of TWRP but after that it is still in a loop and not going to twrp.
I know of the QFIL MODE but I don't want to lose my data.
Can someone please help me ?
Thanks in advance.
Click to expand...
Click to collapse
Since you changed TWRP
I hate to be the bearer of bad news. But it sounds like your phone was short circuited and something is fried most likely the motherboard. I would forget the data, its gone.
But I would absolutely try QFIL, just in case its a very unusual corruption issue. Sorry.
If it was the battery, the usb card, or just a brick ; your symptoms would be very different.
I has a similar issue last month, when the chip is fried you can still use qfil, see the phone in adb, flash roms etc. But never be able to access Recovery or the system, However, you can access Fastboot.

Hi tsongming,
Thanks for your answer but I changed the TWRP after it was in a loop I tought then it might go to TWRP but that was not the case.
And I am not hoping that it is short circuited but if this is the only realistic option what happend then I am going to try the qfil methode .

Bootloop
Hi tsongming ,
I have tried al QFIL options but it did not fix the problem.
Do you know something else to try ?
tsongming said:
Since you changed TWRP
I hate to be the bearer of bad news. But it sounds like your phone was short circuited and something is fried most likely the motherboard. I would forget the data, its gone.
But I would absolutely try QFIL, just in case its a very unusual corruption issue. Sorry.
If it was the battery, the usb card, or just a brick ; your symptoms would be very different.
I has a similar issue last month, when the chip is fried you can still use qfil, see the phone in adb, flash roms etc. But never be able to access Recovery or the system, However, you can access Fastboot.
Click to expand...
Click to collapse

thebestgames said:
Hi tsongming ,
I have tried al QFIL options but it did not fix the problem.
Do you know something else to try ?
Click to expand...
Click to collapse
Try QPST
https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2

Hello tsongming,
Where can I find the Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl" and Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx files ?
tsongming said:
Try QPST
https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2
Click to expand...
Click to collapse

Bootloop
I found the files they were in the in the extracted le_zl1_qfil_ufs_fix.zip .
tsongming said:
Hello tsongming,
Where can I find the Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl" and Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx files ?
Click to expand...
Click to collapse

But QPST didn't work either the phone is still in bootloop.
But thanks for your help

thebestgames said:
But QPST didn't work either the phone is still in bootloop.
But thanks for your help
Click to expand...
Click to collapse
Right everything you need is within the qfil. Although I gave mentioned it already its very important that you have all of the Windows protections disabled. Windows 10 has so much potential, but is severely crippled by its monitoring and assistive programs. If you are using programs such as Qfil, Windows security will delete some of the files and it makes Qfil unsuccessful. So again, make sure that every aspect is disabled.
When you open Flash 1.9 or 2.0 or QPST make sure that they are opened as an Administrator ( Right click)
If QPST and Flash 2.0 are not working try using fastboot.bat. This can be loaded while in EDL mode. You need 5.8.26s which comes with the fastboot.bat file.
All you need to do is place the stock Rom on your desktop, unzip the rom and double click fastboot.bat. ( The file name is either fastboot.bat, flash-all.bat or something similar. I don't remember the exact name) But there will only be one file with the option of flashing all so choose it.
The .bat file It will automatically flash all of the boot images to the phone. Afterwards your device will be fully restored to stock.
Here is the file: https://androidfilehost.com/?fid=673956719939836266

Isn't it possible to make this under Linux? It would be easier while windows has so many Antivir and defender tools. Also the USB driver are creapy under windows. I have often problems to see Samsung and leeco phones under windows. Via Linux they appear without a problem.

Fastboot
QPST , Flash 2.0 and fastboot flash where all successful but the phone is still in bootloop so I think it is a hardware problem.
tsongming said:
Right everything you need is within the qfil. Although I gave mentioned it already its very important that you have all of the Windows protections disabled. Windows 10 has so much potential, but is severely crippled by its monitoring and assistive programs. If you are using programs such as Qfil, Windows security will delete some of the files and it makes Qfil unsuccessful. So again, make sure that every aspect is disabled.
When you open Flash 1.9 or 2.0 or QPST make sure that they are opened as an Administrator ( Right click)
If QPST and Flash 2.0 are not working try using fastboot.bat. This can be loaded while in EDL mode. You need 5.8.26s which comes with the fastboot.bat file.
All you need to do is place the stock Rom on your desktop, unzip the rom and double click fastboot.bat. ( The file name is either fastboot.bat, flash-all.bat or something similar. I don't remember the exact name) But there will only be one file with the option of flashing all so choose it.
The .bat file It will automatically flash all of the boot images to the phone. Afterwards your device will be fully restored to stock.
Here is the file: https://androidfilehost.com/?fid=673956719939836266
Click to expand...
Click to collapse

one of le pro 3 have simillar problem on me its only when cable plugged in device powering on(after 20-25mln) and stuck on logo then goes black..Device can go to fastboot but pc not seeing device ( maybe usb type-c board broken) also device is not going to edl mode( tryed many ways all failed) maybe is there any way to switch edl mode via hardware? device already opened condition. vol+and- with cable without cable didnt worked..

My phone is in the same situation qfil, fastboot, anything has work

its like some write protection on the device if not something died inside...flashing successfull fastboot rom install success but still in bootloop...

eltdesign said:
its like some write protection on the device if not something died inside...flashing successfull fastboot rom install success but still in bootloop...
Click to expand...
Click to collapse
Checkout this possible solution: https://forum.xda-developers.com/showpost.php?p=79302729&postcount=71

Hi,
I have same problem, my phone x720 in bootloop when I try to power on or try to go in recovery mode, I read many tread with different solutions that I tried, but nothing, I can't resolve.
I made with fastboot, with this result
PS C:\Users\Pippo\Downloads\platform-tools> fastboot oem unlock-go
...
OKAY [ 0.013s]
finished. total time: 0.015s
PS C:\Users\Pippo\Downloads\platform-tools> fastboot oem device-info
...
(bootloader) Device product name: [le_zl1_whole_netcom]
(bootloader) Device tampered: false
(bootloader) Device unlocked: true
(bootloader) Device critical unlocked: true
(bootloader) Charger screen enabled: false
(bootloader) Serial console enabled: false
(bootloader) Serial hw output enabled: false
(bootloader) Display panel:
OKAY [ 0.087s]
finished. total time: 0.089s
PS C:\Users\Pippo\Downloads\platform-tools> fastboot flash recovery recovery_twrp.img
target reported max download size of 536870912 bytes
sending 'recovery' (47052 KB)...
OKAY [ 1.025s]
writing 'recovery'...
OKAY [ 0.335s]
finished. total time: 1.365s
PS C:\Users\Pippo\Downloads\platform-tools>
Click to expand...
Click to collapse
And with FlashOne I had this
Writing log to 'C:\Users\Pippo\AppData\Roaming\Qualcomm\QFIL\port_trace.txt', might take a minute
Log is 'C:\Users\Pippo\AppData\Roaming\Qualcomm\QFIL\port_trace.txt'
Download Succeed
Finish Download
Click to expand...
Click to collapse
But nothing, I'm in the same situation, can someone help me?

michiamomork said:
Hi,
I have same problem, my phone x720 in bootloop when I try to power on or try to go in recovery mode, I read many tread with different solutions that I tried, but nothing, I can't resolve.
I made with fastboot, with this result
And with FlashOne I had this
But nothing, I'm in the same situation, can someone help me?
Click to expand...
Click to collapse
Yes same problem everytime phone resart and resart, i follow all step, working at 1 time . Can open and i update 1537515040_LE_ZL1_LEX720-CN-FN-WAXCNFN6003009091S-6.0.03 . When i install apk phone turn off and back to problem. I try unbrick still same. Maybe hardware problem

Sounds like your battery is faulty. Had the same bootloop issue on my X727 and a new battery fixed the problem. Got the battery here www.aliexpress.com/item/32892123537.html and received an original LeEco battery with date code in 2016. Battery works fine though, phone charges well and no more bootloops.

Hola, tuve el mismo problemas un bucle infinito de reinicios y ningun foro que tenga una solución, sin embargo al leer que podría ser un problema de hardware, lo abri y encontre un conector ligeramente desmontado,(conector de banda anaranjada, superior derecho, si vez de frente la batería a la par de un código qwerty) lo conecte y listo volvio mi LeEco pro. Lo comparto por si a alguien mas le puede servir, de hecho ya había descartado mi telefono y compre otro, pero siempre queda la idea de buscar una solución.