yashsingh1/xdaforums huggingface dataset:
[SuperSU] bobby janow:
Android Pay and Apple Pay are not only convenient to use, take less time at the register than waiting for the chip reader to spit out that you can finally remove your card, is more secure due to the virtual number assigned to your credit card, and much simpler for a woman to use rather than opening a purse (security breach right there) finding her wallet, searching for the right card and then all in reverse again. Pull the phone out of the pocket tap it once and you're done.

As for dependent on an electronic current to properly function, doesn't the terminal and the store depend on that as well? I'm not sure where you live but people on a queue are generally forgiving if there is an issue with a card or device while trying to pay. The only actual issue, which is addressed in this thread, is getting root and Android Pay to work simultaneously. Not the value or convenience of the method of payment. I'm not sure why you feel we need to be pitied because we want to use mobile payment methods. I actually think it's going to expand rather than decline in use. Mobile devices are ubiquitous and in people's hands more than you might want to admit. Take a look at people standing in line waiting to pay or take care of some business. I would suspect most of them have a phone in their hands. And if they don't they are easier to retrieve than a wallet or credit card.

But I guess time will tell. I certainly appreciate the efforts of the OP and will continue to use both AP and root if possible.
[SuperSU] Gamu79:
Thanks a lot chainfire

Working on I9505 !!!!
[SuperSU] YaKillaCJ:
This is exactly why I'm reading thru all this. Thanks for testing it. I have a Redmi Note 3 Pro as well. I heard it works good on CM13 and I'm guessing it'll work fine on RR as well. But I don't wanna give up Miui 8, I tried it daily for a week and it has won me over.
[SuperSU] ianmacd:
There's no card removal at a contactless terminal. You hold your NFC-equipped debit card in front of the reader and your part of the transaction is then complete. It's no different than Android Pay in this regard, because that, too, relies on an NFC chip.

Why would it be any easier for a woman to find a phone in her bag than a debit card in the same bag? And why do you consider opening a purse at the cash register of a shop to be a security breach? If a woman isn't safe with an open purse at the till of a shop, she's probably not safe brandishing a smartphone either. Most smartphones are worth a multiple of the contents of the average purse nowadays; and that was true even before we became an almost cashless society.

Yes, but the two don't depend on the same power source. The shop is much less likely to suffer a power cut than a mobile phone user is to run out of juice on any given day; or to suffer some other hardware issue; or a software failure.

Where I live, we aren't used to tolerating payment failure. We use only cash and cards. Cash can't fail, and cards almost never do. NFC chips are very robust.

When we're held up in the supermarket queue, it's usually because someone is digging in their purse for the right coins, but even that is becoming a thing of the past as people move away from cash altogether. There are already some shops that no longer even accept cash as payment.

Because better (i.e. cheaper and more robust) payment technology predates the use of smartphones, and people should want to use the best technologies.

Championing Android Pay over superior alternatives is like advocating the use of the fax machine over e-mail. It just doesn't make sense. Just because it runs on a smartphone -- and we all love smartphones -- doesn't mean it's inherently better.

Most people queuing in a shop in this country are not holding a phone in their hands. Why would they? They've just been using those same hands to hold and load their shopping basket, so their phone is either in their bag or a pocket (usually the bag, because a pocket is less secure). In either case, it would need to be retrieved in order to pay with it, and in that regard is no different from a debit card. Even if someone stores their phone in a more readily accessible location, that's not an an inherent quality of the phone; it's a question of efficiently organising one's belongings.
[SuperSU] grep_i:
Magisk is required for the version of Xposed you are using [MENTION=4470081]topjohnwu[/MENTION] v86.6

Magisk is not required for the Xposed version I use [MENTION=2476451]romracer[/MENTION] v86.1

If you think you feel more comfortable with [MENTION=4470081]topjohnwu[/MENTION] Xposed than you can use his version v86.2 which also does not need Magisk

I hope I made this clear to you now.
[SuperSU] AleStifini:
Hi guys!

I have P9 Plus

Android 6.0 (EMUI 4.1)

Stock ROM

Rooted with SuperSU 2.78 SR1

I flashed SuHide 0.54 but it lags extremely my smartphone. I don't know why...

How I can resolve this issue, please? Thanks!
[SuperSU] jordiz86:
Thanks a lot, worked perfectly on my s7 edge! :)

Inviato dal mio SM-N930F utilizzando Tapatalk
[SuperSU] Shack70:
Got it fixed after traveling and I assume am on a different tower. Dloaded supersu, installed and all is great. Thanks [MENTION=631273]Chainfire[/MENTION]!
[SuperSU] tejaskadaskar:
Guys I am new to rooting...can anyone plz tell me how flash 2.78sR1 in systemless mode.I am on MM ROM.

Thank you.
[SuperSU] ManikandanGuru:
Excellent. Pokemon Go is working perfect. Anyway I am not going to play that, at least it is not yet released in my country.
[SuperSU] pkelly517:
We get it. You like contactless terminals.

Could you take that conversation to a contactless terminal thread?

Thanks.
[SuperSU] Rhoban:
Boot into TWRP recovery, go to terminal emulator and type

echo "SYSTEMLESS=true"> /data/.supersu

Then flash the su zip.

It should flash in systemless mode.
[SuperSU] krzychunh:
Are you also in the installation, the phone works very slowly hangs? Mate 8
[SuperSU] stanxx:
Tested with Note 4 (N910c) (6.0.1)

- (Odin) Flash stock rom

- Boot to system

- (Odin) Flash TWRP v3.0.2

- (TWRP) Flash SR1-SuperSU-v2.78-SR1-20160915123031

- (TWRP) Flash suhide-v0.54.zip

- Boot to system

- Update google app from play store

- TEST root + safetynet >>>>>>>>>>>>>>>>>>> OK

- (TWRP) Flash Magisk-v7.zip

- Boot to system

- Install MagiskManager-v2.0.apk

- TEST root + safetynet >>>>>>>>>>>>>>>>>>> OK

- Install XposedInstaller_by_dvdandroid.apk

- Open xposed installer and choose to download & install systemless xposed v86.6

- Boot to system

- Optimizing apps... in the end it auto-reboot...

- Bootloop :(

- (TWRP) Flash suhide-rm-v0.51.zip to remove suhide

- Boot to system >>> OK

- TEST root + safetynet >>>>>>>>>>>>>>>>>>> safetynet FAIL

- (TWRP) Flash suhide-v0.54.zip

- Boot to system

- Optimizing apps... in the end it auto-reboot...

- Bootloop :(

My phone model only fit for either one of suhide or xposed, but not both :confused::confused:

I really wish to have both.
[MENTION=631273]Chainfire[/MENTION] would you please be so kind to help, thanks a mil in advance.
[SuperSU] KaMyKaSii:
I may be wrong but I believe that for Note line you must use Xposed Alt Version
[SuperSU] iFedix:
Mee too but today I installed Cyanogenmod 13... with no success.. cause fingerprint sensor doesn't want to work on my rn3p! :crying: so, [MENTION=260994]SolarWarez[/MENTION], you are my last hope! Rolling back to MIUI 8!
[SuperSU] libak24:
xposed keep telling me i should update. can i do that with no issues? if it's risky, is there a way to keep it stop telling me that?
[SuperSU] stanxx:
So far as I'm concerned, please check below, from Wanam's post.

ARM means the devices that are running arm32 operating system (Galaxy S5, Note4,...)

ARM64 means the devices that are running arm64 operating system (Galaxy S7/S6, Note5 and all their variants...)

SDK22 means Android Lollipop 5.1.x

SDK23 means Android Marshmallow 6.0.x

-alt- verion should be used for some Note4 variants: N910F/G/P and Note Edge N915F/G running Marshmallow TW Roms (Those Roms come with two more non AOSP changes on Marshmallow.

I have no problem if only flash xposed without suhide, but not both together, sad...:crying::crying:
[SuperSU] KaMyKaSii:
This with Xposed v86.6 made for Magisk? Have you tried to install v86.2 made for SuperSU?
[SuperSU] Leafia:
On my Sony Xperia M4 Aqua I continuously keep getting messages that Google Service Framework and Google Play Services stopped working. (SR1 and suhide 0.54 installed, happened with 0.53 as well - Magisk, xposed and similar stuff doesn't matter)

suhide 0.54 actually works, though. I can pass SafetyNet and even play Pokemon GO, it's just really annoying having to do everything fast enough in between these error popups.

Is there any way to provide you with useful log files?

(hidesu with phh's SuperUser works perfectly, but I can't use xposed framework with that one.)
[SuperSU] bobby janow:
We don't have that in the US so I can't speak to it. Do you have AP in Amsterdam?

You've never gone shopping with my wife or daughter, I can see that. The wallet is in the bottom of the bag, the phone in a front jean pocket. So unzip the bag, find the wallet, open it, find the card, pay, put the card back in after an interminable wait for the reader to allow you to take it out, wallet back in, zip the bag, take your shopping and eventually walk out the door. Or.. take your phone out, tap it, and walk out the door. No one is stealing the phone from her front pocket if they want to walk away intact. Yes it's an easy mark to see where the wallet went, distract the shopper and not only is your credit card gone but your pictures, license, and everything else in there.

Once again, we do not have those so I can't speak to it.

Completely false argument. Won't even address it.

Nor are they holding a debit card. Skimming is not valid with Android or Apple Pay. They use a token and virtual number so it can't be skimmed. I know in the US skimming is done to the tune of probably billions / year. I'm not sure how the NFC debit works and if that is more secure than our cards.

Either way AP is here to stay and expanding globally. As for suhide, are you using it for something or are you just trying to ruin our fun? Just kidding naturally, but it's nice to have root when you want it without affecting AP and banking apps. I can't speak to POGO either because ... well I tried it and couldn't figure it out, made my phone hot and I felt silly. Angry Birds is quite enough for me.
[SuperSU] stanxx:
Previously I did have several tries on suhide v0.53 + xposed v86.2, same bootloop problem, I can have only either one but not both.

Re-attach LiveBoot logs.
[SuperSU] JBsasuke:
devices samsung note 5, plus, S7 etc. do not know if in another model can try at your own risk. Restart in recovery then flash this 3 things together SuperSU 2.78 R1 suhide v0.54 and magisk v7 reinicial return to the normal restart in recovery mode and flash Xposed 8.6.6 and restart normal and everything worked perfect until greetings excuse my bad English.
[SuperSU] ExpertMC:
So I tried to uninstall systemless Xposed v86.2 with the uninstaller on his post. However i get an error message and fail because it says it requires the Magisk mod. I do not have Magisk installed. how do I uninstall v86.2?
[SuperSU] Ch3vr0n:
Well, I'd suggest you ask that in the xposed thread. You're in the wrong topic.
[SuperSU] gc_geforce:
How do I run this command to add UID of the programs I want to be in the blacklist? I have everything installed I just do not know how to run the /su/suhide/add
[SuperSU] grep_i:
It's described in the OP first post.

There is also an app in the Playstore called:

suhide GUI

A graphical user interface for blacklisting apps for su detection
[SuperSU] youling257:
if mount haploid32 on app_process32，can't boot，bootloops，please see dmesg
[SuperSU] gc_geforce:
Thanks the gui was not working for me, so I just flashed the suhide via flashfire again and now it is working.
[SuperSU] Shack70:
Your root is part of the rom...

Delete the subject files in the /bin/ and /xbin/ directories

Boot into twrp

Under advance open a terminal

Use the echo "SYSYTEMLESS=true" > /data/.supersu command

Install supersu

Reboot

Boot into recovery

Install suhide. 54

Reboot

Add pokemon go to the list to hide(see 1st post for guidance app)
[SuperSU] osm0sis:
Everybody, forever: It's not necessary to add Pokémon GO to the list because it uses SafetyNet and that is blocked by default.
[SuperSU] AmitKilo:
Much thanks!
[SuperSU] redskinsfan:
AdAway works fine in N. It breaks when suhide is flashed. May have to do with how it looks for root.
[SuperSU] bouchigo:
Adaway works fine when suhide isn't installed. I'm running the permissive live command for viper, and adaway still doesn't work.
[SuperSU] Pig Vomit:
6P, stock N, latest TWRP, 2.76......absolutely no issues on 0.01 or 0.12. AP works fine. No PIN required prior to boot.
[SuperSU] CSX321:
Okay, I've maybe narrowed down the problem with freeze/thaw in Titanium Backup. Without suhide it works, but with suhide I got this in the SuperSU log when I tried to thaw an app:

sh /system/bin/pm enable "com.icq.mobile.client"
CANNOT LINK EXECUTABLE: couldn't map "/sbin/suhide32.so" segment 2: Permission denied
page record for 0xb6ee302c was not found (block_size=32)

This is on a Nexus 5 with MM, August patch, ElementalX kernel, SuperSU systemless. Nothing else out of the ordinary, no Xposed, etc.
[SuperSU] voland66:
So I have the same systemless adaway setup as you do (though I think it does not matter when the adaway is installed, what matters is when adaway downloads hosts file). It's strange that it works for you and not for me or some others. I wonder if it is device or the android version (I have nexus 5x, with stock nougat).
[SuperSU] galakanokis:
I get the following when trying to add the UID, /data/adb/suhide-add: not found, I see the folder where it is suppose to be but cannot write from any form of shell. Could it be a permission thing?
[SuperSU] HamsterHam:
Same, how many files do you have in that folder? I'm missing suhide.uid
[SuperSU] SpasilliumNexus:
[MENTION=631273]Chainfire[/MENTION]

May I suggest including that the ROM has to be booted at least once before applying this? Otherwise the device might not boot, or go through a weird app optimization followed by numerous random soft reboots part way through the process. I've learned the hard way by doing exactly this by installing this right after flashing on a clean device without rebooting first.
[SuperSU] cygery:
I'm using the 'u:r:system_app:s0' SELinux context in some of my apps. With suhide the problem quoted above also occurs when trying to use this context:

$ su -cn u:r:system_app:s0
CANNOT LINK EXECUTABLE: couldn't map "/sbin/suhide32.so" segment 2: Permission denied
page record for 0xb6e9202c was not found (block_size=32)

Using SuperSU 2.77 Beta (systemless), suhide v0.12, Nexus 5 MOB30Y.

If there's anything I can test/provide more info please ping me.
[SuperSU] Chainfire:
Oh my god, ICQ still exists?!

Anyway, please get a logcat of this error, I think we'll see an SELinux audit come up that we can fix.

Same for you: please get a logcat of this error, I think we'll see an SELinux audit come up that we can fix.

First I've heard of this.

Are you running the very latest TWRP ? Or how did you flash ?

Are you running the very latest TWRP ? Or how did you flash ?

This has not been properly tested in combination with Magisk or (system and/or systemless) xposed yet. They may have some incompatibilities still.
[SuperSU] HamsterHam:
[MENTION=631273]Chainfire[/MENTION] latest twrp, flashed suhide and then SuperSU.
[SuperSU] Chainfire:
I need /tmp/recovery.log from both flashes
[SuperSU] ShapeShifter499:
I'm still having a issue with version 0.12, my device will hang on the Cyanogenmod Robot forever without once asking for my encryption password. If I flash the suhide-rm script like I did with version 0.01 booting will resume without noticeable issue.

I'm trying this on a Moto X Pure running Cyanogenmod 13.0 Nightly 08/31/16 with Systemless SuperSU version 2.76
[SuperSU] HamsterHam:
Here, hope you can work out the issue.
[SuperSU] dacre:
You continue to amazing. (In my original post I just wanted to report that the concept does work on custom ROMs and not stock only, definitely was not complaining).
[SuperSU] cygery:
09-01 11:52:36.339 W/sh ( 6349): type=1400 audit(0.0:1210): avc: denied { execute } for path="/sbin/suhide32.so" dev="rootfs" ino=5474 scontext=u:r:system_app:s0 tcontext=u:object_r:rootfs:s0 tclass=file permissive=0
09-01 11:52:36.963 D/AndroidRuntime( 6351): >>>>>> START com.android.internal.os.RuntimeInit uid 0 <<<<<<
09-01 11:52:36.967 D/AndroidRuntime( 6351): CheckJNI is OFF
09-01 11:52:36.969 W/app_process( 6351): type=1400 audit(0.0:1211): avc: denied { write } for name="system@framework@boot.art" dev="dm-0" ino=1130500 scontext=u:r:shell:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=file permissive=0
09-01 11:52:37.007 D/ICU ( 6351): No timezone override file found: /data/misc/zoneinfo/current/icu/icu_tzdata.dat
09-01 11:52:37.009 W/main ( 6351): type=1400 audit(0.0:1212): avc: denied { write } for name="arm" dev="dm-0" ino=1130499 scontext=u:r:shell:s0 tcontext=u:object_r:dalvikcache_data_file:s0 tclass=dir permissive=0
09-01 11:52:37.046 I/Radio-JNI( 6351): register_android_hardware_Radio DONE
09-01 11:52:37.065 D/AndroidRuntime( 6351): Calling main entry com.android.commands.am.Am
09-01 11:52:37.092 D/AndroidRuntime( 6351): Shutting down VM
[SuperSU] Chainfire:
You are running SuperSU in system mode, while suhide requires running SuperSU in systemless mode.
[SuperSU] cygery:
Yup, works. Thanks a lot!
[SuperSU] Chainfire:
Don't run that command from you app though - I will integrate it into next update.
[SuperSU] gnex4us:
What files must delate, all? Delate alle Files/bin and /xbin ?
[SuperSU] Shack70:
Yeah I guess your right, bit it won't hurt to add it
[SuperSU] Boosik:
After flashing suhide 0.54, performance of my phone (Huawei Mate 8) is significantly lower than it used to be prior to flashing.

I've tried to install Xposed 86.6 systemless magisk, and performance was like without suhide, but safetynet check won't pass.

After disabling Xposed in magisk manager and rebooting, safetynet check is OK, but the performance is **** again.

Is this normal? Any ideas how to fix this?
[SuperSU] Rhoban:
Yes, it's normal. It's even stated in the OP.

---------- Post added at 09:42 PM ---------- Previous post was at 09:41 PM ----------

If you delete all, you will brick your device.

You're looking for su files.
[SuperSU] gnex4us:
If you delete all, you will brick your device.

You're looking for su files.[/QUOTE]

There are no files thay called su superuser or someone like this:rolleyes:
[SuperSU] Boosik:
[MENTION=6312707]GDReaper[/MENTION] but OP states, that there are performance problems with Xposed. I have performance problems with suhide. After flashing Xposed 86.6 (from magisk manager), performance is great again, but safetynet check will not pass. After disabling xposed in magisk manager, performance problems are back.

It is really strange :(
[SuperSU] tordawgg:
Hey guys, just looking for some clarification on my situation. Verizon S7, 6.0.1

Despite flashing the suhide zip via Flashfire, the suhide GUI app doesn't think it's installed. I originally flashed SuperSU 2.76 when I rooted, and in the SuperSU Google Play app under System it says it's in system-less root mode, so no problems in those requirements. However, I rooted my S7 using this method, requiring a custom boot image: http://xdaforums.com/verizon-galaxy-s7/how-to/how-to-notes-root-install-xposed-unroot-t3411039

Is this the reason I can't get suhide working? I'm just trying to bypass SafetyNet so I can log in to Snapchat again, so if I have to do a fresh wipe/install of my phone just for Snapchat it really isn't worth it in my mind. I have the custom Xposed framework from the linked guide uninstalled, uninstalled Snapchat multiple times, wiped the dalvik cache, reinstalled Snapchat and tried logging in and absolutely none of these methods worked.
[SuperSU] xstahsie:
I have this performance issue with my Nexus 6P. My phone really slows down after flashing Chainfire's suhide and this is without flashing anything else. I didn't experience this issue with phh Superuser suhide but since it no longer passes SafetyNet, I decided to switch back to Chainfire's suhide.

I'll jt have to deal with it until phh releases a new version of his Superuser suhide.
[SuperSU] tordawgg:
ORIGINALLY flashed 2.76. As per the app, I CURRENTLY have 2.78 SR1 installed, how do I know for sure if it's installed systemless? As I said before, in SuperSU it says I cannot install it to /system as its "not (currently) available in system-less root mode, so without really knowing what I'm talking about it seems like it's installed system-less.
[SuperSU] civicsr2cool:
same here, ive gotten all magisk/ supersu's/su hides to work together but su hide just simply doest work with any versions of xposed for me.
[SuperSU] trice187:
suhide doesnt work on my note 4. im using the stock rom with systemless sr1 supersu. does anyone know how to get it to flash through twrp. none of the suhide versions have ever worked for me.

thanks
[SuperSU] sansnil:
No solution but I've observed this on my N6 as well. I assume it's from whatever hoops need to be jumped through to hide root but the performance hit is bad.
[SuperSU] corkiejp:
[MENTION=6974469]tordawgg[/MENTION] 2.78 SR1 has to be flashed by TWRP on to probably stock boot image. Not your modified boot image from your method of rooting.

I could be wrong here, but your modified boot image is conflicting with the root process. Hence suhide not working.
[SuperSU] tordawgg:
The Verizon S7 doesn't have any custom recoveries available, so I can't flash anything without Flashfire, which requires me to download SuperSU from the Play Store to give it root access, just so I can flash 2.78 SR1. If I do that, delete the app from my phone and then flash the zip onto my phone (without writing to system), would that possibly work? I've broken my phone and had to re-flash the custom boot image multiple times already so I wanted to ask before going through that process again when it doesn't work.
[SuperSU] KOLANICH:
[MENTION=631273]Chainfire[/MENTION], isn't SafetyNet a pure Java API? If it is why cannot the ones who want it be bypassed to just hook it and make it say "the phone is original"? The problem can be solved by using native apps, but when dev's use native apps they don't need API, they need a cpu instruction to check the platform integrity. Another way is remote device attestation like in Intel SGX, but it means overcentralizing the platform, no app dev will be ready to pay to ARM or to bunch of cpu vendors to be able to use the feature. In this case cpu vendors are not restricted by google's API and can promote own one. So, why does SafetyNet exist?
[SuperSU] jesssiii:
Based on your posted info, you're Systemless.

Nexus 6P
[SuperSU] tordawgg:
When I try to flash suhide via flashfire, it tells me it failed because it found the /xbin/su file, and asks if I'm sure I have 2.78 installed systemless.... so I'm going to make a judgement call and say it's not installed systemless
[SuperSU] hi_cannon:
SafetyNet doesn't just return a true/false. It connects with Google servers to return a cryptographically secured message that can't be tampered with (ie signed with SSL certificates).
[SuperSU] mrtko:
Pure Awesomeness!!

Used Flashfire on suhide-rm-v0.51.zip

then Flashfire on suhide-v0.54.zip

Back running pogo!! So easy! Great job on getting us back in business so quickly!
[SuperSU] Rhoban:
Slim ROMs seem to have a problem with suhide and Xposed running together.

Suhide alone and Xposed alone works. As soon as I try to run them together, bootloop.