Recent content by zgfg12

It all depends how old is the last Xiaomi.eu release. If older than 2024 Aug or Sep (not sure exactly which date) then no chance. At some point at that time previous year summer, Xiaomi.eu made a significant change- before, Inject module was not possible to disable, after that they made it...

If you want to go back to stock, that's of course not a single step. You must download the official firmware, flash (it will include a Factory reset - without, don't expect the switch would work smoothly). Besides, re-locking Bootloader by Bootloader itself forces a Factory reset - if you try to...

The keybox you use was shadow revoked (for now, until it gets properly revoked, any time soon). That's not a bug but on purpose by Google and has nothing to do with your Play Integrity app checker

Seems you don't just use the root but more likely spoof the prints to pass Play Integrity. if so, ask on the forums or TG channels where you followed the guides Eg, if you use Play Integrity Fork, you must not permanently keep spoofVendingSdk enabled (for <A13 verdicts) since that will affect...

App is given its package name by developer, not by you when you 'create' a dual app. Xiaomi provides the mechanism to run the same app (with the same package name) with the two different user settings - like two WhatsApps, using two different phone numbers It has nothing to do with app cloning...

It may result in boot-loop if the old boot.img is not compatible with the upgraded ROM So, as I described above (for APatch, but same for Magisk): Before upgrading: - unzip to copy out the boot.img - patch that new boot.img Then either: - replace the original boot.img with the patched one...

First of all distinguish the SafetyNet from Play Integrity SafetyNet cannot be 'fixed' since the SafetyNet servers have been finally (after ovrr two years upon the first announcements) once and forever shut down by the end of February (half a year ago !!!) on the Google side. Try to do...

You mean Magisk (not Magisks)? 99,9% of all computer errors are sitting on the keyboard"

By flashing various ROMs from not trusted sources/developers and/or by playing with fastboot (not knowing what partitions are for what) you might had wiiped or overwrote your EFS and similar partitions Since they contain phone persistent info (like IMEI), flashing this or that ROM will not...

Try to boot to Fastboot (like keep pressing Power button together with Vol- and flash again but full install with Factory reset

And BTW, a tip regarding to updating Xiaomi.eu I do with APatch, but similarly should work with Magisk (yeah, long ago when using Magisk I did similarly) Download Xiaomi.eu, unzip, find boot.img (nowadays it's in the Images folder), copy the boot.img out and upload to the phone. Or, I download...

That's not true. At least in APatch YOU CAN hide modifications FROM the apps (Deny list in Magisk does not hide certain apps but hides 'root' from the apps: to hide some apps [from the other apps] use HMA module like in Magisk) And you can do the same in APatch, just it's called Exclude...

They will never include because it requires usage of leaked private keys from the real phone vendors. Dealing with that is at least, forging someone else's digital property (and authority) Besides, whenever Google finds one of those keyboxes being used massively for spoofing Play Integrity...

Than you cannot setup and pass, as simple as that

cannot properly edit missed quotations, hence deleted (don't have time to write the same post from the beginning)