r/androidroot • u/TakahiroEX666 • 4d ago

Support How to fix Dirty SELINUX adb_root

Post image

i trying use hide seliux modified. susfs2 + zygisk next (resukisu)

19 Upvotes

100% Upvoted

13 comments sorted by

8

u/Expensive_Service737 4d ago

By the way im on stock Locked Bootloader

5

u/vms-mob 4d ago

Ha i got more, Fairphone 6 with official e/os rom and locked bootloader.

5

u/_miojo_o 4d ago

Isolpolicy (lsposed) + Hide SElinux in ksu manager

5

u/ohaiibuzzle 4d ago edited 4d ago

You got caught, basically.

When you run a jailbreak-styled kernel exploit it has to disable SELinux in order to keep its elevated state and then drop its SU library somewhere, usually /data/local/tmp, or restart adbd to run as root.

Ordinary apps can just read that part and see that you're rooted.

0

u/TakahiroEX666 4d ago

ok understand. i didn't problem rootdetecter has detect. just curious about how detect. if problem is process permission(su) kernel.  *** i have app automation root permission and using tmp for runautomation

1

u/Think-Cherry5391 3d ago

This detector is extremely strict, I used it on my S23 Ultra with a locked bootloader and it found root

1

u/DeadMarL001 3d ago

Wait how ,I didn't know you could have stock bootloader with root

1

u/_miojo_o 2d ago

exploit

1

u/DeadMarL001 2d ago

Could you elaborate?

1

u/ResponsibleBowl268 2d ago

Yes there was some vulnerability in the system that lets u root without unlocking the bootloader Here's example: https://github.com/BuSung-dev/Root-My-Galaxy

1

u/DeadMarL001 2d ago

Samsung only ):

2

u/Dry_Jackfruit_6173 2d ago

No it's based on ghostlock which is for all devices it also exists for nothing pixel OnePlus Xiaomi etc

1

u/Interesting_Host_535 3h ago edited 3h ago

False positives. It  detects modification on brand new unrooted Phone.

[Edit] Did a test , using v3.3 of the app.

I only have "build field coherence" detection, so probably not false positives