macOS Monterey Patches Released

The official OC 0.7.2 has landed.
 
  • Like
Reactions: elixir
hi everyone, I'm new to this and to your forum....so I edit the config file and I am still getting the same kernel panic as tuliodomingos I enable the ProvideCurrentCpuInfo quirk and I am still getting the panic....is there anything I'm missing?
 
hi everyone, I'm new to this and to your forum....so I edit the config file and I am still getting the same kernel panic as tuliodomingos I enable the ProvideCurrentCpuInfo quirk and I am still getting the panic....is there anything I'm missing?

Did you edit the core count patch to match your CPU?
 
Did you edit the core count patch to match your CPU?
yes......
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>Base</key>
<string>_cpuid_set_info</string>
<key>Comment</key>
<string>algrey - Force cpuid_cores_per_package 10.13,10.14</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>wegaAAAA</data>
<key>Identifier</key>
<string>kernel</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data>//3/AAAA</data>
<key>MaxKernel</key>
<string>18.99.99</string>
<key>MinKernel</key>
<string>17.0.0</string>
<key>Replace</key>
<data>B8080000 0000</data>
<key>ReplaceMask</key>
<data>//////8A</data>
<key>Skip</key>
<integer>0</integer>
 
Updated to OC 0.7.2 and installed new patches in my config.plist, Installed 12.0 Beta 4 with no issues! Everything seems to be working fine so far.

 
Olá a todos, sou novo nisso e em seu fórum ... então edito o arquivo de configuração e ainda estou recebendo o mesmo kernel panic que [USER = 175] tuliodomingos [/ USER] Eu habilito a peculiaridade ProvideCurrentCpuInfo e eu ainda estou tendo pânico ... há algo que estou perdendo?
Diversos -> Segurança -> SecureBootModelser desabilitada na configuração. ???
 
yes......
<dict>
<key>Arch</key>
<string>x86_64</string>
<key>Base</key>
<string>_cpuid_set_info</string>
<key>Comment</key>
<string>algrey - Force cpuid_cores_per_package 10.13,10.14</string>
<key>Count</key>
<integer>1</integer>
<key>Enabled</key>
<true/>
<key>Find</key>
<data>wegaAAAA</data>
<key>Identifier</key>
<string>kernel</string>
<key>Limit</key>
<integer>0</integer>
<key>Mask</key>
<data>//3/AAAA</data>
<key>MaxKernel</key>
<string>18.99.99</string>
<key>MinKernel</key>
<string>17.0.0</string>
<key>Replace</key>
<data>B8080000 0000</data>
<key>ReplaceMask</key>
<data>//////8A</data>
<key>Skip</key>
<integer>0</integer>

You've got a mixture of base64 and hex there... To match the rest of the patch there the Replace value would be uAgAAAAA
 

As a MSI motherboard user, I can confirm that on Beta 3 and 4, the installer can't recognize the NVME drive (stuck at NVME assert failed).
Success on Beta 2, but no luck on Beta 3 and 4.
Hi, here to report that after I reverted my MSI X570 ACE BIOS version to E7C35AMS.150, the error went away and successfully installed beta 4 on the NVME drive.

 
Dortania Install Guide has now been updated to reflect the patch changes :)
 
Last edited:
Diversos -> Segurança -> SecureBootModelser desabilitada na configuração. ???
I followed your video and everything installed, I'm now running beta 4.....thank you
 
Last edited:
  • Like
Reactions: tuliodomingos
So who is going to try Monterey Beta 5 (21A5304g) first? 🙂
 
Screenshot 2021-08-11 at 22.02.17.png
The new Patches are holding up nicely.
Introducing Monterey Beta 5 :)
 
I wish there was a fix for SmallTree kext :(
 
I wish there was a fix for SmallTree kext :(

Give it some more time, possibly when Monterey is out of beta the kext may be worked on.


Sent from my iPhone using Tapatalk
 
  • Like
Reactions: Seyven
Any other reports on Beta 5 before I update?


Sent from my iPhone using Tapatalk
 
  • Haha
Reactions: AudioGod
Hi guys,

I'm recently droped my Gigabyte B450m DS3H and it was working flawlessly from Big Sur to Monterey Beta 5 with the new patches.. But now on my new board, MSI B550m Mortar Wifi, i'm facing seriously difficulties... I simply cannot install Monterey on the latest stable Bios version. And I have alrealdy tried everything. Like someone described here before, it points some NVME error.

While scrambling the OC settings to find some solution I somehow messed up my EFI and now I cannot even install BigSur.. It enters recovery starts to install and suddenly reboots. =/

If someone find the solution, please share with us.. For now i gave up trying..
 
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.