Jump to content

[pre-release] macOS Big Sur


3,698 posts in this topic

Recommended Posts

Just now, BALDY_MAN said:

ok I've seen that. and just changed it ti 67000000. in a back up efi just going to try it now. thank you all for your quick reply

 

If it doesn't work with 67000000 which indicates SIP is partially Disabled, try my example 00000000 which indicates SIP is totally Enabled, some systems will not allow the update with SIP Disabled. Good luck.

Link to comment
Share on other sites

I’m happy to report that I updated to beta 10 with no issues and didn’t need the full install. In my build every new update since beta 6 has been installed smoothly. 
 

GA-Z97-HD3 dGPU AMD Gigabyte RX-580, i5 4790k, 16GB RAM, Broadcom Wifi & BT Combo card 4331 half mini PCIe

  • Like 1
Link to comment
Share on other sites

1 hour ago, eSaF said:

What a journey!!!! - I tried Three times to update to this latest Beta and each time I was offered a full install and each time it would be the same Beta I am already running. The cure to over come this, I changed Security/SecureBootModel from Default to Disabled and only then I was offered the update at 3.82 GB.

  Reveal hidden contents

1209865140_Screenshot2020-10-14at21_35_26.png.e9efaddfc737a87212baf3d90912bf63.png

 

@eSaf

 

Same here. Thanks for the tip !

  • Like 1
Link to comment
Share on other sites

finished. the beta 10 update, with (secureboot set to disable )

 

now can't boot into os, OCB: StartImage failed - Aborted.

(securboot set to default now.) open core beta from today.

 

please help! 

 

Link to comment
Share on other sites

3 hours ago, HBP said:

because of server issues with Apple, and due to discrepancies in the install of beta 9 some of us are being forced to install the full os again.  I am in the same boat. downloading the full install after doing updates from 8 to 9 then trying to update to beta 10.

 

HBP

Even having upgraded from 12gb again prompted me to download 12gb continuously
I solved the problem by starting Big Sur with Opencore 6.2, perhaps with the clover on this aspect there is a problem ..

Schermata 2020-10-15 alle 01.29.12.png

  • Sad 2
Link to comment
Share on other sites

1. the main problem if Snapshots Sealed: Broken so there is no OTA Update

 

 Volume disk5s5 9796CEE4-6435-4893-8EC4-9D114EF9984F
        ---------------------------------------------------
        APFS Volume Disk (Role):   disk5s5 (System)
        Name:                      BigSur (Case-insensitive)
        Mount Point:               /private/tmp/msu-target-LahGPIpX
        Capacity Consumed:         15002284032 B (15.0 GB)
        Sealed:                    Broken
        FileVault:                 No
        |
        Snapshot:                  57F4DA5D-08D6-4762-BE29-28A7FA4078C5
        Snapshot Disk:             disk5s5s1
        Snapshot Mount Point:      /
        Snapshot Sealed:           Yes

 

with this configuration you can get OTA Update

 

Snapshot Sealed Broken cause we tocuh /S/L/E or /L/E

 

2. AFAIK Clover not yet implemented secureboot (cmiiw)

Edited by pico joe
Link to comment
Share on other sites

2 hours ago, markpenn said:

finished. the beta 10 update, with (secureboot set to disable )

 

now can't boot into os, OCB: StartImage failed - Aborted.

(securboot set to default now.) open core beta from today.

 

please help! 

 

 

I was having this error. I just cleaned the NVRAM and I didn't have that anymore

Link to comment
Share on other sites

Hi @fusion71au I set value 67000000  in nvram but get different result with yours

 

pico@picos-iMac ~ % nvram csr-active-config
csr-active-config    %e7%03%00%00
pico@picos-iMac ~ % csrutil status
System Integrity Protection status: unknown (Custom Configuration).

Configuration:
    Apple Internal: disabled
    Kext Signing: disabled
    Filesystem Protections: disabled
    Debugging Restrictions: disabled
    DTrace Restrictions: disabled
    NVRAM Protections: disabled
    BaseSystem Verification: disabled

This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

 

 

Link to comment
Share on other sites

@pico joe,

 

With OC, you need to Reset NVRAM through the OC picker before the csr-active-config value set in your config.plist takes hold...

Spoiler

2125875846_OCResetNVRAM.thumb.png.dade9f3207a455ddc9c86cd808fae519.png

 

Another option to change the nvram csr-active-config value is to boot to macOS using a Clover USB boot stick with config.plist/RtVariables/CsrActiveConfig=0x67.  Unlike OC, Clover changes the nvram value immediately without needing a NVRAM reset...

 

Spoiler

2028587304_CloverCsrActiveConfig.png.945e2417840cecbd9c13a3d88f0d6cd7.png

 

 

 

47 minutes ago, Matgen84 said:

Idem here on my Z390 Aorus Master :(

Is your config.plist/Misc/Security/SecureBootModel set to disabled?  What is your SIP/csr-active-config setting?  Are you booting off the original sealed APFS snapshot?

 

20 minutes ago, Matgen84 said:


I use Clover with csr-active-config = 0x67. The original sealed APFS snapshot exists.

Try the delta OTA update again using OC 0.6.2.  @ludox reported the same problem with Clover r5124, solved after changing back to OC.

Edited by fusion71au
  • Like 2
Link to comment
Share on other sites

Oh Okay .. it’s just clarify as I remember I enabled SIP in recovery csrutil enable and with 670000 in nvram, but after OTA update Beta 10 the value change automatically if I check via terminal

 

btw thanks

Oh Okay .. it’s just clarify as I remember I enabled SIP in recovery csrutil enable and with 670000 in nvram, but after OTA update Beta 10 the value change automatically if I check via terminal

 

btw thanks

Link to comment
Share on other sites

57 minutes ago, fusion71au said:

 

Is your config.plist/Misc/Security/SecureBootModel set to disabled?  What is your SIP/csr-active-config setting?   Are you booting off the original sealed APFS snapshot?


I use Clover with csr-active-config = 0x67. The original sealed APFS snapshot exists.

EDIT: csr-active-config=0x0 (enable) via Clover GUI, same issue: software updater show Full macOS instead of Update. Now I try with OC.

Edited by Matgen84
Link to comment
Share on other sites

@WizeMan - Hi few things to try, run 'Fist Aid' in 'Disk Utility' on all the BS volumes, reboot and clean NVRAM and see if the update shows up, if it doesn't you may need to run the 'Developers Beta Access' program again. Good luck.

Edited by eSaF
  • Like 3
Link to comment
Share on other sites

Solution since had the same problem to upgrade from 9 to 10
Since clover was unable to download the 4gb 10 and returned me to 12gb here's what I did:


1-I temporarily booted with Opencore 6.2 with all upgrading kexts on a USB stick
2- 4gb detection in normal download
3-After the first reboot, restart with the Clover 5124 until the update installation is complete.
4- Starting with normal Clover 5124 BG beta 10, all perfectly working.
 
  • Like 2
  • Thanks 1
Link to comment
Share on other sites

16 minutes ago, ludox said:
1-I temporarily booted with Opencore 6.2 with all upgrading kexts on a USB stick
2- 4gb detection in normal download

On OpenCore I still get that I'm up-to-date, and with DeveloperBetaUtility I got 12 GB update instead of 4.

csr-active-config: 67000000, SecureBootModel=Disabled, Reseted NVRAM

Edited by kushwavez
Link to comment
Share on other sites

13 hours ago, eSaF said:

What a journey!!!! - I tried Three times to update to this latest Beta and each time I was offered a full install and each time it would be the same Beta I am already running. The cure to over come this, I changed Security/SecureBootModel from Default to Disabled and only then I was offered the update at 3.82 GB.

  Reveal hidden contents

1209865140_Screenshot2020-10-14at21_35_26.png.e9efaddfc737a87212baf3d90912bf63.png

 

Thats why since Beta 7 I disable S..... boot model :angel_not:

433862548_ScreenShot2020-10-15at5_48_31AM.png.adb7f7184731e6c932698d9742e6b011.png

 

HP ProBook 6570b DONE ⬇︎

Spoiler

screen58.png.13a0d9943f3605ecd68b8c73fd1fa68e.png

 

Edited by chris1111
HP ProBook 6570b DONE
  • Thanks 1
  • Haha 1
Link to comment
Share on other sites

Crazy how we have to bend our selves and our systems into pretzels to get these latest Beta updates, as far as OC has immensely progressed with this new OS X version and the way it is constructed, we still have a journey ahead of us to fully say all is well judging by how we are still struggling. :(

  • Like 3
Link to comment
Share on other sites

14 minutes ago, kushwavez said:

Thanks so I changed to that, reset NVRAM but still no updates and with Utility I've got 12 GB.  

use done this config .. remove or insert what you need for your hardware configuration and test .. and let me know opencore 6.2
 

config.plist.zip

14 minutes ago, kushwavez said:

 

Link to comment
Share on other sites

2 minutes ago, corint1 said:

I don't believe you ... I've tried dozens, maybe hundreds of times and the clover failed to boot...

Hi - Please don't use such a negative response directed at members trying to help others, remember what doesn't work for you may work for others, all our systems are different. If you tried a method and it didn't work for you then try to find another.

  • Like 3
Link to comment
Share on other sites

Guest
This topic is now closed to further replies.
×
×
  • Create New...