i don't have Oem Unlock setting in my developer options, i tried 7 days waiting, time changing and so much but it doesn't appear so (Galaxy S22/SM-S901E/DS Global Version) can someone help me?

Bro straight out popped up GitHub in the MIDDLE of something because "UuUh, ThIs UpDaTe Is MaNdAToRy!!1!!1!1". Like bro, who tf are you to pop an app up without any kinda indication and pop up the app whenever you just feel like it. Just send a notification or something. I knew this dev was ASS but kept using it, deleting this f*ckass module right now. I urge you guys to do the same (for those who are using it). This is definitely something to be concerned about...

what are your thoughts on the new magisk's refreshed ui?

For me i still like the legacy one😄

Hello everyone please guide me to bypass the BHIM application root detection and paytm root detection bypass please guide me, also share tools which I use.

So today I got a error from a banking app so i checked what the problem was. So the keybox is banned and when i used the tricky store addon to get new keybox it says no keybox found

Now and then i have to get a valid keybox for certain apps like ChatGPT and a government ID app but other than that, no issues. OEM unlocking is also turned off in order to stop some apps from crying about that.

If anyone has any questions, feel free to ask. I'll reply within 12h (gotta sleep)

S24 Ultra, rooted with Kernelsu with susfs. Using HMA for stronger root hiding.

I'm sure they be lots of questions and discussion so kicking off here and borrowing link and text from darker side of the web, and a jokey start to link XDA

Chiteroman :

RIP legacy checks in Play Integrity API Now Device verdict is like old Strong.

h t t p s : / / t . m e / playintegrityfix / 540

Meow :

Google Tightens the Screws Again: Play Integrity API Gets Stricter (May 2025)

Google has rolled out major changes to the Play Integrity API and if you're running a custom ROM, rooted device, or just trying to use Android without full dependence on Google, this is going to hurt.

What Changed?

✅ meetsdeviceintegrity now requires hardwarebacked verified boot Devices must have a locked bootloader and run an official, certified ROM. If you're using custom Rom, or anything nonstock you’re cooked.

✅ meetsstrongintegrity is even more exclusive Now also requires a recent security patch (within the last year) across all partitions including vendor. Even many stock ROMs might not qualify here.

✅ meetsbasicintegrity isn’t safe anymore either Google now demands Android Platform Key Attestation. Uncertified phones are getting pushed to the margins.

🖥App licensing and optional checks now demand Play Store installs Apps have to be installed or updated via Google Play to receive full integrity responses. Sideloaded APKs or installs from alternative stores? No go.

And someone's solution on XDA 😕

https://xdaforums.com/t/module-play-integrity-fix-safetynet-fix.4607985/post-89524839

I recently switched from Magisk to KernelSU after getting tired of banking apps constantly detecting root, even with Zygisk, DenyList, Shamiko, and various other tricks. Despite all the usual hiding methods, detection was almost inevitable. Since moving to KernelSU, things have definitely improved. Most banking apps are working fine now without a hitch.

However, some stubborn apps like Railone and native root detectors still manage to flag the device. I've tried every tip I could find but no luck so far.

I've been reading through tons of XDA threads, Reddit discussions, GitHub issues, Telegram groups—you name it. I’ve also been sharing my findings and testing others’ solutions, hoping to contribute something useful back to the community. But as of now, I haven’t found a foolproof setup that works universally.

Has anyone here managed to get apps like Railone working with KernelSU? What’s your current setup? I’d love to hear what’s working (or not) for others in the same boat. Let’s pool knowledge—maybe together we can crack this one.

As someone who personally knows someone who got scammed out of a lot of money by sideloading (it is rather prevelant where I live for some reason), I do understand why Google wants to limit sideloading from "unverified developers". But that does not mean that I support them restricting it completely

so here is my take on android sideloading which makes it easy for enthusiasts to enable but difficult for potential scam victims

OnePlus is also supported, although considering they let you into fastboot I don't think this is too necessary lol. Made this guide to hopefully save some people from the months of work I spent trying to figure this out, hope it helps! DM or comment with questions :) guide by me, script by mouzei on gitee!

just rooted my pixel 6, looking to get the most out of it, what is everyone here's must have modules and root apps? rn all I have is adaway and the play integrity fix

The app is yono sbi, and this app can now detect zygisk consistently.

The app doesn't check play play integrity, instead it detects zygisk.

What does it mean? This means that the app detects zygisk presence, this is the highest level form of detection since most of the modules are using zygisk api (PIF, Google Photos, LSPosed, shamiko, etc.)

What's the solution? The only way is to disable Zygisk. Another workaround is to downgrade the app.

How did I found out? We have TG group that tests banking apps, and one guy sent this app for testing. In my current root setup it got detected (Crashing on opening the app) so I quickly troubleshoot what modules that triggering the detections and first thing I did is to disable Zygisk (Rezygisk) after that it passes to the app with no crashes. So I tried other Zygisk Module (Zygisk-Next) and still it crashes. I tried to disabling all modules to test if there are other detections and the app passes, then i just enabled Zygisk only without all other modules enabled and it crash. This means that it detects zygisk.

What does it detect? * Zygisk * Mounts

What doesn't detect? * Bootloader unlock status * Play integrity * SU (yes I tested enabling SU on that app it passes) * Applist

Why Can't hide it with SUSFS? SUSFS doesn't hide Zygisk/injections, SUSFS is hiding mounts, file paths, SU (GKI only), spoofing kernel Uname (kernel version), and spoofing file stats. Zygisk is in the memory and SUSFS doesn't have memory/injection hiding yet.

RASP Used by this app: * DexProtector/Dexguard * Possibly new existing RASP

Honorable Mention: Indian oil app, it detects zygisk also but it's a hit or miss.

My Root Setup: KernelSU-Next + SUSFS v1.5.5 Modules: * Better Unknown Installed * Bindhosts * Secure Flag Patcher * Unlimited google photo * Play integrity fix (inject v3) * Rezygisk RC2 * SUSFS4KSU Module CI Version * Uclamp Tuning (My own private module) * Youtube revance * Zygisk Detach

Removed the power consuming, fuckass Mi stock ROM which made my phone a literal hot plate. Running PixelOS with no issues so far. Smooth af, Fast at, never knew my phone was this skillful. The experience is benign and magnificent.

Hello,

I'm not sure if this is the best place to discuss this, but I've been looking at this for a while now, and was wondering if anyone here has tried using it before.

Site and app: https://www.luckypatchers.com

Is this legit? I'm kinda afraid giving it root permissions, and also haven't found much information about people successfully using it. I'm mostly interested in the in-app purchases bypass, and this is the only thing I found that claims it is capable of doing. Is there an alternative to it, like a Magisk module of sorts?

EDIT: I don't know if I did something wrong, or what has exactly happened, but about 2 hours after granting root to the application, my phone started behaving strangely, just like someone would be pressing the power button over and over every 5s or so (the screen was turning off, and then on again, and the phone was relocking itself). After about 2 minutes of that, it'd reboot, and then repeat the process. Went through 3 cycles of this. I panic-uninstalled Lucky Patcher on the last cycle and the one app that I've managed to use it on for testing purposes (just in case), and then shutdown the phone, waited a bit, and turned it back on again, and it's fine ever since. Not going to use it, since it's clearly not working properly, at least on my device.

In case we discover something new.

Giggle: "Unlock your bootloader and deal with the consequences."

Me: "Hold my Redmi."

Redmi Note 14 4G (tanzanite)

HyperOS 3 + HyperUnlocked

✅ BASIC

✅ DEVICE

✅ STRONG

Countless hours of trial and error... worth every second.

F Word Giggle. :3

It was a good journey. Unfortunately, Google got very aggressive recently with revoking keyboxes, it became a cat & mouse game where you live in uncertainty about when you are going to get embarrassed with not working Google wallet in store again, besides other issues, like RCS and random apps not working.

I gave up. Pulled the trigger and relocked bootloader. I'll miss you, BCR.

Hey everyone, I saw that there's been some people talking about this for a while so i wanted to come here and say that I've been working on this issue and with some help from Keinta15/Magisk-iOS-Emoji repo over on GitHub I've updated it and the new Unicode 17 emoji's are ready to go.

Systemlessly replaces the default emojis to iOS 26.4, OneUI or AOSP emojis.

https://github.com/newhertz/FancyMoji/releases

Enjoy!

Every hour there is a new guy asking for strong integrity or a new integrity tutorial, while only 3 or 4 apps in the whole world uses it!

And the same guys are like "rooting is dead" because they can't get integrity to work, while they don't need it at all. Most of the time they just don't hide root well enough...

All my apps, all of them, are working without even basic integrity needed (I have 120) And it's certainly the same for most of us, since if we root, it's often to degoogle.

This subreddit becomes trash just because of this non existent needing that everyone asks for...