yashsingh1/xdaforums huggingface dataset:
[Magisk] admicos:
There isn't any Magisk debug files there. There is a magisk.img and a magisk_merge.img which is apparently 2 terabytes (according to mixplorer)
[Magisk] Pkt_Lnt:
apparently 2 terabytes (according to mixplorer)

:eek: :eek: :eek:

Where did you get a phone with that much storage space?!?! :cyclops:
[Magisk] admicos:
I wish it was real lol
[Magisk] vergilbt:
Is working without reboot? Only FC the manager? Will try.

Gesendet von meinem MIX mit Tapatalk
[Magisk] Didgeridoohan:
:eek:

Yeah... That's, a lot. :laugh:

Your Magisk installation seems quite broken. There's been a lot of posts recently and I can't quite remember if you've uninstalled everything and tried again. It might even be possible that a complete wipe if your system could help. Make a backup and see if a clean install makes any difference. Trying different ROMs is also an option.

You have an Axon 7, right? Unfortunately that device has a history of issues with Magisk, so far. There's a few open GitHub issues of varying age: https://github.com/topjohnwu/Magisk/issues?utf8=✓&q=is:issue is:open axon

Magisk v13 is practically a complete rewrite, so compatibility issues might occur.

If you can't get things working, upload a recovery log from the installation and a Magisk log from after booting up to a relevant (or new) GitHub issue. With those, also upload a copy of your boot image.
[Magisk] akpe:
Edit: cancel that, apparently issue has to do with the module itself.

Στάλθηκε από το HTC 10 μου χρησιμοποιώντας Tapatalk
[Magisk] Huskied:
V4A module is seeming to be hard heavy on me. I don't know if anyone is experiencing this but V4A starts up and works on boot. After a few hours or so V4A shuts off completely and at that point it does not detect the module installed. Only a reboot will get it up and running.

Tried reinstalling but to no avail.

I'm running AOKP 7.1.2 Magisk rooted v13 release.
[Magisk] Artim_96:
No problem here. But I don't know if it can now work work Magisk again without letting SN fail. So after fixing the latest SN patch maybe topjohnwu takes a look into that since the version in the modules list was made by himself
[Magisk] Huskied:
Eh, Maybe it's due to the Universal SN fix, and since the version is supposed to pass SN might as well give it a shot.
[Magisk] paolo200:
The magisk 13.2 safetynet fix module works well on my phone it is true for both lines but I'm a bit curious as to how it works exactly what does it change in the system in order to make it pass?
[Magisk] callumbr1:
Since updating magisk manager app everytime I go to superuser in the app it force closes? Also safety net fail. And ideas?
[Magisk] Huskied:
Oh shoot I have the v12 version, I definitely need to update that..
[Magisk] Didgeridoohan:
Crash: https://xdaforums.com/search/thread/3432382?query=Manager crash superuser

SafetyNet: https://xdaforums.com/search/thread/3432382?query=SafetyNet fail
[Magisk] SGE_DEW:
[MENTION=5351947]Iceburn1[/MENTION] thank you for the fix. Worked on Nexus 6p running official DU and RR.

FORZA SGE
[Magisk] DaveX2012:
Hey guys for those who passed safety net, is magisk modules worked for you ? Mine don't work ( non of them magisk modules). S7 nougat
[Magisk] westeight:
The Magisk V4A module needs to be updated. It's temperamental at best and SafetyNet fails for me when I add it on my U11.

Flashed the latest Viper 6.1.zip in TWRP instead and it works flawlessly. Processing for Neutron, Spotify and YouTube :cowboy:
[Magisk] Huskied:
I might have to do that then, Thanks! :good:
[Magisk] :
NP it is not my mod though just so everyone knows, just trying to spread the word, so we can all have working Magisk.
[Magisk] Bobthahog:
Go to your settings and then go to your apps and find magisk manager and clear cache and data. Then magisk manager will not crash on you.
[Magisk] ZerosMadness:
I was going to post yesterday about a slight fix for Nexus 6 users but the thread was locked. Basically I let magisk recover my backup, then I went to manager and clicked uninstall there rather than using the flashable zip. When I came back I was able to pass everything except the bootloader check. I use Pure Nexus on the N64 with stock kernel. So if the issue happens again I'd try to do that as a way to get around it until a fix happens like this. Hopefully no one posted this yet lol
[Magisk] Bobthahog:
Can someone please help me out? I have tried 3 or 4 modules that use template v4 and none of them install. When I add them in the Magisk manager it shows that they install but when I reboot it still shows the red letters saying module will be updated on next reboot. When I pull the log from Magisk manager it's like it doesn't even show that module was read. I have attached a screenshot of what it looks like after I have installed the module and Rebooted and also attached a log. Could someone please find out why no module using version 4 template will not install on my phone. I am using a Sprint Galaxy Note 5 and everything else is running smooth. I am passing safety net with the work around posted earlier. But for some reason no module that is version 4 template works. As soon as I flash a module using version 3 template it works just fine.
[Magisk] bluenote73:
Speaking of the Axon 7 (but maybe different variants) would you be so kind as to interpret the last logs here and comment if you see anything that makes sense as far as a cause?

https://github.com/topjohnwu/Magisk/issues/229
[Magisk] RagingHarry:
Just a small thought, the quick fix module provided earlier in this thread.

Wouldn't it be easier to maintain Magisk and those Google checks... To be it an updatable and maintained module?

Instead of it being given a quick fix as it is for now..

In other words, what the quick fix is now for safetyNet, and Magisk every time needs to updated for it (when Google hits that bin/flush) . Could it be an effort for maintaining Magisk to turn the Google sheit play stuff, to turn into an updatable module, since that would mean for (the more difficult devices) /most devices just a single reboot.

Also that would result in far less needed updates of Magisk., but just a check module update ;)

Just my thoughts atm..
[Magisk] serajr:
Already tried that before asking for help... anyway, thank you!

[MENTION=4471890]whalesplaho[/MENTION] did you get v13.2 working on your xperia?

Could you (or someone else) please check this out. Thanks in advance!
[Magisk] Anonaru:
Having this run auto at start ended up being the only method that got my M8 to pass safetynet (and open Pokemon Go). The module worked for only one reboot, then it went back to failing (weird..).

That's the HTC One M8 (Base model, Sprint) running JW 5.4 and its built-in ElementalX kernel. Once I got that sorted, I haven't had any issues, even after clearing cache and multiple reboots. Glad we have so many awesome users around here to save us dopes :laugh:
[Magisk] ZerosMadness:
How do we get terminal commands to auto run? Sorry if it's been answered
[Magisk] Anonaru:
universal init.d is the best way imo, though I think you can do it with kernel auditor as well. :silly:
[Magisk] ZerosMadness:
Thanks! I'll try both
[Magisk] Bobthahog:
Yes, I had originally done it that way using kernel aduitor and universal init.d but then I put the script into the service.d folder and it works also. So either way is workable.
[Magisk] Lazing_About:
Pleas add Magisk to forum menu

HI there mods / admin. [MENTION=2854207]snickler[/MENTION]

I'm a new member and was just using the search tools on the website. If I go FORUM > ROOT TOOLS >....................... there is no "MAGISK" available. Would be quite helpful to some if it could please be added to that menu.

Thank you.
[Magisk] pranayysharma29:
I installed the bellota font module and kind of don't like it.

If I delete it from the section under modules, will default font be restored?

Has anyone tried it?

TIA
[Magisk] Artim_96:
You can just use Magisk afaik. Just make a module and paste it to services.sh. no need to try to get init.d to run
[Magisk] Didgeridoohan:
Is there a su.db in data/user/0/com.topjohnwu.magisk/databases? Or is it there and the issue is that it can't be read?

Had another thought... What file system is /magisk mounted as? If it isn't ext4, try remounting it and change the file system.

Magisk's post-fs-data.d or service.d, or a Magisk module, or Tasker, or several other ways...
[Magisk] bluenote73:
Since I don't have root, I went to TWRP and used the file manager, and, I don't know what this means, but, /data/user only has a _file_ named "0" in it.

I do have a /data/data/com.topjohnwu.magisk/databases, and there is a repo.db, su.db, su.db-shm and su.db-wal in there.

Is this something I can maybe edit myself?

thanks
[Magisk] ZerosMadness:
None of them actually worked for me. Guess I did it wrong probably. I'll just wait for 13.3.
[Magisk] sToRm1nG:
I suggest that you document your findings in the github issue (issues with the path).

I don't think that there is an easy way to change it yourself but I'd have to go through the code to figure out how Magisk is specifying the path to the files needed.

Maybe someone else can shed some light here?

In the mean time: have you tried to completely uninstall Magisk and reflash it, to see if this solves the problems you're encountering? I assume you are on Stock Rom, right?
[Magisk] gozzaa:
Hey, where did you get that zip file? :)
[Magisk] bluenote73:
I'm on stock nougat 7.1.1 A2017U and yes, I've been clean flashing and/or reinstalling and every combination I can think of since before the beta and through most of the betas versions too.

Ill add this detail to the GitHub issue, thx
[Magisk] Didgeridoohan:
That's some progress.. From what I understand, /data/user/0 is supposed to be a symlink to /data/data. It's the main users directory for app data. Any other users on your device will have their own folder under /data/user, with their own ID, where all their apps data are stored (not a symlink).

What are the details for the file "0". In terminal, as su, type:

ls -l /data/user/0
stat /data/user/0

Now on to figure out why the 0 folder isn't a symlink... From a quick search it looks like the Axon 7 doesn't support multiuser by default. That's probably why. You could try to enable multiuser and see it it changes anything. Should be enough to set these values on your device (easiest done with a boot script or a Magisk module):

fw.max_users=10 [I](or whatever number of users you want to allow)[/I]
fw.show_multiuserui=1

It is also possible that you could delete the file "0" and create your own symlink, as a workaround. In terminal, as su:

rm /data/user/0
ln -s /data/data /data/user/0

The above SHOULD be safe, but please make sure you have a backup of your device... :laugh:

Add all the new info to the GitHub issue and hopefully [MENTION=4470081]topjohnwu[/MENTION] can take a look at it.
[Magisk] poulopoulosa:
Hello

I am having some really strange behaviour with SF. SafetyNet has been tripping so I installed the temporary safetyNet fix. SafetyNet was still failing so removed Magisk 13.2 though TWRP with the uninstall script. Despite the fact that I have no root or Magisk, SafetyNet fails.

Any clues or ideas of what it might trip SF?

is there any folder or remaining file in my system? ( I quite doubt it since I am systemless since magisk v3).

edit: I also removed the manager and still SF fails.
[Magisk] Bastion46:
Hi all, I'm having some strange issue with Magisk 13. Sorry if I can not explane it very well, but it's just difficult to explane it in my language.

v12 warked fine, but when I try to update (Both Manually and from manager, and with both 13.1 and 13.2) my device, Galaxy Note 2 N7100, boot but then it don't work fine.

Some apps keep crashing (as Play store and play service), other apps work fine, but the real problem is that the system UI keep crashing and restarting in loop, the icons disappear and reappear soon, and this with both standard launcher and Nova.

Also, i've noticed another strange thing. When i try to open the directory were i put the Manager apk with file manager, it crash.

Also, if the Manager is installed, when I open the app drawer and i scroll down, the launcher crash when i arrive to the letter M, before i can see the manager app.

Someone help?
[Magisk] 7root:
The maintainers of this thread must be annoyed by the safetynet issues occuring in v13.2. But it just does not work! Tried resetprop in terminal and as a init.d in Kernel Adiutor (correctly spelled there??). Also tried the universal Safety net fix. Also tried all of these methods on permissive mode. Still cannot get it to work. Please help?

EDIT: tried the fix via an adb shell and got it to work. Interestingly it does not work via init.d script. And yes, init.d is fully set up on my device.
[Magisk] Vitmor01:
Mio
[Magisk] Didgeridoohan:
SafetyNet will also trigger from an unlocked bootloader and permissive SELinux.

Logcat from the crashes might show something.

And if you haven't already, a complete clean install of Magisk might work. Run the uninstaller - flash a clean boot image/dirty flash your ROM, install Magisk v13.2.

Tuo?

Please note - English only on xda.
[Magisk] Hassanator:
Hey guys I've got Moto G5 Plus and it doesn't have init.d, its running 7.0 and I've tried the universal init.d app and it just crashes right away. I'm not super knowledgeable on all the other fixes or how to do them. Could anyone please help me sort it out?

Also I had android pay installed back when my safetynet worked and the app still opens and looks to be fine even with the safetynet failing but I've not tried to buy anything using it yet (also kinda afraid to try cuz I don't wanna look like an idiot if it doesn't work) what do you guys think would it work?
[Magisk] poulopoulosa:
SELinux is enforcing.

I completely forgot that SafetyNet would trigger because of the bootloader even w/out magisk

I tried multiple ways enabling/disabling core mode removing all modules (apart of the magisk fix)

Any other clues or suggestions, anyone?
[Magisk] jbltpcblt:
Hello,

Problem encountered on xiaomi mi note 2 miui v8.7.

Magisk Rel 13.2

Magisksu -> OK

Maigkshide - Does not work properly, does not hide root at aplications. Below the log:

--------- beginning of main

I( 446: 446) Magisk v13.2(1320) daemon started

I( 446: 448) ** post-fs mode running

--------- beginning of system

I( 446: 749) ** post-fs-data mode running

I( 446: 749) * Mounting /data/magisk.img

I( 446: 749) * Running post-fs-data.d scripts

I( 446: 749) * Loading modules

I( 446: 749) * Running module post-fs-data scripts

I( 446: 761) * Starting MagiskHide

I( 446: 761) hide_utils: Hiding sensitive props

I( 446: 761) hide_list: [com.google.android.gms.unstable]

I( 446: 761) hide_list: [mobi.inthepocket.bcmc.bancontact]

I( 446: 761) hide_list: [com.bpo.thaler.mobile.smartphone.prd]

I( 446: 761) hide_list: [com.kbc.mobile.android.phone.cbc]

I( 446: 761) hide_list: [com.cbc.mobile.android.oob]

I( 446: 761) hide_list: [com.netflix.mediaclient]

I( 446: 761) hide_list: [com.google.android.gsf]

I( 446: 761) hide_list: [com.android.vending]

I( 446: 927) ** late_start service mode running

I( 446: 927) * Running service.d scripts

I( 446: 927) * Running module service scripts

I( 446: 761) proc_monitor: init ns=mnt:[4026531840]

Small idea?
[Magisk] Didgeridoohan:
Wait... It will be fixed.
[Magisk] Bastion46:
I've just tried a clean install but I have the same result, only with 13.1/13.2 btw, v12 is still working fine, but i don't need it without safetynet pass.

Thanks for the reply :good:
[Magisk] monkeywithbanana:
I don't know if adoptable storage is yet fixed or not, atleast it's still listed on the known issues section, but i flashed 13.0 beta and now on 13.2 and everything is working perfectly, even though i have my sd card formatted as internal storage.
[Magisk] DodoGTA:
Try moving Magisk Manager to SD card
[Magisk] wserfer:
Can't use it with M5 kernel on 5.1. How I can install it manually?
[Magisk] DodoGTA:
Can you attach the recovery.log?
[Magisk] Didgeridoohan:
"Can't use it" doesn't say anything...

If you're talking about it not being able to install, do what [MENTION=6429309]DodoGTA[/MENTION] says. If you have other issues post a Magisk log (or logcat, depending on your issue). If you're having problem with MagiskHide not working you're going to have to update your kernel. That one's too old...
[Magisk] theandroidguy:
I'm facing these issues although magisk is installed, permissions also cannot be changed, plz help me
[Magisk] theandroidguy:
Had to reflash magisk, everything is working....btw what is dm-verity and forced encryption???
[Magisk] wserfer:
Installer claims that the installation is successful.

No one will update this kernel for me. Can you say what can be missing in the kernel for work?
[Magisk] DodoGTA:
dm-verity: https://source.android.com/security/verifiedboot/

Encryption: https://source.android.com/security/encryption/
[Magisk] Didgeridoohan:
MagiskHide uses mount namespace to hide root from apps and processes (SafetyNet). For that you need a Linux kernel version of at least 3.8 (your kernel is 3.4), or the mount namespace support needs to be backported. Edit: And please note that this is not the place to ask for help on how to do that... :p

And about the recovery log: That the script claims "successful" just means it finished running. To know if something went amiss we'll need to see the actual log.
[Magisk] whalesplaho:
Its working here brov.... Have yhu solved it!?

1. Flash uninstaller zip for magisk

2. Fastboot tha patched kernel

3. Fastboot working twrp 3.1.10

4. Flash magisk zip 13.2

5. Reboot

6. Connect device with ADB mode

7. Remove Magisk Manager pre-installed app "adb.exe uninstall com.topjohnwu.magisk"

8. Install Magisk Manager latest app "adb.exe install MagiskManager-v5.0.6.apk"

It should be okay... Its working fine here!!!
[Magisk] wserfer:
Thx, I understood. But the Manager does not show anything at all. I doubt that kernel version is the only one problem.
[Magisk] olivercervera:
Hi guys,

I have an issue with an app that seems to be circumventing MagiskHide, called Intesa Sanpaolo Mobile (com.latuabancaperandroid)

It is made by an Italian Bank and is their Mobile Banking app.

I have tested this scenario on several smartphones but to keep things simple I will be using a Nexus 5X as reference. This N5X is running a custom Rom (PureNexus). I know it is not the perfect example, I will try to test with a stock rom asap.

This app works fine even if root is not hidden, however there is a feature called "PayGO" that allows users to pay with NFC (basically an Android Pay replica). When I try to enable this functionality, it detects that root is present on the device, or that the latter has been modified in some way. This issue has been reported here already.

These are my observations, following this troubleshooting guide.

Obviously MagiskHide is working fine on this device. I can hide root for other apps without problems.

This app seems not to use SafetyNet. Currently SN is broken, but PayGO functionality never worked with Magisk

App has been added to MagiskHide

This app is not deliberately targeting Magisk Manager. I installed Magisk Manager (without Magisk) on a stock unmodified Galaxy A5 2016, I can enable the functionality successfully

I have checked "Sensitive Props" comparing them with a stock N5X

This app requests permission to Phone, I guess to get some details. I've hidden root to Phone as well, no luck. I've disabled this permission as it is not trivial, no difference too.

Unfortunately to replicate the issue you need to have an account with this bank, but the issue can be always replicated on several smartphones.

I'm guessing they have found something that Magisk is leaving behind, or targeting Magisk props.

My next steps are testing on a Nexus 5X running stock + Magisk, and using the temporary fix for SafetyNet that removes some Magisk props.

Anything else you could recommend? What should I look in ADB logs? I filtered for the app name and could not see anything relevant.

Thanks in advance.
[Magisk] DodoGTA:
Did you add that app to the Magisk Hide list?
[Magisk] jenslody:
There is an issue, where modules with new template-file can not be update through MagiskManager in some cases (they stay in status updated-at-next-boot), but through recovery.

I found the cause for this issue:

execv bails out with "access denied" when trying to create /data/magisk_merge.img.

That happens, because magisk is called with absolute path (/data/magisk/magisk), but Android does not allow apps to be run from below /data .

I created two pull-requests at github that works around these issues:

https://github.com/topjohnwu/magisk-module-template/pull/22

https://github.com/topjohnwu/Magisk/pull/293

It can be done in a different way, where the util_functions.sh-script does not need an update, but the module-template has to be updated in any case unfortunately.

Additional issue opened on github (https://github.com/topjohnwu/Magisk/issues/297), so it is more visible.
[Magisk] olivercervera:
Yes I did, sorry for not mentioning that, will edit the post. I also added Settings and Phone to Magisk Hide.
[Magisk] Didgeridoohan:
That recovery log throw a ton of warnings during the flash. I also see you're flashing over a previous Magisk installation. If you haven't already, try doing a clean flash (uninstall Magisk and reinstall).

The Linux kernel version might not be the issue for this specific problem, but the kernel/boot image most likely is. You can also try a different kernel...
[Magisk] ellenth:
Hi, I have managed to install magisk on my (new) S8 but now I get security messages . I believe from knox and keeps asking me to restart my phone. How can I disable these messages?

Thx in advance
[Magisk] tdhite:
Not quite sure why the suggestion permissive will trigger SafetyNet. Magisk hides the state. I run permissive, set in a module I made for my kernel, SafetyNet passes always, Magisk properly logs it is "hiding the state."

Just FYI.
[Magisk] Didgeridoohan:
If you'd actually read the conversation you're replying to you'd have seen that that user had completely uninstalled Magisk and still couldn't get SafetyNet to pass (it was the unlocked bootloader that did it). FYI... :p
[Magisk] tdhite:
Haa. Fair point. Once in a while I indeed miss a few posts . . . All in good faith, trust me.
[Magisk] Didgeridoohan:
In this thread (especially since the SafetyNet farce started again), it is quite easy to miss a post here and there... :laugh:
[Magisk] dsjd:
I know magisk safety net is not working right now but under normal circumstances if i install an app as a system app and then uninstall it will it still trip safety net?
[Magisk] barankas:
Hi,

Any workaround for this UOB apps?

Thinking of terminating my UOB Account.
[Magisk] dazeone:
SafetyNet working here and here is how I got it to work. Follow link in video to get the script. Follow instructions in video. Use magisk 13.2 with apk v 5.0.6

https://youtu.be/ylWFGZh4KkM
[Magisk] dsjd:
Thanks..if i install an app as a system app ..use it for sometime and then uninstall the app..will it trip safety net?
[Magisk] dazeone:
SafetyNet is also being triggered by unlocked bootloaders and some Custom ROMs. Removing it as system can still trigger it. I tried myself to go full unroot and still failed.