yashsingh1/xdaforums huggingface dataset:
[Magisk] DaniloFerracini:
I flash the latest build dirty flash:

-Google camera dont work;

-Snapdragon camera works (video recording bug still exist, freeze on 55", any tips?)
[Magisk] La1x:
Getting problem with safetynet test on magisk 13. Errors after tap "The response is invalid" and "Cannot check SafetyNet, no internet?", but internet connection is ok. Any ideas?

Custom LOS14.1, Meizu M2 mini.
[Magisk] tdunham:
This happened to me as well on this latest beta but worked the next time I tried it. Reboot or clear data on the app and try again.
[Magisk] saayairie:
magisk manager v5.x crashes on Android 6.0.1 arm64

F/libc (23511): invalid address or address of corrupt block 0x10804c2 passed to dlfree
F/libc (23511): Fatal signal 11 (SIGSEGV), code 2, fault addr 0xdeadbaad in tid 23511 (opjohnwu.magisk)
F/DEBUG (406): *** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
F/DEBUG (406): LineageOS Version: '13.0-20170505-UNOFFICIAL-kenzo'
F/DEBUG (406): Build fingerprint: 'Xiaomi/kenzo/kenzo:6.0.1/MMB29M/6.7.21:user/release-keys'
F/DEBUG (406): Revision: '0'
F/DEBUG (406): ABI: 'arm'
F/DEBUG (406): pid: 23511, tid: 23511, name: opjohnwu.magisk >>> com.topjohnwu.magisk <<<
F/DEBUG (406): signal 11 (SIGSEGV), code 2 (SEGV_ACCERR), fault addr 0xdeadbaad
F/DEBUG (406): Abort message: 'invalid address or address of corrupt block 0x10804c2 passed to dlfree'
F/DEBUG (406): r0 00000000 r1 00000000 r2 00000000 r3 00000002
F/DEBUG (406): r4 010804c2 r5 deadbaad r6 f7001f38 r7 a4932000
F/DEBUG (406): r8 010804ca r9 ff80bf7c sl f6f63993 fp f6f6399c
F/DEBUG (406): ip f6ffc5d8 sp ff80be68 lr f6fcdc85 pc f6fcdc84 cpsr 600f0030
F/DEBUG (406):
F/DEBUG (406): backtrace:
F/DEBUG (406): #00 pc 00030c84 /system/lib/libc.so (dlfree+1287)
F/DEBUG (406): #01 pc 000157cd /system/lib/libandroidfw.so (_ZN7android13ResStringPool6uninitEv+38)
F/DEBUG (406): #02 pc 0001651d /system/lib/libandroidfw.so (_ZN7android10ResXMLTree6uninitEv+14)
F/DEBUG (406): #03 pc 0001653b /system/lib/libandroidfw.so (_ZN7android10ResXMLTreeD1Ev+4)
F/DEBUG (406): #04 pc 00013267 /system/lib/libandroidfw.so (_ZN7android12AssetManager10getPkgNameEPKc+258)
F/DEBUG (406): #05 pc 000132c3 /system/lib/libandroidfw.so (_ZN7android12AssetManager18getBasePackageNameEj+62)
F/DEBUG (406): #06 pc 00088a1b /system/lib/libandroid_runtime.so
F/DEBUG (406): #07 pc 73b0cc71 /data/dalvik-cache/arm/system@framework@boot.oat (offset 0x1fbf000)
F/DEBUG (406):
F/DEBUG (406): Tombstone written to: /data/tombstones/tombstone_00
E/DEBUG (406): AM write failed: Broken pipe
[Magisk] Spiricore:
I was one of the people reporting the LONG flash times on previous betas -- 54e6a79 wasn't a problem! :good::highfive:

Although my Galaxy Note5 seems to be struggling with performance now. I'll report back if I can figure out if anything else is causing it.
[Magisk] Super_Vegito07:
I just installed v 12 over 13 and then safety net passed thanks for sharing your views anyway.
[Magisk] ahgt4:
cts mismatch

View attachment magisk_error_20170624_223848.log
[Magisk] imna357:
Thanks a lot...worked the first try...hope it'll stick. I am a supporter of your Magisk 12=) EXCELLENT job
[Magisk] Kris Chen:
Xiaomi Redmi Note4X pass SNC

It's amazing that Xiaomi Redmi Note4x pass SafetyNet Check even without the module of Universal SafetyNet Fix.Thanks !

P.S.

My Rom is RR official version - 0618.
[Magisk] mikevb:
Just uninstalled previous beta (passed both SafetyNet checks), installed 54e6a79, not passing either check now. Nexus 6 stock 7.0.

Accidentally turned off Magisk Hide. All good here!
[Magisk] jhedfors:
Please do not paste logs - instead attach them. Thanks.

(Painful scrolling on mobile)
[Magisk] Fen-X:
Edit : I m using omnirom 6.0.1 (20161124 build). Now i've just tested with omnirom 7.1.2 and the last magisk beta buid run (no problem). Maybe the issue come from the changes of the new magisk beta build. Will stay on (96f8efc) until a new update.

Thanks for your work.
[Magisk] khanjui:
The thing is, it does not pass on MIUI.
[Magisk] :
Latest beta failing cts AND basic integrity on Resurrection Remix 5.8.3
[Magisk] apophis9283:
I'm on RR and it works perfectly. Since you didn't say anything about device or setup, I'm gonna assume it's something you're doing
[Magisk] :
Well, I have installed Resurrection Remix on YU Yureka+ (tomato). No mods flashed, a custom kernel. Basically, the setup is the same as the last beta, which passed both checks. [emoji17]
[Magisk] apophis9283:
Thank you. Have you tried a clean flash? Or uninstall magisk, then flash your kernel, then reflash magisk.
[Magisk] :
No. But now that you've pointed it out to me, I'll try some basic troubleshooting steps. [emoji16]
[Magisk] appman1234:
What rom are you using?
[Magisk] apophis9283:
I wasn't trying to be an a**. I think this thread would be a lot smaller if people tried basic troubleshooting first, if that fails, give as many details as possible. Given that there are soooo many people in this thread, if you absolutely can't get it to work and its outside of the known issues. Send me a message on Hangouts and I will help you when I get a chance. My Hangouts is steaven.android@gmail.com. at least taking it there, takes it out of the thread. No promises but I will do my best.
[Magisk] Papabendi:
Working fine on my Samsung Galaxy S8. Works perfect. Safety net passed
[Magisk] combat44:
I use Call Recorder to record calls. It has the function to start recording an outgoing call after the subscriber answers. When using Magisk, this function does not work. Can you fix it?
[Magisk] Vipery:
Flashed again my rom, uninstalled all modules just kept Magisk v13 last build. Uninstalled also Xposed Manager and Viper app. Still can't pass safety net. My boot.img is clearly modded also because it's patched when I flash the kernel.
[Magisk] Papabendi:
I had to restore my stock boot image before flashing Magisk v13
[Magisk] EViollet:
Hi. No problems here with latest Magisk beta version. Call recorder is working as it should.
[Magisk] Papabendi:
Yep not even getting any of the bugs after install. Good job.
[Magisk] wartomato:
Well, maybe mention your ROM? I assume you are on MM 6.0.1?

Well it works flawlessly on 7.1.x with viper, AdBlock, yr block and a custom kernel...

...since "day one". ;)
[Magisk] Vipery:
I am on MM 6.0 LG G4 H815 with Imperium Rom and Kernel.
[Magisk] wartomato:
Afaik this is a pre-rooted, modded stock ROM.

It has Magisk or SuperSU for giving root access. Assuming the magisk v12 worked with your ROM and your modules fine, why not wait for your ROM dev to get it working in his ROM and custom kernel?
[Magisk] Windforce0511:
Ultra fast installation on Galaxy S6. Working great so far! Anyone got Viper4Android working?
[Magisk] j-a-c-k:
Magisk hide is not working

Hi.

The latest version of Magisk (54e6a79) has the Magisk hide function broken.

Symptoms:

1. After boot Bluetooth stays disabled

2. Safety Net check completely failed

3. Have to run magiskhide --enable manually

4. After #3 any application from hidelist startup takes ages

See the logs attached.

Meanwhile reverting to v12 :(
[Magisk] Deep-Knight:
Xiaomi Redmi4x MagsikHide wont work

Redmi 4x 7.6.22 (Nougat) MagiskHide wont work. Gives an app root access dialog even it is listed for hide...

MagiskHide enabled, rebooted twice... Magisk Hide seems to start, and then i crashed...

--------- beginning of main
D( 423: 423) client: connect fail, try launching new daemon process
I( 424: 424) Magisk v13.0(54e6a79) daemon started
D( 424: 425) sepol: Starting large patch thread
I( 424: 426) ** post-fs mode running
--------- beginning of system
D( 424: 425) sepol: Large patch done
I( 424: 675) ** post-fs-data mode running
I( 424: 675) * Mounting /data/magisk.img
I( 424: 675) * Running post-fs-data.d scripts
I( 424: 812) ** late_start service mode running
I( 424: 812) * Running service.d scripts
D( 424: 812) resetprop: New prop [ro.magisk.disable]
D( 424: 812) resetprop: setprop [ro.magisk.disable]: [1] by property_service
--------- beginning of crash
D( 424: 5551) su: request from client: 9
D( 424: 5551) su: request from uid=[10258] (#1)
D( 424: 5552) su: collector started
D( 424: 5551) su_db: query root_access=[1]
D( 424: 5551) su: wait_result waiting for 5554
D( 5554: 5554) su: child process started
D( 5554: 5554) su: use namespace of pid=[5543]
D( 5554: 5554) su: argc=[2]
D( 5554: 5554) su: argv[0]=[su]
D( 5554: 5554) su: argv[1]=[-v]
D( 5554: 5554) su: cwd=[/]
D( 5554: 5554) su: pts_slave=[]
D( 424: 5551) su: return code to client: 0
D( 424: 5578) su: request from client: 7
D( 424: 5578) su: request from uid=[10258] (#1)
D( 424: 5578) su: wait_result waiting for 5580
D( 5580: 5580) su: child process started
D( 5580: 5580) su: use namespace of pid=[5555]
D( 5580: 5580) su: argc=[1]
D( 5580: 5580) su: argv[0]=[su]
D( 5580: 5580) su: cwd=[/]
D( 5580: 5580) su: pts_slave=[]
D( 424: 6544) su: request from client: 9
D( 424: 6544) su: request from uid=[10258] (#1)
D( 424: 6544) su_db: query root_access=[1]
D( 424: 6544) su: wait_result waiting for 6546
D( 6546: 6546) su: child process started
D( 6546: 6546) su: use namespace of pid=[6529]
D( 6546: 6546) su: argc=[2]
D( 6546: 6546) su: argv[0]=[su]
D( 6546: 6546) su: argv[1]=[-v]
D( 6546: 6546) su: cwd=[/]
D( 6546: 6546) su: pts_slave=[]
D( 424: 6544) su: return code to client: 0
[Magisk] anttaz:
Need set kernel to permissive with module and V4A working
[Magisk] h1nnak:
Samsung Galaxy S6 Flat (G920F)

Everything works great.

1. Delete magisk manager

2. Reboot into recovery

3. Flashing magisk uninstaller

4. Flashing newest beta of magisk v13... (54e6a79)

5. Reboot

6. Starting manager - cts & basic failed

7. Reboot

8. Starting manager - cts and basic TRUE

Great work, thumb up ?
[Magisk] Illutorium:
But Uninstall "Magisk Manager of Stable" it's a optional anyway... But Reboot might be helped when "SafetyNet bypass for LineageOS" of Stock it's not a depend if be pass.
[Magisk] kramer04:
i try the latest 54e6a79

root is ok

cts profile : false

basicIntegrity : true

phone : Samsung Galaxy Note 3 SM-N9005 HLTE

ROM : AspireTeam C9 PRO

kernel : Phantom 1.2k

Edit : with Universal SafetyNet Fix all is ok
[Magisk] Deep-Knight:
If you are rooted and basicIntegrity is true, magisk hide is working. For CTS Profile fales

you can try Module : https://xdaforums.com/apps/magisk/xiaomi-safetynet-fix-t3600431
[Magisk] Windforce0511:
Which module for permissive kernel?

Btw I have bootloop on Galaxy S6 logo after flashing V4A module.
[Magisk] witekkowal:
Everything works perfect on Samsung S5, especially survive addon. I flashed again the rom and magisk is still there :)

Wysłane z mojego SM-G900F przy użyciu Tapatalka
[Magisk] combat44:
Sorry for my bad english. I'll try to explain.

There is a problem.

Now:

Dialing a number - Calling - Recording ON - Sending beeps - Answer the caller.

Should be:

Dialing a number - Calling - Sending beeps - Answer the caller - Recording ON.
[Magisk] kramer04:
Edit 2 :I've randomly pass safetynet. Now it says the response is invalid

Edit 3 : all is fine with Universal SafetyNet v2 beta 1
[Magisk] JpegXguy:
Using a Huawei P8 Lite (ALE-L21), on EMUI 4.0.3 (Marshmallow)

Had previous beta with modified script (otherwise install failed with error 1 in TWRP)

- Flashed uninstaller zip

- Flashed Magisk-v13.0(54e6a79).zip with no problems

Magisk Hide is on

SafetyNet check

:

ctsProfile: false

basicIntegrity: true
[Magisk] ShadySquirrel:
Huawei Honor 5X on Lineage. Flashed original V4A module OP made, and added a fix for SELinux, works like a charm. Backup and try on S6
[Magisk] jenslody:
54e6a79 does not work on J5 with latest MarshMallow.

Unisntalled MagiskManager, uninstalled previous beta and flashed stock boot.img to be sure.

Wiped Dalvik and rebooted.

Boot in TWRP again.

Flashed 54e6a79-beta (no error) and rebooted: no MagiskManager, no root seen in RootVerifier.

Flashing modified 96f8efc works.

I attach recovery.log for both installs.

I also run logcat while booting, but with 54e6a79 magisk is not even mentioned anywhere in the log.

Just to mention: dirty flash does not work either.

EDIT:

Installing MagiskManager before or after flashing did not work.

I added the first 100 lines of the boot-logs, where the difference can be seen.
[Magisk] tdunham:
It appears the app is still having some issues installing for some and you wont have root unless manager is installed. As a mentioned workaround, extract the apk from the zip and install as a normal app.
[Magisk] gil80:
Hi all. Using OnePlus One. 6.0.1, SultanRom. Seems to be working fine except Viper4Android. Can anyone help with this one?
[Magisk] EViollet:
Ok. Sorry for the misunderstanding.

To be honest, I never looked at WHEN recording really starts. All that matters to me is that it records... :cyclops:
[Magisk] Spartacus500:
Before downloading the new version of Magisk, I do not use any modules. First thing is that all the sliders in the magisk manager on off, then delete the cache and the application data magisk manager, then remove the magisk manager application. Once in TWRP I am uploading a magisk uninstaller, then reboot system and boot loop ... Once to TWRP and install the latest version v13 (54 ..) reboot system and everything works great :) Samsung Galaxy S7 edge nougat 7.0.
[Magisk] :
[MENTION=4470081]topjohnwu[/MENTION]

I've to update myself: addon.d survival support isn't working with my OnePlus 3 (arm64) - magisk root doesn't survive after flashing new rom nightly Funny thing, addon.d survival support with my Nexus 4 (arm) is working fine. Both devices have latest LineageOS on board.
[Magisk] ShadySquirrel:
App gives you Abnormal as status? Check first post here
[Magisk] Lordsinko:
Hey all got magisk 13 to work on samsung galaxy s6 sm-g920I with safetynet bypass pass i used arter kernel97 and magisk 13 stock 6.0.1rom also pokemon go works with latest update :)
[Magisk] counterfeit187:
I was getting "failed to load cards" from pixel launcher for the past 2 days, before updating to latest beta. Coincidence? It literally fixed as soon as I flashed.
[Magisk] will5:
Tried to flash magisk on note 4 910t and didnt work (using beastmode kernel) Only works with stock kernel.
[Magisk] tdunham:
Are you sure you flashed ONLY the kernel? He (and most kernel developers) have to include root with their flashables. You need to extract the custom boot.img or edit the installer to prevent root from installing, it will conflict.
[Magisk] gil80:
I tried it. It doesn't work. Still Abnormal.

How come the V4A zip file is so low when downloading via Magisk? This file should be about 4MB.

Anyway, is there some other solution?

Must I use the file provided from the modules menu?
[Magisk] will5:
Hi, installed the complete kernel zip, the flashed unsu then magisk, but no luck.

Do you think I should flash boot.img and then magisk?

There are many libraries inside the .zip, not sure if will be ok to flash only boot.img.

Here is the beastmode updater script:

Do you know what should I edit to avoid root installing?

Thanks
[Magisk] SPARTAN_TECH:
Thanks this worked for me i must have over looked the post from page 113 i appreciate the help
[Magisk] tdunham:
Interesting.. I cant say if the other stuff is necessary for whatever build you are on but the second from last line is one that is necessary to just flash the kernel.

Remove all but this line and see how it goes.

package_extract_file("boot.img", "/dev/block/platform/msm_sdcc.1/by-name/boot");

---------- Post added at 01:48 PM ---------- Previous post was at 01:45 PM ----------

Also, I would still run the UnSU and magisk uninstallers too just to be certain it is a clean install; then kernel and magisk beta.
[Magisk] ShadySquirrel:
Weird, it works for me. Also I don't have any V4A modules in repo? so I'm using original topjonwu's module + V4A Materialised, just added that fix. That module is under 1MB, it doesn't provide app, just drivers and some settings.
[Magisk] Watanabe_You:
Hi, I am experiencing a series of crashes and the occasional bootloop with Magisk v13. Details are in here: https://github.com/topjohnwu/Magisk/issues/250

Maybe other devs may be able to check in case something can be fixed.
[Magisk] jenslody:
I tried this already, but forgot to mention it in my post. I edited it accordingly.

As I wrote magisk is not even seen while boot.

I attach the first 100 lines of the log from booting to my original post.

Magisk appears very early in the working version, but never in the non working.

I added shortened boot-logs to my first post.

If I use the update-binary from fixed 96f8efc (see: beta tracking thread) it works.

So it must be something in the new update-binary which does not work correctly on all phones.
[Magisk] zukmabawls:
My Moto G4 does not boot after flashing... just a black screen, with a white flashing led if i've got a datacable connected. Gotta restore backup to get it to boot again. :(
[Magisk] demonoidmaster:
You know you can activate pro for free on SuperSU right? There's no point in paying for it, it's only like a donation, you're not obligated to pony up money
[Magisk] Apollopt:
Flashing the zip in custom recovery fails

Hello Guys,

I tried to flash already a few times but I have always the same error as you can see below.

I even completely format and just install a new ROM (https://xdaforums.com/galaxy-s5/development/rom-ane4-kitkat-4-4-2-multi-csc-t2813628), but still same issue.

Please check the attached error (printscreen)

Thanks in advance.
[Magisk] tdunham:
Bad download? Or try a newer version of twrp if it is available for you.
[Magisk] hiimpig1:
Look like magisk.apk from last 3 build only crash on MM ROM
[Magisk] digital0:
Latest magisk 54e6a79 installs, but no root (no su found). Log attached. I see in the log:

- Flashing new boot image

dd: /dev/block/mmcblk0p3: No space left on device
[Magisk] dahawthorne:
Wow. What an incredibly mean response. Quite apart from not answering the question asked, if you can't afford the price of a cup of coffee to support the many hours of the dev's work, how can you afford a smartphone...?
[Magisk] apophis9283:
I don't think chainfire gets the money from supersu pro anymore anyways
[Magisk] grego3140:
Hello,

I don't find MagiskManager.apk ?
[Magisk] DodoGTA:
Magisk Manager is now automatically installed when you flash the Magisk ZIP (If you didn't find Magisk Manager app after installing Magisk, then extract the APK (common/magisk.apk) from the Magisk ZIP and install the extracted APK)

Note: These things only apply to Magisk v13.0 beta builds
[Magisk] JERW28:
Everything is working fine on my moto G4 with the latest bata. Try reflashing your boot.img before flashing the latest bata (54e6a79). If that doesn't work, please give device details (see my signature if you want an example of what to provide). Also, please state the exact steps you took and attach logs. This will help pinpoint the problem.
[Magisk] laupuy:
Hi,

it's included the .zip

;)
[Magisk] grego3140:
The root don't work on SM-N9005, how can I open adb shell ?
[Magisk] Zeghio:
You can try to flash the unistaller and flash Magisk again ORR reboot 1-2 times, it sometimes happens (it bugs and doesnt show the modules installed) :silly:
[Magisk] bidav1:
Guys magisk manager crashes when going to superuser menu in manager.

Latest beta, g955n.

All other is working fine including safetynet.
[Magisk] Didgeridoohan:
https://xdaforums.com/apps/magisk/beta-magisk-v13-0-0980cb6-t3618589/post72793628#post72793628
[Magisk] preference:
Flashed (54e6a79) on a Galaxy Tab s2 running OMNIROM. I ended up failing SafetyNet check. Used the same Magisk Beta on my Nexus 6P running latest PureNexus, and everything passed. Is there something that can cause a safetynet fail inside our ROMs? Like, should I be bothering the developer of OMNI?

Thanks all.

EDIT: rebooted the galaxy tab s2 after putting coreonly mode, still failed. Rebooted it again after putting magisk into 'normal' mode and everything passed. Don't know what happened but please ignore my post.
[Magisk] Nevermindthelabel:
You don't need root to open adb shell, only if you call su. As long as adb is installed and working properly from your computer
[Magisk] gil80:
Where did you download this V4A from?
[Magisk] CharFalco:
I remember reading in the OP that Pixel/Pixel XL aren't yet supported. How about the Pixel C (dragon) tablet?
[Magisk] grego3140:
MagiskManager don't work for me ...

The safetycheck don't pass but the application don't see i'm root
[Magisk] some_shyguy:
I was having the same problem and after reading your post I did the same thing and had magisk working.

Much appreciated.
[Magisk] TheUndertaker21:
[MENTION=4470081]topjohnwu[/MENTION] , Hope you're having a great weekend.

latest beta breaks Samsung pay for gear 3. kept getting detected

but the previous version works fine, I know this isn't your priority but just wanted to let you know
[Magisk] Abort Retry Fail?:
LG G5 Fulmics ROM Helper Module

First of all kudos to topjohnwu for his continued magnificent work. The latest beta (54e6a79) is running perfectly on my LG G5 H850. I did notice that after flashing this beta xpirt's module of tweaks for Magisk had disappeared. I was able to track down the mysterious disappearance to the /magisk folder. After initially flashing Magisk (at xpirt's strong recommendation) while installing Fulmics a folder named "fulmics" was placed in /magisk. This folder was nowhere to be found after flashing the beta. I was able to solve the problem by copying the "fulmics" folder from the Fulmics installation to /magisk. After rebooting the Fulmics module reappeared in Magisk, specifically the "Fulmics ROM Helper." (The Fulmics ROM Helper module was bundled with the Fulmics installation ROM and does not appear as a Magisk Download.)

An alternate method to restore the module is to unzip the Fulmics ROM installation file, grab fulmics_helper.zip from /additions/magisk, and flash it with TWRP.
[Magisk] demonoidmaster:
When did i say I'm not in favor of supporting a dev? You didn't buy the pro version, all you did was donate, SuperSU can be pro-activated no matter if you donate or not, so it's not like you'd lose what you donated for

And no, it wasn't meant to be a "mean" response, but i sure asf ain't afraid to say stuff the way it is, truth hurts

---------- Post added at 01:51 AM ---------- Previous post was at 01:49 AM ----------

Wouldn't think he does, even though buying pro is a donation so maybe he does idk, it's his app afterall

---------- Post added at 01:53 AM ---------- Previous post was at 01:51 AM ----------

Uninstall Magisk, reflash it, check to make sure the /magisk folder is populated

Flash your modules via TWRP, check that they appear in /magisk and other files are still there. After that flash fulmics, check /magisk folder to be sure everything checks out

IF the whole /magisk folder is empty, only thing to blame is the fulmics thing you're trying to flash
[Magisk] gil80:
V4A keeps asking me to install the drivers every time I open the app.

I have downloaded viperfx-mkm-v4.1-magisk.zip and installed it via TWRP

I have copied the file 'vipersupportfix.sh' to the /.core/post-fs-data.d folder and gave the file -rwxr-xr-x permissions (this should be chmod 755).

But it doesn't help. After every reboot, it asks to install the drivers. I still have Abnormal status.

This used to work flawlessly with Magisk12.

Is there another installation method?

Is there any other solution?
[Magisk] apophis9283:
[MENTION=7086291]demonoidmaster[/MENTION] Thats what I am saying. SuperSU isnt Chainfires anymore. He sold it to some company....
[Magisk] demonoidmaster:
Ah i see, that i didn't know, thank you for the information
[Magisk] MitoTakatori:
Passing safety net on latest magisk. Device is S7 edge running Superman rom v2.5.0
[Magisk] ketwi15:
You had Samsung pay working? It's always failed for me.
[Magisk] Skittles9823:
Yes. Use ARISE Magnum Opus it sounds fantastic and has a thread to goto for support if you need it other then you going to a thread for a root tool and not the module thread.
[Magisk] TheUndertaker21:
https://xdaforums.com/showthread.php?t=3624869

If you have a gear 3 or gear smart watch yes.

It has been working on rooted devices for a while now.