[Guide] Booting the OS X installer on LAPTOPS with Clover

[RehabMan]

What am I missing from my profile?

The instructions in post #1 are very clear...

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

Mobo: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
Mobo: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.

Note: When specifying your bootloader, if using Clover legacy, please be sure to specify "Clover legacy"). Specifying "Clover" will be assumed as "Clover UEFI"

--

Looking at your profile:
Mobo: missing model of laptop (and chipset should be in 'CPU').
CPU: chipset should be here too (not in Mobo)
Graphics: missing screen resolution

 

[ThatRedstoneGuy]

The instructions in post #1 are very clear...

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

Mobo: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
Mobo: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.

Note: When specifying your bootloader, if using Clover legacy, please be sure to specify "Clover legacy"). Specifying "Clover" will be assumed as "Clover UEFI"

--

Looking at your profile:
Mobo: missing model of laptop (and chipset should be in 'CPU').
CPU: chipset should be here too (not in Mobo)
Graphics: missing screen resolution

Wow! Don'y I feel stupid. I had ALL of that.... not in the signature. Sorry again.

 

[ThatRedstoneGuy]

The instructions in post #1 are very clear...

Please provide complete details in your profile/signature
(Profile/Settings link in upper right corner of this site)

Mobo: manufacturer/model + bootloader(Clover/Chameleon/Chimera)
CPU: detailed CPU model + motherboard chipset
Graphics: all graphics devices + laptop internal screen resolution

For example, typical Ivy laptop:
Mobo: HP ProBook 4540s (Clover)
CPU: i5-3320m/HM76
Graphics: HD4000, 1366x768

Use CPU-Z on Windows to find CPU (Core iX-xxx) and motherboard chipset (HMxx), and graphics capabilities. For a laptop, these details are important and affect critical installation procedures.

Note: When specifying your bootloader, if using Clover legacy, please be sure to specify "Clover legacy"). Specifying "Clover" will be assumed as "Clover UEFI"

--

Looking at your profile:
Mobo: missing model of laptop (and chipset should be in 'CPU').
CPU: chipset should be here too (not in Mobo)
Graphics: missing screen resolution

Hows the profile looking?

 

[RehabMan]

Hows the profile looking?

Typically with a single system, all information is placed in the profile and the signature is left blank. Because with an incomplete profile, I may only look there, and never look at the signature for the missing information.

 

[ThatRedstoneGuy]

Typically with a single system, all information is placed in the profile and the signature is left blank. Because with an incomplete profile, I may only look there, and never look at the signature for the missing information.

Interesting. So back on topic. I get that prohibited sign and you have my latest efi.zip. Any idea? I'm completely lost.

 

[RehabMan]

Interesting. So back on topic. I get that prohibited sign and you have my latest efi.zip. Any idea? I'm completely lost.

Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).

 

[ThatRedstoneGuy]

Boot verbose, show photo. Attach EFI/Clover folder as ZIP (omit 'themes' folder).

It seems to be getting stuck at 'missing bluetooth controller transport.'

 

[RehabMan]

It seems to be getting stuck at 'missing bluetooth controller transport.'

"Still waiting for root device" when booting from USB indicates a USB problem.

Make sure you try all USB ports. Since is unlikely your USB3 controller is supported, use a USB2 flash drive.

 

[LooseMoose]

Search for ELAN PS2 drivers.

Do you have a link to one I could use..? Really don't know which one to pick.

 

[ThatRedstoneGuy]

"Still waiting for root device" when booting from USB indicates a USB problem.

Make sure you try all USB ports. Since is unlikely your USB3 controller is supported, use a USB2 flash drive.

Okay, all of the ports results the same error and the USB type is 2.0.