yashsingh1/xdaforums huggingface dataset:
[Magisk] toddre:
So no luck with Magisk V6. Losing root after reboot. Have tried numerous times both clean and dirty. Anyone want to take a guess what the most likely cause it? Stock rom and kernel Nexus 6. I have installed in this order Magisk, modified phh-superuser, Magisk manager and then phh app from play store. Root works and I can grant permissions as needed until reboot.
[Magisk] Artim_96:
Get the zip of phh's SuperUser v2 (don't know if it's still linked here somewhere), unpack the installer apk from there, install it zip uninstall it and then try again the version 1.2... Sounds strange but it works.
[Magisk] M4rt1n94:
[MENTION=4470081]topjohnwu[/MENTION] First: Thank you for this awesome App works for me (OnePlus 3T) perfectly!

There in one thing that I would like to request.

Can you make a Module which disables "Secure Flag" because I'm on Android 7.0 and XPosed SDK 24 is not out yet but maybe you can port that Module to Magisk? :)

Would be awesome!
[Magisk] saikoz:
Thank you so much!

silly me, miss this out ...
[Magisk] Fentadroid:
[MENTION=4470081]topjohnwu[/MENTION] did you find out possible reason for Titanium Backup (any version) crash at startup? I'll try to uninstall magisk and see what happen.... (oneplus 3 with OOS 4.0.3).
[Magisk] Didgeridoohan:
Are you talking about bypassing secure windows (FLAG_SECURE) and being able to take screenshots of apps that don't normally allow it?

That's not how Magisk works. Both Magisk and Xposed use the words "module", but they're not the same and have no cross compatibility whatsoever. Think of Magisk as a "file injector" where it can replace files and props in the system to do it's thing and it does this on boot, not on a running system. Xposed is a "code injector" that can alter the code and behaviour of running apps.

[MENTION=4470081]topjohnwu[/MENTION] have hinted at a "code injector" concept for Magisk, but that could take a very long time to develop (as in: don't hold your breath)...

Source: https://xdaforums.com/showpost.php?p=71136458&postcount=9473

---------- Post added at 10:49 ---------- Previous post was at 10:35 ----------

Have you tried the unofficial snapshot release? If it has to do with TiBu's compatibility issues with MagiskSU (system rw), that has been fixed in source and the fix will be in the snapshot release.

https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901

Also, when debugging things like an app crashing it's really useful to provide a logcat from the crash. How to logcat.
[Magisk] Fentadroid:
Sure, i'll try that!! Thanks

I'll provide logs :)
[Magisk] mobileman88:
I am using stock nexus 6p with march update just fine on magisk 11.1 . might be a root conflict in your ROM?
[Magisk] M4rt1n94:
Yes that was what I was asking about :)

Also I made some deep testings and found some bugs.

I tested it (best Appy to test something like that) on a Bank App "VR-SecureGo" (known for detecting ALL kind of root)

First it worked like a charme then 1 hour later it failed sometimes so I had to switch to Systemless Host-Data and back and it worked again. After hours ago it failed again (root got detected) and I had to turn busybox off and on, also Hide-Modus off and on. Then it worked again.

I had advanced logs enabled and will upload the log here.

Additional information:

I'm using a unlocked OnePlus 3T with OOS 4.0.3

I use MagiskSU not SuperSU

#Edit:

When I reboot this Bankapp detects Root, so I switch to SuperUser-Permission from "Adb & Apps" to "Apps" and back again and everything wirks again...strange
[Magisk] Didgeridoohan:
There are a lot of instances of VR-SecureGo in the log. Have you been starting it a lot or is the app simply running in the background and performing constant checks? Could be that it "overloads" the Magisk Hide daemon and it just needs a restart (and that happens when you toggle the different settings). Did you try turning Hide off and then on again those time it started detecting root again? That's a surefire way of restarting the daemon.

On a reboot it sometimes happens that the Hide daemon doesn't start properly. Toggling Hide off and on usually takes care of that.
[Magisk] M4rt1n94:
Like I wrote I tested this over some hours and yes I started it a many times.

When the App is reopened this should not overload the App as this will happen soner or later when you use you phone for a while.

An indicator if the deamon is running (and all the other things are properly ok) would be good :)

Just saying, but the App itself is just great!

#Edit:

Sometimes I git the feeling the deamon is crashing every x-min because i just tested it again (without opening it a lot times) first time it did not work, now it works again
[Magisk] Didgeridoohan:
Looks like TiBu doesn't have permissions to access the storage. Check in "App info" if it has the proper permissions.

(And don't post logs directly in your post. Attach or use a service like Pastebin.)

---------- Post added at 12:36 ---------- Previous post was at 12:22 ----------

Maybe you could try catching a logcat of the app not detecting root and then detecting root all of a sudden and uploading it as an issue on GitHub (with Magisk logs and boot image as well)? Might be something useful in there for [MENTION=4470081]topjohnwu[/MENTION] to look at...
[Magisk] oakley470:
Exact same problem I am having on N6 with lineage, others on op3 don't remember which ROMs. For me I had to run the magisk uninstaller, then reinstall and never enable magiskhide. You'll keep root but won't pass until someone figures out what's going on
[Magisk] NovaViper:
Um.. Didgeridoohan, I STILL can't seem to get the latest to work. The steps I tried ends up with the phone bootlooping
[Magisk] Spacedementia87:
I seem to be having issues with an app called payqwiq (https://play.google.com/store/apps/details?id=com.tesco.payqwiq&hl=en_GB)

My root hiding is obviously working becvause android pay is working fine, payqwiq is still sating i cant use the app on rooted devices still...

SafetyNet Checker passes.
[Magisk] Didgeridoohan:
Simply sounds like it's not compatible then... Remind me: did you try a beta snapshot?

Could be that the app looks for other apps or processes as well, or certain prop values. I've collected some tips here:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] NovaViper:
I do but I did used to run v10.2 of Magisk.. Maybe its my current baseband version?
[Magisk] Didgeridoohan:
I'd guess it's your boot image not playing nice. Samsung... Not exactly the mod friendliest devices around.

I'd open an issue on GitHub with details about your problem, a copy of the boot image and whatever logs you have.
[Magisk] NovaViper:
Odd thing is.. I think its something relating with the fact that I had bricked my phone fro flashing the SM-G925F rom and kernel on the phone (it had completely bricked the phone and even flashing my phone's stock firmware and kernel didn't work).. Today I'll try to flash PG3 firmware and see if it makes a difference
[Magisk] fndpena:
When I had supersu, I used to update OTAs using flashfire (to prevent loosing root). But now with Magisk I'm not sure what I need to do...

I guess flashfire won't keep magisk if I try to update. Is there anyone here in the same situation as me?
[Magisk] Artim_96:
... Where is the problem in just flashing Magisk again after the update? You only have to flash one zip do the rest is saved inside the magisk.img
[Magisk] Telperion:
Trying asking again in here... Is it conceptually possible to create a fork of Magisk that uses a ramdisk block device instead of a loop mounted block device? This would extend Magisk functionality to devices with no loop mount support, such as Nougat on the Honor 8.

Something like this which works on Ubuntu (modified slightly), unsure if it would work on Android:

# mknod -m 660 /dev/block/ram3 b 1 1
# chown root:disk /dev/block/ram3
# dd if=/dev/zero of=/dev/block/ram3 bs=1k count=64k
# /sbin/mkfs -t ext4 -m 0 -O ^has_journal /dev/block/ram3 4096
# mount -t ext4 /dev/block/ram3 /magisk
[Magisk] fndpena:
There's no problem flashing magisk after... I was just wondering if there was any straightforward solution, because I don't have a custom recovery.

Back in supersu days, I used to download the zip, flash it with flashfire and I was good to go.

Maybe I can put magisk in the flashfire queue, just after the OTA zip, but I'm not sure if it's gonna work...

EDIT: To be more precise, I'm running stock and I wish to install march's security patch.
[Magisk] jhedfors:
Just tested this myself with no SuperSU installed. Should work fine.
[Magisk] fndpena:
Hmmm good to know :)

Thanks a lot!
[Magisk] Sharp852:
How is the Magisk Multirom feature doing?
[Magisk] jhedfors:
Look at [MENTION=4470081]topjohnwu[/MENTION]'s comments in the release thread. It is on hold while he focuses on compatibility for more devices.

BTW, I want this badly as well, as the current solutions all have issues.:)
[Magisk] fndpena:
This is what I'm planning...

The last one is franco kernel.
[Magisk] Artim_96:
That means that you are running either a Nexus or a Pixel device?

That should mean that you can boot a custom recovery without the need to install it.
[Magisk] fndpena:
Yes, but that involves connecting the device to a PC. With Flashfire I wouldn't need to do that.

That's the difference...
[Magisk] dreamland2000:
I've tried this process with a ROM for the 5x but found that the boot.img didn't wipe the SuperSU from the system so caused issues installing magisk.
[Magisk] Artim_96:
That means that it already contains supersu. So either you need a different ROM or at least kennel with it's own ramdisk
[Magisk] jhedfors:
Try flashing Osmosis's unsu zip to remove root from system. Restoring boot image does nothing to remove system root (only systemless).

EDIT: NVM, I see that [MENTION=5125527]Artim_96[/MENTION] already responded.
[Magisk] dreamland2000:
That's what i thought, i was hoping I could have got rid of SuperSU but even the unsu zip doesn't work.

---------- Post added at 04:19 PM ---------- Previous post was at 04:18 PM ----------

I've tried that and it still want remove it fully enough to install magisk su
[Magisk] Artim_96:
No, since it needs you to flash a clean boot.img afterwards. So as long as you are not able to remove supersu from it, you have no other choice
[Magisk] Elanza_48:
I think the magisk hide is creating the issue. Working fine after disabling it.
[Magisk] oakley470:
Yes that is the case. I haven't pulled any logs beside the magisk hide log showing su running fine even though it isn't though, so we won't get any support until someone opens an issue on GitHub with a log showing it failing somewhere
[Magisk] jhedfors:
[MENTION=4470081]topjohnwu[/MENTION], Excuse my ignorance, but is root required for Magisk to load modules?

Could you run Magisk without root, just installing modules in recovery? If so, it might be useful to have a rootless option for those who want the customization of Magisk, but want the added security of not being rooted.
[Magisk] Artim_96:
Uh..."not being rooted" and "security"... If you have a malware that can use root rights then I'd prefer to be already rooted and have an app that can manage this permission... Of course assuming that it can't work its way around that. Because since root isn't that common you have to expect them to have included some nasty exploits to gain root access.

But for your question: doesn't only the Magisk manager request root access? Wasn't it possible to use Magisk when it didn't include stuff for root and you hadn't installed it? I mean the only problem was when the manger still required root to open, but you could try to get Magisk 9 to run without root a see what modules are actually able to execute. I mean Magisk basically only copies stuff from /system, read permissions shouldn't require root, and otherwise just mount the image over the existing /system, for all I understood it only needed the SELinux changes in the boot.img to execute the mount scripts
[Magisk] jhedfors:
Thanks for the insight. I may try v9, just to see what happens.
[Magisk] Telperion:
I'll echo what [MENTION=5125527]Artim_96[/MENTION] said, I prefer to have my phone rooted and an app to manage root permissions rather than have malware silently gain root without my knowledge. It's a tangent, but it's one of my issues with SafetyNet (or I should say not SafetyNet itself but the way in which many apps implement it), I'd contend that I'm more secure having a device rooted with open-source code than a device with potential malware running rampant.
[Magisk] yochananmarqos:
Flash Franco Kernel before Magisk.
[Magisk] fndpena:
Are you sure? When I first installed, I'm almost sure that I lost franco after installing magisk, then I had to flash franco again. But I don't remember well.
[Magisk] yochananmarqos:
Yes. Magisk backs up the current boot.img and will restore it after uninstalling. If you flash Franco Kernel after, you will lose it if you uninstall Magisk.
[Magisk] gk1984:
Just flashed March security update for the Nexus 6 last night. Now getting CTS profile mismatch with safetynet check. I checked the log and the magisk hide daemon did start. Hadn't failed before, but some weird bug did occur yesterday causing System UI to keep crashing. Had to factory reset. I did this before flashing the security update.

Just sharing as an FYI. But either Google is now doing something different to block us or I've got something else going on that's only affecting me...
[Magisk] Honeycd:
I left it to install correctly but now I get error in safetynet. This is my setup, what can I do?
[Magisk] Didgeridoohan:
You're not alone. There was another couple of reports of this yesterday. But also a success report. Look back in the thread a little. I believe it was [MENTION=5124760]yochananmarqos[/MENTION] that reported a success.

I've collected a bunch of tips for this in it's own thread. See if any of those work:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828
[Magisk] gk1984:
Thanks. I found it but nothing useful for me... I had the same setup. Stock ROM, Franco kernel, magisk 11.1. only I flashed arise sound mod. Never was a problem before. I did see in another Magisk thread that using systemless hosts caused this problem for someone else m I tried disabling that too, but didn't work. I think I'll go full stock after work and test. Then try 1 thing at a time.
[Magisk] jhedfors:
Yes. It worked on module that changes props via post-fs-data, but not on one that changed via system.prop. So as you indicated, it is probably hit-and-miss as far as module compatibility.

I was more curious than anything. I am happy with the way it works now.
[Magisk] meiser:
DELETED
[Magisk] Spacedementia87:
Unfortunately none of these tips seem to work.

Tried hiding from a load of stock apps that done need root and changed all 4 of those props (at least I think I did. I ran the commands in material terminal, I couldn't see a way to get magisk manager to do it like it says)
[Magisk] Artim_96:
1. Try to hide as less as possible with Magisk hide, the more a you select the more likely it is to break.

2. Of course there is no option in Magisk manager to change the props, you'll need to make a module for it
[Magisk] Didgeridoohan:
Apart from what [MENTION=5125527]Artim_96[/MENTION] have pointed out, the props in that thread are only examples. Your app might look for different things... To properly figure out what the app is looking for you might have to decompile the apk and take a look in the code (Google it).
[Magisk] jhedfors:
To add on to this. You can try this:

https://xdaforums.com/showthread.php?p=71273904#post71273904
[Magisk] pairedprototype:
[MENTION=4470081]topjohnwu[/MENTION] I know Pixel support is yet to come but if you'd like an additional tester for it, I'll play guinea pig for you :D

I'd like to fork the repo and take a shot at adding support in and create a PR, but my C/++ knowledge isn't very extensive and I wouldn't know where to start, to be honest. Though, I may have a poke around during the weekend anyway :)
[Magisk] Lost Dog:
I'm in the same situation. I just side loaded the March security update and now get the CTS error. I never did with the previous stock builds on my nexus 6.
[Magisk] locolyric:
is that normal when safety net test fail if systemless xposed installed？
[Magisk] jhedfors:
Yes. Magisk does not hide Xposed.
[Magisk] staygreen420:
i want to root and play pogo with my s6 but want to make sure i got it right before doing it.

do i have to worry about dm-versity?

going to use odin to get twrp

copy magisk11.1 to phone internal sd(its all s6 has)

swipe to allow mods and flash magisk then reboot then its done?
[Magisk] fndpena:
So I finally installed march security patch on my nexus 6p. I've flashed the OTA, Franco Kernel and Magisk (in this order) using Flashfire. Everything went just fine.

As soon as the system booted up, the SafetyNet check wasn't passing, but then I re-enabled Magisk Hide, rebooted and it worked :)
[Magisk] sorewinner:
I really hope phh can fix the disappearing root issue on phones in doze mode. Every day, on multiple phones, reboot to recovery, delete data/magisk directory and img, reflash stock boot, and reinstall magisk, just to restore root. Boot, re-enable systemless adblock check in magisk manager, and another reboot for adaway. Is there any work that topjohnwu can do, since he's now forked phh's root into MagiskSU?
[Magisk] teddy0209:
Check github or just try the unofficial snapshot builds of magisk...
[Magisk] tech_head:
I'm running with the March release and I see no issues on my phone.

I can run Android Pay along with Mobile@Work (Mobile Iron).

What I can't do is run Android Pay on my watch. Whatever mechanism the watch uses to detect root/unlocked bootloader, it's not masked.

Not an issue, just an observation.
[Magisk] Didgeridoohan:
[MENTION=1830372]Lost Dog[/MENTION] [MENTION=3443130]gk1984[/MENTION] and whoever else having issues with their Nexus 6 not passing SafetyNet on the March security update. Check the N6 forums... There seems to be some issue not related to Magisk. Even users with stock, locked systems report SafetyNet triggering (CTS profile mismatch).
[Magisk] fndpena:
Check Android Wear app in Magisk Hide list and see if it does the trick... Since that's the app that makes the connection, maybe it's detecting root and not allowing anything to happen in the watch.
[Magisk] Honeycd:
I've collected a bunch of tips for this in it's own thread. See if any of those work:

https://xdaforums.com/apps/magisk/magisk-magisk-hide-troubleshooting-tips-t3561828[/QUOTE]

in this section you put a few lines of commands that might resolve the problem, can You tell me where I have to enter them? Thanks

"Samsung...

Yeah... Samsung doesn't have the mod-friendliest devices out there. But anyway...

Some Samsung users with custom ROMs have reported that they have had to do some modifications to the permissions for a couple of files related to SELinux to pass SafetyNet. These files are "/sys/fs/selinux/enforce" and "/sys/fs/selinux/policy". The "enforce" file should have permission 640 (rw-r-----) and the "policy" file should have permission 440 (r--r-----). This can be easily automated with Magisks General Purpose Boot Scripts. See here for details. The lines needed for the script are:

Code:

#!/system/bin/sh

chmod 640 /sys/fs/selinux/enforce

chmod 440 /sys/fs/selinux/policy"
[Magisk] Artim_96:
in this section you put a few lines of commands that might resolve the problem, can You tell me where I have to enter them? Thanks

"Samsung...

Yeah... Samsung doesn't have the mod-friendliest devices out there. But anyway...

Some Samsung users with custom ROMs have reported that they have had to do some modifications to the permissions for a couple of files related to SELinux to pass SafetyNet. These files are "/sys/fs/selinux/enforce" and "/sys/fs/selinux/policy". The "enforce" file should have permission 640 (rw-r-----) and the "policy" file should have permission 440 (r--r-----). This can be easily automated with Magisks General Purpose Boot Scripts. See here for details. The lines needed for the script are:

Code:

#!/system/bin/sh

chmod 640 /sys/fs/selinux/enforce

chmod 440 /sys/fs/selinux/policy"[/QUOTE]

Create a module and write the last two lines into the the post-fs-data script and configure the module.
[Magisk] jhedfors:
Alteratively (I think this should work the same as [MENTION=5125527]Artim_96[/MENTION] suggested) put these in a file, and put them in the magisk/.core/post-fs-data.d directory:

chmod 640 /sys/fs/selinux/enforce

chmod 440 /sys/fs/selinux/policy
[Magisk] requiiiem:
Same here
[Magisk] Honeycd:
I don't know if I'm doing something wrong. I have put the file in the folder and I still dating the error message on safetynet
[Magisk] fndpena:
I know this sounds too obvious, but did you try to re-enable magisk hide, reboot and check SafetyNet again?

It worked for me:

https://xdaforums.com/showpost.php?p=71330021&postcount=10066
[Magisk] Didgeridoohan:
Another shout-out to Nexus 6 users with SN issues on the March security update.

[MENTION=1830372]Lost Dog[/MENTION] [MENTION=3443130]gk1984[/MENTION] [MENTION=6150522]requiiiem[/MENTION]

Have you guys tried disabling USB debuggin?
[Magisk] Lost Dog:
Yes, I've both turned off/on magisk hide and also shut off USB debugging.

Looking at the Nexus 6 forum, even people running the unrooted stock ROM are failing the security check.
[Magisk] Didgeridoohan:
Yeah... It was a longshot... Seems like Google forgot to CTS certify the Nexus 6 for this update. :D
[Magisk] gk1984:
Yup to it all and still fail. Looks like it's in Google's hands now.
[Magisk] tech_head:
I tried to enable hiding for Android Wear and all the associated. Nothing worked.

Interesting enough i did manage to have Mobile@Work (MobileIron) quit working.

Safetynet still passes with no issues.

I'll stop fiddling before I break everything.
[Magisk] H4X0R46:
Failing safety net check on my Nexus 6 with March update as well! Guess I'm not the only one! Hope it gets fixed soon!
[Magisk] yilun:
Does anyone know why my n5x won't boot after flashing magisk? Yes, only ROM and magisk won't boot. Tried with validus and pure Nexus. It just stays on the "google" text and a lock.
[Magisk] NovaViper:
Sorry for taking so long to respond! I was trying to find a ROM but couldn't succeed so I flashed back to stock and installed SuperSU and finally got it to install v11! The phone isn't bootlooping either :D
[Magisk] konoplya:
what version of android does this support?? i have 4.4.2 on my nexus...
[Magisk] yochananmarqos:
No, no one knows why without a TWRP log. I've never had that happen on my 5X.
[Magisk] hsiehboss:
My cell phone also had this problem before yesterday.

I uninstall all doze function software such as greenify and update franco kernal , until now, it has not yet happened again.

To provide you with reference.

我從使用 Tapatalk 的 Nexus 6P 發送
[Magisk] Link_of_Hyrule:
With the latest version it seems to be working fine now.
[Magisk] agustincordoba:
Hi, quick question. I am looking for a way to hide/disguise the root status from certain applications - these show a message when you try to run them saying that they will not run in routed devices. I am using a Meizu M2 Note. Is Magisk what I need?

MTIA
[Magisk] Jenanga:
Ähm.......... Yes
[Magisk] Didgeridoohan:
Probably. Magisk has a function for that, Magisk Hide. No guarantees, but if your device is compatible you should only have to install Magisk, activate Magisk Hide and add the apps to the Hide list. Note that you have to use the included MagiskSU for Magisk Hide to function. If you're using systemless SuperSU that needs to be removed prior to installing Magisk. The installation script will attempt to remove any other root solution found and install MagiskSU instead.

Take a look in the release thread for installation instructions and you can also take a look at my collection of troubleshooting tips and tricks if you run into trouble along the way.
[Magisk] agustincordoba:
Great. I'll start reading the tutorials then. My Meizu has the stock Rom and I am already root...
[Magisk] agustincordoba:
Can I simply click on download/install from within the application?