Hardware issue in my Mi 11 Pro


Franch

Members
Jan 21, 2022
76
20
Hi
After updating stable ROM 13.0.13 over A12 in my Mi 11 Pro, my device suddenly died. Hardbricked, no signal, no fastboot. No sound or vibration when connecting to PC. Even no sound or light of charging when connect to charger.
After trying to fix by software with test points (via Telegram), they told me that it was a hardware issue (motherboard damaged).
It can not be repaired, and a new motherboard is too expensive.

I guess this issue was caused by new type of updating (13.0.13 was first TWRP update, after several fastboot ones)

Anybody here having this problem?
 

ingbrzy

Xiaomi.eu ROM leader
Staff member
Feb 11, 2012
11,040
322
Strange..
ROM version 13.0.13 has more than 7k downloads..
1664769759083.png



So please explain step by step what you did and we will tell you where you broke it..
 
  • Like
Reactions: Tecalote

Franch

Members
Jan 21, 2022
76
20
Strange..
ROM version 13.0.13 has more than 7k downloads..
View attachment 44251


So please explain step by step what you did and we will tell you where you broke it..
My device is Mi 11 Pro, and was bought in January 2022. Since then, I was using Android 12 over Stable ROM (13.0.9 first, 13.0.12 later). Updated by fastboot.
When 13.0.13 Stable ROM was released, it was the first TWRP update for this device. I installed TWRP and I update to 13.0.13.
The process was right, my device rebooted properly. I was checking this new ROM for one or two minutes, and suddelny screen turned to black.
I tried to turn it on again, but there was no response. No fastboot, no light or sound when connecting to PC. I tried to combine buttons in all ways (on + vol. up, on + vol.down, ...). No success. Hard brick.

I contacted a Telegram group to fix it. I put my device in test points mode (opening back cover), then PC detected. But no flashing ROM was possible. I was told that there was a hardware issue (motherboard damaged).
I went to a physical repair shop. Same diagnosis, motherboard memory damaged.
I think I had bad luck, and hardware was defective from the begining. But it failed just after new ROM updated via TWRP. Because of that, I ask for anyone more with this issue.
 

Interviewer

Members
Jul 5, 2021
24
15
@Franch Which version of TWRP exactly did you use?
My case is different. I install the recommended twrp and update to the new rom, and everything was fine for at least 3 weeks, until few days ago. There is a chance that my device problem is only a hardbrick and not hardware issue?
 

Franch

Members
Jan 21, 2022
76
20
My case is different. I install the recommended twrp and update to the new rom, and everything was fine for at least 3 weeks, until few days ago. There is a chance that my device problem is only a hardbrick and not hardware issue?
Have you tried to repair it? You can do a "test points" checking with device connected to PC via USB. If device is detected, a new ROM can be flashed in EDL mode.
I did it, but flashing was not possible: motherboard memory damaged.
To do the "Test point" checking, back cover must be opened. It's not easy but it can work...