yashsingh1/xdaforums huggingface dataset:
[Magisk] CarteNoir:
Then that's probably the issue since this seems to need a custom kernel or at least a patched stock kernel to work. Either that or it's straight up not compatible with O, but you're never going to know without a kernel to flash.
[Magisk] anuraj1:
Time to build a custom kernel to go with your custom recovery! :D
[Magisk] Nick80835:
Not enough source is out :silly:
[Magisk] goodwin_c:
I think it's time to relax and wait final release :) Currently O is in beta stage, so it's not worth spending too much energy on it

P.S. Porting v13.4 beta 2 currently for Pixels ;)
[Magisk] eg1122:
Any idea on what needs to be edited on the module template to make them work on the pixel?
[Magisk] EstiR86:
Anyone know how to convert apps to system apps using Magisk everything I try gets me an error or doesn't work.
[Magisk] pcriz:
Wait so you're telling me there isn't a custom kernel for Android zebra cake yet?

OMG I swear these slots are screwing everything up!
[Magisk] goodwin_c:
Did you miss me a little? Yes? Then i'm here again - new release is already on my AFH! Please welcome Magisk v13.4 Beta2 (build 1)!
[Magisk] MusikMonk:
I'm a bit lost, where can we find the changelog for the betas? I only found the one for the stable releases in a topjohnwu thread.
[Magisk] pcriz:
Dirty flash over top?
[Magisk] goodwin_c:
In most cases changelog is same as official release with same number - with only difference that my builds are universal - they are working on Pixels and non-Pixels. Official releases are not working on Pixels at all

But in this release - there is extra improvement - i have added selinux rules for call recorder as was mentioned before.
[Magisk] EstiR86:
Seems that ARISE does not work even with he Magisk v4 zip any suggestions
[Magisk] pcriz:
Mine is working fine with the arise aroma and the compatibility v4 zip.

I'm using the latest screwed rom

Latest Magisk 13.3 (pixel edition)

Just installed it and adjusted the sound for my BT headset

I installed the aroma and compatibility back to back. I only use the core modules with profiles.
[Magisk] cmo220:
This seems to be ROM specific. I have found the latest version of ARISE works on Pure Nexus, but not AOKP. Those are the only ROMs I've tried so far. I'm also still on Magisk 13.3 since it's working and I haven't seen what changed on 13.4.

The problem with not working is something with the ROM and Magisk Compatibility Module. Try finding and flashing the Magisk Compatibility Module v3.3 and see if that works on your ROM. That made it work on AOKP.
[Magisk] pcriz:
I was using 3.3 last week and it was fine. I loaded up this morning with 4 just to test if it worked or not and both worked.
[Magisk] wlchen:
anyone can tell me how to install this ?:crying:

My steps:

1. Install TWRP

2. Flash Magisk-v13.4-Pixel-beta2-build1.zip via TWRP

3. Install Magisk Manager

But it didn't work :crying:

What should I do to install magisk in Pixel successfully?

My ROM and Kernel are stock, should I flash custom one?
[Magisk] cmo220:
What ROMs?

And did you start clean or flash 4 over 3.3

Nevermind, if you're flashing Aroma you're using an old version. [MENTION=7722355]EstiR86[/MENTION] What Arise version are you using?
[Magisk] CarteNoir:
The file names here obviously aren't the exact names, look around for the files:

boot into your bootloader

fastboot boot twrp-rc1.img

use twrp rc1 to flash the twrp-rc2.zip

use twrp to reboot into recovery (this takes you to RC2)

flash magisk.zip

flash custom kernel.zip (e.g. ElementalX) - this must be done or it won't stick

flash twrp-rc2.zip again

reboot system

install Magisk Manager

---------- Post added at 06:08 PM ---------- Previous post was at 06:05 PM ----------

Thanks so much for your hard work and dedication in getting Magisk working for us man! I really appreciate it! Would you have any tips on getting Magisk Modules working with your builds? Particularly the modules that change /system files? e.g. BusyBox, iOS Emojis, Greenify4Magisk, etc :)
[Magisk] wlchen:
Thanks a lot. I didn't flash custom kernel.

I will do it later.
[Magisk] pcriz:
Install 13.3b4
[Magisk] CarteNoir:
Yeah I was having that issue a couple of days ago too because I wanted to stay on the stock kernel. Everyone says the custom kernel is just for the helping bypass Safetynet, but it's not - Magisk doesn't install without it. You can use the stock ROM but you gotta have a patched/custom kernel unfortunately. I'm going to look into making a patched stock kernel and see if that works with this.
[Magisk] EstiR86:
I'm using stock 7.1.2 and when I try and install arise and set up Viper it says BusyBox not installed any ideas? From what I hear BusyBox is not possible with Magisk because it can't mount system to RW any suggestions would be highly appreciated
[Magisk] pcriz:
I just installed the modular zip ARISE+Magnum+Opus+20170724 after a dirty flash of my rom.

I didn't need to flash a separate compatibility zip for magisk

I followed the directions in the zip and it is working like a charm right now.

Got it here: https://www.androidfilehost.com/?w=profile&uid=24549084345925777

---------- Post added at 07:41 PM ---------- Previous post was at 07:40 PM ----------

This might be helpful
[Magisk] EstiR86:
Did you get Viper to work tho? I can get the other modules to work but no viper as BusyBox is needed
[Magisk] pcriz:
Viper4Arise, didn't ask for busybox
[Magisk] EstiR86:
Very weird it asked me to install drivers did you use the Aroma or the build.prop method?
[Magisk] pcriz:
The older aroma and the build prop method, neither asked for busybox

Edit: Nevermind, the rom I am using comes with busy box
[Magisk] EstiR86:
Interesting I just flashed a bsuybox for Magisk and just tried Viper through aroma and still same problem but the 2.5.0.4 verison gives me an IO error rather than the BusyBox error so I guess progress. I'm going to try and do the build prop and see if that works
[Magisk] pcriz:
I updated my other post, I checked and my rom comes with busybox
[Magisk] cmo220:
I never got Arise working on Stock. I think I saw that it was possible if you install the flashable busybox zip but I think you have to make some other changes too. It will work for sure on a custom ROM though.
[Magisk] EstiR86:
Ah I see bummer anyways a report no IO or BusyBox errors just says to keep installing drivers and reboot
[Magisk] cmo220:
One thing that might make it work is in V4A settings, go to developer mode and turn it on. Then disable selinux. Then exit V4A from the three dot button and open it again. Your phone will go back to enforcing selinux every reboot.

You'll fail safetynet with it disabled but a reboot should fix that.
[Magisk] EstiR86:
I'll give this a shot some other time, mostly given up at this point I'm just using feel the beatz and ice config setup and that seems to be enough for everything right now.
[Magisk] ItWasAllIntended:
I've noticed a beta Magisk 13.4 on your AFH. I can't find any documentation on 13.4 so what's new and is it worth updating early?
[Magisk] EstiR86:
I flashed this beta and it passes safety net I was hoping for the update to allow mounting to system as read/write but it just seems to be a small update with some bug fixes.
[Magisk] pcriz:
It's not so much that you can't mount system as read write because root explorer and FX file explorer can. It's WHERE apps are looking for the su binary magisk uses that is the issue. So that could be updated on the app end
[Magisk] EstiR86:
I can't edit system files or create new folders in the root directory with whatever file manager I use.
[Magisk] pcriz:
Root explorer has been working fine for me.
[Magisk] Cares:
There's no mention of v13.4. Any idea if I should flash this if I'm not having issues with v13.3 beta3?

I'm flashing August factory images and letting you guys know if I have any issues.

Edit: On August factory images and v13.4 not showing any issues at the moment.
[Magisk] bggold:
Just flashed Aug update on my XL and still passing SN.
[Magisk] ryandolan123:
Hey, i'm having issues installing 13.4 on the August update. I flashed everything except for Userdata and I installed the latest TWRP. Any clue?

Edit: I can't seem to figure out how to upload recovery.log as a file. I put it up on pastebin. https://pastebin.com/MTa8EDPZ

Edit 2: SOLVED: I was simply running an old version of TWRP. derp. Thanks!
[Magisk] drdrewdown:
You are using an extremely old version of twrp. Magisk can only be flashed using the latest RC2

|StayDirty|[emoji769]
[Magisk] PFusion:
[MENTION=2461994]goodwin_c[/MENTION]

Call recorder by [MENTION=2859866]skvalex[/MENTION] doesn't seem to work when using the call recording method called CAF. With Magisk v13.4

It says the root method is not supported. Can you take a look at it and see if it's something you can fix?

I will be happy to donate for a solution
[Magisk] piccit:
Root Explorer works for me too. Just have to manually hit the 'mount r/w' button in "/" rather than relying on it prompting you to mount rw

---------

Actually, [MENTION=2461994]goodwin_c[/MENTION], what is /system and/or where is that pointing to? IIRC, when using the supersu method, there is a /system_root mount and /system is a bind mount to that. But in poking around the cmd line, I'm not seeing any mount related to system when using Magisk.

As I said above, root explorer is able to mount something that allows /system rw -- but I'm not sure what it's actually doing to accomplish that. (I was trying to recreate manually on the cmd line, but quickly found I had no idea what to actually mount).
[Magisk] pcriz:
So magisk is a systemless root. The magisk su binary is placed in another location and hidden from path.

You can symlink magisk so it mitigates the issue where devices don't recognize root but that could potentially break the systemless function and make it so apps that couldn't see past magisk hide now can detect it
[Magisk] piccit:
That's not what I'm asking.

I'm asking what "/system" is at runtime. It's not its own mount nor a bind mount (at least as far as I can tell from running "df -a")

But I guess the answer I ultimately want is what command would one run on the command line to remount whatever needs to be mounted to get /system rw (i.e whatever root Explorer is doing when you hit that button while in "/")
[Magisk] dardack:
Can anyone let me know before I go through with this. Do I need a non stock kernel to do this? I see all the guides saying install Elemental X something. Thanks.

EDIT: NVM I see Aug 2nd posting that a custom kernel is needed.
[Magisk] ryandolan123:
Apparently I flashed the wrong zip in my downloads folder for TWRP and did the old one instead of the new one. Derp :S

Thank you!
[Magisk] Evo_Shift:
Everything seems to be working great for me. I don't use a ton of root apps but the ones I do are working (Titanium, Adaway, Root Explorer) and I am able to pass safetynet.

Thanks.
[Magisk] JimSmith94:
Sorry if I missed it, but I have installed Magisk-v13.4-Pixel-beta2-build1.zip and MagiskManager-5_1_1.apk and they are working fine. However, I keep getting notifications to download and install a new Magisk Manager update. Can I ignore it or is there a newer version for Pixel? If not, is there a way to turn off the notification?
[Magisk] pcriz:
It's gonna download the official one. I'd just disable it.

There is an option in settings
[Magisk] itsme_4ucz:
Tried installing 13.4, installation went well, but when i launch magisk manager, it says magisk not installed.

However i have root and saftey net passes.

any thoughts?

I am on RR 3.8.3 which has custom kernel
[Magisk] pcriz:
Clear data on magisk manager?
[Magisk] itsme_4ucz:
Reinstalled magisk manager 5.1.1 and it worked, thanks.
[Magisk] ppppman:
Hi,

I have done Magisk successfully, got rooted and passed safenet tests.

However, when i installed Sony Framework and try to install Ps4 remote play, it comes up with error of "app not compatible" and I cannot see the app in play store as well. Seems all root required apps can get root access just fine but PS4 remote play is definitely does not work at all.

any suggestion??
[Magisk] inscythe:
Have you turned on magisk hide and specifically enable it on Play Store?
[Magisk] hackel:
These will work with regular, non-XL Pixels as well, right? I'm assuming there is no problem, since it's not installing a new Kernel, but I just wanted to confirm before I start flashing. Thanks for your work on this!
[Magisk] pcriz:
It will work fine.
[Magisk] Evo_Shift:
Yep. I followed these instructions and everything went smooth. https://xdaforums.com/showpost.php?p=73264657&postcount=283
[Magisk] Zebov:
Only because I tried this months ago, couldn't get it to work, and had to go back to my old setup on my pixel, I need to ask a few questions. First, does this work for only 7.1.2 or is it for "O" also? Second, does it require a full wipe if you're on 7.1.2 with SuperSU or just uninstall SU? Finally, would it be better to do this before or after an update to "O?" A very sincere thank you for your help.
[Magisk] pcriz:
You need a custom kernel for it to work and so since there isn't one for O right now that's a no to the first part.

Doesn't require a full wipe, uninstalled su is a start but that doesn't fix the changes to the boot.img that su makes. I would download the factory firmware extract the boot.img and run the following command:

fastboot flash boot --slot all boot.img

First sentence should answer your last question.
[Magisk] Zebov:
That was extremely helpful. I can't thank you enough.
[Magisk] pcriz:
Also if you aren't stock I would recommend dirty flashing your rom to clear the boot.img changes.

The other solution of fastbooting the boot.img will wipe out twrp so you will need to fastboot boot and flash that again.
[Magisk] ppppman:
Yes. I hid all google related services in magisk hide but ended up same result. I cannot find PS4 remote play in store and still cannot install downloaded .apk of PS4 remote play. Any suggestion? Thx.
[Magisk] Gooch4130:
After installing magisk, what is needed to get tethering working for users on the Verizon UDP? That's basically the only reason I want to root my pixel. Thank you in advance!
[Magisk] inscythe:
Has Sony framework ever worked on Pixel before?

TBH, I'm not familiar with the Sony Framework mod. You might need to change the device name, I think...
[Magisk] ppppman:
I really do not know. it seems to work with many brand but i could not find info on Pixel.

I did try to change the model name in build.prop and it did not help.

thx. for your comment. ;)
[Magisk] danaff37:
That's probably your problem. Keep in mind that build. Prop changes are only applied after reboot. And, I've tried to modify build.prop and it didn't stick after reboot. Is your build.prop changes still there? I had to modify build.prop through terminal in TWRP to get it to stick (not for this though, but build.prop changes in general). YMMV.
[Magisk] Sh0X31:
Is it true that Substratum don't work mit Magisk on the Pixel?
[Magisk] Soooperstar:
False
[Magisk] just_visiting:
not true.
[Magisk] pcriz:
You can't change your boot animation in substratum using magisk for SU, at least not without some tinkering.
[Magisk] rohitece06:
[MENTION=2461994]goodwin_c[/MENTION] magisk manager 5.1.1 fails to open (it installs fine) on PixelDust_r10 ROM (the most recent one). magisk v 13.3 b4 insalled fine, I have root, safetynet passes but magisk manager doesnt open so no custom hiding apps. surprisingly though, I was able to login into venmo and snapchat even if I had root with magisk, that didnt use to happen. I had to login into those app before I insalled magisk.
[Magisk] pcriz:
Did you try clearing storage on it?
[Magisk] rohitece06:
It was a fresh install so I didn't think of clearing data but I did it anyways and now it works. Thanks.
[Magisk] UberFiend:
So I'm trying to change fonts and after many apps/routines failed I noticed I can't change anything in the /system directory. Am I missing something obvious?
[Magisk] pcriz:
The apps using root to perform said tasks arent explicitly compatible with the method in which magisk grants root..

Its why Solid Explorer can't modify system but Root Explorer can..

Are you using substratum because I just applied a font to my device through that.
[Magisk] UberFiend:
Thanks, I knew I was missing something obvious there. If Root Explorer works [I used Solid] then I can work from there.

---------- Post added at 06:40 PM ---------- Previous post was at 06:37 PM ----------

Actually, is there another file manager that works? I'm not paying for an app I'll use once
[Magisk] pcriz:
File Explorer

https://play.google.com/store/apps/details?id=nextapp.fx

With root add on

https://play.google.com/store/apps/details?id=nextapp.fx.rr
[Magisk] Tulsadiver:
I like x-plore by lonelycatsgame
[Magisk] EstiR86:
FX file explorer works great
[Magisk] UberFiend:
OH! I thought you meant the jrummy one. That one worked!
[Magisk] Gooch4130:
Anyone have any info on getting tethering bypass with Magisk (ie what is needed)? This is on a Verizon UDP.
[Magisk] EstiR86:
I'm confused what your question is, if you asking if you can get tethering to work on the Verizon pixel running Magisk the answer is yes.
[Magisk] Gooch4130:
What are the steps? Keep in mind I'm on the Unlimited Data Plan so tethering is blocked by verizon.
[Magisk] EstiR86:
Ahh for me it was simply during it on but I don't have unlimited data not sure what would need to be done to get tethering to work
[Magisk] pcriz:
Their question was if there was a way to bypass verizon being able to know when they are tether and how much while using magisk as their su solution. Not if they could simply tether with magisk.
[Magisk] stargzrr11:
Just use the Magisk tether module. Works fine.
[Magisk] EstiR86:
I was under the impression modules don't work
[Magisk] stargzrr11:
Most of them don't. The tether module is an exception.
[Magisk] EstiR86:
Ah cool well then we solved that problem
[Magisk] EstiR86:
Does anyone have any suggestions about how to switch custom kernels, will I still have Magisk or will I have to reinstall the zips?
[Magisk] pcriz:
If the kernel has a flashable zip then flash it. If you boot and magisk says it isn't installed then go back into recovery and flash that.
[Magisk] EstiR86:
Okay cool will try this later
[Magisk] JellyRollz:
What combination of Magisk and the tethering module versions works for you?

goodwin_c's Unofficial Magisk v12.0 and Tether Enabler v10 works for tethering (grandfathered Verizon UDP plan), but SafetyNet fails as expected.

Unofficial Magisk v13.4b2 and Tether Enabler v10 passes SafetyNet, but tethering doesn't work. I don't remember if I tried unofficial 13.3.

Tethering Enabler v11 from Github doesn't load in either Magisk v12 or v13 with a "The zip is not a Magisk Module!" error
[Magisk] stargzrr11:
I go into Magisk Manager, downloads, and install the tethering enabler v11. It works, and I still pass safety net.

I'm on Magisk v13.3, Magisk Manger v5.1.1.
[Magisk] JellyRollz:
Ok, thanks for the report. I guess I'll try 13.3 the next time I'm updating.
[Magisk] pcriz:
https://twitter.com/topjohnwu/status/895662487294550019

Some one just got a pixel
[Magisk] jeremy.wang:
I was unable to flash kernel after magisk is installed. Anybody knows how to solve this?
[Magisk] EstiR86:
Woooahhh hopefully some official support will come soon but right now I'm digging this unofficial port thanks for all the work !
[Magisk] wpbear:
Did you figure this out? What was the solution?
[Magisk] EstiR86:
I asked this before apparently all you gotta do is flash the custom kernel and if that doesn't work just flash the Magisk files again.
[Magisk] kurt.gomez:
After you flash Magisk, flash TWRP RC1 and then reboot recovery and flash the kernel
[Magisk] JayCizzo:
Has anyone experienced horrible battery life with Magisk? I installed the August factory image fresh and installed TWRP and Elemental's kernel. I had no problems with the same setup using SuperSU. I'm not blaming Magisk, but I'm not sure what else it could be. I tried using Greenify but it doesn't seem to be helping much. Any help or recommendations is appreciated.
[Magisk] Soooperstar:
I use it with greenify and average about 20-24 hours with average use and about 18 hours with heavy use
[Magisk] MArtyChubbs:
Has anyone tried to install the xposed magisk module?
[Magisk] EstiR86:
Are you using the Greenify module or the app?

No I doubt anyone has since Xposed for nougat is still under development

Also if I can ask for a feature can you try and make and make a workaround for 2 special modules one is BusyBox for NDK and the other is the Greenify module. I believe all the Greenify module is trying to do is make Greenify a system app which it fails to do however it displays a success message and I'm not quite sure about the BusyBox module as it is a little more complicated. As always thanks for your time and hard work incorporating Magisk into the A/B structure for us Pixel owners.
[Magisk] MArtyChubbs:
Most of the apps on xda are still in development, lol.

People are installing xposed on 7.1.2 via flashing. Pixels are the oddball just like with Magisk due to A/B. I bet xposed will not work, but I gotta try anyways...

https://xdaforums.com/showthread.php?p=73092562
[Magisk] EstiR86:
I understand that but I thought it was clear from reading the thread that Xposed doesn't support the A/B partition set up yet.
[Magisk] MArtyChubbs:
Are you being a smartass? Seems like it. No ****. Is that what was asking? Forget it... You don't understand.
[Magisk] EstiR86:
Maybe I don't understand your question if your talking about the Magisk modules available for Xposed in the Magisk manager app those won't work with the Pixel or devices running 7.0 or higher. Same with the unofficial Xposed yet I haven't looked at the submodule verison yet but maybe that is what you were referring too. Sorry if I came off as a smartass
[Magisk] pcriz:
This would all be solved by just flashing it yourself.
[Magisk] MArtyChubbs:
No It would not.

---------- Post added at 02:56 PM ---------- Previous post was at 02:46 PM ----------

Sorry, I thought wrong. I was the one being a ****.

If magisk works on the Pixel, will the framework hide the pixels a/b boot partition issues from the module? Ill find out. Unfortunately I am on my daily driver and I am an old man, so have too much going on to do something that is a known failure, that's insanity.
[Magisk] raynan:
You absolutely can, but for those not too comfortable with the process, I figured a quick app would help. If it's still relevant, I attached it here. All it requires is root (for obvious reasons). I also have a screenshot of the task used to make this app if you want to create a boot scenario to automatically launch it via Tasker.

Edit: forgot to specify that the app needs to be opened manually after each reboot, but only takes a second and you're good to go.
[Magisk] graymatic:
I am having the same problem. (ERROR 1) when attempting to flash. Currently on ResRemix
[Magisk] kartikb:
Safety Net failing on the newest b1 build. Log attached.
[Magisk] cmo220:
There were a lot of issues with the 5.1.0 official app. Some people said the older app worked though. There's been an update since. But since the Pixel one was 5.1.0 I didn't upgrade that. I only installed b1 version over the new10 version. It's been three or four hours now. No problems with root or hide.
[Magisk] Cares:
Really weird behavior. I had no issues with v13.2 earlier. Then suddenly kept saying not rooted. I upgraded to b1 and I'm rooted now but not passing SafetyNet now.
[Magisk] Soooperstar:
Just installed the b1 version over 13_10 and working fine for me so far
[Magisk] WyldOne91:
Just installed B1 with the most recent app update as well, safetynet is failing again though :/
[Magisk] Soooperstar:
Are you guys flashing over 13_10? Everything is passing for me
[Magisk] WyldOne91:
No, lemme download that and flash one over the other and I will report back.
[Magisk] pcriz:
Isn't magisk hide still eventually crashing though?
[Magisk] WyldOne91:
Just tried it, no luck. Still failing the safetynet.