yashsingh1/xdaforums huggingface dataset:
[Google Pixel Guides, News, & Discussion] Archangel:
I know for root explorer, any time you have to make changes to a system partition, you have to check the "mount r/w" tab at the top and you can make all the changes you need. Magisk just doesn't auto mount those partitions on boot but it does work. Cant speak for other explorers. For some apps like ad away I have to go into root explorer and click mount r/w and then go into ad away and install the libraries and it works. If I dont click remount for certain apps wont install.
[Google Pixel Guides, News, & Discussion] bbender716:
This worked for me in terms of mount system r/w for my busybox installer that wasn't working. However, I'm actually trying to get viper4a to work and it absolutely refuses to.
[Google Pixel Guides, News, & Discussion] qwer777:
Has anyone found a way to get substratum to work with magisk on non OMS roms?
[Google Pixel Guides, News, & Discussion] itsme_4ucz:
Is anyone having issues​ with v12.0 modules? Any module installed causes boot loop, this worked fine on 11.2
[Google Pixel Guides, News, & Discussion] stackz07:
will franco kernel work with this?
[Google Pixel Guides, News, & Discussion] stackz07:
blep
[Google Pixel Guides, News, & Discussion] stackz07:
im getting cts profile mistmatch
[Google Pixel Guides, News, & Discussion] stackz07:
I feel like a lot of people are kind of lost all over the place just recieving their pixel and finding out where twrp is in dev and install issues.. Below worked for me but I did modify the steps a bit, I'll edit the quote below to list what worked for me, a new out of box pixel user. Hope this helps.

Open up the magisk manager app and check "hide magisk" and everything else you want, then reboot. only after the reboot check the safety net check
[Google Pixel Guides, News, & Discussion] JAYNO20:
I am also getting a "getting cts profile mismatch"

I am on May PN rom with ElementalX kernel installed. Everything works as far as a few rooted apps I have. I don't get why I'm getting this error.
[Google Pixel Guides, News, & Discussion] mac796:
Old method above your post all you need to do is flash the new pixel v12 magisk zip. Install rc2 after that boot to system install magisk manager from the thread. Can't get it from play store. I check those 3 boxes, busy box, systemless, and magisk hide. You may need to do one reboot. But I can confirm it works on newest pn.
[Google Pixel Guides, News, & Discussion] JAYNO20:
Never mind. I had the wrong file. I got it installed now, but now it is saying I am not rooted and I have no option to check for busybox, etc.?
[Google Pixel Guides, News, & Discussion] mac796:
Yeah I haven't had much luck with that I did get it to work one time but the only Surefire way I can get magisk to work on the new May bootloader is I set up my phone on the May firmware with April bootloaders. With whatever ROM u want. You can either keep it on April bootloaders and Flash magisk and rc2 again at this point. Or reboot to recovery. install v3 zip both slots , then reboot to Bootloader fastboot flash May bootloader. I did both slots. Reboot to system from bootloader. Then you should be able to reboot to TWRP install magisk, rc2, then v3.

This method worked for me 3 times so far on lil pixel and XL, also worked on super su. I tried some of the other guides I had no luck.

Edit sorry I thought your post said v3. It says v12. I thought you were trying to install it on May bootloaders lol
[Google Pixel Guides, News, & Discussion] JAYNO20:
I didn't say that, but I am on the May bootloader lol. I got V12 to flash (I used the V3 stuff from chainfire) but now when I open it up it says I am not rooted with no options to root.
[Google Pixel Guides, News, & Discussion] mac796:
Yea I read your post wrong I thought u said v3 was my mistake

If you didn't do a clean Flash or u installed magisk again you may need to reboot TWRP mount system , advanced, file manager , data\magisk delete everything in there, then go back one and scroll to bottom delete that magisk. IMG file then install magisk again
[Google Pixel Guides, News, & Discussion] JAYNO20:
I am still getting the not rooted error after doing that.
[Google Pixel Guides, News, & Discussion] mac796:
Maybe you have wrong file or bad one. Here's mine v12
[Google Pixel Guides, News, & Discussion] mac796:
This is the magisk manager apk u need

http://tiny.cc/latestmanager
[Google Pixel Guides, News, & Discussion] stackz07:
Turn off hide magisk, reboot, turn on again, reboot again and run the safety check. worked for me
[Google Pixel Guides, News, & Discussion] JAYNO20:
A fresh install of everything fixed it for me. All good now :)
[Google Pixel Guides, News, & Discussion] Pøîñtßlåñk:
Do you mind sharing the correct steps of a fresh install? I'm currently on stock rom with magisk v12 and may update. Would love to flash PN. ;)
[Google Pixel Guides, News, & Discussion] carlylemiii:
Is there any working solution to modifying System in any way? I want to add my Adguard HTTPS cert to System so that apps targeting Nougat can successfully be adblocked, but I can't add anything to /system/etc/security/cacerts. (MoveCerts failed for this purpose - works with SuperSU, sadly, so I was trying to do it manually, but also seems like a no-go.)

Edit: Should have just looked a bit harder. Seems this works. Just can't use Solid Explorer.

https://xdaforums.com/showpost.php?p=72233151&postcount=302
[Google Pixel Guides, News, & Discussion] colormedroid:
This worked for me... Don't worry about changing slots because there's really no need:
[Google Pixel Guides, News, & Discussion] PFusion:
So I installed TWRP, PureNexus, flashed the latest build of Elemental 1.11, and then I installed Magisk 12, then installed the manager. Everything looks good but I get this message when I boot everytime

"Your device software can't be checked for corruption. Please lock the bootloader."

Does this affect anything or Or is it normal?

My Objectives are

Have root hidden so I can run certain apps that won't run if root is detected

Not have Safety Net tripped etc..

[IMG="screenshot"]https://i.imgur.com/g6z75Ya.jpg[/IMG]
[Google Pixel Guides, News, & Discussion] TonikJDK:
Normal, tht screen won't effect anything you are trying to accomplish.
[Google Pixel Guides, News, & Discussion] unhappybirthday:
To clarify, elemental will hide the fact that the bootloader is unlocked from SafetyNet.
[Google Pixel Guides, News, & Discussion] pennywaltz:
has anyone gotten App systemizer to work with their pixel?
[Google Pixel Guides, News, & Discussion] sovanyio:
Not me, causes a boot hang until I fastboot boot twrp and remove it from /magisk
[Google Pixel Guides, News, & Discussion] adma84:
Even worse is that it hoses permissions for tons of your apps. Something must be broken for the magic mount on pixel
[Google Pixel Guides, News, & Discussion] JAYNO20:
This is exactly what I did that worked for me:

Boot to TWRP

Flash TWRP RC2

Reboot to Recovery

Flash Pure Nexus rom

Flash TWRP RC2 again

Reboot (see vendor message error)

Reboot to Bootloader

Flash Vendor Image

Boot back into TWRP

Flash Magisk v12

Flash TWRP RC2 again

Reboot

Install Magisk APK
[Google Pixel Guides, News, & Discussion] mikeprius:
I tried to get this to work for over 1 hr last night and was not able to. Just have SuperSU right now. It's a shame it has gotten to this point to even root anymore. Too much Micky mouse bullsh-t from Google. Eventually the phone will be like Samsung and 100% locked
[Google Pixel Guides, News, & Discussion] mikeprius:
Wow. I actually got it working
[Google Pixel Guides, News, & Discussion] cccthestyle:
Out of curiosity which method?
[Google Pixel Guides, News, & Discussion] mikeprius:
ROM kernel magisk

After using various doze apps and kernels I think I actually got something good.

The magisk won't work on stock ROM. That's why it did not work for me
[Google Pixel Guides, News, & Discussion] piccit:
It should be noted that the OP is out of date.

1) The newest Magisk install zip (v12) is available in the RR ROM thread.

2) You don't need to install SuperSU at point

As it has been said before:

Boot TWRP, flash TWRP RC2, flash Verified Boot Signer, reboot recovery

Flash ROM, (flash Verified Boot Signer in case your ROM didn't sign, if it did just abort)

Reboot to system

Boot TWRP, flash, TWRP RC2, flash Verified Boot Signer, reboot recovery

Flash kernel (flash Verified Boot Signer in case your kernel didn't sign, if it did just abort)

Reboot to system

Reboot to recovery

Flash magisk, flash Verified Boot Signer
[Google Pixel Guides, News, & Discussion] sovanyio:
It will work on a stock ROM, but if you are using the May update, the boot image needs to be signed after anything that touches it (kernel, magisk, twrp...)
[Google Pixel Guides, News, & Discussion] Sheeezy:
So guys, I kinda messed up and had to revive my device with my TWRP backup a few times...

Right now I'm on PureNexus May Update (with April Bootloader, so no Verified Bootsigner) and rooted with SuperSU.

What I tried:

- tried flashing th Magisk v12.zip and get Error: 1 (I have the stock PureNexus Kernel)

- tried unSU.zip

- tried installing Magisk via the Magsik apk

Anyone can point me in the right direction ?
[Google Pixel Guides, News, & Discussion] JAYNO20:
Start from scratch. That's what I did when I was having issues and now it's working perfectly.
[Google Pixel Guides, News, & Discussion] Sheeezy:
Yes thanks for the input but unfortunately everything works just great at the moment so I don't wanna start from scratch it use TiBu. Maybe with the next PureNexus update.

Btw. do you know what the error 1 means when installing magisk via TWRP ?
[Google Pixel Guides, News, & Discussion] JAYNO20:
I don't remember the exact error code I got but when I first attempted to install magisk (v12) I got an error in twrp (red text) and it wouldn't let me do it. That's when I decided to try a fresh install and it all went perfectly.
[Google Pixel Guides, News, & Discussion] unhappybirthday:
Are you installing from TWRP RC2?
[Google Pixel Guides, News, & Discussion] Sheeezy:
I have used RC1 the whole time but before flashing magisk.zip, I updated to RC2
[Google Pixel Guides, News, & Discussion] Sh0X31:
Here you find a newer tutorial with unofficial Magisk v12
[Google Pixel Guides, News, & Discussion] Abolfazl:
Updating my older post to include VerifiedBootSigner process for OTA's that are post-N2G47E

Thought I would make concise instructions on installing Magisk since I have not seen a post that explains the full process.

How to Install on Pixel

FYI: Magisk can only be installed on TWRP RC2 and because there is no RC2 boot image, you have to boot into RC1 and then install RC2.

FYI2: If you want to bypass SafetyNet, you need to install a custom kernel. I personally use ElementalX.

FYI3: The following files are meant for the Pixel. If you want the Pixel XL files you just need to get the corresponding TWRP files from Here.

The following is what I did. I was already rooted when I did this but it should not matter. People have done this on custom and stock ROMs. These instructions will NOT wipe your data. Just be careful to remove the -w flag if you install latest image via flash-all.

Download twrp-3.0.2-0-RC1-fastboot-sailfish.img to your computer.

Download the following to your phone: twrp-pixel-installer-sailfish-3.1.0-0RC2.zip (TWRP RC2), Magisk-v12.0-Pixel.zip (Magisk V12), VerifiedBootsigner.zip and ElementalX-P-1.11.zip (ElementalX Kernel, Only if you want to bypass SafetyNet)

(Optional) Make sure you have the latest OTA (N2G47E or equivalent for your carrier)

run

adb reboot bootloader

run

fastboot boot X:\Path\to\twrp-3.0.2-0-RC1-fastboot-sailfish.img

. This will boot phone into TWRP RC1.

Select 'Install' and flash the twrp-pixel-installer-sailfish-3.1.0-0RC2.zip zip.

Flash VerifiedBootSigner.zip

Go back to main TWRP menu and select Reboot > Recovery. (Some instructions recommend rebooting phone normally and rebooting into recovery but it is all the same)

You should now be loaded in TWRP RC2. Go to 'Install' and flash the Magisk-v12.0-Pixel.zip file.

(Optional) If you want to bypass SafetyNet, Flash the ElementalX-P-1.09.zip file.

Reflash the twrp-pixel-installer-sailfish-3.1.0-0RC2.zip zip file.

Flash VerifiedBootSigner.zip

Reboot system

Download latest version of Magisk Manager from APKMirror

Install the apk by running

adb install -r MAGISKMANAGER.apk

. the -r flag will reinstall it in case it was already installed.

(Optional) If you are bypassing SafetyNet, you will need to go into Magisk Manager > Settings > enable 'Magisk Hide' and then reboot.

(Optional) Don't forget to uninstall the SuperSU app from your phone if you had root before. Magisk Manager will replace the need for it.
[Google Pixel Guides, News, & Discussion] :
Thank you for the clear directions. That worked the 1st try on nhg47n for Verizon.

View attachment 4173009
[Google Pixel Guides, News, & Discussion] Coronado is dead:
So... does Netflix show up in the play store for you?
[Google Pixel Guides, News, & Discussion] :
I never use Netflix. I went back to SuperSU because of the limitations with Magisk.
[Google Pixel Guides, News, & Discussion] danaff37:
Netflix does for me, and it's not currently installed.
[Google Pixel Guides, News, & Discussion] fink.nottle:
Magisk + EX kernel works for me with the latest June image. SafetyNet, however, is a bit hit or miss. Sometimes it shows pass, whereas other times it fails.
[Google Pixel Guides, News, & Discussion] carlylemiii:
Safetynet has been updated and Magisk no longer passes :((
[Google Pixel Guides, News, & Discussion] Abolfazl:
Same case for me.
[Google Pixel Guides, News, & Discussion] carlylemiii:
Did you happen to update to Magisk Manager 5.0? I did, not knowing that it's not fully compatible with 12.0, and now after reinstalling the older version and restarting, things look okay...so far...
[Google Pixel Guides, News, & Discussion] Abolfazl:
Just upgraded to 5.0.1 Beta and it is still failing and I do not even see Magisk Hide as an option anymore in the settings
[Google Pixel Guides, News, & Discussion] carlylemiii:
Sorry, I should have been more clear with my question. You should NOT upgrade to 5.0 as it isn't compatible with 12.0. I downgraded and my issue seems to be resolved right now. I have "just core" checked and have only Magisk Hide enabled
[Google Pixel Guides, News, & Discussion] Abolfazl:
Oh no, I was still on 4.3.3. I uninstalled 5.0.1 and reinstalled 4.3.3 and i am still getting CTS Profile Mismatch.
[Google Pixel Guides, News, & Discussion] jlee08517:
Yeah. Ever since I updated to PN June cts no longer passes...
[Google Pixel Guides, News, & Discussion] ipeedalil:
Same issue safety net fails
[Google Pixel Guides, News, & Discussion] tacofart:
Failing too. Haven't updated magisk at all and am still on may PN
[Google Pixel Guides, News, & Discussion] danaff37:
Same here. Probably an update in Google play services.

---------- Post added at 07:36 PM ---------- Previous post was at 07:02 PM ----------

Enabling core options only will allow safety net to pass. This disables downloaded modules, but root, hide, systemless hosts, and BusyBox still work. Not sure downloaded modules work anyways on pixel.
[Google Pixel Guides, News, & Discussion] history:
In Magisk Manager checking the box for Magisk Core Only Mode seems to work. I also have Magisk Hide and Seamless hosts checked. Play store also reports as certified.
[Google Pixel Guides, News, & Discussion] brangalm:
Mines also still working.

On June stock with magisk 12.0, elemental kernel.

I keep everything updated - just had some apps update last night and no change to magisk. I do have the magisk core mode on since I don't use any modules, if that makes a difference.
[Google Pixel Guides, News, & Discussion] JAYNO20:
Mine also stopped working (noticed today) on PN May update. Was working perfectly yesterday (around 3pm) and now today failed (CTS Mismatch). I checked the "Core only mode" and that fixed it for me.
[Google Pixel Guides, News, & Discussion] billiepreks:
Same here and same solution, I've checked the Core only mode.

But if I want to use any module, how can I do it ?
[Google Pixel Guides, News, & Discussion] mac796:
Even though it's not showing my arise module anymore. It's still working. Not sure about other ones. Only one I use
[Google Pixel Guides, News, & Discussion] piccit:
I read that the Magisk dev said he had a fix that will be in the next beta. So it may be a while because you'll also need whomever to make the Pixel compatible zip
[Google Pixel Guides, News, & Discussion] billiepreks:
Yeah I've read that too on xda news

I've question, anybody here has tried to use any module from Magisk repo ? When I successfuly install and reboot I've 0 modules installed in Magisk Manager. It's normal ?
[Google Pixel Guides, News, & Discussion] Golf c:
For the Pixel it is normal not to have modules. It's an unofficial build. The only one that works is Arise sound mod. And that might be broken cause of Google's latest safetynet patch. We will need an update to fix that patch.
[Google Pixel Guides, News, & Discussion] billiepreks:
Oooh thanks, I've done so many try with different modules, it never worked and some modules are caused an irreparable bootloop, I began to despair I thought it was my installation who are wrong !

You said that an ARISE module was compatible with the Magisk Pixel version? I didn't see it on Magisk repo, could you tell me the link?

If I uncheck Magisk Core mode, I don't care about SafetyNet until the update, should the module work?
[Google Pixel Guides, News, & Discussion] Golf c:
[MENTION=5998428]mac796[/MENTION] Help!

I'm sorry, I don't use it. A friend told me it works. We will find out for you.

Here is the link to Arise, they will know.

https://xdaforums.com/android/software/r-s-e-sound-systems-auditory-research-t3379709/page2786
[Google Pixel Guides, News, & Discussion] mac796:
Delete

---------- Post added at 04:48 PM ---------- Previous post was at 04:41 PM ----------

I'm sorry I just saw this now. The new 05/24 Build had it included inside the prop file. For some reason they took that build down off the file section but here's the module used for the 05/06 build.

https://drive.google.com/file/d/0B2n4LSlxHxTQS3c2SEZjZHJSaEE/view?usp=drivesdk
[Google Pixel Guides, News, & Discussion] billiepreks:
Thanks you for your help.

This is a Magisk Module, so I've to flash it in Magisk Manager, right ? But he told me "it's not a Magisk Module". Should I flash it directly in TWRP ?
[Google Pixel Guides, News, & Discussion] mac796:
You flash it in TWRP. But since Google updated the security deal I've been having to run my magisk in core only mode which doesn't show the modules but it's still working for me. I guess there's a fix out just not for us Pixel People yet
[Google Pixel Guides, News, & Discussion] billiepreks:
Oh it worked, the module is recognized in Magisk! But I did'nt get any of the related applications, VIPER and others. It's normal ? What should I do ?
[Google Pixel Guides, News, & Discussion] mac796:
You have to flash the arise build in TWRP. Once you flash it it has a prop file that Is moved to your internal storage you need to open it up with an editor and put true for the core and anything else you want I would pick 2.44 it seems to work better on our pixel least for me anyway. You can also extract it to the internal storage yourself to save you a step from having to flash it twice. Because after you pick those things in the prop you need to flash it again for it to go into effect
[Google Pixel Guides, News, & Discussion] billiepreks:
Hmm I understand the procedure but I did'nt see any prop file to edit.. I search for Arise_customize.prop, it's correct ?

Edit: I looked on the topic of ARISE, I should have in /sdcard a folder VIPER4ANDROID and the file Arise_customize.prop, but I do not have them .. How can I do?
[Google Pixel Guides, News, & Discussion] mac796:
Yes. Just flash arise in TWRP. Then go to your internal storage and you'll see the arise customize prop in there open it with your editor and fill in everything you want and save it

Then flash arise again in TWRP
[Google Pixel Guides, News, & Discussion] mnrivera210:
Anyone have luck with v13?
[Google Pixel Guides, News, & Discussion] billiepreks:
I had to download the version 05/24 on the topic of ARISE for having the creation of the Arise_customize.prop, but besides it thank you very much for the help without your explanations I would have difficult to understand how works This installation! thank you very much
[Google Pixel Guides, News, & Discussion] mac796:
The 5/24 arise build has the magisk module built in the customize prop. Your welcome
[Google Pixel Guides, News, & Discussion] jawonder:
Yeah i did that and also uninstall and reinstalled Titanium, rebooted and it still not getting root .

After reboot Magisk is now failing Safetynet Check.
[Google Pixel Guides, News, & Discussion] mac796:
Mine did that at first to, after the reboot and just waiting a bit it all started working. Been working ever since. I remember having a hard time getting busy box to install, once I checked that box I still download the busy box app and installed it. I have the pro version if that makes a difference
[Google Pixel Guides, News, & Discussion] jawonder:
Yeah, i just reboot again and its working now and Titanium is working now too. Thanks
[Google Pixel Guides, News, & Discussion] mac796:
Good deal I know it took a reboot or two. Remember it is still experimental. But so far been working good for me on rr
[Google Pixel Guides, News, & Discussion] Archangel:
Weird but, possibly a good thing. I flashed Super SU and now I have Magisk installed and all blocks are green except for safety net check. When I click to check it,,,it does nothing however, Android pay still works? Didnt think it would work if safety net check didnt show green.
[Google Pixel Guides, News, & Discussion] asad510:
I did that too but when you go to the shops to use AP it will give you a error.
[Google Pixel Guides, News, & Discussion] Archangel:
Well that sucks,,,I never used AP but it would have been nice, just cant give up root that allows me to mod at system level.
[Google Pixel Guides, News, & Discussion] uodii:
It looks like there might be a commit that needs adding to boot. Elemental X is a common denominator so far. I tried on PN with stock kernel and magisk didnt install properly. I dirty flashed PN to remove any remaining garbage left behind and rebooted to make sure SafetyNet passed while everything was back to stock PN.

Then I installed Elemental X, Experimental Magisk, and then TWRP and everything is working atm
[Google Pixel Guides, News, & Discussion] jawonder:
So now Magisk is saying i'm not rooted . Should i flash the Magisk zip again in recovery ?. I thinking i can't flash supersu a the Magisk zip i used had it build in .

Edit : Reboot a few time a it's fix . Seems rebooting is the key to fixing malfunctions.
[Google Pixel Guides, News, & Discussion] kingkong0821:
I also saw that in my phone. Flash the zip again fixed it
[Google Pixel Guides, News, & Discussion] mac796:
If your on rr, follow the second post of this thread, don't use su at all it will work good.
[Google Pixel Guides, News, & Discussion] aholeinthewor1d:
I've never used this before. Is the point of it his to hide root? Aren't there kernels with the safety net patch. Just trying to understand the benefits of this vs a customer kernel
[Google Pixel Guides, News, & Discussion] asad510:
if you want root and still use AP etc apps this is the best way to go.
[Google Pixel Guides, News, & Discussion] mac796:
Just a different way to root. Still experimental. You will have root and pass safety
[Google Pixel Guides, News, & Discussion] jawonder:
Tried this a bunch of times and i can't get Magisk app to install on PureNexus . I tried with TWRP RC1 and RC2.