Jump to content
xpamamadeus

Ozmosis

6,187 posts in this topic

Recommended Posts

Advertisement

@medallo

 

Replace SMC+Sensors, Ozmosis, OzmosisDefaults with current versions and add GM apfs.ffs.

 

 

In OzmosisDefaults:

 

Change FirmwareFeatures, FirmwareFeaturesMask, BiosVersion, BiosDate

 

 

Use KextToFfs to convert new OzmosisDefaults and apfs.efi to their ffs-versions:

 

Put OzmosisDefaults.plist in Ozm and apfs.efi in Efi.

 

 

attachicon.gifBildschirmfoto 2017-09-26 um 08.21.11.png

./KextToFfs.command

You will find the resulting ffs files in the Ffs folder.

 

 

Use MMTool and replace the files in the bios like this:

 

Load the bios file in MMTool and select the entry you want to replace, select the Replace tab and browse for the new file and hit replace.

 

 

attachicon.gifBildschirmfoto 2017-09-26 um 08.25.21.png

 

 

Save As different file ;) and flash it.

 

Where we can found current versions of SMC+sensors and Ozmosis?

Share this post


Link to post
Share on other sites

Here you go. The Archive contains following Files:

 

- OZ 1.03.167X-CPWN Release (the one patched for HighSierra)

- APFS.EFI patched for reduced verbose Output and taken from the Release Version of HighSierra

- FakeSMC and Sensors Rev 6.25-333 (SMC Version 2.22f16)

 

And the rest of the OZ Files taken from the XMAS Release. Be careful with the GPU Sensors they might trigger a Kernelpanik if used with a NVIDIA Pascal based GPU. The defaults in this package identify the Maschine as an iMAC14,1.

HighSierra.zip

Share this post


Link to post
Share on other sites

Here you go. The Archive contains following Files:

 

- OZ 1.03.167X-CPWN Release (the one patched for HighSierra)

- APFS.EFI patched for reduced verbose Output and taken from the Release Version of HighSierra

- FakeSMC and Sensors Rev 6.25-333 (SMC Version 2.22f16)

 

And the rest of the OZ Files taken from the XMAS Release. Be careful with the GPU Sensors they might trigger a Kernelpanik if used with a NVIDIA Pascal based GPU. The defaults in this package identify the Maschine as an iMAC14,1.

Hi Griven,

 

Could you make a Z87N-WIFI High Sierra ROM ?

 

Attached is your Modded ROM posted on hackintosh-forum forum that I use in my machine.

 

Thanks.

 

Regards.

Z87NWIFI-F6-Sierra.rom.zip

Share this post


Link to post
Share on other sites

Here you go. The Archive contains following Files:

 

- OZ 1.03.167X-CPWN Release (the one patched for HighSierra)

- APFS.EFI patched for reduced verbose Output and taken from the Release Version of HighSierra

- FakeSMC and Sensors Rev 6.25-333 (SMC Version 2.22f16)

 

And the rest of the OZ Files taken from the XMAS Release. Be careful with the GPU Sensors they might trigger a Kernelpanik if used with a NVIDIA Pascal based GPU. The defaults in this package identify the Maschine as an iMAC14,1.

Hi ..thanks griven.

but black screen and it doesn't advance.

:(

Share this post


Link to post
Share on other sites

The black screen is no OZ Issue at all. Please keep in mind that flashing a new Rom onto your board will reset all settings to factory default and in case you use a dedicated GPU you might end up with a black screen since the iGPU is reactivated and initialised as primary video output. Try to connect your screen to your iGPU instead of the dedicated one and you should be able to enter your bios setup utility and configure it properly (turn off igpu etc...)

 

@DoGuiTTo sorry but Z87N-Wifi has not enough available space to hold all necessary files so the time being there is no way to make this ROM HighSierra compatible.

Share this post


Link to post
Share on other sites

it is after setting the bios that it stays on the screen in black and does not advance.

My machine: Asus P8Z77-M, CPU:Core i5 3470, GPU EVGA Geforce 210 1024MM, SSD Kingston.

in Sierra  10.12 it works well.

Share this post


Link to post
Share on other sites

You can easily add an entry via efi shell and bcfg comand...

How does it work? Do you have tutorials or links?

Thanks

Share this post


Link to post
Share on other sites

The black screen is no OZ Issue at all. Please keep in mind that flashing a new Rom onto your board will reset all settings to factory default and in case you use a dedicated GPU you might end up with a black screen since the iGPU is reactivated and initialised as primary video output. Try to connect your screen to your iGPU instead of the dedicated one and you should be able to enter your bios setup utility and configure it properly (turn off igpu etc...)

 

@DoGuiTTo sorry but Z87N-Wifi has not enough available space to hold all necessary files so the time being there is no way to make this ROM HighSierra compatible.

 

Thanks Griven,

 

I managed replace the Osmosis.ffs patchedFakeSCM*.ffs plus the InjectorKext.ffs and DisablerKext.ffs  from your zip in the BIOS. 

 

Removed the OsmosisDefaults.ffs as I have it on /Oz

 

Is there a way to load APFS.efi and after that HighSierr, like if I put it on CLOVERx64drivers (or whatever it is called) ?

 

And HermitShellx64.efi (when needed)  ??

 

Thanks... Regards

Share this post


Link to post
Share on other sites

it is after setting the bios that it stays on the screen in black and does not advance.

My machine: Asus P8Z77-M, CPU:Core i5 3470, GPU EVGA Geforce 210 1024MM, SSD Kingston.

in Sierra  10.12 it works well.

or am I missing something to do?
or what causes this problem?

 

I'm stuck in this. thank you.

Share this post


Link to post
Share on other sites

@griven

Sure that black screen it is not a OZ issue?

I use OZ not in BIOS but via efi shell and bcfg comand

and I also get a black screen (NVIDIA GeForce GT 640 )


I did try all listed " initial display outputs" IGFX, PCIe 1 Slot etc.

I had to disable driver ozmosis.efi to get back my screen.

I can boot via clover, so my BIOS settings should be ok

Share this post


Link to post
Share on other sites

A short story:

 

One mont ago, ammoune78 decided to leave Ozmosis to try Clover and to leave ROM untouched. The work for the EFI partition was finally done after a day, good, and config.plist with hot patches make the life easier, kexts placed, SSDT's also! Life will be easier for him without problems only, hhhhh,, but what happened is trying to install Sierra and finding other problems beside Config.plist being corrupted, in addition to all working OS X partitions became not bootable. Finally two days with no success, rrrrrrrr!

 

I don't know but, three disks with 2x10.12.6 and 10.13 had the exact same problem, even if they booted before without any kind of problem. I'm not happy and I don't want to wast my time, the simplest solution are here, yes, OZMOSIS backup, yes I did a backup of my OzmRom, hhhhh, it's simple like HermitCrabs Lab: QUO Your Computer, Your Configuration, Your Choice!!!!!

 

I already commented before for giving a special thanks for all the OZMOSIS developers and all who they worked on it, today also, I sincerely THANK YOU ALL BECAUSE THIS WORK IS A BEAUTIFUL HARDROCK WORK.

 

I love you all guys and i wish you all the best  

Share this post


Link to post
Share on other sites

There is one thing which is really annoying with OZ and apfs. Since OZ won't pick up boot entries for APFS Volumes on it's own you have to manually add them via EFI Shell and bcfg which is not much of a deal except your motherboards NVRAM is not writable at all. One Example my Z77-DS-3H (F10 Firmware) has writeable NVRAM and I am able to add boot entries for HighSierra and The Recovery Partition inside The APFC Container without any issue. Once added they stay persistent until I perform a NVRAM Reset on a QOU AOS the same thing won't work. You can add boot entries as well but as soon as you restart the machine or leave the EFI Shell they are gone.

 

Any Ideas how to solve this Issue? Or is there even any progress in a way that OZ will detect this entries on it's own?

Share this post


Link to post
Share on other sites

There is one thing which is really annoying with OZ and apfs. Since OZ won't pick up boot entries for APFS Volumes on it's own you have to manually add them via EFI Shell and bcfg which is not much of a deal except your motherboards NVRAM is not writable at all. One Example my Z77-DS-3H (F10 Firmware) has writeable NVRAM and I am able to add boot entries for HighSierra and The Recovery Partition inside The APFC Container without any issue. Once added they stay persistent until I perform a NVRAM Reset on a QOU AOS the same thing won't work. You can add boot entries as well but as soon as you restart the machine or leave the EFI Shell they are gone.

 

Any Ideas how to solve this Issue? Or is there even any progress in a way that OZ will detect this entries on it's own?

So, is the Hermitshell included in the Bios published on the Hackintosh-forum.de website? If it's not the case, one would have to make a USB stick with Efi Shell to be able to boot from HS...

Share this post


Link to post
Share on other sites

It depends on the available space. We try to integrate as much as possible first of all the core files and the APFS driver and if there is enough space left the shell, sensors and stuff like that where we have a priority on the shell. The older Z7X Roms are mostly complete newer ROMS and the B or H flavoured Chipsets may lack the Theme, Shell or both. Don't get me wrong it's not about the ability to boot HighSierra through the shell it's about persistent boot entries. One of the strongest arguments pro OZ is the ease of use which includes that there was no need to take care about boot entries and stuff like that before. Most OZ users are not advanced users they use OZ since it used to work out of the box.

 

This kind of people don't want to mess around with stuff like shells and boot entries they are not used to it and most of them don't want to learn about it. Prior to HighSierra and APFS it doesn't really matter wether the NVRAM is persistent or not since OZ took care about it and scanned the boot entries on each and every start and added them on the fly with APFS this mechanism broke and if the NVRAM is not persistent you'll end up with no bootable Volume which kind of sucks...

Share this post


Link to post
Share on other sites

@griven

The way you're talking about for APFS has been disputed, it's somehow difficult to perform it since the last time cecek did a try. You can push the post up by your questions for searching for a solution, but as I think OzDev's don't want to do something for Ozmosis. I use only Oz with no APFS, for me it's enough!

I hope also like you as many of us, we are still waiting :)  ^_^  ! 

Share this post


Link to post
Share on other sites

@ammoune78 sure you're right the OZ Dev's don't care about anything and that's the only sad thing at the long end...

 

For me in person it doesn't matter at all since I luckily own a Mobo which offers enough space to insert all the needed stuff and provides writeable and persistent NVRAM as well. All I've got to do is to add a boot entry via HermitShell and i am good to go but that's not my point.

 

OZ was released as a supplemental BIOS Upgrade for the all-mighty QUO AOS Motherboard and it's kind of ironic that especially the QUO Customers are not able to use their Boards any more since OZ in combination with HighSierra lacks to detect APFS Volumes and even fail to hold manually added boot entries (added via shell with bcfg). In Fact they are forced to use Clover as an alternative since their overpaid solution isn't capable to detect and boot apples latest OS anymore and that is a shame. 

 

Don't get me wrong it's not about Cecek this guy did everything possible to give OZ life support. He did great things when Sierra pops out (the OZ devs didn't care about it at all but claimed how well OZ was designed that a simple patch is enough to make it run *sigh*) and he did it again when HighSierra pops out and with the KernextPatcher he also added a long  awaited an truly needed feature.  My concerns and/or thoughts about APFS might have been disputed but nevertheless APFS is a real hurdle which needs to be taken if not by the OZ Devs themselves than hopefully by someone else...

Share this post


Link to post
Share on other sites

Maybe a driver could be written that adds the apfs boot entry automatically? Instead of using a shell. Edk2 kit has a sample app that displays and allow you to change the boot order so maybe with a little alteration you could make it work. Just a thought. Anyhow Oz is eol so anything goes,,

Share this post


Link to post
Share on other sites

the OZ Dev's don't care about anything and that's the only sad thing at the long end...

 

You have to know...

 

(the OZ devs didn't care about it at all but claimed how well OZ was designed that a simple patch is enough to make it run *sigh*) 

 

Bin-patch an old Clover to work with a new version of macOS, then comment again on this topic.

 

I suggest you to remove all the FD files from your forum, not a brilliant idea offering such badly supported software from horribly evil devs, eh?

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.

  • Similar Content

    • By Slice
      Since rev 4844 Vector Themes are supported and there are ready-to-use Clovy by Clovy, cesium by Slice and BGM_SVG by Blackosx.
      You may see it's structure to create own theme
      -------------------------------------------------------------------------------------------------------------------------------------------------------
       
       
      Now I want to add vector graphics support in Clover. See rev 4560 and later.
      It is not working yet but designers may begin to create Vector Themes.
      It supposed to consist of SVG elements and has design size. It will be rendered to any screen size scaled from design size.
       
      What application in macOS can create SVG graphics?
      Inkscape is not working in macOS 10.11+. Pity.
      LibreOffice Draw works with SVG but buggy.
      Boxy SVG cost 10$ but looks good enough. It creates the best in simplicity files and have more then enough features.
      Illustrator is good but expensive.
       
      How to improve SVG file?
      Clover has restricted support for SVG. It is your job to make compatible file and as small as possible to speedup rendering.
      Some helps:
      Help:Inkscape – From invalid to valid SVG Inkscape files
      From invalid to valid SVG Adobe Illustrator files
      From invalid to valid SVG files of other editors: BKchem, ChemDraw and CorelDRAW
      Help:Illustrator – Assistance with creating and saving SVG images in Adobe Illustrator that will pass W3C validation
      User:Quibik/Cleaning up SVG files manually
      Later I will write own instructions specific to Clover abilities.
       
      How to create SVG fonts?
      You can google to find ready-to-use SVG fonts.  I found some problems with too beaty fonts: slow rendering and overflow crash. Be careful.
      You can get ttf or otf fonts and convert them into svg by using online WEB services. Not a problem to google.
      But then I want to find a way to simplify the font to reduce a size and speedup rendering.
      You can create own font by FontForge It is opensource and available for Windows, Mac and GNU+Linux. It creates otf font which you can convert to svg font.
       
      Pictures from Badruzeus
      https://www.insanelymac.com/forum/applications/core/interface/file/attachment.php?id=301597
    • By thomaspetersen
      Hi All
       
      I'm trying to start a Hackintosh High Sierra 10.13.5 installation:
      - MSI B350 PC Mate
      - Ryzen 5 - 2600
      - Radeon Pro 580 GPU
      - 4 x 8GB DDR4
      (Have a working clover bootloader for HS 10.13.3 - but for some reason, I can't use that setup with the 10.13.5) 
       
      Have tried different bootloader setup, with different outcomes...
      ATM. I get this error/hang - "Unknown CPU: family = 0x17, model = 0x8, Stepping = 0x2"
      Have search google, and can see that the threads ppl. are getting this, is when they look at "About this mac", I haven't yet installed the OSX.
       
      So can someone help...

      I'm running the newest Kexts: AppleALC, FakeSMC, Lilu, RealtekRTL8111, USBInjectAll and WhateverGreen.
      In Bootloader setup, i'm running: -v, -s, -f, -no_compat_check, busratio=34, PCIRootUID=1, npci=0x2000, dart=0 and nv_disable=1
      In SMBIOS i'm using the iMac18,2 and in RT i'm using BooterConfig: 0x28 and CsrActiveConfig: 0x67
      In installed drivers i'm using: AptioMemoryFix, EmuVariableUefi-64, OsxAptioFixDrv-64 (Have tried Fix2 as well)
       
      But i'm, keep getting the Unknown CPU hang/error, can someone help...
      Or do someone have a setup with the same CPU and GPU, that can show me his/her setup for Bootloader/Kexts...
    • By apianti
      Just so you all know I actually have done something. I have pushed the source to both my github and to sourceforge, please commit to the experimental branch and I will merge it into the stable branch once it is safe. Also, nothing meaningful happens yet so don't get too excited. Only the Visual studio build works right now. I haven't set up the Xcode or Makefile builds yet, I'm trying to do them now.
       
      https://github.com/apianti/Clover
      https://sourceforge.net/p/cloverefiboot/Clover
       
      IA32/X64/ARM/ARM64 testing ISO (6/7/2018): Clover-3.0-experimental.iso
    • By cvad
      Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
×