Database Develop

Phone can't boot stuck at "Your device is booting now" Please Help

Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery
Code:
adb reboot recovery
. When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat

Which twrp you flashed? Check the correct twrp in my signature for honor 5C repository.

TassiloBalbo said:
Hello, I wanted to install TWRP and ROOT my phone. I flashed TWRP using adb terminal. But when I tried to boot into TWRP it was stuck on "Your device is booting now..". Then if I held the power button for few secs it rebooted normally. So I tried to google it and I found adb command that reboots to recovery . When I executed the command it rebooted to the "Your device is booting now.." screen and it stays like this forever. No button combination works to reboot the phone if i hold power button it reboots shows honor logo and then shows the "Your device is booting now.." screen. I waited for the battery to drain and then i put the phone on charger and when I tried to boot it, it was the same. Now when I try to reboot the phone it shows ultra low baterry symbol and then boots to "Your device..." screen.
NEM-L21; EMUI 5.0; 7.0 Nougat
Click to expand...
Click to collapse
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot

hassanjavaid8181 said:
I think you have flashed wrong twrp.download correct twrp and flash it via adb fastboot
Click to expand...
Click to collapse
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...

Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Meaning you can boot to fastboot but your pc doesn't recognise it?

Crocni said:
Hi hassanjavaid8181
I think I have the same issue here, phone is stuck on "your device..." screen forever and it's impossible to do anything else (reboot ends up on the same screen).
How is it possible to flash twrp or stock recovery if we are stuck on this screen ? Fastboot doesn't see the phone...
Click to expand...
Click to collapse
Did you try all method to going in fastboot.by adb fastboot command or by pressing vol- and power button?

Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support

Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Glad that you fix your device.
If it is not bothering you let it be and enjoy using your phone.

Crocni said:
Hi guys, thanks for your replies.
I somehow managed to boot to fastboot after waiting for the battery to go out completely. From there I used the following commands in ADB from the extract of a stock update.img :
fastboot flash boot boot.img
fastboot flash recovery recovery.img
fastboot flash system system.img
fastboot reboot
And it worked ! The first boot was veeery long and now it's normal again.
Now my last concern is that I still have bootloader unlocked. As I wish to come back to factory state and avoid the warning message on boot, do you guys think it's safe to re-lock bootloader ?
I'm kind of scared to try anything else and screw the whole thing now
Thanks again for your support
Click to expand...
Click to collapse
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.

TassiloBalbo said:
Can you please explain to me how did you managed to boot into fastboot? I tried waiting for the battery to drain completely. Now I can't fully charge my phone. When i connect it with charger. It starts normally charging like it would with 0% battery then after a few moments the honor logo shows up and then the screen "Your device.." shows. When I try vol- and powerbutton it vibrates and shows the red lightbolt then after few moments it boots the same way into the your device screen. When I connect it to the pc it doesn't react. I don't even hear the classic windows beep sound.
Click to expand...
Click to collapse
Try removing the usb cable and then try to biot to fastboot. What about erecovery

shashank1320 said:
Try removing the usb cable and then try to biot to fastboot. What about erecovery
Click to expand...
Click to collapse
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.

TassiloBalbo said:
When I remove the usb cable it's still the same. When i try to press the power button it vibrates shows the low battery red lightbolt and dies. If you mean by erecovery emui recovery, then it looks like it's not installed.
Click to expand...
Click to collapse
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press

shashank1320 said:
You need to press power + volume down key to boot into fastboot. Keep trying 4-5 times sometimes it takes due to wrong press
Click to expand...
Click to collapse
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]

TassiloBalbo said:
So I managed to get into the fastboot. Where can I get boot.img, recovery.img and system.img? I have downloaded some update.zip files from this russian site (first 5) http://hwmt.ru/hwmtsite/firmware-database/?firmware_model=NEM-L21&firmware_page=0. But I don't have boot, recovery and system images in these zips.
I also tried reboot in fastboot but its still the same:
fastboot devices
8SC4C16A13006909 fastboot
fastboot reboot
rebooting...
finished. total time: 0.026s[/CODE]
Click to expand...
Click to collapse
Meaning the fastboot is accessible.
Now you have firmware zip, extract it amd you will get few files. Use dload method as given in my signature and you are good to go.
Else use Huawei extractor and browse to update.app you just got in above downloaded zip. You will get boot, recovery, system img you need.

I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery

TassiloBalbo said:
I downloaded some firmware versions and extracted them. I don't know which is for my device. So I tried one of them. I flashed boot.img and recovery.img but I din't flashed the system.img, becouse it was too big. When I tried to reboot the phone it was the same. The fastboot was no longer accessible. I put the phone into servis but they didn't fixed it. it's the same but I can enter erecovery
Click to expand...
Click to collapse
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you

shashank1320 said:
Please flash only files for your device and nothing else. Did you try dload method?
Give me model and build number, will get the correct files for you
Click to expand...
Click to collapse
NEM-L31 but I don't know the build number

TassiloBalbo said:
NEM-L31 but I don't know the build number
Click to expand...
Click to collapse
Build number is necessary to get right files..

hassanjavaid8181 said:
Build number is necessary to get right files..
Click to expand...
Click to collapse
I know. So do you think it's dead?

TassiloBalbo said:
I know. So do you think it's dead?
Click to expand...
Click to collapse
You should try huawei service center....

My 3T went crazy and shut down by itself. Will only start up to the bootloader now.

This happened last night and my phone is currently running Paranoid Android with the latest TWRP and Magisk.
So I was holding my phone in my hand and when I checked my phone it was as if 5 pairs of hands were touching the screen. I was not touching the screen myself but the phone was opening all sorts of apps and locking itself and opening the app drawer in such a quick way that I could not even shut the phone down since when I tried to hold the power button to shut down the phone, I did not even have the time to press the power off option before the phone started going crazy again.
Once it reached about 5%, the phone shut off by itself. I've been trying to open it however it will only reach the bootloader screen. Once I try to open the phone to recovery or standard mode, the oneplus logo will appear but it will quickly shut down again after a few seconds. I tried flashing TWRP already but the phone still won't boot to recovery. The oneplus logo would appear but it just turns off around the time TWRP should be appearing.
Does this mean I bricked my phone? Is there any way to recover my photos and data currently on my phone?

Have you tried to leave the phone to charge overnight and then boot?
Check if TWRP boots with
Code:
fastboot boot twrp.img

Symbiotec said:
Does this mean I bricked my phone? Is there any way to recover my photos and data currently on my phone?
Click to expand...
Click to collapse
Unless you can at least boot TWRP (and then just mount storage or adb pull) I don't think you can retrieve much of anything.
It always surprises me that folks wait for a disaster (and then ask for recovery solutions), instead of regularly backing up the data that is important to you.

Honestly this sounds like hardware damage more than a software brick, can't be certain until the unbrick guide is done though. I have seen the same thing happen to other water damaged phones where it starts to randomly open applications then dies.

przemcio510 said:
Have you tried to leave the phone to charge overnight and then boot?
Check if TWRP boots with
Code:
fastboot boot twrp.img
Click to expand...
Click to collapse
I tried this however it said it could not find the file in the directory?

redpoint73 said:
Unless you can at least boot TWRP (and then just mount storage or adb pull) I don't think you can retrieve much of anything.
It always surprises me that folks wait for a disaster (and then ask for recovery solutions), instead of regularly backing up the data that is important to you.
Click to expand...
Click to collapse
I backup my files monthly, it just so happened that my phone went haywire a few days before I was gonna backup January's files.

ZVNexus said:
Honestly this sounds like hardware damage more than a software brick, can't be certain until the unbrick guide is done though. I have seen the same thing happen to other water damaged phones where it starts to randomly open applications then dies.
Click to expand...
Click to collapse
That's what I initially thought too. However, if it was hardware damage wouldn't that mean I couldn't open the bootloader?

Symbiotec said:
I tried this however it said it could not find the file in the directory?
Click to expand...
Click to collapse
Obviously you have to type twrp's .img file name or rename the file to twrp.img. Don't forget to download it first from https://twrp.me

Man i see kind of threads a lot lately. I feel there isn't any hardware damage, just people that don't know what they are doing or doing things wrong.
Download the twrp image and boot it through adb, if the oneplus logo appears than it HAS to at least boot the recovery. Also, before you do anything with your phone, considering it isn't the cheapest thing in the world(at least for me) do some reading first, it always helps.

Symbiotec said:
I tried this however it said it could not find the file in the directory?
Click to expand...
Click to collapse
That means you did it wrong.
As mentioned, the syntax has to be correct. If you use the command verbatim: fastboot boot twrp.img
Then the file has to be exactly named twrp.img and it needs to be located in the same folder where fastboot.exe is located (which is the same directory you need to be running the command from).
Also, if in Windows, and you renamed the file; make sure you have the Windows option disabled to hide known file extensions. It is usually enabled by default, so turn that option off! Otherwise, you may have unwittingly named the file "twrp.img.img" and not know it (the screen will show "twrp.img").
These are all common mistakes. But if your top post when you said "I tried flashing TWRP already but the phone still won't boot to recovery" it would have been more useful to tell us that if failed to flash.

przemcio510 said:
Obviously you have to type twrp's .img file name or rename the file to twrp.img. Don't forget to download it first from https://twrp.me
Click to expand...
Click to collapse
I tried running it in ADB and according to ADB, TWRP finished booting on the phone. The oneplus logo appeared with the text "fastboot mode" below it however the phone shuts down a few seconds after this screen appears. Is it still a problem in how I tried to boot the TWRP?

redpoint73 said:
That means you did it wrong.
As mentioned, the syntax has to be correct. If you use the command verbatim: fastboot boot twrp.img
Then the file has to be exactly named twrp.img and it needs to be located in the same folder where fastboot.exe is located (which is the same directory you need to be running the command from).
Also, if in Windows, and you renamed the file; make sure you have the Windows option disabled to hide known file extensions. It is usually enabled by default, so turn that option off! Otherwise, you may have unwittingly named the file "twrp.img.img" and not know it (the screen will show "twrp.img").
These are all common mistakes. But if your top post when you said "I tried flashing TWRP already but the phone still won't boot to recovery" it would have been more useful to tell us that if failed to flash.
Click to expand...
Click to collapse
My apologies. According to ADB the TWRP flash was successful however the phone still refuses to open in recovery.

Symbiotec said:
I tried running it in ADB and according to ADB, TWRP finished booting on the phone. The oneplus logo appeared with the text "fastboot mode" below it however the phone shuts down a few seconds after this screen appears. Is it still a problem in how I tried to boot the TWRP?
Click to expand...
Click to collapse
You were supposed to use fastboot command, is this what you meant?

przemcio510 said:
You were supposed to use fastboot command, is this what you meant?
Click to expand...
Click to collapse
I already performed the command in fastboot. Once the command was finished the oneplus logo appeared with the text "fastboot mode" below

I have "the same problem", but my OP I can turn on again.
I was using it with Ressurection Remix 7.1.2, so I tried to update to Z-Unleashed 8.0 and my problems start on this moment... So, I tried to reinstall the Ressurection, but it continue restarting .... I'm thining that's an hardware problem....

rodrigoo said:
I have "the same problem", but my OP I can turn on again.
I was using it with Ressurection Remix 7.1.2, so I tried to update to Z-Unleashed 8.0 and my problems start on this moment... So, I tried to reinstall the Ressurection, but it continue restarting .... I'm thining that's an hardware problem....
Click to expand...
Click to collapse
How did you fix the problem?

Symbiotec said:
How did you fix the problem?
Click to expand...
Click to collapse
I don't know. I think that it have emotions. Actually is working normally with Z-unleashed.
I entered in bootloader mode and:
"fastboot format -w system" (you'll lose all your data) and installed all again...
Default kernel...

[FIXED] Fastboot? Recovery bootlooping, but never getting there

Hi All, I need fastboot!
Perhaps someone can help with my brick? I've unlocked the bootloader, installed TWRP and had lineageOS 18.1 installed once. The screen was dim so I tried to flash DotOS. And got a "failed to mount /tmp/com.android.resolv.apex to loop device /dev/block/loop16" error so I tried to reinstall stock 57 ROM.
I did "fastboot flash recovery boot.img" with the decrypted boot.img hoping to get colourOS recovery.
The phone is now bootlooping trying to get into recovery mode. It won't power off or respond to button presses except vol up + vol down seems to delay the reboot on a blank screen.
I was hoping to get to fastboot mode to flash TWRP. Can anyone help? Should I surrender and accept the bricking?

you can get back to stock by install the stock rom, vendor, and kernel with adb drivers and commands.
or
if your mobile is MIUI you can just use the software to revert back to stock rom remember it re-locks the bootloader and again you need to unlock

The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(

frolyx said:
The phone is currently boot looping.
I can't even turn it off.
It displays RealME/Android logo, then small "> RECOVERY MODE" text at bottom, then "Orange State" text. Repeat..
It has no response to a usb cable - no usb messages in dmesg. So it is not detected by adb or fastboot.
When the battery finally goes flat, my only hope is that I can get fastboot to flash TWRP into the recovery partition. I am not confident of this :-(
Click to expand...
Click to collapse
did you ever get this solved and fixed? i have accidently done the same thing.

hey guys follow this youtube
managed to unbrick my phone

smiley.raver said:
did you ever get this solved and fixed? i have accidently done the same thing.
Click to expand...
Click to collapse
Not yet, but I will try the youtube method above..

This recovered the Phone!
But, win10 reported the MCT extractor contained a worm (the python script under linux didn't work). I'm not sure I can trust this phone 100% from now on LOL!

the bypass just deactivates mtk hardware verificaton as normally they have a special dongle they use with the software download
I havent had any issues
I will upload thw bypass i use which doesnt havw any virus

Mi A2 won't boot past Android One

I charged my Mi A2 overnight and woke this morning to find that it won't boot past the Mi A2 splash screen; it shows the splash screen for a few of seconds and then dies. I read advice to hold down power and 'up' keys, this just resulted in the same. I tried power and 'down' key and that got me as far as the Fast Boot splash screen, but no further (phone just continued to display that splash screen). I've tried taking the SIM out and turning it on - no change. I tried opening it up and disconnecting the battery for 3 minutes - no change. I'd be very grateful if anyone could suggest a fix. I know this is hugely unhelpful, but I can't remember what I did to the phone in terms of unlocking the bootloader and/or rooting, but I have a feeling I left it stock (I've owned the phone for a couple of years and haven't changed anything material since initial setup).

Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?

Martinocom said:
Disclaimer: you need adb tools to execute following command. You can find info where your wish about it.
Try to make it on FastBoot mode, then attach to PC and execute
fastboot reboot
If it brings you again to flashing screen, again, bring the phone in fastboot mode. Then try to change active slot.
fastboot --set-active=a
If not working with a, try with b. After setting it, launch the command to reboot again.
What recovery do you have? Pressing up + power when turning on where brings you?
Click to expand...
Click to collapse
Thank you very much for your help.
Executing fastboot reboot via adb just brought me back to the Android One splash screen for a few seconds before the screen went black.
Changing the active slot to both A and B gave me the following error message:
FAILED (remote: 'Slot Change is not allowed in Lock State')
Pressing up + power when turning on just brought me to the Android One splash screen for a few seconds before the screen went black. I held those two buttons down for several minutes and the same thing kept happening: splash screen followed by black, repeatedly.
Is there anything else I can try?

You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!​
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.

Martinocom said:
You can try fastboot oem unlock or
fastboot flashing unlock to try to fix the "Locked State".
If I'm not wrong it erases your data! Before doing it please be sure and wait for some more time: maybe there is another solution for it!!!​
Main reason I'm making you this steps is that I think your phone applied some kind of system update that break something. Thanks to A/B partition maybe you can have a working system on the "not corrupted" one, so I'm trying to get you into it (either A or B)
Remember that doing this commands sometimes make the situation worse, or format your data, so please read if there are any side effects.
If nothing will work you can try to wait for someone more expert than me. Maybe you have a chance to recover from this state.
Another thing: turn on the phone (normally) without holding it in charge. I had a bug that won't let me pass the splash screen if phone was charging.
If really nothing works, try to find a tutorial on how to flash a ROM via TWRP, there are plenty of them. You will probably loose your data.
Click to expand...
Click to collapse
Thank you.
If anyone reading knows of a way to get my phone to boot without losing my data I'd be very grateful for your help.

Question Redmi Note 11 Stuck/boot loop in Recovery mode

I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)

Sheist! said:
How exactly did you set up your custom recovery, and when exactly did it stop working? (has the recovery ever worked normally for you?)
Click to expand...
Click to collapse
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Edit:
I saw this in another thread, we have the same problem.
KMS45 said:
Hello to everyone,
So basically i read all the 10 pages of this thread and I have not found someone that have the same problem as me. I have the “bootloop” but the thing is that my phone is not even turning on. It is just booting and going back to the recovery menu. So I choose the reboot option but still coming back to the menu. I have already turned on the debug usb option because I used to be using it before my phone dies. I have a Xiaomi MI10 Lite 5G. I also tried the MiAssisstant but no succes because device not detected.
If someone have a solution without wiping all my precious data pls ?
Click to expand...
Click to collapse
KMS45 said:
Here is a video to understand what is happening when:
Reboot:
https://imgur.com/a/rB9QhSZ
Safe Mode:
https://imgur.com/a/X0KH5AD
Click to expand...
Click to collapse

mhegz said:
I didn't do anything, I just charged my phone while it was turned off. Then I turned on the phone and the same thing happened as with others where when I unlocked it from the lock screen, the phone restarted and that's what happened.
Click to expand...
Click to collapse
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.

Sheist! said:
If you have your phone to automatically install updates, it might have done exactly that, and it borked. i.e. incomplete installation. There is no recovery partition on the spes so the boot image is potentially whacked. Try reflashing boot and dtmo and vbmeta images in Fastboot from your current ROM. That should get you back to where you were.
Click to expand...
Click to collapse
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.

mhegz said:
Sorry, I'm not really knowledgeable about this. Can you guide me or give me a link on how to do it? I don't have any experience in flashing through fastboot but earlier, I tried using ADB to check if my device is being recognized and I think it was recognized.
And also, I don't know which firmware to download or what is the current version of my phone because I only know the basic details of my device like this is Redmi Note 11 6/128 4G, I think this is the global version, and by the way, I'm from the Philippines.
Click to expand...
Click to collapse
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.

Sheist! said:
Enter fastboot, check your phone is unlocked.
fastboot getvar unlocked (response will be unlocked: yes)
If you are global, then get the fastboot version from here: https://xiaomifirmwareupdater.com/miui/spes/stable/V13.0.12.0.SGCMIXM/
This one is mine. Be careful you get the non-4g-in-the-name ROM for your 4g phone if yours is like mine:
Xiaomi Redmi Note 11 - Full phone specifications
www.gsmarena.com
Beware of the other one that has a Mediatek processor and has 4G in the name and is NOT my phone type: https://www.gsmarena.com/xiaomi_redmi_note_11_4g-11241.php
If this one fails to get you booted at the end, drop back a version and try that one. Check your phone box to see what region version phone you bought.
Unpack it to a folder and get the images for boot, dtbo and vbmeta. Put these files into your adb/platorm-tools directory in Windows. (you will need the boot and vbmeta images later if you choose to install Magisk) Since you ran adb already, then you must already have adb installed.
Open command prompt as root, change to that platform-tools directory.
fastboot devices (to ensure Windows sees you)
fastboot flash boot boot.img
fastboot flash dtbo dtbo.img
fastboot flash vbmeta vbmeta.img
Reboot system.
If this gets you booted, run Device Info HW app to see what version is actually installed, and look under About Phone as well.
EDIT: I corrected the 3 command lines above.
Click to expand...
Click to collapse
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files

mhegz said:
Sorry for the delayed reply.
It seems that my bootloader is still locked, so I cannot flash it using fastboot. Is that correct?
Is there a way to flash my device without losing my files? I really need to get my files
Click to expand...
Click to collapse
Then ignore my steps, since they won't work on a locked bootloader. I will defer to others who have clues regarding a locked bootloader and a down system.
You COULD try to unlock it, but that would definitely wipe all your data:
"Unlocking the bootloader will wipe all data"
Get the unlock tool and instructions here, if you so choose anyway:
Apply for permissions to unlock Mi devices
en.miui.com
NOTE: that gives you unlock version 6.5.224.28 but it might/should prompt you after install to install the updated version since mine is 6.5.406.31 from April of 2022. When you run it, it makes you wait a week.
NOTE 2: It does state this warning, however:
"First, confirm that your device can be unlocked
Your device functions normally and not in a bricked, soft-bricked, bootloop state."

mhegz said:
I need help, I did some research but I couldn't find a solution to my problem.
I know that others have a problem with rebooting to recovery when unlocking, but my problem is different. My phone is just stuck in a loop into recovery mode and won't boot normally even in safemode.
I haven't tried wiping the data yet because I want to save my files. Do you have a solution for this?
I turned on USB debugging before this bootloop happened.
Click to expand...
Click to collapse
I am facing same problem my phone is stuck in recovery mode it keeps rebooting I have tried selecting safe mode recovery reboot but it keeps rebooting did you find a solution to this problem please let me know.Thank you.