11 thoughts on “Unbrick Redmi Note 4 By Flashing MIUI ROM | Fix Stuck at Mi Logo”

      • Hi, the link to the Qualcomm QDloader USB driver is pointing to an article

        “How to Unlock Bootloader of Xiaomi Redmi Note 4” where it involves the official method of getting permission from Xiaomi to unlock etc

        This is an issue for me because my mi max 2 is currently bootlooped with a locked bootloader and the device is not bound to the mi acc since I could not get back to miui mode to do the above.

        Pls could you advise how I can fix this problem? I just need to reflash my phone back to factory default settings with the above constraints.

        Rgds

  2. Hi I was trying to root my Redmi note prime phone by using trwp by mistake I choose some option in twrp and my phone got stuck into mi logo. I have tried flash fastboot using mi flash tool and command prompt but after flashing with both the tools my phone again going stuck into mi logo…. please help me my phone is Redmi note prime.

    • Download the Correct MIUI Fastboot ROM of your device & then flash it through Fastboot mode using Mi Flash tool or Using Fastboot Commands. If the bootloader of the device is locked then you can Boot it into EDL Mode then try flashing.

      All the best!

  3. Thx a ton for the post.. Actually option 2 worked for me. Tried several posts and threads (even on official MI site) for the same but couldn’t flash into system. MI PC Suite won’t detect the phone when connected by usb cable. MIFlash tool wouldn’t do it due to some unknown errors. Was really getting frustrated as no method was working as intended. Finally stumbled upon this post after much search and Viola, was able to bring the phone back from the dead.

    Now let me tell you what happened. The entire story is here. It’s a a really, really long story. So pls have some time and patience to read out the same:
    I wanted to flash my phone clean as I suspected some kind of malware was slowing and hanging my Redmi. Btw my device is Redmi 3S Prime and was running on MIUI 9.5.1.0 (MALMIFA). The Android version was 6.0.1. MMB29M (Marshmallow).
    I had installed TWRP and the device was rooted using SuperSu. First I tried to factory reset the phone from the settings menu. The device prompted me twice with passwords – the phone password and the MI Account password. Once both passwords were matched the phone rebooted. But it rebooted into TWRP menu. Now as I was (and still am) NAIVE in terms of booting, flashing, TWRP, etc etc. I didn’t knew what to do. I clicked on the exit to system/boot menu and the phone again rebooted into the normal mode.
    Since I was hell bent on flashing the phone and erasing everything on the device [inlcuding killing the handing virus :), pun intended], I downloaded the Global Rom version for the Redmi 3S Prime (MIUI 9) and put the entire downloaded zip file into a folder in my computer and copied the entire zip file also in the root directory of the phone’s internal memory. I think this was the starting point of my blunder as the SU Superzip zip file was also in the same root directory.

    Anyways I again rebooted to TWRP recovery menu by pressing Volume UP button and power button simultaneously and this time I decided to use the option update from zip file in the TWRP menu. I navigated to the zip file of the rom which was put by me in the internal memory of the phone. After that some prompts appeared on the TWRP menu screen for confirmation (slide right for the update) and the phone started to update from the ROM zip file which I had mentioned in the TWRP menu path. However the phone didn’t booted successfully as it was stuck at the MI logo. Usually after a few seconds of rebooting “the powered by Android” option appears at the bottom of the screen in addition to the MI logo during a boot. But in this case the boot was stuck at the MI logo inspite of rebooting the phone several times.
    Then I searched again for some more threads on google as I suspected the TWRP was not allowing a successful reboot. After seaching for the phrase how to remove TWRP Recovery from MIUI/Redmi phones, I finally stumbled upon the following site: http://en.miui.com/thread-631845-1-1.html with the heading:
    “How to remove twrp recovery without root.”

    Now a thread at this site asked for the following steps:
    ========================================
    “Download stock recovery Img file. You can find it in forum under ‘Tool, tips and tutorials’ section.
    Extract the downloaded .zip file
    Find the .img file
    Rename it recovery.img
    Copy paste to C:/adb folder
    On window C:/adb folder, press shift +right click
    Click on open command window here
    Connect your phone to PC in fastboot mode
    Enter fastboot command

    Fastboot devices
    Fastboot erase recovery
    Fastboot flash recovery recovery.img
    Fastboot reboot

    Best regards ”
    ===========================================

    The method executed in the adb shell prompt but when I executed the final command “Fastboot reboot”, the phone was still stuck at the MI Logo. After a few unsuccessful attempts I tried to renter the recovery mode once again but the volume up and power button didn’t responded and I could only enter the fastboot mode (by clicking both volume down and power button for a few seconds).
    I was really beginning to feel frustrated as none of the sites were able to resolve the problem. The MI PC suite won’t detect my device and the MI flashing tools option gave error (no succh directory exists). However the option 2 at the site worked like charm though once I wandered again for some time in this option also (partly because of my impatience).
    Actually after executing the first command mentioned in step 2 of this article:
    “fastboot flash system system.img”
    “Press Enter to Continue”
    gave this message on the adb prompt/command prompt:
    “target reported max download size of 536870912 bytes”

    There was no activity on the command prompt for a few minutes and I thought this was some kind of error and then I started to search for this error on google (what a dumb a** I am). Actually this is not an error. It can take some time at the first command (fastboot flash system system.img) as the file can be quite large at the initial stage. I had pulled of my data cable after a few minutes thinking that the command prompt had become unresponsive. However when I came back from the browser to the adb/command prompt, the following error was showing on the adb prompt:

    C:\adb\FASTBOOT ROM\images>fastboot flash system system.img
    target reported max download size of 536870912 bytes
    erasing ‘system’…
    OKAY [ 0.138s]
    sending sparse ‘system’ (524096 KB)…
    FAILED (data transfer failure (No such file or directory))
    finished. total time: 30.348s

    So I again rebooted my phone to fastboot mode and again reinserted the data cable into the bricked phone at fastboot logo and executed all the commands religiously one by one and finally I was able to reclaim my bricked phone which I was going to declare as dead (RIP my phone :). One advise to everyone who used the method 2. The first command : “fastboot flash system system.img” might take a while but don’t abandon the process or take the cable out from the phone as it will take some time initially. Here is the complete list of commands executed and the success message after each command. Will help and guide you if you are in same situation of bricked phone at MI Logo. I think this can also work for other models and phones provided you have the actual ROM with relevant image files as asked in the command.

    C:\adb\FASTBOOT ROM\images>fastboot devices
    32c1307e7d63 fastboot

    C:\adb\FASTBOOT ROM\images>fastboot flash system system.img
    target reported max download size of 536870912 bytes
    erasing ‘system’…
    OKAY [ 0.042s]
    sending sparse ‘system’ (524096 KB)…
    OKAY [ 31.603s]
    writing ‘system’…
    OKAY [ 3.781s]
    sending sparse ‘system’ (507199 KB)…
    OKAY [ 30.977s]
    writing ‘system’…
    OKAY [ 3.905s]
    sending sparse ‘system’ (522838 KB)…
    OKAY [ 31.401s]
    writing ‘system’…
    OKAY [ 4.003s]
    sending sparse ‘system’ (508705 KB)…
    OKAY [ 28.634s]
    writing ‘system’…
    OKAY [ 3.653s]
    sending sparse ‘system’ (523999 KB)…
    OKAY [ 47.059s]
    writing ‘system’…
    OKAY [ 5.924s]
    sending sparse ‘system’ (468319 KB)…
    OKAY [ 30.565s]
    writing ‘system’…
    OKAY [ 11.067s]
    finished. total time: 232.891s

    C:\adb\FASTBOOT ROM\images>fastboot flash boot boot.img
    target reported max download size of 536870912 bytes
    sending ‘boot’ (20683 KB)…
    OKAY [ 0.745s]
    writing ‘boot’…
    OKAY [ 0.165s]
    finished. total time: 0.950s

    C:\adb\FASTBOOT ROM\images>fastboot flash recovery recovery.img
    target reported max download size of 536870912 bytes
    sending ‘recovery’ (21823 KB)…
    OKAY [ 0.795s]
    writing ‘recovery’…
    OKAY [ 0.828s]
    finished. total time: 1.661s

    C:\adb\FASTBOOT ROM\images>fastboot flash cache cache.img
    target reported max download size of 536870912 bytes
    erasing ‘cache’…
    OKAY [ 0.038s]
    sending ‘cache’ (6248 KB)…
    OKAY [ 0.263s]
    writing ‘cache’…
    OKAY [ 0.079s]
    finished. total time: 0.450s

    C:\adb\FASTBOOT ROM\images>fastboot erase userdata
    ******** Did you mean to fastboot format this partition?
    erasing ‘userdata’…
    OKAY [ 1.124s]
    finished. total time: 1.151s

    C:\adb\FASTBOOT ROM\images>fastboot flash userdata userdata.img
    target reported max download size of 536870912 bytes
    erasing ‘userdata’…
    OKAY [ 0.063s]
    sending ‘userdata’ (168174 KB)…
    OKAY [ 5.953s]
    writing ‘userdata’…
    OKAY [ 1.238s]
    finished. total time: 7.310s

    C:\adb\FASTBOOT ROM\images>fastboot reboot
    rebooting…

    finished. total time: 0.022s

    C:\adb\FASTBOOT ROM\images>

    “this is the end of the commands at adb and the phone will most probably return to normal boot (as happened with me)

    Thx for reading the soooooooooooooo loooooooooooooooooonnnnnnnnnngggggggggggggg post 😉

    I wanted to flash

Comments are closed.