Closed test-pad closed 1 month ago
There are old issues talking about this: https://github.com/scottyab/rootbeer/issues/179
Looks like no one maintains the project any more
Hey @grubeli sorry it feels that way. Merged your PR thanks for the contribution.
@scottyab when you guys are gonna release this version?
@scottyab
Reading over the internet I have found that ro.build.selinux
is unreliable, it may be 0 and still SELinux is enforced or it may also be missing completely.
It is more reliable to execute /system/bin/getenforce
that return Enforcing
, or read /sys/fs/selinux/enforce
that return 1
.
See also here: https://erev0s.com/blog/3-ways-detect-selinux-status-android-natively/
@ale5000-git
Could you please fix the code in pull request so that lib owner can merge
Facing same issue. False Positive @ale5000-git Can you help?
@scottyab You may wanna check https://github.com/kdrag0n/safetynet-fix/pull/166#issuecomment-1509789489 and remove the check altogether.
this detector is dead
Selinux is returning a false positive.
We have removed the Selinux method in 0.1.1 given it's not accessible on later versions of Android and is not "truly" an isRooted indicator. Thanks for flagging this issue.
Hi. I have a Samsung note 20 ultra. I am not sure why rootbeer sample app indicates that my phone is rooted. My phone is not rooted.
I have used other apps like root checker, advanced root checker and root beer fresh and all indicate my phone is not rooted.
May I know if there are ways to check if there is a bug or there are something that is causing the false positive? Some screenshots below for your reference.
Thank you very much.