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

Initialization doesn't abort gracefully if binary with compat=USER is missing #528

Closed
d4rken opened this Issue Sep 27, 2016 · 1 comment

Comments

1 participant
@d4rken
Owner

d4rken commented Sep 27, 2016

If for some reason we can't get a user compatible binary, but could get a root compatible binary, setup will continue instead of gracefully aborting.

Not yet sure how it can happen that we get a root binary but no user binary?

@d4rken d4rken added this to the v4.3.6 milestone Sep 27, 2016

@d4rken d4rken closed this Sep 27, 2016

@d4rken

This comment has been minimized.

Owner

d4rken commented Sep 27, 2016

Found the reason...

V/SDM:Shell:StaticExecutor: mount -o ro,remount /system /system
V/SDM:Shell:StaticExecutor: Error: mount: '/system' not in /proc/mounts

Nougats native mount applet doesn't like that syntax...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment