Hello at June 2017 i used magisk and all works fine with magisk v12
In August it comes a Update and i updated my Manager and installed at the same Time xposed Installer But it Than it doesnt works until now
I tried so much things to fix that i deleted and deinstalled xposed, reinstalled magisk, used safetynet fix modules and deinstalled it because it doesnt works. I dont know what i can doing now cant Update my Google play Store or play any games or look netflix.
I Read ( https://forum.xda-developers.com/ap...leshooting-t3641417/post73145987#post73145987 )this guide but i cant fix it
I have a Samsung Galaxy S8+ (SM-G955F)
Android 7.0
ARMv8
Please help me
Logs... I like logs. I guess I need to move the "Asking for help" section to the beginning, because no-one seems to read that part of the guide... But now I'm rambling.
Anyway...
Did you have a functioning setup with SafetyNet passing before trying to install Xposed? Have you tried wiping your system and doing a clean install? You might have messed around too much...
Yea i wiped my Phone but it still dont works
>12-01 03:48:32.850 3127 3238 I Magisk : * Enabling systemless hosts file support
12-01 03:48:32.850 3127 3238 I Magisk : bind_mount: /sbin/.core/img/.core/hosts -> /system/etc/hosts
12-01 03:48:32.851 3127 3283 I Magisk : * Starting MagiskHide
12-01 03:48:32.851 3127 3283 I Magisk : hide_utils: Hiding sensitive props
12-01 03:48:32.852 3127 3283 I Magisk : hide_list: [com.google.android.gms.unstable]
12-01 03:48:32.866 3127 3283 I Magisk : hide_list: [com.netflix.mediaclient]
12-01 03:48:32.878 3127 3283 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-01 03:48:33.618 3127 3434 I Magisk : ** late_start service mode running
12-01 03:48:33.618 3127 3434 I Magisk : * Running service.d scripts
12-01 03:48:33.618 3127 3434 I Magisk : * Running module service scripts
12-01 03:48:44.522 3127 3283 I Magisk : proc_monitor: zygote ns=mnt:[4026533751] zygote64 ns=mnt:[4026533599]
12-01 03:49:16.316 3127 3283 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6584 ns=mnt:[4026533846])
12-01 03:50:41.248 3127 3283 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13261 ns=mnt:[4026533827])
12-01 03:54:12.673 3127 14029 I Magisk : * Stopping MagiskHide
12-01 03:54:14.464 3127 14037 I Magisk : * Starting MagiskHide
12-01 03:54:14.464 3127 14037 I Magisk : hide_utils: Hiding sensitive props
12-01 03:54:14.467 3127 14037 I Magisk : hide_list: [com.google.android.gms.unstable]
12-01 03:54:14.513 3127 14037 I Magisk : hide_list: [com.netflix.mediaclient]
12-01 03:54:14.559 3127 14037 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-01 03:54:16.661 3127 14037 I Magisk : proc_monitor: zygote ns=mnt:[4026533751] zygote64 ns=mnt:[4026533599]
12-01 03:54:19.089 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=14044 ns=mnt:[4026533827])
12-01 06:47:48.599 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=22126 ns=mnt:[4026533831])
12-01 07:01:59.425 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=25286 ns=mnt:[4026533859])
12-01 08:06:46.136 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=655 ns=mnt:[4026533854])
12-01 08:12:20.309 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=3269 ns=mnt:[4026533818])
12-01 11:46:12.321 3127 14037 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13881 ns=mnt:[4026533793])<
Thats my last logs
Upgraded to Magisk v15.0 and now when I run SafetyNet check I receive an API Error.
I am running Android 8.1 on Nexus 6P and have uninstalled Magisk using the Uninstaller and re-installed and still receive the same API error.
I've searched and read through quite a few threads and haven't come up with any fixes. Closest thing I found was a fix on the OnePlus forum.
Attached is a screenshot of the Magisk screen for reference.
Any help would be greatly appreciated.
Thanks in advance!
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
I had the same problem. I solved it by doing a clean install of Magisk (completely uninstall previous version, install new version).
J_M_V_S said:
I had the same problem. I solved it by doing a clean install of Magisk (completely uninstall previous version, install new version).
Click to expand...
Click to collapse
I tried this before and still received the error.
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
That worked! Thanks so much for the quick fix.
mandhir said:
I tried this before and still received the error.
That worked! Thanks so much for the quick fix.
Click to expand...
Click to collapse
Worked for me too!! Thanks a lot!
SafetyNet not passed
Samsung Galaxy S5 G-900F latest magisk 15.1 and magisk manager 5.5.2 SafetyNet not passed. Clean install, no problem on 14.0 version.
Code:
06-20 02:29:05.240 265 265 I Magisk : * Creating /sbin overlay
06-20 02:29:05.390 265 265 E Magisk : mount tmpfs->/sbin failed with 13: Permission denied
06-20 02:29:05.390 265 265 E Magisk : symlink /root/adbd->/sbin/adbd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/bgcompact->/sbin/bgcompact failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/emmc_quickverify->/sbin/emmc_quickverify failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ffu->/sbin/ffu failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/healthd->/sbin/healthd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/knox_changer->/sbin/knox_changer failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/sswap->/sbin/sswap failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ueventd->/sbin/ueventd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/watchdogd->/sbin/watchdogd failed with 17: File exists
06-20 02:29:05.390 265 265 I Magisk : * Mounting mirrors
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/system failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : mount: /sbin/.core/mirror/system
06-20 02:29:05.390 265 265 E Magisk : symlink /sbin/.core/mirror/system/vendor->/sbin/.core/mirror/vendor failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : link: /sbin/.core/mirror/vendor
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/bin failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : bind_mount: /sbin/.core/mirror/bin
06-20 02:29:05.390 265 265 I Magisk : * Setting up internal busybox
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/busybox failed with 30: Read-only file system
06-20 02:29:05.390 269 269 E Magisk : execvpe failed with 2: No such file or directory
06-20 02:29:05.390 269 269 E Magisk : symlink /sbin/.core/mirror/bin/busybox->/sbin/.core/busybox/busybox failed with 2: No such file or directory
06-20 02:29:05.390 269 269 I Magisk : Magisk v15.1(1510) daemon started
06-20 02:29:05.390 269 273 I Magisk : ** post-fs mode running
06-20 04:29:06.210 269 277 I Magisk : ** post-fs-data mode running
06-20 04:29:06.210 269 277 I Magisk : * Mounting /data/adb/magisk.img
06-20 04:29:06.210 269 277 E Magisk : mkdir_p /sbin/.core/img failed with 30: Read-only file system
06-20 04:29:06.340 269 277 I Magisk : * Running post-fs-data.d scripts
06-20 04:29:06.340 269 277 I Magisk : * Running module post-fs-data scripts
06-20 04:29:06.350 269 277 I Magisk : * Loading modules
06-20 04:29:06.350 269 289 I Magisk : * Starting MagiskHide
06-20 04:29:06.350 269 289 I Magisk : hide_utils: Hiding sensitive props
06-20 04:29:06.360 269 289 I Magisk : hide_list: [com.google.android.gms.unstable]
06-20 04:29:06.380 269 289 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-30 17:08:38.099 269 575 I Magisk : ** late_start service mode running
12-30 17:08:38.099 269 575 I Magisk : * Running service.d scripts
12-30 17:08:38.099 269 575 I Magisk : * Running module service scripts
12-30 17:08:42.049 269 289 I Magisk : proc_monitor: zygote ns=mnt:[4026534515]
mkdante381 said:
Samsung Galaxy S5 G-900F latest magisk 15.1 and magisk manager 5.5.2 SafetyNet not passed. Clean install, no problem on 14.0 version.
Code:
06-20 02:29:05.240 265 265 I Magisk : * Creating /sbin overlay
06-20 02:29:05.390 265 265 E Magisk : mount tmpfs->/sbin failed with 13: Permission denied
06-20 02:29:05.390 265 265 E Magisk : symlink /root/adbd->/sbin/adbd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/bgcompact->/sbin/bgcompact failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/emmc_quickverify->/sbin/emmc_quickverify failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ffu->/sbin/ffu failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/healthd->/sbin/healthd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/knox_changer->/sbin/knox_changer failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/sswap->/sbin/sswap failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/ueventd->/sbin/ueventd failed with 17: File exists
06-20 02:29:05.390 265 265 E Magisk : symlink /root/watchdogd->/sbin/watchdogd failed with 17: File exists
06-20 02:29:05.390 265 265 I Magisk : * Mounting mirrors
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/system failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /dev/block/platform/msm_sdcc.1/by-name/system->/sbin/.core/mirror/system failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : mount: /sbin/.core/mirror/system
06-20 02:29:05.390 265 265 E Magisk : symlink /sbin/.core/mirror/system/vendor->/sbin/.core/mirror/vendor failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : link: /sbin/.core/mirror/vendor
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/mirror/bin failed with 30: Read-only file system
06-20 02:29:05.390 265 265 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
06-20 02:29:05.390 265 265 I Magisk : bind_mount: /sbin/.core/mirror/bin
06-20 02:29:05.390 265 265 I Magisk : * Setting up internal busybox
06-20 02:29:05.390 265 265 E Magisk : mkdir_p /sbin/.core/busybox failed with 30: Read-only file system
06-20 02:29:05.390 269 269 E Magisk : execvpe failed with 2: No such file or directory
06-20 02:29:05.390 269 269 E Magisk : symlink /sbin/.core/mirror/bin/busybox->/sbin/.core/busybox/busybox failed with 2: No such file or directory
06-20 02:29:05.390 269 269 I Magisk : Magisk v15.1(1510) daemon started
06-20 02:29:05.390 269 273 I Magisk : ** post-fs mode running
06-20 04:29:06.210 269 277 I Magisk : ** post-fs-data mode running
06-20 04:29:06.210 269 277 I Magisk : * Mounting /data/adb/magisk.img
06-20 04:29:06.210 269 277 E Magisk : mkdir_p /sbin/.core/img failed with 30: Read-only file system
06-20 04:29:06.340 269 277 I Magisk : * Running post-fs-data.d scripts
06-20 04:29:06.340 269 277 I Magisk : * Running module post-fs-data scripts
06-20 04:29:06.350 269 277 I Magisk : * Loading modules
06-20 04:29:06.350 269 289 I Magisk : * Starting MagiskHide
06-20 04:29:06.350 269 289 I Magisk : hide_utils: Hiding sensitive props
06-20 04:29:06.360 269 289 I Magisk : hide_list: [com.google.android.gms.unstable]
06-20 04:29:06.380 269 289 I Magisk : proc_monitor: init ns=mnt:[4026531840]
12-30 17:08:38.099 269 575 I Magisk : ** late_start service mode running
12-30 17:08:38.099 269 575 I Magisk : * Running service.d scripts
12-30 17:08:38.099 269 575 I Magisk : * Running module service scripts
12-30 17:08:42.049 269 289 I Magisk : proc_monitor: zygote ns=mnt:[4026534515]
Click to expand...
Click to collapse
Same with me, HTC A9, latest magisk 15.2 and magisk manager 5.5.3 SafetyNet not passed!! orz
---------- Post added at 03:56 AM ---------- Previous post was at 03:00 AM ----------
I removed Xposed installer and re-installed Magisk 15.2 with Magisk Manager 5.5.3, then SafetyNet is worked again!
Also on NOTE 8 it does not pass
HTML:
01-02 09:01:52.873 3244 3244 E Magisk : symlink /root/magisk->/sbin/resetprop failed with 17: File exists
01-02 09:01:52.874 3244 3244 I Magisk : * Mounting mirrors
01-02 09:01:52.874 3244 3244 I Magisk : mount: /sbin/.core/mirror/system
01-02 09:01:52.874 3244 3244 I Magisk : link: /sbin/.core/mirror/vendor
01-02 09:01:52.874 3244 3244 I Magisk : bind_mount: /sbin/.core/mirror/bin
01-02 09:01:52.874 3244 3244 I Magisk : * Setting up internal busybox
01-02 09:01:52.882 3244 3244 I Magisk : Magisk v15.2(1520) daemon started
01-02 09:01:53.005 3244 3253 I Magisk : ** post-fs mode running
01-02 09:01:53.628 3244 3360 I Magisk : ** post-fs-data mode running
01-02 10:01:53.628 3244 3360 I Magisk : * Mounting /data/adb/magisk.img
01-02 10:01:53.776 3244 3360 I Magisk : * Running post-fs-data.d scripts
01-02 10:01:53.777 3244 3360 I Magisk : * Enabling systemless hosts file support
01-02 10:01:53.777 3244 3360 I Magisk : bind_mount: /system/etc/hosts
01-02 10:01:53.777 3244 3375 I Magisk : * Starting MagiskHide
01-02 10:01:53.777 3244 3375 I Magisk : hide_utils: Hiding sensitive props
01-02 10:01:53.777 3244 3375 I Magisk : hide_list: [com.google.android.gms.unstable]
01-02 10:01:53.787 3244 3375 I Magisk : hide_list: [fr.bnpp.digitalbanking]
01-02 10:01:53.796 3244 3375 I Magisk : proc_monitor: init ns=mnt:[4026531840]
01-02 10:01:54.252 3244 3499 I Magisk : ** late_start service mode running
01-02 10:01:54.253 3244 3499 I Magisk : * Running service.d scripts
01-02 10:02:11.097 3244 3375 I Magisk : proc_monitor: zygote ns=mnt:[4026533806] zygote64 ns=mnt:[4026533796]
01-02 10:02:30.700 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=7258 ns=mnt:[4026533924])
01-02 10:02:30.703 7264 7264 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:03:07.270 11262 11262 W Magisk : su: request rejected (10225->0)
01-02 10:03:20.984 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=12816 ns=mnt:[4026533889])
01-02 10:03:20.992 12831 12831 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:03:35.121 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13855 ns=mnt:[4026533969])
01-02 10:03:35.124 13861 13861 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:04:22.494 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17089 ns=mnt:[4026533924])
01-02 10:04:22.499 17095 17095 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:06:34.773 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=20020 ns=mnt:[4026533924])
01-02 10:06:34.789 20034 20034 I Magisk : hide_daemon: Permissive detected, hide the state
01-02 10:06:35.792 3244 3375 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=20079 ns=mnt:[4026533931])
01-02 10:06:35.795 20085 20085 I Magisk : hide_daemon: Permissive detected, hide the state
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Click to expand...
Click to collapse
Worked for me.Thankyou.:good:
arya12321 said:
Worked for me.Thankyou.:good:
Click to expand...
Click to collapse
+1 This worked for me and as far as I can tell all modules and settings were retained.
please how can i root my tecno k9 plz i have tried evey thing help me out plz i need this root plz guys
hi. how to clear magisk manager data? i cant see the options in app settings
Hi, I seem to be having a problem with safetyNet API, I have a samsung s5 with the newest Magisk installed have tried all the suggestions on this thread but nothing works. Still get "Safety API Error" anybody have any other suggestions. Im running Android 6.0.1 on security patch 1 October 2016.
iPusak Gaoq™ said:
Clear Magisk Manager data and when you relaunch/open Magisk make sure you have a good internet connection cause you need that to download a files that help to check safetynet API when you click on Tap To Start Safetynet Check...
Sent from my A0001 using Tapatalk
Click to expand...
Click to collapse
Oh thanks. That was easier than what I have imagined. Thanks a lot.
mandhir said:
Upgraded to Magisk v15.0 and now when I run SafetyNet check I receive an API Error.
I am running Android 8.1 on Nexus 6P and have uninstalled Magisk using the Uninstaller and re-installed and still receive the same API error.
I've searched and read through quite a few threads and haven't come up with any fixes. Closest thing I found was a fix on the OnePlus forum.
Attached is a screenshot of the Magisk screen for reference.
Any help would be greatly appreciated.
Thanks in advance!
Click to expand...
Click to collapse
You Can Simply Add A Google Account If You Dont Have Any To Solve This Problem. I Did The Same.
Guys i have the same problem and The most strange point is that it all came up after I fresh installed a rom I had been using for a while and had no problem. I tried like every solution here e.g. adding google account or clearing magisk data etc. with no joy.
Any help is appreciated
I recently upgraded from Magisk 12 to the latest 15 and found that the last 2 versions (1531 and 1540) seem to have compatibility issue with Xposed (89.2-sdk23-topjohnwu). With any of these 2 versions, Xposed Installer always show "installed but inactive" and none of the installed modules are enabled. Version 1530, however, works fine. Magisk Manager always show Magisk is installed successfully for all 3 versions. Root and SafetyNet (without Xposed) are successful too.
I've tried many advice but none of them fix this problem. Of course, I can stay in 1530 but I fear that I'm unable to try future versions.
My phone is a Xperia X Compact running Marshmallow stock ROM, kernel patched with TA PoC.
Magisk log:
Code:
02-13 11:52:29.367 4146 4146 I Magisk : Magisk v15.4(1540) daemon started
02-13 11:52:29.367 4146 4154 I Magisk : * Starting MagiskHide
02-13 11:52:29.368 4146 4154 I Magisk : hide_utils: Hiding sensitive props
02-13 11:52:29.368 4146 4154 I Magisk : hide_list: [com.google.android.gms.unstable]
02-13 11:52:29.402 4146 4154 I Magisk : proc_monitor: init ns=mnt:[4026531840]
02-13 11:52:30.453 4146 4154 I Magisk : proc_monitor: zygote ns=mnt:[4026535950] zygote64 ns=mnt:[4026535951]
02-13 12:03:26.742 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=9099 ns=mnt:[4026536040])
02-13 12:03:55.977 4146 10987 E Magisk : sqlite3 open failure: unable to open database file
02-13 12:03:55.977 4146 10987 E Magisk : su: cannot find requester
02-13 12:03:55.981 10989 10989 W Magisk : su: request rejected (10230->0)
02-13 12:04:10.040 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=11752 ns=mnt:[4026536015])
02-13 12:04:33.288 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=13374 ns=mnt:[4026536031])
02-13 12:04:58.467 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=15340 ns=mnt:[4026536053])
02-13 12:07:11.041 4146 16761 E Magisk : sqlite3 open failure: unable to open database file
02-13 12:07:57.953 4146 4154 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=17502 ns=mnt:[4026536031])
I manage to install Magisk v16 (by replacing the Magisk patched boot.img with the stock one) in an Asus Tinker Board running Android 6.0.1. Everything seems works fine except Kodi v17 failed to playback any video and lost it's sound after Magisk installed, Kodi App also failed to Exit.
Things return to normal after Magisk being uninstall by replacing the patched boot.img with the stock, below is the logs generated by Magisk:
Code:
04-08 06:55:18.705 197 197 I Magisk : * Creating /sbin overlay
04-08 06:55:18.706 197 197 I Magisk : * Mounting mirrors
04-08 06:55:18.706 197 197 I Magisk : mount: /sbin/.core/mirror/system
04-08 06:55:18.707 197 197 I Magisk : link: /sbin/.core/mirror/vendor
04-08 06:55:18.763 197 197 E Magisk : mount /data/adb/magisk->/sbin/.core/mirror/bin failed with 2: No such file or directory
04-08 06:55:18.763 197 197 I Magisk : bind_mount: /sbin/.core/mirror/bin
04-08 06:55:18.763 197 197 I Magisk : * Setting up internal busybox
04-08 06:55:18.764 202 202 E Magisk : execvpe failed with 2: No such file or directory
04-08 06:55:18.764 202 202 I Magisk : Magisk v16.0(1600) daemon started
04-08 06:55:18.765 202 204 I Magisk : ** post-fs mode running
04-08 14:55:20.340 202 233 I Magisk : ** post-fs-data mode running
04-08 14:55:20.341 202 233 I Magisk : * Mounting /data/adb/magisk.img
04-08 14:55:20.456 202 233 I Magisk : * Running post-fs-data.d scripts
04-08 14:55:20.456 202 233 I Magisk : * Enabling systemless hosts file support
04-08 14:55:20.464 202 233 I Magisk : bind_mount: /system/etc/hosts
04-08 14:55:20.464 202 243 I Magisk : * Starting MagiskHide
04-08 14:55:20.464 202 243 I Magisk : hide_utils: Hiding sensitive props
04-08 14:55:20.465 202 243 I Magisk : hide_list: [com.google.android.gms.unstable]
04-08 14:55:20.472 202 243 I Magisk : proc_monitor: init ns=mnt:[4026531840]
04-08 14:55:22.407 202 243 I Magisk : proc_monitor: zygote ns=mnt:[4026533453]
04-08 14:55:24.072 202 311 I Magisk : ** late_start service mode running
04-08 14:55:24.072 202 311 I Magisk : * Running service.d scripts
04-08 14:57:06.565 1413 1413 E Magisk : dup2 failed with 9: Bad file descriptor
04-08 14:57:06.565 1413 1413 E Magisk : dup2 failed with 9: Bad file descriptor
Not new here, but had to create another account.
I'm using Magisk 16.7 from beta release (updated withing app), and i have tried almost everything from here to pass the SafetyNet. While checking with Magisk, it says "Service not Responding".
Did something change with SafetyNet? Trying to use the Google Pay app. Hided it with MagiskHide, using the Magisk Core, using systemless...
Using Huawei P8 Lite 2017 (ALE-21 with B896), emui 4.1
Code:
2 19:18:17.260 2432 2432 I Magisk : ** Initializing Magisk
08-22 19:18:17.262 2432 2432 I Magisk : * Creating /sbin overlay
08-22 19:18:17.266 2432 2432 I Magisk : * Mounting mirrors
08-22 19:18:17.267 2432 2432 I Magisk : mount: /sbin/.core/mirror/system
08-22 19:18:17.267 2432 2432 I Magisk : link: /sbin/.core/mirror/vendor
08-22 19:18:17.268 2432 2432 I Magisk : bind_mount: /sbin/.core/mirror/bin
08-22 19:18:17.268 2432 2432 I Magisk : * Setting up internal busybox
08-22 19:18:17.396 2511 2511 I Magisk : Magisk v16.7(1671) logger started
08-22 19:18:17.397 2505 2505 I Magisk : Magisk v16.7(1671) daemon started
08-22 19:18:17.405 2505 2513 I Magisk : ** post-fs-data mode running
08-22 19:18:17.504 2505 2513 I Magisk : Upgrade/New module: terminal_debloater
08-22 19:18:17.505 2505 2513 I Magisk : Upgrade/New module: APFE
08-22 19:18:17.505 2505 2513 I Magisk : Create /data/adb/tmp.img with size 96M
08-22 19:18:17.761 2505 2513 I Magisk : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img
08-22 19:18:20.365 2505 2513 I Magisk : * Move /data/adb/tmp.img -> /data/adb/magisk.img
08-22 19:18:20.366 2505 2513 I Magisk : * Mounting /data/adb/magisk.img
08-22 19:18:20.996 2505 2513 I Magisk : * Running post-fs-data.d scripts
08-22 19:18:20.996 2505 2561 I Magisk : * Starting MagiskHide
08-22 19:18:20.996 2505 2561 I Magisk : hide_utils: Hiding sensitive props
08-22 19:18:20.997 2505 2561 I Magisk : hide_list: [com.google.android.gms.unstable]
08-22 19:18:21.017 2505 2561 I Magisk : hide_list: [com.theappninjas.gpsjoystick]
08-22 19:18:21.032 2505 2561 I Magisk : hide_list: [com.nianticlabs.pokemongo]
08-22 19:18:21.048 2505 2561 I Magisk : hide_list: [com.google.android.apps.walletnfcrel]
08-22 19:18:21.063 2505 2561 I Magisk : hide_list: [org.freeandroidtools.root_checker]
08-22 19:18:21.078 2505 2561 I Magisk : hide_list: [pl.allegro]
08-22 19:18:26.024 2505 2963 I Magisk : ** late_start service mode running
08-22 19:18:26.025 2505 2963 I Magisk : * Running service.d scripts
08-22 19:18:49.710 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick
08-22 19:18:52.457 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick:remote
08-22 19:19:10.967 2505 2561 I Magisk : proc_monitor: com.google.android.gms.unstable
08-22 19:19:15.931 2505 2561 I Magisk : proc_monitor: com.google.android.apps.walletnfcrel
08-22 19:19:36.608 2505 2561 I Magisk : proc_monitor: com.nianticlabs.pokemongo
08-22 19:19:40.728 2505 2561 I Magisk : proc_monitor: org.freeandroidtools.root_checker
08-22 19:19:41.205 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick
08-22 19:21:37.520 2505 2561 I Magisk : proc_monitor: com.google.android.apps.walletnfcrel
08-22 19:26:48.882 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick
08-22 19:26:55.893 2505 2561 I Magisk : proc_monitor: com.google.android.apps.walletnfcrel
08-22 19:27:18.562 2505 2561 I Magisk : proc_monitor: com.google.android.gms.unstable
08-22 19:31:27.906 2505 2561 I Magisk : proc_monitor: com.google.android.apps.walletnfcrel
08-22 19:34:58.044 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick
08-22 19:35:07.076 2505 2561 I Magisk : proc_monitor: com.google.android.gms.unstable
08-22 19:35:17.037 2505 2561 I Magisk : proc_monitor: org.freeandroidtools.root_checker
08-22 19:37:22.086 2505 2561 I Magisk : proc_monitor: com.theappninjas.gpsjoystick
Yes, Google updated their api so every app that wants to check safetynet has to be updated. changes to magisk have been committed on GitHub, I hope the next version of MM will fix it.
https://mobile.twitter.com/topjohnwu
I discovered and installed magisk today on my P9 lite, imagine my questions after seeing "response is invalid" in MM ^^