yashsingh1/xdaforums huggingface dataset:
[Magisk] Didgeridoohan:
Did you take a look at the recommended reading I linked earlier? There's a little bit of info in the release thread about the pseudo enforce mode.
[Magisk] Galactus:
Some random information for UK Banking App users

Confirmed Working by myself

Natwest - Works (Fingerprint Works)

TSB (New App) - Works (Fingerprint Works)

Halifax - Works
[Magisk] seacowx:
Ok i understood. Thank you, sir.

To be honest, I haven't. I'll have it later.

*Had issue with my old Viper4Android. doesn't work as selinux changed to enforcing upon magisk hide. Updated to ARISE and it works.

Sorry for spamming this thread and for bothering you, bytheway. Thank you, sir.
[Magisk] chazarss:
phone has stuck after removed root via SuperSu and rebooting, can anyone suggest way to fix ?
[Magisk] Didgeridoohan:
Could be the boot image that's messed up. Try reflashing your ROM's stock boot image.
[Magisk] Fry-kun:
Any luck with fixing lost root on Lineage?

I don't use root explicitly very often, and seems that AFWall applies its rules in time before the root is lost (and they stay applied, which is great!).. but I still need a soft reboot to get root to work for other use cases...
[Magisk] chazarss:
Fixed now thanx, just flashed magisk.zip via twrp over this issue
[Magisk] _Dusty_:
For some reason my magisk hide stopped working properly?

Atleast I think it's magisk hide, the problem I have is that I can't install certain apps from the play store anymore (Netflix and Super Mario run for example)

Normally I would enable magisk hide after a clean flash and it would fix everything however this time it doesn't seem to work.

Here is the log, looks oke right?

[IMG="Log"]http://imgur.com/a/ui86t[/IMG]

ugh embed the image doesn't seem to work :/ imgur.com/a/ui86t while I try to fix it.
[Magisk] Didgeridoohan:
You'll need to make sure you pass SafetyNet, then clear data for the Play store and reboot.
[Magisk] _Dusty_:
Ahaa I tried everything in the troubleshoot post but I forgot to reset cache ! :D Thanks everything works fine now :)
[Magisk] fhLan:
[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=7460565]seacowx[/MENTION] yes I'm stuck at permissive
[Magisk] Didgeridoohan:
What about the logcat from when things are working, that I asked about earlier: https://xdaforums.com/showpost.php?p=72250291&postcount=13246
[Magisk] culiacanazo:
Didge, can you please, at your convenience, hit me up on pm? I've never been able to start a conversation, only reply (I'm on labs, never tried other methods)

Thank you
[Magisk] DAXX:
I'm experiencing magisk not rooted functionality greatly limited. Not sure why???

---------- Post added at 04:45 PM ---------- Previous post was at 04:42 PM ----------

The only temporary solution to my issue is to re-flash the system.img through TWRP, until it happens again...
[Magisk] darylzero:
Does magisk support Nexus player

nexus player is ARM x86

i installed magisk on it loads up well but modules when downloaded and installed do not show after reboot

like modules after reboot disappear

i wanted to use magisk for nexus for the adblock module

thnx
[Magisk] Handsome Jack:
unlocked bootloader is required to install Magisk?

hxxp:\\www.droidviews.com\install-magisk-systemless-interface-android
[Magisk] DodoGTA:
Yes (because it modifies the boot image)
[Magisk] Handsome Jack:
Does this mean that I have to root my phone first?
[Magisk] teddy0209:
No...

---------- Post added at 04:42 AM ---------- Previous post was at 04:41 AM ----------

Why system.img? Magisk does nothing to system...
[Magisk] Bryanx86:
Have you tried just rebooting without flashing system img to see if that works?
[Magisk] DAXX:
Not sure why??? but It works momentarily...

---------- Post added at 10:00 PM ---------- Previous post was at 09:57 PM ----------

I did, It did in the beginning, but now it keeps saying the same message which is super weird... I ended up going back to supersu as it works the best. :/

Anyway to hide supersu on nougat? Xposed is sort of out of the question at the moment as the framework isn't ready yet, any other methods similar to root cloak? Magisk doesn't seem to be working well with the custom rom that I'm using... :/
[Magisk] teddy0209:
Just clear data of magisk manager and reflash magisk... If that doesn't work, restore your boot.img, delete magisk.img and reflash magisk...
[Magisk] tag68:
If system is modified, Magisk most probably will not be the cause. So it seems you need to search for an app using root rights to modify system, causing you to lose root. A start may be to look in the Magisk Manager which apps are allowed to use root.
[Magisk] DAXX:
Tried that, no luck... :/
[Magisk] Bryanx86:
Have you also tried flashing BusyBox cleaner zip and then reflashing magisk v12? I did this when I had an issue similar to yours. There's a link for that zip somewhere in this thread if use search function
[Magisk] DAXX:
yupp, still no luck. :(
[Magisk] AiaceT:
Magisk installation on O+3T after unroot via SuperSU app

Hello to everyone,

I had unroot my Oneplus 3T using the SuperUser in app function, after that I have flash from TWRP Blue Spark edition the OnePlus3T_4.1.3-(11-4-17)-Firmware-flashable.zip and after the Magisk-v12.0.zip (one after the other).

I obtained a

ERROR: 1 Error installing zip file '/sdcard/download/Magisk-v.12.0.zip

Despite I don't had a bootloop but considering the Error 1 issue as "something that goes wrong" and considering what is written on XDA - [2017.4.26] Magisk v12.0 - Root & Universal Systemless Interface [Android 5.0+]

I flashed the Magisk Uninstaller and then I reboot the system. All good, system reboot normally and now I have no root, no SuperSU, no busybox, no Magisk.

Following the TWRP complete log to have your advice and suggestion:

Updating partition details...
...done
Full SELinux support is present
MTP Enabled
Installing zip files'/sdcard/Download/OnePlus3T_4.1.3-(11-4-17)-Firmware-flashable.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
Flashing OOS 7.1.1 Firmware + Modem
Writing 7.1.1 system

Updating partition details...
...done
Installing zip files'/sdcard/Download/Magisk-v12.0.zip'
Checking for MD5 file...
Skipping MD5 check: no MD5 file found
******
Magisk v12.0 boot image patcher
******
-Mounting /system(ro), /cache/, /data
-Device platform: arm64
-Constructing environment
-Creating /data/magisk.img
-mounting /data/magisk.img to /magisk
-Found boot image: /dev/block/sde18
-Unpacking boot image
-Checking patch status
[B]SuperSu patched boot detected![/B]
Adding ramdisk patch script for superSU
[COLOR="Navy"]We are using SuperSU's own tools, mounting su.img
!SuperSU image mount failed
Magisk scripts are placed correctly
flash SuperSU immediately to finish installation[/COLOR]
Updater process ended with error: 1
Error installing zip file '/sdcard/download/Magisk-v.12.0.zip

Updating partition details...
...done
******
Magisk uninstaller
******
-Mounting /system(ro), /cache/, /data
-Device platform: arm64
-Found boot image: /dev/block/sde18
-Unpacking boot image
-SuperSu patched boot detected!
-Flashing stock/reverted image
-Removing Magisk files
-Done
Updating partition details...
...done

Observing the log, do you consider that someting was not correctly done?

Do you evaluate that the bolded line "(SuperSu patched boot detected!)" concerning that the unroot via SuperSU and the next reboot had let some SuperSU "residue" on the O+3T?

Considering the blu log lines:

"We are using SuperSU's own tools, mounting su.img

!SuperSU image mount failed

Magisk scripts are placed correctly

flash SuperSU immediately to finish installation"

do you evaluate that if a SR3-SuperSU-v2.79-SR3-20170114223742.zip flash via TWRP was done after the Magisk v12.0.zip flash as asked in the log file (flash SuperSU immediately to finish installation), Magisk will be installed properly on the device?

Why the log report a "!SuperSU image mount failed" when it tried to install the "SuperSU's own tools "?

Sorry for my worse english and thanks to all that will spend some time to give me suggestions to solve the problem
[Magisk] teddy0209:
Your boot.img is still patched with supersu, you have to restore a clean boot.img... If the one that comes from your rom is patched, find a clean one... Then install magisk...
[Magisk] Handsome Jack:
Alcatel Ideal (4060a) cannot unlock bootloader. It can be rooted.

There is a person told me "if you're​ rooted you should have the bootloader unlocked anyway."

Should I root this Alcatel Ideal (4060a) and then install Magisk?
[Magisk] TheCech12:
Samsung Galaxy S3 (i9300) - Magisk Hide Problem

Hey!

I have some trouble with Magisk Hide on my Samsung Galaxy S3 i9300. I wiped the phone with TWRP (Dalvik, Cache, System, Data, Internal Storage).

I flashed LineageOS 14.1 (10.05.2017) (it has no root), Open GApps (11.05.2017) and Magisk v12. After initializing the phone I turned Magisk Hide on and restarted the device. The phone is rooted but I tested SafetyNet and it checked the status forever... :/

So I read some guides to fix that problem. I found out, that Magisk Hide does not unmount something:

** Magisk post-fs mode running...
** Magisk post-fs-data mode running...
* Running post-fs-data.d
* Loading core props
** Magisk late_start service mode running...
* Linking binaries to /sbin
* Starting MagiskSU
* Running service.d
* Starting MagiskHide
MagiskHide: Moving and re-linking /sbin binaries
MagiskHide: Removing dangerous read-only system props
MagiskHide: resetprop by nkk71 & topjohnwu
Initializing...
Modify data structure: 'ro.debuggable'='0'
Existing property: 'ro.debuggable'='1'
Recheck property: 'ro.debuggable'='0'
Done!
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=
MagiskHide: com.google.android.gms.unstable(PID=4479 ns=[0 4479 10034 com.google.android.gms.unstable service com.google.android.gms/.droidguard.DroidGuardService]
)

I found this thread. The kernel logcat support runs. I didn't change the logger buffer size from 256.000. Systemeless Hosts and Busybox are deactivated. The Core Only Mode didn't change anything. Magisk v11.6 has the same problems on my phone.

After manually disable and enable Magisk Hide, these lines are added to the log:

MagiskHide: Stopping MagiskHide daemon
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Removing dangerous read-only system props
MagiskHide: Killing com.google.android.gms.unstable
MagiskHide: Starting MagiskHide daemon
MagiskHide: Update process/package list:
MagiskHide: [com.google.android.gms.unstable]
Zygote(0) ns=

So the unmounting does not run. I also tested the Xiaomi workaround and changed the last line of the enable script. This didn't change anything.

I tested to change the build.props (type, tags, flavor) to the safe values. It didn't change anything.

I don't know, what I can do now. I hope someone can help me.

Note: When I don't flash Magisk, the SafetyNet test is green

Note 2: SELinux is Enforcing
[Magisk] AiaceT:
Magisk install on O+3T via SuperSU

Thanks teddy0209!

Could you think that a stock ROM installation from TWRP recovery will be solve the boot.img patched with SuperSU problem?

Otherwise could you suggestiva where to find a clean boot.img to restore and how restore it?

Always thanks
[Magisk] teddy0209:
Go to your device forum... That's better place for that... Just try extracting the boot.img from your rom and flash that in twrp... If it still gives that error then go to your device forum and look there...

---------- Post added at 10:56 AM ---------- Previous post was at 10:53 AM ----------

Why the xiaomi workaround if your device is not xiaomi?... Remove that module, reinstall magisk... Try disabling and reenabling via terminal...
[Magisk] TheCech12:
I tested disable and reenable manually (with terminal) before I tested the Xioami workaround.

I never installed any module. I reinstalled magisk so many times on a clean rom and every time the same problem. :/
[Magisk] Didgeridoohan:
Interesting. Let's see if we can figure out what could cause this then... I'd love to add it to my guide.

Could you run the disable and enable script manually in a terminal emulator and report back with the output?

su
cd /magisk/.core/magiskhide/
sh disable
sh enable

And as first post goes, this one's absolutely brilliant. It warms my old XDA heart to see someone actually doing research before posting. Thank you. :highfive:
[Magisk] teddy0209:
If you want to use that workaround, you need to add the props values for your device...
[Magisk] Didgeridoohan:
Hold your horses... I just reread your post and saw the thing about the SafetyNet never finishing.

Have you made sure if Magisk Hide works at all? Add a root checker or an app requiring superuser access to the Hide list and see if it can't detect root.
[Magisk] Wire1122:
This is my boot.img http://www22.zippyshare.com/v/vmPVSZGz/file.html

I can't flash magisks 12.zip with twrp becouse an error occours. Can't mount image error
[Magisk] teddy0209:
It's better to post the log here than the boot.img... You boot.img most probably is patched for supersu, you need a clean one...
[Magisk] xavihernandez:
Hi,

R
[Magisk] seacowx:
Because that from nandroid backup boot.emmc.win

Twrp flashes only .zip / .img

(and if the boot.img backup already patched with superSU then it's useless to flash it. Magisk won't be installed)

Suggestion 1: Try to extract original boot.img from your ROM zip and flash within twrp.

Suggestion 2: If you can't find boot.img, And only if the boot.emmc.win backup is unpatched, then try flash it using fastboot.

fastboot flash boot boot.emmc.win

If it doesn't work, just restore your backup using twrp.

If you're insisted installing magisk on your curent ROM.. Then find a way to:

• Clean up your device from superSU patches (full unroot).

•• Or re-flash original boot.img (the unpatched one).
[Magisk] xavihernandez:
Hi

Root is working for some apps (Greenify, file manager, Ghot log, oandbackup, etc.), but for some others it just cannot (even Root verifier tells me I have a root binary but app cannot get root, autostarts won't change autostart settings).

Has anyone got any clue?
[Magisk] seacowx:
Not sure what troubles you're facing.. If not the superSU probs. Then just do us a favor repeat the process..go to twrp re-flash magisk. Go back to twrp menu, click advance - click copy log. Grab the log and send it here.
[Magisk] teddy0209:
If that is his only problem, he can just restore it, or rename the file to boot.img...
[Magisk] seacowx:
Not sure about renaming it. You tried? did it flashable?

Uh! don't bother we're talking a ghost. He's not even read our posts here. *Log's needed.
[Magisk] Didgeridoohan:
After having time to take a proper look I realised you probably have some kind of issues with zygote and the mount namespace. I have very limited knowledge about the inner workings of android, so that's a bit out of my league. It could be a ROM issue (I don't trust LineageOS :p). Since you're wiping and flashing anyway, you could try another ROM, maybe one that's more based on stock and see if there's a difference.

There's been a lot of changes in the code since Magisk v12, so there's a chance it'll work in the next version. You could try the most recent beta snapshot. It's far from certain it'll work (they haven't exactly been release ready for a while), but if it does work give that a try and see if it fixes things.
[Magisk] Wire1122:
Sorry this is my log http://www38.zippyshare.com/v/W9rUQ0vB/file.html

---------- Post added at 03:30 PM ---------- Previous post was at 03:26 PM ----------

Sorry this is my log http://www38.zippyshare.com/v/W9rUQ0vB/file.html

When i flash magisks through twrp, it fails to flash with an error: create magisks.img, can't mount image.

I want root my lg g5 SE h840 through magisks and not supersu. Supersu unroot success. Thx
[Magisk] teddy0209:
Yeah... been doing that img to twrp backup and vice versa...
[Magisk] MysteryMan105:
I have been trying to root my Huawei Nova for the past few days and it has constantly failed one way or another. Before all of this I did have EMUI 5.0 and Nougat, that I installed normally through an update, but during the process of rooting I had a few problems with TWRP that caused my device to enter a bootloop and I had to install a stock ROM that downgraded me to EMUI 4.1 and Android 6.0. I already found a way of again returning to EMUI 5.0 and Nougat but I believe that the TWRP versions that are for my device (unofficial, as there weren't any for the Nova on the official TWRP website) aren't compatible with EMUI 5.0 and Nougat. I have searched a bit and have found out that there is a way of rooting without the use of a custom recovery by using ADB and Fastboot, which I actually have been using the entire time :(. This is my first time rooting so I would definitely appreciate if someone answer a few questions I have:

1. Is there a stock recovery.img for my device that you can link me, as this seems to be a way of removing TWRP (if there are other methods of removing TWRP that you know of some help with that would be awesome!)

2. Is Magisk compatible with my device

3. Because I have already had many failed attempts to flash Magisk and phh's Superuser, could there be some files that were installed despite the flash failing (Updater process ended with ERROR: 1) and if so will these cause me problems with rooting after updating to EMUI 5.0 + Nougat and removing TWRP with stock recovery.img (>If true some help to remove those files would also be great!)

I'm sorry for the long post, I just wanted to make sure that my problem can be understood so that anyone willing to help has all the info necessary.
[Magisk] seacowx:
1) Can't create /data/magisk.img

2) Data can't be mounted

3) Cannot locate Boot image

4) Etc.. it's in italian language?

Try to mount Data, Cache in twrp menu. click Mount →check box Data and Cache only (and microsd card if you placed the magisk.zip in that)

Edit: Still not working? Reflash your clean boot.img. and try flash magisk again. have you done that?

>> I don't know if magisk be able to flash using twrp 3.0.2 or not. Ask around..<<

If it's still failed. Worst case scenario..you need to dirty flash your ROM.

*Ask others for other suggestions.
[Magisk] teddy0209:
Logs please... You said you've tried flashing a few times... For the stock recovery, you can extract from your rom zip/or whatever the format your oem is using...
[Magisk] Wire1122:
Italian
[Magisk] MysteryMan105:
Is this the log you need?

https://pastebin.com/ndAVYhhE
[Magisk] Wire1122:
Can't mount data is greyed out
[Magisk] teddy0209:
What are you trying to flash?

I don't see magisk in the log, or maybe I'm just sleepy...
[Magisk] MysteryMan105:
I tried to flash phh's Superuser and Magisk but it could also be that I had tried flashing Magisk before installing the TWRP recovery that I used to fix my bootloop and that downgraded me too EMUI 4 and Android 6 (wasn't a stock ROM, my bad)
[Magisk] Wire1122:
Can't mount data, it is greyed out
[Magisk] TheCech12:
Thanks for the hint to the beta snapshots. I tested the actual snapshot (Build 170512: Magisk & Magisk Manager App) and it looks like the same problem. But it looks like that Magisk Hide does not start anymore. When I disable it at terminal I get the message "Magisk Hide is not enabled". And when I enable it nothing happens there is no message. :/

I will try it after the weekend again.

I like LineageOS very much, but if there is no other possibility, I have to try another ROM.

Are there any workarounds for problems with zygote and the mount namespace?
[Magisk] DodoGTA:
Try to run "magiskhide --enable" on Magisk v13.0 snapshot
[Magisk] :
I wish to request a multi-user feature, just like the one we have in SuperSU.

As you can see, I modified my buildprop and have more than one user. Pic #3 is from the Magisk Manager on profile #2, and pics #4 and #5 are from the manager on the "owner" profile, where we can see Manager for profile #2 is being denied. Not only is it being denied, but it also doesn't prompt me to grant it permission, and I can't manually add apps to the "grant" status without the prompt, much less one from a different profile.

This means profile #2 has no root access, so I am requesting the multi-user feature to be added to Magisk and/ or its manager. The same option SuperSU has.

Thanks in advance.
[Magisk] DodoGTA:
MagiskSU multiuser support is planned
[Magisk] :
[MENTION=6429309]DodoGTA[/MENTION]

Thanks.
[Magisk] DEVILOPS 007:
Hi, how do I access root through terminal? su worked with supersu but I'm not sure about with magisk. Also, anyone know how to fix this? Thanks.
[Magisk] DodoGTA:
By typing "su" in it
[Magisk] DEVILOPS 007:
Su with quotes? I tried typing su normally like with supersu but it didn't work.
[Magisk] rignfool:
I'll bet you either don't have the manager installed... Or haven't opened the manager before opening titanium backup...
[Magisk] DEVILOPS 007:
I did both of those.
[Magisk] rignfool:
What device?

Did you enable busybox in Magisk... Did you enable magiskhide?
[Magisk] DEVILOPS 007:
Nexus 6p and yes I did and no I didn't enable magiskhide.
[Magisk] rignfool:
Does your ROM include busybox in system?
[Magisk] tech_head:
Did you get a prompt asking for root access?

I never had to do anything special. I have a 6p running 7.1.2 and Magisk 12.
[Magisk] DEVILOPS 007:
I don't think so, I just tried everything again but made sure to update magisk manager then tick the busybox option before anything else. That are titanium backup and su commands work fine! However, I wanted to test what a dirty flash would do and a dirty flash caused the same issues again with titanium backup not having root access and termux not working with root.

---------- Post added at 10:22 PM ---------- Previous post was at 10:21 PM ----------

I did only after trying again and I made sure to update magisk manager then tick the busybox option before anything else. That are titanium backup and su commands work fine! However, I wanted to test what a dirty flash would do and a dirty flash caused the same issues again with titanium backup not having root access and termux not working with root.
[Magisk] njk45h6:
Problems after rooting my s8+

I rooted my Galaxy S8+ (SM-G955F) with Magisk, I've enabled Magisk Hide and selected the SecurityLogAgent app from the list. However, I still get the notification on the drop bar which says:

How do I prevent this? I don't want to disable SecurityLogAgent; just bypass it by making it looks like the root process is fine and there no unauthorized changes on the device.

I can't even receive software updates. This message pops up:

.

A similar message pops up also when using the pre-installed "Personal Area" app by Samsung.

So I unistalled it both from inside the app and by using the Magisk-uninstaller-20170320.zip script. Then I proceeded to format the partitions, do a wipe (data,cache and dalvik) and flash the stock ROM for my country (taken from here). So my phone should look "fresh". The software updates work fine but it still says

What should I do to fully unistall it or make it truly hidden from the apps?
[Magisk] therawski:
Hello, I am trying to get Super Mario Run to work and while i am using Majisk hide and editing my build.prop I still am unable to get this game to load. I have a T-Mobile Samsung Galaxy S4 and am running on Optimized Lineage OS 7.1.2 Stable 3 (it worked on Stable 1 & 2)
[Magisk] teddy0209:
Did you check the troubleshooting tips thread?... Check that... Just to check if magiskhide is working, you can use root checker app, add it to magisk hide and do a rootcheck...
[Magisk] therawski:
Well it's quite hard to troubleshoot this as I have been all over the place trying to find help specific to this problem.

If I turn on Majisk hide and add it to the hide list, root checker says I'm properly rooted. Am I not supposed to add SMR to the hide list?
[Magisk] teddy0209:
Just check the thread... Pretty much everything is written there... https://xdaforums.com/showthread.php?t=3561828
[Magisk] Kireto00:
My magisk after download modules it says installation failed in all modules it downloaded right but the problem is in installation my phone is honor 4x .......thx for help