yashsingh1/xdaforums huggingface dataset:
[SuperSU] GuardianUSMC:
Got it, thank you.

I get that and know how to search GP, thank you; but I am not a fan of installing a bunch of apps for every little thing if there is a way to do it without the overhead. So, I was mostly asking in that spirit of using ADB or Terminal on the device itself. Or even a native interface, akin to how Samsung gives you the Knox status itself without having to install something else. So, yeah - thanks.
[SuperSU] krazekid7:
I can confirm suhide works on opr6
[SuperSU] m00head:
Samples for the Google SafetyNet API - GitHub

https://github.com/googlesamples/android-play-safetynet
[SuperSU] gverma1:
Have never used a Developer Preview image before, hence the question. Can I flash Developer Preview opr6 like any other regular factory image after removing -w flag? I want to retain all my apps and settings, as setting them up again is a painful process.
[SuperSU] GopalKaul:
When Android O is officially released, why Developer preview?
[SuperSU] gverma1:
Cant see Oreo in Factory Images. But can see opr6 in Developer Preview download section.
[SuperSU] jcmm11:
https://developer.android.com/about/versions/o/download.html
[SuperSU] DEVILOPS 007:
Am I able to make play store certified for apps like Netflix? I've already hidden the play store from root but do I need to do something else or is it not possible? Thanks
[SuperSU] KaMyKaSii:
You do not need to select the PlayStore to hide root. The only package needed to hide root is already selected by default. If your device still does not appear as a certified, you are probably in a custom rom where the device ID props differ from the stock rom
[SuperSU] DEVILOPS 007:
I am on a custom ROM but I just assumed that hiding root like magisk hide would be the same as suhide but I haven't really looked into how this safety net stuff works much. Thanks for the response.
[SuperSU] jcmm11:
It took me a little while. I also rebooted in-between. I now show as certified. Custom ROM.

Don't even have to be in hide mode (suhide and supersu are currently visible). So just give it some time (24 hrs?) and see what happens.
[SuperSU] Locura18:
Or delete the cache and data out of play store app in the settings and reboot. And that should do it
[SuperSU] DEVILOPS 007:
Already tried leaving it a while as I've been using it for about a week or two now.

---------- Post added at 06:13 PM ---------- Previous post was at 06:12 PM ----------

I tried your suggestion and it worked like a charm! Thanks a ton!
[SuperSU] KaMyKaSii:
As has been said, clearing PlayStore data speeds up this process. But the recommended is to download an app that checks Safetynet. If you pass basic integrity but not CTS, it means that suhide is working but your custom rom does not use some stock rom props related to device identification, so Safetynet does not identify your device as certified by Google and fails.
[SuperSU] Locura18:
I'm glad it helped.
[SuperSU] DEVILOPS 007:
That didn't seem to be the case as I was already passing all the checks and tried downloading an app and all but nothing worked except clearing data and cache.
[SuperSU] GuardianUSMC:
I think you are somewhat missing my point but I still appreciate it. Thanks anyway.
[SuperSU] KaMyKaSii:
I mentioned some app like the Safetynet Helper Sample or Safetynet Test, not any app
[SuperSU] bggold:
Just flashed with no wipe on my pixel xl O official release and before I flashed supersu 2.82 sr3 and suhide v1.08 I ran the phone for a good hour and no issues. Just flashed supersu and suhide with modded twrp and phone started to lag a few mins after reboot and becomes unresponsive. I am going to uninstall suhide and see if issue persists. If it doesn't I will grab logcat and ps. Will report back.

Thanks
[SuperSU] KaMyKaSii:
Have you installed both in a single TWRP session? The instructions say you should install SuperSU in SBIN mode, boot on Android and then go back to TWRP and install suhide
[SuperSU] bggold:
Crud I knew I forgot something. Brain fart. Thanks
[SuperSU] DEVILOPS 007:
I know, I tried that. Only thing that solved it for me after trying lots of things is clearing the data.
[SuperSU] bggold:
Well that wasn't the fix. I ended up clearing supersu and letting all the apps re authentic again. Test device has been stable for the past 3 hours. The issue would occur right away.

Hope this helps others.
[SuperSU] pellajl:
Just installed suhide following the instructions to the letter.

All TWRP flashes were successful, however I can't find the suhide GUI anywhere.

What am I missing?
[SuperSU] Ch3vr0n:
Check your app drawer. It's an app like any other.

Sent from my Nexus 6P with Tapatalk
[SuperSU] pellajl:
That is the first place I looked!

I can only see the normal SuperSU app. What am I looking for? SuHide? If that is the case, it not there.

EDIT: suhide was not installing. I navigated to /sbin/supersu/suhide/ and found the .apk file and installed it.

Now it appears in the app drawer.
[SuperSU] jcmm11:
Between this post and the one in the SR3 thread I'm beginning to suspect that something isn't right about your suhide install. I'd try removing suhide, reboot at least once, then try installing it again. This time grab a log of the install and if it doesn't work again post the log. Chainfire is currently on vacation so I wouldn't expect to hear from him super quick.
[SuperSU] JimSmith94:
Sorry for the probably dumb question, but I'm back to SuperSU and SuHide after using Magisk for a while. I upgraded from 7.1.2 to 8 release version with flash-all without the '-w', followed the instructions to install SuperSUConfig, SuperSU, and SuHide, and everything showed as rooted in SuHide. Because of this I didn't have to grant access on an app by app basis as before. I did have to remove root access for the few apps that didn't work with it.

How do you clear SuperSU? It seems to be working fine but I don't see it listed in either my app folder or in Settings-> Apps. If that is by design, I'm fine with that, but I'm pretty sure I used to be able to open SuperSU to see the apps that had root access, revoke access, etc.
[SuperSU] GuardianUSMC:
I believe this has to do with an option that provides hiding SuperSU from the "apps", so in that regard, I think flipping that option off would allow you to see the SuperSU directly on the app drawer. I could be wrong but that was my understanding.
[SuperSU] JimSmith94:
I think I remember seeing that option when I used SuperSU before. I fastboot booted into TWRP and ran SuperSuConfig again, but didn't see that as an option, and of course I can't toggle it from inside of SuperSU, since I can't see it to open it in the first place.
[SuperSU] jcmm11:
Since you're running stock she moment it won't be in settings. Can you see suhide in the app folder? If not I would imagine you toggled hide mode (Volume up/down 3 times within 3 seconds) in which case repeat the process to show both suhide and SuperSU.

If suhide is visible but SuperSU isn't them it's possible that the apk never got installed for some reason. This assumes that SuperSU has never been visible since you installed it. You can extract the apk from the SuperSU zip file, common folder, and sideload it.
[SuperSU] GuardianUSMC:
I am sorry I wasn't clear, I meant in the Suhide interface.
[SuperSU] JimSmith94:
Thanks!!! I extracted and installed the APK and I can finally see and open SuperSU! Now I'm not so sure I like it though. Before, all apps defaulted to having superuser rights (from SuHide I think). Now I have to go back and grant them access one-by-one again.
[SuperSU] jcmm11:
Nah they defaulted because you had no su manager installed so anything and everything that asked for root got it.
[SuperSU] JimSmith94:
I guess that makes sense, but this could have been a real problem if I had some malware on my phone that got root before I installed the APK!

As a retired old school programmer, I would say that this is a very serious bug! Maybe there should be a check for SuperSU being installed correctly before SuHide gets installed.
[SuperSU] Charles IV:
From looking through the thread, it looks like this passes safety net on some custom roms, but not others.

Generally the reason for this is referred to as 'the prop's'.

Does LineageOS generally pass, and as I am compiling it myself, is there a way I can make it pass? (e.g. making the system.prop the same as the stock one)

On a side note, I was wondering if these apps could use root to protect themselves, or is this not possible.
[SuperSU] KaMyKaSii:
There is a module for Magisk that focuses on pass Safetynet and this includes custom roms, you could take a look at the content. I believe the props needed to pass the CTS are those related to the fingerprint. The dangerous props I think suhide already hides them by default

https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431/post73432221

Sorry but I did not understand what you mean
[SuperSU] Charles IV:
Thanks.

Also what I meant was if it was possible for apps that needed to be secure (like banking apps) to use root to protect themselves from malicious apps. I'm not sure how it could be done though.
[SuperSU] defens23:
I'm rooted and on 7.1.2. Not running any custom ROMs. Do I need to do a dirty flash and reinstall the July factory image and TWRP before I put suhide on my phone or can I just boot into TWRP and follow the instructions to install suhide?
[SuperSU] ipdev:
[MENTION=4453526]defens23[/MENTION] What device and current root?

N2G48C (7.1.2 Aug. 2017) was working fine on my n5x. I was even able to download and updated to OPR6 OTA. Still seems to be working so far.

Nexus 5X (bullhead)

- N2G48C (7.1.2 Aug. 2017)

- SuperSU beta in SBIN

- suhide-lite (Not at all configured)

Now :

- OPR6 - OTA (8.0.0)

- SuperSU beta in SBIN

- suhide-lite (A little configured)
[SuperSU] defens23:
Sorry. Verizon Pixel XL. SU 2.79 SR3.
[SuperSU] ipdev:
[MENTION=4453526]defens23[/MENTION] Sorry, I don't have a Pixel yet, so I can not comment for sure on it.

Hopefully someone who does will chime in. :)
[SuperSU] bggold:
You.need to be running su 2.82 Sr3.
[SuperSU] gverma1:
Download opr6 (Oreo 8.00) factory image.

Modify flashall.bat to remove -w flag.

Update this in fastboot.

Phone will reboot on its own. This first reboot will take some time.

Transfer supersu2.82sr3 and suhide1.08 to phone.

Put phone in bootloader mode.

Use modified twrp to fastboot boot into twrp.

Flash supersu2.82sr3 in Twrp. Since Oreo 8.00 ensures SuperSU is installed in SBIN mode so no extra steps required before flashing SuperSU.

Reboot phone - will bootloop a couple of times but will eventually boot up.

Put phone in bootloader mode.

Use modified twrp to fastboot boot into twrp.

Flash suhide1.08 in Twrp.

Reboot phone.

Done.

All your previous apps and settings will be retained. However, I still back up everything before updating- just in case!!!
[SuperSU] Sojourner353:
Hi all,

Can someone please have a look at my recovery log to see why I cannot install SuperSU in SBIN mode?

I first ran the config zip selecting SBIN leaving all other options on the following pages to let SuperSU decide then I flash 2.82 SR3 but it fails.

So far have tried different ROM's and Kernel's but get the same result every time, I'm using a Note 4 SM-N910U.

Thanks for the help.
[SuperSU] Ch3vr0n:
Simple, you didn't read the first post.

Your device:

o.build.description=omni_treltexx-eng

5.1.1 LYZ28J
[SuperSU] Sojourner353:
Thanks for the fast reply [MENTION=1754043]Ch3vr0n[/MENTION], I have read the first post and thought i met the requirements, not sure why its saying 5.1.1 when I'm on a 6.0.1 ROM.
[SuperSU] twistedumbrella:
Install Magisk. Don't waste your time making things overly complicated by trying to use a solution only intended as a last resort when an easier one exists. It is fully working on that device, along with systemless Xposed (toggled off to pass SafetyNET).

TL;DR. It will never be completely beyond reach because the second it is, so are those sales numbers they need.
[SuperSU] Ch3vr0n:
Overly complicate? Hardly, please go promote magisk and Xposed somewhere else.

Sent from my Nexus 6P with Tapatalk
[SuperSU] GopalKaul:
I agree. thanks
[SuperSU] defens23:
Thanks. I've downloaded that version to my phone already.
[SuperSU] defens23:
I've installed 8.0. Do you have the link to the modified twrp? I saw it somewhere in one of these threads and don't remember where I saw it.

Edit:

I believe I found it. Can someone confirm that this is the correct TWRP to use?

https://xdaforums.com/pixel/development/mod-twrp-recovery-pixel-android-o-dp4-t3651896
[SuperSU] gverma1:
This is correct. Developer is gubacsek.
[SuperSU] DEVILOPS 007:
I've got a weird issue. Suhide isn't passing safety net anymore for me but android pay works and Netflix shows in the play store but the play store is uncertified. This happened after I dirty flashed to get out a bootloop I caused by messing with the system and won't go away even after clearing data for the play store and multiple reboots. I've also tried flashing suhide a second time. Any ideas as I'm really stuck, maybe flash SuperSU again? Please help, thanks.
[SuperSU] defens23:
Thank you.

---------- Post added at 10:36 PM ---------- Previous post was at 10:07 PM ----------

Up and running with no issues so far. Made sure to hide playstore in SU hide and can get Netflix now. Trying to get Directv Now to work.
[SuperSU] osm0sis:
Not necessary to block Play Store, it uses the SafetyNet status to determine whether it's "Certified" or not. You may just have to wait several days for it to refresh that check, or hurry it along by clearing Play Store data.
[SuperSU] DEVILOPS 007:
While you're around do you have any idea what could possibly be causing my issue? Thanks
[SuperSU] osm0sis:
Android pay working suggests SafetyNet is passing just fine. Maybe try a different checker? I've always used the SafetyNet Helper Sample one. For Play Store I had to clear data on it a couple of times before it worked right.
[SuperSU] DEVILOPS 007:
I tried clearing data and used the same app. Play store shows uncertified but apps like Netflix still show. I have no clue what is going on.
[SuperSU] defens23:
This noob thanks you and everyone else who helps me out. I will delete the Play Store data in Titanium.
[SuperSU] Sojourner353:
I was using Magisk but i also use Xposed and Apps2SD and once Apps2SD is setup it breaks Xposed so that's the reason I want to use SuperSU.

I'm using Rootcloak to hide my apps that detect root but wanted to try this.
[SuperSU] ozgrcvdr:
Huge thanks
[SuperSU] Jnthnjns:
I keep trying to install the final suhide zip, and I keep getting "Fatal error: Super SU image found at /data/su/img". Then if I delete this file it says I'm not rooted. Any help appreciated
[SuperSU] Ch3vr0n:
read the first post again. u need SR3 in sbin mode
[SuperSU] DEVILOPS 007:
I have no clue what is going on but right now I am not passing safetynet or anything and android pay and all that isn't working now. I installed SuperSU and and suhide with no error so could it be because Google possibly updated their safetynet [MENTION=631273]Chainfire[/MENTION]?
[SuperSU] NLBeev:
Just checking my Nexus 6 with rootswitch installed.

Root disabled - Safetynet passed.
[SuperSU] DEVILOPS 007:
I'm not using rootswitch currently as I was hoping that suhide would work for me. Good to hear that rootswitch is still an option. Thanks.
[SuperSU] twistedumbrella:
Not sure if you wanted Xposed to be functional, but this specifically states it is incompatible.

In Magisk, you would check the box for the app under the Magisk Hide tab. No Rootcloak necessary.
[SuperSU] jekyll530:
SuperSU 2.82 SR3 + suhide-lite 1.08, SafetyNet passed just few seconds ago.

OnePlus 5 with stock OxygenOS 4.5.8 (rooted, of course).
[SuperSU] shaggyskunk:
Did you use the Aroma installer for SuperSU v2.82 SR3?

From Down the Rabbit Hole by:

My SM-G930W8 ??
[SuperSU] jekyll530:
I tried it once and succeeded, but I didn't use Aroma the last time I flashed SuperSU.
[SuperSU] Syoenth:
do you have alink to download the latest version of rootswitch? I tried 1.3.3.2 this but it didn't disabled root
[SuperSU] AbiDez:
That's the wrong thread...

I'll send you a pm...

CarHDRom V.30.3-C by Carotix S6edge
[SuperSU] NLBeev:
On my N6, only version 1.3.3.16
[SuperSU] Alxoom33:
Why would you bother with Root Switch when Suhide 1.08 works so well?
[SuperSU] KaMyKaSii:
I just want to warn you that I installed the official Xposed v86 after installing suhide and both are working together, unlike the old suhide that caused bootloop. Of course it is not possible to pass Safetynet with Xposed installed on the /system but it is already a start
[SuperSU] NLBeev:
I'm using SUhide.

Just helping someone.
[SuperSU] osm0sis:
Hey, it's good to have a fallback for when The Google Strikes Back. ;)
[SuperSU] Alxoom33:
Yes, I understand. But Rootswitch never works well for me. I also don't like all of the files it leaves behind. I don't trust the source, I guess.
[SuperSU] NLBeev:
We have a partnership with Calimero....
[SuperSU] 000zui:
Here, from my htc 10 works flawlessly, even on a custom rom. Safetynet passed with SuperSU SR3 & suhide 1,08. Thanks [MENTION=631273]Chainfire[/MENTION] as always.. Your works are still awesome, even after years.
[SuperSU] snovvman:
Are you saying that, as [MENTION=631273]Chainfire[/MENTION] ages, you expected him to become less awesome? Are you saying that older people are less awesome than younger?
[SuperSU] Alxoom33:
Lol! I don't know Calimero, but the fact that rootswich is posted only on a Chinese blog/website dosn't give me the warm and fuzzies. Can you vouch for rootswich?
[SuperSU] osm0sis:
I haven't packet sniffed it, but I've looked into all the scripts and they're all well written, and on the up-and-up.

It's not a Chinese blog/website, it's the Chinese language version of the official ASUS Zentalk forums, which the long-standing xda developer who wrote Root Switch, [MENTION=1813976]shakalaca[/MENTION], is more active on (possibly a moderator if it translated correctly). There is also an English language version of both the forums and the Root Switch thread, but it's just not as up-to-date since the Chinese forums there are more active, and the developer is Chinese so possibly more comfortable in that language.

shakalaca has done a lot of great work for the ASUS community in general over the years - the project I'm most familiar with being the reverse-engineering of the Intel $OS$ boot.img format that was mostly used on older x86 ASUS devices - I can't imagine him developing ulterior motives at this point.

Just because a person is Chinese doesn't make them untrustworthy. Let's all please take a minute and try not to be xenophobes.

/OT ;)

Edit: Turns out the developer is actually Taiwanese, hopefully that doesn't undermine my point.
[SuperSU] GuardianUSMC:
I took that to clearly mean that after years of doing this and despite all the challenges, the quality of his work and dedication hasn't suffered. There is no reference to age or who is better, older or younger, you are reading a possible personal bias into it or possibly a language barrier. :eek:
[SuperSU] Alxoom33:
Thank you for your detailed explanation [MENTION=1143630]osmosis[/MENTION]. My concern wasn't about the nationality of the developer, I work with many brilliant Chinese (and Taiwanese) nationals who are well respected and honerable. It was the blog/thread source, with which I had no familiarity or confidence. Based on your explanation, I feel much more comfortable with Root Switch and its developer than I had before. Thank you very much!
[SuperSU] NLBeev:
Calimero is a metaphor. Google is big Calimero is a little bird. What ever happens people keep loving him.

https://www.likefigures.com/calimero/
[SuperSU] Alxoom33:
LOL! Thanks, he is a cute little guy, shell, pack and all!
[SuperSU] 000zui:
[OT]

Spoiler content hidden.

TL;DR

Exactly the opposite.

[/OT]

Anyway, this project really suited my needs, I can finally use an app I couldn't before.
[SuperSU] snovvman:
Nice retort :good: I was bored this afternoon and tried to stir up trouble :silly:
[SuperSU] DEVILOPS 007:
I'm finally passing safety net out of nowhere but am still uncertified in the play store for some reason. I did clear the data of the play store. Is there another way or should I just assume it will become certified itself.
[SuperSU] osm0sis:
Clear the data a couple more times - mine didn't work the first time - and/or wait.
[SuperSU] DEVILOPS 007:
Okay, so now I'm not even passing safetynet at all! Why me!? Google is straight up trolling me!
[SuperSU] KaMyKaSii:
In addition to the PlayStore also try wiping Google Play Services data
[SuperSU] tHset-01:
Cant pass safetynet for basic integrity and cts profile match, having pure nexus on nexus 5, franco kernel 107, latest supersu and suhide.
[SuperSU] Alxoom33:
I'm not having any problems with Stock Android 7.1.1 August patch. It is either your "Pure Nexus" rom or the Franco kernel. Are you running Xposed?
[SuperSU] jcmm11:
When you say latest SuperSU you do mean 2.82-SR3, correct? Do you have it installed in SBIN mode?
[SuperSU] Droidphilev:
Hi all,

On my nexus 6 SuHide is working just fine. I use the aroma installer to force SuperSU into sbin mode. However... on another device i own (Moto G4 plus codename Athene) i can do whatever i want, flashing SuHide ends with "Fatal error: SuperSU image found at /data/su.img SuperSU must be installed in BINDSBIN mode" and error code 1. I tried different roms, kernels, selinux permissive, selinux enforcing etc etc etc nothing seems to work. Anyone have an idea please?

grts

Phil
[SuperSU] pendor24:
https://plus.google.com/+Chainfire/posts/XikxTkhHpiG

can be here
[SuperSU] Droidphilev:
Will take a read, thanks.
[SuperSU] Droidphilev:
Hi,

Oh well... what i did on this device was:

flash rom

flash unsu

flash ex kernel

did the echo command (tried both manual and the aroma installer)

flashed SuperSu

boot

flash SuHide which failed everytime

After searching it seems that flashing the kernel unmounted /data in twrp. Because of this SuperSU simply cannot read the .supersu file eventhough it's there.

Sorry for wasting your time :-|
[SuperSU] ZarltanXDA:
Tried installing this step by step but it is coming up with the following fatal error "/system/xbin/su" then it asks if I have the latest SuperSU installed in SBIN mode which I have as I flashed the Config selected systemless O+ and then flashed the latest SR3 2.82 Super SU

My system:

Lineage OS 14.1

I know it's not been tested on Lineage but is that error a Lineage problem or something different?
[SuperSU] jcmm11:
I believe that Lineage has a built-in root and that's what's causing the problem. You'll need to remove the built-in one before installing SuperSU.

Hopefully someone who's actually done this will come along with better advice (I've never run Lineage). If I'm wrong about built-in root I'm sure someone will let me know ?
[SuperSU] ipdev:
Official lineage builds are not rooted by default.

(They offer a su-addon that can be flashed separately.)

Unofficial builds may have root baked in for one reason or another.

Edit :

Just tested on Nexus 5. Clean install, seems to be working fine.

lineage-14.1-20170829-nightly-hammerhead-signed.

SR3-SuperSU-v2.82-SR3-20170813133244. (sbin mode)

UPDATE-suhide-v1.08-20170815171034.
[SuperSU] PuppetOfFate:
So I've tried a few times to get this to work and it can't install SUhide. I get the configuration and SuperSU installed but not SUhide. I already had SuperSU installed previously I tried to do this but I have tried reflashing. Any ideas?
[SuperSU] ipdev:
[MENTION=8522820]ZarltanXDA[/MENTION]

A week or so ago I ran into a similar problem on a lineage 13 port.

I disabled the built-in root and flashed an unsu, SuperSU (sbin) and suhide-lite. suhide failed.

Rebooted into rom and checked, SuperSU was working and installed in /sbin. Built-in root was not available but there were some files left behind, including /system/xbin/su.

(I was able to delete them with a root file manager.)

Rebooted into twrp and flashed suhide-lite without a problem.

- Just be careful and make sure SuperSU is working correctly before you start deleting su files. -