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

mounting binaries to /bin makes device stuck at boot logo #18

Closed
laggardkernel opened this issue Nov 29, 2016 · 4 comments
Closed

mounting binaries to /bin makes device stuck at boot logo #18

laggardkernel opened this issue Nov 29, 2016 · 4 comments

Comments

@laggardkernel
Copy link

laggardkernel commented Nov 29, 2016

I just mention this problem in #17 . After adding binaries in the module, the device stuck at the boot logo, I'm sure it's boot logo this time, not the animation. I remember the days on v6 mounting binaries worked well for me, but it has been broken since v7.
As I said,

According to the magisk.log, everything worked well and ended with late_start service mode running.

I will attach all the logs i find in /cache, wish it will help you figure out the trouble. There is some binaries in the /magisk/v4a/system/bin directory.

mount_bin_err.zip

Tested on OnePlus3, OxygenOS 3.2.7, Marshmallow 6.0.1. Magisk v9 commit 670fe85 + phh's superuser.

@laggardkernel
Copy link
Author

laggardkernel commented Dec 7, 2016

Commit c07e9ac fixed the problem of mounting files to /bin. But I stuck at boot animation with a module including frameworks, files like /system/framework/*.jar. Mounting frameworks works well before this commitment. @topjohnwu

Besides, I found out this problem with only Magisk + phh's superuser, Xposed and some test frameworks installed. I also stuck at boot logo once with all my daily Magisk modules installed. I guess there is some other module causing the boot logo stuck. I will try to get more detail by testing the modules one by one later sometime.

Anyway, there's much improvement on the magisk_mask.sh thesedays. We all appreciate your hardwork behind it. Take your time.

update 1: modules with .replace failed to be mounted in commit c07e9ac. Replacing existing system apps without .replace results in app folder loss. Creating an overlay directory systemless-ly failed.

@topjohnwu
Copy link
Owner

All issues are fixed in the massive refactors (c07e9ac and 1e35866)

@laggardkernel
Copy link
Author

laggardkernel commented Dec 9, 2016

I tried all the commitments you submitted yesterday. With the latest commit c9157cc, I still encountered boot logo stuck. I removed binaries in the mod, but no magic happened. Maybe it's related to replacing existing apps since I had problem mounting a modified SystemUI this time. I will try to dig deeper.

@ljani
Copy link

ljani commented Dec 11, 2016

I had problems with (new) /system/framework/*.jar files at v9 too, but they seem to work as of b2431b9. (S7E, stock 6.0.1.) Many thanks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants