So the modules are not working.
Tried to turn core-only off. Rebooted. It's ON again.
Log :
Code:
--------- beginning of main
--------- beginning of system
09-10 10:58:03.623 301 301 I Magisk : Magisk v19.3(19300) daemon started
09-10 10:58:03.623 301 301 I Magisk : * Device API level: 25
09-10 10:58:16.217 301 542 I Magisk : ** late_start service mode running
09-10 10:58:16.438 301 542 E Magisk : * post-fs-data mode is not triggered
09-10 10:58:16.441 301 542 I Magisk : * Initializing Magisk environment
09-10 10:58:16.540 301 542 I Magisk : * Mounting mirrors
09-10 10:58:16.542 301 542 I Magisk : mount: /sbin/.magisk/mirror/system
09-10 10:58:16.542 301 542 I Magisk : mount: /sbin/.magisk/mirror/data
09-10 10:58:16.542 301 542 I Magisk : link: /sbin/.magisk/mirror/vendor
09-10 10:58:16.576 301 542 I Magisk : * Setting up internal busybox
09-10 10:58:16.751 301 542 I Magisk : * Running service.d scripts
09-10 10:58:16.816 301 673 I Magisk : * Starting MagiskHide
09-10 10:58:16.817 301 673 I Magisk : hide_policy: Hiding sensitive props
09-10 10:58:16.881 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android]
09-10 10:58:16.893 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:crash]
09-10 10:58:16.903 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:phoenix]
09-10 10:58:16.912 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:stuffing]
09-10 10:58:16.921 301 673 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
09-10 10:58:16.929 301 673 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
09-10 10:58:17.497 301 815 I Magisk : ** post-fs-data mode running
09-10 10:58:17.500 301 815 I Magisk : * Initializing Magisk environment
09-10 10:58:17.500 301 815 I Magisk : * Mounting mirrors
09-10 10:58:17.501 301 815 E Magisk : mount /sbin/.magisk/block/system->/sbin/.magisk/mirror/system failed with 16: Device or resource busy
09-10 10:58:17.501 301 815 I Magisk : mount: /sbin/.magisk/mirror/system
09-10 10:58:17.501 301 815 E Magisk : mount /sbin/.magisk/block/data->/sbin/.magisk/mirror/data failed with 16: Device or resource busy
09-10 10:58:17.501 301 815 I Magisk : mount: /sbin/.magisk/mirror/data
09-10 10:58:17.502 301 815 I Magisk : * Setting up internal busybox
09-10 10:58:17.513 301 815 I Magisk : * Running post-fs-data.d scripts
09-10 10:59:21.071 301 1953 I Magisk : ** boot_complete triggered
09-10 10:59:51.698 301 673 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[4345] UID=[10010]
-update
Cleared mobile cache and Magisk repo cache and it worked.
Seems that fix works
I have same trouble after installing some modules, that fix worked for me
Didnt work for me.. Tried everything. Revmoving the caches. Uninstalling everything trying older version nothing works.. I think my rom is the issue but I don't want to change roms.. I want a workaround or fix
Edit: i just noticed a beta finally came out. 19.4 after installing it and disabling core only and installing a module it finally stayed off after boot
It doesn't work just uninstall and start all over again.
18.1 is still the best.
Sent from my Sony G8142 using XDA Labs
rootenshi said:
-update
Cleared mobile cache and Magisk repo cache and it worked.
Click to expand...
Click to collapse
How to clear magisk repo cache??
Thejayyadav said:
How to clear magisk repo cache??
Click to expand...
Click to collapse
Open Magisk -> Settings -> Clear repo cache
i am too facing the issue but clearing repo cache and all application caches does not help, any solution?
pl refer here https://forum.xda-developers.com/showpost.php?p=81177129&postcount=26
codergenius said:
i am too facing the issue but clearing repo cache and all application caches does not help, any solution?
pl refer here https://forum.xda-developers.com/showpost.php?p=81177129&postcount=26
Click to expand...
Click to collapse
flash MultiFunctionsPlus and reboot.
Related
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
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
Why magisk modules not working on realme 2 pro
They can be installed but don't activate after reboot
Only we have an old patched version of magisk installer v17.1 which have working modules but it is old version with very few modules
Please fix this and support realme 2 pro mdroid pie
Without more info or any kind of logs it's extremely hard to offer any kind of help. Take a look here:
https://didgeridoohan.com/magisk/MagiskHelp
Here is the log
Code:
301 542 I Magisk : link: /sbin/.magisk/mirror/vendor
09-10 10:58:16.576 301 542 I Magisk : * Setting up internal busybox
09-10 10:58:16.751 301 542 I Magisk : * Running service.d scripts
09-10 10:58:16.816 301 673 I Magisk : * Starting MagiskHide
09-10 10:58:16.817 301 673 I Magisk : hide_policy: Hiding sensitive props
09-10 10:58:16.881 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android]
09-10 10:58:16.893 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:crash]
09-10 10:58:16.903 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:phoenix]
09-10 10:58:16.912 301 673 I Magisk : hide_list init: [com.snapchat.android/com.snapchat.android:stuffing]
09-10 10:58:16.921 301 673 I Magisk : hide_list init: [com.google.android.gms/com.google.android.gms.unstable]
09-10 10:58:16.929 301 673 I Magisk : hide_list init: [org.microg.gms.droidguard/com.google.android.gms.unstable]
09-10 10:58:17.497 301 815 I Magisk : ** post-fs-data mode running
09-10 10:58:17.500 301 815 I Magisk : * Initializing Magisk environment
09-10 10:58:17.500 301 815 I Magisk : * Mounting mirrors
09-10 10:58:17.501 301 815 E Magisk : mount /sbin/.magisk/block/system->/sbin/.magisk/mirror/system failed with 16: Device or resource busy
09-10 10:58:17.501 301 815 I Magisk : mount: /sbin/.magisk/mirror/system
09-10 10:58:17.501 301 815 E Magisk : mount /sbin/.magisk/block/data->/sbin/.magisk/mirror/data failed with 16: Device or resource busy
09-10 10:58:17.501 301 815 I Magisk : mount: /sbin/.magisk/mirror/data
09-10 10:58:17.502 301 815 I Magisk : * Setting up internal busybox
09-10 10:58:17.513 301 815 I Magisk : * Running post-fs-data.d scripts
09-10 10:59:21.071 301 1953 I Magisk : ** boot_complete triggered
09-10 10:59:51.698 301 673 I Magisk : proc_monitor: [com.google.android.gms.unstable] PID=[4345] UID=[10010]
The magisk is forced to run on Core mode only and cannot be switched
elswerky said:
Why magisk modules not working on realme 2 pro
They can be installed but don't activate after reboot
Only we have an old patched version of magisk installer v17.1 which have working modules but it is old version with very few modules
Please fix this and support realme 2 pro mdroid pie
Click to expand...
Click to collapse
To make magisk modules working properly, use fix magisk for oppo and realme by wzsx150.
Flash it with your twrp.