Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug] Magisk module doesn't work properly. Module columns are erased when rebooting. #741

Closed
1 task done
Kami-0x10 opened this issue Nov 14, 2023 · 1 comment
Closed
1 task done
Labels
bug Something isn't working

Comments

@Kami-0x10
Copy link

Steps to reproduce/复现步骤

I myself do not speak Chinese and English, so I am sorry that I may not be able to communicate well as I am writing this in translated Japanese!

Steps to reproduce

  1. Install as usual
    I downloaded the build.sh file from an external source because I could not mount VHDX in the normal way.
  2. Then start the custom wsa and launch magisk
    Select the module.zip you want to add from the modules section, install it, and reboot.
  3. If you open Magisk again after rebooting, you will see that it is not working properly

Expected behaviour/预期行为

I don't know what to write here, so I'll just write why this bug (which may be a specification) occurs.

But first, I'd like to digress.
I was going to use Google Play VRChat on my handheld PC, so I built this repository, but the original image file is not designed for very high spec usage, and I guess it's because the device name is Pixel 5. But the original image file was not intended for very high spec use, and I was disappointed that there were many apps that were not supported even if I put in Google Play.

So I decided to add Magisk and try to forge a terminal with MagiskHidePropConf.
Naturally, it doesn't work because I'm throwing an issue.

Why doesn't it work?

MagiskHidePropConf uses BusyBox
This BusyBox is quite a tricky one, and if you select Magisk on the first Root app screen, it will probably start without the BusyBox.
In the case of kernel SU, there is no problem because it is built-in, but in the case of Magisk, I guess that this is probably not the cause because it does not enter by ReadOnly even if I try to enter newly.

I installed MagiskHidePropConf with the BusyBox path changed in the kernel SU once again based on these events, and it started fine (well, PropConf itself is not updated, so I could not play the smartphone version of VRChat).

Actual behaviour/实际行为

.I don't know what to write, so for now, I'm not going to write anything here.

MagiskOnWSALocal commit full SHA/MagiskOnWSALocal 提交的完整哈希

I don't know what to write, so for now, I'm not going to write anything here.

Linux distribution info/Linux 发行版信息

DE used for build is Ubuntu 20 LTS with WSL

Windows version/Windows 版本

Well, I tried it another way and it worked, so there's nothing to describe here for now.

Build Parameters/构建参数

Bug Param=x64 release type retail Magisk gapps brand Mind The Gapps gapps variant pico root
No Bug=x64 release type retail KernelSU gapps brand Mind The Gapps gapps variant pico root

Version requirement/版本要求

  • I am using latest commit of MagiskOnWSALocal/我正在使用最新 commit 的版本

Logs/日志

# Replace this line with the log / 将此行用日志替换
@Kami-0x10 Kami-0x10 added the bug Something isn't working label Nov 14, 2023
@Burgerd4sh
Copy link

Burgerd4sh commented Nov 21, 2023

duplicate with #687 (comment)

I had the same issue too. You can try the solution below. They work to me.
1、MustardChef/WSABuilds#154
2、Using an older version of Magisk:MustardChef/WSABuilds#154 (comment)

@github-actions github-actions bot locked and limited conversation to collaborators Mar 3, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

3 participants