search

HuskyDG / magisk-files

1.84k stars 77 forks source link

Modules not installing after reboot on WSA #88

Open bropines opened 5 months ago

bropines commented 5 months ago

https://github.com/MustardChef/WSABuilds/issues/154

This issue discusses this issue. What's on Kitsune, what's on the original Magisk. After installing the module, we restart the shell (well, the subsystem is stupidly rebooted) and the module disappears. It's not in the magisk folder or anywhere else. There is an installation method that involves moving the module directly to modules and it really works. Can this be fixed at the magisk level?

HuskyDG commented 5 months ago

No further information such as magisk logs and logcat

bropines commented 5 months ago

No further information such as magisk logs and logcat

https://github.com/HuskyDG/magisk-files/assets/57861007/40391680-92d1-4b1d-9ffe-4a5f533e9853

I'm a bit dumb, and generally an idiot, but how do you record logs.... Reboots? The video shows Magisk 26403, but the same problem occurred on Magisk Delta. https://github.com/MustardChef/WSAMagiskDelta/issues/9

Log:

01-20 06:39:41.738   120   120 I :  Magisk d7750b72(26403) daemon started
01-20 06:39:41.738   120   120 I :  * Device API level: 33
01-20 06:39:41.748   120   122 I :  ** post-fs-data mode running
01-20 06:39:41.748   120   122 I :  * Mounting mirrors
01-20 06:39:41.762   120   122 I :  * Initializing Magisk environment
01-20 06:39:41.767   120   122 I :  * Running post-fs-data.d scripts
01-20 06:39:41.769   120   122 I :  Upgrade / New module: aml
01-20 06:39:41.770   120   122 I :  * Running module post-fs-data scripts
01-20 06:39:41.770   127   127 I :  zygisk_lsposed: exec [post-fs-data.sh]
01-20 06:39:41.776   120   122 I :  * Loading modules
01-20 06:39:42.591   120   122 I :  ** late_start service mode running
01-20 06:39:42.591   120   122 I :  * Running service.d scripts
01-20 06:39:42.592   120   122 I :  service.d: exec [aml.sh]
01-20 06:39:42.593   120   122 I :  * Running module service scripts
01-20 06:39:42.593   120   122 I :  zygisk_lsposed: exec [service.sh]
01-20 06:39:42.757   148   148 I :  zygisk64: replace nativeForkAndSpecialize
01-20 06:39:42.757   149   149 I :  zygisk32: replace nativeForkAndSpecialize
01-20 06:39:42.757   148   148 I :  zygisk64: replace nativeSpecializeAppProcess
01-20 06:39:42.757   149   149 I :  zygisk32: replace nativeSpecializeAppProcess
01-20 06:39:42.757   148   148 I :  zygisk64: replace nativeForkSystemServer
01-20 06:39:42.757   149   149 I :  zygisk32: replace nativeForkSystemServer
01-20 06:39:43.297   120   122 I :  denylist: initializing internal data structures
01-20 06:39:45.180   120   122 I :  ** boot-complete triggered
MustardChef commented 4 months ago

I can confirm that the same issue is present on the last build of Magisk Delta and latest build of Kitsune (v26.4-kitsune-2).

bropines commented 3 months ago

do you need any more data to fix the tor fixed in the new alpha version?

MustardChef commented 3 months ago

do you need any more data to fix the tor fixed in the new alpha version?

The next commits in MagiskOnWSALocal repo may have fixed the issue. New LTS builds will be released soon.