nolirium / aroc

Android root on Chrome OS
GNU General Public License v3.0
129 stars 51 forks source link

A lot of files cannot be accessed #21

Open ValkyrieViolet opened 5 years ago

ValkyrieViolet commented 5 years ago

Acer R11 running Version 71.0.3578.94 (Official Build) (64-bit)

I tried running the combined patch too, but that didn't seem to work (I tried to use the Pull Request from smartguy1196: #18)

These are the error logs:


chcon: cannot access '/usr/local/Android_Images/Mounted/system/xbin/sugote': No such file or directory
Creating directory system/bin/.ext/.su
Copying su to system/bin/.ext/.su and setting permissions and contexts
cp: cannot stat '/home/chronos/user/Downloads/x86/su.pie': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/bin/.ext/.su': No such file or directory
chcon: cannot access '/usr/local/Android_Images/Mounted/system/bin/.ext/.su': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/bin/.ext/.su': No such file or directory
chgrp: cannot access '/usr/local/Android_Images/Mounted/system/bin/.ext/.su': No such file or directory
Copying supolicy to system/xbin, libsupol to system/lib and setting permissions and contexts
cp: cannot stat '/home/chronos/user/Downloads/x86/supolicy': No such file or directory
chmod: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
chown: cannot access '/usr/local/Android_Images/Mounted/system/xbin/supolicy': No such file or directory
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
ln: failed to create symbolic link '../bin/install-recovery.sh': File exists
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
ERROR: No running Android system found. Unable to patch sepolicy.```
xe500linux commented 5 years ago

I'm running v71.0.3578.127 (Samsung Chromebook 3) and had the same problem. The only way it works is by switching to the Beta release channel, following the prompts, then switching back to the Stable channel (requires powerwash). After this, run the remove-rootfs-verification cmd in crosh (from Nolirium): sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions $(( $(rootdev -s | sed -r 's/.*(.)$/\1/') - 1)) Reboot, and then try running the script again. I still can't get BusyBox or Xposed, but SuperSU works flawlessly after this, and SU apps can edit system files after doing an additional remount cmd (only really necessary for heavy operations, like trying to install Xposed): In ROOT crosh shell, followed by a reboot (from Nolirium): sed -i.old 's|mount rootfs rootfs / remount bind ro.*$|mount rootfs rootfs / remount bind ro|g' /opt/google/containers/android/rootfs/root/init.rc

I have to do the stable->beta->stable switch every time I want to powerwash, otherwise scripts will fail again. I can't get BusyBox or Xposed because everytime I install them, Chrome OS "fixes" itself automatically, which is a mandatory powerwash. The script seemed to skip the BusyBox part, or at least I didn't see any error codes. But it's definitely not there - just SuperSU.

Specifically, I used smartguy's 01Root.sh with the normal 02patch, not the combined script.

ghost commented 5 years ago

I'm having the exact same problem with the Pixel Book, and have since the day I received this device. The above recommendation doesn't fix the problem either, supersu does not work flawlessly for me.

jshiftr4b commented 4 years ago

i ran the combined script, the only error i had said somthing like, "No Android system runing : unable to patch policy". i am using a google pixelbook with developer mode on & on the developer-unstable channel!

Please help. THANKYOU!..