Cortex-a53 Cannot Resume. Cannot Read 'pc'. Cannot Read 'r0'. Instruction Transfer Timeout

# OpenCore Boot Bug

Issues surrounding from initial booting the USB itself to right earlier you cull to kick the macOS installer

• Stuck on a blackness screen before picker
• Stuck on no vault provided!
• Stuck on OC: Invalid Vault manner
• Can't run across macOS partitions
• Stuck on OCB: OcScanForBootEntries failure - Not Found
• Stuck on OCB: failed to match a default kicking pick
• Stuck on OCB: System has no boot entries
• Stuck on OCS: No schema for DSDT, KernelAndKextPatch, RtVariable, SMBIOS, SystemParameters...
• Stuck on OC: Driver Thirty.efi at 0 cannot be found
• Receiving "Failed to parse real field of type 1"
• Tin't select annihilation in the picker
• SSDTs not being added
• Booting OpenCore reboots to BIOS
• OCABC: Incompatible OpenRuntime r4, require r10
• Failed to open OpenCore image - Admission Denied
• OC: Failed to discover SB model disable halting on disquisitional error

# Stuck on a blackness screen before picker

This is likely some mistake either on your firmware or OpenCore, specifically it'due south having troubles loading all the drivers and presenting the menu. The all-time way to diagnose it is via OpenCore's DEBUG Build and checking the logs whether OpenCore actually loaded, and if and then what is it getting stuck on.

Situations where OpenCore did not load:

• If there are no logs nowadays even after setting up the DEBUG version of OpenCore with Target set to 67, there'south likely an issue either with:
  • Incorrect USB Folder Structure
    • See Booting OpenCore reboots to BIOS for more info
  • Firmware does not support UEFI
    • You'll need to setup DuetPkg, this is covered in both the macOS and Windows install pages

Situations where OpenCore did load:

• Check the final line printed in your logs, there will likely be either a .efi driver that'due south been loaded or some form of Assert
  • For ASSERT'southward, you lot'll desire to actually inform the developers about this issue hither: Acidanthera's Bugtracker (opens new window)
  • For .efi drivers getting stuck, bank check over the following:
    • HfsPlus.efi load issues:
      • Effort using HfsPlusLegacy.efi (opens new window) instead
      • This is recommended for CPUs that do not back up RDRAND, mainly relevant for 3rd gen Ivy bridge i3 and older
      • VBoxHfs.efi (opens new window) is another option however is much slower than HfsPlus'south version
    • HiiDatabase.efi load problems:
      • Likely your firmware already supports HiiDatabase, so the driver is conflicting. Simply remove the driver as you don't need information technology.

# Stuck on no vault provided!

Plough off Vaulting in your config.plist nether Misc -> Security -> Vault by setting information technology to:

• Optional

If you have already executed the sign.command you will demand to restore the OpenCore.efi file as the 256 byte RSA-2048 signature has been shoved in. Can grab a new copy of OpenCore.efi here: OpenCorePkg (opens new window)

Note: Vault and FileVault are 2 split up things, run across Security and FileVault (opens new window) for more details

# Stuck on OC: Invalid Vault mode

This is likely a spelling mistake, options in OpenCore are case-sensitive and so make sure you lot check closely, Optional is the correct way to enter information technology nether Misc -> Security -> Vault

# Tin can't meet macOS partitions

Main things to cheque:

• ScanPolicy prepare to 0 to testify all drives
• Have the proper firmware drivers such as HfsPlus(Annotation ApfsDriverLoader shouldn't exist used in 0.five.8)
• Gear up UnblockFsConnect to True in config.plist -> UEFI -> Quirks. Needed for some HP systems
• Set SATA Style: AHCI in BIOS
• Set UEFI -> APFS to meet APFS based drives:
  • EnableJumpstart: YES
  • HideVerbose: NO
  • If running older versions of High Sierra(ie. 10.13.5 or older), set the following:
    • MinDate: -i
    • MinVersion: -1

# Stuck on OCB: OcScanForBootEntries failure - Not Found

This is due to OpenCore being unable to find whatsoever drives with the current ScanPolicy, setting to 0 will permit all boot options to exist shown

• Misc -> Security -> ScanPolicy -> 0

# Stuck on OCB: failed to match a default boot option

Aforementioned fix equally OCB: OcScanForBootEntries failure - Non Plant, OpenCore is unable to find any drives with the electric current ScanPolicy, setting to 0 will let all boot options to be shown

• Misc -> Security -> ScanPolicy -> 0

# Stuck on OCB: System has no kicking entries

Aforementioned fix as the to a higher place 2:

• Misc -> Security -> ScanPolicy -> 0

# Stuck on OCS: No schema for DSDT, KernelAndKextPatch, RtVariable, SMBIOS, SystemParameters...

This is due to either using a Clover config with OpenCore or using a configurator such every bit Mackie's Clover and OpenCore configurator. You'll need to offset over and brand a new config or effigy out all the garbage you need to remove from your config. This is why we don't back up configurators, they are known for these issues

• Annotation: These aforementioned issues will also occur if y'all mix outdated configs with newer versions of OpenCore. Please update them accordingly

# Stuck on OC: Driver XXX.efi at 0 cannot be constitute

This is due to an entry existence in your config.plist, nonetheless non present in your EFI. To resolve:

• Ensure your EFI/OC/Drivers matches up with your config.plist -> UEFI -> Drivers
  • If not, please run Cmd/Ctrl+R with OpenCore to re-snapshot your config.plist

Note that the entries are example-sensitive.

# Receiving "Failed to parse real field of type 1"

This is due to a value fix as real when it'south not supposed to be, generally being that Xcode converted HaltLevel by accident:

To fix, swap real for integer:

# Tin can't select anything in the picker

This is due to either a few things

• Incompatible keyboard commuter:

  • Disable PollAppleHotKeys and enable KeySupport, so remove OpenUsbKbDxe (opens new window) from your config.plist -> UEFI -> Drivers
  • If the above doesn't work, reverse: disable KeySupport, then add OpenUsbKbDxe (opens new window) to your config.plist -> UEFI -> Drivers

• Missing PS2 keyboard commuter(Ignore if using a USB keyboard):

  • While most firmwares will include it past default, some laptops and older PCs may still demand Ps2KeyboardDxe.efi (opens new window) to function correctly. Remember to add together this to your config.plist too

# SSDTs not existence added

So with OpenCore, there's some extra security checks added effectually ACPI files, specifically that table length header must equal to the file size. This is actually the fault of iASL when you compiled the file. Instance of how to discover it:

The Length and checksum value is what nosotros care about, and then if our SSDT is actually 347 bytes and so we want to change Length to 0x0000015B (347)(the 015B is in HEX)

Best style to actually fix this is to catch a newer re-create of iASL or Acidanthera's copy of MaciASL (opens new window) and remaking the SSDT

• Note: MaciASL distributed past Rehabman are prone to ACPI corruption, please avert information technology as they no longer maintain their repos

# Booting OpenCore reboots to BIOS

• Incorrect EFI folder construction, make certain all of your OC files are inside an EFI folder located on your ESP(EFI system partition)

Example of folder structure

# OCABC: Incompatible OpenRuntime r4, require r10

Outdated OpenRuntime.efi, brand certain BOOTx64.efi, OpenCore.efi and OpenRuntime are all from the same exact build. Annihilation mismatched will break booting

• Annotation: FwRuntimeServices has been renamed to OpenRuntime with 0.5.7 and newer

# Failed to open up OpenCore prototype - Access Denied

On newer Microsoft Surface device firmwares, loading OpenCore volition at present upshot in a security violation fifty-fifty when Secure Boot is disabled. To resolve this, enable UEFI -> Quirks -> DisableSecurityPolicy in your config.plist. See here for more info: Failed to open up OpenCore epitome - Access Denied #1446 (opens new window)

# OC: Failed to detect SB model disable halting on disquisitional error

This is a typo, ensure that in your config.plist Misc -> Security -> SecureBootModel is gear up to Disabled

wilsonworning.blogspot.com

Source: https://dortania.github.io/OpenCore-Install-Guide/troubleshooting/extended/opencore-issues.html

Share this post