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

[Mochimino]

Hello @Mochimino,

Glad to hear the system has been stable! Mojave is very old now, but the upgrade to Monterey or Ventura shouldn't be too bad. If you go back 3 or 4 pages in this thread, you'll see that @madmax559 just went through the same process:

• He made a clone of Mojave on a spare SSD, then attempted to upgrade the clone (the original SSD was always kept safe)
• He first replaced Clover with OpenCore on the clone SSD
• Then he booted into the Clone SSD (still with Mojave) to make sure OpenCore was working properly
• After that, he did an in-place upgrade to Monterey (if I recall correctly)

If you're willing to give this a try, I can help you...

Hi, thanks for your answer!
Doing a clone on another SSD sound great. It could allow me to try to update without messing up the original SSD, I like the idea. But I never did a clone or anything like booting into cloned SSD, so I will definitely need some help!
Will any SATA SSD work? My system is on a 1TB NVMe SSD at the moment.

 

[madmax559]

Hi, thanks for your answer!
Doing a clone on another SSD sound great. It could allow me to try to update without messing up the original SSD, I like the idea. But I never did a clone or anything like booting into cloned SSD, so I will definitely need some help!
Will any SATA SSD work? My system is on a 1TB NVMe SSD at the moment.

Yes, any SATA SSD will work
Here is how my system is laid out

Layout

1. 1 x 1TB Samsung M.2 EVO 970 Plus //primary drive,
2. 2 x 1TB Samsung EVO 860 SSD //SATA drives

Clones

1. Use Super Duper to clone primary drive to one of the SSD & name that "clone"
2. Use EFI mounter & copy over whole EFI folder from primary to clone EFI partition
3. Reboot & make sure you can boot from clone

Clover -> OpenCore (Optional, if you are on Clover)

1. Remove L/E or just rename that directory & touch L/E
2. Remove or move rc scripts for Clover or add exit after 1st line for bash so the script will have no effect
3. Boot from USB stick with OpenCore
4. Pick EVO 970 & let it start up Mojave & make sure everything works under OC
5. Mount primary EFI & move EFI folder to EFI.clover.
6. Drag over EFI folder from USB to EFI partition on primary 970
7. Remove stick & reboot back into your OS via Clover
8. At this point the "clone" is intact & has Clover in it's EFI (in my case)

Upgrade from Mojave -> Monterey
I'm waiting on the Thanksgiving sales to get a WD Black M.2 1TB so I can replace my primary SSD

1. Aftre testing a few days. Update the EFI on "clone" with the EFI on primary so now both are on OpenCore
2. Add a scheduled nightly task to SuperDuper to auto update clone every single day
3. Download OSX Monterey & copy or move that into Applications on "clone"
4. Do a last smart update from SuperDuper
5. Reboot & pick "clone" from OC picker. It will be named "clone" or whatever label your SSD has
6. Or your can set your BIOS to boot from the "clone"
7. Start "Install OSX Monterey" & go make coffee
8. Reboot after install into updated OS
9. Come back here & let us know

 

[tyns]

The SN850 seems to be EOL. Is the SN850x a viable replacement? Has anyone had any controller compatibility problems reported yet?

 

[NZRichard]

Is the SN850x a viable replacement?

Working fine here on a Z690 system - see profile

 

[Mochimino]

@madmax559
Thanks a lot for your answer! I will buy an SSD and see when I find time to do it, probably in December.
I think the cloning part I can handle, however the switch from Clover to OpenCore looks more challenging as I haven't much understood but I'll come back here and ask more specific question when the time come.
Thanks again for your time, i'm always amazed of how nice the Hackintosh community is!

 

[CaseySJ]

@madmax559
Thanks a lot for your answer! I will buy an SSD and see when I find time to do it, probably in December.
I think the cloning part I can handle, however the switch from Clover to OpenCore looks more challenging as I haven't much understood but I'll come back here and ask more specific question when the time come.
Thanks again for your time, i'm always amazed of how nice the Hackintosh community is!

After the clone is done, don’t worry about the next step. We’ll help you with that.

 

[etorix]

@Mochimino Post #1 provides a complete EFI for your system, which only needs serial numbers; you may reuse those from your Clover installation. All further instructions are to purge (a copy of) your existing installation of anything installed under /L/E, and keep a copy of the working installation.

Alternatives would be:

• Update Clover to a recent version which can boot Monterey and later. This will involve manual installation (no more *beast), and updating config.plist to the new structure, including OpenCore-derived quirks.
• Make a clean installation of macOS with OpenCore on a new drive and use Migration Assistant to move your applications and data to the new drive. (But do not migrate Clover scripts and additions to /L/E.)

 

[EdBogie]

@CaseySJ

I finally dug through and found the bit about selecting macOS Installer from the USB when it reboots during installation, so I was on the right track. But, when I select that, it turns into a never ending boot loop where the Apple logo pops up for a second then I get the motherboard screen with the F12 for Boot options/Del for BIOS page. I’ve got it set to automatically boot to my USB drive, so whether I hit F12 and select the USB or let it go automatically, I always get a second of Apple logo then restart, and, after about a dozen reboots, I just shut my system off. Any ideas?

Thanks!

(Trying to install Monterey using your EFI for OpenCore).

 

[NCMacGuy]

@CaseySJ

got it set to automatically boot to my USB drive, so whether I hit F12 and select the USB or let it go automatically, I always get a second of Apple logo then restart, and after about a dozen reboots I just shut my system off. Any ideas?

@EdBogie

Sorry to butt in, but this could be caused by the BIOS setting for CFG Lock being Enabled. Go to your BIOS "Boot" window, I'm using BIOS F9i, and see if there is a CFG Lock setting, and confirm it is DISABLED.

 

[EdBogie]

@EdBogie

Sorry to butt in, but this could be caused by the BIOS setting for CFG Lock being Enabled. Go to your BIOS "Boot" window, I'm using BIOS F9i, and see if there is a CFG Lock setting, and confirm it is DISABLED.

Alas, CFG lock is already disabled. Thanks, though!