How can I recovery the bricked Xiaomi Mi A2 ?

[fabio-filho]

Everything begun after a simple reboot and the phone didn't start again, even it's was working well with a custom ROM before and I didn't do anything.

Then, I believe I made some mistake, because I tried to recovery it flashing a stock ROM (jasmine_global_images_V10.0.13.0.PDIMIXM_9.0), with XiaomiMiFlash app,
but the app didn't accept the flash because of the if bellow:

So, it's now when I think that I made something bad. I removed the line with red arrow, because I thought it wouldn't be a serious problem. After that, the phone does not start anymore. Then, I remove the battery and I tried to make a manual connection after disconnected the battery, like the guy bellow, to flash a ROM (check this video), but it didn't work:

Now, every time I try to flash I got this:

When I open the Windows Device Manager, I see this:

I already ave tried these versions:

And, when I try to execute some command through fastboot, like before (flashing or boot the twrp image), I got
failed because the device was not found and I cannot enter on EDL mode again since my last stupid try.

Is there anything that I can do?

 

[sz.hatef]

Everything begun after a simple reboot and the phone didn't start again, even it's was working well with a custom ROM before and I didn't do anything.

Then, I believe I made some mistake, because I tried to recovery it flashing a stock ROM (jasmine_global_images_V10.0.13.0.PDIMIXM_9.0), with XiaomiMiFlash app,
but the app didn't accept the flash because of the if bellow:

View attachment 27234



So, it's now when I think that I made something bad. I removed the line with red arrow, because I thought it wouldn't be a serious problem. After that, the phone does not start anymore. Then, I remove the battery and I tried to make a manual connection after disconnected the battery, like the guy bellow, to flash a ROM (check this video), but it didn't work:


View attachment 27235


Now, every time I try to flash I got this:
View attachment 27236


When I open the Windows Device Manager, I see this:

View attachment 27237


I already ave tried these versions:

View attachment 27238

And, when I try to execute some command through fastboot, like before (flashing or boot the twrp image), I got
failed because the device was not found and I cannot enter on EDL mode again since my last stupid try.

Is there anything that I can do?

What is your ARB version?!
And which kind of USB do you use to connect it to the PC? USB2 or USB3?!

 

[fabio-filho]

@sz.hatef ,
I think it's ARB version 4 and the USB port is 2.0 .

 

[sz.hatef]

@sz.hatef ,
I think it's ARB version 4 and the USB port is 2.0 .

If you have ARB4, flashing Jasmin Roms (A2 Roms) lead you to breaking your phone, as what you have right now.
You need just forget Android One and flash Wayne Roms (6X Roms) and use MIUI for now on.

You can find plenty guidelines to recover a brake converted A2 to 6X (since you have ARB4 it means your phone is converted to 6X).

 

[fabio-filho]

@sz.hatef ,
I'm trying different wayne versions.
I followed this tutorial and I'm not getting success yet:

[GUIDE][MI A2 / MI 6X] How to unbrick from ARB (EDL state)

Salve! As you may know, Xiaomi enabled ARB (Anti-Roll Back) for Mi 6X starting with MIUI 10. It means that if you try to downgrade from MIUI 10 to MIUI 9, your device will enter in a brick EDL state and the only way to recover it is to send it to...

forum.xda-developers.com

Even the flash got success after five minutes, but the cellphone does not wake up.
I'll try a PixelExperience right now.

Is there any chance to hardware broken in this case?

 

[sz.hatef]

@sz.hatef ,
I'm trying different wayne versions.
I followed this tutorial and I'm not getting success yet:

[GUIDE][MI A2 / MI 6X] How to unbrick from ARB (EDL state)

Salve! As you may know, Xiaomi enabled ARB (Anti-Roll Back) for Mi 6X starting with MIUI 10. It means that if you try to downgrade from MIUI 10 to MIUI 9, your device will enter in a brick EDL state and the only way to recover it is to send it to...

forum.xda-developers.com

Even the flash got success after five minutes, but the cellphone does not wake up.
I'll try a PixelExperience right now.

Is there any chance to hardware broken in this case?

I don't think that here a Hardware failure would be a case, it is really unlikely that you can manage to break your phone permanently.

BTW after flashing Android 9 there will be a huge chance that your TWRP won't works. (You need to use PitchBlack instead)

And after triggering ARB4 you can only use MIUI 10+ (no MIUI 9 and no Android One)

 

[AndrielFR]

If you have ARB4, flashing Jasmin Roms (A2 Roms) lead you to breaking your phone, as what you have right now.
You need just forget Android One and flash Wayne Roms (6X Roms) and use MIUI for now on.

You can find plenty guidelines to recover a brake converted A2 to 6X (since you have ARB4 it means your phone is converted to 6X).

Hello, I'm in the same situation as him, MiFlash always gives the error "can not read from port COM3" and when I try to flash a Wayne ROM, MiFlash asks for an authorization that at the moment, I don't have, can you help me?

 

[sz.hatef]

Hello, I'm in the same situation as him, MiFlash always gives the error "can not read from port COM3" and when I try to flash a Wayne ROM, MiFlash asks for an authorization that at the moment, I don't have, can you help me?

Hi, I am afraid that hear you encounter a problem over flashing,

About the first error I suggest you to use an USB2 port not 3. If your PC hasn't got any, use a hub instead ( apparently not an USB3 one )

For the second one you can find a solution, I think; I have never experienced such a problem with my account, and my account is a normal one, so I do assume that you can manage to solve that too.

I hope to hear you soon that every thing is safe and sound again.

Gesendet von meinem Redmi Note 8 mit Tapatalk

 

[AndrielFR]

Hi, I am afraid that hear you encounter a problem over flashing,

About the first error I suggest you to use an USB2 port not 3. If your PC hasn't got any, use a hub instead ( apparently not an USB3 one )

For the second one you can find a solution, I think; I have never experienced such a problem with my account, and my account is a normal one, so I do assume that you can manage to solve that too.

I hope to hear you soon that every thing is safe and sound again.

Gesendet von meinem Redmi Note 8 mit Tapatalk

I already use USB 2.0 port :/, on the account, I am not authorized to download

 

[Strelock07]

Hi, I am afraid that hear you encounter a problem over flashing,

About the first error I suggest you to use an USB2 port not 3. If your PC hasn't got any, use a hub instead ( apparently not an USB3 one )

For the second one you can find a solution, I think; I have never experienced such a problem with my account, and my account is a normal one, so I do assume that you can manage to solve that too.

I hope to hear you soon that every thing is safe and sound again.

Gesendet von meinem Redmi Note 8 mit Tapatalk

May work with usb 2.0 front ports of my desktop? I'm running W10pro. I'm with the same problem https://xiaomi.eu/community/threads/mi-a2-lite-persist-corrupted.55738/

 

[sz.hatef]

May work with usb 2.0 front ports of my desktop? I'm running W10pro. I'm with the same problem https://xiaomi.eu/community/threads/mi-a2-lite-persist-corrupted.55738/

Just try it, it should work work for you.

Gesendet von meinem Redmi Note 8 mit Tapatalk

 

[Strelock07]

Just try it, it should work work for you.

Gesendet von meinem Redmi Note 8 mit Tapatalk

Hi, below Supported API 3 shows:
Failed to clear BCB message: failed to fsync /dev/block/bootdevice/by-name/misc: Operation not permitted

Pretty sure this is why I can't sync to pc nor wipe factory reset