imperador / chromefy Goto Github PK

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

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)

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

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

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?

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

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

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.

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.

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.

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]$ 

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.

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?

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.

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...

Where download caroline.bin?
I cannot find.

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?

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

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]

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)

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...).

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.

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

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

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?

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.

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?

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

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 :(

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.

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

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.

Automate the process of creating a chrome img read to deploy

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

Thanks

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.

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

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

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

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

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!

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.

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.

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

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?

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?

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?

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.

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.

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?