Related
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
knijntjes said:
You will need a recovery for adb sideload. Easiest is to use twrp, first flash twrp, and when in twrp click on sideload so the device is able to receive the files. If you are trying to sideload stock rom, you can also flash stock recovery and click sideload from there.
I guess you are now trying to sideload a rom in fastboot mode?
Edit: excuse me, i think i misunderstood you.
Click to expand...
Click to collapse
At the moment I am trying to find a way to install TWRP without an OS installed and OEM locked. In research I recognized this as the easiest way to install a new ROM. The only thing I need TWRP now.
If I were you, I'd flash the phone using the unbrick method and unlock the bootloader, so you won't lock yourself out in the future
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
This might help:
http://www.oneplusbbs.com/thread-3203158-1-1.html
I can translate this for you if you need.
You need to flash a special build of Oreo beta to be a more to downgrade to Nougat according to the thread here below.
https://forums.oneplus.net/threads/guide-how-to-go-from-oreo-to-stock-nougat.661713/
But since you've deleted everything your best bet now is the Qualcomm factory restore recover method.
https://www.google.se/amp/s/forum.x...ick-unbrick-tutorial-oneplus-3t-t3515306/amp/
TaddyQuup said:
I wanted to go back from Oxygen OS 5 to 4. And started with making a full wipe, data and system. Now I know that was my mistake. But I did it anyways because it worked the same way before as i upgraded to Oxygen OS Beta xx (An Oreo one).
For refreshing 1I did go trough some tutorials but the process was how I remembered it. I did not change the computer or reseted it since the last time. So I was confidend I still got everthing istalled properly. Driver for my OnePlus 3T seemed to have been installed, too, because I drag&dropped the files I wanted to save on my computer from my OP3T priviously.
But then I starttyped everything in cmd this came up. https://i.imgur.com/Zmo1qeD.png?1
Here is the Installation Folder of ADB with the new Rom inside: https://i.imgur.com/9RD20Ac.png
I already tried this workaround: https://forum.xda-developers.com/showpost.php?p=69648733&postcount=47
As I researched on my own the idea came to my mind that adb/windows does not recognize my device. This thing is listed in my device manager: https://i.imgur.com/VO86zuw.png
Thank you in advance! Hope u guy can help me.
Edit: After some digging depper I think I found my mistake. ADB only works when the devices is booted into OS. Which is not possible anymore for me. Now I need to find a way around that.....
Click to expand...
Click to collapse
Some things you've missed:
1. Your first screenshot shows that ADB connects successfully to your phone because it shows the device ID. So drivers and ADB are ok.
2. ADB reads files from the directory it is invoked in. Your command shell is starting in c:/windows/system, so that's the directory ADB is looking in for OP.zip. you can either cd to the correct directory or specify the full path of the OP.zip file.
So, if you reboot your phone into recovery and select install from ADB then start ADB and verify its connected then run the sideload command pointing to the correct director it should flash the ROM successfully.
Sent from my OnePlus3T using XDA Labs
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
just calm down and try to unlock bootloader again by (miflash_unlock) then install in computer (adb-setup-1.4.3) then keep press on power and volume down button for fastboat then open miflash (version=2017.4.25.0) and connect your phone and press refresh to see your phone on list then download India Stable Firmwares version in same thread you mention and unzip the file and unzip the result file then you will see 12 file (images/ flash_all.bat .....) and in miflash choose the file and press flash and wait... when its done your phone will work but will give account is locked just connect with wifi and write your micloud password and done .
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Miflash only works on an unlocked bootloader. It appears that you have a Chinese Model and you just did what was supposed to be avoided. You should get accustomed to Miflash moving forward. Never use Flash_All_Lock while cross flashing China/Global roms. You'll have to wait to unlock your Bootloader now and post that flash the China rom to get back. If any time you wish to move to the India rom, either use a twrp recovery or just use Flash_All while using the fastboot image which should eventually avoid locking the bootloader
Sent from my Redmi K20 Pro using Tapatalk
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
hippo2s said:
Hi All, I did the same thing - whoever build the UI for MiFlash should be shot - why default that selection to something that will be undesirable!!?
Anyway, i tried to flash indian rom and forgot to set to Clean All, it locked the bootloader.
So i now have redmi recovery and Fastboot options only on phone.
Have tried fastboot + miflash but all options (now with Chinese rom) - says Erase Boot Error.
Tried MiAssistant + Mi PC Suite - it is not detecting the phone in either MiAssistant recovery mode nor Fastboot mode. what is weird is the phone and connector animation on phone is correctly depicting when it is plugged in/unplugged. But the PC suite isnt detecting the device.
Soft bricked - *sigh.... any help will be greatly appreciated from the community
BTW i am more worried that the phone will run out of battery and never wake up once battery drains completely as it is in bootloop into Redmi recovery and can't be turned off (someone tell me how!?) - I don't see the phone respond to charging in any state... : (
Click to expand...
Click to collapse
Read this https://forum.xda-developers.com/k20-pro/help/destroyed-error-fastboot-locked-t3946012
And this
https://forum.xda-developers.com/k20-pro/help/k20-pro-bricked-t3951531
You're probably going to have to open up the phone and pay $20 for someone to use their authorised account to flash an official ROM whilst remoting in to your PC.
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
hippo2s said:
Some great ideas - Just tried to unlock bootloader - This device came pre-unlocked so the device is tied to the seller's account.
I have unlock permission - but unlocker say device is not bound to my account matching my assumptions - anyone know what's the best way to re-claim ownership? Especially when I can't get into ROM at all?
Click to expand...
Click to collapse
My comment was meant for OP but I hoped it would help you as well! I am personally not well informed about the Xiaomi / Redmi ownership situation when the seller unlocked the phone.. maybe you can contact them and get a corresponding password to the account, it has been the solution I have seen offered here. Maybe the emergency flash solution from Robbo.5000 works?
I just got this phone a week now and was only able to unlock and flash yesterday, I was aware of the ownership problem thanks to this forum so I bought the sealed CN version. Hope you figure it out!
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
322Reznov said:
Can you still reach fastboot? If so you can unlock phone again and flash TWRP using ADB. After that boot straight into TWRP and connect it to your computer, internal SD storage should then automatically mount. Drag and drop ROM .zip into internal storage, use TWRP file manager to move it out of the data folder and do a default wipe using TWRP. Then flash .zip ROM (for example xiaomi.eu stable) and you should be back in business. Please let me know if you need any files like working recovery image and further instructions.
I had some trouble with my TWRP recovery yesterday, flashed it on unlocked bootloader with Chinese stable ROM installed, on reboot out of fastboot it boots straight into ROM and overwrites the TWRP recovery with default recovery. I fixed it by flashing recovery again, boot straight into it and flash xiaomi.eu stable, now recovery is TWRP and does not get overwritten.
Click to expand...
Click to collapse
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Mooatreides said:
You need yo flash magisk after you flash twrp if you want to run regular miui, to prevent it from overwriting the recovery. Its the same on poco and all xiaomi phones
Click to expand...
Click to collapse
Ah alright thank you for the info! This is my first ever Xiaomi / Redmi phone haha
dsown said:
The situation is that I just bought the K20 Pro. Then i unlock and flash by miflash with Global Rom via this thread then the device has bricked and has the message "This MIUI version can't be installed on this device".
Tried boot into recovery but the TWRP has gone and the bootloader has been locked.
Flash back to China Rom by miflash is doesn't work either, help me please, i don't know what to do now, i tried every thing i can.
:crying::crying:
P/s: Sorry for my bad English.
Click to expand...
Click to collapse
Did you flash the global rom on an existing running Chinese rom or on an empty device (formatted)? Just for myself cuz I'm not sure whether to unlock and then unable to relock. Thanks.
pungky771 said:
1. if you can still enter fastboot mode, there is a possibility that you can do TWRP flashing again (the TWRP version must be correct so that the data on the cellphone can be read properly) / Flashing from the PC (if you are lucky, the flashing will work properly without any problem or you can bypass the bootloader locked using software or something else). [make sure ROM version must be appropriate because this is very crucial]
2. You can try using the test point method (EDL / Emergency Download Mode) [This method is usually used if your K20Pro is constrained by Hardbrick due to ARB4] , but this method requires you to open the case / body behind your K20Pro. and I cannot guarantee that the flashing process will succeed easily because in some cases if the K20Pro is detected damage / error due to ARB4, then you are required to have an Authorized Mi Account. I might be able to help you remotely, if you agree with the risks & requirements in the flashing process (I can lend my account, but it's not free).
Click to expand...
Click to collapse
My k20 pro is hard bricked and i cant get fast boot or any thing it wont even come on. Assistance please
hippo2s said:
Thanks guys. I am going for the Test Point solution - have made contact with the Russian tech the others did and made an appointment. I just have to pretend to be Jerry Rig before then and open her up! Fingers crossed!
Click to expand...
Click to collapse
Could you please point me to the person you have contacted?
I'm in EDL for about two weeks now, unable to solve it by different means (seller sais 'send it back', which I'm not goong to do; S-unlock has the service unavailable, even though I've paid them and the guy I contacted there tried through TW to no avail, waiting for a 'money back' now)..
Yeah, I'm not feeling very smart right now.
Short story:
Accidentally wiped OS in TWRP, now only seem to have access to fastboot. Can I fix this? Flash another ROM? Anything? Bootloader is unlocked, can't seem to get into TWRP anymore. Power + Volume up only takes me to fastboot again.
Long story:
Magisk module caused a bootloop. Wanting to try and avoid a factory reset, I tried sideloading Magisk for TWRP which didn't work, ultimately gave up and wanted to perform a factory reset via TWRP, but I've been working late and ticked the wrong box without thinking. Bad idea, I know. Wiped system, yes.
Aside from feeling exceptionally stupid, can this situation be salvaged? The phone doesn't switch off, it just sits in fastboot. I have Minimal ADB and Fastboot on my PC. Any help will be greatly appreciated, really.
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
divided by zero said:
Just in case anyone else ends up with a similar problem, the resolution was fortunately rather straightforward - I needed to grab the Mi Flash tool (as it turns out, this version worked best), stock firmware for my version, go into fastboot (which was no issue as that was the only thing my phone would do) and then open the Mi Flash tool and flashing the firmware was pretty straightforward from there. I even managed to get a BSOD during the process, but it's not like it could get any worse, anyway. Rebooted, restarted the process and about 10-15 minutes later, my phone was happily booting again.
Click to expand...
Click to collapse
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
crs951 said:
With Fastboot mode and Mi flash as fail safes , we can flash to our hears content with no worries !
Also a more automated tool is a custom mi flash tool by a developer called XiaimiToolV2 ,which has a dedicated mode for bricked phones or downloads the latest fastboot roms for you.
Click to expand...
Click to collapse
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
I had excaxtly that witha my mi5 , completely dead .
Leave it on the charger for a little bit,mine after an unsuccessful flash with mi flash (catastrophic error message) it turned back on.
IF not download XiaomiTool V2 and try the option for bricked phones.
I tried that yesterday but that option is still in development. Only the modifications one is supported currently. As for the issue mentioned, maybe it's really just a matter of charging the phone first. Can't hurt either way.
mstaglicic said:
I have similar problems , but my Mi9 is not recognized by PC and wont enter fastboot . Only sign of life is blinking white LED sometimes I connect it to charger,to PC or try to turn it on.
Can anyone suggest me what to do ?
Click to expand...
Click to collapse
Try to use the EDL mode
How to force it to EDL by key combination or maybe deep flash cable ?
My Mi account is authorized for EDL flash but I cant get Mi9 into EDL mode on my PC ( Windows10 )
No OS, but working TWRP
Hi,
I have a similar problem with my mi 9.
I followed a really bad description for the update xiaomi.eu from MIUI10 to MIUI11.
https://www.chinahandys.net/xiaomi-eu-rom-update/
It recomended to wipe alvik / Art Cache, Cache AND System :crying:
So I do not have no OS any more. However, TRWP is still working.
I have a Backup but it did not work :crying:
Is there a better option than the Mi Flash tool?
Please help me!
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
sangbuana said:
Since you already have TWRP, download the latest Xiaomi.eu custom ROM available for the Mi 9, which is 9.11.7 to your computer.
Also download the latest TWRP by Mauronofrio from XDA which is 3.3.1-42.
Then use adb to transfer both the ROM and TWRP to your Mi 9.
In TWRP, install TWRP first and manually reboot to twrp using the vol up + power button.
In TWRP, install the ROM, do a factory reset, then finally reboot.
Sent from my MI 9 (Cepheus) using Tapatalk
Click to expand...
Click to collapse
Thank you very much for your reply.
When I tried to make my TWRP backup work I had several problems.
First was "vendor read only". So I went in TWRP to "mount" and unticked the "mount vendor partition read-only" (sounds easy, took me some time to find out)
Then I was able to do the restore without error message. However just boot loop and only the possibility to access TWRP.
After some while I realized that this restored the wiped system partition.
So I flashed the aktual MIUI 11 9.11.7 again and rebooted.
And it worked perfectly! :victory:
I did no Factory reset all the time, it seems that everything is perfect!
No lags, no problems with the camera, no issues with auto rotation.
Tom
Hello guys, so, today i was trying to install miui 9 in my mi a2, then later going to update to miui 10. I was trying to install by flash mode (XiaoMiFlash) Everything was going fine, until my windows accidently turned off for updates (RIP). When my pc turned on, i was desperately opening miflash as fast that i could, but then when i try to install again it was saying "cannot recieve hello packet". I tried to restart it thinking that would fix it, but its just stuck in a MI logo with mi.com screen(Bootloop). I was trying to unplug usb cable and then putting again trying to fix it, clicking refresh to see if it appears, but it doesn't. Same with fastboot mode, doesn't get recognized. I really need help to fix it and sorry if i wrote something wrong, english is not my native language.
Same problem happened with me today. Any Solution?
Are you able to boot into fastboot?
Something similar happened to me once with the A2.
I somehow too managed to interrupt some update process and got stuck in the same scenario.
I could resolve it by getting one of these now superseded fastboot stock files with some installer scripts in them.
The scripts also wouldn't work, but I could install the firmware files one by one manually, following the script's content.
First off though, you could try to get into fastboot mode (as mentioned before), boot the official twrp img and flash the latest firmware zip file from here
Then you could go ahead and flash miui for the A2 like any other custom ROM (or did you just post in the wrong section and actually got an 6X? - seeing that you used miflash, it really seems like it..
Just in case here is the right thread for downloading miui for the A2: A2 miui port)
Yaroray said:
Are you able to boot into fastboot?
Click to expand...
Click to collapse
Hey, sorry for not awnsering for a long time. Yes, i can enter in fastboot, but the problem is that my MI A2 doesn't get recognized. (nothing happens if i try to flash it in fastboot mode).
i same that trouble, i can try to bootloader but when i connect usb to my pc it not recognized, i don't run anycommand from my PC,
I think if i change to second slot i will boot my phone, and i want to change slot without command "fastboot set active-slot "
Hello all,
I just got the V12.5.5.0 update on my Redmi Note 10 5G (Global).
After I rebooted the system tapping the complete notification it is stuck on the MIUI Recovery screen.
My device is not rooted. It just has received OTA updates.
I tried to reboot the system a few times, but it didn't work.
Also, I tried the safe mode, but it didn't work either.
After Reboot or safe mode, it returns to the MIUI Recovery screen.
I haven't tried the Wipe Data option because I want to back up my files first if possible.
Is there any way to back up my files or be able to fix it?
Please help.
Thanks in advance.
the only solution is enter into fastboot mode and flash stock fastboot firmware via miflash or similar tool
wetito said:
the only solution is enter into fastboot mode and flash stock fastboot firmware via miflash or similar tool
Click to expand...
Click to collapse
I tried that, but I am getting an error saying not allowed in locked state. It looks like the bootloader is locked, so I tried to use the Mi Unlock tool but I am getting error 1004. Also I tried wipe data, but it didn't work either. Right now, I don't care loss my data, I just want to have my phone back, any help is appreciated. Thanks
I have the exact same problem, after the update, lock on recovery mode, then when I tried to flash stock fastboot firmware it says that it is locked. And I also can't access Mi Unlock Tool for some reason, so if anybody has a solution to unlock bootloader I would really appreciate it.
Thanks
I got this same issue. Is there any way we can report this to mi? I don't mind if I lose my data rn, I just want this to start working normally again. someone please help if you know how to fix this
jyeros said:
Hello all,
I just got the V12.5.5.0 update on my Redmi Note 10 5G (Global).
After I rebooted the system tapping the complete notification it is stuck on the MIUI Recovery screen.
My device is not rooted. It just has received OTA updates.
I tried to reboot the system a few times, but it didn't work.
Also, I tried the safe mode, but it didn't work either.
After Reboot or safe mode, it returns to the MIUI Recovery screen.
I haven't tried the Wipe Data option because I want to back up my files first if possible.
Is there any way to back up my files or be able to fix it?
Please help.
Thanks in advance.
Click to expand...
Click to collapse
Same here, albeit I have Chinese version on Global ROM
wetito said:
the only solution is enter into fastboot mode and flash stock fastboot firmware via miflash or similar tool
Click to expand...
Click to collapse
Have you downgraded? Tried to, but accidentally locked bootloader. And it shows that version I have installed isn't compatible.
Use MTK Bypass for reparing https://megafon929.github.io/mtk
Timenator said:
Have you downgraded? Tried to, but accidentally locked bootloader. And it shows that version I have installed isn't compatible.
Click to expand...
Click to collapse
i'm an absolute beginner at this stuff, so could you tell me how to downgrade it?
i suppose try booting in safe mode dint work. the only solution is flashing full firmware, cause the ota packet is bugged.
try this tool
Home - Tool All In One
TOOL ALL IN ONE This tool support 67 different devices of some different OEMs. DOWNLOAD CHANGELOG XDA THREAD OTHERS PROJECTS
toolaio.tk
Timenator said:
Have you downgraded? Tried to, but accidentally locked bootloader. And it shows that version I have installed isn't compatible.
Click to expand...
Click to collapse
I received the device yesterday, the update notification arrived and I installed it, I didn't imagine it could be a problem, I tried to reinstall the rom but the bootloader is also blocked, I don't know what else to do, I'm desperate.
LucciM-Anon said:
i'm an absolute beginner at this stuff, so could you tell me how to downgrade it?
Click to expand...
Click to collapse
Rafaelmaga said:
I received the device yesterday, the update notification arrived and I installed it, I didn't imagine it could be a problem, I tried to reinstall the rom but the bootloader is also blocked, I don't know what else to do, I'm desperate.
Click to expand...
Click to collapse
Found a solution on web. If your phone is on Mediatek(I suppose all Note 10 5g are Mediatek? or no?) So, if it is, just look for an unlocker. You will also need MiFlash and I recommend to install Global MIUI 12.5.4. https://xiaomifirmwareupdater.com/miui/camellian/stable/V12.5.4.0.RKSMIXM/ - MIUI
Step by step guide:
How to Fix Your Hard Bricked Xiaomi Phone With Locked Bootloader
If you are familiar with custom ROM or flashing your phone, then there's a possibility that you have tried flashing your Xiaomi/Redmi/POCO Phone. Earlier
gadgetstouse.com
Timenator said:
Found a solution on web. If your phone is on Mediatek(I suppose all Note 10 5g are Mediatek? or no?) So, if it is, just look for an unlocker. You will also need MiFlash and I recommend to install Global MIUI 12.5.4. https://xiaomifirmwareupdater.com/miui/camellian/stable/V12.5.4.0.RKSMIXM/ - MIUI
Step by step guide:
How to Fix Your Hard Bricked Xiaomi Phone With Locked Bootloader
If you are familiar with custom ROM or flashing your phone, then there's a possibility that you have tried flashing your Xiaomi/Redmi/POCO Phone. Earlier
gadgetstouse.com
Click to expand...
Click to collapse
unfortunately this tutorial doesn't work here, I followed everything but it still didn't unlock the bootloader
Hi guys, I just woke up and my phone was in MIUI Recovery mode, just like yours.. Probably made the update automatically.
It seems this is a recent problem for many of us. I'm nowhere near an expect but I will continue looking for the solution (if possible, without whiping out the data or at least to be able to back-it up).
Will really appreciate if somebody posts if they find a solution.
Thanks!
The only solution is to wipe the phone. I got my lesson I will buy a samsung now
Hello all,
I got the V12.5.5.0 update to on my Redmi Note 10 5G (Global).
After I rebooted the system tapping the complete notification it is stuck on the MIUI Recovery 5.0 screen.
My device is not rooted. It just has received OTA updates.
I tried to reboot the system a few times, but it didn't work.
Also, I tried the safe mode, but it didn't work either.
After Reboot or safe mode, it returns to the MIUI Recovery screen.
I have tried the Wipe Data option and it worked and got me back to MIUI V12.5.4.0. But unfornnatly i lost all my files (about 90 Gb of data).
And this is the last i install any MIUI update until i see that a lot of user's have install it review it
My Poco M3 Pro 5G Global wasn't affected.
I manually download the OTA package and installed successfully.
This phone has a/b slot.
I'm wondering those facing this issue, have you tried switching from a to b slot or vice versa?
fastboot --set-active=a
fastboot --set-active=b
guyz92 said:
My Poco M3 Pro 5G Global wasn't affected.
I manually download the OTA package and installed successfully.
This phone has a/b slot.
I'm wondering those facing this issue, have you tried switching from a to b slot or vice versa?
fastboot --set-active=a
fastboot --set-active=b
Click to expand...
Click to collapse
i think the ota released by xiaomi is bugged. you're operation is correct, but a correct ota might do this automatically. i have noticed that many users with unlocked bootloader, after the update have phone that dont boot. i think they cant enter on fastboot mode. the only solution is flash using mediatek SP FLASH TOOL. or MI FLASH PRO. or ALL IN ONE TOOL
Was someone able to access the "Connect with MIAssistant" part using pcsuite?
I couldn't, but I think it might be because the USB cable I'm using is not the original one from Xiaomi or one compatible.
work only if you have installed also pcsuite on your device. if u have a full stock loked device only solutions are Mediatek tool or miflash pro! or all in one tool. as i said a million time already