yashsingh1/xdaforums huggingface dataset:
[Google Pixel XL Guides, News, & Discussion] firewave:
In SuHide, add GSF.
[Google Pixel XL Guides, News, & Discussion] madmaverickmatt:
Good Afternoon All.

I tried to run this, but coming from a clean install of the June build Im getting this error when flashing Magisk in TWRP;

Updater process ended with ERROR:1 Error installing zip file 'sdcard/Magisk-v12.0-pixel.zip.

Thoughts?

Thank you
[Google Pixel XL Guides, News, & Discussion] pcriz:
Are you flashing with rc2?
[Google Pixel XL Guides, News, & Discussion] madmaverickmatt:
I was not. Thanks. I found that on Reddit just a minute ago.

now im just trying to get past the safety net check Im getting CTS Profile mismatch.

Back to teh forums with me lol.
[Google Pixel XL Guides, News, & Discussion] pcriz:
Did you turn on Magisk Hide in Magisk Manager settings?
[Google Pixel XL Guides, News, & Discussion] madmaverickmatt:
lol, Yep. Literally just found that too.

Thank you again. ;)
[Google Pixel XL Guides, News, & Discussion] c7j8d9:
I have tried these steps many times and get the dots just dancing across my screen never booting up. Using rc2, June and elemental 12. Any suggestion on order of flashing? Sucky part is I had it working when I first updated from may but I tried the art optimization module and got bootlooped. Starting over I have not been able to get it working again.
[Google Pixel XL Guides, News, & Discussion] firewave:
I have yet to test with elementalx 12, but even if it's auto-sign, I think it would lead to bootloop when firstly restarting TWRP. I will test this ASAP.
[Google Pixel XL Guides, News, & Discussion] firewave:
Just tested it, and I can confirm that it works flawlessly with June update and ElementalX-PXL-1.12
[Google Pixel XL Guides, News, & Discussion] c7j8d9:
Ran art optimization uninstall and wiped dalvik/art cache and it installed again! now it says not rooted but magisk is install. no option for hide magisk.

Edit: Missed a step. Followed steps exactly and works perfect. Must have been the art cache. Thanks OP!
[Google Pixel XL Guides, News, & Discussion] GillRigged:
Did you start completely over by flashing the latest image and no trace of SuperSU root? I believe Magisk has its own Busybox but I still use Busybox Pro.
[Google Pixel XL Guides, News, & Discussion] GillRigged:
This again worked for me. Started using Magisk and ElementalX last month when the 2.80 SuperSU broke root. Was pleasantly pleased with being able to use Android Pay with my PXL... Along with the Netflix issues.
[Google Pixel XL Guides, News, & Discussion] firewave:
I'm glad it's working for you too! Thanks for the reporting!
[Google Pixel XL Guides, News, & Discussion] firewave:
Thanks for the reporting!
[Google Pixel XL Guides, News, & Discussion] nikpoth:
I followed the steps and everything works perfectly!

Have you tried magisk modules?

https://xdaforums.com/apps/magisk/collection-magisk-modules-v2-t3575758
[Google Pixel XL Guides, News, & Discussion] pcriz:
I'd highly caution you because very few work with the pixel and quite a few will cause you to bootloop. As in factory reset your device boot loop
[Google Pixel XL Guides, News, & Discussion] c7j8d9:
I see the arise module is working on some roms. Anyone get it working on stock? and is substratum possible?
[Google Pixel XL Guides, News, & Discussion] pcriz:
Substratum has more limited functionality but works. Never tried arise on stock.
[Google Pixel XL Guides, News, & Discussion] Juzman:
The only issue I find with Magisk and EX is you don't have option for gestures and stuff when installing the kernel.
[Google Pixel XL Guides, News, & Discussion] pcriz:
https://xdaforums.com/pixel-xl/development/kernel-stock-kernel-safetynet-patch-t3588154

You can fastboot the patched stock kernel..
[Google Pixel XL Guides, News, & Discussion] Juzman:
I'm running PureNexus. What I mean is "sweep to wake" etc when flashing EX with Magisk. With SuperSU, the gesture options are all there and work fine.
[Google Pixel XL Guides, News, & Discussion] pcriz:
So the additional gestures added by the Kernel. Yes that's been one of the sacrifices of going the magisk route since day one.
[Google Pixel XL Guides, News, & Discussion] sruel3216:
just use the app
[Google Pixel XL Guides, News, & Discussion] Juzman:
Doesn't have "Gesture" option with Magisk.

Ended up going back to SuperSU. :)
[Google Pixel XL Guides, News, & Discussion] filotti:
I have my Pixel XL rooted just for AdAway. Lately I've been having issues downloading Netflix from the play store and logging in to Snapchat.

I was able to follow your instructions, however I'm experienced in installing custom roms and using fastboot and ADB. I was on the May update, with a bootloader unlocked Verizon Pixel XL, rooted with Chainfire's boot to root and SuperSU.

SafetyNet is passing and I was able to download Netflix from the Play Store and log in to Snapchat.

For anyone already rooted with SuperSU I would suggest running a full unroot from SuperSU and uninstalling the app before flashing.

Thank you, you saved me a lot time investigating how to root my phone with Magisk.
[Google Pixel XL Guides, News, & Discussion] firewave:
EX is no way linked to Magisk, and you should be able to use another kernel. But keep in mind that 1 of the 3 safetynet controls implies a call to the boot loader. This call is made by the kernel. For compatibility, Android accept that AVB is not implemented in the bootloader. So the trick is to patch the kernel to answer No_AVB_Present to any request.

So I suggest EX because I know it is AVB patched, but you could use any patched kernel, or patch yourself :cool:

Here is the patch made by sultanxda https://github.com/sultanxda/androi...bc05b16bbd33521c2fffaf491c5657a94bfcfc5.patch
[Google Pixel XL Guides, News, & Discussion] pcriz:
Pretty much every custom kernel in the pixel forum is patched plus the patched stock kernel.

I was responding to the statement about losing gestures that might make users think they lose stock gestures if they aren't familiar with EX.
[Google Pixel XL Guides, News, & Discussion] firewave:
I also can confirm it's working great on Pure Nexus too.
[Google Pixel XL Guides, News, & Discussion] diabl0w:
lol I've seen this done by multiple ppl, so strange
[Google Pixel XL Guides, News, & Discussion] pcriz:
Probably because

1. It's a reputable source

2. It's easy to choose what version if you don't want the most up to date for whatever reason

3. Don't have to follow three different links or read through broken tags (looking at you arise and XDA labs) just to download an apk.
[Google Pixel XL Guides, News, & Discussion] diabl0w:
reputable source ? really ? first time I've heard that
[Google Pixel XL Guides, News, & Discussion] pcriz:
Give me a source that states otherwise please? You can read the mission statement on their site, obviously it could be bull, you can do a hash check of one of their apks compared to an extracted one from the play store and see if they line up.

They dont offer paid apps for free, they don't offer modded apps, a ton of sites from Droid Life to Android Central have used their links. They mirror whats in the playstore, the exact same apks signed. You may even check back in a few weeks and see Magisk is no longer there because its no longer in the playstore, like they did with adaway.

Here help yourself and read up on why it exists: http://www.androidpolice.com/2014/11/19/meet-apk-mirror/

Also just because you haven't heard of something, doesn't mean it isn't true.
[Google Pixel XL Guides, News, & Discussion] diabl0w:
ayeee calm down captain don't take it so personal... enjoy you're third party apps I'll be getting mine from the source . I'm not that lazy where I can't handle a couple extra clicks to ensure my phone is secure
[Google Pixel XL Guides, News, & Discussion] pcriz:
Everyone is welcome to get them where they like, I just find it ironic that people question OPs choice in links without looking into it at all. Not to mention in a thread about downloading a zip file that can give root access from a google drive location modded by a guy you neither know nor is a recognized dev.

But the source of where you get Magisk Manager is where you get concerned. That's just a tad ironic no?

BTW by definition any application not preinstalled or downloaded from the Play Store is technically 3rd party.
[Google Pixel XL Guides, News, & Discussion] diabl0w:
lmao brotha where the hell do you get your definition of third party that says getting an apk directly from the developer is a 3rd party source ? thats unreal... also i think you needa find some new parents cuz yours obviously never taught you what happens when you assume... I never said I didn't have problems with any other links, I never said that just because I never heard something makes it not true, I never said a bunch if the things you're assuming so get you're head out of you're a$$ amd stop making **** up in you're head. I feel like you woke up today angry and thought that coming on xda and talking **** would make you feel better bigguy, you're palms have probly been sweating waiting for me to respond , I don't have time to entertain you're ignorance and I hope you got you're arguing fix in, loser
[Google Pixel XL Guides, News, & Discussion] pcriz:
I got my definition of third party software from: http://www.dictionary.com/browse/third-party-software or https://www.merriam-webster.com/dictionary/third-party

But you are entertaining my ignorance?

Have a good one, if I was having a terrible day its slightly better now lol.
[Google Pixel XL Guides, News, & Discussion] firewave:
What matters, and you're right pcriz, is that I need to publish a regular patch for Pixel XL of the Magisk tree. That way, anyone would be able to patch it, even Magisk owner.

I plan to do it so ASAP.
[Google Pixel XL Guides, News, & Discussion] micmars:
The gentleman with whom you're corresponding is absolutely right.

He's also extremely helpful, and needn't be insulted or denigrated.

If you have an issue with him, it'd be wise to take it to PM.

Sent from my Pixel XL, #WhiteUIsMustDie, #EndDarkAppOppression
[Google Pixel XL Guides, News, & Discussion] twistanesh:
Thanks

Hey OP thanks for the walkthrough, I was able to get it to work coming from the May build with su
[Google Pixel XL Guides, News, & Discussion] 640k:
looks like google updated safetynet and the pixel xl no longer passes CTS profile.
[Google Pixel XL Guides, News, & Discussion] pcriz:
On stock? I'm still passing, im on Pure Nexus June build with a June base. Rooted with Magisk 12.

Nevermind, I'm not passing
[Google Pixel XL Guides, News, & Discussion] 640k:
using the elemental kernel+"unofficial" magisk 12.0 method on stock ROM.
[Google Pixel XL Guides, News, & Discussion] pcriz:
I updated my post, Im not passing, I was last night.
[Google Pixel XL Guides, News, & Discussion] pcriz:
Turned on magisk core only and I am passing again
[Google Pixel XL Guides, News, & Discussion] marc.ientilucci:
does this method include any root apps like SuperSU or the magisk root app?
[Google Pixel XL Guides, News, & Discussion] pcriz:
You have to use Magisk Manager
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
I see in this post: https://xdaforums.com/showpost.php?p=71658118&postcount=19 that topjohnwu introduced, "Core Only Mode. It can be enabled in the new Magisk Manager."

I am running Magisk-v12.0-Pixel and Magisk Manager 4.2.7, but I don't see core mode as an option. Is that in a new version or is it "Disable Magisk" in Settings?
[Google Pixel XL Guides, News, & Discussion] pcriz:
I have it in 4.3.1
[Google Pixel XL Guides, News, & Discussion] JimSmith94:
Thank you sir! I found and installed 4.3.3 and now I have the Core Mode option and have passed SafetyNet again.
[Google Pixel XL Guides, News, & Discussion] firewave:
Interesting. I don't use any module so Core only is activated by default.
[Google Pixel XL Guides, News, & Discussion] pcriz:
What version are you using. I think most of us don't use modules because the majority don't work. I wasn't but every version of magisk I have used (up to 4.3.3) requires it to be anabled regardless.
[Google Pixel XL Guides, News, & Discussion] jschill31:
Hey everyone,

I finally had time to update to June release and chose to go with Magisk over SU. All is good and I am passing, Netflix wanted to update before I even cleared the Play Store. One item I think may be lost using this method is Substratum. I can't seem to get it to recognize systemless mode on stock. Is there a module or any work around as I struggle without a dark background.

Cheers
[Google Pixel XL Guides, News, & Discussion] The Lich:
It was working flawlessly until I disabled core mode and tried to install the iOS 10 emoji switcher. I got greedy (>~<)

Gotta redo this whole thing again, then look into getting Stick Mount to work...

---------- Post added at 03:05 AM ---------- Previous post was at 02:28 AM ----------

Ok, back to working again. Thankfully I came across this thread earlier:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828

And was able to use the Mount-Magisk.zip to remove the module that was causing the problem.

Still waiting on Stick Mount. Anybody know anything about that? I paid for Pro and all that, and now it doesn't work.
[Google Pixel XL Guides, News, & Discussion] just4747:
Using this method to root and to get busybox, what method/version (if any) of Viper/V4A can we flash or install that will actually work? So far I've tried this: https://xdaforums.com/pixel-xl/themes/mod-weta-audio-t3491179/page16 as well as another random Nougat Viper thread: https://xdaforums.com/nexus-6p/general/how-to-install-viper4android-nougat-t3465597 and neither worked. I either get that the driver won't install due to I/O error or I can install the driver but it doesn't stick after reboot.

Also, somewhat related, while trying the various Viper methods, one of them wanted me to rename/delete the vendor/etc/audio_effects.conf file but no matter what I tried, Root Explorer, ES, etc would all tell me it failed to rename or delete. If we are rooted and my root explorer apps all have root permissions, why can't I do system file modifications no matter what? I've tried everything.
[Google Pixel XL Guides, News, & Discussion] pcriz:
The only one I had working required a compatibility mode through Magisk. Since we have to use Magisk Core only all mods are disabled.
[Google Pixel XL Guides, News, & Discussion] jschill31:
Hello,

For those who miss Substratum, this may be an option: https://xdaforums.com/apps/magisk/module-systemless-substratum-legacy-t3623607 . I will not have a chance to try for a day or two but worth a look.

Cheers
[Google Pixel XL Guides, News, & Discussion] pcriz:
Lemme tell you why this won't work. If you are using magisk to pass safetynet, you currently need to have Magisk Core Only enabled. This means all modules are disabled.
[Google Pixel XL Guides, News, & Discussion] jschill31:
Hello,

I admit I am new to the Magisk method and modules. What I am not clear on is if the module is only needed to build the themed apps and set up sym-links or does it need to stay active to direct that traffic to the themed apps once built?

Cheers
[Google Pixel XL Guides, News, & Discussion] pcriz:
That is certainly a possibility that they don't need to be active any other time than when the theme is being applied. The other question is does this even with on the pixel. In my personal experience very few modules work on the pixel file system.
[Google Pixel XL Guides, News, & Discussion] jschill31:
Hard telling and you are correct on module issues with Pixel(s). I do think in theory though the module may only need to be active to build and apply the theme. Before I understood more about how Magisk works I tried to apply a theme in Legacy mode on stock 7.1.2. Without any direction from me, Substratum created a new folder under data and placed all the themed apps there. I am hoping that the module just sets up the needed re-directs to those newly created themed apps. If this is the case there should be no reason we need to leave it active and can go back to core only for SaftyNet. Then again it may also need to stay active to keep the re-directs working...could go either way? When I was running SU in Legacy everything was under the system partition as you would expect. I wish I had my Pixel with me but I decided to take my Nexus and will be traveling for a couple days. I am sure someone will try it and report back.

Cheers
[Google Pixel XL Guides, News, & Discussion] firebrain:
Hi,

Just tried this method . Magisk Manager 4.3.3 is not showing rooted at all. Coming from a stock 7.1.2 (brand new phone). Any help would be appreciated
[Google Pixel XL Guides, News, & Discussion] pcriz:
Did you manually install magisk manager or are you using the one that gets installed with the zip?
[Google Pixel XL Guides, News, & Discussion] The Lich:
You followed each step from the OP in order?

Are you running any of the carrier variants or did you get it from Google?
[Google Pixel XL Guides, News, & Discussion] firebrain:
Yes.

Directly from Google.

---------- Post added at 01:02 AM ---------- Previous post was at 01:01 AM ----------

Installed manually. I didnt see Magisk Mnanager on phone after I flashed the zip
[Google Pixel XL Guides, News, & Discussion] Bloodgod:
[/COLOR]

followed the instructions except for the kernel since i'm using pure nexus rom and kernel. rooted and passed safety net on 7.1.2 problem i had was wrong twrp. updated to rc2 and all went well. thank you. using verizon variant XL :good:
[Google Pixel XL Guides, News, & Discussion] Captain Hindsight:
I reflashed recently (June Update) and had to do the process twice to get Magisk to pick up

it might have been a reboot doing it, but I'd recommend reflashing again to see.
[Google Pixel XL Guides, News, & Discussion] whotton:
Worked perfectly for me, the tutorial isn't a dummies guide so some may struggle but I had no issues. Thanks! :good:
[Google Pixel XL Guides, News, & Discussion] firebrain:
Thank you for calling me a dummy lol.

I am trying the tutorial again from step 1 will see if it works this time.
[Google Pixel XL Guides, News, & Discussion] Captain Hindsight:
good luck

2nd time was the charm for me.
[Google Pixel XL Guides, News, & Discussion] nikitis:
This is a dumb question, but I did read this entire post as well as the OP's post multiple times, and I'm unclear on this as it was not mentioned.

We can re-lock the bootloader after all of the steps correct? I mean I assume that's why we run the boot signer v8 so that it will use our newly signed keys, but since the step wasn't mentioned I did not lock my bootloader back yet.

Can someone confirm that this can be done? Or shouldn't be done?

I'm currently bootloader unlocked. Thanks in advance!
[Google Pixel XL Guides, News, & Discussion] pcriz:
I wouldn't with a modified boot.img. Also why would you want to
[Google Pixel XL Guides, News, & Discussion] yearn2burn:
If you re-lock the bootloader, the next time you update you're going to have to re-unlock assuming you want to keep root. And that means wipe all data. With no gain from locking that I can see, except maybe the esthetics of not seeing the unlocked bootloader message every time you boot. So why re-lock?.
[Google Pixel XL Guides, News, & Discussion] pcriz:
You responded to the wrong person, also have you locked with a modified boot.img before? I ask because I know I have read about others that have unlocked while on a custom rom and bricked, isn't that a possibility with a modded boot.img.
[Google Pixel XL Guides, News, & Discussion] Captain Hindsight:
From everything that has been posted to date

you CAN lock you bootloader when not on stock.

but you WILL get a brick.

you don't need hindsight for that one my friend
[Google Pixel XL Guides, News, & Discussion] ScottIsMyName:
I'm on PureNexus.....I've read conflicting reports that you do/do NOT need to run the bootsigner if you're on the June firmware. Can someone please verify this?
[Google Pixel XL Guides, News, & Discussion] pcriz:
June bootloader doesnt require boot signing.
[Google Pixel XL Guides, News, & Discussion] The Lich:
It may have changed active boot slots on you. I'm still getting used that aspect of the Pixel.

You can manually change it with ADB or in TWRP. It will tell you which one is active in the bootloader.

I know this happens after you take OTAs sometimes (my phone automagically downloaded one or two right after setting it up, while still un-rooted)

Apparently updating will occasionally change your active boot partition in order to help with seamless updates. It'll update the opposite partition then boot you into that from then on until you take another OTA or flash something else.

That would also explain why some people had to flash it twice to get it to work - it flashed partition a first but booted up into partition b, then flashed partition b the second time and booted into partition a.

---------- Post added at 03:46 PM ---------- Previous post was at 03:44 PM ----------

Either way, would it *hurt* to sign it with the bootsigner?

I feel like I came late to the game because I started the whole root process with the June update, and everything worked fine with the signer zip.
[Google Pixel XL Guides, News, & Discussion] pcriz:
OTAs always flash to the other slot.

The idea is that a fresh device should be fully bootable in your active slot. The inactive slot has a functioning bootloader and then essentially placeholders. So when you get the update it installs into the inactive slot and upon the next reboot it's active. Like you had said.

Problems can arise with this when it comes to flashing because one slot is always outdated. Normal use it's no issue but when you use zips that touch both slots it may cause problems. Example being the people that OTAd back from Android O and can't flash TWRP.

Most people when all this started had at least one OTA under their belt so in reality you could flash and it not be an issue.

If you flash a factory image though it puts those place holders back in the other slot. So when you flash a rom it places the room on the inactive slot with the placeholders.

So a good baseline is to simply flash the factory image in slot A and B so both slots are equally bootable.

But no it doesn't hurt to still flash vbs as far as I can tell.
[Google Pixel XL Guides, News, & Discussion] vacaloca:
Just wanted to say that the instructions in the OP worked perfect to get Magisk/root and safetynet passing on my Pixel XL with the June update, thanks OP!
[Google Pixel XL Guides, News, & Discussion] jschill31:
Hello,

Has anyone figured out a global EQ option while maintaining SaftyNet? I use Amazon Music and can't seem to find anything other than V4 for global use. I have a systemless option for my N6 but can't seem to find one for my Pixel XL.

Sorry for the OT

Cheers