Search results

Are you site you have set the correct KB? Have you checked that? Have you tested do you pass <A13 Device Integrity - exactly as asked here Once everything set correctly, Wallet can take 72 hours to clean the cache and start working --- Details can be found on XDA

Now you have new KB on KeyHub (requires login via TG account) or that same valid KB can be more simply installed from TrickyStore AddOn WebUI, Open, Install valid KB

There are many different guides bcs there are many similar modules where devs forked one module and made some cosmetic change. Then somebody reports as new method CURRENTLY THERE IS NO LEAKED BUT VALID KEYBOX, hence no matter which 'different' guide or method you use, it will eventually fail...

I dunno what you mean by fetch and what Yuri does not have a valid KB at the moment - there is no valid KB currently leaked Latest valid leaked KB was revoked (Google will revoked any leaked KB, sooner or later) Until somebody posts somewhere for free another valid KB (it will spread around...

Instead you could have simply remove the revoked KB. Strong 3/3 One way or another, Wallet will break sooner or later without the valid KB

Banking apps are a vague term. Without any further comments, a banking app from a bank A may look for and require completely different security than a banking app from the bank B Specially, banking and similar apps from particular countries might be very demanding (Btw also, the latest leaked...

Once you make it working you (root, modules, etc), you just need to regularly update prints (Action button in PI Fork) and to update to the newer valid KeyBox (best and usually the first to release) is to look for the Strong KB on KeyHub site Some newer/forked modules provide Open/WeUI menu...

You mean modules? You must have Magisk/APatch, or KSU.and root. Open Modules tab and find the icon)option to install a module from the downloaded zip file. Search on YouTube how to install a module in Magisk, APatch, KSU or whatever you have and see there

Be aware that that 'valid' KeyBox is already shadow-revoked (and soon can be publicly revoked)

Sorry but where have you been for a month or so, you didn't read this Forum or what. inject module and all about is a past now

I have/had also an older Redmi 20K with the same date of last release. I was not able to make it pass Play Integrity. Since that was my old phone (not even the last but one) I moved back to stock and locked bootloader but couldn't make it to pass there either, since the ROM security patch is too...

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...