[pre-release] macOS Big Sur

[iGPU]

9 minutes ago, mnfesq said:

 

It looks like your KP is being caused by the apfs.efi file you have in OC.  It is conflicting with the apfs.efi file in the prelinked kernel.

 

I didn't necessarily want to use, but tried this approach. If I don't use, and just use the regular EFI for booting into BigSur, then I get the "OCB: LoadImage failed - Unsupported" error that loops back to menu system.

[Andrey1970]

16 minutes ago, iGPU said:

 

I didn't necessarily want to use, but tried this approach. If I don't use, and just use the regular EFI for booting into BigSur, then I get the "OCB: LoadImage failed - Unsupported" error that loops back to menu system.

JumpstartHotPlug=Yes

[luky35]

6 hours ago, fusion71au said:

 

Already answered here.  Once Big_Sur volume sealed after installation, AFAIK, you can't unseal it.

 

If you want to easily access your Big_Sur volume from older macOS, you have to prevent sealing before it happens in the first place eg use @ASentientBot's hax2 to patch the Installer.  I don't recommend the "UpdateOptions.plist method" since this seems to interfere with deleting APFS snapshots later on.

 

 

 

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

 

The UUID is unique to your own system and is actually the UUID of your Big_Sur — Data⁩ volume.  Easiest way to find out the UUID value is to list the contents of Preboot - from terminal (after mounting the Preboot volume with sudo diskutil mount diskXsY), type...

 

ls -l /System/Volumes/Preboot 

Also can see in Finder...

  Reveal hidden contents

 

Not OK, (Operation not permitted)

Edited July 24, 2020 by luky35

[iGPU]

1 hour ago, Andrey1970 said:

JumpstartHotPlug=Yes

 

Thanks, but I've already set this to 'Yes' (as mentioned in original post here).

 

With APFS/HideVerbose disabled, I see the following:

Spoiler

 

Edited July 24, 2020 by iGPU
added apfs verbose image

[AppleBreak]

31 minutes ago, iGPU said:

 

Thanks, but I've already set this to 'Yes' (as mentioned in original post here).

Set your ScanPolicy to 0 then try.

[arsradu]

6 hours ago, eSaF said:

Guys have a look in System Preferences/Startup Disk and see if the Big Sur disk is there. I am dual booting with Windows and only that disk is showing. To make BS show I have to mount all the volumes on the BS disk, I am wondering if it is a bug or just my machine.

  Hide contents

Above image after mounting all BS volumes.

 

Yeah, same here. And I wasn't paying attention to it with previous betas, but yeah, I think that might be a bug.

 

Also, interestingly enough, now I can boot into Recovery without the apfs.efi file. Just with JumpstartHotplug set to Yes. Not sure what changed, but I'm glad it works now.

 

Edit: sorry, my bad. It does show up if you mount it. But for some reason now it shows the currently booted system and the Bootcamp partition but not the other partition with Big Sur on it (which is still mounted). :)) Is it limited to two disks in the UI? :))

Edited July 24, 2020 by arsradu

[HBP]

Beta 3 updated with open core ver listed earlier on this thread just fine.

 

hbp

[iGPU]

20 minutes ago, AppleBreak said:

Set your ScanPolicy to 0 then try.

 

This looks like a good suggestion!

 

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

 

Spoiler

 

[luky35]

14 hours ago, fusion71au said:

 

Already answered here.  Once Big_Sur volume sealed after installation, AFAIK, you can't unseal it.

 

If you want to easily access your Big_Sur volume from older macOS, you have to prevent sealing before it happens in the first place eg use @ASentientBot's hax2 to patch the Installer.  I don't recommend the "UpdateOptions.plist method" since this seems to interfere with deleting APFS snapshots later on.

 

 

 

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

 

The UUID is unique to your own system and is actually the UUID of your Big_Sur — Data⁩ volume.  Easiest way to find out the UUID value is to list the contents of Preboot - from terminal (after mounting the Preboot volume with sudo diskutil mount diskXsY), type...

 

ls -l /System/Volumes/Preboot 

Also can see in Finder...

  Reveal hidden contents

 

Disable authenticated root SIP by setting csr-active-config to 77080000 in OC's config.plist, then reset NVRAM through the OC boot menu.  Alternatively, with blank csr-active-config setting, boot to Recovery/Big Sur Installer and run csrutil disable, then csrutil authenticated-root disable in terminal.

 

Added to config.plist number 77080000 and Preboot changed to macOS Big Sur.

Many thanks fusion71au

Edited July 24, 2020 by luky35

[Takiller]

@chris1111do you have a new USB wifi installer for beta 3, as the beta 2 one is failing to install in beta 3?

[pico joe]

I get sleep problem in beta3, wake after sleep return to booting

 

in beta1&2 no problem

[OrpheusInHell]

Anyone succeeded to create a bootable USB with AMD that actually works ?

[arsradu]

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.

 

Such as this video: 

 

Edited July 24, 2020 by arsradu

[ileikcaek]

The same issues as B1 to B2 plague me again when trying to get from B2 to B3. I ran the update command in CLI and it says the update can't be installed because I'm not snapshot booted. I've made attempts to fix this by deleting snapshots and creating/linking a new one but it still doesn't boot to a snapshot.

 

This all could be a side effect of my install originally being done in a VM, my coffee lake laptop still has issues installing on bare metal with VirtualSMC or FakeSMC, the initial write never completes (obviously) as it goes to reboot too soon, then stage 2 wont run because data is missing.

[polyzargone]

10 minutes ago, ileikcaek said:

The same issues as B1 to B2 plague me again when trying to get from B2 to B3. I ran the update command in CLI and it says the update can't be installed because I'm not snapshot booted.

 

I eventually fixed it by enabling SIP with 00000000 on my Dell E7470 but I can't do that on my Z170-P rig as I suspect my NVRAM is not working properly. Actually, it works fine while booting with Clover (System Integrity Protection status: enabled) but not with OpenCore (System Integrity Protection status: unknown (Custom Configuration). I've cleared/reseted NVRAM many times. Also tried to use Emulated NVRAM as per Dortonia's guide without any success (nvram.plist not created).

 

But even with SIP fully enabled with Clover, the error persists

[SavageAUS]

2 hours ago, ileikcaek said:

The same issues as B1 to B2 plague me again when trying to get from B2 to B3. I ran the update command in CLI and it says the update can't be installed because I'm not snapshot booted. I've made attempts to fix this by deleting snapshots and creating/linking a new one but it still doesn't boot to a snapshot.
 
This all could be a side effect of my install originally being done in a VM, my coffee lake laptop still has issues installing on bare metal with VirtualSMC or FakeSMC, the initial write never completes (obviously) as it goes to reboot too soon, then stage 2 wont run because data is missing.

My coffee lake laptop i7-9750H works great with Catalina and Big Sur. I’ll update this post with my EFI folder folder soon.


Sent from my iPhone using Tapatalk

Edited July 24, 2020 by SavageAUS

[arsradu]

@eSaF I actually noticed the same issue on my MBP initially. Didn't pay much attention to it with previous Betas, but now that you mentioned it, then this looks more and more like a bug with Beta 3.

 

As for the wishful thinking...personally, I like to think positive. Cause I believe, when we do that, positive things happen. Call ma naive, if you want. I don't care. I've seen it working way too many times before to know it can't be a coincidence. I also don't believe in coincidences. Cause that would mean that I also believe in random. And I don't think that anything that's happening with us, to us, is random, or can be random. I think we just don't know the reason for it...yet.  So..., to answer your question, no, I wouldn't be surprised if it actually was pretty much smooth sailing going forward.

 

I still couldn't figure out how to fix the "preboot" issue, but it doesn't really bother me that much, especially since I know it's also an issue on real Macs. Yeah, I have tried enabling/disabling SIP...but no change on my side.

Anyway, as I said, I don't really mind it that much. :)) Hopefully next betas will fix this one, too.

[ileikcaek]

14 minutes ago, SavageAUS said:

My coffee lake laptop i7-9750H works great with Catalina and Big Sur. I’ll update this post with my EFI folder folder soon.


Sent from my iPhone using Tapatalk

 

i7 9750H is 'refresh' coffee lake I think and I believe chipsets are the same, I have i5 8300H. Still it's quite odd the issues I've been having with updating or installing bare metal but it working fine if the install is done via a VM, but then it doesn't appear to ever snapshot boot and only live boots the disk so updating isn't possible. If I attempt to install via the 12.88GB Beta 3 installer it begins counting down the minutes but at 12 minutes remaining it jumps to restart, but the MacOS install partition it creates does not boot because the previous data write obviously failed.

 

I have seen some others have had similar issues around Beta 2 release, but I never found a solution and ended up just installing beta 2 to my SSD using vmware. I knew for sure I'd have issues at Beta 3 again though.

[SavageAUS]

For info, this is my startup disk selection.

@ileikcaek

Attached is the exact EFI folder i am using on my laptop to boot Big Sur, Catalina, Windows and Arch Linux

 

Spoiler

 

EFI.zip

Edited July 24, 2020 by SavageAUS

[SavageAUS]

2 minutes ago, eSaF said:

@SavageAUS - Ok you've convinced me - I am gonna do a Recovery and see if I can get the Disk to show in the Start Up section and if need be a full re-install, I got time on my hands for 'Crappery' today. 

My Big Sur disk does not show up though.

[SavageAUS]

1 minute ago, eSaF said:

Yea but you do have the choice to pick which disk to restart from whether it is BS or another if you're Dual-Booting? Because the pic you posted I can see BS, in mine I only see Windows unless I manually Mount the BS volume then it shows in the Start Up Disk section.

I must be going blind as i cant see my Big Sur disk. Only Windows 10 and Catalina.

Spoiler

 

[SavageAUS]

2 minutes ago, eSaF said:

@SavageAUS - Aha so it is not just me then on my machine and yet Chris1111 and a few others don't have the problem/glitch. It is killing me right now (Oh why do I let small $hit like this bother me so much ).

Im trying to set my csr active config to 77080000 but propertree won't load on Beta 3 even with python installed.

How would i enter 77080000 into xcode for my config.plist?

[FredWst]

20 hours ago, mick3lson said:

I'm trying to update to beta3 on hp4540s but at first reboot,  stuck on: apfs_module_start:2411

 

was in the same case.

adding vsmcgen=1 in boot-args solved the trouble for me. (Mac mini 8,1)

Edit : same for my iMac15,1.

 

Fred

 

Edited July 24, 2020 by FredWst

[Takiller]

You see now this beta 3 is just refusing both my AR5B95 Wifi card and the TP Link 725n usb Wifi, no matter what I try. They are both working with the previous two betas. I wonder what they did, but I will keep on trying till I get at least one of them working 

[MorenoAv]

@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 ...

Edited July 24, 2020 by MorenoAv