Robbish's 8yr old ATX IvyBridge Hackintosh GA-Z77-DS3H - i5-3570K - HD 4000 [OpenCore/macOS Big Sur]

[MilkyTech]

the guide here uses opencore

Are you reading anything I am writing? "I want to just do a fresh install of Big Sur with OpenCore"

I am attempting to get a working USB installer of Big Sur with OpenCore! Post #106 Clearly shows that I am following this guide using Opencore. BayCityRoller, with the same exact specs as me, used this guide with Robbish's EFI and was able to install Big Sur. For some unknown reason, my installer is not working as shown in post 106. Please help with this issue. If I can't get the USB installer to boot with Opencore, then there is no reason to attempt to change my current Catalina install to Opencore just to attemp a directr upgrade from there. I've already attempted to directly upgrade from Catalina using clover and It won't work. I don't actually need any apps or files from Catalina so I am fine with a fresh install of Big Sur with Opencore. I actually have an unused HDD that I want to attemp the install on first before i overwrite my Catalina installation. To do this, I need the USB installer to boot!

 

[Feartech]

Are you reading anything I am writing? "I want to just do a fresh install of Big Sur with OpenCore"

I am attempting to get a working USB installer of Big Sur with OpenCore! Post #106 Clearly shows that I am following this guide using Opencore. BayCityRoller, with the same exact specs as me, used this guide with Robbish's EFI and was able to install Big Sur. For some unknown reason, my installer is not working as shown in post 106. Please help with this issue. If I can't get the USB installer to boot with Opencore, then there is no reason to attempt to change my current Catalina install to Opencore just to attemp a directr upgrade from there. I've already attempted to directly upgrade from Catalina using clover and It won't work. I don't actually need any apps or files from Catalina so I am fine with a fresh install of Big Sur with Opencore. I actually have an unused HDD that I want to attemp the install on first before i overwrite my Catalina installation. To do this, I need the USB installer to boot!

you still need the USBPorts.kext (a properly created one for your system) to help with your installation

 

[MilkyTech]

USBPorts.kext - My custom USB Port Limit Patch, (this will be created later in Post Install)

This is what the guide says...The USBPorts.kext is created in Post Install. But you are saying I need to create it Pre Install. To do this properly, needs to be done using Hackintool in macOS, but then how would anyone be able to do a fresh install of macOS if they don't already have macOS?

 

[UtterDisbelief]

This is what the guide says...The USBPorts.kext is created in Post Install. But you are saying I need to create it Pre Install. To do this properly, needs to be done using Hackintool in macOS, but then how would anyone be able to do a fresh install of macOS if they don't already have macOS?

You say that you thought USBPorts.kext is for post install only. Well not necessarily. Since Big Sur 11.3, USB configuration using standard methods has been broken. That is why we recommend using Catalina to create your USBPorts.kext and then carry that forward to later updates.

When you start to install Big Sur it's possible that the USB sub-system will become disabled during the process, scuppering it all. In that case having a pre-made USBPorts.kext in the EFI/kexts folder of your installer, will help.

Also, the fact you are just using other members EFI folders puts you at a disadvantage because you don't always know what is going on. For example, your hardware might be superfiicially the same but is the brand of SSD or the BIOS settings the same? Small stuff that makes a difference.

 

[MilkyTech]

Also, the fact you are just using other members EFI folders puts you at a disadvantage because you don't always know what is going on. For example, your hardware might be superfiicially the same but is the brand of SSD or the BIOS settings the same? Small stuff that makes a difference.

I have the exact same specs as @BayCityRoller and he successfully used this guide to install Big Sur using Robbish's EFI folder including Robbish's USB mapping and even Robbish's SSDT-PM (see this thread). It's possible he altered the config.plist slightly but no way to know which is why I am hoping he will see this and share his final working EFI folder with me. We have the same MB, CPU, and GPU and we have both set our BIOS settings exactly as this guide says to. I've never seen anywhere in any Hackintosh install ever (been making hackintosh's since Snow Leopard) where the hard drive brand matters.

 

[Robbish]

I am trying this from windows and I see option P to dump DSDT but don't see any option to "dump your own SSDT-EC"

Options 1 though to 8 dump your SSDTs. However, the only SSDT that will be useful for your Z77 motherboard from SSDTTime is the FakeEC (aka SSDT_EC).

For power management, you would need to use the PikeRAlpha method (as per my guide's Power Management )

 

[UtterDisbelief]

I have the exact same specs as @BayCityRoller and he successfully used this guide to install Big Sur using Robbish's EFI folder including Robbish's USB mapping and even Robbish's SSDT-PM (see this thread). It's possible he altered the config.plist slightly but no way to know which is why I am hoping he will see this and share his final working EFI folder with me. We have the same MB, CPU, and GPU and we have both set our BIOS settings exactly as this guide says to. I've never seen anywhere in any Hackintosh install ever (been making hackintosh's since Snow Leopard) where the hard drive brand matters.

Opinion noted.

However you then have to ask why your build is not working if it is identical?

Logic suggests that something is different. I was just offering a couple of ideas ...

As you have been hackintoshing since Snow Leopard - that's 2009 - then you must surely understand that.

 

[Feartech]

I have the exact same specs as @BayCityRoller and he successfully used this guide to install Big Sur using Robbish's EFI folder including Robbish's USB mapping and even Robbish's SSDT-PM (see this thread). It's possible he altered the config.plist slightly but no way to know which is why I am hoping he will see this and share his final working EFI folder with me. We have the same MB, CPU, and GPU and we have both set our BIOS settings exactly as this guide says to. I've never seen anywhere in any Hackintosh install ever (been making hackintosh's since Snow Leopard) where the hard drive brand matters.

also with the USB port mapping, your case may differ in regards to front usb ports

also the sacrifice of some of the ports at the back of the machine and any other internal ports you may or may not be using

 

[MilkyTech]

I created my own USBPorts.kext in Catalina and also my own SSDT-EC. However, still the installer USB stops booting at the same spot.

 

[MilkyTech]

@Robbish the power management step is Post Install correct? I should not have an SSDT-PM file in my Install USB EFI folder, correct? Right now I am just trying to get the Install USB to boot to the GUI.

I have no way of creating this file in my Catalina installation which runs on Clover. I have tried switching this installation from Clover to OpenCore without success. For some strange reason, the OC bootloader doesn't see the Catalina APFS partition. I have taken all of the troubleshooting steps possible for this problem and still the partition doesn't show. The only option I have of installing big sur is a Fresh Install on a blank HDD. In order to do that, I need the OpenCore USB Installer to boot. Based on your guide here, I don't need the PM file nor the USBKexts file (although I did create the USBKext anyway) for initial install, correct? For the sake of being thorough, I have also tried using the prebuild EC file for Ivy Bridge but that didn't help either.