@Chainfire what do you mean by Xposed not supported? After installing suhide can I install xposed or suhide Will not be able to hide root from apps? Please explain
If you install Xposed you will not pass Safety Net, you will always be detected as rooted. suhide is, along with SuperSU, no longer developed or maintained. For active root development/hiding see Magisk. But you still won't be able to hide xposed.@Chainfire what do you mean by Xposed not supported? After installing suhide can I install xposed or suhide Will not be able to hide root from apps? Please explain
If you install Xposed you will not pass Safety Net, you will always be detected as rooted. suhide is, along with SuperSU, no longer developed or maintained. For active root development/hiding see Magisk. But you still won't be able to hide xposed.
If you install Xposed you will not pass Safety Net, you will always be detected as rooted. suhide is, along with SuperSU, no longer developed or maintained. For active root development/hiding see Magisk. But you still won't be able to hide xposed.
Remove /data/adb/su/suhide folder in TWRP.
**This is not regarding Su, but magisk.**
Hello, I'm really wanting to get some major help and don't know where to start yet; unless someone can point me in the right direction. I'm looking for a really really effective way to hide root and what Snapchat considers "3rd party" or not within their bs police state rules regarding things.. Passing SafetyNet and bypassing many (if not all)root hide methods and ultimately even (secretly and privately; appops, xprivacy) revoke permissions, isolate storage, even use workprofile (Island) isn't even enough for snapchat (god knows what other apps can do then..) To this day it doesn't seem possible to hide apps from other apps (sudohide is dated and crashes a lot; repackaging is cumbersome and not viable for every app that snapchat may throw a fit on (how it works around Island, I do not know). Use advanced root detector or any it use root detector, and it picks up that magisk manager is installed even with ZERO permissions granted. There isn't any articles (as far as I know) about how and what snapchat even picks up! Since snapchat can pick up any package name, like magisk's, this does mean it's possible for it to lock you out even without having the "risky" edxposed framework, assuming it does trigger a random ban occasionally.
Magisk (magisk hide enabled) + Riru Core + EdXposed + EdXposed Manager (unmodified package name) + Magisk manager (repackaged) + AppOps/xprivacylua (deny relevant permissions)/Storage Redirect (deny app to see entire phone storage). To make things complicated, when I used Island, which keep apps isolated from the actual device (apps can still detect root/busybox if magisk hide not enabled) snapchat randomly locked me out after a while; I denied it certain permissions via appops before the random ban, so maybe denying it certain permissions is suddenly grounds for a ban?
Xposed is now able to pass safetynet on android pie. EdXposed and Riru Core bypass safetynet. But it's still not enough when it comes to snapchat apparently.
---------- Post added at 05:49 PM ---------- Previous post was at 05:40 PM ----------
Can you confirm if snapchat checks for permissive or enforcing kernel.Remove /data/adb/su/suhide folder in TWRP.
**This is not regarding Su, but magisk.**
Hello, I'm really wanting to get some major help and don't know where to start yet; unless someone can point me in the right direction. I'm looking for a really really effective way to hide root and what Snapchat considers "3rd party" or not within their bs police state rules regarding things.. Passing SafetyNet and bypassing many (if not all)root hide methods and ultimately even (secretly and privately; appops, xprivacy) revoke permissions, isolate storage, even use workprofile (Island) isn't even enough for snapchat (god knows what other apps can do then..) To this day it doesn't seem possible to hide apps from other apps (sudohide is dated and crashes a lot; repackaging is cumbersome and not viable for every app that snapchat may throw a fit on (how it works around Island, I do not know). Use advanced root detector or any it use root detector, and it picks up that magisk manager is installed even with ZERO permissions granted. There isn't any articles (as far as I know) about how and what snapchat even picks up! Since snapchat can pick up any package name, like magisk's, this does mean it's possible for it to lock you out even without having the "risky" edxposed framework, assuming it does trigger a random ban occasionally.
Magisk (magisk hide enabled) + Riru Core + EdXposed + EdXposed Manager (unmodified package name) + Magisk manager (repackaged) + AppOps/xprivacylua (deny relevant permissions)/Storage Redirect (deny app to see entire phone storage). To make things complicated, when I used Island, which keep apps isolated from the actual device (apps can still detect root/busybox if magisk hide not enabled) snapchat randomly locked me out after a while; I denied it certain permissions via appops before the random ban, so maybe denying it certain permissions is suddenly grounds for a ban?
Sent from my SM-N960F using Tapatalk
I'd say the odds of that happening are somewhere between slim and none. And slim left town a few years ago heading for parts unknown.
I tested it on my note 3 with C9 pro rom 6.0.1
After flashing supersu to sbin mode, the root doesn't work
After flashing suhide, the suhide gui doesn't appear in app drawer and device seem that is not rooted
Reflashing supersu zip file in system mode and root worked again
Thanks
No. Use Magisk.
It's what I usually use but I have a module making me loop and wanted to delete it from /data, my rom is encypted and twrp does not decrypt it
adb wait-for-device shell magisk --remove-modules
Run the adb command below on your computer, turn on your device and plug in the USB cable. As is off-topic, any additional help should be requested in the Magisk discussion thread.
Code:adb wait-for-device shell magisk --remove-modules
SuperSU (and by extension, suhide) is EOL and no longer supported. Best use Magisk if you are looking to hide root.I first flash SuperSU Config and select Systemless SBIN mode then Reflash SuperSU v2.82 SR2 then Flash the suhide ZIP
in xiaomi mis5s plus. When i open supersufree, it immediately closes it. i cant also see suhide as an app.
I only want to use an app that needs to be shown as unrooted
edit
i again did flashing suhid zip. this time i wiped cache and rebooted. it waited at start, becasuse there was a progress bard. then i could login. There was different screensaver.
i cant see again suhudi icon. Now i cant open any app.. nothing is clickable
edit: after tryings, now i can click apps. UI changed but still cant see suhide icon
SuperSU (and by extension, suhide) is EOL and no longer supported. Best use Magisk if you are looking to hide root.
Most apps that detect root fall into the payment, banking/investing, corporate security, or (anit cheating) gaming category.
While a lot of apps have their custom root detection routines, with the introduction of SafetyNet the situation for power users has become worse, as developers of those apps can now use a single API to check if the device is not obviously compromised.
SafetyNet is of course developed by Google, which means they can do some tricks that others may not be able to easily do, as they have better platform access and control. In its current incarnation, ultimately the detection routines still run as an unprivileged user and do not yet use information from expected-to-be-secure components such as the bootloader or TPM. In other words, even though they have slightly more access than a 3rd party app, they still have less access than a root app does.
Following from this is that as long as there is someone who is willing to put in the time and effort - and this can become very complex and time consuming very quickly - and SafetyNet keeps their detection routines in the same class, there will in theory always be a way to beat these detections.
While reading that may initially make some of you rejoice, this is in truth a bad thing. As an Android security engineer in Google's employ has stated, they need to "make sure that Android Pay is running on a device that has a well documented set of API’s and a well understood security model".
The problem is that with a rooted device, it is ultimately not possible to guarantee said security model with the current class of SafetyNet tamper detection routines. The cat and mouse game currently being played out - SafetyNet detecting root, someone bypassing it, SafetyNet detecting it again, repeat - only serves to emphasize this point. The more we push this, the more obvious this becomes to all players involved, and the quicker SafetyNet (and similar solutions) will grow beyond their current limitations.
Ultimately, information will be provided and verified by bootloaders/TrustZone/SecureBoot/TIMA/TEE/TPM etc. (Samsung is already doing this with their KNOX/TIMA solutions). Parts of the device we cannot easily reach or patch, and thus there will come a time when these detection bypasses may no longer viable. This will happen regardless of our efforts, as you can be sure malware authors are working on this as well. What we power-users do may well influence the time-frame, however. If a bypass attains critical mass, it will be patched quickly.
More security requires more locking down. Ultimately these security features are about money - unbelievably large amounts of money. This while our precious unlocked bootloaders and root solutions are more of a developer and enthusiast thing. While we're all generally fond of shaking our fists at the likes of Google, Samsung, HTC, etc, it should be noted that there are people in all these companies actively lobbying to keep unlocked/unlockable devices available for us to play with, with the only limitation being that some financial/corporate stuff may not work if we play too hard.
It would be much easier (and safer from their perspective) for all these parties to simply plug that hole and fully lock down the platform (beyond 3rd party apps using only the normal APIs). Bypassing root checks en masse is nothing less than poking the bear.
Nevertheless, users want to hide their roots (so do malware authors...) and at least this implementation of suhide is a simple one. I still think it's a bad idea to do it. Then again, I think it's a bad idea to do anything financial related on Android smartphone that isn't completely clean, but that's just me.
Note that I have intentionally left out any debate on whether SafetyNet/AndroidPay/etc need to be this perfectly secure (most people do their banking on virus ridden Windows installations after all), who should get to decide which risk is worth taking, or even if Google and cohorts would be able to design the systems more robustly so the main app processor would not need to be trusted at all. (the latter could be done for Android Pay, but wouldn't necessarily solve anything for Random Banking App). While those are very interesting discussion points, ultimately it is Google who decides how they want this system to work, regardless of our opinions on the matter - and they want to secure it.