Xiaomi Redmi 9 Stuck in Bootloop and Unresponsive after TWRP Fail

Name: Xiaomi Redmi 9 Stuck in Bootloop and Unresponsive after TWRP Fail
Uploaded: 2022-01-01T10:18:08+01:00
Description: Hello, I have a problem... After a failed installation of TWRP, Xiaomi Redmi 9 went into bootloop and resets on the start screen with the word XIAOMI. I cannot enter fastboot mode or Recovery Mode (key combination Volume - Power On). It seems to work because the phone responds with vibration,...

Question

Hello, I have a problem... After a failed installation of TWRP, Xiaomi Redmi 9 went into bootloop and resets on the start screen with the word XIAOMI. I cannot enter fastboot mode or Recovery Mode (key combination Volume - Power On). It seems to work because the phone responds with vibration,...

blahfff · Accepted Answer

This model is based on the Mediatek system, so there is no EDL here, because it only applies to models with a Qualcomm processor

blahfff · Accepted Answer

All you have to do is upload the software or at least restore the original recovery. The phone should be detected in bootrom mode after connecting to the computer with both volume keys pressed. The original recovery can be restored this way using mtkclient from github. It is also possible to upload the software, but you have to manually restore each partition. Alternatively, an unauthorized service center with some equipment should be able to handle it without any problems.

blahfff · Accepted Answer

It`s normal. Bootrom mode is only available for a moment, and if nothing connects to the device, it continues. Without having my phone in front of me, not really. - you can use this, it even has a GUI now. Of course, you need to find software for your model, in the same version that you currently have on your phone - this shouldn`t be a big problem. As I suggested earlier, to start with, simply restore the original recovery this way.

leonov · Answer

Do you have USB Debugging mode turned on? You could use ADB commands. Alternatively, there is this cable

blahfff · Answer

ADB requires a phone that connects to the system. That`s not the case here. These cables only worked in Samsung. They have absolutely no use in Xiaomi.

leonov · Answer

Maybe this one, but there are others e.g. deep flash / EDL Descriptions on forums, e.g.

Kuku1125 · Answer

When the phone was still working, debugging was active... I’ve already tried with these cables... I’ve been browsing all forums for 2 weeks and looking for a solution... I can only hope that someone has had such a situation before, or they will end up on some forgotten forum and will be able to advise something... If it doesn’t work, it’s either service or sale for parts

Kuku1125 · Answer

Could you somehow guide me on how to do this? This is starting to make my head burn... I think I`ve already tried connecting the phone to the computer with all possible key combinations and, as I said, maybe Windows detected something twice, but only after 2 seconds. it was disappearing. I was thinking about reinstalling the recovery, but I don`t even know if it`s possible, because I was looking for instructions all day long and all to no avail. Because either it was an installation with EDL or Fastboot, and for some reason I don`t have any access to these functions

FranekDolas · Answer

For new MTKs, the Infinity CM2MT2 works best for me.

Kuku1125 · Answer

Well, after dealing with this MTK, there are some flashes of life and Windows regularly shows an unknown USB device for about 2 seconds. But I still can't get him to pick up the phone. After returning from work, I will try this Infinity CM2MT2 again, maybe I will take another step forward.... And so, step by step, in 2 months I will launch this phone 😁😁

Kuku1125 · Answer

emat to close, the combination of MTKClient and the guide from this video got the phone back on its feet.... Thank you all for your help.

[Solved] Xiaomi Redmi 9 Stuck in Bootloop and Unresponsive after TWRP Fail

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Post #9

Post #10

Post #11

Post #12

Topic summary