Search results

As far as I know, twrp is unable to decrypt data partition on most devices with android 14 and 15. The only use of twrp is as a bridge for adb sideload feature.

That's it, thank you so much.

I can not relate to your problem guys. I just tried it with my topaz device and everything works perfectly. I had to perform a clean install though, as i had another ROM installed before. A clean flash will probably solve the problem. @yago78 have a close look at your device manager when in...

I remember a chinese website that would upload detailed changelogs for every update xiaomi would release. Not just bullsht like "Improved system performance" but what exactly was actually changed. I cant remember the name or URL of the site though, and google also doesnt help because it's...

Is there a way to enable circle search in Button navigation mode on shennong? I read that it's possible to map it to "long press home button" but it's not in the corresponding menu and I can't find any other settings related to it.

After all this time, you've probably found a solution yourself... In case you didn't: For Hyperceiler, the HyperOS 2.0 update was just published today (on GitHub), and there's an official Pengeek beta build that works on HyperOS 2.0 in the telegram group. Works well for me.

Hello DEVs. First of all, I'm not asking for ETA. But since the HyperOS 2.0 beta ROMs are now live, are you considering to make xiaomi.eu versions of these beta builds aswell?

Y'all are overreacting a bit I think. Install magisk (v27.0 or v28.1), enable zygisk, add WA to deny list and install play integrity fix magisk module. This setup has worked for me ever since I got my 14 pro. From HyperOS 1.0 weekly dev builds until now with HyperOS 2.0 stable 2.0.7.

I just tested it aswell, it doesn't work even on a rooted device with heavy root cloak and play integrity fix (everything else works - gpay, banking apps etc). Seems like revolut seriously requires Play integrity STRONG_INTEGRITY tag. As far as I know, there is no way to spoof it - not even for...

Not sure what your question is. Xiaomi.eu usually releases the modified ROM a few days after official is released. Since they released HyperOS 1.0 for topaz, I think we can expect HyperOS 2.0 for it aswell (only if there's an official one of course). If you're looking for tapas ROM, look here...

Magisk yes. Without any problems. Just in case you use LSPosed, no. If you have original LSPosed active on android 15, it will corrupt and disable the whole zygisk functionality. There are forks tho (im using jingmatrix for now), that fix this problem.

Anyone installed 2.0.7.0 on shennong yet? Any problems?

Apparently not. You have to install driver for adb and fastboot separately. Once the device is in fastboot mode, open device manager and go through the whole driver installation process, choosing "Android bootloader interface".

I'm not actually sure but I can imagine that. Hyperos 2.0 brought a pretty useless but big rework to system appearance. So probably themes built for hyperos 1.0 won't apply to the system part of hyperos 2.0.

If you are willing to pay 70$ and wait a few weeks or months, yes. (ncunlock.com) If you own an account with lvl 5 on Chinese mi community and you have wide knowledge about android/Linux backend, also yes. Otherwise, no.

To be honest, I dont know much about the backend and the overall functionality of Play Integrity. But from what I see, Google isnt actively blocking anything, right? All google does is provide a verification API that apps CAN access IF they feel they need/want to. If google would shut down Play...

I'm not 100% sure, but I wouldn't take any risk and flash the ROM listed for your device here first, as that was the ROM intended for switching from weekly to stable.

In any way of installing xposed framework, you will at least need an unlocked bootloader. For debloating, you can use an adb connection in order to uninstall most pre installed apps, including 80% of what we would call spyware. For blocking ads, I like to use AdAway project. It works with both...

I do know that MiFlash has a log function, never had any problems while flashing with MiFlash though... Do you have an example for what kind of problems could occur and what the log would state in that case?

That's how this works. You can use this script to bind the phone to your account, and a few days later you can unlock the bootloader through miflash_unlock program and phone in fastboot.