yashsingh1/xdaforums huggingface dataset:
[Verizon Motorola Droid Turbo Q&A, Help & Troublesh] sgtaylor565:
I TWRP flashed http://xdaforums.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949.

Installed all of my apps and customised:

Gained root using the Beta SuperSU 2.62.

Used these http://xdaforums.com/droid-turbo/development/rom-mcg24-251-5-100-stock-t3512949/page3 post #29 to get boot right.

Titanium Backup removed the Google Play apps Books, Games, Newsstand, Movies and TV. Also Gmail, Google + and Photos (I use MEGA.co.nz for everything!)

Titanium Backup moved Nova Launcher to system and removed Launcher 3.

All of this worked using CF's 1.30 Lollipop build. No Google Play Services problems there.

Now, Google Play Services crashes all of the time. I've reinstalled the Google Play apps I removed before, but they're not system apps; I can hide them using Nova Launcher Prime. I could also do the same for Google+ and Photos. Don't really want to put Gmail back on, because AquaMail is that much better, and I don't want defaults competition.

Should I reflash the original, or just wait for CF to get his build better?

UPDATE: Reinstalled everything I removed, and re-enabled disabled Google-related apps. Google Play Services not crashing on reboot. So, is the real problem Google Play Services permissions that have to be modified by a developer or is it something else?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Stock Pixel/PixelXL Kernel + SafetyNet Patch

Current version:

android-msm-marlin-3.18-nougat-mr1

Suitable for build: NMF26U

Security patch level: January 5, 2017

I compiled the stock kernel for the Pixel/PixelXL (they both use the same kernel) and applied the SafetyNet patch by sultanxda. The kernel name says

marlin

, but this also works on

sailfish

. Google just created one kernel that works on both

sailfish

(Pixel) and

marlin

(Pixel XL) devices.

Use case for this kernel:

- If you want to stay completely stock, but have an unlocked bootloader, the SafetyNet is tripped which disables features such as Android Pay.

- This kernel is completely stock except for the addition of a patch that removes the SafetyNet check.

- If you do not have an unlocked bootloader there is no need to use this kernel. It's exactly the same as the kernel included in the stock builds, except with the addition of the SafetyNet patch.

Installation:

- Download attached .zip and unzip into a folder

- Reboot device into bootloader (power down device, then Power + Volume down)

- Connect device to computer

- Verify connection by typing 'fastboot devices'. Your device should show up (check serial number)

- Enter command: fastboot flash kernel <kernel_image>

- Once flashing is complete, enter command: fastboot reboot

- Disconnect device and wait for reboot sequence to complete.

- You now have a stock Pixel with an unlocked bootloader that can use Android Pay

**WARNING**

If flashing this kernel for whatever reason ruins your device, please don't hold me accountable. Use this at your own risk!

And otherwise, I'm not a professional developer, just a hobbyist. Please don't ask me for a ton of help, I only created this kernel because I want to run completely stock, but still use Android Pay while having an unlocked bootloader in case I ever decide to root my device in the future (am running a Verizon Pixel). I will try to maintain this kernel with each new release until I lose interest :)

Downloads:

NMF26U

All versions
[Google Pixel ROMs, Kernels, Recoveries, & Other De] joetheshmo:
If one wants to stay completely stock wouldn't they just keep bootloader locked?

Edit: nevermind seems like this will cater to Verizon pixel owners since you can't unlock the bootloader on latest build. Good job!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] iPwn_:
Yep, let's us unlock the bootloader in case we need it in the future, without committing to any mods or losing Android Pay just yet.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jay661972:
Stock + Safetynet patch.... Finally.

Thank you
[Google Pixel ROMs, Kernels, Recoveries, & Other De] shinesthru:
Thanks for sharing your work, OP.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] computercarl:
Any chance of you turning this into a flashable TWRP zip? Then I could run ElementalX and root when I want to, and flash back to stock if I want to, all from my phone, in a single reboot.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jay661972:
Just want to confirm that this is for Sailfish also. The name of the file is marlin and just want to make sure. Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
[MENTION=2044082]Sakete[/MENTION], I appreciate your attitude.... You need something, you just make it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Yes, it will also work on sailfish. Sailfish and marlin both use the same kernel. I installed it last night on my own Pixel (sailfish) and it works great, no issues so far (and am not expecting any since it's just stock + safety net bypass patch)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Your Verizon Pixel can be unlocked and rooted, yet Android Pay works. What else can you want, right?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jay661972:
You are right there should have no issues at all since the change was the safetynet patch.

Thanks for this..
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Android Pay will not work with root. This only enables Android Pay to work with an unlocked bootloader. If you root your phone as well, Android Pay will not work.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Sure it does. AP works on both of my Pixel and Pixel XL. Here's the trick. Well, actually, it's no trick, but it's something I remembered from 6.0. With 6.0, you could temporarily unroot, add cards in AP, then resume root. You have to add your credit cards in AP prior to rooting.

In the beginning, I rooted first, then AP couldn't get past the Add Card screen. I flashed back to 7.1.1 stock, install your (or any) SafetyNet-bypassing kernel. That gets AP working (allows me to add cards). Then re-root.

If screenshots are needed to demonstrate this, I can do that, but that seems rather childish.

---------- Post added at 12:20 PM ---------- Previous post was at 12:15 PM ----------

Here goes, unlocked BL + rooted + Android Pay. Screenshot of my multitask screen.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
That's good to know. If I ever decide to root my device, this will be my workaround (and since I already added my card I should now be able to root it without incident regarding Android Pay).

Thanks for sharing!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
No, thank YOU for the kernel.

One item I must mention. That is, AP will break if you disable login security, or even just changing from PIN to password, or anything that would normally require a reactivation of your Android Pay credit cards. Then you just need to reflash the kernel, which in essence kills root. Add back AP, then reroot.

... Of course, Google can always implement another layer to circumvent this workaround in the future. But that's what makes Android fun.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bytethegroove:
thank you for this kind sir.

*next on my list is a deodexed stock 7.1 so i can start themeing this device...

time to bring BuuF back :)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] pigmoose:
Doesn't work for me. I unlocked my VZW Pixel with depixel, took the OTA to 7.1.1, but when I flash this kernel it reverts me to 7.1, and lots of stuff is broken like the soft key buttons stop functioning. Gotta factory reset...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Odd... that isn't supposed to happen. Were you rooted when you flashed?

And did you by chance take the OTA for NMF26Q? This kernel is for NMF26O, might not be compatible with the Q build. Haven't created a new kernel yet, will probably just wait for the January update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] autoprime:
almost sounds like the active slot got swapped from A to B or B to A. When that happens the previous update boots instead of the current build.

the active slot can be changed in bootloader w/fastboot.

I believe the command for that is:

1. fastboot set_active _a

or

2. fastboot set_active _b

depending on which slot you want active.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Archangel:
I assume that we can flash this over a custom kernel no problem in order to go back to stock?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
This is a "custom" kernel since it's been modified.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
You can try, no guarantees though.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Forgive me for being so naïve, but I am not extremely familiar with SafetyNet, outside of the basics. If these kernels patch SafetyNet, why would it still be tripped if we are rooted? It is my understanding that this patch will allow you to have an unlocked bootloader, but not be rooted. Why is this so?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
I think you're jumbling up several unrelated components of a secured smart device certification. First, the bootloader: OEMs, Google/Apple, and carriers negotiate to approve certain OSes to be run on their given devices. Within their guidelines and compliance processes, they release OSes that they believe cannot be exploited by unscrupulous groups or individuals. To that end, they lock the bootloader as to not allow uncertified, unverified OSes. To most of us, that's simply an innocent custom ROM to theme our phones, or a custom kernel to overclock them, or to run certain software not approved by Google/Apple. However, with a bootloader unlocked, thieves can install/embed malicious codes to steal financial data. Google introduced SafetyNet with Marshmallow to verify that a phone has not been tampered with. Google also knows full well that not all phones, in all markets, run Marshmallow or later. Only newer phones running later OSes have SafetyNet attestation capability. Google only put this SafetyNet restrictions on certain devices running certain OSes. These patched kernels simply remove our Pixel from being recognized as a device on that SafetyNet required list. You can make the kernel yourself, it's not difficult. So, while Google knows we've bypassed its SafetyNet verification (because it flashes the warning every time we boot the damn phones), at the moment, it chooses not to disallow it completely due to the reason expressed earlier (too many different devices not running the latest OS). I hope that answers your question "If these kernels patched SafetyNet, why the warning is still there?" Furthermore, our phones periodically report back to Google what OS, apps, drivers they currently use. (I believe it's once a week, or bi-weekly.)

Two, super user permissions, or root: If the good guy can assert high privileges to block ads, the bad guy can also utilize those same privileges to send our credit card data to a private server. While an unlocked BL allows us to run unverified OSes, root allows apps to execute at a level beyond what Google deems safe. You can have an unlocked BL, an app can still refuse to run because your phone failed the root test. Many banking apps check root status before they execute. This was why I said earlier that you were intermixing an unlocked BL with the act of rooting. They can be independent of each other. You can have a rooted phone with a locked BL. The Pixel and Nougat, with increased security for the /system partition, has made it difficult to root without first unlocking the bootloader. If we can't root it by imposing superuser permissions in the system partition, we'd have to attack the boot image, hence systemless root.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
Thank you for all of that helpful information, but I believe you are mixing my questions up with someone else's. I fully understand bootloader, root, and the differences between the two. The question I was asking, was comprised because of a statement made earlier in this thread. Someone stated that while this patch will allow you to run AP with an unlocked bootloader, if you you are rooted, it will not. I am wondering why that is the case. If the patch allows your device to be 'exempt' from safetynet, then root should not affect that. Unless, AP checks for both safetynet and root status
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
Yes, AP checks for both. At the beginning of Marshmallow, it only checked for SU. And we got around that. Google now added another layer with SafetyNet. And we're overcoming that as well, with these custom kernels. Eventually, G will add another layer, when the majority of phones use Marshmallow or Nougat. It never ends.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
And is there currently no way of hiding SU? Even just for a specific app or set of apps?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
No longer able to hide SU (not yet anyway) because of higher security in /system. We're just fortunate that most apps are not checking for root status. Simple as that.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ansontyl96:
Just flash this kernal on my pixel without root but it seems that saftynet could not be passed
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
See if AP works. That was the main purpose of this patch I applied to the kernel. I did not create the patch (I linked the original creator in the OP), just applied it.

The patch does this:
[Google Pixel ROMs, Kernels, Recoveries, & Other De] jay661972:
It works on mine,
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
What about the idea of making this flash able?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
By flashable, I assume you mean a flashable zip using TWRP? Probably not gonna happen as I don't have TWRP so no way for me to test if it works properly. Feel free to download the kernel and create your own flashable zip though.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
Check PM
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
I think I got something in the form of flashable...

Haven't tested the idea but using FlashFire, flash the zip.

If you want to revert use TWRP.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] wy1d:
Have you actually tried paying with AP with this setup? I unlocked, flashed the kernel, added cards in Pay and then rooted as you said but when I went to use it, I got the "This device cannot be used with Android Pay" message presumably because the root check occurs at each transaction.

I didn't think there was a way around it.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ansontyl96:
Yea I have the same result as well
[Google Pixel ROMs, Kernels, Recoveries, & Other De] je2854:
Any update patch for 6Q?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Q uses the same kernel as O, so nothing to update. Q was just an update for some European phones I believe to address some modem issues, otherwise it's the same as O.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] smohanv:
How about returning to stock. I could stock boot.img is 24mb compared to this patched kernel size which is 18mb. Also, the file within the zip file has no extension hence we may have to rename with img extention, I guess.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Just to clarify, this file is

not

a boot.img, this is just a kernel binary. Do not confuse the two. If you flash my file in the boot slot, you will get a boot loop, or worse, brick the device. You don't have to rename anything, just follow the instructions in the OP and you'll be fine.

And if you want to return fully stock, then just flash the stock boot.img.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] smohanv:
Thanks. I just flashed as mentioned in your OP though it confused me a little. All done and my AP works.

I cannot live without root. There may be a solution here or elsewhere to have temporary unroot when AP is launched.. I have no idea if it is achievable.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sravanz:
hi

i am using this kernel but otherwise stock not rooted. Today i got a software update but when i try to install it says failed. Any work around for this?

Do i need to flash back stock kernel and then update and flash your kernel again or is there any other way? Appreciate your help.. Thanks
[Google Pixel ROMs, Kernels, Recoveries, & Other De] JimboLodisC:
You quoted the instructions to do this in your comment...
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Yup, like you said. OTA only works when fully stock.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Update for NMF26U in OP

An updated kernel suitable for the NMF26U build is available. Includes the January security updates, along with the safetynet patch of course.

Download link is in the OP.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] lazinase:
Thanks for the quick update!

I managed to have both Android Pay and Root, thanks to your kernel patch!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
AP, unlocked BL, and root? All working?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] bush911:
Nope, system must not be rooted. I have tried two slot, one root one unrooted +safetynet patch kernel,

bank app works fine, but something wrong with the userdata, this leads me can't access quick settging and developer options etc.

Maybe in the near future, someone will figure it out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sravanz:
Can you please provide the NMF26O stock kernel for pixel?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Just flash the stock boot.img from NMF26O.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Haz3:
Can/has anyone got this to work with PN ROM?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] computercarl:
Yep, works great. 5+ SOT, ~15-20 hrs total from unplugging to ~15% battery left.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Skitals:
I just installed PN and it passes SafetyNet test in SafetyNet Helper, so it looks like the included kernel is already patched.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] driz:
Here is my story.

Part 1 - failure

Pixel with latest OTA and rooted.

Flashed the kernel, went into a bootloop. likely due to taking the latest OTA or something, no biggie.

Part 2 - Success

downloaded the stock image for NMF26U

flashed it to the device.

flashing the kernel patch

rebooted

activated fi and downloaded my apps

safetynet check - https://picload.org/image/rorlwrpa/sncheck.png

android pay - added two cards successfully

Part3 - Partial success

root device - success

verify AP - just purchased lunch with AP

verify SN pass - fail with response payload validation fail even after hiding root

sailfish:/ $ su

sailfish:/ # id

uid=0(root) gid=0(root) groups=0(root) context=u:r:init:s0 <--normal root

sailfish:/ # exit <-- disable root in supersu

sailfish:/ $ su

/system/bin/sh: su: not found

Interestingly, when hiding "root" in supersu, the su binary is not found on the shell, but apps can still successfully request root access (tested with better battery stats)
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ansontyl96:
So you manage to get saftynet pass with root?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] driz:
i guess "after work" was unclear

i mean, i'll do it after work and provide updates :)

completed test on original thread.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mngdew:
dang, that's a looooooooong shift.:D
[Google Pixel ROMs, Kernels, Recoveries, & Other De] driz:
The rough life of a consultant! I cry myself to sleep!
[Google Pixel ROMs, Kernels, Recoveries, & Other De] mpappas87:
Do you think this will work with NDE63P? I know it's not the model number you mention but are there hardware differences between the models or is it just one was made for verizon and one wasn't?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] maflin18:
To be clear: has anyone gotten AP to work reliably with unlocked bootloader AND root?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] robotnikz:
Yep, working here on Stock Rom, installed TWRP and rooted.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
I have no idea.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sir_Bruce_Lee:
Does this with Feb / NOF26V?

If not, anyone have an updated version?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Question for other devs

Anyone know which kernel version is included in the latest February update for Google Pixel? I built this kernel off of android-msm-marlin-3.18-nougat-mr1 but looking at the source tree I see there is now android-msm-marlin-3.18-nougat-mr1.3

I'm trying to figure out which kernel would include all the latest security patches, not really clear by looking at the source tree. That way I can create an updated kernel for the Feb update.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] sosquidtaste:
I'm not sure if this is what you were asking, but I've just sideloaded the OTA .zip and finished booting into the February 2017 update. Settings --> About Phone --> Kernel version reads:

3.18.31-g367e645

android-build@wpiv1.hot.corp.google.com #1

Wed Dec 7 23:10:51 UTC 2016
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Razor1973:
One I must use for work (Good Mobile, recently renamed BlackBerry Work) does, unfortunately. As far as you know, there is still no solution to hide unlocked bootloader and root for our Pixels yet. Or is there?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] quangtran1:
I've been busy with several projects that I haven't kept up with this. There were some noises with suhide that you may want to check out.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] uodii:
What root are you using? And are you sure AP actually works? Can you add a card and also make a purchase?
[Google Pixel ROMs, Kernels, Recoveries, & Other De] ipeedalil:
Is there anyway that the safety net patch and/or this Kernel could be made into a zip flashable in twrp
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Nateg900t:
With each of the last two monthly security updates, I've come back to this thread to grab an updated stock+safety net patched kernel to re-apply after doing a full reload without data wipe. Does anyone know if the February update requires a new kernel, and if there are still plans to update/replace it?

Edit: Oops, I see that Sakete is the original thread author and is working on trying to rebuild for the february update per the post above with questions about compiling it. I will eagerly await any updates.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
Yeah sorry, been busy with work, haven't had time to deal with this yet. Maybe sometime this week.
[Google Pixel ROMs, Kernels, Recoveries, & Other De] Sakete:
No more updates for now

Just wanted to let you all know that I will no longer be maintaining this kernel. I don't really use Android Pay at all, I've come to realize, so for me it's not worth the effort to build a kernel each month.

It's fairly easy to do yourself though, all the information is out there. I can give some pointers if you'd like. Most importantly, you'll need a Linux machine.
[OnePlus 3 Questions & Answers] M.Dinesh:
Is There a Pure Nexus Rom For Op3??
[OnePlus 3 Questions & Answers] Prattham:
No
[G3 Developer Discussion [Developers Only]] dandu3:
I saw the demo on the Windows YouTube channel. It was Windows 10 Enterprise running on SnapDragon 820, running extremely smoothly, also with full x86 Photoshop running and all.

Does anyone have any info on that version of Windows? Would it be possible to make that run on the 801 from the G3?
[G3 Developer Discussion [Developers Only]] Shady282:
wow, that is amazing if possible, please share video, if possible,
[G3 Developer Discussion [Developers Only]] dandu3:
https://www.youtube.com/watch?v=A_GlGglbu1U