-
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
A lot of files cannot be accessed #21
Comments
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): 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. |
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. |
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. |
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:
The text was updated successfully, but these errors were encountered: