yashsingh1/xdaforums huggingface dataset:
[SuperSU] ZabiGarma:
I used v86.2, since that's what Chainfire said in the OP. I also read a few comments, and everyone who installed v86.2 had no issues.
[SuperSU] woooz:
Unfortunately this way with magisk make my system crash. And normal way doesn't work, even without xposed, after adding app to blacklist it still doesn't pass SafetyNet.
[SuperSU] yung40oz84:
Ok so now I'm really confused, I flashed suhide-rm then unSU and then superSU, the latest version, booted up my ROM, then went back, flashed suhide and I'm still getting the error asking if I have systemless root installed? Now oddly enough it worked one single time, I haven't gotten it to work again. But what is causing it to not detect systemless root, because I clearly have systemless root installed. Angler, AOSIP beta N.
[SuperSU] igoticecream:
/su/suhide/add 10005 gives me "/su/suhide/add: not found"

Listing the files on /su/suhide gives me

app_process32

suhide.uid

Whay am i doing wrong?

EDIT: Reflashed with FlashFire and everything went well
[SuperSU] Artim_96:
That's what I use SolidExplorer for. It has a dedicated section for apps, you only need to choose system apps or normal apps, scroll to your app and under properties you have the UID.

---------- Post added at 03:45 PM ---------- Previous post was at 03:41 PM ----------

I don't think you should use this together with Magisk, especially since it's not that compatible with SuperSU.

And sometimes, you need to revive app data before reboot, but sometimes you even need to reinstall the app.

And it's possible, that it uses a detection suhide can not work around (yet)
[SuperSU] woooz:
I did uninstal xposed, unistall magisk, unroot.

PokemonGo passes SafetyNet check so everything is fine.

I did flash SuperSU v2.78 SR1 and suhide-0.53.zip.

SuperSU is in systemless mode (first screen) and suhide is there because I can view list and I can add/remove apps from this list (second screen).

It looks like it's ok, but it doesn't pass SafetyNet check.

Tried this with SafetyNet Helper and it didn't work too.

What could go wrong?

EDIT:

Few post above, people tried this and it worked so I decided to test it myself because normal way didn't work.

Don't think that's the case, it works for some people.
[SuperSU] bobby janow:
Very cool app, thanks. Only a buck 99 for full version too. So used to root explorer so I'll have to play around with it see if it's useful to me other than UID detection.
[SuperSU] duowing:
I tried the rootbeer app, and added the UID to suhide and it only said rooted/detected due to busybox. It passed the su check. I then removed the UID rebooted and tried again and got many more strikes against me. Also in just playing around I realized that each time I would install, uninstall, reinstall the app that the UID would change.
[SuperSU] CSX321:
I started fresh last night, cleaned it up and flashed the stock boot image, SuperSU, and suhide v0.53. It's made it over 12 hours without a crash. :good: So now I just flashed ElementalX, and I'll see if it remains stable.
[SuperSU] blue4you:
What ever you did done in 0.53 - you did it right :D

On my device suhide still works and now both of my banking apps works without crashes und they did not detect root :D (still the 1st don't run on rooted device but both crashed with 0,52)

I'm very thankfull for you awsome work!!
[SuperSU] flotux:
Will it work for Motoroloa users? I have a Motorola Moto G 1st edition ("falcon") with the current CM13 nightly on it.

I'm asking as I read that Magisk does not work on Motoroloa hardware. I'm eager to find a solution to proceed with Pokemon Go. :)
[SuperSU] yung40oz84:
This is what I did before, but I found another method posted by a user to flash rom, gapps, suoerSU, boot up, then back to recovery and delete su folder from system/bin and system/xbin then flash suhide then superSU again and this actually worked, safety net passed
[SuperSU] AsturzioAugias:
This method actually worked, now I'm trying to flash xposed v86.2 and see if android pay and pokemon works

edit: seems working even with xposed flashed and activated, f*** yeah
[SuperSU] Mudvayne622:
Did you unmount System after erase system/bin/su and system/xbin/su?
[SuperSU] AsturzioAugias:
If this can help you, I did NOT unmount system after erasing the two folders
[SuperSU] CrazyCypher:
does systemless xposed 86.5 work too? Or only 86.2? Is 86.2 systemless?
[SuperSU] Franceschiello:
No.
[SuperSU] AsturzioAugias:
I used 86.2 systemless as stated in the first post ("you must be using [MENTION=4470081]topjohnwu[/MENTION] 's systemless xposed v86.2 exactly. It seems to mostly work during my non-extensive testing, but there are still some performance issues. Proceed with caution, expect bootloop.")
[SuperSU] Mudvayne622:
Success!! Have systemless root, passed safetynet check and PokÃ©mon Go working. Here's what I did.

Disable built-in root on AICP MM for Nexus 6

Reboot to TWRP

Flash Sr1 SuperSu 2.78

Reboot system

Install SuperSu Pro app (SuperSu was installed in system)

Reboot to TWRP Delete su from system/xbin (nothing in /bin)

Go to TWRP terminal and input command to force systemless install

Flash Sr1 SuperSu 2.78

Flash Suhide 0.53

Reboot system

Cry Tears of joy to have a Buddy PokÃ©mon

No crashes yet. Gotta try Android Pay

What happens when I want to update my Rom to the latest nightly? Do I need to do the whole process over?
[SuperSU] Malik Kim:
I couldn't use this app. This app can discover root.

Could you make suhide that couldn't find root of this app?

It is Korean bank app

App name is kb bank
[SuperSU] macschwag14:
Do I need to do anything special with Viper4Android? I know Magisk had a special V4A module because the modified /system tripped SafetyNet.
[SuperSU] Slypnslyde:
Aw man here we go

https://www.reddit.com/r/pokemongodev/comments/53heua/niantic_may_have_just_blocked_magisk/
[SuperSU] stnokd:
Hello,

I'm on Sony Xperia Z5 Compact E5823, with 32.2.A.0.253 and patched kernel (rootkernel v5.0 without root and busybox).

1.) Flash patched kernel.

2.) In TWRP Terminal: echo "SYSTEMLESS=true" > /data/.supersu

3.) Flash SR1-SuperSU-v2.78-SR1-20160915123031.zip and reboot.

4.) Reboot in TWRP, flash suhide-0.53.zip and reboot.

i.imgur.com/7FkdWbx.png

5.) i can't Flash xposed-v86.2-sdk23-topjohnwu.zip with with TWRP (error: requirement supersu =or> to v2.76)

Thank you.

Edit: Problem resolved, thank to Flashfire
[SuperSU] Rhoban:
I used echo "SYSTEMLESS=true" > /data/.supersu

But the SuperSU zip still flashes in system mode.

Should there be any confirmation in the terminal emulator after introducing that command? Or is there any specific format I have to use?
[SuperSU] nathanchance:
No but you can cat /data/.supersu to make sure there is text in there
[SuperSU] Rhoban:
Nevermind. I actually got it working right after posting that.

But thanks anyway :good:
[SuperSU] Gamu79:
Tried to do all the steps on post 1# on a S4 Gt9505 (arm v71..snapdragon qualcom)lollipop 5.0.1 stock rom odex

With no luck

:(

Have to wait then. ...
[SuperSU] chazall1:
I believe you are missing one Key in the command an (>)

it should be:

SYSTEMLESS=true" >> /data/.supersu

that should work
[SuperSU] Keksdroid:
SafetyNet check is finally successful! Switched from DU to RR Rom (both have built in root), repeated all my steps and finally it works as expected :)

Thanks a lot!
[SuperSU] nathanchance:
Already explained here that it doesn't matter.
[SuperSU] ZabiGarma:
Today I got the notification for a new Android OS update (7.0 Nougat - I currently have 6.0.1 Marshmallow). So, whilst I'm not keen on updating any time soon, I've been wondering how I should proceed, considering I've got suhide now and I'll want to update the OS at some point.

Thus far, all I've done is to download the IMG from the Android website, and flash it with FlashFire. However, now that I've got suhide and xposed installed, I've got no idea what I should be doing.
[SuperSU] unknown00:
i can't get this to install. i keep getting fatal error system/xbin/su exists process ended with error: 1. when i try to delete system/xbin/su i get error 1 again. i am using Magisk with it's systemless supersu
[SuperSU] stevecaboose:
Im running suhide just fine on cm14 but keep in mind there is not a working xposed for api level 24
[SuperSU] desztan:
I think you need to be on android 6 to work...
[SuperSU] Ch3vr0n:
I suggest you read the requirements again. Suhide NEEDS Android 6 or above. There's nothing to wait for as lollipop simply isn't and won't be supported.
[SuperSU] Artim_96:
I used root explorer too and still have it, but since I'm quite often using FTP I wanted something with it build in. First I had ez explorer... But as soon as I found out the CM-assholes bought it I went on searching for a new one. SE was the one I'm sticking to. I think it's great, worth its money and therefore won't be turned into an ad bomb in the near future.
[SuperSU] goister:
The 2 apps don't use any data, so I tried uninstalling them, reinstalling them, removing the original UIDs from the blacklist and adding the new ones in, then rebooting the device. It worked for the Digipass soft token app, but Rootbeer still detects the device as rooted.

As for Android Pay, am I to understand that as long as com.google.gms is in the blacklist (the first UID in the blacklist is 10009, which corresponds to com.google.gms), any app that uses SafetyNet for root detection will work with suhide? I've tried Pokemon Go as well, which I believe uses SafetyNet, and it ran just fine as well.

---------- Post added at 09:11 AM ---------- Previous post was at 09:05 AM ----------

Yup, I got almost the same result, except even after removing rootbeer from the blacklist, "su exists" comes out clean. It detected "root management apps" though. UID changes also. UID changes for the Digipass demo app as well upon reinstall.
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] have the logs shown anything? I happened to catch a play services crash in the act and see the 'impact'. I had just started streaming from my pc with the Plex app to my Chromecast. When the play services crash happened, the connection between the Plex app on my phone and the Chromecast stopped. Item playback timer no longer progressed and connection to the Chromecast had to be reestablished.
[SuperSU] CSX321:
Hmm. My Play Services just crashed, too, for the first time today. I had reinstalled everything from scratch last night, and I thought it was stable. I have a log, but I can't upload it until morning.

Edit...Just crashed again. :-/

And again.
[SuperSU] bigknowz:
Nougat

If you are decrypted, do not run the flash-all script or the OTA.zip. Manually flash the radio / bootloader / images and then flash a custom kernel before boot, otherwise the phone will try to encrypt and then not good things.
[SuperSU] goister:
Hi,

I just realized that since all the suhide related files are in /su/suhide, doesn't all an app need to do to detect suhide is to detect the existence of this folder, or perhaps the relevant binaries add, rm, list?

In fact, can't the app just detect the existence of the /su folder to determine root status?
[SuperSU] naeco:
Hi!

Any chance for it to work with Android 5?

Thanks!
[SuperSU] Hisucchi:
Hi, just created this account to say a massive THANK YOU to [MENTION=631273]Chainfire[/MENTION] for making this wonderful piece of software. Like many others a certain fad app wouldn't work any longer on my M8, and since MaximusHD never got updated since release I thought, why not refresh my phone with a new ROM? Major props to [MENTION=398245]LeeDroid[/MENTION] for a slick ROM that works flawlessly too (loving the HTC 10 camera) - thanks mate!

Flashing SuperSU and suhide was a cinch and everything worked right off the bat, seeing quite a few ppl struggling in this thread I'm surprised everything went so smoothly. Fingers crossed it will stay that way!
[SuperSU] Chainfire:
I have a lead on the cause, but I'm not able to reliably reproduce the crash yet, which makes testing difficult.

If you find a combination of actions that produce the crash reliably, please do let me know.

EDIT: Also, try clearing Google Play Services' data
[SuperSU] Federixbest:
Nothing to do... I can't flash suhide v0.53 because, during the flash, the installation can't find superSU SR1 in systemless on CM13.
[SuperSU] Artim_96:
Well, then it seems that RootBeer uses an unsupported root detection.

And yes, as long as SafetyNet doesn't fail and an app uses only that for verification, it shouldn't be able to notice any changes of the system
[SuperSU] goister:
As I suspected, I just did a check for the existence of the /su folder from my app, and was able to detect this, and hence detected a rooted device.
[SuperSU] Rhoban:
echo "SYSTEMLESS=true"> /data/.supersu

This is what worked for me.
[SuperSU] Chainfire:
Sure. There are other artifacts left as well. However, RootBeer returns 'not rooted' for me after blacklisting it and rebooting...
[SuperSU] Hellberg:
Is there anyone who managed to get suhide working on XtreStoLite (3.3.1) for Galaxy S6? The rom is pre-rooted which I guess might cause problems. I did a full unroot though and then SafetyNet checks passed, but when I install SuperSU v2.78 SR1 and then suhide v0.53 the check fails. I have verified that the right uid for com.google.android.gms was added to suhide and I added the SafetyNet-checker itself also just to be sure. I also tried installing Root Validator and adding that to suhide, and it still finds and uses root (not sure if it's supposed to work that way though).

When installing SuperSU v2.78 SR1 through TWRP (3.0.2.1), I get these error messages during the "Boot Image Patcher":

--- Already patched, attempting to find stock backup

--- Stock restore failed, attempting ramdisk restore

--- Ramdisk restore failed, aborting

Although root still works after patching, so SuperSU seems to be installed correctly but I guess there might be some leftovers from the SuperSU included in XtreStoLite that causes this. The SuperSU GUI reports the right version installed anyway (v2.78SR1) and apps using root works just fine. I tried restoring sboot.img from the latest stock rom (I'm not sure if that is the boot image that the installer is trying to patch though) and then flashed SuperSU again, but that still gave the same message as above.

Whenever I unroot using the SuperSU GUI, SafetyNet checks passes without any problems, so it seems like the rom itself passes when it's not rooted.

Any ideas?
[SuperSU] haga22:
do we need to unlock bootloader for systemless SuperSu?

do we need to unlock bootloader for systemless SuperSu, guys?

When i flash systemless-mode SR1 v2.78 SuperSu, i saw the log: "boot image patcher" and fail to extracting ramdisk. Here is my log?

Thks
[SuperSU] ratelutz:
My setup:

Xperia Z5 Stock ROM

kernel patched with rootkernel_v5.0

installed SuperSU 2.78SR1 in systemless mode

installed suhide 0.53

for testing i blacklisted an app and it seams to work, but my device does not pass the SAFETYNET CTS Test.

any hind how i can figure out what is wrong
[SuperSU] Artim_96:
Maybe the kernel could be what's triggering it? It shouldn't, but as long as there is nothing else that changed anything in /system, I don't know what else could have this side effect.
[SuperSU] Musa95:
Hey [MENTION=631273]Chainfire[/MENTION] it seems like suhide is not letting the device to rebuild dalvik cache.. Many of my apps are starting to force close.. First was only snapchat.. Then snapprefs.. Xposed installer.. Now gmail and Google play.. Need a logcat? Thanks in advance
[SuperSU] Triviox:
Hello [MENTION=631273]Chainfire[/MENTION], first: thanks for this great tool!!

i too report some bugs, in Galaxy S5 g900m; with SuperSU v2.78 SR1, suhide 0.53 and [MENTION=4470081]topjohnwu[/MENTION] 's systemless xposed v86.2.

I uninstall others systemless xposed, magisk; them flash stock rom with odin, and flash twrp.

After i follow the "how to" steps (that you said in the OP) to install supersu, suhide and xposed systemless.

Bugs :

-Cant do wipe dalvik /cache, if i wipe it in twrp the "optimize app" take only 10 seconds (over 330 apk, usually take minutes to optimize).

-When i reboot phone system takes more time that usually in bootanimation before starts, and try "optimize app" (only 10 seconds) after all reboot.

-The prompt to give su access is very slow to show in screen, some times i need open the apk more than 1 time to see it and press allow.

I attach liveboot.log

Any suggestion to fix it?

Thanks!!
[SuperSU] Chainfire:
That's an issue with that version of systemless xposed, I think. Not sure though.
[SuperSU] blue4you:
I had the same problem on my Z5 Compact.

Befor I tried su-hide I used a patched with su.

As I try su-hide at first time my Z5C also fails the safetynet test.

I flashed my Z5C with .253 FW with flashtool (without wipe data and apps), using a kernel without su and flashed supersu 2.78 SR1 and su-hide 0.53 and now all safetynet tests passed :)

Maybe the patched kernel with su leave some attefacts someware in the system.

Maybe you try it like I did...
[SuperSU] Triviox:
Thanks for your feedback, them, we'll wait for a better way to flash xposed systemless with supersu + suhide. Tell me if need more info or wanna test something.-
[SuperSU] ratelutz:
Thats what i also did.

But i changed some files in /system like hosts and gps.conf.

Am i right: modifing files in /system results in not passing safetynet check?
[SuperSU] shoey63:
Well I'm running SuperSU v2.78 SR1, suhide v0.53, Magisk v6, and systemless Xposed 86.5 on my Z3 concept MM 6.01. Not a single crash, and PoGo working with pokmon-controls-xposed-moduleDidn't even have to blacklist Pogo.:good:
[SuperSU] macschwag14:
We should ignore the notification to update the SU binary and not update it, correct?
[SuperSU] Triviox:
Oks, i'll try uninstall Xposed Systemless 86.2 and install 86.5; and will give feedback.

Thanks!
[SuperSU] karimrim:
Hi,

bootloop flashing 0.53, on my A510F with Android 6.0.1 stock.

Unstalling it fixes the bootloop.

Liveboot log attached
[SuperSU] Federixbest:
Yeeees, all works fine on my GT-I9515 with CM13. Thank you so much for your work [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] exodius48:
I get that issue too, then i check xposed log there is error like this "forcing image recompilation because /data/dalvik-cache/arm64/system@framework@boot.art is not compiled for the current Xposed version". Do you have error log like it?

So i think this issue come from Xposed v86.2.
[SuperSU] blue4you:
I don't know but I think its possible.

I did not make any changes on system partition after flashing.

The only think I have done is using adaway with a symlink (adaway make it by itself if you chose another path for hosts file)
[SuperSU] woooz:
Does it work for someone with Huawei device?

I have Huawei p8 lite with emui 4. Root is working in systemless mode but suhide doesn't. Just wondering if it's because of emui? Magisk was working without problems. Does emui somehow make it not working? Or it's not related?

[MENTION=631273]Chainfire[/MENTION]
[SuperSU] Triviox:
Question: if you now make wipe cache and dalvik, it works OK? After it, when you start system, the "optimize apk" works OK?

I uninstall Xposed Systemless 86.2 and reboot (with SuperSU v2.78 sr1 and suhide v0.53 still installed); and, after some reboots "optimize apk" was OK.

But, when i install magisk v6 and Systemless Xposed v86.5 the "optimize apk", after wipe dalvik and cache, dont work (only take 10 seconds optimize more 330 apks :rolleyes: ...them really dont optimize nothing).

I think that that problem will be fix in an update of xposed systemless topjohnwu's, or when someone develop a new xposed systemless that works 100% with supersu + suhide :D
[SuperSU] Uz986:
how can i installed supersu in systemless mode? and i am on cm14 so will this work?
[SuperSU] gothicVI:
This has been described several times in the SuperSU subforum as well as in this thread, e.g. two pages back.

Gesendet von meinem Moto G 2014 LTE mit Tapatalk
[SuperSU] Ch3vr0n:
[MENTION=631273]Chainfire[/MENTION] the procedure I posted in a previous reply pretty much always causes a crash. 1. Pull device out of standby, 2. Connect plex app to Chromecast, 3. Start playback of a video file. I usually within minutes the crash happens.
[SuperSU] urzahil:
With version 0.53 I'm getting the following message when I try to add an UID:

shamu:/su/suhide # ./add 10015

./add[9]: can't create /su/suhide/suhide.uid: Read-only file system

How can I remount the /su file system in rw mode?
[SuperSU] ZabiGarma:
To be honest, I've got no idea if my phone is decrypted.

All I've done to it is install systemless root, TWRP, suhide and now systemless Xposed.

I've always flashed the OTA zips. So, I'm completely ignorant on how to update in any other way.
[SuperSU] bigknowz:
Encryption

Settings > Security

Under Encryption it will say Encrypt Phone if you are decrypted.

Regardless, back up everything. I learned my lesson the hard way.
[SuperSU] ZabiGarma:
My phone is decrypted then.

That being said, why would it become encrypted? Does the Nougat update always do that?

Or is that an effect of having suhide and Xposed installed.

I do have a backup from the time I installed the latest SuperSU.
[SuperSU] DryEagle:
In the start of thread it says android 6.0 required. I take it there is some technical reason for this? Is it completely impossible that it will work in 5.1? I don't want to try if it will just brick the phone...

Also, has anyone test if it works with CM13?
[SuperSU] Meloferz:
[MENTION=631273]Chainfire[/MENTION], I recreated the bootloop on my phone and I attached the log. I'm using a Xperia Z2 with stock rom 6.0.1, Advance Stock Kernel, Magisk, Systemless Xposed 86.2, SuperSU 2.78 SR1 Systemless

View attachment 3882295
[SuperSU] CSX321:
[MENTION=1754043]Ch3vr0n[/MENTION] I'm starting to think maybe my Play Services crash is unrelated to suhide. It went over 12 hours without crashing, crashed 3 times within 15 minutes last night, but now hasn't crashed again for over 16 hours. Looking at the log, it almost seems like mine was caused by some kind of comm failure, possibly something about my home Wi-Fi. As far as I can recall, it hasn't crashed while I've been at work.
[SuperSU] ZjemCiKolege:
I found problem on g3 zip no install files from zip like add list rm and su.d
[SuperSU] igoticecream:
i have got them same issue and found a solution. Use FlashFire instead TWRP to flash suhide (maybe i forgot to mount data or something, idk)
[SuperSU] .NetRolller 3D:
Note 4 N910C on stock Marshmallow. Getting a bootloop with SuperSU 2.78 SR1 + Systemless Xposed 86.2 + suhide 0.53.

It appears from the logs that Xposed refuses to acknowledge its newly compiled dalvik-cache files as its own, instead clearing the dalvik-cache and triggering another rebuild before the ongoing rebuild even had a chance to finish.

Xposed alone works (& is able to build a good dalvik-cache that persists across reboots), as does suhide alone.

Disabling Xposed using the Xposed Installer before flashing suhide makes no difference.

3 logs attached in the zip:

liveboot-failed.log was created by booting into SuperSU + Xposed (no suhide) to generate/verify a good dalvik-cache (which therefore shouldn't be regenerated when suhide is then flashed), enabling liveboot log saving, flashing suhide, and rebooting. Despite Xposed-ized dalvik-cache files being present, dalvik-cache is wiped over and over again, never to be fully rebuilt. No "Android is starting" screen shows uo,

I force-rebooted to recovery after letting it loop for a while, and flashed suhide-rm to uninstall suhide. The next boot session was logged using both liveboot (liveboot-good.log) and logcat running on a PC (logcatgood2.log), as liveboot stopped logging as soon as the "Android is starting" screen appeared.

The same behavior is seen also if I allow dalvik-cache to be regenerated without xposed, then flash xposed and suhide in one go. So, regardless of what xposed finds in the dalvik-cache, it's rejected and deleted if suhide is installed.
[SuperSU] woooz:
Tried so many ways and this is only one that worked for me:

Device is lagging a bit with xposed enabled but it works.