nolirium / aroc

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

Playstore broke after rooting #3

Open Lila14 opened 6 years ago

Lila14 commented 6 years ago

I'm running Version 63.0.3239.140 (Official Build) (64-bit)

uname -a output is: Linux localhost 3.18.0-16288-g64d05cf80004 #1 SMP PREEMPT Mon Jan 8 23:21:11 PST 2018 x86_64 Intel(R) Celeron(R) CPU N3060 @ 1.60GHz GenuineIntel GNU/Linux

Device is a Samsung XE500C13

After applying the scripts successfully, I was able to open apps installed via the playstore, but I did a reboot and after that 2nd reboot those apps and the playstore itself stopped working. Trying to re-enable the playstore functionality in chrome's settings led to an failure after accepting the terms and conditions with the "something went wrong" message.

The only solution was to rollback the OS img.

nolirium commented 6 years ago

Not sure what went wrong here, I'm afraid. I might suggest retrying, it you haven't already, perhaps with the combined script (which should root and patch selinux without requiring a reboot in between). You should be able to run the combined script with the following command (all one line):

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

Just to mention as well, in case you weren't aware, in the case of a failed rooting attempt, or if you otherwise want to restore the original (unrooted) Android system, the easiest way to do this is normally to just restore the backed-up original Android system image. Normally it shouldn't be necessary to roll back or powerwash ChromeOS in its entirety. You should be able to restore the original Android system image with the following command (all one line):

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

pinuke commented 5 years ago

If the play store breaks, you can use a recovery image. It will delete everything, but I have been having the same issue when this rooting method breaks.

It likely happens, because the Android image didn't get installed properly.