Search results

Same question here.

Play Integrity broke a few days ago due to a change on Google's side. Magisk Modules which fix this was incompatible. This update fixes Play Integrity again.

I have some questions about the safety of dirty flashing. I used to do this a lot with AOSP ROMs, but this is pretty much the first time I'm using MIUI. I wanted to ask if it was safe to dirty flash from an Offical ROM to Xiaomi.eu, or should I clean flash and try another way to keep the...

New rollout on Google's end. No fix in sight, third party fix magisk module incompatible with xiaomi.eu for now.

Someone made a magisk module https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/page-72 but it is incompatible with Xiaomi.eu due to a conflict with system-level spoofing. Wait for devs I guess?

Same thing here with Marble on latest. Failed CTS on HARDWARE_BACKED SafetyNet and DEVICE_INTERGRITY on Play Intergrity.

the new rules from the rumour you sent. The rule that OEMs must prevent risks of bad ware before delivery to customer. This means preventing BL unlocking by resellers, but Xiaomi could misunderstood that.

Either 1:Xiaomi misunderstood the new regulations, 2:Xiaomi wants to force engagement on the Xiaomi Community App, or 3: To block warranty fraud since Xiaomi warranties devices with custom ROMs or ROOT.

The requirement says manufacturers must try to prevent the device being sideloaded with malware before first sale to consumer(so basically no unlocking bootloader until the OEM knows it’s in the hands of the final customer, not a reseller). Xiaomi’s 168h rule already exists to prevent this. But...

No, but it is increasingly difficult(or, based on recent announcements, impossible for international users)

If this ends up being the final decision I'm done with Xiaomi/Redmi/POCO. Will probably move to OnePlus or Pixel or Nothing Next.