I was not able to run android-sh without re-enabling permissive mode after rebooting Chrome OS having manually run the steps in root.sh (the script itself did not run properly for me).
Similarly I thought it might be helpful to continue to have a rootfs writeability check in root.sh as there was in aroc:
check_writeable_rootfs() {
# At present, we try and create a file on the CrOS rootfs to see if rootfs verification is disabled.
# If we couldn't create the file, rootfs verification likely still needs to be turned off.
if [ -e /usr/local/arob_writable_test ]; then
rm /usr/local/arob_writable_test
fi
touch /usr/local/arob_writable_test 2> /dev/null
if [ ! -e /usr/local/arob_writable_test ]; then
echo "Error!"
echo "Unable to modify system!"
echo "You can disable rootfs verification by running the following command, then rebooting."
echo "sudo /usr/share/vboot/bin/make_dev_ssd.sh --remove_rootfs_verification --partitions $(( $(rootdev -s | sed -r 's/.*(.)$/\1/') - 1))"
echo "Please run the "remove_rootfs_verification" command now, then reboot and run this script again."
exit 1
fi
rm /usr/local/arob_writable_test
}
I was not able to run
android-sh
without re-enabling permissive mode after rebooting Chrome OS having manually run the steps inroot.sh
(the script itself did not run properly for me).Similarly I thought it might be helpful to continue to have a rootfs writeability check in root.sh as there was in aroc: