logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

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

Kuku1125 29487 11
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
Report a violation of the law
| New topic
  • #1 19793151
    Kuku1125
    Level 5  
    Posts: 28
    Rate: 4
    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, but that`s where it ends) After connecting to the PC, it`s also a bit of a bummer because in 99% of the connection attempts, the computer doesn`t see anything (Maybe a new device "Mediatek COM3" appeared about 3 times, but it disappeared after 2 seconds)
    Does anyone have any advice? Or is the phone a complete brick and there`s nothing you can do about it?
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 19793490
    blahfff
    Level 41  
    Posts: 4929
    Help: 1030
    Rate: 1281
    leonov wrote:
    Do you have USB Debugging mode enabled? You could use ADB commands.


    ADB requires a phone that connects to the system. That`s not the case here.

    leonov wrote:
    Alternatively, there is this "cable" https://forum.xda-developers.com/t/download-mode-usb-cable.1653042/


    These cables only worked in Samsung. They have absolutely no use in Xiaomi.
  • Helpful post
    #5 19793689
    blahfff
    Level 41  
    Posts: 4929
    Help: 1030
    Rate: 1281
    leonov wrote:
    Maybe this one, but there are others, e.g. deep flash / EDL


    This model is based on the Mediatek system, so there is no EDL here, because it only applies to models with a Qualcomm processor ;-)
  • ADVERTISEMENT
  • #6 19793778
    Kuku1125
    Level 5  
    Posts: 28
    Rate: 4
    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
  • Helpful post
    #7 19794044
    blahfff
    Level 41  
    Posts: 4929
    Help: 1030
    Rate: 1281
    Kuku1125 wrote:
    In general, I have been browsing all forums for 2 weeks and looking for a solution... I can only hope that someone has ever had such a situation, or they will come across some forgotten forum and be able to advise something... If it doesn`t work, it will either be serviced or sold for parts.


    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.
  • #8 19794270
    Kuku1125
    Level 5  
    Posts: 28
    Rate: 4
    blahfff wrote:
    Kuku1125 wrote:
    In general, I have been browsing all forums for 2 weeks and looking for a solution... I can only hope that someone has ever had such a situation, or they will come across some forgotten forum and be able to advise something... If it doesn`t work, it will either be serviced or sold for parts.


    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.



    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
  • ADVERTISEMENT
  • Helpful post
    #9 19794287
    blahfff
    Level 41  
    Posts: 4929
    Help: 1030
    Rate: 1281
    Kuku1125 wrote:
    as I said, maybe Windows detected something twice, but only after 2 seconds. it was disappearing.


    It`s normal. Bootrom mode is only available for a moment, and if nothing connects to the device, it continues.

    Kuku1125 wrote:
    Could you somehow guide me on how to do this?


    Without having my phone in front of me, not really. https://github.com/bkerler/mtkclient - 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.
  • #10 19796244
    FranekDolas
    VIP Meritorious for electroda.pl  
    Posts: 4458
    Help: 300
    Rate: 69
    For new MTKs, the Infinity CM2MT2 works best for me.
  • #11 19797628
    Kuku1125
    Level 5  
    Posts: 28
    Rate: 4
    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 😁😁
| New topic
Report a violation of the law

Topic summary

✨ The Xiaomi Redmi 9 has encountered a bootloop issue following a failed TWRP installation, rendering it unresponsive and unable to access fastboot or recovery modes. Users suggest checking USB debugging settings and utilizing ADB commands, although the phone's current state complicates this. Recommendations include using MTKClient to restore the original recovery or upload software, as the device is based on a Mediatek system, which does not support EDL mode. Some users have reported intermittent recognition of the device by Windows, indicating potential for recovery. Ultimately, a combination of MTKClient and specific guides has successfully revived the device for at least one user.
Generated by the language model.

FAQ

TL;DR: Fix Redmi 9 bootloops using 1 tool—mtkclient—via BootROM; “All you have to do is upload the software or at least restore the original recovery.” Restore stock recovery first, or reflash partitions, then reboot. [Elektroda, blahfff, post #19794044]

Why it matters: This helps Xiaomi Redmi 9 owners recover a non-booting, Fastboot-less phone without specialized service.

Quick Facts

How do I unbrick a Xiaomi Redmi 9 stuck in a bootloop after a failed TWRP?

Use BootROM with mtkclient to restore the original recovery, then reboot. Connect the phone while holding both Volume keys to get detection. If needed, flash the firmware by restoring partitions manually. Start with restoring the stock recovery as the simplest corrective step. [Elektroda, blahfff, post #19794044]

Why does my Redmi 9 only appear on USB for a moment and then disconnect?

You are seeing BootROM, which exposes USB briefly. “Bootrom mode is only available for a moment.” If nothing connects immediately, the phone continues booting and drops the link. Launch your tool first so it catches the handshake at once. [Elektroda, blahfff, post #19794287]

Can I use EDL or deep-flash methods on a Redmi 9 (MediaTek)?

No. Redmi 9 uses a MediaTek SoC, and EDL is a Qualcomm-only service mode. Use BootROM-based tools such as mtkclient instead. [Elektroda, blahfff, post #19793689]

Is ADB an option if I had USB debugging enabled earlier?

No. ADB requires the device to enumerate and stay connected in Android or recovery. In a bootloop without a stable connection, ADB cannot attach. Focus on BootROM-level access and flashing tools. [Elektroda, blahfff, post #19793490]

What is mtkclient, and how does it help here?

mtkclient is an open-source MediaTek tool that connects during BootROM. It can restore stock recovery or write individual partitions. A GUI is available now. Use software for your exact model and the same installed version to avoid mismatches. [Elektroda, blahfff, post #19794287]

Is Infinity CM2MT2 a good alternative if mtkclient doesn’t work for me?

Yes. Users report Infinity CM2MT2 works best on newer MediaTek devices. It is a professional-grade solution and may simplify detection and flashing. [Elektroda, FranekDolas, post #19796244]

How do I enter BootROM mode on the Redmi 9 and start recovery?

Try this: 1. Open mtkclient on your PC. 2. While holding both Volume keys, connect the phone via USB. 3. When detected, restore the original recovery or required partitions, then reboot. [Elektroda, blahfff, post #19794044]

Windows keeps connecting and disconnecting; it fails in 99% of attempts—what should I do?

This is expected timing behavior. One user saw Windows fail to detect the phone 99% of the time. Prep your tool first, then plug in and retry quickly until it catches the short BootROM window. Persistence is part of the process. [Elektroda, Kuku1125, post #19793151]

Can restoring only the stock recovery fix the bootloop without full flashing?

Yes. The recommended first step is restoring the original recovery. It is simpler than a full firmware rewrite and often enough to boot. Use mtkclient to push the stock recovery image, then restart. [Elektroda, blahfff, post #19794044]

Will flashing the wrong firmware version cause more issues?

Avoid mismatches. Use software for your exact model and the same version currently installed. Version mismatches can prevent booting and complicate recovery. Verify build numbers before writing partitions to reduce risk. [Elektroda, blahfff, post #19794287]

I still can’t catch BootROM reliably—should I go to a service center?

Yes, if repeated attempts fail. An unauthorized service center with appropriate MediaTek equipment should handle this quickly. They can restore recovery or flash partitions without Fastboot access. [Elektroda, blahfff, post #19794044]

What finally worked for the original poster with a Redmi 9 bootloop?

They recovered the phone using mtkclient along with a step-by-step video guide. This combination restored normal operation and closed the case. [Elektroda, Kuku1125, post #19809453]

Do Samsung-style “download-mode” or USB jig cables help on Xiaomi?

No. Those cables historically target Samsung mechanisms and have no utility on Xiaomi devices. Focus on MediaTek BootROM workflows instead. [Elektroda, blahfff, post #19793490]

Do I need Fastboot access for this unbrick?

No. The guidance here relies on BootROM detection and partition restore. Restoring the original recovery via mtkclient does not require Fastboot access. [Elektroda, blahfff, post #19794044]
Generated by the language model.
ADVERTISEMENT