yashsingh1/xdaforums huggingface dataset:
[Magisk] Johnmy212i:
lol. Of course you can, I'm using s6 flat. Just use root explorer or anything else then change the permission, enforce to 640 and policy to 440.

More info, look at [MENTION=4667597]Didgeridoohan[/MENTION] post above and click the link.
[Magisk] SuperSandro2000:
Boot times went insane with the 22 build. Bootloader/kernel time is now almost at stock and bootanimation is as fast as always.
[Magisk] KatariaMax:
Hello new 322 version also causes loss of root like 11.5 and 11.6
[Magisk] KatariaMax:
Thanks for 327 build lost root issues fixed[emoji106] [emoji106] [emoji106]

---------- Post added at 07:02 AM ---------- Previous post was at 07:02 AM ----------

For Samsung devices
[Magisk] a-dead-trousers:
Same here on SM-G800F :victory:
[Magisk] Artim_96:
Ok, now SELinux is detected as enforcing again, even though the settings still say permissive:good:
[Magisk] Chiyo-chan:
Exactly the contrary on a OnePlus 2: I didn't lose root for days with the previous version while 327 only last a couple of hours...

Envoyé de mon ONE A2003 en utilisant Tapatalk
[Magisk] stangri:
When you say "lost root" do you mean Magisk Manager is not detecting your phone being rooted or other apps?
[Magisk] Chiyo-chan:
I meant Magisk and all other apps.

Envoyé de mon ONE A2003 en utilisant Tapatalk
[Magisk] LikeATrollFace:
Still getting that safety net mismatch...

I'm running lineage OS nougat on my sm-g920f and for some reason when changing the selinux to enforcing it changes back to permissive the same second.. https://imgur.com/BiY7yUP

---------- Post added at 10:49 PM ---------- Previous post was at 10:48 PM ----------

Here are some other pics for reference.

https://imgur.com/a/CcOc4
[Magisk] Artim_96:
For SELinux, don't rely on what the settings tell you. Open a terminal emulator with root and enter "getenforce". If it returns enforcing everything is fine.

But for SN it can be impossible to pass on your configuration. Had over to the official thread, a link with tips was posted often enough to find it.

I only remember that someone find a way to modify the system in a way that some devices can pass which wouldn't pass before. But before we can say anything he needs to send a pull request for his code on GitHub to topjohnwu and he would need to implement it. So maybe with the next big update there could be more devices passing SN
[Magisk] LikeATrollFace:
Getenforce does tell me permissive sadly :/
[Magisk] Artim_96:
Strange... I had that problem with v11.5/11.6, but not anymore on this beta.

Maybe you should make a fresh install, so just flash your stock boot.img and Magisk beta afterwards. That's what I did when I switched from 11.6 back to beta.
[Magisk] biggdevon:
Anyone have an idea as to why RootBeer app detects "Root Cloaking app" on v5(322) but not with the v4.2.7? SafteyNet still passes but other apps that look for more specific things might have issues (banking apps in particular).

SM-N920T Magisk v12(328/v5(322)

Edit: Apparently RootBeer app has been recently updated and is now detecting Magisk mgr.
[Magisk] Artim_96:
Not for me. Still only detects the last experimental entry. On v328 and latest version of RootBeer
[Magisk] biggdevon:
I was on v11.6/4.2.7 with the same as you and correcting with resetprop command for ro.build.selinux. Chose to give v12 a run now RootBeer detects the bottom two. Even after using the uninstaller and re-installing v11.6
[Magisk] lkbfreak:
Hi all! I have a rom that includes Magisk and Magisk manager. I also successfully updated to Magisk v12 snapshot but can't install Magisk manager v5 over Magisk manager v4.2.7 (App not installed. The package conflicts with an existing package by the same name). Any help dealing with Manager installation would be greatly appreciated! Thanx!
[Magisk] davall:
Deinstallation of old Magisk manager and afterwards installing the new manager will do it ;)
[Magisk] Artim_96:
You shouldn't need to set those props anymore, Magisk now does it itself. Maybe that's what's interfering
[Magisk] biggdevon:
I'm pretty sure it's because I'm using a Samsung device. Everything functions pretty well regardless of reseting the ro.build.selinux value but I like to cover all aspects as I have yet to successfully use Android Pay while rooted. But the quest continues.
[Magisk] stangri:
Thanks for bringing this up, I've had instructions that uninstall of the release Magisk Manager is required before, but then I cleaned up the first post of the thread and accidentally removed them. I've added these instructions back.
[Magisk] a-dead-trousers:
FYI: MagiskManager not being built automatically

Hi!

Despite the fact that there are new commits for MagiskManager no new daily builds are being offered on https://github.com/stangri/MagiskFiles

Wkr

ADT
[Magisk] djb77:
Just a heads up that the official Magisk v12 is now released.
[Magisk] ddimple4:
To what degree do the snapshot builds and the unofficial manager app reflect the official changes?

V12 was released on after/before the 330 build?

Which is "more" up to date?
[Magisk] Julian CM Kwan:
Installed Magisk Manager from Play store but can't update and install Magisk v12 zip file within the app. I need to download the ZIP from threads and flashing it through TWRP recovery.

Booted with no issue but I can't pass Safety Check in Magisk Manager with my Samsung note 3 hlte rooted properly.

Any ideas from you guys out there?

Thanking in advance for any kind and prompt advice.
[Magisk] Artim_96:
Head over to to official thread, there are links to a help thread where you can find possible solutions
[Magisk] stangri:
Thanks for your post, I just ran the build script manually and it worked fine. Do report if the snapshots fail to build automatically from now on.
[Magisk] wogooo:
what does this app do?
[Magisk] Artim_96:
1. This is not a app

2. Read the official Magisk thread and use that. Come back when you know enough about it.
[Magisk] wogooo:
its some sort of xposed?
[Magisk] Artim_96:
No, not at all. Like I said, read the official thread and cone back if you know enough. That means that your actually used the official version. This is only s beta
[Magisk] jhedfors:
OMG. What about number 2 is not clear? Are you trolling?
[Magisk] wogooo:
Look, not everybody here is a total geek. Number 2 was absolutely clear and i even did it. My conclusion was that this is some sort of xposed-thing, which turned out not te be true. I'm very sorry for this.
[Magisk] Captain_Throwback:
Maybe you need to read up on what Xposed is too, then...
[Magisk] wogooo:
:cowboy:
[Magisk] :
The Snapshot released before where easy to install by just uninstall magisk and install snapshot build but i am little lost now how to install them bcz i have leaved snapshots for some times I am bit confused readed previous posts now there is auto-update module plz some one assist me how to install latest snapshots plz?????? is the method same or changed
[Magisk] Artim_96:
...just get the newest manger. If that's not telling you that there is a new version of Magisk just get the zip and flash it yourself. What's the problem with that?
[Magisk] kimikim0:
im new with this unofficial thing, my question is how stable is this snapshot than the official build ?
[Magisk] Didgeridoohan:
At the moment there's no difference since nothings been added to GitHub since the last official release (v12). When there's a beta snapshot available that has new code, it might be stable or it might be unusable. That's the nature of an unofficial beta snapshot...
[Magisk] oreo27:
Thanks! Hope you can keep this updated while we're all waiting for the official release. :)
[Magisk] Didgeridoohan:
No worries. I don't think anyone here thinks you're a dumb person. But, you did make it sound like you're using Magisk Hide to hide SuperSU, which you're not... As already stated though, the synergy effects are quite interesting.
[Magisk] oreo27:
So I just built a snapshot myself for Magisk dated today and noticed some things:

/cache/magisk_mount/ seems like it isn't being read.

Root seems to have been lost

Xposed doesn't seem to work

I had to reflash SuperSU then Magisk V9 again to get it back up and running.

This all happened after I updated my personal module which only added a file to system/etc and is working with v9.
[Magisk] stangri:
Weird, it's smooth sailing for me. Maybe something's wrong with your module/template you've used for it.

PS. I've uploaded 16'12'23 builds for Magisk and MagiskManager, links are in first post.
[Magisk] oreo27:
Perhaps I built Magisk incorrectly because I didn't change anything in my module. Is there a new template that I should be using? I checked the template in Github and it seems like the last commit was November 15.
[Magisk] stangri:
AFAIK the current one was released together with magisk v9. I was just making sure you're using it.
[Magisk] oreo27:
Yup. Definitely using that template. You could check my mod here - https://github.com/0reo27/oreo27-Mods-for-MIUI8 - It's barely working at this state since right now I'm uploading all my mods to cache/magisk_mount. I just found it easier for testing. No zipping of files and installing through Magisk Manager. It's just upload and reboot.
[Magisk] nimjk:
Bump doesn't work in my LG-F400S (lg g3 korea). You should check this problem.
[Magisk] JEANRIVERA:
Could you build magisk manager with yesterday's commits please they look really interesting....
[Magisk] stangri:
I just did, but couldn't get the new app to start without crashing on two nougat devices I have. The new apk is in the first post.
[Magisk] JEANRIVERA:
I'll test and report back thanks!!

yes same issue here!!! :crying:
[Magisk] jsaxon2:
I built this and it has the new SafetyNeet Check. It is working for me on HTC 10 Viper N rom with Magisk v9.1. Maybe it is the Magisk v10 beta that is the problem. Here is my build that is working for me. https://drive.google.com/open?id=0B1iRsZPFZo3EWktDTGZhQ3d1aHM

Edit, I downloaded your version from the first post and it did not work. I reinstalled mine and it is working again. Must be something messed up with your build.

Mine was just sync'd and build about an hour ago with all the latest changes.
[Magisk] JEANRIVERA:
Your version is working fine for me thanks I do have magisk v10 beta
[Magisk] stangri:
Hey Jason, thanks for sharing your build. I've tried again with freshly cloned repo and still can't get the app to start (neither debug, nor release).

Did you build from master branch? Did you build from CLI or from the Studio?

PS. I'm using the keys from main/assets to sign, which keys are you using?
[Magisk] jsaxon2:
I wish I could help more, but I am a novice. All I did was clone the repo, open in Android Studio on Windows 10 and build the apk, the generate signed apk using my own key. I was getting errors when I tried to clone the repo into the old MagiskManager folder I had, so I cloned it to a different folder using GitHub for Desktop app.
[Magisk] stangri:
Weird, with both CLI and GUI builds on Mac I can't get the resulting apk to run without crashing. :( Maybe something's amiss in my SDK/NDK setup, but it did build just fine 3 days ago.

I'm also struggling with MagiskHide. After I enable MagiskHide and reboot I lose root right from the get-go. The only way to get it back is to uninstall Magisk and then reinstall it.
[Magisk] stangri:
Scratch that, the GUI-built file is fine, don't know howcome it's built broken from CLI. :(
[Magisk] Didgeridoohan:
Does this happen with Manager v2.5 as well? Your Magisk v10 snapshot with Manager v2.5 works flawlessly for me. Magisk Hide has been working almost perfect from the get go. Passing Safety Net and everything... I could never pass Safety Net on v9 or your earlier snapshot. The commit to move sbin binaries seems to have done some magic.

On v9 I lost root as soon as I opened a root detecting app while Magisk Hide was enabled. I also lost root sometimes on a reboot, having to do multiple reboots to bring it back.

The only snafu I experienced with your snapshot was that my nightly run of Titanium Backup seemed to disable root. I haven't tested that to any extent, but after excluding the Magisk Manager from the backup all's fine.
[Magisk] stangri:
You know what, it's too painful to recover if it does, so I made my peace with living without magisk hide for now. ;)
[Magisk] mrxtc89117:
Does Magisk v10 fix MagiskHide losng root randomly?
[Magisk] :
Got it thnx
[Magisk] dahawthorne:
Sorry if this is a stupid question, but if v13 is the same as v12, why does this thread exist?
[Magisk] Artim_96:
It is at the moment. But since there already was another update it isn't anymore. Now it's the 13 beta. That's what this thread is obviously for
[Magisk] Ardany Jolón:
What is the changelog for the snapshot versions?

Sorry for my bad English ???
[Magisk] Didgeridoohan:
GitHub. There are links to the commit logs in the OP.
[Magisk] Ardany Jolón:
Thanks ???
[Magisk] Didgeridoohan:
The moment passed...
[Magisk] JonathanRAZ:
Official magisk v12

1-arte97 kernel n920t v22.0

2-Unsu

3-flashed v12 magisk

4-reboot to system

No root

Unofficial magisk v13

1-arte97 kernel n920t v22.0

2-Unsu

3-flashed v13 magisk

4-reboot to system

Everything works

Thanks for the magisk v13 170405
[Magisk] Tyrannis78:
Yes, Magisk 13 work perfect for me too, 12 fail a lot.

Enviado desde mi Note 7
[Magisk] Shadowghoster:
There is only one (maybe two) more commits in the latest v13 build compared to official Magisk v12, but the latest fixes some selinux things so maybe that fixed your problems.

Gesendet von meinem A0001 mit Tapatalk
[Magisk] dahawthorne:
And I can guess what happened during that moment. Thanks for counting to ten and not giving me both barrels... :)

Sorry, it was a genuine question, not smartassedness, just badly phrased. Since your previous comment said "At the moment there's no difference", I was puzzled. I'm just not clear why we have a separate strain of Magisk going on when topjohnwu continues to work on Magisk.
[Magisk] Didgeridoohan:
At the time of writing that comment, there really wasn't difference. Shortly after (only a few hours, I believe) there was a commit submitted to GitHub. That apparently has fixed a few issues. :good:

This thread is for the ones that wan't to try bleeding edge, but doesn't have the time/skill to build their own version from the code on GitHub. All the code is from [MENTION=4470081]topjohnwu[/MENTION], but this version is built by [MENTION=2226076]stangri[/MENTION].
[Magisk] biggdevon:
I want able to get v12 working with a custom kernel (arter97's v22) but stock kernel worked fine. No issues with v13 with stock kernel either.
[Magisk] JonathanRAZ:
What version are you on? Dqa2? I cant get it to work with stock boot only works with arter kernel on dqa2
[Magisk] biggdevon:
I'm still on PK6. I did have issues with QA2 and flashing root in general so I downgraded. Never bothered to look into what QA2 update was, just downgraded and haven't looked back.
[Magisk] JonathanRAZ:
Ok sir thanks maybe will try with the boot.img from pk6 and see what happens
[Magisk] medes22:
Latest manager and Magisk installed

Why isn't it starting?

Can't check sfatynet

Gives just cts fail

But it doesn't start the program
[Magisk] medes22:
The version numbera
[Magisk] kyzn:
Have you tried turning off Magisk Hide rebooting and then turning it on again?

(I'm not saying whatever fixed Samsung devices broke something for the rest but...Magisk Hide now only works for me after every other reboot. :silly: )

SafetyNet fails the same way on both the official and this version for me. And fixes itself some time after a couple of reboots.
[Magisk] medes22:
That did the trick thank you Sir
[Magisk] stangri:
UPDATES:

Apr'16: Thanks to a tip from [MENTION=4667597]Didgeridoohan[/MENTION] -- I've set up Magisk builds to also track the new unify_daemon branch (Magisk-UD-v13-*), current build on master branch fails.

Apr'16: Magisk Manager build fails ever since [MENTION=4470081]topjohnwu[/MENTION] switched to Android Studio 2.4 which supports Android O tools. I've installed the same build_tools as required by the app, but get a bunch of APPT complaints on missing resource identifiers so ':app:processDebugResources' task fails. I suspect I'm missing some gradle command in the build process, but don't know which one.

I haven't had much time to look after the build process lately, so if anyone wants to take over and/or gain access to publish to this repo, let me know. Current build script supports building on macOS/Linux.
[Magisk] doomscooter:
Magisk v13-170415 right?
[Magisk] stangri:
No, Magisk-UD-v13-* files. The current one is https://github.com/stangri/MagiskFiles/blob/master/Magisk-UD-v13-170416.zip

If it proves stable, [MENTION=4476591]Deic[/MENTION] might want to change his update tracker to that branch as well.
[Magisk] SuperSandro2000:
Did topjohnwu not fix losing root? I am currently running aicp on my s5 and it comes preloaded with magisk. I do not lose su with the preloaded version. But as soon as I update magisk I am starting to loose su again randomly. Anyone knows something about that?
[Magisk] medes22:
So anyone flashed the unified zip?

How is it?
[Magisk] Didgeridoohan:
Certain ROMs have been known to have a losing root issue with Magisk busybox enabled. Since you're posting in the snapshot thread I'm assuming you've tried the latest snapshots. There was a new one built today. Try that... No guarantees whatsoever. :p
[Magisk] SuperSandro2000:
I only lose root with the magisk framework snapshots. If I use the version that aicp provides I do not loose root. I have the exact same settings and the same companion app version. Could it woke if I replace the zip inside the aicp zip?

Other question: sometimes when I open the app it shows that I lost root and has the light theme. (Using normaly dark theme) then I close it and open it again and everything is back to normal. Is this a know bug?
[Magisk] Didgeridoohan:
ROM with built-in Magisk is out of my zone. I only ever use ROMs with no built-in root solution.

Aggressive battery optimisation, maybe?
[Magisk] SuperSandro2000:
Aicp ist the only daily or weekly build Rom that is feature rich for my device. I try to replace the zip file inside the room zip.

Good idea. I try that. Thanks for you help.
[Magisk] Artim_96:
Does not create Magisk.img or detect existing one
[Magisk] jsaxon2:
Correct. Currently the lines for magisk are commented out on GitHub. You will have root, but no magisk. I would not bother flashing till topjohn has more time. This is not a bug, he commented out the lines for a reason. I do not know the reason, but I'll patiently wait.
[Magisk] wrongway213:
Thanks for explaining this - I was trying to look thru the log for errors and such, didn't even hit me to check the actual code :p
[Magisk] medes22:
And how is the unify_deamon Magisk working for you all?
[Magisk] Artim_96:
Not
[Magisk] Mezabaru:
Latest one root worked but nothing else. I had run yds busybody cleaner and unsu then flashed latest yds busybox from github latest none UD magisk then UD magisk 17. Interested when a more useable build comes out.
[Magisk] WoodpeckerS:
UD170417 did not work (no Magisk, no root) on my setup so I had to revert to 150417. However I cannot get into Superuser anymore. Then Magisk Manager 170331 closes. The same happens when an app are using - and getting root access - and works. Then Magisk Manager stops and obviously reinitiates again.
[Magisk] tuckandroll:
i am also having this issue is there a fix for this?
[Magisk] Mezabaru:
As it's an unofficial build we just have to wait an hope :).
[Magisk] Artim_96:
If it doesn't stick with busybox disabled, then not
[Magisk] tuckandroll:
I'm on version 12 I thought that was official...
[Magisk] Didgeridoohan:
In that case you're in the wrong thread... :D
[Magisk] dacorsa:
Thanks for all yours works !!!
[Magisk] Pekempy:
Any idea how to get Magisk + Root working on O? I thought 13 might have magisk for O and it works, but i cant get it to work with root (SuperSU 2.79 SR4)
[Magisk] Didgeridoohan:
Wait until there's a new release (either official or possibly a snapshot). The current working snapshot doesn't have any interesting changes from v12.

There was a LOT of commits pushed to the master branch today and we know that [MENTION=4470081]topjohnwu[/MENTION] have had his N5X with O preview running Magisk. https://xdaforums.com/showpost.php?p=71876014&postcount=12268
[Magisk] FeelThePoveR:
He just pushed commits from the unify branch to the master branch and deleted unify branch.
[Magisk] Didgeridoohan:
Uhm... Yes. :confused:
[Magisk] FeelThePoveR:
So all these 'new' commits aren't really new and latest snapshot is up to date or almost up to date as it was based on the now deleted unify_deamon branch.
[Magisk] Didgeridoohan:
Now I understand the confusion. New to the master branch... I was unclear. Thank you for clearing that up.

From reports in this thread, the latest snapshots based on the unify branch are not usable.

Edit: well, actually... Rereading my earlier post, I didn't write anything about "new" commits. But anyway...
[Magisk] FeelThePoveR:
Yeah what confused me was that you said that there weren't any interesting changes from v12 whereas there were lots of them just maybe not working on the snapshot (I'm still on the v12, but I track progress on the v13). Anyway good that's cleared up. :)
[Magisk] Mezabaru:
he just pushed commits, Magisk manager built, I'll edit with results in a few minutes.

Nothing with latest commits of Magisk, though no issues with latest commits on Magisk manager.

I attached the Magisk Manager I built if anyone is interested.

Edit; Stangri uploaded to his repo removing the APK to avoid confusion.
[Magisk] DodoGTA:
I recently built Magisk and Magisk uninstaller with the latest commits from master branch of Magisk :)
[Magisk] Artim_96:
Well, are they working?
[Magisk] DodoGTA:
They're untested (because I don't have my phone right now)
[Magisk] Mezabaru:
Same as my build not working, atleast I haven't had anything weird happening with magisk manager on Samsung s7
[Magisk] android_htc:
This version of Magisk does not install on my Samsung Note 4
[Magisk] stangri:
[MENTION=6429309]DodoGTA[/MENTION] aciu! (is that how it's spelled ;))?

I've edited my build script to work with the most recent [MENTION=4470081]topjohnwu[/MENTION] changes, so at least today, both Magisk and Magisk Manager built.
[Magisk] 13680201:
HI win click download and install in magsik manager, download file but show file install.

Please help for install magsik.zip file

Thanks

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] teddy0209:
Go back to 0415 version for now, the 0424 version does not install properly...
[Magisk] 13680201:
How do I install it?

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] Jenanga:
Really, this question?
[Magisk] 13680201:
How install v.415 in magsik manager v.424

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] teddy0209:
Please do some more readings before you brick your device... You have to download the zip file and install via custom recovery (e.g. twrp)...
[Magisk] 13680201:
Magsik manager v.424 installed.

But magsik v424.zip filed in install!

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] doomscooter:
https://github.com/stangri/MagiskFiles?files=1
[Magisk] 13680201:
Error in binary magsik.zip v.424

Filed install

Please update and fix file

فرستاده شده از SM-T805ِ من با Tapatalk
[Magisk] teddy0209:
I already told you, just use the 0415 for the mean time...
[Magisk] dahawthorne:
Well, people can criticise the poster for failing to read, but he's right - I get the same.

Nexus 6, Pure Nexus April latest NHG47K 7.1.2, was on Magisk v13 170415, got the Manager update notification of 170424, so I installed via Manager & rebooted. Red "No Magisk installed" message. No problem, I thought, I'll just install in TWRP. With the same result. So now I'm back on 170415, with a blue "170424 available" in Magisk Manager...
[Magisk] Didgeridoohan:
There's never been any promises that these snapshots will be stable and/or even usable...