yashsingh1/xdaforums huggingface dataset:
[Magisk] Ansuel:
Why with v12 i have saftynet pass and with snapshot it doesn't pass?
[Magisk] Didgeridoohan:
You might have to restart the Hide daemon (toggle off/on). I had to do this when I tried 170604 on my Nexus 6.
[Magisk] Ansuel:
i have integrity pass but cts profile no...
[Magisk] Didgeridoohan:
Yeah, I saw that a couple of times as well... Reboot, toggle off/on, it might work.

Remember, this is an unofficial beta snapshot we're talking about. Don't expect it to always be functional...
[Magisk] Ansuel:
also any problem with module installation ?

or v12 module are not compatible?

(or i should remove v12 and then install v13, and not flash over it)
[Magisk] KaMyKaSii:
The Answer to The Ultimate Question of Life, the Universe, and Everything is: CLEAN FLASH.
[Magisk] Ansuel:
will try... ahahaha
[Magisk] r1l_Alex_™:
Wiped the whole device clean. All the way down. Compiled the boot image. Built running V13 604 installed on clean flash with 604 Manager on start. All is good in the world!

:) x2 clean flash it.
[Magisk] fndpena:
[MENTION=2226076]stangri[/MENTION] or [MENTION=4470081]topjohnwu[/MENTION] do you know something about magisk hide not starting on boot?

I always have to manually switch off and on to get it work after rebooting the phone...
[Magisk] genbu:
Thanks, that works. Now i can have root on my a7 :)
[Magisk] Genericxx:
Indeed interesting! I'm curious, if deinstalling Magisk Manager is really needed or if a simple rename of the APK might solve it. Dunno if spushtan explicitly scans for magiskmanager.apk file or for running process. Maybe someone is able to check this out, i won't get the opportunity before tomorrow. This would turn the tide for me.
[Magisk] _litz:
Been running the 5/31 build for a few days now ... works well, except it is constantly losing root.

Multiple times daily; have to force-stop Magisk Manager, and restart it ...

While it's an improvement over "have to reboot the whole device to recover root", it's still not ideal. any ideas?

I see errors in the magisk log about sqllite being unable to access settings.sql when this happens.

13beta 170531, on a Moto X Pure (running latest 6.0 stock firmware)
[Magisk] DodoGTA:
Install latest Magisk Manager snapshot build when it comes out
[Magisk] otaconremo:
I can see there's a new spapshot for magisk manager apk v170604 but I can't install it.

Error: The package conflicts with an existing package by the same name.

Do I have to use uninstaller to reinstall this newer version?
[Magisk] DodoGTA:
Uninstall the current Magisk Manager to install the new one
[Magisk] kantjer:
uninstall MagiskManger and install the new build.

If you want to keep your setting (like root permissions) you can restore MagiskManger data with for example Titanium BU after the reinstrall.

EDIT: ninja'd :)
[Magisk] otaconremo:
I can't uninstall the manager app. I only have Disable and Force stop in my app settings.

I think the reason it won't install/update is because of its version number. The previous builds were written as "5.0.1705xx" but the latest is ".170604" only.
[Magisk] DodoGTA:
Uninstall it using some system app remover
[Magisk] Sheetzie03:
Come on man, your on XDA, your obv rooted, and your telling me you couldn't figure out a way to remove an app that didn't have the uninstall button? Honestly? Come on.
[Magisk] DodoGTA:
Hahaha :D :D :D
[Magisk] otaconremo:
Of course I know how to uninstall this.

I was just pointing out there's an error in building the last update.

I have an Axon 7 chinese version which doesn't have kernel support from any dev here and the first time I used magisk v13 was from a modified version from [MENTION=5492451]NFound[/MENTION]. His script was edited to install magisk as system app.

My problem is that when I updated the app to v0531, it doesn't give su permission to apps. Tibu then force closes when opened. Thus, i can't uninstall system apps.

But I did find a way to get it out. So don't be so hard on me. :P
[Magisk] dahawthorne:
Maybe it's a function of Nova Launcher, but have you tried long-pressing the icon on your home screen or drawer for an Uninstall option? That worked for me when I had your exact same problem last time with Magisk.

Edit: Ah, I see I'm too late... :)
[Magisk] DodoGTA:
TWRP is your friend in this case :)
[Magisk] kantjer:
That's just cosmetic, it isn't the cause of your issue

That cosmetic issue is due to

MAGISKMANVER='5.0'

is missing in the build script
[Magisk] guest4711:
Just to state: Updated my maguro from 13.20170531 to 13.20170604 via magisk-managers built-in updater without problems.
[Magisk] stangri:
Thanks, fixed.

I personally (not the box which has the build cronjob set up) will be offline for the next 10 days, but there're other people with the write access to the repo who could fix things while I'm gone.
[Magisk] Gilfreitas:
I uninstalled the old version but build 6/6 does not install.
[Magisk] _litz:
Did that, no difference.

Still lose root and have to restart Magisk Manager.

Appears to happen any time Magisk Hide goes active ... basically it hides then never unhides. Can clearly see in the log where hide_daemon umounted sbin, magisk, and system/etc/hosts ... then never remounted them.

Restarting Magisk Manager restores things.
[Magisk] ajaxcbcb:
use the magisk uninstaller. then reflash the 6/6 version.
[Magisk] Gilfreitas:
That's what I said and did. I gave the Uninstaller flash and etc.
[Magisk] Shen Ron:
Can the magisk manager app include the mount namespace seperation option just like chainfire's supersu app?
[Magisk] otaconremo:
Does your 0606 app crash when opened?

I can only open my app during after install or when I clear data. After reopening the app, it just crashes.

Same thing happens with 0604. For 0531, it doesn't give SU permissions.

The only version that works for me is still 0528.
[Magisk] kantjer:
have you tried uninstalling the app and reinstall?
[Magisk] otaconremo:
Yes I did, even going back to previous versions of the app and even magisk too..

0528 works well for me except that it crashes when I go into Superuser tab.
[Magisk] Shadowghoster:
Last time I had that error, uninstalling magisk manager and manually deleting the package from /data fixed it for me.

Since the new build system got implemented I can only flash the new magisk versions when flashing v12 before once, otherwise flashing aborts with error 1. I'll try to get a log next time.
[Magisk] -ION-:
The new installation scripts fail to create a proper magisk.img. What worked for me was flashing 170602 and the latest version on top of that (so that it doesn't have to create the magisk.img).
[Magisk] Team DevDigitel:
thank you for this unofficial branch. This addressed a ton of issues v12 official brought to my lg v20 development. The latest version 0606 with newest manager runs great. Phone seems to have 0 lag now after a full reboot, no lock screen shutter etc that was caused by magisk building things up on boot and causing the system ui to freeze/fc. Version 12 was completely dead for us on the stock kernel causing endless bootloops. This was the exact fix we needed for some time!! Thanks guys for looking at some improvements and tweaks to the main variant.

Ill be moving my builds to support the unofficial manager from here forward! Awesome work team!

On that note, is it okay to include the unofficial magisk in my rom with proper credits and link to op for discussion of it and magisk related questions etc?
[Magisk] teddy0209:
These builds are from the official source as far as I know... ???... So I believe you should ask john wuh himself... ?
[Magisk] Team DevDigitel:
his page says yeah, but this is a forked build so i need their perms and i didnt see a dev clause at bottom..

I know orig. magisk is cool with it, just making sure the fork team is on board
[Magisk] ultyrunner:
Nevermind. Tested this and it didn't work. Fully unrooted Super SU, installed magisk from TWRP and then it worked like a charm.

---------

Can anyone tell me if you can install the manager app and then update root from within if you're on a normal systemless Super SU? Or, being a branch of the original, do I need to flash magisk and then install the manager app? I'm tempted to try anyway, but just thought I'd ask if anyone has done that.
[Magisk] DodoGTA:
SuperSU updates are ONLY done from SuperSU app or by flashing updated SuperSU ZIP
[Magisk] ultyrunner:
That actually isn't remotely related to my comment. In the original version of magisk, you can theoretically install magisk over SuperSU systemless from Magisk Manager. However, on V13 it didn't work. I edited my comment to reflect that and to say that I fully unrooted via SuperSU and then installed magisk without problem. So, I have no idea what you're referring to, because unrooting SuperSU is, of course, done from the SuperSU app.
[Magisk] DodoGTA:
Then ask [MENTION=4470081]topjohnwu[/MENTION] to fix that issue
[Magisk] ultyrunner:
Dude, really? There is nothing to fix. Read my comment. I made it work fine by unrooting. Done feeding trolls.
[Magisk] DodoGTA:
But I'm talking about Magisk systemless SuperSU compatibility
[Magisk] wrongway213:
Thread is for Snapshot/betas - v13. Try the Magisk General Support / DIsccusion thread here
[Magisk] Team DevDigitel:
Lol...

Sorry you didnt get a good reply.

Yes.. I installed magisk manager and installed 0606 zip dowbloaded from the magisk manager and it installed the zip fine without issue.

I was on official magisk v11.6 and just unistalled the manager and replaced with the unofficial one.
[Magisk] Ubimo:
Why are the latest snapshots big again (6.91 MB)? The builds before were only 1.27 MB.
[Magisk] abacate123:
Maybe it's coming with the manager apk inside.
[Magisk] fndpena:
I can confirm that. It's coming with the latest APK now. Makes sense, since the app is no longer in Playstore...
[Magisk] Artim_96:
He stated an hour ago that it's intended to be that way, support will be back later. So if the question comes up again you can link to the latest entry from topjohnwu now
[Magisk] ultyrunner:
It was more my original ask about installing over SuperSU from Magisk Manager, which V12 is supposed to do. It made more sense to me to do a clean install anyway. No clue what the other guy was on about :silly:
[Magisk] LazerH:
Will this be continued now there is an official beta for v13?

This works very fine for me do far, that's why I plan to stick with it until official stable v13 ( I know that's not the purpose of y beta)
[Magisk] teddy0209:
Auto builds should continue as long as development of magisk continues... The purpose of the official beta is for debugging prior to the release of v13...
[Magisk] SavageRobot:
FYI

Running v13.170531 no issues at all. flashed 170606 Tuesday, lost root randomly today/last night. Simple reboot fixes so not really issue, just letting know.

LG G4 H815

DU 7.1.2
[Magisk] biggdevon:
Is there an available link for v13 beta? I read the updated post by topjohnwu but the download links still point you v12. Guessing I already have my answer.
[Magisk] LazerH:
There is a new thread for the beta, as he purpose of it is testing.

Can't give u the link, I'm in phone
[Magisk] biggdevon:
It's a little early here, didn't think you check the threads for a new one. ? thanks again
[Magisk] teddy0209:
There it is, I was late... It's attached on the first post...
[Magisk] _litz:
Try force-stopping, then immediately reopening Magisk Manager, and see if you regain root access ... that's works for me, vs a reboot ... and it's a whole lot faster.
[Magisk] JRJ442:
Also just clearing the Magisk Manager from recents works.
[Magisk] sergey1977:
always need to reinstall maggsk if did changes in buid.prop ?

i did some changes in build.prop and after reboot phone was always hot. then reinstall maggsk and phone became normal temp
[Magisk] swa100:
Can anyone confirm that the latest v13 release works with Android O dp3?
[Magisk] Artim_96:
Try yourself, there aren't many people lucky enough to have such a device. But topjohnwu has so if it doesn't work out will very soon

---------- Post added at 11:39 PM ---------- Previous post was at 11:37 PM ----------

Then maybe your changes where corrupted? Or maybe you made an error in the module?

Maybe upload some logs, or probably your module.

And it's that change the only one making problems?
[Magisk] Maxr1998:
Magisk V13 works on DP3, SafetyNet thus also fine, just make sure to remove your Substratum themes before or have a rescue zip handy0..
[Magisk] otaconremo:
Since topjohnwu released his v13 beta, will this thread still continue?

I still haven't any luck on app v5 0528 later. Although I'm using magisk v130606.

Even with the latest beta, same thing also happens app keep crashing unless data is cleared and/or not giving root perm. Also i noticed in my 0528 app, it only gives forever root permisssion to the first app it allows after installing or clearing data. The next app to request root will crash the magisk app unless I only allow it once for root.
[Magisk] Artim_96:
Logs don't show any error. If your don't pass SN then either follow once of the numerous guides or you are out of luck and you can't pass
[Magisk] Sartharon:
I prove you wrong. :) Don't take it personal you may have missed it.

04-15 04:24:37.596 265 311 E Magisk : resetprop: setprop error

Tbh I don't a lot about this error or how to resolve it. Or if it even is the root of his problem. But there you go maybe some smart guys know how to fix it
[Magisk] Didgeridoohan:
That error looks like it is from the Magisk module, CTSEnabler. It might not be compatible with v13 or otherwise faulty...
[Magisk] Ardany Jolón:
Exactly because of that error in that line that is a question, that in versions of previous days and worked, pitifully in the compilations of the past week and the present one was that the fault began.

The build that worked well was the 29th of last month.

I will continue to look for solutions, just as if someone has a solution, thank you very much :good::good::good:
[Magisk] Didgeridoohan:
Nope...

It MIGHT have stability issues because there MIGHT be commits that needs testing and MAY have introduced bugs, not because it's "unofficial".

This "unofficial" v10 build has been rock solid for me, much more so than v9.
[Magisk] Deic:
The best explanation ever, you won.
[Magisk] _litz:
The loss of root problem seems to be fixed; been running the 12/27 build without issues, even without the "final" commit from the 29th.
[Magisk] _litz:
I tried to follow this, and I can't get anything to work ... what has to be done to properly install and configure android studio to allow Magisk to compile?

All I get from the cmd window is a bunch of android.mk not found errors.

I develop .NET stuff for windows, android is new to me. It is very obviously not plug and play.

Edit: looks like some pre-reqs were missing in the SDK setup, that aren't set by default ... seems to be working better now
[Magisk] _litz:
Nope, can't get magisk to compile. Even after adding missing items in SDK (ndk, cmake), magisk does not compile. the MagiskManager app does, no problem, but all I get from Magisk itself is :

************************

* Building binaries

************************

jni/Android.mk:5: jni/resetprop/Android.mk: No such file or directory

jni/Android.mk:6: jni/sepolicy-inject/Android.mk: No such file or directory

jni/Android.mk:7: jni/su/Android.mk: No such file or directory

jni/Android.mk:9: jni/selinux/libsepol/Android.mk: No such file or directory

jni/Android.mk:10: jni/selinux/libselinux/Android.mk: No such file or directory

jni/Android.mk:5: jni/resetprop/Android.mk: No such file or directory

jni/Android.mk:6: jni/sepolicy-inject/Android.mk: No such file or directory

jni/Android.mk:7: jni/su/Android.mk: No such file or directory

jni/Android.mk:9: jni/selinux/libsepol/Android.mk: No such file or directory

jni/Android.mk:10: jni/selinux/libselinux/Android.mk: No such file or directory

jni/Android.mk:5: jni/resetprop/Android.mk: No such file or directory

jni/Android.mk:6: jni/sepolicy-inject/Android.mk: No such file or directory

jni/Android.mk:7: jni/su/Android.mk: No such file or directory

jni/Android.mk:9: jni/selinux/libsepol/Android.mk: No such file or directory

jni/Android.mk:10: jni/selinux/libselinux/Android.mk: No such file or directory

jni/Android.mk:5: jni/resetprop/Android.mk: No such file or directory

jni/Android.mk:6: jni/sepolicy-inject/Android.mk: No such file or directory

jni/Android.mk:7: jni/su/Android.mk: No such file or directory

jni/Android.mk:9: jni/selinux/libsepol/Android.mk: No such file or directory

jni/Android.mk:10: jni/selinux/libselinux/Android.mk: No such file or directory

make: *** No rule to make target `jni/selinux/libselinux/Android.mk'. Stop.

---------- Post added at 03:35 PM ---------- Previous post was at 03:32 PM ----------

Reason seems to be that the files are not populating when the githib project is pulled, cloned, or downloaded ... so it basically seems to be impossible to pull this project to local directory right now ... :(

---------- Post added at 03:41 PM ---------- Previous post was at 03:35 PM ----------

Aha, it appears that you don't get projects included inside other projects; you have to grab each one separately. This stupid ... this should be recursive.

---------- Post added at 03:55 PM ---------- Previous post was at 03:41 PM ----------

and once that's done, it does compile!
[Magisk] JEANRIVERA:
do you mind sharing your builds maybe by pm? but please if you do don't do it as attachments in xda since they are broke for now upload them to different server maybe dropbox or google drive...
[Magisk] Link_of_Hyrule:
Can someone upload the 12/30 files to another host since if you download the attachments they aren't valid files? (Yes I read that it's XDA's fault).
[Magisk] jsaxon2:
Magisk v10 from 12/30

https://drive.google.com/file/d/0B1iRsZPFZo3ETVFVYlhCMWdWdDA/view?usp=drivesdk
[Magisk] Link_of_Hyrule:
Much appreciated can you upload the newest version of the magisk manager 2.6 apk file as well?
[Magisk] jsaxon2:
Magisk Manager 3.0 built 12/31

https://drive.google.com/file/d/0B1iRsZPFZo3ER3Fyb0J1ZlVDOGc/view?usp=drivesdk
[Magisk] Captain_Throwback:
I'm not a mod...look again.

You don't have a monopoly on phrases or the English language, so I think you're giving yourself too much credit. But yes, I used a similar phrase intentionally, because clearly you don't understand, and yet you suggested that I didn't.

Just to put this to rest, [MENTION=4470081]topjohnwu[/MENTION] himself once told me to build a Magisk zip from the repo because it included some fixes that weren't in the current v9 version. So that itself proves that stability has nothing to do with the 'officialness' of the build.
[Magisk] Link_of_Hyrule:
Installed for 5 minutes and root is already gone again so seems like it's still not fixed. Unless I had to completely uninstall the old magisk to get the new one to replace it but I installed my ROM and then magisk so that should do the same thing I would imagine.
[Magisk] _litz:
Here you go :

https://www.dropbox.com/s/n484q6devk0jrbn/Magisk-v10_test_123116.zip?dl=0

https://www.dropbox.com/s/0o2ckiotlvfuhx6/MagiskManager-v10_test_123116.apk?dl=0

Remember these are signed with different keys, you have to uninstall/reinstall both magisk and the manager.
[Magisk] Captain_Throwback:
It isn't fully fixed yet.

But now [MENTION=4470081]topjohnwu[/MENTION] knows what the problem is (finally!) and is working on a proper fix. No idea how long that'll take, but I believe he wants it fixed before the next "official" release, lol.
[Magisk] Link_of_Hyrule:
Awesome, hopefully very soon!
[Magisk] _litz:
This commit : https://github.com/topjohnwu/Magisk/commit/0bf04c04f9aa2ab119d2fb1df6d3995a0b77880e is labeled "The final fix", and it should be in the next official release.

It should also be in any unofficial release compiled after 12/30/16
[Magisk] Link_of_Hyrule:
Great now we just need a new build with this commit in it!
[Magisk] Link_of_Hyrule:
Since the file downloads on XDA don't work can someone upload the 12/31/16 Magisk 10 and Magisk Manager apk to a different file host? I don't really understand why the attachments are still being used when they are broken right now.
[Magisk] Link_of_Hyrule:
Cool thanks :good: idk how I missed that lol. Can't wait for the official build to kick in it's been a log time coming!
[Magisk] Artim_96:
Well then you should get way more specific if you want help. That log doesn't really say anything helpful.

What device do you use? Which Android version (OEM/custom) and which patch level?
[Magisk] saransh arya:
Unable to install,installation failed in recovery,pure stock rom with twrp recovery moto g turbo Merlin xt1557,help!
[Magisk] Didgeridoohan:
Help us help you. We're not mind readers...

Logs or it didn't happen (TWRP -> Advanced -> Copy Log).
[Magisk] dahawthorne:
Not enough info. Try earlier versions. I've just upgraded my Nexus 10 to the newest Pure Nexus and Magisk 170606 & 170604 didn't work, but 170602 does, though I get CTS mismatch, which doesn't bother me, since all I want is root and that works perfectly.
[Magisk] Ubimo:
Why no more builds after 0606?
[Magisk] Ardany Jolón:
[MENTION=4470081]topjohnwu[/MENTION] [MENTION=2226076]stangri[/MENTION] I have been doing different tests injecting lines in build.prop from system.prop of magisk, but none works, I consider that it is directly a problem in the most recent constructions. The last build with which I have succeeded in testing adding lines to system.prop was the Magisk-v13-170529.zip
[Magisk] teddy0209:
V13 is under testing now prior to the release, if you want to help in the debugging, head to the v13 beta thread, try it and provide logs...

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

V13 is under testing now prior to the release, if you want to help in the debugging, head to the v13 beta thread, try it and provide logs...
[Magisk] ridobe:
But, that's not the point of this thread. The build script is supposed to create a new build if any new commits are present in topjohnwu's git repo.
[Magisk] teddy0209:
I know that's not the point of this thread... That's why I directed them to the beta thread to help if they can by providing logs...
[Magisk] Ardany Jolón:
Motorola Moto G3 Osprey, LineageOS 13 recent, security patch May 1.

A while ago I was testing with the beta version provided in the other thread and I've passed SafetyNet.

I forgot to clarify that CTS I have spent with a module.
[Magisk] kantjer:
For some reason your cronjob isn't starting the builds (no new builds since you left)

I made a build and pushed it to your git. I will keep monitoring the source for updates and push builds until your back.
[Magisk] Ubimo:
Yippee, Magisk-v13-170611.zip it the first fully working version since 170415 for me. SGS7 edge SuperMan rom 2.5

No long boot time at boot screen

Modules working

Edit:

I've attached an error log. Does anybody see errors in it? Or is this normal?

Edit2:

The log entries are getting more and more, something is not right I think.
[Magisk] kramer04:
Just install the v-13 170611 and works good.

This is the first one which works completely both root and safetynet

My advice Samsung galaxy note 3 SM-N9005

I'll go to try module
[Magisk] sperelli:
how did u do that? unistalling 0606 from recovery with its uninstaller?
[Magisk] kramer04:
No i'd had v12 before because v13 didn't work.

I uninstall completely magisk manager and magisk.

And to be sure install my kernel again.

Boot

And then install v13 -170611

Don't use module.. they can't install
[Magisk] kantjer:
In my experience modules work just fine when installed via TWRP
[Magisk] kramer04:
Thanks

Just reboot and now it works...
[Magisk] Paschfire:
Nexus 5, twrp-3.1.1-0, DU11.5-2017/06/09-N-7.1.2, FKr107(also tried on stock du boot image)

When flashing v13-0611 install errors that it connot find boot image.

See attached recovery log.

Sorry if not the proper logs, pls let me know what else is required if needed, this is my first time reporting an issue on this thread.

Thanks!