Contribute
Register

Did the Clover-UEFI Bootloader damage my BIOS?!? Elitebook 8560p

Status
Not open for further replies.
Joined
Jul 1, 2014
Messages
4
Motherboard
HP Elitebook 8560p
CPU
Intel Core i7-2620M @ 2.7GHz
Graphics
AMD Radeon 6470M
Mac
  1. 0
Classic Mac
  1. 0
Mobile Phone
  1. 0
Hello Everyone!

Long Time ago, i already tried to hackintosh my Elitebook. But i have the Version with AMD Graphics and last Year, there wasn't a solution for this so i gave up....

Now, with the actual PBI my model is supported too. I downloaded everything and followed the guide carefully. Everything was fine, i even got iMessage&Facetime to work!

Things started to go bad when i tried to install Windows on a second SSD.
My Goal was to have two completely unrelated Systems. So, NO mix of OSX and Windows on one SSD or needing an additional Bootloader to boot Windows. I wanted to select my OS by swapping the SSD everytime....

-I removed the Hackintosh SSD from the internal Bay
-Installed a clean SSD in the internal Bay
-I began to install Windows 8.1Pro (in UEFI Mode)

As the Installer almost finished i got an Error saying: "Windows could not update the computer's boot configuration. Installation cannot proceed."

-I tried to install again, again, again and again...
-swapped out the SSD for another one
-tried another USB-Stick
-tried another ISO
-set BIOS to Defaults, made EC reset, even disconnected Battery and CMOS-Battery for 3 hours.

On every attempt, iget the same Message!
without UEFI-Mode i can install Windows without any Problem.

I began reading a lot about (U)EFI and finally understood: There are writable Areas in the BIOS and found proof on my Elitebook too:

I removed both SSDs and started from a USB-Stick containing a Ubuntu Live CD. From there i installed the program "efibootmgr". This tool showed me CLOVER Entries (while there was no other SSD, HDD or USB-Stick connected aside the Linux-Live-Stick).

I deleted the CLOVER-Entris, but no success.


Who can explain such behaviour?



BR
germi
 
Hello Everyone!

Long Time ago, i already tried to hackintosh my Elitebook. But i have the Version with AMD Graphics and last Year, there wasn't a solution for this so i gave up....

Now, with the actual PBI my model is supported too. I downloaded everything and followed the guide carefully. Everything was fine, i even got iMessage&Facetime to work!

Things started to go bad when i tried to install Windows on a second SSD.
My Goal was to have two completely unrelated Systems. So, NO mix of OSX and Windows on one SSD or needing an additional Bootloader to boot Windows. I wanted to select my OS by swapping the SSD everytime....

-I removed the Hackintosh SSD from the internal Bay
-Installed a clean SSD in the internal Bay
-I began to install Windows 8.1Pro (in UEFI Mode)

As the Installer almost finished i got an Error saying: "Windows could not update the computer's boot configuration. Installation cannot proceed."

-I tried to install again, again, again and again...
-swapped out the SSD for another one
-tried another USB-Stick
-tried another ISO
-set BIOS to Defaults, made EC reset, even disconnected Battery and CMOS-Battery for 3 hours.

On every attempt, iget the same Message!
without UEFI-Mode i can install Windows without any Problem.

I began reading a lot about (U)EFI and finally understood: There are writable Areas in the BIOS and found proof on my Elitebook too:

I removed both SSDs and started from a USB-Stick containing a Ubuntu Live CD. From there i installed the program "efibootmgr". This tool showed me CLOVER Entries (while there was no other SSD, HDD or USB-Stick connected aside the Linux-Live-Stick).

I deleted the CLOVER-Entris, but no success.


Who can explain such behaviour?



BR
germi

Make sure you have the latest BIOS version. Reset BIOS settings to default, but make sure UEFI is enabled. Then install Windows with the target device connected to the primary SATA connector.
 
Thanks for your interest!

-I have actual BIOS (F60A)
-I did try it on the internal bay (not on upgrade bay).


Additional info:

"06/19/15 17:12:57 EFI HP BIOS Update 2.7.1.0 Started
06/19/15 17:12:58 Failed init of SMBIOS data"

This is what i got in the Log-File on the HP_TOOLS USB-Stick when i reapply the BIOS Update
 
Thanks for your interest!

-I have actual BIOS (F60A)
-I did try it on the internal bay (not on upgrade bay).


Additional info:

"06/19/15 17:12:57 EFI HP BIOS Update 2.7.1.0 Started
06/19/15 17:12:58 Failed init of SMBIOS data"

This is what i got in the Log-File on the HP_TOOLS USB-Stick when i reapply the BIOS Update

Try update of BIOS from Windows.
 
Try update of BIOS from Windows.


Did that more than once yesterday.

I've noticed: The splash Screen didnt't Change when i updated or re-applied the update from Windows8.1Pro. (<-This Windows is non-uefi Installation on a seperate harddisk from a previous Installation)

After that i tried the USB-Stick with the EFI Application generated by the HP-Tool.
Now, my "NINTENDO":lol:-Splashscreen was gone.

I think there we're some Settings more reflashed? :crazy:




But, Rehabman: Can you confirm this is real NVRAM-Content on Mainboard i saw in Linux's "efibootmgr"?
 
...
But, Rehabman: Can you confirm this is real NVRAM-Content on Mainboard i saw in Linux's "efibootmgr"?

I've never used efibootmgr on my ProBooks. The BIOS boots directly to hardcoded names (eg. \EFI\Microsoft\Boot\bootmgfw.efi, \BOOT\bootx64.efi, etc).
 
Even if You didn't use it the Entries are there in the real NVRAM .

I'm almost sure now (after some testing) that These Entries are written to the Physical NVRAM of These Laptops. I think EVERY new Installation in UEFI Mode creates a new Entry!

You can check this by viewing the table with the tool under linux i mentioned
 
Even if You didn't use it the Entries are there in the real NVRAM .

I'm almost sure now (after some testing) that These Entries are written to the Physical NVRAM of These Laptops. I think EVERY new Installation in UEFI Mode creates a new Entry!

You can check this by viewing the table with the tool under linux i mentioned

I'll check it out when I get a chance.

FYI: That efibootmgr tool on Linux is pretty buggy...
 
Status
Not open for further replies.
Back
Top