Jump to content
meklort

OS X compatible motherboard -> QUO

4,390 posts in this topic

Recommended Posts

Sure it is :D

Boot into the build in Shell and use the 

bfcg boot add 

command to manually add an entry for HighSierra on APFS Volumes. Just make sure you find the correct volume by browsing your volumes with the FS Command. Once the correct Volume was found remember it´s identifier and complete your bfcg command with the required information. For example if your installation is on FS1 then just type

bcfg boot add 1 fs1:\System\Library\CoreServices\boot.efi "macOS"

after the boot Entry has successfully been added you may trigger a reboot and your HighSierra Installation should show up in your boot menu or OZ Gui.

Interesting!  Last time I checked, it wasn't possible yet. Great! With these commands, are you able to do an install of Sierra? I think IronManJFF was saying something about having to install by using a external HD enclosure to bypass APFS. I think we still cannot boot APSF, right?

Share this post


Link to post
Share on other sites
Advertisement

Sure it is :D

Boot into the build in Shell and use the 

bfcg boot add 

command to manually add an entry for HighSierra on APFS Volumes. Just make sure you find the correct volume by browsing your volumes with the FS Command. Once the correct Volume was found remember it´s identifier and complete your bfcg command with the required information. For example if your installation is on FS1 then just type

bcfg boot add 1 fs1:\System\Library\CoreServices\boot.efi "macOS"

after the boot Entry has successfully been added you may trigger a reboot and your HighSierra Installation should show up in your boot menu or OZ Gui.

This method supposed to make it work cause i tried it with adding Linux boot entry before i knew it could be possible to add the extfs as guided by The King But it doesn't work with apfs mac drive, it tell me cannot find file, also to let you know, I've embedded the apfs.ffs file into rom, and tried with loading the driver from disk that was pointed by crusher82 still no go, the only method that works is going to fsx and load the file manually by typing  

 

System\Library\CoreServices\boot.efi
this way the system will load and then i have to go to the control panel and startup and choose mac disk and reboot, I use the shell from latest Clover installed on a external USB disk.

Share this post


Link to post
Share on other sites

@Tusskan you're right if you just use one instance of HighSierra and do not wish to add any other boot entries such like the recovery partition SystemSettings -> Startup Disk is by far the easiest way to do it and it will work nicely. If you need to add more than just this entry or like to add a more customised entry as macOS then the EFI Shell is a pretty handy tool to do it. To make it work APFS.ffs of course has to be part of your custom rom but once this is done you may proceed. Here is how I did it:

 

The only thing you have to do is find the right the location of boot.efi inside the APFS Container. Diskutil (the terminal command) is handy for that. Open up a terminal an type diskutil list you'll get something like that as the result

/dev/disk0 (internal, physical):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk2         499.9 GB   disk0s2

/dev/disk2 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +499.9 GB   disk2
                                 Physical Store disk0s2
   1:                APFS Volume Sierra                  325.4 GB   disk2s1
   2:                APFS Volume Preboot                 19.0 MB    disk2s2
   3:                APFS Volume Recovery                523.3 MB   disk2s3
   4:                APFS Volume VM                      2.1 GB     disk2s4

As you see there is a physical Disk (Disk0) which holds the EFI Partition as well as the APFS Container and there ist a virtual (synthesized) Disk (disk2) which represents the the content of the APFS Container located on the first physical Disk. To add a boot entry via EFI shell all you need to know is the partition UUID of your OS Partition inside the APFS Container. To get the needed Information just type

diskutil info disk2s1 | grep "Partition UUID"

where disk2s1 of course has to be replaced with your Identifier. The command should bring up something like that:

diskutil info disk2s1 | grep "Partition UUID"
Disk / Partition UUID:    3C199D35-CB13-3164-9BF0-22821813CB91

Write down the UUID or remember it since we'll need it for the next step (This can also be done for the recovery Partition as well).

Now reboot your maschine into the build in Hermit Shell (or a different shell) and browse the available filesystems (use the fsX: and ls command where X has to be replaced by any number) until you find the one which holds a single folder that is named like the UUID you wrote down before. This filesystem represents the Filesystem which holds your HighSierra installation inside the APFS container (in my case it was fs3). Finally to add the boot entry type 

bcfg boot add 1 fs3:\3C199D35-CB13-3164-9BF0-22821813CB91\System\Library\CoreServices\boot.efi "HighSierra"

where fs3 has to be replaced by your finding and that's it you're done. The created entry will last until you reset your NVRAM and of course it can be done that way for the recovery Partition as well. 

Share this post


Link to post
Share on other sites

So I had some downtime and wanted to give myself a challenge so I went ahead and installed High Sierra on another partition. Basically, I was able to make a clean install on a real mac then install the drives I need (Nvidia, Apogee). Then I did a Carbon Copy Cloner of that partition and transferred that partition over to a new partition on my Hackintosh keeping the Mac OSX Extended Journaled file system intact (No APFS conversion). After restarting, I was able to boot the volume but I am receiving some errors. First one is "busy timeout (0),  (60s): AppleACPICPU" and then after that, I get a "IOConsoleUsers: gIOScreenLockState 3, hs 0, bs 0, now 0, Sm 0x0". Maybe something to do with my Defaults Plst or FakeSMC?

 

Anyone have any suggestions? 

 

 

Thank you!

Share this post


Link to post
Share on other sites

I you were using my SSDT remove it for High Sierra

That was it. I saw your post a few pages back and removed that SSDT and i'm now all good and working in 10.13.1

 

Thanks IronMan!

Share this post


Link to post
Share on other sites

Is there anything special that needs to be done when upgrading from 10.13.0 to 10.13.1?   I just run this command by Rehabman to avoid APFS conversion before I upgraded from 10.12.6 to 10.13.0.  Just not sure what else I may need to do before upgrading to 10.13.1?  There were reports from machines using Clover that the installer did not see certain files or some error messages occured.  Not sure if this will be the case for Osmosis boot loader?

/Applications/"Install macOS High Sierra.app"/Contents/Resources/startosinstall --converttoapfs NO --agreetolicense 

Thanks

 

Edited:

 

Per IronManJFF's post, I removed the SSD placed it into SATA to USB converter cable (StarTech product USB3S2SAT3CB), installed the update no problems.  The code above is only good on the full install downloaded from the app store so you have to upgrade before Apple lets you download the full version.

Share this post


Link to post
Share on other sites

Have you recently added some new usb bus powered devices .. Maybe you a simply requesting too much current from the USB bus ...

Other things you can try : Clear NVRAM, revome files in /Library/Preferences/SystemConfiguration/

Sent from my iPad using TapatalkIf you remove the Wacom tablet .. Do you still have issues with the mouse right-click and vice-versa ?

Sent from my iPad using Tapatalk

I tried zapping PRAM, but now it is booting directly to the EFI shell. I can hold down option and get to the system selector, but when i try and start from my hard drive, the system just shuts down. The same thing if I try for the recovery partition, or if i directly try and boot from the bios options.

 

I tried plugging in a backup system via USB 3, but the same thing happens. When I try and start from it the system just shuts down after the screen going black for a while.

 

Does anyone have any ideas. The system will not boot at all now.

 

The system is running El Capitan with the following defaults plist. It was working except the usb issues until i trued zapping the pram.

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Version</key>

<string>1.0.1</string>

<key>Date</key>

<integer>0</integer>

<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>

<dict>

<key>boot-args</key>

<string>-v</string>

<key>csr-active-config</key>

<integer>103</integer>

</dict>

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>

<dict>

<key>DisableNvidiaInjection</key>

<true/>

<key>BootEntryTemplate</key>

<string>$label</string>

<key>DarwinDiskTemplate</key>

<string>$label $platform.$major.$minor</string>

<key>DarwinRecoveryDiskTemplate</key>

<string>$label $platform.$major.$minor</string>

</dict>

</dict>

</plist>

post-1089344-0-23222600-1510008091_thumb.jpeg

Share this post


Link to post
Share on other sites

I've established that I can do a fresh install of 10.13.1 to a USB drive, using a real Macmini, and it runs on the Quo without problem. I've removed IronmanJFF's SSDT, although it did boot OK once prior to removing it and I believe I have the right firmware info in my Defaults.plist (attached). I can't get past the firmware error if I try to update 10.12.6, though and feel I need to be able to do this before moving my working system to HS. Has anyone managed to do an update as yet?

 

Defaults.plist.zip

Share this post


Link to post
Share on other sites

I tried zapping PRAM, but now it is booting directly to the EFI shell. I can hold down option and get to the system selector, but when i try and start from my hard drive, the system just shuts down. The same thing if I try for the recovery partition, or if i directly try and boot from the bios options.

 

I tried plugging in a backup system via USB 3, but the same thing happens. When I try and start from it the system just shuts down after the screen going black for a while.

 

Does anyone have any ideas. The system will not boot at all now.

 

The system is running El Capitan with the following defaults plist. It was working except the usb issues until i trued zapping the pram.

 

<?xml version="1.0" encoding="UTF-8"?>

<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com...yList-1.0.dtd">

<plist version="1.0">

<dict>

<key>Version</key>

<string>1.0.1</string>

<key>Date</key>

<integer>0</integer>

<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>

<dict>

<key>boot-args</key>

<string>-v</string>

<key>csr-active-config</key>

<integer>103</integer>

</dict>

<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>

<dict>

<key>DisableNvidiaInjection</key>

<true/>

<key>BootEntryTemplate</key>

<string>$label</string>

<key>DarwinDiskTemplate</key>

<string>$label $platform.$major.$minor</string>

<key>DarwinRecoveryDiskTemplate</key>

<string>$label $platform.$major.$minor</string>

</dict>

</dict>

</plist>

What is the last thing you see when you try to boot the system ?

Sorry I am very late , @work been crazy lately

I've established that I can do a fresh install of 10.13.1 to a USB drive, using a real Macmini, and it runs on the Quo without problem. I've removed IronmanJFF's SSDT, although it did boot OK once prior to removing it and I believe I have the right firmware info in my Defaults.plist (attached). I can't get past the firmware error if I try to update 10.12.6, though and feel I need to be able to do this before moving my working system to HS. Has anyone managed to do an update as yet?

 

attachicon.gifDefaults.plist.zip

You can try these values, they work for iMac13,2 ... don't know if they will for MacMini
 
<key>FirmwareFeatures</key>
<integer>0xE907F537</integer>
<key>FirmwareFeaturesMask</key>

 

<integer>0xFFFFFFFF</integer>

Share this post


Link to post
Share on other sites

Hi guys, I have a QUO Motherboard running Mac OS 10.12 (installed via a mr. tony86), and I want to upgrade to High Sierra, the vanilla way, can anyone give me hand?

 

I am not great in the whole Hackintosh scene, so I would appreciate the help  :)

Share this post


Link to post
Share on other sites

Did you change bios version and date, too?

<key>BiosDate</key>
<string>08/08/2017</string>
<key>BiosVersion</key>
<string>IM132.88Z.010F.B00.1708080805</string>
<key>FirmwareFeatures</key>
<integer>0xE00FE137</integer>
<key>FirmwareFeaturesMask</key>
<integer>0xFF1FFF3F</integer>
<key>FirmwareRevision</key>
<integer>0x0001000A</integer>

Share this post


Link to post
Share on other sites

No joy with getting past the firmware error. I can do a clean install and use the Migration wizard, so no great problem. I'll wait for 10.13.2 Final and see if that will update the 10.13.1 clean install. As It's my main system, I'd prefer not to take too many chances and prefer to stay with the iMac 13,1 and serial no setup I have.

 

Thanks for everyone's help.

Share this post


Link to post
Share on other sites

No joy with getting past the firmware error. I can do a clean install and use the Migration wizard, so no great problem. I'll wait for 10.13.2 Final and see if that will update the 10.13.1 clean install. As It's my main system, I'd prefer not to take too many chances and prefer to stay with the iMac 13,1 and serial no setup I have.

 

Thanks for everyone's help.

 

Here ... just put in a valid serial for iMac 13,2

Defaults.plist Template.zip

Share this post


Link to post
Share on other sites

Here ... just put in a valid serial for iMac 13,2

Thanks IronMan. That did the trick. I think I was never getting the right combination of firmware info, BIOS info and serial number together. Now on 13,2.

Share this post


Link to post
Share on other sites

Hi all, great work keeping this lovely board going!
 
I am using the specs in sig and this defaults.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Version</key>
    <string>1.0.1</string>
    <key>Date</key>
    <integer>0</integer>
    <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
    <dict>
        <key>BiosDate</key>
        <string>08/08/2017</string>
        <key>BiosVersion</key>
        <string>IM131.88Z.010F.B00.1708080805</string>
        <key>FirmwareFeatures</key>
        <integer>3759006007</integer>
        <key>FirmwareFeaturesMask</key>
        <integer>4280287039</integer>
        <key>ProductId</key>
        <string>Mac-FC02E91DDD3FA6A4</string>
        <key>ProductFamily</key>
        <string>iMac</string>
        <key>ProductName</key>
        <string>iMac13,2</string>
        <key>SystemVersion</key>
        <string>1.0</string>
        <key>FirmwareVendor</key>
        <string>Apple</string>
        <key>ChassisAssetTag</key>
        <string>iMac-Aluminum</string>
        <key>SystemSerial</key>
        <string>XXXXXXXXXXXXX</string>
        <key>BaseBoardSerial</key>
        <string>XXXXXXXXXXXXXXX</string>
        <key>SystemSKU</key>
        <string>MD095LL/A</string>
        <key>HardwareAddress</key>
        <string>XX:XX:XX:XX:XX:XX</string>
        <key>ProcessorSerial</key>
        <string>XXXXXXXXXXXX</string>
        <key>platform-uuid</key>
        <string>XXXXXXXX-XXXX-XXXX-XXXXX-XXXXXXXXXXXXX</string>
        <key>AAPL,ig-platform-id</key>
        <string>0x01660004</string>
    </dict>
    <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
    <dict>
        <key>boot-args</key>
        <string>-v kext-dev-mode=1</string>
        <key>csr-active-config</key>
        <integer>103</integer>
    </dict>
    <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
    <dict>
        <key>DisableNvidiaInjection</key>
        <true/>
        <key>BootEntryTemplate</key>
        <string>$label</string>
        <key>DarwinDiskTemplate</key>
        <string>$label $platform.$major.$minor</string>
        <key>DarwinRecoveryDiskTemplate</key>
        <string>$label $platform.$major.$minor</string>
    </dict>
</dict>
</plist>

I created a test disk and ran the HS update, it resulted in:

kexd stall[0], (240s): 'AppleACPICPU'

What more changes do I need to do to update from Siserra to High Sierra?

Share this post


Link to post
Share on other sites

Hi all, great work keeping this lovely board going!

 

I am using the specs in sig and this defaults.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Version</key>
    <string>1.0.1</string>
    <key>Date</key>
    <integer>0</integer>
    <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
    <dict>
        <key>BiosDate</key>
        <string>08/08/2017</string>
        <key>BiosVersion</key>
        <string>IM131.88Z.010F.B00.1708080805</string>
        <key>FirmwareFeatures</key>
        <integer>3759006007</integer>
        <key>FirmwareFeaturesMask</key>
        <integer>4280287039</integer>
        <key>ProductId</key>
        <string>Mac-FC02E91DDD3FA6A4</string>
        <key>ProductFamily</key>
        <string>iMac</string>
        <key>ProductName</key>
        <string>iMac13,2</string>
        <key>SystemVersion</key>
        <string>1.0</string>
        <key>FirmwareVendor</key>
        <string>Apple</string>
        <key>ChassisAssetTag</key>
        <string>iMac-Aluminum</string>
        <key>SystemSerial</key>
        <string>XXXXXXXXXXXXX</string>
        <key>BaseBoardSerial</key>
        <string>XXXXXXXXXXXXXXX</string>
        <key>SystemSKU</key>
        <string>MD095LL/A</string>
        <key>HardwareAddress</key>
        <string>XX:XX:XX:XX:XX:XX</string>
        <key>ProcessorSerial</key>
        <string>XXXXXXXXXXXX</string>
        <key>platform-uuid</key>
        <string>XXXXXXXX-XXXX-XXXX-XXXXX-XXXXXXXXXXXXX</string>
        <key>AAPL,ig-platform-id</key>
        <string>0x01660004</string>
    </dict>
    <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
    <dict>
        <key>boot-args</key>
        <string>-v kext-dev-mode=1</string>
        <key>csr-active-config</key>
        <integer>103</integer>
    </dict>
    <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
    <dict>
        <key>DisableNvidiaInjection</key>
        <true/>
        <key>BootEntryTemplate</key>
        <string>$label</string>
        <key>DarwinDiskTemplate</key>
        <string>$label $platform.$major.$minor</string>
        <key>DarwinRecoveryDiskTemplate</key>
        <string>$label $platform.$major.$minor</string>
    </dict>
</dict>
</plist>

I created a test disk and ran the HS update, it resulted in:

kexd stall[0], (240s): 'AppleACPICPU'

What more changes do I need to do to update from Siserra to High Sierra?

 

The first is Ozmosis to let you boot to HS:

 

Ozmosis.ffs.zip

 

While you use SSD, the Disk will be formatted as APFS automatically, so register the APFS file that you have to put on the EFI/Efi/APFS.efi => SSD not usb after the install procedure is done

Put USB InstallMedia out

Restart

@ the Boot screen use shell from F12 and type:

Note: assuming that your SSD will be the first bootable Disk0s1 then use fs0: and press enter after each line

 

 

fs0: 

cd  Efi

bcfg driver add 1 APFS.efi "APFS"

 

You're done

Share this post


Link to post
Share on other sites

@ niXta  This website is called: INSANELYMAC , and it's true, one of the most! I just used what it was used by cecekpawon the MAN.

 

You can follow this Topic and Ozmosis Topic, if any update will be made you can know it ^_^  .

Edited by ammoune78

Share this post


Link to post
Share on other sites

@ niXta I thought my two qou mobos where the only ones that ended up in Sweden.

 

At the moment and since about a year back one of my two mobos is broken though. Probably the bioschip need replacing so Ill try that when I get the time.

Share this post


Link to post
Share on other sites

@ niXta I thought my two qou mobos where the only ones that ended up in Sweden.

 

At the moment and since about a year back one of my two mobos is broken though. Probably the bioschip need replacing so Ill try that when I get the time.

Haha, I always wondered if anyone else had a quo in Sweden, I've been running mine since launch, it and OZ has been awesome

Lycka till med att flasha/byta bios'et, håller tummarna!

Share this post


Link to post
Share on other sites

Yes at least two more lol and I have had so much fun with these fantastic mobos so Im glad i bought two cause one is still working.

Tackar för tummarna håller mina med lol .

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By Tricchi
      Vorrei assemblare un nuovo hackintosh partendo dallo stretto necessario per poi aggiungere altri componenti nel tempo. Dato che la mobo penso sia fondamentale vorrei prenderne una che mi dia la possibilità di future espansioni ma che non costi troppo. Ho visto che su Amazon ci sono delle mobo come ad esempio la Asrock Z370 Taichi usate ad ottimi prezzi. Voi che ne pensate? Vale la pena o è rischioso? Nella descrizione c'è scritto "Come nuovo" o "Ottime condizioni".
      Riguardo alla compatibilità di questa scheda madre con hackintosh che mi dite? Il modulo wi-fi e bluetooth è compatibile?
      Grazie.
       
      Marco
    • By Surfman
      Ciao a tutti.
      dopo aver installato High Sierra il pc non può avviarsi dall'SSD mostrandomi la schermata nera che dice di scegliere il boot. facendo partire il pc con l'USB inserita, da dove ho installato il tutto, mi viene mostrata schermata di scelta dove posso effettivamente fare partire osx appena installato dal ssd ma con una lentezza mostruosa!. se provo con la chiavetta scollegata stessa schermata nera con la scelta del boot. inutile aggiungere che ho cercato di cambiare l'ordine di avvio dal BIOS, aggiornato il BIOS, ma senza successo. l'ssd funziona perché dopo ho installato da questo stesso anche linux o windows tranquillamente
      cosa posso fare? grazie a tutti

      MOBO: Gigabyte GA-B250M-DS3H
      CPU intel i5
      GPU NVIDIA MSI N750 Ti TF 2GD5 / OC  

    • By srmusico
      Hello guys.
      This is not my first hackintosh, but this will be the first time to create a hackintosh with thunderbolt.
      First of all, i have read some info about MoBos with Thunderbolt, but im a bit confused.
      I need to create a working hackintosh with Thunderbolt 2/3 .
       
      At this moment i know that we got 2 options (Correct me if im wrong),
      -we can get one MoBo and ad a Pcie Card with thunderbolt (only if the chipset is compatible)
      -we can get one MoBo with thunderbolt integrated via USB-C connectors (like the new Macbook Pro)
       
      What are the possible MoBos that have integrated Thunderbolt vía USB (or directly thundelbolt ports)?
      I have read a lot of buyers guides from some webs , but a lot of that MoBos with thunderbolt enabled, are "discontinued" or without stock
      Should we only choose Gigabyte MoBos? 
       
      I Have been too looking at Gigabyte website, and seems that the Chipset Z170 its the only one with Thunderbolt (vía USB-C)
      ports.
       
      Could you help me with these please?
       
      Thanks You So Much!
    • By Costanegra
      Hello.
       
      It's been about 3 or 4 years since I built my first, and so far only hackingtosh. I did so fallowing a guide written by good guy ^Andy^, witch came with hardware recommendations. I now feel it's time for me to upgrade to a faster system to keep up with heavier work loads. I'm strongly considering building a hackingtosh around the new i7-6700K Skylake processor, but I haven't come across guides for  this type of processor. I was wondering if any of you could recommend me a motherboard that's compatible and that won't become a hassle when trying to install OS X. Also, if there's a guide you know of, please let me know.
       
      Thanks in advance.
    • By FrankOshe389
      Hi,
      I'm currently running a Windows 7 x64 PC with:

      8GB DDR3 Ram

      AMD FX 4170 GPU

      AMD Radeon HD 7870 CPU

      1TB HDD (Windows 7)

      150GB HDD (Blank)
       
      Gigabyte GA-970A-DS3 Motherboard
      I am aware that getting OSX on an AMD machine is not an easy task, but can it be done with my setup?

      I am currently running OSX 10.8.3 in VMWare which is OK but lags a fair bit and lacks any kind of 3d acceleration and would like to be able to dual boot it natively alongside windows on the 150GB HDD.

      Thanks 
×