<< Solved >> Issues updating OC in order to install macOS Monterey

[jps]

Hey there,

after trying for hours and reading various posts, i'm still clueless on how to solve my problem.

Problem:
Cannot boot 11.6.1 with OC 0.7.4 and all kexts updated.

Rig:
Motherboard: Asus ROG Strix Z390-I
Chipset: Z390
Audiochipset: Realtek ALC1220
LAN-Chipset: Intel I 219V
WLAN & Bluetooth Chipset: Intel Wireless-AC 9560
CPU: Intel i3 8350k (Coffee Lake 8th Generation)
GPU: Intel UHD Graphics 630 (onboard, used for computing tasks) and AMD Sapphire RX 580 (dedicated, used for driving three displays)
SSD: Samsung 970 EVO NVME M.2

What I've tried so far:
- Checked BIOS Settings. Everything is totally fine here.
- Checked config.plist and updated it to the reference plist from OC 0.7.4. Seems fine to me.
- Tried all possible combinations of SetupVirtualMap and RebuildAppleMemoryMap (since a post indicated there was a bug, at least in older version of OC)
- Tried an older version of virtualsmc kext (since a post indicated there could be a problem with the virtualsmc). Didn't work.
- Tried the SecureBootModel set to Default asw ell as to j137. Didn't work.

Everything resulted in the same error you can find attached to this post.
The only thing that resulted in a successful boot was to downgrade OC back to 0.7.2 with all kexts staying at the latest versions. OC 0.7.3 didn't work and resulted in the same error as 0.7.4.

Attachments:
Complete EFI folder as well as logging output from booting.

I hope somebody can help me out because to me this is kind of wizardry right now. Never happened to me before that I couldn't get a OC update to boot.

Thank you so much in advance

 

[Feartech]

Hey there,

after trying for hours and reading various posts, i'm still clueless on how to solve my problem.

Problem:
Cannot boot 11.6.1 with OC 0.7.4 and all kexts updated.

Rig:
Motherboard: Asus ROG Strix Z390-I
Chipset: Z390
Audiochipset: Realtek ALC1220
LAN-Chipset: Intel I 219V
WLAN & Bluetooth Chipset: Intel Wireless-AC 9560
CPU: Intel i3 8350k (Coffee Lake 8th Generation)
GPU: Intel UHD Graphics 630 (onboard, used for computing tasks) and AMD Sapphire RX 580 (dedicated, used for driving three displays)
SSD: Samsung 970 EVO NVME M.2

What I've tried so far:
- Checked BIOS Settings. Everything is totally fine here.
- Checked config.plist and updated it to the reference plist from OC 0.7.4. Seems fine to me.
- Tried all possible combinations of SetupVirtualMap and RebuildAppleMemoryMap (since a post indicated there was a bug, at least in older version of OC)
- Tried an older version of virtualsmc kext (since a post indicated there could be a problem with the virtualsmc). Didn't work.
- Tried the SecureBootModel set to Default asw ell as to j137. Didn't work.

Everything resulted in the same error you can find attached to this post.
The only thing that resulted in a successful boot was to downgrade OC back to 0.7.2 with all kexts staying at the latest versions. OC 0.7.3 didn't work and resulted in the same error as 0.7.4.

Attachments:
Complete EFI folder as well as logging output from booting.

I hope somebody can help me out because to me this is kind of wizardry right now. Never happened to me before that I couldn't get a OC update to boot.

Thank you so much in advance

set these to -1

<key>MinDate</key>
            <integer>0</integer>
            <key>MinVersion</key>
            <integer>0</integer>

 

[jps]

Thanks. Sadly it didn't work. Same result / error.

 

[Feartech]

Thanks. Sadly it didn't work. Same result / error.

boot verbose and take a picture where it hangs

also reset nvram on any config.plist change you make

 

[jps]

The verbose boot shows exactly what the log I attached is showing...
nvram has been reset.

 

[bmoag]

If "upgrading" rather than creating a new EFI with newer versions of OC I have always failed, which is my understanding of what the OP did.
Apologies if I misunderstand the situation.
Creating a new 7.4, to replace existing 7.0, takes much less time than it took to download and install the latest BigSur "security" update.
My new 7.4, using existing identifier numbers and canned everything except the custom USB kext, booted BigSur and after replacing 7.0 upgraded to Monterey sans hiccough. I use ethernet and an old Bluetooth USB dongle which likely simplifies the process.
Not sure what I get out of Monterey other than the challenge of getting there, but that is off-topic.
If the OP created a new 74 the failure suggests to my limited understanding a problematic setting in the configp as there is no need to change any motherboard settings.

 

[spad357]

jps, if you have not resolved your boot issue, I think I found the problem. There was a problem with propertree removing Arguments, Comment, Enabled and Path from each driver in the UEFI/Drivers section. If not done so, you need to update to the latest propertree which has been corrected. See the attached images, yours and my UEFI/drivers section. If you have already resolved your problem, please disregard.

 

[jps]

spad357, that's it! It is finally booting! Thank you so much for this hint

 

[FormerUser-400995]

... you need to update to the latest propertree which has been corrected...

This was overlooked by quite a number of people, judging by the amount of similar complaints I've seen. Keeping a close eye on the differences between OpenCore versions is always a good practice, but ultimately, a successful build often comes down to the tools used (or in this case, keeping them updated and in sync with O.C.).

 

[Rajkhand]

I found this tool for updating Opencore and I have successfully upgraded my OC since 0.7.0

https://github.com/ic005k/QtOpenCoreConfig/releases

For a Guide search google for "Updating and maintaining OpenCore"