yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
I already blocked the ones I could find including:

Com.android.vending

Com.google.android.ext.services

Com.google.android.gms

Com.google.android.gms.feedback

Com.google.android.gms.persistent

Com.google.processes.gapps

Under the app tab I also blocked Google services framework which added several things along with it.

I am now adding everything related to Google, Android and Qualcomm. But not enthusiastic. I think Android Pay was recently updated so that probably explains it.

Has anyone had success actually using AP to make a purchase as opposed to just adding cards to it???
[Google Pixel XL Guides, News, & Discussion] Fenny:
Yep just worked at the store this morning.

Don't forget to reboot after adding those services (preferably by PID instead of by name -- the process lookup happens instantly if it is by id, name takes a second to decide it needs to be blocked).

Try leaving rootswitch toggled off and only turn it on when you are going to use root features, Safteynet does background checks, and will fail if one of them recently detected root.
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
Interesting. I'm thinking another possibility is to add a second user. So far, I've gotten to point of passing SafetyNet and adding cards to Android Pay for a second user. To do it, I just set up the second user and installed the apps I want to hide from root and nothing else. SUHide GUI, etc is just for main user. Turn Rootswitch for main user to "disabled" and flip to second user. Seems the second user approach may hide more tracks otherwise evident in the main user's data. Works so far in vitro. Excited to give it a try in a store.

Update: Woohoo! Tested at CVS on the way home and works when used as above: As main user, set Rootswitch to "disabled," switch to second user and use Android Pay from there.
[Google Pixel XL Guides, News, & Discussion] sakuhei:
In fact, no need to be so troublesome. Before you wanna use AP, turn off root in rootswitch and add the credit card in AP again. No need to switch to 2nd user.

Learn this from the main thread for suhide. They mentioned AP will perform safetynet check in background regularly.... So after you add credit card in AP and turn on root in rootswitch again, in sometime the AP would fail...

Got the same error msg as yours before and it is solved now (I.e. add the card again before you use AP)
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
What you say is informative and explains why it works for Fenny who runs SUHide as default disabled. Default disabled wouldn't work for me though. But understanding why failures may occurs let's people come up with the solution that works best for them.

But honestly, re-adding a credit card sounds much slower than pulling down the status bar and switching users. I just timed it. 5 seconds from pulling down the status bar to fully switch. But
[Google Pixel XL Guides, News, & Discussion] ghostENVY:
Just tried this method and it works good thanks for the share :good:
[Google Pixel XL Guides, News, & Discussion] burtonlax:
I've been able to use AP by disabling root and just tapping to add a card then back out. It seems to reset the root check for AP.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Yeah, you don't have to go all the way through the process of adding a card.
[Google Pixel XL Guides, News, & Discussion] DracoDan:
I have build NDE63P, would you mind creating a patch for that? I searched the thread and didn't find any mention of it.

Thanks!
[Google Pixel XL Guides, News, & Discussion] JU57US:
NDE63P is the October 2016 build for Verizon. If you're not wanting to be on the latest build anyway, at least just upgrade to NMF26O, which is the December 2016 7.1.1 build and flash those patched files. You can get that specific update by downloading the factory images from https://developers.google.com/android/images
[Google Pixel XL Guides, News, & Discussion] DracoDan:
My understanding (and fear) is that updating to that would affect my unlocked bootloader, do you know if that's true?
[Google Pixel XL Guides, News, & Discussion] ghostENVY:
Tried the Patched PureNexus files on the Resurrection Remix Rom and it caused a loop. Is it because its based on Lineage and not AOSP?
[Google Pixel XL Guides, News, & Discussion] JU57US:
If your bootloader is already unlocked, upgrading will not affect it's unlocked state. Just don't ever re-lock it unless 1) you're on a completely stock build, stock kernel and stock recovery, AND 2) you don't ever want to unlock it again.
[Google Pixel XL Guides, News, & Discussion] fiveighteen:
Unlock your bootloader and take the OTA? No need to make patches for every previous version.

Here is my guide from stock 7.1.1 build (Jan 5, 2017) on Verizon USA
[Google Pixel XL Guides, News, & Discussion] trevorcobb:
has anyone successfully patched the files for build NPG05E (7.1.2 beta 1)?
[Google Pixel XL Guides, News, & Discussion] trevorcobb:
or the NOF26V build?
[Google Pixel XL Guides, News, & Discussion] JU57US:
No. The latest patched files available are the ones listed for Pure Nexus, which actually work on NMF26V. Nobody has patched files for NMF26U or anything after that. The learning curve to do it seems to be somewhat steep, but you can have a crack at it.
[Google Pixel XL Guides, News, & Discussion] trevorcobb:
yeah i've read all 32 pages of this thread so far and am not ashamed to say that I have no clue how TF to do most of what is needed to patch my own files. i know that [MENTION=522448]Fenny[/MENTION] talked about making an automated tool, or the possibility of chainfire including this patching in an updated version of SUHide. Any progress on that front?
[Google Pixel XL Guides, News, & Discussion] psychatog64:
@ fenny can you possibly do a patch for nmf26u? If not to much trouble I can apply the patch simply enough but patching the files my self yea that's not gonna happen lol
[Google Pixel XL Guides, News, & Discussion] anuraj1:
Has a patch been released for the latest security update (NOF26V)?
[Google Pixel XL Guides, News, & Discussion] cmo220:
No. Not yet. Hopefully there will be one.

I haven't done much modding, at all really, but definitely none in a few years. I started looking at the write up to see if it's something I could try to do, but only for a few minutes. This is the type of thing I used to love to figure out, but I don't have much free time anymore. And I'm sure that's why another hasn't been made yet.

[MENTION=522448]Fenny[/MENTION] did a great write-up, just didn't mention what tools were used to make the changes. Any chance you could give a little more info on how this was done, just in case?
[Google Pixel XL Guides, News, & Discussion] JU57US:
Actually, he did. IDA Pro, Vbindiff, HxD.

[MENTION=522448]Fenny[/MENTION] also reported his intent to create a flashable zip and a proper release thread. And when people have asked about patches for the new monthly versions, he reiterated his desire to simply create an auto-patcher, as I'm sure he doesn't want to be a slave to patching and posting these files every month.
[Google Pixel XL Guides, News, & Discussion] cmo220:
Thanks! I guess it turns out those few minutes that I spent reading I didn't look close enough. An auto-patcher would be great. I know doing this monthly or more with betas and all would be way too much work.
[Google Pixel XL Guides, News, & Discussion] JU57US:
What I question is how long this will even be viable. It seems it won't work with anything beyond SuperSU 2.79 (current version is now 2.79 SR3) and chainfire seems to have all but abandoned any idea of keeping suhide working at all.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Has anyone tried this on Pure Nexus 02/15/17?
[Google Pixel XL Guides, News, & Discussion] Fenny:
Should just be a matter of patching the libs.

It should be possible to set init permissive enough to allow suhide to work with newer SuperSU builds, haven't done much research into it yet.

I have not taken the update to that patch level yet. Should be doable, nothing jumped out at me in the changes to framework.

Maybe one day I will be less busy, or optionally, less lazy. :P
[Google Pixel XL Guides, News, & Discussion] anuraj1:
No worries [MENTION=522448]Fenny[/MENTION], I didn't mean to sound like I was demanding it. I was just curious.
[Google Pixel XL Guides, News, & Discussion] jrac86:
My phone auto updated on its own. Really hoping that there is a new patched version posted here soon.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Oh, neat, the OTA does indeed still apply on modified system partitions.

Quick patch for build NOF26V.
[Google Pixel XL Guides, News, & Discussion] fiveighteen:
For future reference, you can disable the "Automatic System Updates" toggle in Settings/Developer Options to stop that from happening.
[Google Pixel XL Guides, News, & Discussion] JU57US:
Sweet, thanks [MENTION=522448]Fenny[/MENTION]! I think I'm going to give this a try now.

Are you still running into troubles on an auto-patching app? (This is not asking for an ETA, this is referencing your post from several pages back where you mentioned running into a problem with that idea altogether. I'm unsure what the problem was, specifically, but I think you mentioned it being something that may prevent an auto-patcher from being a possibility).
[Google Pixel XL Guides, News, & Discussion] Fenny:
I can auto patch the arm lib with simple pattern matching pretty reliably, but the arm64 lib seems to be a moving target as far as offsets between the individual patches go. I am hoping that these patches won't be required for too long.
[Google Pixel XL Guides, News, & Discussion] MArtyChubbs:
Used the patched NOF26V libs on PN 021517 (NOF26W) and suhide gui detected suhide. Used rootswitch to turn off root. AP detected something was up.

I am using franco kernel. Could the failure be in my kernel or is it because the wrong lib version?

Update: Same issue with ElementalX. I'll wait for the NOF26W patched libs.
[Google Pixel XL Guides, News, & Discussion] kleptonez:
seems to be a kernel issue. Used the files on an untouched PN 021517 (NOF26W) and it worked for me. Try going back to the PN kernel.
[Google Pixel XL Guides, News, & Discussion] Fenny:
I can at least confirm that AP works on NOF26V, I tested it this morning, so we're not dealing with a new detection method (as far as I can tell).
[Google Pixel XL Guides, News, & Discussion] cmo220:
Worked fine here too with PN kernel.
[Google Pixel XL Guides, News, & Discussion] LazerL0rd:
Would this work for Nexus devices? I know I'd have to change it manually for my device though, I'm just wondering is this possible for the Nexii too?
[Google Pixel XL Guides, News, & Discussion] jrac86:
I'm still having some issues... What versions of SU and SUHide are used for this to work? I thought the process was to flash SU, replace lib files, and then flash suhide, but suhide keeps failing the install. Any help would be very much appreciated!

EDIT: Followed the guide from earlier on in this forum and realized I was forgetting to delete the fstab file. Thanks for patching the files and all your work for this!
[Google Pixel XL Guides, News, & Discussion] ScottIsMyName:
I was under the impression that using the downloads in the first post on a custom rom would not work as the custom rom has probably made other system changes to libandroid_runtime.so . Is this not the case with Pure Nexus, for instance?
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Can't you just use magisk?

---------- Post added at 08:02 PM ---------- Previous post was at 08:00 PM ----------

I'm running the previous version of PN with the modded files in the thread. I would assume the new version needs the files so I haven't updated.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Yes, it will definitely work on the nexus devices, and it should work even on third party devices like HTC, etc... as long as they are not deviating too far from the AOSP tree. In fact there were modified files posted in the Suhide thread by someone who followed the patching guide for an older build (DEC?) on the nexus 6.
[Google Pixel XL Guides, News, & Discussion] LazerL0rd:
Um.. does Magisk even run that early? I don't think it'll be able to run early enough at boot.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I'm not sure what you mean. I had Magisk on my 6P before I got my pixel so I could play POGO and still have root.
[Google Pixel XL Guides, News, & Discussion] LazerL0rd:
In other words. If I make a magisk module for this, would the module load before the system boots? This file is used at boot to block suhide which it why the patch was created.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Sorry I still don't get your question. What are you trying to run? Even with the patch when you reboot you are rooted until you use rootswitch to turn it off. Which is what magisk does without any headaches of patched files. You just use magisk manager I believe it's called to turn root on and off as required. But maybe someone else can chime in on this.
[Google Pixel XL Guides, News, & Discussion] LazerL0rd:
Sorry I misunderstood you. I thought you told me to use a Magisk Module instead for this patch. I'm using Magisk, but with SuperSU. So I can't use Magisk Manager to disable root unfortunately.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I think getting Magisk working will be a lot easier than trying to get this working. But anyways good luck
[Google Pixel XL Guides, News, & Discussion] laxattack:
Just as others have posted latest NOF26V files working just fine on the PureNexus rom build for 2/15/17. Thanks [MENTION=522448]Fenny[/MENTION]
[Google Pixel XL Guides, News, & Discussion] SanJoseCA:
Experts, a little help required here... Not exactly related to the process.. When I flash SuperSU-v2.79-201612051815.zip (I suppose this THE stable release that we are talking about here) it tells me that, it flashed successfully. But when booted, root seems to be absent. I also don't see the later part of log that V2.79-SR3 prints during flashing.

What I did:

1) clean flash even with -w present. (Stock Feb 2017)

2) boot into recovery with fastboot boot.

3) delete fstab.marlin

4) sideload SuperSU-v2.79-201612051815.zip (stable). ( Does it make any difference?)

6) Just to note : The later part of logs that supersu v2.79-SR3 prints e.g. patching kernel etc. is not printed with stable.

7) no root present upon boot. Not even supersu app present.

Am I missing something very basic?

Edit: SR3 worked perfect with same steps.. of course without suhide.

Edit2: Somehow supersu installer (stable) is always installing in system mode, moreover root is not present upon boot. Not honoring /data/.supersu settings.
[Google Pixel XL Guides, News, & Discussion] banciii:
I am also having problems with my Pixel (sailfish) - on Pure Nexus (02/15/16/NOF26W/PureKernel)

1. downloaded and replaces the files with Root Explorer (and ofc set 644)

2. downloaded SuperSU 2.79 (stable) and suhide 0.55

3. rebooted into recovery and tried to flash SuperSU 2.79 (coming from 2.79 SR3) and suhide 0.55, but SU got installed somehow in system mode, so suhide could not be installed

4. rebooted, installed SuperSU from play store (2.79) which showed I have su installed fine

5. rebooted into recovery and tried to flash suhide 0.55 alone, which went fine this time

6. rebooted > bootloop

x. tried to re-flash SuperSU 2.79 SR3 to restore the original state, but it still gave me bootloop

x. re-flashing SuperSU 2.79 stable made the system bootable again

Am I missing something here? :'(
[Google Pixel XL Guides, News, & Discussion] Fenny:
With the newer builds of TWRP, there was an fstab file added that causes problems with the older builds of SuperSu. Either boot the older build of TWRP (alpha2), or delete the *.fstab file using the built in TWRP file explorer. (It's a tmpfs so you're not deleting anything permanently.)
[Google Pixel XL Guides, News, & Discussion] SanJoseCA:
Perfect.. TWRP Alpha 2 did the trick. Thank you.

Just one question, after countless flashings, despite deleting fstab.marlin why wouldn't it work with twrp RC1 ?
[Google Pixel XL Guides, News, & Discussion] Fenny:
I can't say for sure why deleting the fstab file didn't fix it for you. That has worked fine for me in the past. The problem was the method Chainfire was using to detect whether or not the install should be done systemless. His boot to root image use a fairly unmodified version of the recovery partition. That recovery partition did not have an fstab file. So, detecting whether or not it was there was a very simple way for him to determine that he was using a pixel device that needed systemless install.

The older version of TWRP used a similar method to his and did not create that file. Rc1 added it.
[Google Pixel XL Guides, News, & Discussion] ansontyl96:
Hey, I am having an issue while flashing suhide on my sailfish on Pure Nexus (02/15/16/NOF26W/PureKernel)

File used: supersu 2.79 stable, libandroid_for purenexus rom from post 195, TWRP RC1

what I did:

1.Flash supersu

2.reboot and confirmed that root present

3.replcae the lib and lib64 file through twrp, all 6 file's permission have been set to 644

4.from this point, my device was stucked in bootloop, which I have to reflash system in order to boot

Am I doing anything wrong here? I have read through the thread and I think I am following the right procedures...
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Your answer is 6 posts up
[Google Pixel XL Guides, News, & Discussion] ansontyl96:
Thanks for replying, I've try that file as well but i still went into bootloop..
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I haven't had time to try it yet
[Google Pixel XL Guides, News, & Discussion] billiepreks:
My phone freeze everytime I try to disable root on rootswitch.. Anyone knows this issue ?
[Google Pixel XL Guides, News, & Discussion] ansontyl96:
Apparently that might casued by problem of corrupted file, after a clean flash, supersu sable and that lib files, I am able to get suhide work in my purenexus rom!
[Google Pixel XL Guides, News, & Discussion] fiveighteen:
Post #294
[Google Pixel XL Guides, News, & Discussion] Juzman:
I tried this.

Copied over the patched libandroid files, and booted fine.

I was already rooted, so just flashed suhide, and when I went to boot, stuck on bouncing dots.

Flash suhide-rm and booted fine again.

Edit: I'm using SR3-2.79 SuperSU. Will try with the stable: SuperSU-v2.79-201612051815

Edit 2: Booted with SuperSU-v2.79-201612051815.
[Google Pixel XL Guides, News, & Discussion] SanJoseCA:
Based on what [MENTION=522448]Fenny[/MENTION] told and my experiments, TWRP RC1 didn't work, despite deleting fstab.marlin. ALPHA2 worked for me with 2.79 stable.

Won't unroot option work for you? You could unroot and reroot with stable.
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Has anyone tried this patch on March's NOF27B or will we need a new patch for it?
[Google Pixel XL Guides, News, & Discussion] Fenny:
The new build will need to be patched.
[Google Pixel XL Guides, News, & Discussion] sakuhei:
Will wait for patched file or I won't upgrade the phone :D

It is now my only consideration for upgrading OS now!!
[Google Pixel XL Guides, News, & Discussion] mims1979:
I can confirm that libandroid_runtime_pixelxl_NOF26V.tar works as expected with NOF27C security update.

safetynet app passes, suhide/rootswitch/Android pay all still work.
[Google Pixel XL Guides, News, & Discussion] Fenny:
That is surprising. There must not have been runtime changes. I haven't yet looked at the commits this go-round, but hey, I'll take it.
[Google Pixel XL Guides, News, & Discussion] mims1979:
Idk if it makes a difference, but I just side loaded the OTA from Google. File sizes are the same so I gave it a shot. Worst case I'd just put the old one back
[Google Pixel XL Guides, News, & Discussion] JU57US:
Of course, NOF27C is the "Rogers Only" variant. Everyone else uses NOF27B. With no problems on C, what's the chances of your NOF26V patch also working on NOF27B?

---------- Post added at 04:23 PM ---------- Previous post was at 04:10 PM ----------

I think this must be one of those "your mileage may vary" kind of things, because TWRP RC1 has been reported as working by simply deleting the fstab.marlin file from within TWRP and before installing SuperSU 2.79 stable. Fenny just stated that he didn't know why it didn't work for your situation. fiveeighteen, in his guide on post 294, had it work on the first try.

I'd say it would be best to use TWRP RC1 instead of Alpha2, as long as it works, as per the recommendation of Dees_Troy.
[Google Pixel XL Guides, News, & Discussion] mims1979:
Well, the google ota site didn't mention that it was "rogers only" so I just went with whatever was the latest, which was NOF27C. I read somewhere else that you can't downgrade from C to B or else I'd give it a shot on that. Regardless, from what I can tell everything is working as it was before(network signal, wifi, sms, mms). I guess I'll wait until next release and update to the correct "everybody else" version following the same process and keep my fingers crossed.
[Google Pixel XL Guides, News, & Discussion] Fenny:
The following is OT, but whatever, it's my thread, so I can have as much off topic discussion as I like, right?

I came from the S7, so I have yet to try magisk. I am eagerly awaiting the port. From what I am reading, I think we may be able to fix most of the compatibility issues with that root vs supersu with a simple sepolicy/supolicy wrapper script. I.E. convert the commands that work on one to the compatible command on the other (and probably add some default SuperSu policies that are missing.). Should be able to get most things working that don't out of the box with magisk's root right now.
[Google Pixel XL Guides, News, & Discussion] mims1979:
my impatience and need to constantly tinker doesn't allow me to wait a month for another update. I was successfully able to sideload marlin-ota-nof27b-ca49da7b and reapply the patches and everything still works. So looks like the B version is all good too!
[Google Pixel XL Guides, News, & Discussion] ScottIsMyName:
So the version for V works on B as well? Can I do this without installing TWRP?

I'm currently rooted using the standard boot-to-root method from chainfire. Wondering what steps are needed to get AP to work besides installing the patched runtime files.
[Google Pixel XL Guides, News, & Discussion] mims1979:
I'd assume you can replace the files with root explorer/root browser, you still need to install suhide as well though. I'd say you could probably just open up suhide.zip and look at the script and manually install it. It suppose it's worth a try. But from what I've read and my experience it was very picky about which version of superuser so make sure you have the one I mentioned.
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
Anybody else try and succeed with these patches for the latest available build?

Just got my Pixel XL yesterday, it's still on NDE63L. I haven't even unlocked the bootloader yet. Want android pay with twrp and root.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
You can boot TWRP from fastboot without installing it
[Google Pixel XL Guides, News, & Discussion] mims1979:
yea, it's working on 7.1.1 nof27b. But I believe you need to unlock your bootloader with depixel8 before you upgrade as I think it's blocked after that.
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
I meant other than you hah. And I've got a play store model.