[GUIDE]Triple Booting Remix OS, Linux and Chrome OS - Remix OS for PC

The trick is to install Chrome OS first, shrink the Chrome OS main partition, and install Linux and Remix in their own partitions.
Download Chrome OS from here and install it as directed. It will destroy everything else on the disk, and make a large partition for data storage, and another 11 partitions for whoknows what.
Boot Linux with a live USB stick or CD. Shrink the first, large partition using parted. I started out with a 450GB partition that I shrunk to 180. Make 5 new partitions using fdisk or whatever you like for partitioning. I made a 250 MB partition for Linux boot, a 120GB partition for Linux /, a 120GB partition for Linux /home, an 8GB partition for Linux swap, and a 30GB partition for Remix. Use your own judgment.
Install Linux in the Linux partitions. I use Gentoo, but you can use whatever you like.
Boot up linux.
Install Remix OS in the last partition:
Download the zip file from this thread. Unzip the file; it contains an installer for Windoze(<somethingorother>.exe), and an .iso file. Make a temporary directory
Code:
mkdir /mnt/tmp
and mount the iso in it:
Code:
mount -o loop <name_of_iso>.iso /mnt/tmp
Format the Remix partition, mount it, and copy the files in the iso to the Remix partition (in my case it is /dev/sda17):
Code:
mkfs.ext4 /dev/sda17
mkdir /mnt/remix
mount -t auto /dev/sda17 /mnt/remix
cd /mnt/tmp
find . -xdev -depth -print | cpio -puvdm /mnt/remix
Make a grub menu entry for Remix OS in /etc/grub.d/40_custom:
Code:
#!/bin/sh
exec tail -n +3 $0
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
menuentry "REMIXOS Resident Mode" --class android-x86 {
insmod part_gpt
search --file --no-floppy --set=root /system.img
set root=(hd0,17)
linux /kernel initrd=/initrd.img quiet root=/dev/ram0 androidboot.hardware=remix_x86
androidboot.selinux=permissive quiet SRC= DATA=/ CREATE_DATA_IMG=0
## VGA=791
video=uvesa DPI=96 UVESA_MODE=1280x800
initrd /initrd.img
}
You may need a different VGA= or MODE= depending on your monitor.
Make a data directory. For some reason it doesn't get created automatically:
Code:
mkdir /mnt/remix/data
Assuming grub is installed, make the grub menu and finish up.
Code:
mount /boot
grub2-mkconfig -o /boot/grub/grub.cfg
umount /boot
umount /mnt/tmp
umount /mnt/remix
rmdir /mnt/remix
When you reboot, you will see two entries for Chrome OS, generally listed as "Unknown Linux Distribution". Either one will work to boot Chrome.
Follow the directions in the Remix thread listed above on how to enable the Google Play store on Remix.
Took me a lot of trial and error. Hopefully it will be easier for you.

---

what do you mean it destroy everything on disk

---

deepakhope said:
what do you mean it destroy everything on disk
Click to expand...
Click to collapse
If you run the installer that comes with it, it will wipe out anything that was on the disk before. There's no way to install it and leave what was there before untouched. That's why you need to install Chrome OS first.

---

pixbuf said:
If you run the installer that comes with it, it will wipe out anything that was on the disk before. There's no way to install it and leave what was there before untouched. That's why you need to install Chrome OS first.
Click to expand...
Click to collapse
That's what held me off trying ChromeOS; can you at least select to install to an external drive with it?
Just a couple points from OP;
1. You probably should be saying CloudReady (open-source version of ChromiumOS) rather than saying ChromeOS; as that is a hardware-specific closed source OS.
2. There's a bit of redundancy in your grub:
Code:
menuentry "REMIXOS Resident Mode" --class android-x86 {
insmod part_gpt
[color=red][b]search --file --no-floppy --set=root /system.img
set root=(hd0,17)[/b][/color]
linux /kernel initrd=/initrd.img quiet root=/dev/ram0 androidboot.hardware=remix_x86
androidboot.selinux=permissive quiet SRC= DATA=/ CREATE_DATA_IMG=0
}
Those two lines are doing the same thing - removing the first one might result in a faster boot (probably non-noticable); removing the second should make the whole entry partition no. independent.

---

How could I add windows 10 to the mix here?
Institute chromium, followed by Linux and then windows and finally restore grub?