yashsingh1/xdaforums huggingface dataset:
[Magisk] uudruid74:
NO. Viper doesn't need it to be permissive. Technically, nothing should ever be permissive. What it needs is proper permissions for that one app. If you want to give your friend access to your car, you give him the car key. You don't take all the locks off every door you can find in your car, house, boat, and storage building.

There are better installers that come with scripts to set selinux permissions for Viper so you can keep selinux as enforcing. Likewise, ARISE will do the same.

Keep selinux enforcing and the rest of your problems will go away
[Magisk] rignfool:
Your advice is horrible...

With VERY FEW exceptions... All ROMs ship with a boot.img...

When people are referring to stock boot.img... they are talking about the one that is shipped with the ROM...

By your logic... I would flash the boot.img that came with my device... Completely ignoring the fact that Dirty Unicorns has many ramdisk edits that make it possible for the ROM to boot... And flash a stock Google image...

Or even worse... Flashing a TouchWiz boot.img on an AOSP ROM on a Samsung...

Not everyone stays on the software shipped with the device... And ignoring the base of the ROM like your blanket statement does... Is wrong
[Magisk] demonoidmaster:
Relax i already explained to him about this a few posts back. But thanks for helping out with explaining further what i was trying to say in my other message to him
[Magisk] Dylanballardlgv20:
Oh ok. I didnt know that. So any idea why its not hiding it from safteynet? Any ideas on what to do? Im scratchin my head here

---------- Post added at 12:42 AM ---------- Previous post was at 12:38 AM ----------

Im guessing so. Just wonder why when i setenforce selinux into permissive it still fails saftey net. Its wierd. Cause everything else is working. And was told psuedo selinux was moved and its supposed to hide the permissive status from cts. Ima try uninstalling magisk and reinstalling and see whats up. Thanks for trying to help though. If it doesnt work after a reinstall ill see what else i can find out and if i find that magisk hide isnt doing what its supposed to ill post a log. But like you said it could be and cflumen is just being stupid.

---------- Post added at 01:18 AM ---------- Previous post was at 12:42 AM ----------

Its cf lumen. Even when i put my phone into permissive cf lumen still demands it be permissive. Even when it is. But in compatibility mode it works. So meh ill leave it alone.
[Magisk] yung40oz84:
Does 13.6 fix systemless hosts?
[Magisk] Zackptg5:
Works for me :)
[Magisk] JERW28:
Works for me. See my signature for device details.
[Magisk] yung40oz84:
What works? What u using or flashed? I just used unified hosts 2.7 and as soon as I install it and reboot root is gone. Same issue with the first new beta.
[Magisk] yung40oz84:
Sorry forgot screenshot after flash unified hosts module.
[Magisk] Zackptg5:
Clean flashed 13.6, then uha 2.7 in TWRP and all was fine for me
[Magisk] yung40oz84:
After removing module, root back
[Magisk] yung40oz84:
Mines clean flash, as soon as I flash I lose root, as soon as I remove the module root is back, lol

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

Well at least AdAway is working, that was also breaking root on last beta, so far root is sticking, but no dice with unified hosts module
[Magisk] otaconremo:
Regarding adaway, is it normal that it really modifies the system/etc/hosts file? I mean the date changed and its filesize.

Btw adaway has greyed out option for systemless mode in its preferences. I also toggled on systemless host in manager.

Sorry if this out of topic already.
[Magisk] tag68:
It shouldn't. How did you find out it did? Are you sure you looked at the original? Really?

Question to all: How to prevent any app from mounting system RW? Is is possible to do a "wrapper" inside Magisk around mount which does accept the command for mount system RW, but not execute it, but execute every other command like the original does? I don't want to have a hacker-safe system, just prevent accidental modifications because some app developer for a root tool thinks modification would be what I want and does not explicitly state that system needs to be modified for the current action.
[Magisk] Tweezydak1d:
My OP5 does not boot on latest beta
[Magisk] otaconremo:
I browsed system/etc/hosts and its file details are changed. While all others in the folder are dated Jan 1, 2009, hosts is dated on the time I updated adaway.

I could also find the magisk host located in magisk/.core/hosts which is the same date and size on system/etc.

I believe if magisk implements systemlessly, it shouldn't have allowed adaway to modify system/etc but rather just on magisk/.core.
[Magisk] tag68:
That's why I was asking. And added if you are sure that it is modified. When browsing /system, you don't see /system. You see /system including the virtual changes by Magisk.

You modify /system/etc, but you only think so. In reality you edit the magisk/.core version. Best sign for this is exactly same size, date and time! How shall that be if one is not a virtual copy of the other?

You see the truth only when the mount --bind is not active! Boot into recovery and look there. Do not just browse /system - it was modified systemless by Magisk ;)
[Magisk] jenslody:
For users having issues, when flashing (at least) Xposed through MagiskManager (might also affect other modules, that set non-default selinux-contexts for files) I attached a modified v13.6 to my previous post.
[Magisk] otaconremo:
Thanks for your inputs.. I tested disabling systemless host from magisk and I can confirm my system/etc/hosts reverted back to an old date (Jan 1, 2009 same with other files in the folder).

Now it makes sense magisk is truly systemless. Haha!
[Magisk] rignfool:
You can modify either...

/system/etc/hosts is mirrored from /magisk/.core/hosts...

Modify either... Get desired effect
[Magisk] Loader009:
As earlier stated, I have storage problems with v13.5 and v13.6.

logcat is attached for v13.3 (170806) and v13.6 (current version).

Please take a look. I do not use xposed.
[Magisk] DenyDarko:
The reboot button does nothing after installing any module.

Is it only me?
[Magisk] loner.:
Works for me.
[Magisk] MisiekDP:
I flashed Magisk v12.0 to Nougat (dual ROM) and no root :/

Anyone can help me?
[Magisk] Ja_som:
Wrong thread, this is about v13.6 beta
[Magisk] MisiekDP:
Ouh, sorry :/
[Magisk] Didgeridoohan:
Clear data for the Manager.
[Magisk] JERW28:
I noticed this with 5.2.0 too.
[Magisk] adekboreanaz:
On MIUI Nougat 7.0 Redmi Note 4 Magisk suddenly lost either root or the magisk it self, i only have last_magisk.log hope it contains something if didn't tell me what to do perhaps i could do some other logs

And only with beta 13.6 i have this issues.13.5 never have it
[Magisk] Aldideos:
Hi guys, I installed Magisk 13.6 on my tablet (x86_64) via adb method due the lack of recovery... Now I'm facing errors when I try to install modules "Magisk in not actived!" abort... I checked data and there is no Magisk folder and IMG... I don't know if it could be the problem... Root is working fine, safetynet, for the records, fails but the Rom is in userdebug and test key... Tomorrow I'll send the logs but I think the problem si the lack of files in data... Thanks for the help
[Magisk] Artim_96:
As long as you took the logcat logs with the second terminal windows the should be enough to find out what went wrong.

The one thing I could suggest would be to start again and pay a bit more attention to the guide, maybe you missed a little detail
[Magisk] Aldideos:
These are the commands I have done via adb ( the second command of the guide is not working so I done it one by one) and the logcat while doing these commands... Redoing it I see that the magisk folder in data is created but magisk img still not... I still have the problem...

Thanks for the help :)
[Magisk] jenslody:
It's a known issue, see my post.
[Magisk] velimirchek:
/crosspost from osm0sis thread,/

Don't know if correct thread and if even error, but with both 13.3 and 13.6 when I install osmosis busybox module I cannot keep systemless hosts on :/.. It always turns off when existing magisk manager.

What I am doing wrong. See pics and logs. When busybox is gone, systemless hosts switch stays on :(

Thanks for all the work.
[Magisk] velimirchek:
Scratch that uninstalled and installed magisk again and all fine now.. Don't know what happened. Sorry.
[Magisk] Aldideos:
Uhm, I tried to create myself the Magisk.img via Magisk - - createimg... But I have two problems... The first is that the Magisk IMG is not mounted at boot... The second is that I doesn't understand how to create hidelist in .core...

Hope somebody knows how to fix this issue... I don't really understand why the image is not created by the script and why the image is not mounted at boot.. :(
[Magisk] marisaleh:
Under V13.6 Installed Adblock Module, when I go to a terminal and do su then type hosts and enable everything

ie mfgps with Magisk Systemless

I am then unable to connect with Facebook via Chrome

Now when I disable everything and start all over again

but this time only enable mfgp

ie leave s (master+social) out I can now connect with Facebook

Can you please guys verify this or is it just my implementation on Nexus 6 running Nitrogen Rom

So enabling host s stops connecting to Facebook
[Magisk] DenyDarko:
If you enable social it will (obviously) block facebook.
[Magisk] Artim_96:
I think I encountered some strange problem. I checked Magisk manager because Greenify wouldn't do the screen off and hibernate. It says "rooted but no root permission, not allowed?" but everything else is green. So I did a reboot but no change.

I'll do a reinstall, but here are the Magisk logs, maybe that can help to avoid it in future
[Magisk] harshal__shah:
Yes I Xposed Rom is Eui n kernel letv
[Magisk] demonoidmaster:
s blocks all social media, it's not a bug.....

---------- Post added at 12:45 AM ---------- Previous post was at 12:43 AM ----------

Did you grant it root when asked?

Also js but greenify needs xposed for some of its features to work
[Magisk] demonoidmaster:
[MENTION=5125527]Artim_96[/MENTION]

Make sure you have this

Other image is for the watchdog service that might help
[Magisk] DodoGTA:
Then remove Xposed
[Magisk] harshal__shah:
Tysm

tysm
[Magisk] DenyDarko:
It seems cleaning magiskmanager app data fixed the reboot button not responding issue.

Weird.

Can't see how those two can be connected. An action button and application data.
[Magisk] Chlorophyll:
After using magisk stable/latest beta version ROOT CALL BLOCKER stopped working.

It worked flawlessly with supersu.I need RCB very badly.Pls help me out of this issue

Thanks in advance
[Magisk] jenslody:
Where do you create it ?

And how do you name the image, Magisk.img or magisk.img ?

The name is case-sensitive.

But it should be created anyway, if it not exists.

Even if it i not populated with the needed binaries. This is because of size-limitations on most boot-images.

But it's a cool method to root your device without relying on exploits, if you can not use a custom recovery for whatever reason.

Can you provide a logcat from booting after you flash the newly created boot.img ?

But @topjohnwu is aware of this and a solution will surely be found (sooner or later).

Flashing this way needs more manual work (at the moment) as through recovery, unfortunately.
[Magisk] Didgeridoohan:
Magisk built-in busybox has been changed between v13.3/v5.1.1 and v13.5/v5.2.0 beta. The button uses this and you need to clear the app data to reload all the busybox stuff...
[Magisk] kartik verma:
unable to install magisk everytime "failed to mount image !"

Device - Moto E4 Mediatek

Android version - 7.1.1

both log file and screenshot from recovery attached below.

plss help.

:(
[Magisk] Syl157:
Hi

i have a moto z play , Android 7.1.1 stock rom with force-encrypt off and dm-verify too, no xposed

Magisk works, but safetynet is red, seems magisk hide is not working even with core mode

here the log on post, thanks :)
[Magisk] guest4711:
Perhaps your magisk.img is broken. Please try the following:

1. Boot into recovery (TWRP)

2. Open the integrated filemanager (on 2. page)

3. Navigate to /data and rename magisk.img to magisk.img.orig

4. flash magisk.zip

5. report your results
[Magisk] kartik verma:
thanks for this quick support :D

i will try it right now :fingers-crossed:

---------- Post added at 03:45 PM ---------- Previous post was at 03:28 PM ----------

still not working and same error..

supersu also not working. supersu unable to create directory /su and other.

:mad:
[Magisk] guest4711:
Bad news. Either it cannot mount system r/w or a problem with root... as if there are some rests of older root installations. Did you uninstall supersu etc. before installing magisk?
[Magisk] kartik verma:
i never install Supersu. only phh's superuser working.

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

another problem init.d also not working.

install-recovery.sh not executing on boot ! can't figure out the problem.
[Magisk] :
Hey guys !

As you may have noticed this thread`s air conditioner isn`t working for quite a while so it is already hot in here , please don`t make it even hotter ... I will keep the windows opened then to facilitate a proper ventilation and also I will be able to properly hear when someone is talking way too loud, I`m pointing to no one for now , just saying

Thanks for understanding

Dan - forum moderator
[Magisk] :
:laugh:
[Magisk] EstiR86:
Seems to be you can't mount system as r/w try flashing the uninstall scripts for phhs superuser and if that doesn't work try a clean flash, get TWRP, then flash Magisk.
[Magisk] Fishawy:
<OffTopic>

This is - hands down - the funniest and nicest warning I have seen during my years on XDA. Love the spirit. :)

</OffTopic>
[Magisk] demonoidmaster:
SuperSU...well there's your issue.

Uninstall SuperSU entirely , same with phh su, remove it all
[Magisk] rignfool:
That quote... Was epic
[Magisk] djmax81:
Unfortunately I too Faced similar issue over Note 4 Exynos !

BTW : seems issue is new new su binary since magisk v13
[Magisk] Illutorium:
SafetyNet are be updated,Then even of "xdaforums.com/apps/magisk/safetynet-fix-pass-safetynet-2017-07-17-t3637801" aren't be helped.
[Magisk] Ja_som:
Please read the OP:
[Magisk] totalcmdext:
Installation is finished properly but the Magisk Manager isn't available.
[Magisk] sumitarora2:
Open the magisk zip you downloaded and then go to "common" folder and install magisk manager from there
[Magisk] Vee89:
Le Sm-t350 ne reboot pas apres linstallation d'un module Magisk.

Bon travail, vous êtes les meilleur! :)
[Magisk] RSDamasceno:
Bug reports:

1) Modules installed through recovery do not appear in the MagiskManager after reboot.

2) MagiskManager unable to install modules.

I'm trying to install the busybox module via recovery (without errors) but after starting the ROM the module does not appear in MagiskManager.

I also tried to install via MagiskManager and the installation did not finish.

3) Systemless host turned off after reboot.

INFOS:

Recovery: TWRP 3.1.1 (With MultiROM v33)

Secondary ROM: AospExtended-v4.5-quark-20170815-1402-OFFICIAL

Magisk-v13.6-170819 (Snapshot)

MagiskManager-v5.2.0-170819 (Snapshot)

LOGS:
[Magisk] demonoidmaster:
Tu peut voir si ton dir Magisk a des fichiers et dirs comme ca ds la pic?

C'est dans /Magisk

PS: quand je dis dir(s) jveut dire "directoire(s)"

Edit: pourquoi tu utilise multirom? Je crois que c'est ca qui cause des problemes :/

-English translation since it's required-

Can you check if your Magisk folder if there's files and folders in it like in the picture?

It's in /Magisk

PS: when i say dir(s) i mean directories

Edit: why are you using multirom? I think that's what's causing problems
[Magisk] zelendel:
Reminder. All posts must be in English or contain an English translation.
[Magisk] demonoidmaster:
The guy speaks french, so i replied to him, why am i the one being told to speak English when all i did was reply to someone..

But fine, cool, I'll just update my post with English below

Edit: i updated my post [MENTION=1140856]zelendel[/MENTION]
[Magisk] Vee89:
Oui

---------- Post added at 04:16 AM ---------- Previous post was at 04:15 AM ----------

Really sorry my english is bad & thanx for ur efforts
[Magisk] demonoidmaster:
Isn't your fault, i was told to write what i wrote to you in english too
[Magisk] reversegear:
Having same issue
[Magisk] Ja_som:
It can be a server side update, and from the OP:
[Magisk] lagendbun:
Just found this thread
[Magisk] Ja_som:
aaaaaaaand?
[Magisk] chjun90:
Stage of "Running service.d scripts" sometime doesn't

run.
[Magisk] Loken88:
I have a problem installing Magisk with version 13+, version 12.0 installs quiet but if I try to update me as an error, I have tried both from recovery and the manager.

Some help?
[Magisk] Demonsannoyed38:
I'm wondering if there is some way in which the sdk/api could be compiled without safetynet built in. How hard would it be to remove that from nougat I wonder. The real issue here is looking at would part of safetynet google are hooking into that is causing the safetynet trip. I reckon Topjohnwu is on this and will find a way. You the man Topjohn.
[Magisk] Bibi white sheep:
I am a fan of Android Rom. I have been following xda for sometime and I really like it a lot. May I ask if anyone has S8 driver with which I can remote my device's NFC as a smartcard reader from Windows 10.
[Magisk] xanthrax:
Hi and welcome to xda!

Unfortunately this is not the place to find answers for your particular problem, please post on your device forum section questions and answers

Thanks for your cooperation

Dan - forum moderator
[Magisk] Vee89:
Sm-t350 (french guy) unable to reebboot after install magisk modules on stock rom, Fixed by downloaded a new rom

---------- Post added at 02:35 AM ---------- Previous post was at 02:32 AM ----------

Vrt-L09 unable to reeboot after install magisk module on stock and custom rom

---------- Post added at 02:39 AM ---------- Previous post was at 02:35 AM ----------

Me 2 had the same probleme on stock rom but i found that on deoxeded custom rom I works
[Magisk] frankensteinhostage:
:confused:
[Magisk] Legendary Cryptid:
Just checked the log this morning. Should I be worried?
[Magisk] TheFixItMan:
Magisk still can't be flashed via twrp on the Moto G5

Details

Device - Moto G5 Cedric

Rom - LineageOS 14.1

Android version - 7.1.2

Security patch level - 5th August 2017

Attempting to flash magisk v13. 6

TWRP log in attachment
[Magisk] Artim_96:
If you don't have problems ignore logs. And this thread is only when you actually have problems, not to just report logs when you get bored to be told if you actually have problems or not.
[Magisk] Legendary Cryptid:
Well, for one thing, I wasn't bored at all. There were so many commands I thought something might've been wrong.
[Magisk] Artim_96:
I'd guess that your /data partition is formatted with an older version of F2FS which had a bug causing failure of image mounts. You'll most likely have to go to your device thread for that. You should find either a custom kernel with an updated version of F2FS or even a modified version of Magisk that uses the /cache partition instead of /data. For all I know that one is not formatted with F2FS.

---------- Post added at 02:32 PM ---------- Previous post was at 02:31 PM ----------

Still, logs are there of you have problems. If not everything is most likely to work as supposed
[Magisk] TheFixItMan:
Thank you - this makes sense as to why it's not mounting
[Magisk] Demonsannoyed38:
Hello my friend. I'm using the exynos s7 edge with superman rom pre rooted with magisk 13.3 on nougat 7.0. This rom worked fine with safetynet until I installed systemless xposed sdk24. This tripped the safetynet. What process would I use to install a newer version of magisk for it to pass safetynet? Is it not possible for magisk hide to just hide all google apps and xposed, then reboot and find that it passes? I never thought xposed would trip it as its not really changing to much as not fully hooked in to the framework. Please advise my friend.
[Magisk] naboleo:
Surprisingly 13.6 doesn't detect the boot partition correctly (should be sda26) and stops install with error 1, whereas 13.3 installs perfectly....

Found old solution but not sure it's still a valid fix (was for 13.0) https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72784350#post72784350

Log as an attachlent
[Magisk] TheUndertaker21:
hope we get a way to backup our modules sooon

since flashing these things over over after a new flash a pain lol
[Magisk] Artim_96:
... Just backup the image. You only have to install them if you uninstall Magisk.
[Magisk] demonoidmaster:
Anything SafetyNet related don't get answered here. (As noted in the OP)
[Magisk] a-dead-trousers:
Beside of the violation of the forum rules [MENTION=7086291]demonoidmaster[/MENTION] denounced, I think a little bit of help is not a bad thing to do:

Because of its intended usage xposed can't be hidden by magisk. If you want safetynet to be green don't use xposed. There are some modules in the Magisk repositiory which emulate popular features you had with xposed (e.g. Greenify) without the need for xposed.
[Magisk] rignfool:
The last time I tried to do that across different build-keys... I had some error which required me to remove the image and start over...

Have you actually tested... Or is it a theory?
[Magisk] Artim_96:
Well, you basically reinstall Magisk when switching ROM. And no, I don't think I ever tried that with different built-keys. But still, if you get a module, its up file is downloaded to the Magisk Manager folder in internal storage. So just use them to install your modules after New installation of Magisk.

But if you try with copying the image, first name sure the image is in place and then install Magisk so it detects it. That should prevent bugs
[Magisk] LinuxPanda:
In Magisk Manager, Magisk version still shows as v13.3. Neither v13.5 nor v13.6 showed up. So I manually flashed v13.6 but it still shows the latest version as v13.3.

I tried uninstalling using the uninstaller and reinstalling it but still the same. Everything else works fine.

Even module updates (and the entire list) are appearing fine. Please help. Thanks.
[Magisk] DodoGTA:
Well, I see that Magisk v13.6 is installed :)
[Magisk] :
It shows you have 13.6 installed.

The latest stable version is 13.3, that's why it's displayed as latest version.
[Magisk] rogirogi:
You have successfully installed magisk13.6.

It is a normal display.
[Magisk] LinuxPanda:
I do understand that. :D

This is what I was talking about because in some of the screenshots posted earlier in this thread, it shows the latest version as 13.5/13.6 where as for some others like me, it still shows as 13.3.

Do I need to install XDA Labs? :confused:
[Magisk] :
This thread should give you the answer: https://xdaforums.com/apps/magisk/unofficial-magisk-v10-beta-built-t3521901
[Magisk] LinuxPanda:
Please forgive my ignorance as I'm new to Magisk (using it only since v13).

From what I've understand now, only stable builds appear as the latest build in Magisk Manager, so that normal users don't update to beta versions. But at the same time, people like us can install beta versions (not talking about the community builds) released by topjohnwu and just be fine with it.

Thank you very much. :)
[Magisk] :
I am not 100% sure, but I believe that if you install the MagiskManager from the link I posted above, it will display the latest beta build as 'latest version'.

I read this somewhere...
[Magisk] Demonsannoyed38:
No worries my friend. Everything works fine now. Magisk is working fine with xposed and passing safetynet too.
[Magisk] lapapunk:
hi guys!

anybody of you had a problems with titanium-backup? Right after flashing new beta magisk (13.6), tb started crashing, and still crashing even after reinstalling tb. So I wounder where is the reason of this bug? Its because of new magisk or something else?

not the magisk bug! sorry