Error msgs running chromefy - losetup, invalid option & chromium lacking system partition

[chipbite]

Trying to follow the instructions for option 1 - I get a problem running chromefy. First an invalid option error message, then another error message re the chromium image. I got the chromium image "Cx86OS_R58-9334.B-Vanilla.7z". From my console:

vmw:/mnt/hgfs/chromeos# bash chromefy.sh chromiumos_image.img chromeos_11895.118.0_eve_recovery_stable-channel_mp.bin chromeos_11895.118.0_caroline_recovery_stable-channel_mp.bin
losetup: invalid option -- P

Usage:
 losetup loop_device                                  # give info
 losetup -a | --all                                   # list all used
 losetup -d | --detach loop_device                    # delete
 losetup -f | --find                                  # find unused
 losetup [ options ] {-f|--find|loop_device} file     # setup

Options:
 -e | --encryption <type> enable data encryption with specified <name/num>
 -h | --help              this help
 -o | --offset <num>      start at offset <num> into file
 -p | --pass-fd <num>     read passphrase from file descriptor <num>
 -r | --read-only         setup read-only loop device
 -s | --show              print device name (with -f <file>)
 -N | --nohashpass        Do not hash the given password (Debian hashes)
 -k | --keybits <num>     specify number of bits in the hashed key given
                          to the cipher.  Some ciphers support several key
                          sizes and might be more efficient with a smaller
                          key size.  Key sizes < 128 are generally not
                          recommended
 -v | --verbose           verbose mode

Image chromiumos_image.img does not have a system partition (corrupted?)
aborting...
vmw:/mnt/hgfs/chromeos# 

Am I doing something wrong?

BR!

[revcam]

I had a similar issue, it looks like your running from a VM, make sure to copy the files into the VM's local folder, like downloads or documents. I was trying to do this from the host and it must not have the same permissions or something. Hope that helps!

[chipbite]

Thanks revcam, I think that sounds reasonable, will try it.

[chipbite]

No dice... Same issue even though I now copied the images to a drive instead of sharing it...

I wonder what losetup: invalid option -- P means.

vmw:/chromeify# sudo bash chromefy.sh chromiumos_image.img chromeos_11895.118.0_eve_recovery_stable-channel_mp.bin chromeos_11895.118.0_caroline_recovery_stable-channel_mp.bin 
losetup: invalid option -- P

Usage:
 losetup loop_device                                  # give info
 losetup -a | --all                                   # list all used
 losetup -d | --detach loop_device                    # delete
 losetup -f | --find                                  # find unused
 losetup [ options ] {-f|--find|loop_device} file     # setup

Options:
 -e | --encryption <type> enable data encryption with specified <name/num>
 -h | --help              this help
 -o | --offset <num>      start at offset <num> into file
 -p | --pass-fd <num>     read passphrase from file descriptor <num>
 -r | --read-only         setup read-only loop device
 -s | --show              print device name (with -f <file>)
 -N | --nohashpass        Do not hash the given password (Debian hashes)
 -k | --keybits <num>     specify number of bits in the hashed key given
                          to the cipher.  Some ciphers support several key
                          sizes and might be more efficient with a smaller
                          key size.  Key sizes < 128 are generally not
                          recommended
 -v | --verbose           verbose mode

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

[shuffleznl]

Hi @chipbite I had similar behaviour trying the script on WSL1.0 with Ubuntu. Basically this means making a file available as a block device, allowing you to access filesystem within file (kinda like mounting a VMDK in VM).

Possibly VMware (workstation?) doesn't fully support losetup/loop-devices. For WSL2.0 it now supports losetup (you can enable 2.0 on Insider Build).

[dragon788]

I had a similar failure trying to do the creation in the Crostini VM which made me kind of sad.

I can confirm that it works fine in WSL2, though you have to burn the image from the host since the VM doesn't see the USB devices. I ended up using the Chrome Recovery Tool to burn my Chromefy image for the ultimate in irony.