[pre-release] macOS Big Sur

[ameenjuz]

Just now, pico joe said:

 @fusion71au methods .. still working at beta3

i know to deleting snapshot to working on beta 3

but i m asking only about seal

is it possibla to disable sealing after installation?

i mean only sealing

[polyzargone]

Anyone with this error when trying to update from B2 to B3?

 

 

Quote

polyzargone@SkyBook-Pro ~ % sudo softwareupdate --verbose -ida
Password:
Software Update Tool

Finding available software
2020-07-23 18:09:29.969 softwareupdate[1522:52306] Creating client/daemon connection: 78713804-3BEA-4711-BAAF-D02C8572B8DF
Downloading macOS Big Sur Beta 3
downloading: 100.00%
Failed to download & prepare update: Error Domain=SUMacControllerError Code=7722 "[SUMacControllerErrorPreflightPrerequisiteCheckFailed=7722] Failed to perform PreflightPrerequisite operation: com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6) | The volume can not be used because it is not snapshot booted.
-> Current device configuration requires an alternate installer to perform the update.: [com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6)|Unknown Error Indication|]" UserInfo={SUMacControllerErrorIndicationsSummary=|Unknown Error Indication|, SUMacControllerErrorIndicationsMask=8, SUMacControllerErrorIndicationsDescription=-> Current device configuration requires an alternate installer to perform the update., NSUnderlyingError=0x7ffe805098f0 {Error Domain=com.apple.MobileSoftwareUpdate.preflight.error Code=6 "The volume can not be used because it is not snapshot booted." UserInfo={NSLocalizedDescription=The volume can not be used because it is not snapshot booted., NSLocalizedFailureReason=The volume can not be used because it is not snapshot booted., MSUPreflightAlternateInstallerRecommended=true}}, NSDebugDescription=[SUMacControllerErrorPreflightPrerequisiteCheckFailed=7722] Failed to perform PreflightPrerequisite operation: com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6) | The volume can not be used because it is not snapshot booted.
-> Current device configuration requires an alternate installer to perform the update.: [com.apple.MobileSoftwareUpdate.preflight.error(Preflight):MSUPreflightErrorTargetIsNotSnapshotBooted(6)|Unknown Error Indication|], NSLocalizedDescription=Current device configuration and target is invalid for install in the current state. Please try again.}

 

It happens on my Dell E7470 and Asus Z170-P (both booted with modded Clover r5119 or OC 0.6).

[Bios-PC]

Can’t pass stage 3 , after install and reboot first time it work to the second stage , also go fine , in the third stage it’s reboot all time  .

 

anyone has this issue also?

[luky35]

Please, what am I doing wrong, that I can't rename Preboot to MacOS Big Sur?

Spoiler

 

Edited July 23, 2020 by luky35

[mnfesq]

In Beta 3, Safari is virtually unusable for me and disabling all extensions didn't help.

[jlrycm]

5 hours ago, 123Mike said:

Thank you, when your ready.

 

Hello @123Mike. Attached is my EFI except for the Resources folder that is excluded to keep the zip file within limits.

7-23-2020 Big Sur beta 3 copy.zip

[norton287]

1 hour ago, MICKHAEL said:

hi. well, in both case I have VoodooI2C as my laptop have a I2C-HID devices. the only deference its first one had a old version (thats working well on Catalina)
but, I'm unable to boot installer. Big Sur beta3
YES, same issues, no kext injection. but I also tried with compiled 2 day ago, Clover, that booted installer, Big Sur beta 2

I'm having the same issue with clover, no kexts are loading and the finally errors displayed are about loading the NVME drivers.  Attached is my efi file if anyone sees anything out of the ordinary.  I was able to install beta 2 no problem and boot into Big Sur after some help with a NVRAM command.

 

John

EFI.zip

[Partime]

2 hours ago, eSaF said:

@fusion71au Thanks - With your help I achieved what I wanted and got rid of the 'Preboot' disk name and it is now labelled 'Big Sur'. Again thank you Sir. 

Only add...you can copy his file, even edit and change the name of the disk. No need to mount the partition here...for some reason I can see the entire directory.

[Matgen84]

37 minutes ago, luky35 said:

Please, what am I doing wrong, that I can't rename Preboot to MacOS Big Sur?

  Reveal hidden contents

 

 

 

 

Just my opinion: do you try to type only UUID instead of your own UUID  I don't test yet on my Z390 config.

[luky35]

6 minutes ago, Matgen84 said:

 

Just my opinion: do you try to type only UUID instead of your own UUID  I don't test yet on my Z390 config.

Tried only UUID, not OK.

[JahStories]

Everything smooth on my dell, updated from the App like a Mac! just four reboots!

 

 

[AppleBreak]

Thanks to @fusion71au's fantastic guide, The Intel Power Gadget is now working properly on my machine and I was able to modify CPU name without deleting the Snapshots.

 

Spoiler

 

For those of you who don't already know, the easiest way I know so far to modify CPU name in "About This Mac" without deleting the snapshots is to mount your Big Sur system-volume to your desktop, navigate to Processors.strings from the Finder and edit the file from there as you will have full read/write access this way.  After that, use @fusion71au's guide to create a Snapshot.

 

To mount system volume on Desktop. (X and Y is to be replaced with your Big Sur volume's disk identifier)

sudo mkdir ~/Desktop/Test && sudo mount -t apfs /dev/diskXsY ~/Desktop/Test

 

One more thing I'd like to mention is that, if you have not deleted your previous snapshots, you can retag them for your next boot, if necessary. (This is to be done in Recovery)

 

Mount as read/write, find the name of your Snapshots,  and tag one of your working snapshots for the next boot.

mount -uw /Volumes/Big_Sur
diskutil apfs listsnapshots /Volumes/Big_Sur
/System/Library/Filesystems/apfs.fs/Contents/Resources/apfs_systemsnapshot -r "Name of your Snapshot" -v /Volumes/Big_Sur
Reboot

 

 

 

 

 

 

 

Edited July 23, 2020 by AppleBreak

[fusion71au]

12 hours ago, ameenjuz said:

i know to deleting snapshot to working on beta 3

but i m asking only about seal

is it possibla to disable sealing after installation?

i mean only sealing

 

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.

 

 

12 hours ago, luky35 said:

Please, what am I doing wrong, that I can't rename Preboot to MacOS Big Sur?

 

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

Spoiler

 

32 minutes ago, luky35 said:

Not OK, (Operation not permitted)

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.

 

Edited July 24, 2020 by fusion71au
disable SIP if operation not permitted

[Riley Freeman]

Had to download the full 12GB installer as the delta wouldn't work with APFS snapshots deleted.

 

Beta 3 is much better here. The app crashes and hangs I had with Beta 2 are gone and the menubar is nice and snappy.

[MorenoAv]

Well after some time, a redone EFI done from scratch now I have Bluetooth ...  

The only thing that isn't solved is the annoying message "this pc can't read the disk connected" ... at boot ...

[MorenoAv]

Now I mounted it in disk utility, and it mounted ... I hope that solves it...

Thanks for the tip...

[MorenoAv]

Anyone knows why suddenly Propertree stoped working with BG beta 3 ... today I tried to edit the last config.plist and it crashes...

[iCanaro]

use python 385?

https://www.python.org/downloads/

[Irish_Man]

No hiccups during the update from Beta 2 to Beta 3. Big Sur appears as Preboot in OC boot menu.

 

 

The only "issue" I have is that if I remove "vsmcgen=1" arg I get stuck on this error: 

 

 

After I add "vsmcgen=1" I can boot normally. OC and kexts all updated to the latest versions. 

 

EFI-Haswell.zip

 

[123Mike]

6 hours ago, jlrycm said:

Hello @123Mike. Attached is my EFI except for the Resources folder that is excluded to keep the zip file within limits.

7-23-2020 Big Sur beta 3 copy.zip

Hello   Thank you kindly, I will give this a burl. This is what makes this community what it is.
Michael

[chris1111]

1 hour 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.

  Reveal hidden contents

Above image after mounting all BS volumes.

for my part it does not show me all the disks, because I have two Big Sur and it shows me my other system and same thing when I try on the other system

Spoiler

 

[mnfesq]

No problem getting Startup Disk to detect all of my installations.

Spoiler

 

[ameenjuz]

intrrupting installation on phase 3 do not work on beta 3 to avoid snapshot sealing

anyone tried this trick?

i tried this but no luck

[iGPU]

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.

 

Spoiler

 

Edited July 24, 2020 by iGPU

[mnfesq]

23 minutes 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. 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.

 

  Hide contents

 

 

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.