yashsingh1/xdaforums huggingface dataset:
[SuperSU] smitharro:
About the SuperSU 2.61: it's working fine so far. But it's clearly work in progress. It's not finished! Keep that in mind before complaining about incompatible apps, bootloops and draining batteries!

Unfortunately it's all I have for Android 6.0.1/CM13 (besides the CM13 built-in root) since SuperSU 2.52 is giving me bootloops (yes, now I'm complaining myself...).

Positive: so far all my root apps seem to work and I got rid of the ugly # in my statusbar of the built-in CM13 root.

Negative: it's systemless root. It patches my boot image. For me the classical root would do just fine because Android Pay is not supported for my device (no NFC), nor for my country.

Written with my XT1068 using Tapatalk on CM13
[SuperSU] Chainfire:
Seriously?

http://xdaforums.com/showthread.php?p=64224716#post64224716
[SuperSU] Chainfire:
The upcoming 2.62 will wipe 2.52, but if you want easy OTA in the future, reflashing stock /system is advised (and the only 'supported' upgrade path)

You think wrong.

Don't project your own preferred way of working on a few dozen million users, you will come up short.

2.62 will have a possible work-around for your problem. When it's out (probably some time today), try again, and let me know if the issue was fixed.

The "Full Unroot" option in SuperSU settings will automatically reflash boot. And there's more stuff coming to make OTAs easier. Surprise, not everything can be done in one day. And again, systemless root does not prevent you from modifying system.

Actually it should have removed the old ones automatically. I changed the script from uncompressed backups to compressed backups at some point and forgot to fix up the cleanup part as well. This will be fixed in 2.62. You can figure out which one is the current correct backup by looking at the end of /init.rc, or when 2.62 is out, flash back stock boot image before applying the new ZIP, and the old ones will be removed automatically.

Exactly this.

Root Explorer, like many other apps, will need to be updated.

It's weird how everyone expects everything to just work perfectly out of the box every major Android update even though they change half the system around.
[SuperSU] mickrussom:
Guess I wish I hadnt paid. To take the side of a company weaponizing open source against the user is just wrong.
[SuperSU] egingell:
You paid Chainfire. You didn't pay Google... Although, they took their cut... unless you paid via PayPal or Amazon.

Chainfire must comply with Google's security measures. It would be very easy for them to take away any root prospects.

P.S. If you are so unhappy with Google's policies, I hear Apple makes similar devices.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] bigknowz:
Magisk

Anyone try Magisk? http://xdaforums.com/android/software/mod-magisk-v1-universal-systemless-t3432382
[SuperSU] SpasilliumNexus:
Did you look at the chart in that thread you linked? Not to mention everything is explained there, along with a different version of SuperSU for that thing.
[SuperSU] mickrussom:
Next step is going to be removing all apps that have anything to do with root from the appstore. Next will be to have something worse than selinux forcing the signing of apps to run. Licking Google's boots now will ensure we will all be out of our devices very very soon. The world is shrinking fast. Custom ROMs out, Samsung at best xposed and root out on stock android. And all of this under the guise of security which is garbage. Complying with Google's totalitarianism to live another day - it wont change the eventual outcome. They are wrong and they are the enemy and they must be resisted.
[SuperSU] ChromeJob:
Some of these gripes are amazing.

You paid Chainfire to a) donate for development work you otherwise got for free, and b) to unlock extra features. You got that, right? Fair transaction IMHO.

Google is ensuring that a feature with high expectation of privacy and security, for users' financial info, only works on stock unrooted devices. Devices with the security model modified by the user, are denied that feature. Seems a fair request to make in order for banks to get on board with AP. Yes, it's a disappointment that it worked before, and recently, but the loophole is getting plugged. Boo-hoo.

You're still free to do one or the other, there are even workarounds for the bleeding edge types.
[SuperSU] royorbs3:
I dl ap from apkmirror. use root cloak from xposed. Still works for me
[SuperSU] bunklung:
Has anyone figured what exactly is the detection method? I renamed the su binary and that didn't fool the Safety Net check.
[SuperSU] ldubs:
Root cloak from exposed still working? Trying to figure out an easy method to use it without jumping through hoops, rebooting my phone three times, saying a couple of prayers, and then having my wife scoff at me while her fricking Apple Pay works just fine... I'm wondering if temp unrooting would work, I don't believe I modified /system in any other way.
[SuperSU] a1exus:
I tried to use Android pay, but it didn't work for me( I'm on latest August patch on 6p
[SuperSU] ldubs:
Need more info - what does it mean that you tried to use it? Rooted? Unrooted? System modified or not? Things you've tried as work-arounds?
[SuperSU] a1exus:
I went to Starbucks, tried to pay with Android pay, didn't go through. I'm root'ed, AP used to work, I yet to go to another location to try it again and see.. I don't know what work around to try(
[SuperSU] Alxoom33:
You need another way.[emoji6]
[SuperSU] bobby janow:
Agree. Fail safe way, unroot and reboot works every time. You need root again then cf-auto-root if you're on stock recovery or flash SuperSU if you're lucky enough to have twrp working on your device. I've been finding I need root less and less but that's just me. I really just need it now for Titanium backup when I flash a new rom which is also less and less since being on N dp5. Ether that or simply stop toying with AP and pick your poison. Google has it figured out so stop lambasting them. They're just doing their job. You don't like it then see above. Pick what you want and stop complaining. As in life, you can't have your cake...
[SuperSU] photolarry:
As of the newest Play Services, you cannot be rooted. Period. Sadly this systemless workaround will no longer suffice. If you need root, you cannot have Android Pay any longer :( I am just as bummed. I removed root. The only thing I wanted to tweak was some kernel settings but no deal since Google really does not want you rooted. It is a security hole.
[SuperSU] Citizen_Snips:
Not specifically to you, but the last few posters in the thread as well..

I don't mean to hijack Chainfires thread, but I figure this is dedicated to AP & root so if anyone is interested, read on. If there's a problem, mods feel free to edit or remove the post.

You cannot have Android Pay and SuperSU, currently. There are others options.

See here.

That's the link to the systemless Xposed thread. If you download the Magisk v3 zip, the phh superuser v2 zip, w/ AP support from the thread I linked above & download the phh superuser app on the play store, then you can root and have Android Pay working. Transactions confirmed working as well. Basically, it unmounts root temporarily (no root apps will function during the time you set in the "Magisk Manager" app, default 5 mins) and during that time SafetyNet will pass and transactions will go through. Once the time limit is up, SafetyNet will fail as will AP, but root is active again. It works on the fly, no reboot needed. Also, if you download systemless Xposed from the thread, it will also work with Xposed installed and active without having to disable it either.

Read up on the linked Magisk thread to see how & why it works. It's linked in the thread I linked above.

Oh I can confirm it's working on Nexus 5 & Nexus 6P.

Edit: Some people seem to have issues using AP with Xposed, it seems. I used AP rooted with this method without Xposed and it worked. N5. YMMV.
[SuperSU] Alxoom33:
Works on the Nexus 6 without Xposed, just fine.
[SuperSU] photolarry:
Just my opinion.... But installing Xposed framework puts the phone at high risk and isn't recommended if you ask me. If you root and don't care about security, go right ahead. But you're opening up your system to hackers of you do what's suggested. The safety net has a purpose to protect against hacks.

---------- Post added at 07:51 PM ---------- Previous post was at 07:49 PM ----------

What version of Android? If you're on the most recent marshmallow, and play services, it shouldn't work. As I mentioned, is vulnerability in your system when root is applied. Up to you. If it doesn't pass safety net, then I'm not interested in by passing. Just my feeling on security.
[SuperSU] a1exus:
I use root only for BatterBatteryStats - maybe I should let it go already... I'm Nexus 6p: Android:6.0.1/MTC20F & GPS: 6.9.15.G-all [0]3104571 and I get "Android Pay can't be used" message(
[SuperSU] bobby janow:
You don't need root for BBS.
[SuperSU] Citizen_Snips:
Not for nothing, but you know root is also an exploit, which under the correct circumstances can be used to hack your device as well, right? You know that just root alone also fails SafetyNet? You also know that the Superuser method you're using now is closed source, correct? Who knows what's going on under the hood. Or do you not use root at all and just hang around this thread?

Now I'm not making accusations against Chainfire, he's one of the highest respected developers in the Android scene. It's just the principle of it. How do you say you shouldn't use 'X' since it's an open sourced security flaw which can be exploited, while you have no problem using 'Y' which is a closed source security flaw which can be exploited?

All I did was post a link to Systemless Xposed thread which links to the Magisk framework. You don't need Xposed to get AP working with root. Like I said, read the Magisk thread if you want to learn more about it.

As I stated earlier, while this is CFs thread, it's also about AP & Root. He said himself in the OP that he isn't going to fight SafetyNet and any versions on SuperSU which pass is a bug on their end, not a feature on his. So I posted for everyone who wanted both still and didn't seem to be in the loop. Thank you for your concern.
[SuperSU] egingell:
Its Play Store page says different.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] photolarry:
Dude I'm not some amateur. Obviously I'm aware of everything you've said and I'm not bashing chain fire. I'm saying that is unwise to root and delude yourself into thinking you aren't compromising safety and security of your device. If you wish to do that... Go ahead. He even said he's not intending to bypass security on AP and this thread was created because he doesn't want to address such an issue. He knows it's putting your device at risk.
[SuperSU] a1exus:
I believe you do (since marshmallow), otherwise you'll see very little stats.
[SuperSU] photolarry:
Play services have been updated recently say you cannot root and have AP function. It's big security risk. If you've not figured that out. Banks have been working with Google.
[SuperSU] NYLimited:
I guess we shall not tell all those Linux & and Unix & Solaris & BSD &.. users about this exploit in their OS. :)

I might call it trust or confidence based on long term experience. Considering that too many never look at source code and too many couldn’t read it anyway we might also call open source a bit of confidence. Lots of people use lots of software which us not open source.

Anyway, nothing against open source. It is a cool concept. But having open source does not invalidate other methods of publishing at all.
[SuperSU] egingell:
I was not talking about AP.

Sent from: SGS5 - MM 6.0.1 / SGS4 - LP 5.0.1
[SuperSU] ldeveraux:
Is there anything you DON'T have an opinion on?
[SuperSU] photolarry:
No moron. What an asinine thing to say. I gave advice and really don't care what you think. Please gtfa
[SuperSU] bobby janow:
Read the thread, specifically this post. I've been using it non-rooted for some time now with all stats available.

http://xdaforums.com/showpost.php?p=67441059&postcount=30633

---------- Post added at 08:19 AM ---------- Previous post was at 08:18 AM ----------

Been using it for some time now and I see all stats.
[SuperSU] a1exus:
awesome! thank you so much for that info! greatly appreciate it!
[SuperSU] bobby janow:
Android Pay coming to Chase on September 7th. You heard it here first.
[SuperSU] Empty Hand:
Nice job, you beat Android Police by 4 days.
[SuperSU] duy757254:
thanks
[SuperSU] Chainfire:
As you've said yourself: this is off-topic, and does not belong here. As such, I have removed the post.
[SuperSU] Chainfire:
suhide may work for some of you - http://xdaforums.com/apps/supersu/suhide-t3450396
[SuperSU] Pig Vomit:
Had I known you were working on suhide, I never would have posted that! Glad to see an alternative from you. :good:
[SuperSU] CSX321:
Tip for using Pay with Smart Lock (rooted or not, really):

I think this may vary by card, but with Smart Lock enabled and tied to my Wear watch, my credit card always prompts me to re-enter my unlock code after I tap the payment terminal. Then I have to tap a second time to actually pay.

Yesterday I realized that before making a payment, you can tap the "unlocked" icon before swiping it up, and you'll be prompted to enter your unlock code as if Smart Lock was not enabled. Then Pay doesn't prompt you to re-enter it, and you only need to tap once to pay.

This behavior is obvious in retrospect, but it hadn't occurred to me until yesterday.
[SuperSU] lexluthor:
I've got a Verizon LG G3 running stock ROM w/systemless root. I'm using SuperSU and I have TWRP installed. No xposed.

I really don't want to use xposed/magisk and I'm probably willing to lose root (would be nice if it was temporary vs permanent).

If I uncheck enable superuser in SuperSU and reboot, Android Pay still doesn't work.

So what exactly do I need to do in order to get Android Pay working?
[SuperSU] Pig Vomit:
You need to do a full removal (Settings, near the bottom), and restore original boot.
[SuperSU] lexluthor:
What do you mean by restore original boot exactly?

Sounds like if I do that, I'm never getting root back. I think to re-root my LG G3, I might have to go back to a way earlier OTA, root that and then get to current. That would be destructive and time-consuming to get back to where I am. Still might consider it though and just give up root forever.
[SuperSU] Pig Vomit:
You said you were willing to lose root in order to use Android Pay, and you didn't want to use Magisk.

Currently Magisk is the only way to have root and use AP until (unless?) Chainfire is able to update suhide. The only way to get AP working without Magisk is to completely unroot.

SuperSU will ask you if you want to restore original boot image when you do a complete removal. You can chose not to and see what happens.....but SafetyNet would likely fail as a result. I'm not running a custom ROM.....so when I unrooted prior to installing Magisk, I restored my boot image.
[SuperSU] lexluthor:
Yes, I possibly am, but the other questions are does "completely unroot" on my Verizon LG G3 mean that there's no easy way to get root back (like some sort of 1 click root on my current ROM, which I don't think is possible, but not sure) and how exactly do I completely unroot? I understand the SuperSU in unroot, but what other steps are going to be required?

The last thing I want to do is lose root with no easy way to get it back and not have Android Pay working. And, also I won't do this if it requires a full wipe. A restore is too much of a PITA for me usually.

Appreciate the responses.
[SuperSU] Pig Vomit:
Sorry, in the alcoholic haze I was posting under last night I may have posted with the foggy assumption that everybody has a Nexus and every root solution is SuperSU. Perhaps another G3 owner could help, but they would likely need to know what ROM and which one-click root solution you are using.

BTW.....I will never buy another non-Nexus (Pixel?) phone again. And, of course, Verizon blows! Nexus makes life so much easier for modding phones.
[SuperSU] JedTech:
Are you posting from 2012? Nexus/Pixel is quickly becoming a locked down alternate to iPhone.
[SuperSU] Chainfire:
Please note that suhide has been updated to v0.51 - http://xdaforums.com/showpost.php?p=68747345&postcount=569
[SuperSU] benjiboythelad:
Has anyone ever looked at what safteynet is

Firstly I'm not after any android pay. I think it's unsafe and an easy way to spend someone else's cash

I'm overly irritated by the implementation of safteynet in every day apps. And games . Take pogo for instance . It's basicly been so lazy that rather than use find a solution to mock locations it's just implemented safteynet excluding the ever growing development community rather than devising how to make android pay work. I don't like that people are even thinking about this but each to there own.

Why not talk about the sorce code used in 3rd party apps to implement the cts check . I'm currently looking through pogo looking for a code line with cts api or safteynet. But I'm unable to locate it so if anyone knows what I should be looking for I can take the line of code out or render it useless. This might be possible for you're android pay. But as it's part of player services I would imagen you'd have to recompile android framework to remove all traces of safteynet api and cts api and any. JSON /.SNET files so have fun with that :) anyone with any ideas message me I do not wanna run magic system seamless or what ever
[SuperSU] ruifung:
Except you are missing the point that the whole SafetyNet API is so troublesome because it allows or server side validation.

If it was only a client side check it would have been circumvented by an exposed module long, long ago.
[SuperSU] Alxoom33:
AP, no problems on N6 with SuHide 0.53 Android 7.0/
[SuperSU] clfrog:
Can someone tell me what exactly the new Safetynet is detecting??

im on Resurrection Remix Marshmallow for galaxy Note 3 (hlte)

fully unrooted, no xposed

still not passing safetynet check...
[SuperSU] higedamc:
I think its because you not using Stock ROM.
[SuperSU] cmh714:
.55 is broke after yesterdays updates...
[SuperSU] bxlegend:
You have to delete the su bin in both /system/bin & /system/xbin. You can do this in TWRP using the file manager after mounting the system partition.
[SuperSU] Alxoom33:
[MENTION=631273]Chainfire[/MENTION] is not sure either. So, probably not :)
[SuperSU] clfrog:
I figured it out, sort of...

something about Resurrection Remix a CM13 mod is triggering safetynet.

i flashed official CM12.1 on my note 3 and now safetynet passes and I am running pogo

(deleted SU from bin and xbin for CM12.1)

i guess that is the temporary fix? I guess i wont be using other roms other than official CM now...

im not sure what this means but im also hearing AOSP roms are triggering Safetynet, dunno what AOSP means.
[SuperSU] frecciak:
try to flash boot...i solved in this way whit my p8
[SuperSU] NoSpax:
Just a simple question: Can SafetyNet detect root, if the binary isn't called "su"?

Allow me to throw an idea into the room.

Lets say, SuperSU doesn't install a "su"-binary but more like "sxu22".

What if SuperSU keeps a list of all "new" binaries.

If you use an app, which requires root - it has to ask SuperSU for it, SuperSU gives the name to the app.

The app now has to use the renamed su, which asks SuperSU again to aquire root.

It's an idea, but this change will (negatively) impact the whole scene and all apps dependant on "su" as a file. :/
[SuperSU] baniaczek:
I've got strange effect. Just for your info

Both SafetyNet and PokemonGo failed

After full unroot and unmagisk: SafetyNet still fails, but PokemonGo works without any issues.
[SuperSU] DROITURK182:
Has anybody figured out what safety net is checking for, because I'm not rooted but on a custom ROM and it's failing the checks after Android pay got updated the other day?
[SuperSU] Captain_Throwback:
Is your ROM SELinux in permissive mode? That will trip SafetyNet.
[SuperSU] Amiganaut:
SafetyNet checks for many things, but SeLinux permissive/enforcing was what was doing it for me. Your kernel needs to be set to enforcing. http://xdaforums.com/showpost.php?p=69120611&postcount=733
[SuperSU] DROITURK182:
I'm on ICE rom sense 8.1.0 and I think the kernel is set to permissive, how do I set it to enforcing? Thanks for the reply Cap..
[SuperSU] bbrabham:
The "bootloop" you encountered was your device attempting to re-encrypt, had you waited, it would have finished boot and upgraded apps, and wouldn't give you the corruption notification at start up.
[SuperSU] photolarry:
I am not even bloody rooted and using a custom kernel and all of a sudden this Android frikken Pay is failing and so is Safetynet. HELP! I do not get why if I fully unroot and flashed boot/kernel and system stock images why would AP fail still? Something in /data ???
[SuperSU] Amiganaut:
I think Safetynet got another update today. I've been getting intermittent fails since this morning, and I have not changed a thing on my phone. Sometimes it does pass, sometimes not. Usually when it passes for me is right after I've rebooted my phone. If I wait a few minutes, it fails again. I'm suspecting I have some process that starts up soon after boot that causes it to fail. Just a hunch at this point, I'll fiddle around some more and see what I can come up with. I've unrooted on a custom ROM with an SElinux enforcing kernel.
[SuperSU] photolarry:
Let us know

Ya I thought I had done something and was frustrated because I unrooted specifically to get AP to work. And now fk it, failing, I am going to root again until they quit the BS.
[SuperSU] GatorsUF:
It appears safetynet now blocks unlocked bootloaders in general...

I have completely wiped my phone and flashed stock boot images:

Bootloader locked: Safetynet helper pass!

Bootloader unlocked: Safetynet helper fail - CTS Profile Match = fail

I'm on a Nexus 6P so it may be different for other phones...
[SuperSU] adrman:
I believe you're correct. I just checked my wife's nexus 6. It's completely stock and had never been rooted, just unlocked bootloader. AP is now unable to add a card.
[SuperSU] SamuelBegui:
Well if that's the case, I have a OnePlus 3 and need my unlocked bootloader lol.
[SuperSU] Powereh:
Can confirm I'm completely stock with an unlocked bootloader, Used it last night but today it trips.
[SuperSU] photolarry:
This is stupid. Now my bootloader must be locked too? That's just idiotic. They won't allow root and now this. Screw this. I'm not going to lock my bootloader. They'd told me they would loosen these root restraints few months after it was released. Not continue making it harder to root. It was a deal breaker since I could use custom kernel and not be rooted. But if that's not enough....I'll use my card and frikk them
[SuperSU] Alex_Lema:
Same here. Nexus 6P, full stock with unlocked bootloader, Safetynet validation fails ("CTS profile match false").
[SuperSU] HpNoTiQ:
We need an app to lock/unlock bootloader on demand (like this one on my old nexus5!!)

https://play.google.com/store/apps/details?id=net.segv11.bootunlocker
[SuperSU] dratsablive:
Doesn't locking/unlocking the bootloader wipe the phone?
[SuperSU] JsChiSurf:
Wow, I am in complete disbelief at the abrupt and complete and utter abandonment of the developer community by Google. The developer community, IMHO, has played a significant role in evolving Android into what it is today.

In a desire to use Android Pay, and "play by the rules", I finally relented about a month ago and un-rooted my device, while still having the bootloader unlocked so as to run a custom kernel. Now, apparently, even that is not good enough, without so much as a warning or a heads up that the rules have changed.

With such a locked ecosystem, at this point, what's the difference between this and being an iSheep? Hard to tell anymore...
[SuperSU] fOmey:
Amen, I'm very surprised they have taken this route..