Trouble with booting into EDL - Xiaomi Mi A2 / 6X Questions & Answers

Hi guys, for the last couple of days I've been trying to flash miui on my A2 with the guide that's in this forum, but can't boot into EDL mode. I have unlock the bootloader (both oem unlock and unlock_critical) but I still can't boot into EDL with any of the methods I found online. Fastboot seems to recognize the commands sent by A2 Toolkit but just leaves a blank screen with no blinking led, and the flash utility doesn't seem to recognize any phone connected (it shows an "specified is not cast" error, that also shows when my phone isn't conected). Also, it doesn't seem to show in device manager, but I do hear the "new device connected" sound that windows runs when I plug it in with this blank screen. I have reinstalled the drivers with the flashing tool, but didn't seem to change anything.
Anyway, that's what happened to me, am I missing something that needs to be done in order to boot into EDL? Im running windows 10 btw
Thanks in advance

Related

Please Help_After OTA Update Xiaomi Mi A2 died

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.

Phone got bricked randomly - QUALCOMM HS-USB QDLOADER 9008 (NEED HELP)

I was using my mi a2 and it randomly freezed, then i restarted using power button, but he didn't turned on, now it is just black screen and i can't get into bootloader mode or turn the phone on.
Bootloader was locked, never tried to unlock.
I think it got stuck on EDL mode because it shows up 'qualcomm hs-usb qdloader 9008' on device manager on windows.
Already tried to use mi flash tool to flash the last ROM, it recognize the phone but fails every time.
Neither adb or fastboot recognizes the phone.
Some errors that i had using the tool:
Failed to open the SDCC Device slot 0 partition 0 (it shows up only on version 2019.11.15.0)
Cannot receive hello packet (when i get this error, i hold the power button for a few seconds then i try again only to get the error below)
Error when flashing storsec.mbn
Can someone help me?
UPDATE
I downloaded mi flash tool 2016.08.30.0 and i can successfuly flash the rom, but still got black screen with no response.
I ve little same issue. need help too.
I have Mi A2 runnig on android8.1
but it didnt update 9.0
so I try with twrp but fail no boot anymore.
I use miFlash tool. accdently I locked phone. flashed rom didnt boot.
now I ve just fastboot mode. or open 'android one' screen and then goes black.
I try EDL mode by test point inside phone.
flash with 2018 mi Flash tool but stuck in flashing...
flash with 2016 mi Flash tool write succesful flashed afte 6min. but not boot.
I read 2 days on forums. cant find anything to do.
is there any solution?
thanks
Hi, has anyone made any progress?
Theduardds said:
I was using my mi a2 and it randomly freezed, then i restarted using power button, but he didn't turned on, now it is just black screen and i can't get into bootloader mode or turn the phone on.
Bootloader was locked, never tried to unlock.
I think it got stuck on EDL mode because it shows up 'qualcomm hs-usb qdloader 9008' on device manager on windows.
Already tried to use mi flash tool to flash the last ROM, it recognize the phone but fails every time.
Neither adb or fastboot recognizes the phone.
Some errors that i had using the tool:
Failed to open the SDCC Device slot 0 partition 0 (it shows up only on version 2019.11.15.0)
Cannot receive hello packet (when i get this error, i hold the power button for a few seconds then i try again only to get the error below)
Error when flashing storsec.mbn
Can someone help me?
UPDATE
I downloaded mi flash tool 2016.08.30.0 and i can successfuly flash the rom, but still got black screen with no response.
Click to expand...
Click to collapse
A year ago i had the same issue kinda. The only thing that worked for me was flashing mi 6x stock rom and after some trial an error it flashed and it fixed. The only problem is i have a mi 6x forever. Basically download mi 6x stock rom. Try that mi flash tool and keep hard rebooting and click flash button right after it vibrates. If lucky sometime will work and flash. If nothing try older versions of mi flash tool. Good luck.
all of you have the same problem ... you bootloop into edl mode because you have ARB4 triggered ..that means the only stock you can flash in miflash is ARB4 rom ( latest most up to date )
you also need patched programmer file since flashing ARB4 requires miui account
the fix to this problem is documented everywhere and explained lots of times ...just read ..follow this guide and one-click tool to unbrick
next time read ......a little ..
https://miui.blog/mi-6x/unbrick-mi-6x-wayne/

I can't install twrp, make a hard reset, update by OTA, nothing O.o

SOLVED
Hi there.
I had my couple's mobile rooted with Magisk and MIUI Global 10.3. Once wanted to update twrp and the issues began. Actually the mobile isn't rooted but with unlocked bootloader, apparently.
I list the issues down below:
1) Trying to install twrp with fastboot by CMD, pressing enter after the command the cursor just blinks and nothing happens. At first it showed "waiting for device", so I installed adb drivers and the mobile appeared in Device Manager. It run once up to "sending 'recovery'" but not farther. The mobile was connected in fastboot mode indeed as well as in usb debugging but couldn't activate oem unlock as it stated it as unlocked and the option was dimmed.
2) Tried to unlock the mobile with Miflash_unlock and the phone was recognized, but the tool checked the device up to 50% and then showed that it Couldn't verify the device.
3) Then I tried to make a backup of the user data and doing a Hard Reset from settings. It went forward up to reboot, so I did, then it entered in fastboot mode for a few seconds and it powered off. Rebooted the phone and it was up and running as if nothing happened. So I cannot make a hard reset.
4) I can't enter the recovery too. If pressing volume - and power on it enters in fastboot mode. With volume + and power on it does the same With recovery enter tools isn't possible either. It seems as it's been corrupted.
5) I've just tried to flash the Global_8.0 rom with MiFlash 2019.12.6.0 and on the progress line it says "echo Mismatching image and device" How? I'm sure its a Mi Mix 2 'chiron' Rom, so... Anyway, I start to flash and the tool seems to progress but it never ends. So I disconnect the phone, reboot, and it keeps untouched running as before, OMG
6) On top of that I can't update android by OTA, as it gets downloaded, then reboot, then enters fastboot mode and after few seconds it powers off as before, and powering it on afterwards shows that it couldn't be updated
So I don't know what to do next. However, the mobile runs apparently ok.
May someone lend me a hand, please?
Thank you.
SOLVED: The Xiaomi Mi MIX 2 is up and running with the last firmware installed. The issue was that, as I build a new PC lately, I connected the phone in fastboot mode to the front USB ports, which are 3.0 version, and you need a 2.0 USB port at most, causing errors in MiUnlock and MiFlash.

Fast Boot

I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
blkair445 said:
I received my new sony 1 ii and have checked and the bootloader can be unlocked and the phone can be rooted. I thought I was away to the races but I'm mystified. I can't get the phone to boot into fast boot.
I appears I have the drivers in place and the phone is recognized by the computer but no luck with fast boot.
I have searched and can't seem to find out why this is. I suspect some kind of driver issue with win10 but when I connect to the computer with the phone off and hold the up-volume nothing happens. I have also tried to boot into recovery mode and that does not work as well. Any help would be appreciated.
Click to expand...
Click to collapse
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
blkair446 said:
Thanks for the input. I have done that and am still unable to action ADB - It is a little confusing since the phone only shows the blue light and nothing else.
If I normally boot the phone it will register as an ADB device. I also find it strange that it will not boot into recovery. The android icon flashes but when you release it boots to safe mode. I assume it is a driver issue but it is not revealing its self to me . Cheers
Click to expand...
Click to collapse
The blue light is fastboot mode. There is no ui interface in fastboot for sony devices. Just a blue light and black screen.
R800x_user said:
On Sony devices you need to power off and hold volume up and plug in the USB cable. That should leave the blue LED to indicate fastboot mode. I'm not 100% sure since it's been a while since I've messed around with Sony devices
Click to expand...
Click to collapse
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
blkair446 said:
Same person but had to change user name -- more on the issue
I managed to unlock the boot loader and it seems that at every step for rooting I am running into curve balls. Windows was not working for me so I managed to unlock the bootloader with Linux and going on to the next step I had to go back to windows to find a current factory ROM.
The next issue: going back to the "how to" I am unable to located boot.xxxxx.sin in the factory ROM and the closest I could find is boot_x-Flash-ALL-2389.sin and that doesn't work.
In the boot directory all files are bootloader_X_44 and a combination of zip and sin files
Can anyone steer me through the muddy waters
The factory rom was downloaded through XperiaFirm application
Click to expand...
Click to collapse
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in https://developer.sony.com/develop/open-devices/get-started/unlock-bootloader/#unlock-code?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
jepher said:
May I know how did you unlock the bootloader? Did you use xperia 1 as your device in ?
I have already installed usb drivers and have the platform tools. But everytime I boot my device to fastboot, whether using "adb reboot bootloader" or power button + volume up, screen only shows black (led is solid blue). I did left it for a couple of minutes, nothing happened.
Click to expand...
Click to collapse
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
blkair446 said:
I unlocked my bootloader after obtaining the unlock code from sony developers I used adb/fastboot commands in linux mint. Pretty straight forward but the next step for rooting is giving me issues. Just select xperia 1 and the imei number will identify your phone -- cheers
Click to expand...
Click to collapse
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
jepher said:
Yes I followed those. But may I know how long it took you to finish the unlocking?
Install ADB/SDK drivers
Download platform tools
Plug the device
Make sure adb can see my device
Use adb reboot bootloader command
Device booted to fastboot mode
Execute the command with the unlock code
...stucked here
If I miss something. Please do let me know
Click to expand...
Click to collapse
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
blkair446 said:
I assume you are using windows and I must say I gave up trying to get win10 to work and I was stuck at the same place you are. I then switched to linux and it went a lot smoother and I didn't need all those tools as laid out in the description.
In linux you must use the phone to go into fastboot mode if you boot from computer it actually boots to a visible screen on the phone and I didn't have connection that would take the command line commands. Linux is very good because if you are missing something it will give you a link or a command line input when you execute the ADB or Fastboot command.
I have run a windows/linux dual boot desktop for a while now and I'm no expert but coming from the era of command line I can muddle through. Sorry if I can't give you more info on windows but win10 is such a pain and I find that with a lot of things linux works better. If I didn't need adobe acrobat I would not even bother with windows.
cheers
Click to expand...
Click to collapse
Yes I am using w10. Will try linux later. I have searched everywhere and stucked at the same step. Thank you.
I have managed to unlock the bootloader and root the phone. But problem is. I can't write on the root folder.
More to this I think I might have located the boot file boot_X-flash-all-2396.sin but using magisk it returns no boot image found. I see the guide says use the canary built but that seems to have been shut down, so at an impasse here and am still reaching out for help - damn op phone were never this funky
I might as well put this one out there then -- Is there anyway to flash a op 8 pro in2025 to dual sim - it's the cause of this painful trip
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
jepher said:
I was reverting my phone to unroot and locked bootloader. And it is saying that "Your Device is corrupt. It can't be trusted and will not boot" loop.
I tried flashing it using the new flasher. But after flashing, it will do SONY boot loop. If I connect it to a charger it goes back to "Your Device is corrupt. It can't be trusted and will not boot" loop.
I can't use Sony Companion since it is saying that my battery is low, and I can't charge the phone since it will just continue looping.
Do you know/have any recovery.img?
Edt: Fixed my phone. Relocked the bootloader
Click to expand...
Click to collapse
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
cd993 said:
Any chance you could post the steps to relock successfully? I presume using the fastboot commands etc though did you then just re run the command to relock the bootloader? Many thanks
Click to expand...
Click to collapse
Yes. Relock it using fastboot command.
I use ubuntu to do it. If you can run fastboot commands in windows10 lucky you.

HELP!!!!!! Any unbrick tool for cn rom?

Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...
[email protected] said:
Hey guys,
I need some assistance as I am not able to unbrick my RM3 with unbrick tool. Multiple times I have already got it worked, flashed many times, but this time I am not getting my phone started. Normally, I use the NON-EU unbrick tool, all goes well but this time, it says THIS DEVICE CAN'T BE TRUSTED, WON'T BOOT UP. After multiple tries, I tried that EU unbrick too as well, but the same result.
I think I have locked the bootloader while on CN Rom 5.14, most probably this is the only reason, I was doing some tweakings and got it bricked. Anyone here who can tell me if there is such thing named CN Unbrick tool or any other way around to get it worked. I can enter FASTBOOT and EDL Mode but recovery mode showing black screen and adb is not recognising as didn't enable USB debugging. please help...
Click to expand...
Click to collapse
I think any unbrick tool should work both EU and non EU
you must pc driver uninstall reboot pc driver install again reboot your pc and also check your port number eld mode
red magic 3 driver reinstall in may case port number change automaticly i m notice this point it will help you to start your device red magic 3

Categories

Resources