:~$ echo "console=tty1 debug verbose root=/dev/sda3 rootwait rw rootfstype=ext4" > /tmp/config-usb Patch the kernel, in our case, with wireless injection patches. :~$ git clone -b chromeos-3.4 chromeosĭescription = "Chrome OS kernel image with one or more FDT blobs" ĭata = /incbin/("arch/arm/boot/exynos5250-snow.dtb") Once that’s done, proceed with the following instructions.įetch the Chromium kernel sources and place them in our development tree structure: :~$ mkdir -p ~/arm-stuff/kernel/ If you’re not using ARM hardware as the development environment, you will need to set up an ARM cross-compilation environment to build an ARM kernel and modules. Compile the Samsung Chromium Kernel and Modules :~$ gdisk kali-custom-chrome.img root/etc/nf :~$ parted kali-custom-chrome.img -script - mktable gpt Partition and Mount the Image File :~$ parted kali-custom-chrome.img -script - mklabel msdos :~$ dd if=/dev/zero of=kali-custom-chrome.img conv=fsync bs=4M count=7000Ġ3. :~$ sudo apt install -y kpartx xz-utils gdisk uboot-mkimage u-boot-tools vboot-kernel-utils vboot-utils cgpt Next, we create the physical image file that will hold our Chromebook rootfs and boot images. By the end of this process, you should have a populated rootfs directory in ~/arm-stuff/rootfs/kali-armhf. Start by building a Kali rootfs as described in our Kali documentation, using an armhf architecture. You’ll need to have root privileges to do this procedure, or the ability to escalate your privileges with the command “sudo su”.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |