[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

[Feartech]

It was a blind spot for me. excuse me. thank you for teaching me.

no worries, it is quite a large thread!

 

[suteapod]

Please forgive me for the question again. Which guide should I follow to set the numbers in this part?
I'm reading the guide "Transferring OpenCore Platform Info Using HackinDROM", but it's unclear how to set it specifically.
I don't understand how to set the values of System Product Name, System Serial Number, Motherboard, System UUID, and ROM.
I have an intel Core ™ i7-9700K and a Sapphire Technology NITRO + AMD Radeon RX 6800.
I'm sorry. Please help me.

 

[suteapod]

I'm sorry to ask many questions. Should I follow the "Final Steps After Installation" section of the main guide page? There is a spoiler that sets the system name. Here it says iMac 19.1, should I set it too?

 

[NCMacGuy]

I'm having some trouble getting a bootable backup for Big Sur working. I had one working fine with Catalina. Carbon Copy Cloner seems to report that the APFS replication procedure failed. One question I have is related to first attached screenshot; I am unfamiliar with this snapshot partition, could that be causing a problem? (For anyone that may come across this post in the future, Ars Technica has a good article in their Big Sur review about how this works) I don't see the normal system and data volumes so I figured I would bring it up. The second screenshot is what I get when I try to run first aid in disk utility. With these problems, and the lack of a bootable backup due to Carbon Copy Cloner deleting my Catalina one, I'm a bit nervous. Any advice on how I should proceed? I haven't had any issues with Big Sur.

@jlr

I'm not sure what you mean by "I haven't had any issues with Big Sur." But here's an approach based on what I think you mean.

Be sure you have the latest version of Carbon Copy Cloner. Your "Container disk3" is what is typically displayed in Disk Utility because of Apple's "Secured System Volume."

I don't know why you are getting a Disk Utility error. You should get YOUR data backed up ASAP to another drive making a full Time Machine backup. It looks like you may need to reformat the Samsung 970 EVO and reinstall a new macOS system and restore your data to be sure you get the error corrected.

You should fix the problem with the Samsung 970 EVO before you try to make any CCC backups or clones from it.

I make full bootable backups of Big Sur and Monterey Betas all the time with CCC. The "trick", at least for me, is to ERASE the drive (in your case "Big Sur Local Backup") in the Container you are going to use for the bootable backup first. Otherwise if you try to use the CCC "APFS Replication" feature it may or may not simply report a failure when it starts to run the Task to make the clone.

For example, if you are trying to make your bootable backup to "Big Sur Local Backup," you need to use Disk Utility to select "Big Sur Local Backup" and Erase it.

Then in CCC select "Big Sur Local Backup" as the destination drive. Then select the "APFS Replication" selection in the popup list and in the dialog that is displayed select the option to let CCC (once again) erase the "Big Sur Local Backup" drive. Start the clone operation and all should proceed normally. (At least from my experience.)

In subsequent backups to the backup drive, CCC will only copy your changed data because the System is "secured" and none of its contents should have been modified.

For example, if you had updated the Big Sur version in your working source disk, the next time you run the CCC Task to clone the source drive, only your data is cloned. The prior Big Sur version files will not be cloned.

You also may need to install the appropriate EFI folder on the newly bootable backup drive for OpenCore to use to boot.

This has worked for me to make bootable backup drives on both internal and external drives.

Another option was also suggested where you use CCC to clone all your data to a drive, then use a Big Sur or Monterey installer to install the system on that drive to make it bootable.

BE VERY CAREFUL SO YOU DON'T LOOSE YOUR DATA! Always have your data backed up on another drive that you are sure contains everything you need.

 

[CaseySJ]

Are Hackintoshes compatible with the new Apple keyboard with the touch ID sensor?
Can it be used to authenticate things normally, like in the MacBook?

The new Apple keyboard (Bluetooth) might work, but Touch ID key will certainly not work. I haven't come across any posts from other users of that keyboard.

 

[CaseySJ]

@jlr - CCC can't make a bootable backup of Big Sur (and beyond) because of the way that Apple now secures the system files:

Just google "Carbon Copy Cloner Big Sur" and it should give you a link to the blog where they discuss it. (I tried to insert it here, but I don't think tonymacx86 allows links to external sites)

You're not doing anything wrong: It's not a fault, it's a feature!

I forget the workaround for this. I believe you make a fresh Big Sur install on your backup drive, then use CCC to copy over the files. But I haven't bothered to do this myself yet.

I've looked at their documentation (by clicking the ? after i got this error), and from what I understand it uses this APFS replication procedure the first time, and then just clones the data volume every other time. I'm having problems with the first backup.

CCC can indeed make bootable backups with both Big Sur and Monterey, but the procedure requires erasing the destination APFS volume with Disk Utility before running CCC.

When the destination volume has been erased (i.e. reformatted as APFS) we apply these options in CCC 6.x:

 

[CaseySJ]

Please forgive me for the question again. Which guide should I follow to set the numbers in this part?
I'm reading the guide "Transferring OpenCore Platform Info Using HackinDROM", but it's unclear how to set it specifically.
I don't understand how to set the values of System Product Name, System Serial Number, Motherboard, System UUID, and ROM.
I have an intel Core ™ i7-9700K and a Sapphire Technology NITRO + AMD Radeon RX 6800.
I'm sorry. Please help me.

If this is a brand new installation and you want to create new serial numbers, just do this:

I'm sorry to ask many questions. Should I follow the "Final Steps After Installation" section of the main guide page?

Please provide a link to the guide you're following...

 

[diversgens]

Hello,
my system is working like a charm under Clover 5122 with Catalina 10.15.7.
My goal is to switch to Big Sur
I have try many time to use OC on USB stick but without success, it crash soon after beginning to boot (see attach file)
I use OC 0.7.4, i have follow a lot of tutorials in this thread but i don't understand what i've missed...
My graphic card is an "old" RX 570 8go
If someone can point me to the right direction, thanks in advance

 

[CaseySJ]

Hello,
my system is working like a charm under Clover 5122 with Catalina 10.15.7.
My goal is to switch to Big Sur
I have try many time to use OC on USB stick but without success, it crash soon after beginning to boot (see attach file)
I use OC 0.7.4, i have follow a lot of tutorials in this thread but i don't understand what i've missed...
My graphic card is an "old" RX 570 8go
If someone can point me to the right direction, thanks in advance

Hello @diversgens,

Let's get you moved over to OpenCore. First, I need to ask whether you're following this guide:

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

the error came with OpenCore Configurator 2.15.0.0 try to update OCC and then your config.plist This doesn't seem to work. It is since I tried to upgrade today. I also placed back an older EFI, but the same error occurs. More suggestions?

www.tonymacx86.com

...and whether you're running BIOS F9g or BIOS F9i.

 

[NCMacGuy]

CCC can indeed make bootable backups with both Big Sur and Catalina, but the procedure requires erasing the destination APFS volume with Disk Utility before running CCC.

@CaseySJ

I have also used the same process with CCC to make bootable Monterey Beta clones.