yashsingh1/xdaforums huggingface dataset:
[Magisk] rauleeros:
My logcat is attached to this post. Even though I pressed the "Freeze" button 3 times to make it easier to find in the logcat, I have not been able to see any messages that can give us any information.

Thanks for the tip, but this did not work either. What is interesting tho, is that if it works for you, the problem shouldn't be in TiBu... What "Processing mode" do you have in TiBu settings? I have the "Auto Direct". Also, in "Troubleshooting settings" do you have the last option "ICS-friendly Freezing" checked?

Nevertheless, I have tried playing with the different options, but still got nothing
[Magisk] rmead01:
I'm having an issue with Magisk 11.1 that I haven't had since a few versions ago. I'm on a Nexus 5x using 7.1.2 and used the last stable version of 10 with no issues. Since upgrading to v11.1 I lose root after a few hours of normal use. I open the Magisk Manager app and it tries detecting the Magisk version and says root is unavailable. Rebooting the phone fixes this issue. I have Magisk Hide on but the only things hidden are the default programs detected to use safety net.

I'm attempting another fresh magisk installation after flashing my boot and system images. Just at a loss to what is going on and didn't see much recently about this issue.
[Magisk] Didgeridoohan:
Users that experience loosing root on v11.1 have reported disabling Busybox in Manager settings as a temporary fix until the bug can be found and fixed. Give that a try...
[Magisk] rmead01:
Busy was never enabled to begin with. :(
[Magisk] Didgeridoohan:
Ok. Too bad... Then I'd advice you to try catching a logcat of the issue to help with troubleshooting.
[Magisk] rmead01:
It's been a long time since I've done a logcat. Is the magisk log enough? Also because I don't know exactly when it looses root, just notice when I don't have it eventually, will that be a problem with a timely log?
[Magisk] 101_North:
I'm now thinking that the 'losing root' issue is simply the app failing to display root properly for some reason. I had disabled busybox but today the app showed no root several times. All my root apps functioned fine. No reboot needed. If I closed magisk manager from my recents and reopened it then root showed green again.

I have re-enabled busybox and rebooted. Again magisk manager has showed no root but my apps all work OK. Simply closing and reopening manager makes root show green again.

I'll need to watch over the next few days, with busybox both enabled and disabled, to see if root is actually affected or if it's just a status reporting issue in the manager app.
[Magisk] Boole_the_boolean:
Noob question here. How can I flash MagiskSU ? I don't see any options on the Magisk App to do so... (Nexus 6P , PureNexus, ElementalX kernel)

Thanks !
[Magisk] gohamstergo:
It's part of 11.1. Flash that and install the latest Magisk Manager and you'll have it.
[Magisk] Boole_the_boolean:
Thanks !

I tried to flash it, but then I've got an error: "SuperSU patched boot detected .." . What should I do now ? Flash the boot img again ?

Thanks for your help !
[Magisk] culiacanazo:
Exactly that...
[Magisk] Kr47os:
Hi can anyone explain me how to backup and restore boot.img on twrp recovery?

Thanks to everyone answer
[Magisk] Badger50:
Select boot from the menu, and back it up. Then when you want to restore it, hit restore from the TWRP menu, select boot, and there ya go.

Sent from me :)
[Magisk] jhedfors:
You can find the boot image in your ROM zip. In twrp, select install, and choose image option, instead of default zip format.
[Magisk] sunkit:
Hello all, I have a new Xiaomi Mi5s PLus, unlocked bootloader, flash twrp recovery, install Magisk v11 with su, have xposed also, got the green light of SafeNet check.

But still cannot use Android Pay, is there any things I can try? or it due to the unlocked bootloader?

another problem is Titanium backup, when I used Magisk v10, it still can freeze the apps (cannot uninstall system apps, is it because of systemless root?)

but after update to V11, it cannot freeze anymore, neither system apps or installed apps.

I’d appreciate it if you’d help me.
[Magisk] RandomPooka:
Just out of curiosity, when you look in a file manager, is there an /sbin/su symlink to the actual file /magisk/.core/su/su ? Maybe the placement of the files is different for your device? I'm on a Nexus 6 (shamu), and it doesn't play well with Tasker.

I'm beginning to wonder if the problem is that Tasker won't follow the symlink on its own and detect root, unless expressly directed to call su in my tasks. Even after it is approved in the superuser list, it still can't find it.
[Magisk] rolandyip:
Deleted.....
[Magisk] rolandyip:
After i put off Sim Tool Kit from hide list still same.

When i disable MagiskHide SELinux is permissive Phone is working. But when enable MaiskHide SElinux become Enforcing Phone wont working.
[Magisk] nimjk:
I found an error with dorimanx and magiskhide.If I want to use magiskhide (so I turned it on), the screen went black out. But I turned it off, this doesn't happen... And i can use dorimanx stweak with v11 but can't use with v11.1
[Magisk] foxsprout:
Good morning! I found that *probably* after Magisk v11, the boot time has been increased substantially (my boot time is about 2 mins now). Is it just me? Or is it just placebo since I also have many apps. But I reckon that before v11, the boot time is fast (<1 min). I'm asking because I wasn't sure whether Magisk is the culprit.

P.S. I'm using OP3T OOS 4.0.3 with Franco Kernel and Magisk v11.1, flashed using TWRP 3.0.4-1
[Magisk] GryphonBR:
Haven't had any problems with SystemUI so far, but I can't seem to get Magisk Hide to work anymore. The log is incomplete, it doesn't seem to be able to actually hide the necessary folders - any tips?
[Magisk] LuanTeles:
Fail to restore Ramdisk on galaxy s6 running tn kernel Magisk 11.1
[Magisk] Phazonclash:
EDIT: Nevermind, I searched thought the thread and found out I'm no the only one who can't get root (MagiskSU) to install when /data is formatted using the f2fs filesystem.

Hope someone will figure out what's happening someday ;)

Weird issue I have with a Galaxy S7 edge + Magisk 11.1.

As long as I'm using ext4 partitions (system, data and cache), everything's perfect. I can flash a different kernel, reflash Magisk 11.1, and I end up with a perfectly bootable, MagiskSU rooted phone that passes Safetynet

But as soon as I convert my /data and /cache partitions to f2fs (my kernel and ROM both support f2fs and /system is writable), then reinstall my ROM, my kernel and Magisk 11.1, problems start: I can reflash Magisk 11.1 as many times as I want, MagiskSU will never install and work, even if TWRP says otherwise.

On the Samsung S7 edge, MagiskSU simply won't install correctly if you use /data and /cache f2fs partitions!

Any idea?
[Magisk] Didgeridoohan:
I'm gonna continue with some pure and utter speculation.

If it's SELinux and the new pseudo-enforcing mode that Magisk Hide uses causing you issues it should be easy to test... Change SELinux to enforcing without enabling Hide and see if the problem arises. I guess it could be possible that whatever ROM you're using can't handle even pseudo-enforcing SELinux...

If you're interested in passing SafetyNet, this would be a problem since permissive SELinux triggers SN... I see you have a couple of other apps on the list as well though.
[Magisk] bmg1001:
As soon as you boot up, open the Magisk app and check if it shows root. If so, does closing the app and reopening later on show that it is not rooted?
[Magisk] Didgeridoohan:
I'm gonna continue my wild speculations today and try dabbling in mind reading (DISCLAIMER: This is a poor attempt at sarcasm brought on by the underwhelming lack of details provided. Please ignore.).

Your boot image is probably still patched for SuperSU. If that's the case (you can see it in the recovery log), flash a clean boot image and start over.
[Magisk] yochananmarqos:
Magisk should have no impact on boot time as it does nothing until boot is completed.
[Magisk] Phazonclash:
I managed to fix my problem 5 minutes ago :good:

Looks like there's a bug in TWRP 3.0.2-4 preventing Magisk 11.1 to be flashed properly on a f2fs /data partition.

I found a patched/modified version of TWRP 3.0.2-4 here for the S7 edge that pretended to fix the inhability to flash Magisk 11.1 (and MagiskSU) properly on f2fs partitions

Confirmed. After flashing that TWRP modified version using Odin, I used the TWRP file manager to navigate to /data and indeed, I could see files and folders in /data. That folder was empty (couldn't be read) using the official TWRP 3.0.2-4 build, so it couldn't be written neither

So from here, I:

-Formatted my ext4 /data partition

-Converted it to f2fs

-Restored its content with a TWRP backup I had

-Confirmed TWRP didn't reflashed it back to ext4 (wasn't the case)

-Reflashed my kernel (SuperStock)

-Reflashed Magisk 11.1

Here's the result (f2fs /cache and /data + ext4 /system + working Magisk 11.1 and MagiskSU):

:good:
[Magisk] Filip013:
My device (Xiaomi Redmi Note 3 Pro) doesn't support NFC, so I'm not sure, but when you open Google Play and go to settings does it say Certified? If not, try clearing app data for Google Play. Also, I just tried freezing and defrosting an app and it works.

I have no idea what you just said. There is a symlink file /sbin/su on my system, but I can't make sense of it with a text viewer. See if you can. Also, here's a log if that can help you.

Sure! Make sure you enable Magisk Hide after you've disabled Xposed (for some reason it won't even start with Xposed active). Second of all, do a proper reboot. (Side rant: I hate how long it takes MIUI to shut down. And I especially hate it when I get a phone call while shutting down so I have to listen to my phone ring for half a minute and not be able to do anything). Maybe you lost me there. The point is you can't use Xposed Installer to reboot, you have to use the power menu. And finally, maybe Magisk Manager updated itself to 4.1? It could be that you forgot to disable auto-update in Play Store after a clean flash. :confused:
[Magisk] tag68:
Be careful! If I remember the explanation correctly, it is dangerous to use a corrected kernel (in your twrp) and afterwards a kernel without that fix.
[Magisk] Wesley_NL:
a question , when will there be a updated magisk that get the /system/ part also writeable of the SM-G928F Nougat rom, if that part is fixed i can change/mod couple files to pass safetynet and get viper4android to work
[Magisk] garthybarthy:
I'm still having the issue on 11.1 with magisk hide having to be toggled on/off on each reboot. Samsung G920F. No big deal though. I'm using a custom kernel as per OP instructions.
[Magisk] teddy0209:
Aren't you able to mount it using file manager? (Like root explorer, solid, etc...)
[Magisk] foxsprout:
I thought it has something to do with boot because of Magisk Hide
[Magisk] bland.life:
I read that Magisk has problems with Titanium Backup.

Seems like only freezing apps is talked about, how about backup and restore?

Is the backup and restore functionality affected?
[Magisk] Didgeridoohan:
Titanium Backup may have problems if you need to do something that requires /system to be mounted rw. Like deleting system apps.

Everything else should work without issues. I've used both backup and restore extensively the last couple of days.
[Magisk] ElenaPower:
Hi, I just installed SuperMan-Rom 2.1 with current version of Magisk and I have a problem in running a root needed tasker task that starts a shell command.

I use tasker for enabling/disabling flight mode in the night hours on my S7. For this I have created a tasks that beside other things runs a shell command.

Up to now after I installed a new rom version I had to manually run this task in tasker one time to get the dialogue from SuperSu for giving tasker root rights. Now, with the new version of Magisk this does not work anymore. I get no dialog for granting root access. Setting supersu to not ask but always allow root does not work too.

I made two screenshots. the second shows what tasker shows me when I manually run the task. Hope this can be fixed.
[Magisk] Didgeridoohan:
It's a known issue that Tasker doesn't recognize root with MagiskSU.

Edit:

https://xdaforums.com/showpost.php?p=70956425&postcount=8841
[Magisk] Wesley_NL:
as you can see in the attachments, root browser say operation failed and es file explorer says rename sucsefuly but no changes, abit odd isn't it ? that es file explorer can sucseed but dont aply changes

also mount it with root browser? how? root browser is alowed in magisk su same for es file exploere
[Magisk] 101_North:
Just lost root again with busybox enabled. Root apps stopped working. Closed the magisk manager from recents panel and then reopened it. Root status goes green and all my roots apps work again. Looks to me like root is never actually 'lost'. I'm not sure that the busybox option is the reason as I can replicate the issue, and the solution, with busybox either enabled or disabled.
[Magisk] teddy0209:
Try root explorer...
[Magisk] dcdruck1117:
This isn't working for me to get Tasker commands to use root again with Magisk Manager 4.1 and Magisk 11.1. The commands still error out and complain about no root.

However, if I install phh's superuser from the Play Store again, then try again in Tasker, it does work. What's odd to me though is it's MagiskSU that prompted and granted root to Tasker (not phh's), it just couldn't be detected without phh's installed, too. If I go to the phh app, the are no "granted" apps listed. If I go MagiskSU, Tasker is now listed.

Note that if I uninstall phh, Tasker stops working again.
[Magisk] Nomelas:
I still keep randomly loosing root using magiskSU even though I haven't touched any settings. I'm on lineageOS 14.1 for oneplus one.
[Magisk] RandomPooka:
Looking at the file in a text viewer isn't going to help much. You should be able to see where it points in any self respecting file browser. If not, try long pressing on it and selecting "properties" and see if it tells you where the REAL su binary is located.

Or just navigate to /magisk/.core/su/ and look to see if that's where it is. Either way, it's less of a problem for you, if you aren't actually having issues with Tasker and Magisk 11.x. I was mostly thinking out loud in case someone else could add to it.

In Tasker's task view, for each individual shell command in a task that needs root, try put your ENTIRE shell command and all the command line arguments in quotes, and put 'su -c' in front of it (without the quotes). This is working for me, at least.

That's odd. Is your Tasker command something you can screenshot without exposing personal information? Maybe there's a typo. But, that command should make Magisk Manager prompt you for root access. Double check the superuser section of Magisk Manager to see if you don't have Tasker denied, then make sure the "Use Root" box is unchecked. Empty.
[Magisk] Didgeridoohan:
Remove Magisk Manager from any battery saving apps (Greenify) and set it to not optimise in battery settings. Could be that the Manager can't wake up properly after getting "hibernated".
[Magisk] dcdruck1117:
It's a simple "input keyevent 26" that I had changed to "/sbin/su -c input keyevent 26" but I forgot to uncheck the "Use Root" box so that could have been why it still didn't with. Tasker didn't show up at all in Magisk Manager at that point though, denied or otherwise.

I'm kind of ok with my current workaround though of having phh's also installed just bc it allows Tasker to find MagiskSU root. Kind of a bizarre workaround, but it's working for me for the time being.
[Magisk] 101_North:
I'll give it a go. Thanks.
[Magisk] ElenaPower:
That did not work for me, you mean:

su -c '<my complete shell command>'

I still get the message with missing root rights. But installing phh's superuser worked like described by dcdruck1117.

Now Tasker thinks that root rights are available and the command works fine. I even can freeze phh's superuser with Titanium Backup and it works. And not phh's super user asked me to grant root rights but Magisk's and Tasker now is in Magisk's Superuser list as allowed what it was not before.

So it looks as Tasker is only checking for existing files/directories?
[Magisk] RandomPooka:
The quote needs to be before INPUT

su -c "input keyevent 26"

So strange that it works for that. If you uninstall the phh app after tasker starts behaving normally, does it break again, or do you need to have it installed and frozen?
[Magisk] kryptikal:
Great find! [MENTION=6168497]dcdruck1117[/MENTION]

Previously I couldn't even get Pairs to launch because it said there was no root and Magisk's prompt to grant superuser never appeared.

While I was able to get Tasker to work with [MENTION=3053466]RandomPooka[/MENTION] 's workaround ( e.g.

uncheck

"Use Root", then /sbin/su -c "input keyevent 26"), I was not looking forward to altering all of my "Use Root" commands as I have quite a few to simulate various screen taps & gestures. I can happily confirm that installing phh's SuperUser app from the PlayStore then freezing it with TiBu does indeed fix the issue. MagiskSU, for whatever reason, now allows all of my "Use Root" Tasker commands to work normally and both Tasker & Pairs appear in the list inside Magisk Manager -> Superuser.

Thanks! :D:D:D
[Magisk] LazerL0rd:
Is there a way to pass SafetyNet with Magisk Hide and SuperSU? I've got a CTS profile mismatch but Android Pay does finally open. Previously, it used to show an error saying that my system was modified or something. Does it mean that I'll be able to use it in purchases yet?
[Magisk] dcdruck1117:
You're right. That was a silly mistake on my part. I'm sure it would have worked had I entered the command properly in Tasker AND unchecked "Use Root".

For me, if I uninstall phh's Superuser after getting Tasker to work, Tasker does break again and can no longer find root. I did not try freezing phh at all, but if I start to notice compatibility issues with having both MagiskSU and phh's installed at the same time then I will try it. For now though it seems to be working OK for me.
[Magisk] Captain_Throwback:
Doubtful.
[Magisk] LazerL0rd:
1) Have you got any idea on the best way I could do this?

2) Btw this thing installed/updated randomly that is called "Google Play services for Instant Apps", since it's a Google Play Services thing, should I hide it from Magisk?

3) Google Play says my device is "Uncertified". Should I hide it too?
[Magisk] Captain_Throwback:
Magisk Hide does not hide SuperSU.
[Magisk] :
I am on Nitrogen OS 7.1.1 with Magisk 11.1 installed and MagiskSU and SELinux Enforcing. Magisk Hide is enabled, but still can't bypass SafetyNet. Any suggestions?
[Magisk] Captain_Throwback:
Logs...
[Magisk] :
Here.
[Magisk] Captain_Throwback:
Advanced logging enabled?
[Magisk] :
Seems the same even with Advanced Logging enabled.

PS: It's different.
[Magisk] Captain_Throwback:
Could be a ROM issue. I don't know anything about the ROM you're using, but there are many factors that can cause SafetyNet to fail. Magisk Hide only patches the most common ones that typically affect stock ROMs. There are too many variables in custom ROMs to be able to ensure it works on those. So you may need to seek help in your device forum and/or ROM thread.
[Magisk] :
Yeah, probably a ROM issue, I had the exact same settings on Lineage OS 14.1, but never had an issue. But I though I might be missing something, so asked here first.
[Magisk] moktadir:
On OnePlus One CyanogenOS Marshmallow, trying to find a workaround led to my UI bricking, so I ended up installing from scratch. Oddly enough, my data partition must've been corrupt, because a fresh install finally led back to Magisk working and SELinux happy again.

I tried enabling Systemless, but doing that once again triggered the CTS mismatch.

Hopefully this info is useful for anyone still having trouble.

Sent from my OnePlus One
[Magisk] Filip013:
I have a question. When you run SafetyNet Helper or SafetyNet Playground, what results do you get? Is it just CTS profile mismatch or is it also Basic Integrity: false? Because if it's just CTS profile mismatch without Basic Integrity: false, it means that you are not doing anything wrong. Your ROM is simply not certified and there's no way for you to make it certified. But you should still be able to use some SafetyNet apps like Pokemon GO. (I don't play it, but it's a useful app for testing.) I don't think you'll be able to use Android Pay (if your phone/country supports it).

If you're getting Basic Integrity: false that means something is wrong with your ROM and there may or may not be something you could do. I don't know the situation with your device.
[Magisk] :
Cool, thanks I din't know that! :D

To be honest, I didn't pay much attention if it CTS Profile Mismatch or also Basic Integrity: False. I can't check what it was, because I moved from this ROM due to this.
[Magisk] chlap:
Anyone running Barclays app with magisk?
[Magisk] devilman30:
No issues here with Barclay's.
[Magisk] chlap:
Can you send me what you did it works. How you set up magisk....? Android pay works but Barclays detecting root.
[Magisk] tafo:
Guys, i had the problem that i lose root while using magisksu 11.1 , i installed BusyBox app and reinstalled busybox again, so far the root still fixed and working properly.
[Magisk] GryphonBR:
Not exactly sure how, but I managed to do it (it might just have been sheer patience, though after my previous boot I waited for, like, 20 mins and it never started properly) - and even with Xposed active, in fact.

Currently running v4.0+v11.0 with Xposed MIUI arm64 and all seems to work, except for a few perks (like Fingerprint Enabler module not working at all, but I guess that has to do with MIUI customisation).
[Magisk] LazerL0rd:
Well it did from Android Pay. I think it's cause I've kinda merged Magisk with SuperSU's boot.img but idk. SafetyNet still fails.
[Magisk] yung40oz84:
I cannot pass safety net, flashed all the latest, AOSIP, OP3....all options checked in settings for busybox, magisk hide, do I have to disable magisk???

Here is a log for no safety net pass
[Magisk] Didgeridoohan:
Woah! That Arise module is a heavy one... Log looks ok. I'm gonna go with my goto response:

https://xdaforums.com/showpost.php?p=70426733&postcount=7120
[Magisk] Rennie-Boy:
OK so I have magisk flashed with MagiskSU and now I have "root" and finally passing Saftynet after trying loads of other things so I'm rooted and can now play Pokemon Go etc.

The only thing is I don't appear to have full root. Titanium back keeps giving me a message and does nothing (I know this is an issue but I mounted system as RW and still doesn't work), Lucky Patcher doesn't show any patch to android options and various other apps only have limited options compared to other roots.

I tried flashing SuperSU systemless along with Magisk which gives me all my root options and privileges back in my apps but then fail Saftynet again (even with SUhide). I can't seem to win. Is there something I'm missing?
[Magisk] yung40oz84:
OK, maybe ADB debugging, I am trying a new setup anyway here, I get back to ya bro
[Magisk] Didgeridoohan:
You're new... A tip: using "that" app (the fortunate one) is a sure way of not getting any help on xda. This is a developers forum and that app is used to cheat developers... Doesn't matter if you're not using it "that way". Don't use it.
[Magisk] Filip013:
I'm still curious how SafetyNet works on different devices. I have a hunch that no (or hardly any) custom ROM can pass SafetyNet. Try this.