yashsingh1/xdaforums huggingface dataset:
[Magisk] SirPsp:
I cannot toggle root off.

I have root access, but when I try to toggle it off it turns itself back on after 1 second, however no apps have root access anymore until a reboot. (no root access, but SafetyNet still fails).

If I delete /system/xbin/su myself then it says Not Rooted, and SafetyNet will pass. Root toggle is unavailable. A reboot restores root.

Samsung Galaxy S4.

CM13 freshly installed.
[Magisk] zzzhead:
Read the posts last few pages, there are other locations with su binaries. You have just identified one..
[Magisk] Tesla:
No. CM13 is fine with this.

Just do a full unroot and follow the instructions in OP.
[Magisk] Mauziii:
Tried this on my OPO with Android N, cannot get it to boot up. Is it because Android N is not supported yet or am I doing it wrong? If so, could someone provide me a guide for it?
[Magisk] SirPsp:
I have read the previous pages. I don't have binaries in any of the other locations mentioned. I've seen other people post who are unable to toggle and have no solution.
[Magisk] Turbopuschel:
What exactly makes sense to you? Lollipop being the culprit?

Because as I see it now after trying to research the matter, Magisk requires the possibility to root your phone systemless which means without modifying the /system partition. This seems to generally require at least Android Marshmallow but it seems to be also possible on some (or all?) Samsung phones with Lollipop. That would explain why I could use this Magisk method on Marshmallow RR ROM on a Sony device (Xperia Z1 Compact) but not the newest stock ROM (Lollipop 5.1.1).
[Magisk] gk1984:
It's working for me on Nougat on my Nexus 6. It might be your device, rom, or something the manufacturer might have done differently than others that might require something specific. Unless you're missing something in the steps.
[Magisk] Skyrider:
Magisk Manager:

Boot version: Magisk v

Root status: Not rooted

Senlinux status: Enforcing

Root toggle: off (GREY)

Selinux Toggle: On (GREY)

^ Any reason why they are grey? (and thus uncheckable) I've installed magic v6 & phh superuser 17 magisk through TWRP.
[Magisk] Brnway:
Hopefully an easy question:

I got Magisk and SuperSU set up and working great yesterday. Pay and PokeGo both working flawlessly.

Today SuperSU prompted me to update my su binary. Will Magisk continue to be able to hide root if I allow SuperSU to update that?

Sent from my IBM Selectric
[Magisk] aliabkad:
Awesome, magisk is the futuristic mod, thanks topjohnwu, this is amazing, amplify, greenify, gravity box wannam, xposed 86.5 , safety net all works , my goodness, with a stock rom, emotion r26 kernel on zerolemon, my phone is golden , expect my donation .
[Magisk] hokey10:
when i toggle the root off and reopen the manager, it reverts back to on again.

trying to get a system update but root just stays permanently on.

what am i doing wrong? are those 2 toggles the only settings available?
[Magisk] westeight:
This usually happens if you have some residual files left over from a SuperSU uninstall.

More info in the Magisk / Android Pay thread.
[Magisk] agentdr8:
Chroma comes prerooted (at least for the 5x). Either flash the UnSU package floating around, or run the "Full unroot" option within the SuperSU app. If you've flashed any Xposed framework installs, you'll want to flash their uninstaller packages too.
[Magisk] anshsharma123:
Getting this! Unable to log in! Followed all steps correctly!
[Magisk] lukazaz:
Can someone please confirm steps for CM12.1 (for a galaxy S5) and CM13 (Nexus 6/Shamu)

From what I understand its

1 - dirty or clean CM flash

2 - flash magisk

3 - install/flash magisk module manager

4 - reboot

5 - success??
[Magisk] Tesla:
Apparently not.

Do you have regular xposed installed? If so uninstall it.

---------- Post added at 05:40 PM ---------- Previous post was at 05:36 PM ----------

I skipped step one, did fine.

First make sure that you have a complete unroot.

Then make sure that you have uninstalled xposed.

There are stepps you are missing, more to install. Look at OP or search this thread and you will find what.

Everything you need to know is in this thread. Find it :)
[Magisk] Didgeridoohan:
And your ROM/kernel have native init.d support, or are you using some kind of workaround?

Have you tried placing the script in /magisk/.core/post-fs-data.d instead?
[Magisk] Rom:
I have RR Rom on my D855 (LG) so yes this ROM have init.d native support :good:

I will try that in few hours when i will have my computer, i could merge my script in th other path.

EDIT: I do not understand clearly how to configure the file "post-fs-data.sh", i understand his interest has explain (https://xdaforums.com/showpost.php?p=68967750&postcount=3) but i don't know how to setup this file.

I must put my file path to start instead of "${0%/*}" in the quoted indication about "modname" ?

Or i must "copy & past my file" in the "commun" folder ?

Thanks in advance for explanations @Didgeridoohan :)
[Magisk] alexbelgium:
Hi, the knox 0x0 works alright on my S5. However, the system status is custom, even though it is systemless root. It switches to custom as soon as I flash TWRP. Is it possible to have a system status official while on magisk 13.3?

Thanks!
[Magisk] dashu42332:
Alcatel Pixi 4 (7) 8063

Hi Guys,

I am having Alcatel Pixi 4 (7) WIFI model 8063 chipset MediaTek MT8127. I have the stock backup of ROM. i have try the above magisk patch, but still the same issue cannot mount boot.img. My tab 8063 is marshmallow and it don't have fastboot. I am also attaching the recovery.log. and also block info of my tab.

https://dl.xda-developers.com/4/1/7/0/4/3/8/block.jpg?key=1oziXqln8jU97McW-Rd8GQ&ts=1501508287
[Magisk] yunzo:
Hi,

Thank you for your development of great tools.

On my moto z2 play (XT1710-09, 4GB RAM, 64GB storage, stock ROM), installation of Magisk succeeded with 13.0 (96f8efc, a90e8b6),

but failed with others -- 13.0(54e6a79), 13.0(c4377ed), 13.1, 13.2 and 13.3 -- showing error message as below:

> mount /dev/block/loop1->/magisk failed with 13: Permission denied

There are difference in mounting/unmounting process on /META-INF/com/google/android/update-binary between succeeded and failed version.

So I tried installation of Magisk 13.3 plus replacement of these parts of script including mount_image() function, and succeeded.

But installation of furthur modules (ex. Unified Hosts Adblock) from Magisk manager failed showing error message as below:

> ** post-fs-data mode running

> * mounting /data/magisk.img

> mount /dev/block/loop0->/magisk failed with 13: Permission denied

I think it is because magisk binary fails to mount / on my environment.

Is my assumption correct?

/META-INF/com/google/android/update-binary in 13.0 (96f8efc, a90e8b6):

mount_image $IMG /magisk
is_mounted /magisk || abort "! Magisk image mount failed..."
MAGISKLOOP=$LOOPDEVICE
.....
if ! $BOOTMODE; then
mv /sbin_tmp /sbin
ui_print "- Unmounting partitions"
umount /magisk
losetup -d $MAGISKLOOP 2>/dev/null
rmdir /magisk
umount -l /system
fi

/META-INF/com/google/android/update-binary in 13.0 (54e6a79, c4377ed) and 13.3:

if ! is_mounted /magisk; then
ui_print "- Mounting $IMG to /magisk"
MAGISKLOOP=`$BINDIR/magisk --mountimg $IMG /magisk`
fi
is_mounted /magisk || abort "! Magisk image mount failed..."
...
if ! $BOOTMODE; then
$MAGISKBIN/magisk --umountimg /magisk $MAGISKLOOP

rmdir /magisk
recovery_cleanup
fi
[Magisk] MPeti1:
Hi again! :D

I've updated to Magisk 13.3, and i realized there is no Xposed (MIUI version) for that version. I tried to port the old module, but i figured out i can't use things like that as group with set_perm:

u:object_r:zygote_exec:s0

What could i use for that? I need to set the group of the following file:

$MODPATH/system/bin/app_process32

---------- Post added at 04:33 PM ---------- Previous post was at 04:24 PM ----------

Good question. I think i used total commander or mixplorer, but i don't really remember.

---------- Post added at 04:35 PM ---------- Previous post was at 04:33 PM ----------

Anyway the problems i mentioned are gone, and Liveboot is working :D Now i don't use SuperSU. Only thing is the not updated modules, but i'll try to do something
[Magisk] jenslody:
I can still use the "old" systemless xposed module (flashed through TWRP), but I am on stock Samsung. If the module works with v12, it should also work with v13.x. Only issue is, that it has to be flashed through TWRP, otherwise it bootlops on my J5.
[Magisk] Didgeridoohan:
Your boot image is not recognised by the installer. Try the latest, official version (found here).
[Magisk] Mamayahuasca:
I've checked it on a fresh ROM rooted systemlessly with SuperSU and the SafetyNet check didn't make me lose the root. If you mean losing root gained with Magisk, I don't think SafetyNet check was connected with this issue. It seemed to happen randomly. I also noticed that if I start Magisk Manager just after system start it was more probable to get the information about "No root" if my phone establishes the Internet connection earlier. But maybe I'm wrong.

Now I can't check it because i changed ROM. Now I'm trying with LineageOS 14.1 but it seems I have to flash another kernel (current is 3.4.0). I'll restore a NAND backup later and give you response. I also have to find out about logcat.

It's the first time I hear about the MultiRom. I simply do the factory reset every time before I flash ROM by TWRP.

But I really did it. I didn't have the faintest idea about what is SafetyNet, Magisk and so on. I just wanted to spoof my location and find out I need Xposed v87.0 with MockMockLocation module so I installed it on fresh stock ROM and that's it. It worked for 3 days then it stopped. It's why I'm here :p.
[Magisk] dashu42332:
thank you for reply .i have try both version 13.2 and 13.3 magisk. But give same error "Unable to detect boot image". i have attach log
[Magisk] MPeti1:
Ok, thanks :D

But i also have a problem with downloading modules from the repository. For example if i try to download Audio Modification Library, it starts to install and fails for some reason. I can't read the log because the "Magisk Manager crashed" window immediately pops up. Here i uploaded the logcat captured only about the manager. Before i tried again i cleared the Logcat so you will only see the session when it's crashed.

What caused it? There are old modules in the repository that needs to be flashed in twrp?

---------- Post added at 09:56 PM ---------- Previous post was at 09:20 PM ----------

update: old xposed module not working if flashed from twrp
[Magisk] Augustin79:
Does anyone know why magisk manager crashes every time I choose superuser from the menu?

Magisk 13.3 & manager 5.1.1
[Magisk] shaggyskunk:
I'd suggest that you get a log of the crash - Magisk isn't crashing on my device and it's difficult to say without a log.

From Down the Rabbit Hole by:

My SM-G930W8 ??
[Magisk] quimbexa:
Magisk 13.3 breaks v4a module support for me. That wouldn't be a problem as I'm still on 12 but now I dunno why but I lost root as well... :confused:
[Magisk] Pkt_Lnt:
Clear cache and data of Magisk Manager. Recommended and confirmed to work for the bazillion posts about this. ;)
[Magisk] Augustin79:
Yeah, sorry! Should have searched, my bad! Thanks for the help though, it worked.

---------- Post added at 09:45 PM ---------- Previous post was at 09:32 PM ----------

---------- Post added at 09:50 PM ---------- Previous post was at 09:45 PM ----------

Thank You!!!

I changed Mount Namespace Mode to "Global", uninstalled TiBU, rebooted to recovery and wiped cache/dalvik, installed TiBu and got it to work again. Unsure about the namespace thing so I changed it back to "Inherit" and everything still works. Thanks again, was completely lost as to how to get TiBu to work again until I saw your post.
[Magisk] MPeti1:
Forgot to give logs. Saved from Magisk Manager log.

https://gist.github.com/1bcd55f95c262edee1e22da28bf40c6d
[Magisk] Mamayahuasca:
[MENTION=4667597]Didgeridoohan[/MENTION] I've just solved problem by installing a custom ROM AICP 12.1. Anyway I wanted to say thank you for your tips :D

[MENTION=4925991]Dave_247[/MENTION] maybe you should try this ROM with your Xperia. I think the Sony stock ROM isn't a good option :/
[Magisk] -Happy Feet-:
Hello,

with the latest Update (13.3) i got an Error at payback Pay .

Error 7222. seems the like detect root access again. Anyone using the APP?
[Magisk] -Happy Feet-:
Maybe this log help
[Magisk] Ilsasta:
On my HTC 10 payback Pay works fine with Magisk 13.3.
[Magisk] Rekesz:
Hi guys,

Could someone please help with this? I know that a similar error was solved in another thread with another zip, but that did not help. I tried uninstalling and reinstalling v12, but found that none of the modules work anymore. So I reinstalled v13.1,but the device or resource is busy error message still appears. I have upgraded to v13.3, but it's still coming up.
[Magisk] Finchy11:
There is something wrong with my magisk, modules does not work, only te message visible on screenshots. I'm using Galaxy Note 3 with MagMa UX 9.5 Rom. I will upload log as soon as I will be able to use PC.
[Magisk] methoddon1:
what's up everyone...

will installing Greenify4Magisk open those extra (xposed) module features as to simple Greenify as an app?!

and does Enable Doze for Google Services module actually controls wakes/alarms like Amplify for example? ... (not to that extant of course but to some).
[Magisk] jenslody:
There is an issue with Samsung phones that leads to this.

There is alink on the Unified Hosts Adblock OP that provides more info and a version of the zip, that works also from MagiskManager, but as you also have a broken yt-module you can try to install the modules through TWRP, that should work in any case.

---------- Post added at 01:59 PM ---------- Previous post was at 01:57 PM ----------

For the greenify4magisk-question: no, as far as I know.

The second question, I really don't know, but I would ask in the modules thread.
[Magisk] Didgeridoohan:
Just to clarify on the answer by [MENTION=8340552]jenslody[/MENTION], no. :p None of those modules will give you Xposed-like results.

Greenify will simply be a system app and have a little more oomph when hibernating apps. None of the Xposed features will activate. For that you need Xposed...

The Doze module will simply give you the option to add Google services to the list of optimised apps in the built-in battery optimisation (Doze), nothing else.
[Magisk] methoddon1:
I'm curios if I should exclude apps like Greenify or Magisk Manager from "Optimized" list.
[Magisk] Recycool:
G901F - LineageOS 14.1 26-07-2017, problem: bootloop on magisk 13+, magisk 12 working fine, here you have log, please tell me if this is what you need and if you need me to do something else or just be patient. http://www90.zippyshare.com/v/DRaDciUk/file.html

Tried to upload it on xda but it exceed by much the size limit.

I'll be waiting an answer, thanks!
[Magisk] chemita:
No work for mi. Huawei P9 lite magisk manager 5.1.1 any idea??
[Magisk] cutesniper22:
Hi,

I made a custom script to modify build.prop and put on the path: /magisk/.core/post-fs-data.d/custprop.sh , but it seem like not working. Did i wrote the script wrongly? How do I know the script is running properly? (seem like not logged in magisk manager.). The script written as following:-

resetprop -v ro.miui.region "TH"

resetprop -v persist.sys.timezone "Asia/Bangkok"

resetprop -v net.dns1 "8.8.8.8"

resetprop -v net.dns1 "8.8.4.4"

resetprop -v ro.product.model "Mi5 Pro"

Device Info:

MIUI 8 Marshmallow 6.0.1

Magisk v13.3
[Magisk] Devilix:
Hi, i would like to know if is it possible to use magisk on a stock samsung rom Galaxy A3 2017 (SM-A320FL).

Because i'm worryed about "custom binary block by frp"... Is there a way to remove that kind of block permanently?
[Magisk] DodoGTA:
Did you try to run "chmod 755" on that script?
[Magisk] cutesniper22:
Thanks.. it works. Before that, the permission was in 644.
[Magisk] st_voss:
Mate 9 / Magisk 13.3 systemless hosts support

Using Magisk 13.3 on Huawei Mate 9.

Despite having activated the "systemless hosts file" option in Magisk Manager there is no bind mount of /system/etc/hosts.

The log says a bind mount was setup:

--------- beginning of main
I( 355: 355) Magisk v13.3(1330) daemon started
I( 355: 358) ** post-fs mode running
I( 355: 408) ** post-fs-data mode running
I( 355: 408) * Mounting /data/magisk.img
I( 355: 408) * Running post-fs-data.d scripts
I( 355: 408) * Loading modules
I( 355: 408) * Running module post-fs-data scripts
I( 355: 408) * Enabling systemless hosts file support
I( 355: 408) bind_mount: /system/etc/hosts
I( 355: 487) ** late_start service mode running
I( 355: 487) * Running service.d scripts
I( 355: 487) * Running module service scripts

But the bind mount for /system/etc/hosts isn't there

> adb shell mount | grep loop
/dev/block/loop0 on /magisk type ext4 (rw,seclabel,relatime,data=ordered)

I should note that on the Mate 9 (and probably other Huawei models) /system/etc/hosts is a symbolic link to /vendor/etc/hosts per default.

> adb shell ls -l /system/etc/hosts
lrw-r--r-- 1 root root 17 2017-06-30 00:42 /system/etc/hosts -> /vendor/etc/hosts

Can anyone confirm this?

It kind of used to worked with Magisk v12. With v12 Magisk followed the symlink from /system/etc/hosts to /vendor/etc/hosts and setup a bind mount for /vendor/etc/hosts.
[Magisk] DeathHacker:
I can confirm that systemless hosts do not work if hosts file is a symlink.

My device (the Yoga Tab 3 Plus) has a normal (non-symlink) hosts file, and systemless hosts works fine with that.

To test, I renamed the hosts file to hosts-old, created a symlink to /vendor/etc/hosts, and tried again. This time, it failed. (Note however that /vendor/etc/hosts does not exist on my device)

Also tried simply symlinking hosts to hosts-old, still didn't work.
[Magisk] Mamayahuasca:
Hi Rekesz, I had the same error message with Magisk installed on Xperia Z1C and i solved it by flashing another ROM (AICP 12.1 N 7.1.2 by LAOS Team). Please try flash AICP 12.1 for Samsung Galaxy S4. Good luck! :good:
[Magisk] Dave_247:
Eh it's not that bad. I like still like it because of how stable it is, looks fancy but doesn't bog things down as much as TouchWiz ROMs, as well as being more customisable.

Currently we have OmniROM and recently Paranoid Android but the first is in nightlies and the second only just realised, so both are kinda unstable and have a few issues here and there.

Either way I can't win.
[Magisk] mirko8054:
Does magisk block encryption like supersu does? (oneplus3)
[Magisk] Martydem:
I am new to rooting but I want to remove bloatware from a Lenovo yoga tab 3. Are there step by step instructions for someone new? I don't know what the instructions here mean so can someone lend a hand? Thanks, Marty
[Magisk] Pkt_Lnt:
Start here.
[Magisk] SuperSandro2000:
Nightly is a term that it is build every night. Does not mean it runs less stable. Back when cm did nightlies my maintainer ajay's recommended to use nightlies because they are more stable then experimentals. Sometimes you find a little bug but nightlies do not mean that you need to update every night.
[Magisk] smeejaytee:
She
[Magisk] st_voss:
What do you mean by "blocking encryption"?

I think per default Magisk removes mount options like "forceencrypt" from the fstab file so that /data doesn't get encrypted on the first boot.
[Magisk] matpower64:
For people curious about Fate/Grand Order:

It works fine with LineageOS' su binary + iSU, you need to fix the build.prop through iSU (Hide dangerous props) and it'll break dev options + adb will be wonky.

I wasn't able to do the same with Magisk through, Magisk Hide works well enough to hide RootBeer's detection (even better than iSU, it can pass SELinux checks) but Fate/Grand Order catches it, I tried removing Magisk Manager after setting Magisk Hide up, but Fate somehow still catches it, I even tried deleting /system/sbin (everything Magisk is there) but it was a no go.

Fate/Grand Order doesn't need SafetyNet - It works fine with my phone and it can't pass SafetyNet without Magisk Hide + Universal SafetyNet Fix. AFAIK it checks for su binary in the common locations (Magisk Hide should hide this), ro.debuggable flag and ro.secure flag (Magisk Hide should hide this), release/user keys (Magisk Hide should hide this) and root-related apps such as Titanium Backup, BusyBox and Root Explorer (this being easily fixable for testing), but it seems that there is a deeper check that Magisk Hide misses. Trying to logcat it forcing close was useless here and it doesn't seem to depend on external checks to detect root.

I believe the only reason it works with LineageOS' SU is due to the fact that it can hide itself at kernel level when toggled off.

If someone wants to try cracking the exact issue down, it would be really nice. This is the best I could come up with and it forces you to use system modifications and LineageOS plus breaking SafetyNet.
[Magisk] Rom:
Hello, anyone could tell me how can i update my magisk module by using "post-fs-data.sh" file please ?

On the wiki i don't find clarely procedure to configure that.
[Magisk] Didgeridoohan:
I'm not sure why you're trying to set up a module... I was simply talking about popping your existing init.d script in the /magisk/.core/post-fs-data.d folder.

:eek: You're probably using a way to read the forum that doesn't show signatures, but you should take a look in mine...
[Magisk] wazer1337:
Hello I'm getting Updater process ended with ERROR: 1

Recovery log

https://pastebin.com/iJ6e5V42

Device A7600-F

Android: LineAgeOs 13
[Magisk] deepak3048:
I have oneplus-3 stkck rom and instal with magusk manager 13.3 apk version 5.1.1 but stil sefty net fail what will do plz help any one
[Magisk] mirko8054:
Yes i need this feature. My op3 is unencrypted and for keep the memory unencrypted i have to flash supersu.zip everytime there is an OOS update (before boot). Is magisk the same?
[Magisk] IamIrene:
Hi OP, I just upgrade my firmware

So I just tried to flash magisk 13.3 again, same thing happened, showing Updater process ended with ERROR:1 this message

As requested previously, here is the recovery.log :o

Hope it helps
[Magisk] st_voss:
Yes, it's the same.

Magisk default feature. You can disable the "forceencrypt" removal by selecting "keep force encryption" in Magisk Manager.
[Magisk] Rom:
I thinked that i must configure some strings in the sh file, so i can simply copy my file in the /magisk./core/post-fs-data.d folder, right ?
[Magisk] Rekesz:
Thanks for the advice, but to be honest I'd rather use my current rom as it is a great daily driver. I find it strange that I'm the only one experiencing this ad magisk v12 still runs fine. I'll try over in the rom's thread, maybe someone came across this.

I'll also try to get earlier versions of the module and keep on using v12 if nothing helps.
[Magisk] SolusCado:
This is the only way I can get Magisk to install in TWRP, but it doesn't seem to load properly. SafetNet checks fail (though root works), and I see the following in the Magisk Manager logs:

mount /dev/block/loop0 ->/magisk failed with 13: Permission denied

I have a Moto Z which I just reverted back to stock Nougat in an effort to start from scratch. (https://xdaforums.com/moto-z/development/android-nougat-moto-z-unlocked-versions-t3552210)

I've also tried flashing the boot.img from that ROM separately via Fastboot, installed the latest UPDATE-unSU-signed.zip to ensure there are no traces of SuperSU anywhere, and run the Magisk Uninstaller multiple times. I've also manually removed any files and folders I could find related to Magisk. I've also tried installing Magisk v13.2 and the beta Magisk-v13.0(c4377ed).zip, but every time the installation fails with the same error:

Updater process ended with ERROR: 1

Immediately preceding that the logs say the following:

- Mounting /data/magisk.img to /magisk

! Magisk image mount failed...

Can you explain more about what this patched version is doing that is different from the release version of Magisk?
[Magisk] woozie.2007:
try to instal magisk 11.6, if works, update to magisk 13.3 from the magisk manager.