Contribute
Register

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

Reattempt & Failure - 10.15.3 to 10.15.14 Update

reattempting the 10.15.3 to 10.15.4 update after making the following changes:
  • setup nvram support (mini guide on page 1730)
  • updating to clover 108
  • updating to latest lilu, whatevergreen, and apple kexts
update starts smoothly, unlike first effort where it would hang giving me hope. Then well into the update the update presents this window - macOS could not be installed on your computer. The installed resources were not found. Quit and Restart.

System will boot to 10.15.4 as before and the two preboot volumes remain.
I tried that unsuccessfully as well. My primary system still has the leftover "macOS Install" volumes. I vaguely remember a Terminal command (perhaps a sudo defaults write com.apple... type of thing) to back out of an in-progress update, but I've been unable to find that.

My options for now:
  • Wait for 10.15.5.
  • Wait for someone to find the magic answer.
  • Fully erase, reformat, and install Catalina 10.15.4 from scratch (making sure a 10.15.3 full backup exists).
    • But use exactly the same SMBIOS and RtVariables sections as 10.15.3 (just borrow them from the old config.plist).
    • Then transfer all my Apps and Documents from the 10.15.3 backup disk to 10.15.4.
  • Hide the leftover boot volumes in Clover.
 
Hi guys, I also have an antelope interface and would love to help, to get my interface working and to give back to this community from which I've gained so much.

However, two questions:
1. What are the risks? My designare build is my main studio machine and I totally rely on it everyday.
2. Can you all guide me? I'd be completely out of my depth; Although I've been Hackintoshing since Tiger I'm no computer scientist!
On a mission critical system your best bet is this:
  • If getting the Antelope Audio Interface to work is not mission critical, then it's probably best not to make any changes to a mission critical computer.
  • But if it is mission critical, then proceed by following the 3 guides in the red boxes below (see Post #1 for links):
Screen Shot 2020-03-30 at 8.45.47 AM.png

  • Once you're ready to begin, attempt only to read the Thunderbolt flash chip three or four times in a row.
  • Compute the checksum of each file.
  • If all checksums match, type strings name-of-extracted-file.bin just to make sure the files are not empty.
  • All these steps are described in the guides referenced above.
  • If the chip cannot be read easily, don't force it and instead, STOP and let us know what's happening.
 
I tried that unsuccessfully as well. My primary system still has the leftover "macOS Install" volumes. I vaguely remember a Terminal command (perhaps a sudo defaults write com.apple... type of thing) to back out of an in-progress update, but I've been unable to find that.

My options for now:
  • Wait for 10.15.5.
  • Wait for someone to find the magic answer.
  • Fully erase, reformat, and install Catalina 10.15.4 from scratch (making sure a 10.15.3 full backup exists).
    • But use exactly the same SMBIOS and RtVariables sections as 10.15.3 (just borrow them from the old config.plist).
    • Then transfer all my Apps and Documents from the 10.15.3 backup disk to 10.15.4.
  • Hide the leftover boot volumes in Clover.

Have you tried THIS
 
Have you tried THIS
Oh, looks like that thread just got more replies:
Will try this momentarily...

EDIT: It does not work on 10.15.4. The procedure on Page 6 is for 10.15.1. By the way it's much easier to press CMD-Shift-. (dot) to toggle hidden files in Finder.
 
Last edited:
I think if I remember the posts you regained native NVRAM but before that you did do a CMOS clear. Hopefully that + the Native NVRAM will have this sorted for you.

I see, but what gets me off is it simply got back to the original issue after regaining MSR register, as posted here
 
Yes, many times. Been looking at HWmon also, but the screen freezes and shows no changes or spikes unfortunately. Although I’m not sure how to monitor GPU temps on a hack. Is there a way?

I've only ever had one freeze on my Hackintosh because of a faulty USB device plugged on a HUB. I guess-if you've not tried this already-you could try unplugging everything except keyboard and mouse for one of these long sessions where you would get a freeze, you could also try a different GPU output if you haven't done so already.

Also, I'm using HWMonitorSMC2 to monitor my GPU temps and fan speeds, works great here, just remember to enable GPU temp from its options.
 
Oh, looks like that thread just got more replies:
Will try this momentarily...

EDIT: It does not work on 10.15.4. The procedure on Page 6 is for 10.15.1. By the way it's much easier to press CMD-Shift-. (dot) to toggle hidden files in Finder.

How about just directly downloading the 10.15.4 combo update and running that?

I don't have the issue to be able to test it but logically it should work if it finishes the update cleanly.
 
Because you're installing Mojave and have most likely used the latest UniBeast or MultiBeast, you are running Clover 5xxx instead of 4xxx. In Clover 5xxx there is no drivers64UEFI folder. Instead, perform all those steps in drivers/UEFI folder.
perfect! thank you Casey
 
Was super hard. I did it using Virtualbox & Rufus. For what I understood it is not possible anymore create a pendrive using Etinbootin or Teminals command because the new Windows iso is more bigger then 5GB, and the only what is using Windows media creation tool or Rufus.
so, were you finally able to create a windows USB installer that works?
 
Hello, @CaseySJ,
I have a question please ,
Whenever I press the Power Button on the First Time (when the PC is completely shut down), the computer Starts for 1seconds, then shut down, then it starts again alone for 2 seconds to shut down again. Again, a 3rd time it starts on automatically (without pressing Power) and this time really Boot.
The first two times it starts and shut down, the computer don't reach the BIOS/UEFI. The 3rd time it does.

I have to say that this happens each time on the first time I run the computer (not if I Restart) on the day.
This is not an Hardware issue as I have 2 exactly same computer with the same problem (Mine and one of my friend).

Furthermore I haven't overclock or touch anything related to this. The bios is setup as you said in your first post.
On some forums they might say that It could result from insufficient power, and may be might be fix by "Turbo Mode in the bios ???"

My hardware is brand new:
I9-9900 k
Z390 Designare
RM750 Corsair
64GO RAM Crucial 3000mHZ Cas 15 DDR4
Sapphire Nitro 8GO RT5700X.
FEnvi T919
2 SSD NVME

Thank you
 
Back
Top