yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
[MENTION=5911874]YoGieZ[/MENTION] That's a very general question without a general answer. Better to take it to the support thread... Or your device's/ROM's forums.

[MENTION=5981435]android_smater[/MENTION] Nothing new there, except for the parts that are wrong... There's no need to remove or disable Busybox to use MagiskSU or Magisk Hide. If this is true on your device then something is wrong and it's better if you collect some data (logcat, etc) about it, and then either open a new issue on GitHub or add the collected information to a relevant, already existing, issue.
[Magisk] android_smater:
i don't know what happen but that disbale busybox work in both in resurrectionremix android N as well as Stock miui rom amdroid 6.0 in Xiaomi Redmi Note 3 kenzo for me
[Magisk] Didgeridoohan:
Well... That's not how it's supposed to work... I and many others have a fully functioning Magisk setup with Busybox installed/enabled.

If you're having these issues, please help the community by collecting data and reporting it through the proper channels (like I said in my last post). I promise, if something you did makes Magisk better; it's gonna give a really nice, warm and fuzzy feeling inside.
[Magisk] android_smater:
yap i will help however even i disbale busybox and no other busybox is installed in my current rom but many app working and detecting busybox like kernal auditer but saftynet pass :D

and app like irctc connect and pokimon go which not work with root also working like charm ;)

i you want log i will upload it
[Magisk] Nomelas:
So.. you cant have busybox with magiskhide?
[Magisk] Didgeridoohan:
Yes you can.
[Magisk] Nomelas:
It works fine for my Gf running stock android on her nexus 5x, but I keep losing root on my phone running LineageOS with both enabled.
[Magisk] Didgeridoohan:
Then your setup has an issue that needs solving. You should collect some data (logcats, etc) and open an issue on GitHub or add your collected data to an already existing issue (I believe there might be one or two open already about the loosing root issue).
[Magisk] Syndrome666:
You absolutely can, I'm running it all the time both BusyBox and BusyBox on Rails, safetynet passes as long as Magisk manager and MagiskSU are both updated to suit the latest security patch, for example, on February's security patch MagiskSU 11.1 with Magisk Manager 4.2.6 allowed safetynet to pass with SUhide and BusyBox toggles enabled. On March security update, these Magisk Manager and MagiskSU versions no longer worked. Updating MagiskSU to 11.5 or 11.6 and Magisk Manager to 4.2.7, allowed safetynet to pass again.
[Magisk] Didgeridoohan:
Uhm... The Magisk updates are not connected to the security patches. Magisk v11.1 and Magisk Manager 4.2.6 works just fine with March security update...
[Magisk] Nomelas:
Is there anyone who is running LingeageOS with Magisk able to keep root with hide+busybox enabled?
[Magisk] Didgeridoohan:
Ok... Wrong thread. Support questions go here.
[Magisk] Syndrome666:
I didn't think they were, but I'm currently using SIX ROM, and it was recently updated to the March security update. I reflashed MagiskSU​ 11.1 zip and Magisk manager 4.2.6 was the latest update at the time. Safetynet failed after updating from Feb to Mar security update. As soon as Magisk updates became available, I flashed MagiskSU 11.5 and updated Magisk manager to 4.2.7, safetynet passed without issues. Passes with SUhide and BusyBox toggles in both enabled or disabled positions. I'm using this setup on Shamu, currently on the latest SIX ROM update v6.5 OMS. I've dirty flashed the ROM from v6.4 OMS and reflashed the latest Magisk updates, safetynet passed again without issues. The dev of SIX ROM, said it's likely Google's latest security patch breaking Magisk. Somehow the latest Magisk updates fixed the safetynet for me, so I assumed something was patched on Magisk side of things for safetynet to pass. In any case it's working great with my setup, so just throwing some info out there from my personal experience using this superuser. I'm not blaming any party for this by any means, just reporting what works and what may not. I'm sure experience with other ROMs may vary. In either case the updates won't hurt most likely.
[Magisk] Didgeridoohan:
Coincidence... I can tell you for sure it was not Google's March security patch.
[Magisk] Chichi.Lopez:
Hi, I'm new to Magisk but already read the thread. My ROM ist latest "Official LineageOS 14.1 for GT-I9305". So far I couldn't pass the SafetyNet check, it shows me "CTS profile mismatch".

Last night I've installed the latest ROM version. After booting I'd a look at the Magisk Manager and it showed me "Magisk not installed" and "device not rooted". I curiously pressed the safetyNet check and it became green. Afterwards I tried to get Magisk 11.6 by using the Mangager, but it didn't work, so I flashed the 11.6-zip by using TWRP 3.1.0-0. After reboot the Mangager showed me "Magisk 11.6 installed" and "device rooted", but I couldn't pass SafetyNet. It again showed me "CTS profile mismatch". So far I tried almost everthing mentioned above, but Magisk did not hide root. SELinux status: Moderat. I would very pleased if you give me a hind whatelse I could try. Thanks in advance!!!
[Magisk] Didgeridoohan:
When updating your ROM it overwrites the boot image and uninstalls Magisk. You'll have to reflash Magisk every time you upgrade.

From what I've seen LOS doesn't always play nice with Magisk Hide. CM was notorious for breaking things, so I'm not surprised if Lineage continues on that... lineage. :D

But, this is not the support thread. Go there instead for help.
[Magisk] coronafire:
My xiaomi miui based rom had working Magisk hide on v9 + phh but not on v11.x

I found a simple fix for this which has just been merged: https://github.com/topjohnwu/Magisk/pull/149

Hopefully it'll help for some other people in a similar situation!
[Magisk] Didgeridoohan:
Updated for Magisk v12.
[Magisk] torekiki:
Hi,

after v12 udate i can't enable magiskhide.

enable scrip won't work

Miui Rom

update

it works only if I run first disable script from shell
[Magisk] justjr:
On my LG (signature) the SefetyNet check keeps running and never gives me a result. Anyone faced it? What should I do? On moto G works fine.
[Magisk] Bradl79:
anyway to pass safetynet with permissive?
[Magisk] Didgeridoohan:
Yes, by activating Magisk Hide. You probably should read through the first few posts of this thread before posting (or at least post #4).
[Magisk] Bradl79:
right i have enabled that, and everytime i go to permissive and even reboot it still fails unless i change it to enforcing, is there anything i have to enable with Magisk Hide?
[Magisk] Didgeridoohan:
Wait a minute... You're the guy from the support thread... Go there instead (I've answered you there as well), this thread isn't for Magisk support.
[Magisk] tag68:
Seems right. The last days I always passed SafetyNet with Magisk 12.0 on Moto Z Play MM 6.0.1, now it fails CTS profile mismatch. Fortunately I'm currently not using anything that needs it :)
[Magisk] Didgeridoohan:
Why are you quoting the suhide thread here?

And if SafetyNet has been updated recently we'll soon hear about it (still passing on my devices). Meanwhile, I think it's more likely that Magisk Hide didn't properly start on a reboot...
[Magisk] tag68:
Because the posting I wanted to refer to was there, but I'm using Magisk.

Sorry, you were right. Toggled Hide and it worked again, thank you!
[Magisk] supertoast92:
Has anyone here been successful in getting Microsoft Intune Company Portal happy with their phone? I'm about to throw in the towel but thought I'd give one last attempt to see if anyone knows how to fix it.

It's detecting root somehow, even if I do a full unroot and go about cleaning up files and apps, uninstall BusyBox, disable Developer Options... Might be the bootloader being unlocked but I thought if I could pass Safety Net I might be good. ¯\_(ツ)_/¯

Ultimately I'd like to keep Magisk and hide it from the app! Got it working for other buggers like Mario Run, Pokemon, etc. But no joy with our Outlook email migration here.

Edit: Got it. My ROM's thread had the answer all along!
[Magisk] Didgeridoohan:
Mind sharing the solution? In case someone else comes looking...
[Magisk] supertoast92:
In build.prop

Change​ the line containing

test-keys

to

release-keys

Staying unrooted for now, so unsure if it would still work. I imagine it would if this is all it took for me.
[Magisk] Didgeridoohan:
Thank you. That was what I was going to suggest until I saw your edit that you'd already fixed it. :p
[Magisk] Madreverse:
Hey everyone :)

I'm a still a newbie in rooting - only started learning about it 3 days ago - so excuse me if I sound basic or ignorant.

I've managed to successfully root my Huawei P8 (Marshmallow), install and update de SuperSU and it's binary when it asked me to (SuperSU-v2.79-201612051815) but I'm facing an issue in installing Magisk. I've been reading a lot in XDA and other places but I can't seem to resolve anything.

I get the error 1 when installing the v12 in the recovery program TWRP:

Updater process ended with ERROR: 1

Error installing zip file '/sdcard/Download/Magisk-v12.0.zip'

I know that Didgeridoohan in the beggining of this thread wrote a paragraph about it "Installation script fails with "Error 1" and asks me to flash SuperSU or detects SuperSU patched boot image and fails" but according to what I'm reading in the error description it's a problem in installing the zip file?

I thought about opening the zip installer in the computer and maybe pass directly the file into the phone, but the zip folder has many files in there that I have no ideia what they are for and I was afraid of doing smtg stupid.

Any help would be amazing. Thank you.
[Magisk] Didgeridoohan:
Post your recovery log from the installation to the support thread. Error 1 can mean many things and to be sure you'll need to check the logs.
[Magisk] supertoast92:
Alright, so to follow up, root still breaks Intune/Outlook. Seems to get around Magisk hide. I can live without root though - mostly wanted custom ROM features :)

Everything works again once unrooted.
[Magisk] zoltar1308:
I have only one problem after magisksu root. My adaway not apply host for ad block.
[Magisk] Didgeridoohan:
The Magisk support thread is here. And there's a really good Magisk module for ad-blocking that you can download through the Manager. It's thread is here (in case you need help with it).
[Magisk] wrongway213:
So I have been all over the Magisk forums and even flashed v13 Snapshot to see if I could figure it out, but I still face one sole issue with Magisk: I am unable to pass Safetynet with Magisk Busybox enabled. I saw OP here is the one who was talking with me in another Magisk thread, and this thread seems more appropriate for my issue, anyway. I have watched the logs, and it is clear that Magisk Hide tries to initiate with Busybox enabled, and that is where the logs stop - "Starting MagiskHide". I am able to even go in and manually toggle MagiskHide off and back on and it WILL pass Safetynet. However, if I test Safetynet before this toggle it will faill, and it will then fail even after the toggle. If I leave Busybox disabled, the log shows MagiskHide starting normally without interruption, and I am able to pass Safetynet with no user intervention. Three logs attached - first being with BusyBox enabled, second with Busybox enabled after restarting MagiskHide, third is with Busybox disabled. If anyone has any clue what the issue might be, I'd be glad to hear - thus far everyone else I've attempted with Magisk, other than unmounting certain directories, has worked flawlessly.

Edit: logs taken here using Magisk v13 Snapshot - issue is identical in logs in v12
[Magisk] Didgeridoohan:
I try to keep actual Magisk support questions away from this thread and direct them towards the support thread instead.

But, having said that..

It does seem like on your device/setup Magisk busybox stops Hide from starting properly. I've seen that myself several times with some modules (especially after installing modules that mount files to /system), but it usually always works again after a couple of reboots. Never really had any issues like that with busybox though. Have you tried rebooting a couple of times after enabling busybox? Thought: You don't happen to have busybox included in your ROM (that caused me some issues on an earlier release of Magisk)?

I just wrote a post in the support thread about the v13 snapshots, that I'm not sure sure they contain the latest development due to it being moved to a separate branch for the unified daemon. The development being done though looks really interesting.

I'd actually consider opening a GitHub issue for this if I were you (with all possible details, logs and a copy of your boot image), since it sounds like you have a completely reproducible problem. I don't think I've seen one like it reported, but I haven't kept a very close eye on that lately.
[Magisk] wrongway213:
Thanks for the thorough answer. Sorry this was not the right thread for this - I picked it because it seems a particular issue with MagiskHide, and also because you were the one who had spoken with me about this issue before. I'll move issues to the support thread going further - or maybe to an issue on GitHub as suggested, as I do have a repliicable issue with logs. My ROM (or something in my setup) does include a busybox in system/xbin, but this is something that is quite common, as far as I know. I do feel we'd see an influx of this issue if that alone caused SafetyNet failure. I've rebooted more than several times, obviously - I've actually updated my ROM and such at least twice since this issue started. I'll likely take this to GitHub or maybe send these logs over to the support thread first and see if there's any luck. Thanks again for taking the time to reply!
[Magisk] Didgeridoohan:
No worries, mate. I'm always happy to help. There was just a new beta snapshot built from the unify_daemon branch. Don't know if it's actually usable, but you could give that a go and see if it fixes things. Named Magisk-UD-v13*.
[Magisk] Madreverse:
I've been trying to get said logs, but I can't seem to do it. Where can I find the installation log?

Thanks by the way.
[Magisk] Didgeridoohan:
Google: TWRP recovery log.
[Magisk] :
Problems with Mate 9

Hello there

I have some problems with Magisk on the Huawei Mate 9. It comes always the error: "Can't find Boot"

(I was using FlashFire, TWRP crashes instandly)

Can sombody Help me?

Thanks

Merlin Jehli
[Magisk] Didgeridoohan:
Wrong thread. The support thread is here: https://xdaforums.com/apps/magisk/mod-magisk-v1-universal-systemless-t3432382

Sounds like a serious incompatibility issue though. There's already a GitHub issue open for the Mate 9 (https://github.com/topjohnwu/Magisk/issues/170) so I'm guessing you're not alone.

If you can manage to capture some kind of log of your issues, post those with as much detail as possible in the support thread (not here). Also, asking in your device's forum might also be a good idea.
[Magisk] :
Sorry and Thanks :D
[Magisk] KRiST0F:
what was your solution.

I'm struggeling with it aswell and am planning to give it up.
[Magisk] Didgeridoohan:
Did you keep reading the thread? The answer was given two posts later...
[Magisk] KRiST0F:
Yes but it wasn't that clear to me

so on a custom rom for example Testla / Tipsy from Ground zero Roms that has Magisk build in

i simply uninstall magisk, change test-keys to release-keys?

or...?
[Magisk] Didgeridoohan:
That's what that user did and it seem to have worked.
[Magisk] Chaplan:
Passing Safety Net is a big concern for most (Magisk) users.

I was one of the users that found it hard to pass.

Magisk logs did not show anything strange.

Long story short. I will describe what worked for me:

Developer Options/Debugging/Logger Buffer Sizes

DON'T sellect OFF value.

Choose 64k or any positive value and you are good to go.

Steps to reproduce.

Change Logger Buffer Sizes to 64k, open Magisk settings, turn Magisk Hide OFF and ON. Go to Magisk status, start Safety Net test, Green light (if all other requesits apply).

Change Logger Buffer Sizes to OFF, open Magisk settings, turn Magisk Hide OFF and ON. Go to Magisk status, start Safety Net test, Red light. This breaks safety net no matter what.

Me and two close friends tested this on different devices with different ROMs.

USB Debugging ON or OFF never made a difference in my case.

I don't claim it will make Safety Net pass on any particular setup as this depends on other factors.

But as it seems at the moment with Logger Buffer Sizes OFF "none shall pass..."

I might be wrong though so testing should be open to more setups to fully validate this info.

Not all devices have the mentioned OFF option, not all the users will actually turn it OFF so it is what it is.

I searched for this after I came to this conclusion and no info came up that's why I'm sharing it here.

Hope it helps the next user.
[Magisk] Didgeridoohan:
Well... Yes. Of course even...

Magisk Hide monitors logcat events to know when a process starts and to unmount the necessary folders. If you turn off the log buffer, there won't be any logging to monitor and Hide won't see when a process starts. You can see it in the Magisk log. No more unmounting will be done after you've turned it off.

The real question here is why the average user would turn off the logging buffer?
[Magisk] Chaplan:
Troubleshooting it was a hit or miss in my case because all the Tips i read (ADB, Systemless hosts, BusyBox...) never made the cut.

I don't understand why you think the average user wouldn't turn off the Logger Buffer Sizes! Given the option every choice is a valid one.

All makes sense now. I did not find info on the Logcat monitoring being a requirement when i was troubleshooting this on my own.

But it is in the OP so all is good.

I hope the average user reads the OP (I actually did only after publishing my post and reading your reply because i was reading the Magisk General Support threads prior to it. I only found this one when i decided to post it. A bit sorry for that. I'm all in favour off reading the OP in every single scenario).

And i hope the average user makes the connection if he has Logger Buffer Sizes set to OFF, otherwise it wont pass Safety Net.
[Magisk] Didgeridoohan:
No worries. It's a real interesting find actually... I'm gonna add it as a tip (although an obscure one) when I have the time.

What I'm honestly curious about is what benefits the average user would have from setting logging buffer to off.
[Magisk] sumitgp:
Good morning sir

I m using leeco le 1s device,and i m running RR N 5.8.3 Kernal name f2fs use in samsung or may be any other device My problem is that i m not able to pass safety net

I tried hide magisk but it not work I don't want to play any game my only concern to run banking apps

Which close and showing waring ur device is rooted this app not work with rooted device

So please suggest me what should i do to pass safety net

Link for your help

[ROM][7.1.2.][STABLE][OFFICIAL]Resurrection Remix 5.8.3 Updated 17.04.2017

https://xdaforums.com/leeco-le-1s/development/resurrection-remix-5-8-2-android-7-1-1-t3575823
[Magisk] Didgeridoohan:
Good morning.

Read post #4 in this thread, try everything that you find applicable, check the logs, etc.

If you can't get it to work, go to the support thread and provide as much detail as possible about what you've done and all the results (with logs) from that.

Good luck
[Magisk] sumitgp:
Thank you sir for giving me such advice

I will try my best
[Magisk] biggdevon:
Is there a simple module out there I could copy/tailor you use the built-in resetprop functionality? Trying to set/suedo set a couple build prop values. I have the template downloaded but I have very minimal coding knowledge. Thanks in advance.
[Magisk] Didgeridoohan:
There's no coding knowledge required. Just follow the instructions in the template carefully, start with config.sh and module.prop. After that you add your prop values in system.prop (there's an example to follow).

There are plans on adding a prop value editor to the Magisk Manager and while waiting for that you could also simply add a file (name doesn't matter) in /magisk/.core/post-fs-data.d with the following contents:

#!system/bin/sh
resetprop <whatever prop you'd like to change> <the value you'd like to change it to>

It'll be executed at boot and that way you won't have to tinker around with modules.

Magisk and Magisk Hide is working as it should. CTS profile mismatch while basic integrity reports as true means Google doesn't trust your device/ROM (there's no matching certification profile on their servers). This isn't a Magisk issue and I think your best bet would be to try to find some info in your device's forums.
[Magisk] smoothfreeze:
My bad on the crosspost. I did some digging and found out that an unlocked bootloader instantly FAILS SafetyNet. Magisk is indeed working as it should be. Sigh. There's no way getting past this, right..?
[Magisk] Didgeridoohan:
Well, if you look in your log, you'll see that Magisk is actually masking your unlocked bootloader (ro.boot.verifiedbootstate). If that wasn't working basic integrity wouldn't report as true.

Did you actually read the the first few posts of the thread you're posting in (this one)? I believe I've covered most of this in post #4... I see I need to do some minor updates though.
[Magisk] Didgeridoohan:
Did you read or search? No...

Your question is answered in one of the sections in post #2 of this thread...
[Magisk] biggdevon:
Is this a hard change or a suedo change like the rest of Magisk functions?
[Magisk] Didgeridoohan:
All of this is systemless. It's kind of the point of Magisk... :)
[Magisk] biggdevon:
Tis the very reason I'm using Magisk. Never used the scripting method so wasn't sure whether or not it was still a systemless change. Thanks for the help.
[Magisk] sumitgp:
Dear sir

I tried as u said but i m not able to pass safetynet with the hlep of magisk but i m abled to pass safetynet through #isu v4.5 apk

Basically #isu v4.5 apk work with los or cm base rom

Currently i m using rr 5.8.3 in leeco le 1s(X507) i just turn all props green and then write in ro.build.fingrprint following

"Letv/Le1s_IN/X3_HK:6.0/DHXOSOP5801911241S/1479990092:user/release-keys"

I don't know due to this i passed safetynet or not

Major drawback for using #isu. it doesn't support xposed module in nogat(7.0.x) like magisk has its own module and also only support cm or los su other su not work with #isu

#isu only and only work in cm or los based rom

Sir plz don't get me wrong i just want to help magisk team to make magsik more perfect and useful tool

So i m sharing link of #isu bcoz i read before magisk has issues with cm or los based rom .

iSu [4.5] Simple app to deactivate activate CyanogenMod/LineageOS SU at will

https://xdaforums.com/android/apps-games/isu-simple-app-to-deactivate-activate-t3478348/page77

Thanks and regards as well as lot of love to all magisk team
[Magisk] Bebi_v24:
I enabled Busybox and "lost" root, usually it goes away after some reboots but not this time. In Magisk Manager the setting to disable (along with other settings) aren't there since it doesn't think I'm rooted. Can I disable Busybox via recovery? What should I do?

EDIT: Disregard, meant to post in the support thread
[Magisk] YourTheBest:
I can't remove system apps with Magisk on EAX rom.

Why? I have V12 version. I can have root access, but not in /system. Help...
[Magisk] Didgeridoohan:
Wrong thread.

You need to take a left at the next intersection. The first door on your right is the support thread.

And make sure you gives as much details as possible about your device, what you're trying to do, how you're trying you did it and it's also a good idea to provide logs (a Magisk log is a good start).
[Magisk] markkuw33:
fingerprinter stoped workin

Hi,

I did just installed and rooted with magisk to my honor 8, android version 6.0.

When I booted up everything worked fine,(including safenet) but... My fingerprint/fingerscaner doesn't work att all.

Can any1 tell me what's wrong?

Thanks in advice