Search results

I guess the term for that these days is "brain rot".

That's your opinion. Custom ROMs existed long before SafetyNet/Play Integrity/NFC payments became a thing, and no one complained.

Google has strengthened Play Integrity* protection and our workaround is no longer effective. You can just accept it and use another payment method (like Curve Pay), try using complex root hacks (example) at your own responsibility, or return to an official ROM with the bootloader locked...

No idea, I don't have that device. Official ROMs don't have "Turn off screen" for double-tapping the fingerprint sensor, it was always our mod.

It's a scrollable list... scroll up for the rest of options.

We plan to support it soon.

If you're not already using our ROM, this thread is not for you. The thread is for feedback about the existing releases. We have a Q&A section for general questions.

Support for MIUI 14 ended long ago. Moved to Mi General.

As far as I remember, it's unlocked.

There is nothing we can do about how Circle to Search works. It's a Google function. If it doesn't always trigger specifically when long-pressing the gesture bar, then Xiaomi needs to fix their launcher.

https://xiaomi.eu/community/threads/frequently-asked-questions.73215/

Because we don't get to decide how Circle to Search works.

Not advised without a data format. Won't boot if security patch version is different. Also, apps are not designed for downgrades, so some system apps may crash. None of this has anything to do with ARB though (which hard-bricks on downgrades).

"Downgrade" from 2.0.10 to 2.0.7? I'm not sure what version 2.0.10 is, latest version we have is 2.0.9. ARB? It was only used for 4 devices many years ago, Mi Max 3 was one of them.

The feature appears and officially supported only on newer devices.

There is no one bored enough to sit and document every single change made to every single ROM for every single device.

We don't have a Xiaomi.eu ROM for Redmi Note 13 5G (gold/iron), it's a MediaTek Dimensity device.

Depending on the device, init_boot.img needs to be patched if it exists (newer devices), otherwise boot.img (old devices). "--disable-verity --disable-verification" is not allowed in many newer devices and will prevent you from booting at all. Don't know where you got the idea to try to patch...

https://xiaomi.eu/community/threads/frequently-asked-questions.73215/

I don't see how a broken TWRP is any of our problem, we're not about to change our whole packaging due to that.