Just Installed Rebuilt Battery Pack in Prius Red Triangle Again

# Troubleshooting

Hither are some common errors users may experience while using this patcher:

• Stuck on This version of Mac Bone Ten is non supported on this platform
• Cannot kick macOS without the USB
• Infinite Recovery Os Booting
• Reboot when inbound Hibernation (Sleep Wake Failure)
• Booting with a non-flashed GPU
• How to Boot Big Sur Recovery
• Stuck on "Your Mac needs a firmware update"
• No Brightness Control
• Cannot connect Wi-Fi on Monterey with legacy cards
• No Graphics Acceleration
• Black Screen on MacBookPro11,3 in macOS Monterey
• No DisplayPort Output on Mac Pros with Nvidia Kepler
• Volume Hash Mismatch Error in macOS Monterey
• Cannot Disable SIP in recoveryOS

# Stuck on This version of Mac OS X is not supported on this platform

This means macOS has detected a SMBIOS it does not support, to resolve this ensure you lot're booting OpenCore before the macOS installer in the boot picker. Reminder the option volition be called EFI Boot

Once you've booted OpenCore at least once, your hardware should now car kicking information technology until either NVRAM reset or yous remove the drive with OpenCore installed.

# Cannot boot macOS without the USB

Past default, the OpenCore Patcher won't install OpenCore onto the internal bulldoze itself during installs. Instead, you'll need to either manually transfer (opens new window) OpenCore to the internal drive's EFI or run this patcher's Choice 2 again but select your internal drive.

Reminder that once this is done, you'll need to select OpenCore in the boot picker again for your hardware to recollect this entry and car boot from then on.

# Infinite Recovery Os Booting

With OpenCore Legacy Patcher, we rely on Apple Secure Kicking to ensure OS updates work correctly and reliably with Big Sur. Nonetheless this installs NVRAM variables that will confuse your Mac if non running with OpenCore. To resolve, simply uninstall OpenCore and reset NVRAM (opens new window) .

• Annotation: Machines with modded root volumes will besides event in infinite recovery until integrity is restored

# Reboot when entering Hibernation (Sleep Wake Failure)

Known issue on some models (opens new window) , temporary fix is to disable Hibernation:

# Booting with a non-flashed GPU

For Mac Pro, Xserve and iMac users with not-flashed GPUs, yous can all the same easily boot OpenCore and view the entire boot process. To do so, make sure SIP is disabled(to allow NVRAM write admission) and run the following:

• Note yous will need to replace VOLNAME with the Volume proper name of your USB or hard drive with OpenCore
• Note 2: Once done, you tin can re-enable SIP
• Note 3: The EFI partition OpenCore was installed on must be mounted, if it's unmounted simply rerun "Install OpenCore to bulldoze"

Once you boot OpenCore for the first time, LauncherOption will install itself every bit the top boot priority making OpenCore ever launch. Combined with RequestBootVar, all kick options must go through OpenCore ensuring seamless usage even with OS installation and updates.

# How to Boot Large Sur Recovery

By default, the patcher will try to hide extra kick options such as recovery from the user. To make them appear, simply press the "Spacebar" within OpenCore's Picker to list all kicking options.

# Stuck on "Your Mac needs a firmware update"

Full error: "Your Mac needs a firmware update in order to install to this Book. Please select a Mac OS Extended (Journaled) book instead."

This error occurs when macOS determines the firmware to not have full APFS back up. To resolve is quite simple, when building OpenCore head to "Patcher Settings" and enable "Moderate SMBIOS Patching" or higher. This will ensure that the firmware reported will testify as supporting full APFS capabilities.

# No Brightness Control

With OCLP v0.0.22, we've added support for effulgence control on many models. However some users may accept noticed that their brightness keys practise non piece of work.

To work-around, we recommend user try out the below app:

• Brightness Slider (opens new window)

# Cannot connect Wi-Fi on Monterey with legacy cards

With OCLP v0.2.5, we've added support for legacy Wi-Fi on Monterey. However some users may have noticed that they can't connect to wireless networks.

To piece of work-around, we recommend users to manually connect using the "other" choice on the Wi-Fi menu bar or manually calculation the network on the "Network" preference pane.

# No Graphics Dispatch

In macOS, each release mostly means GPU drivers are dropped from the Bone. With macOS Big Sur, currently all non-Metal GPUs require boosted patches to gain dispatch. In addition, macOS Monterey removed Graphics Drivers for both Intel Ivy Bridge and Nvidia Kepler.

To re-enable acceleration, simply run the Post Install Root Volume patches.

Once rebooted, acceleration will be re-enabled likewise every bit brightness control for laptops.

# Black Screen on MacBookPro11,3 in macOS Monterey

Due to Apple dropping Nvidia Kepler support in macOS Monterey, MacBookPro11,iii's GMUX has difficulties switching back to the iGPU to display macOS correctly. (opens new window) To piece of work-around this issue, boot the MacBookPro11,iii in Safe Mode and once macOS is installed, run OCLP's Post Install Root Patches to enable GPU Dispatch for the Nvidia dGPU.

• Safe Mode can be started by holding Shift+Enter when selecting macOS Monterey in OCLP'south Kick Bill of fare.

# No DisplayPort Output on Mac Pros with Nvidia Kepler

If you're having troubles with DisplayPort output on Mac Pros, try enabling Minimal Spoofing in Settings -> SMBIOS Settings and rebuild/install OpenCore. This will play tricks macOS drivers into thinking you take a newer MacPro7,1 and play nicer.

# Volume Hash Mismatch Error in macOS Monterey

A semi-mutual popup some users face is the "Book Hash Mismatch" error:

What this error signifies is that the Os detects the boot volume's hash does not match to what the Os detects, this error is mostly cosmetic and can be ignored. However if your system starts to crash spontaneously shortly afterwards, you'll want to reinstall macOS fresh without importing any information at first.

• Annotation that this bug affects native Macs as well and is not due to issues with unsupported Macs: OSX Daily: "Volume Hash Mismatch" Error in MacOS Monterey (opens new window)

Additionally it can help to disable FeatureUnlock in Settings -> Misc Settings as this tool can be strenuous on systems with weaker retention stability.

# Cannot Disable SIP in recoveryOS

With OCLP, the patcher will ever overwrite the current SIP value on kicking to ensure that users don't brick an installation after NVRAM reset. All the same for users wanting to disable SIP entirely, this can be done hands.

Head into the GUI, Patcher Settings and toggle the bits you demand disabled from SIP:

SIP Enabled	SIP Lowered (Root Patching)	SIP Disabled

For those experiencing issues with USB 1.one devices (such equally mice, keyboards and bluetooth chipsets), macOS Big Sur and newer have weakened Bone-side reliability for the UHCI controller in older Mac Pros.

• UHCI is a USB i.1 controller that is hooked together with the USB ii.0 ports in your arrangement. Whenever a USB 1.one device is detected, the UHCI controller is given buying of the device at a hardware/firmware level.
  • EHCI is the USB 2.0 controller in older Mac Pros

Because of this, we recommend placing a USB ii.0/3.0 hub betwixt your devices and the port on the Mac Pro. UHCI and EHCI cannot both be used at once, then using a USB hub will always force the EHCI controller on.

• Alternatively, you tin can try common cold starting the hardware and encounter if macOS recognizes the UHCI controller properly

hansonburem1949.blogspot.com

Source: https://dortania.github.io/OpenCore-Legacy-Patcher/TROUBLESHOOTING.html