yashsingh1/xdaforums huggingface dataset:
[Magisk] DiamondJohn:
I have a daily phone running a Lineage based 6.0.1 ROM, init.d does not work on this ROM. I also have a Nexus 5 running Resurrection Remix 7.1.1. Last I checked init.d does not work on that phone either.

I have a LOT of boot scripts, so was very disappointed when init.d did not work, and even tossing up on reverting back to a previous ROM. However, Magisk has its own boot script method. The directory"/magisk/.core/post-fs-data.d" works as init.d without installing any other apps :good:

Now, on my daily ROM I noticed that changing the SELinux to permissive triggered the init.d directory to be processed, so I would guess that a Magisk Module would also enable init.d; personally happy to run with the directory I listed above.
[Magisk] Michele_Catella:
Goodmornign at all!

I have a problem with Magisk on my Gt-i9300 running Cyanogenmod 13 without SU in developer option.

When i intall Magisk, MagiskSU won't prompt request SU access for apps like Boeffla config v2 or Titanium Backup! I have another problem with CST profile! The verification result are failed! How can i repair to this problems? I have installed Magisk on fresh installed ROM, but nothing change! Please help me and the comunity! ?
[Magisk] mobileman88:
deleted
[Magisk] MBariya:
Magisk file not getting installed.

Giving Boot partition insufficient space error.

Any solution ??
[Magisk] dahawthorne:
I'm only guessing here, but it looks as if you have a custom kernel that Magisk doesn't recognise, therefore can't process it, therefore that custom kernel is taking up the space that magisk needs...?

And why are you trying to install 11.6 instead of the new 12?
[Magisk] Tobi@s:
Found the problem:

Sony RIC service stops the /system partition of being mounted RW and prohibits altering the system partition, therefore this step in magic_mask.sh fails:

log_print "* Linking binaries to /sbin"
mount -o rw,remount rootfs /
chmod 755 /sbin
ln -sf $MAGISKBIN/magiskpolicy /sbin/magiskpolicy
ln -sf $MAGISKBIN/magiskpolicy /sbin/sepolicy-inject
ln -sf $MAGISKBIN/resetprop /sbin/resetprop
if [ ! -f /sbin/launch_daemonsu.sh ]; then
log_print "* Starting MagiskSU"
export PATH=$OLDPATH
[B][SIZE="5"] ln -sf $MAGISKBIN/su /sbin/su
ln -sf $MAGISKBIN/magiskpolicy /sbin/supolicy[/SIZE][/B]
/sbin/su --daemon
export PATH=$TOOLPATH:$OLDPATH
fi
mount -o ro,remount rootfs /

To fix this you need to disable Sony RIC service. (for example with [MENTION=357342]tobias.waldvogel[/MENTION] boot.img patcher)

[MENTION=4470081]topjohnwu[/MENTION] don't want to bother you, but maybe thats something you can add in your installation script
[Magisk] BootloopedMillennials:
This app that utilizes init.d is only flashable via TWRP. How would I go about linking it to post-fs-data.d instead?
[Magisk] Romullo Sousa:
I had some problems when I upgraded from 11.0 to 11.6 by the app lol .. my apps started to stop all ... but it was simple thing I think some conflict with the ROM..:silly:
[Magisk] jaysonic88:
Thank you this worked! :good:
[Magisk] kbnsalem:
I've Lost Root when I updated from 11.6 to v 12.

Moto G5 Plus Stock ROM.
[Magisk] lover:
The 0000liveboot file exist and contains these codes:

#!/system/bin/sh
/system/bin/sh /data/user/0/eu.chainfire.liveboot/files/liveboot &

Still doesn't work
[Magisk] mikeyb123:
[MENTION=4470081]topjohnwu[/MENTION]. Thank you so much for the hard work you have put into this, previous 11.6 never worked for me but v12 is working excellent, samsung g920f :)
[Magisk] oakley470:
[MENTION=4667597]Didgeridoohan[/MENTION] I know this is useless without logs and what not but I was posting more just for a general question rather​ than I solution. But in regards to the loss of root on lineage ROMs with BusyBox enabled, [MENTION=4470081]topjohnwu[/MENTION] suggests disabling busybox but I am having the opposite. I run with magisk busybox always enabled and root stays fine. When I enable magiskhide root eventually disappears, if I disable busybox and leave hide on it again eventually disappears. Sometimes it comes back after reboot but most times it requires uninstall magisk and a reinstall to get root back. This is in my n6 with lineage os 3/17/17 build, running Franco r65 kernel and magisk 11.1 with magisksu. No modifications beyond that and it is reproducable every time
[Magisk] neth15:
Just an update: It works, I just had to wait some time (to new SafetyNet check I guess). Thx guys, Magisk's awesome! :good:
[Magisk] kopitalk:
I just did a test and putting a script in /magisk/.core/post-sf-data.d folder is indeed being executed. Try it.

Edit: I just tested again by moving 0000liveboot from init.d to post-sf-data.d folder, and it works.
[Magisk] adewisman:
how are you bro ?
[Magisk] rignfool:
Goddamn...

We're gonna tag some people so my question doesn't get lost...

[MENTION=4667597]Didgeridoohan[/MENTION] [MENTION=1162986]Captain_Throwback[/MENTION]

Wondering if replacing a jar is possible yet... Specifically services.jar

Thanks
[Magisk] chrcol:
i assume when using magisk hide on terminal emulator?

it reports permissive also attaching result of root beer sample

about to test 12.0 since just done nandroid backup but getenforce fails when i cannot su in terminal emulator i need an app to test without root but magisk hide is disabled on it it reports permissive

--update--

After bumping to v12 the dangerous props now passes (I did add safe props to build.prop but I guess that didnt work)

Still failing on root cloak and that final experimental selinux test, getenforce and settings both report selinux as permissive. My only root cloaker is magisk hide.

-- 2nd update --

with xposed disabled safetynet still passes same as v11 however afwall cannot get root permissions anymore which is odd. Lloyds banking app works for the first time in ages, presumably bad props blocked that. barclaycard and myee remain broken as they detecting root somehow (possibly linked to the root cloaker detection in root bear app)

So my 2 lingering issues are root cloaker detection and selinux policy, tkkg the dev of the kernel said its locked to permissive, I guess that lock is also blocking magisk psuedo mode.
[Magisk] biggdevon:
SM-N920T

arter97's kernel

Stock 6.0.1 PK6

Was passing all checks with v11.6 but v12 fails profile. Basic integrity is true, selinux and Knox shows enforcing/0x0.
[Magisk] ps3hacker3:
The latest version 11.6 has basically rendered my device semi bricked until get back home (HTC One a9) with the update I have lost root access and I cannot boot into twrp or download mode under any circumstances (refuses to boot into either with the normal key trick on bootup) if anyone has any ideas on how to get back to 11.6 I'm all ears because it was working perfectly...
[Magisk] khangcobra:
I use custom rom :D dont like Miui :>
[Magisk] MBariya:
Giving error in both v12 and v11.6.

Anyway to increase space for boot partition??
[Magisk] dahawthorne:
I would never even try to mess with my partitions, particularly the boot. If I were in your position, I would first try flashing the ROM's own boot, and then try Magisk again.
[Magisk] einhuman197:
Hi,

Is there a way to use liveboot or an alternative with magisk? I tried magisk with the init.d plugin but it doesn't show the log on boot. Thanks in advance.
[Magisk] Didgeridoohan:
It's in /system/framework, right? Using a Magisk module to replace it with a modified version shouldn't be a problem then... If it'll work? I've no idea... That's outside my skill set.

---------- Post added at 16:37 ---------- Previous post was at 16:34 ----------

No... Don't put terminal on the Hide list! That'll cripple it and has nothing to do with checking prop values and SELinux state.

Run setenforce 1 in terminal as su (sets SELinux to enforcing) and see what happens.
[Magisk] rignfool:
I'm hesitant to try it because I currently don't have volume buttons or power so I can't recover a bootloop...

I did at one point try manually making an ARISE module and it would always error when I added the jar files...
[Magisk] chrcol:
I already did that last time, its locked to permissive. Also see my 2 updates to the post, tkkg wont allow enforcing on the kernel.

I already know the actual mode cannot be changed to restricted, but I thought magisk masked it and pretends its set to enforcing?

https://xdaforums.com/showpost.php?p=71572181&postcount=8
[Magisk] EpicLPer:
So all old modules were removed even tho the one I used was still working, thanks a ton... not...
[Magisk] Didgeridoohan:
Hide should do it's pseudo-enforcing thing... What does your Magisk log state about it?
[Magisk] phuhcue:
Same device here. Same kernel though I'm using darkstalker v11. Everything works fine on 11.1 but nothing after that works at all, no root etc.

Did you do anything other than update through the manager for 11.6 to work for you?
[Magisk] lover:
Yes it works but for some reasons my boot is longer and every time it wants to update my apps (two spinning gears) so for now i give up liveboot and wait for its proper Magisk Module
[Magisk] Didgeridoohan:
You can still install them manually... They'll just not show up in the repo. [MENTION=4470081]topjohnwu[/MENTION] need to have some kind of protection against outdated modules causing issues.
[Magisk] chrcol:
Says this

"permissive detected"

"Unable to set enforce, hide the state"
[Magisk] JudgeDread11:
Why not use phh's superuser?

You could always make your own module. ;)
[Magisk] bigknowz:
2nd try

Yes, guy had me try two times, now I know why.
[Magisk] Nodens:
Because of a colleague's clever idea to hard depend on SuperSu and their reluctance to support phh because "it involves extra work for a project that may or may not stick around". They also could not care any less

that I want to run systemless xposed among other things on my device heh. I'm using two custom in-house applications related to source code version control that depend on SuperSu..

As much as I'd love to contribute to the community by making my own module and publish it, I am currently drowning with work, actively developing and maintaining 4 C++ x86/x64 projects (2 of them being Windows+Linux cross-platform) and a Windows dll project that I will soon release as open source. I have literally 0 time available to take up any extra work :(
[Magisk] AndroidGee209:
So has anybody else had an issue with the camera not working anymore after installing Magisk ?
[Magisk] Tipika:
No, my camera is still working

Inviato dal mio Nexus 5X utilizzando Tapatalk
[Magisk] chazall1:
No, my camera is still working
[Magisk] CHAMAVELI:
My "module" is no longer working and nothing has changed. It is a cache mod running post-fs.sh containing setprop just like in the first post to change DPI.

I can see the script being run in the logs but DPI isn't taking effect.

Like I said, nothing has changed on my device. It was working when Magisk was first installed.
[Magisk] Artim_96:
Oh, that sounds really nice. So it will be kind of like flashfire without the need of SuperSU? And will that be only for Magisk itself or for modules too?
[Magisk] lainataprudnqta:
" Remove ANY kind of root (SuperSU, phh's su, KingRoot...); Remove v85.x Systemless Xposed by me, romracer's Systemless Xposed, official system Xposed by reverting to stock boot image or use uninstallers. Please make sure to remove included root COMPLETELY (/system/xbin/su, /data/su.img, /sbin/su etc. "

Should have read more carefully ... i think I bricked my Z3C :D
[Magisk] hua_wuxin:
EDIT: It found to be that folders with new file(s) inside will get wrong permission after "Auto Mount".

I added new file(s) to /system/fonts, /system/media/audio/notifications and /system/media/audio/ringtones, all these 3 folders are having wrong permission.

ORIGINAL:

I made a simple system patch based on Magisk-module-template.zip, and found

Magisk v6 is not handling permission for the /system/fonts folder properly, which makes Samsung stock Contacts app FC (due to unable to access SamsungSans-Num3L.ttf within this folder).

Please see attached image for details. Thanks.
[Magisk] AndroidGee209:
Are you supposed to flash the template? Could that be the reason my camera fc?
[Magisk] gohamstergo:
No.......it's a TEMPLATE for people to use as a starting point to develop modules.......
[Magisk] Fedroid:
Ok, finally running fine.

I am on Huawei P8 Lite with marshmallow on custom Rom.

Perfect! Now bankinter payment app works fine because thinks I an no rooted.

Phh su. Live boot, busybox, viper4android and xposed working a full
[Magisk] JudgeDread11:
Are all the files still in place? I had it because SD maid cleaned the cache and deleted some files.

In that case if you use any cleaning app make sure you whitelist the /cache/magisk folder.

If it everything is in place check if it all has the right permissions set.

---------- Post added at 02:12 AM ---------- Previous post was at 02:10 AM ----------

You can set the permissions to use on the template.
[Magisk] CrazyCypher:
Hy guys, could you point me in the right direction... I want to "delete" apps from system/app and system/priv-app. Especially apps like UDove and RootPA.

So I create a folder inside Magisk folder and give it a name. I gave name "RemoveSystemApps", so now I open this folder and inside I make directories system/priv-app/RootPA and system/app/UDove where RootPA and UDove are empty folders. After that I put .replace file inside "RemoveSystemApps" folder and reboot, this should be OK or should I do something different?
[Magisk] JudgeDread11:
In the collection of magisk modules thread is a mod I created to do the same thing. It's called de-bloat mod.

You can use it as an example.

You don't need to create all the folders, just add then to the replace.txt file. Magisk will then create them when you flash the mod.
[Magisk] mati_boy:
the .replace file should be in RootPA and UDove folders and you should add an empty 'auto_mount' file in RemoveSystemApps. I don't think it's already necessary for this version but most of the modules also have a module.prop file, just find that file from another mod and edit with a text editor.
[Magisk] CrazyCypher:
I cant seem to find it, could you link it to me please? I appreciate it.
[Magisk] JudgeDread11:
http://xdaforums.com/android/software/collection-magisk-modules-t3445257/page6
[Magisk] CrazyCypher:
Thank you, I will try it as soon as I can :)
[Magisk] kopitalk:
I have none if what you're experiencing. Anyway ymmv.
[Magisk] Didgeridoohan:
Yeah... Probably your kernel then... Time to change?
[Magisk] chrcol:
I can flash stock kernel see if fixes barclaycard and myee, if it doesnt switch back afterwards. The stock kernel is a lot more limited tho I cannot tune a lot of stuff so I dont want to use it.
[Magisk] Didgeridoohan:
Time for a new device, maybe? I threw out my Nexus 6 yesterday in favour of a OnePlus 3T. I liked the N6, but after one day with this baby, I'm not gonna look back...
[Magisk] Captain_Throwback:
That's always been possible...
[Magisk] epickid37:
When I try to install v12.0 it says that it succeed and asks me if I want to reboot, when I do, it tells me that I need to update because I'm still on 11 (I have tried this more than once)
[Magisk] MBariya:
Custom kernel should not be any problem..

I am using Magisk since v8..

But is giving error from v11.6+.
[Magisk] Citizen_Snips:
Just chiming in to say all is well on Magisk v12. No issues losing root. MagiskHide works perfect. Passing SafetyNet. All my root apps work. Webview works. Nexus 6P on March security update.

Thanks!
[Magisk] tamer7:
All of the props you mentioned in your troubleshooting thread are fine by default. The only one I had to change was ro.build.selinux to set it to 0 manually

However, S-PushTAN 1.0.11 (previous to latest version) which was working with Magisk v11.6 is now saying it detects root with v12, despite Rootbeer finding no trace of root and all its checks pass, and of course both safetynet checks also pass.

Any other ideas?
[Magisk] sugigu:
Titanium Backup and CTS mismatch after v12

del
[Magisk] DallasBelt:
In v11.6 I had a module to change the stock emojis to Emoji One. It's still working with v12 but no longer displayed in Magisk as installed (or in Downloads). Could be the module itself that has to be updated? Thanks!
[Magisk] rignfool:
The buttons work... I just can't reconnect the ribbon cable... My meathook hands aren't delicate enough for the operation required
[Magisk] Citizen_Snips:
The change log for v12 said all outdated modules would be hidden and only modules using the v3 template would be shown.

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445/page2
[Magisk] biggdevon:
Nothing special. Updated through the app but manually rebooted because the app did not.
[Magisk] quorn23:
May I ask which business solution you're referring to? :)
[Magisk] teddy0209:
I'm ok mate...?
[Magisk] DallasBelt:
Thanks! Yes, I read that just after posting my question. Sorry for that.
[Magisk] dahawthorne:
But since Magisk tinkers with the bootloader, perhaps something has become corrupt. If you use TWRP to erase the boot partition and then flash your boot again, Magisk will have a clean boot to work with. I can't think of anything else that would suddenly make your boot partition too small.
[Magisk] MBariya:
Ok

Problem was with my custom kernel.

Kernel was permissive, which was creating problem.

Flashed enforced kernel..now working ok.

But...all module dev need to update Magisk Module..

Not even single module available for v12 as per new change log.

[emoji27]
[Magisk] dahawthorne:
You're welcome... :)
[Magisk] android_htc:
Yes, finally.. Magisk v12 now installs on my stock Samsung kernel (Note 4) and passes SafetyNet (Android pay also works, see why I make this comment below) :victory:

However, initially updated Magisk on my Permissive custom kernel, SafetyNet did turn green. But, Android pay detected root when I tried to tap in at the train station... I had to remove Magisk and install stock kernel as I would have missed two trains, lol. Will test again.

Thanks for the support on the Samsung devices.
[Magisk] chrcol:
seems every kernel made for the 930F is permissive mode locked, except of course for the bog standard samsung one.

Also remembering both apps work when magisk is uninstalled, is perhaps not pointing to selinux but rather that magisk is detectable on my device (somehow root beer sample detects the root cloaking.

I wish that root beer app would show how it detected but it does not.
[Magisk] Garock:
I've read all these Magisk threads numerous times already and still fail to understand what exactly do I need to do

Here's my setup, Pixel C tablet, Android 7.0, rooted with SuperSU. not sure systemless or not, people keeps saying magisk manager will tell you which one I'm using but apparently there is nothing in the manager to see that

I have "Properly rooted 2.79:SUPERSU" in the status screen but that's about it

Then I installed Magisk, reboot, and the manager now shows "Installed Magisk v12.0", but the root status still "Properly rooted 2.79:SUPERSU"

SafetyNet check also still failing

So how do I replace SuperSU with MagiskSU now?

I've read some reports that simply flashing Magisk zip file will end in soft brick, so I need to full unroot first before attempt to reinstall Magisk, but I have my doubts on this. Anyone can support this claim?

Also why did it keep using SuperSU after I installed Magisk? Shouldn't it be replaced with magisk automatically?

If anyone can give me step by step on what I need to do, it would be very helpful
[Magisk] Artim_96:
Unsu.zip by Osmosis...
[Magisk] Karls0:
Again md5: 1EC332817B86F276F5E4BC5E144C7049

Is it correct md5 hash for Magisk v12.0?
[Magisk] tamer7:
That indicates a regression in v12 because in v11.6 setting pseudo-enforced mode was hiding permissive selinux status successfully for all MagiskHide-listed apps.

I will try to confirm

Edit: I tried but could not reproduce.
[Magisk] ghbuur:
it's called "good for enterprise". in play store, similar to airwatch. on rooted devices not possible without xposed module until now ;)
[Magisk] neth15:
With Magisk v12 phone won't enter deep sleep mode (Active time in battery graph is full). Restored to same configuration with v11.6 and everything's fine.
[Magisk] baybephace:
Nexus 10 - Can't restore MagiskSU root after updating to v12.0

Previously I successfully installed Magisk v11.6 on the following three disparate device setups:

OnePlus One (bacon) - CyanogenOS 13.1.2 (6.0.1)

Nexus 9 (volantis) - Factory Image 7.1.1

Nexus 10 - LineageOS 13.0 (6.0.1)

I enabled MagiskSU, Magisk Hide and Busybox on all 3, selected no individual apps, and SafetyNet also passed on all 3.

I then recently attempted to upgrade to Magisk v12.0 through Magisk Manager, which was successful on the OPO and Nexus 9 (other than having to manually reboot).

On the Nexus 10 however, while the installation was successful (at least according to Magisk Manager) I had lost root.

I tried the Magisk Uninstaller route, then manually flashing the stock boot image route, then flashing back to Magisk v11.6.

In all cases, root never returned.

I understand there are potential issues between LineageOS and busybox. Unfortunately, seemingly due to lack of root, the "Magisk" and "Superuser" sections of the Settings do not show up, so I can't perform the suggested solution of "disabl[ing] busybox in MagiskManager".

Is there any way to manually disable busybox (assuming this is the issue) via the command line? I dug around via recovery but nothing jumped out at me. I also tried completely uninstalling Magisk Manager and reinstalled from the stub hoping it would clear the options to no avail.
[Magisk] dahawthorne:
I wondered about the N10 as well. I reckon that Magisk doesn't work because there is no suitable Magisk boot image for it. There is a comment I read that if your device is not on the list (and I don't know where any list exists) then you have to upload your boot image for the required Magisk work to be done. Given the age of the N10 I didn't think it was worth bothering the dev.
[Magisk] drewski_1:
Or full unroot in Super SU app
[Magisk] RagingHarry:
Just went ahead to try v12 (11.1 & 11.6 worked properly) on my OP3 & Galaxy Tab S2 2016, and everything installed just fine.

SuHide works correctly and both pass the safetynet check.

Thnx for the update!!
[Magisk] Thomas_BA:
So, just to verify..

I updated to Magisk 12, everything running smoothly, SuperSU was disabled during install of Magisk (asking for binaries if I launch it)

So should I do a full unroot from inside SuperSU (systemless) if I want to get rid of it? Won't affect root which is given in the moment by MagicSu and the functionality of the xposed module by Magic?

P. S. Just saw that I can't do a full un root from inside Supersu as it is disabled. So how to proceed. Simple un install?
[Magisk] chjun90:
why does resetprop hasn't effect on my oneplus3. i write "resetprop -n persist.sys.oem.region CN" on post-fs-data.sh and see it has been executed. but nothing happen.
[Magisk] baybephace:
Fair enough. I thought it was working perfectly fine with Magisk v11.6, but as you said, the device is rather old and I don't use it as my primary tablet, so perhaps it only appeared to work the first time I installed it. Going back to v11.6 after restoring factory boot.img doesn't work now, so maybe I was imagining things.

Edit: spelling
[Magisk] dahawthorne:
I'm afraid you are, because I tried 11.6 and it refused to work. I spent an hour looking for anyone who had Magisk on an N10 - there are none (that I could find).
[Magisk] jasio2k:
Hi

On Htc one m8 RR 5.8.2, magisk 12.0 problem with disappearing root still persists :( but fauxsound is working again thx

Here is log

https://drive.google.com/file/d/0B2SG1vOm1yHmRUNFcFczdFdaRnM/view?usp=drivesdk