yashsingh1/xdaforums huggingface dataset:
[SuperSU] photolarry:
Maybe so. Just weird that a few library files can be cause of Android unable even boot up. It's stupid that Google is being so ridiculous. Making you lock your bootloader... And wipe the phone... Just for Pay to function??? Screw them
[SuperSU] mobileman88:
We all just need to hang in there. either november update or no SN pass
[SuperSU] harpin14789:
lol, I didn't mean to say that. I meant to say su folder. sorry, autocorrect somehow changed it to that.
[SuperSU] littlefabio:
I am running purenexus 6.0 , latest supersu, and can't get suhide to work. Any suggestions?
[SuperSU] michaely123:
Nexus 6p 7.0.0 NBD91K

I flashed SuperSU v2.78 SR3, suhide v0.55, and ElementalX 3.09. Ended up in a boot loop for me.
[SuperSU] dratsablive:
Yes suhide will cause bootloop on > 7.x
[SuperSU] mobileman88:
Same for all of us on the November update.
[SuperSU] bushwakko:
I'm on 7.1 (crDroid cm14), with supersu and suhide installed. I'm booting just fine. However, I can't log in to snapchat, and my Vipps app says it's "not supported on rooted devices".
[SuperSU] Trak-X:
Use rootswitch to disble temporarely root, login and the reenable root
[SuperSU] bushwakko:
I tried doing 'full unroot' in supersu and then rebooting. However, snapchat still wouldn't log in, and Vipps still thought it was on a rooted phone. I have a samsung s4 lte.

---------- Post added at 04:31 PM ---------- Previous post was at 04:15 PM ----------

I can't find rootswitch on the app store, and it's not obvious what you are referring to by googling either.
[SuperSU] Trak-X:
https://www.asus.com/zentalk/tw/for...wNDk1fGJmMjhjZGZifDE0NzY0MDUzNjB8MHwxNzM1NDI= - this is the original thread where it was found. I received it on Google Plus.
[SuperSU] bushwakko:
Ok, I found it on a page the asus forum (it just had chinese characters so I didn't trust it at first). Anyway, disabling root with "stop all su daemons" checked off didn't help. Still get login problem message with snapchat. In addition, re-enabling from root switch doesn't seem to work...
[SuperSU] Fenny:
If you stop all the su daemons, you probably can't launch processes as root anymore because partitions are mounted with nosuid.

[MENTION=631273]Chainfire[/MENTION] For the pixel phones, do you think we could fork all processes (or at least zygote) from the real init inside of a sort of chroot jail to hide the bind mount?
[SuperSU] mattzeller:
Make sure you add snapchat to suhide

Sent from my SCH-R220
[SuperSU] grep_i:
Probably suhide is not working on Android 7.1 as a lot of users already reported.

Snapchat does not have to be added to the suhide blacklist as it utilizes safetynet which is blacklisted by default if you install suhide correctly.
[SuperSU] mattzeller:
For me snapchat wouldn't log in until I added it to suhide. Since he flashed suhide and the device booted, makes me think it's working for him being it's custom ROM (I am assuming here)

Sent from my SCH-R220
[SuperSU] deniskr:
If you can't pass SN while you're phone is unrooted, then you can't pass with installed suhide and rootswitch... First flash original boot.img than do clean ROM install, then unroot within SuperSU app, and than run SN(you should pass this time)... And than you can follow suhide installation process, with root switch ofc...
[SuperSU] xGarro:
Suhide doesn't seem to be working for Galaxy J5 users apparently, (myself using SM-J500M with Android 6.0.1). I hope with the upcoming CM13 it starts working.
[SuperSU] ScottIsMyName:
This is not true. For phones where safetynet is able to check for a locked bootloader, you actually need root to pass safetynet, otherwise, even without root, your phone will fail. Root allows installing modules like xsetprop that are able to set normally read only build.prop items to whatever value you want.
[SuperSU] vt0r:
You don't necessarily even need root for that. Several custom kernels for the 6P and other devices omit the ro prop that's used to determine bootloader unlock status (mine included), and that resolves it with no userspace apps/daemons/mounts or any requirement for end user root access.
[SuperSU] yochananmarqos:
That makes absolutely no sense. An untouched bootloader using the stock ROM will pass SafetyNet on any device. Installing a custom kernel that includes the commit to hide the bootloader status does not require root.
[SuperSU] bushwakko:
SafetyNet helper fails "response validation" with error msg: "Response payload validation failed". I'm on a galaxy s4 (9506) with crDroid 7.1. I rooted this phone so long ago, I don't even remember what I did to the bootloader (if that matters).

edit: So if it's because of my unlocked bootloader, how do I lock it and what is the consequences of doing that?
[SuperSU] jed_f:
Since nobody here confirmed if their AP transactions are successful I went to Fairprice today to buy a mineral water and tested AP and it's successful. Before tapping on the terminal add card then X out of it. To Chainfire thank you for suhide and SR3.. To the guy in the Asus website for the Rootswitch thanks :)
[SuperSU] osm0sis:
Apologies for the semi-OT.

My updated unSU Script zip is now posted/linked in my Odds and Ends thread for those unrooting to pass SafetyNet checks. :good::)
[SuperSU] grep_i:
You finally found some time to do it.

Looking good.
[SuperSU] deniskr:
He have S4 LTE and those have factory unlocked bootloader, so they can pass SN without root,and without kernel modification... Only phones with manual unlocked bootloaders are problem for SN...
[SuperSU] alelopinf:
After many tries I can't remove suhide with the zip. Manually with root explorer I can't find in system "su/hide". How can I find it and how can I finally remove or uninstall suhide?

Enviado desde mi eMAX mini mediante Tapatalk
[SuperSU] neo_mat:
no boot after suhide installation: see liveboot.log

Hello

Problem with QSEECOMD

With miui 8 and a nexus 5, I cannot boot after suhide installation. ( I can boot if I remove "/data/su.img" or TWRP restoring)

supersu 2.78 SR3 woks correctely.

Okboot.log is only with supersu boot.

thanks
[SuperSU] ScottIsMyName:
The Nexus 6 cannot use the custom kernel commit to hide the bootloader status (like the 5x and 6p can). So, N6 users who are running stock with an unlocked bootloader will fail safetynet checks with no root.
[SuperSU] grep_i:
I won't argue with you but it is strange indeed, on my device it is working out of the box as does PoGo because of checking SafetyNet if safetynet check fails

SC and PoGo do not work either as soon as I pass SafetyNet SC and PoGo works again without me adding anything to the blacklist.

I guess something is wrong with your setup if you have to add SafetyNet checking apps to the blacklist.

Is it in any way possible you updated suhide from earlier version without removing earlier version first ?

Well in the end it is working for you even though not as designed.
[SuperSU] Tikerz:
nevermind
[SuperSU] mattzeller:
I wouldn't necessarily say that there is something wrong with my setup considering with 3 different ROMI I have to do the exact same thing. But I always live by: even if devices are supposed to be the same every single one of them is different, and will behave different.

Sent from my SCH-R220
[SuperSU] koko115:
[MENTION=631273]Chainfire[/MENTION] this project is dead ?
[SuperSU] shuckeru:
Hi [MENTION=631273]Chainfire[/MENTION],

i've got a logcat of my endless boot issue that a few users also experience in the new november update for 7.0 nougat. This logcat is from a nexus 6p running NBD91K 7.0 stock rom, with Flash kernel 3.15, and SuperSU SR3 systemless. no xposed, no magisk.

removing suhide allows the device to boot and be used with root normally. have tried combinations of SuperSU SR1/SR3 and suhide 0.53/0.55 with the same results. did not have a problem on NBD90X 7.0 october update

it is quite clear at the end of the logcat file that the system cannot access the sensor server.

thanks for your work so far :)
[SuperSU] Tin_Man_0:
Su update for G935X rooted phones

Any chance there will be an update to the SU on rooted G935X phones? Currently the root limits us to stay with a custom SU 2.74. In order to try out suhide we need at least 2.78R1.
[SuperSU] yochananmarqos:
Any chance you could ask in your device thread? The limitations you specified have nothing to do with suhide.
[SuperSU] lg-ks20:
I do buy your explanation.
[SuperSU] akenis:
I pass SN with Pure Nexus, Elemental, SR3, suhide 55, and root switch. But Android Pay says I may be rooted when checking out.
[SuperSU] :
Can somebody explain how to do?

I have a Samsung Galaxy S4 running CM13 and i can't delete /xbin/su. Gives me an error evertime..

So, how can i delete it to use suhide?
[SuperSU] Mynacol:
In Recovery (TWRP) it will work, although not tested myself
[SuperSU] mattzeller:
In TWRP make sure you mount system and using TWRP's file manager you can delete them

Sent from my SCH-R220
[SuperSU] :
Yes it worked, thanks. But Pokemon already doesn't :(
[SuperSU] lg-ks20:
Pokemon will definitely work on CM13.

It seems you haven't remove the su file in /system/bin.
[SuperSU] :
Ok i'll try again tomorrow.

I did it so:

Flash rom and gapps and supersu 2.78 sr3

Reboot to system

Install magisk

Reboot to system

Reboot to recovery

Remove /bin/su and /xbin/su

Flash suhide

Reboot to system

Install Xposed v86.6 with magisk manager

Reboot to system

Install pokemon
[SuperSU] orlyyan:
It's necessary install xposed ? For have root, personally I am not iinteresed Po go , only want root my fone , what is the steps
[SuperSU] dafluke24:
That doesn't sound correct. I have a N6 with unlocked bootloader, no root and still pass SN just fine and AP works.
[SuperSU] ScottIsMyName:
What version of android? This is for 7+
[SuperSU] Tin_Man_0:
It kinda does. It's one of the minimum requirements and it's the same developer. But I get your point. I already posted there too.

The way I figure it, this whole app will become a check box in SU Pro in the not so distant future anyway.
[SuperSU] Artim_96:
Of course not. And no, we can't help you to root your phone.

1. This thread about suhide, not root itself

2. Since the root process is at least manufacturer specific if not device specific this thread is not the place to discuss that. You should go into your devices sub forum, you'll find all information on how to root there
[SuperSU] Portgas D. Ace:
Magisk is the problem. It is detected by SN, so you won't be able to play PoGo with Magisk installed. Use Xposed v86.2 from the OP instead and remove Magisk completely.
[SuperSU] Nevuly:
I can't boot when I flashed suhide.

I using Nexus 5X, and I flashed November Security Patch.

It was worked on October Security Patch, But Now I can't use that.

I using SuperSU 2.78 SR1, and that is modifed to use banking apps.
[SuperSU] :
Half right. I forgot to tick "hide" in magisk. Damn...
[SuperSU] Portgas D. Ace:
But Magisk doesn't hide Xposed, so Xposed is detected, right?

Magisk Hide does only hide itself plus its modules, but not Xposed (even given the fact that Xposed is a Magisk module).
[SuperSU] :
My knowledge is not so good. But on my S7 did it work ?
[SuperSU] Portgas D. Ace:
If it is true that you pass SN with Magisk and Xposed, then you should report this in the Magisk thread.
[SuperSU] :
Now i tried without magisk and without Xposed. Only supersu and suhide. I deleted the two files. Doesn't work... Don't know why
[SuperSU] Portgas D. Ace:
Clean flash? SuperSU, suhide, removed all other su files and Xposed files?
[SuperSU] Jayman007:
I seem to be having issues as well on my 5x after flashing nov patch. Just after flashing SU I can't boot. I have tried sr1, sr2, and sr3.
[SuperSU] :
Clean flash yes. Wiped cache, dalvic, system, data and internal storage. Flashed cm13, gapps and supersu. Rebooted to system. Rebooted to recovery. Removed /bin/su and /xbin/su. Flashed suhide. Rebooted to system.

So what am i doing wrong?
[SuperSU] Portgas D. Ace:
Die you remove Xposed before uninstalling Magisk?
[SuperSU] :
I don't understand. I did a clean flash. Wiped system, data, cache, dalvik and internal storage. So everything must be removed or not?
[SuperSU] lg-ks20:
Did you install Root Switch v1.3.3.2 & disable root within the app w/o ticking other options ?
[SuperSU] Portgas D. Ace:
You'd be surprised how many people around here consider a clean flash being to wipe system, cache and dalvik, therefore my question. But you did a complete clean flash, which should be the correct way. Mayne your ROM's default kernel is permissive, but from my understanding this might also trip SN.

Also the question about root switch (see reply above) is a good one. The root switch app is required to disable root temporarily.
[SuperSU] :
No. I'll have a look at. Thanks

Stock Kernel of cm13 is enforcing if i am not wrong
[SuperSU] lg-ks20:
Yes, it's enforcing.

PoGo also works in permissive mode on CM13.
[SuperSU] ltjmax:
Find any workaround for this bug?
[SuperSU] Nekromantik:
same issue here in screwed on latest vendor and suhide 0.55.

had to remove su hide.

I also get issue where suhide cant install as it detects su in /system/xbin even on systemless mode.
[SuperSU] Jayman007:
So I did some more testing on my 5x with the Nov patch and it seems that suhide is causing the phone to not boot. When I flash back to the october release of 7.0 I am able to get AP to work and play nice rooted using rootswitch, suhide, sr1, franco kernel.
[SuperSU] Hannibal226:
First Problem seems to be related to november patch (here, too)

But because the second u just have to delete the SU file in "/system/xbin/" via TWRP file manager. (before u have to mount system)

CHEERS!
[SuperSU] Tikerz:
November patch screwed suhide.

Google: We will just detect root and fail SafetyNet

Google: Fack

Google: Let's detect unlocked bootloader

Google: Fack

Google: Let's detect Magisk

Google: Fack

Google: Let's detect suhide

Google: We're winning now!
[SuperSU] Jayman007:
No worries. I reverted back to October build and then use the Nov Franco kernel which has some of the nov security patches.

That is working for me until we get an updated suhide from [MENTION=631273]Chainfire[/MENTION].
[SuperSU] Tikerz:
I wish we had Franco Kernel on the OP3. Been playing with the latest CM14.1 nightlies so we're stuck with November patch until suhide is updated.
[SuperSU] nzzane:
When flashing the latest .55 in TWRP 3.0.2, it says unable to mount /su etc etc

I have SuperSU 2.78 SR1

Fatal error: /su could not be mounted

Do you have SuperSU 2.78 SR1 or newer installed in systemless mode?

Updater process ended with ERROR:1

Side Note: while trying to flash SuperSU 2.78 SR3 when installing systemless - it brings up an error

Finding boot image

boot image /dev/block/mmcblk0p29

extracting ramdisk

decompressing ramdisk

checking patch status

already patched, attempting to find stock backup

stock restore failed, attempting ramdisk restore

ramdisk restore failed, aborting

PASTEBIN with entire log

I have a Z5C, unlocked bootloader, TWRP 3.0.2, latest firmware - .302. ROM: XPOWER 5

To install supersu in the first place i flashed a custom kernel.
[SuperSU] danieldmm:
After the android-6.0.1_r74 merge with the november patch running lattest cm13 phone will display a black screen when finish booting and stays there with suhide installed, remove suhide and phone bootup just fine.

On my case its not even a matter of safety net detect or not, its phone with a blackscreen not letting making anything.

Cheers and hope [MENTION=631273]Chainfire[/MENTION] can find something about this.
[SuperSU] G U C C I:
This is a very well known issue.
[SuperSU] Nevuly:
Maybe SuHide need to update for Nov patch.
[SuperSU] danieldmm:
Can you point me to the post that stats its a will know issue? Because search és the thread for black screen after boot and did not find nothing about.

Thanks in advance.
[SuperSU] mattzeller:
There are at least 30 posts stating that it doesn't work with the latest iteration of 7.*

Sent from my SCH-R220
[SuperSU] dratsablive:
Suhide and 7.1 causes bootloop CM included.
[SuperSU] danieldmm:
No, this is only happen after November patch, using 7.1 for a few weeks and it always worked, no bootloop. So, again, where is stated its a know problem? Because using previously CM14 and then CM14.1, never have a single bootloop using Suhide ( kernel permissive ) , and with November patch, phone does not bootloop. After boot screen goes black dimmed and stays there ( no bootloop )
[SuperSU] dratsablive:
It's been a problem for standard 7.1.1 since release. Go back through thread and read.
[SuperSU] kidlerek:
android pay not work with supersu 2.78-sr3 and suhide v0.55. On 1+3 stock Rom 2.3.7 any ideas?
[SuperSU] Portgas D. Ace:
Well, it does work. But without further details about your device and ROM, no one will be able to advice properly.
[SuperSU] kidlerek:
Ok my mistake. I have one plus 3, stock Rom 3.2.7

Wysłane z mojego ONEPLUS A3003 przy użyciu Tapatalka
[SuperSU] neo_mat:
Is someone with miui 8 can boot after suhide installation ?

boot loop on :

<5>[ 243.956872] init: Service 'qseecomd' (pid 7819) exited with status 255
<5>[ 243.956933] init: Service 'qseecomd' (pid 7819) killing any children in process group
<5>[ 248.958061] init: Starting service 'qseecomd'...
<5>[ 248.958574] init: Starting service 'thermal-engine'...
<5>[ 248.958995] init: Starting service 'ssService'...
<5>[ 248.962315] init: Service 'thermal-engine' (pid 7988) exited with status 1
<5>[ 248.962411] init: Service 'thermal-engine' (pid 7988) killing any children in process group
<3>[ 248.971602] init: cannot execve('/system/bin/ssServices'): Exec format error
<5>[ 248.972117] init: Service 'ssService' (pid 7989) exited with status 127
<5>[ 248.972211] init: Service 'ssService' (pid 7989) killing any children in process group
D/QSEECOMD: ( 7987): qseecom listener services process entry PPID = 1
E/QSEECOMD: ( 7987): Listener: index = 0, hierarchy = 0
E/QSEECOMD: ( 7987): Init dlopen(librpmb.so, RLTD_NOW) is failed....
E/QSEECOMD: ( 7987): ERROR: RPMB_INIT failed, shall not start listener services
<5>[ 248.975779] init: Service 'qseecomd' (pid 7987) exited with status 255
<5>[ 248.975836] init: Service 'qseecomd' (pid 7987) killing any children in process group
<5>[ 253.981412] init: Starting service 'qseecomd'...
<5>[ 253.982291] init: Starting service 'thermal-engine'...
<5>[ 253.98314 nt trigsrie'sevc'.
<3>[ 253.984556] init: cannot execve('/system/bin/ssServices'): Exec format error
<5>[ 253.985272] init: Service 'ssService' (pid 8142) exited with status 127
<5>[ 253.985453] init: Service 'ssService' (pid 8142) killing any children in process group
<5>[ 253.985866] init: Service 'thermal-engine' (pid 8141) exited with status 1
<5>[ 253.986093] init: Service 'thermal-engine' (pid 8141) killing any children in process group
<5>[ 254.032606] init: Service 'qseecomd' (pid 8140) exited with status 255
<5>[ 254.032838] init: Service 'qseecomd' (pid 8140) killing any children in process group
D/QSEECOMD: ( 8140): qseecom listener services process entry PPID = 1
E/QSEECOMD: ( 8140): Listener: index = 0, hierarchy = 0
E/QSEECOMD: ( 8140): Init dlopen(librpmb.so, RLTD_NOW) is failed....
E/QSEECOMD: ( 8140): ERROR: RPMB_INIT failed, shall not start listener services
<6>[ 256.861007] max17048_work: rsoc=0x74BE rvcell=0x0BE3 soc=59 v_mv=3803 i_ua=589651 t=344
<4>[ 5.058 elh:bteyl5 =83t3. = t3c73cg
[SuperSU] danieldmm:
Dont answer if you dont have any constructive answer. Will repeat one last time. Never got any issues with Suhide on Android 7.0 and 7.1 , the problem only appear with the November patch. Its also black screen with people that install Xposed, Suhide its not the only facing the same problem. Again, this only appear with the November patch ( in case you did not read last times wrote here )
[SuperSU] Fenny:
November update:

This is what breaks suhide.

https://android.googlesource.com/platform/frameworks/base/+/b8be33b0bedec211708c4525b9d3f3b4effb385c
[SuperSU] danieldmm:
Thanks, tonight will revert that on my rom. Cudos for pointing the commit.
[SuperSU] Fenny:
I would just add to the whitelist:

"/data/adb/socket_haploid32_root",

"/data/adb/socket_haploid64_root"

Edit:

Actually it would probably close the sockets still even when whitelisted because they are unix_fd. Your way is better for now, but may be detectable in the future.
[SuperSU] dratsablive:
Sorry, but I have been on 7.1.1 since October, and SuHide has caused the bootloops since then. It is a known issue before the November update. If you would read mine and other posts on this you would see this.
[SuperSU] mobileman88:
The issue has been located in one of the commits. Hopefully the Dev can fix it
[SuperSU] imarq24:
Will this work for air watch ? I need to use that app for work email but due to being rooted can't use..
[SuperSU] mobileman88:
No idea. Test it? Don't have Airwatch so can't confirm
[SuperSU] Fenny:
I can confirm that reverting that commit, or patching libandroid_runtime.so is required. I was able to get suhide working(-ish) on the pixel XL. The only problem is that my modified libandroid_runtime.so mounts kept getting hidden which means ACTUALLY hiding su from any apps causes a bootloop. xD If I disable verity and write the file to system it will resolve the issue, but also defeat the purpose.

*EDIT*

See patched files here, maybe someone can get further with these: http://cheatersedge.org/android/PixelXL/libandroid_runtime_pixelxl_NDE63V.tar
[SuperSU] danieldmm:
For me the revert its working like a charm... CM14.1 on OPO

Enviado do meu A0001 através de Tapatalk
[SuperSU] SamuelBegui:
Apologies, but what did you revert to get it working on your end?
[SuperSU] Fenny:
This commit.
[SuperSU] kwstakis:
Is there any chance to hide unlocked bootloader?cause i cant read 489 pages :? lg g4 android 6.0 unlocked supersu magisk suhide rootswitch
[SuperSU] Artim_96:
1. There is always the search function

2. Yes, at least for Nexus devices it seems that Franco Kernel send to do that
[SuperSU] soder:
I'm on a OnePlus One with the stock COS 13.1.2 version.

It was rooted with 2.78-SR1, had suhide 0.55, was running Magisk v8 and Xposed 86.6 (the Magisk version I guess). A couple of weeks ago I had to use Root Switch 1.3.3.2 to be able to pass Safety Net.

Today I updated to Magisk v9 and then later I flashed 2.78-SR3.

I know there is something called Magisk Hide within Magisk Manager now, and I wonder if there's something I can do with 2.78-SR3, suhide 0.55 and Magisk v9 to pass SafetyNet without the need of turning if off with Root Switch?

Thanks for the help, and sorry if I missed some obvious posts about this...

/Söder
[SuperSU] an0therus3r:
How do i tell if SuperSU is in systemless mode?

I flashed SuperSU SR3 on this N rom http://xdaforums.com/oneplus-one/development/cyanogenmod-14-0-t3464337

It has the October security patches so i flashed suhide 0.55 and it complained about su being found in /system/xbin/, removed this and installed suhide without issues.

But i think it's not working because apps from Good (which are bad) still complain about device being jailbroken. With my previous Marshmallow ROM this method worked perfect but now i'm unsure if i really have SR3 installed in systemless mode or that suhide installed successful.
[SuperSU] danieldmm:
Setpropex can do that, search for this tool to use on terminal...
[SuperSU] soder:
When in SuperSU settings, at the bottom, there is an option under System "Install SuperSu into /system. That shall be greyed out if you're in systemless mode. It shall say "Not (currently) available in system-less root mode".

/Söder
[SuperSU] an0therus3r:
Yeah i found that also but was unsure if it was correct. Thanks for clarifying.

Seems the people behind Good Technology are smarter than i thought about detecting root.
[SuperSU] lg-ks20:
Please read posts # 3208 & 3209 at page 321 for AutoRoot Switch.
[SuperSU] soder:
Hmm, automate, isn't that just some kind of Tasker lite?

Well, is this the only way to do it, by some kind of extra apps, I kind of can toggle it myself.

/Söder
[SuperSU] mobileman88:
Awesome. At least we're getting somewhere. I tried both 7.1 DP1 and 7.0 November, same issue of getting stuck in boot animation.