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

sh: 713: cd: can't cd to /usr/local/Android_Images/Mounted/system/priv-app #13

Closed
kgptzac opened this issue Dec 1, 2018 · 3 comments
Closed

Comments

@kgptzac
Copy link

kgptzac commented Dec 1, 2018

Samsung Chromebook Pro here running beta version of Chrome OS (Version 71.0.3578.71 (Official Build) beta (64-bit))

And for the love of the gods I can't figure out how to select and scroll down pages in crosh to copy the full logs I'll only copy a few lines...

Converting system.raw.expanded.img to sparse image
fallocate: fallocate failed: keep size mode is unsupported
Mounting system.raw.expanded.img
SELinux successfully set to 'Permissive' temporarily
Copying Android system files
Moving original rootfs image to /opt/google/containers/android/system.raw.img.bk
Creating symlink to /usr/local/Android_Images/system.raw.expanded.img
Now placing SuperSU files. Locations as indicated by the SuperSU update-binary script.

Creating SuperSU directory in system/priv-app, copying SuperSU apk, and setting its permissions and contexts
sh: 713: cd: can't cd to /usr/local/Android_Images/Mounted/system/priv-app
Copying su to system/xbin/su,daemonsu,sugote, and setting permissions and contexts
sh: 325: cd: can't cd to /usr/local/Android_Images/Mounted/system/xbin
cp: cannot create regular file '/usr/local/Android_Images/Mounted/system/xbin/su': No such file or directory
cp: cannot create regular file '/usr/local/Android_Images/Mounted/system/xbin/daemonsu': No such file or directory
cp: cannot create regular file '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/xbin/su': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/xbin/daemonsu': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/xbin/su': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/xbin/daemonsu': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/su': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/daemonsu': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/su': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/daemonsu': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
Creating directory system/bin/.ext/.su
sh: 351: cd: can't cd to /usr/local/Android_Images/Mounted/system/bin
@nolirium
Copy link
Owner

nolirium commented Dec 4, 2018

It's OK, you got the relevant part. (I know what you mean about scrolling and selecting in crosh/hterm. There may be an easier way, but I usually zoom out with Ctrl- until the text is postage stamp sized.).

Not sure why fallocate is failing now though. Possibly something's changed in CrOS, the script may need updating again...

Could you perhaps try using the combined rooting script, as that 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

@kgptzac
Copy link
Author

kgptzac commented Dec 23, 2018

I've installed the latest beta of chrome os and ran the combined script and no issue was seen. Thanks!

@kgptzac kgptzac closed this as completed Dec 23, 2018
@ghost
Copy link

ghost commented Dec 23, 2018

Why didn't it work for me then?

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

2 participants