Hi I'm finding Multibeast High Sierra is not working for me.
I've been building haxys since snow leopard and can usually solve any problems i run into, but i've been hacking at this for a week.
Unibeast is making a working H-S install (APFS) and all hardware is working after running Multibeast...
ok so today, i went through the build onto
another kingston ssd - wouldn't boot via UEFI or legacy
a seagate hard drive - which installed as a HFS+ so Multibeast failed.
and finally a build onto a samsung evo 750, which again runs fine, just multibeast fails to install a working bootlaoder...
yeah - its the same job re-visited. sierra builds well.
but HS and Mojave seem to hit a wall.
last week, i somehow managed to get a UEFI to work, but when i tried to repeat the process from scratch i get nothing :-(
you'd think cloning the EFI part across would work, but nope.
not gonna tear my...
I wasn't aware that there were problems with some ssd's - although i'm certainly suspecting it may the issue.
The Good SSD is a kingston and the others are all ADATA.
so i guess i'm going to have to find another few ssd to test.
Reading up on Samsung Plus, they seem to be an NVM which i'm...
Hi UtterDisbelief thanks for responding.
I've been building Hackintoshes using these guides since 10.6.
I'm having no problems with the Install, and multibeast is adding the kexts i need for my system without problems.
The only problem i'm having is my motherboard can't boot from my SSDs EFI...
I'm also finding Multibeast High Sierra is not working for me.
maybe a less angry mod can help ?
EFI partition is created and looks to have the correct files in it (compared to another High Sierra disk which is booting fine).
So i'm wondering if something went wrong with the bless command ...
Hi, I have an Intel DQ77MK Mobo which is working well with OSX 10.8.5 (for legacy apps), OSX10.10 Yosemite and a slightly buggy OSX10.12 Sierra.
Now I've just built a couple of High Sierra Installs - one on an SSD in HFS+ format, and a 2nd SSD in APFS format.
These SSDs were blessed using...
I had the same issue with a previously downloaded installer that worked last year, but now says its damaged.
A bit of googling said its the date. You need to set the unix date to a day or so after the date when you downloaded the installer from apple.
I changed the date in my BIOS to a day...
just incase anyone else gets this, the given command copies everything from the directory where you are, so its possible you forgot to:
cd /macOS\ Install\ Data
i got distracted and ended up running it from root dir !
i also ran into a permission denied problem - maybe just the way my machine...