[pre-release] macOS Big Sur

[JahStories]

On 7/14/2020 at 6:47 PM, JahStories said:

With iMac 15,1 I can't see anything DRM protected anywhere (VideoProc hevc not supported h264 not supported)

Using iMacPro 1,1 I can see AppleTV and NetFlix on chrome (VideoProc hevc supported h264 supported)

But using safari I just get a red screen and using AppleTV app a green striped screen (audio works on both)

Old movies bought from iTunes when played on the AppleTV app show just a red screen as NetFlix.

I solved on Catalina using these boot-args, sadly shiki is not working on BigSur, let's hope some developer will find a solution...

"shikigva=80 shiki-id=Mac-7BA5B2D9E42DDD94"

I'm already using an iMacPro smbios, but had to add that id too to make it work...

 

Spoiler

 

Edited July 17, 2020 by JahStories

[Pavo]

40 minutes ago, JahStories said:

I solved on Catalina using these boot-args, sadly shiki is not working on BigSur, let's hope some developer will find a solution...

"shikigva=80 shiki-id=Mac-7BA5B2D9E42DDD94"

 

 

Spoiler

 

This is a known issue https://github.com/acidanthera/bugtracker/issues/1034#issuecomment-656701712

[JahStories]

yeap I've read that I know... Hope they find a fix!

[Pavo]

2 minutes ago, eSaF said:

@Pavo - Astonishing, how did you manage to get a screen grab of Apple TV because I tried to do it to show I am using Booting shikigva=80 and nothin else with Mac Model 1.1 pro and can show all my Apple movie collection as well as Apple TV+ or am I missing something here. When I try to get a screen grab using OS X builtin method, it results in a black pic, so basically I am asking what app you used if any.

What screen grab of AppleTV are you referring to? You can not take a screenshot of DRM content, it will result in a black screenshot.

Edited July 17, 2020 by Pavo

[Pavo]

1 minute ago, eSaF said:

In the post 3 above this one with the Apple cartoon. Yea I know about DRM content hence I wondering how you got that pic to illustrate your point.

That wasn't me, that was @JahStories

[opnoise]

2 minutes ago, Pavo said:

What screen grab of AppleTV are you referring to? You can not take a screenshot of DRM content, it will result in a black screenshot.

 

I think it was a photo that was taken and linked by @JahStories of someone's screen with multiple options of DRM working in Catalina (based off of the background pic), not something @Pavo did. 

 

Speaking of, @Pavo, I've seen you mention getting DRM working on a number of your AMD dGPU setups using without WhateverGreen using only ACPI SSDT patches. Is that something that only works on the Radeon VII and Vega cards you have or something that would also work with the Polaris Ellesmere (RX580) card? Have any pointers or guides to link to on how to accomplish that?

[Pavo]

2 minutes ago, opnoise said:

Speaking of, @Pavo, I've seen you mention getting DRM working on a number of your AMD dGPU setups using without WhateverGreen using only ACPI SSDT patches. Is that something that only works on the Radeon VII and Vega cards you have or something that would also work with the Polaris Ellesmere (RX580) card? Have any pointers or guides to link to on how to accomplish that?

Not using any patches, just using a SSDT that makes the dGPU identify as it should in macOS. I have used the same SSDT (with slight modifications to Devices under Scope) for R9 290-x, RX 480/580, Vega 64 and now Radeon VII and they all work as intended. The one thing to remember though, I never had a system that had a iGPU at all, so results may vary.

Here is the SSDT I currently use:

DefinitionBlock ("", "SSDT", 1, "APPLE ", "GFX", 0x00001000)
{
    External (_SB_.PCI0.SE0_, DeviceObj)

    Scope (_SB.PCI0.SE0)
    {
        Device (GFX0)
        {
            Name (_ADR, Zero)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "hda-gfx", 
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                })
            }
        }

        Device (HDAU)
        {
            Name (_ADR, One)  // _ADR: Address
            Method (_DSM, 4, NotSerialized)  // _DSM: Device-Specific Method
            {
                Return (Package (0x02)
                {
                    "hda-gfx", 
                    Buffer (0x0A)
                    {
                        "onboard-1"
                    }
                })
            }
        }
    }
}

 

[Ludox]

The new clover bootloader (5120) with big sur support has been released

 

[JahStories]

1 hour ago, Pavo said:

...

Here is the SSDT I currently use:

...

I tried using this SSDT on BS (with adaptation for my HW) but it does not solve my DRM issues...

 

About the image I posted, is not a screenshot it's a picture took with my phone xD

Edited July 17, 2020 by JahStories

[Max.1974]

On 7/11/2020 at 9:06 PM, fusion71au said:

 

 

Thanks @fusion71au works like a charm your tutorial !!! 

[Ludox]

Clover r5120 disables the lan and the audio and how it did not load the kexts AppleALC.kext and IntelMausiEthernet.kext, hp had to reset 5119 to have all activated again, how come?

 

[Max.1974]

27 minutes ago, ludox said:

Clover r5120 disables the lan and the audio and how it did not load the kexts AppleALC.kext and IntelMausiEthernet.kext, hp had to reset 5119 to have all activated again, how come?

 

 

Im have no idea...hahahaha its a crazy Horse now...mess around and all charm from Hack...but im will prefer Clover and if is possible AVOID OC----- -r

Edited July 17, 2020 by Max.1974

[fusion71au]

On 7/17/2020 at 11:32 AM, ameenjuz said:

i have already deleted snapshot using usb installer but i still can't mount the Big Sur Volume in Catalina

Remember i have installed Big Sur and Catalina in one drive

i have updated catalina to 10.15.6 

still problem persist Incompatible Disk issue

 

On 7/17/2020 at 9:39 PM, ricoc90 said:

Yep I've read about it however it didn't work for me since I'd always get a "operation not permitted" error on running apfs_systemsnapshot (SIP and ARV both disabled).

My workaround was to boot stage 3 of the installer in verbose mode. Once it reached this line:

I restarted my system and booted from the BS volume instead. No sealing, no snapshot booting.

 

@ASentientBot posted an excellent summary of Volume Sealing and APFS snapshots @MacRumors forum post#807. 

 

It looks like @ameenjuz's problem is that his Big_Sur volume is sealed, and there is no way to unseal it once already sealed, short of reinstalling again and interrupting phase3 installation (like @ricoc90) or using a patched installer in the first place (based on @ASentientBot's hax2 or hax3.dylib).

 

Re Volume Sealing:

"This is the means by which the boot volume is cryptographically signed and modifications are detected. It also seems to be the reason why BS system volumes cannot be mounted under Catalina or older (specifically due to the APFS_INCOMPAT_SEALED_VOLUME flag, see here). My latest installer hack turns off sealing (but not snapshots, which is why it failed to fix error 66 for most people). There doesn't seem to be any way to fully unseal a volume once it's been sealed: snapshots and verification can be turned off, but it will never mount on an older OS since that flag is still present. So the install-time disabling seems like a must."

 

My guide on deleting APFS snapshots will only solve the "error 66" problem when trying to mount your / as read/write eg when installing/replacing kexts in /S/L/E.  Hope this clarifies things now .

 

Extra info:  @ResEdit_ResEdit edited "/macOS Install Data/UpdateOptions.plist" file (booted into macOS on separate drive after phase1 reboot) to prevent volume sealing occurring later on during phase3...

 

Spoiler

 

As reported by @AppleBreak and confirmed by @ameenjuz, the "UpdateOptions.plist method" to prevent sealing of the Big_Sur volume has the unfortunate side-effect of later preventing the deletion of APFS snapshots from Recovery/Installer USB, throwing out "Operation not permitted" and "Insufficient privileges" errors.  Therefore recommend interrupting of phase3 installation method or using @ASentientBot's hax2/hax3 patched installer to prevent volume sealing and allowing access to Big_Sur volume from older macOS...

Spoiler

 

Edited July 21, 2020 by fusion71au
Extra Info

[jsl2000]

20 hours ago, ludox said:

The new clover bootloader (5120) with big sur support has been released

 

This new version can boot Big Sur, Catalina, & 10.14.x without any issue except I need add apfs.efi in addition to ApfsDriverLoader.efi in my Z77 hackintosh. There's one bug I found. It can recognize one of APFS partitions (10.15.x or 10.16 beta) only to boot. OpenCore 0.6.0 can recognize both and select one of them to boot.

Edited July 18, 2020 by jsl2000

[gengik84]

3 hours ago, fusion71au said:

Extra info:  @ResEdit_ResEdit edited "/macOS Install Data/UpdateOptions.plist" file (booted into macOS on separate drive after phase1 reboot) to prevent volume sealing occurring later on during phase3...

Or...

Eg: if you don't have separate drive for modify UpdateOption.plist
After first phase, boot installer again, open terminal and write

/usr/libexec/PlistBuddy -c "Set DoNotSeal true" /volumes/bigsur/"macos install data"/UpdateOptions.plist 

reboot

 

note: change /volumes/bigsur with your /volumes/disk_name

[Ludox]

1 ora fa, jsl2000 ha detto:

Questa nuova versione può avviare Big Sur, Catalina e 10.14.x senza alcun problema, tranne per il fatto che ho bisogno di aggiungere apfs.efi oltre a ApfsDriverLoader.efi nel mio hackintosh Z77.

You can share your EFI clover to compare with mine, because I have network and audio card activation problems when I start with the new clover bootloader

[manmo71]

I created a bootable macOS Catalina 10.15.6 USB drive with the latest Clover 5120.

 

I have 3 m.2 drives on my MOBO, and I use both OC and Clover (trying to get it installed). I am running it with the following specs

• Drive 1 - OC 0.6 Big Sur
• Drive 2 - Trying to install macOS Catalina 10.15.6 with Clover
• Drive 3 - OC 0.6 Catalina 10.15.6

The OC versions are both functional and working fine. I am unable to get the USB drive to boot successfully and install Catalina 10.15.6 onto Drive 2.

In the past I was using just clover for the past couple of years with a working configuration and had the config.plist configured just fine.

I accidentally deleted the only backup copy of my Clover EFI, Now I am again struggling to get the system back the way it used to be with Clover.

I am running iGPU headless and DGPU RX580. I am not sure what I am doing wrong, can some one help me out here with the clover version?

 

I have attached my EFI folder if someone can take a look at it...EFI.zip

 

[PC IT]

Hi to all here, i am still trying thousands of times to boot Bigsur from internal ssd, it just boot from usb external ssd and it is slow, and cannot show the internal ssd disk , i have the usb properly mapped, , bios updated, and i dont know what is preventing the boot, is this the problem woth all, or just in my system , all kekst and oc bootloader are the latest new , waiting any reply or help thanks   

[Matgen84]

3 hours ago, manmo71 said:

I created a bootable macOS Catalina 10.15.6 USB drive with the latest Clover 5120.

I have attached my EFI folder if someone can take a look at it...EFI.zip

 

 

Be patient    Slice has removed the last release r5120 not working
 

 

[Riley Freeman]

Every boot I get a "Your computer restarted because of an error" dialog. Even though I can't find any trace of a panic. I've deleted the apfs snapshots so it's not baked into one of those. Does anyone have any idea how to solve this? There's still a few flaky bits in Beta 2 for me but this is the main annoyance for me right now. Hoping the next one smooths things out a bit.

 

[Cyberdevs]

@d5aqoep and @MICKHAEL

This topic is for Vanilla installation only your posts will be moved to 

 

[mnfesq]

4 hours ago, PC IT said:

Hi to all here, i am still trying thousands of times to boot Bigsur from internal ssd, it just boot from usb external ssd and it is slow, and cannot show the internal ssd disk , i have the usb properly mapped, , bios updated, and i dont know what is preventing the boot, is this the problem woth all, or just in my system , all kekst and oc bootloader are the latest new , waiting any reply or help thanks   

 

I'm still having the same problem as well.  It's not just you.

[Max.1974]

 

Hi @fusion71au one more time im thankful for you help us... my question is about hax2 or hax3. How install this for usb installer? Just run it "Build.tool"? Thanks again!!! 

 

12 hours ago, fusion71au said:

 

 

It looks like @ameenjuz's problem is that his Big_Sur volume is sealed, and there is no way to unseal it once already sealed, short of reinstalling again and interrupting phase3 installation (like @ricoc90) or using a patched installer in the first place (based on @ASentientBot's hax2 or hax3.dylib).

 

 

 

  Reveal hidden contents

 

 

 

Edited July 18, 2020 by Max.1974

[Guest ricoc90]

1 minute ago, Max.1974 said:

How install this for usb installer? Just run it "Build.tool"? Thanks again!!! 

Use parrotgeek's script:
https://parrotgeek.com/bigsur/

[Max.1974]

2 minutes ago, ricoc90 said:

Use parrotgeek's script:
https://parrotgeek.com/bigsur/

 

Thanks @ricoc90!!! 

Edited July 18, 2020 by Max.1974