Database Develop

Redmi 4 (Santoni) bricked. Please help.

I unlocked my redmi 4 (Santoni) boot loader and flashed pixel experience ROM (https://mega.nz/#F!INZgnAZI!9fuWhfCuazOO5YPBjxGlmA). It was working fine for a few days (Small heating issue was there). Then one day while i was charging the phone the phone turned off and never turn back on. When i try to switch on the mi logo flashes for a split second and then turns off. I tried to get into recovery but couldn't.
I can get into fastboot mode. I tried flashing the phone using Mi flash tool and fastboot rom. But it shows an error "flash tz error". When i tried an old version of mi flash tool i get the "Unspecified error (0x80004005: FAILED (remote: Critical partition flashing is not allowed))
Please Help.....

can you access the twrp?

foneiamone said:
can you access the twrp?
Click to expand...
Click to collapse
No. I can only access fastboot.

Somebody please help...

unbrick
u can get to edl fastboot with testpoints.
redmi 4x edl fastboot
in edl fastboot flashing should work again :angel:

PierceB said:
u can get to edl fastboot with testpoints.
redmi 4x edl fastboot
in edl fastboot flashing should work again :angel:
Click to expand...
Click to collapse
Dont know how to do that. But i saw some tutorials on how to. Gonna try it. Thank you for the suggestion.

jaseemharry said:
Dont know how to do that. But i saw some tutorials on how to. Gonna try it. Thank you for the suggestion.
Click to expand...
Click to collapse
Did already share a description! https://forum.xda-developers.com/showpost.php?p=74818435&postcount=3 Or U can buy a deepflash cable this should also work.

jaseemharry said:
No. I can only access fastboot.
Click to expand...
Click to collapse
Have you tried installing TWRP via fastboot?

I had the same exact problem, i put my phone on charge & when i came back to check it was switched off. It wouldn't turn on except the mi logo. I tried to flash through fastboot turns out my bootloader was re-locked for some reason. I had to re-unlock it then proceed on to fash fastboot miui rom. Check if your bootloader is locked or not.

foneiamone said:
Have you tried installing TWRP via fastboot?
Click to expand...
Click to collapse
obstinate_penguin said:
I had the same exact problem, i put my phone on charge & when i came back to check it was switched off. It wouldn't turn on except the mi logo. I tried to flash through fastboot turns out my bootloader was re-locked for some reason. I had to re-unlock it then proceed on to fash fastboot miui rom. Check if your bootloader is locked or not.
Click to expand...
Click to collapse
This is a good idea! Probably u first try to install trwp in fastboot mode. If this doesn't work try to unlock bootloader again and then install trwp.
When all these Option doesn't work u still can open the phone and use edl fastboot mode to flash miui again.

jaseemharry said:
I unlocked my redmi 4 (Santoni) boot loader and flashed pixel experience ROM (https://mega.nz/#F!INZgnAZI!9fuWhfCuazOO5YPBjxGlmA). It was working fine for a few days (Small heating issue was there). Then one day while i was charging the phone the phone turned off and never turn back on. When i try to switch on the mi logo flashes for a split second and then turns off. I tried to get into recovery but couldn't.
I can get into fastboot mode. I tried flashing the phone using Mi flash tool and fastboot rom. But it shows an error "flash tz error". When i tried an old version of mi flash tool i get the "Unspecified error (0x80004005: FAILED (remote: Critical partition flashing is not allowed))
Please Help.....
Click to expand...
Click to collapse
No big problem just go in edl mode
Search how to go in edl Redmi 4 in Google
Problem is your boot loader is locked

Harshad patel R said:
No big problem just go in edl mode
Search how to go in edl Redmi 4 in Google
Problem is your boot loader is locked
Click to expand...
Click to collapse
but he already unlocked his bootloader before so it should be easier to unlock in again and then flash whatever he wants...

PierceB said:
but he already unlocked his bootloader before so it should be easier to unlock in again and then flash whatever he wants...
Click to expand...
Click to collapse
One time fail in flashing = locked boot loader
Or for unlocking bootloader from official (easy) need live mobile not dead

foneiamone said:
Have you tried installing TWRP via fastboot?
Click to expand...
Click to collapse
Tried but failed. Boot loader was locked again somehow.

PierceB said:
This is a good idea! Probably u first try to install trwp in fastboot mode. If this doesn't work try to unlock bootloader again and then install trwp.
When all these Option doesn't work u still can open the phone and use edl fastboot mode to flash miui again.
Click to expand...
Click to collapse
Tried unlocking boot loader and was not successful because the phone was bricked. My only option was to use edl test point. Now i installed miui 11. (Aprart from some minor bugs which can be eliminated by reflashing some other roms) Thank you guys. Now my phone is successfully unbricked.

For somebody who is having the same issues,
My phone (Redmi 4_Santoni) was completely bricked. The only thing i can access was fastboot by pressing the volume down + Power button combination. But i could not install twrp or any other recovery because my boot loader was locked. I got it fixed completely with the help of you guys (Thanks again) and i want to share the procedure i went through.
Condition: Completely bricked with only fastboot access, Locked bootloader.
I tried this video (https://www.youtube.com/watch?v=j27x5iJSS40) but failed because i could not access recovery. So my only solution was to use edl test point flashing. I followed this guide https://forum.xda-developers.com/showpost.php?p=74818435&postcount=3. It was very easy to do. But in the device manager (Press Windows key + R and then type devmgmt.msc and press enter) instead of showing "Qualcomm HS-USB QDloader 9008", the device is shown as "Qualcomm HS-USB Diagnostics 900E". The problem was you have to plug in in USB cable while the test points is being connected with a pair of tweezers or a paperclip as shown in the link above.
Make sure you already downloaded the latest mi flash tool from here https://xiaomiflashtool.com/ and download fast boot rom from the official website. (Go to https://en.miui.com/ Click rom downloads. Click flashing guide. Download the fastboot rom from there for your device.) Now flash your device using mi flash tool and voila. your phone is unbricked.
Thank you guys..

edl mode 9008 v40 very easy

(french) hello
I could not start in edl mode with the xda instructions but I found a videos
phone on android, connected to the computer by usb. you keep pressing the power button and the volume down button.
when the screen goes black immediately you strafe the volume + button for 2 sec.
the secret is the windows song if the phone is on. when you hear windows song strafe the volume +. i know I did it with my phone off and my phone on quite a few times
normally your computer will recognize the phone in the correct mode. if there is a problem do not forget to install these drivers and restart the computer as it will stay in edl mode and will be well supported.
QDLoader HS-USB Driver_64bit_Setup
MediaFire is a simple to use free service that lets you put all your photos, documents, music, and video in a single place so you can access them anywhere and share them everywhere.
www.mediafire.com
that's funny visibbly before you unlock or reflash the original bootloader the phone don't have fastboot mode with me. but fastboot don't work well in windows. it work erfectly on linux ubuntu with me at exemple.
thanks for your attention

yeah, it is very easy

So this is how you go into fastboot ?
I have the V405 EBW & I am unable to go to fastboot to get the device ID.

Doush_504 said:
So this is how you go into fastboot ?
I have the V405 EBW & I am unable to go to fastboot to get the device ID.
Click to expand...
Click to collapse
no no we should not confuse.
there is download mode in originale lg phone for flash stock roms
there is "edl mode" for unlock bootloader
there is fastboot mode when you unlock the bootloader with this screen.
a tips. root first your phone. 2 backup your firmware. 3 flash twrp. i had problem because i don't do this. there is stock firmware already rooted. its easily.

bsteph27 said:
no no we should not confuse.
there is download mode in originale lg phone for flash stock roms
there is "edl mode" for unlock bootloader
there is fastboot mode when you unlock the bootloader with this screen.
a tips. root first your phone. 2 backup your firmware. 3 flash twrp. i had problem because i don't do this. there is stock firmware already rooted. its easily.
Click to expand...
Click to collapse
Unfortunately, I am unable to root because I am unable to unlock the bootloader (because I can't go to fastboot to get Device ID & send it to LG)

Doush_504 said:
Unfortunately, I am unable to root because I am unable to unlock the bootloader (because I can't go to fastboot to get Device ID & send it to LG)
Click to expand...
Click to collapse
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.

AsItLies said:
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.
Click to expand...
Click to collapse
beware to put your phone in android oreo before the unlock...... i forget this detail. and i try to unbrick my phone with testpoint. maybe i do a howto if i succes to fix my phone.

AsItLies said:
But you can get to fastboot, just not the way you read on the internet.
The device doesn't have fastboot available, until, you put it in edl mode and use qfil to flash the 'engineering' abl. That's what gives you fastboot.
You could, at that point, use fastboot to get the info for unlock.bin. But why? because at that point you can just type 'fastboot oem unlock', and it's unlocked.
Click to expand...
Click to collapse
Oh OK
I'll have to read more about that.
Thank you

bsteph27 said:
beware to put your phone in android oreo before the unlock...... i forget this detail. and i try to unbrick my phone with testpoint. maybe i do a howto if i succes to fix my phone.
Click to expand...
Click to collapse
Unlock only works with Oreo ??
I have Pie
How do I downgrade without root ?
Is it possible ?

If I can flash a firmware without root
I'd be more than happy to flash a custom rom which has LG's apps instead of Google annoying ones.

Doush_504 said:
Unlock only works with Oreo ??
I have Pie
How do I downgrade without root ?
Is it possible ?
Click to expand...
Click to collapse
you are like me your phone is "bricked". your phone don't have download mode, fastboot mode. maybe you have
edl mode 9008. but often you have to open your phone for put it in edl mode.​wait my howto i hope fix mine today or tomorow and i wil do an howto to unbrick lg v40. is not very hard to solve it but it must a howto.

Question Black screen and hard brick

Hello everyone today i flash an incompatible rom with twrp and my screen turn completely black After reboot twrp in recovery .
Do you have solution ?
Sorry for my bad English

Hi if you can open bootloader, flash stock rom

The easy solution is press power+volume down. Phone should boot into fastboot mode. Then flash fastboot ROM without relocking the bootloader.
The other way is taking phone to service center. They'll flash stock in edl mode.

I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Doesn't EDL need authorized mi account these days? It'd better to visit service center because installing EDL driver & all the fuss will be useless

May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.

Miui 13 said:
I can't seem to put it in fastboot mode. but by pressing the 3 buttons or by changing the buttons I managed to put it in something else I think that at times I manage to put it on a fastboot but the screen always remains black impossible to know i have this message in device manager (Unknown usb devices request for descriptor) do you think it causes me to reinstall drivers what could be the cause? how to adjust as soon as i can connect it so l is not a Qualcomm USB hs 2008.
Click to expand...
Click to collapse
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).

RAMBO29 said:
May be you can find some drivers which can recognise your phone to work with ADB in fastboot and flash a new ROM. If that doesn't work, then a service center is the next best option.
Click to expand...
Click to collapse
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked

Andrologic said:
Sounds like your device boots into EDL mode, likely due to a corrupted bootloader from the incompatible firmware you've flashed. If you have the EDL firehose files for your device, you can use QFIL to flash a compatible ROM, alternatively try to EDL flash the boot partition with a working boot (that may get you from EDL to a soft brick with a working bootloader and Fastboot - from there you can try try and flash a working firmware).
Click to expand...
Click to collapse
I see it's super interesting as information I did not know that we could flash only a partition with QFIL.
Unfortunately I could not find the firehose files for the phone as the phone is probably very recent.
I had to pay someone to unlock my phone with an edl account of course .
My work now

Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Miui 13 said:
I unfortunately tried to install all the drivers but nothing has worked difficult to know if a fastboot is started it's a hassle when the screen is completely black even with the task manager open I don't I did not succeed finally I ended up paying someone who had me unlock my phone it cost me 29 € my phone is now unlocked which I can advise on the other hand for those who would like to install roms or root their phone is good it is to wait until no auth file is leaked
Click to expand...
Click to collapse

RAMBO29 said:
Was the unlocking done in person or online? Anyways glad to see it's sorted out.
Click to expand...
Click to collapse
yes it was done online I unlocked it with TeamViewer thanks to an edl account

Bricked after attempting to unlock bootloader. What now?

I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?

protatocrisp said:
I was attempting to unlock the bootloader on my V40 at&t(405ua) using the guide by Xsavi. I booted into EDL mode and used Qfil to flash the V35 bootloader to abl_a and it was successful but when i tried to enter fastboot mode it would just restart to the normal boot. I read in one of the comments that this could be fixed by flashing the V35 file to abl_b also, so i tried that. I flashed the file to both abl's but when i tried to boot i got a screen saying "Your device has failed a security check." and at the bottom says "All slots are unbootable!"
What can i do to fix this?
Click to expand...
Click to collapse
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.

AsItLies said:
Well if it's "bricked", then you can't fix it. Bricked means it's a brick, and doesn't respond.
But since it's actually NOT bricked, then maybe flash the original abl's back? Using qfil. That's the thing about edl mode, you can get to it from any screen, it doesn't have to be booted. The only thing you won't get is a timer count down from 5, so you'll have to kind of time that yourself, to start spamming the vol up key.
One other thing, with the engineering abl, the device isn't intended to be able to boot, it's only suppose to be used to unlock the bootloader, then use fastboot to flash the original ones back. The device (almost always) won't boot with those abl's.
Click to expand...
Click to collapse
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.

protatocrisp said:
Thats the thing. I booted into fastboot mode and unlocked the bootloader but when i tried to flash the original abl's it says it cant flash when the bootloader is unlocked and if i reboot it only boots into fastboot mode and when i flash the abl's in Qfil i get the screen saying that the device has failed a routine check. Thats why im unsure of what to do now.
Click to expand...
Click to collapse
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.

AsItLies said:
sounds like you've got some files mismatched / mislabeled. The engineering abl won't give you the message 'can't flash when the bootloader is unlocked'. But the fastboot you get when deleting the laf partition will give you that message.
and if you're using qfil and flashing the original abl's back, and that's all you've changed, and you get the message 'fail routine...', then you're doing something wrong. Either yer flashing to the wrong partitions, flashing the wrong files, or you've changed something else also.
Click to expand...
Click to collapse
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.

protatocrisp said:
Well im not exactly sure where i went wrong, but i can still enter download mode so would i be able to flash the stock android 9 rom?
Also if i reflash the v35 file and try the fastboot flash abl_a and abl_b it flashes successfully but when it press the power button on the phone it restarts to fastboot mode.
Click to expand...
Click to collapse
well if there's a lesson here it's that it's exceptionally important to pay attention to exactly what you're doing. Double check everything; that you're flashing the correct files, that you back up the correct files and name them appropriately, read directions over and over to be sure u understand.
it sounds like if you keep going back to fastboot when trying to start system, then you're probably re-flashing the engineering abl and not the original abl, which yer suppose to save off first.
yeah, maybe start over again by flashing a stock rom.

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.