Related
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..
Hi can somebody help me? i was on caos gsi and i tried to flash with fastboot the new global miui 12,now my phone wont boot.
i mean i still can access to fastboot and i tried to flash the gsi back,now my phone is stuck on '"redmi powered by android" but it's stuck there,no bootloop at all and i still can access recovery and fastboot
NorternLights said:
Hi can somebody help me? i was on caos gsi and i tried to flash with fastboot the new global miui 12,now my phone wont boot.
i mean i still can access to fastboot and i tried to flash the gsi back,now my phone is stuck on '"redmi powered by android" but it's stuck there,no bootloop at all and i still can access recovery and fastboot
Click to expand...
Click to collapse
May be your fastboot process failed...try again or go to recovery and clean all usure data
i tried,but now my phone is a pricey brick.
never again an mtk devices.
I have suffered this situation few days ago, I was using platform-tool to install MIUI 12.01 recovery rom using flash_all.bat but got bootloop everytime. Then I tried to flash the fastboot rom via Miflash tool and finally it booted up, it also re-locked bootloader after flashing, but the phone is live again!
I also tried to Wipe User Data in Recovery ([Volume up] + [Power]) before flashed the ROM with Miflash. Didn't know if it'd fixed the problem.
Have you try spflash tool yet?
fortunately i was able to recover the device using miflashtool then i sold it and i bought a redmi 9s
dont buy mtk devices guys,worst experience ever
You must know what you do on MTK than its ok!!!
-CALIBAN666- said:
You must know what you do on MTK than its ok!!!
Click to expand...
Click to collapse
Mtk is made for poor people..if mtk is not available then we can not buy a smart phone....
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
KnowThyPro said:
Hi ,
I have an ASUS ROG2 and I'm experiencing quite a problem here , I would like to know if this can still be rescue or not? or maybe I'm missing some steps here. here's what I've done so far.
Before it got to this dilemma my phone is suffering from autoshutdown so i rooted my phone using magisk and applied the thermal mode by one of the OP here. everything is working fine , the phone is not shutting down until today. it suddenly restart before me and it is stuck in ROG Logo.
what I've done.
1) i flash the stock boot img for my firmware version 2009.49 using fastboot flash boot 2009.49stock.img both slot A & B then followed by fastboot reboot so it can boot to system but it is still stock at the ROG Logo
2) i downloaded a RAW Firmware of 2009.49 , put my phone into fastboot mode. i made sure it was detected by the PC using the command fastboot devices and surely it was. i execute the flashall_AFT.cmd and waited , after it finishes my phone reboots but still stuck at the ROG Logo and here's the problem.
I reboot my phone into bootloader , scroll to Recovery after pressing Power button to select it , it boots and stuck at the ROG Logo at this point i'm confused since i need to factory reset it. so i downloaded TWRP for ROG2 Android 10 the one i usually use then i tried to boot from it using fastboot boot twrp10.img , it only boots and stuck at the ROG Logo again
3) I tried to flash a firmware using EDL mode , everything went well without any errors and there's the success message in Xiaomiflashtool , i reboot the phone to recovery and it is still stuck in ROG Logo.
any guesses? I'm kinda lost here since both RAW and EDL are not working.
Click to expand...
Click to collapse
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
reg66 said:
You could try booting into TWRP 3.4.0-0 Q Unofficial by mauronofrio without flashing ( fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img ) , then copy the zip over to root of internal storage, either 2009.49 or lastest 2012.65, from here. Be sure to check during flash which slot gets flashed first. Then repeat the process, booting twrp so that you can flash the other inactive slot. If you want to be sure you have changed slots, click on reboot in twrp and see which is active before flashing. Good luck
Hopefully flashing both slots successfully will do it. Let us know how you get on.
Click to expand...
Click to collapse
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
KnowThyPro said:
Hi Reg !
Thanks for replying , i think I'm using the official version of TWRP so I'll give this a try , i should overcome the obstacle of booting into TWRP..
I'll let you know the outcome.
Click to expand...
Click to collapse
Any news?
reg66 said:
Any news?
Click to expand...
Click to collapse
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
KnowThyPro said:
I used the TWRP you've linked. and i'm afraid that it is stuck on the rog logo again..
what i've done. ' fastboot boot twrpQ3400.img ' after i sent that command , the phone reboots and instead of going to twrp , it goes to rog logo and stuck there.
is there anyway i could check if there's partition? it feels like the phone has no partition that's why it is always going back to the rog logo.
Click to expand...
Click to collapse
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
reg66 said:
Did you change the name of the twrp file? the fastboot boot twrp-3.4.0-0-I001D-Q-mauronofrio.img cmd must have an identical name to the file, which as the original should be twrp-3.4.0-0-I001D-Q-mauronofrio.img
and just to be sure, you have the twrp img in fastboot folder, correct?
Click to expand...
Click to collapse
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
KnowThyPro said:
Yes i did rename it as twrpQ3400.img and yes also , it is in the same folder as my adb & fastboot folder enviroment.
i'll try a different approach maybe using QFIL? although i don't know where to start like finding the XML / Programmer or firehose..
any ideas?
Click to expand...
Click to collapse
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
reg66 said:
Well i'm running out of ideas, never used QFIL so wouldn't know. since you cannot boot into twrp (i'm assuming you didn't relock bootloader? twrp won't work with locked bootloader), you could try this thread. be sure to use the supplied 1910.35 images as it tried and tested. read posts 1 and 2 at the very least, post 2 has useful steps
if successful, you'll then need to update 1910.64 before android 10 2004.60 to start with, then up to latest
Click to expand...
Click to collapse
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
KnowThyPro said:
yes , i didn't lock my bootloader since i can still see the bootloader unlock message.. i'm also running low in ideas , for worst it is a bricked phone at best. i'll check the link.
thanks for helping. i'll still update this thread to maybe update u as well.
edit: i checked the link , i already did the xiaomi flash tool approach on the link.. everything was a success with no errors... maybe i shud give qpst tool a try? although i'm not familiar using it.
Click to expand...
Click to collapse
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
reg66 said:
did you remember to shut the phone down after successfully flashing, boot into recovery and wipe data, then reboot? as per the instructions...?
Click to expand...
Click to collapse
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
KnowThyPro said:
yes , ofcourse since the phone is in EDL mode the only way to shut it down is by using Power + volume up + volume down like around 15 seconds then phone will shutdown since the 9008 COM in device manager will be gone this means that it's no longer in EDL mode. i wait like 1minute before i power it up to recovery by power + volume down then scroll to recovery in bootloader. then with no luck still stuck to Rog logo..
it's like the recovery partition is gone...
Click to expand...
Click to collapse
I've been googling for you dude but no joy yet.... will have another look tomorrow
reg66 said:
I've been googling for you dude but no joy yet.... will have another look tomorrow
Click to expand...
Click to collapse
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Sorry bud, really not sure what's going on with your phone or know much more. Good luck with it tho
KnowThyPro said:
was able to boot the phone but can't connect to wifi and is locked by google frp :/ any guides i can follow to remove that FRP without wifi connection ?
Click to expand...
Click to collapse
Actually, if you now have recovery, what about booting into twrp and flashing lastest 2012.65 zip from asus website, twice - both slots. see if that fixes your wifi issue
As you said using the QFIL approach worked to boot into system and recovery is back - boot to twrp from that state
KnowThyPro said:
Thanks man , i'm searching for the qfil approach but i'm getting a sahara error. currently searching for fixes
edit : i manage to boot the phone using the link you've provided by using QFIL approach and not thru XiaomiFlashTool
the phone boots successfully and i can use the recovery again ! although there's a problem , it can't read my sim card and everything is like stock android without any skins or what.. i used the RAW firmware to update it but the problem with stuck logo is back :/
gonna re-flash using QFIL and i'll check some more ~ maybe use TWRP and flash the firmware there no?
edit: the one from the link is not working , stuck at rog logo.. but the one from the internet i was able to boot to system but can't detect simcard , also when plugging to PC it will go to crashdump mode.
also can't flash TWRP will result in stuck at ROG logo :/
Click to expand...
Click to collapse
I think my i messed my phone like yours. Can you provide me step by step? I have tried those step one by one but still stuck at rog logo
I don't want to brick my device yet, is there any stable working twrp recovery? Also I don't have OTG cable so not sure about the twrp in which touch is not working.
sajalkmr said:
I don't want to brick my device yet, is there any stable working twrp recovery? Also I don't have OTG cable so not sure about the twrp in which touch is not working.
Click to expand...
Click to collapse
TWRP
https://forum.xda-developers.com/f/poco-m3-pro-redmi-note-10-5g.12315/?prefix_id=33
What do you want to do with TWRP?
sajalkmr said:
I don't want to brick my device yet, is there any stable working twrp recovery? Also I don't have OTG cable so not sure about the twrp in which touch is not working.
Click to expand...
Click to collapse
twrp doesnt work for a/b devices, they dont have a recovery partition for it so even if a twrp could boot it could be useless and flashing couldnt work if im sure
1lopes said:
twrp doesnt work for a/b devices, they dont have a recovery partition for it so even if a twrp could boot it could be useless and flashing couldnt work if im sure
Click to expand...
Click to collapse
Twrp works perfectly with devices with A/B partitions.
(see threads for Xiaomi series 12 for example).
For Mediatek soc devices there is little or no development whatsoever for roms or Twrp.
The Twrp(s) for this phone are unofficial because the Team Win Recovery Project currently developed by SKKK does not provide TWRP for this device.
https://dl.akr-developers.com/?dir=skkk/TWRP
stay away from twrp for camellia. the risk is damage bootloader (it happened to my phone few days ago), with bootloop. and the only way to solve this mtkcli with phone in brom mode. a difficult procedure. so enjoy your phone without twrp. follow my suggestion
wetito said:
stay away from twrp for camellia. the risk is damage bootloader (it happened to my phone few days ago), with bootloop. and the only way to solve this mtkcli with phone in brom mode. a difficult procedure. so enjoy your phone without twrp. follow my suggestion
Click to expand...
Click to collapse
Seriously?
I have twrp 3.7.x a12 different developer version, I can enter twrp but I don't have mouse, will it damage files or partitions? (fastboot?)
Fungkyy said:
I have twrp 3.7.x a12 different developer version, I can enter twrp but I don't have mouse, will it damage files or partitions? (fastboot?)
Click to expand...
Click to collapse
if u can enter in twrp it's safe
i flashed twrp in boot partition / flash boot. I can already enter, I will flash in the advance menu to save twrp, it's safe right? And Can Back To Boot System?
wetito said:
stay away from twrp for camellia. the risk is damage bootloader (it happened to my phone few days ago), with bootloop. and the only way to solve this mtkcli with phone in brom mode. a difficult procedure. so enjoy your phone without twrp. follow my suggestion
Click to expand...
Click to collapse
Sir please help me I am in the same problem. I unlocked bootloader on Redmi Note 10T 5G and tried to install "Indonesia version of MIUI 14", but It stuck on Empty battery logo and enter into fastboot mode automatically. And show error like "dm-verity corruption" . How do you sloved the proble using mtkcli with phone in brom mode....Kindly help me sir....
vaideesh_narayanan said:
Sir please help me I am in the same problem. I unlocked bootloader on Redmi Note 10T 5G and tried to install "Indonesia version of MIUI 14", but It stuck on Empty battery logo and enter into fastboot mode automatically. And show error like "dm-verity corruption" . How do you sloved the proble using mtkcli with phone in brom mode....Kindly help me sir....
Click to expand...
Click to collapse
try this guide
https://forum.xda-developers.com/t/guide-unbrick-your-hard-bricked-mtk.4564029/
1lopes said:
try this guide
https://forum.xda-developers.com/t/guide-unbrick-your-hard-bricked-mtk.4564029/
Click to expand...
Click to collapse
I thought to try the guide given by you. but unfortunately now my phone not entering into fastboot and recovery mode. when I turn on or connect with charger or laptop, it powered on then showing " dm-verity corruption " error and automatically off then repeating the same process. What to do sir...Please help in this
vaideesh_narayanan said:
I thought to try the guide given by you. but unfortunately now my phone not entering into fastboot and recovery mode. when I turn on or connect with charger or laptop, it powered on then showing " dm-verity corruption " error and automatically off then repeating the same process. What to do sir...Please help in this
Click to expand...
Click to collapse
you should try again, but this time, with libusb to filter the usb.
check below:
https://forum.xda-developers.com/t/...ed-after-installing-gsi.4563191/post-88302451
then, retry the same process again.
Ok sir , i will try it...
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.