-
Notifications
You must be signed in to change notification settings - Fork 51
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
no such file or directory #14
Comments
From the screenshot I can't be sure, but I think you might be running into the same problem as in issue #13. If so, the rooting script might need to be updated slightly before it will work again. In the meantime, you could try using the combined rooting script, since it uses a slightly different method to create the container. The command to run the combined script is as follows:
|
is there anyway to install magisk? |
Could you scroll up a bit? Or zoom out, perhaps, so more of the text is on show? (you could zoom out enough so that the whole script output is visible, then copy and paste it here). As it might be useful to know at what point the errors start occurring, and I can't see that in your screenshots.
Possibly, at least as a root manager, but it might be something of a hassle to get it set up. I'll look into it. |
Now it's looking for the original container, but it's been replaced with a symlink (by the script, previously). The script normally keeps a backup of the original Android container; at this point I might suggest attempting to restore the backup, then rebooting (the reboot is important), then trying again with the RootandSEpatch.sh. You should be able to restore the original Android container with:
|
im having a similar problem. |
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory ERROR: No running Android system found. Unable to pachgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory ERROR: No running Android system found. Unable to patch sepolicy. Please check the output of this script for any errors. You will need to reboot the Chromebook in order to properly re-mount the new rooted Android container. Please check the output of this script for any errors. You will need to reboot the Chromebook in order to properly re-mount the new rooted Android container. |
This looks a lot like the errors I was getting for #17. I'm applying a fix right now |
check smartguy fix.....no space is because ARM file was being created which was smaller. |
is their a fix yet? |
I had the same file no found errors and I managed to get this working by downloading the supersu zip from the url in the script and extracting it to ~/Downloads first. Though the script still failed in one place: |
did everything but this happends
chrome book acer,
Version 70.0.3538.110 (Official Build) (64-bit)
The text was updated successfully, but these errors were encountered: