Can't pass SafetyNet - Service not responding - Magisk 16.7 - Magisk

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 ^^

Related

Modules install correctly but won't work after reboot (log inside thread)

It always says "modules will be updates at next reboot" but they don't even work.
Tried several different magisk manager and zips. I am not on 14.5/5.4.3
11-27 00:17:14.897 3227 3342 I Magisk : * Creating /sbin overlay
11-27 00:17:14.898 3227 3342 I Magisk : * Mounting mirrors
11-27 00:17:14.898 3227 3342 I Magisk : mount: /dev/block/platform/11120000.ufs/by-name/SYSTEM -> /sbin/.core/mirror/system
11-27 00:17:14.898 3227 3342 I Magisk : link: /sbin/.core/mirror/system/vendor -> /sbin/.core/mirror/vendor
11-27 00:17:14.898 3227 3342 I Magisk : bind_mount: /data/magisk -> /sbin/.core/mirror/bin
11-27 00:17:14.898 3227 3342 I Magisk : * Setting up internal busybox
11-27 00:17:14.907 3227 3342 I Magisk : * Mounting /data/magisk.img
11-27 00:17:15.076 3227 3342 I Magisk : * Running post-fs-data.d scripts
11-27 00:17:15.076 3227 3342 I Magisk : * Running module post-fs-data scripts
11-27 00:17:15.076 3227 3342 I Magisk : * Loading modules
11-27 00:17:15.077 3227 3362 I Magisk : * Starting MagiskHide
11-27 00:17:15.077 3227 3362 I Magisk : hide_utils: Hiding sensitive props
11-27 00:17:15.077 3227 3362 I Magisk : hide_list: [com.google.android.gms.unstable]
11-27 00:17:15.092 3227 3362 I Magisk : proc_monitor: init ns=mnt:[4026531840]
11-27 00:17:15.613 3227 3457 I Magisk : ** late_start service mode running
11-27 00:17:15.614 3227 3457 I Magisk : * Running service.d scripts
11-27 00:17:15.620 3227 3457 I Magisk : * Running module service scripts
11-27 00:17:19.157 3227 3362 I Magisk : proc_monitor: zygote ns=mnt:[4026533794] zygote64 ns=mnt:[4026533649]
11-27 00:17:34.011 3227 3362 I Magisk : proc_monitor: com.google.android.gms.unstable (PID=6102 ns=mnt:[4026533902])

SafetyNet Fails

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

Magisk 1531/1540 issue with Xposed

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])

[ISSUE] Magisk hidelist clean after reboot

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

[HELP] Modules not showing after installation

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

Categories

Resources