With your Chromebook turned off hold down the ESC and Refresh While keeping them held down, press the power button once. – Live Linux USB drive (I’m using Kali Linux 2018.2)ĭeveloper mode will wipe your Chromebook back to factory settings so make sure you back up any data not on your Google drive. Instructions were taken from these locations: THIS WILL DELETE EVERYTHING FROM YOUR CHROMEBOOK. This will REPLACE ChromeOS with Kali Linux. If you want to install Kali Linux on your Chromebook and remove Chrome OS, this tutorial is for you. Figure out what processor you’ve got and go to this link to see if your Chromebook is compatible: This sets the priority to 10, the number of tries to 10 and the succesful value to 1.Īnd that's all i have to say at the moment.I will not tell you if your Chromebook is compatible. Assuming that you've copied the disk image created by the kail-arm build, and then resized the rootfs partion, you should run something like the following command sudo cgpt add -i 1 -P 10 -T 10 -S 1 The key is about adding the priority, tries and succesful flags to the partition that holds the kernel. Some details of what is going on is here: This was a very frustrating excercise for me until i understood what was going on. Resizing the size of the partition deletes some magic chromeos partition information, which then causes the the chromebook to not boot and beep at you. The old version was iirc 1.0.97 and then version i upgraded to was 1.0.123 I upgraded the version of debootstrap and the problem stopped. From what i can tell, older versions of debootstrap do not check to see if /proc is mounted and then fail out. Where the error was complaining about /proc being already mounted. I was getting an issue with the line: LANG=C systemd-nspawn -M $ /debootstrap/debootstrap -second-stage The version of debootstrap needs to be relatively recent. this would cause the build to stop, which then requires deleting the WIP files and starting again. I have no idea why, but several packages just got missed. The build-deps.sh script not installing all the required dependencies. if you want to resize the image to let you use the full capacity of the disk, you'll need some additional magic. If you don't resize the created image, you'll boot just fine. If you don't have any issues with that process, you'll then get a nice image that you then copy (dd) to a SD card or USB stick. The instructions from the readme are basically: git clone I'll go into my issues and the solutions below. In my case i had a lot of issues with getting the basic process to work without issues. Go to and follow the instructions listed in the Readme.md. This is some quick notes on what i needed to do to get kali-arm building. When i first installed it, offensive security had an image avaliable for download ( ) but with the latest release (2020.1) it was not listed, so i decided to try building it myself. I started using Kali-ARM on the chromebook when official ChromeOS support for it finished a few years ago. The size (~11" screen) is pretty compact and keyboard feel is decent too for the size. It's a bit low on the IO (1x USB2, 1x USB3 and a SD card slot) but i have it, and it's still useful. This is an ARM based chreomebook released in 2012. Kail-arm on Samsung Chromebook Kali-ARM on Samsung Snow Chromebook
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |