chromefy
chromefy copied to clipboard
imperador
Black screen and caps lock flashing
Trying for days, with different Chromiumos distro and different recovery emydeOS working fine after installing it in the ssd but when i try to convert it to chromeos using the instructions, using Quote: sudo bash chromefy.sh /dev/sda recovery.bin swtpm.tar
and after booting, i got black screen with the caps lock flashing Option 1 gives me missing os but only when i install it in the ssd, when i boot from the usb, it work fine, dunno why Option 2-A gives me black screen with caps lock flashing still OPTION 2B and Option 3
Please any help will be appreciated
Laptop: HP Pavilion 15-bc504TX
Having same issue here, was working fine with v76 (dev, eve) but isn't working with latest release v77.
I had the same problem I was trying to create a Img for the first time v77 fails and caps lock blinks then I made another image for v76 after seeing this and it works fine.
V76 is the recovery file right ? and for chromium build, i'm using emydeOS, it will be a problem? because when i tested arnoldthebat, playstore doesn't working
using EmydeOS_V3 swtrp recovery file v76
and the problem still exist
please any help ?
Try making the modifications in this comment to the write_gpt.sh script to give the root partitions more space. You will need to do that after you are booted into a Chromefy USB, so if you aren't getting that far, try using the ArnoldTheBat r76 and a matching ChromeOS recovery at r76 to build your base image.
Try making the modifications in this comment to the
write_gpt.shscript to give the root partitions more space. You will need to do that after you are booted into a Chromefy USB, so if you aren't getting that far, try using the ArnoldTheBat r76 and a matching ChromeOS recovery at r76 to build your base image.
but, write_gpt.sh is already have the size 134217728 mentioned in the comment (EmydeOS_V3) so how can i edit that file in the recovery file? ( if that what i should do )
What size are the ROOT partitions in the write_gpt.sh file from EmydeOS? I'm not familiar with that one, is it a fork of Fyde?
I keep getting a blinking caps lock as well. When installing, I edit write_gpt.sh to match the correct size. The only difference between this issue and my situation is that it happens for me when I try to log in on an existing installation. I'm using an HP x360 15-cr0037wm
@TotalChris Are you using FydeOS as the base as well or one of the Arnold The Bat builds? I'm wondering if there is a kernel module difference or if they have a slightly different layout that doesn't like these changes.
I'm currently using an ATB based build. This problem has happened using Nocturne as my main recovery and Caroline as my TPM. I've tried both ATB's 78 and 80-Alpha builds.
An interesting discovery I made was related to camera processes. What usually happens is that when I try to log in, the screen freezes after I submit my password and hangs until either it decides to log me in, or everything freezes completely and the caps light starts blinking. After a successful boot, I checked boot logs and noticed where the time gap began and ended. I combed through a couple of logs and came across alot of camera processes that were started and timed out around the same point as the freeze. The reason these processes time out is that my ChromeOS builds don't know how to use my laptop's camera. This might be what's causing the issue.
Does Nocturne have a similar CPU/chipset to your laptop? You may want to see if you can disable the camera in the BIOS and whether that helps, but using the recovery image from a system that has a similar chipset to yours GREATLY increases the odds of success and lowers the risk of strange crashes.
