yashsingh1/xdaforums huggingface dataset:
[Magisk] tdunham:
There are hundreds, probably thousands of different setups between phones, manufacturors and rom variants so that is why the developer prefers a clean install with the proper documentation for issues. And the support team is getting a little frustrated at the users that aren't abiding by the steps posted on the op and just posting for the sake of it.
[Magisk] Sirence:
Audio Modification Library 1.4

Dolby Atmos r6.5-c

Installed these earlier today but now I can't add any others.

I removed the Dolby Atmos one to see if that would install again but it now gives the same error.
[Magisk] demonoidmaster:
Yh ik

---------- Post added at 09:30 PM ---------- Previous post was at 09:29 PM ----------

Flash them through twrp and see what it says in logs
[Magisk] Sirence:
They install without error in twrp, and show up in magisk. The log in the manager is still empty and I still can't install from within the app anymore.
[Magisk] demonoidmaster:
No i meant TWRP log not magisk. In any case some modules upon being installed may finish and appear in the list and saying you need to reboot but in reality said module actually like screws up a users magisk install, so best bet is to send your logs to the devs of these modules so they can fix it

Just reinstall magisk in TWRP and only flash modules you're certain 100% work flawlessly
[Magisk] Sirence:
Oh sorry, do you mean the lines that show during the installation? Those seemed all fine, no error and a success message at the end.
[Magisk] DenyDarko:
Best wishes for your exams. That's way more important than volunteer debugging :)

We'll be around spamming the thread with logs when you finish xD
[Magisk] majee12:
No luck flashing . Return error 1 . I have gone through the fixes that have been uploaded here but still no luck .
[Magisk] shadowxp13:
Bug Report

Hi, i've been using magisk's stable version for months, and when the beta launched i switched to it. Every other beta was fine for me, but then when i flashed beta 96f8efc my phone started to have some crazy behaviours. When i rebooted from twrp to my rom (LineageOS 13) my launcher, package installer and settings app just crashed. Then i tried to open Magisk Manager, and when i done that, my screen just froze and the phone started playing its boot animation again, and after some time it booted again. Then i tried to uninstall Magisk Manager, and when i was going to uninstall it the package installer crashed,so i tried again and the same thing happened. I was using an shortcut, so i tried the normal way of uninstalling an app (System Settings>Apps) then Settings App crashed again. When i was doing some tests i decided to force the uninstalling of magisk manager by deleting its folder in /data via TWRP's file manager. For my surprise when i rebooted the system everything was fine, and nothing was crashing anymore. I made two logcats and two dmesgs, and these are done from boot and from the screen froze/reboot.

Info:

ROM:LineageOS 13

Phone: Galaxy Grand Prime (gprimeltezt)

Magisk Modules: Xposed Systemless

Logs: goo.gl/6s41TF (That is a link. i don't have 10 posts, sorry...)
[Magisk] ThE_DeamoN:
My problem was Substratum overlay for play store… shiz happens when you forget what exctly is modified :)
[Magisk] demonoidmaster:
Installed them through Magisk and can confirm they (whichever one of the two) wipe the /magisk folder if you reboot

I'll try flashing them through TWRP after i flash magisk zip again
[Magisk] Munyola:
Before you could have been performing rom,you should have been backups the data and whatever to help in case of failure. Try to rom Clockwork recovery and then consider dev for required teamwork mode for your setting programming.
[Magisk] firebrain:
Seems offline. Can you relink it?

If you upload to my gdrive I will host it.

https://drive.google.com/drive/folders/0B7fNZAj0wN-4Tkc4bFoyUHlkQjQ?usp=sharing
[Magisk] yochananmarqos:
The modules aren't being wiped, the magisk.img is failing to mount. It seems to be an issue a few were having including myself.
[Magisk] Iradj:
How i can set a prop on the beta ? cause on Magisk v12, I could adjust the magisk hide script or entered the command in a terminal but the down side in terminal is, it reverts after restart so it have to stick on reboot. Do I now have to make a modul for this ?
[Magisk] eos:
Magisk kills Netflix???

Hi,

I have managed to install Magisk v13.0 (96f8efc) on my Samsung Galaxy Tab S3 (SM-T825) with root working and SafeNet being completely green. One thing I have noticed so far is that while I can run Netflix on a virgin firmware, with Magisk installed Netflix will not get past the initial screen and eventually gives up entirely displaying the error code -9. Please note that I have tried all possible combinations (known to me) including running Magisk in core only mode, selecting Netflix and PlayStore in Magisk Hide etc. I am also attaching whatever log files I could collect so far. Please let me know if anything is missing or if I should have tried something else altogether.

Now, because I started off here https://xdaforums.com/galaxy-tab-s3/development/recovery-twrp-3-1-0-1-samsung-galaxy-t3581359, I have figured out by now that if I install the permissive kernel from ashyx there will be no more issues with Netflix. However, I would like to avoid running a permissive kernel for obvious reasons and doing so also breaks some essential system functions such as WiFi and Bluetooth. Given this observation do you think this has to do with SELinux and some specific policy the Netflix app would require to run under Magisk?

Many thanks for your help!
[Magisk] demonoidmaster:
So did some testing and these modules only install via TWRP properly (update your twrp to 3.1.1-0 cuz what ya using is outdated) and show up in Magisk on reboot, /magisk folder is populated with the modules and stuff too so yh

However, I just tried installing a random module via Magisk and on reboot everything is gone, so my guess is that the culprit is Magisk Manager (seems like it is)

*Tl;dr install your Dolby and Audio Mod modules through TWRP, not Magisk.*

---------- Post added at 10:57 PM ---------- Previous post was at 10:56 PM ----------

Or that lol, seems like Magisk Manager ain't doing it's job right when installing modules

---------- Post added at 10:59 PM ---------- Previous post was at 10:57 PM ----------

Are you using Magisk Manager 5.0.2? Cuz Magiskhide is in it so..
[Magisk] Bright09:
hi i have issues setting se enforcing to permissive it doesnt seem to find adb shell in terminal or is it missing su binarys or something im lost any one could help thanks since switching over to magisk from supersu i just flashed lineage os and then latest magisk on my nexus 7 2013 any help thanks
[Magisk] Iradj:
Yep 5.0.2 installed
[Magisk] phenom97:
I managed to get v13 installed. the v3 posted worked for me.

thanks everyone!
[Magisk] jenslody:
I already updated the post and attached a newer zip to it.

My hoster currently has issues on some systems, unfortunately my (v)server is on one of them.
[Magisk] _litz:
Been on my list of things to get to, just did so
[Magisk] equitharn:
The install probably messed up with your phone's host file, I guess.

In '/etc/hosts' remove everything except the first line or update host file via AdAway.

You'd probably already know it just FYI In case anybody else stumbles on the same.
[Magisk] Brasstear:
Quote:

Added new logs - finally found the "magisk_debug.log" after the phone (Samsung SM-901F) won't boot after installation in TWRP. Sorry for this triple-posting.
[Magisk] Iradj:
For now there is no fix or Hiding possibilty but just out of curiosity, i compared the SEQR App Version 2.6.23 and 2.6.27 and i found out, that both have the same Root-Detection but the only difference is, that the OLD 2.6.23 version searches for ROOT-BUSYBOX and the NEW 2.6.27 dont have the busybox line instead it searches for ROOT-FILES. The rest is the same. So this is just what i have found out, now how we hide root files that it searches i dont know, thats maybe something we will never find out.
[Magisk] firebrain:
Thanks for the updated link. Still getting error 1

On Pixel XL 7.1.2 stock unlocked.
[Magisk] tdunham:
That is not a currently supported device for this beta right now.
[Magisk] demonoidmaster:
Why are you trying to use LineageOS AddonSU with Magisk v13 and the Manager? It already does root.. what you're doing is illogical
[Magisk] :
Sorry off topic but I need some MOAR knowledge from the greatest. Thank you for supporting community. Op you are legendary also thanks for all your time n hard work.
[Magisk] :
Samsung Galaxy S5 klte

CosmicOS 7.1.1 20170429

Magisk 13

Hi, when Magisk is enabled (so without core mod) Snapchat and Twitter stop working but, when I activate the core mod Snapchat and Twitter working perfectly..

Any ideas to fix this? ?
[Magisk] carefen:
great !!
[Magisk] Tesla:
Best comment in the whole thread :good:
[Magisk] H4X0R46:
Posting new results here. Just reinstalled my stock boot.img file, my custom kernel, my multirom zip (BEFORE Magisk, key word here) and then Magisk. It's working just fine! Passed safety net just fine. To anyone that uses multirom, flash your multirom zip BEFORE Magisk beta.

Device is a Nexus 6, guess I should've mentioned that sooner lol
[Magisk] p34rp34r:
I'm not sure if anyone answered you, but I think the same thing happened when I installed the latest beta. What I saw mentioned elsewhere (I forget where...) was to extract the magisk.apk and then manually install it after flashing and rebooting. That worked for me.
[Magisk] putti71:
I have the same problem
[Magisk] Noor9933:
Not working on miui 8 nougat on my redmi note 4 (mido)

---------- Post added at 08:17 AM ---------- Previous post was at 08:13 AM ----------

Anyone here who had pass safety net feature on miui 8.

Please reply .. the process

Thanks in advance.
[Magisk] aseferfan:
Okay after testing for quite a while on my SM G900F These are the results i found,

1.Fixed zip from here solves error 1 during TWRP installation of magisk

2.no long time install error on my device

3.safety net passes successfully with no modules enabled

4.module installation inside magisk manager fails (on first method),2nd method sometimes works (the file method)

5.after installing modules and rebooting magisk fails to load modules.rebooting again fixes it

6.'no module load error' can be avoided by flashing the modules from TWRP

7.The only module i found to be keeping safety net green with enabled is SD card write access enabler Any other module whether it comes with system app or not seems to trip off safetynet(verified : verified V4A Audlib version,Magic Folder Binder)

8.Have not tested Unified host enabler but first time i did it it seem to have disabled all my modules and i had to reinstall v13 of magisk

I have added some logs as well with one tripping safetynet red with magic folder binder enabled and another one with safety neet green with sd card rw enabler enabled only

EDIT : if anyone knows any way to get at least V4A working with magisk and safetynet green and also any way to get the folder binder working with safetynet green to mount internel foldder to externel sd please let me know,without those modules the device really is a brick xD
[Magisk] suvam69:
SN?

Modules- only ARISE magisk compatibility
[Magisk] marceldenice:
Hello,

I would use the application "Molotov TV" on my Galaxy S7 Edge. When connecting this application to a TV channel I get the error message "Error while recovering the DRM license".

So I installed Magisk-v13.0 (96f8efc) and Magisk Manager-v5.0.2 to replace SuperSU. I activated Molotov in Magisk-Hide and checked that SafetyNet was turned off.

In spite of this I always have the same error message with Molotov TV

For information I installed the rom SuperStock V2.8 and SuperKernel V2.6.1 on my S7 Edge.

Thank you for your help.
[Magisk] Brasstear:
I was just checking opportunities for myself. Neither with or without pre-root my Magisk installation worked out (boot animation for >15min; just resulting resulting in a hot device).
[Magisk] white7561:
Don't think u should check ur apps on the magiskhide tab. I think the check is for bypassing the magisk hide
[Magisk] witekkowal:
Hi,

I can confirm that this version works fine with SM-G900F on LineageOS. Safety Net is OK. I had to unistall previous version of Magisk (12.0) and then flash 13.0.

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Magisk] marceldenice:
@ white7561

Thank you for your answer. In the "MagiskHide" menu I tested the following two solutions:

- Case "Molotov" activated  does not work ("Error during the recovery of the DRM license") at the launch of Molotov TV

- Case "Molotov" activated  does not work ("Error during the recovery of the DRM license" at the launch of Molotov TV
[Magisk] danmaman:
OnePlus 3T with Open beta 9

And stock kernel

No problems here
[Magisk] Brasstear:
Have you had to wait long for the initial reboot?
[Magisk] witekkowal:
No, as usual.

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Magisk] Zeghio:
Flash magisk unistaller. It should work. Else u need to flash ur ROM again.

Enviado desde mi LG-D855 mediante Tapatalk
[Magisk] Artim_96:
As long as you didn't delete it is backed up in /data
[Magisk] Brasstear:
Flash Magisk Uninstaller from

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445
[Magisk] scorpion112:
im already rooted with supersu

and i need to root with magisk

---------- Post added at 11:38 AM ---------- Previous post was at 11:35 AM ----------

im rooted with supersu and i need to root with magisk
[Magisk] adekboreanaz:
Unroot via Supersu app on setting, then flash magisk again, that should be worked but if it doesn't dirty flash your rom flash magisk
[Magisk] Didgeridoohan:
The Magisk Hide tab is used to hide root from apps that aren't using SafetyNet (that's hidden by default). If you have an app that you want to Hide root from you check it in the Hide list.

Many apps use proprietary ways of detecting root that Magisk Hide can't bypass.

Are you taking about an error that states your boot image is patched by other programs? You'll find a clean boot image in your ROM/firmware package. If the ROM doesn't come pre-rooted with SuperSU that is. Ask in your device's forum/ROM thread.
[Magisk] Brasstear:
You tried uninstall/unroot supersu before flashing magisk? There's an option in supersu app itself for that.

Or try it with "UPDATE-unSU-signed.zip"
[Magisk] bnbagiz:
magisk is deleting my modules ?! this appears to happen after i installed viper4android 4.1 via twrp cause via magisk it does not work for me.

and sometimes magisk does not show anything in the supersu tab ? after my modules got deleted, the supersu tab is showing everything it should. whats going on ?
[Magisk] scorpion112:
Are you taking about an error that states your boot image is patched by other programs? You'll find a clean boot image in your ROM/firmware package. If the ROM doesn't come pre-rooted with SuperSU that is. Ask in your device's forum/ROM thread.[/QUOTE]

yes i have error message boot image is patched by other programs were i can find this clean boot im on superman rom v2.5
[Magisk] Didgeridoohan:
Well, since you have supersu you need to first uninstall that. If the ROM comes pre-rooted that might be a problem. Go to your ROM thread for advice.
[Magisk] demonoidmaster:
You're literally flashing root along with Magisk which already goes root...
[Magisk] RedAntares20:
Samsung s6

G920FXXU5EQCD

TWRP 3.1.1-0
[Magisk] DvLAx3l:
Hi guys, just trying the v13 latest beta, uninstall with the uninstaller, reboot, then flash through recovery and the magiskhide dosen't work... Here is the log, if someone can help me, tell me what to do and I will do it! :D

Device: Samsung Galaxy S4 GT-I9505

Rom: JDCTeam 7.1.2 Optimized LineageOS 14.1-Stable4

Recovery: TWRP 3.1.1-0

I had problem also with the Magisk v12 stock included in the rom.
[Magisk] apophis9283:
The boot image has been patched by other programs hints at you've flashed something else that modifies the boot.img????
[Magisk] Didgeridoohan:
That's probably gonna be SuperSU. Magisk v13 is dropping SuperSU compatibility. Completely remove SuperSU before flashing Magisk. That includes the patches done to the boot image...
[Magisk] digital0:
Fails to install on ONDA oBook 20 (Cherry Trail Intel Atom tablet). Log attached.
[Magisk] ElSalvatore:
Do I understand this correctly: in v13.+ if I activate Modules safetynet can't be passed anymore?

I've been trying for over 2 hours now to get that safetynet pass - without success.

I'm on TugaPower 37 and Franco 50 on my OPO.

Apparently modules make the safetynet check fail. Does anyone know if this happens with any module or only with specific ones?
[Magisk] apophis9283:
Im using the latest beta with modules and its working fine. Make sure you are on the latest beta, if it still fails check other points of failure.

---------- Post added at 09:49 AM ---------- Previous post was at 09:47 AM ----------

I am not a pro in this area but...... I think the ROM may have something to do with it not flashing.
[Magisk] Wesley_NL:
Ok i hope this is the right place , i cant seems to pass safetynet, i use the one with random busybox because this regular beta would not install, and dont get error 1 it simply dont go further

I use with the fix for safetynet but no luck

https://xdaforums.com/apps/magisk/beta-workarounds-to-issues-magisk-beta-t3624176
[Magisk] apophis9283:
I know from experience, unlocked bootloader (kernel commits can hide this), Selinux permissive and android debugging can trip it. Im speaking from having a nexus 6 so this may not be the whole story and make sure magisk hide is enabled.
[Magisk] ElSalvatore:
Thanks for your answer!

I'm also on the latest official BETA of Magisk. Switching all modules off helped, as mentioned. I can't seem to be able to pinpoint the reason it can't passt with active Modules. Heres a Screenshot from both, the failed pass and the installed modules:
[Magisk] Wesley_NL:
I have no clue what this is. It was already abit complicated to swap from super su to magisk for me, root itself work fine as far as i can see but hide not

Would be nice if someone can give me a stepped guide ,
[Magisk] apophis9283:
Well, I would be willing to help you and go through a simple checklist to see if I cant help you narrow it down
[Magisk] whiplash1:
Dolby module is tripping safety net for me. But I kinda like that module :( what could be done?
[Magisk] apophis9283:
Try disabling them one at a time. See if you cant pinpoint which one may be causing the issue.
[Magisk] Wesley_NL:
Uhh? What do i have do then?

I gave magisk log

No errors installing the workarround zip

I installed the sn fix

So whats left then?
[Magisk] syamsoul:
v3 installed correctly now on Samsung Galaxy Note 3 N9005 custom MM MagmaNx Rom.

safetynet pass too :):svetius::good:
[Magisk] apophis9283:
Check to make sure adb debugging is off, selinux is enforcing, and possibly its not tripping over an unlocked bootloader. I know in the development of my kernel, we have a commit that hides it.
[Magisk] Wesley_NL:
Sorry i dont have knowlwdge of advanced stuf

I dont even know what adb is and selinux, bootloader exc... i know how to flash zips thats all, im already happy i can run custom rom and use this root but a game suffer from this now and i realy am not advanced enough to know all this in depth scanning or something, i tried what i could by posting the log with screen shots,

But ok its fine i guess i wait till someone do it with same device with more advanced thinking
[Magisk] apophis9283:
Honestly selinux status should be in about phone. ADB debugging is in developer options. Its usually a toggle. Make sure its off.
[Magisk] DvLAx3l:
[MENTION=4392154]apophis9283[/MENTION]

Can you give me a tips or hints to what to do please? I will be very grateful, also I want to help people in the rom main thread ??

I attached the log at page 151
[Magisk] Wesley_NL:
Oh , thx now im helped

Also by adb debug > usb debug?

I dont have adb debug option as far as i can see

But have a option called verify apps over usb

That is the only option with adb in it

Screen shot of kernel
[Magisk] apophis9283:
Your SElinux is permissive, you want enforcing. Usb debugging turn it all off.
[Magisk] Didgeridoohan:
[MENTION=3168239]Wesley_NL[/MENTION] [MENTION=4392154]apophis9283[/MENTION]

Sorry to interrupt your troubleshooting, but the log [MENTION=3168239]Wesley_NL[/MENTION] posted show that Magisk Hide isn't starting or unmounting folders as it should. Have you tried disabling and enabling Magisk Hide? You might have to do it manually by typing this in a terminal emulator:

su
magiskhide --disable
magiskhide --enable

I don't know how much it still applies, but if the above doesn't work there's a section about Magisk Hide not unmounting folders in my troubleshooting guide for v12 here: https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] apophis9283:
So was it working before? If so I would try a dirty flash of the rom
[Magisk] nick1467:
I'm loosing root access randomly,I'm on latest beta however a reboot is fixing the issue,is there any permanent solution? Should I provide any logs?

Thanks in advance

Edit: my device is Moto g3,ROM:- RR 5.8.3, security patch :- may 2017,android:-7.1.2
[Magisk] apophis9283:
Im following your lead sir, I dont know much about specifics. Just trying to lend a hand.
[Magisk] emrozkok:
Would you recommend it ? Im using dolby atmos
[Magisk] DvLAx3l:
Nope, it never worked for me ☹️
[Magisk] apophis9283:
Whenever Magisk Hide isnt working I always go for the main culprits. Selinux, adb debugging and that maybe its being flagged due to unlocked bootloader..

---------- Post added at 11:00 AM ---------- Previous post was at 10:59 AM ----------

I love ARISE. Know quite of few of the developers. Maybe its favoritism, maybe its Maybelline. :)
[Magisk] emrozkok:
It looks really complicated. Is there any magisk or twrp thing for that ?
[Magisk] RedAntares20:
I've just removed the root from the phone
[Magisk] ElSalvatore:
Did that, didn't work. Did it again now and apparently the Viper Module was causing it.

Seems like I jumped that one on the first try... :eek:

Thanks a lot buddy for your help!
[Magisk] apophis9283:
It's a zip that you flash, and you have a prop that the zip reads from when you flash it.
[Magisk] mey139:
Working fine on the latest RR :good:
[Magisk] wrongway213:
Apop! Good to see ya - we love you too, bud :highfive: Hope you've been well
[Magisk] RedAntares20:
I flashed magisk manager, supersu and gltools just enough, but I've always had problems with magisk, although i put the v12 not risked rooting the phone with magisksu.
[Magisk] tdhite:
I can confirm. Attached image 'fixed' relative to the above passes SN on deodexed, deeply debloated custom ROM I made for S6 G920P devices, also with my highly customized kernel that includes/requires a magisk module for boot setup.

Point is, the beta works when cleaned up as needed, so long as the basis ROM/kernel passes, as I see things.
[Magisk] apophis9283:
:) one of my favorites. If you go to the arise thread this guy would answer any questions you have.
[Magisk] jabarel:
i need to activate magisk hide to get all to works?
[Magisk] mey139:
I flash the latest uninstaller 1st...
[Magisk] nguyen4514:
I just wanted to leave some information.

I have flashed the most recent Magisk beta onto my HTC One M9 and M8. On both devices, magisk hide works well with the stock roms. I installed Lineage on both and it seems like everything is running smooth as well. Great that magisk hide is working with or without core mode enabled.

I noticed that magisk hide didn't work well when I uninstalled magisk 12 and installed magisk 13 right after. Magisk hide would work for the first initial boot, but wouldn't work anymore after a restart. Again, this problem only happened if I uninstalled magisk 12 and installed magisk 13 afterwards. No problems when I did a new install on a stock rom or Lineage.
[Magisk] Wesley_NL:
Ok and enforcing? How do i change that ,and do it have any restrictions?
[Magisk] Didgeridoohan:
That's not going to matter unless you can get Magisk Hide to work on your device, which it doesn't...