yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
From the beta thread OP:

I'd guess he's waiting with the Pixel until he has one in his hand...

That sounds like it could use an opened issue or a pull request on GitHub.
[Magisk] goodwin_c:
The opened request is very outdated. I have spent days debugging v13 on Pixel. Now i have it working, i have all fixed source locally. In next days i'll update my github repo. But still can't get any response from topjohnwu - he is ignoring me everywhere, this gives really bad feelings. So i'm not planning to make any more pull requests.
[Magisk] ilatimer1:
Well I tell you what, if there is anything you need, let me know and I will see if I can help.
[Magisk] goodwin_c:
If somebody is interested on Magisk for Pixel - here is my upload folder https://www.androidfilehost.com/?w=files&flid=183895

Currently, latest zip and manager has suffix "_new10"

By the way, "new10" has core mode already fixed - let see when it will got fixed in mainstream :)
[Magisk] FartyParty:
Anyone know anything about this :D?
[Magisk] Didgeridoohan:
I was talking about opening an issue or pull request for the Core Only mode bug you mentioned, not the Pixel support...

If you're talking about him not responding to PMs, I'd be surprised if his inbox isn't completely swamped. He has previously mentioned that he will reach out to the developers that has made progress on Pixel support. From what I understand he's had a whole lot of real life going on the past few months (school), so I guess priorities has had to be made. It's also been pretty clear that Pixel support hasn't been a priority so, like I said, it's probably a matter of having to wait until he has a device in hand.

But yeah, I get it that it can be discouraging and frustrating not getting any answers. Been there, done that... All I'm writing here is just guessing, but I'm just trying to get you to reconsider and continue to contribute. :good:
[Magisk] ariy11:
I did that thanx
[Magisk] Didgeridoohan:
All I know is from the "Known Unsupported Devices" section of the beta thread OP:
[Magisk] FartyParty:
Refer to what info though. I sent a PM to the guy that patched V12.

Magisk is really awesome so I would love to use V13 as well.
[Magisk] Artim_96:
The beta thread says unsupported. But I thought that was changed a while ago to "problems with sunny devices with secondary boot image" since tools to handle the elf format should be available. But maybe there where more problems, so wait for the official v13 and test it
[Magisk] goodwin_c:
Don't worry, i'll not leave my lovely pixel without some little of magic :)

And i'm not complaining anybody - i'm very thankful for all topjohnwu contribution. He is only a reason that this projects exists.

What i'm saying - i prefer to keep everything in one place, to bring Pixel family support into mainline. And not keep it as separate fork. But currently this is only way as i can support Pixel.
[Magisk] FartyParty:
Haha "sunny".

I will, thanks!
[Magisk] Didgeridoohan:
Like it says: the info you get when flashing v13.0 in custom recovery...
[Magisk] FartyParty:
Oh, makes sense now. I will try it when it gets released and see.

---------- Post added at 11:28 PM ---------- Previous post was at 11:18 PM ----------

Haha well that was simple, got update notification, installed and rebooted.

Works flawlessly :).
[Magisk] digital0:
Intel Cherry Trail tablet, Android 5.1. The latest beta worked, 13.1 installs, but no su available:

$ adb shell

root@inet_w:/ # su

/system/bin/sh: su: not found

Log attached.
[Magisk] fndpena:
13.1 installed over the latest beta. Works like a charm :)
[Magisk] Sam Nakamura:
Yeah, finally passing safetynet again with my 5+ modules installed, even with Dolby Atmos it works - good job guys :highfive:
[Magisk] Aria.A97:
delete
[Magisk] DodoGTA:
[MENTION=4470081]topjohnwu[/MENTION] Magisk Manager v5.0.4 doesn't play well with the lowmemorykiller

Screenshot attached

I'll attach a logcat later (because it's very late here)
[Magisk] [Lemmy]:
hm. I just flashed 13.1 on my Galaxy Tab S2, and on my S6 edge.

With Magisk 12 (in core only mode) both devices passed safetynet.

Now with 13.1 my Tab S2 passes, my S6 edge fails. Both have the same settings, no modules.

...any ideas?
[Magisk] DodoGTA:
Can you attach a Magisk log from Magisk Manager?
[Magisk] goodwin_c:
Core only mode is broken in v13 tree. I can even point in source where is issue :P
[Magisk] Taiego:
Help

How do i install magisk?

I already have the manager

Thanks
[Magisk] [Lemmy]:
Sure, where do i find that Log?
[Magisk] goodwin_c:
(deleted)
[Magisk] [Lemmy]:
....interestingly enough it works on one of my devices...

---------- Post added at 10:16 PM ---------- Previous post was at 10:12 PM ----------

yep, on my Tab S2 Magisk 13.1 works just fine with core only mode turned on, and the device passes safetynet;

on my S6 Edge I had to turn OFF core mode, and now that device passes as well.

*scratches head*
[Magisk] goodwin_c:
No, basically it works. But it breaks systemless host and magisk hide :) Just try - after boot you will not pass SafetyNet until you will go to settings and re-enable hide manually.

https://github.com/topjohnwu/Magisk/blob/master/jni/daemon/bootstages.c - lines 543-544, it ends doing anything if core mode is enables (and skips systemless host and magisk hide phase)

Fix is easy - instead of going to end, make another label on line 702 and change this goto to line 702. Pretty easy, works perfectly in my Pixel build of magisk
[Magisk] 530farm:
What changes to you make? Do you have the source for your compiled version? I saw a magisk repo, but looks like last commit was a couple months ago.
[Magisk] Iradj:
New build still breaks VoLTE for me , in V12 it worked perfectly.
[Magisk] Mickyman:
Everything works great for me! Altough, I would like to change the language of the app to english but it seems there is no option for that :)
[Magisk] WalkingHat:
In terms of files placed on /system what's changed from version 11.1 to 13.1? A game I have checks for root, but not via safetynet. After 11.1 something changed and the game is able to detect root. Any help?
[Magisk] Captain_Throwback:
No version of Magisk has ever placed any files on /system.
[Magisk] grmcdorman:
For those upgrading from 12.x, I found a couple of issues when using the 12.x Magisk app to upgrade; I had the 4.3.3 version of the app installed:

When Magisk says it's complete and asks if you want to reboot, tapping 'Reboot' (or was it yes?) has no effect. A manual reboot is required.

After rebooting, the 4.3.3 app says Magisk isn't installed and prompts you to upgrade/install, although it reports the device is rooted.

You need to install the 5.0.4 APK from the release thread to get it to work properly (not surprising, considering that 13.0 is a major overhaul).
[Magisk] WalkingHat:
Ah, what about on the root directory?
[Magisk] Ronii10:
Does v4a work with the latest version of Magisk?
[Magisk] Pkt_Lnt:
I did not have what you describe happen to me. I upgraded in the app from 12 to 13 smoothly.
[Magisk] mikePerreman:
Galaxy s6 issue

Hello, I am having this weird issue with magisk, where when I flash the .zip (through TWRP) it doesn't install, I had it installed, followed a tutorial, and it worked perfectly, I rebooted, then went to install a module, turned on magiskHide, and rebooted, on next boot, when I go to Magisk manager it tells me that I'm not rooted, Greenify still has superuser rights and the audio driver that I installed works fine. I tried to install magisk through TWRP, Magisk manager doesn't think that I am rooted.

I have a Sprint Galaxy S6, running 7.0 Nougat, I think that this is the best place to get help for this.

EDIT:

I just got the notification for version 13.1, I'll see if my problem 'mysteriously' disappears.
[Magisk] Ronii10:
Reboot again
[Magisk] IDPBBrisa:
That issue is happening in some devices. my reboot button has no effect aswell. Also, the update broke my settings (if i try to access it, it shows a blank app) and also broke my USB connection. I'm doing a clean flash atm.

Moto G4 plus, latest RR, EX Kernel.
[Magisk] :
Galaxy s5 g900w8

Stock 6.0.1

Success.

Updated from v12 within magisk manager.

Passing SN, no issues. All settings retained.

Thanks very much :)
[Magisk] Pkt_Lnt:
None of that happened to me either. I just had to reapply my Substrtum overlay for Magisk Manager was all, but I expected that. ;)
[Magisk] mikePerreman:
Thanks, That did it, now if feel like an idiot, lol
[Magisk] Ronii10:
No problem :)
[Magisk] zagzag99:
So i got updated to 13.1

Root is fine.

Only thing is that none of the audio mods are working now.

V4a is installed but the app indicates no support.

It was fine with v12.

I'll need to find another way to boost Bluetooth volume...

A question, now in v13 can apart from better su hide can magisk fake the phone encryption?

Unfortunately my phone can't encrypt and yet i would be glad if i could pass MDM.
[Magisk] RagingHarry:
I can't get it to install the driver, osmosis busybox worked properly on the beta but doesn't work on 13.1Magisk.
[Magisk] jenslody:
v13.1 does not install on my J5.

Neither clean nor dirty flash.

I get a segfault in TWRP when modifying sepolicy.

Recovery- and boot-log attached.
[Magisk] akpe:
Updated to 13.1, after boot when I open Magisk Manager it gets stuck on the logo, app does not open. Anything I can try to fix that?

Edit: cancel that, app gave me the "unfortunately magisk has stopped" error but when I pressed to restart, it started without an issue :D
[Magisk] YodaDaCoda:
Enable soft keys

I've created a module and added qemu.hw.mainkeys=0 to the system.prop but it hasn't enabled the onscreen keys (this worked with magisk v12). When I check out /magisk with my file manager I can see that the module installed, but the system.prop isn't included in the module's directory or anywhere in /magisk/.core/.

Does anyone know what I'm doing wrong?

Thanks in advance for any help, and thanks to topjohnwu for such an awesome tool!
[Magisk] JERW28:
Try clearing Magisk Manager app data.
[Magisk] IDPBBrisa:
old modules don't support magisk v13 and manager 5, as stated in the magisk topic stickied, topjohnwu gave devs some time to update their modules, at the next release, magisk manager will filter out all modules on the repo with template version lower than v4
[Magisk] joetan123:
Using device kenzo redmi note 3 with global room MM, magisk was working with v12, however after uninstalling and updating to v13.1 either from the manager or recovery after uninstalling it does not work. If anyone has a solution to this please share, thanks!
[Magisk] foosion:
That was my experience on a Nexus 5, although I extracted and installed the apk from the zip. It never passed safety net despite repeated reboots and reinstalls. I went back to v12.

It worked fine on my Nexus 7, other than needing to manually reboot.

Both running stock marshmallow.
[Magisk] soulark:
Updated to 13.1 via magisk manager (ver: 5.04). After reboot, WIFI can never turned on. Oneplus 3, OOS 4.1.6. Any idea? thanks.
[Magisk] Bolo46:
Thank you so much dev! I got a way faster boot up after updating to the latest version. I loved it!
[Magisk] jhobc:
Flashed the latest version of Magisk 13.1 and when I try to open the Superuser tab it crashes

Device: Zuk Z2

ROM: AEX 4.4

Log attached
[Magisk] Shtiff1:
Good to go here!

XT1254, 6.0.1, stock rom

Installed 5.0.4 over 4.3.3

Installed 13.1 over 12

Rebooted, success!
[Magisk] Ronii10:
Same for me

---------- Post added at 02:06 ---------- Previous post was at 02:03 ----------

I had a similar problem on my Redmi Note 3 running RR (7.1.2) after my phone rebooted both wifi and mobile data weren't working properly I got a message saying "connected but no internet" after 2-3 minutes the internet were working fine
[Magisk] Wolfcity:
So modules like Arise compatibility, Tasker root support or doze for GMS won't work until their Devs update them?

Or is it just not foreseeable if a module work?
[Magisk] young666:
Crashed superuser

Same here :(
[Magisk] ibaii:
Same here. WiFi never turned on in magisk 13.1 in my OnePlus3.
[Magisk] romskidd:
I think there is a version of it for SuperSu but it's better if you go stock and install phh superuser..
[Magisk] djjohnnyblaze:
I'm starting to become fairly certain that there is a limit to how many directories/files can be mounted due to the size of /magisk.

If I only mount a fgew directories they mount without any issues and the logs show that. If I try to mount everything that the ARISE sound mod requires, things don't get mounted and the logs get cut off.

Can anyone confirm this? I imagine its due to the size limitation of /magisk and being overwhelmed when mounting the dummy system.
[Magisk] DanielF50:
From what I can establish, the magisk directory is mirroring the whole system partition under ".core", within a system image (.img) that changes size depending on what you flash.

Eg. Without OP's V4A installed, my magisk directory was 1.8gb, but with V4A installed it's measuring at 2.10gb.

Im not confident that we would be able to get the ARISE system installed and working without any input from OP or at least until they come out with a solution to enabling modules from the Magisk manager app, as I can't find any documentation that would help us do so.
[Magisk] Skyrocket2Paradise:
Is it possible to modify phhs superuser to support FlashFire? Sounds like you've been doing a lot of work! Can't wait to give everything a try!
[Magisk] KAsp3rd:
[MENTION=4470081]topjohnwu[/MENTION] I recommend we ask a mod to throw a link to a Q&A thread as you are soon going to get a crap load of "How do I use this" due to the new Pokemon Go update (which uses SafetyNet to check for root)
[Magisk] adrman:
I haven't used it, but I've read that FlashFire works if you set selinux to nonenforcing in Magisk.
[Magisk] jhedfors:
I just tried this. While the FlashFire app loads when toggling selinux, it does does not complete the backup task, and I have to hard reset.
[Magisk] SecSpyral:
so i'm assuming this is impossible for users with the g935p since we dont have a custom recovery? is there anyway to achieve this method by working backwards with flashfire?
[Magisk] cire27rn:
Anyone who tried this and made latest pokemon go working? Can you give me some instructions?
[Magisk] sohsatoh:
Hi.

I'm using nexus5x with custom rom, kernel, and Xposed.

Then I installed Magisk, phh's superuser, and systemless-xposed.

But I cannot use android pay....

How to fix this problem?

Sorry for my English.
[Magisk] dabenaute:
+1 plz
[Magisk] nyknight77:
Yes, we need some guidance for pokemon go please
[Magisk] MWin123:
If you unrooted via SuperSu and uninstalled Xposed with the .zip uninstaller and Pogo still doesn't work, you can wipe your /system partition with TWRP. Unrooting and uninstalling Xposed made Pokemon Go work again for me, but I wiped /system to make sure nothing was left behind that could interfere with Magisk. You have to flash your ROM (and gapps) after wiping /system. I didn't lose any data that way.
[Magisk] Portgas D. Ace:
What more of guidance do you need beside reading the OP, which will tell you how to set up your device to use Magisk? If you aren't willing to read and figuring out how to do it yourself, you are in the wrong place.
[Magisk] AvisAile:
Hi ! Do magisk is compatible with android 7.0 nougat ? because I have android 7.0 in my phone and I yould play at pokmon go ... Thanks :)

PS : same question for xposed :)
[Magisk] renezada88:
Hi! Could someone please help me?

I did everything that was stated on the guide including flashing my ROM again.

After installing all the apps root can not be checked and I can't use root apps at all.

Thanks a lot!
[Magisk] cire27rn:
I dont know what to do after I flash the stock rom. Do we first install the latest PoGo app from the playstore and flash magisk? Or flash first magisk then install PoGo? Supposedly it was finished, what do we do before opening the game? Do we have to unmount and remount then open the game or first open the game whatsoever. Sorry im a newbie to this magisk.
[Magisk] Artim_96:
Magisk should run, XPosed will not. And it won't unless the official version has been updated to work with SDK 24
[Magisk] Blueblob:
PG is working on my side with SuperSU method.

Flash magisk then SuperSU for magisk

Reboot, install magisk apk.

Before playing PG, unmount root and enjoy :)

Remount after your PG session ;)

Where is my Pure Nexus ROM ? ?
[Magisk] SynaTech:
Magisk manager refuses to open after installing 13.1
[Magisk] Viggen66:
On magisk 13.1 on my android gadget it won't boot at all, it stays at splash logo
[Magisk] soulark:
I have to use Magisk-uninstall-20170711.zip to uninstall it, and then install Magisk-v12.0.zip, WiFi works again. Just downgrade to v12 doesn't help.
[Magisk] Codebucket:
Is it only for me or is SafetyNet Test failing when you have systemless hosts enabled in Magisk Manager?

System: ViperOS 2.1 (Android 7.1.2)

Device: Redmi Note 3 (kenzo)

Magisk: v13.1 with core mode enabled
[Magisk] 24imelqui:
Is the uninstaller backward compatible?
[Magisk] vasujahagirdar:
V13.1 fails

Got notification about new version, tried to install, but it's fails, tried also through twrp, still fails !!

Now manger says no magisk installed. Tried many times.mine is htc 10 device with viperone 5.10 rom. Help
[Magisk] raddatt:
Does anyone know how to use the new multiuser function?
[Magisk] jeffreymcclain:
For me, disabling core only mode fixed it. Previously with 12.1, I had to enable core only mode. Odd.

- Nexus 6P
[Magisk] Kiid:
Magisk not installed.

Still getting the magisk not installed/no root error in Magisk Manager. No matter how many reboots, clean installs (uninstall magisk, flash stock boot, flash magisk etc) or dirty flashes I do, still get the same thing. Any ideas?

Edit: will try to get the magisk logs.

S6 - NNE4.5 - 7.0
[Magisk] ketwi15:
Clear app data in Magisk Manager
[Magisk] RagingHarry:
Clear data cache of current installed Magisk, then uninstall.

Extract magisk.apk from latest magisk.zip.

Reboot and install magisk.apk.

Then you should be fine.
[Magisk] WalkingHat:
What about on the root directory?
[Magisk] Emenaria:
So I noticed this in the latest changelog.

"- [General] Remove bundled busybox because it causes a lot of issues '

What does it mean?

I updated to v13.1 but I still have a module called "busybox for Android NDK" in Magisk Manager. Should I delete it?
[Magisk] bluenote73:
On Axon 7 A2017U after MM uninstall plus flashing magisk uninstall then stock and boot.img flash, installing magisk v13.1, then magisk manager keeps crashing when anything tries to request SU. adb shell su reports 'permission denied'.

Then after this, every time MM opens it crashes right away.

If I uninstall MM, or clear data for MM, then I can enter MM once, and after that it crashes repeatedly, and still no SU functionality.

Thanks so much if anyone can look at these logs and see what the problem is.

thanks

Problem history on github along with boot.img: https://github.com/topjohnwu/Magisk/issues/229

Here are my logs:
[Magisk] yochananmarqos:
Upload it and I'll take a look.

He didn't say modules using the template v3 and older won't work with Magisk 13.1. The person you're replying to could have created the module with the new v4 template for all you know.

They work with Magisk 13.1. The module devs will need to update to the v4 template in time for the next version as was stated.

Clear Magisk Manager app data.

Yes.

You tried the same thing that didn't work many times expecting a different result? I think there's a mental condition related to that... :p

Uninstall Magisk, flash your stock boot.img then Magisk.

No, because topjohnwu hasn't released the documentation yet. He's working on it.
[Magisk] Kiid:
Thanks for the suggestion mate, unfortunately that didn't work

either. Might have to go back to the beta
[Magisk] [•G-SpotteR•™]:
Same on my end Magisk Manager crashes every time I access the superuser tab.

Superman ROM

MAGISK ZIP V13.1
[Magisk] AmineHadef:
Hi, i just updated from v12 to v13.1 and i have this problem when i try to open superuser panel .. Help

Edit: solved

-cleared app data
[Magisk] yochananmarqos:
This issue was already mentioned and two people including myself already instructed to clear Magisk Manager's app data.
[Magisk] adriansticoid:
Anybody got TiBu to work in 13.1? Other root apps work except for TiBu. Others include Kernel Adiutor, Link2SD, L Speed, Greenify, Root Explorer, Terminal.
[Magisk] jhobc:
Thanks! Supersu Tab opening normally now.
[Magisk] YodaDaCoda:
Here you go (attached)

Edit: I'm an idiot and didn't set PROPFILE=true in config.sh. Fixed version attached for anyone that wants it.
[Magisk] Captain_Throwback:
What about it?
[Magisk] yochananmarqos:
Yes, I just granted it root privileges just now.
[Magisk] admiralspeedy:
I don't want to sound like a ****, but why do you completely ignore Goodwin on Git? According to his posts, he has repeatedly tried to contact you because he has added support for the Pixel and Pixel XL to Magisk, but you simply don't reply or acknowledge him.
[Magisk] kgr:
I updated to v13.1 today, and it seems to be working ok. But I still have problems with MagiskHide not enabling on reboot - the switch is on, but its not working; the solution is to toggle it, or to run the following in terminal emulator and its all good until the next reboot.

magiskhide --disable

magiskhide --enable

Does anyone know of a fix for this - I'm even thinking I could run a script at boot, but I haven't a clue how to do that lol.

I'm happy to upload logs here if that would help at all :)
[Magisk] admiralspeedy:
But does it work...? Since switching to Magisk I have never been able to restore or remove system apps with TiBu because almost every root app is unable to mount /system as RW. The only two apps I've found that can do it are FX File Explorer and Root Explorer. I can mount it fine with SuperSU and with Magisk if I do I try to manually mount it through a terminal, it tells me that /system isn't in /proc/mounts.
[Magisk] adriansticoid:
Dafuq. I don't know why only that app doesn't work. I already tried reinstalling it.
[Magisk] kgr:
I had this problem early on when I switched to Magisk - I just used the terminal debloater module to remove system apps.

I think TiBu is working for me now to remove apps though.
[Magisk] Shtiff1:
Yes
[Magisk] bobonit:
I'm having the same issue. I tried your suggestions and it didn't help. But just to clarify, I cleared data cache for Magisk Manager, then uninstalled Magisk Manager. I then performed the rest of your steps. Still shows Not installed/No Root.

FYI, this is on an older HTC One M8. I had to use the "Magisk-v13.0(96f8efc)_dev_random_busybox_var_path.zip" beta in order to get to install previously. I even tried the latest uninstaller.
[Magisk] m0han:
https://play.google.com/store/apps/details?id=com.rerware.android.MyBackupPro&hl=en

could you guys here try to run this app and see if you can make backups of all your apps + app-data. i flashed magisk 12.0 and busybox 1.26.2 (3rd july release by osm0sis) and i can't. any help to get things working would be nice. many thanks.
[Magisk] dudeperfect:
Magisk manager force closes after updating to v13. 1 :( please help.
[Magisk] kgr:
Clear app data and/or uninstall & reinstall the app.
[Magisk] PhrostB:
Good work jw. I haven't updated yet but I just wanted to say thanks. This is clearly a labor of love for you and the community appreciates all you do for us :)
[Magisk] JonathanRAZ:
[MENTION=4470081]topjohnwu[/MENTION] for the play store uncertified.....this is what i have done if i do a clean rom installation i setup first and as soon as i get to the homescreen i open magisk first than anything an tap to verify if saftynet is succsesfull if it does you should get certified because sometime even if you know mahisk works and safetynet you might get uncertified.....and this is another case if you already have uncertified try clear app data of play store after having a uncertified and after clear app had certified.......verify if it works for you on the htc i have done this on my note 5
[Magisk] Flole998:
I'm also having issues with latest 13.1 and HTC One M8 (Google Play Edition). It always shows "not installed". 12.0 is working perfectly fine.