[GUIDE] OC 10.13.6 Z490 Gigabyte Aorus Xtreme + Core i5 10400 / i9 11900K + Nvidia GTX 1060

[JCaser]

Hello, I would like to know how you solved the problem with the integrated graphics? I can't get Intel UHD 630 to work, I've been stuck for 4 days on this, Intel UHD 630 only recognizes 7 Mb, sorry for my English

 

[Middleman]

Hello, I would like to know how you solved the problem with the integrated graphics? I can't get Intel UHD 630 to work, I've been stuck for 4 days on this, Intel UHD 630 only recognizes 7 Mb, sorry for my English

Which version of macOS are you running? Also need to be specific with the exact version.

 

[vives21]

Hello, I downloaded your EFI folder for Big Sur and it boots first try but then my USB stop working so I get stuck in macOS recovery and I don't know what else to do.

 

[Middleman]

Hello, I downloaded your EFI folder for Big Sur and it boots first try but then my USB stop working so I get stuck in macOS recovery and I don't know what else to do.

My EFI is designed mainly for Z490 users. If you have problems booting it might be you need to add in your own UUID and system board serials into the config.plist under the PlatformInfo section which can be generated using SSDTPRGen. In any case you can refer to CaseySJ's guide and the main Dortania guide here for general help.

> https://www.tonymacx86.com/threads/...lt-3-amd-ryzen-7-3700x-amd-rx-5600-xt.304553/

> https://dortania.github.io/OpenCore-Install-Guide/

To edit the config.plist file you must have a PLIST editor installed such as ProperTree, PList Pro etc. Opencore Configurator (OCC) can also work, but you must know which version of Opencore bootloader (OC) is used in the EFI folder, and download the appropriate OCC version to edit the file - otherwise it will cause problems ie. you can't use latest version of OCC with an earlier version of OC because it will add things into the file that aren't there yet in the bootloader (causing it to crash). My earliest EFI used Opencore v0.6.1 as bootloader, and subsequent versions from April 2021 on used OC v0.6.5 and v0.6.8 (which are marked on the ZIP). So you'll need Opencore Configurator v2.11.1.1 to edit OC v0.6.1, OCC v2.22.2.0 for OC v0.6.5 and OCC v.2.35.0.0 to edit OC v0.6.8.

As I see you are using Z590 board, there is also a guide you can check for it here by OChang. But I see you are also using 11th gen Intel. You may have difficulties with running macOS as 11th gen Intel is not officially supported.
> https://www.tonymacx86.com/threads/ohchangs-build-gigabyte-z590-vision-g-i7-10700k-amd-rx580.310986/

 

[kevino83]

Hello guys,
thanks to your help i was able to boot a backup disk of a previous macbook with high sierra on my hackintosh with gygabite z490m + 10700.
The system however has messed up with my previous Big sur partition/apfs, it does not start anymore!
I also did a test with a new clean install of bigsur in a new partition, it was working but after an High sierra start big sur volumes are no more bootable!
Also instead of seeing an apfs container now i see two, i am using a different install of big sur to do the tests. I would like to recover the first partition with all the data I was working of, the disk is readable but doesn't boot.

I before it was something like :

disk1
- mac (big sur)
- test (big sur)
- data (only data)

now is like:

disk1
- mac
- mac - dati
- test
- test - Dati
- data

In opencore bootfase before it was

- mac
- test
- Recovery

and now:

- mac - dati
- test - Dati

not bootable anymore

did I have really to recreate a fresh big sure installation and manually migrate?
Any helps or tips?
I tried to repair from disk utility with no effects.

 

[kevino83]

the high sierra volume was on different fisical disc in a usb-c case, instead the big sur disc is an internal nvme
it seemd apfs on high sierra messed up with apfs big sure container, I'm the first one or it is something know?

 

[Middleman]

Hello guys,
thanks to your help i was able to boot a backup disk of a previous macbook with high sierra on my hackintosh with gygabite z490m + 10700.
The system however has messed up with my previous Big sur partition/apfs, it does not start anymore!
I also did a test with a new clean install of bigsur in a new partition, it was working but after an High sierra start big sur volumes are no more bootable!
Also instead of seeing an apfs container now i see two, i am using a different install of big sur to do the tests. I would like to recover the first partition with all the data I was working of, the disk is readable but doesn't boot.

I before it was something like :


now is like:


In opencore bootfase before it was


and now:

not bootable anymore

did I have really to recreate a fresh big sure installation and manually migrate?
Any helps or tips?
I tried to repair from disk utility with no effects.

Sorry to hear of your troubles, but technically speaking High Sierra cannot boot your Big Sur partition. There would be a lot of new changes made to Big Sur in relation to security and the APFS file system in general that simply stops High Sierra from using the Big Sur partition. Your best chance here for data recovery would be to disconnect any existing connected macOS drives, reinstall Big Sur on a newer separate drive, and then migrate the data over with Migration Assistant. Use the latest versions of my EFI files for the Big Sur install.

 

[kevino83]

really thanks for your reply!
I think my problem here is related to the fact that high sierra tried to do something on the other disc (reading, trim, indexing, I don't know...).
The same operetion on a macbook pro 2019 doesn't cause this.
On this computer I initially created my hack directly for big sure and i was quitly proud of it

I'm really the only one that suffer this?

Ps. I never tried to boot big sur from high sierra, I used an usb open core 0.6.8 for it and for big sur I had a complete installation with OC 0.7.2 and port mapping.

This means that next time I want to use my hSierra I need to disconnect every BigSur drive from the system?

Anyway on a different bigsur installation I can read correctly and see the partitions in finder, but is a little messed in disk utility or in Open core menu

 

[kevino83]

I tried to use Migration Assistant, can it be that do not works on the same drive?
sorry, I was on 11.5.2 vs 11.0.1, after update and migrating in 2/3 hours it seems it came back working, in a new installation on the same disk.

It seems that you can install directly on the non bootable to restore it, but I tested only on the fresh new installation and not the original one, I can not guarantee no data loss.

Anyway migration assistan seems working for me
In the next days I can tell by sure

Thanks

 

[Middleman]

really thanks for your reply!
I think my problem here is related to the fact that high sierra tried to do something on the other disc (reading, trim, indexing, I don't know...).
The same operetion on a macbook pro 2019 doesn't cause this.
On this computer I initially created my hack directly for big sure and i was quitly proud of it

I'm really the only one that suffer this?

Ps. I never tried to boot big sur from high sierra, I used an usb open core 0.6.8 for it and for big sur I had a complete installation with OC 0.7.2 and port mapping.

This means that next time I want to use my hSierra I need to disconnect every BigSur drive from the system?

Anyway on a different bigsur installation I can read correctly and see the partitions in finder, but is a little messed in disk utility or in Open core menu

I had reread your earlier post to see what it was you were trying to achieve. So you were basically trying to read/install an existing native macOS Macbook High Sierra install using a hackintosh?

Okay. Your problem with as to why it didn't work was threefold. First was the system format. While HFS+ and APFS can be read by High Sierra, Big Sur doesn't use HFS+ anymore. High Sierra was indeed the first macOS to implement APFS, but the implementation has since been updated with Big Sur. The biggest difference between HFS+ and APFS is the use of 'containers' to separate user data and system data. If you've not got the correct credentials the system simply will not allow you in. In addition, data encryption (FileVault) has been added with Big Sur which probably explains why your High Sierra install has difficulty reading a Big Sur drive.

Secondly, Mac native systems do not use any EFI folders for booting, only Clover and Opencore.

Thirdly a hackintosh drive will contain an EFI partition, whereas on a Mac native drive this partition may exist but will be mostly empty. These are the reasons why the partitions are not being read correctly under Disk Utility.
Either that or the drive data has been corrupted. That's why you must always install with a fresh drive on a hackintosh build.

Anyways good to hear you finally solved it.