Jump to content

Cannot boot from Tahoe USB with only error OC: Boot failed - Aborted OCB: StartImage failed


22 posts in this topic

Recommended Posts

My computer:

 

ASUS PRIME Z370-A (PRIMEZ370A)
Intel Core i5-9600K (BX80684I59600K)
Patriot Viper DDR4, 32 GB,3200MHz, CL16 (PV432G320C6K)
SSD: ADATA 512GB M.2 PCIe NVMe XPG SX8200 Pro
RADEON RX 560 2GB (90YV0AHC-M0NA00)
 
I used Hackintosh from some years, firstly Catalina, now Ventura. I'd like to install the newest Tahoe, but I can't boot USB stick with created installer. Immediately after boot I get black screen with no entry sign and error OC: Boot failed - Aborted OCB: StartImage failed
 
I used this guide: https://kextcache.com/macos-tahoe-hackintosh-guide/ I checked BIOS settings with this guide:
 

Disable: Fast Boot, Secure Boot, CSM (Compatibility Support Module), Intel SGX, CFG Lock (this settings I set)

Enable: Above 4G Decoding (set), but Re-Size BAR Support, XHCI Hand-off I couldn't find in my BIOS

 
To create install media I used: https://kextcache.com/guide-to-create-a-bootable-macos-usb-drive-using-gibmacos-tool/ I tried firstly with HPFS+ and when didn't worked I tried FAT (some YouTube video about installing Tahoe suggested it), but with no results.
Command used to create installer: sudo /Applications/Install\ macOS\ Tahoe.app/Contents/Resources/createinstallmedia --volume /Volumes/hackOS
 
config.plist I created using this guide: https://dortania.github.io/OpenCore-Install-Guide/config.plist/coffee-lake.html#starting-point and hints from https://dortania.github.io/OpenCore-Install-Guide/extras/tahoe.html#table-of-contents (e.g. I included VoodooHDA.kext and changed csr-active-config in config.plist to 03000000.
 

I tried to look for sth about this error. I found it may be connected with FileVault and do this: https://dortania.github.io/OpenCore-Post-Install/universal/security/filevault.html to patch it. I did it, but with no result. I found that it may be something wrong with 

SSDT-PNLF.aml file. I tried include this file in my EFI, and EFI without this file in config.plist. No result. According to used guide, I tried the newest OpenCore 1.0.7, and tried switching it to 1.0.5 used in the guide.

I'm afraid that I may have a mess in ACPI and Kexts due to different tries with different configurations from different guides.

 

I included my latest EFI (I tried different solutions, as I mentioned about it). Thank you in advance for any help.

EFI.zip

Edited by kzez1986
2 hours ago, kzez1986 said:

I'd like to install the newest Tahoe

Disable SecureBootModel. iMac Pro 1.1 is not compatible with Tahoe. Either use Boot/Patch or MacPro 7.1. Disable the BT kext until the end of installation. WhateverGreen.kext 1.7.1 may cause problems for RX560; use version 1.7.1d.

If you are installing Tahoe using a dGPU, you will need to turn off the iGPU in the BIOS using SMBIOS = MacPro7,1 and add -wegnoigpu to boot-args.
If your dGPU is Polaris 10 or later but Navi 10 series or earlier, use WhateverGreen.kex tversion 1.7.1d.
If you are using WhateverGreen.kex version 1.7.0, disable WhateverGreen.kex from Kernel/add/ before installing, then enable WhateverGreen.kex after installation.
 

Edited by Asural
8 hours ago, Oyecomova said:

Trying this without changes give me a graphical menu of the choosing operating system, but next the same error. Firstly, included screen and next error OC: Boot failed - Aborted OCB: StartImage failed. Exaxtly the same result.

1000010338.jpg

7 hours ago, strangeron said:

Disable SecureBootModel. iMac Pro 1.1 is not compatible with Tahoe. Use MacPro 7.1. Disable the BT kext until the end of installation. WhateverGreen.kext 1.7.1 may cause problems for RX560; use version 1.7.1d.

@kzez1986 I'd listen above recommendation by @strangeron.

 

Unfortunately, I made changes according to your advices (included new config.plist), but the same error. I also replaced whatevergreen.kext with version from this post: https://www.insanelymac.com/forum/topic/361912-release-macos-tahoe-261/#comment-2843158 

 

Changes I made:

- disabled SecureBootModel

- changed MacPto1,1 to MacPro7,1

- added wegnoigpu to boot-args

- disabled BlueTooth Fix kext

 

I wonder that this is a some stupid bug like incorrectly made installation media or something like this.

 

config.plist

It moved forward slightly, but running installer is stuck at line successfully initialised AHCI controlled, as I included on the screen. I waited more than half an hour and nothing happened. I also included log from OpenCore.

20251223_100026.jpg

opencore-2025-12-23-090112.txt

1 hour ago, eSaF said:

Hi try using the Hybrid WEG.kext may help.

Replace the one in the kext folder and the config.plist, reboot, clean NvRAM and see if the result is favourable.

 

Good luck.

 

WhateverGreen.kext.zip 275.67 kB · 1 download

This kext didn't change anything. I cleaned NVRAM and replaced kexts.

 

44 minutes ago, Asural said:

This may or may not happen depending on the model, but sometimes I was unable to get out of the loop unless I used the Apple Keyboard.
 

 

I've an old iMac with Apple Keyboard. I tried to connect it, but sth strange happened. This keyboard worked with my PC, but USB option disappeared from Boot Menu! What's more, I couldn't boot from my hard drive with Ventura. Of course, I didn't disconnect anything expect the keyboard replaced by Apple.

45 minutes ago, kzez1986 said:

I've an old iMac with Apple Keyboard. I tried to connect it, but sth strange happened. This keyboard worked with my PC, but USB option disappeared from Boot Menu! What's more, I couldn't boot from my hard drive with Ventura. Of course, I didn't disconnect anything expect the keyboard replaced by Apple.

One more thing I forgot to mention: in Sequoia and later, you cannot escape the loop unless you disconnect the built-in DVD/CD drive.
 

18 minutes ago, Asural said:

One more thing I forgot to mention: in Sequoia and later, you cannot escape the loop unless you disconnect the built-in DVD/CD drive.
 

I have an old DVD drive, but it isn't connected, it's only takes place in the tower instead of a hole. It's probably IDE and it isn't possible to connect it. I've only connected USB DVD drive. I can disconnect it, if it can help.

 

But why do you think it's a loop? The loop would be when the same notice appears infinite times. But for me, it looks like installer hangs up on line successfully initialised AHCI controlled and does nothing.

Edited by kzez1986
42 minutes ago, kzez1986 said:

I have an old DVD drive, but it isn't connected, it's only takes place in the tower instead of a hole. It's probably IDE and it isn't possible to connect it. I've only connected USB DVD drive. I can disconnect it, if it can help.

 

But why do you think it's a loop? The loop would be when the same notice appears infinite times. But for me, it looks like installer hangs up on line successfully initialised AHCI controlled and does nothing.

I see the log for this post often, but it seems to have finished after quite a long time.
It talks about the internal DVD/CD connection when installing Sequoia, and it keeps getting an infinite Port Error .
The same error is displayed as an AHCI error, so don't worry about it if it's not related to you.
 

This reminds me of something else...
The USBMap.kext up to Sequoia will not work, so you'll need to create a USBMap.kext for Tahoe.
It seems you can also create one using Hackintool, and I used that tool to create it.
 

45 minutes ago, Asural said:

so you'll need to create a USBMap.kext for Tahoe.

The kext I added is an adapted version of the USB kext prepared for the Z370, but for the Tahoe.

  • Like 1
8 hours ago, strangeron said:

Add the attached kext to config.plist and boot the system with NVRam Reset.UTBMap.kext.zip

You can also try with the attached EFI.

https://drive.google.com/file/d/1eRCA6lmyU0FA_7tyugF7gKPjKau9-hLw/view?usp=sharing

 

Thank you very much for this EFI. It installed without any modifications. The only problem now is do sound. Should I use VoodoHda.kext?

12 hours ago, kzez1986 said:

Should I use VoodoHda.kext?

First, try changing the alcid=xx value to a value compatible with your sound card model. Currently, alcid=17. A different value might work with sound. If that doesn't work, VooDooHDA is another option.

I have another something strange problem. I teied to configure sound and something broke tha lt MacOS stops running. I reinstalled it to have a fresh copy, but another installations behaves strange. After first-time configuration it runs properly, but after first reset something sttange happens. It runs in something sttange mode thay I don't understand:

 

- it runs very quickly, one second

- there are no text lines, only Apple logo through a second

- user icon on login screen is different than I chose during install

- my password isn't accepted, so I can't login.

 

The only thing I can do is another reinstallation. Only one installation behaved normal, another after first reset were in this sttange mode without login possibility.

 

Do you know where's the problem?

@kzez1986 FileVault issue. Have a read here.

 

I suggest you search the forum for ways to disable FileVault for fresh install or disable FileVault via Terminal on already installed macOS in recovery environment. Alternatively, continue using FileVault with suggested workaround in the above link.

I found a solution. I changed csr-active-config to install VoodooHDA.kext and it caused problems. During installation and first reboot after first run after first-time config it must be set to 0. It can be changed later. I also properly installed VoodooHDA and audio is working now.

×
×
  • Create New...