Search results

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.

If you have a question, just ask here.

MiFlash is futile as long as your phone isn't bricked. To update the ROM, you can just run the "windows_fastboot_update_rom.bat" file from the xiaomi.eu package while your phone is in fastboot (or the corresponding other file format if you're not on windows). No need for a custom recovery. If...

I think you should be able to bypass the restrictions through this.

There is a dedicated feature named "Call recording" in system phone app. It should work better.

I think you've got something substantially wrong here. You're currently trying to boot the patched boot.img. that doesn't work which is why the phone just boots normally. What you want to do is flash the patched boot.img to the boot slot. To do so, use the command "fastboot flash boot...

A new version of the fix module was released a few hours ago. Have you already tried that?

Where did you flash the modem.img to? What exact command did you use? The fact that you can't access bootloader and baseband version seems like you partially ****ed up your bootloader. What exactly happens when you try to enter fastboot from that screen?