muntashirakon / chrome-os-multiboot Goto Github PK

In the instructions you say we dont need to do steps 2 & 5 if we are not converting to Chrome.
Thats still leaves step 3 "SWTPM.tar" with no clear indication of what to do with it.

I only ask because I tried the install_chromium.sh many times unsuccessfully.
Script reported a successful install.
It gets to the Chromium boot logo screen and hangs.
I finally tried the conversions script and it worked great.

So.... How do I just do a plain Arnold the bat (Chromium) install?
I have tried multiple versions of arnoldthebat builds.
They boot fine on USB but I cant get it to work with your script without chromfy (Chrom OS conversion).
Your script seems to be doing something or not doing something (I cant narrow it down)

@MuntashirAkon in your github what do you mean
Install in HDD with cd ~/Downloads/ChromeOS/ && sudo bash install_chromium.sh chromiumos_image.img sda4 sda5 sda6. Do I use exactly this command then replace after installing to HDD Or do I replace it right away while executing install_chromium.sh? Thanks

I used croissant.sh instead of chromefy.sh and fydeos6.0.img with samus73.bin recovery and swtpm.tar to have chrome:flags enabled in chrome. Coz when i use eve and caroline recovery chrome:flags on chrome is empty. Did you use chromefy.sh instead of croissant? Do you think using fydeos, samus and swtpm.tar causes it to power wash? Will try building the image again later in linux ubuntu as i have done the image using chrome os.

Originally posted by @b1t0y in #1 (comment)

I used this in my new Rammus 86
to save it
sudo cp /home/chronos/user/Downloads/mount-internals.conf /etc/init/

I stumbled upon this repo as was quite exited, as I've always enjoyed using Chrome OS. However, there was a major issue I ran into last time I dual booted: I messed with the rootfs, boot broke, and then the recovery process wiped my entire hard drive. Now, I asked on the chromefy repo, and they said there there wasn't anything done in defense, which is understandable since it's a pure Chrome OS USB maker. However, given the multiboot focus of this repo, what would be the chances of it handling this case more safely?

I used install_chromium.sh to install the os to hdd.
Then i booted to chromeos,it boot starts with "system is repairing" only a few second then reboot,And in the process of cycling.

How to judge what the problem is.
Thanks.

More partitions make disk more mess. So I want to put efi-system to esp partition. It is possible to work?

Automate the conversion of Chromium OS to Chrome OS:

• --skip-conversion: skip conversion altogether, use vanilla method
• <code_name>: code name of the recovery file to be downloaded
• [--skip-swtpm]: Skip swtpm
• [--skip-state]: Skip formatting and copying state partition

NEW USAGE:

install_chromium.sh chromiumos_image.img <efi_part> <root_part> <state_part> <code_name>|--skip-conversion [--skip-swtpm] [--skip-state]

Hi, i running into this error while running the chromefy.sh that tells me i don't have enough free space, i have 100GB+ availabile free space on my drive that i do the chromefy. Here's the error message:

cp: cannot create directory '/home/chronos/local/boot': No space left on device
'/home/chronos/RAW/usr/lib64/dri/i965_dri.so' -> '/home/chronos/local/usr/lib64/dri/i965_dri.so'
cp: error writing '/home/chronos/local/usr/lib64/dri/i965_dri.so': No space left on device
'/home/chronos/RAW/usr/lib64/dri/swrast_dri.so' -> '/home/chronos/local/usr/lib64/dri/swrast_dri.so'
cp: error writing '/home/chronos/local/usr/lib64/dri/swrast_dri.so': No space left on device
'/home/chronos/RAW/usr/lib64/dri/kms_swrast_dri.so' -> '/home/chronos/local/usr/lib64/dri/kms_swrast_dri.so'
cp: error writing '/home/chronos/local/usr/lib64/dri/kms_swrast_dri.so': No space left on device
'/home/chronos/RAW/usr/lib64/dri/nouveau_dri.so' -> '/home/chronos/local/usr/lib64/dri/nouveau_dri.so'
cp: error writing '/home/chronos/local/usr/lib64/dri/nouveau_dri.so': No space left on device
'/home/chronos/RAW/usr/lib64/va/drivers/i965_drv_video.so' -> '/home/chronos/local/usr/lib64/va/drivers/i965_drv_video.so'
cp: error writing '/home/chronos/local/usr/lib64/va/drivers/i965_drv_video.so': No space left on device

Of course that is not all, i only copied a few last error on the terminal. Here's the picture.

The error happen both when i include swtpm.tar or not. At first i ignored the error and proceed to boot the chromeOS. But It will always get stuck after GRUB.

I'm using zork recovery image of chromeOS and my laptop specs are AMD Ryzen 3550H. Do you have any idea what happen and how to solve it? I've been trying the brunch method too, it will boot chromeOS, but then it will get stuck on chrome logo, but i can access it's terminal (using ctrl+alt+f2) when i get stuck. It is because my CPU not supported? I read that zork recovery support for AMD Ryzen 3XXX series. and when i use other recovery image (grunt), brunch will not boot into chromeOS and proceed to bootloop.

if you manage to integrate the cros_update.sh for using against swtpm.tar, it'll be breeze....

Originally posted by @Crescendo-BLYAT in #2 (comment)

!! PRO TIPS !! You can also test them inside Chrome OS (will be reset upon a restart), to do that run the following commands on CrOS terminal:

sudo su
cp /etc/chrome_dev.conf /usr/local/
mount --bind /usr/local/chrome_dev.conf /etc/chrome_dev.conf
exit
Now, you can use vim editor to edit the file.

sudo vim /etc/chrome_dev.conf

What I did to put chrome flags directly on chrome os:

1. Ctrl-alt-t for crosh terminal --> shell
2. sudo su
3. sudo mount -o remount,rw /
4. cd /etc
5. sudo vim chrome_dev.conf
6. cut and paste your chromeflags or type it
7. press shift q then w enter then q enter
8. reboot
   It work for me...