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.
Related
Rebuilding and updating
https://software.intel.com/en-us/android/articles/intel-usb-driver-for-android-devices
https://drive.google.com/open?id=0B3vLobe8_2u7THFQRGJTNDI5Umc
https://drive.google.com/open?id=0B3vLobe8_2u7VVhMTkNDUGUwTVU
http://23pin.logdown.com/posts/240975-zenfone-rescue-guide
https://4pda.ru/forum/index.php?showtopic=584672&st=460#entry33842670
https://firmware27.blogspot.cz/2014/12/file-raw-asus-zenfone.html
When you have white USB logo on your phone you only need shut down device and after press volume up button with power button. When you after this acces in droidboot you only need select reboot and after USB logo disappear. Before doing this steps you must disconnect your phone from USB cable.
When you dont have unlocked bootloader you cant flash recovery,fastboot or system. You only can sideload stock firmware.
what is the different on your tool unlocking bootloader?
droidboot_sign.img
swiczak said:
droidboot_sign.img
Click to expand...
Click to collapse
a to je ?
del
swiczak said:
To ti přihlásí fastboot (bootloader) prostě ti to zapíše seriový IMEI a fachá to pouze jenom s tím starým bootloaderem..zkoušel jsem to udělat tak že by se rovnou přeflashnul novej lollipop bootloader ale prostě nefunguje protože není sign. To samí je třeba u Gapps, taky mas přihlášeny a nebo neprihlášeny.
Click to expand...
Click to collapse
imei je ale identifikace telefonu v siti, je to na volani, jen si dej do ciselniku *#06#, nemyslel jsi treba serial number ? ale jestli to mas spravne tak promin jinak seriovy cislo v bootloaderu na lollipopu bude porad 123456blabla pokud teda nepouzijes starej bootloader, neni to chyba
del
swiczak said:
No tak jsem vyřešil jenom sériový číslo Stane se
Click to expand...
Click to collapse
v pohode
Doesn't take me to droidboot
When I click the debrick.bat, it doesn't take me to droidboot. My phone just had the usb logo with a red bar below. Please help me.
Awesome... it fixed my device thank you very much
Edit: after booting (it showed that the device is almost completely charged) i powered off the device and tried to power it on but it didnt boot
after connecting the charger it shows that the device is charging but i can neither boot the device nor access fastboot or recovery
i will try booting again after it shows that the battery is completely charged
Edit2: the green battery bar is completely filled but the LED is still orange
Edit3k its booting normally again
thank you , but if i want remove imei not recovery it , what i can do ?
custom rom , CM13 - Asus Zenfone 5 A500CG
now mobile works but battery not charging and after flashing battery is 0
how to fix this problem
rashmi0733 said:
now mobile works but battery not charging and after flashing battery is 0
how to fix this problem
Click to expand...
Click to collapse
did you try to use another cable, maybe your cable is not working well
ozank said:
did you try to use another cable, maybe your cable is not working well
Click to expand...
Click to collapse
use different cable , charger , plug but not charging led is on but battery not charging.
rashmi0733 said:
use different cable , charger , plug but not charging led is on but battery not charging.
Click to expand...
Click to collapse
if charging led is on, how is battery not charging?
assuming that now you have fastboot, maybe you can change to your latest fastboot (which were you using from kitkat or lollipop)
After run debrick.bat, my device not into droidboot. After showing usb logo, my device vibrate and showing intel inside logo repeated. Any solutions? sorry my bad english
Hello guys,
I'm in trouble with my zenfone 6 A601ac. Trying to solve the problem of "no signal" of my two sim cards, installed and reinstalled several times the stock firmware. And as a last attempt of desperation I did the command (fastboot fastboot flash fastboot.img) with fastboot.img of zenfone 5 (not 6). However, I did not had no more access to Droidboot / Fastboot (vol + / power), when I did this command the device enters an infinite loop, no way, with zenfone running android interface no longer was possible the fastboot command, when I did this command only appears the message "waiting for device".
Than, I saw this post, and did all debrick process. Now i can use fastboot pressing Vol + and Power as should to be, But, My screen is dead!!!! Sometimes appears some white lines when should appears asus logo. I'm thinking about some kind of screen resolution problem. Now i can't install the rom, cause i cant enter on ADB ( no see nothing). Has someone any idea???
Please help me!!!
Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.
Does it enter fastboot mode? Turn it on holding volume down+power.
whoadood said:
Does it enter fastboot mode? Turn it on holding volume down+power.
Click to expand...
Click to collapse
No, it doesn't even turn on
R4aPt0rX said:
No, it doesn't even turn on
Click to expand...
Click to collapse
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.
whoadood said:
Check the Device Manager of your computer and see if the mobile is detected as anything. Maybe it's detected as a Qualcomm/QCOM whatever.
Click to expand...
Click to collapse
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)
R4aPt0rX said:
Yes, right now is detecting it as Qualcomm HS-USB QDLoader 9008 (COM10)
Click to expand...
Click to collapse
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.
whoadood said:
You might need something like http://www.aryk.tech/2016/12/toolstudio-emmc-download-tool-helps-you.html
But there might be easier ways, I don't know.
Click to expand...
Click to collapse
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
Did you fix the restarting issue?
R4aPt0rX said:
I could flash again the system, but now when the system it's starting when the Google wizard starts the phone keeps restarting, I think it's related with the wifi not working, because when it starts to look for wifi access points the wizard stops and then the phone restarts, I flashed the December Update and then the August update and either of one works. Thanks for your help, you have been helping me a lot :good:
Click to expand...
Click to collapse
WiFi not working means you have a wrong kernel. Flash a full system image again
Edwin Hamal said:
Did you fix the restarting issue?
Click to expand...
Click to collapse
Not yet, I am still trying to
tinyXperia said:
WiFi not working means you have a wrong kernel. Flash a full system image again
Click to expand...
Click to collapse
Which image do you recommed me to use, and which tool do you recommed me to use?
R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.
Edwin Hamal said:
Then just flash the august persist.img using fastboot flash persist persist.img that should fix your issue. I got mine dead trying to fix that and the service guys had to change the whole motherboard.
Click to expand...
Click to collapse
OMG it worked!! Thank you man!! I really appreciate all the help!
R4aPt0rX said:
Not yet, I am still trying to
Which image do you recommed me to use, and which tool do you recommed me to use?
Click to expand...
Click to collapse
Any full image (1GB size) should work. Use mi flash tool to flash it
Hey guys,
I'm having the same problem. My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:
earthscaper said:
My MI A1 shows as 9008 in Ports section in Device Manager on the computer. I couldn't get it to boot into fastboot. I'm not sure whether the phone is unlocked or not, but I don't think there's anyway to check, USB debugging is not enabled. Can anyone tell me how to solve this? :crying:
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=74978236&postcount=310
https://forum.xda-developers.com/mi-a1/help/mi-a1-stuck-edl-9008-flash-t3724567/
R4aPt0rX said:
Hi guys i need some help. Yesterday I was flashing the latest stable ROM and my computer suddenly shutdown. I started the process again, but i didn't check and the XiaMiFlash had a different image from my device (I had flashed my friend device earlier that day) and started the flash process. The program displayed a flash error and now my phone is death. When I connect the device to my computer it does not recognize it and the LED on the phone just blinks. Can it be recovered? or it is really death. In advance thanks for your help.
Click to expand...
Click to collapse
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..
my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader
Try persist from other builds.
leo_hacker82 said:
my phone now is recovered but i have the restart issue and when i flash the persist.img it say this image isnt allow to dowenload..i have unlocked bootloader
Click to expand...
Click to collapse
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.
Edwin Hamal said:
Please try flashing persist.img from other builds, that one's from August and works for most of the devices but might not with the new batches.
Click to expand...
Click to collapse
phone failed i try many persist.img i got latest and old firmwares and when i flash it fails...isnt allowed to download
leo_hacker82 said:
hermano con que flasheaste el telefono?
que programa usaste para cargar la rom?
miflash o el emmc studio
bro how did u flash the rom with miflash or emmc studio?
im on same boat and flashing with miflash take a long time..
Click to expand...
Click to collapse
Lo cargue con MiFlash con la opción de limpiar y bloquear.
I flashed it with MiFlash with the Clean and lock option active.
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).
Somehow the phone went fully bricked.
No led wants to light up nothing is recognizing it except device manager as Qualcomm HS-USB QDLoader 9008 (COM3).
Click to expand...
Click to collapse
Only way i was able to get it to run into another boot loop was by fully charging it and attempting to press power on ... happened on occasions but software is damaged, so i can enter it into fastboot mode max.
It has some security system inside not letting me Flash it without an authorized account.
Click to expand...
Click to collapse
I tried to use everything i have found including Firehose , sadly in such a mode it is ineffective ...
My phone is not rooted, not flashed, i didnt try any hardware manipulation yet.
Are there any recommendation ?
Is your phone's bootloader unlocked? If yes and you are able to boot into fastboot mode than you can flash the factory ROM. If your bootloader is not unlocked you cannot flash any ROM. So, you have to bruteforce flash the factory ROM through 'EDL'. Good luck!
Nitin Rai said:
Is your phone's bootloader unlocked? If yes and you are able to boot into fastboot mode than you can flash the factory ROM. If your bootloader is not unlocked you cannot flash any ROM. So, you have to bruteforce flash the factory ROM through 'EDL'. Good luck!
Click to expand...
Click to collapse
Id need to glash it through EDL since my bootloader is locked.
I cant find any tutorial for it, other than being an authorized xiaomi user to fix it...
xer094 said:
Id need to glash it through EDL since my bootloader is locked.
I cant find any tutorial for it, other than being an authorized xiaomi user to fix it...
Click to expand...
Click to collapse
There are plenty of YouTube videos out there. You can search like this - " Redmi note 6 pro Test point edl flashing "
Nitin Rai said:
There are plenty of YouTube videos out there. You can search like this - " Redmi note 6 pro Test point edl flashing "
Click to expand...
Click to collapse
Okay, ill check it out, thanks :good:
xer094 said:
Okay, ill check it out, thanks :good:
Click to expand...
Click to collapse
Good luck! Don't forget to hit that thanks button if I helped you ?
Hello, I 'm facing the same issue, mine got bricked while I was installing the stock firmware. Now I'm getting following error.
https://ibb.co/nMpvcfL
Kindly update here when you'll find the solution. Thanks
Nitin Rai said:
Good luck! Don't forget to hit that thanks button if I helped you ?
Click to expand...
Click to collapse
Sadly, im still facing the same issue, i cant find any correct site/video where i could fix the phone ... im in EDL Mode but requires authentication to work ...
No Source ive found works without an authorized login
Problem solved....!
xer094 said:
Sadly, im still facing the same issue, i cant find any correct site/video where i could fix the phone ... im in EDL Mode but requires authentication to work ...
No Source ive found works without an authorized login
Click to expand...
Click to collapse
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0
forevrknight45 said:
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0
Click to expand...
Click to collapse
Yep, this is what I was talking about
forevrknight45 said:
I removed the back cover and disconnect the battery. Under the battery ribbon there are three points. You have to short circuit two points while connecting the data cable. than press flash button and here you go. Problem solved. It will take 10-12 mins. watch following video
https://www.youtube.com/watch?v=dJ7EDizk5N0
Click to expand...
Click to collapse
For me this process doesnt work, i get storsec.mbn error as it is flashing...
One of the suggestions from the video comments is written to try QPST, sadly this one isnt working with me ... or could be i havent found a good source for it.
Still not solved, getting storsec.mbn error
I had the same problem, need an authorized account to flash, so, before giving up, i contacted a russian guy who flashed my phone via teamviewer for 20 USD. Better than nothing I guess.
xer094 said:
Still not solved, getting storsec.mbn error
Click to expand...
Click to collapse
That means one of your phone's partition is corrupted
So you can try using a flash tool called "Qfil Fash Tool"
If qfil also doesn't work then try "EMMC DL Tool"
(With shorting the pins in the motherboard)
In these two tools you will get different modes of flashing. Try them out. Good luck!
felipetnk said:
Tive o mesmo problema, preciso de uma conta autorizada para fazer o flash, então, antes de desistir, entrei em contato com um cara russo que fez o flash do meu telefone via teamviewer por 20 dólares. Melhor do que nada, eu
Click to expand...
Click to collapse
RSOLVEU?
I flashed stock ROM to my Lenovo TB8704F recently, but when I rebooted, I ended up in EDL mode. I've searched online for solutions but they all appear to be for other manufacturers and don't work on my tablet. How do I exit EDL mode on my Lenovo Tab 4 8 Plus? All the usual hold power button stuff like that don't work.
bump
Bump
Bump
Bump
Bump
ADB reboot edl:
https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/
puszcza said:
ADB reboot edl:
https://www.magnetforensics.com/blog/qualcomm-phone-edl-mode/
Click to expand...
Click to collapse
I'm stuck in EDL and can't access normal mode or recovery where adb works, so no.
Bump
Bump
ChasTech said:
I flashed stock ROM to my Lenovo TB8704F recently, but when I rebooted, I ended up in EDL mode. I've searched online for solutions but they all appear to be for other manufacturers and don't work on my tablet. How do I exit EDL mode on my Lenovo Tab 4 8 Plus? All the usual hold power button stuff like that don't work.
Click to expand...
Click to collapse
Just a guess...but if you're stuck in EDL mode, it should be as easy as using Lenovo's LMSA tool to rescue the tablet. Connect your tablet to the PC when LMSA prompts you to. Don't worry about pressing the Volume Up button, because you're already in EDL mode.
This will flash the stock ROM and wipe your data. At the end of the process, it automatically reboots into Android setup.
If that doesn't work, then confirm you're actually in EDL mode. Connect the tablet to a Windows PC and confirm in Device Manager that it shows as a "Qualcomm HS-USB QDLoader 9008" port device.
The only other trick I know of is that some users have reported that EDL mode's ability to connect to a PC times out after a short period. So reboot your device (if you can) before connecting it to LMSA.
Yahoo Mike said:
Just a guess...but if you're stuck in EDL mode, it should be as easy as using Lenovo's LMSA tool to rescue the tablet. Connect your tablet to the PC when LMSA prompts you to. Don't worry about pressing the Volume Up button, because you're already in EDL mode.
This will flash the stock ROM and wipe your data. At the end of the process, it automatically reboots into Android setup.
If that doesn't work, then confirm you're actually in EDL mode. Connect the tablet to a Windows PC and confirm in Device Manager that it shows as a "Qualcomm HS-USB QDLoader 9008" port device.
The only other trick I know of is that some users have reported that EDL mode's ability to connect to a PC times out after a short period. So reboot your device (if you can) before connecting it to LMSA.
Click to expand...
Click to collapse
I've tried using LSMA, but it just says it failed to restore.
ChasTech said:
I've tried using LSMA, but it just says it failed to restore.
Click to expand...
Click to collapse
That doesn't sound good. I assume you're using the "powered off" rescue mode in LMSA, and entering the correct Hardware Code for your tablet.
After you connect the tablet to LMSA, does the progress bar move at all? If it does, at what point does it fail?
Did you get any further with QComDLoader and/or QFIL ? Did they give you more descriptive error messages?
Can you confirm the port name for your powered-on tablet in Windows Device Manager? It's usually either "9008" (EDL) or "900E" (diagnostics).
Yahoo Mike said:
That doesn't sound good. I assume you're using the "powered off" rescue mode in LMSA, and entering the correct Hardware Code for your tablet.
Click to expand...
Click to collapse
Yes, yes I am.
After you connect the tablet to LMSA, does the progress bar move at all? If it does, at what point does it fail?
Click to expand...
Click to collapse
It goes from 67% "Downloading recovery file to device" straight to 100%, then it says FAIL.
Did you get any further with QComDLoader and/or QFIL ? Did they give you more descriptive error messages?
Click to expand...
Click to collapse
QFIL gave me a sahara error, QComDLoader doesn't recognise the device.
Can you confirm the port name for your powered-on tablet in Windows Device Manager? It's usually either "9008" (EDL) or "900E" (diagnostics).
Click to expand...
Click to collapse
It does show up as "Qualcomm HS-USB QDLoader 9008 (COM4)"
ChasTech said:
Yes, yes I am.
It goes from 67% "Downloading recovery file to device" straight to 100%, then it says FAIL.
QFIL gave me a sahara error, QComDLoader doesn't recognise the device.
It does show up as "Qualcomm HS-USB QDLoader 9008 (COM4)"
Click to expand...
Click to collapse
I wonder if it it's a USB-driver problem.
You could try to uninstall & delete the 9008 driver from Device Manager (when you tablet is connected to PC). Then uninstall LMSA and reboot. Reinstall LMSA and see how you go. You should end up with the 9008 EDL driver from Lenovo. That should be compatible with LMSA.
Yahoo Mike said:
I wonder if it it's a USB-driver problem.
You could try to uninstall & delete the 9008 driver from Device Manager (when you tablet is connected to PC). Then uninstall LMSA and reboot. Reinstall LMSA and see how you go. You should end up with the 9008 EDL driver from Lenovo. That should be compatible with LMSA.
Click to expand...
Click to collapse
I just tested something: I tried flashing it without the tablet plugged in. Surprisingly, it did exactly the same as I said it had done in my reply, it was at 67% then went to 100% and failed. Therefore, I am beginning to think that LSMA does not recognise the device. I have tried doing what you recommend, but still the same.
ChasTech said:
I just tested something: I tried flashing it without the tablet plugged in. Surprisingly, it did exactly the same as I said it had done in my reply, it was at 67% then went to 100% and failed. Therefore, I am beginning to think that LSMA does not recognise the device. I have tried doing what you recommend, but still the same.
Click to expand...
Click to collapse
If there's a lengthy pause between 67% and 100%, then that's typical behaviour when your connected tablet is not in receptive EDL mode.
Double check that the 9008 driver is the one provided by Lenovo dated 21/10/2014 v.20.0.9.6. You can check in the driver's properties in Device Manager.
Remember to power the tablet off and back on just before connecting it to the PC when LMSA is sitting at 67%. Many users report that if a device is in EDL mode too long, then it won't connect to the PC. The solution is to reboot the device and re-start EDL mode. Sometimes that involves disconnecting & reconnecting the battery - let's hope you don't have to do that.
Try a different USB cable. Not all cables are fully wired.
@AlaskaLinuxUser had some luck trying older versions of QFIL. You could get lucky and find one that works for you.
Otherwise, you might be forced to send the tablet to Lenovo for repair. Something obviously went horribly wrong when you flashed that ROM to your tablet. I wouldn't flash that ROM again.
AndroidGuy087 said:
Sim, sim, eu sou.
Ele vai de 67% "Baixando o arquivo de recuperação para o dispositivo" direto para 100% e diz FALHA.
QFIL me deu um erro de sahara, QComDLoader não reconhece o dispositivo.
Ele aparece como "Qualcomm HS-USB QDLoader 9008 (COM4)"
Click to expand...
Click to collapse
Bom Dia! estou com o mesmo problema, voce conseguiu resolver, pode me ajudar?
AndroidGuy087 said:
Eu mostrei ROM de estoque para meu Lenovo TB8704F recentemente, mas quando reiniciei, acabei no modo EDL. Procurei soluções online, mas todas parecem ser de outros fabricantes e não funcionam no meu tablet. Como faço para sair do modo EDL no meu Lenovo Tab 4 8 Plus? Todas as coisas usuais de manter o botão liga / desliga como esse não funcionam.
Click to expand...
Click to collapse
Bom dia, estou com o mesmo problema voce conseguiu resolver?
Atailson said:
Bom Dia! estou com o mesmo problema, voce conseguiu resolver, pode me ajudar?
Click to expand...
Click to collapse
Please use English on XDA
Google translation
Good Morning! I have the same problem, you managed to solve it, can you help me?
Click to expand...
Click to collapse
Atailson said:
Bom dia, estou com o mesmo problema voce conseguiu resolver?
Click to expand...
Click to collapse
Good morning, I have the same problem, were you able to solve it?
Click to expand...
Click to collapse