New Magisk modules don't work


Poipoi

Members
Jan 24, 2018
62
20
Hi, I have a mi5 (gemini) with miui 10 stable (V10.0.1.0.OAACNFH).
I installed magisk v 17.1 with four modules:
  • Audio Modification Library
  • Ainur Sauron
  • Dolby Atmos (guitardedhero for oreo)
  • Energized Protection
They don't work, the icons don't show in the drawer, but looking at magisk log there are no errors.

I'll make a logcat if it's useful
 

nuvul

Members
Feb 1, 2018
61
20
Is it possible that the modules have to be updated for Magisk 17? You can ask in xda.
 

Poipoi

Members
Jan 24, 2018
62
20
ok they are ready for magisk 17.1, they are developed for magisk 15+
 
Last edited:

Igor Eisberg

Developer
Staff member
Oct 6, 2016
3,401
322
Can't see how this has anything to do with us. We have no involvement in Magisk.
You can try to downgrade to Magisk 16 somehow and see if it solves your issue, but I don't even know what we're supposed to do here.
I'm using Magisk 17.1 with "Magisk SELinux Permissive Script" and "Volume Steps Increase". Both work correctly on MI 5 Beta 8.9.4. Can't see why it wouldn't work on a Stable ROM.
 
  • Like
Reactions: grzesb

MarkHUK

Founder of Xiaomi.eu
Staff member
Nov 6, 2010
5,225
1,000,000
Can't see how this has anything to do with us. We have no involvement in Magisk.
You can try to downgrade to Magisk 16 somehow and see if it solves your issue, but I don't even know what we're supposed to do here.
I'm using Magisk 17.1 with "Magisk SELinux Permissive Script" and "Volume Steps Increase". Both work correctly on MI 5 Beta 8.9.4. Can't see why it wouldn't work on a Stable ROM.
Just suggested to ask you as I am not using Magisk etc and know you guys do or did :)
 

Poipoi

Members
Jan 24, 2018
62
20
Can't see how this has anything to do with us. We have no involvement in Magisk.
You can try to downgrade to Magisk 16 somehow and see if it solves your issue, but I don't even know what we're supposed to do here.
I'm using Magisk 17.1 with "Magisk SELinux Permissive Script" and "Volume Steps Increase". Both work correctly on MI 5 Beta 8.9.4. Can't see why it wouldn't work on a Stable ROM.
I reported this to you because in the previous versions of miui everything was fine, and maybe in this release there was something wrong.
Anyway, I'll try to downgrade. Thanks for your help
 

Igor Eisberg

Developer
Staff member
Oct 6, 2016
3,401
322
I reported this to you because in the previous versions of miui everything was fine, and maybe in this release there was something wrong.
Anyway, I'll try to downgrade. Thanks for your help
We haven't altered anything that is even remotely related to Magisk, so it's more likely that Magisk 17.1 (which was released after 8.8.30) glitched rather than the ROM. Especially when upgrading Magisk from 16 to 17 proved to be a fatal procedure.
 

Poipoi

Members
Jan 24, 2018
62
20
We haven't altered anything that is even remotely related to Magisk, so it's more likely that Magisk 17.1 (which was released after 8.8.30) glitched rather than the ROM. Especially when upgrading Magisk from 16 to 17 proved to be a fatal procedure.
I tried to completely uninstall Magisk 17.1 and then reinstalling it, with no luck.
I'll try to downgrade
 

Poipoi

Members
Jan 24, 2018
62
20
I tried to downgrade with no results. I think magisk glitched on my device, so for now I can say goodbye to Magisk.
Maybe I'll try it again in the next stable version.
 

Daenjel

Members
Mar 6, 2018
53
30
Those modules uses an Unity "Instaler" that was conflicting with the new magisk 17.1, they are now updated to Unity 1.7.1+ so they work perfectly now, i know because i use those as well, you should try them now :)
 

Poipoi

Members
Jan 24, 2018
62
20
Those modules uses an Unity "Instaler" that was conflicting with the new magisk 17.1, they are now updated to Unity 1.7.1+ so they work perfectly now, i know because i use those as well, you should try them now :)
I tried, but they still don't work. May the Magisk log could help?

Code:
09-29 11:11:03.228   485   485 I Magisk  : ** Initializing Magisk
09-29 11:11:03.231   485   485 I Magisk  : * Creating /sbin overlay
09-29 11:11:03.238   485   485 I Magisk  : * Mounting mirrors
09-29 11:11:03.239   485   485 I Magisk  : mount: /sbin/.core/mirror/system
09-29 11:11:03.239   485   485 I Magisk  : link: /sbin/.core/mirror/vendor
09-29 11:11:03.239   485   485 I Magisk  : bind_mount: /sbin/.core/mirror/bin
09-29 11:11:03.239   485   485 I Magisk  : * Setting up internal busybox
09-29 11:11:03.300   492   492 I Magisk  : Magisk v17.1(17100) logger started
09-29 11:11:03.301   488   488 I Magisk  : Magisk v17.1(17100) daemon started
09-29 11:11:03.306   488   494 I Magisk  : ** post-fs-data mode running
09-29 11:11:03.372   488   494 I Magisk  : Upgrade/New module: energizedprotection
09-29 11:11:03.372   488   494 I Magisk  : Upgrade/New module: ainur_sauron
09-29 11:11:03.373   488   494 I Magisk  : Upgrade/New module: aml
09-29 11:11:03.374   488   494 I Magisk  : Upgrade/New module: dolbyatmos
09-29 11:11:03.374   488   494 I Magisk  : Create /data/adb/tmp.img with size 64M
09-29 11:11:03.466   488   494 I Magisk  : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img
09-29 11:11:03.765   488   494 I Magisk  : * Move /data/adb/tmp.img -> /data/adb/magisk.img
09-29 11:11:03.766   488   494 I Magisk  : * Mounting /data/adb/magisk.img
09-29 11:11:03.800   488   494 I Magisk  : * Running post-fs-data.d scripts
09-29 11:11:03.800   488   494 I Magisk  : post-fs-data.d: exec [sauron.sh]
09-29 11:11:03.803   488   494 I Magisk  : post-fs-data.d: exec [aml.sh]
09-29 11:11:03.809   488   494 I Magisk  : * Running module post-fs-data scripts
09-29 11:11:03.809   488   494 I Magisk  : ainur_sauron: exec [post-fs-data.sh]
09-29 11:11:03.927   488   494 I Magisk  : aml: exec [post-fs-data.sh]
09-29 11:11:04.319   488   494 I Magisk  : dolbyatmos: exec [post-fs-data.sh]
09-29 11:16:19.850   488  1316 I Magisk  : ** late_start service mode running
09-29 11:16:19.868   488  1316 I Magisk  : * Running service.d scripts
09-29 11:16:19.869   488  1316 I Magisk  : * Running module service scripts
09-29 11:16:19.869   488  1316 I Magisk  : ainur_sauron: exec [service.sh]
09-29 11:16:19.876   488  1319 I Magisk  : * Starting MagiskHide
09-29 11:16:19.876   488  1319 I Magisk  : hide_utils: Hiding sensitive props
09-29 11:16:19.877   488  1319 I Magisk  : hide_list: [com.google.android.gms.unstable]
09-29 11:16:26.107   488  1316 I Magisk  : dolbyatmos: exec [service.sh]
09-29 11:17:08.675   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
09-29 11:24:41.055   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
09-29 12:03:53.571   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
 

MarkHUK

Founder of Xiaomi.eu
Staff member
Nov 6, 2010
5,225
1,000,000
I tried, but they still don't work. May the Magisk log could help?

Code:
09-29 11:11:03.228   485   485 I Magisk  : ** Initializing Magisk
09-29 11:11:03.231   485   485 I Magisk  : * Creating /sbin overlay
09-29 11:11:03.238   485   485 I Magisk  : * Mounting mirrors
09-29 11:11:03.239   485   485 I Magisk  : mount: /sbin/.core/mirror/system
09-29 11:11:03.239   485   485 I Magisk  : link: /sbin/.core/mirror/vendor
09-29 11:11:03.239   485   485 I Magisk  : bind_mount: /sbin/.core/mirror/bin
09-29 11:11:03.239   485   485 I Magisk  : * Setting up internal busybox
09-29 11:11:03.300   492   492 I Magisk  : Magisk v17.1(17100) logger started
09-29 11:11:03.301   488   488 I Magisk  : Magisk v17.1(17100) daemon started
09-29 11:11:03.306   488   494 I Magisk  : ** post-fs-data mode running
09-29 11:11:03.372   488   494 I Magisk  : Upgrade/New module: energizedprotection
09-29 11:11:03.372   488   494 I Magisk  : Upgrade/New module: ainur_sauron
09-29 11:11:03.373   488   494 I Magisk  : Upgrade/New module: aml
09-29 11:11:03.374   488   494 I Magisk  : Upgrade/New module: dolbyatmos
09-29 11:11:03.374   488   494 I Magisk  : Create /data/adb/tmp.img with size 64M
09-29 11:11:03.466   488   494 I Magisk  : * Merging /data/adb/magisk_merge.img + /data/adb/magisk.img -> /data/adb/tmp.img
09-29 11:11:03.765   488   494 I Magisk  : * Move /data/adb/tmp.img -> /data/adb/magisk.img
09-29 11:11:03.766   488   494 I Magisk  : * Mounting /data/adb/magisk.img
09-29 11:11:03.800   488   494 I Magisk  : * Running post-fs-data.d scripts
09-29 11:11:03.800   488   494 I Magisk  : post-fs-data.d: exec [sauron.sh]
09-29 11:11:03.803   488   494 I Magisk  : post-fs-data.d: exec [aml.sh]
09-29 11:11:03.809   488   494 I Magisk  : * Running module post-fs-data scripts
09-29 11:11:03.809   488   494 I Magisk  : ainur_sauron: exec [post-fs-data.sh]
09-29 11:11:03.927   488   494 I Magisk  : aml: exec [post-fs-data.sh]
09-29 11:11:04.319   488   494 I Magisk  : dolbyatmos: exec [post-fs-data.sh]
09-29 11:16:19.850   488  1316 I Magisk  : ** late_start service mode running
09-29 11:16:19.868   488  1316 I Magisk  : * Running service.d scripts
09-29 11:16:19.869   488  1316 I Magisk  : * Running module service scripts
09-29 11:16:19.869   488  1316 I Magisk  : ainur_sauron: exec [service.sh]
09-29 11:16:19.876   488  1319 I Magisk  : * Starting MagiskHide
09-29 11:16:19.876   488  1319 I Magisk  : hide_utils: Hiding sensitive props
09-29 11:16:19.877   488  1319 I Magisk  : hide_list: [com.google.android.gms.unstable]
09-29 11:16:26.107   488  1316 I Magisk  : dolbyatmos: exec [service.sh]
09-29 11:17:08.675   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
09-29 11:24:41.055   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
09-29 12:03:53.571   488  1319 I Magisk  : proc_monitor: com.google.android.gms.unstable
Ask the Magisk developers... We dont give that support here!