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

no such file or directory #14

Open
ghost opened this issue Dec 4, 2018 · 12 comments
Open

no such file or directory #14

ghost opened this issue Dec 4, 2018 · 12 comments

Comments

@ghost
Copy link

ghost commented Dec 4, 2018

image
did everything but this happends

chrome book acer,
Version 70.0.3538.110 (Official Build) (64-bit)

@nolirium
Copy link
Owner

nolirium commented Dec 4, 2018

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:

curl -Ls https://raw.githubusercontent.com/nolirium/aroc/onescript/RootandSEpatch.sh | sudo sh

@ghost
Copy link
Author

ghost commented Dec 4, 2018

same error
image

@ghost
Copy link
Author

ghost commented Dec 4, 2018

is there anyway to install magisk?

@nolirium
Copy link
Owner

nolirium commented Dec 4, 2018

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.

is there anyway to install magisk?

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.

@ghost
Copy link
Author

ghost commented Dec 4, 2018

image
now its not loading

@nolirium
Copy link
Owner

nolirium commented Dec 4, 2018

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:

sudo mv /opt/google/containers/android/system.raw.img.bk /opt/google/containers/android/system.raw.img

@proable
Copy link

proable commented Dec 10, 2018

im having a similar problem.
log.txt

@proable
Copy link

proable commented Dec 10, 2018

chgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
cp: cannot stat '/home/chronos/user/Downloads/x86/libsupol.so': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
Copying sh from system/bin/sh to system/xbin/sugote-mksh and setting permissions and contexts
Adding extra files system/etc/.installed_su_daemon and system/etc/install-recovery.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
Symlinking system/bin/install-recovery.sh to system/etc/install-recovery.sh
Adding system/bin/daemonsu-service.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
Creating file init.super.rc in Android rootfs
Adding daemonsu service to init.super.rc
Adding 'import /init.super.rc' to existing init.rc
Substituting '|mount rootfs rootfs / remount bind rw' for '|mount rootfs rootfs / remount bind ro' in existing init.rc
A backup of init.rc will be stored as init.rc.old
Attempting to install BusyBox into Android container
Executing './busybox --install -s ../xbin'
./busybox: 1: ./busybox: Syntax error: word unexpected (expecting ")")
Replacing absolute symlinks created by 'busybox --install' with relative symlinks

ERROR: No running Android system found. Unable to pachgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
cp: cannot stat '/home/chronos/user/Downloads/x86/libsupol.so': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/lib/libsupol.so': No such file or directory
Copying sh from system/bin/sh to system/xbin/sugote-mksh and setting permissions and contexts
Adding extra files system/etc/.installed_su_daemon and system/etc/install-recovery.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/etc/install-recovery.sh': No such file or directory
Symlinking system/bin/install-recovery.sh to system/etc/install-recovery.sh
Adding system/bin/daemonsu-service.sh
cp: cannot stat '/home/chronos/user/Downloads/common/install-recovery.sh': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/bin/daemonsu-service.sh': No such file or directory
Creating file init.super.rc in Android rootfs
Adding daemonsu service to init.super.rc
Adding 'import /init.super.rc' to existing init.rc
Substituting '|mount rootfs rootfs / remount bind rw' for '|mount rootfs rootfs / remount bind ro' in existing init.rc
A backup of init.rc will be stored as init.rc.old
Attempting to install BusyBox into Android container
Executing './busybox --install -s ../xbin'
./busybox: 1: ./busybox: Syntax error: word unexpected (expecting ")")
Replacing absolute symlinks created by 'busybox --install' with relative symlinks

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 do so nowtch 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 do so now

@pinuke
Copy link

pinuke commented Dec 30, 2018

This looks a lot like the errors I was getting for #17. I'm applying a fix right now

@nashi2000
Copy link

check smartguy fix.....no space is because ARM file was being created which was smaller.

@ghost
Copy link
Author

ghost commented May 15, 2019

is their a fix yet?

@bline
Copy link

bline commented Oct 24, 2020

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:
sed: can't read /../init.rc: No such file or directory
and subsequently so does su after reboot in the 02SEPatch.sh

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

5 participants