Big Sur to Monterey Error

[ugrbnk]

On 7/14/2021 at 7:49 AM, Shinji3rd said:

Ok, I have some news.

After several days testing different things and cleaning my EFI, I FINALLY FOUND THE SOLUTION! It was all about the quirks. Even if it all worked great in Big Sur, for some reason I needed to activate a couple more quirks to be able to upgrade to Monterey.

If anyone else has this problem, with that MSU 1130 error or something like that, this is what I did. I don't know if all of this is required, but hey, it's what I did, it solved the issue, and as Monterey is now installed and perfectly working I can't test if some steps are not required, so here's the list of things I did:

- Deleted the APPLE folder inside my EFI folder.

- Enable "AllowRelocationBlock", "ProtectMemoryRegions" and "SyncRuntimePermissions" in the Booter section of my plist. Leave all the other quirks exactly as I had them.

- Misc -> Security, I set SecureBootModel to Disabled.

- Reboot the system, and in the picker I chose Clear NVRAM. System reboots.

- Boot Big Sur. No issues booting. Run the Monterey update again. This time, I had the feeling that it took a little longer than before.

- System reboots, and the update process begin. Everything went smooth, and after some time, Monterey loaded and everything works: wi-fi, bluetooth, graphics acceleration, sound...

So, if you are experiencing this error or something similar, compare the quirks you have and if you are missing the ones I mention, give it a try. Just take this in consideration:

- If you are using a Broadcom Wi-Fi/BT module, you have to disable BrcmBluetoothInjector and enable the new BlueToolFixup.

- CpuTscSync is not working in Monterey (yet), so you have to replace it with TSCAdjustReset.

- If you want an EFI folder valid for Big Sur and Monterey without the need to manually activate / de-activate kexts, just set the MaxKernel to 20.9.9 in those kexts that should not be injected in Monterey, and the MinKernel to 21.0.0 to those that are exclusive to Monterey and up. That way OpenCore will inject ones or the others depending on if you are booting Big Sur (or older) or Monterey.

The update problem is solved. Thank you

[mr buffy]

On 7/14/2021 at 11:49 AM, Shinji3rd said:

Ok, I have some news.

After several days testing different things and cleaning my EFI, I FINALLY FOUND THE SOLUTION! It was all about the quirks. Even if it all worked great in Big Sur, for some reason I needed to activate a couple more quirks to be able to upgrade to Monterey.

If anyone else has this problem, with that MSU 1130 error or something like that, this is what I did. I don't know if all of this is required, but hey, it's what I did, it solved the issue, and as Monterey is now installed and perfectly working I can't test if some steps are not required, so here's the list of things I did:

- Deleted the APPLE folder inside my EFI folder.

- Enable "AllowRelocationBlock", "ProtectMemoryRegions" and "SyncRuntimePermissions" in the Booter section of my plist. Leave all the other quirks exactly as I had them.

- Misc -> Security, I set SecureBootModel to Disabled.

- Reboot the system, and in the picker I chose Clear NVRAM. System reboots.

- Boot Big Sur. No issues booting. Run the Monterey update again. This time, I had the feeling that it took a little longer than before.

- System reboots, and the update process begin. Everything went smooth, and after some time, Monterey loaded and everything works: wi-fi, bluetooth, graphics acceleration, sound...

So, if you are experiencing this error or something similar, compare the quirks you have and if you are missing the ones I mention, give it a try. Just take this in consideration:

- If you are using a Broadcom Wi-Fi/BT module, you have to disable BrcmBluetoothInjector and enable the new BlueToolFixup.

- CpuTscSync is not working in Monterey (yet), so you have to replace it with TSCAdjustReset.

- If you want an EFI folder valid for Big Sur and Monterey without the need to manually activate / de-activate kexts, just set the MaxKernel to 20.9.9 in those kexts that should not be injected in Monterey, and the MinKernel to 21.0.0 to those that are exclusive to Monterey and up. That way OpenCore will inject ones or the others depending on if you are booting Big Sur (or older) or Monterey.

I was having this issue installing Monterey beta as an update or fresh install. Modifying the 3 parameters in the Booter section fixed it.

Thanks for the tip!