yashsingh1/xdaforums huggingface dataset:
[Magisk] Bradco:
Hi everyone,

I have a question about magisk and xposed to be property.

what is the difference between xposed and xposed magisk ?

I root my smartphone with magisk I have to use magisk xposed or xposed official also works, what do you advise me?
[Magisk] bmg002:
Adding to my previous post:

So what I did try was doing a complete uninstall of Magisk (flashed the uninstaller as well as the unSU zip) so I would be near factory (with unlocked bootloader). I then installed magisk manager 5.3.5 and did a safetynet check and basic integrity was passed.

I then ran Root Checker and it said I wasn't rooted and no SU binary or SU apps were found. BUT busybox was found. When I look, busybox exists in /system/sbin (as does toybox). I believe this was installed by my ROM. I am expecting that the busybox included in the ROM is what is causing problems with magisk. My understanding is that modifying the /system partition will cause safetynet to fail, so what is a good solution to this? Or is this not actually a problem?

I also see toybox installed on /system/bin. It looks like a lot of things are aliased out to toybox, nothing appears to be aliased to busybox that I can see. I have a feeling that having busybox baked into the stock ROM (not developer ROM, but global stable) that it is causing problems with Magisk? I did dirty flash the stock ROM over top of my current setup and it still had busybox and toybox installed on it.

---------- Post added at 01:17 PM ---------- Previous post was at 12:35 PM ----------

xposed magisk is systemless so OTA updates shouldn't break it. xposed is otherwise written to /system and thus OTA updates will generally fail.

If you have magisk installed, you should use the magisk version of xposed. Xposed (magisk or otherwise) will cause safetynet checks to fail.
[Magisk] Sunnymen1975:
Yes I have tried this, but it doesn't change anything ?
[Magisk] jenslody:
[No message]
[Magisk] bmg002:
I ran that (without magisk) and it tells me it is BusyBox v1.20.2-MIUI so that answers that question. Gave it a try with Magisk installed and it said the same thing - BusyBox v1.20.2-MIUI. I bet that the MIUI busybox is what is causing my headache with safetyNet and magiskhide, eh?
[Magisk] seshanth:
Safety net fails...
[Magisk] Didgeridoohan:
There's this in your log:

E/Magisk ( 139): readlink /proc/2256/ns/mnt failed with 2: No such file or directory

I'm going to take a wild guess that your device has an old kernel (no mount namespace support) and thus isn't compatible with MagiskHide.
[Magisk] trawel:
Hi,

I have a problem that randomly I loose root - though I have flashed magisk, after some time magisk manager shows that there is new version and when I open the app, it says device not rooted. After a reboot everything works fine but maybe you can tell what might be the problem. I'm running OxygenOS 4.5.0 on OnePlus 3 and blu_spark kernel.

Did pull a logs but don't know that stuff and can't tell if there's any problem - it happened somwhere between yesterday from 9PM till today 7AM.

Logs available here https://drive.google.com/file/d/0B9DmhuIkNPnBN3hjbUVsZ3ppVmNZcW1mUm9DcUxyNUxnYkhv/view?usp=drivesdk

Thanks for help
[Magisk] seshanth:
It was working fine, but it failed suddenly.

Kernel: 3.10.54+
[Magisk] Didgeridoohan:
Ok. Wild guesses are sometimes (often) wrong... :laugh:

I'd try a complete reinstall (uninstall Magisk and Manager, restore stock boot image and any custom kernel and install Magisk again).

You can't think of anything you were doing (any kind of tinkering) to your device around the time MagiskHide started failing?
[Magisk] seshanth:
Unistalled magisk and flashed stock boot image. After reinstalling magisk, it still doesn't pass SN.
[Magisk] woozie.2007:
One time at 2 days, my phone lost the root, after restart it works again. This is the magisk log, can tell me an expert if anything wrong? All was installed on clean stock firmare, thanks

beginning of main

I( 432: 432) Magisk v14.0(1400) daemon started

I( 432: 436) ** post-fs mode running

--------- beginning of system

I( 432: 468) ** post-fs-data mode running

I( 432: 468) * Mounting mirrors

I( 432: 468) mount: /dev/block/bootdevice/by-name/system -> /dev/magisk/mirror/system

I( 432: 468) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor

I( 432: 468) bind_mount: /dev/magisk/mirror/bin

I( 432: 468) * Mounting /data/magisk.img

E( 432: 468) mount /dev/block/loop0->/magisk failed with 13: Permission denied

I( 432: 702) ** late_start service mode running

I( 432: 702) * Running service.d scripts

I( 432: 702) * Running module service scripts
[Magisk] Pkt_Lnt:
Known issue, many, many posts about it here. It has been hard to find and no one had gotten logs that show what actually causes root loss. A possible fix is in early private testing to see if it works, you just have to wait for it, since right now there is no proven solution.

Some modules seem to cause it for some, uninstall any you have and reinstall one by one, give each a day to see if that makes it better or worse.
[Magisk] EddoWagt:
I've had it happen without modules as well
[Magisk] Pkt_Lnt:
Me too. two devices, no modules on either. I've tried running aLogcat or SysLog for days in the background trying to get the real cause and no results. Root loss never happened while I had the logcat apps running. :rolleyes:

As I stated, it is a known issue and possible resolution is in testing. Magisk is highly advanced technology, and as always, the Lubarsky's Laws of Cybernetic Entomology apply. :D
[Magisk] woozie.2007:
I have not any module installed, just root
[Magisk] DodoGTA:
Has anyone tried to replace audio-related libraries (like audio.primary.*.so) with a Magisk module? If so, then what are the results?
[Magisk] woozie.2007:
Who, me?
[Magisk] DodoGTA:
I'm asking that question to everyone (Not specifically you)
[Magisk] woozie.2007:
Oh, sorry, i dontnknow how to do that, or if its necesary
[Magisk] bmg002:
I installed Viper4Android on my device and it was successful. Looking at the magisk logs, it looks like it replaces various audio libraries such as libaudiopreprocessing.so, libbundlewrapper.so, libdirac.so, libdownmix.so, libeffectproxy.so, libldnhncr.so, etc. I don't see anything specific to "audio.primary.*.so" though. Are you are talking about changing the ones in the /system/lib/hw folder? If so, I would strongly encourage you not to change them. My understanding of the HW folder is that that contains libraries specific to your hardware. Changing those will more than likely crash applications on your phone and/or cause certain features on your phone to be unavailable. Changing the audio.* libraries for your phone in the HW folder will likely cause audio problems on your phone. Mine appear to be specific to the msm8996 chipset so I would not want to change those unless I knew of a better one for the msm8996 chipset.

Is there a reason you want to change the hardware libraries?
[Magisk] giosaxda:
Hi,

I'm new to Magisk. I've flashed it via TWRP.

My question is will it accept OTA?

I've stock Oreo, TWRP, ElementalX, Systme apps removed, device Nexus 6P.

Thank you.
[Magisk] DodoGTA:
Yes (because my device's platform has a few audio-related library configurations, but they have their own advantages and disadvantages)

And I want to swap those configurations because SM-G310HN configuration has a few annoying issues (And I'm looking at you, [MENTION=5980306]sandpox[/MENTION], because you used that configuration just because it has higher sound quality :mad: ), but that's the end of this post, because it's now quite off-topic
[Magisk] bmg002:
Makes sense then. But if you have multiple audio configurations, wouldn't it be safer to modify the config file (audio_effects.conf) to pick the appropriate audio libraries to use instead of replacing the entire library?

But it is a bit off topic, but not really. My understanding is that using magisk you should be able to modify any /system file without actually modifying /system so in theory I think it should be possible, but I am not aware of anyone swapping it out. Also, not 100% sure how you'd test it. On my phone I have no need to swap out the audio library nor am I sure there is a compatible one out there.
[Magisk] Didgeridoohan:
There's actually official documentation about that:

https://github.com/topjohnwu/Magisk/blob/master/docs/tips.md#ota-installation-tips
[Magisk] bmg002:
Adding again to my previous post - it seems that nothing I try is successful with getting magisk hide to work. Thinking it must be blocked by my ROM somehow. Guess I'll need to wait for the next magisk to come out and hope it is magically fixed or downgrade to an older ROM version. It is weird as I can see magisk hide notes in the log, but when I start an app up that is one of the ones I tried to hide, it doesn't seem to add anything else to the log except that root access was denied.
[Magisk] Simonex16:
If i want to update magisk manager,i have only to update it like a normal app trough is apk?(i'm on v12.0 and i want to upgrade to 14.0 stable)
[Magisk] clb2c4e:
This is a very basic quesion but I'm trying to get a handle on the difference between Magisk and and PHH SuperUser, both root the device but it's unclear to me whether both are required with a current version of Magisk and what the difference was in the first place.

Also, DM verity (verifies the kernel and if I install TWRP and allow modifications then it has a fit and refuses to all the phone to boot basically?) I see it can be disabled by flashing a zip, but it appears Magisk (or PHH SuperUser?) do this on their own?

Finally, Magisk Manager (it's basically the front end?) it should install when I flash Magisk via TWRP but if not I can install it as a normal apk?

Again, sorry for the basic questions, I'm slowly getting a handle on this but have read for a little while now and still don't have a clear idea of these..
[Magisk] Pkt_Lnt:
Post 1 on 3 Oct 2016 - Magisk started with PHH for su

https://xdaforums.com/apps/magisk/official-magisk-v7-universal-systemless-t3473445

Post 12 on 5 Feb 2017 - Magisk got MagiskSU built in based on PHH but no longer needs PHHsu to work.

https://xdaforums.com/showpost.php?p=70897029&postcount=12

If you install Magisk by installing the Magisk Manger via apk as a normal app, and then letting it install Magisk zip and reboot, then you can check if you want dm verity. There are other methods to install, but remember if you have installed any other root method, you must remove it first, re-flash the stock kernel and then install Magisk or it will fail.

Magisk Manager is the GUI manager for Magisk. It is now in the v.14.x zip and *should* install during flash, but in some rare instances it does not, so you can extract it from the zip and install separately. You can also download in in the release thread that is the link above in the Post 1 part.
[Magisk] SignetSphere:
I'm having a problem. The option "systemless host" on Magisk is not sticking after I enable it. It reverts back after I clear my recents and after I reboot my device.

Prior to that I was using the systemless AdAway (was working fine) and removed it. But discovered that the Unified AdBlock is better but I'm having problems as i've first mentioned.
[Magisk] Pkt_Lnt:
It is cosmetic only. Adaway will work fine, (at least up to Nougat) even with the option grey. It has been discussed here many times and the complete cosmetic fix is in GitHub but not pushed yet. Still if you set it in Magisk, it will work.

https://xdaforums.com/showpost.php?p=72364090&postcount=9154
[Magisk] SignetSphere:
I see... still fairly new to magisk so yeah... haha. One thing though... I don't know if it's valid to ask here but when I'm using the Unified Host Manger app and I select Install it gives me an Error. Any idea on that? Or is it cosmetic as well?
[Magisk] Pkt_Lnt:
No, I do not use it. Post the logs asked for in this thread and someone likely can help. Magisk log, recovery log, logcat.
[Magisk] SignetSphere:
Nevermind that haha I just reverted back to the systemless AdAway apk. Thanks anyway :good:
[Magisk] reggjoo:
I updated to magisk 14.1 , and somehow it reverted back to version 14.0, and safety net failed, after a few days. There was no intervention from me to make any changes. Now it says there's no updates past 14.0. Any ideas?
[Magisk] AlfaRune:
View attachment magisk_error_20171013_105725.logI can't download any module. Here's the logcat.
[Magisk] manos78:
Hi [MENTION=4470081]topjohnwu[/MENTION],

Please, can you add support in the Magisk Manager for "touch/untouch" the file "/cache/.disable_magisk"?

When I boot with this file touched (for a temporal disable) it will be usefull to have a simple switch in the Manager for delete this file.

Yes, I can do it with another tool. However, it will be a great idea to have this native in the Manager (like the Xposed Installer has for enable/disable the Framework).

You agree?
[Magisk] SignetSphere:
Anyone knows a module be it Xposed or a Magisk module that randomizes the numbers on the lock screen when you lock your phone?
[Magisk] Artim_96:
No. Magisk won't be possible and it's very unlikely that a XPosed module can do that either
[Magisk] SignetSphere:
That's sad but oh well lol... Thanks for answering :)
[Magisk] Artim_96:
It would definitely be a big point for security, but the question is if it's even implemented in Java. Maybe not so you should ask a ROM developer if he could implement something like that
[Magisk] SignetSphere:
I just asked and they removed it (Resurrection Remix ROM user here). And I think it's due to the reason you've stated.
[Magisk] pellajl:
Hi,

Just installed [ROM][7.1.2][trltexx] Resurrection Remix 5.8.5 [20171002][OFFICIAL] on my Galaxy Note 4 and I have found the IR Blaster isn't working.

Searching the thread, a couple of users have found removing Magisk and installing SuperSu enabled the IR Blaster. See link below:

https://xdaforums.com/showpost.php?p=73178734&postcount=1896

I don't understand why this should be the case.

Is this a known issue and is there a fix?

Thanks
[Magisk] Pkt_Lnt:
I experience this daily! :D :cowboy: :angel: :cyclops:
[Magisk] Sayenah:
Hello,

I have a peculiar situation, so first a little background: I am running LineageOS 14.1 with Magisk 14.0 (MagiskSU) on a Samsung Galaxy Tab S 8.4 (SM-T700). I am failing the ctsProfile check but passing the BasicIntegrity check.

I am trying to run the PS4 Remote Play app; installed the available Sony Firmware module (which enables the app to be downloaded from the app store). The app launches but still is detecting root (error: 88001003; which means root is being detected by app). The app is added to Magisk hide.

Tried rebooting, reinstalling, re-enabling Magisk hide a million times but the root is still being detected. Tried the "Universal SafetyNet Fix (beta 5 Magisk v14.0 hotfix)" and I get a black screen. here are my questions:

1. What am I doing wrong? Any tips?

2. I have read that I need a custom kernel for my device; what would be a good recommendation?

Cheers
[Magisk] DodoGTA:
The module attached to this post will help you to pass ctsProfile (install it with Magisk Manager or recovery)
[Magisk] Fif_:
The Gravity Box for Nougat Xposed module can do that. Amongst many other things...
[Magisk] Bigben37:
I'm having the same issue. Remving /data/data/com.topjohnwu.magisk and /data/app/com.topjohnwu.magisk did also not work. I checked with RootBeer Sample for root detection, and I only got a red cross at "ROOT CLOAKING APPS" (even though I tested this when I had the com.topjohnwu.magisk folders removed).

Also in my magisk log it says "beginning of crash":

--------- beginning of main
I( 198: 198) Magisk v14.0(1400) daemon started
I( 198: 200) ** post-fs mode running
--------- beginning of system
I( 198: 213) ** post-fs-data mode running
I( 198: 213) * Mounting mirrors
I( 198: 213) mount: /dev/block/platform/msm_sdcc.1/by-name/system -> /dev/magisk/mirror/system
I( 198: 213) link: /dev/magisk/mirror/system/vendor -> /dev/magisk/mirror/vendor
I( 198: 213) bind_mount: /dev/magisk/mirror/bin
I( 198: 213) * Mounting /data/magisk.img
I( 198: 213) * Running post-fs-data.d scripts
I( 198: 213) * Running module post-fs-data scripts
I( 198: 213) * Loading modules
I( 198: 213) * Enabling systemless hosts file support
I( 198: 213) bind_mount: /system/etc/hosts
I( 198: 225) * Starting MagiskHide
I( 198: 225) hide_utils: Hiding sensitive props
I( 198: 225) hide_list: [com.google.android.gms.unstable]
I( 198: 225) hide_list: [com.starfinanz.mobile.android.dkbpushtan]
I( 198: 225) hide_list: [de.dkb.portalapp]
I( 198: 225) hide_list: [com.entersekt.authapp.dkb]
I( 198: 225) hide_list: [com.scottyab.rootbeer.sample]
I( 198: 225) proc_monitor: init ns=mnt:[4026531840]
I( 198: 271) ** late_start service mode running
I( 198: 271) * Running service.d scripts
I( 198: 271) * Running module service scripts
I( 198: 225) proc_monitor: zygote ns=mnt:[4026535216]
I( 198: 225) proc_monitor: com.google.android.gms.unstable (PID=3043 ns=mnt:[4026535255])
I( 3051: 3051) hide_utils: Re-linking /sbin
I( 198: 225) proc_monitor: com.scottyab.rootbeer.sample (PID=3405 ns=mnt:[4026535308])
I( 198: 225) proc_monitor: com.google.android.gms.unstable (PID=5307 ns=mnt:[4026535362])
I( 198: 225) proc_monitor: com.starfinanz.mobile.android.dkbpushtan (PID=5362 ns=mnt:[4026535363])
--------- beginning of crash

Any ideas?
[Magisk] bmg002:
two thoughts - first, do you have any battery saving apps installed? Those can force-kill things like this.

second - When I had that "beginning of crash" showing up in my log, I did a full uninstall (flashed the uninstaller as well as flashed the unSU app) followed by a fresh install of Magisk 14.2 and the beginning of crash notice went away.

Looking at your log, I see things in it that don't exist in mine though. Like most of those proc_monitor lines and the re-linking /sbin. The only proc_monitor that shows up for me is the one that is watching init... not sure why the others don't show up in my log :(.
[Magisk] jenslody:
This file does not disable magisk, it just puts Magisk in "core only"-mode on next reboot.

This means modules are not loaded, but root and magiskhide should still work.

It can be controlled with a checkbox in the MagiskManager's settings.
[Magisk] Bigben37:
Thanks for the input. I don't have any battery saving apps installed. I flashed the uninstaller and also flashed the addonsu-remove from LineageOS again, since I used this to get su before. Then I installed 14.2 , but I still get the "beginnin of crash" error when I start the DKP tan2go app.

I mean it works perfectly fine for other apps, only when I start this app I get this crash error.
[Magisk] SignetSphere:
Kinda conflicts on mine since I'm using a heavily modified custom rom. Thanks for suggesting it anyway :)
[Magisk] countersv:
Magisk will extract it for you from the AP part of the firmware, but it's useless as after patching and flashing it back, there's a bootloop. I have found no solution yet...
[Magisk] andrea0807:
Hi guys, I have a problem.I can not install any module, in the download section, of magisk manager.

The application tells me "processing error". I was able to install only xposed because I manually flashed the recovery zip.

I have a leeco le max 2 with paranoid android 7.1.2 Magisk version 14.0 Version magisk manager 5.3.0
[Magisk] Deus.:
Create a folder on your phone, MagiskManager in /storage/emulated/0

You need a file browser with root privileges, or you can use a terminal (even from TWRP or from the OS), type: mkdir /storage/emulated/0/MagiskManager
[Magisk] klausstoertebeker:
Can't install Magisk v14 on my Sony Xperia Z5 compact running Android 6.0.1

Hello to the community!

I have two Sony Xperia devices on which I want to install "Magisk v14", both running Android Marshmallow (Android 6.0.1):

Sony Xperia Z5 compact (E5823; Android build E5823_32.2.A.0.253_1298-1220_R2C)

Sony Xperia Z3 Tablet compact (LTE; SGP621; Android build SGP621_23.1.A.1.28_1289-9163_R6C)

This is my procedure to install "Magisk v14" having in mind that its mandatory to use an original stock rom without installed super user solution, but with custom recovery and virtually restored trim area so that the device looks like never has been unlocked or rooted:

download the appropriate ".tft" file via "XperiFirm"

download the appropriate "TWRP" image (version 3.0.2-0)

extracting the kernel with "Flashtool 0.9.23"

building a boot image using "Trim Area - Proof Of Concept" (great tool to virtually restore your original TA Partition. Your phone looks like never have been unlocked or rooted). Building options were: Include recovery image, dm-verity disabled, Sony RIC disabled

flashing boot image with "Flashtool 0.9.23"

installing "Magisk v14" with "TWRP 3.0.2-0"

On both devices I was able to boot into recovery and install the "Magisk v14" zip file without error.

But only the Sony Xperia Z3 Tablet compact boots into Android after "Magisk v14" installation.

The Sony Xperia Z5 compact stucks in a boot loop so that I have to install the "Magisk Uninstaller" to remove "Magisk v14" completely. Then my Sony Xperia Z5 compact starts up without problems. I then tried installation with clearing Dalvik cache, but I got stuck into a boot loop again.

Does anyone made similar experiences or has a solution?

Greeting from Germany

"klausstoertebeker"
[Magisk] theandroidguy:
Somehow I was able to recover my phone from this same bootlooped state.After the bootloop, open recovery and flash the stock boot.img, then flash supersu. Now you will be able to boot into your rom. Now download the unsu.zip from xda, go to recovery flash the unsu.zip and reflash the stock boot.img and then flash Magisk again, now u will be able to boot into your system without any bootloop + Magisk installed

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

Gravitybox i.e. a Xposed Module will easily do the job for you

---------- Post added at 11:09 AM ---------- Previous post was at 11:03 AM ----------

Xposed is a framework which lets you install modules to customise the OS "on the fly". You need a rooted device, and AFAIK, Xposed modifies /system as soon as you install it (so it breaks SafetyNet, Android Pay etc.).

Magisk, on the other hand, is a framework which allows you to modify the OS without directly altering /system. With the Magisk framework installed, you can install a number of mods systemlessly - most notably root access (Magisk includes its own SU and binary), but there are a number of other modules which have been adapted to interface systemlessly with Magisk.

Actually, Xposed is one of the available Magisk modules. In other words, if you've installed the Magisk framework, you can systemlessly install Xposed. If your device is compatible with Magisk Xposed(N) then it will be a better choice to use Xposed systemlessly(i.e. using Magisk) otherwise if you are unable to use Xposed using Magisk then flash the official xposed.zip

---------- Post added at 11:11 AM ---------- Previous post was at 11:09 AM ----------

the best way to downngrade is to flash the Magisk remover.zip and then flash the magisk 13.6 again
[Magisk] Simonex16:
How can i update magisk v12 to v14?

TWRP?

Lg G3 fulmics 7.6 d855 kernel stock
[Magisk] Deus.:
Start Magisk when you are connected to the internet. The app will search for updates automatically and gives you the possibility to download and install the newer version.

If it doesn't happen, visit the Magisk thread and download the 14.0.
[Magisk] andreasy:
First time user of Magisk on s7 edge and I have some questions:

1. I installed superstock rom and selected magisk for root. Then I flashed the csc change tool and changed my csc. Everything fine so far. I factory reset rom and magisk was gone. Why is that? Isn't it built into rom?

2. Some apps like titanium backup and call recorder ask me to install Supersu because magisk isn't compatible. Can I install supersu side by side with magisk?

3. I installed a few modules in magisk (3 maybe) and reboot. That gave me boot loop which was only fixed after I uninstalled magisk and reinstalled. But that required me to install everything again. This time I installed only one module at a time and reboot. Could that be the problem?