Xiaomi CC9 Pro (Mi Note 10)Which device? It always worked fine on MIUI 13 on my Poco F3 (Alioth).
Xiaomi CC9 Pro (Mi Note 10)Which device? It always worked fine on MIUI 13 on my Poco F3 (Alioth).
you have stable or weekly version?Which device? It always worked fine on MIUI 13 on my Poco F3 (Alioth).
Haven't run MIUI13.eu since December. I used to have stable on one of my F3 and dev on the other. Android auto always worked fine on both. I'm running MIUI14.eu dev on both of them now.you have stable or weekly version?
You must wipe or you'll have issues.Is it ok to downgrade xiaomi.eu 14 stable to xiaomi.eu 13 stable on xiaomi 11T pro without problems and without twrp? Thank you.
It has fastboot. Should i use this? 'windows_fastboot_first_install_with_data_format.bat'? Just like the first flash? Will i get anti roll back error? Thank you and godbless!You must wipe or you'll have issues.
If there's a fastboot or hybrid rom for your device then you can do it without TWRP. If not, then no.
That would be the easiest way to go. Just make sure you back up any important data you have on the device first, as this will be a clean flash.It has fastboot. Should i use this? 'windows_fastboot_first_install_with_data_format.bat'? Just like the first flash? Will i get anti roll back error? Thank you and godbless!
Thank you and godbless!That would be the easiest way to go. Just make sure you back up any important data you have on the device first, as this will be a clean flash.
No you won't trigger an anti roll back error with the .EU roms.
"S" stands for Android "S" (12), "T" stands for Android "T" (13)...Looking at sourceforge, the latest MIUI 13 update for Redmi Note 10 Pro is V13.0.18.0.SKFMIXM. But the updater in the phone is telling me that there is a newer version. It's called V14.0.1.0.TKFMIXM. I noticed that it's (T)KFMIXM instead of (S)KFMIXM. Is this just an error?
Yes, using the search function on this forum. This has been reported dozens of times and affects nothing unless you're flashing more zips after installing the rom. Before that you'll see in the log that it installed fine.Hello everyone! I'm running into an issue trying to get my Poco F2 Pro from the EOL weekly to the latest stable. The installation with TWRP seems to go fine, but when I try to restore my backup I get these errors at the very end.
failed to mount /system_root (invalid argument)
failed to mount /system_ext (invalid argument)
failed to mount /product (invalid argument)
failed to mount /vendor (invalid argument)
failed to mount /odm (invalid argument)
Am I missing something obvious? I've always done the same when going to a different version of the same rom with no issues, but last time was a while ago, so I might have overlooked something
I forgot to say that its not just the error, the phone wont boot to system and keeps rebooting to recovery. All I could find was "dont worry it installed fine", which is not my case sadlyYes, using the search function on this forum. This has been reported dozens of times and affects nothing unless you're flashing more zips after installing the rom. Before that you'll see in the log that it installed fine.
Just because the latest stable was released after the EOL weekly doesn't necessarily mean it is newer and safe to dirty flash to. You'll probably want to reflash that EOL weekly and see if you can get it to boot, then backup your important data to try wiping \data\. If it still won't boot, you're going to have to backup everything you can through recovery (ie with a usb OTG adapter and flash drive, or though ADB) and wipe anyway.I forgot to say that its not just the error, the phone wont boot to system and keeps rebooting to recovery. All I could find was "dont worry it installed fine", which is not my case sadly
First of all, thank you for taking the time to help me. I didnt dirty flash, I format data before installing the latest stable. I'm currently trying to reflash the EOL and see if I can get it to boot.Just because the latest stable was released after the EOL weekly doesn't necessarily mean it is newer and safe to dirty flash to. You'll probably want to reflash that EOL weekly and see if you can get it to boot, then backup your important data to try wiping \data\. If it still won't boot, you're going to have to backup everything you can through recovery (ie with a usb OTG adapter and flash drive, or though ADB) and wipe anyway.
You said "when I try to restore my backup".First of all, thank you for taking the time to help me. I didnt dirty flash, I format data before installing the latest stable. I'm currently trying to reflash the EOL and see if I can get it to boot.
Once i downgraded to xiaomi.eu v13 from xiaomi.eu v14 can i flash stock official global rom v13.0.8 without trigerring the anti roll back? Thank you.You must wipe or you'll have issues.
If there's a fastboot or hybrid rom for your device then you can do it without TWRP. If not, then no.
You could have probably flashed it directly from eu 14 without even bothering to downgrade first. I never had a problem going back to stock on my older Xiaomi devices, but I haven't had to in a while. There have been a few threads asking about how to return to stock recently. You should try the search function and read some of those.Once i downgraded to xiaomi.eu v13 from xiaomi.eu v14 can i flash stock official global rom v13.0.8 without trigerring the anti roll back? Thank you.
hello can you read my post and see if its normal? thanksYou could have probably flashed it directly from eu 14 without even bothering to downgrade first. I never had a problem going back to stock on my older Xiaomi devices, but I haven't had to in a while. There have been a few threads asking about how to return to stock recently. You should try the search function and read some of those.
Probably just a bug and a missed translation. If the phone is working fine otherwise, then you're fine.Hello I flashed to xiaomi.eu MIUI 13 stable rom from china stable rom with data wipe today and everything is working smoothly as far as i see but my phone model number changed to 2201116sg from 2201116sc and cpu name is also in chinese. Is this normal? Glow charging animation also doesn't work and showing blurry big lightning pic. It's my first time flashing this rom so if I'm missing something please let me know... Thank you.
ok thank you!Probably just a bug and a missed translation. If the phone is working fine otherwise, you're fine.
Ok. Thank you very much!You could have probably flashed it directly from eu 14 without even bothering to downgrade first. I never had a problem going back to stock on my older Xiaomi devices, but I haven't had to in a while. There have been a few threads asking about how to return to stock recently. You should try the search function and read some of those.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation