Yes, it's not a new one and is already being discussed here. I've worked for several days, did some troubleshoots with other CN HyperOS-based ROMs and found out it might be related with some traces left from Xiaomi.eu ROM's Play Integrity fix.
I'm currently using weekly Xiaomi.eu ROM on a Xiaomi 13 Ultra.
The issue started with the abnormal crash from the Octopus pay app in HK (P1), and the restriction from Uber (disabling the app's native UI and redirecting to a webview page). Those scenario can be observe under a clean environment and a rooted environment (KernelSU 11838, Zygisk Next 1.0.5, Shamiko 1.0.1, LSPosed 7024, HideMyApps with suspicious stuff properly hidden, including Xiaomi.eu's fix).
Then I tried those two apps on a locked Redmi K70, which had only passed Basic Integrity due to Xiaomi's problem. Octopus didn't crash and refused the login attempt as expected, and Uber also works fine with full function.
I brought out my Redmi K20 Pro at last, with a modified CN-based HyperOS ROM (modified from Xiaomi 13's ROM) and a rooted environment (same opponent with Play Integrity Fix installed, can pass Device Integrity), and those two apps would work smooth as they expected.
So I tried to locate the issue from the newly-flashed Xiaomi.eu ROM. Using NativeDetector and Memory Detector (original dev turned the repo private, but apk can still be reached here), modification on constant properties can be found (P3, Property Modified (20), the other output means the bootloader is unlocked) which other ROMs doesn't have, and Memory Detector found out it is related to native bridge (P2).
So far I think the problem can be located on Xiaomi.eu's Play Integrity fix method, but as an amateur this is the furthest I can go. I'd really appreciate it if you guys can figure out the rest.
I'm currently using weekly Xiaomi.eu ROM on a Xiaomi 13 Ultra.
The issue started with the abnormal crash from the Octopus pay app in HK (P1), and the restriction from Uber (disabling the app's native UI and redirecting to a webview page). Those scenario can be observe under a clean environment and a rooted environment (KernelSU 11838, Zygisk Next 1.0.5, Shamiko 1.0.1, LSPosed 7024, HideMyApps with suspicious stuff properly hidden, including Xiaomi.eu's fix).
Then I tried those two apps on a locked Redmi K70, which had only passed Basic Integrity due to Xiaomi's problem. Octopus didn't crash and refused the login attempt as expected, and Uber also works fine with full function.
I brought out my Redmi K20 Pro at last, with a modified CN-based HyperOS ROM (modified from Xiaomi 13's ROM) and a rooted environment (same opponent with Play Integrity Fix installed, can pass Device Integrity), and those two apps would work smooth as they expected.
So I tried to locate the issue from the newly-flashed Xiaomi.eu ROM. Using NativeDetector and Memory Detector (original dev turned the repo private, but apk can still be reached here), modification on constant properties can be found (P3, Property Modified (20), the other output means the bootloader is unlocked) which other ROMs doesn't have, and Memory Detector found out it is related to native bridge (P2).
So far I think the problem can be located on Xiaomi.eu's Play Integrity fix method, but as an amateur this is the furthest I can go. I'd really appreciate it if you guys can figure out the rest.
