Jump to content

[pre-release] macOS Big Sur

gengik84

By gengik84,
in New Releases and Updates

 Share
3390 posts in this topic

Recommended Posts

Matgen84
Matgen84
Posted
Posted
19 minutes ago, MorenoAv said:

@eSaF, 

You are determined to wind the BS war... I like it, today when I return home I'm erasing my BS thingy and start fresh, because there are some things that I don't like.

For that reason although I solved the "Preboot" issue, the bluetooth... fresh install it is...

 

PS: On a side note, right now I'm at work, and I have a real Mac mini 2018, the update appeared and I installed it but it was only 4,99 GB. after finishing that update appeared the other with 11,98 GB to download. BS is weird even in real Macs... LoL ...

 

@MorenoAv
 

Apple developers says: macOS Big Sur 11 beta 3 is a full app instead of only incremental update image. Maybe that means B1+B2+UpdateBS3=Beta 3 :)
 

Despite of fresh install, I've got the "Preboot" issue on my Aorus Master :cry: it does not matter

  • Like 2
dvil
dvil
Posted
Posted (edited)
31 minutes ago, Matgen84 said:

 

@MorenoAv
 

Apple developers says: macOS Big Sur 11 beta 3 is a full app instead of only incremental update image. Maybe that means B1+B2+UpdateBS3=Beta 3 :)
 

Despite of fresh install, I've got the "Preboot" issue on my Aorus Master :cry: it does not matter

 

 I did a clean install using the Big Sur recovery partition and I also got the Preboot "issue" at the end. However, following the instructions of @fusion71au the "issue" was solved.

 

I didn't copy any file, I  just run csrutil disable, then csrutil authenticated-root disable in the terminal in the BS recovery partition and restarted my computer. After that the Big Sur volume was correctly shown in the OC picker! just like that.

 

I hope it helps,

 

Good luck. 

Edited by dvil
  • Like 1
  • Thanks 1
JahStories
JahStories
Posted
Posted
On 7/23/2020 at 10:29 AM, fusion71au said:

...

For those who want to rename "Preboot" in your OC GUI menu to "Big Sur", extract the text file disk_label.contentDetails into your ~/Downloads folder.

 

Use diskutil to mount Big_Sur's Preboot volume, then copy the file disk_label.contentDetails to /Preboot/UUID/System/Library/CoreServices with the "." prefix eg

sudo mv ~/Downloads/disk_label.contentDetails /System/Volumes/Preboot/UUID/System/Library/CoreServices/.disk_label.contentDetails ...

...

Perfect, I even renamed the drive inside the text file to match my HD (Macintosh HD)

Works as intended, thanks!

JahStories
JahStories
Posted
Posted (edited)
6 hours ago, arsradu said:

Have any of you guys tried the new VP9 decoding feature of Safari in Beta 3? I can't seem to get it to work... I mean, it's enabled in Developer options, it's just not giving me the options for resolutions higher than 1080p in YouTube for example.

I can't set anything higher than 1080p, other resolutions are not showed...

even with VP9 enabled

Edited by JahStories
  • Like 1
dvil
dvil
Posted
Posted
3 minutes ago, eSaF said:

@dvil - Although I did it previously with fusion71au method and was successful, I just tried your method and got - 'This Tool needs to be executed from Recovery OS' - ah well I'll leave it for a while and see what happens or until it does my head in, which ever one happens first. :lol:

 

That's correct, you need to do it from the recovery partition.

 

Cheers,

AlfredoM
AlfredoM
Posted
Posted
On 7/23/2020 at 1:56 PM, arsradu said:

 

The post you quoted above doesn't have anything to do with this message. It was only meant for people who can't see the update in Software Update section.

 

Please, take a look at the known issues here: https://dortania.github.io/OpenCore-Install-Guide/extras/big-sur/#installation

 

"This is actually the part at where macOS will seal the system volume, and where it may seem that macOS has gotten stuck. DO NOT RESTART thinking you're stuck, this will take quite some time to complete."

how can you stop sealing? so that you then have full write permissions?
It was possible with the option "pull plug" at this point, is that still possible and then the sealing is

stopped but the system is then completely installed?

iGPU
iGPU
Posted
Posted
8 hours ago, iGPU said:

 

This looks like a good suggestion!

 

It booted further into Recovery than before, stopping at image below.

 

  Reveal hidden contents

BS-Recovery.thumb.jpg.592cb2e75b92475dfcaa1399acc974cc.jpg

 

 

I finally got into BS Recovery. Besides, leaving ScanPolicy = 0 (as suggested above by AppleBreak),

AppleALC and WEG needed to be enabled (both of which are not normally needed for the VM I'm running).

Matgen84
Matgen84
Posted
Posted (edited)

Hi Guys

 

With OpenCore 0.6.0 (latest), I can't boot to BS3 Recovery Partition despite of Jump settings in my config.plist ?

 

Message error! loadImage failed - Unsupported

 

Any ideas ! Where I made a mistake

  

	<key>UEFI</key>
	<dict>
		<key>APFS</key>
		<dict>
			<key>EnableJumpstart</key>
			<true/>
			<key>HideVerbose</key>
			<true/>
			<key>JumpstartHotPlug</key>
			<true/>
			<key>MinDate</key>
			<integer>0</integer>
			<key>MinVersion</key>
			<integer>0</integer>
		</dict>

 

 

Edited by Matgen84
  • Like 1
AlfredoM
AlfredoM
Posted
Posted
11 hours ago, iGPU said:

I've successfully updated from ß2 to ß3 using the 3970X VM in my signature. However, I have the Preboot label on the boot drive, not BigSur as intended. I'd like to change this, but I cannot seem to get into Recovery to disable csrutil. I had this same problem with ß2 Recovery; I could not boot into Recovery on Big Sur.

 

I can boot into Catalina Recovery just not Big Sur Recovery, so this makes me think that it's a BigSur APFS / OpenCore issue.

 

I tried many things, the first simply being to use the OC v060 that I use to boot into Big Sur (kexts and everything seems to work when booted into Big Sur). If I use this boot EFI, then I get an error saying "OCB: LoadImage failed - Unsupported".  This message then loops back to the OC menu each time the Big Sur Recovery disk is selected. (BTW, EnableJumpstart and JumpstartHotPlug are enabled.)

 

As some have suggested on this thread, I've tried adding apfs.efi or ApfsDriverLoader.efi, but these do not help much. They do show the Apple logo with a progress bar that goes ~5% and stops. When verbose is active, it stops as shown in image below (boot arguments are "-v vsmcgen=1"; oddly it says no kexts are loaded...)

 

I'd appreciate any help. Thanks.

 

  Reveal hidden contents

Failed_Recovery.thumb.jpg.02d51a6ea0d1cf1f6d662c37d939d48c.jpg

 

yes I did it the same way in phase 3, then macOS installer started again from Open Core and the installer does the sealing again. The interruption in phase 3 is of no use.

iGPU
iGPU
Posted
Posted
7 minutes ago, Matgen84 said:

Hi Guys

 

With OpenCore 0.6.0 (latest), I can't boot to BS3 Recovery Partition despite of Jump settings in my config.plist ?

 

Message error! loadImage failed - Unsupported

 

Any ideas ! Where I made a mistake

  


	<key>UEFI</key>
	<dict>
		<key>APFS</key>
		<dict>
			<key>EnableJumpstart</key>
			<true/>
			<key>HideVerbose</key>
			<true/>
			<key>JumpstartHotPlug</key>
			<true/>
			<key>MinDate</key>
			<integer>0</integer>
			<key>MinVersion</key>
			<integer>0</integer>
		</dict>

 

 

 

Look at my post immediately above your post. (You can trace thru my previous posts from yesterday where I had same issue); maybe it will help your set up too.

  • Thanks 1
AlfredoM
AlfredoM
Posted
Posted
1 hour ago, arsradu said:

@MorenoAv yeah, the 5GB one is the incremental update. The 12GB one is the full installer. And the fact that it's showing both seems to be a bug.

I think it's nice that both updates are coming. So you can create a USB Install Stick with the big update.

SavageAUS
SavageAUS
Posted
Posted

I’m leaving the disk name alone (Preboot) and the lack of a big sur option in startup disk so I can see what the next update brings. Should only be a week or so? I’m happy to be a guinea pig

 

 

Sent from my iPhone using Tapatalk

  • Like 2
Matgen84
Matgen84
Posted
Posted
12 minutes ago, iGPU said:

 

Look at my post immediately above your post. (You can trace thru my previous posts from yesterday where I had same issue); maybe it will help your set up too.

 

I can boot on Catalina Recovery without any change in my config.plist :) Despite of that I test ScanPolicy=0 as you says before.

  • Like 1
AlfredoM
AlfredoM
Posted
Posted (edited)
5 minutes ago, Matgen84 said:

 

I can boot on Catalina Recovery without any change in my config.plist :) Despite of that I test ScanPolicy=0 as you says before.

even with scanpolicy = 0 and all correct entries in the config.plist with OC 0.6.0, I cannot get into recovery, the same as was posted here in the pictures.

Edited by AlfredoM
  • Like 1
Max.1974
Max.1974
Posted
Posted
23 hours ago, MorenoAv said:

I have a Preboot too, after one more fresh install, but my biggest problem is not having bluetooth... it appears disabled in Hackintool ... 

 

 

Hi my friend, try use Kext-Dropet by Chris1111 and install in L / E that will works!!! Im could get it install on my both Hacks!! Lenovo and Desktop!! 

But only was needed make this on Lenovo...:) 

  • Like 1
ileikcaek
ileikcaek
Posted
Posted
4 hours ago, SavageAUS said:

For info, this is my startup disk selection.

 

Thank you,

 

I did some checks to compare mine to yours and changed some of my options but it resulted in no boot at all, I will probably go through it all again and only change one or two things at a time and see what happens.

 

I'm not expecting this to help my major issues with updating/installing on bare metal though but we will see.

MorenoAv
MorenoAv
Posted
Posted (edited)

Thanks @Max.1974,

I was able to solve that a while ago... I don't know how but it worked... LoL

 

PS: I'll tell everything but the only thing that I do was made another EFI folder from scratch, complete with fresh kexts, and compile the last commit of OpenCore... nothing more...

Edited by MorenoAv
  • Thanks 1
Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...