My device is a Note 8 Ginkgo, but for some reason TWRP recognize it as a Willow (Note 8T), so only allows me to flash Willow stuff (if I try to flash .zip for Ginkgo it shows me an error message saying that the device is a Willow).
To install TWRP first I flash the vbmeta.img.
I was able to install LineageOS 17 for Willow on it, and work without big issues (GCam doesn't work, but any other camera app does).
But I was trying to install a GSI LineageOS 17 ROM, and following a tutorial that teach how to flash a Android 10 GSI, I may have commit a huge mistake.
This tutorial guide to wipe everything expect Internal Storage and flash the firmware before the ROM, but I was afraid to wipe the Vendor layer/partition on TWRP, so I uncheck it and wipe the rest.
After wiping, I flash the firmware for Willow using TWRP and reboot.
When the device tried to reboot, it just blink a black screen for 1,5 second without anything appearing and turn off.
Trying to hold the power button lead to the same, but the device vibrate first.
Holding the power button plus volume down shows the Fastboot image for the same 1,5 second and turn off again.
If I connect it to the power cable, its stay with this behave in a loop, blinking the screen while the cable is on.
So, I don't know if the mistake I made was by flashing the Firmware without wiping Vendor, or if was because I flash the Firmware for Willow, or both, or because I use TWRP instead doing by Fastboot.
Just to clarify my question, did it is bricked or there is a solution?
A video of this behave down bellow.
https://youtu.be/B28Np_e2APs
Rodolfo Candido said:
My device is a Note 8 Ginkgo, but for some reason TWRP recognize it as a Willow (Note 8T), so only allows me to flash Willow stuff (if I try to flash .zip for Ginkgo it shows me an error message saying that the device is a Willow).
To install TWRP first I flash the vbmeta.img.
I was able to install LineageOS 17 for Willow on it, and work without big issues (GCam doesn't work, but any other camera app does).
But I was trying to install a GSI LineageOS 17 ROM, and following a tutorial that teach how to flash a Android 10 GSI, I may have commit a huge mistake.
This tutorial guide to wipe everything expect Internal Storage and flash the firmware before the ROM, but I was afraid to wipe the Vendor layer/partition on TWRP, so I uncheck it and wipe the rest.
After wiping, I flash the firmware for Willow using TWRP and reboot.
When the device tried to reboot, it just blink a black screen for 1,5 second without anything appearing and turn off.
Trying to hold the power button lead to the same, but the device vibrate first.
Holding the power button plus volume down shows the Fastboot image for the same 1,5 second and turn off again.
If I connect it to the power cable, its stay with this behave in a loop, blinking the screen while the cable is on.
So, I don't know if the mistake I made was by flashing the Firmware without wiping Vendor, or if was because I flash the Firmware for Willow, or both, or because I use TWRP instead doing by Fastboot.
Just to clarify my question, did it is bricked or there is a solution?
A video of this behave down bellow.
https://youtu.be/B28Np_e2APs
Click to expand...
Click to collapse
Maybe you do have a Willow and not a ginkgo..
Try holding power button for 10 secs or something....also what happens if you press the vol up and power button
You use the buttons to go on the fastboot, what happen if you use the commands on adb fastboot.
If you are lucky and have access to the fastboot then your phone is totally salvable.
First you need to download an official fastboot rom (you need to be sure of your phone though check your box 8= Gingko 8t= willow)
I personally used this website and it did work (I got a Willow)
Willow: https://mirom.ezbox.idv.tw/en/phone/willow/
Ginkgo: https://mirom.ezbox.idv.tw/en/phone/ginkgo/
Then proceed to flash it using miflash.
I used this tutorial and it did fix my phone https://www.youtube.com/watch?v=yBK-duw43BQ
Hope it will work. If you have access to fastboot and it is just the screen flickering it worth a try.
---------- Post added at 03:50 AM ---------- Previous post was at 03:31 AM ----------
If you don’t have access to the box another way to check what fastboot Rom to get is to look at the chin of the phone on the note 8T it is slightly bigger.
Check on those photos
Redmi Note 8 (Ginkgo)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Redmi Note 8T (Willow)
If you are not able to access fastboot or recovery mode then I am afraid that you have bricked your phone and the only way to repair it will be by going to the official service centre .
Also, please try to access the recovery mode (only saying this because you haven't talked about it). If you are able to enter into the recovery mode then the recovery process will be easy as you only have to wipe all partitions (including vendor) and installing a new ROM.
islander29 said:
You use the buttons to go on the fastboot, what happen if you use the commands on adb fastboot.
If you are lucky and have access to the fastboot then your phone is totally salvable.
First you need to download an official fastboot rom (you need to be sure of your phone though check your box 8= Gingko 8t= willow)
I personally used this website and it did work (I got a Willow)
Willow: https://mirom.ezbox.idv.tw/en/phone/willow/
Ginkgo: https://mirom.ezbox.idv.tw/en/phone/ginkgo/
Then proceed to flash it using miflash.
I used this tutorial and it did fix my phone https://www.youtube.com/watch?v=yBK-duw43BQ
Hope it will work. If you have access to fastboot and it is just the screen flickering it worth a try.
---------- Post added at 03:50 AM ---------- Previous post was at 03:31 AM ----------
If you don’t have access to the box another way to check what fastboot Rom to get is to look at the chin of the phone on the note 8T it is slightly bigger.
Check on those photos
Redmi Note 8 (Ginkgo)
Redmi Note 8T (Willow)
Click to expand...
Click to collapse
Nope lol, I have a Ginko and the chin is just as big as the willow image. The picture they used to advertise the Note 8 is fake, with a much smaller chin than reality.
A better test is whether it has a notification led. Willow does not have one
One more thing try to boot into fastboot mode even if your screen is turning on/off. This behaviour is may be because you have flashed willow firmware on ginkgo.
If your MI Flash tool is recognising your device then you can save your device.
Follow these steps to flash from fastboot mode.
https://c.mi.com/thread-1712713-1-1.html
Thank you guys for the response, but as I said, it doesn't enter neither Fastboot or Recovery. It behaves exactly the same when I try to boot, blinking the screen and turning off.
Asking for help in the amazing group in Telegram, a very helpful user said that could be Kernel Panic, and I should enter EDL mode to be able to fix.
He recommended to take the phone in a Service Center, where they could solve.
I will do that and post the results later.
I have the same problem that you, twrp says my device is willow, but in fact is ginkgo, hope you can solve your problem and someone someday figure out why this stupid device have an identity crisis
Rodolfo Candido said:
Thank you guys for the response, but as I said, it doesn't enter neither Fastboot or Recovery. It behaves exactly the same when I try to boot, blinking the screen and turning off.
Asking for help in the amazing group in Telegram, a very helpful user said that could be Kernel Panic, and I should enter EDL mode to be able to fix.
He recommended to take the phone in a Service Center, where they could solve.
I will do that and post the results later.
Click to expand...
Click to collapse
Jos_Hdez22 said:
I have the same problem that you, twrp says my device is willow, but in fact is ginkgo, hope you can solve your problem and someone someday figure out why this stupid device have an identity crisis
Click to expand...
Click to collapse
hope both of you flashed the latest recovery..if you have the older version then flash recovery.img via recovery itself and just select recovery partition while flashing...although I do know few other guys who have the same issue. I might know a workaround though..If you are absolutely sure it's a ginkgo, and you are flashing a ginkgo rom then in the rom.zip you can go to META-INF/com/google/android/updater-script->here remove the following line:
Code:
getprop("ro.product.device") == "ginkgo" || abort("E3004: This package is for \"ginkgo\" devices; this is a \"" + getprop("ro.product.device") + "\".");
Now recovery won't verify your device and you can flash the proper rom. Although don't extract your full rom.zip. Just open(not extract) with winrar, go to the mentioned path and extract the updater-script, make changes with notepad++ and drag the new modified updater-script back in the same path.
Alternatively you can visit service center but you cannot explain them this exact issue as unlocking bootloader/flashing roms/root=no warranty.So you might have to boot device in EDL mode or brick your device somehow so it's in edl mode and then visit service center(I STRONGLY DO NOT RECOMMEND BRICKING YOUR OWN DEVICE.)
Hope it helps for now
will update you if I find any proper solution.
Weird result actually
Bro I did the same mistake Did you made it to fix it I was reading something about buy a EDL cable or you can made your own in home( you will need a micro usb cable and type c adapter look for it how to make one in YouTube but in my country we are under Quarantine I cant get the goddam usb type c adapter well with that cable you boot in EDL Mode and mi flash will recognize your phone like qualcom port 9008 you will able to bring him back to life Hope this info help you In my case I need to wait the end of quarantine and buy my usb type c adapter to fix mine tell me if it work for you
Greetings from panama city stay safe
Sorry for.my crappy english with doesnt talk english here
jean000 said:
Bro I did the same mistake Did you made it to fix it I was reading something about buy a EDL cable or you can made your own in home( you will need a micro usb cable and type c adapter look for it how to make one in YouTube but in my country we are under Quarantine I cant get the goddam usb type c adapter well with that cable you boot in EDL Mode and mi flash will recognize your phone like qualcom port 9008 you will able to bring him back to life Hope this info help you In my case I need to wait the end of quarantine and buy my usb type c adapter to fix mine tell me if it work for you
Greetings from panama city stay safe
Sorry for.my crappy english with doesnt talk english here
Click to expand...
Click to collapse
EDL cable and everything won't work..better visit a service center.... Xiaomi has changed it's policies and you can't flash anything if your phone is in EDL mode...it requires authorized accounts which Xiaomi provides only to service centers..
the_weird_aquarian said:
EDL cable and everything won't work..better visit a service center.... Xiaomi has changed it's policies and you can't flash anything if your phone is in EDL mode...it requires authorized accounts which Xiaomi provides only to service centers..
Click to expand...
Click to collapse
Bro I dont Know about your country but here in panama we are under quarantine everything its close and its going to be for a long long time and I live in panama there´s no oficial center here not yet
jean000 said:
Bro I dont Know about your country but here in panama we are under quarantine everything its close and its going to be for a long long time and I live in panama there´s no oficial center here not yet
Click to expand...
Click to collapse
Like I said...EDL mode won't help you..trust me....you will gain nothing by buying that EDL cable or anything because you won't have an authorised account to flash..
I got the same problem... Any fix yet? Did you fix it?
same here, with a willow. Any solution?
Try the xiaomitool2
Authorized account for flashing ginkgo/another device t
JohnyVole said:
I got the same problem... Any fix yet? Did you fix it?
Click to expand...
Click to collapse
U can send messages if U need Authorized account for flashing ginkgo/another device t.me/tesbot99
Related
Hi guys,
Looks like I have a big problem now on my Mi5s Plus. After flashing a chineese developer ROM 6.12.29 in EDL mode I got permanent MI.COM icon on the screen, so device is bricked, power button only restarts the icon. The worst thing is I cannot enter EDL mode anymore since I cannot switch off the device. I have deep flash cable, but it doesn't help, because the phone has to be turned off before release a button. The bootloader is locked, I have permission to unlock, but it doesn't work, saying account on the device is different to account I logged in.
Does anybody know how can I enter again EDL mode in this situation? How can I proceed to get the device unbricked? Please suggest.
I have tried chinees MiFlash to flash the ROM, but also without result (stops in the beginning).
Many thanks in advance.
USB cable mod, search for "USB cable EDL mode"
zebster said:
USB cable mod, search for "USB cable EDL mode"
Click to expand...
Click to collapse
I could find only the topic with modified fastboot, tried, no effect, restart to the same logo.
Could you please give me a link of the post which you think will help me.
Many thanks!
http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.
zebster said:
http://en.miui.com/thread-324300-1-1.html
As simple as that.
You have to join the two wires and then connect it to the usb port on PC.
To flash you have to separate them as a normal cable.
Click to expand...
Click to collapse
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!
DR2010 said:
It doesn't work in my situation, I've been trying already since 4 days, because to use this method and cable the phone has to be switched off, and this is not possible, because it always restarts when I press power button. I tried to switch it off in fastboot mode, leaving it in fastboot mode not connected to anything, then after approx. one minute the screen is fully off, but when I connect deep flash cable with joined wires and release the wires, it is just switching on to the same MI.COM logo and then the battery charging screen...((( The cable was working when device was alive, so contacts are correct (black and green)...
I need either the way how to bypass bootloader locking in fastboot, or another way how to reach EDL mode.
I really thought it is always possible to go into EDL with deep flash cable, but looks like it is not... Maybe I use the wrong moment to release the button. I insert cable into PC and wait 3 seconds, then release the button... Tried many times and different moments. But when device was alive it was working immediately and always...(((
Are there other ideas, guys?
Please help!!!
Click to expand...
Click to collapse
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen
zebster said:
No, you don't have to have the phone swithed off.
Connect the cable with the mod and then press the power button until it shutsdown.
When it restarts it will be already on EDL mode.
I had exactly the same problem as you.
---------- Post added at 03:52 PM ---------- Previous post was at 03:48 PM ----------
With the phone as you have do this:
- use the modded usb cable and connect the phone to PC
- press power button until the phone restarts
- disconnect usb from PC
- use normal USB cable to connect phone to PC
Now you should see the "Qualcomm HS -USB QDLoader 9008" device on you PC device manager, EDL mode on the phone with a black screen
Click to expand...
Click to collapse
Unfortunately it doesn't work, as I told above(((
When I press the power button and do not release it, the phone cyclically restarts independently if it is connected to something or not and with mod cable or not...
When did you release a power button?
1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
zebster said:
1. Have you tried to press both power and volume up to enter recovery? If you can, select download to flash with MIflash.
2. Can you enter fastboot mode? I so:
https://forum.xda-developers.com/redmi-note-3/how-to/guide-reboot-to-edl-mode-fastboot-test-t3398718
Click to expand...
Click to collapse
Dear zebster, many thanks for your kind efforts to help me.
Yes, I can enter both - standard recovery and fastboot. In standard recovery there is no any selection possible. MiFlash doesn't see anything in this mode as expected.
There is only animated (connected/disconnected) cable and adb interface available on the phone when I connect in this mode to PC, but chineese Mi PC Suite can see the phone, starts flashing even, but hangs on 5% approximately, saying there was an error, please try again (of course doesn't help).
Also I have tried before modified fastboot utility from the link to enter EDL, only restarts the phone, like I pressed the power button, and I get again lovely MI.COM logo...(((
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
if you can see this option you should be able to flash thru miflash
zebster said:
if you can see this option you should be able to flash thru miflash
Click to expand...
Click to collapse
no, I have just standard recovery from official ROM (but God knows from which one now...): on the black background screen the white edges of smartphone are pictured and the USB cable below. When I connect device to PC cable becomes connected, when disconnect - disconnected. That's all. You have different recovery...
You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html
zebster said:
You have this:
My advice is to download the original rom and flash it thru fastboot:
http://en.miui.com/download-314.html
Click to expand...
Click to collapse
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...
DR2010 said:
As far as I know it would work if the bootloader would be unlocked, but it is locked!
And the unlocking software says that account is different (I even have official permission to unlock the bootloader). So, I got stucked in a circle((((
I even tried it yesterday, but MiFlash itself in this case crashes...
Click to expand...
Click to collapse
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.
zebster said:
I've flashed mine with bootloader locked in EDL mode.
If you can use Miflash with bootloader you can flash it even with bootloader locked.
Download the oficial ROM and flash thru MIflash.
To unlock you may need to flash the China Developer ROM.
Click to expand...
Click to collapse
Thanks, but again doesn't work on my device...
As I expected, MiFlash 2016.12.14.1(Release) in fastboot mode says that "Partion flashing is not allowed" and finishes with error...
The same as I do it manually via fastboot command interface...(((
Which version of MiFlash did you use? Where can I download it?
Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl
zebster said:
Use miflash 2015.10.28.0
Was the version that worked for me.
You can also try to enter EDL on fastboot using:
fastboot oem edl
Click to expand...
Click to collapse
fastboot oem edl needs the bootloader to be unlocked.
do you have a link to download miflash 2015.10.28.0?
thanks!
I had the same problem with my Mi 5s.
This is what I eventually did to solve it (from memory - Google a bit for detailed instructions):
Download the Chinese version of Mi PC Suite (It has more options than the english version)
You can then recover from bootloop, by using it's recovery;
- Start MiPCSuite
- Boot phone to recovery (volume up + power)
- Select "Connect with MiAssistant" (bottom option)
- Phone should be detected, and a popup will show on PC with recovery options.
I believe it could download the latest version for you, or you can select a downloaded .zip file to flash.
It will have to be the same type that was previously installed (during the failed flash). So you can not go from Dev to Stable, or from CN to Global.
Go here for (Mi 5s) roms: http://en.miui.com/download-314.html#456
On the PC it immediately said flash failed, but the phone re-flashed the ROM anyway.
Hope this helps some...
P.S. Used my old phone with Google Translate App to read Chinese (Instant translation with the camera)
P.P.S. Other options won't work, because Xiaomi locked out the EDL in Chinese Developer versions. Even with the Deep Flash cable.
I'm now running Chinese Dev. version, and can not enter EDL anymore. I'll have to wait for bootloader unlock before I can flash again...
P.P.P.S. It seems I was wrong about not being able to switch: just flashed Global ROM 8.0.3.0 (From Chinese Dev. ROM 7.1.20) using the same method.
Again on the PC it said flashing failed (immediately) and stays at 0%, but the phone shows it's updating...
After flashing had to clear/reset data (again from MiPCSuite - Middle option in popup - Red button in 2nd popup), otherwise all apps keep crashing.
Because I'm back to Global ROM now, I can also use my Deep Flash cable again.
Dear Zappo, many thanks for your reply! I still fighting with the problem... already tried to disconnect the battery, not going to EDL as well.
I think only JTAG-flasher will help in my case (cannot get it, because I'm out of "civilisation" for a long time), but you have given to me the last hope))
Could you please make a screenshot where you did see the option "Connect with MiAssistant". Which version of chinese MiPCSuite did you use?
I used version 2.3.0.9091, it hangs on approximately 5% (on the phone) and does not proceed... was waiting for 30 minutes, no progress... I used it in a way to download the latest ROM and then install it.
My dear friend Zappo, I still do not believe, but I had success recovering this brick with chinese MiPCSuite v2.3.0.9091. It just downloaded the latest ROM for the device from internet and was flashing it during 1 hour 10 minutes!!! Before I had no success because I was waiting only half an hour, not more!)) But exactly after half an hour it continues and finalizes successfully!!! Another reason of my success I think could be (but less probable) that I have opened a device some days ago and disconnected the battery in order to try to get in EDL mode without the power (but was also not successful). Also today before I started MiPCSuite I have switched on the device from completely OFF state with Volume+ and Power button... So, I really do not know how the success come, but now I'm really happy!!! Many, many, many thanks for your help and for second breath )))
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
UnBrick Leeco Phones - LeEco variants X720/X727 Instructions for X722, X720 and X727
First, yes there is another thread called Unbrick your Le Pro3, tested and working
Consider this thread to be a version 2.0, a companion to that existing thread, with alternative steps and better overall clarity.
The person who created that original thread is no longer active within the Leeco Pro 3 community and the original file links are mostly dead anyway. In addition, the original Qfil file on that thread OP was corrupted and lead to a lot of frustration via countless sahara errors and other issues.
I have tried to support the many people with bricked phones, and over a long period of time, and I made many of those posts on that original thread. It's way too hard to keep things updated on that thread when I can't even find my own original posts.
There is no question that this thread will help me keep relevant information for saving bricks organized, and will better serve people with bricked devices. and maybe help resolve the clutter issue caused by the weekly " Help I bricked my phone" threads that are created almost weekly.
TLDR: The original tested and working has good information, some really nice images to view along with the instructions. But its outdated, has bad links, and a corrupted Qfil. This is too confusing so here is the updated unbrick thread that this community needs.
Note
Before attempting any of these steps : first try just leaving the phone plugged in for a few hours and wait and see if it comes back to life. It is possible that the cable is bad, your battery stats are off, and the battery is simply on 0% Especially if you have a faint blue light, instead of a red light.
X722 Qfil
This thread was inspired by the new X722 Qfil by @F.L.V For the X722 Elite Owners : these instructions will be helpful for the returning X722 users ready to unbrick their devices with the new F.L.V Qfil
Note If you are new here: the X720/X727 models use a different Qfil than the X722
Modes
* Fastboot: * Press and hold the power button and the volume down (minus) to enter fastboot mode.*
* Recovery:* Press and hold the power button and the volume up (plus) to enter Recovery mode.
* Qualcomm FIL AKA "Emergency Download Mode ( Also called ËDL" Press and hold the power key and the volume up and down key ( at same time!) to enter EDL Note, you have to be in EDL mode to see Port 9008
If you can not get the computer to recognise the phone
Try another usb C cable
Try another usb port
Make sure antivirus is disable
Reinstall android drivers
Reboot the computer
Make sure that your user has admin rights
FLASHALL.bat Method
There are several ways to unbrick, flashall.bat is absolutely the easiest and fastest. Instructions and Rom posted on the post link below.
https://forum.xda-developers.com/showpost.php?p=79854585&postcount=90
Qualcomm EDL Mode
Manual Method
You need to press all 3 buttons Volume up and Volume down + the power button simultaneously
Turn*off and press and hold [*Volume button**+**Power button**] for about 10 seconds to enter*fastboot mode
plug in the data cable to connect the computer
ADB Method
Below are instructions to boot into EDL mode for both ADB and Fastboot method.
How to Boot into EDL Mode via ADB
Setup ADB and Fastboot on your Windows PC.
Enable USB debugging on your Android device.
Open a command window on PC and connect your device to PC via USB cable.
Issue the following command via the ADB command line
Code:
adb reboot edl
└ You may get a pop-up screen on your device to authorize ADB, accept it.
Here are the Files
Qfil and Flash 2.0 https://androidfilehost.com/?w=files&flid=244213
[Qualcomm Diag QD-Loader Windows 10 Drivers :https://www.androidbrick.com/downlo...mm-diag-qd-loader-windows-10-drivers-signed/#
Make sure you place and run Flash 2.0 from the root of your PC I.E : C:/
Do not unzip Qfil yet, when selecting it needs to stay a zip file ( you can unzip later if your computer does not extract the needed files)
Qualcomm Drivers: and QPST https://www.qpstflash.com/
Keep these files. In case you ever need them again and if it works for you.*
Alternate Files if links above are broken:
QPST_2.7.104 For Leeco .zip : https://www.androidfilehost.com/?fid=6006931924117912435
QDLoader HS-USB Driver For Leeco.zip : https://www.androidfilehost.com/?fid=6006931924117912434
FlashOne 2.0 For Leeco.zip: https://www.androidfilehost.com/?fid=6006931924117912440
X722 Owners Go Here Make sure you thank and if you can donate a coffee to @F.J.V
Instructions :
Install the "RELINK HS-USB QDLoader 9008" driver
Plug your phone USB cable into the back of your desktop ( those ports usually have more power)
QFIL mode: Press on vol+ and vol- simultaneously while holding power*
Alternate way to get into edit mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode.
[email protected] Place Qfil in Main Drive: I.E the C or D, etc primary system drive
Once there uncompress your Qfil.zip Note that your directory is now C:\Qfil, or D:\Qfil.
Launch Flash 2.0 main.exe from within the Qfil directory ( Again its: C:\Qfil, or D:\Qfil.)
To start Flash program : Open Flash 2.0 Folder and click "main.exe"
Within Flash app: Click "Flash Type" window select "Qualcomm - flash dead phone"
Refresh> then you will see that port 9008 is now available
Click "Select file and then choose the Leeco "Qfil" Firmware (The path cannot not contain spaces) If you have trouble selecting the file > Right click on file> click properties > then highlight the path and right click copy> Paste into select file window.
Click the "Flash" button at the bottom of the window.
Once completed, disconnect the phone and power on. To exit the Qualcomm Recovery mode, keep the Power Button pressed for about 1 minute or until the phone will vibrate and restart into system.
After restoring your device with Qfil, the phone memory will display the incorrect amount. The solution is to flash the original stock EUI firmware.
After you have performed all of the steps
* Your Le Pro 3 will have the technicians repair version of EUI.
* The phone may not boot automatically.
* Press and hold the Power Button for 30+ seconds and the phone will vibrate
* Release the power button, it will vibrate again after 10-20 seconds*
* The phone will leave the Qualcomm Repair Mode, and will vibrate continuously for 20 seconds or longer.
* In some cases the phone could take as long as 15 minutes to start. But usually it's faster.
* Immediately you will notice that part of your storage is missing, reformat storage to resolve
Repair Storage
Restore to Default Stock Software for your Device
Option 1: Flash your Zl1 Recovery or My Recovery
Option 2 Flash full stock X720 firmware.
Option 3: Push the latest TWRP Recovery and Root to the phone. > Use SuperSu at this stage, as Magisk will not work yet.
You can use the Leeco Official Rom Downloads
Le Pro 3 : http://bug.letv.com/cn/download/phone/56 ( X720/X727)
Elite : http://bug.letv.com/cn/download/phone/80 ( X722 - Use only with ADB )
Custom Rom Install: ( The All in One Tool provides quick easy options for Stock and Custom Rom installation
Once TWRP is installed,
Format storage and reboot to Recovery
Format.> Type yes. then immediately reboot to recovery > you may see a message that no OS is installed, ignore, check to install TWRP
Reboot to Recovery and place files in Storage via your Desktop or Better Yet: Use an OTG Flash Drive and install from it.
Now you are ready to flash a Compatible Rom, Gapps And Magisk
So that is how you unbrick.
If you would rather have a visual guide the embedded link may be easier for you to follow.
Although the link above is for the Leeco Max 2., the steps are identical!
It's not in English: so use Chrome and enable Google Translate
QPST Alternative Method
Go Here: https://forum.xda-developers.com/showpost.php?p=77723528&postcount=2
Remember to only use the files for the your device and the only Qfil that will work for the X720 /X727 is named : Qfil: le_zl1_qfil_ufs_fix
If you have an X722 go to the F.L.V thread linked above for your Qfil file then you can come back here for instructions if needed.
Good luck, be patient, the first time unbricking can be stressful and will sometimes take a while, mostly because you are not familiar with the steps yet. Otherwise it's usually a fast process.
P.S.
Please Do not spam my PM box, these are the only instructions that you need and there is nothing more that I can give you beyond these instructions.
This year I have received possibly hundreds of PM's concerning bricks. ( Not kidding!) Hundreds!
So I can not respond to PM's about bricks, its too much., especially when the majority of these people never read the basic instructions. So any questions or answers concerning unbricking needs to happen here on this thread I apologise, but I will have ignore PM's with questions about de-bricking your device. However, I myself an hopefully others will check this thread often.
Note : If all else fails and you still can't get it and you absolutely need my help: You can mail the phone to me to attempt to debrick it for you for a small nominal fee or it will make a beautiful paperweight.
Hey recently recovered bricked X722 survivors:
Your help is needed here : Please help with supporting people with bricked phones. It will be greatly appreciated, and since most of you guys recovered you phone for free! Why not help out? We should have a lot of experts! [/COLOR][/B]
It Failed : Start Over
Ensure that your antivirus software is turned off it will detect these tools as a malware and delete parts of the file making them useless.
Did I mention that you should turn off antivirus?
To reiterate: trust that nothing bad will happen, you are already bricked, so turn off antivirus or pay someone to unbrick your phone, for you.
Trust that the people who do these type of repairs for a living rarely use antivirus because most "exploits" can often be be removed manually with ease.
Don’t give up so easily if something goes wrong
Simply do a gut check by rethinking and rereading the steps:
Did you follow instructions?
Did you reboot the computer after installing the drivers?
Uninstall and reinstall the drivers then reboot your desktop.
Did you disable Antivirus?
Unless your phone has hardware issues these steps will eventually work.
To reiterate If you device refuses to unbrick
most likely You missed a step!
Its either your cable, your desktop computer, or the device hardware.
Some X727 owners will have success using Qfil and unbricking and still have a black screen > First check that the phone has actually restarted normally, and is not still in EDL repair mode.
If you checked everything and still have this issue, your LCD may likely need to be replaced.
However, there is a couple of other methods which will be added that may resolve this kind of issue.
Go to post #2 and # 3 on this thread for additional ways to unbrick
Hypothetical Hardware Damage repair for cheap steps listed at this post.
One Last thing:
I understand that you are upset about your phone, but I DO NOT want to read your whining and ranting about Leeco using bad parts or the rom had poor development. IT'S YOUR FAULT PERIOD. >>> YOU decided to use custom roms.
Next, If I am spending my time to help you : you should really click thanks or I might be likely ignore your plea's There is nothing more annoying than spending 20- 30 minutes on multiple occasions, attempting to help someone that can't even click a thank you button. I am not collecting likes...it's simply a matter of common courtesy.
Yay you are now un-bricked! If you want to courteous and buy me cup of coffee, for making things easy for you, it will be appreciated. Have a nice day.
tsongming said:
Alternate Way to Unbrick Using the QPST Method
tldr.
Click to expand...
Click to collapse
I finally was able to go through with 100% success on flashing the QPST package via Qfil.
My phone is still on black screen with a strong short vibration everytime i try to turn it on. That's the only sign of life. I can't get the display to show anything to me (it was used only for a month and still is brand new and I don't think that screen is suddenly dead).
Phone still boots into 9008 mode and thats pretty much it. Can't try anything as phone doesn't boot normally. Are there any extra pointers to try the revival?
Alternate Way to Unbrick Using the QPST Method
Keep in mind that issues that remain after using Flash 2.0 or QPST could be caused by your Desktop.
Make sure that antivirus and defender is disabled
Try right clicking on the unknown device listing in Device manager and choose update driver.
Afterwards use the All in One tool to update Android drivers, ADB and allow system wide privileges.
Try another computer if you have one nearby.
Make sure that you are in EDL Qualcomm mode :
QPST - Try Flash 2.0 first before attempting to use QPST. Most of the time Flash 2.0 is a fast and easy way to unbrick your device.
QPST Flash Tool: https://androidmtk.com/download-qpst-flash-tool
B]Update android Drivers on PC, and turn on test signing.[/B]
If your phone is not seen in Device manager:
* Go into QFIL mode: Press on vol+ and vol- simultaneously while holding power*
* Alternate way to get into EDL mode ( Press vol+ and vol- while plugging usb into pc. enter in edl mode. ( See OP for using ADB)
* Now you should be able to see the phone as 9008 Port .
* Install QPST.WIN.x.x installer
* Install Qcom Driver*
* Run Qfil main.exe and set the configuration to download configuration.
* Device Type: Set To UFS,
* Other Options Don't Change. *
* Press Ok To Confirm .
* Select Build Type – Flat Build
* Select Programmer *Choose "Prog _Ufs_Firehose_8996_Ddr.Efl"
* Load *Xml- Choose All Ramprogxxxx —Choose All Pathxxx
* Ensure that you are in EDL mode
* Connect The Usb Cable > Qualcomm Hs-Usb Qdloader 9008 "Port Appears at the top Press Download To Flash , If Flash Failure To Stop , You Need Press Three Key To Power Off Your Phone , And Do Up Step Again To Flash , Try again until successful.
If the steps from the OP and within this QPST post fail:
This link may have additional things to try: http://en.miui.com/thread-266598-1-1.html
If none of this works you unfortunately have a hardware based problem.
Once you have restored your phone, you will need to repair your storage space.. You can do repair several ways. I would suggest that you use one of the two options below:
You could flash my recovery: https://forum.xda-developers.com/le-...clean-t3727920
It has Magisk and Root, though it would need to be updated. But, it will restore you partitions. > From here you can quickly return to using custom roms.
Another Option is return to full stock with the stock Rom : http://ota.scloud.lfengmobile.com/ot...41S-5.9.02.zip
Note this needs to be flashed via ADB or by using the All In One Tool ; it will remove all data from phone and restore the phone as if it just came out of the box.
Edit :
Another version of Official Stock: http://bug.letv.com/cn/download/phone/56
Once the phone is restored by Qfil to the Technicians Repair copy
Boot into fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Unlock Bootloader and Flash Roms, Gapps and Magisk
HOW TO INSTALL TWRP
Enable developer options
Allow oem unlock
Power off
Hold Volume down + Power for Fastboot mode
fastboot oem unlock-go
fastboot boot twrp.img
adb push twrp.img /sdcard/
Choose "Install" and then "Install Image"
Select twrp.img
Select Partition "Recovery"
Confirm Flash
Reboot to recovery
One more method to try : Flash-all.bat
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
i did the qfil flash everything went perfect but the eui is a dev version and it thinks my phone is x720 and its on 5.8.415d how do i go back to eui 5.8.21s
Coconut tree said:
i did the qfil flash everything went perfect but the eui is a dev version and it thinks my phone is x720 and its on 5.8.415d how do i go back to eui 5.8.21s
Click to expand...
Click to collapse
This is an edited duplicate post to ensure not only that you get the message, but to benefit others, by making a change to the reserved spot above
Follow instructions here: https://forum.xda-developers.com/showpost.php?p=77723530&postcount=3
After you have restored your phone to full stock : you would need to start from the beginning, to use custom Roms again : I.E, unlock the bootloader etc.
tsongming said:
This is a duplicate post to ensure that you see it, and for the benefit of others.
You could flash my recovery: https://forum.xda-developers.com/le-...clean-t3727920
It has Magisk and Root, though it would need to be updated. but, it will restore you partitions.
Another Option is full stock, http://ota.scloud.lfengmobile.com/ot...41S-5.9.02.zip
Note this needs to be flashed via ADB or the All In One Tool ; it will remove all data from phone and restorte the phone as if it just came out of the box.
To use custom Roms again you would need to start from the beginning.
Click to expand...
Click to collapse
Umm first thank you very much I followed your instructions on how to unbrick my phone it worked but I don't have TWRP and for some reason my phone won't connect to my PC can that file be flash via the stock recovery?
Coconut tree said:
Umm first thank you very much I followed your instructions on how to unbrick my phone it worked but I don't have TWRP and for some reason my phone won't connect to my PC can that file be flash via the stock recovery?
Click to expand...
Click to collapse
Okay,
While in fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Edit: I a made an Addendum to the post above, with steps you may find helpful
tsongming said:
Okay,
While in fastboot, You can push TWRP and SuperSU to your device as long as its unlocked
Another option
Download the stock Rom, change its name to "update.zip" then use Leeco's Recovery mode to install the software.
Edit: I a made an Addendum to the post above, with steps you may find helpful
Click to expand...
Click to collapse
I appreciate all of your help but I've been searching for the stock ROM for days and can't find it I'm only finding the eui 5.8.28s for the x720 model and I heard that update has lots of bug's with the playstore
Coconut tree said:
I appreciate all of your help but I've been searching for the stock ROM for days and can't find it I'm only finding the eui 5.8.28s for the x720 model and I heard that update has lots of bug's with the playstore
Click to expand...
Click to collapse
Use this thread
https://forum.xda-developers.com/le-pro3/development/le-eco-pro-3-x727-twrp-backup-clean-t3727920
andrew2401 said:
Use this thread
https://forum.xda-developers.com/le-pro3/development/le-eco-pro-3-x727-twrp-backup-clean-t3727920
Click to expand...
Click to collapse
I've read everything on the tread but sorry for the stupid question I'm a noob but it looks like that back up is from TWRP but I'm using leeco stock recovery where I live data is very expensive so I want to know if it will work before wasting my data downloading it??
Coconut tree said:
I've read everything on the tread but sorry for the stupid question I'm a noob but it looks like that back up is from TWRP but I'm using leeco stock recovery where I live data is very expensive so I want to know if it will work before wasting my data downloading it??
Click to expand...
Click to collapse
If your plan is to return to custom Roms, do what I mentioned earlier.
Push TWRP and SU to your device.
Then boot to TWRP, your storage folder will now be accessible by your desktop computer. If you do not own an OTG adapter, buy one it makes using custom Roms a thousand times easier. They usually cost $3, and you can buy them at Walmart.
Download my Recovery, and unzip the file inside the TWRP folder, in storage. ( This path can only be this deep: Sd/twrp/Brbxxxx/files here ( don't created and name any additional folders after Brbxxxx)
Next boot to Twrp recovery, and click restore, selecting everything.
Now you will have clean stock with TWRP, and Magisk.
From there flash you flash you the latest TWRP...Again yes, the Recovery overwrote TWRP.
Next flash your Rom, Gapps and the very latest Magisk.
If you would rather have stock, there are plenty of versions of stock all over the internet...Every version. When I return home, I will see if I can find a link, or you can just Google " Leeco X720 Stock firmware"
If you foliar stock of Lt flash from And or the AllinOne Tool.
Sent from my LeEco LEX727 using XDA Labs
Okay here is stock 5.8.26.
I added it to my personal mega drive.
Here is the link from my drive
https://mega.nz/#!xB5ggKbQ!OeJbUAGKmlk6AZlzfMjxSGK8OnBkiYsDvdeekTauRag
Yes, it for a X720. It doesn't matter, the X720 and X727 ate the same with the exception of the Sim card, simply flash the radio driver"firmware" from the x727 5.8.20s to remind the phone that it is a X727.
Reminder, I have an X727. My recovery is a X727 5.8.20s recovery.
Sent from my LeEco LEX727 using XDA Labs
tsongming said:
Okay here is stock 5.8.26.
I added it to my personal mega drive.
Here is the link from my drive
https://mega.nz/#!xB5ggKbQ!OeJbUAGKmlk6AZlzfMjxSGK8OnBkiYsDvdeekTauRag
Yes, it for a X720. It doesn't matter, the X720 and X727 ate the same with the exception of the Sim card, simply flash the radio driver"firmware" from the x727 5.8.20s to remind the phone that it is a X727.
Reminder, I have an X727. My recovery is a X727 5.8.20s recovery.
Click to expand...
Click to collapse
Thanks ? and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Coconut tree said:
Thanks and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Click to expand...
Click to collapse
First you can download the stock rom on the phone, then rename it to update.zip
Then boot to Leeco Recovery and install the stock Rom as a n update,.
If your computer is not seeing the phone, its either a driver issue ( Android USB driver) or the Firewall/Antivirus,
It could also be a corrupted user account. BTW, the account must have admin privileges. If all else fails use a different computer.
Since you restored the phone via Qfil,
Don't forget to enable developer options
Enable usb debugging,
set to MTP File transfer
OEM Unlock is selected.
The All in One tool should be able to show whether or not the bootloader is unlocked, while in fastboot mode.
Now that your phone is fixed read my signature.
Coconut tree said:
Thanks and I'm planning on staying on my stock recovery and ROM but I don't think you're noticing that I'm saying I don't have TWRP on my phone and my phone won't connect to my PC is there any way to update without a PC and TWRP?
Click to expand...
Click to collapse
no luck i downloaded the file change the name to update.zip and i got a error (failed to update cause:corrupted)
Coconut tree said:
no luck i downloaded the file change the name to update.zip and i got a error (failed to update cause:corrupted)
Click to expand...
Click to collapse
It is really beginning to sound like you skipped a step
Did you do this part?
After your phone boots, you will see that its storage is abnormally 9.71 GB, to fix this just factory reset your phone choosing the option “Format Virtual SD card”. File system will be restored to normal values.
Now there should be no reason why the phone is not seen by your computer, and you cannot install a factory Rom. Unless the phone has hardware damage. ( which would not make sense since you were able to unbrick the phone ) In addition, did you try another desktop user, removing the android drivers and reinstalling? Worst case scenario, if you can't get it PM me, you can mail the phone to me and I will fix it for you ( This happens alot )
tsongming said:
It is really beginning to sound like you skipped a step
Did you do this part?
After your phone boots, you will see that its storage is abnormally 9.71 GB, to fix this just factory reset your phone choosing the option “Format Virtual SD card”. File system will be restored to normal values.
Now there should be no reason why the phone is not seen by your computer, and you cannot install a factory Rom. Unless the phone has hardware damage. ( which would not make sense since you were able to unbrick the phone ) In addition, did you try another desktop user, removing the android drivers and reinstalling? Worst case scenario, if you can't get it PM me, you can mail the phone to me and I will fix it for you ( This happens alot )
Click to expand...
Click to collapse
Well yeah that's the weird part my phone would only charge when it's connected to my computer but windows 10 says it's damage but I did the qfil part without any problem and yes I factory reset my phone so that doesn't make any sense and I tried installing TWRP but no luck I ordered a USB port replacement hope that's the problem. And I would mail you my phone but I'm only 15 and I live in the Caribbean
Coconut tree said:
Well yeah that's the weird part my phone would only charge when it's connected to my computer but windows 10 says it's damage but I did the qfil part without any problem and yes I factory reset my phone so that doesn't make any sense and I tried installing TWRP but no luck I ordered a USB port replacement hope that's the problem. And I would mail you my phone but I'm only 15 and I live in the Caribbean
Click to expand...
Click to collapse
Okay no worries,
I am not totally convinced that there is an issue with the usb card, although it is possible.
Can you get access to another computer?
If so place all of your files ( All in One tool, Drivers, firmware, Rom, Gapps, Root etc) on a flash drive and take them with you..
If you can simply get a computer to see the phone again, you will be good to go> A computer with Linux would be a great option for testing the connectivity and proving that the issue lies with the Windows drivers or something that is blocking the connection ( Antivirus, etc)
On Windows: Go to the Control Manager> System > Device manager > then go to where it has USB and see if it lists the phone as a unknown device.or by name
If it does, that is the issue. Just uninstall flash 2.0, the qualcomm drivers, and te android usb driver and then reinstall, it could resolve the issue for good.
If you order the card it can be tricky because some of those card come with the option of two flex cable options such as this : You want this one Yellow Flex Cable
In fact, most of the time the issue is just the cable and not the card, those cables, have been known to go bad.
tsongming said:
Okay no worries,
I am not totally convinced that there is an issue with the usb card, although it is possible.
Can you get access to another computer?
If so place all of your files ( All in One tool, Drivers, firmware, Rom, Gapps, Root etc) on a flash drive and take them with you..
If you can simply get a computer to see the phone again, you will be good to go> A computer with Linux would be a great option for testing the connectivity and proving that the issue lies with the Windows drivers or something that is blocking the connection ( Antivirus, etc)
On Windows: Go to the Control Manager> System > Device manager > then go to where it has USB and see if it lists the phone as a unknown device.or by name
If it does, that is the issue. Just uninstall flash 2.0, the qualcomm drivers, and te android usb driver and then reinstall, it could resolve the issue for good.
If you order the card it can be tricky because some of those card come with the option of two flex cable options such as this : You want this one Yellow Flex Cable
In fact, most of the time the issue is just the cable and not the card, those cables, have been known to go bad.
Click to expand...
Click to collapse
I tried it on a different PC still no luck even after uninstalling those you mentioned the weird part is i got my phone to put up in fastboot mode but it was giving me a weird error failed (command write failed (no error))..... I was using the dev rom for a few hours it's pretty stable (but constant red light flashing on the screen "strick mode off in developer options" and phone constantly loosing signal I'm planning on giving up ??? all i want to do is get back to eui 19,20,21s for the American version but it's impossible to find the stock rom online
Coconut tree said:
I tried it on a different PC still no luck even after uninstalling those you mentioned the weird part is i got my phone to put up in fastboot mode but it was giving me a weird error failed (command write failed (no error))..... I was using the dev rom for a few hours it's pretty stable (but constant red light flashing on the screen "strick mode off in developer options" and phone constantly loosing signal I'm planning on giving up ? all i want to do is get back to eui 19,20,21s for the American version but it's impossible to find the stock rom online
Click to expand...
Click to collapse
Le Pro 3 : http://bug.letv.com/cn/download/phone/56 ( X720/X727)
Edit the link above is the current Official stock : Remember that I gave you the link to an earlier version in Post 2 : https://forum.xda-developers.com/showpost.php?p=77723530&postcount=3
Hi,
soo I wanted to go from a Android 6 RR ROM to the newest Android 9 one.
Flashed new TWRP, and then the ROM using TWRP. Didn't boot, I looked it up and found that I needed to flash a 2.5 or 3.5 ZUI first.
I tried flashing a 3.5 ROM for about 5 hours using QFIL, with various errors (pretty much tried everything).
I was finally able to flash it using a 2016 MiFlash version (it reported "success").
I then plugged out the phone and tried rebooting it. Now, whatever I do (even just plugging in the cable), it vibrates once, and then over and over again every 12 seconds or so. No LED flashes.
I tried every possible key combination to get it back into EDL, unsuccessfully (while having to disconnect the battery lead each time because I can't get it to turn off).
I would greatly appreciate any help, as I'm now completely lost here. I've never seen a phone that is able to be bricked that hard before.
Kind regards
I bricked my Z2 Plus on two separate occasions whilst trying to flash ROMs. The first time I was able to get into EDL mode using the hardware buttons on the device, but it was incredibly difficult and relied on precise timing because the device was stuck in a reboot loop to the bootloader screen, hence it kept switching off whilst trying to do the button combination.
The second time I bricked this phone, I was unable to get into EDL mode using the hardware buttons. So I had to resort to making a 'deep flash' cable using the USB Type-C cable that came with the device. You have to strip the coating off the cable and then stick a pin through two of the wires to force the phone into EDL mode.
There's a guide here that I used to help:
https://zukfans.eu/community/thread...-from-hard-brick-state-9008-mode-easily.3504/
Alternatively you can purchase a proper 'deep flash' EDL cable from somewhere like eBay or AliExpress. It's just a normal USB cable with a button on it that you can press to get into EDL mode. Hope this helps.
Thanks. I managed to get the phone into EDL mode by making the cable suggested, but I still find myself unable to flash anything properly. The port shows correctly as Qualcomm HS-USB QDLoader 9008 (using Qualcomm driver 2.1.22).
I now tried flashing a 2.5 ROM and the 3.5 one again using MiFlash (version 2016.03.30.0) and it fails with various errors (Reached EOF while receiving hello packet etc.).
Trying to flash using QFIL (version 2.0.1.1, installed using QPST) gets me this error:
Code:
14:43:15: ERROR: function: sahara_rx_data:237 Unable to read packet header. Only read 0 bytes.
14:43:15: ERROR: function: sahara_main:924 Sahara protocol error
14:43:15: ERROR: function: main:303 Uploading Image using Sahara protocol failed
Download Fail:Sahara Fail:QSaharaServer Fail:Process fail
Finish Download
I already tried many of the steps suggested to fix that (like shortening the path etc.), but even before bricking I could only get past the Sahara Fail error a few times.
Thanks a lot
I tried again using MiFlash and it got to flashing but crashed in between with
Code:
Fatal Error(0x8000ffff: Send configure command)
d0ntflash said:
I tried again using MiFlash and it got to flashing but crashed in between with
Click to expand...
Click to collapse
Install latest qfil ,load rom in it
Click on download as soon as phone boots to edl
JV Spartacus said:
Install latest qfil ,load rom in it
Click on download as soon as phone boots to edl
Click to expand...
Click to collapse
I installed it from QPST.2.7.460.zip, is that the latest version?
d0ntflash said:
I installed it from QPST.2.7.460.zip, is that the latest version?
Click to expand...
Click to collapse
I think QPST 2.7.474 is the latest. I would also recommended you use QFIL 2.0.1.9 instead of MiFlash. As JV mentioned you must start the flash process quickly after the phone enters EDL mode. If there's a delay then that can cause errors to appear.
Ok, this is the furthest I got so far:
https://pastebin.com/EQgXDwEe
And the last (relevant) lines from the mentioned logfile:
https://pastebin.com/3ZmMiBZA
Do I have a damaged image file? I downloaded it from this thread (This file: http://cdn.zui.lenovomm.com/downloa...SER_Q00030.1_O_ZUI_3.5.389_ST_180525_qpst.zip)
Thanks
Got a little further with the 2.5 Image, but not quite there yet:
https://pastebin.com/c0xGg2qy
Is it a connection problem?
I finally managed to flash 2.5 using QFIL and get the phone to boot again. Thank you very much!
This is how you make a proper "deep flash" cable guys
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Cheers!
d0ntflash said:
This is how you make a proper "deep flash" cable guys
Cheers!
Click to expand...
Click to collapse
That's pretty good. You even managed to fit a button!
Since 3 days I could not be able to boot my zuk z2 plus, my phone is completely bricked now. Every time I press the power button of the phone it gives a small vibration and nothing cames out in the screen. It starts when I was in aex 5.8 rom and someone in xda provided a zui 2.5 rom ( twrp). I tried to flash it and it fails. I wipe the dalvik , cache and accidentally pressed reboot system and that thing is started. When I try to flash stock rom via qfil it always show as 900E port and when I press the download button it says, "fail to switch to edl" . Please help me . I need my phone back as soon as possible.
Rit2005 said:
Since 3 days I could not be able to boot my zuk z2 plus, my phone is completely bricked now. Every time I press the power button of the phone it gives a small vibration and nothing cames out in the screen. It starts when I was in aex 5.8 rom and someone in xda provided a zui 2.5 rom ( twrp). I tried to flash it and it fails. I wipe the dalvik , cache and accidentally pressed reboot system and that thing is started. When I try to flash stock rom via qfil it always show as 900E port and when I press the download button it says, "fail to switch to edl" . Please help me . I need my phone back as soon as possible.
Click to expand...
Click to collapse
Hallo,
i am in the same circle. Cable with button = created, backcover of tablet = removed, in device manager showing only iagnostic 900E (never see 9008 or something else).
Rescue and Smart Assistant cannot switch tablet to EDL, cannot rescue, cannot flash stock...
2Rit2005: your tablet is ok right now?
2ALL: can someone help me, please?
Krabat
krabat said:
Hallo,
i am in the same circle. Cable with button = created, backcover of tablet = removed, in device manager showing only iagnostic 900E (never see 9008 or something else).
Rescue and Smart Assistant cannot switch tablet to EDL, cannot rescue, cannot flash stock...
2Rit2005: your tablet is ok right now?
2ALL: can someone help me, please?
Krabat
Click to expand...
Click to collapse
I am having the same EDL problem on my ZUK Z2 Pro. Always 900E.
Screen is out. Buttons method doesn't work (holding Volume+ button for 15sec, pressing Power button for 0,5sec and pressing and holding it and finally plugging in the cable into USB port).
I have made the deep flash cable (I connect black and blue wires as I am left with pink and white), but I get notifications from windows 10 that it does not recognize the device when I have the wires connected ( I assume it is ok).
When I disconnect the wires I don't get 9008 in Device Manager ports.
Need help with that pretty please whoever can
Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here <Moderator Edit>: warning, comes up as Trojan:Script/Wacatac.B!ml in Windows Defender.
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
If it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
3- <Moderator Edit>: not allowed
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now
This is sweet, how much are the credits?
11214 said:
This is sweet, how much are the credits?
Click to expand...
Click to collapse
It depends on your country but it is about 1 US dollar per credit
raminta said:
It depends on your country but it is about 1 US dollar per credit
Click to expand...
Click to collapse
That's great, much better than the €25 I had to pay.
Thanks for the guide.
raminta said:
Hello guys
Today I'm going to tell you about how to bring your phone back to life when it is bricked and also you don't have access to fastboot.
few days ago when I wanted to turn back to Xiaomi EU weekly ROM from HOS, the fastboot script which is provided by Xiaomi EU team in order to flash the ROM gave me to many errors when it was trying to flash "super" partition and mistakenly I had rebooted my phone and then I realized the the phone is dead, it didn't show any sign of life (I mean no vibration, no fastboot and no screen light, literary nothing at all).
After some research I found out that Qualcomm powered devices have something called EDL which is stand for (Emergency Download mode) and it is there to flash fastboot ROMs when you don't have access to fastboot (as matter of fact EDL mode is one level lower than fastboot and let you to access the phone when it is dead and also it cannot be erased with fastboot).
Important: with this tutorial you can fix your phone by yourself and also there will be no need to pay anyone with authorized xiaomi account to connect to your personal computer and do the flash for you.
Lets head to tutorial:
Requirements:
1- A windows system
2- EDL drivers which can be found here
3- Original USB cable
4- Xiaomi pro tool which can be found here
5- Fastboot ROM for your phone which can be found here
method:
1- first you need to boot your phone into EDL mode (you can do this by holding volume up button and connect your phone with its USB cable and check "device manager" on windows to check if your PC recognized your phone or not. you should see "Qualcomm HS-USB QDLoader 9008" under "ports" section (look at below picture)
View attachment 5547309
If it didn't showed up follow this tutorial to install drivers
2- then open the Xiaomi pro tool,register on it then change the "select model" to your phone model (in this case POCO F3(Alioth)) and next change port to EDL booted device (should be like this: Qualcomm HS-USB QDLoader 9008)
View attachment 5547333
3- You need to buy at least 5 credits in order to flash ROM on your device you can buy it on the internet just google "credits for xiaomi pro tool" (Iranian users can use this site to buy credits)
4- go to "xiaomi firmware flasher" page on xiaomi pro tool app and locate the downloaded ROM (you should locate "image" folder (downloaded ROM/images)) after that you will see that it loaded files correctly.
View attachment 5547349
5- Disconnect your phone and hold power button for 15 second then press and hold volume up button and connect your phone with its USB cable to boot to EDL mode again and check thee "ports" on the tool app again (it should be same as step 2)
6- Click on flash device which is on the bottom right of the xiaomi pro tool app then it will ask for using your credits in order to flash device that you should click on "yes" button and after that you will see that flash processing is going on.
7- The tool will reboot your phone automatically but if you find your phone completely dead after the flashing process(not responding to anything and not going to EDL mode again (which was my case)) just don't panic, your phone maybe out of charge so just connect your phone to a charger and wait, after some minutes you will see the battery icon on your device.
8- hooray, you made it. you can enjoy your phone now
Click to expand...
Click to collapse
that's absolutely i done but for those people who don't have access to buy credit can search patched hose but till now no one has patched for our device poco f3. for patching it requires reverse engineering skill which i don't have.
why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...
pedrosantosobral said:
why are the credits needed? this program is going to be likely used by desperate users that destroyed the phone and they even have to pay? i get the developers need money but its just bad...
Click to expand...
Click to collapse
The only other option is paying €25 to a random person on the net to tunnel into your PC and do the job for you.
Nice
It's difficult to trust these random programs, but desperate users with bricked phones don't have many other options...
I had to pay 25€ to get mine running again. The fact that you have to pay sucks. It shouldn't be like that.
I paid more than $30 to random person I found on youtube and I still had to disassemble my phone myself to put it on EDL mode (was it really necessary? - since my phone has an unlocked bootloader).
WARNING! Xiaomi Tools Pro contains a backdoor virus
Win32/Bladabindi!ml - Virus
This will allow the hacker to gain control of your computer and potentially draining your bank accounts/bitcoin.
you have been warned.
I have always bought Xiaomi Products but after reading all the trouble that you have to go through and zero customer support with most software infected by ****ty backdoors, I have to go back to some oneplus or pixel or mainstream phones.
Hello everyone,
I just wanted to say I followed the instructions above and it worked fine. I paid 10€ for 10 credits at <Moderator Edit>: (removed) and I used the tool and everything went smooth with my poco f3. Just like it says in the tutorial, if it does not reboot automatically, just charge your phone for a few minutes and voilá. Just wanted to leave my input in here, so if anyone is in this situation, you CAN fix your phone.
<Moderator Edit>: Thread closed. @raminta look for my PM shortly.
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
TheGhost1951 said:
From the image you posted, it looks like you are using the wrong MSM version. "Device not match image".......
Click to expand...
Click to collapse
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
And it is pretty interesting.. As far as i know EDL connection only alive for 5-10 sec, but currently MsM tool shows Connected until my phone was plugged in (even after refreshing it)
pmppm said:
I used this exact version on this phone like 2 days ago, I dont think it is a version problem, but thanks for the help!
Click to expand...
Click to collapse
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
TheSayaMan said:
Just like the other posted said. If it says that error, it means that your device ID is different. Did you possibly use the India MSM which would change your device ID and not allow you to use the one you were using before? You can also try unchecking sha265check and check use lite firehose and see if it works that way.
Click to expand...
Click to collapse
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
pmppm said:
Okay so basically, you're both right. I got the Global version, but with the correct MsM version for that did not worked. The solution was to use the Indian version to unbrick it, then ofc switch back to the global. I took this idea from this post, It's seemed so idiot to do it that way, but I had nothing to lose. Thanks again!
Click to expand...
Click to collapse
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
TheGhost1951 said:
Once you used the Indian MSM, then to go global you have to install the updater tool from Google Play store to choose the version you want and install it that way. I believe.....
Click to expand...
Click to collapse
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
TheSayaMan said:
I don't believe it's available in play store, have to Google search for it but otherwise your right, once you use the India MSM, your device ID is permanently changed and can no longer use the reg MSM for the device.
Click to expand...
Click to collapse
Would this not work?
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
V0latyle said:
I am not sure how OnePlus implements it, but many devices have a Qualcomm USB mode or "Emergency Download Mode" for performing a low level reflash of basic firmware such as the bootloader. Most often, when a device screen doesn't come on, but it vibrates and a PC shows a connected device, this is the case - the PC has detected the QUSB mode.
Unfortunately, Qualcomm does not make their Qualcomm Product Support Tool available to the public, and most OEMs do not provide the necessary binaries to restore the bootloader. The device cannot be repaired or restored without these tools, unless the mainboard is replaced. Unfortunately in this case, I believe that is your only option.
Click to expand...
Click to collapse
It is called the MSM Download Tool. And it is device specific and ready available.
TheGhost1951 said:
It is called the MSM Download Tool. And it is device specific and ready available.
Click to expand...
Click to collapse
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Odin is for flashing Samsung devices. Samsung and now OnePlus are the only two devices I have worked with.
pmppm said:
Hey.
This post is my last faith in this device.
So basically I was about to flash partitions, but when I tried to go into fastbootd to flash the critical stuff, after the "fastboot reboot fastboot" command my phone was completely got bricked. I already tried every type of key combinations, the screen was black the entire time, and the phone won't even vibrates.
The only signal of it's being alive, when I plug it and press pwr + vol up, windows gives the sound of a connected/disconnected device, and the MsM tool shows that too. At this point, i was sure about the MsM tool and didn't panicked, I knew that I can almost always unbrick the phone with that... Hmm... This time it was different, because every time I get an error: "Sahara communication failed", or "Param preload", and I cant even do anything. Currently the phone was completely dead.
If you have any idea how to fix that Please let me know! Thanks.
View attachment 5788047
Click to expand...
Click to collapse
India device or global devices
And tip
Reboot to edl
Power off the phone
And press and hold pressed the voll up and voll down
And putt in the usb cable and hold pressed the voll up and voll down
And try msm tool
V0latyle said:
Oh, specifically for the OnePlus. Good to know. I suppose I'm of absolutely no help here
Click to expand...
Click to collapse
Not only specific to OnePlus but also specific to OOS versions.
Might try to uninstall Qualcomm drivers, make sure PC driver signing is disabled. Reboot PC, then re-install latest Qualcomm drivers, re-boot PC and try again with MSM tool. The windows sound when plugging in before is the sound of a device plugged in but couldn't recognize it and threw it out of device manager. That was the reason for the TWO sounds you heard. Also try holding down on vol + - and pressing power and holding it down to try to boot into fastboot mode. If it does, flash boot boot TWRP.img and then boot into edl from there with phone connected to PC and MSM tool in start mode ready to flash as soon as device is connected.