The system has been destroyed - Xiaomi Redmi 8 Questions & Answers

Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?

sabbath88 said:
Hello, after unsuccessful OTA update my phone doesnt boot into Android any more.
I had an original, untouched xiaomi system (not a custom one, not rooted etc).
Bootloader locked like default.
I think update.zip could be faulty - I have no idea how.
I am able to run Fastboot but due locked BL I cannot do much there.
I deasemble phone, pull out the battery, connected EDL pinouts with a wire, and all this togetcher connecter to PC.
Phone is visible by PC.
Downloaded ROM, and tried to flash via MI Flash..
On last moment I am getting error with information that my mi.com account is not athourised to do such a thing.
I tried also Mi Flash Pro founded on Cyanogenmod forum, but without luck - still getting same error.
Does anyone know how to get out from this situation or should I rather open warranty process in Gearbest?
Click to expand...
Click to collapse
Just flash a custom recovery, the device even had the offical twrp. So?? Just not into fastboot and then flash the recovery by the -- command
fastboot flash recovery recovery.img
(You have to rename the twrp file to recovery or whatever, just write the image file name instead of recovery in the second one. Ex fastboot flash recovery 123.img)
Then command
Fastboot reboot
(Hold the power up button for booting into twrp before hitting enter)
Download a miui recovery rom for your device from anywhere, I don't know I'm lazy.
And before flashing, go into mount select vendor and system if not selected.
And then select wipe
Advanced wipe
Select vendor system data cache.
Swipe to clean
Move the rom to your device
(If your device does not show up in your pc, then go into mount (twrp) select enable MTP if it's disabled, if it shows disabled then enable it again)
After that just flash your rom and then a permissive patch you can ask anyone. Or just flash pitchblack recovery. Fixed my problem of not not booting.
Sorry for the wrong format, wrote it on mobile, as I am a lazy bum.
Wut bruh.

Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.

ChakibDEV said:
Something similar happened to my friend's Poco F1. It was locked and I only could boot into fastbook, looked everywhere for a solution and found this lifesaving tool . It may work for Redmi 8 too.
Click to expand...
Click to collapse
thanks so much, that helped

Related

I need help for my bricked k20 pro!!

The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
just calm down and try to unlock bootloader again by (miflash_unlock) then install in computer (adb-setup-1.4.3) then keep press on power and volume down button for fastboat then open miflash (version=2017.4.25.0) and connect your phone and press refresh to see your phone on list then download India Stable Firmwares version in same thread you mention and unzip the file and unzip the result file then you will see 12 file (images/ flash_all.bat .....) and in miflash choose the file and press flash and wait... when its done your phone will work but will give account is locked just connect with wifi and write your micloud password and done .
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Miflash only works on an unlocked bootloader. It appears that you have a Chinese Model and you just did what was supposed to be avoided. You should get accustomed to Miflash moving forward. Never use Flash_All_Lock while cross flashing China/Global roms. You'll have to wait to unlock your Bootloader now and post that flash the China rom to get back. If any time you wish to move to the India rom, either use a twrp recovery or just use Flash_All while using the fastboot image which should eventually avoid locking the bootloader
Sent from my Redmi K20 Pro using Tapatalk
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
hippo2s said:
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Click to expand...
Click to collapse
Read this https://forum.xda-developers.com/k20-pro/help/destroyed-error-fastboot-locked-t3946012
And this
https://forum.xda-developers.com/k20-pro/help/k20-pro-bricked-t3951531
You're probably going to have to open up the phone and pay $20 for someone to use their authorised account to flash an official ROM whilst remoting in to your PC.
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
hippo2s said:
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
Click to expand...
Click to collapse
My comment was meant for OP but I hoped it would help you as well! I am personally not well informed about the Xiaomi / Redmi ownership situation when the seller unlocked the phone.. maybe you can contact them and get a corresponding password to the account, it has been the solution I have seen offered here. Maybe the emergency flash solution from Robbo.5000 works?
I just got this phone a week now and was only able to unlock and flash yesterday, I was aware of the ownership problem thanks to this forum so I bought the sealed CN version. Hope you figure it out!
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Mooatreides said:
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Click to expand...
Click to collapse
Ah alright thank you for the info! This is my first ever Xiaomi / Redmi phone haha
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Did you flash the global rom on an existing running Chinese rom or on an empty device (formatted)? Just for myself cuz I'm not sure whether to unlock and then unable to relock. Thanks.
pungky771 said:
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Click to expand...
Click to collapse
My k20 pro is hard bricked and i cant get fast boot or any thing it wont even come on. Assistance please
hippo2s said:
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
Click to expand...
Click to collapse
Could you please point me to the person you have contacted?
I'm in EDL for about two weeks now, unable to solve it by different means (seller sais 'send it back', which I'm not goong to do; S-unlock has the service unavailable, even though I've paid them and the guy I contacted there tried through TW to no avail, waiting for a 'money back' now)..

Xiaomi Mi 9 stuck in a bootloop, now with no OS. Help needed

Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.
I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode
How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )
No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom

Question Can't install fastboot roms

Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
Oh well, a phone that turns on in fastboot is not a big problem you'll say, and I thought the same as i previously had a problem and solved it by reflashing the stock rom in fastboot, so I took my nice computer (actually it's a 12 year old pc that runs on carbon, but that does its job), I opened the mi flash tool, connected the phone, selected the fastboot rom, precisely the EEA 12.5.7.0 (like the one natively installed before the damage) and started the installation. 20 minutes later ... error: cannot load bla bla bla, ok ok, i seached various solutions on Google and tried every metods, i changed the directory of the mi flash, of the rom, I updated the version of mi flash, i installed both on C:/ drive, reinstalled the drivers, i edited the batch file to remove the anti rollback but nothing, it arrives at flashing the super image and after some minutes it fails the flashing. Before you ask, YES, the bootloader was unlocked. I also tried to flash the rom in twrp, but ... the phone no longer had the twrp. The only way to start it was via command (fastboot boot twrp.img), the onekey injection did not make it permanent, and connecting the phone to the pc it revealed the device, but not the internal memory, I tried to make a format data but nothing. I managed to make it permanent only once, manually flashing only the vendor_boot and boot images in one of the boot_ * slots, in that case incredibly the pc also detected the internal partition, I copied the flashable rom and ... the twrp said to restart the recovery for I don't remember what, but basically I couldn't install the rom via twrp. At that point I finally gave up and took the phone to an authorized xiaomi service center where they fixed it (bye bye 25€), I don't know how exactly, I would opt through edl mode I think, and now i have my working phone...but heeeeeey, they flashed me the 12.0.1 TW version, not the EEA... Ahhhhh come on. They also re-locked the bootloader, so... agaaaain i re-unlocked the bootloader, this time i downloaded the unofficial tool xiaomi flash tool v2, it installed every needed driver, i clicked on "my phone works and i want to mod it", this time i tried to flash the global rom 12.5.7.9 and when it arrives at flashing the super image IT FAILS (fast boot flash_all failed, exit code:1, output: flash super error), and like a nightmare the phone was stuck in fastboot again, fool once but never fool twice, this time I had previously made a twrp backup of everything except the data partition, I install it and the phone restarts perfectly, I also notice that despite the attempted flash of the rom in fastboot after restoring the twrp backup without the data partition, nothing has been deleted from the data partition. So benevolent gods of xda, how the heck should I change rom region? Thanks for your attention and I hope I haven't stressed you out any more than I already am.
you are probably uploading rom miflashem pro and hence this error - I had the same. Use miflash's built-in pro miflash and it should go - it worked for me
SpYneX_ said:
Hi everyone, I'm writing this post to ask for your help regarding an issue that is driving me to exhaustion. I also apologize in advance for any errors. It all started after trying to overclock the gpu with the konabless app, previously the app made me make a backup of the vendor_boot image in case of post modification problems, so next i edited the frequencies of the gpu, I applied the changes, rebooted and BOOM, a phone freezed at mi logo. So I rebooted in twrp to reflash the stock vendor_boot image, and for my great intelligence I flashed it on the boot image partition, and what did I get? A phone stuck in fastboot.
---
Click to expand...
Click to collapse
1/ OMG, take your time, espace your words, compact your questions...
2/ For old configuration a user have fix adb/drivers/detection problem with an another driver pack, and a old is btter than the lastest for some old configuration (so if your conputeur jhave 12 years, maybe...)
So try to install this drivers here
Change your USB port and verify your cable
3/ If problem occur, change computer (family/friend computer), just for flash, for be sure it's a communication/usb/detection problem
PS : Finally, why trying to overclock a soc already overclock by Snapdragon and always overheat ? It's really want finding problems ^^

Question Can't boot into anything, only shows charging screen then turns itself off after. PLEASE HELP ME! How do I fix this???

Yesterday I unlocked my phone with the official Xiaomi unlock tool, Then it wiped everything, after setting my phone up, I flashed TWRP (not for my device but for redmi k20, I thought 9T and K20 is the same) and now I'm stuck on fastboot, I tried power button + volume buttons but still stuck on fastboot, I tried adb but still stuck, I tried Reiboot for Android but still stuck. So I used XiaoMiTool V2 (unofficial) and selected 'my device is bricked' then it asked me to select what device am I using, I selected k20 bc I thought it's the same with redmi power, after downloading a rom for an hour, it tries to install but fails because it detects that it's not k20, so I closed it and rebooted my device, now my device only shows the charging battery icon, can't boot into fastboot, can't boot into anything, PC can't detect my phone including adb. Please help me (for free), I really need your help. Thanks!
Your mistake was booting a wrong twrp and then a wrong fastboot rom. You could have saved your device when it was in fastboot mod by flashing an official fastboot rom for your device. But now your device seems hopeless. I think you have no option but to send it to a service center.
In this Case, buy only from Trusted Places! Or Learn how to Flash properly.
If the bootloader is unlocked...
Flash vbmeta.img
Then flash the suitable recovery for 9 power... It might boot to recovery then

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.

Categories

Resources