Related
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Joaosacramento said:
Hello all!
I recently bought a second hand Xiaomi MI A2 online however I found a problem.
The previous owner did a factory reset on it but I'm stuck in the initial set up configuration because it asks me for the google account credentials attached to the phone. I texted the previous owner but had no answer.
So I tried to flash the official ROM to bypass the issue but I get an error message from Xiaomi Flash Tool saying "remote: Flash is not allowed in Lock State".
I think this is happening for one of the following reasons:
The previous owner didn't enable USB Debugging (thing I can't do because I'm stuck in the set up configuration)
The bootloader is locked (and I can't unlock it because I don't have the credentials of the attached account)
Does anyone knows how can I solve this problem?
Thank you for your attention
Click to expand...
Click to collapse
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
daitalos said:
Maybe you can see/ask in this thread for mia2 toolkit (I'm not sure but you can ask there )
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
Click to expand...
Click to collapse
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Joaosacramento said:
Thank you, will give it a try!
EDIT: Not working, every time I try to execute the unlock I got an error message "remote: Flashing Unlock is not allowed"
Click to expand...
Click to collapse
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Just unlock bootloader(critical too) and use miflash
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
You need to do an unlock of critical partitions - "fastboot flashing unlock_critical"
daitalos said:
(yes...normally, first you must enable "OEM unlocking" from developer option
_ https://forum.xda-developers.com/mi-a2/how-to/guide-how-to-unlock-bootloader-xiaomi-t3831484
__but first for your problem with locked device, see here for FRP apk : https://www.google.gr/search?q=com.....69i57j0l5.14869j0j8&sourceid=chrome&ie=UTF-8
__and here frp mia2 : https://www.google.gr/search?q=frp+.....69i57j0l3.7035j0j8&sourceid=chrome&ie=UTF-8
first "unlock" your device & then you can unlock bootloader easy ....
sry for english
Click to expand...
Click to collapse
Hey! It worked, thank you very much!
Face_11 said:
I also have a Mi A2 stuck in android logo screen can't can't boot into device developer options to unlock bootloader.
Fastboot oem unlock give me error flashing is not allowed.
Is there anyway around this?
Click to expand...
Click to collapse
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
daitalos said:
https://forum.xda-developers.com/mi-a2/how-to/mi-a2-toolkit-unlock-bootloader-root-t3834585
(or flash stock rom via mi flash tool/ fastboot files) : http://en.miui.com/download-353.html
follow / read fastboot quide : http://en.miui.com/a-234.html
Click to expand...
Click to collapse
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
yes it's difficult .... I understand
edl maybe work, but I'm not sure...maybe if you go to a repair shop is a better solution
(see & here : https://forum.xda-developers.com/mi-a2/help/edl-deep-flash-cable-t3828732 )
https://youtu.be/n_7RVmW2Rvs
https://forum.xda-developers.com/showpost.php?p=77327325&postcount=2
Gl
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
I would try a wipe from the recovery but if that doesnt work then just test point the phone. It isnt that hard, I had to do it myself today because of a soft brick. You just need a T3 screwdriver really. Take out the 2 bottom screws. Take a razor and slide it under the corner of the display and lift it enough the get a credit card in there. Then just work around and you should be able to get the screen off. Take the small metal plate off just above the battery and disconnect the battery and the connector on the right. There will be the test points, short them out, connect the phone to the pc(you can stop shorting out the points when it gets detected) and you have like 10-15secs to start flashing the phone in miflash(obviously you need to have the drivers already set up).
I have same problem with xiaomi mi a2 which had bootloop. Was not able to start device at all so no oem unloco no developer options and no usb debug. It was possible only adb sideload and fastboot. Adb sideload did nothing. I was trying to flash with adb sideload but it stops at 47% with message 1.00 x. Did try several roms with same results. Then i tried fastboot options. Falied to unlock not allowed. Itsl was impossible to get even into phone to activate developer options so i can activate oem unlock and the rest. I tried edl mode which did flash but then i got error message in bootloader it failed to mount system etc. Then i tried mi x6 rom to convert phone to another which doesnt have usual recovery mode but a stripped oem recovery mode. Now when u go back to mi a2 rom its bricked so there is no option of adb at all now. I tried to use mi x6 mi assistant option but app wont recognize usb connection it shows try normal mode then switch. When activating mi assistant on phone it does recognize rom version from recovefy flash in mi assistant app but when it downloads update rom version it cant continue. With pixel you can do anything with adb and it is so easy but xiaomi sucks big time. You cant do anything. Fastboot flashing unlock critical and fastboot oem unlock gets error failed. Flashing not allowed. U tried diferent cables but no luck. So now what? Thats why i hate adb. On samsung odin you can do impossible possible. Even with sp tools on mtk. Even boxes works flawlessly but xiaomi system is just thr worse. It doesnt matter if you get soemthing lost there is always a solution to other phones.
After having device sit as a paper weight for a few months, i broke down and ordered a phone repair kit. Opened device up and flashed via test point method. Worked Flawless. Time to enable OEM unlock so i don't have to open it up again. Thanks to community for all the help.
Use cmd
- go to fastboot then "fastboot oem unlock"
- go to fastboot again "fastboot flashing unlock_critical"
Flash with mi flash
Done
Just stumbled upon this and while may be 18 months too late, here's the step by step process to flash ROM on MI A2 that's giving error "Flash is not allowed in Lock State":
1) switch off device
2) enter fastbood mode (press hold power+vol down few seconds)
3) connect device with laptop
4) install and open adb folder on laptop (https://forum.xda-developers.com/showthread.php?t=2588979)
5) within adb folder -- shift + right click = open powershell here
6) fastboot flashing unlock_critical
7) step #6 may be pointless if phone is bricked but do it anyway
8) fastboot oem edl
9) find and download latest stock rom for your device (FASTBOOT version). It'll be .tgz file
10) extract the image folder from within (would be the same name as .tgz file)
11) open miflash (coudln't find link but look it up, it's easy)
12 select the image folder you extracted in step #10
13) click refresh. device name appear means it's recognized
14) from bottom of mi flash tool select whatever you want. I do "clean all"
15) flash (top right mi flash tool)
Face_11 said:
Thanks. I've tried the MIFlash Tool and I get Error Flashing Not allowed in Lock State. I've also tried the MI A2 ToolKit and get the same message. Basically anything I try and do states device is locked or unable to run in Lock State.
Boot Loader is currently locked and I cannot access developer mode to enable OEM unlocking. Question I have is :
- Can I use EDL Cable to work around this or do EDL cables not longer work with Newer Xiaomi phones?
- If EDL cable doesn't work, is the tespoint method my only option.
thanks in advance
Click to expand...
Click to collapse
Flashing is not allowed in lock state
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
IamUmesh said:
i got a error recently in my mi a2 no software is installed but locked.
when i try to flash from mi flash tool it says flashing is not allowed in lock state
when i try to unlock in cmd flashing is not allowed in lock state
is there any one to fix this
Click to expand...
Click to collapse
you need to open phone with screwdriver & do the test point ..search for video on YouTube...then EDL deepflash state you can use miflash to put back OFFICIAL only rom to device.
Here we go:
1- Today i got a new phone
2- Wanted to remove the Google search bar and disable google app
3- Restart and the phone screen is very different like another version, so i decide to do a soft reboot
4- Phone stuck on auto loop
5- Try recovery mode, dont work
6- Fastboot works
7- I download new room jasmine_global_images_V10.0.12.0.PDIMIXM_20190712.0000.00_9.0_1e580ee45b
8- Download Miflash and Minimal ADB and fastboot.
9- Plug the phone in pc
10- Unlocks OEM with app
11- Opened Mi flash
12- Miflash have installed all the drivers
13- When i click on refresh the Fastboot icon(the android and the soviet cat) dissapears and the only thing i have is in one corner "press any key to shutdown"
Important data:
-i have windows 10 with usb 3.1 and 2.0
-USB debugg is locked
-By pure luck once i managed to do a full boot sequence but when it finished the layout of the screen was different, like another version and i started updating it, after a couple of updates it stuck again on bootloop.
- i have no idea what was the original version on the room but in the last point and in nº 3 it was 10.0.7.
- i have nothing that i cannot recover so i dont mind wiping out my userdata
-i have considered a test point but i dont know if it going to work
-return it to amazon its my last ressort
- i read about the issues in december and january with the bootloop but i tried everything
-i have acces to a computer with linux
-its very difficult to start the fastboot logo/menu and almost impossible the recovery mode, it almost always ends with phone booting, when i plug it onto my pc it start with the bootloop.
-sometimes when i click on refresh while the phone with the screen in black or starting up with the android one logo it changes to fastloop automatically
- also tried a hard resset and nothing changed
I have no clue what to do, should i do the test point, ask for another in amazon, spray it with holy water??
Sorry for the possible typos and all the numbers i wanted to explain myself and to put some order in my head.
Please help and Thanks in advance
Fastboot rom
Try FASTBOOT method to unbrick your mi a2,
Karthickvel1988 said:
Try FASTBOOT method to unbrick your mi a2,
Click to expand...
Click to collapse
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
SrBisectriz said:
My PC does not recognize the phone and when i click on refresh the fastboot icon goes out and i can only se "pres any key to shutdown"
Click to expand...
Click to collapse
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
K9998 said:
I think you should connect your phone via USB 2.0, from my previous experience, the USB 3.0 port will give press any key to shutdown message on your phone
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
SrBisectriz said:
Does the same
I gave up
Using the fastboot mode and the adb voids the warranty?
Click to expand...
Click to collapse
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
K9998 said:
In this case I think you haven't unlock your bootloader, or haven't unlock both OEM and critical. Following up your steps, you didn't mentioned this part.
Have you done these codes?
fastboot flashing unlock
And
fastboot flashing unlock_critical
?
Select OEM unlock in settings doesn't unlock your bootloader automatically
Sent from my Mi A2 using Tapatalk
Click to expand...
Click to collapse
I tried these and only worked once or twice
But mi Flash did not recognise the phone
SrBisectriz said:
I tried these and only worked once or twice
But mi Flash did not recognise the phone
Click to expand...
Click to collapse
Mi flash required both unlock to do the work.
Sent from my Mi A2 using Tapatalk
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Bump.
Bump.
Bump.
Xenomorphs said:
Hey,
So, basically, I'm having this issue where my phone fails to enter fastboot mode. It just gets stuck on the screen. I can restart normally if that happens by just holding down the power and volume down button, but I really don't get why it isn't booting into fastboot properly. Anything I can do to fix it? I'm on 12.5.9, Redmi 9T Global version. I need to boot into fastboot in order to install TWRP, and I can't do that due to this issue. Also, as a side question, how can I downgrade MIUI?
Thanks in advance.
Click to expand...
Click to collapse
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
qwertz512 said:
Have you tried using adb and fastboot method. Try using adb to force boot it into fastboot
Click to expand...
Click to collapse
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Xenomorphs said:
Any detailed steps for that? Right now, I'm facing another issue, too, where I apparently have an update (MIUI 13), but it can't verify it, hence, not installing it.
Click to expand...
Click to collapse
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
hakudayo said:
Enable developer options and enable usb debugging after that download android adb tools and adb drivers for your phone. After that you have installed everything go to the directory where you have adb installed and from that open a elevated command prompt and type in "adb devices". It should say a random string followed by device (if your device is plugged in) After that type adb reboot bootloader and it should reboot into fastboot. For the update issue I've had that too its when the download was interrupted mid-way and it got corrupted somehow and the md5 doesn't match. Make sure to download it on the screen without turning off the screen or switching off to others apps.
Click to expand...
Click to collapse
Thank you so much. I'm going to try.
Xenomorphs said:
Thank you so much. I'm going to try.
Click to expand...
Click to collapse
No problem if you have any questions just ask me
Now I'm stuck with this same issue.,
Got into this while trying to boot TWRP OrangeFox-R12.1_3_A12_FBEv2-Unofficial-lime.zip on xiaomi A12 ROM
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
I cant go to service center as my device is out of warranty
in google there is a pc program than can unlock bootloader of mediatek devices, search for it
Bro i cant access the bootloader, so unlocking it doesnt make any difference
I want to restore the bootloader.
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
Okay so first of all download "mtk client"
Than open the mtk client
It will give you instructions on how to connect your phone, take back of everything except system(super),vendor and userdata. Tap on flash tab there you'll notice a option called unblock bootloader tap on it and your bootloader will be unlocked
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Manmeet_2008 said:
Bro Will this restore my bootloader or only unlock it because if it only unlocks then your help wont work.
Click to expand...
Click to collapse
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Ok bro thanks for your help
tutibreaker said:
you dummy, you need to unlock the bootloader in orden to restore it installing the firmware with miflashtool or mtk client .
Click to expand...
Click to collapse
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
try some sp flashtool that come with miflashtool , turn off phone and press volume- and plug the cable in , some type of mtk download mode
Ok bro i will try tomorrow
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Manmeet_2008 said:
Hello everyone, today i used the tool but when i went through the tool i saw a 'erase flash' option in mtk universal tab. Can anyone please tell that what this option is used for and ticking it will lead to any sort of issues?
Click to expand...
Click to collapse
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
tutibreaker said:
dont use it, will erase all the device data and partitions turning it into a useless brick, dude, in youtube there a lots of tutos to how restore original firmware go check them first
Click to expand...
Click to collapse
Ok bro thanks for telling, will not use it for flashing
Did it work is it debricked?
Manmeet_2008 said:
I have redmi note 10s. I bacame bored of miui because of several bugs. So i decided to mod the device with a nice custom rom. I started the process. Because it is a mtk device, it has complicated flashing process than snapdragon devices. I entered the fastbootD mode and cleared the system by using adb command(which i dont remember). Then i flashed the custom rom. By mistake, I locked the bootloader by typing adb command fastboot oem lock. But now due to complicated case, the device is showing your system has been destroyed and when i try to force reboot it into fastboot, it still give systen destroyed error(means fastboot mode is inaccessible). Can anyone please help me to fix this issue without using edl pins? I am in a great issue
Click to expand...
Click to collapse
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
hookkrox said:
You need to sSee this video,
Make sure Disconnect your phone battery then start flash
Click to expand...
Click to collapse
You need to see the PM I've sent to you. You will find it here.
Start from BROM mode - that is always available. Then you can use mtktool to restore everything. I have an article about it on my blog, but I am not supposed to post it here... find it in my profile, or send me a PM for help.
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.