yashsingh1/xdaforums huggingface dataset:
[Magisk] atarek:
Thanks aloot for ur reply.

So i decided to return to v.12 until support.

for time being i wanna pass safety net as before so if any one could check magisk log and give me advise or troubleshooting guide it will be appreciated.
[Magisk] psychoela:
I( 502: 502) hide_daemon: Unmount Failed (/dev/magisk/dummy/system/lib/

anyone no this mine what? I get from magisk log, same thing wrong or nothing just log? btw I has never pass SN for now. using latest beta.Thanks:o
[Magisk] H4X0R46:
Yeah sure, any time bud! This should get sorted out soon, dev is hard at work!
[Magisk] dahawthorne:
Read the forum before you post.

Rant mode on.

Why are people so lazy that they can't be bothered to look at the previous few posts, or use the forum search, or even try Google, before posting questions?

Rant mode off.

Sorry, but I'm getting really short of patience with this. We all try to help, but are people expecting us to fly over to their houses to update their devices because they can't perform a simple search?
[Magisk] dbroer91884:
Yep this did it! Thanks!
[Magisk] DrAgNbOi:
No worries I had the same issue before but someone from here mentioned to do that and it worked.
[Magisk] Ph@nta:
Does anyone know how to turn su.d scripts into magisk-compatible ones? I'm not entirely sure how su.d works to know where to start converting things. Could I just move them to a different folder and Magisk would just automatically run them?
[Magisk] Skanin:
I got it to work! Forgot I still had busybox installed. As the main post says, all root have to be removed before flashing Magisk. Use the "unroot" oprion in superSU, and use the Xposed uninstaller. Also remove busybox. See if that works! If not, you can do a complete wipe of your device, to make sure all root are removed :)
[Magisk] topjohnwu:
Haven't been so active on XDA lately, but it doesn't mean the development has stopped :)

Some massive updates will be in the next release, both in the Magisk Manager and Magisk itself.

Thanks to fellow developer [MENTION=3400685]digitalhigh[/MENTION], the progress of the Module repo system is almost done, so expect Magisk to be more popular and easier for developers and users to work with!

On a side note, due to the fact that Chainfire never replies to me about fixing SuperSU, I assume that SuperSU is not maintained by him anymore, or maybe he is not interested in collaboration. I will now officially drop SuperSU support. Too bad that I've been using SuperSU since its early days and never changed the option, I think it's about time to drop it and embrace open source solutions.

The next Magisk will bundle with phh's superuser by default (you can still use SuperSU, however no support from my side)

phh's superuser is super versatile that I can tinker with it in many ways to create wonderful solutions. Also, I've fixed many things, both for Magisk and phh root (and all open source! ), and I can't wait to release the new update!
[Magisk] crime_of_heart:
Any idea on the above?

What could cause the bootimg partition not being recognized?
[Magisk] esrvR:
Can't wait for this update, thanks for all the hard work :o
[Magisk] rgawenda:
Then please, don't wait, release! :angel:
[Magisk] djjohnnyblaze:
Hi everyone,

I am experiencing an interesting issue.

I am working on a mod port for Magisk V6 and when I flash the .zip in TWRP and return to system, I can see the files have been placed into /magisk/MODNAME, but I no longer have root.

Setup:

Magisk V6

SuperSU Magisk version

Magisk systemless xposed

Keep in mind before flashing the mod Magisk/Root/Xposed are fine.

EDIT: after waiting, the system also locks up and screen goes black and will sometimes show connected to wifi text. Is Magisk failing to mount stuff to system? not sure what is happening here.

EDIT2: After waiting for a very long time, the system has come back to normal. The files from the MOD are in place, however, now both Magisk Manager and SuperSU both report no root. Did I lose root+xposed after Magisk Mount?

Thanks in advance!
[Magisk] CHAMAVELI:
It seems like it will work for a reboot or two per creation of a module. When post-fs runs it successfully runs the commands yet they don't get set (getprop). It's like there may be some sort of cache mechanism for loading values that Magisk can't overwrite. Or maybe something is happening before post-fs is loaded that stops the values.
[Magisk] Didgeridoohan:
Yes. I've noticed that every other reboot Xposed gets disabled. Deactivating Xposed, rebooting and reactivating it again brings it back. This process usually also activates my setprop ro.sf.lcd_density, just to deactivate it on the next reboot. Root (phh's Magisk 17) and the Busybox and BetterBatteryStats modules from the Module Collection thread work consistently across reboots wich leads me to suspect systemless Xposed as the culprit. I'll do some more experimenting later.
[Magisk] steveo17:
[MENTION=4470081]topjohnwu[/MENTION]

Chainfire has stated that he is only have here for the month of September. I'm sure he would like to collaborate with you, but the fact that you keep calling him out like this is only making matters worse for you I feel.

give the man some time.
[Magisk] abodyirq:
Hello excuseme for bad language.

I've completed all the steps and everything, but after the success busybox a xposed is disabled ??

why !!
[Magisk] :
Switch the disable switch off and then back on and reboot.
[Magisk] rgawenda:
I've heard he sold SuperSU to a company.

For me, the combination of Magisk and phh's superuser is way more useful.
[Magisk] abodyirq:
Thanks for the answer but what do you mean ؟؟

Please explain
[Magisk] Ph@nta:
I believe he means in the xposed installer, switch the framework off, reboot, go back and switch it on, and then reboot again.
[Magisk] benwalburn:
Has anyone tried this with Nougat's file based encryption? TWRP can't decrypt it currently, and the 6P build has an issue with making backups, so I'd like to avoid flashing Magisk until I know it won't break anything. I'd assume that flashing it through sideload will work fine, just leaving the /data files unencrypted.
[Magisk] Captain_Throwback:
Are you sure TWRP can't decrypt it? I'm pretty sure there are updated builds of TWRP that support Nougat decryption for most of the Nexus devices.

Either way, it *shouldn't* affect Magisk.
[Magisk] ~N.A.W.Y~:
So if i delete these strings from the updater script of the rom, would it flag it?

"assert(getprop("ro.product.device") == "ailsa_ii" || getprop("ro.build.product") == "ailsa_ii" || getprop("ro.product.device") == "axon7" || getprop("ro.build.product") == "axon7" || abort("E3004: This package is for device: ailsa_ii,axon7; this device is " + getprop("ro.product.device") + "."););

assert(axon7.verify_trustzone("TZ.BF.4.0.1-00315") == "1");

ui_print("Target: ZTE/P996A01_N/ailsa_ii:7.0/NRD90M/20170128.052618:user/release-keys");"

(The point of deleting these strings are to make the rom able to dualboot as secondary rom)

Rocketed from my Mi5
[Magisk] Jfelips:
I figured out by myself one second after writing the question. Actually I wasn't finding the beta thread and then I found it. All I needed was a link.

I guess my internet wasn't loading all the comments of this thread so I couldn't read all.

If u already explained why don't you just copy and paste??
[Magisk] dahawthorne:
I hear what you say, but you could have used that second to do a proper search. I try to be helpful and I have posted several update suggestions already. All I'm asking is that people ask questions as a last resort, not as a first.
[Magisk] Jfelips:
Anyway, I get you. I know people are annoying (probably​ including me).thx for the help.
[Magisk] Gerard15799:
How do I install v13...I'm running with magisk v12...my rom is RR 5.8.3..the rom was built in with magisk...do I need to uninstall the manager first then flash the uninstaller..then flash v13?
[Magisk] H4X0R46:
Yes
[Magisk] Njaiker:
cannot pass safetynet [Redmi Note3, running developer MIUI]

I have tried almost everything I could find to solve this problem including tips in the troubleshooting thread but I still cannot make the device pass the safetynet. Another thing is, when Magisk is not flashed, Basic integrity check passes, but after installation of Magisk even that fails.

anyone who succeeded in passing the test with a similar setup to mine.
[Magisk] Gerard15799:
I flash it already but the app keeps stopping?? Is there anything I can do
[Magisk] motopig:
I have v12 installed on my new-to-me Nexus 6. I now have root and my banking's app no longer complains about mods whereas it would on my previous Zenfone 2 rooted with more conventional methods. (I hid magisk from it) Nice! Now see if I can get Xposed on it and add that youtube adblock mod.

Now how can I add the tcpdump binary into /system/xbin under Magisk and have it preserved across reboots? I see Magisk mounted a tmpfs there so I'm not sure Magisk would save it if it's not put there by a module. I could investigate whipping up a simple module but I'd like to take a more direct approach if possible.
[Magisk] Gerard15799:
NVM it's already ok but safety net...I got this results...
[Magisk] Gerard15799:
This is the log
[Magisk] CryonicCore:
Use core only mode in magisk. It's in the settings. Reboot then check SN. You won't be able to use modules from magisk though but this is a temp fix till v13 is fully working. I don't trust betas lol
[Magisk] Gerard15799:
Is there a way to pass safety net in v12??
[Magisk] CryonicCore:
Core only mode. In magisk settings
[Magisk] Gerard15799:
Ok thanks will try and see

---------- Post added at 07:45 AM ---------- Previous post was at 07:42 AM ----------

Should I enable magisk hide also?
[Magisk] CryonicCore:
Yup
[Magisk] Gerard15799:
Ok thanks
[Magisk] CryonicCore:
Example
[Magisk] Gerard15799:
Hmm...I did what u did...but it failed...
[Magisk] CryonicCore:
Did you hide SystemUI as well?
[Magisk] Gerard15799:
Yea
[Magisk] CryonicCore:
Hmm not sure then sorry. Maybe someone else knows more then me
[Magisk] Gerard15799:
Hmm it's ok.. thanks for your help.... I'm using Asus Zenfone 2 laser running with Resurrection Remix ROM 5.8.3...
[Magisk] kramer04:
Go to the beta thread https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589

And try with the magisk v13 b3da28e
[Magisk] Didgeridoohan:
Your log looks fine. Have you enabled core only mode? If not, do so and reboot. Might fix it.

That means Magisk Hide tried unmounting that folder and failed. There's been a few similar reports in the beta thread. Some users reporting the issue have found it's usually some specific module causing the issue.

Probably not. I've seen people having a lot of trouble with Axon 7 devices though...

Xiaomi devices can't pass SafetyNet on developer MIUI. There's a SafetyNet fix module that could help. It's recently been updated though and made universal so your device will seem to be a MI 6 to the rest of the world. If you don't care about that, give it a try.

The direct approach with Magisk would be a module... Here's some recommended reading: https://xdaforums.com/apps/magisk/magisk-details-dummies-to-developers-t3473486

Looking at your log and screenshot from the v13 beta you pass basic integrity but not CTS profile matching. Your setup probably can't pass SafetyNet fully... It seems like it's possible to spoof your device fingerprint to make it seem like a different device. I posted a link above that does that... You could give it a go.
[Magisk] Gerard15799:
Thanks for your help
[Magisk] muralidharpattar7:
How to install busy box?
[Magisk] ~N.A.W.Y~:
I should've mentioned it, my device is actually Xiaomi Mi5. I just copy-pasted these strings from a thread where it was suggested to remove them in order to dualboot.

Rocketed from my Mi5
[Magisk] Didgeridoohan:
Ok. Xiaomi devices have their own issues with SafetyNet... But that's generally on beta/dev MIUI.

Please report back when you're done. It'd be interesting to know how it goes.
[Magisk] wmg.architect:
Hello.. I am on carbon rom / Z3C, with supersu root. Tried to flash magisk after removing supersu root. But it gives me error on twrp that magisk need supersu to flash correctly.

After flashing supersu again, magisk flashing has done. But in the system it seems unuseful. Supersu still the root and if i remove it. Magisk stops.

And safetynet check doesn't work
[Magisk] Didgeridoohan:
If you want to pass SafetyNet with Magisk you have to use MagiskSU.

After uninstalling SuperSU you'll also have to flash a boot image without the SuperSU patches. Your ROM's stock boot image, unless the ROM comes pre-patched, then it'll be trickier to find a compatible boot image.

Also, it looks like you're using Manager 5.x with Magisk v12. They're not compatible. Magisk v12 goes with Manager 4.3.3 and Magisk v13 (still in beta) goes with Manager 5.x.

Because of recent updates to SafetyNet you'll have to enable core only mode in the Manager settings if you want to pass SafetyNet (unless you want to jump on the beta train).
[Magisk] Skulltec:
I don't seem to get pass the safety net.

Today i wiped all my data and started fresh. Flashing Pure Nexus, Elemental X and then magisk.

i have enabled magisk hide and disabled busybox in the magisk manager. safetynet cts profile mismatch error
[Magisk] toodlenoodle:
I just installed 12.0 on my Mi Mix running Resurrection Remix. Now there's a new 13.0 beta, what is the best way to go about updating? Can I install the new manager over the old apk and use twrp to flash over the old version?

Do I have to remove any modules?
[Magisk] ~N.A.W.Y~:
So i've installed lineage as secondary rom (with those strings deleted) it's giving safetynet fail now. I guess i gotta stick to one rom at once if i wanna keep safetynet green.
[Magisk] nguyen4514:
I have an odd issue that I noticed about a week ago.

For the past several months, I've been able to use viper4android without any problems passing safetynet. I've also been able to use Android pay throughout this time.

About a week ago, I noticed that I've been failing safetynet. I've tried uninstalling viper4android, but I still fail safetynet. I've tried unrooting and rooting again with magisk without additional modules, but still fail safetynet.

I can pass safetynet if I use core mode. This is fine, but I just find it odd that even without modules installed, I still fail safetynet without core mode enabled.

Does anyone have an idea what happened with safetynet within the last week?

Thanks
[Magisk] Garock:
well this is the main topics for any magisk threads for the past few days/a week

try the latest beta https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589
[Magisk] Kapiljhajhria:
Yes something did happen recently. Check xda portal to know more.

Safety net got updated. U might have to switch to magisk beta and magisk beta isn't working well with all the modules right now.

Even all the phones are not yet supported.

U will have to play around with settings in magisk manager app if u flash magisk beta. Make sure to search the thread as everyone there asks same question after every few posts.

Don't visit that thread for general magisk issues. It for beta testers. People who can troubleshoot some stuff on their own. That thread is now filled with people who are asking to be spoon fed.

Read the OP of that thread and then proceed accordingly.
[Magisk] nikexv2:
I have a weird issue on my one plus 3

I'm running Dirty unicorn weeklies, and passing safetynet without any problem.

My banking apps work, as well as android pay and any other app like netflix that need safetynet to pass.

But i'm using an mobile payment app named seqr, and it tells me that my phone is rooted no matter what i do. I uninstalled magisk manager to see if it was looking for the package name, but it still tells me i'm rooted.

I use this app since months now with magisk, but the last week it stoped and started to tell me that i'm rooted (the app has been updated since the last week)

What could be the issue ?
[Magisk] Artim_96:
The problem is most likely that it's a payment app. Like banking apps it probably used detection methods where even Chainfire already said that he has no idea how they can detect anything, even with nougats extremely strict rules on what an app can see from other apps. Thus, it's simply impossible to hide root from them as long as it's unknown how they work or at least what they detect.
[Magisk] nikexv2:
Oh i get it, i was wondering because it is the only app doing this, even android pay and my bankong apps dont detect it, only this one :p

But i guess i'll have to wait :)
[Magisk] vectorer:
Does SE mode need to be enforcing?
[Magisk] Didgeridoohan:
SELinux needs to be enforcing to pass SafetyNet, but Magisk Hide can spoof that with the pseudo-enforcing mode. In other words, you should be able to keep your system permissive and still pass SafetyNet.
[Magisk] Gerard15799:
Holy crap it passed!!!!!! I use that module and it worked....Jesus Christ I've been wanting it to pass yesterday!!!
[Magisk] CryonicCore:
Where do you get that? I don't see it in downloads in magisk.
[Magisk] Artim_96:
https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431/page39

I'll try it too new
[Magisk] CryonicCore:
Yea I found it and it works great.
[Magisk] Artim_96:
I'll see tomorrow... It just destroyed my whole Magisk installation. Maybe because I run the beta. It deleted all modules and every setting in Magisk hide...
[Magisk] CryonicCore:
Works on v12 but I didn't try v13 beta. Install v12 and then use the universal safetynet fix.
[Magisk] yochananmarqos:
No, it didn't. If you'll notice, the magisk.img isn't mounted. You'll see /magisk is empty. Reboot and it may return to normal. I believe it's an issue with the latest Magisk beta.
[Magisk] One-ti-teuf:
Work for me.

Htc M9. Venom 6.0.1 ?

Envoyé de mon HTC One M9 en utilisant Tapatalk
[Magisk] yochananmarqos:
Yes, it works--but it also will change your build fingerprint to Xiaomi/sagit/sagit:7.1.1/NMF26X/V8.2.17.0.NCACNEC:user/release-keys since it was originally designed for Xiaomi devices. I commented out the two correspoding resetprop lines so it will work on any device without changing your build fingerprint. You'll need to have a build fingerprint that passes SafetyNet either way, so you may need to change it if my mod does not allow you to pass. It's attached to this post.
[Magisk] Artim_96:
It is an issue with the latest beta, it shows an empty modules list every time you try to install any module. And then it likes to cause bootloops... In the OEM splashscreen

EDIT: ok... Now I actually pass both tests on a LOS derivate. I used to of only basic integrity:eek:
[Magisk] ypnos42:
I installed Magisk on my Xperia X Compact. First boot worked like a charm. Then I installed two modules and rebooted. Now I am stuck at kernel bootup (SONY logo displaying) until the battery drains out.

How can I find out what is going wrong during bootup? Is Magisk writing any log files?
[Magisk] Artim_96:
At least TWRP is creating log files of flashing. I had the same problem with v13 beta, it seems that it had problems with mounting the Magisk image
[Magisk] Timberlake.C:
after flash??install magisk apk??
[Magisk] Artim_96:
Before, after, doesn't matter. Just install it
[Magisk] jugoslavpetrovic:
Hey guys.

If I want to put script to run with boot time, where should I put it?
[Magisk] Artim_96:
If it's not important to run as soon as possible, just put it into a module in service.sh. otherwise in post-fs-data.sh
[Magisk] igorinolw:
Redmi note 4 snapdragon,Having trouble with ALL miui ROMs.(global Dev and xiaomi eu)

ALL ROMs fails on ssafetynet, but i still Can play pokémon before installing magisk, after i install, cant play anymore.(core only enabled)

Cannot install magisk beta, It gives me error.

Works Fine tho in RR, with magisk beta. ALL Green.

Forgot to mention, already used the universal safetynet fix miui ROM, didn't worked either
[Magisk] ypnos42:
What I did is flash v12 and install Manager in TWRP. This works w/o issues. I installed modules from manager, and the phone didn't boot anymore. Then uninstalled and re-installed Magisk from TWRP again, everything is fine.

I see in Manager some debug output can be turned on, where would I find it after the failure?
[Magisk] Didgeridoohan:
If you just want to run a script, place it in /magisk/.core/post-fd-data.d or /magisk/.core/service.d. If you're making a module, use the files [MENTION=5125527]Artim_96[/MENTION] is talking about.
[Magisk] Artim_96:
It only makes a bigger log, but I don't know if it actually starts making a log in that early stage. If it gets created it's under /cache
[Magisk] Umbardacil:
This mode solved my all problem so far.! God bless you good man ;) [emoji72]
[Magisk] kessaras:
hi guys, i'm trying to push my scripts inside service.d but from twrp.

i tried many ways to mount magisk and do my trick from inside updater_script but none worked.

Am i really forced to create a whole module for just copying 1 simple script to execute on boot ? Because i understand nothing about that.

Yes i did google, i did find the template , i did try to follow those, hard for me, instructions but i still don't understand.

The old fashion way was to just push a script in init.d and it was so nice and simple. Why in the year 2017 things get more complicated ? Do i have to study for hours just to copy/paste a script ???

(And no i don't want to copy/paste it from inside rom, i wanna do this from twrp)

The other way i thought was to make my own twrp that will mount magisk, but .... the question is if i can do it with an easier way, i don't want to spend hours for that, lmao!

Any ideas, any help ?
[Magisk] Captain_Throwback:
https://xdaforums.com/apps/magisk/collection-magisk-modules-v2-t3575758

Look for "Mount Magisk"
[Magisk] kingmateusz:
Hi

I've flashed rom Resurrection Remix to my sgs3 and i want to log in to snapchat, i have clicked on hide magisk in settings, then selected snapchat, tap to check safety net and it's failed? What to do?
[Magisk] noldar:
With v13 flashed, snapshat is OK for me. I had to reboot after first boot to pass SN.
[Magisk] jugoslavpetrovic:
The moment I put the file there I got boot loop. The script is very simple to bring headphones volume to +1db. It was working fine with SuperSu in su.d
[Magisk] manudhomra:
I'm facing this issue. Any solution??
[Magisk] Didgeridoohan:
I have several boot scripts running in both those folders with no issues... Could you upload the script?
[Magisk] Pkt_Lnt:
Snapchat detects root directly and can NOT be hidden. Unroot completely, log into Snapchat, then re-root is the only solution.
[Magisk] MasterPoiuy:
Agreed but pre rooted custom roms can't be unrooted right?
[Magisk] Karls0:
Usually they can by using uninstall option and optionally manual restoring unroored boot.img
[Magisk] Pkt_Lnt:
I think the UNSU zip from osm0sis can remove root from pre-rooted ROMs, try it.

https://xdaforums.com/showthread.php?t=2239421

edit - and as [MENTION=4586683]Karls0[/MENTION] point out, you probably need a unmodified boot image.
[Magisk] jugoslavpetrovic:
Sure

Here is the content of the script

#!/system/bin/sh

echo "1" > /sys/class/misc/soundcontrol/volume_boost
[Magisk] Didgeridoohan:
I just gave that a shot on my Nexus 6, Magisk v13.0(96f8efc) beta, with no issues... Check for typos.

You could also very easily make a Magisk module to simply replace the volume_boost file with one that has the desired value. If you'd want to keep your system partition untouched this'd be the way to go...
[Magisk] kingmateusz:
I've tried almost everything and only this option worked, flash backup of old rom, unroot, log to snapchat, root, backup in TB, flash backup of new rom, restore snapchat in TB. And that took me 5 hours xD
[Magisk] igorinolw:
Any Help here?
[Magisk] Didgeridoohan:
Did you read the OP of the Universal SafetyNet fix? It's got some good instructions...
[Magisk] CryonicCore:
There is a module you can download called Universal Safetynet Fix. Just google it and you will find it on the top of page first entry, linking to XDA thread. Download then install through TWRP. You should be green on all and device certified in play store.
[Magisk] kingmateusz:
Installed it and still failed.