yashsingh1/xdaforums huggingface dataset:
[Magisk] jhedfors:
I have given up on MultiROM because of the inability to pass SN on secondary ROMs. Even stock unrooted backups that pass on primary fail when placed on secondary.

I was really looking forward to the Magisk MultiROM solution. :( However, that may be a long while...

The release thread says nothing about compatibility with (Tassadar's) MultiROM.
[Magisk] 135Shadowsoul:
Good morning every1,

with post 9170 i asked a question and did not get any answer, so i will repost it. Sorry if any1 is annoyed or it is against any rules, but the question still remains:

"Is it possible with magisk (and its root solution) to have the "BINDSYSTEMXBIN=true - mode" and still pass SN? i found a thread (link currently not at hand), which said it would break SN-passing. Can any1 confirm/refute? And if possible to pass SN with magisk (and its root solution) how to use the BINDSYSTEMXBIN=true? (What/how to change during installation process) i need it for some bad coded apps which... (CM built-in file manager for example)."

please help me :)

Greetings
[Magisk] TheDarknessEffect:
hey guys, I have a rooted THL 4000 phone, what should I do to install magisk?

since the the google play app is not compatible with my device.
[Magisk] :
A nightmare

Magisk is a nightmare.Apps are disappearing from my launcher and GPS is not working.If I disable Magisk everything works fine.Plus,if I update Magisk through Magisk Manager I get CTS Profile Mismatch.If I don't update Magisk at all I get Safetynet Passed.

I think MagiskSU destroyed everything that made Magisk a great Systemless Interface.
[Magisk] crusader727:
very useful post :silly:
[Magisk] :
This is a thread used for support,which includes bugs and problems...

It's not about usefulness.
[Magisk] flandy7:
I have a problem using the busybox from the Magisk because my stock firmware (MIUI 8) already has busybox, but the old version 1.13.3. When I choose "Enable BusyBox" after that in /system/xbin/ busybox remains stock, although the rest of the files are links to /data/magisk/busybox
[Magisk] rignfool:
Good... Please don't use this mod anymore... Kthnxbai
[Magisk] kinfam:
If you want help, you should post things such as:

Your phone?

Your rom?

Any custom kernels?

Any modifications other than magisk?

What modules do you have installed?

Have you tried reformatting your phone?

Logs?

Loose ranting isn't enough to go on.
[Magisk] jadajada:
Hi!

I am using S7 Edge on Nougat. I have installed TWRP and removed encryption. I wanted to install Magisk, and I flashed latest Magisk V. 11.1 zip from TWRP. Now I am in a bootloop. It boots to Samsung logo, and then reboots back to Samsung logo.

Did I miss a step?
[Magisk] githyanki:
Flash your rom, should fix bootloop.

Is your rom pre-rooted? You have to remove that before trying magisk.

Install the magisk app and see if you can get safety net to pass before installing the zip. That way you can make sure that you have removed root completely.
[Magisk] milesian:
It's not the end of Magisk. It's just the end of you.
[Magisk] :
Of course it's not the end of Magisk,since those problems will be solved at some point.But for now,I will use something else.

---------- Post added at 06:16 PM ---------- Previous post was at 06:15 PM ----------

Good to know,but I already moved to another solution.Thanks!

---------- Post added at 06:20 PM ---------- Previous post was at 06:16 PM ----------

I have stopped using it already,but I will be around to see what amazing things are added to this mod.
[Magisk] Zackptg5:
For anyone having issues with magisk suddenly saying that you're not rooted (when using magisksu), I think the problem is with the magisk manager. I've noticed that whenever I clear it from recents, this issue occurs. Hiding magisk manager from recents seems to prevent it from happening. Perhaps it should be made a system app in the future so it won't be killed by the system

Edit: There's more to it then this. This step still helps though
[Magisk] Captain_Throwback:
Made a system app? Seriously?
[Magisk] jhedfors:
Systemlessly, of course. LOL :laugh:
[Magisk] FreeTheWeb:
Is there any app that can control apps permissions like the modules from xposed for android 7+ and magisk
[Magisk] darkeyes22:
Delete phh's superuser manager and update magisk manager 4.1 8)
[Magisk] Nomelas:
No, actually a lot of people are having issues with root disappearing and other things since the release of magiskSU.

Some of us just can't wait patiently
[Magisk] jcrompton:
Is there any thing else we can try to make secondary ROMs work with Magisk Hide and ultimately pass SafetyNet??
[Magisk] humzaahmed155:
"Systemless root"

Lulwut
[Magisk] yochananmarqos:
Android Settings > Apps > App Permissions
[Magisk] Artim_96:
No, that's impossible. Either it's backed into the system or its archived by heavily modifying the apps Java code and the system to not "optimize these changes away". That's not what's Magisk built for. You'll have to use XPosed for that.
[Magisk] Hadookie:
Any Viper module out there working with 6P on latest PN, Franco kernel and latest Magisk? Last two I've tried have caused me bootloops which only full wipes could fix. Tried restoring a nandroid backup but somehow needed an encryption key afterwards to mount my partitions which I never set....
[Magisk] pranayysharma29:
More often than not, after a reboot magisk root fails to activate. I get no toast/notification for it so I don't get to know until I either open magisk manager or another app that requires root. Reboot fixes this.

Attaching screenshot.

Edit - device oneplus 2 running Resurrection remix.
[Magisk] Didgeridoohan:
Next time it happens, boot into TWRP and copy the Magisk log from /cache. It'll tell us a bit more (hopefully) than a screenshot.
[Magisk] luly:
New Magisk Update is forceclosing on my S7 Edge, after updating from Play Store.....
[Magisk] thinkingrobot:
Anyone can share their exact flashing order/procedure from stock 4.0.3 rom to Dirty Unicorns v11.1 RC with Magisk v11.1 on Oneplus 3T? Thanks!

I have no problem getting the DU ROM working (with phh superuser root or without) but once I flashed Magisk v11.1, it won't boot, stuck on the Oneplus Boot Logo screen forever. :(

BTW. I'm using blu_spark/eng.stk's TWRP
[Magisk] yochananmarqos:
Magisk does not touch /system. Flash the mount Magisk module in TWRP and delete the module directory.
[Magisk] pranayysharma29:
Will do that. Didn't know where to find them. Thanks!
[Magisk] zenyman:
need help installing magisk.. the problem is when i try flashing the magisk via twrp and magisk manager app then rebooting, it only boots in recovery , it wont boot in the main system... already tried clean install. wipe/format .. using lineage os 14.1 nighties build..
[Magisk] Nomelas:
See attached
[Magisk] Arju:
Nexus 6
[Magisk] _litz:
I have tried 11.1 (and a v12 test magisk compiled from the latest source) on both a nexus 9 and a moto x pure.

Both have a fatally flawed root. With magiskhide enabled, root works for at most 1/2 a day, maybe a full day, then magisk loses root and fails to work until the device is rebooted.

The exact same devices functioned perfectly under 10.2 ... so something has been broken in between 10.2 and 11.1.

The lack of reliable root is crippling, so I've had to revert back to 10.2 until this is resolved.
[Magisk] garthybarthy:
4.2 also fc on s6 flat.
[Magisk] swordzmega:
Magisk Manager v4.2 FC when xposed is enabled, but works fine when I disable xposed. Galaxy Note4 (SM-N910F).
[Magisk] aldanopolis:
su logs, on command section always show /system/bin/sh, instead the executed command. Is that a bug?

Sorry for the english

Enviado desde mi Moto G mediante Tapatalk
[Magisk] nek46:
Ice rom nougat, htc m9 all ok with new version magisk:)
[Magisk] jadajada:
I was using stock rom on S7 Edge with stock kernel. I found out that Magisk does not work with stock kernel. Two of the apps I use everyday perform some kind of kernel detection. They will not launch with any custom kernel, I have tried Magisk + Magisk Hide also, but it's the kernel itself which is the problem. So my stock kernel was the problem for Magisk.
[Magisk] Didgeridoohan:
I asked you a question about this in the unofficial build thread. This is probably a better place for it though... I'm gonna copy pasta:

Did you try removing the app from recents (swiping it away) and then opening it again? There has been reports about this working...

---------- Post added at 10:56 ---------- Previous post was at 10:43 ----------

It looks like Magisk hide is going a bit crazy on your device... Could you try disabling Hide and see if this fixes the issue?

Edit: and by the way: is that log from right after a reboot, when you've noticed root isn't working?
[Magisk] koko115:
Fc on s7 edge
[Magisk] lahceneamine:
I confirm, got FC (doesn't even launch) with the new Magisk Manager v4.2 on S7 Edge MM.

Tried a clean install, didn't work either.

Installed from the Play Store.

Edit:

It seems that the issue have already been reported, my bad.
[Magisk] civato:
magisk without a build-in root.

I would love to see a magisk without a build-in root. Some apps still are able to detect it, so I cannot use this anymore.

The previous version where you could install without build-in root where better for me.

Here you find a solution
[Magisk] Nomelas:
Yeah
[Magisk] lahceneamine:
I'm sorry, I didn't understand, a solution for what exactly ?
[Magisk] reas0n:
Did anyone managed MagiskSU to work on Xiaomi Mi5 with LOS? Magisk Manager is showing no root no mather what I was doing.
[Magisk] luly:
Same here, I went back to 4.1, flashon zip trough recovery.
[Magisk] Ashwa:
I am unable to update 11.1 from v9. Updater is not installing. I tried in recovery ( twrp3.1) unable to update the zip getting a error 1. Unable to mount su image.

I am on latest dev preview of nougat with Nexus 5x.
[Magisk] Danny94:
Magisk is causing bootloops on Meizu m3 mini with Flyme 5.1.5.0G OS (based on android 5 i think ). Anyone has an idee how to fix it please ? Else Pogo doesn't work and we bought it just to play that game.
[Magisk] swordzmega:
Yeah. I just reinstalled v4.1 apk. Hopefully this problem will be dealt with soon.
[Magisk] ConnerJSP:
SOLVED: Root access fix for cm file manager- https://xdaforums.com/showpost.php?p=71105448&postcount=9335

Hey I'm currently facing the same issue with cm file manager, no root access. I'm curious about the apps having hard coded su paths. There was a solution to fix the permissions using this code:

su

mount -o remount, rw /system

ln -s /su/ bin/su /system/xbin/su

mount -o remount, ro /system​

I'm guessing we could write a symlink to where su is installed using magisk instead of /system/xbin/su to make it follow the correct path? I would need to know where the su is for magisk, is it located here: /magisk/.core/su/su?
[Magisk] luly:
Jepp, only thing is that I had problems with Viper 4 Android after the force close.

I had to delete it woth Titanium and reinstall Viper from Magisk 4.1, then delete cache and dalvik trough recovery to get it working again.

The driver showed abnormal status until I did this.
[Magisk] bam80:
Sony

[MENTION=4470081]topjohnwu[/MENTION] what is the problem with Sony? There are many apps editing Sony's ELF kernel exist, here is one: [ROOT][Kernel][TWRP] repack of the stock kernel with dm-verity and SONY RIC off
[Magisk] ishtiz:
magisk on ASUS ZenFone 2 z008 with lineage 14.1

i tried flashing magisk v 11.1 on my z008 (as it would help me play pokemon go again and also use tasker) it flashed well and viewed everything successful but my device dint reboot to system ...it rebooted everytime to the twrp recovery.....so i had to again flash the lineage rom!

So is there a way i can use magisk?or did i do something wrong or miss anything out?
[Magisk] swordzmega:
Glad to hear you got that issue taken care of. I haven't had any problems since reverting back to v4.1. So, freakin' yay!
[Magisk] Jv1391:
Hello, I need help:

IF I clean install Magisk 11 in Magisk Manager it appears MagiskSu BUT it says I have to install Magisk everytime: even if I already installed it obviously to have magiskSu.

If I use Supersu SR3 it displays Supersu correctly and Magisks 11.1 correctly installed.

BUT I wanna to install magisk without supersu just flashing the zip to have magisksu...

I'm on GS5 6.0.1
[Magisk] yochananmarqos:
No, it's /sbin/su.
[Magisk] LucentBirch:
Anyone still losing root randomly?
[Magisk] ShadowElite:
Hi to all, I'm a kernel developer, and I successfully passed Safety Net with my custom kernel on Xperia Z2, using magisk v11, but when I enable magiskhide after some time the device reboots and it still rebooting until I disable magiskhide, anyone can support me?
[Magisk] Artim_96:
Not without some logs

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

Then don't root it if you only bought it to play PoGo...

No one knows when Google decides to also kill off Magisk, it might never happen but it could theoretically happen every day.

---------- Post added at 10:53 PM ---------- Previous post was at 10:51 PM ----------

What about completely removing it and start fresh? In the worst case reflash your boot.img, a backup is stored in /data
[Magisk] Danny94:
[MENTION=5125527]Artim_96[/MENTION]

-.- i would'nt do if it works withouth.
[Magisk] Artim_96:
Well, if it won't work without, then it will probably not with
[Magisk] phen0m2016:
Hi,

I just updated from Magisk v10.2 to Magisk v11.1 using Magisk Manager v4.2. Previously I also had phh's SuperUser 2.0 [Beta 11] installed, but after the update it disappeared, except the App Icon. Now the SuperUser Requests are managed by MagiskSU.

Do I need to do something extra in order to fully remove phh's SuperUser 2.0 [Beta 11]?? (In case I want to return my phone to Stock, for example)
[Magisk] Artim_96:
Remove the app to avoid interferences. Or freeze it is you have apps that refuse to detect root unless they see the app.

To go back to stock just flash your stock ROM (and run the Magisk uninstaller before).
[Magisk] _litz:
Tested this ... it appears that swiping it away does not help.

Force closing, and wiping cache, then relaunching Magisk Manager, however, does seem to restore it to being able to detect things correctly, and also appears to restore root.

Edit: Just saw new Magisk Manager released yesterday. Trying that now.
[Magisk] Nomelas:
Issue persists on new manager released yesterday.

Not sure what the gms.unstable app is but I disabled the ViPER4Android module to see if that helped
[Magisk] kryptikal:
Thanks for the continued support [MENTION=4470081]topjohnwu[/MENTION]

Donated: 6KP744630E991312W
[Magisk] chjun90:
changes can't be restore to default after removing system.prop

Latest Magisk Version: v11.1

Latest Magisk Manager Version: v4.2

oneplus 3 Oxygen 4.0.3

changes can't be restore to default after removing system.prop. i can only do it making a default changes in system.prop to restore to default.
[Magisk] Didgeridoohan:
Ok. That's probably useful information, I think... Was it necessary to wipe cache? It wasn't enough with force closing?

That's Magisk Hide bypassing SafetyNet. The log shouldn't be full of updates to the process list though... Especially with a process that you as a user has no controll over. Yeah, try without V4A and if that doesn't work without Magisk Hide.

What do you mean by "removing system.prop"? Uninstalling the module and rebooting? That always resets the prop values I've changed with a module to deafults...
[Magisk] ConnerJSP:
CM File Manager root access fix

I had an issue with the Cyanogenmod file manager not having an option for root access. Although it is a dying brand, already dead rather, this may still may help similar problems. Thanks to

yochananmarqos

for the final step!

Short explanation: the file manager looks for su in a certain folder that is created with CM's built-in root. Therefore, it is necessary to write a symlink in order for the app to find a different su the user has installed, on a custom rom.

These are the commands entered into terminal using Sultan's CM13 with Chainfire's SuperSU:

su
mount -o remount,rw /system
ln -s /su/bin/su /system/xbin/su
mount -o remount,ro /system

And the commands also with Sultan's CM13 but with MagiskSU:

su
mount -o remount,rw /system
ln -s /sbin/su /system/xbin/su
mount -o remount,ro /system

Hope this helps whoever may need it.
[Magisk] str8str:
Having issue getting safety net to stop checking. No pass or fail just keeps checking. Logs say Google android gms unstable. Anyone know what's happening?

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

I downloaded safety net check app and the cts profit match fails. I have nothing installed except aicp rom and latest magisk fresh flash no super su arise, etc. Using n6
[Magisk] topjohnwu:
Nice. Samsung devices always bring surprises.

Magisk Manager works just fine on most devices, while crashes immediately on Samsung devices.

Viewing logs from Play Store shows that the crash doesn't happen in code I've written......

And I get tons of negative reviews, thanks to this crash.

Great job Samsung, you wanna force developers to buy your devices, only to test if the code will work properly on your product.

And this is just a sad and unfortunate truth of this Android platform, applications build with official IDE (Android Studio) does not behave like you expected on one device to another.

I'll push a small update to resolve some issues, not sure how long it will take as school starts today.
[Magisk] kerbiii:
the new magisk manager is force closing when i open it
[Magisk] _litz:
Probably only needs force close ... I usually wipe cache on the app too, just out of habit ... note that's wipe cache, not wipe data.
[Magisk] SoundGuy_025:
Yep. Did the trick. Thanks. Shame it can't work with SuperSU though.
[Magisk] FantasyFlow:
+1, same issue.

Just updated my rom, reflashed twrp and magisk. Root seems ok but Titanium Backup (TiB) freezes at 0% during restore operation.

Everything works fine before the update:crying:

P.S: I read in the OP thread that we need to mount system before using TiB... But how?:eek:

------------------------------------------------

Update 20170221: Solved...

1. Uninstall Magisk using the provided zip

2. Install latest SuperSU in systemless mode through TWRP. I looked at the log, it said "systemless", although I do not know how to enable systemless flashing or check if it is indeed systemless *noob*

3. Restart to system.

4. Checked in Magisk Manager : properly rooted with SuperSU.

5. Flashed Magisk 11.1 through Manager.

6. Reboot to system.

Titanium Backup now works normally.

One downside is that SafetyNet fails even with suhide 0.55
[Magisk] MandoH:
I'm on Stock 7.1.1, stock kernel, What is the proper way to install Majisk? N6.

Flash Majisk 11.1,

Installed Majisk Manager.

Where do I find the MajiskSU zip?.
[Magisk] FantasyFlow:
Afaik, MagiskSU is included in the zip as long as you don't have SuperSU systemless flashed before that.

I followed the same route as you, installed magisk from stock.

Just that, I installed TWRP with no-dm-verity... and then flashed Magisk 11.1. Device is rooted with MagiskSU

Stock recovery should be able to install Magisk zip.
[Magisk] MandoH:
Flashed 11.1zip in TWRP and get a message saying to flash super user to complete installation?. Idk. New to this Majisk.
[Magisk] Ashwa:
[MENTION=5125527]Artim_96[/MENTION] I can't find a boot image backup in /data there is only Magisk.img in /data root. Is this boot image or do I have look some where for original boot image. Unfortunately I deleted the stock boot image backup from twrp

[
[Magisk] Didgeridoohan:
https://xdaforums.com/showpost.php?p=70426733&postcount=7120

Sigh... Look above you...

You didn't properly uninstall SuperSU and your boot image is still patched. Extract the boot image from your corresponding factory image and reflash.
[Magisk] reis1996:
Magisk hide NOT WORKING!!!!

Pokemon go logged in even after safety net failed. Pokemon go not logging in after flashing magisk 11.1

Using magisk manager 4.2

Tried disable/enable then restart the magisk hide interface.

Someone told me this is a magisk issue please see the log

Using a galaxy note 2 n7100

Running Lineage os ( a version that came out last month which had removed root access)

Safety net failed after clean flash and failed after installing magisk11.1 too.

NO SuperSU installed ever
[Magisk] darkeyes22:
It can. Delete magisk completely, flash systemless superSU and flash Magisk then.

Note: MagiskHide won't work with SuperSU.
[Magisk] FantasyFlow:
Hmm that is strange... I also flashed using TWRP but no such message.

Is your device rooted before updating?

Anyway, download Magisk Manager and check your installation + root status.

If it fails, you can try flashing the Magisk Uninstaller zip and reinstall.

There are multiple ways to get this done, depending on what your root solution is.

You either choose:

1. Systemless SuperSU

2. MagiskSU > included in the zip. If 1 exists, the zip will not install MagiskSU.

3. If both 1 and 2 do not exist, the zip will install MagiskSU by default.
[Magisk] Artim_96:
As long as you haven't deleted that too, there should be a stock_boot.img in /data
[Magisk] Didgeridoohan:
It works, if your device and system is otherwise compatible. Lately I haven't seen anyone reporting success with LineageOS.

Not strange, see my answer in post #9346
[Magisk] IzaacJ:
Started to experience weird behaviour on my Moto G3 running latest RR (full unroot w/ supersu before Magisk install) and Magisk 11.1. Root does work for about 3-4 minutes after reboot, then it's gone until I do a full reboot. This happens with both stock kernel and FireKernel. The device passes SN so I doubt theres some leftovers of the original su in the ROM.

Wiped system, data, internal storage and restored stock boot on every reinstallation to try and troubleshoot this, but w/o any luck.

Any ideas?
[Magisk] kerbiii:
yeah just notice it after i post,
[Magisk] reis1996:
It doesn't work on my mm ROM either
[Magisk] Didgeridoohan:
What happens if you force close the Manager instead of rebooting?
[Magisk] chjun90:
i just removed the system.prop but it turns out nothing happend. Only i can do it is making a converse changed system.prop to restore to defaul.
[Magisk] SoundGuy_025:
Yeah. I meant with MagiskHide. I read the developer can't because SuperSU isn't open source.
[Magisk] Didgeridoohan:
Wait, what!? Start from the beginning... What have you done to start with and what are you trying to accomplish? In as much detail as possible.

If you have a Magisk module changing props with system.prop, you revert those props to default by disabling or uninstalling the module (in the Manager) and rebooting.
[Magisk] chjun90:
for example:thers is a prop i do in the system.prop like persist.sys.oem.region=Overseas where it is persist.sys.oem.region=CN in the default build.prop. After i removed the prop or system.prop file and reboot it can't reset to persist.sys.oem.region=CN. I just make persist.sys.oem.region=CN in system.prop to reset it. I found that persist.* cause the problem...