Jump to content

Hackintosh not boot after Bios update


MikeSantos
 Share

32 posts in this topic

Recommended Posts

if u have a skylake and good and stable bios version, why update bios for support kabylake?

 

I keep getting multiple boot entries (up to 135) even though I removed the 2 other drives.  Sometimes I'm *unable* to enter the BIOS and frequently get the message "Unable to boot, ...Enter BIOS...Loads Defaults and Restart...Load something else.  I don't remember.  Just some message with 3 options on a black background.  Oh, the BIOS' time and date are always wrong and I'm frequently correcting it.

Link to comment
Share on other sites

 

 

 

I updated 2 versions forward, but I only can go back one, as the bios changed to kabylake compatibility and not allow to go back from it.

 

 

Same problem: two identical MB (Gigabyte h110m-s2h) , one F4 bios, other F20. First one immediatly booted and installed osx . Everything was ok.

Second one reboots when I see AppleACPI platform bla bla bla...

 

I just added EmuVariableUEFI-64.efi in my Extension folder, but nothing to do...

I also tried to downgrade the BIOS..  but It does not allow me.

On Gigabyte boards, it is possible to downgrade the BIOS by booting with a MS-DOS (or FreeDOS) USB stick and the FPT.EXE program.

You will also need the FPARTS.TXT file to sit alongside FPT.EXE at the root of the USB stick.

 

The version I found here <http://www.mediafire.com/file/p66jhts7cfi26y8/fpt_DOS-Z170.zip> worked fine for my Z170X Gaming 5.

How to use FPT :

To save current BIOS : fpt -d bios.sav

To restore previously saved BIOS : fpt -f bios.sav

To flash another BIOS : fpt -f `PathOfBIOSFile`

 

Trick initially found here : <https://forums.tweaktown.com/gigabyte/28441-gigabyte-beta-bios-post507306.html#post507306>. Your mileage may vary.

 

I keep getting multiple boot entries (up to 135) even though I removed the 2 other drives.  Sometimes I'm *unable* to enter the BIOS and frequently get the message "Unable to boot, ...Enter BIOS...Loads Defaults and Restart...Load something else.  I don't remember.  Just some message with 3 options on a black background.  Oh, the BIOS' time and date are always wrong and I'm frequently correcting it.

UEFI shell is your friend here…

Once into UEFI shell, you can list the boot entries with `bcfg boot dump` and remove them with `bcfg boot rm`

Help command is available : for instance `help -b bcfg boot`

 

The solution listed here works fine : <https://sourceforge.net/p/cloverefiboot/tickets/226/#d1a9/0222/8cc1>

Instead of suppressing/renaming the /BOOT/BOOTX64.EFI as suggested, you might also try to explicitly add an entry for it through the UEFI Shell (`bcfg boot add...`), so that Clover will not try to add one itself at each boot, which apparently is the cause of the proliferation.

Link to comment
Share on other sites

 

 

 

 

 

UEFI shell is your friend here…

Once into UEFI shell, you can list the boot entries with `bcfg boot dump` and remove them with `bcfg boot rm`

Help command is available : for instance `help -b bcfg boot`

 

The solution listed here works fine : <https://sourceforge.net/p/cloverefiboot/tickets/226/#d1a9/0222/8cc1>

Instead of suppressing/renaming the /BOOT/BOOTX64.EFI as suggested, you might also try to explicitly add an entry for it through the UEFI Shell (`bcfg boot add...`), so that Clover will not try to add one itself at each boot, which apparently is the cause of the proliferation.

 

 

And that will solve the difficulty in entering the BIOS and the wrong BIOS time?

Link to comment
Share on other sites

The time issue might be unrelated.

 

The time was UTC because the time on MacOS, top right corner is correct.

Link to comment
Share on other sites

 Share

×
×
  • Create New...