Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

RPatel19

macrumors newbie
Original poster
Apr 22, 2025
5
0
Hi All, I am new to Mac and purchased a Mac Pro 5.1 which had Sonoma installed on it along with Windows 10, I've been using it for the past 6 months now updated the OC when the pop-up comes up with no issues, but the latest update which I believe was 2.20, it won't boot into Windows and every time I try and boot into Sonoma I get the following message:

#[EB.LD.LF|IN] 0 1 <"NULL STRING>"> <"1">
#[EB.B.SBS|SZ] 723512
#[EB|B:SHA] <7c6b81afef3db6a4df77bb929480dfb853177bba>
#[EB.WL.PWLFNV|! Err(0xE) <- RT.GV wake failure 7C436110-AB2A-4BBB-A880-FE41995C9F82
#[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLFNV
#[EB.WL.PWLFRTC|NONE]
#[EB.WL.DT|!] Err(0xE) <- EB.WL.PWLRTC
#[EB.LD.LKC|D] <"boot\System\Library\KernalCollectIONs\BootKernalExtensions.kc.developement">
#[EB.LD.OFS|OPEN!] Err(0xE) <"boot\\System\\Library\\KernalCollectIONs\\BootKernalExtensions.kc.developement">
#[EB.LD.LKC|R.2] <"boot\System\Library\KernalCollectIONs\BootKernalExtensions.kc.developement">
OC: Plist Kexts\USB1.1-Injector.kext\Contents\PlugIns\AppleUSBUHCI.kext\Contents\Info.plist is missing for injected kext USB1.1-Injector.kext\Contents/PlugIns\AppleUSBUHCI.kext (USB1.1 - AppleUSBUHCI)
Halting on critical error

I have been at this since Friday and searched on the internet for possible solutions, but none seem to work.

I have even tried creating a Sonoma boot USB with the OpenCore-Patcher.pkg using my iMac 27 inch running Catalina, but I just can't get past the above, HELP please.
 
I have also tried installing Sonoma on a fresh SSD, to try and recover the failed one, as it has apps, documents and settings that I want to keep, I can get to the boot screen showing the install USB Drive, but again halts on the critical error above.

I have tried putting the SSD into an enclosure and plugged into my iMac but it doesn't seem to get recognise, yet when placed back in the Mac Pro attempts to boot from it.
 
Basics:
  • What GPU do you have installed? You can't switch GPU if using OpenCore as patches GPU specific.
  • If you updated the OpenCore-Patcher application, did you Build and Install OpenCore to the EFI on Sonoma boot drive?
  • Hold down Option key while booting. This macOS Boot Picker. Pick EFI Boot. This put you in OpenCore Boot Picker. Pick your Sonoma boot drive.
  • Did you Post-Install Root Patches?
 
Basics:
  • What GPU do you have installed? You can't switch GPU if using OpenCore as patches GPU specific.
  • If you updated the OpenCore-Patcher application, did you Build and Install OpenCore to the EFI on Sonoma boot drive?
  • Hold down Option key while booting. This macOS Boot Picker. Pick EFI Boot. This put you in OpenCore Boot Picker. Pick your Sonoma boot drive.
  • Did you Post-Install Root Patches?
  1. AMD RX580 GPU 8GB
  2. On previous OC updates I have done this, and again on this latest update
  3. Holding down the Option key while booting, does bring me the option to boot either to my Windows, Sonoma or install macOS Sonoma, but when I select either Sonoma or the install macOS Sonoma I keep getting the halt on critical error
  4. I was not able to do the Post-Install Root Patches
I would have thought that I would be able to remove the original Sonoma boot disk and put in a fresh new one and install Sonoma again, but does not get past the error above.

Trying to boot to my Windows just results in a hung system and I have to force power off.

I can't even get into recovery mode to attempt the Post-Install Root Patch.

Holding the Option key while powering up, I think brings me to the padlock screen and it then requests a password, I have tried all the passwords the I know but can't get past this either.
 
Holding the Option key while powering up, I think brings me to the padlock screen and it then requests a password, I have tried all the passwords the I know but can't get past this either.
Appears firmware password is set. You need to enter firmware password to boot into Recovery or another disk other than the original boot disk. If you did not set firmware password, your options are extremely limited.
 
ok I have attached an apple monitor to my system now and I can now see the following before the rest of the error message appears:

LNX: AutodetectingLinux not root fs - Not Found
APFSStart:1589: Mounting with apfs_efi_osx-2317.61.2
efi_fusion_paring:672: Container 0c79ef17-79a3-4ada-bd0a-b6b6291da9bb
efi_fusion_paring:677: fusion uuid: 00000000-0000-0000-0000-000000000000
efi_container_create:1189: -efi_container_create, Status = 8000000000000003
apfs.efi: LocateProtocol(AppleLogging) succeeded
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.