Jump to content

Issues Booting Windows in Clover


buttcrap
 Share

13 posts in this topic

Recommended Posts

I can't seem to track down an issue I'm having booting into ANY Windows installation using Clover.

 

 

The laptop I'm attempting to dual boot is a BIOS only, with an unlocked Insyde H20 F1.B. It has two hard drives, but rather than use one for each OS, I'm partitioning the first one and using the second one as a shared ExFat drive between Yosemite/Windows 10 TP. The reason I'm setting it up like this is because my first drive is an SSD, second one a hybrid.

 

 

Because the machine is BIOS only, in order to use a GPT style startup disk (as opposed to the less attractive MBR) I need to load the Windows installer via Clover, to avoid getting an error message about how Windows can't install. The whole goal is to avoid using MBR/hybrid MBR at all.

 

In addition to the Windows USB installer(this one is actually in GPT format) I have, I also have one Windows 10 TP partition currently on the startup drive using MBR, and an old Windows 7 install on my secondary HDD, also using MBR.  So I definitely need a Clover USB drive that will be able to boot into Windows pretty consistently, as once I'm using all GPT on my old BIOS only machine I cannot rely on the Windows bootloader at all.

 

None of the Windows installations will boot using Clover. I select them, press enter, and they show a box. Waiting doesn't seem to do anything. I initially tried this using the latest Clover, r3193, and when it didn't work I tried r3185... It continued like that for a while, I'm pretty sure I've tested all versions of 2.3 by now. On some versions of Clover, none of the Windows drives will even show up! I've tried various versions on 3 different USB sticks I have, and when they do show the Windows it will immediately show a square if I try to boot into them, and I have to hold hard reboot.

 

I have a good functioning installation of OS X on the 2nd HDD, so I have an edited DSDT.aml and config.plist that has native power management etc. No matter if the DSDT is there or not the behavior is exactly the same. I do have LegacyBIOSDefault on, and I've tried exploring PBR to no avail.

 

When making the USB, I make sure to select 'Install boot0af in MBR' under Bootloader, and Clover EFI 64 bits Sata, and I typically don't mess with any of the other options. I tried BiosBlock once, but Clover never booted.

 

I'm new to Clover, and obviously, I am missing something here. I've tried looking everywhere to see what I'm doing wrong, but this one is stumping me. Any ideas?

 

It is booting OS X beautifully though :)

Link to comment
Share on other sites

@buttcrap,

 

1.  Make sure you have copied all the installer files from the Windows DVD/iso to a FAT32 partition on a USB

2.  You need to select bootx64.efi from "Boot UEFI external" at the Clover Main Menu when booting the UEFI Windows Installer USB through Clover:

 

essjmDT.png
 


Ja4W7c1.png

 

If you don't see the above entry, most likely it is hidden (the latest Clover revisions >r2999 automatically hide bootx64.efi from the GUI, unless you press <F3> at the Main Menu to unhide)....

 

Try this workaround:

 

1.  Rename cdboot.efi in efi/microsoft/boot folder to cdboot.BAK

2.  Copy bootmgfw.efi into /efi/microsoft/boot

      a. In Windows 7, you can extract bootmgfw.efi from the "install.wim" using 7-Zip (open the iso and navigate to sources/install.wim/1/Windows/Boot/EFI/bootmgfw.efi).

 

      b. For Windows 8 and 10, you can extract bootx64.efi from the iso using 7-Zip (in the /efi/boot folder) ---> copy to efi/microsoft/boot folder on your UEFI Windows installer USB and rename it bootmgfw.efi.

post-846696-0-97818800-1428017613_thumb.png

3.  Reboot the computer with the Installer USB and select "Boot Microsoft EFI boot menu", then press <spacebar>

post-846696-0-05059700-1428015205_thumb.png

4.  Select "Run bootmgfw.efi" and then press <spacebar> ---> should now boot into the UEFI Windows Installer

post-846696-0-04505300-1428015231_thumb.png

 

After installation, Clover will be able to boot Windows by running bootmgfw.efi from the hard disk EFI partition (in /EFI/Microsoft/Boot).

 

Refer to

Creating_Windows_UEFI_Boot-Stick_in_Windows

[Guide] Install Windows 8 UEFI on Legacy BIOS with Clover (and Dual boot with Yosemite)

Post#29 for creating a multiboot installer

Link to comment
Share on other sites

@modbin I wish you were right :(

I am. Take a look at the firmware on the support page for the DV6t-6100. It's full of 64 bit PE files. There is a setup option called UEFI Boot in the setup menu. Set it to enabled. Then you don't have to use UEFI->CSM->DUET->Clover->boot.efi. Lowmemfix.efi should be enough on Insyde to get boot.efi starting.

Link to comment
Share on other sites

  • 2 weeks later...

@fusion71au 

 

Thanks a million for this suggestion!! I've been super busy at work but just got to try it out. Perfect reading material for this issue linked as well.

 

What would be the advantage of hiding these in a bootloader? Will I have to perform a similar procedure to EFI boot Windows after it's installed?

 

After following the steps, it still doesn't show my Windows 10 installer USB. I'm going to try tomorrow to use a different USB stick, but is there any common reasons why it wouldn't read the USB? I'm fairly certain I didn't need any Clover drivers when I booted into my OS X installer from a partitioned USB. I tried renaming cdboot.efi to both cdboot.bak and cdboot.BAK, and the installer boots fine without Clover involved.

 

My Clover USB is in MBR, would that matter at all?

 

 

@modbin I really hope I'm wrong here, but I think there are both BIOS and UEFI models as it's a 2011 which is right on the line of when HP switched over to UEFI. I don't have a UEFI Boot option anywhere in my startup settings, and I'm using Donovan6000's unlocked F1.B which shows more than the default 5 or so options.

Link to comment
Share on other sites

Firmware F1.B from this page is UEFI not Bios: http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv6-Entertainment-Notebook-PC-series/5082212/model/5118671#Z7_3054ICK0KGTE30AQO5O3KA30R1

You can open it in Phoenix Tool  and you'll see it. If u don't have uefi boot option in setup menu it's been crippeld by HP. You can however unlock setup options like the advanced menu for example. I thought u already have everything unlocked. Here is a video with everything unlocked on the F.1B

https://www.youtube.com/watch?v=Xozl0phLKz8
Link to comment
Share on other sites

 

Firmware F1.B from this page is UEFI not Bios: http://support.hp.com/us-en/drivers/selfservice/HP-Pavilion-dv6-Entertainment-Notebook-PC-series/5082212/model/5118671#Z7_3054ICK0KGTE30AQO5O3KA30R1

You can open it in Phoenix Tool  and you'll see it. If u don't have uefi boot option in setup menu it's been crippeld by HP. You can however unlock setup options like the advanced menu for example. I thought u already have everything unlocked. Here is a video with everything unlocked on the F.1B

https://www.youtube.com/watch?v=Xozl0phLKz8

 

Yeah I've seen this page before, is there any possibility that there were different versions of the DV6-6100 that would behave differently on the same BIOS update?

 

The reason why I wonder this is because I don't have the option to UEFI boot at all. I have a non whitelisted WiFi card installed and native power management/full QE in OS X so I'm sure my BIOS is actually unlocked.

 

A couple months back I ran that 'UEFI Update' on the link you provided and after that my BIOS was no longer unlocked and still did not have the option to UEFI boot. Re flashed with Donovans for the coveted native power management. 

 

Here's where I got the mod: http://donovan6000.blogspot.com/2013/12/modded-bios-repository.html

Did Donovan6000's mod leave this part out? I noticed that in the YouTube link you posted the guy says in the comments that he unsoldered his card and flashed it that way. I just used a modded HP BIOS Flash Utility provided by donovan. 

 

There are actually some options I have that the video doesn't have, too - they both state that the BIOS is F1.B, (sp55068.exe) and have 'INSYDE H20 SETUP UTILITY - REV. 3.5' in the corner. The options he has are slightly different - however at a glance our BIOS look exactly the same. I don't have the Quick Boot and most of the options under 'UEFI Boot', but I do have a 'Switchable graphics' setting where I can control which GPU is on.

Link to comment
Share on other sites

The UEFI Boot setting is hidden in the HP version. However, if u extract it and take a look at the module FE3542FE-C1D3-4EF8-657C-8048606FF670, u can see that the UEFI Boot option is there. Donavan has a guide on his page on how to enable it http://donovan6000.blogspot.de/2013/07/insyde-bios-modding-hidden-settings.html

 

Running the IFR Extractor tool from him against the FE3542FE-C1D3-4EF8-657C-8048606FF670 module will give u following Information:

 

 


0x123F6 Form Set: System Configuration {0E 24 F4 27 4A A0 00 DF 42 4D B5 52 39 51 13 02 11 3D 5A 00 C9 00 00 00 00 00 00 00 00 00 01 00 00 00 84 03}
0x1241A     Form: System Configuration, Form ID: 0x1 {01 06 01 00 5A 00}
0x12420         Subtitle:   {02 04 C9 00}
0x12424         Suppress If: {0A 03 00}
0x12427         True {27 02}
0x12429             Setting: UEFI Boot, Variable: 0x79[1] {05 09 79 00 01 EF 00 F0 00}
0x12432                 Option: Enabled, Value: 0x0 {09 09 EB 00 00 00 01 00 00}
0x1243B                 Option: Disabled, Value: 0x1 {09 09 EA 00 01 00 00 00 00}
0x12444             End of Options {10 02}
0x12446             Setting: Quick Boot, Variable: 0x6D[1] {05 09 6D 00 01 2A 01 2B 01}
0x1244F                 Option: Enabled, Value: 0x1 {09 09 EB 00 01 00 01 00 00}
0x12458                 Option: Disabled, Value: 0x0 {09 09 EA 00 00 00 00 00 00}
0x12461             End of Options {10 02}
0x12463             Setting: Quiet Boot, Variable: 0x6E[1] {05 09 6E 00 01 2C 01 2D 01}
0x1246C                 Option: Enabled, Value: 0x1 {09 09 EB 00 01 00 01 00 00}
0x12475                 Option: Disabled, Value: 0x0 {09 09 EA 00 00 00 00 00 00}
0x1247E             End of Options {10 02}

 

Looks like almost everything got disabled by HP. Happy Firmware Hacking :) Maybe u can get unlocked firmware from this youtube guy. Since Insyde UEFI doesn't need Aptiofix but just free some pages in low mem it should be perfect for OSX.

  • Like 1
Link to comment
Share on other sites

@modbin

Hey I found this http://donovan6000.blogspot.com/2013/08/look-what-i-did.html

 

it looks like you're right; there is a UEFI booter in Insyde F1.B, but Donovan is saying that it doesn't comply with EFI standards and must be booted from an EFI shell.

it looks so promising at first, but it seems to be only implemented as part of a specific hp diagnostic so it never needed to be 'complete'. he says that UEFI boot is actually enabled already too, so unhiding the option didn't do anything in terms of functionality.

 

I really can't think of a better way for hp to get a bunch of people really excited and then massively let down than with this limited UEFI implementation...

 

:(

Link to comment
Share on other sites

I didn't know that HP sucks so bad. However, the SHA-1 of CryptRSA.efi is 6332436A0AD4694DB2D0A5E0C04B2EBE7A235AE2. It is stored in a file with this GUID C783CC01-82AE-48A2-A5FF-54C5B3A0E04D. The actual check is done in a PE with this GUID AEB8657C-AEBF-40A1-9866-BB22C7223FF0. Maybe u can patch it in order to allow the start of any efi files.

Link to comment
Share on other sites

 Share

×
×
  • Create New...