HP chromebook 14a-Windows Bootloader

I’m using your UEFI firmware, installed my OS [Windows 10], and it still boots to the EFI shell - what do I do?

Did you use Rufus for the flashing of the installation media? Maybe you chose the wrong settings in Rufus, try to reflash your installation media with the right settings (I think it was GPT for the partition table type and then you can select UEFI in the Targeting System, google it just incase if you have doubts). @me if you need more help. I hope this helps!

The windows installs completely smooth but after it reboots still fails to boot from the “windows boot manager” Is there any command that can help to Fixing the issue?

I’m facing the same problem here. Were u able to resolve it?

Hello!

Same problem here! Anyone found a solution for this?

Thanks in advance!

post a pic of the boot menu, and provide the board name.

HP 14a could be any of a dozen different devices. we stress this in the docs for a reason.

Sorry for the incomplete post!

The laptop model is: hp 14a-nf0002na 14in intel n100 4gb 128gb chromebook

I’ve flashed the firmware with a suzy-cable, using the instructions on your site, backed up original firmware, created 3 different bootable usb with windows 11, got the same result!

Thank you for the reply!

The boot menu!

ok, the issue is the internal storage (UFS) is not being detected by the bootloader (edk2).

I have a new driver that should fix this, but still needs testing

1 Like

Thank you for the updated firmware! It works perfect!

1 Like

One thing i noticed, is that the laptop doesn’t fully power off! The light at the charging port keeps flashing, and the battery drains about 20% left over night! Doesn’t bother me, but just to let you know!

Also the drivers for the touchpad don’t seem to work, for my model!

Thanks again for the help!

flashing LED means it’s in sleep mode, not powered off. You probably need to disable hibernate under Windows.

Touchpads are usually connected via an i2C controller, and so requires all system/chipset drivers (like those for the I2C controllers) to be installed for it to work. coolstar’s drivers are not sufficient, they are for the touchpad itself not the controller.

1 Like

Resolved the touchpad driver with Driverpack! I think my model isn’t fully compatible with 14a plus model, the command for installing the chipset drivers in power shell didn’t work for me! Tryed putting the file in different folder, same error!

All the ADL-N boards use the same chipset drivers, plus or not.

post a pic of the command used / error

1 Like

Also I am having trouble with coolstar website to buy the drivers! Been trying for two days from diferent devices!

Disable windows 10/11 fast startup.

1 Like

This worked! Thank you!

the problem is that the instructions assume that you are running powershell from your user home directory (you’re running it from c:\windows\system32), and when you’re not – and don’t understand command line arguments/file paths – things break.

the argument --file .\Downloads\autoinstall-intel.ps1 tells powershell to run this file, but the path assumes that 1) the file is in your Downloads folder, and 2) that you are running it from the user dir of the logged in user (eg, c:\users\Cristi). The instructions could be more clear to help avoid this problem, but the command/drivers do work when run as intended.

1 Like

New to linux-like comands, but trying to understand them like when installing windows from a boot disk! :slight_smile:

Now still strugling with coolstar site to download the licensed file to upload it in the program to generate the license! :hugs: