Xiaomi Mi A2 lite bricked

Crashex

Member
Oct 19, 2015
5
1
0
25
Hello to everyone,

Yesterday I tried to install the api for the gcam but I done a big mistake. From the developer options I removed the option "enable OEM unlock" for the bootloader and on fastboot mode I relocked it. Now my mi a2 is completely bricked and I can't unlock. On the display now there is a red triangle with "The system has been destroyed" Help help help
 

InfinityXDA

Senior Member
Nov 28, 2016
158
46
38
18
∞:\Earth\UnitedStates\Missouri\Unknown
Hello to everyone,

Yesterday I tried to install the api for the gcam but I done a big mistake. From the developer options I removed the option "enable OEM unlock" for the bootloader and on fastboot mode I relocked it. Now my mi a2 is completely bricked and I can't unlock. On the display now there is a red triangle with "The system has been destroyed" Help help help
Get MiFlash

goto fastboot (power + volume down)

Recognize the device in MiFlash and download the stock rom here

extract it twice with winzip until you hit a folder

select the folder in MiFlash

Then flash it. It will take a bit to start for the first boot but you must redo the bootloader stuff and everything
 
  • Like
Reactions: cashflow67

Kineceleran

Senior Member
Dec 14, 2018
105
37
38
Hello to everyone,

Yesterday I tried to install the api for the gcam but I done a big mistake. From the developer options I removed the option "enable OEM unlock" for the bootloader and on fastboot mode I relocked it. Now my mi a2 is completely bricked and I can't unlock. On the display now there is a red triangle with "The system has been destroyed" Help help help
Oh why did you relock it?
I made this mistake before
and i solve this problem by "Test Point" method
You can solve this problem with just EDL mode.
https://www.youtube.com/watch?v=YctyUhBgp34
There is a video for how to get in to EDL mode.
https://www.youtube.com/watch?v=NkeqJwKpgm0
And there is another video.
Plug the usb cable to a PC while tweezers touching these points
 
Last edited:
  • Like
Reactions: Crashex

CarlosAG10

Senior Member
May 2, 2012
156
68
0
I think there's a way out of there just by reflashing the boot image... It should be, but I don't know if it'll work after disabling OEM in developer options ... Big mistake there.
 

kftX

Member
Jan 26, 2019
26
33
0
I think there's a way out of there just by reflashing the boot image... It should be, but I don't know if it'll work after disabling OEM in developer options ... Big mistake there.
Yeah, that's how I killed a Redmi Note 4 once, I was in a hurry so I forgot to choose the non-relock option in MiFlash and then the flash went bad, rip phone.

However I've heard that this EDL trick that was mentioned seems to do the trick, so try that OP!
 

Crashex

Member
Oct 19, 2015
5
1
0
25
Oh why did you relock it?
I made this mistake before
and i solve this problem by "Test Point" method
You can solve this problem with just EDL mode.
There is a video for how to get in to EDL mode.
And there is another video.
Plug the usb cable to a PC while tweezers touching these points
Thanks you so much. The phone now is ok! I flashed the last stock rom updated with the January fix. You saved my life. Thanks you so much?
 
  • Like
Reactions: cashflow67