HyperOS 2.0 HyperOS 2.0 STABLE RELEASE


Hi there, I wanted to report this typo in settings. It reads "Personalisation" instead of "Personalization"

I attached screenshots below.
 

Attachments

  • Screenshot_2025-07-28-07-11-16-745_com.android.settings.jpg
    Screenshot_2025-07-28-07-11-16-745_com.android.settings.jpg
    276.2 KB · Views: 131
  • Screenshot_2025-07-28-07-11-53-410_com.android.thememanager.jpg
    Screenshot_2025-07-28-07-11-53-410_com.android.thememanager.jpg
    788.2 KB · Views: 132
Outside of America it's spelled "Personalisation" the "z" is an American English thing. Might be an option to set American English as system language, but that's how it's spelled.
Yes, yes, I'm aware of that, that's why I'm reporting, my device language is English (United States), as you can see, it's spelled "Personalisation" in the list, but once you enter the menu, the header reads "Personalization", I mean, there should not be two different strings for the same word in EN_US.
 
Last edited:
Yes, yes, I'm aware of that, that's why I'm reporting, my device language is English (United States), as you can see, it's spelled "Personalisation" in the list, but once you enter the menu, the header reads "Personalization", I mean, there should not be two different strings for the same word in EN_US.
English translation is provided by Xiaomi.
 
Small heads up for houji users going through TWRP for updates.
It might just be me, but this time the option "flash current TWRP" didn't work.

Maybe a hick up on my side, but would advice to flash the actual image to be sure.
 
Small heads up for houji users going through TWRP for updates.
It might just be me, but this time the option "flash current TWRP" didn't work.

Maybe a hick up on my side, but would advice to flash the actual image to be sure.
go on install, switch to image and then flash the img to the recovery partition
 
go on install, switch to image and then flash the img to the recovery partition
I know, but I didnt have the image on my device as I always use the native TWRP option.

So if I would have been traveling (without a laptop) I wouldn't be able to get root after rebooting.

So that why I'm just giving a heads up to prevent others getting into such issues.

I had a computer nearby so was up and running again in a few moments.
 
I know, but I didnt have the image on my device as I always use the native TWRP option.

So if I would have been traveling (without a laptop) I wouldn't be able to get root after rebooting.

So that why I'm just giving a heads up to prevent others getting into such issues.

I had a computer nearby so was up and running again in a few moments.
yep sadly had the same issue....
i hope they will be able to put that recovery into the rom as standard
 
yep sadly had the same issue....
i hope they will be able to put that recovery into the rom as standard
Dont think they will ever.
For some reason also internet thinks TWRP is not good anymore.

In my opinion better would be to have no recovery in the "update" file.
Let people keep what they have.

But they have their reasons I guess.
And I'm not going to complain, as I'm happy with all other.
 
I installed the ROM successfully on the 14 Ultra. It seems working fine, but one issue appeared. I can't receive 2-step verification SMS from Google. I receive SMSs from friends and messaging seems to be working fine. Does anyone else have such experience? Also, I'm not sure if installing modem firmware from the latest global version may solve the issue, as I receive SMSs and maybe the issue is somehow related to Google...
Just to confirm that 2-step verification by SMS doesn't work on the latest Aurora 2.0.2090. SMS messages from Google aren't being received. I receive SMS messages from friends and messaging seems to be working fine. 2FA was working before installing Xiaomi.eu, and it works on my other phone with the same SIM card. Sorry to say, but this prevents me from using this ROM because I need 2FA for work.
I'm wondering if it will work if I install HyperOS 1.0....
 
In my opinion better would be to have no recovery in the "update" file.
Let people keep what they have.

But they have their reasons I guess.
And I'm not going to complain, as I'm happy with all other.
If I remember well, the update without recovery was broken for people not using HyperOS 2 previously.

Found it :
 
Last edited:
If I remember well, the update without recovery was broken for people not using HyperOS 2 previously.

Found it :
That makes sense, although it would than be an option to stop this from now on and make a clear message for people coming from A14 to first flash an earlier A15 version.

I assume there are now more people updating who use TWRP than there are people still coming from A14.

Anyway, again, for me no problem, just that I recommended before to use "flash current TWRP" and this time (maybe just once) if wasn't working.
 

Tenker

 

Tenker

Hello,

Is there no image available for Xiaomi 14T Pro, or have I overlooked something?

Thank you

seems that Dimensity processor is not supported directly =(
so no support for 14t for this thread, only paywalled by community at second link
 
  • Like
Reactions: Tenker
That makes sense, although it would than be an option to stop this from now on and make a clear message for people coming from A14 to first flash an earlier A15 version.

I assume there are now more people updating who use TWRP than there are people still coming from A14.

Anyway, again, for me no problem, just that I recommended before to use "flash current TWRP" and this time (maybe just once) if wasn't working.
No, having a fully bootable ROM "out of the box" is a must, having TWRP is a user choice.
Forcing people to flash something else before flashing our ROM just because some users use TWRP is not acceptable.
 
  • Like
Reactions: NXTwoThou
No, having a fully bootable ROM "out of the box" is a must, having TWRP is a user choice.
Forcing people to flash something else before flashing our ROM just because some users use TWRP is not acceptable.
Flashing "something else" would still be your ROM.
But I see what you mean and don't disagree actually.

Maybe in an ideal world, let the updater app download a version without recovery inside.
But I see the extra work that would mean for you guys.
 
Flashing "something else" would still be your ROM.
But I see what you mean and don't disagree actually.

Maybe in an ideal world, let the updater app download a version without recovery inside.
But I see the extra work that would mean for you guys.
"A version without recovery inside" means uploading 2 separate ZIPs. SourceForge will not be happy about that.
 
  • Like
Reactions: Bamn09
Hello. First of all, thank you to the developer team for these ROMs. Yesterday, I installed the latest Xiaomi EU ROM on my Xiaomi 14 (houji) device, and after installing it, I rooted it with KernelSU. Rooting was very simple — I just patched the init_boot.img file using the app and flashed it, that's all. After that, I installed the modules Trickystore, TrickyAddon, Play Integrity Fork, and Zygisk Next. In Trickystore, I selected “Select All” and tapped “Set Keybox,” and now I have full integrity. It was actually simpler than I expected.
 

Attachments

  • Screenshot_2025-08-01-01-42-14-506_gr.nikolasspyr.integritycheck.jpg
    Screenshot_2025-08-01-01-42-14-506_gr.nikolasspyr.integritycheck.jpg
    145.6 KB · Views: 9
Hello,
I'm delighted with the Xiaomi.eu project. I've been supporting it since 2019 and will continue to do so for as long as necessary, but I believe we, as users, need information...
I'd simply like to know if a solution is being sought for the payment module or, on the contrary, if Google has won.
I'm in no rush for it to be resolved, but I would like you to be honest with users.

I repeat, I'm delighted with the project and am not interested in switching to any other ROM.

Thank you for your work.
 
  • Like
Reactions: eleutherios0
I don't understand what other information you expect. In my opinion, the developer's statement is more than sufficient.
 
Hello,
I'm delighted with the Xiaomi.eu project. I've been supporting it since 2019 and will continue to do so for as long as necessary, but I believe we, as users, need information...
I'd simply like to know if a solution is being sought for the payment module or, on the contrary, if Google has won.
I'm in no rush for it to be resolved, but I would like you to be honest with users.

I repeat, I'm delighted with the project and am not interested in switching to any other ROM.

Thank you for your work.
Google has own, that's the bottom line. There are solutions but these are not cut and dry. You need to research and nothing is guaranteed. Keyboxes are banned left and right by big G so even Strong integrity is short lived and needs constant attention

Sent from my 2210132G using Tapatalk
 

Similar threads

  • Locked
HyperOS 1.0 24.7.1
Replies
54
Views
55K
Replies
51
Views
71K
  • Locked
HyperOS 1.0 24.7.15/17
Replies
87
Views
111K
  • Locked
HyperOS 1.0 24.7.8/12
Replies
50
Views
44K