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
Related
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Don't worry have you backup you data?
if you have, just install the driver for qhusb
then your phone should be able to recognises by MIflash then flash any fastboot rom, You phone should be good to go.
I had a similar issue but i tried to hold the power button for like 30 seconds and the phone booted. If it didn't work, you should follow this thread: en.miui.com/forum.php?mod=viewthread&tid=73348&highlight=Mi3%2Bunbrick&mobile=no
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
murattiy said:
partition error
u must download fastboot rom this link : http://en.miui.com/a-234.html > Xiaomi Mi 4 CDMA/WCDMA/LTE Latest Global Stable Version Fastboot File Download
and unzip change flash_all.bat file special this flash_all.bat link https://drive.google.com/file/d/0B2UMSvqNe0deMXFVeE13VGNHTTg/view
use flash_all.bat after max 6 minutes ready your phone
Click to expand...
Click to collapse
Did you personally tried that? Because flash all bat do uses fastboot to flash, which can't be accessed.
I wonder whether the other one u poster doesn't use fastboot, cant check the file content atm
I have tried many times
last times tried 3 hours ago, for alpha 5.12.24
my video under explain
http://m.youtube.com/watch?v=fSl9xrR_J4g
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
you need to do İnstall spacial flash_all.batt change to in flash_all.batt "cancro_global_images_V7.0.5.0.KXDMICI_20151016.0000.3_4.4_global"
dont use miFlash .. enough u clik speical flash_all.batt
If your device not boot into fastboot/recovery mode press power button for around 30-40 seconds .
and still not boot into fastboot/recovery mode
battery cable exist than try.. i tried many times))
Me_Ashish_ said:
I installed the latest 12.24 alpha version (http://bigota.d.miui.com/5.12.24/miui_MI3WMI4WAlpha_5.12.24_1e8fc7c2ed_6.0.zip) of MIUI 7 - MM (someone posted link on CM13 thread: http://forum.xda-developers.com/showpost.php?p=64500712&postcount=154)
I was on extended partition before. Everything succesfully got flashed in TWRP. But after rebooting system, phone died.
Connecting to PC I can see the device as QHUSUB (might have misspelled) and can see lots of drives connected (which it asks to format to use, which I won't as it ends up badly)
Any solution now? Otherwise like last time it got bricked, I will wait a day to battery get drained and than possibly hope for Fastboot to come back though I believe this issue can be fixed via PC only, not sure.
And I guess it got bricked due to extended partition as the ZIP probably merges both System.
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Prince Chandela said:
From where can i get QHUSUB Bulk drivers?
Now Mi4 is not even getting detected by USB?
Click to expand...
Click to collapse
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
coolkillermax said:
Currently i installed Kingroot in slimbit LP rom but after see people suggest method i uninstalled it & follow him tap root access in devolopment section & reboot but still not get Root access Than i try go in TWRP restore back this rom my phone stuck+ bootloop & keep loading in MI logo only !!! Pls help HELP HELP !! What should i do... i try fastboot flash fastboot rom failed too HELP HELP HELP !!!
Not going to send to phone center & currently my ROM can't not boot because of extend partition before & not stock partition... Help me PLEASE !!!
Click to expand...
Click to collapse
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
回复: Bricked Mi3 - Showing QHUSUB Bulk in PC
Prince Chandela said:
You don't need Qhusb driver. secondly can you boot in fast boor mode (power +vol-)?
Click to expand...
Click to collapse
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
coolkillermax said:
Fastboot can & if press volume up+power button Phone won't boot to twrp recovery… Just MI logo blinking……
Sent from S660 using xda premium 4
Click to expand...
Click to collapse
flash miui fastboot rom then
Prince Chandela said:
flash miui fastboot rom then
Click to expand...
Click to collapse
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
coolkillermax said:
Flashed many ROMs including MIUI 7 fastboot ROM = Not working After flash MI logo keep blinking
Click to expand...
Click to collapse
can you boot in recovery now?
Prince Chandela said:
can you boot in recovery now?
Click to expand...
Click to collapse
No...
http://forum.xda-developers.com/xiaomi-mi-3/help/mi3w-lost-partition-userdata-img-t3293583
Me_Ashish_ said:
@murattiy that flash file didn't help either as it was based upon fastboot
But, the device was directly detected in MiFlash and simple flashing made it run lol
Click to expand...
Click to collapse
Really need your help..
Can you explain it further?
please..
Thread Closed
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Arnys said:
tell what you did, to brick phone.
what android version was before, what android wersion you tried to instal, what recovery you used. ?
oh, but if fastboot isnt working, you more or less are done. if im correct, even dc phoenix use fastboot..
"Step 1
Write compatible UPDATE.APP file in fastboot with DC Phoenix"
Click to expand...
Click to collapse
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
vinfrix said:
i just use the SRKTool Lod Chan and try to unlocked the bootloader
and it success , after that i proceed to replace recovery with TWRP
but doesn't work . afterwards i bring back to re-lock bootloader
then the phone reboot . the phone stuck at android boot logo
no recovery no fastboot cannot identify even in PC
but when the phone gets drain and i plugged the charger on it
the phone reboots directly into the system or its OS
but when i try to power it off again ( reboot )
the same thing happen it will stuck in the boot logo
until the battery dries again ,.
i never upgrade to Nougat so my phone still in Marshmallow version
thank you .
Click to expand...
Click to collapse
what wersion of twrp ? link. there are MM and N versions, and, if you on MM put N version twrp, you will brick phone.. and, even with dead battery i was able to enter fastboot, when i instaled wrong twrp. but for me solution was simple, instal right twrp and all was good (ofcorse if you didnt delete system)
i can't remember the version but im sure it all arounds in 2.1...something
no i wasn't load the Nougat version because i know i am MM the only thing i remember is the TWRP i load is from SRKTool Lod Chong there was an option there to install twrp recovery
can i be able to enter the fastboot ?
if i can go over to fastboot i can repair this
but i can't go fastboot
volume rocker technique doesn't work
even using adb reboot bootloader too
when i am doing volume down ( hold )
the phone only vibrates then stuck at logo
even when its connected to adb command
when the phone reboot it stuck at the logo
can't go to fastboot ?
is there any way of forced
reflash the boot.img & recovery.img?
Hi, i have P9 L19 with C432 B210 i want to update do Android 7, but mistakely put wrong UPDATE to phone memory. Now I'm stucked at Huawei logo and cant turn off device.
Only I can get to Fastboot&Rescue Mode. After press all three buttons nothing happened, phone juest restarts and stuck at logo. I tried put right UPDATE to SD card but no luck
Bootloader: locked
FRP: locked
debbuging: off
Please help me.
no one knows how to fix our problem so sad
Please close the thread
problem issue solved!
please help me same problem as you...
JCB117 said:
please help me same problem as you...
Click to expand...
Click to collapse
Easily Unbrick Your Phone via this method
https://forum.xda-developers.com/p9/help/huawei-p9-brick-easiest-to-unbrick-t3662350
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Reflash miui with miflash, be sure yo untick the lock thing onnthe bottom sonyoubdont lock bootloader, then try again.
Sounds like partition is fked
Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.
Robbo.5000 said:
After flashing TWRP and still in fastboot, hold power and vol+. Keep both held while it reboots, it takes a few seconds. When the Redmi logo appears and the phone vibrates release the power button. Keep holding the vol+ button until it boots into TWRP.
Click to expand...
Click to collapse
this was the first thing i tried, but it keeps rebooting to fastboot, if i hold it longer it wil just reboot again. i've tried miflash, but miflash can't find a flash all.bat and when i go into explorer i can't find it either.
problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along
Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks
kh805794 said:
Hey glad to hear you solved the issue. What version of TWRP did you end up flashing and what tool did you use to flash it? I'm facing a similar issue.
Thanks
Click to expand...
Click to collapse
I can't answer for OP, but he looks to have abandoned the thread.
What I can recommend from personal experience is that using latest version of TWRP - I think it's 4.3.3 (can't tell you exactly, as I'm writing this without checking my laptop on which I have the TWRP and ROM files) - will resolve all your problems.
Thanks for your reply I actually just managed to get root/TWRP/Magisk to work. A lot of the TWRP recovery images that I encountered just caused the phone to boot loop or get stuck on fastboot mode.
The TWRP that worked for me was twrp-3.3.1-15-raphael-mauronofrio.img
following:
fastboot flash recovery twrp-3.3.1-15-raphael-mauronofrio.img
For reference I have the global Mi 9T Pro
Rikkertbiemans said:
problem solved, i installed another version of twrp, deleted it and reinstalled the first one. thanks for all answers, it really helped along
Click to expand...
Click to collapse
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses
camelCaseOnly said:
I am also having this issue, after doing the exact same thing you did...
Would you be able to post the download link you got your TWRP version from? And maybe go into a little more detail about the reinstalling order (if that is important)?
Also the "mauronofrio" version didn't work (I have the Mi 9T), are there any other options out there?
Many thanks for any responses
Click to expand...
Click to collapse
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.
theCroh said:
Did you ever get this solved? I'm in a similar situation after what I thought was a normal ROM flashing.
EDIT: Nevermind. Got it fixed using MiFlash.
Click to expand...
Click to collapse
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers
Rikkertbiemans said:
im really stupid, i was installing twrp, i did a advanced wipe to afterwards install a custom rom, and when my phone was done wiping i accidentally pushed the power button and turned of my phone. now it is stuck in fastboot mode. i tried reinstalling twrp but i can't boot into twrp, it keeps turning on in fastboot mode
thanks in advance
Click to expand...
Click to collapse
Flash images manually mr
camelCaseOnly said:
Hey sorry didn't see your reply... I haven't had time in the last month to look at it so I'm still stuck. How did you fix it using MiFlash? Did you make it force load TWRP onto the phone or something?
I think there is definitely something wrong with the partition, as when I plug it into the computer it no longer comes up in "my computer" - although I do have the MIUI recovery working again.
Cheers
Click to expand...
Click to collapse
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)
EpickBroVlad said:
Flash images manually mr
Click to expand...
Click to collapse
Where can I find the right commands for flashing
theCroh said:
I just flashed a full fastboot MIUI ROM in fastboot using the MiFlash portable tool. No need to do anything in recovery.
Edit: You can find fastboot ROMs from the OP of this thread https://forum.xda-developers.com/k20-pro/how-to/redmi-k20-pro-firmware-10-3-8-0-9-6-13-t3939647/ (labeled as ...fastboot)
Click to expand...
Click to collapse
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)
camelCaseOnly said:
I'm still not able to get TWRP working... I think all of my problems will be solved as soon as I can get into it, but each time I load the recovery image on (using command prompt) it says it completes, but when I try to reboot it into recovery mode it never works (if I use command prompt to reboot into recovery it just shuts down but if I hold the button combination it either reboots back into fastboot or the original MIUI recovery mode - and yes, I am using the right button combinations).
I've tried every version of TWRP I could find, so I'm certain its not a problem with the recovery image itself... Have you or anyone else had this happen before? It's so infuriating that it just doesn't work, but I don't know why...
BTW the commands I'm using are
Code:
fastboot flash recovery "recovery.img"
(which works) and then
Code:
fastboot boot "recovery.img"
(which gives 2 OKs, but the phone just turns off).
(this all after setting the directory to my adb folder)
Click to expand...
Click to collapse
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
claudioita said:
This worked
https://forum.xda-developers.com/k20-pro/development/recovery-unofficial-twrp-xiaomi-redmi-t3944363
now shall I keep read only or allow modifications?
Click to expand...
Click to collapse
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).
solution
you need the version for youre board if you open aida64 on youre phone is says davinci on my xiaomy mi 9t so download the twrp for davinci and it works i had the same problem too stuck in fast boot , im new to this this is my frist time im trying to install a new beta for miui
camelCaseOnly said:
Unfortunately I wasn't able to access that link for some reason, but I did FINALLY manage to get it to work using another version from this thread; specifically the 4PDA 3.3.1-3 build and instructions referenced in the original post (I was using MIUI 11.0.1.0 at the time).
Click to expand...
Click to collapse
Yy
help!
my honor 9 lite bootloader is unlocked and i have installed an unknown kernel and now when i want boot into twrp it will boot into stock recovery and when i flash twrp and boot it will boot into stock
i tried all of twrp versions :|
wtf should i do?
plz help me
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Already tried power and minus option.when you connect to a desktop what does it say ?
Dokrak99 said:
Already tried power and minus option.when you connect to a desktop what does it say ?
Click to expand...
Click to collapse
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
That's bad.
Hold the power +/- longer then 15 seconds try both.
Second
Charge for about 10 minutes and try the same again.
Last drain it when down keep pushing the power button to flat it.hook it up on desktop and install miflashtools.or try power +/- again
Dokrak99 said:
Hold the power +/- longer then 15 seconds try both.
Click to expand...
Click to collapse
Same as:
LordRedstone05 said:
It goes on and Windows makes the sound for a new device connected, and then it goes off again, and Windows makes the sound for disconnecting a device. This repeats for around 4 or 5 minutes then it goes finally off.
Click to expand...
Click to collapse
Dokrak99 said:
Charge for about 10 minutes and try the same again.
Click to expand...
Click to collapse
When I try to charge it it goes in the bootloop again until I disconnect it and the battery runs out.
Dokrak99 said:
Last drain it when down keep pushing the power button to flat it.
Click to expand...
Click to collapse
It goes on, shows this battery icon, that it's empty and goes off. This repeats until I release the button.
Dokrak99 said:
hook it up on desktop and install miflashtools.or try power +/- again
Click to expand...
Click to collapse
The miflashtool does nothing when I click on Flash with the images and scripts loaded. Power +/- does the same as before.
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Dokrak99 said:
Sorry I thought flash tools had a option in top for selecting boot options.There is a mi tool around where can select the boot options.i need to search on my desktop what it was.we need to trigger it in fastboot/recovery mode some how.most likely it was xiaomi tools V2 but I really need to check it.tools V2 got a bricked option do.but since it restarts everytime it's pretty long shot
Click to expand...
Click to collapse
Thanks in advance
What should I do in this tool? The tool doesn't recognize my phone. It brings nothing since I cannot access Fastboot.
Well basically there is only one real option left . contact mi service center because mi don't support or they closed there download,edl support on there phones to prevent rom swapping .there is a edl cable with mtk support around but that's a long shot.because I never had a messed up phone like this.at least not one with mtk.without recognise you're desktop I don't see a fix in this to get in fastboot or flash it.
Download platform tools drop it on c:/ so c:/platform tools .install abd drivers package if you didn't have it.go in platform tools the top line and tick Cmd hit enter.try command : fastboot devices .try a few times if a number pops up you can try .fastboot reboot fastboot
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
TWRP bricked my redmi Note 9 too, but i had ADB Connection in the black Screen so i rebooted to Fastboot over ADB and reflashed the Stock rom
LordRedstone05 said:
A couple days ago my Redmi Note 9 (merlin) 4/128 GB NFC automically installed the Update from V12.0.3.0.QJOEUXM to V12.0.4.0.QJOEUXM over night. I had rooted and installed a TWRP on it. As I had noticed that it was not rooted anymore I tried to reflash the TWRP over Fastboot because it was overwritten by MIUI. When I tried to boot the twrp.img the phone did so and the screen was on but black. After 4 or 5 tries it hanged up in a bootloop and I cannot access Fastboot Mode or something else anylonger.
Is there something left I can try?
Click to expand...
Click to collapse
Did you find solution on this? Please answer bro i need your help
Jayson Galang said:
Did you find solution on this? Please answer bro i need your help
Click to expand...
Click to collapse
Unfortunately i haven't found a solution. I had to send it to a service center 2 Days ago. Sorry, that i couldn't help.
the right driver is mtk this is not adb nothing happens the this you could fixs is
go to the nearest techniciann beacause they need special tools to fix properly
Is your phone still bricked, If yes, I can provide link for the factory firmware recently released for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
Communos said:
Is your phone still bricked, If yes, I can provide link for the factory firmware recently leaked for Merlin, You could give flashing that in SP Flash a try, does not need auth account.
Click to expand...
Click to collapse
yow is that legit? Had my redmi note 9 bricked for a week now.
CruisaderX said:
yow is that legit? Had my redmi note 9 bricked for a week now.
Click to expand...
Click to collapse
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If it keeps restarting, you've made any wrong modification. You need to follow your steps back and try to unmake your modification.
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
If you are using V12.0.5.0 or higher, TWRP will not work.
If you want to use sp flash tool, you need to flash the stock rom preloader using V12.0.4.0 (or lower). (It will works perfectly with lower preloader binary version).
With an older preloader version, your phone will can receive DA files and accept flashing with NO auth.
Everything you need to do is plug your phone in usb (without press any key, if you press any key it will enter in EDL mode and requests authenticaion).
Here, are PRELOADER binaries for flashing: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4221081/
Here, are DA files for flashing using flash tool: https://forum.xda-developers.com/t/...omi-redmi-10x-4g-xiaomi-redmi-note-9.4209767/
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
VD171 said:
If you got bootloop after flashed magisk, you need to flash stock rom boot.img.
If you got bootloop after flashed TWRP, you need to flash stock rom recovery.img.
If you got bootloop (or black screen) after flashed misc partition, you need to erase misc partition.
If you are using V12.0.5.0 or higher, TWRP will not work.
Here, you can find boot images for original stock and magisk patched: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If you want to keep TWRP working on V12.0.5.0 or higher, you need to flash the stock rom lk partition using V12.0.4.0 (or lower). (It will works perfectly with lower lk partition version).
Here, are LK images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4218925/
If you want to disable TWRP, you need to flash stock rom recovery partition.
Here, are RECOVERY images for flashing: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204671/
If your device keep booting in recovery (or blackscreen), you need to erase misc partition.
Here, is the guide for erasing MISC partition: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4209299/
If you want to know what is working for MERLIN, take a look: https://forum.xda-developers.com/t/...omi-redmi-note-9-xiaomi-redmi-10x-4g.4204873/
Good luck
[/QUOTE
Click to expand...
Click to collapse
I tried actually before after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting), I will call this state 1 brick. In state 1 brick you can still access fastboot mode normally. Then i tried to flash twrp hoping to just flash a rom to fix it leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot bootloader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi devices. Now I am stucked with a hard bricked note 9 with no way of fixing.
CruisaderX said:
i tried before actually after failed attempt of flashing twrp. First, I got my redmi note 9 bricked after following one of the guides posted here (rooting, I will call this state 1 brick. In state 1 brick you can still access fastboot mode. Then i tried to flash twrp hoping to just flash a rom leading to state 2 brick. In state 2 brick, it seems like it is stucked on recovery (btw the recovery is only displaying black screen) and is classifying fastboot as the bootloader, meaning you can boot into fastboot using adb command reboot boot loader. Then I followed one of the guides here again and then it managed to lead my device to state 3 brick. In state 3 brick it continuously boot looping only displaying the boot image for a second then repeat. Normally it can be fixed by flashing a stock rom using sp flash tool but not with xiaomi device. Now I am stucked with a hard bricked note 9 with no way of fixing.
Click to expand...
Click to collapse
You need to read every line and every word careful and follow only specific guide for your specific problem.
If you try to do anything you see, obviously you will cause more damages to your device.
Please, read my post again: https://forum.xda-developers.com/t/redmi-note-9-merlin-4-128-nfc-hard-brick.4201717/post-84379823
If you can't enter in fastboot mode or recovery mode, you need to flash stock rom using sp flash tool.
If you are using V12.0.4.0 or lower, you can flash without EDL and authentication.
If you are using V12.0.5.0 or higher, you need EDL and authentication for flashing.
Do you need help with your MERLIN device ?
Read this FAQ: https://forum.xda-developers.com/t/...for-merlin-redmi-10x-4g-redmi-note-9.4225177/
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.