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])
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 ^^
Hi,
I have magisk v17.1 and manager v5.9.1, but my magisk hidelist is always clean after reboot. The "hidelist" file inside /sbin/.core/img/.core/ has owner and group as "root" and permission 666 (rw-rw-rw). It writes into it just fine, I can see the new entries there, but after every reboot, it has only one entry (com.google.android.gms.unstable) and the change date is set to the time of the reboot.
Here is the log:
09-04 08:37:04.724 330 330 I Magisk : ** Initializing Magisk
09-04 08:37:04.725 330 330 I Magisk : * Creating /sbin overlay
09-04 08:37:04.731 330 330 I Magisk : * Mounting mirrors
09-04 08:37:04.732 330 330 I Magisk : mount: /sbin/.core/mirror/system
09-04 08:37:04.732 330 330 I Magisk : link: /sbin/.core/mirror/vendor
09-04 08:37:04.732 330 330 I Magisk : bind_mount: /sbin/.core/mirror/bin
09-04 08:37:04.733 330 330 I Magisk : * Setting up internal busybox
09-04 08:37:05.082 337 337 I Magisk : Magisk v17.1(17100) logger started
09-04 08:37:05.092 333 333 I Magisk : Magisk v17.1(17100) daemon started
09-04 08:37:05.096 333 339 I Magisk : ** post-fs-data mode running
09-04 08:37:05.097 333 339 I Magisk : * Mounting /data/adb/magisk.img
09-04 08:37:05.130 333 339 E Magisk : mount /sbin/.core/block/loop08->/sbin/.core/img failed with 13: Permission denied
09-04 08:37:05.133 333 339 I Magisk : * Running post-fs-data.d scripts
09-04 08:37:05.133 333 339 I Magisk : * Running module post-fs-data scripts
09-04 08:37:05.133 333 339 I Magisk : * Loading modules
09-04 08:37:05.138 333 345 I Magisk : * Starting MagiskHide
09-04 08:37:05.139 333 345 I Magisk : hide_utils: Hiding sensitive props
09-04 08:37:05.139 333 345 I Magisk : hide_list add: [com.google.android.gms.unstable]
09-04 08:37:06.160 333 428 I Magisk : ** late_start service mode running
09-04 08:37:06.161 333 428 I Magisk : * Running service.d scripts
09-04 08:37:06.161 333 428 I Magisk : * Running module service scripts
09-04 08:37:33.018 2538 2538 W Magisk : su: request rejected (10131->0)
09-04 08:38:01.971 333 345 I Magisk : proc_monitor: com.google.android.gms.unstable
09-04 08:38:22.577 333 345 I Magisk : proc_monitor: com.google.android.gms.unstable
09-04 08:38:38.320 333 345 I Magisk : proc_monitor: com.google.android.gms.unstable
09-04 08:43:00.481 333 345 I Magisk : proc_monitor: com.google.android.gms.unstable
The only problem I see here is this:
09-04 08:37:05.130 333 339 E Magisk : mount /sbin/.core/block/loop08->/sbin/.core/img failed with 13: Permission denied
But I have no idea what to do about it.
Does anybody know fix for this? THX
I'm having an issue with Magisk Manager modules not showing in my app drawer or anywhere else.
I have Magisk v18.1 and Magisk Manager v7.0.0 on my Samsung A3 2016 (A310F) running Android 7.0, SafetyNet passed.
I can download and install modules from Magisk Manager, however after reboot there is no sign of the app on the phone. The Downloads and Modules sections of Magisk Manager both show that the requested apps are installed.
I have TWRP Recovery, and have tried installing from the Recovery menu, however that doesn't work either.
All modules have this problem, I have tried it with several different ones.
I have also tried reinstalling Magisk as a direct installation from Magisk Manager, creating a MagiskManager folder on my internal storage, disabling the native YouTube app, none of which has worked.
These are the logs that I could find on my device:
MAGISK INSTALL LOG:
- Copying zip to temp directory
- Installing App_Systemizer_(Terminal_Emulator)-v16.2.zip
- Mounting /system, /vendor
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: common/
inflating: common/aapt
inflating: common/file_contexts_image
inflating: common/mod-util.sh
inflating: config.sh
inflating: module.prop
*******************************
Terminal App Systemizer
by veez21 @ xda-developers
*******************************
******************************
Powered by Magisk (@topjohnwu)
******************************
- Creating /data/adb/magisk_merge.img with size 64M
Creating filesystem with parameters:
Size: 67108864
Block size: 4096
Blocks per group: 32768
Inodes per group: 4096
Inode size: 256
Journal blocks: 1024
Label:
FLEX_BG size: 0
Blocks: 16384
Block groups: 1
Reserved block group size: 0
Created filesystem with 11/4096 inodes and 1286/16384 blocks
Create /data/adb/magisk_merge.img with size 64M
e2fsck 1.42.9 (28-Dec-2013)
- Extracting module files
Archive: /data/user/0/com.topjohnwu.magisk/cache/install.zip
creating: system/
creating: system/xbin/
inflating: system/xbin/systemize
- Setting permissions
- Done
MAGISK LOG:
02-17 14:24:30.020 2206 2206 I Magisk : * Creating /sbin overlay
02-17 14:24:30.130 2208 2208 I Magisk : * Device API level: 24
02-17 14:24:30.130 2208 2208 I Magisk : Magisk v18.1(18100) daemon started
02-17 14:24:30.131 2208 2209 I Magisk : ** post-fs-data mode running
02-17 14:24:30.131 2208 2209 I Magisk : * Initializing Magisk environment
02-17 14:24:30.139 2208 2209 I Magisk : * Mounting mirrors
02-17 14:24:30.141 2208 2209 I Magisk : mount: /sbin/.magisk/mirror/system
02-17 14:24:30.141 2208 2209 I Magisk : link: /sbin/.magisk/mirror/vendor
02-17 14:24:30.143 2208 2209 I Magisk : bind_mount: /sbin/.magisk/mirror/bin
02-17 14:24:30.146 2208 2209 I Magisk : * Setting up internal busybox
02-17 14:24:30.203 2214 2214 I Magisk : Magisk v18.1(18100) logger started
02-17 14:24:30.265 2208 2209 I Magisk : * Running post-fs-data.d scripts
02-17 14:24:30.366 2208 2209 I Magisk : Upgrade/New module: terminal_systemizer
02-17 14:24:30.367 2208 2209 I Magisk : Create /data/adb/tmp.img with size 64M
02-17 14:24:30.796 2208 2209 I Magisk : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img
02-17 14:24:30.916 2208 2209 I Magisk : * Move /data/adb/tmp.img -> /data/adb/magisk.img
02-17 14:24:30.917 2208 2209 I Magisk : * Mounting /data/adb/magisk.img
02-17 14:24:30.968 2208 2209 I Magisk : * Running module post-fs-data scripts
02-17 14:24:30.968 2208 2209 I Magisk : * Loading modules
02-17 14:24:30.968 2208 2209 I Magisk : terminal_systemizer: constructing magic mount structure
02-17 14:24:30.969 2208 2209 I Magisk : mnt_tmpfs : /system/xbin
02-17 14:24:30.969 2208 2209 I Magisk : bind_mount: /system/xbin/systemize
02-17 14:24:30.969 2208 2209 I Magisk : bind_mount: /system/xbin/cpustats
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/dexlist
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_connect
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_disconnect
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_lsp
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_showtime
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_simple_client
02-17 14:24:30.970 2208 2209 I Magisk : bind_mount: /system/xbin/jack_transport
02-17 14:24:31.000 2208 2256 I Magisk : * Starting MagiskHide
02-17 14:24:31.000 2208 2256 I Magisk : hide_utils: Hiding sensitive props
02-17 14:24:31.012 2208 2256 I Magisk : hide_list: [com.google.android.gms/.droidguard.DroidGuardService]
02-17 14:24:31.812 2208 2309 I Magisk : ** late_start service mode running
02-17 14:24:31.814 2208 2309 I Magisk : * Running service.d scripts
02-17 14:24:32.342 2208 2309 I Magisk : * Running module service scripts
02-17 14:25:29.051 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[5327] ns=[4026539997]
02-17 14:26:30.072 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[9575] ns=[4026540017]
02-17 14:27:27.018 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12050] ns=[4026539997]
02-17 14:27:27.142 2208 2256 I Magisk : proc_monitor: com.google.android.gms/.droidguard.DroidGuardService PID=[12071] ns=[4026539999]
TWRP RECOVERY LOG:
I'm happy to post this if needed, however it's very long and I didn't want to make this hard to read.
What can I do to fix this installation issue?
The only module you have installed, according to both the install log and Magisk log is App Systemizer and that doesn't come with an app. You run it through a terminal emulator. Take a look at the module documentation/thread for details.
Didgeridoohan said:
The only module you have installed, according to both the install log and Magisk log is App Systemizer and that doesn't come with an app. You run it through a terminal emulator. Take a look at the module documentation/thread for details.
Click to expand...
Click to collapse
Oddly, Magisk Manager (within the Modules section) showed that I also have Youtube Vanced installed, and I was certain that was supposed to have an app icon showing.
However, your comment made me try a different emulator than the one I already used to test App Systemizer (Terminal Emulator for Android from the Play Store), so I downloaded Termux instead and the commands worked! I'm not sure why, but I'm glad it is working.
This pushed me further to delve into the Youtube Vanced issue, and it turned out that requirement disabling auto updates on the native Youtube app, an option that I could not see on my device, only appeared after I re-enabled it, uninstalled it, and then searched for it again. Once I toggled the auto update option that was now visible, the Youtube Vanced app became visible in my app drawer.
Thank you very much for pointing me in the right direction.
Hello,
I seem to have a problem with
In downloads only few modules are showing., youtube vanced and dolby atmos etc.. showing., its says module not found how can i fix it.. T_T