I just did the update on my note9 pro 5g. Went pretty smoothly - followed katerpane's instructions. Had no issues with decryption and rom installation.Followed the procedure , using V13.0.6.0.SJSCNXM_v13-12-fastboot , and flashing via fastboot, then adb twrp, decryption works, using updater, flashing V13.0.10.0.SJSCNXM_v13-12, decryption is lost no error just:
Running recovery script...
Done.
Full SELinux support is present.
MTP Enabled
Formatting data doesn't help, everything still garbled.
Do you actually see the decryption notice in TWRP?I just did the update on my note9 pro 5g. Went pretty smoothly - followed katerpane's instructions. Had no issues with decryption and rom installation.
Not sure what you mean. Twrp asked for password, inserted the password and it was accepted. Then installed the rom.Do you actually see the decryption notice in TWRP?
It seemed to upgrade ok, just leaving the encryption undecrypted...
what is your challenge?what i did try so far is installing stock and EU rom (12.5 and above)., all via fastboot, the flashing TWRP, all decrypted fine, the moment i flash to the lrecovery EU 13.0.10.0, decryption is lost without any error
I was wondering, as last resort, since it does seem to be ok for flashing the recovery rom, does it matter if user data is encrypted, since it is the system that is being written to?
Provide a better description of your problem.Sorry i do not understand?
I doubt you are using this custom ROM here: In this ROM Mi Message is the default message app, not Google Messages. So your issue has nothing to do with this ROM. You should adress it to official Xiaomi global forum.Hi,
does anybody have still problem with receiving of text messages? I only recieve some of my incoming text messages (approximately 90 %). I have Mi 11 Ultra (CN) with EU last stable ROM (MIUI V13.0.13.0). I have this problem since I bought the phone (with CN ROM version also):
What I have already done:
- updated the ROM
- disabled the default Google Messages (I couldn't remove it with ADB because the app wasn't visible in the app list, so I just disabled it)
- cleared data + cache on both message applications (Textra, default Google Messages)
- updated the APN settings according to the network provider settings
…
Can anybody help me?
Use a recovery that can decrpyt an A12 ROM. Check this thread: https://xiaomi.eu/community/threads/mi-10t-lite.66954/With mi10Tlite, upon moving from 13.06 fastboot to 13.0.10 recovery, TWRP does not decrypt, there is no error message, just:
Running recovery script...
Done.
Full SELinux support is present.
MTP Enabled
flash does seem to work ok, reflashing the 13.0.10 recovery rom from SD card, so does Magisk, but on internal storge it is encrypted..
Used stock fastboot V12.5.7 as base and upgraded to 13.04 EU , then to 13.0.10, decryption works up to recovery flashing of 13.10, then after flashing via updater, rebooting and going back to recovery, fails to decrypt.
The recovery is fine up to AFTER the flashing of the recovery 13.10 rom.Use a recovery that can decrpyt an A12 ROM. Check this thread: https://xiaomi.eu/community/threads/mi-10t-lite.66954/
I know/think, that ROM has nothing with this issue, because the same issue was also on other (first) CN ROM. My mistake, unfortunatelly application called in my language only "messages", yes, there are Mi Messages application, not Google.I doubt you are using this custom ROM here: In this ROM Mi Message is the default message app, not Google Messages. So your issue has nothing to do with this ROM. You should adress it to official Xiaomi global forum.
I have the same phone and the same version of the rom and no problems with apps. Maybe try a factory reset (which is a pain to reinstall your apps) but then you know for sure that you have a clean installation.Hi guys, I installed the update V13.0.13.0SKACNXM for my Xiaomi Mi11 Ultra and every day different apps stops working, when I reinstall the app works and after one day its stop working. Someone else having this issue?View attachment 44193
You should better always declare your device since updates for Stable do not come to all devices in parallel. Hence the problem you have would not be on other devices and it's unclear who (with the same device) can check and answer to you
We use essential cookies to make this site work, and optional cookies to enhance your experience. Cookies are also used for ads personalisation