[pre-release] macOS Monterey

[odemolay]

13 minutes ago, miliuco said:

Me too. It seems to be installing beta 2, rebooting, etc., but at the end I stay in beta 1. Tried 2 times.

same here

 

[Partime]

20 minutes ago, Hervé said:

Straight & easy update with Clover r5133 on my Skylake/HD520 Dell Latitude E7270 laptop.

 

More complicated update with OpenCore v0.7.0 on my Haswell/HD4400 Toshiba Satellite Pro R50-B: initiated the update, rebooted from the temp install partition a 1st time, then a 2nd time. On 3rd boot of that temp partition, laptop went into a boot loop. Booted the original Monterey partition and laptop went through a xx minutes remaining as if finishing off the update but, on reaching the desktop -> Monterey beta1.  

 

Clover still better for me... 

 

I have the same problem, I was never able to complete update to B2 since i don't have clover :O

 

[naiclub]

I think there must be a crash at OC 0.7.1. I have tried reverting to version 0.6.0. It's much better. Show CPU name exactly As it should be (0.7.1 listed as unknown CPU iMac Pro1.1), this could be the main reason for not being able to update.

Edited June 28, 2021 by naiclub

[Anto65]

 

but thanks .... the graphics card is shown again 😆

[ameenjuz]

Anyone have InstallAssistant.pkg link for Monterey beta 2

[iCanaro]

all spun smooth as oil, no problems detected 

[Irish_Man]

6 minutes ago, eSaF said:

Well there we have it, This update has broken my Monterey install by way of at the first reboot where it creates the HD installer volume it goes into an endless series of reboot loops when selected to complete the install. Using the latest OC release also with previous boot args used in the first one makes no difference. Although I can boot into the original install, I now have an extra useless install volume at the boot menu. So I am having all the fun at the fair with this update although I'm at a lost as to what else to try. 

 

It seems like the Clover gang has left us OC boys behind on this one!!! 

Happened to me until I changed SecureBootModel to Disabled

[miliuco]

19 minutes ago, eSaF said:

Well there we have it, This update has broken my Monterey install by way of at the first reboot where it creates the HD installer volume it goes into an endless series of reboot loops when selected to complete the install. Using the latest OC release also with previous boot args used in the first one makes no difference. Although I can boot into the original install, I now have an extra useless install volume at the boot menu. So I am having all the fun at the fair with this update although I'm at a lost as to what else to try. ...

Exactly as you. I've tried OC 0.7.1 and 0.70. 😬 

13 minutes ago, Irish_Man said:

Happened to me until I changed SecureBootModel to Disabled

I'll try and comment.

[mnfesq]

Just now, eSaF said:

Already disabled in BIOS by default. Will have to be patient and wait for the OC Devs to offer up a solution or as @Hervé suggested bite the bullet and dust off my Clover Folder which will be more fun as I left that behind a few versions ago.

 

SecureBootModel is still an OC setting. You might try to set it to disable irrespective of your BIOS settings.

[miliuco]

20 minutes ago, mnfesq said:

 

SecureBootModel is still an OC setting. You might try to set it to disable irrespective of your BIOS settings.

Tried OC 0.7.0 and 0.7.1 with SecureBootModel=Disabled. No luck.

[mnfesq]

For those of you who cannot update to Beta 2 using OC but don't want to abandon OC, you can install Clover 5137 on your EFI partition and select the setting in the Clover installer to use the bootloader chooser.  It installs a BOOTX64.efi file in your BOOT folder and when you boot, you can hold down the space bar and it will give you the option to choose your bootloader, which for me is either Clover or OpenCore.  It shouldn't be that hard to get Clover to work for you since you can use most of your Quirk settings. in OC for the Quirk settings in Clover.

 

Edited June 29, 2021 by mnfesq

[b0ltun]

No issues with updating to Beta 2 with OC 0.7.1 

Couple of reboots and it's done. 

[Djlild7hina]

1 hour ago, Irish_Man said:

Happened to me until I changed SecureBootModel to Disabled

 This worked for me thanks!

[chris1111]

Update easy from DELL Optiplex 790

Also from HP Probook 6570B

Patch HD 4000 after Update  Pefect Shot 

Edited June 29, 2021 by chris1111

[Pavo]

Most the time when people have issues with getting the update to show up is because their APFS seal is broken it they have SIP disabled. The APFS seal should be not broken and SIP should be enabled.

[fusion71au]

Successful and smooth update to beta2 on my Skylake NUC6i5SYH, OC 0.7.0, SIP enabled but SecureBootModel set to disabled in OC config.plist.

 

Just like normal OTA delta update, process finished after 3 reboots...

 

Spoiler

 

Graphics card is now shown in "About This Mac" 😀

 

cc @SavageAUS: Re OpenCanopy icons in the above OpenCore GUI screenshot - these are from @blackosx's GIT repo Set3/Light/HardDrive

Edited July 3, 2021 by fusion71au
Link to OpenCanopy icons added

[Slice]

I see again "Reload this page" in Safari. It was absent in beta 1.

[Guest 5T33Z0]

@naiclub If the csr-active config is not correct, you won't get updates,I guess (just like in Big Sur). Enable SIP temporarily.

[Slice]

4 minutes ago, 5T33Z0 said:

@naiclub If the csr-active config is not correct, you won't get updates,I guess (just like in Big Sur). Enable SIP temporarily.

The keyword "partially".

For update you have to enable SIP partially.

[Guest 5T33Z0]

Updates are working fine here with EF0F0000 

 

 

SIP looks more than just "partially" disabled to me:

Edited June 29, 2021 by 5T33Z0

[Slice]

EF0F00 is not FF0F00

[naiclub]

33 minutes ago, 5T33Z0 said:

@naiclub If the csr-active config is not correct, you won't get updates,I guess (just like in Big Sur). Enable SIP temporarily.

 

28 minutes ago, Slice said:

The keyword "partially".

For update you have to enable SIP partially.

I had this set up before installing, but it didn't work, so I went back to clover

[Matgen84]

10 hours ago, antuneddu said:

Sorry but what's in it, it's not the bootloader that detects updates

 

Few month ago, users noticed that the value assigned to csr-active-config had an influence on the appearance of updates. I don't know if it is the same for Monterey.

[Guest 5T33Z0]

@chris1111 After updating to the lastes beta of Monterey I noticed that you have to Patch HD4000 again oherwise the screen stays at the boot screen, while the system is actually running in the background (I got an email Notification, etc). So I took the disk out, put it in an external case, started macOS Catalina on my Laptop, ran HD4000 Patcher v2 and mounted the Monteray disk. After selecting the Monteray-DISK partition, I get this error:

 

 

Edited June 29, 2021 by 5T33Z0

[hiphopboy]

why i checking the Software update but have no the new beta 2