MP 1,1-5,1 MP 5,1 won't finish Monterey installation

[Rochlin]

HELP needed,

My CMP 4,1 => 5,1 has had an NVME boot drive for the past few years and it was running great, I added OC to a small ssd in slot 1 and was able to install Big Sur successfully.
After updating to Monterey (quite easily ) my bluetooth stoped working and all hell broke loose.

I originally installed Monterey on the small ssd that has OC on it, and used that to install it to the NVME. (same way I did with Catalina and Big Sur), it worked fine.

While trying to resolve the Bluetooth I did the CMD+Option+R+P 5 times and at first it wouldn't boot at all. I removed all the drives and was able to boot to the small SSD, and then added back the NVME and it worked, but bluetooth still didn't work. I tried a lot of the solutions suggested in the forums, at least the ones the didn't require an understanding of code or kexts, but nothing worked.

I decided to reinstall the OS and now its not finishing the installation. When it reboots after the first part it starts loading the progress bar and all of a sudden it dies and reboots, then it defaults to the other drive, every time I select the NVME in the OC boot selector it does the same thing, I have now tried installing it like 7 times, also tried on another SATA drive that I have connected to to another PCI and its the same.
I also noticed that the Firmware changed by it self to 9144.0.7.9.1.

Getting very frustrated, any advice would be greatly appreciated !!

Thank you

 

[sfalatko]

HELP needed,

My CMP 4,1 => 5,1 has had an NVME boot drive for the past few years and it was running great, I added OC to a small ssd in slot 1 and was able to install Big Sur successfully.
After updating to Monterey (quite easily ) my bluetooth stoped working and all hell broke loose.

I originally installed Monterey on the small ssd that has OC on it, and used that to install it to the NVME. (same way I did with Catalina and Big Sur), it worked fine.

While trying to resolve the Bluetooth I did the CMD+Option+R+P 5 times and at first it wouldn't boot at all. I removed all the drives and was able to boot to the small SSD, and then added back the NVME and it worked, but bluetooth still didn't work. I tried a lot of the solutions suggested in the forums, at least the ones the didn't require an understanding of code or kexts, but nothing worked.

I decided to reinstall the OS and now its not finishing the installation. When it reboots after the first part it starts loading the progress bar and all of a sudden it dies and reboots, then it defaults to the other drive, every time I select the NVME in the OC boot selector it does the same thing, I have now tried installing it like 7 times, also tried on another SATA drive that I have connected to to another PCI and its the same.
I also noticed that the Firmware changed by it self to 9144.0.7.9.1.

Getting very frustrated, any advice would be greatly appreciated !!

Thank you

The firmware version is due to booting with OpenCore. I think it comes from Martin Lo's package.

Some things to check - do you have more than one instance of OpenCore installed? I could not tell from your narrative but it seems like you might. Do you still have the ability to boot without OpenCore (a Mojave install)? If so I would delete your current OpenCore install(s) and reinstall and rebless.

 

[Rochlin]

The firmware version is due to booting with OpenCore. I think it comes from Martin Lo's package.

Some things to check - do you have more than one instance of OpenCore installed? I could not tell from your narrative but it seems like you might. Do you still have the ability to boot without OpenCore (a Mojave install)? If so I would delete your current OpenCore install(s) and reinstall and rebless.

Thank you Sir!! I was able to get Mojave installed on my NVME, which was huge!
now I'm trying to upgrade it to Monterey and its saying I need a firmware update, I'm running 144.0.0.0, I think that the most recent for the 5,1

 

[tsialex]

Incorrect FIRMWARE FEATURES on your OC config:

OpenCore on the Mac Pro

No. This is explained on the first post of this thread, read "Complete your setup / Spoofing and enabling missing features". You have to edit at least SMBIOS, or PlatformNVRAM and SMBIOS, to something like the example below: PlatformNVRAM BID...

forums.macrumors.com

 

[Rochlin]

Incorrect FIRMWARE FEATURES on your OC config:

OpenCore on the Mac Pro

No. This is explained on the first post of this thread, read "Complete your setup / Spoofing and enabling missing features". You have to edit at least SMBIOS, or PlatformNVRAM and SMBIOS, to something like the example below: PlatformNVRAM BID...

forums.macrumors.com

Thank you, tsialex ill look into it and see if I can navigate that

 

[Rochlin]

Incorrect FIRMWARE FEATURES on your OC config:

https://forums.macrumors.com/threads/opencore-on-the-mac-pro.2207814/post-30926525[/URL

THANK YOU!! That worked, I have M...any ideas on why the Bluetooth isn't working?

 

[tsialex]

THANK YOU!! That worked, I have M...any ideas on why the Bluetooth isn't working?

If you didn't upgrade your original BT module, you will have to root patch at each update to regain BT support since Apple removed support for it. Use the search and learn what you have to do. Personally, I have a extreme dislike of this approach and I did the upgrade on each one of my Mac Pros long ago just to not have to root patch at each minor software update - Apple is doing continuous/rolling software updates and some months they issued three software updates.

If you already upgraded to a BCM94360CD or BCM94362CDP AirPortExtreme and the BT is not working, you could have a corrupt NVRAM volume.

 

[Rochlin]

If you didn't upgrade your original BT module, you will have to root patch at each update to regain BT support since Apple removed support for it. Use the search and learn what you have to do. Personally, I have a extreme dislike of this approach and I did the upgrade on each one of my Mac Pros long ago just to not have to root patch at each minor software update - Apple is doing continuous/rolling software updates and some months they issued three software updates.

If you already upgraded to a BCM94360CD or BCM94362CDP AirPortExtreme and the BT is not working, you could have a corrupt NVRAM volume.

I did upgrade to a BCM943602CDP a couple of years back, is that not compatible anymore?

 

[tsialex]

Both BCM94360CD and BCM943602CDP are still supported with Monterey, but BCM943602CDP is prone to cause bluetoothActiveControllerInfo/bluetoothInternalControllerInfo variable multiplication inside the main VSS store of the NVRAM and when you already have problems, can lead to BootROM corruption/bricking of the Mac Pro.

 

[Rochlin]

Both BCM94360CD and BCM943602CDP are still supported with Monterey, but BCM943602CDP is prone to cause bluetoothActiveControllerInfo variable multiplication inside the main VSS store of the NVRAM and when you already have problems, can lead to BootROM corruption/bricking of the Mac Pro.

OK, ill pull it out immediately, how do I check if the NVRAM is corrupt? and how do I fix it?

 

[tsialex]

OK, ill pull it out immediately, how do I check if the NVRAM is corrupt?

MP5,1: BootROM thread | 144.0.0.0.0

How to check the health of the NVRAM/if the garbage collection is still working: There is a extremely simple way (simple here as in not need to know how the NVRAM works/check free space indicators/validate checksums and etc) to check if the garbage collection failed and the need to reflash with...

forums.macrumors.com

and how do I fix it?

If you already have issues with the NVRAM, you will need a BootROM reconstruction service. I'll send a PM with instructions/cost.

 

[Rochlin]

MP5,1: BootROM thread | 144.0.0.0.0

How to check the health of the NVRAM/if the garbage collection is still working: There is a extremely simple way (simple here as in not need to know how the NVRAM works/check free space indicators/validate checksums and etc) to check if the garbage collection failed and the need to reflash with...

forums.macrumors.com

If you already have issues with the NVRAM, you will need a BootROM reconstruction service. I'll send a PM with instructions/cost.

OK will check! Thank you so much!!