Archive for January 2026

How to Handle Cant remove spoofed device from account with OpenCore or OCLP

Apps guide kimi MacBookPro OpenCoreLegacyPatcher Troubleshooting
--

How to Handle Cant remove spoofed device from account with OpenCore or OCLP

This guide turns the original report into a structured troubleshooting path you can follow without changing too many variables at once.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OpenCore Hackintosh or OCLP case until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

The common cause is usually a mismatch between OpenCore, macOS, hardware support and the installed kexts.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Identify the exact machine: Record the model identifier, CPU, GPU, storage type and wireless chipset.
  3. Check support status: Compare the hardware against current OpenCore or OCLP compatibility notes.
  4. Update core files: Refresh kexts, OpenCore and config snapshots as one controlled change.
  5. Test one feature at a time: Boot, graphics, network, sleep and apps should be verified separately.
  6. Document the result: Save the working EFI, macOS build, OCLP version and any boot arguments used.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • The machine boots consistently.
  • The original problem can no longer be reproduced.
  • No new critical feature broke during the fix.
  • A known-good EFI backup exists.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous EFI and NVRAM state.
  • Return to the last stable macOS version.
  • Avoid unsupported updates on machines needed for work.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "Cant remove spoofed device from account"

I had a MacBook pro 2015 spoofed as an 2016 MacBook pro. I went to go un spoof it and before I did signed out of the apple account. Now for some reason the old spoofed device still appears and the “remove from account” does nothing. Its sitting there like a dead terd how can I remove it.

submitted by /u/CF_169
[link] [comments]
[► Source]
Share:

How to Fix OCLP / createinstallmedia always ends with “Killed: 9” when creating Mojave USB from Apple Silicon Mac on macOS

Apps Boot Graphics guide kimi MacBookPro macOSSonoma macOSTahoe OpenCore OpenCoreLegacyPatcher Performance Troubleshooting USB WiFi
--

How to Fix OCLP / createinstallmedia always ends with “Killed: 9” when creating Mojave USB from Apple Silicon Mac on macOS

Wi-Fi, Bluetooth, AWDL, Continuity and Location Services problems usually come from chipset support, kext pairing, privacy settings or network-location corruption.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OpenCore Hackintosh or OCLP case until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

On Hackintosh systems, Location Services and Continuity depend on working Wi-Fi, Bluetooth, AWDL and correct AirportItlwm or itlwm/HeliPort behaviour.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Confirm the exact chipset: Identify the Wi-Fi, Bluetooth and Ethernet controller from System Information, Hackintool or Linux/Windows device manager.
  3. Use the correct network stack: Match AirportItlwm, itlwm, HeliPort, IntelBluetoothFirmware and BlueToolFixup to the exact macOS version.
  4. Reset macOS network state: Remove the current Wi-Fi service, reboot, add it again, then reconnect to a simple WPA2 network before testing advanced features.
  5. Check privacy permissions: Open System Settings > Privacy & Security > Location Services and confirm Location Services, Maps, Weather and system services are enabled.
  6. Test Apple features separately: Verify normal internet first, then Bluetooth, then AirDrop/Continuity. Do not debug all three at the same time.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • Maps can locate you without falling back to a stale location.
  • Wi-Fi reconnects after reboot and sleep.
  • Bluetooth remains available after a cold boot.
  • Console no longer shows repeated wireless or location daemon errors.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous EFI if Wi-Fi disappears completely.
  • Switch from AirportItlwm to itlwm + HeliPort, or the reverse, if the issue is specific to one driver path.
  • Use Ethernet or USB tethering while testing so you do not lose access to downloads.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "OCLP / createinstallmedia always ends with “Killed: 9” when creating Mojave USB from Apple Silicon Mac"

Hi everyone,

I’m posting this because I haven’t found any existing post describing this exact issue, and I’ve already tried a lot of things before writing this post.

I’m trying to create a macOS Mojave (10.14.6) installer USB using OpenCore Legacy Patcher, but the process always fails with Killed: 9, no matter what I do.

I’ll attach a screenshot of the error.

Target Mac (the one I want to install Mojave on)

MacBook Pro 17-inch Mid 2009

CPU: Intel Core 2 Duo

GPU: NVIDIA GeForce 9600M GT and 9400 m

RAM: 8 GB (upgraded)

Storage: 256 GB SATA SSD (upgraded)

Original HDD removed, and there was no macos installation on it because i ve kinda messed up in the past with, ending up installing windows 10 then linux mint on it, with no macos leftovers, but that was years ago.

Machine is fully functional (USB boot, disk detection, etc.)

My goal OS:

macOS Mojave 10.14.6 (tried to install high sierra with high sierra patcher but got an error too will trying to create it)

Host Mac (used to create the installer)

MacBook Pro (Apple Silicon M1)

macOS Tahoe (latest)

USB-C only (using USB-C → USB-A adapter, tested with different adapters and different USB Disks)

What I’m trying to do

Create a bootable Mojave USB installer

Using OpenCore Legacy Patcher (latest version)

Then boot the 2009 MBP via OpenCore and install Mojave

What i ve tried

Firstly, created a bootable OS X El Capitan USB successfully after downloading .app file with Mist

Installer launches correctly on the target Mac

Installation fails with “This copy of the installer cannot be verified”

Tried all known date workarounds from Recovery:Setting system date back to 2016 / 2017 / 2018 Installing completely offline Disabling SIP

Even with the correct date and no network, El Capitan still refuses to install

Then, while using High Sierra Patcher (failed) :

Installer image is restored correctly to the USB key

During the next step (copying System/Installation/Packages), the process fails

Errors encountered:

cp: /Volumes/USB/... No such file or directory

This happens consistently, even after:

Fully erasing the USB (GPT + HFS+) multiple times, with terminal and disk utility

Launching the patcher from /Applications (not from the DMG)

Ejecting all mounted images

Rebooting the host Mac

https://preview.redd.it/6k9ok3mjhqgg1.jpeg?width=3456&format=pjpg&auto=webp&s=cf94000c2774e00d1d5ae89dcb8d98ce0643f253

Finally, with OCLP :

Using gibMacOS to download and build the Mojave installer (.app)

Installer download and creation attempts (chronological)

First, I tried downloading macOS Mojave using Mist on my Apple Silicon Mac.

The Mojave download failed and never completed successfully.

I then tried OpenCore Legacy Patcher (OCLP).

Mojave did not appear in the installer list, even with “Show older versions” enabled.

After that, I used gibMacOS to download macOS Mojave.

gibMacOS successfully downloaded the full macOS Mojave 10.14.6 installer

A valid Install macOS Mojave.app (~6 GB) was created.

I then used this installer with OpenCore Legacy Patcher:

Selected Create macOS Installer

Chose Use existing macOS installer

Selected the Mojave .app

Selected the USB drive

During installer creation, the USB drive is erased and prepared correctly, but when createinstallmedia starts, the process always fails with the same error:

Killed: 9

This error happens consistently, regardless of the installer source, the usb drive, the USB A to USB C, adaptater or the USB C port used.

https://preview.redd.it/nnvk4jztjqgg1.png?width=1264&format=png&auto=webp&s=4dfd98598e983ce9c13b4e792bd361abb58df9c4

At this point, I’m out of ideas. I would really appreciate any input.

Thanks in advance for your help.

submitted by /u/Agitated-Equal-485
[link] [comments]
[► Source]
Share:

How to Handle Another great e-waste find: Fully loaded 2015 13” Pro with OpenCore or OCLP

guide kimi OpenCoreLegacyPatcher
--

How to Handle Another great e-waste find: Fully loaded 2015 13” Pro with OpenCore or OCLP

This guide turns the original report into a structured troubleshooting path you can follow without changing too many variables at once.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OpenCore Hackintosh or OCLP case until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

The common cause is usually a mismatch between OpenCore, macOS, hardware support and the installed kexts.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Identify the exact machine: Record the model identifier, CPU, GPU, storage type and wireless chipset.
  3. Check support status: Compare the hardware against current OpenCore or OCLP compatibility notes.
  4. Update core files: Refresh kexts, OpenCore and config snapshots as one controlled change.
  5. Test one feature at a time: Boot, graphics, network, sleep and apps should be verified separately.
  6. Document the result: Save the working EFI, macOS build, OCLP version and any boot arguments used.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • The machine boots consistently.
  • The original problem can no longer be reproduced.
  • No new critical feature broke during the fix.
  • A known-good EFI backup exists.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous EFI and NVRAM state.
  • Return to the last stable macOS version.
  • Avoid unsupported updates on machines needed for work.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "Another great e-waste find: Fully loaded 2015 13” Pro"

Another great e-waste find: Fully loaded 2015 13” Pro submitted by /u/Consistent-Order5375
[link] [comments]
[► Source]
Share:

How to Choose the Best macOS Version for Development and maintenance

guide kimi macOSTahoe OpenCoreLegacyPatcher
--

How to Choose the Best macOS Version for Development and maintenance

The best upgrade is not always the newest release; it is the newest release that keeps graphics, Wi-Fi, sleep, battery and daily apps reliable.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OCLP unsupported Mac until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

Unsupported Macs depend on OpenCore Legacy Patcher root patches, and each macOS release changes drivers, security policy and graphics behaviour.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Match macOS to hardware age: 2011-2012 Macs often behave better on Monterey or Ventura; 2013-2017 Macs can usually test Sonoma or Sequoia with an SSD and enough RAM.
  3. Avoid risky releases for production: Treat macOS Tahoe or any newly unsupported path as experimental until OCLP support is explicit.
  4. Update OCLP first: Install the latest OpenCore Legacy Patcher, build/install OpenCore, then run root patches after macOS boots.
  5. Test the real workload: Check browser tabs, Office/Adobe, printing, sleep, Wi-Fi, Bluetooth and battery before calling the upgrade successful.
  6. Keep a downgrade path: Have a USB installer for the previous stable macOS before upgrading.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • The machine boots twice without manual intervention.
  • Graphics acceleration and Wi-Fi work after root patches.
  • The user apps that motivated the upgrade actually launch.
  • Battery and thermals are acceptable for the intended workload.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous macOS from Time Machine.
  • Reinstall the older stable release with OCLP.
  • Keep data on a separate backup before experimenting again.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "Development and maintenance"

YOU GUYS ARE FUCKING LIERS LIKE YOU SAID IN WINTER TAHOE SUPPORT WILL BE RELEASED WITH VERSION 3.0.0 GTA SIX WILL COME OUT BEFORE SO GET YOUR FUCKING VERSION RELEASED OR I AM REPORTING YOU TO DCMA GROUP

submitted by /u/eliekhalil2005
[link] [comments]
[► Source]
Share:

How to Choose the Best macOS Version for all black selection in word

Apps guide iMac kimi macOSVentura OpenCore OpenCoreLegacyPatcher
--

How to Choose the Best macOS Version for all black selection in word

The best upgrade is not always the newest release; it is the newest release that keeps graphics, Wi-Fi, sleep, battery and daily apps reliable.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OCLP unsupported Mac until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

Unsupported Macs depend on OpenCore Legacy Patcher root patches, and each macOS release changes drivers, security policy and graphics behaviour.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Match macOS to hardware age: 2011-2012 Macs often behave better on Monterey or Ventura; 2013-2017 Macs can usually test Sonoma or Sequoia with an SSD and enough RAM.
  3. Avoid risky releases for production: Treat macOS Tahoe or any newly unsupported path as experimental until OCLP support is explicit.
  4. Update OCLP first: Install the latest OpenCore Legacy Patcher, build/install OpenCore, then run root patches after macOS boots.
  5. Test the real workload: Check browser tabs, Office/Adobe, printing, sleep, Wi-Fi, Bluetooth and battery before calling the upgrade successful.
  6. Keep a downgrade path: Have a USB installer for the previous stable macOS before upgrading.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • The machine boots twice without manual intervention.
  • Graphics acceleration and Wi-Fi work after root patches.
  • The user apps that motivated the upgrade actually launch.
  • Battery and thermals are acceptable for the intended workload.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the previous macOS from Time Machine.
  • Reinstall the older stable release with OCLP.
  • Keep data on a separate backup before experimenting again.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "all black selection in word"

I have a 2009 iMac with Ventura installed via OpenCore. I'm having trouble selecting text in Word. A large, completely black selection appears, making it impossible to see what's underneath or the surrounding text. Is there a setting I can fix this?

submitted by /u/Ok-Requirement3682
[link] [comments]
[► Source]
Share:

How to Fix Triple-Boot OCLP/Win/Linux on a MacPro5,1 During macOS Boot or Installation

Boot guide kimi MacPro OpenCoreLegacyPatcher
--

How to Fix Triple-Boot OCLP/Win/Linux on a MacPro5,1 During macOS Boot or Installation

Boot failures need a predictable pass through firmware, USB, storage, EFI and verbose logs before reinstalling macOS.

1. Prerequisites

  • Identify the exact machine: Do not continue until the exact Mac identifier or motherboard/laptop model is known.
  • List the hardware: CPU, GPU, Wi-Fi/Bluetooth chipset, Ethernet controller, storage type and current macOS build must be written down.
  • Collect the tools: Keep OpenCore, OCLP, ProperTree, MountEFI, a USB installer and a backup disk ready.
  • Use verification tools: Confirm hardware with AIDA64, HWiNFO, Linux lspci, Windows Device Manager, macOS System Information or Hackintool.
  • Keep downloads local: Save required kexts before disconnecting from the network or editing EFI.
  • Do not rush: Verify hardware compatibility before changing BIOS settings, root patches or config.plist.

2. Compatibility Snapshot

  • Target type: Treat this as a OpenCore Hackintosh or OCLP case until the exact model proves otherwise.
  • CPU support: Intel Haswell, Skylake, Kaby Lake, Coffee Lake, Ice Lake and Tiger Lake are common OpenCore targets. AMD can work, but kernel patches and app compatibility must be considered.
  • GPU support: AMD GPUs are usually the safest dGPU route; NVIDIA support is limited after Kepler; Intel iGPU success depends on generation, DVMT and framebuffer configuration.
  • Motherboard and chipset: Prefer proper UEFI firmware on Intel Z/H/B series boards. Laptop firmware is stricter and should never be treated like a desktop guide.
  • RAM, storage, network and audio: Start without XMP when debugging, prefer compatible NVMe/SATA SSDs, identify the exact Wi-Fi/Bluetooth card and note the HDA audio codec.
  • Known risk areas: Graphics acceleration, USB mapping, Wi-Fi/Bluetooth, sleep/wake, Apple services and macOS updates are the first things to test.
  • Unsupported paths: Be cautious with NVIDIA Maxwell/Pascal/Turing/Ampere, Intel Iris Xe, experimental macOS Tahoe installs and unknown laptop Wi-Fi cards.
  • OpenCore vs Clover: Use OpenCore as the modern default. Mention Clover only for legacy context or migration.

3. Installation Preparation

  1. Back up first: Keep a Time Machine backup and a zipped copy of the current EFI folder on another disk.
  2. Identify hardware before starting: Use AIDA64, HWiNFO, Windows Device Manager, Linux lspci, macOS System Information or Hackintool before editing EFI.
  3. Prepare firmware: Disable Secure Boot, Fast Boot, CSM/Legacy and CFG Lock where possible. Disable VT-d unless DisableIoMapper is correctly configured.
  4. Enable required settings: Use UEFI mode, Above 4G Decoding where appropriate, Hyper-Threading, EHCI/XHCI Hand-off, OS Type > Other OS and SATA Mode > AHCI.
  5. Prepare graphics firmware: For iGPU systems, enable iGPU Multi-Monitor when required and set DVMT pre-allocated memory to at least 64 MB if the BIOS exposes it.
  6. Create the installer: Use a 16 GB or larger USB drive, GUID/GPT partitioning and a clean installer from App Store, OCLP, ANYmacOS or gibMacOS.
  7. Format correctly: Use APFS for Catalina and newer. Use HFS+ only for older releases where that is expected.
  8. Build or refresh EFI: Update OpenCore, Lilu, VirtualSMC and required kexts as a matched set, not as random individual files.
  9. Understand the installer phases: macOS usually reboots into an installer stage and then into the target disk continuation. Pick the correct entry in the OpenCore picker each time.
  10. For OCLP Macs: Build and install OpenCore with OpenCore Legacy Patcher, then apply post-install root patches after the first successful boot.

4. EFI and config.plist Review

  1. EFI layout: Check BOOT, OC/ACPI, OC/Drivers, OC/Kexts and OC/Tools. Every file in the folders must be reflected correctly in config.plist.
  2. Essential kexts: Confirm Lilu, VirtualSMC, WhateverGreen, AppleALC, IntelMausi or RealtekRTL8111, USBMap/UTBMap, NVMeFix and CPUFriend only when the hardware needs them.
  3. ACPI: Confirm SSDTs match the hardware generation and remove tables copied from unrelated builds.
  4. Common SSDTs: Review SSDT-EC, SSDT-PLUG, SSDT-AWAC, SSDT-PMC and SSDT-RHUB. Prefer correctly generated SSDTs over random prebuilt files.
  5. Booter: Check quirks recommended for the CPU generation; wrong memory quirks often cause early boot failure.
  6. DeviceProperties: Verify GPU, audio and network properties only contain values required for this machine.
  7. Kernel: Make sure kext order is sane: Lilu before plugins, VirtualSMC present, and network/graphics kexts matched to macOS.
  8. Misc and NVRAM: Use verbose boot when debugging: -v keepsyms=1 debug=0x100. Remove old experimental arguments once fixed.
  9. PlatformInfo: Use a suitable SMBIOS and never reuse serials from public EFI folders.
  10. SMBIOS examples: Many Coffee Lake+ desktops use iMac20,x style SMBIOS choices; many laptops use MacBookPro-style SMBIOS choices. Generate unique Serial, UUID and MLB with GenSMBIOS.
  11. UEFI: Confirm drivers such as OpenRuntime are current and that obsolete drivers are removed.
  12. Validation: Run ProperTree clean snapshot or ocvalidate after every meaningful edit.

5. Post-Installation

  1. First boot: Reset NVRAM, boot once with verbose mode, then remove temporary debug arguments after the system is stable.
  2. Move EFI internally: Mount the EFI partition on the USB and the target disk with MountEFI, copy the working EFI folder, then confirm the machine boots without the USB.
  3. Root patches: On unsupported Macs, run OCLP Post-Install Root Patch and reboot before judging graphics, Wi-Fi or audio.
  4. Core tests: Confirm Metal acceleration, audio, Ethernet/Wi-Fi, Bluetooth, sleep/wake, USB ports and shutdown.
  5. USB mapping: Map USB ports with USBToolBox/UTBMap.kext or USBMap.kext before relying on sleep, Bluetooth, internal cameras or installer input. Respect the macOS 15-port limit.
  6. Audio: Identify the HDA codec and test AppleALC layout IDs with alcid= or DeviceProperties injection.
  7. Wi-Fi and Bluetooth: Broadcom often uses AirportBrcmFixup paths; Intel usually uses itlwm/HeliPort or AirportItlwm. Bluetooth support varies by macOS release.
  8. iServices: Confirm unique ROM, MLB, serial and working NVRAM before troubleshooting iMessage, FaceTime, iCloud or the App Store.
  9. Power and sleep: Review SSDT-PLUG, CPU frequency scaling, USB mapping, hibernation and relevant pmset settings.
  10. DRM: Test protected video only after graphics acceleration is confirmed. WhateverGreen and shikigva settings are hardware-specific.
  11. Updates: Update OpenCore/OCLP and kexts before installing a macOS point update, not after a failed boot.

6. Troubleshooting

Likely Cause

Most installer stalls come from firmware settings, an invalid config.plist, wrong SSDTs, bad USB mapping or unsupported storage/controller settings.

Reported Issue Fix
  1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
  2. Boot verbose: Add -v keepsyms=1 debug=0x100 so the final visible line gives a real clue.
  3. Check firmware settings: Disable Secure Boot and Fast Boot, set SATA to AHCI, disable CFG Lock if possible, and use UEFI mode.
  4. Validate OpenCore: Update OpenCore, Lilu and core kexts, then run ocvalidate or ProperTree clean snapshot.
  5. Recreate the installer: Use a fresh USB installer and try another USB port; older Macs may need a USB 2.0 hub for input during setup.
  6. Reset NVRAM: Reset NVRAM from the OpenCore picker before retrying the installer.
Common Hackintosh/OCLP Checks
  • Kernel panics: Read the last verbose line and check /Library/Logs/DiagnosticReports after boot. Note whether the failure is EarlyBoot or UserSpace.
  • Stuck at Apple logo or progress bar: Boot with -v keepsyms=1 debug=0x100, photograph the last line and check Booter, Kernel and storage quirks.
  • LOG:EXITBS:START: Review firmware settings, CFG Lock, Booter quirks, OpenRuntime and outdated OpenCore files.
  • DSMOS has arrived or graphics hand-off stall: Check GPU support, WhateverGreen/NootedRed/NootRX choices, SMBIOS and display connector patches. Try -wegnoegpu or agdpmod=pikera only when the hardware calls for it.
  • USB keyboard, mouse or ports not working: Try a USB 2.0 hub, check XHCI settings, rebuild USB mapping and avoid exceeding the macOS port limit.
  • No graphics acceleration: Confirm Metal support in System Information, review framebuffer/AAPL ig-platform-id values and remove unsupported NVIDIA or Iris Xe assumptions.
  • Wi-Fi, Bluetooth, AWDL, Continuity or Location Services not working: Match AirportItlwm/itlwm, BlueToolFixup and Bluetooth firmware to the macOS version.
  • Ethernet not working: Confirm the PCI ID and switch between IntelMausi, RealtekRTL8111 or another hardware-specific kext as appropriate.
  • Audio missing or partial: Change the AppleALC layout ID, verify the HDA codec and remove conflicting audio injections.
  • Sleep, wake, battery drain or shutdown problems: Check USB mapping, power management, Bluetooth wake sources, hibernation and stale NVRAM.
  • Installer cannot see the disk or APFS/update errors: Confirm AHCI/NVMe support, APFS formatting, date/time, installer integrity and storage kexts. Recovery/prohibited errors can be caused by wrong system date.
  • iServices not working: Clear NVRAM, verify unique ROM/MLB/serial values and confirm the Apple ID is not blocked from activation.
  • App crashes, CEF/Chromium blank screens, Safari/App Store/iCloud issues: Verify graphics acceleration, network identity, SMBIOS services and hardware acceleration settings.
  • macOS update broke boot: Boot from the USB EFI, restore the previous EFI, use an APFS snapshot or restore from Time Machine before attempting another update.

7. Dual Boot and Advanced Configuration

  • Dual boot: Prefer separate physical disks for macOS and Windows/Linux where possible. A shared EFI can work, but it is easier to damage.
  • Windows recovery: If Windows fails after OpenCore changes, repair the Windows BCD and restore the desired boot order from firmware.
  • EFI protection: Keep a backup because Windows updates can overwrite, reorder or add EFI boot entries.
  • Boot picker: Use OpenCore picker entries deliberately and reset NVRAM after major bootloader changes.
  • Custom ACPI: Use iasl and MaciASL only when needed. Decompile the original DSDT and patch device paths such as _HID and _ADR carefully.
  • CFG Lock: GRUB or UEFI shell setup_var methods are risky; use them only with a verified offset for that exact BIOS.
  • SMBIOS refinement: Change SMBIOS only when needed for hardware support or Apple services, then re-test iMessage/iCloud carefully.
  • OpenCore polish: Add OpenCanopy, Resources, HiDPI icons and picker themes only after the system is reliable.
  • Advanced security: Consider Secure Boot Model, SIP, FileVault and root patch trade-offs only after the base system is reliable.
  • Performance tuning: Add CPU power management, USB mapping and sleep fixes after boot, graphics and network are already stable.

8. Verification, Maintenance and Rollback

Verification Checklist
  • Verbose boot moves past the previous stopping line.
  • The installer reaches Disk Utility and sees the target disk.
  • Keyboard, mouse and USB remain active during recovery.
  • OpenCore picker still loads after a cold boot.
Maintenance
  • Update OpenCore, OCLP and kexts before a macOS update, then reboot and test before installing the update itself.
  • Keep dated EFI backups, especially before changing SMBIOS, graphics patches, USB maps or root patches.
  • After every macOS update, check graphics acceleration, Wi-Fi/Bluetooth, audio, sleep/wake and Apple services again.
Rollback Plan
  • Restore the last booting EFI folder.
  • Use the officially supported macOS installer to recover the machine.
  • Do not erase the internal disk until the installer can boot twice consistently.

9. References and Glossary

  • Primary guide: Use the Dortania OpenCore Install Guide for architecture-specific OpenCore rules.
  • Project releases: Check Acidanthera release notes before updating OpenCore, Lilu, WhateverGreen, AppleALC or VirtualSMC.
  • Unsupported Macs: Use OpenCore Legacy Patcher model notes before installing or updating macOS on real Macs.
  • Community references: Compare symptoms with r/hackintosh, TonyMacx86 and InsanelyMac, but never copy an EFI without auditing it.
  • Glossary: EFI, ACPI, SSDT, DSDT, kexts, SMBIOS, NVMe, APFS, iGPU/dGPU, HDA, verbose, panic and picker are the key terms to understand.

Related searches: OpenCore · OCLP · EFI · macOS troubleshooting

Original Question: "Triple-Boot OCLP/Win/Linux on a MacPro5,1?"

I'm refurbishing a Mac Pro 5,1 right now, which obviously has a lot of space to add drives. My plan right now is to try triple booting:

  • MacOS 12 on an NVMe/PCI SSD
  • Fedora 43 on a SATA SSD in Bay-1
  • Windows 10 on another SATA SSD in Bay-2

Is there anything special I need in order to do this? I feel like most of the guides I've seen have revolved around trying to dual-boot multiple OSes on the same drive—which sounds like more of a pain in the ass—but if I'm installing these other OSes on separate drives then it's pretty straight forward, yeah?

submitted by /u/Cool_Barnacle_9021
[link] [comments]
[► Source]
Share: