Hi,
I have a big problem and i don't really know where to ask help so i'm trying here.
So , my Mi 8 is stucked in EDL mode, I don't know how, let me explain what happened:
Yesterday, when I woke up, I took my phone and the screen was all black, I could only saw the notification bar on the top and then I got a lot of app error like "XXX had encountered a problem, send log or cancel" ( translated from french ), the phone then rebooted and was stucked on MI logo.
After ~10 min, it didn't booted so I reseted it by keeping power for 10/15s and then the phone booted properly,I saw I could download a new xiaomi.eu update , I tried to download it on my phone but it said something like "the mirroirs are busy try again later", I played some games, battery went low ( 18% ) I put it on charge and then I came back 30/40 min later and the phone was bricked :/
So here I am , I tried some things like boot in fastboot and recovery ( both didn't worked at all ( screen stay black ) ) so I tried to re-flash by EDL and there's my problem.
When I try to flash using Miflash , the flash seem to start and then I have the message "ping target via firehose" and then "write time out, maybe device was disconnected"
I was on xiaomi.eu rom, my BL is unlocked, I tried different USB ports, USB cables, computers, multiple ROM and multiple Miflash versions, I even tried the pinpoint method.
I'm starting to think that the problem is the memory who seems to be damaged :/
Can someone help me please ?
Zirocks said:
Hi,
I have a big problem and i don't really know where to ask help so i'm trying here.
So , my Mi 8 is stucked in EDL mode, I don't know how, let me explain what happened:
Yesterday, when I woke up, I took my phone and the screen was all black, I could only saw the notification bar on the top and then I got a lot of app error like "XXX had encountered a problem, send log or cancel" ( translated from french ), the phone then rebooted and was stucked on MI logo.
After ~10 min, it didn't booted so I reseted it by keeping power for 10/15s and then the phone booted properly,I saw I could download a new xiaomi.eu update , I tried to download it on my phone but it said something like "the mirroirs are busy try again later", I played some games, battery went low ( 18% ) I put it on charge and then I came back 30/40 min later and the phone was bricked :/
So here I am , I tried some things like boot in fastboot and recovery ( both didn't worked at all ( screen stay black ) ) so I tried to re-flash by EDL and there's my problem.
When I try to flash using Miflash , the flash seem to start and then I have the message "ping target via firehose" and then "write time out, maybe device was disconnected"
I was on xiaomi.eu rom, my BL is unlocked, I tried different USB ports, USB cables, computers, multiple ROM and multiple Miflash versions, I even tried the pinpoint method.
I'm starting to think that the problem is the memory who seems to be damaged :/
Can someone help me please ?
Click to expand...
Click to collapse
Download fastboot dipper images rom, and use flashall.bat method to restore the phone.
Download a fastboot images rom and unpack it twice on your desktop. ( must be unpacked) After unpacking the 2nd time you will have a folder with batch files and an images folder ( see attached )
If you are unable to access fastboot, use EDL mode. Once in EDL - verify that you are in EDL by opening control panel/system/devices/ com/ you should see port 9008 listed.
Download dipper_global_images_ROM Here is the latest fastboot rom ( AFAIK) : http://bigota.d.miui.com/V11.0.6.0....XM_20191022.0000.00_9.0_global_fe09c43d5a.tgz
It has to be a fastboot rom and not a Recovery rom
Unpack the rom twice on your desktop
You will be left with a folder and inside you will see batch files and a image folder.
With the phone connected to a USB2 port, locate and doubleclick the batch file called " Flashall.bat" ( be careful on what you click, you want flashall.bat only) This works regardless if the phone is in phone is in Recovery mode, fastboot or EDL
Flashall.bat is a batch script that will wipe your phone and restore all images, one image at a time and then finally boot to system.
You should then Setup rom
Afterwards install TWRP and root then create a full Twrp backup and save to your PC.
This way you will have a quick solution if you ever need it again in the future.
Unless you have some hardware related issue, this should work and you can go back to enjoying a working phone
Presteps.
Make sure that adb and drivers are up to date, disconnect any peripheral drivers, and be sure to use USB 2, it the steps fail try again using a usb 2 hub. I am almost certain that this is your firehose issue
Especially if the log error has this : lsusb path:"C:\MiFlash*.*\Source\ThirdParty\Qualcomm\fh_loader\lsusb.exe"
First of all I would like to thank you for giving me your time trying to help me !
I tried what you told me to do but it didn't worked, when I click on the flash_all.bat I got the error message "echo missmatching image and device" wich I tried to bypass by commenting the section of the .bat and now it's stuck on "waiting for any device"
( Before you ask it, yes it's a Mi8, I checked on the mi auth site my imei and sn )
Does the fastboot commands works on EDL mode ? ( because "fastboot device" give me an empty line )
As you said it seems like an USB or driver problem.
So I tried to test with an USB hub, I didn't had one so I tried a similar "setup " using USB extender, or "hub" available on my screen and keyboard , ofc it didn't worked , so, do you think I need to buy a "real" USB hub ?
If yes does it need to be a specifical one ( usb 2/3, X ports , etc ... ) ?
Zirocks said:
First of all I would like to thank you for giving me your time trying to help me !
I tried what you told me to do but it didn't worked, when I click on the flash_all.bat I got the error message "echo missmatching image and device" wich I tried to bypass by commenting the section of the .bat and now it's stuck on "waiting for any device"
( Before you ask it, yes it's a Mi8, I checked on the mi auth site my imei and sn )
Does the fastboot commands works on EDL mode ? ( because "fastboot device" give me an empty line )
As you said it seems like an USB or driver problem.
So I tried to test with an USB hub, I didn't had one so I tried a similar "setup " using USB extender, or "hub" available on my screen and keyboard , ofc it didn't worked , so, do you think I need to buy a "real" USB hub ?
If yes does it need to be a specifical one ( usb 2/3, X ports , etc ... ) ?
Click to expand...
Click to collapse
Okay, because you flashed a rom from a different device, that is the only explanation. You phione thinks that it is something else, and the phone should protect itself from being able to flash the wrong and yet it still happened. The good news is that there is a still a possible solution.
In the batch file "flashall" script delete these lines below
fastboot $* getvar product 2>&1 | grep "^product: *dipper"
if [ $? -ne 0 ] ; then echo "Missmatching image and device"; exit 1; fi
After deleting those lines , save the file and then try the flashall process again.
This time it should work, and your phone will be restored.
tsongming said:
Okay, because you flashed a rom from a different device, that is the only explanation. You phione thinks that it is something else, and the phone should protect itself from being able to flash the wrong and yet it still happened. The good news is that there is a still a possible solution.
In the batch file "flashall" script delete these lines below
fastboot $* getvar product 2>&1 | grep "^product: *dipper"
if [ $? -ne 0 ] ; then echo "Missmatching image and device"; exit 1; fi
After deleting those lines , save the file and then try the flashall process again.
This time it should work, and your phone will be restored.
Click to expand...
Click to collapse
Sincerly I don't think I flashed a wrong rom, each one were named "dipper", maybe I did a mistake but all the rom on my desktop are for dipper model.
As I told you on my previous answer I already tried that,
I don't find the exact line you told me but the similar one were :
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
I tried to comment those 2 lines and even delete it, the result is the same , after I re-start the flash_all.bat , the message is : "waiting for any device"
( My device is connected as "Qualcomm HS-USB QDLoader 9008" )
Just like my phone isn't connected, does fastboot commands works on edl mode ?
I'm really starting to think the ufs memory have been damaged, the consecutive app crash, the brick from nowhere , the flash who didn't work ...
If it's a dead ufs can I buy a new mi8 motherboad and change it without problem ? ( IMEI or thing like this ... )
Zirocks said:
Sincerly I don't think I flashed a wrong rom, each one were named "dipper", maybe I did a mistake but all the rom on my desktop are for dipper model.
As I told you on my previous answer I already tried that,
I don't find the exact line you told me but the similar one were :
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || echo Missmatching image and device
fastboot %* getvar product 2>&1 | findstr /r /c:"^product: *dipper" || exit /B 1
I tried to comment those 2 lines and even delete it, the result is the same , after I re-start the flash_all.bat , the message is : "waiting for any device"
( My device is connected as "Qualcomm HS-USB QDLoader 9008" )
Just like my phone isn't connected, does fastboot commands works on edl mode ?
I'm really starting to think the ufs memory have been damaged, the consecutive app crash, the brick from nowhere , the flash who didn't work ...
If it's a dead ufs can I buy a new mi8 motherboard and change it without problem ? ( IMEI or thing like this ... )
Click to expand...
Click to collapse
Try another desktop, your windows installation could be causing issues and corrupting the processing, the commands that I listed were copy pasted from dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global
You could also try using a special deep flash cable. Such as this : https://www.amazon.com/Deep-Flash-Qualcomm-Cable-Octopus/dp/B06XB76BH3
Still doesnt work? : I would spend more time time to resolve this before buying parts that you maybe do not need.
It probably is the UFS, but it's probably not damaged it could just be a partitioning problem and usually that is easily resolved with recovery. but since you dont have recovery there is always this option for worst case scenario : https://xiaomi.eu/community/threads/guide-flashing-rom-using-miflash-mi2-3.19287/page-6 Yes, it is an old post but the steps should still be applicable.
Before doing anything like what is listed in the link above try sending the images manually, one at a time
So you will use the command fastboot flash for each image : I found a post that provides more details on using this method here
Finally, if you do end up buying a motherboard, they are not nearly as expensive as I thought look My only concern would be
tsongming said:
Try another desktop, your windows installation could be causing issues and corrupting the processing, the commands that I listed were copy pasted from dipper_global_images_V11.0.3.0.QEAMIXM_20200118.0000.00_10.0_global
You could also try using a special deep flash cable. Such as this : https://www.amazon.com/Deep-Flash-Qualcomm-Cable-Octopus/dp/B06XB76BH3
Still doesnt work? : I would spend more time time to resolve this before buying parts that you maybe do not need.
It probably is the UFS, but it's probably not damaged it could just be a partitioning problem and usually that is easily resolved with recovery. but since you dont have recovery there is always this option for worst case scenario : https://xiaomi.eu/community/threads/guide-flashing-rom-using-miflash-mi2-3.19287/page-6 Yes, it is an old post but the steps should still be applicable.
Before doing anything like what is listed in the link above try sending the images manually, one at a time
So you will use the command fastboot flash for each image : I found a post that provides more details on using this method here
Finally, if you do end up buying a motherboard, they are not nearly as expensive as I thought look My only concern would be
Click to expand...
Click to collapse
Actually I tried with 5 differents pc ( 3 desktop, 2 laptop ), I'll try to find another one under windows 7 maybe it could work
Deep flash cable isn't used to enter EDL mode ? Because that's not a problem for me actually i'm stuck in edl mode here without adb or fastboot working.
The link you sended for re-partitioning use some adb command wich I can't send because as I said the phone isn't listed as device in fastboot or adb device commands.
Same goes for the "manual flash batching" each command sended are fastboot wich I don't have access :/
So, I'm not really enjoyed to buy another motherboard but with those facts I don't think I have the choice :s
Do you know If I can just swap the motherboard and boot on a "brand new phone" ? Or do I have to flash again or do something ? ( Does my mi account tied to my bricked phone will cause problem ? )
( And again I would like to thank you for your help )
Zirocks said:
Actually I tried with 5 differents pc ( 3 desktop, 2 laptop ), I'll try to find another one under windows 7 maybe it could work
Deep flash cable isn't used to enter EDL mode ? Because that's not a problem for me actually i'm stuck in edl mode here without adb or fastboot working.
The link you sended for re-partitioning use some adb command wich I can't send because as I said the phone isn't listed as device in fastboot or adb device commands.
Same goes for the "manual flash batching" each command sended are fastboot wich I don't have access :/
So, I'm not really enjoyed to buy another motherboard but with those facts I don't think I have the choice :s
Do you know If I can just swap the motherboard and boot on a "brand new phone" ? Or do I have to flash again or do something ? ( Does my mi account tied to my bricked phone will cause problem ? )
( And again I would like to thank you for your help )
Click to expand...
Click to collapse
Okay, Some people think that they are in EDL when they are not which is why I suggested the cable because it electronically forces the phone into EDL basically doing the same thing as the “test points” method. if you have confirmed 9008 in device manager under "Ports"then you are absolutely in EDL. Also, I have helped some people with Mi8's that thought that they could not access fastboot because the screen would stay black, and in fact they were actually able to enter fastboot and repair from there. My guess is that you have already tried and verified this as well.
Next, when pushing individual images to the phone, I wasn't expecting you to use the identical commands that I linked, I suggesting that you use similar commands specifically for the files that are in the images folder. I am surprised that you are having so much trouble, I had a similar issue in August and i was definitely able to flash the phone in EDL, I also could not access fastboot or recovery.
So perhaps you do have a hardware issue. Regarding a motherboard swap, I would have hoped that the experience would be similar to buying a new phone. But those boards are probably taken from a damaged mi8.
According to one of the reviewers for this board, the board was a Chinese Board that came preloaded with a Global rom. I would contact the vendor and ask for a board with a guarantee that you can unlock yourself. or at least be guaranteed to not experience issues. As long as you dont go and relock the bootloader that should suffice.
Another reviewer stated : " The board itself is in excellent condition, there was a global firmware for Android 8. It was updated by air without any problems." So it seems that in this case he could update. using his own account? Honestly, I am not sure.
Try messaging the vendor and asking Worst case, you can choose not to use MiCloud by using the 4 corners method.
There are other options too such as using the MandFx Rom which unlocks theme store and requires no sign in. This guy is great and I have use his roms many times over the past few years including a couple of months ago. He releases updates 2 days before Xiaomi.EU http://www.manosp.com/mandfx/dev/ But with his roms you have to install Google services on your own, it's no big deal if you use Play Services installer ver 3.
Related
Hi,
Last Sunday (5) my phone turns off with 25% battery and just don´t turn on.
I was with the stock Oxygen OS.
Now when i turn it on, the oneplus logo appears and the next "screen" that should be the android or any other OS loading, just don´t appear. It just go to black and turn off.
Reading the Threads here about "OP3T Bricked" they all requests to hold volume up, and connect the usb cable.
The problem is when i do it, the driver just pop up at Device Manager List, and few seconds later it disappears.
(Try it using 4 different computers (Desktop win7 , laptop win7, laptop win 10 and desktop winxp) and 2 original OP cables.)
I had read a lot of informations that you share here in forum, but no tips helps to solve this issue.
So i contact the OnePlus support, they give me some links to download 2 encrypted files that looks like the files you guys shares here (One is the driver and the other is some kind of unbrick tool called MSM).
They connect at my computer and as soon they see that my driver just pop up and disappear, they stop the process and said to me to send the device to one support center.
Probably i will do it, but first i want to guarantee that its nothing i can do here.
So I try to reach my phone throw ADB and fastboot commands.
When at the screen of Fastboot I have some information about the phone and the last line said:
DEVICE STATE - LOCKED
using the command adb devices, we don´t find anything.
using fastboot devices, my device is listed by the serial number.
Should be possible to recover it using fastboot commands ?
There is a way to analyze my phone throw fastboot commands? Something like "all hardware is ok", like the memory, battery, etc ?
Best Regards
I have encountered the same issue while I was playing around with a beta oreo rom the name of which I wouldn't not want to mention here. Got my phone bricked and it wouldn't boot to recovery. Only fastboot was accessible so what I did was just flash the blusaprk v45 recovery and after booting I was finally successful in booting my phone into recovery where I wiped system, data, cache and dalvik without internal storage and flashed a nougat rom. Thankfully I was able to revive my phone and that solved my issue.
UPDATE:
I try to use the fastboot commands, but to do it i must use "fastboot oem unlock"
And guess what?! i can´t ...
FAILED (remote: oem unlock is not allowed)
finished. total time: 0.023s
Click to expand...
Click to collapse
So a lot of answer for the people who get this fail is to use the MSM tool .....
Any tips ?
Have you read THIS thread? Try to follow exactly those instructions...
jonsat said:
Have you read THIS thread? Try to follow exactly those instructions...
Click to expand...
Click to collapse
Hi Jonsat,
Yes, i tested and as i said, i can´t do it because the driver don´t still at device manager list.
So, the problem was solved, i need to use the OnePlus Support and converge them to use the files like "my method":
The Regular method is:
1) Hold volume +
2) When holding, plug the phone at PC
3) The device should appear at device manager, so you can run tools like MSM
This method does not work for me because my device doesn't still at device manager list, it just pops up and disappears.
So to make it work i need to:
1) Turn off the phone
2) Hold power + Volume +
3) Plug the phone
4) The phone should start with fastboot menu
5) Select recovery mode
6) hold volume +
Now the driver still on device list.
Using this solution, the files that we see here in forum does not work.
Need to use the files from OnePlus Support, MSM3.08 + OnePlus3T_A56(A57, or newer) + Driver Qualcomm signed 24/04/2013.
Thanks you
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
jonsat said:
Glad that you solved! Surely your accurate description of correct procedure will be useful for other people.
Click to expand...
Click to collapse
Glad to help
On Saturday appeared an OTA update to do on my mi A2 but after installed and restarting it died. It does not enter recovery mode and the screen is always on with android one bootscreen logo.
PS: I never flash the phone and i never change anyting in the system of the phone.
The only response that i have in the phone is enter in it Fastboot menu. I read some threads and untill now i cant fix my phone.
I will try to explain what i do:
I've tried using this tool https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585.
I try option 3 (Unbrick/Revert to Stock/Force update and the program tell me to unlock the bootloader.
When i tried to unlock bootloader by option 1 and then 1, 2 and 3 ( Unlock flashing critical, unlock OEM , unlock flashing ) the programs says: Failed Unlock is not allowed.
Then i try the response 9 to this thread https://forum.xda-developers.com/mi-a2/help/impossible-flashing-xiaomi-mi-a2-t3837565 to try unlocked the bootloader
But i have the same response ( Flashing Unlock is not allowed )
I read and i try but i cant unbrick my phone, someone can help?? Thanks
We are in the same boat buddy, the same thing happened to the phone of my wife.
It *sounds* like the update failed, and normally that would mean it would switch the slot back to the one that was working and boot that.
But you've tried a bunch of options from some tool, I've no idea what it did, as the tool doesn't tell you what commands it's doing.
I'd suggest to go to fastboot and see if you can tell which slot is active, then switch it to the other slot, then do fastboot reboot and cross your fingers
I have the same problem (for other reasons, but exactly the same problem). You can also try "fastboot oem edl", but it did not work for me, so I suppose you have little chance for it to work.
I have been searching and it looks like there are some "deep flash cables" that can make the phone enter edl mode to flash it using mi flash tool. Maybe these could work for us. There is apparently other way to enter edl mode, but it requires opening the phone (that I do not want to do) to short two test points.
I cant enter revorymode only fastboot mode. But when in fastbootmode my connected pc cant even find the phone. Im going to return the phone.
I have the same problem, I have this edl cable but so far no luck.
Do not realy k Ow how to use.
Are you sure it was the OTA update that bricked your phone? That Treble system isn't just there for the kicks, its there to prevent serious issues like these.
I'm stucked on fastboot, I don't want to open my phone. Could anyone help us? I already tried a lot of things, my computer doesn't recognize my mobile when is on fastboot mode. I already tried to install a lot of drivers or try to use differents adbs.
Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.
joachimvadseth said:
Just bought a used Mi A2 from a guy. He dosent know what Android version it is and its probably locked. Ive been out of the Android game for many years now, but managed to install ADB and Fastboot on my Mac.
The problem is that the device is boot looping on the Android One logo. Managed to get into Fastboot, and the device shows up in ./fastboot devices. Tried to run this quickie, but only get a "Device is already locked!" message.
So please, point me in the right direction as both the Internet and forums here are loaded with information.
In the end I would like to have a custom ROM, LinageOS or something maybe.
Thanks in advance.
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-flash-custom-roms-stuff-t3876375
1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")
Aerobatic said:
1st try to reboot numerously with external power On (if there is a valid Android One ROM in one of two slots, sooner or later bootloader is to boot into this valid ROM).
In case phone does not have a valid Android One ROM, then next step would be MiFlash'ing via EDL (search for TestPoint Guide in "Guides, ....")
Click to expand...
Click to collapse
Like just boot loop it or hold the power to reboot?
I think the EDL pinout opiton is the way to go after some searching, but Im in a desperate need of a torx driver..
joachimvadseth said:
Like just boot loop it or hold the power to reboot?
Click to expand...
Click to collapse
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....
Aerobatic said:
Some people reported that phone rebooted just itself while bootlooping with external power, others recommended to enter fastboot mode and reboot, others recommended to enter stock recovery mode (note that there is a gotcha of "no command" -> press "Power" and then "Vol-") and then "try again: ....
Click to expand...
Click to collapse
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.
joachimvadseth said:
In Fastboot the device only displays "fastboot", no options what so ever. Tried powering on the device without power cable 20 times and no go, boot looped on external power for about 10 minutes, no go.
Click to expand...
Click to collapse
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.
Aerobatic said:
Sure there is no options in fastboot mode, "enter fastboot mode and reboot" means just that -> enter fastboot mode and then reboot (either long-pressing power on phone or with "fastboot reboot" command from PC.
I gave you clues, please don't tease me to dictate step-by-step, I do not own your phone.
Click to expand...
Click to collapse
Ye sure, thats fine mate
did 'fastboot reboot' about 10 times now and still no go.
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.
joachimvadseth said:
Found a Xiaomitool for macOS that has an option for "unbrick my device", but need the previous owners Mi account probably, so Ive asked if he did have a Mi account.
Click to expand...
Click to collapse
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)
Aerobatic said:
Most probably that's a false path, as MiFlash, Mi Account, Mi Unlock and other such stuff are for owners of "native" Xiaomi MIUI phones, while Mi A2 boarding Android One is regarded as stepchild. Better search for Android One solutions (in these forums of in developer.android.com)
Click to expand...
Click to collapse
Maybe. I think the phone is stock, just bricked after some update.
Just need to get the bloody torx driver!
EDIT: when I do manage to find a tiny tiny torx driver and open up the phone, disconnect the battery a bit, connect it back up, and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?
Yes I have same issue, I dont understand, why Xiaomi dont do anything with this ridiculous problem, I dont login with mi account because no paid attention to that, and when I install this update the phone get in bootloop
joachimvadseth said:
..., and its time to connect the two EDL pins, how long do I hold? USB cable plugged in?
Click to expand...
Click to collapse
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Onilink90 said:
..., and when I install this update the phone get in bootloop
Click to expand...
Click to collapse
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.
Aerobatic said:
Disclamer: Have not done it myself, but according to numerous sources the needed Steps (here with Windows PC) are:
1. Open (partially disassemble) Phone to reach 2 contact Test Point spots
2. Connect stock USB cable to USB2.x port on MB of PC, but not to phone, start Device Manager (to see that no USB-phone-related devices are connected and later to see that phone will be connected in EDL)
3. Download desired stock fastboot ROM https://forum.xda-developers.com/mi-a2/how-to/fastboot-xiaomi-mi-a2-fastboot-images-t3824849 and MiFlash, start MiFlash selecting ROM
4. Span the two contacts with something metal and in this state connect USB cable to phone; Device Manager must show newly connected device detected, then contacts may be open
5. Press "Refresh" in MiFlash, same new device must be displayed
6. MiFlash -> clean all, MiFlash -> flash
7. Assemble phone back and reboot
MHO Notes:
a. when EDL/TestPoint method was forced due to soft-bricking, after unbricking it is better to: (1) fully unlock phone and (2) clean-reflash stock ROM via fasboot
(Reason: this particular specimen is subject to OTA soft -bricking)
b. if EDL/TestPoint method fails with Pie (10.0.17.0 or 10.0.2.0), retry using Oreo 9.6.17.0 or 9.6.9.0.
---------- Post added at 01:01 PM ---------- Previous post was at 12:52 PM ----------
Xiaomi is just repacking Google's Android One updates, and, obviously, does not spend much money for testing OTAs (as AndroidOne phones are not their main market items). From the other hand, Google's Android One A/B Slots feature was developed for so called friction-less ( muhaha ) reverting to previously working ROM when updated ROM fails to boot. So, an Android One phone bootlooping after OTA MUST reboot to previous version of ROM sooner or later (supposed to be 7 retries), sure if phone is not compromised / tampered by previous user actions.
Click to expand...
Click to collapse
Managed to get hold of a torx set - phone is now open, battery disconncted. USB-C cable ready (dont have USB-A-C, only USB-C-C). Installed MiFlashTool on my PC and tried to get hold of the drivers. MIFlash is giving me a hard time whineing about drivers. Giving me a erorr message, something about JIT-debugging. Only got it in norwegian.
Edit: managed to flash the stock ROM I think. Fuzzed around a bit with the qualcom driver. Now I have a white screen with a rainbow passing over it..
Edit 2: and we're there! MIUI is in - now time to get rid of it!
Edit 3: think I managed to flash TWRP now - do I need root? Can I just flash a Pixelexperience ROM now or do I need to do something else? Used the Android 9 fastboot image earlier, if that has anyting to do with anything.
Good day everybody
Straight to the point. I tried to flash a different rom, EU version of MI6X MIUI on my device and suddenly, at the reboot after the flash, the screen remained black.
Strange thing is that the device is still detected through usb on my pc, even on MiFlash its detected. But i cannot do anything, tried flashing a rom with Miflash but i get Catastrophic Error!
Please someone help me i dont want to change this phone!
Thank you so much!
Edit: after researching, i seem to be stuck in a useless EDL mode. My pc can detect the phone (Qualcomm 9008), but MiFlash cannot flash anything. The flash starts and based on the version of MiFlash im using gets stuck after a couple of seconds. for a different reason (Authentication on 2018 version, Send configure command on 2015 version) I dont understand. Please help
Marduk666 said:
Good day everybody
Straight to the point. I tried to flash a different rom, EU version of MI6X MIUI on my device and suddenly, at the reboot after the flash, the screen remained black.
Strange thing is that the device is still detected through usb on my pc, even on MiFlash its detected. But i cannot do anything, tried flashing a rom with Miflash but i get Catastrophic Error!
Please someone help me i dont want to change this phone!
Thank you so much!
Edit: after researching, i seem to be stuck in a useless EDL mode. My pc can detect the phone (Qualcomm 9008), but MiFlash cannot flash anything. The flash starts and based on the version of MiFlash im using gets stuck after a couple of seconds. for a different reason (Authentication on 2018 version, Send configure command on 2015 version) I dont understand. Please help
Click to expand...
Click to collapse
if it is in EDL you are in luck .
follow this guide :
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unbrick-arb-edl-t3846426
KevMetal said:
if it is in EDL you are in luck .
follow this guide :
https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unbrick-arb-edl-t3846426
Click to expand...
Click to collapse
Hey thanks!
But i already tried this, with no luck. Miflash doesnt allow me to flash anything. Can you maybe suggest why?
Marduk666 said:
Hey thanks!
But i already tried this, with no luck. Miflash doesnt allow me to flash anything. Can you maybe suggest why?
Click to expand...
Click to collapse
i can only tell if you can tell me exactly your error
KevMetal said:
i can only tell if you can tell me exactly your error
Click to expand...
Click to collapse
On MiFlash 2018 for example, i get the Not Authorized to Download error.
Maybe the fact that i tried to flash a global rom is the problem?
Try to install twrp , and flash hex kernel , and them flash EU rom, if is not possible , try to flash vía TEST POINT
Enriquecalong said:
Try to install twrp , and flash hex kernel , and them flash EU rom, if is not possible , try to flash vía TEST POINT
Click to expand...
Click to collapse
That is the point. Its already in EDL mode, and my pc sees the phone. But Miflash doesnt allow me to flash because of authorization.
Marduk666 said:
On MiFlash 2018 for example, i get the Not Authorized to Download error.
Maybe the fact that i tried to flash a global rom is the problem?
Click to expand...
Click to collapse
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..
KevMetal said:
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..
Click to expand...
Click to collapse
So i tried again with this release V10.3.6.0.PDCCNXM_20190816.0000.00_9.0_cn, with multiple different miflash builds, same error. Tried patching the rom and not. Nothing worked, same edl authentication problem.
I believe, pretty sure, this is the build that bricked the phone: xiaomi.eu_multi_MI6X_8.6.28_v10-8.1
Maybe it can help you understand better? Also, how do i determine which is the highest ARB build available?
Thank you so much for the help!
KevMetal said:
that error is because of your ARB .. DOwnload the latest rom with highest ARB level ...like explained in the guide
if you have latest rom with highest ARB level but still get errors start trying all different versions of Miflash ..I tried three or four before I found one which worked ..
Click to expand...
Click to collapse
Found out how to get the ARB level, but still, i think i stuck on ARB4 and even if i flash an ARB4 rom, which i tried, i just get the same error. Really dont now what to do.
Marduk666 said:
Found out how to get the ARB level, but still, i think i stuck on ARB4 and even if i flash an ARB4 rom, which i tried, i just get the same error. Really dont now what to do.
Click to expand...
Click to collapse
you need to download and try many different versions of Miflash
---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------
Marduk666 said:
So i tried again with this release V10.3.6.0.PDCCNXM_20190816.0000.00_9.0_cn, with multiple different miflash builds, same error. Tried patching the rom and not. Nothing worked, same edl authentication problem.
I believe, pretty sure, this is the build that bricked the phone: xiaomi.eu_multi_MI6X_8.6.28_v10-8.1
Maybe it can help you understand better? Also, how do i determine which is the highest ARB build available?
Thank you so much for the help!
Click to expand...
Click to collapse
did this brick happen when you wanted to change from jasmine to wayne ?
the error you are getting is your phone was stuck in EDL too long ...if you wait for more than 10 seconds you get error ..
open your phone manually amd enter edl again with test point
change to Miflash amd flash but dont wait longer than few seconds
also try with QFIL ...sometimes it will work when Miflash has timeout error
and every error is different ..if you dont tell me the error i can not say ..if you bricked with the 8.1 rom you dont have bad situation .. low ARB ..or if you used conversion zip you wont have ARB and your problem is you are too long in Edl mode
try to enter fastboot by holding power and volume down for very long time ..
if it doesnt work your only way is test point ..im sure you dont want that problem but it is all
explain your errors better if you want success ...if you go to fastboot see if computer will listen to command
fastboot oem edl
try the flashing again .....
look below
KevMetal said:
you need to download and try many different versions of Miflash
---------- Post added at 02:41 PM ---------- Previous post was at 02:37 PM ----------
did this brick happen when you wanted to change from jasmine to wayne ?
the error you are getting is your phone was stuck in EDL too long ...if you wait for more than 10 seconds you get error ..
open your phone manually amd enter edl again with test point
change to Miflash amd flash but dont wait longer than few seconds
also try with QFIL ...sometimes it will work when Miflash has timeout error
and every error is different ..if you dont tell me the error i can not say ..if you bricked with the 8.1 rom you dont have bad situation .. low ARB ..or if you used conversion zip you wont have ARB and your problem is you are too long in Edl mode
try to enter fastboot by holding power and volume down for very long time ..
if it doesnt work your only way is test point ..im sure you dont want that problem but it is all
explain your errors better if you want success ...if you go to fastboot see if computer will listen to command
fastboot oem edl
try the flashing again .....
Click to expand...
Click to collapse
Ok so, ill retry explaining
I was on a CHINA Wayne MI6X originally, unlocked bootloader and TWRP. It was only updated through OTA and never flashed any custom rom before.
Then, i tried through TWRP to flash this build xiaomi.eu_multi_MI6X_8.6.28_v10-8.1, which is a EU rom, think it is A2 rom and the devices reboot to a black screen, EDL mode.
After, i tried flashing many different versions of WAYNE CHINA roms through different builds on MiFlash but none worked. MIUI 10, 11, even 9 but always get EDL AUTHENTICATION error.
So, CHINA to EU to EDL bricked phone.
Now, i tried rebooting to fastboot holding for a long time VOL- POWER button but adb doesnt see the phone, i think im still in EDL mode, because device managaer sees it as QUALCOMM 9008.
Also, now on MiFlash 2014 i get Error loading type library/DDL. (0x80029c4a: wait port ready to use 9)
Same on MiFlash 2015 and 2016.
On MiFlash 2018 i get EDL AUTHETICATION error.
Same o Miflash 2017.
Let me know if you understanded better, still, thank you again!
Marduk666 said:
Ok so, ill retry explaining
I was on a CHINA Wayne MI6X originally, unlocked bootloader and TWRP. It was only updated through OTA and never flashed any custom rom before.
Then, i tried through TWRP to flash this build xiaomi.eu_multi_MI6X_8.6.28_v10-8.1, which is a EU rom, think it is A2 rom and the devices reboot to a black screen, EDL mode.
After, i tried flashing many different versions of WAYNE CHINA roms through different builds on MiFlash but none worked. MIUI 10, 11, even 9 but always get EDL AUTHENTICATION error.
So, CHINA to EU to EDL bricked phone.
Now, i tried rebooting to fastboot holding for a long time VOL- POWER button but adb doesnt see the phone, i think im still in EDL mode, because device managaer sees it as QUALCOMM 9008.
Also, now on MiFlash 2014 i get Error loading type library/DDL. (0x80029c4a: wait port ready to use 9)
Same on MiFlash 2015 and 2016.
On MiFlash 2018 i get EDL AUTHETICATION error.
Same o Miflash 2017.
Let me know if you understanded better, still, thank you again!
Click to expand...
Click to collapse
ok man i think you made a big mistake flashing that package because it locked your bootloader ( i think ) ....
if the computer can see your phone as qualcomm9008 it is in EDL mode
you can save your phone but the authentication error ..could be ARB or locked bootloader ..
but anyway your best and ONLY option now is to get android 10 .zip for Wayne ...latest update for MIUI .. then
follow the instructions in the unbricking thread i sent you ..unzip ..search for folder in MIFLASH ..
-download QFIL flasher ..install and run AT SAME TIME
- select the choose port manually option and leave window open
( so three windows open .. miflash ( ready ) ... QFIL with sekect port open )
- then connect your usb cable to computer ( not phlone )
- get a paperclip and open it and fold it in half to look lkke tweezers
- then on another phone or computer follow video on how to open phone and do test point ( you will hold the twi points of the paperclip on two points in the phone )
- while holding the pin on the points insert usb to phone with free hand
- look at the select port manually window of QFIL ...when you see a device appears here let go of pin ..
now say okay to close sekect port window so it closes ..
- on Miflash press " refresh " then "flash" QUICKLY ..dont wait longer than 10 sec
- it will start to flash
*to opem your phone you need a guitar pick to push between the screen and body ...also special screw driver ( buy on Amazon ) to remove screws you see in video ..
# the reason is your phone has been too long in EDL to flash anymore ..so if you cant exit and enter EDL withbuttons or fastboot you ONLY have one option and that is testpoint
#that is why i said it must in 10 sec after you enter EDL that you flash or you will just have more errors everytime
***then you must just continue to enter and exit tesrpoint using my technique until one copy of Miflash will finish without error .BUT KEEP IN MIND ..everytime you fail you need to start over bevause too much time passed since you were in EDL
******dont lose hope beause miflash will accept and flash the officiak rom ARB4 ... if you find the right miflash version amd start flashing before EDL timeout
good luck bro go watch testpoint video and search for a guitar pick and screwdriver
KevMetal said:
ok man i think you made a big mistake flashing that package because it locked your bootloader ( i think ) ....
if the computer can see your phone as qualcomm9008 it is in EDL mode
you can save your phone but the authentication error ..could be ARB or locked bootloader ..
but anyway your best and ONLY option now is to get android 10 .zip for Wayne ...latest update for MIUI .. then
follow the instructions in the unbricking thread i sent you ..unzip ..search for folder in MIFLASH ..
-download QFIL flasher ..install and run AT SAME TIME
- select the choose port manually option and leave window open
( so three windows open .. miflash ( ready ) ... QFIL with sekect port open )
- then connect your usb cable to computer ( not phlone )
- get a paperclip and open it and fold it in half to look lkke tweezers
- then on another phone or computer follow video on how to open phone and do test point ( you will hold the twi points of the paperclip on two points in the phone )
- while holding the pin on the points insert usb to phone with free hand
- look at the select port manually window of QFIL ...when you see a device appears here let go of pin ..
now say okay to close sekect port window so it closes ..
- on Miflash press " refresh " then "flash" QUICKLY ..dont wait longer than 10 sec
- it will start to flash
*to opem your phone you need a guitar pick to push between the screen and body ...also special screw driver ( buy on Amazon ) to remove screws you see in video ..
# the reason is your phone has been too long in EDL to flash anymore ..so if you cant exit and enter EDL withbuttons or fastboot you ONLY have one option and that is testpoint
#that is why i said it must in 10 sec after you enter EDL that you flash or you will just have more errors everytime
***then you must just continue to enter and exit tesrpoint using my technique until one copy of Miflash will finish without error .BUT KEEP IN MIND ..everytime you fail you need to start over bevause too much time passed since you were in EDL
******dont lose hope beause miflash will accept and flash the officiak rom ARB4 ... if you find the right miflash version amd start flashing before EDL timeout
good luck bro go watch testpoint video and search for a guitar pick and screwdriver
Click to expand...
Click to collapse
Thank a lot man, really! But i DID IT! Following this guide! https://miui.blog/mi-6x/unbrick-mi-6x-wayne/
Now my phone works again, thank you a lot still, for you patience!
Marduk666 said:
Thank a lot man, really! But i DID IT! Following this guide! https://miui.blog/mi-6x/unbrick-mi-6x-wayne/
Now my phone works again, thank you a lot still, for you patience!
Click to expand...
Click to collapse
ok good work it is a good guide and it will help other people if they have trouble finding modified programmer files or connecting the phone and flashing quickly enough
here the difference was that i assumed but forgot to remind you to use the patched programmer files not to be rejecting but it was also included in the post of other XDA guy :good:
Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English
Hi if you can open bootloader, flash stock rom
The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse
RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account