Was able to install 10.13.6 high sierra installed, with these efi settings. Mouse and keyboard don't work in welcome screen just see the languages with mouse locked in top left corner.

Tried a bunch of usb settings no success. I even added FakePCIID_XHCIMux.kext, FakePCIID.kext, & USBInjectAll.kext still no luck with usb. Can't get past welcome page. Motherboard only has usb 3.0. I was able to get the usb 3.0 working in mojave (sadly issues w/ nvidia graphics card driver) using just the USBInjectAll.kext and some of the replace hex patches for usb support and remove limiters.

Share this post

Link to post

Share on other sites

Ok this is the first I heard that the osx86 community hates tonymac. Where would be an install high sierra guide on insanely mac that I can try and refer to? So far I've seen more comprehensive guides on tonymac (I now know it's a repackage of other peoples work for noobs) and https://hackintosher.com/guides/high-sierra-install-full-guide/. Thank you @styrian for the references.

Announcements

Similar Content

I'm trying to get a clean install of High Sierra, but didn't manage to get too far... stuck on pre-installer with some errors.

General flow that i've tried, following relevant guides and some success stories:1. Used [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] to create bootable usb drive.2. Tried to use different options, UEFI boot mode, Legacy boot mode, with and without Clover configuration...

In legacy mode it restarts after last error, while in uefi it hangs on kextd stall...

Are this components compatible with High Sierra? From what i see on other threads, people got it working somehow.Should i use Legacy boot mode as of advice from [url=&quot;http://www.insanelymac.com/forum/topic/279450-why-insanelymac-does-not-support-tonymacx86/&quot;]#####[/url] or is possible to get it working with UEFI? Which one is better?

How to get rid of "Unsupported CPU for reporter"?

Any help would be highly appreciated. I'm desperate on wasting time to get it working.

Disconnect system drive that contains your macOS Mojave install from computer ( This is so that Windows does not overwrite existing macOS Mojave boot loader )

Proceed with a Windows 10 UEFI install.
After installation reconnect macOS Mojave Drive, the Windows installation should now be detected and usable in Clover.
If Windows 10 is not detected or able to boot, then verify you installed Windows 10 as UEFI and not MBR ----> ( Read step 2 - For a drive with Windows 10 installed )

OR

STEP 2 - Using a drive with Windows 10 already installed

Verify your Windows install is GPT / UEFI or MBR / Legacy BIOS.
If Windows install is GPT UEFI then Windows 10 install is ready to use at Clover boot menu, you should be able to boot into Windows directly from Clover boot screen.

But if Windows drive is detected at Clover boot screen, but when booting Windows you get a black screen with a cursor on the top left,
then this is most likely because Windows drive is MBR ( Legacy BIOS ). You can easily convert MBR to GPT using Windows MBR2GPT tool ( this saves hours work having to reinstall Windows 10 and setting up all your applications again )

Hi everyone,
This is my first hackintosh. To be completely honest there's still a lot I'm trying to figure out... And considering I can't even get the installer to begin, seems like there's something I'm just not understanding. Any help would be greatly appreciated!!

I've specced the machine based on a multiple successful builds I've seen in various vanilla forums.
I've set the recommended BIOS, double-checked, but can't even get to an installer screen despite following a Vanilla guide from a popular hackintosh youtuber.
(Not sure if her links can be mentioned, posted etc... Just playing it safe since this is my 1st post...)

I've tried multiple SMBIOS profiles, (listed below). All of them prevent me from even booting the installer with the message below.
At this point I'm wondering if the issue is HS related, or if there's a step that, although obvious to some, isn't obvious to me and overlooking somehow.

Message returned when attempting to boot the installer. (Pic attached):

This version of Mac OS X is not supported on this platform!Reason: Mac-AA95B1DDAB278B95

I also get an error when I click update in Clover saying: Package is incompatible with this version of OS X and may fail to install
^ Seems like this indicates I've missed a step or done something wrong?

Here's a list of the complete steps I've taken so far:

Double-checked BIOS settings according to each build.
Built a vanilla installer based on the video I mentioned above, steps listed below... (I've done this twice now, confirming I followed the steps in the guide.)

Vanilla Installer Steps:
Wiped and formatted my thumb drive with GUID Partition, HFS Extended (Journaled)
Used terminal to create a bootable installer from a 10.13.6 installer I downloaded last june/july.
Installed Clover Bootloader onto the Install macOS High Sierra partition of the thumb drive, and ticked:
Clover for UEFI booting only, Install Clover into the ESP, VBox HFS-64, APFSDriverLoader-64, AptioMemoryFix-64 (leaving everything else unticked.)
Clover Configurator Steps:
Mounted the Thumb Drive's EFI folder, opened C.C. and "downloaded" Lilu, WhateverGreen, & FakeSMC to the Other folder, & installed sensors.
Deleted the default plist and manually created one using the Coffee Lake 'sample plist' from r/Vanilla Hackintosh Desktop Guide.
Copy plist to the mounted EFI folder.
Open the plist with CC and did the following:
Confirmed the following flags were set in CC's Boot section - Verbose (-v), dart=0, debug=0x100, & keepsyms=1
Tried 5 different SMBIOS profiles - iMac 18,1 , iMac 18,3 , iMac 19,1 , iMacPro 1,1 , and MacBookPro 15,1.
All result in the same Mac OS X is not supported on this platform message. The one suggestion I've found so far that seemed like it might work was to add the boot argument:
-no_compat_check

Same results, installer won't start and I get the same message...

Seems like there must be something I've missed or I've done something wrong... I've spent the weekend searching, reading, etc, no luck so far...

A few questions:

I made the installer on my MacBook, not the build I'm trying to hack. Could this be related to the issue?
(I.e. - Does the vanilla method mean you need to create your SMBIOS profile on the actual machine you'll be Hackintoshing?)

Is there a 9900k or Sapphire RX580 compatibility patch needed for 10.13 I haven't seen mentioned in the Mojave builds?
Does the Clover update message package is incompatible with this version of OS X and may fail to install indicate something isn't right with my installer setup?

Please excuse me if anything above isn't clear, I'm brand new to all this and frankly I'm having a hard time wrapping my head around a lot of it!

Making a High Sierra USB Installer Entirely From Scratch in Windows
This is a proof of concept tutorial, to show it's possible to create a vanilla High Sierra installer, entirely from scratch, in Windows (even without App Store downloaded "Install macOS High Sierra.app" from a real Mac ). @PikeRAlpha's link to Apple's Software Catalog provides us with all the URLs necessary to download the needed files directly from Apple instead of some dubious source from the internet...

to a folder named "SharedSupport" on your Windows NTFS drive. A browser download manager (eg Chrono for Chrome, dTA for FireFox) is handy since InstallESD is >4GB ---> allows you to pause/resume interrupted download...

2) Rename InstallESDDmg.pkg to InstallESD.dmg
3) Edit InstallInfo.plist with WordPad/text editor to remove the chunklistURL and chunklistid keys for InstallESD, and renaming it from InstallESDDmg.pkg to InstallESD.dmg (example of edited file attached to this post)...
Note: You can verify the SHA1 checksum of your InstallESD.dmg and BaseSystem.dmg with the correct ones at this website.
Boot Disk Utility to format the Installer USB and Restore OS X Base System HFS partition
1. Format USB with BDU & latest Clover ---> creates boot files in CLOVER partition + second FAT partition
2. Extract 4.hfs from \SharedSupport\BaseSystem.dmg with BDU --> save to it's local folder
3. Restore 4.hfs to USB second partition with BDU ---> 2nd partition becomes bootable "OS X Base System"
Paragon Hard Disk Manager to extend HFS Partition to its Full ExtentOpen Paragon Partition Manager Free and resize the second partition of the USB drive to the full size allowed. Don't forget to apply the changes at the end...
Transmac to Copy "SharedSupport" folder to OS X Base System
1. Open the TransMac program and navigate to the HFS+ Volume/Install macOS High Sierra.app/Contents folder. Right click anywhere in the empty space on the RHS pane and select "Copy Here"...
2. In the next stage, select the "SharedSupport" folder we created above as the "Files and Folders to be copied to the Mac Volume"...
Clover Settings
Clover configuration is required now. The default config.plist (in the Clover FAT32 partition of the USB) maybe sufficient to boot your machine if you’re lucky. If not, look at the Clover Wiki, Clover Instructions and Clover Configuration Thread for pointers and edit /EFI/Clover/config.plist accordingly with Wordpad or Notepad.
The location of the important configuration files for Clover are summarized below
config.plist--->EFI/CLOVER folder
DSDT.aml with or without SSDT.aml--->EFI/CLOVER/ACPI/patched (don't need one if your DSDT is auto patched by Clover in config.plist)
Kexts eg FakeSMC, NullCPUPowerManagement --->EFI/CLOVER/kexts/<osx version> or /Other. NB BootDiskUtility by default already has FakeSMC.kext installed here. You may need to add VoodooPS2Controller for your laptop keyboard/trackpad to work.
If UEFI booting, you will most likely need one of the OsxAptioFixDrv-64 drivers copied from /EFI/CLOVER/drivers-off/drivers64UEFI to /EFI/CLOVER/drivers64UEFI.
If you want to use the installer to run High Sierra in Windows on VMware, you can follow my guide to set up the Virtual Machine and replace Clover's default config with EFI_Clover for VMware (which is compatible to run in VMware). In the screenshots below, I have attached the USB Installer (in this case PhysicalDrive7) to my macOS Virtual Machine. Reboot the system to the USB installer to install High Sierra ...
What happens if we don't have access to TransMac or Paragon Hard Disk Manager?
Not a problem, as long as we get "OS X Base System" bootable, we can launch terminal from the Utilities Menu to copy the SharedSupport folder over to the Installer app. In essence, we will build the full installer app = 5GB+ on the target HD eg "Macintosh HD", by copying both the "small" installer app = 15MB (on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted in this example on /Volumes/DATA)...
-bash-3.2# cd /
-bash-3.2# cp -R Install\ macOS\ High\ Sierra.app /Volumes/Macintosh\ HD/
-bash-3.2# cp -R /Volumes/DATA/SharedSupport /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/
...then start installation with the startosinstall utility...
-bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD --converttoapfs NO --applicationpath /Volumes/Macintosh\ HD/Install\ macOS\ High\ Sierra.app
The above steps can be automated with the attached "startosinstall.command" script, which will assemble "Install macOS High Sierra.app" on "Macintosh HD" and launch the startosinstall utility targeting the "Macintosh HD" volume. Copy/download to "Macintosh HD", then run in terminal (after attaching DATA USB with /Shared Support folder)...
cd "/Volumes/Macintosh HD"
chmod +x startosinstall.command
./startosinstall.command
Updated Download Links for macOS Mojave 10.14.5_18F132
Browse Apple's Regular Software Catalog and find the URLs to download the following 6 installer files...
BaseSystem.dmg
BaseSystem.chunklist
InstallInfo.plist
InstallESDDmg.pkg
AppleDiagnostics.dmg
AppleDiagnostics.chunklist
Note: In Mojave, Apple has removed the --converttoapfs NO and --applicationpath arguments from the startosinstall utility....

eg to use startosinstall for the above section "What happens if we don't have access to TransMac or Paragon Hard Disk Manager?", the syntax is now
-bash-3.2# /Volumes/Macintosh\ HD/Install\ macOS\ Mojave.app/Contents/Resources/startosinstall --volume /Volumes/Macintosh\ HD
This basically means that for Mojave, the default installation will always convert the target volume to the apfs file system.