DarkNeptune0 Posted June 25, 2020 Share Posted June 25, 2020 1 minute ago, mnfesq said: Yup, it sounds like the way to get this installed is to download a cryptographically signed APFS snapshot of an installation made on.a real Mac. So having the system installed, opencore can inject the kext like in any other version of Mac OS? Link to comment Share on other sites More sharing options...
mnfesq Posted June 25, 2020 Share Posted June 25, 2020 5 minutes ago, DarkNeptune0 said: So having the system installed, opencore can inject the kext like in any other version of Mac OS? That's what people are reporting that have built their installation on a real Mac with an external USB drive . Link to comment Share on other sites More sharing options...
DarkNeptune0 Posted June 25, 2020 Share Posted June 25, 2020 On 6/25/2020 at 6:44 PM, dariuxzy said: @DarkNeptune0the error is this ... I also put my EFI, which works perfectly with Catalina but with Big Sur I have this problem (I'm on OC) My main EFI (opencore 0.5.8) that contains all the SSDT, kext etc.. gives me the error of the next capture. The one I attached above is version 0.6.0 with several different settings and it's the one that manages to go further. Maybe you could try to remove some kext or settings and leave the essential. Spoiler Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 25, 2020 Share Posted June 25, 2020 7 minutes ago, mnfesq said: That's what people are reporting that have built their installation on a real Mac with an external USB drive . But that's just because OC hasn't been updated to support booting Big Sur's installer right? After 0.6.0 (or another future version) gets officially released, we'll be able to upgrade or clean install as normal, correct? Link to comment Share on other sites More sharing options...
tore2003 Posted June 25, 2020 Share Posted June 25, 2020 21 minutes ago, mnfesq said: Yup, it sounds like the way to get this installed is to download a cryptographically signed APFS snapshot of an installation made on.a real Mac. What do you mean? Link to comment Share on other sites More sharing options...
mnfesq Posted June 25, 2020 Share Posted June 25, 2020 1 hour ago, ricoc90 said: I guess the biggest issue will be this: Internal changes The most significant structural change inside Big Sur is that the boot System volume isn’t protected by SIP any more, but is a cryptographically signed APFS snapshot. You can’t just disable SIP and mount the System volume for writing, and there’s no way to boot a live System volume which you can write to. Instead, if you need to make changes to the contents of the macOS System volume, you’ll need to disable its authentication in Recovery Mode, mount it, make any changes, create an APFS snapshot, then use that to boot from. Step-by-step instructions for doing this will no doubt emerge in coming days. https://eclecticlight.co/2020/06/24/big-sur-and-apple-silicon-interesting-times-ahead/ This really explains why, for now, we are at a dead end with Clover and OpenCore. Neither can inject any kext into a snapshot. Without kext injection or the ability to write to S/L/E or L/E, we are stuck until someone can figure out how to add FakeSMC or VirtualSMC and other necessary startup kexts to a snapshot that can be used by the Big Sur installer. 2 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 25, 2020 Share Posted June 25, 2020 30 minutes ago, mnfesq said: This really explains why, for now, we are at a dead end with Clover and OpenCore. Neither can inject any kext into a snapshot. Without kext injection or the ability to write to S/L/E or L/E, we are stuck until someone can figure out how to add FakeSMC or VirtualSMC and other necessary startup kexts to a snapshot that can be used by the Big Sur installer. I am sure it is just a matter of time until both Clover and OpenCore developers find a solution to this. Kudos for those guys' efforts. Link to comment Share on other sites More sharing options...
tore2003 Posted June 25, 2020 Share Posted June 25, 2020 2 minutes ago, PropoFlexWX4 said: I am sure it is just a matter of time until both Clover and OpenCore developers find a solution to this. Kudos for those guys' efforts. I’m sure about that too. Clover or OpenCore are gonna find a solution, but we don’t know how much time could it take to share a final version of a bootloader for Big Sur. 1 Link to comment Share on other sites More sharing options...
PropoFlexWX4 Posted June 25, 2020 Share Posted June 25, 2020 3 minutes ago, tore2003 said: I’m sure about that too. Clover or OpenCore are gonna find a solution, but we don’t know how much time could it take to share a final version of a bootloader for Big Sur. It doesn't matter how long it takes for now, as we are still several months away from macOS 11's official release (General Availability). But I suspect we'll get updated boot loaders soon. 1 Link to comment Share on other sites More sharing options...
luki1979 Posted June 25, 2020 Share Posted June 25, 2020 1 hour ago, manmo71 said: Try this modified EFI, if it works...EFI.zip I have just cleaned up your EFI and made small changes, may not be perfect but give it a try... Thank you, still the same. It doesn’t see USB drive at all. I only got Internal drive and Clean Nvram entries in the boot selection. Weird. I’ll look more into it tomorrow. Link to comment Share on other sites More sharing options...
Shaneee Posted June 25, 2020 Share Posted June 25, 2020 Long live AMD Hackintoshing Installed directly to HDD via VBox spoofing as an Intel CPU. Few patches updated using OC 0.6.0 Spoiler 7 1 Link to comment Share on other sites More sharing options...
YukiPowa Posted June 25, 2020 Share Posted June 25, 2020 6 minutes ago, Shaneee said: Long live AMD Hackintoshing Installed directly to HDD via VBox spoofing as an Intel CPU. Few patches updated using OC 0.6.0 You have boot on installer and install is okey ? How please Link to comment Share on other sites More sharing options...
Shaneee Posted June 26, 2020 Share Posted June 26, 2020 Just now, YukiPowa said: You have boot on installer and install is okey ? How please Installer was via VBox without any patches. (CPU Spoofed) Installed system is bare metal with updated patches. Experimental patches will be shared on the AMD OS X github soon but no support will be given for Beta versions of macOS. 1 Link to comment Share on other sites More sharing options...
YukiPowa Posted June 26, 2020 Share Posted June 26, 2020 1 minute ago, Shaneee said: Installer was via VBox without any patches. (CPU Spoofed) Installed system is bare metal with updated patches. Experimental patches will be shared on the AMD OS X github soon but no support will be given for Beta versions of macOS. Okey I have install okay, but My wifi card not work BCM94360CS2 IntelMausi not work Link to comment Share on other sites More sharing options...
Max.1974 Posted June 26, 2020 Share Posted June 26, 2020 On 6/25/2020 at 6:48 PM, YukiPowa said: I have download dmg of other pepole and I dd to my partition ahah Opencore https://monokeith.top/?page_id=11 Im almost get install, but that installer usb get loop from install and nothing change...but thanks anyway!!! Thanks a lot!!! Spoiler Link to comment Share on other sites More sharing options...
tore2003 Posted June 26, 2020 Share Posted June 26, 2020 Clover is working for a new version https://github.com/CloverHackyColor/CloverBootloader/commit/1856b519e5f1fda3ca2d1a018a19119e50dd5ff0 5 Link to comment Share on other sites More sharing options...
monokeith Posted June 26, 2020 Share Posted June 26, 2020 On 6/26/2020 at 4:41 AM, Max.1974 said: Im almost get install, but that installer usb get loop from install and nothing change...but thanks anyway!!! Thanks a lot!!! I had the same issue before, it was caused by the 2 booter-fileset items in NVRAM section of the config file. simply remove those items and clear NVRAM should solve it. 1 Link to comment Share on other sites More sharing options...
Max.1974 Posted June 26, 2020 Share Posted June 26, 2020 Clover is so good, sorry said, but im not like OC, so much brain is needed to make works this "thing" from H*LL kkkk 3 Link to comment Share on other sites More sharing options...
MattsCreative Posted June 26, 2020 Share Posted June 26, 2020 can someone build that clover please Link to comment Share on other sites More sharing options...
Max.1974 Posted June 26, 2020 Share Posted June 26, 2020 19 minutes ago, monokeith said: I had the same issue before, it was caused by the 2 booter-fileset items in NVRAM section of the config file. simply remove those items and clear NVRAM should solve it. Please you can explain how do this, im completely stupid with OC... Link to comment Share on other sites More sharing options...
asapreta Posted June 26, 2020 Share Posted June 26, 2020 2 minutes ago, MattsCreative said: can someone build that clover please The commit is from two days ago. Probably it is under heavy testing. 1 1 Link to comment Share on other sites More sharing options...
MattsCreative Posted June 26, 2020 Share Posted June 26, 2020 Just now, asapreta said: The commit is from two days ago. Probably it is under heavy testing. thats great be nice to test it our selfs now also to report bugs Link to comment Share on other sites More sharing options...
Max.1974 Posted June 26, 2020 Share Posted June 26, 2020 We need delete this 2 lines? Thanks im will try... Spoiler Link to comment Share on other sites More sharing options...
MacHackA Posted June 26, 2020 Share Posted June 26, 2020 Is there anyway to fix this issue in Opencore version 0.6.0 i've tried -lilubetaall and avoidruntimedefrag Spoiler Link to comment Share on other sites More sharing options...
kankon Posted June 26, 2020 Share Posted June 26, 2020 hello someone can help me! am using clover with Catalina 10.15.5 someone can convert it to OpenCore ? my file Link to comment Share on other sites More sharing options...
Recommended Posts