So I have an HP 14a otherwise known as Yukio.
I have converted a chromebook to a windows and/or Linux before without issue, so I’m kinda lost.
Regardless of what I install, it will not boot and just goes to shell. Is there anything I can do? If there’s any other info you need let me know.
I don’t know what it is with this hp model. I’m facing the same problem. Sometimes it boots, sometimes it doesn’t. And the booting is also so slow sometimes.
14a could be any of 15 different models. YUKIO is not a valid HWID, AFAIK.
post your device’s actual board name – as shown in the script header or the firmware settings screen – and the contents of the Boot Menu screen.
mine is the hp chromebook 14a yahiko. After installing mrchromeboox firmware and installing windows it sometimes boots and most times it says cannot boot from windows boot manager and cannot boot from emmc. And sometimes the booting is slow. Below is the picture of when i was flashing again with chromebox firmware through ubuntu
show the boot menu - is the internal storage UFS or eMMC?
@MrChromebox please do you have anything for me to try? I downgraded to 2503, it was the same. I downgraded to 2024.09.08 but still it’s the same. If it boots once and you restart or shut down, it won’t boot again. It just shows the logo and nothing else. I have to restart and shut down several times before it can boot again. And sometimes when it boots, it says cannot boot from windows boot manager. Sometimes when I flash, it’s able to boot continuous for about 5 times, then it goes back to not booting
sounds like edk2’s eMMC drivers are to blame? does the eMMC device show under the Boot Menu when it fails to boot?
Yes. The emmc shows under the boot menu when it fails to boot. I go to boot manager and select the emmc but it says booting fromm emmc failed. When I try boot from file, there is nothing there when it doesn’t boot. But when it boots, the file path of the windows on the emmc is there
if edk2 sees the eMMC controller, but can’t boot from it / doesn’t seen any files on the drive, that’s a lot more complicated problem
So is there a way to fix it?
I have no idea, I can only begin to speculate as to the issue based on observed behavior.
