Jump to content
3390 posts in this topic

Recommended Posts

57 minutes ago, Fordski said:

I had the same thing happen and I changed my config settings for securebootmodel to disabled from default and I was able to download the incremental update to beta 8 successfully.

Can u please to make it more clear This ?

1 hour ago, PropoFlexWX4 said:

20A5364e is Beta 6. If you look at Software Update in System Preferences, you'll find Beta 8 there waiting to be downloaded.

I made a mistake. but I had to do a fish install from a usb which was. the last beta (I thought it was beta 8 I had made.) .

managed to update just to beta 8 but it took along time. got there in the end

1308622012_Screenshot2020-09-22at13_57_59.png.8679d89ae49307ef7118df4d516fe3a7.png

1 hour ago, Fordski said:

I had the same thing happen and I changed my config settings for securebootmodel to disabled from default and I was able to download the incremental update to beta 8 successfully.

The ability to install with securebootmodel disabled was first introduced on Beta 7:

Quote
Resolved in macOS Big Sur 11 beta 7
  • You can now update macOS Big Sur 11 beta 7, if Secure Boot is set to No Security. (63434409)

 

At one of my devices, I found that after I updated to Beta 7, the boot volume wasn't a snapshot anymore, so the installer couldn't update the system. Which is interesting, as I have not removed the snapshot from any of my devices, regardless of being alternative or real Apple hardware. I decided to go clean install route so I cannot check this theory, but as you described, disabling the securebootmodel could also pave a way to bypass the snapshot volume requirement during OS upgrades.

  • Like 3

@eSaF I see that as quite the opposite: had the Acidanthera team not delivered a Secure Boot solution, we would be stuck without the ability to install any beta updates until beta 7. It is amazing they are following Apple that close and we should be very thankful for their efforts.

  • Like 3
28 minutes ago, eSaF said:

@Alex HQuest My discovery also. At first the update only offered a full update which I realised would revert to Beta7 even though I forced it to the choice of Beta 8 (2.34 GB) but a message flashed up saying only the full install was available. So what I did was follow the recommended method of changing SecureBootModel to Disabled, cleaned NVRAM reboot then the incremental update to Beta 8 was made available to download. At this stage I feel the marriage of OC and BS is not quite in harmony as both are still in the development stage so nothing is uniformed or straight forward as yet, not that I am complaining just an observation.

I was just about to perform a full install until I saw your post.

 

Thanks :)

Edited by Blu24
  • Like 2
5 minutes ago, bisdak4920 said:

Make disk Read and Write now works same in Catalina.

i don't understand make disk read&write in catalina it is possible to show big sur partition in catalina without deleting snapshot&sealed

i don't understand make disk read&write in catalina it is possible to show big sur partition in catalina without deleting snapshot&sealed

Yeah some more explanation would be nice.


Sent from my iPhone using Tapatalk

@Pavo know why my SATA Controller shows Generic AHCI Controller in Big Sur

other hand Catalina shows Intel 10 Series Chipset

do you have idea?

Catalina 

Spoiler

image.png.1dfda2beef38aaec578a1db08f9d7f32.png

Big Sur

Spoiler

image.png.1e8a5de5dfd619b0f252e6a0c4f0a475.png

 

Edited by ameenjuz
edited
3 hours ago, Sherlocks said:

anyone who know why not detect update 8 in system preference?

i checked
SIP values
SMBIOS.

i experienced it since BS DP2. so i always have to use crazybirdy script.

Sent from my SM-N960N using Tapatalk
 

I had to enable SIP for Software Update to get Beta8 to download.

  • Like 2
4 hours ago, Sherlocks said:

anyone who know why not detect update 8 in system preference?

i checked
SIP values
SMBIOS.

i experienced it since BS DP2. so i always have to use crazybirdy script.

Sent from my SM-N960N using Tapatalk
 

The update only appeared after clearing my NVRAM.

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