Database Info

stucked in fastboot mode

hello
i have got stucked in fastboot mode while installing custom rom.
please help me how to install os in my phone ( either cyanogen or miui).
Thanks in advance.
Regards,
jeevan.

Fastboot flash stock.

boyapatijeevan said:
hello
i have got stucked in fastboot mode while installing custom rom.
please help me how to install os in my phone ( either cyanogen or miui).
Thanks in advance.
Regards,
jeevan.
Click to expand...
Click to collapse
Hope this helps. Go to their website and download the fastboot ROM of your desired phone and desired locale. There you can also find the MiPhone Flasher exe file. Run that file on your PC, connect the device with a USB cable when in Fastboot Mode, the application will detect the device, then provide the Downloaded ROM path and hit Flash. within 2-3 mins you're good to go

I have same problem with my mi 4i
Falshing via miflash tool , adb and qfil still got stucked on fastboot mode
When i wipe using mirecovery got notice
Wipe data failed
Any more solution to solve this suck problem?

How to Flash fastboot rom in edl mode manually

Everytime when i try to flash fastboot rom using edl mode i get a error saying "....../(PATH TO ROM FOLDER)/images/sec.dat file not found" but i have double checked everything and downloaded both global beta and stable build for my device (Redmi 3s) and have successfully installed all drivers too in the beginning of the flashing procees via mi flash tool there is not error but after 30 sec the error occurs saying sec.bat file not found ia there any alternative to flash in edl or where to get the sec.bat file i have checked fastboot roms for redmi note 4 too there too i haven't found any sec.bat file so whats the error likely to be

Stuck at logo/Bootloop with locked bootloader

My Redmi Note 6 Pro Global version just rebooted itself out of nowhere and now its showing MI logo and rebooting every 3-5 seconds. I didn't unlock bootloader and had MIUI 10 latest stable version installed. I can still enter fastboot mode. What can I do to fix this?

UPDATE
Over the last few days, these are the things that I've tried:
I can enter Fastboot mode and connect to my PC, but can't enter recovery mode.
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
I tried flashing fastboot rom with MiFlash, but when MiFlash causes phone to reboot towards the end of flashing, the bootlooping problem occurs again and it cannot complete flashing.
I also tried flashing TWRP from fastboot, it says that it's successful, but when I try fastboot boot twrp.img, the same problem: MI logo and constant reboots.
I also tried to use fastboot oem edl mode and my phone is recognized as Qualcomm device, but MiFlash can't flash in this mode, saying that hello packet is not received.
At this point, I don't know what else to do and wondering if this is a hardware problem. Any ideas?

Did you tried to press VOL UP + POWER BUTTON after you flash TWRP? If flashing TWRP doesn't work Try to flash Official MIUI RECOVERY 3.0 That's all you can do. Otherwise you should give it to Mi customer service for faster solution.

I have the same problem, did you manage to solve this issue?

hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.

MI stuck at boot logo
m1s3rys1gn4l said:
hello guys,
here is a solution, open your phone backpart and put your phone to edl mode by testpoint pinout,
then try to flash latest stable rom if fail then flash latest dev rom.
Click to expand...
Click to collapse
Hello all ! same problem here !
i reinstall the last version in EDL mode every week !!
I can not handle it anymore !
sometime he match 1 day sometime 3 week ... everytime he stuck on menu and i can't reboot .
the only version i can use its 10.3.2 global ... all other version don't match !
Sorry for my english (i'm french) and thanx you for your help

hi my redmi note 6 pro is stuck on mi logo its not getting over it .
i dont have any pc or laptop at my home how can i solve this issue
during this lockdown ,and now its showing charging in shutdown mode?

Hello All i have the same problem stuck on MI logo
I have tried to wipe through Mi recovery but no use
I cant flash anything because the bootloader is locked
and i dont want to use EDL mode cuz i am stuck at home and dont have necessary tools for that
My question is can we flash anything using Fastboot command or can we ON usb debugging through fastboot be cause Mi flash wont work until USB debugging in On
Please help

Try another flash tool i.e. Qfil_flash_tool

Hi, I have even tried EDL mode to flash latest rom (android 9,miui11.0.4) using Mi flash tool,still facing the same issue.
It constantly reboots while on charging, and it doesn't turn on otherwise(2 Sec of that logo and then it fades away).
Please Help

any one find solution for this?

Hi, my problem is simpler, so is there any suggestion.
after last official update, due to the internal partition was encrypted, update wasn't finished and I am stuck on MI logo when restarted the phone.
bootloader is unlocked and I can enter to (orangefox) recovery, yet I am not sure what is the best way just to return phone to the bootable state? I presume some wiping is to be done, which is not the problem, just to have as short procedure as possible, preferably without need to re-flash clean ROM from recovery?
regards

mertcanekiz said:
I was able to unlock my bootloader (I was in the process of waiting for the 360 hours)
Click to expand...
Click to collapse
Hi, i'm in the same situation as you. How did you solve it? with the miunlock app I can't unlock it because it tells me that I have to select something on the phone first, but if the phone doesn't start I can't select anything ..

Try to remove hardware buttons from board and try

redmi 6 pro (bootloader locked)
same problem...
tried methods :
1) using mi flah tool ( error occurred : )
2) edl method (showing: device is locked)
........still stuck on miui logo .........

Redmi Note 7 Pro - Bricked (Current Device Anti Rollback is greater than this Pkg.)

I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs

hackermssharma said:
Try the command "fastboot oem edl" in cmd of adb folder when device is in fastboot mode. Ur phone should go black but dont panic. Now open miflash tool and u see ur device is connected in edl mode as COMX ( X may be anything 10 or 20 like that). Now try to flash the lattest fastboot rom for over device. Remember to check the option in mi flash tool to not lock bl again. But this will wipe all your data.
Sent from my Redmi Note 7 Pro using XDA Labs
Click to expand...
Click to collapse
Thank you for taking time to reply to my query. I did what you suggested and got into EDL mode. Xiaomi Mi Flash picked up the device as COM10 but when I tried to flash it shows "sahara read end error with status:40" and nothing happens.
Any further idea?

TSKXDA said:
I tried to search regarding this issue but couldn't find a solution so I am posting this issue in hopes that someone can guide me to a solution.
I wanted to install pixel experience on my Redmi Note 7 Pro. My phone was successfully unlocked by myself and no issues were faced. First I tried to install Peter's TWRP but then can't go the recovery instead every time I was booted to fastboot menu. I then tried to just restart by holding the power button to boot straight to OS but instead I was again back to the fastboot menu.
I then downloaded the latest global ROM "violet_in_global_images_V11.0.5.0.PFHINXM_20191022.0000.00_9.0_in_9bff00d97f" for flashing using xiaomi flash tool and faced many errors but resolving one by one and then finally ROM was flashed but it only took 1 sec to complete and nothing happened on the phone. Then I searched around a bit more and tried to use CMD to flash "flash_all.bat" directly and got the error "Current Device Anti Rollback is greater than this Pkg". What I don't understand is that if I am using the latest global firmware then how the current device has a higher arb no. ?
I hope that I am able to explain the situation for other's to understand.
Any help will be appreciated.
Click to expand...
Click to collapse
I suggest you use the older variant of the MiFlash tool.
How did you flash Peter's? Did you use "fastboot flash recovery recovery.img"? That's the only right command.
Also are you sure you have the Indian variant of the phone? Another way to bypass anti roll back would be to clear all partitions, and then flash the required ROM.
Sorry if I'm not able to help you, I'll try having a look later on.

Thank you for your support. I had to go to the service center as no solution could be found.

Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.

dnyaneshmoh said:
Wait i know what happen... Ur phone has twrp and rom successfully installed don't worry about that. Just problem is ur phone has again locked the bootloader thats why its not able to boot os because it has twrp not the official recovery. U can verify that u have bootloader locked.. when ur phone starts when there is mi logo there will not be "unlocked" written in bottom.. see... That is very easy. Just try to unlock bootloader again with mi unlock tool.
And ur good to go. I got same errors on my friends redmi 6 pro. Service center will tell u to change motherboard as it cant be fixed with edl mode. JUST TRY TO UNLOCK AGAIN WITH MI UNLOCK TOOL.
Click to expand...
Click to collapse
Thank you for your feedback but the phone bootloader remained unlocked as when the phone starts there is "unlocked" written in bottom.
I got the phone back from Service Center. It's working fine but strangely still the bootloader is shown as unlocked in the start animation.

Redmi Note 11 bootloop after custom ROM install

Hi, this is my first post in XDA, so sorry if I'm posting in the wrong section.
I recently got a Redmi Note 11 and today I was going to install KomodoOS in it. I did as follows:
First thing I did was to unlock the bootloader, which seems to have worked fine (I can see the open lock icon alongside the Mi logo when it powers on).
I then flashed TWRP (from here https://www.getdroidtips.com/twrp-recovery-redmi-note-11/). When I first tried the command fastboot flash recovery_a twrp.img, I got an error telling me that recovery_a_a doesn't exist, same for recovery_b (which gave me error that partition recovery_b_a didn't exist). I found on Google I could boot into twrp (fastboot boot twrp.img) and then flash twrp itself (Advanced->Flash recovery), which I did and got no error messages. I booted up the system just normal, rebooted into recovery by issuing adb reboot recovery and it got me back into TWRP. So it seems it was installed successfully.
Lastly, while the phone was on TWRP I copied the rom file into the root directory with adb push komodo-version.zip komodo.zip, clicked on Install, selected komodo.zip then confirmed the installation. It took a few minutes (file is 1.3GB) and it completed with a few errors, but at the top there was the message Install successful.
Then I wiped Dalvik and rebooted the system, but now I'm stuck at a bootloop where it goes to the "No command" screen and reboots. I tried holding volume up+power and volume up while reconnecting the USB but to no avail, can't seem to get out of the loop. Also tried spamming adb devices and fastboot devices on pc but can't connect to the phone.
I'm now a bit desperate, since there's (surprisingly?) not much about this phone out there, and I don't know anything that could be done. Is there still hope?
Links/tutorials I used:
Download and Install AOSP Android 12 on Xiaomi Redmi Note 11
Xiaomi Redmi Note 11 launched in January 2022. The handset came with Android 11. In this tutorial, we will guide you to install Android 12 Custom ROM on
www.getdroidtips.com
Download TWRP Recovery for Xiaomi Redmi Note 11 | Root Using It
On this page, we will guide you to install the TWRP Recovery on Xiaomi Redmi Note 11 (spes). This guide contains both the written instruction and a video
www.getdroidtips.com
[4 Methods] How to Fix TWRP Error: FAILED (remote: No such partition)
In this guide, we will show you four different methods to fix the FAILED (remote: No such partition) error while flashing the TWRP Recovery.
www.droidwin.com

Draining battery and directly going into fastboot as soon as plugging in works or not?

.

dont trust getdroidtip , search rom on xda instead

In Shaomi "No Command" error means system partition has been destroyed. You most likely need to Reflash MIUI using >Mi Flash Tool<.
So your issue is that you cant boot into TWRP? Also, have you tried Power + Vol(-) to get into Fastboot mode. You can also try PC softwares like >Reiboot-For-Android.exe< to boot to recovery or bootloader.
>If you have TWRP no need to use ADB push, just use USB OTG to flash ZIP<