yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Working here on PureNexus NOF26W with Fenny's NOF26V patched files.

On TWRP, go to your libandroid patched folder and move lib and lib64 folders to /system/system/.

Go in /system/system/lib/ and chmod 644 the 3 libandroid_runtime files. Do the same on lib64 folder. Reboot. If you stuck on Google splash screen or boot without seeing the bouncing dots, there is a mistake when moved or granted permissions to patched libandroid files.

But after many try I can affirme this: be sure to use TWRP Alpha2 instead of RC1 (cause stuck on bouncing dots) and SuperSU 2.79 instead of 2.79-SR3 (stuck too).

Install Rootswitch 1.3.3.2.apk from Google, grant root access.

Install Suhide GUI from Play Store, grant root access. Reboot to recovery, flash suhide, reboot, open Suhide Gui

and add these processes:

android.ext.services

com.google.android.gms

com.google.android.gms.persistent

com.google.android.gms.feedback

com.google.android.gms.unstable

com.android.vending

com.google.process.gapps

.. And all of your apps you need to hiding root

Reboot, untick "Root Enabled" on Rootswitch, then launch any SafetyNet checker.

Don't forget to grant root access to all of your apps who need root BEFORE flashing Suhide.

Edit: the new TWRP RC2 seems to work with SuperSU 2.79 (but always stuck on boucing dots with 2.79 SR3)
[Google Pixel XL Guides, News, & Discussion] JAYNO20:
I got all the lib files moved over and permissions changed, but when I flash suhide it just sits at the bouncing dots screen forever until I flash suhide-rm. Which version did you flash?
[Google Pixel XL Guides, News, & Discussion] Ker~Man:
[MENTION=522448]Fenny[/MENTION], will you please add patched files for "O" firmware? For us "Dirty" users?:p
[Google Pixel XL Guides, News, & Discussion] Fenny:
Grab a log using chainfire's liveboot. It sounds like maybe only one of the files in lib or lib64 were replaced.

If you will post libandroid_runtime.so from /system/lib and /system/lib64, I can probably modify those for you.
[Google Pixel XL Guides, News, & Discussion] Zavon:
Here are the O files. I'm at work so I can't play too much to get a log of the boot.
[Google Pixel XL Guides, News, & Discussion] JAYNO20:
Will the posted lib files work on the regular (5") Pixel as well or are these strictly limited to the XL?
[Google Pixel XL Guides, News, & Discussion] Fenny:
No clue if they are the same, you can use vbindiff to compare the stock versions with my patch files from the first file I posted.

If you can determine the offset of the areas I patched in your version, you can use a hex editor to apply the patch to yours.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Give these a try:

libandroid_runtime_pixelxl_NMF26O.tar
[Google Pixel XL Guides, News, & Discussion] Zavon:
Boots fine. suhide gui is stuck on initial loading. Flashed suhide0.55.

*Update* Had to set SuperSU default to "grant". After flashing SuperSU no longer prompts for option to grant or deny.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Interesting... I had not noticed that. Which version of SuperSU?
[Google Pixel XL Guides, News, & Discussion] SimplyCity:
Hi guys, I am looking here with hope, nobody answered a word. Forgive interruption, but is there possibility that [MENTION=522448]Fenny[/MENTION]'s method could work for other device? If so, could you try with files from my device if I attached them? Thanks

Echoe™ Team Member / S7E
[Google Pixel XL Guides, News, & Discussion] bajasur:
If your on a Samsung device it's highly doubtful
[Google Pixel XL Guides, News, & Discussion] SimplyCity:
Yes, I am. Alright then, have to forget, it seems. If you guys find universal way, or could try with libs from S7E, would be awesome! Thanks anyway

Echoe™ team member / S7E
[Google Pixel XL Guides, News, & Discussion] bajasur:
Sorry to get your hopes down. Maybe the OP will have better news for you.
[Google Pixel XL Guides, News, & Discussion] Ker~Man:
So, I've tried everything... PoGo still doesn't work, and more importantly, SafetyNet Helpers' third step check fails. At a complete loss...
[Google Pixel XL Guides, News, & Discussion] Zavon:
I was using .78SR5. I'm on .79 now + suhide.55

I'd imagine to pass the CTS checks you'd need a kernel that patches for SafetyNet check. I believe Franco's has this, not sure though just got my pixel xl 2 days ago.

Was able to use rootswitch and even signed up to PoGo just to test. PoGo worked fine. I also pass SN checks with rootswitch.
[Google Pixel XL Guides, News, & Discussion] Fenny:
I could apply the patch to the files from your phone, but in your case, root is not systemless, which means suhide won't work even with the socket whitelist check patched.

Yes, suhide alone is not enough to pass.

Make sure you are adding the PID of apps that need to be hidden from (you can use suhide GUI), and toggle root off with root switch whenever you want to use an app that detects it.

Since chainfire's last release, safetynet updated to check the path variable and look for signs of su. That is why you need things like rootswitch.
[Google Pixel XL Guides, News, & Discussion] SimplyCity:
My good man! I do have systemless root, on MM and on N beta, too. If you are interested in how to, I could guide you with pleasure. If you are so kind and would try with my libs, I could check, if applied, give proper results. Here you go:

https://mega.nz/#!EtQVAQxI!OlWWX588E6WwCD6NedUNl___3hD2l3uzx5EXRrHWq6U

Thank you!

Echoe™ team member / S7E
[Google Pixel XL Guides, News, & Discussion] Fenny:
Your files do not appear to reference the socket whitelist, so it looks like there is nothing to patch.

See this commit:

https://android.googlesource.com/pl...8be33b0bedec211708c4525b9d3f3b4effb385c^!/#F0

The basis of my binary patches is to remove the function calls to

RuntimeAbort(JNIEnv* env, int line, const char* msg)

and remove a later reference to

gOpenFdTable

that was causing a crash.
[Google Pixel XL Guides, News, & Discussion] Souler19:
Is there any chance you could write up a step by step guide for those of us who are less experienced? My goal is to get root and Pokemon go working on my pixel xl Verizon 7.1.1
[Google Pixel XL Guides, News, & Discussion] JAYNO20:
I believe he is working on a guide.
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
Rootswitch is not in the play store. It's in a Taiwanese Asus Zenfone forum. It's linked somewhere
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Yes I know, but I found it directly on Google without subscription. Sorry but I dislike no-ASCII web

Edit: to be clear, I said "from Google", not "from Play Store"
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Sorry for the topic drift, but I haven't gotten any answers from the TWRP thread. This mod works fine with TWRP 3.02 RC1 and SuperSU 2.79, but I'm getting a bootloop with TWRP 3.1 RC2 and SuperSU 2.79. Has anyone gotten this to work?
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Just flashed TWRP RC2 over TWRP RC1 and everything working great here.

Have you reflashed SuperSU 2.79 just after flashing TWRP RC2, before reboot ?
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Yes I did. Are you saying it worked for you without reinstalling SuperSU 2.79? I thought it was required to do both before a reboot.
[Google Pixel XL Guides, News, & Discussion] billiepreks:
No, sorry if my bad english confused you. Here is the step by step:

1- flashing TWRP RC2

2- flashing SuperSU 2.79

3- reboot

That's all :cowboy:
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
This was after doing flash-all of the March NOF27B release. I fastboot booted the TWRP 3.0.2 RC1 img, installed TWRP RC2 and SuperSU 2.79 before rebooting and got the bootloop. I guess I'll do another nandroid backup and try installing them from the installed TWRP 3.0.2.
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Arf, don't know for NOF27B, i'm on latest PN so still on NOF26W
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
Indeed, you did. I stand corrected.

---------- Post added at 07:39 PM ---------- Previous post was at 07:29 PM ----------

@Fenny - As suhide is completely unsupported by Chainfire and has not been updated by him for some time, do you think he would allow you to take over the project? Or go unofficial with it or something?
[Google Pixel XL Guides, News, & Discussion] Fenny:
Suhide is closed source, and chainfire explicitly forbids redistribution. I have half a suspicion that the reason we don't see an update publicly is that chainfire got tired of having to "fix" it. Plus, that all smacks of *effort*.

I am personally happy to wait to see what happens with magisk and magisk root before building my own implementation of the haploid/diploid rootkit from suhide. There is some real potential with magisk since it is open source.
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
Yeah, Magsik / MagiskSu is great. Was using it on my 6P.
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Perfectly works here on PureNexus NOF27C with NOF26V patched files, thanks !
[Google Pixel XL Guides, News, & Discussion] tdct12:
how??? I have suhide on PureNexus NOF27C with supersu stable 2.79/elementalx kernel and I can't pass safteynet attest. I'm trying everything :<

Also life pro tip. After you hit "lets go" in the initial setup screen from a full wipe, starting in the top left corner quickly tap all corners in a clockwise motion and it will skip setup wizzard =)
[Google Pixel XL Guides, News, & Discussion] billiepreks:
Install Rootbeer from Play Store for founding where is the problem
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I saw no mention of rootswitch? you need that to disable root.
[Google Pixel XL Guides, News, & Discussion] TheBobMiller:
Yes you need that to disable root. Here is the link https://www.asus.com/zentalk/tw/thread-173542-1-1.html Once you get it you'll have to flash suhide remover and then grant it SuperSU permission in order to keep your phone from always allow mode in SuperSU. Then just reflash suhide.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Lol I was telling him he needed it. I guess I could have worded it better
[Google Pixel XL Guides, News, & Discussion] tdct12:
Sorry, no I had rootswitch. I tried very, very, very hard to get this to work. Literally did like 8 clean installs, tried everything in this thread, and probably in any thread ever haha. Well not withstanding the last reply's recommendation, I had already just given up and restored stuff by the time he posted. It was probably maybe elementalx judging by some other comments, but I wasn't willing to give up that kernel. Love it too much. Oh and from my billion flashes I have another LPT tip. Sometimes installing systemless SU and certain system modifications requiring reboot while on twrp RC2 will cause a "bootloop" (automatically boots to twrp) From twrp switching the system partition, rebooting with no OS installed (loops back to twrp) switching the partition back, then rebooting system will end the bootlop. Don't know why, but might save someone some clean installs.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I just did it on the latest pure nexus using the guide I posted. https://xdaforums.com/showpost.php?p=70580883&postcount=260 you need to us the NOF26V files in the OP
[Google Pixel XL Guides, News, & Discussion] tdct12:
I followed your guide verbatim so I'm going to assume it's elementalx causing it to fail. Thanks though =)
[Google Pixel XL Guides, News, & Discussion] 420SYN:
I'm using elemental x so that's not your problem
[Google Pixel XL Guides, News, & Discussion] 420SYN:
magisk finally works no more of this nonsense. Thanks for your​ work on this though OP.
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Do you have a link? I see nothing mentioned of Magisk working on either Pixel in the Magisk threads I'm following.
[Google Pixel XL Guides, News, & Discussion] LazerL0rd:
Could this be done on ANY device? I'm thinking of trying it for my Nexus 5X on Android O.
[Google Pixel XL Guides, News, & Discussion] 5.1:
[MENTION=522448]Fenny[/MENTION]: hoping you don't mind I post a link to something unrelated to the subject of your thread. No offence here... :)

Maybe try with this one:

https://xdaforums.com/showpost.php?p=71573863&postcount=1029

Good luck... :good:
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Yes that's the file I used. Here are the instructions I followed someone posted in the PN thread.

Flash-all 27c (no wipe)

Fastboot boot TWRP

Flashed TRWP RC2

Reboot Recovery

Factory Reset

Flash PN

Flash TWRP RC2

Reboot System

Setup

Reboot Recovery

Flash Magisk

Flash TWRP RC2

Reboot System

Failed Safety Net, Passed Magisk root

Enabled Magisk Hide

Reboot System

Passed root and Safetynet

Restored Apps from TiBu
[Google Pixel XL Guides, News, & Discussion] 5.1:
Google it...

"Magisk Pixel XL" should help
[Google Pixel XL Guides, News, & Discussion] Fenny:
I don't mind even a little bit. :D

I was able to get this working with the stock ROM (I.E. Not AOSP/CM).

Steps:

1. Flash to stock. (Wipe not required if already on stock-based rom)

2. Fastboot TWRP.

3. Flash TWRP RC2 (RC1 will not work because the kernel detection will fail.)

4. Reboot to Recovery.

5. Flash a kernel that hides the bootloader flag, I.E. (STOCK WILL NOT WORK -- the magisk patches will fail).

6. Flash the above Magisk zip.

7. Flash TWRP RC2 AGAIN -- This is important, otherwise you will have no (bootable) recovery at all, and will boot without magiskSU enabled.

8. Reboot, enable magisk hide, profit?

I am going to test with magisk for a bit. If it is stable enough, I may not maintain these patches unless people request updates.
[Google Pixel XL Guides, News, & Discussion] 5.1:
Personally, I don't need to hide Root. I don't use Android Pay nor do I play Pokemon, Mario and the likes... :P

But looking at your OP, it sounds like it took you a lot of time to achieve this goal reversing all those lines of codes!

You developers never cease to amaze me! :good:

Cheers...
[Google Pixel XL Guides, News, & Discussion] rockingondrums:
Thank you, I'll wait for your testing results as I'm not doing anything until Magisk works haha. I don't want to flash a bunch of ROMs on this phone. Just want one set up with passing safety net that works. I think the only ROM I'd be interested in is Lineage. Quick unrelated question: does running Lineage on XL cause issues with Photos backup?
[Google Pixel XL Guides, News, & Discussion] Fenny:
Magisk appears to be fairly stable at the moment. I am watching the pull request on GitHub for inclusion into the official codebase. If you install using the linked version, don't update in the app for now. Until that pull request is merged, the boot image patcher will fail on update.
[Google Pixel XL Guides, News, & Discussion] ScottIsMyName:
I have only been on it for about 2 days now, but it seems very stable to me as well on Pure Nexus rom.
[Google Pixel XL Guides, News, & Discussion] xocomaox:
I've been using Magisk on Dirty Unicorns (latest build) for Pixel XL and it is great. Android pay working well.
[Google Pixel XL Guides, News, & Discussion] anuraj1:
So... anyone try the latest patch on 7.1.2 yet? Or should I risk my wife's wrath and be the guinea pig? :D
[Google Pixel XL Guides, News, & Discussion] drxikh:
I'm on the latest 7.1.2 E with Magisk and working fine. Didn't try this suhide method though. Apologies if I'm off topic.
[Google Pixel XL Guides, News, & Discussion] pWEN:
I followed these steps, and after flashing Magisk and then TWRP, it only boots into TWRP. I reflashed PureNexus, booted into system, rebooted into bootloader, loaded the TWRP RC1 image, then flashed RC2. Still reboots into TWRP directly when trying to boot into system. Did Magisk do something to change what loads for the system image? I'm not sure what I might have done wrong.

Edit: Okay, I completely flashed the phone back to stock on both slots (NOF27B). Then from slot A I followed the instructions again (which inevitably put me on slot B from the way PureNexus installs). It's working now! I think the issue before may have something to do with having SuperSU installed when trying to do Magisk, but I'm not sure how that would have told TWRP to become a system image. I thought Magisk would uninstall SuperSU first, but maybe it couldn't. So this time I skipped installing SuperSU. I've also not reinstalled ElementalX; does anyone know if it would be okay to flash that (v1.08) after installing Magisk? I don't want to have to start over again.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Magisk 12.0 seems stable. I used the same steps as above, but the su symlink was missing and I had problems with root initially. The following fixed it:

adb shell
/magisk/.core/bin/su
cd /data/magisk
ln -s /magisk/.core/bin/su
[Google Pixel XL Guides, News, & Discussion] xocomaox:
I'm certain that was the issue. You had SuperSU installed before which was screwing up how the hone booted (after flashing Magisk on top of it). The same thing happens if you flash a newer build of TWRP over an older build, which SuperSU is installed.

Glad it's working for you now, I was too late to reply to you letting you know what was wrong.

You can now flash EleX 1.08. It will not give you all the options it normally does in the AROMA installer, but make those changes (like sweep up to turn on screen) in the Elemental X Kernel Manager app.
[Google Pixel XL Guides, News, & Discussion] pWEN:
Ah, didn't know about the TWRP/SuperSU conflict. Thanks for the clarification!
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
I had been using this libandroid_runtime patches with SuperSU 2.76, but wanted to switch to this with the 7.1.2 release. I uninstalled RootSwitch, ran suhide-v0.55.zip, UPDATE-unSU-signed.zip, and then fastboot flashed 7.1.2 N2G47E with "-w" removed for step 1. Then I followed steps 2-5, but v12 fails to install for step 6.

I'm probably missing something simple. Magisk v11.6 will install but v12 says it failed to mount /system. Do I need to undo the libandroid_runtime changes or is there something else I'm missing?
[Google Pixel XL Guides, News, & Discussion] Fenny:
Which kernel are you flashing? You could try mounting system manually before starting the flash. Additionally you can try deleting

/system/magisk, /data/magisk, and /data/magisk.img from recovery (The first two are folders, and the third contains your magisk modules and settings).
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Thanks for your reply! I don't know how I missed it, but I was trying to install Magisk-v12.0.zip instead of Magisk-v12.0-Pixel.zip! The correct file installed with no problem, imagine that!

For anyone else in the same boat, here is the direct link to Magisk-v12.0-Pixel.zip: https://drive.google.com/file/d/0B1xZ4VKT4JKZUFhVUlk0enhBVFk/view
[Google Pixel XL Guides, News, & Discussion] yourmghq:
Hey just checking before I install magisk, but are you advising that it is stable enough that you plan to stop releasing patches to the libandroid files? Just checking before jumping to another ship.
[Google Pixel XL Guides, News, & Discussion] 420SYN:
Magisk is a million times better. You don't need to turn root on and off all the time
[Google Pixel XL Guides, News, & Discussion] stippLe:
Just so I get this right... I have 7.1.2E elementalX 1.09 superSU 2.79SR3

Can I just TWRP flash this magisk v12-pixel.
[Google Pixel XL Guides, News, & Discussion] drxikh:
I am no expert, but if you are trying to have root and pass SafetyNet, simply flashing Magisk with SuperSU installed might cause you to fail SafetyNet. I would suggest completely removing SuperSU and then try flashing Magisk. I believe the SuperSU App has a way to remove SuperSu completely.

Personally, I used the flash-all.bat on the latest Android version, while removing "-w" to have a clean slate (stock recovery and no root) while preserving data. And then performed the necessary steps to flash Magisk.

You also need Magisk manager, which I downloaded directly from Android Host not the one in the Play Store.

Of course before doing all this I would create a Nandroid. Good luck!

edit: github not android host
[Google Pixel XL Guides, News, & Discussion] stippLe:
ANDROID HOST? What version
[Google Pixel XL Guides, News, & Discussion] drxikh:
oops my mistake it was github.
[Google Pixel XL Guides, News, & Discussion] stippLe:
Thanks Bro. Pretty sure I was doing it right the whole time haha just didn't have that damn pixel version 12. WAS GETTING FRUSTERATED saved me.
[Google Pixel XL Guides, News, & Discussion] stippLe:
Only problem is now... Samsung pay still sees root. Use for gear S3
[Google Pixel XL Guides, News, & Discussion] mims1979:
So I installed 7.1.2 and went with magisk instead of using the modded files. Android pay, etc all work, but for some reason I can't modify anything in system, remove system apps, etc despite the apps having requested and granted superuser access. Rom toolbox, root browser etc can't actually modify anything. Something I did wrong?
[Google Pixel XL Guides, News, & Discussion] drxikh:
Did check Samsung Pay in Magisk Hide? Other than that I have no idea...

You need to set whatever system directory as RW.
[Google Pixel XL Guides, News, & Discussion] stippLe:
Yeah it is. Maybe there's another service or process somewhere

---------- Post added at 11:22 AM ---------- Previous post was at 11:20 AM ----------

Yeah I had same problem when I was trying to modify the build.prop for my hotspot. I just booted the recovering change the permissions of a dir thru terminal.
[Google Pixel XL Guides, News, & Discussion] xocomaox:
How are you able to do this?
[Google Pixel XL Guides, News, & Discussion] drxikh:
Somewhere in this thread there is a list of services that was suggested to add to SuHide. Maybe try adding those to MagiskHide

You can do what the guy above you suggested, changing permissions through the terminal. I used ES Explorer, which has an option to set folders to RW in the root explorer settings.
[Google Pixel XL Guides, News, & Discussion] stippLe:
Yeah after MagiskSU I didn't have permission to edit build prop thru terminal or thru Es editor. Wouldn't even let me modify the I permissions since whole did was read only. So I used recovery terminal.
[Google Pixel XL Guides, News, & Discussion] xocomaox:
I can do it through the browser in TWRP.. I have actually replaced YouTube.apk in system\app\youtube\ to a modified one this way.

I just didn't see a way to make that whole partition mount as R/W. I assumed it was a part of how Magisk was set up to avoid altering system in some way to keep the security clean.. I'll check out ES File Explorer. :good:
[Google Pixel XL Guides, News, & Discussion] Fenny:
Modifying system (without modifying system) is exactly what magisk was designed for. You can create a magisk package (installed to /magisk) that overlays your system modifications without actually modifying system.

P.S. my pixel has died a mysterious red indicator blinking death. Just got an RMA approved.
[Google Pixel XL Guides, News, & Discussion] mims1979:
I've tried factory resets, starting from scratch, etc. Nothing appears to make magisk stable for me. My phone just randomly locks up and requires reboot, so I guess I'm going back to supersu and suhide until there's an official magisk version for pixel.
[Google Pixel XL Guides, News, & Discussion] Fenny:
Hmm, could be the kernel. My pixel is currently out for repair. Can you tell me if the latest patch files are working for you? If not, let me know and post the new version of the libs so I can take a look.

I will update if people will use it.