I just found out, that my GF's Phone (Redmi Note 10 Pro) is still on MIUI 13.0.16 and Android 12 with Security updates 2022-11-01 therefore.
The device is eol, but all sources I could find tell me that the last available version should be Android 13 with MIUI 14.0 or HyperOS 1.0 https://hyperosupdates.com/hyperos/sweet
The Device was set to automatically download and install system updates but apparently it didn't update for 1.5 years. And manually hitting the "search for updates" button only returns the info that no updates are available.
Has anyone of you some idea what could be the issue here?
If you want the latest version of Android with recent security patch, try lineage os or crdroid. But you have to unlock the bootloader and spend little time tinkering on it. You can find a lot of YouTube videos with step by step instructions. I have a device that runs on crdroid with Android 14.
Thanks for your input. Installing lineage os is something I have thought about. And I'll probably do that since it's eol for Xiaomi.
The model codename is sweet like you deduced (the EEA version btw). I have found those unmodified Roms as well, which is the reason why I am so confused here.
On another note:
What made you choose crdroid over stock lineageOS?
What made you choose crdroid over stock lineageOS?
When the google photos became a paid service crdroid was giving an option to do unlimited upload of photos by spoofing the device as pixel. It started like that and it gives more customization compared to lineageOS, so I stuck to it. I used both lineage and crdroid, there is no notable performance difference.
BTW, I'm not longer using Google photos for backup, I setup a homesever and use immich as my backup solution.
One thing to note, it will become very difficult to unlock the bootloader once the device is updated to HyperOS. There is no way to unlock it if you have purchased the china version.
small status update:
i tried the update packages (from both cfirmwareupdater and mi community) and it errored out with the message that the update could not be verified. so i probably need to go the fastboot route anyways so i probably just use an up to date custom rom directly