ROMs won't be published as a fastboot version if a TWRP is available.hi I installed the stable version 13.0.12 fastboot for my mi 11 ultra sucessfull, now for updating it I tried to install the twrp already with the global rom and now also with this one, but without success, it always can't detect internal storage I tried different fixes but no results, I dont want to wipe data again so my question is will updates be released via fastboot?
I got bootlooped. After a clean flash everything is ok.It should work without format data with the same security patch.
you haved used to 99% the wrong twrp… rec boot its mentioned in my guideIf someone might feel this useful... Since new Xiaomi.eu version requires TWRP (no fastboot version anymore) tried to use the TWRP for DITING.
According to the playstore app, it was a A/B version.
fastboot.exe boot twrp.img did not work. Resulted on this.
TWRP "Failed to load/authenticate boot image: Bad Buffer Size
That's the error that appeared, so reading guides, since it was A/B device, it shouldnt let flash the stock recovery... To my surprise it did flash but phone remained on Fastboot screen boot loop.
To fix this... flashed fastboot xiaomi.eu version for DITING (12T Pro) and then it let me enter to recovery (TWRP).
Then had to format data so SSD would appear, transfered ROM and flashed ROM.
Nothing to do with the ROM. It's an old Google issue that has been reported on devices of other brands as well.Small possible bug, but the At a Glance widget no longer opens the calendar app on the Redmi nNkte 10 Pro in the recently released build.
Tried it, didn't work. Boots to lockscreen, reboot loop...Based on these, am I right I can flash my Mi 10T Pro from weekly 22.10.26. to MIUI 13.0.7.0 stable? Both versions have november security patch. Will not be necessary a factory reset after it?
Yes I think soIts possible to upgrade with MIUI 12 and Android 11 to MIUI 13 normally?
Seems like your country might be blocked from receiving OTA info.I updated the device from version 13.0.5 to version 13.0.6. However, it gives a warning as seen in the safety-related pictures. How can we fix this problem?
Thank you. How can I understand this? Are there any steps I can take to resolve this issue?Seems like your country might be blocked from receiving OTA info.
Oh ok. Just started happening after the update so just assumed.Nothing to do with the ROM. It's an old Google issue that has been reported on devices of other brands as well.
I know yet.Tried it, didn't work. Boots to lockscreen, reboot loop...
If you can't access miuipolska.pl, then it is in fact a country block.Thank you. How can I understand this? Are there any steps I can take to resolve this issue?
Your answer gave me the idea. I installed vpn and checked for Update again everything is fine now. Thank you.If you can't access miuipolska.pl, then it is in fact a country block.
It's a geolocation block, so unless you move to another country, you can't resolve this issue.
I have no control over this and I'm not about to instruct you how to circumvent it.
I could not get past the lockscreen. Tried to enter the SIM pin, phone went dark and booted from the miui screen again. After the fourth try I forced a shut down and installed the latest beta again. So I'll wait for the next stable...I know yet.
The NFC icon doesn't appear in the notification bar. At you?
Hi! So far my only "bug" is gmail app is not showing notifications to new e-mails.Small possible bug, but the At a Glance widget no longer opens the calendar app on the Redmi nNkte 10 Pro in the recently released build.
Happens sometimes. Close it and retry.Device: Mi 10 pro
When installing the apk, the package installer view is ridiculous as in the picture.
I asked that and the answer from orjon the polish translator was: with the same or newer Security patch you can do thatI got bootlooped. After a clean flash everything is ok.
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation