imperador/chromefy

Project Croissant: Install Chrome OS on any Computer - Transforming Chromium to Chrome

This project is not regularly maintained anymore. We suggest you to use Brunch Framework instead

Project Croissant

Transforming Chromium to Chrome

You can find us at the Telegram Group: https://t.me/chromeosforpc

Please, ask your questions at the group and don't PM the admins. :)

You can also follow us on Twitter: https://twitter.com/CroissantDev

Observations

• You need a Chromium installation running for the Methods 2 and 3

  We strongly recommend using ArnoldTheBats Chromium Stable (Vanilla) builds. Just deploy the img to a USB Stick, Rufus and similar programs will do the work.

• You have to be logged in (because if you don't, the initial setup won't work).
• We are not responsible for any damage made to your computer by you or by your dog.
• If you are using a Chromebook, you do not need to install Chromium. Just grab a suitable recovery image and follow the installation instructions while in ChromeOS native.
• Don't use zip files. Extract and use the BIN file that is inside of it

---

Required Files

• An official Chrome OS recovery image (downloads on the right; RECOMMENDED: eve (best) or pyro are the most complete images). It must be from the same chipset vendor (Ex: Intel, ARM or RockChip)

  You can use THIS LIST to search for your processor, and then look at the internet which one is the best (the closest, the better).

• The TPM2 emulator (swtpm.tar) (not compatible with all Chromium kernels) or another Chrome OS recovery image from a TPM 1.2 device (EX: caroline); this is only needed if using an image from TPM2 device to fix a login issue, which is most likely the case for newer ones. (If you don't know which TPM1.2 image to choose, just pick caroline)
• An image from a Chromium OS distribution (EX: ArnoldTheBats Builds).
• The Croissant.sh installation script (for the Method 1 and Method 2, the easy ways).

Installation Methods

Project Croissant has three installation options. The first option generates an img ready to deploy into your usb stick and then you can boot from it to install Chrome at your computer. The last two options will probably require you to resize the third partition of your sdX drive (EX: sda3 inside sda) from its current size to atleast 4GB; I suggest using Gparted live USB to resize it;

Option 1: Automated generation of Chrome img

• It uses a script and you don't need to resize partitions.
• Requires: One computer running Linux or Chromium.
• It will generate a Chrome img ready to install.

Option 2-A: Automated Script (drive)

• It uses a script, so the migration is easier.
• Requires: 2 USB sticks: The first to deploy the Chromium img on it and the second to store the two recovery files.
• The script can downsize your sdX5 drive and resize sdX3 with the generated free space (will ask first).

Option 2-B: Automated Script (partition)

• It uses a script, so the migration is easier.
• Requires: 2 USB sticks: The first to deploy the Chromium img on it and the second to store the two recovery files.
• As said before, you will need to resize the third partition of your sdX drive (EX: sda3 inside sda, if your main drive is sda). In this method you can either downsize sdX1 (data partition) or delete the sdX5 partition (we won't need it) to get more unallocated space.

Option 3: Manual Configuration

• It requires some patience and more commands. And it also has several steps that need to be done.
• It can be done with only one USB stick.
• Here you can't just delete the fifth (sdX5) partition, because you will need it.

Choose the best method for you and follow the installation process.

---

Installation Process

With the automated script method you can either generate your own Chrome img ready to run and install (Option 1) or you can also apply the Chrome into a installed Chromium at your computer (Option 2). I strongly suggest you to use the first one, because it will also allows you to have a backup img to deploy anytime you want to install it on a new pc.

Option 1: Automated Script - Generating your own Chrome img:

Here you will generate your img and then deploy it to a usb stick, this will allow you to install it on your computer. If you already have a Project Croissant generated ChromeOS img, you can deploy it to a usb stick, boot from it at your computer and then jump to the Installing an img at your computer. We won't provide the imgs.

Generating the img

Log into a Linux or Chromium OS computer. Download your Chromium image (e.g Arnold the bat), your ChromeOS recovery image (e.g Eve), TPM2 emulator (swtpm.tar) or TPM1.2 ChromeOS recovery image (e.g Caroline [https://cros-updates-serving.appspot.com]) and the Croissant.sh script (https://github.com/imperador/chromefy/releases). Place all the files in one location. Downloads is a good idea.

In the next step you need to replace '{path}' with the location of all these files. If you put them in Downloads then {path} would be replaced with 'home/chronos/user/Downloads'. If the files are in another folder, replace it with the other folder location. If you don't know how to discover the path, internet is your friend, you can learn how to discover it.

Note: Your original chromium.img file will be replaced, so backup it if you want

Now open a terminal (if you’re using ChromiumOS press CTRL + ALT + T, then type the command shell.) For any other Linux OS a normal terminal is fine, and then type the following commands:

sudo su
cd {path}
bash  croissant.sh  chromium.img  recovery.bin  caroline.bin

or

sudo  bash  croissant.sh  chromium.img  recovery.bin  swtpm.tar

Reminder: {path} is the folder where you saved your files

After finishing the process, you will have the chromium.img. It is now a full ChromeOS img. You can use any program to deploy it to a usb stick and boot from it. Programs like Etcher (Windows or Linux), Rufus (Windows only) and Chromebook Recovery Utility (Chromium only) will do the work. Just deply the img to your usb stick.

Installing an img at your computer

If you already have a Project Croissant generated ChromeOS img, you can deploy it to a usb stick and then just boot from it at your computer.

When the login screen appears, press "CTRL + ALT + F2" and type the following commands:

chronos
sudo su
cd /
sudo   /usr/sbin/chromeos-install  --dst  /dev/sda  --skip_postinstall

When the process finish, turn off your computer, remove your usb stick and turn it on again. It will boot into your Chrome OS device. Congratulations!

Fixing Grub

If it doesn't work after your reboot, just boot into your USB stick again, make sure you have an internet connection, go to the shell command line and type this command:

curl  -L  https://goo.gl/HdjwAZ   |  sudo  bash  -s  /dev/sda

Updating Chrome OS

To update Chrome OS, repeat the process, but when you run chromeos-install make sure to add the flag --preserve_stateful like so:

chromeos-install --dst /dev/sda --skip_postinstall --preserve_stateful

This ensures that existing Chrome OS user data is not wiped.

---

Option 2: Automated Script - Applying Chrome to Chromium:

Flash the selected Chromium OS build on the first USB, boot into the live USB and install it on your HDD/SSD by typing the following command on the shell (keep in mind this will wipe your HDD, so backup everything you need and don't blame us later)

sudo /usr/sbin/chromeos-install --dst YOURDRIVE (Ex: /dev/sda)

• Now make sure that your chromium HDD/SSD installation is working before proceeding. Also save your chosen recovery image (that we will be calling chosenImg.bin), swtpm.tar or caroline recovery image (here called carolineImg.bin) and the Installation script to the second USB stick.

OPTION 2B ONLY: Resize the third partition of your sdX drive (EX: sda3 inside sda) from its current size to atleast 4GB (suggestion: search about using Gparted live USB to resize it). And remember: You can either downsize sdX1 (data partition) or delete the sdX5 partition (we won't need it) to get more unallocated space.

Multiboot users: You must use the ROOT-A partition instead of your third partition (sda3).

After this, connect both USB sticks to you computer and boot from your live USB again (with Chromium), make sure you have your Chrome OS images available (on the second USB stick) and go to the folder where you downloaded the croissant script and run it with the following command (considering your system partition as /dev/sda3):

OPTION 2A:

sudo bash croissant.sh /dev/sda /path/to/chosenImg.bin /path/to/carolineImg.bin_OR_swtpm.tar

OPTION 2B:

sudo bash croissant.sh /dev/sda3 /path/to/chosenImg.bin /path/to/carolineImg.bin_OR_swtpm.tar

Don't leave live USB yet, make a powerwash (manually) by typing

sudo mkfs.ext4 YOURDATAPARTITION(Ex: /dev/sda1)

You can now reboot and enjoy your new "chromebook"

To update, repeat the process, but:

1. when you run chromeos-install make sure to add the flag --preserve_stateful like so:

	* chromeos-install  --dst  /dev/sda  --skip_postinstall --preserve_stateful

2. Run Option 2B, *even if* you installed with option 2A.

3. Omit the last step where you run mkfs.ext4

---

Option 3: Manual Configuration

After finishing installing a Chromium OS, open the browser and press CTRL+ALT+T to open chroot Type:

shell
sudo su

Installing Chrome OS (some notes):

• If the file is in Downloads folder, replace '{path}' with 'home/chronos/user/Downloads', if it is at another folder, replace it with the other folder location. Use the path accordingly with your file location
• Save your chosen recovery image (that we will be calling chosenImg.bin) and caroline recovery image (here called carolineImg.bin) at this folder
• Any password or username will be 'chronos'

Configuring the new Chrome partition

Use the following commands to configure the sda5 (or nvem0n1p5) and other basic things (the exemple is using caroline recovery file): Type "lsblk" to know your partitions. Search for sda, sdb or nvme0n1 with the size of your usb or HDD. In the following commands, change "sda" for the one that you've found:

losetup -fP {path}/chosenImg.bin
mkdir /home/chronos/image
mkdir /home/chronos/local
mkfs.ext4 /dev/sda5
mount /dev/sda5 /home/chronos/local

Copying the img to the local path

Type "losetup" to get a list, search for loop{number} that has the img file on it Memorise the number. So if it is loop2, then {number} = 2 Type the following commands (using the {number} that you got in the last step):

mount /dev/loop{number}p3 /home/chronos/image -o loop,ro
cp -av /home/chronos/image/* /home/chronos/local
rm -rf /home/chronos/local/lib/firmware
rm -rf /home/chronos/local/lib/modules/ 
cp -av /lib/firmware /home/chronos/local/lib/
cp -av /lib/modules/ /home/chronos/local/lib/
rm -rf /home/chronos/local/etc/modprobe.d/alsa-skl.conf

Change in /home/chronos/local/etc/selinux/config the word enforcing to permissive with the following command:

sudo sed '0,/enforcing/s/enforcing/permissive/' -i /home/chronos/local/etc/selinux/config

Type "sync" and press Enter

Now restart your computer. When the screen with the boot options appear (the grub), press 'e' FAST (or it will boot into the chromium). You will have to change the root for: root=/dev/sda5

Now press F10. If it boots corectly, you are ready to go

ADDITIONAL:

• Using ChromeOS with other Operating systems (Multiboot)
• Updating ChromeOS (for the Method 2)
• Resolving Problems With Login

---

Using ChromeOS with other Operating systems (Multiboot)

Not everyone is willing to wipe their hard drives just to install ArnoldTheBats Chromium as a base, and for those people we have made a handy multiboot guide. You can check it out here: MultiBoot Guide

Chainloading is not a requirement with ArnoldTheBats Chromium, however you may need to when you make the initial ChromeOS upgrade. Also remember to save your partition layout in between upgrades to newer ChromeOS versions, and also when you initially upgrade to ChromeOS otherwise it will not find the State partition which is needed for a successful boot.

---

Updating ChromeOS (for the Method 3)

Updating ChromeOS and Chromium Native: The Setup

You will need a Live USB of any Linux distribution. I recommend Mint or Ubuntu. Note: Replace "chronos" with the your username if dual booting or the name of the of distribution if booting from USB

Find and download the updated recovery image for the device you used at chrome.qwedl.com

Now type in the following commands in the Linux terminal:

losetup -fP /home/chronos/user/Downloads/chromeos_image.bin
losetup -fP /home/chronos/user/Downloads/chromium_image.bin
mount /dev/sda5 /home/chronos/local
losetup

The last call of losetup without paramaters prints a list of Loop devices, find the one that corresponds to your ChromeOS and Chromium Image and then type:

mount /dev/loop{chromeos_number}p3 /home/chronos/image -o loop,ro
mount /dev/loop{chromium_number}p3 /home/chronos/native -o loop,ro

Updating both ChromeOS and Chromium Native: The actual upgrade

Remember, the commands outlined here must be done in EXACTLY this order to guarantee everything goes smoothly. IF you don't do this and find neither the touchscreen, trackpad, or keyboard works, that's on you. Not me, or anyone else.

rm -rf /home/chronos/local/*
cp -av /home/chronos/image/* /home/chronos/local
rm -rf /home/chronos/local/lib/firmware
rm -rf /home/chronos/local/lib/modules/
cp -av /home/chronos/native/lib/firmware /home/chronos/local/lib/
cp -av /home/chronos/native/lib/modules /home/chronos/local/lib/
rm -rf /home/chronos/local/etc/modprobe/alsa-.conf

(Alsa-* being whatever the config name is, in my case it would be Alsa-skl.conf)

Change in /home/chronos/local/etc/selinux/config the word enforcing to permissive with the following command:

sudo sed '0,/enforcing/s/enforcing/permissive/' -i /home/chronos/local/etc/selinux/config

If you use multiboot, do not forget to change /usr/sbin/write_gpt.sh again. For details, see the multiboot section above.

---

Resolving Problems With Login

Bypassing TPM for select recovery images (Eve, Fizz, etc)

• Instructions: Done automatically using the script above so long as your second argument is a TPM2.0 image(Such as Eve or Fizz) and the third argument is a platform1.2 image (Such as Asuka or Caroline)
• The reason we need to bypass TPM2.0 for newer recovery images is because these images fail to login otherwise, or may get stuck in a login loop. Images such as Sentry, Asuka, and Caroline are using TPM1.2 which allows login to go successfully

---

Credits:

• imperador for the Project Croissant idea and the scripts
• TCU14 for upgrading, and the MultiBoot guide
• alesimula for the installation script and also for the XDA Tutorial
• DiogoSilva48 from the Telegram Group for the corrections on the firmware migration and also for creating and managing the Telegram Group
• sublinhado for writing down the steps needed for the TPM bypass method
• Dnim Ecaep from the Telegram Group for the shell command to change the SELINUX to permissive
• Danii from the Telegram Group for the work on the TPM bypass method and TPM emulation method

Big Thanks:

• allanin for all of his ideas on Arnoldthebat discussion, most part of the scripts here is based on his ideas
• arnold for his awesome builds
• stefanberger for swtpm, a Libtpms-based TPM emulator we use.
• ++ some more that I will add soon (remind me if I forgot someone)

chromefy's Issues

Incredibly long boot time

No matter which time it is starting up, the Chrome OS screen sits for several minutes before successfully loading the OS. The process I've followed several times with various images all resulting the same way. The OS functions great once it's loaded, even wake up is snappy. I'm using Eve and Caroline on a Yoga 2 Pro i7 - any other info I can provide I will.

"Missing OS"

So, after a succesfull install my PC says "Missing OS", so I tried running the "curl -L https://goo.gl/HdjwAZ | sudo bash -s /dev/sda" but I don't have any wifi, is there any way I could run it without internet maybe?

Touchpad Lag/No Gesture Support

I assembled a ChromeOS image using arnoldthebats Chromium image, eve, and caroline per the recommendations because that seemed to be the best for my device(Dell e7250 i7 5th, trackpad registers as AlPS/2 ALPS Glidepoint via evtest). Everything else seems to work including the touch screen, but trackpad is laggy(as if it sticks) and multitouch gestures(3+) and tap to click/right click don't work. 2 finger scrolling and pinch to zoom do, however. I have tried various workarounds including editing /etc/chrome_dev.conf, /etc/gesture/40-touchpad-cmt.conf and 50-touchpad-cmt-eve.conf(the latter of which I don't think would do anything considering it doesn't share the same identifier) and editing the grub.conf to try and force different drivers. Everything else otherwise works fine.

I remember(inversely) that when I was putting ubuntu on my old falco that I needed to add/change some synaptics finger settings to the .conf file and I wonder if something's just missing there. I used the Special .img build and the trackpad works fine in Ubuntu live, as I got to test it there when I was resizing partitions.

One last thing, although I don't think it matters, but I installed via writing the image to my drive directly with rufus and an external msata reader, afterwhich I resized the partitions.

One last edit: the trackpad isn't so much laggy or glitchy as it is that it hesitates before it starts moving. If I get it moving and keep it moving, even varying my pace it tracks accurately. This, again, makes me think there could be something to do with the conf file needing some settings adjusted but I'm not sure.

Legacy (BIOS) Support

I have tried to run chrome os on my old ASUS Eee PC 1008P it doesn't have UEFI support.
Its not working. Also do i need x86 recovery images for this to work? Theres not much of them.

Legacy Bios

Would you be able to make the grub installer script work with legacy bios or is it not possible. I have chrome os isntalled but i just installed the usb img to my hdd as it wouldn't work after installing

Can't boot to generated image

Hi, thanks for the release! I got problems booting the usb installer, hope you guys can help me understanding the issue!

My target device: Thinkpad T420.

I choose method 1, which generating ChromeOS image. To do that I'm using Antergos on my T440. I'm using latest chromiumos_image.img, chromeos_11021.81.0_eve_recovery_stable-channel_mp, and chromeos_10895.56.0_caroline_recovery_stable-channel_mp.

After I finished generating the image (no error whatsoever), I'm using Rufus to put the image into a 8GB usb stick on my windows machine.

Then I booted up the usb stick on T420 in UEFI only, there's a grub with 5 choices (boot image A, boot image B, verified boot img A, verified boot img B, and other image -- maybe not exact word by word since I'm currently on the go. I also tried the Legacy boot first option, same result, so I think the usb stick is booting on UEFI.

Any idea why?

Issues with method 1, claiming no disk space?

I have tried method 1 a few times on different Linux distros - they all have plenty of disk space but every build with Chromefy errors out with random out of space errors like:

cp: error writing ‘/home/chronos/local/usr/lib64/libtspi.so.1.2.0’: No space left on device
cp: failed to extend ‘/home/chronos/local/usr/lib64/libtspi.so.1.2.0’: No space left on device

The home mount point has 50GB free, or more, on each distro I have tried - One Centos, One Ubuntu and a Mint machine...

Any ideas what may be the issue? (I Thought inodes and a few other things, but they all check out fine)

Malware warning on chrome.qwedl.com

When following the guide: 'Getting the right IMG for YOUR @pc'
and attempting to navigate to chrome.qwedl.com I get the following warning from my router:

I think it would be better to obtain the image from the cros-updates site. You can obtain official recovery images for the last few versions under the 'Recovery' column for each boardname / device.

-DennisLfromGA

No Linux Apps

Android Apps are working fine, but no option for Linux apps under settings.

Using Eve 72, with Caroline 72 for TPM fix.

Also cannot see the flags, so I guess the TPM is not working still, would this cause no Linux apps?

Otherwise working well on HP X2 Elite G1.

OTA Updates?

What's about OTA updates? My "Chromebook" is always saying that I'm on the latest version (71)...

Thanks

Long boot time from ssd but not from hdd.

After successful installation with method 1 it takes about 10 minutes to boot from ssd. Same installation on HDD boots without any problems.

Upgrade image script

An option in the script to create a new image that is split into the Root-A and kernel parttitons so they can be imaged using DD to a partition

The logic for this is for making bootable Chrome OS USB devices and easily updating them.

Raspberry Pi 3

Aweosme work here!

qq - there are official versions of chrome for ARM, however - can we get this working on the Raspberry pi?

i have both the 3b and 3b+ and neither boots...

Chromefy on a Chromebook

I saw some posts over at Reddit about Chromefy on a Chromebook to get Android apps working. I was wondering, how can you install Chromefy on a Chromebook?

(question) what is this actually?

from what I understand, this somehow merge chromium os with chrome os. correct? basically hackintosh, but chrome os?

also generating your chrome imgs : you said "We won't provide the imgs." Why? Is this is not the easiest way?

successfully chromefy pyro into my nex hz550 book, but google play dosent work

google play cannot be loaded, it shows something wrong, so does the linux function.
anyone has the same issue?

Boot stanza for rEFInd? (Type 3/partition)

Has anyone gotten this to work with rEFInd? The GRUB entries are unusual (at least to me) and I’m having a hard time translating them.

I’m also having issues where sometimes the boot location is the EFI partition (sdb5 for me) and sometimes it comes up at the ROOT-A partition (sdb8). I’m not at all clear on what’s happening. STATE is sdb9 - is that where I point GRUB’s “root” command?

No space left on device [Method 1 and 3]

I'm using version 69 vanilla recovery along with version 69 eve and caroline.
I get this using method 1 and also manually converting trying method 3

'/home/chronos/tpm1image/usr/lib64/libtspi.so.1.2.0' -> '/home/chronos/local/usr/lib64/libtspi.so.1.2.0'
cp: error writing '/home/chronos/local/usr/lib64/libtspi.so.1.2.0': No space left on device
cp: target '/home/chronos/local/usr/sbin/' is not a directory
'/home/chronos/tpm1image/usr/share/cros/init/tcsd-pre-start.sh' -> '/home/chronos/local/usr/share/cros/init/tcsd-pre-start.sh'
cp: error writing '/home/chronos/local/usr/share/cros/init/tcsd-pre-start.sh': No space left on device
'/home/chronos/tpm1image/usr/share/cros/init/chapsd.sh' -> '/home/chronos/local/usr/share/cros/init/chapsd.sh'
'/home/chronos/tpm1image/etc/dbus-1/system.d/Cryptohome.conf' -> '/home/chronos/local/etc/dbus-1/system.d/Cryptohome.conf'
'/home/chronos/tpm1image/etc/dbus-1/system.d/org.chromium.Chaps.conf' -> '/home/chronos/local/etc/dbus-1/system.d/org.chromium.Chaps.conf'
tss:!:207:root,chaps,attestation,tpm_manager,trunks,bootlockboxd
tss:!:207:207:trousers, TPM and TSS operations:/var/lib/tpm:/bin/false
sed: couldn't flush /home/chronos/local/lib/udev/rules.d/sedl4PcoR: No space left on device
sed: couldn't flush /home/chronos/local/etc/camera/sedRYip9V: No space left on device

ChromeOS image created: this is for personal use only, distribute at your own risk

BIOS freeze/crash, can't load USB

Edit: Solved. Simply used a different flash drive.

BIOS locks up when USB is plugged in containing the Method 1 generated image. I can't access the boot menu or anything, it freezes, my USB light (and Caps Lock light for whatever reason) blinks and flickers for a while, then it shuts off and restarts and tries again, endlessly looping.

If the USB is unplugged, then I boot Chromium like before.

"Hanging" at G Symbol boot-screen

Hey there,

When using the eve and caroline (for tpm) images as base, the system will hang there... Tho when pressing Ctrl + Alt + F2 it will launch the console just fine and I can log in as root! I'm using the Dell Latitude 5580 btw

Incorrect reference to /dev/sda when determining partition sizes

Line 130 has:

START_NEWB=`expr $(sfdisk -o Device,End -lq /dev/sda | grep "^""$PART_GRUB"[[:space:]] | awk '{print $2}') + 1`

but it should refer to "$chromium_image" like line 134. (-lq "$chromium_image")

Thanks

Can't mount /dev/loop1

I think title tells it all. I am using Method 1, falco 70 image, ArnoldTheBad 72 special image, and getting this:

Installing partition 1 to /dev/sda
Installing the stateful partition...
mount: wrong fs type, bad option, bad superblock on /dev/loop1,
missing codepage or helper program, or other error
umount: /tmp/install-mount-point: not mounted
localhost /home/chronos/user #

Originally posted by @Wolfley-Matt in #7 (comment)
Pretty much what was noticed in #7. Any way I can bypass this error, what's happening over there? Sure, if I try this command manually, I get same result. My hardware shouldn't really matter here, but just in case I'm installing it on Sandy Bridge HP laptop with SSD. What's the matter?

Android apps won't work after reboot

When I reboot chromefy's Chrome OS I cannot reopen any installed android apps.

Base Chromium runs fine, but after Chromefy, it hangs on white chrome os logo screen

I installed FydeOS on my computer. It boots fine after the install. Then apply chromefy with YES to using local files, YES to repartitioning, and NO to selinux. When I reboot, the computer hangs on the white chrome os logo screen. I can enter terminal with Ctrl+Alt+f2 but cannot exit with Ctrl+alt+f1. Also, tried smashing the keyboard when it is on the white logo screen, but that doesn't force the login, like it has done for me on other machines before.

bash: croissant.sh: No such file or directory but exist on sdb

20190323_093629](https://user-images.githubusercontent.com/48853711/54863960-a255f780-4d0c-11e9-9acc-4d488ef264b4.jpg)
cant proceded with the istallation on chromium os with chrome os why the terminal speak with this command: bash: croissant.sh: No such file or directory

unable to see command line/vt/bash output

im currently working to write the usb to my HP Steam11
however after going into VT/2 with ctrl+alt+2 i do not see anything on the screen
it lights up - but output
ive tried connecting hdmi but still no output from VT
i actually tried to do it blind too
but no luck

any ideas?

Error: Image chromiumos_image.img does not have a system partition (corrupted?)

Using Method 1:
Linux Mint 19.1 in Virtual Box on Windows 10 with shared folders
Downloaded and extracted ATB Special Build Camd64OS_R72-11316.B-Special.7z to chromiumos_image.img
I tried with both R69 and R72 multiple times. Download is not corrupt.
Ideas?

Automating the Dual Boot process

Create a script to deploy the dualboot option into a chrome build

Immediate crash after welcome screen display

Hi,

Using R69 versions of arnold and recovery (eve & caroline) I created an image using method 1, flashed it on a usb drive and booted from it. On my old Samsung XE700T1C it boots and works beautifully, I can even install it to the disk and multiboot with Android and windows.

However on my Dell XPS 15 9560 as soon as the "G" Logo is finished and the welcome screen is displayed (the one with the enable debugging functionality link) the screen turns black then the laptop halts.

Unfortunately I have no more info and don't really know how I can get more logs, tried looking into the USB drive's state partition for any logs but couldn't find any, let me know if there's a way to debug/log what is happenning.

Thanks

Can't make the image boot on TinkerBoard

Device: TinkerBoard (RK3288 - armv7)
Method: 1
Device for boot: 32GB SD Card
Base image: https://chromium.arnoldthebat.co.uk/special//Cx86OS_R60-9592.B-Special.7z
Recovery image: ASUS Chromebit CS10 (RK3288)(https://dl.google.com/dl/edgedl/chromeos/recovery/chromeos_11021.81.0_veyron-mickey_recovery_stable-channel_mickey-mp-v2.bin.zip)
TPM: Caroline

Steps:

1. Clone this repo
2. Download the img / bin files
3. Rename Base image to chromiumos_image.img
4. Run sudo bash chromefy.sh chromiumos_image.img chromeos_11021.81.0_veyron-mickey_recovery_stable-channel_mickey-mp-v2.bin caroline.bin
5. Burn the remaining chromiumos_image.img to an SD Card using Etcher.

It when i start the device, it shows nothing, only power led is on :(

Acer C720 boots to blank black screen from live usb

I used the first method +
Camd64OS_R72-11316.B-Special
chromeos_11316.165.0_peppy_recovery_stable-channel_mp-v3.bin
swtpm.tar

• balena on Ubuntu.

When I boot from the live usb, all I get is a blank screen, but I do hear the Chrome beeP welcome noise. The same usb boots successfully on a t430 thinkpad (but no Gplay or linux option...).

Mount internal partitions so that they show up in Files?

I don't really know where to post this issue, and there are not many resources available for Chrome OS. Since I've installed Chrome OS using this tool, I'm posting it here, in case somebody faces the same problem as myself.

I've installed Chrome OS alongside three other OSs in my hdd. Now, by default, Chrome OS can only mount the external (or removable) partitions using mount-passthrough, I believe. Since I've many files in my internal drive (in separate partitions), I'm wondering if there was a way of mounting them so that they would show up in Files.

I know I can mount any partition using the mount command, but they don't show up in Files since they're no mounted at /run/arc/media/ directory, and I understand that I can't mount any directory there (no permission, even being a root user).

Any help would be appreciated. Thanks.

How to update Chrome OS in a multi-boot system

How can I update Chrome OS in a multi-boot system? I used Eve + Caroline with ArnoldTheBat. Now, there's an update available. How can I update Chrome OS to the latest version? And which recovery image should I be using --- Eve or Caroline?

Src and Dst are the same /dev/sda = /dev/sda

When trying to install the IMG using method one (the bootable live USB) after running the command to install I get that error. I tried installing to my nvme01 drive which is my main and only drive as this computer has an nvme drive but it doesn't work, I get a black screen after grub loader on reboot

Automating the Img generation

Automate the process of creating a chrome img read to deploy

EFI partition nonexistent/empty after boot

So I installed it, but... There's no GRUB. And I tried to run the scripts but there's no EFI partition found.

Installation does not boot / GPT headers invalid

While installing it complains that the GPT headers are invalid. At the end it says it can't find Grub, same with running the script for when it does not boot.

After restart, my PC says that there is no bootable medium.

Image created with method 1 has blank EFI partition

Downloaded Arnold's Chromium, Caroline recovery.bin, and Eve recovery.bin. Ran the method one and flashed the resulting image to a flash drive. The created drive has a blank EFI partition, thus I cannot boot it.

[parker@stealth ~]$ sudo fdisk -l /dev/sda
[sudo] password for parker: 
GPT PMBR size mismatch (8708128 != 60567551) will be corrected by write.
The backup GPT table is not on the end of the device. This problem will be corrected by write.
Disk /dev/sda: 28.9 GiB, 31010586624 bytes, 60567552 sectors
Disk model: USB DISK 3.0    
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 6AB674D5-FDDD-AE4D-9CCC-D5DB3C2F822F

Device       Start     End Sectors  Size Type
/dev/sda1  4513792 8708095 4194304    2G Microsoft basic data
/dev/sda2    20480   53247   32768   16M ChromeOS kernel
/dev/sda3   323584 4513791 4190208    2G ChromeOS root fs
/dev/sda4    53248   86015   32768   16M ChromeOS kernel
/dev/sda5   315392  323583    8192    4M ChromeOS root fs
/dev/sda6    16448   16448       1  512B ChromeOS kernel
/dev/sda7    16449   16449       1  512B ChromeOS root fs
/dev/sda8    86016  118783   32768   16M Microsoft basic data
/dev/sda9    16450   16450       1  512B ChromeOS reserved
/dev/sda10   16451   16451       1  512B ChromeOS reserved
/dev/sda11      64   16447   16384    8M unknown
/dev/sda12  249856  315391   65536   32M EFI System

Partition table entries are not in disk order.
[parker@stealth ~]$ udisksctl mount --block-device /dev/sda12 
Mounted /dev/sda12 at /run/media/parker/EFI-SYSTEM.
[parker@stealth ~]$ cd /run/media/parker/EFI-SYSTEM/
[parker@stealth EFI-SYSTEM]$ ls
[parker@stealth EFI-SYSTEM]$ 

Creating USB installation with Method 1 (no such file or directory)

I keep recieving this messege when i try to create USB installation with method 1 script

cp: cannot stat '/home/chronos/local/usr/lib64/dri': No such file or directory
cp: cannot stat '/home/chronos/local/usr/lib64/va': No such file or directory
Error while copying ChromiumOS files locally (insufficent disk space?)

i am using ArnoldtheBat image

Black screen when android apps are under windows.

Issue:

The screen blinks, completely black, three to five times every time an Android App is covered by another window (ChromeOS/Android/Linux, doesn't matter). After the obnoxious blinking, the Android virtualization would crash and shell/GUI would restart. Literally shutting down the Android and Linux environments and keeping ChromeOS still running.

This could be a problem in ChromiumOS itself, the Chromefy hack, or the laptop's video driver. I just wanted to post this for possible fixes that might help everyone else having the same issue.

Device and Recovery Images:

Two months ago (Nov. 2018), I successfully installed an ArnoldTheBat build of v69 on a Dell Inspiron 11 3138 with Eve and Caroline recovery images. Everything seemed to work fine and no issues.

Anyway, when I came back to the XDA thread (Dec. 2018) to see any workarounds for Chrome OS updates, I saw the new method and tried it out to install v70. Everything seemed fine until I opened the Google Play Store, this issue occurred.

Today (Jan. 2019), I came back to this repository and tried out option 2a to install v71. Everything worked fine and the system was much faster than before, but the blinking screen issue was still existent to this day.

\r: command not found

Actually, after buying new SSD (because Dual boot isn't yet automated by script & I didn't want to lose my files), years of trying to have all files accessible during the installation process and looking for required recovery images, I was ready to do it. So I typed sudo bash chromefy.sh with all required params (path to caroline.bin, etc.). And pressed ENTER. And... BOOM! This error:
chromefy.sh: line 2: $'\r': command not found
chromefy.sh: line 6: $'\r': command not found
chromefy.sh: line 11: $'\r': command not found
chromefy.sh: line 15: $'\r': command not found
chromefy.sh: line 27: syntax error near unexpected token '$'{\r''
'hromefy.sh: line 27: 'function cleanup_chromefy {. I have no idea, what does it mean (Some sort of compilation error?), because I never learned bash ( #OnlyObjectPrograming ), but I would be happy if you tell me what's going on.

Thank you!

Problem with loading boot image

Where download caroline.bin?

Where download caroline.bin?
I cannot find.

Live usb dosn't see my ssd

HI i am trying to install chromefy on toshiba chromebook, i generated the image by the method 1 and made the live usb but when i try to install the chrome os from the live usb it doesn't see my ssd when i run fdisk -l i only get my usb. Maybe for chromebook there is a better way to install chromefy

Google Play Service and Linux emulation doesn't work

I installed Chrome OS with Chromefy on my computer with dual boot (Ubuntu).
No problems with the installation, I follow all the Google Docs.
When the OS boot (after the grub root path problem) Google Play service get an error on configuration and Linux emulator setup get also an error.
What can I do ?
(PS : I had other issue like infinite shutdown but I think they had a link between all issues like an error on installation)

Won’t boot without USB after a successful installation

I installed using method 1 successfully, but now cant seem to boot without the usb drive. After the grub menu it hangs at a black screen and once I plug in the usb it startsup. [Surface Pro 3]

Internal mic and webcam

I have a Dell XPS 15. I can't get my internal mic or webcam to work. I current use fydeOS 6.0, nocture, and kip. Is there a recomment configuration that will allow for mic and/or webcam to work? Any suggestions.

FYI: installing Mode 3 (in a partition)... need to set partition flags

Just something I (think) I came across after a lot of rebooting late last night. In Mode 3, where you're preparing the stripped-down partitions for Chromium to be bootable, you've got to set the boot flags BOOT and ESP on the EFI_SYSTEM partition for it to get picked up properly by something like rEFInd. Or GRUB also, I think. Otherwise, the system doesn't seem to realize that's meant to be a bootable partition.

If I'm wrong on this, feel free to correct me. But setting those flags made my Chromium install immediately visible and test-bootable.

Newly created Chrome OS IMG won't install

I've just created a bootable chrome OS usb stick and chrome runs flawlessly off the USB. When it comes to installing to my ssd after running the script it seems every partition has errors and the operation aborts. I've run the script flawlessly and still no luck. Any ideas? Thanks in advance for any feedback.

no chrome://flags visible after successful installation

Problem:
I have a Dell Venue Pro 11 7140. I installed Chrome OS on it following the tutorial.

I'm very unsure if this is even the right place for this issue or if it is a chrome os bug but:

When I navigate to chrome://flags I'm only presented with the site's top part with the searchbar but no flags that I can enable. Everything below the search bar is just empty. Typing in the searchbar changes nothing.

What I tried so far to fix it based on answers I found googling (but nothing worked):

• Launch Incognito mode and go to chrome://flags -> no change

• launch guest session from login screen -> flags are visible, changes apply to current session, but are not persisted to my user account

• powerwash -> no change

• log in with a second gmail account that I have -> also see no flags

If this has nothing to do with the "chromification" process an is a chrome bug, just let me know and close this issue.