Jump to content

OS X compatible motherboard -> QUO

meklort

By meklort,
in New Releases and Updates

 Share
4,397 posts in this topic

Recommended Posts

elviejo
elviejo
Posted
Posted

Today I made the upgrade to High Sierra from beta developer and it wasn't easy, first of all the firmware error creep back again so I have to update the Ozmosis Defaults.plist in bios ( I don't use the efi option in the first hdd ), the good news, there is no more restrictions to the usb ports, so I use iMac 14,2 settings, but it keep giving the firmware error in the second stage, at that point I tried the second stage with clover ( same defaults.plist ) and was able to pass the firmware error but the installation hangs with apple acpicpu, so I boot normal with f12 and High Sierra wasn't in the entries, I choose to boot to Sierra ( Thank God I have Sierra on another drive ) and select to boot to High Sierra in start up disk in System preferences and was able to finish the installation, this was a clean installation, then another problem arise when I try to migrate my High Sierra beta with Migration Assistant, no matter what I did it always fail at the end so I go back to Sierra and erase the High Sierra drive and made a restoration of my High Sierra beta from Time Machine and run the installer from there ( I tried the startosinstall method and it didn't work ) the install didn't work booting with Ozmosis so I used Clover again to finish the installation, boot to Sierra choose High Sierra in start up disk and voila I have High Sierra installed with all my settings and applications. So there is several problems in Ozmosis that have to be solved to have a smooth installation; first the recognition of the apfs drives in the boot stage is problematic and the firmware settings don't appear to be passed to the installer, until this is solved is going to be troublesome to install. :worried_anim:

 

post-35379-0-01712800-1506476853_thumb.png

  • Like 1
Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

Looking forward to a high sierra ready BIOS update! thanks for putting in all the testing

I'm working on it and I'm sure I am not the only one. :D

so attached are templates for the rom, the rom posted has the OzmosisDefaults.plist removed and there is one without the serials, you can obtain the serials with clover configurator ( use the last updated one ) and insert the serials with Xcode or a plist editor ( don't use a text editor!!! ) after that convert it to ffs with kext to ffs and insert it in the rom with UEFI Tool ( how to do it can be learn in the Ozmosis section on the  Forum ). Good luck. :thumbsup_anim:

 

Ozmosis templates.zip

  • Like 1
Link to comment
Share on other sites
ntsmkfob
ntsmkfob
Posted
Posted

I'm working on it and I'm sure I am not the only one. :D

so attached are templates for the rom, the rom posted has the OzmosisDefaults.plist removed and there is one without the serials, you can obtain the serials with clover configurator ( use the last updated one ) and insert the serials with Xcode or a plist editor ( don't use a text editor!!! ) after that convert it to ffs with kext to ffs and insert it in the rom with UEFI Tool ( how to do it can be learn in the Ozmosis section on the  Forum ). Good luck. :thumbsup_anim:

 

attachicon.gifOzmosis templates.zip

Hi elviejo, thanks for putting this together.  I can't get past the 'MacOS could not be installed...', verifying firmware error, though. I am using a 13,1 BIOS info dated 08/08/17, which I think is the latest.

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted (edited)

Cannot upgrade to release with my current setup which has been working up until the last beta.

The firmware version hasn't changed so it could be the firmware features or firmware features mask (SysDef iMac13,2) or the version of APFS

 

Quote

 

Sep 28 22:43:20 iMac OSInstaller[572]: ROM Features returned: 3909612855

Sep 28 22:43:20 iMac OSInstaller[572]: ROM does not support APFS
Edited by IronManJFF
Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

Hi elviejo, thanks for putting this together.  I can't get past the 'MacOS could not be installed...', verifying firmware error, though. I am using a 13,1 BIOS info dated 08/08/17, which I think is the latest.

 

Cannot upgrade to release with my current setup which has been working up until the last beta.

The firmware version hasn't changed so it could be the firmware features or firmware features mask (SysDef iMac13,2) or the version of APFS

If you read my post http://www.insanelymac.com/forum/topic/285920-new-os-x-compatible-motherboard-quo/?p=2501432, you will see that I have the same problem and have to use clover to pass the second stage because the firmware error even as I used the same plist, I think Ozmosis is not passing the firmware information to the installer, that is something I hope the coders ( Hello ccepawon ) would take a look on it; for the moment I suggest to use the clover avenue ( only to pass the firmware error ) or you could wait until a solution is found. Good luck. :yes:

This are the latest: http://www.insanelymac.com/forum/topic/291655-ozmosis/?p=2502506 

Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

The whole point for me is to not rely on Clover and I won't die if I don't run High Sierra today.

On iMac14,2 on the latest beta there were no restrictions on the USB2 ports but the USB3 ports were restricted. Have you checked the USB3 ports ?

I understand your point of view, check this http://fortune.com/2017/09/29/apple-mac-update-security-sierra-firmware/, apparently that is one of the problems and I think here reside the solution http://www.insanelymac.com/forum/topic/291655-ozmosis/?p=2502416, about the USB3 ports I think they are working fine, check the ioreg attached.Jose’s Mac Pro.ioreg.zip

Link to comment
Share on other sites
Nubira
Nubira
Posted
Posted

Do you ever have time to use your computers? To me it looks all you do is fixing them for the next up os x version. But I guess it is fun and time consuming cause some does not seem to be able to find the time with the replying or just don not .....

 

Or does that only happen to those who do not list their every little piece of hardware they own?

 

Good thing this is a big forum lots of interesting stuff going on in other threads

Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

Do you ever have time to use your computers? To me it looks all you do is fixing them for the next up os x version. But I guess it is fun and time consuming cause some does not seem to be able to find the time with the replying or just don not .....

 

Or does that only happen to those who do not list their every little piece of hardware they own?

 

Good thing this is a big forum lots of interesting stuff going on in other threads

This is a hobby and I can assure you we have time to use it and much more, not everybody have the same interests and that is ok.

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

Thanks for your guy's hard work! Nice to know that people are working hard to get High Sierra working. For those wanting to upgrade, at this moment their is really no need to if your on Sierra. Wait it out till a new BIOS is released with all the proper modifications, By then, we might be seeing 10.13.2 (seeing that apple has already released 10.13.1 beta)

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

Is there an install guide available for high sierra. I have read success a few posts back with apfs but not sure if one can install from a flash drive with clover on it for example or just create an installer partition on the ssd. Not sure of the exact process and what the defaults.plist need to contain. I still have to update to Sierra compatible firmware. Is Quo no longer in business?

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

Is there an install guide available for high sierra. I have read success a few posts back with apfs but not sure if one can install from a flash drive with clover on it for example or just create an installer partition on the ssd. Not sure of the exact process and what the defaults.plist need to contain. I still have to update to Sierra compatible firmware. Is Quo no longer in business?

I would advise on waiting for a BIOS. To my knowledge, Quo is not in business anymore

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

Cannot upgrade to release with my current setup which has been working up until the last beta.

The firmware version hasn't changed so it could be the firmware features or firmware features mask (SysDef iMac13,2) or the version of APFS

 

Updated APFS in ROM image, still no go.

Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

The whole point for me is to not rely on Clover and I won't die if I don't run High Sierra today.

On iMac14,2 on the latest beta there were no restrictions on the USB2 ports but the USB3 ports were restricted. Have you checked the USB3 ports ?

You were right, with iMac14,2 we lost the USB3 ports in the back.....so back to mac mini6,2. :poster_oops:

In the next two days I'm going to try again to install High Sierra with Oz only support, will keep posted. :yes:

Link to comment
Share on other sites
ntsmkfob
ntsmkfob
Posted
Posted

well, after more tries no dice, the same firmware error surface. :wallbash:

Looking at the tail end of the ia.log in /MacOS Install Data, the install starts to run through the various firmware upgrades and gets to the point where it determines that the firmware doesn't support apfs. It then bails out pretty quickly.

 

I've pulled the last few lines out below. Whether it helps or not I've no idea:

 

Sep 28 18:50:03 iMac OSInstaller[580]: Firmware update package path: /Volumes/InstallESD/Packages/FirmwareUpdate.pkg

Sep 28 18:50:03 iMac OSInstaller[580]: Evaluating 1 disks

Sep 28 18:50:03 iMac OSInstaller[580]: Evaluating SKDisk { BSD Name: disk24s2 Mount point: /Volumes/InstallESD Role: kSKDiskRoleLegacyMacData Type: kSKDiskTypeHFS }

Sep 28 18:50:03 iMac OSInstaller[580]: InstallESD is a valid target.

Sep 28 18:50:05 iMac OSInstaller[580]: Running /usr/libexec/FirmwareUpdateLauncher using directory: /Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.402 FirmwareUpdateLauncher[622:48736] Checking for MultiUpdater at /Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools/MultiUpdater/MultiUpdater.efi

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.405 FirmwareUpdateLauncher[622:48736] Running /usr/libexec/smcupdater (

Sep 28 18:50:05 iMac Unknown[556]:     "-p",

Sep 28 18:50:05 iMac Unknown[556]:     "/Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools/SMCPayloads",

Sep 28 18:50:05 iMac Unknown[556]:     "-s"

Sep 28 18:50:05 iMac Unknown[556]: )

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.456 smcupdater[623:48744] path: /Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools/SMCPayloads/Mac-00BE6ED71E35EB86

Sep 28 18:50:05 iMac Unknown[556]: Failed dir stat

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.524 FirmwareUpdateLauncher[622:48736] smcupdater exited with status: 11

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.524 FirmwareUpdateLauncher[622:48736] Running /usr/libexec/ssdupdater (

Sep 28 18:50:05 iMac Unknown[556]:     "-p",

Sep 28 18:50:05 iMac Unknown[556]:     "/Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools",

Sep 28 18:50:05 iMac Unknown[556]:     "-s"

Sep 28 18:50:05 iMac Unknown[556]: )

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.642 FirmwareUpdateLauncher[622:48736] ssdupdater exited with status: 255

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.642 FirmwareUpdateLauncher[622:48736] Running /usr/libexec/usbcupdater (

Sep 28 18:50:05 iMac Unknown[556]:     "-p",

Sep 28 18:50:05 iMac Unknown[556]:     "/Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools",

Sep 28 18:50:05 iMac Unknown[556]:     "-s"

Sep 28 18:50:05 iMac Unknown[556]: )

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.695 usbcupdater[625:48756] Error reading plist: No files to support boardID: Mac-00BE6ED71E35EB86

Sep 28 18:50:05 iMac Unknown[556]: 2017-09-28 18:50:05.762 FirmwareUpdateLauncher[622:48736] usbcupdater exited with status: 13

Sep 28 18:50:05 iMac OSInstaller[580]: /usr/libexec/FirmwareUpdateLauncher finished with status: 1

Sep 28 18:50:05 iMac OSInstaller[580]: Running /usr/libexec/efiupdater using payload /Volumes/Mac El/macOS Install Data/FirmwareUpdatePackageExpanded/FirmwarePackageExpanded/Scripts/Tools/EFIPayloads

Sep 28 18:50:05 iMac Unknown[556]: Raw EFI Version string: MBP131.88Z.0212.B00.1708080127

Sep 28 18:50:05 iMac Unknown[556]: EFI currentVersion: [0000000002120000]

Sep 28 18:50:05 iMac Unknown[556]: EFI updateVersion:  [00000000010F0000]

Sep 28 18:50:05 iMac OSInstaller[580]: /usr/libexec/efiupdater preflight finished with status: 1

Sep 28 18:50:05 iMac OSInstaller[580]: Advancing to next progress phase: OS Installer 2

Sep 28 18:50:05 iMac OSInstaller[580]: client 0x7f96d8c431c0: phaseName = "OS Installer"

Sep 28 18:50:05 iMac OSInstaller[580]: ISAP: Done with Phase "OS Installer"

Sep 28 18:50:05 iMac OSInstaller[580]: ISAP: Done with Phase "OS Installer"

Sep 28 18:50:05 iMac OSInstaller[580]: Connection = 0x7f96d8c23d50, callers = (

        "<IASUPCaller: 0x7f96d8c760f0>",

        "<IASUPCaller: 0x7f96d8fd1e60>"

    )

Sep 28 18:50:05 iMac OSInstaller[580]: Registering the connection

Sep 28 18:50:05 iMac Installer Progress[177]: Done with phase = "OS Installer"

Sep 28 18:50:05 iMac OSInstaller[580]: client 0x7f96d8fd38e0: phaseName = OS Installer 2

Sep 28 18:50:05 iMac Installer Progress[177]: IASSetCurrentInstallPhase: Current phase name set to "OS Installer"

Sep 28 18:50:05 iMac Installer Progress[177]: IASSetCurrentInstallPhase: Current phase name set to "EFI Firmware Update"

Sep 28 18:50:05 iMac Installer Progress[177]: IASSetCurrentInstallPhase: Current phase name set to "OS Installer 2"

Sep 28 18:50:05 iMac OSInstaller[580]: ROM Features returned: 2147488791

Sep 28 18:50:05 iMac OSInstaller[580]: ROM does not support APFS

Sep 28 18:50:05 iMac OSInstaller[580]: Clearing automation and attempting to rebless. source volume: SKDisk { BSD Name: disk2s2 Mount point: /Volumes/Mac El Role: kSKDiskRoleLegacyMacSystem Type: kSKDiskTypeHFS } rebless: 9F501769-A582-3A00-A7EB-427F3DDF38A4

Sep 28 18:50:06 iMac OSInstaller[580]: OSIInstallElement <OSIVerifyROMElement: 0x7f96d8e9c170> errored out:Error Domain=com.apple.osinstall Code=512 "An error occurred while verifying firmware." UserInfo={NSLocalizedDescription=An error occurred while verifying firmware.}

 

end of log.

Link to comment
Share on other sites
IronManJFF
IronManJFF
Posted
Posted

Values for FirmwareFeatures and FirmwareFeaturesMask in Defaults.plist must match what is expected from a real Mac you are trying to emulate.

 

MBP131.88Z.0212.B00.1708080127: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136

Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

Does 10.12.6 work well and if not which MacOS works the best so far. Is there a link to the latest or last bios QUO released and a link to the Osmosis firmware/boot loader, I am attempting to do updates.

 

Also will the Nvidia EVGA GTX770, GTX760, GT740, GT640 GT210 etc work? I understand I may need to modify the default.plist.

 

Thanks

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

Does 10.12.6 work well and if not which MacOS works the best so far. Is there a link to the latest or last bios QUO released and a link to the Osmosis firmware/boot loader, I am attempting to do updates.

 

Also will the Nvidia EVGA GTX770, GTX760, GT740, GT640 GT210 etc work? I understand I may need to modify the default.plist.

 

Thanks

 

10.12.6. works very well on my system with a 1080 TI.  I'd recommend upgrading to that version and wait for a proper 10.13 bios.  Here is the bios modified for sierra that i'm using, you will need a Defaults.plst specifically for your setup and SIP disabled for your system to boot properly. Look around page 150 and go on from there for information on what to do .

Z77MXQUOAOS.H2O.167X-MASS.zip

  • Like 1
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

10.12.6. works very well on my system with a 1080 TI.  I'd recommend upgrading to that version and wait for a proper 10.13 bios.  Here is the bios modified for sierra that i'm using, you will need a Defaults.plst specifically for your setup and SIP disabled for your system to boot properly. Look around page 150 and go on from there for information on what to do .

 

I seem to be having the same issue as in Post 3041 page 153, the prohibitory sign.  I used another mac to create a Sierra 10.12.6 installer partition and even went as far as installing Sierra on the SSD.   No bootloaders were installed on this drive when I installed Sierra.  I did the nvram reset.  I am wondering if the EFI needs to have the Osmosis tree before it boots the SSD since I actually did not install Sierra from QUO I am wondering if the EFI tree was properly made will all the Osmosis folders and files or is that not the issue with booting to the prohibitory sign, maybe something else is the issue?  It happens on the installer partition, recovery and the MacOS.  It does boots to the EFI shell every time.

Link to comment
Share on other sites
dwdrummer0
dwdrummer0
Posted
Posted

To my knowl

 

I seem to be having the same issue as in Post 3041 page 152, the prohibitory sign.  I used another mac to create a Sierra 10.12.6 installer partition and even went as far as installing Sierra on the SSD.   No bootloaders were installed on this drive when I installed Sierra.  I did the nvram reset.  I am wondering if the EFI needs to have the Osmosis tree before it boots the SSD since I actually did not install Sierra from QUO I am wondering if the EFI tree was properly made will all the Osmosis folders and files or is that not the issue with booting to the prohibitory sign, maybe something else is the issue?  It happens on the installer partition, recovery and the MacOS.  It does boots to the EFI shell every time.

To my knowledge, the EFI partition stays the same with each update. Only changes to it would be by the user by adding SSDT's or PLST's. Have you tried disabling SIP? Thats a classic reason behind the prohibition sign.

  • Like 1
Link to comment
Share on other sites
oSxFr33k
oSxFr33k
Posted
Posted

To my knowl

 

To my knowledge, the EFI partition stays the same with each update. Only changes to it would be by the user by adding SSDT's or PLST's. Have you tried disabling SIP? Thats a classic reason behind the prohibition sign.

 

Well I cannot disable it on QUO since I get the prohibitory sign on the Recovery Partition, MacOS and install partitions.  I removed the drive and boot on another mac and disabled it from there.

 

Also placed the Defaults.plist in /EFI/EFI/Oz.

 

Been working on this for the last two hours going to give up for now, continue tomorrow night.  Maybe I will refresh the firmware again.  Should I set Optimized defaults after the fresh firmware install followed by the Nvram reset?   Doesn't the Defaults.plist have the correct settings to disable SIP which I grabbed from page 153 or 154 don't remember but its for the iMac13,2 and I am using EVGA GT740 so the Defaults has Nvidia injection disabled which should work since this card does not need Nvidia injection its supported natively.

 

Can't figure out the issue!

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...