Lenovo Legion 5 Pro16ACH6H AMD Hackintosh — Ventura boots through verbose, then black screen

[Minime]

Hi everyone,

I'm trying to install macOS Ventura on a Lenovo Legion 5 Pro, and I'm stuck at the same point during boot. I've been troubleshooting this for a while and would really appreciate some guidance from someone experienced with AMD laptop Hackintosh setups.

Hardware​

Laptop: Lenovo Legion 5 Pro

• CPU: AMD Ryzen 7 5800H
• GPU: Nvidia 3070 but disabled
• iGPU: AMD Radeon Graphics (Vega)
• RAM: 32 GB
• Internal SSD: Samsung MZVLB1T0HBLR-000L2 1 TB NVMe
• Wi-Fi/Bluetooth: MediaTek Wifi 6 MT7921(disabled)
• Ethernet: Realtek
• OS: Windows 11
• Target macOS: macOS Ventura

I have a working macOS Ventura USB installer.

OpenCore starts correctly and I can select:

• Windows
• Install macOS Ventura

When I select Install macOS Ventura, macOS starts verbose booting.

I get a large amount of verbose output and it gets quite far into the boot process.

However, eventually the display becomes completely black/faint and the system appears to hang.

The LCD itself is still powered, so it doesn't look like the laptop simply turned the display off.

I've also tried:

• Waiting 15+ minutes
• Cmd + Ctrl + F1/F2
• External monitor
• Rebooting and trying again
• Multiple boot attempts

None of these recover the display.

The last visible messages vary slightly between boots.

SMBIOS: MacBookPro16,3

BIOS :

SecureBoot: disable

Deviceguard: disable

Memorybuffer: 4G

If you have any question regarding anything please feel free to ask also here's my EFI:

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

 

[Edhawk]

OK, the first thing I would point out is that your Samsung NVMe drive is not the best choice. Read the blurb about Samsung PM981 drives on the Anti-Hackintosh Buyers Guide linked below.

Storage | Anti-Hackintosh Buyers Guide

Common issues with AMD laptops, using VEGA graphics is that NootedRed.kext can cause a Black screen issue when installing macOS. You would be advised in this case to disable NootedRed.kext in your config.plist until you reach the macOS Desktop, i.e. can log in to your new user account.

Another element is that NootedRed.kext doesn't play well with any DeviceProperties, it is usually best to avoid using any DeviceProperties, add the elements you need via a custom SSDT or Boot Argument when possible (i.e. for audio use alcid=21).

Looking through your EFI folder I would comment as follows, see screenshot below.

Finder view of EFI folder contents.

The IOReg path for the Nvidia dGPU may not be a match for how the dGPU is addressed in your AMD system. The SSDT-dGPU-Optimus-Off.aml table seems to be set for what I would expect to find in an Intel laptop. You may have to use the -wegnoegpu boot argument to disable the Nvidia dGPU in macOS.

Contents of SSDT for disabling the Nvidia dGPU.

This appears to be a Dortania SSDT that hasn't been adapted to suite your AMD laptop settings. So it is probably not doing anything helpful when you boot in to the macOS installer. This may be another reason why you are seeing the black screen after the Verbose text. As the laptop would look to use the dGPU when possible, i.e. when power is supplied via the power brick.

Your /EFI/OC/Kexts folder contains too many unnecessary kexts, for the first installation of macOS on an AMD laptop. You would be better off keeping the number of kexts to a minimum of those actually required for the components in the system, which you need to boot and install macOS.

1. As your builtin WiFi & Bluetooth (MediaTek) are not compatible with macOS you shouldn't have any WiFi or Bluetooth related kexts in your setup.
2. Any Sensor kexts are likewise unnecessary, except for the Battery Manager.
3. Others such as FeatureUnlock, NVMeFix and RestrictEvents can be omitted/disabled until the system is booting to the OS desktop. As none of these are essential for a first installation.

Your /EFI/OC/Tools folder contains a lot of unnecessary files.



All that should be present in this folder is the OpenShell.efi file, all the others are unnecessary and simply taking up space, they have absolutely no bearing on your hack.

Were I creating your OC EFI it would look like this.

Revised EFI folder contents, with appropriate edits made to the config.plist to match.

The AMD Kernel patches you are using are at least a version that would support Ventura. However if you planned to update the system to Sonoma or newer you would need to replace/update the AMD Patches to do so.

The Bluetooth entries in the NVRAM > Add section of your config.plist are again unnecessary. Especially as the corresponding parts are missing from the Delete section of the NVRAM entries.

I have attached a revised EFI folder for you to try, based on the comments above. All you should need to do is add your Serial Number, MLB, ROM and SystemUUID details to the config.plist.