Jump to content

73 posts in this topic

Recommended Posts

Hello Everyone

 

Can someone help me create an Ozmosis v1479 BIOS with my stock Asrock Z77 Pro-m v2.00.ROM?

 

I've getting these errors when using the ./OZMTool --ozmcreate option.

Roberts-Mac-Pro:Ozmosis v1479 Asrock Z77 Pro-M v2.00 robert$ ./OZMTool --ozmcreate -a 1 -cr -ck -f Ozmosis-1479 -d DSDT.aml -o AsrockZ77ProM-200-Ozmosis-1479.rom -i AsrockZ77ProM-200.rom
OZMTool - v0.3
Warning: No KEXT-dir given! Injecting only Ozmosis files!
Info: Aggressivity level set to 'Delete network stuff from BIOS'...
Info: Compressing CORE_DXE is selected!
Info: Compressing Kexts is selected!
Inserting supplied DSDT into image...
* Dumped AmiBoardInfo from BIOS...
* Injecting DSDT into AmiBoardInfo...
ERROR: PE32 has .ROM but not DYNAMIC_BASE set -> Unpatchable atm..
ERROR: Failed to patch DSDT into AmiBoardInfo!
ERROR: Failed to inject DSDT!
! Program exited with errors !

Status code: 240
Roberts-Mac-Pro:Ozmosis v1479 Asrock Z77 Pro-M v2.00 robert$ ./OZMTool --ozmcreate -a 1 -cr -ck -f Compress-Ozmosis-1479 -d DSDT.aml -o AsrockZ77ProM-200-Ozmosis-1479.rom -i AsrockZ77ProM-200.rom
OZMTool - v0.3
Warning: No KEXT-dir given! Injecting only Ozmosis files!
Info: Aggressivity level set to 'Delete network stuff from BIOS'...
Info: Compressing CORE_DXE is selected!
Info: Compressing Kexts is selected!
Inserting supplied DSDT into image...
* Dumped AmiBoardInfo from BIOS...
* Injecting DSDT into AmiBoardInfo...
ERROR: PE32 has .ROM but not DYNAMIC_BASE set -> Unpatchable atm..
ERROR: Failed to patch DSDT into AmiBoardInfo!
ERROR: Failed to inject DSDT!
! Program exited with errors !

Status code: 240 

The files i'm using are attached, if that helps someone figure it out. This is an Aptio Asrock UEFI. I haven't seen anyone make an Asrock OZ UEFI/Bios setup yet or maybe I just haven't look hard enough.

 

Thanks!

 

Robert aka Mrengles

Share this post


Link to post
Share on other sites
Advertisement

Out of curiosity if I would like to re-create the QUO .rom file but including my own defaults.plist into it.. what would be the steps involved ?

./OZMTool --ozmextract --out outputdir --input OZM.ROM

Then what  ?

Share this post


Link to post
Share on other sites

Out of curiosity if I would like to re-create the QUO .rom file but including my own defaults.plist into it.. what would be the steps involved ?

./OZMTool --ozmextract --out outputdir --input OZM.ROM

Then what  ?

 

Hello,

 

You need UEFITool, open you rom file, go on OzmosisDefaults, extract as body raw file, save as Defaults.plist, modify it, and replace in rom as body.

 

Fred

Share this post


Link to post
Share on other sites

Thanks Fred .. would that be true for any .ffs found in the rom image ?

 

Yes, but this is the only one that is readable without doing anything.

 

Fred

Share this post


Link to post
Share on other sites

Hi

 

When I trying to inject DSDT to Z97-A bios using OZMTool I am getting these errors:

ERROR: AmiBoardInfo contains '.ROM' section => unpatchable atm!
ERROR: Failed to patch AmiBoardInfo with new DSDT!
! Program exited with errors !

I have first extracted DSDT using OZMTool then modified it and try to inject but no success. the weird thing is even if try to inject unmodified DSDT still I am getting these errors..

 

Please help..

Thanks

Share this post


Link to post
Share on other sites

I've downloaded OZMTool_v0.3_osx and am trying to run it, however the process gets killed whenever I run it. 

bash-3.2$ ./OZMTool --help
Killed: 9
bash-3.2$ ./OZMTool
Killed: 9

I'm running on Sierra. I've tried right clicking on the file to open it to bypass Gatekeeper warnings, but that didn't fix it. Does anyone have any suggestions?

Share this post


Link to post
Share on other sites

Hi,

 

I have a suggestion for the next release of OZMTool in that it would be cool if it would compress a bios file without adding any OZ files.

So you could manually add the files as you please after. Many times when modding bios for whatever purpose finding space is the thing

and if the app could just compress the file without looking for OZ files would be a nice feature.

 

Thank you

Share this post


Link to post
Share on other sites

Anyone know how to compile ozmtool from source? Was wondering is this done in Ubuntu, Osx, or Windows for building a windows executable?

 

Thank you

Share this post


Link to post
Share on other sites

No experience at all though was able to compile ozmtool with the 5.62 version of QT in Windows. Any other version I try causes errors. Only thing is got to have two dll files hanging off the side for it to run as there's no way I know of to link them into the exe without a QT license,

Share this post


Link to post
Share on other sites

I used the QT GUI environment in Windows opening up the .Pro files and launching build. I also tried it in Ubuntu running 'Qmake nameoffile.Pro && make'. I havent tried it on my mac yet. Wonder if its possible to cross compile for windows on Ubuntu. The QT Sdk in windows takes like 40 Gb at least and every version you add on is like another 15-20 Gb. Prefer command line though all the windows guide use Visual studio. Seems like a pain.

Share this post


Link to post
Share on other sites

I would avoid cross-compilation as long as you haven't established a working native environment.
I cannot assist for windows as I have only setup QT for mac and to be honest it was a pain in the a...

Share this post


Link to post
Share on other sites

I would avoid cross-compilation as long as you haven't established a working native environment.

I cannot assist for windows as I have only setup QT for mac and to be honest it was a pain in the a...

 

Thats why I'm using a VM so I can roll back every screwup. My macbook has so many different libraries of this and that already installed it would be messy.

Share this post


Link to post
Share on other sites

I compiled the releases with Qt 4.8.3 iirc - natively built on the target OS.

 

Sorry guys, I am short on time lately, and I am very unhappy with the code layout of OZMTool..

Only real option would be a full rewrite imho..

Share this post


Link to post
Share on other sites

I compiled the releases with Qt 4.8.3 iirc - natively built on the target OS.

 

Sorry guys, I am short on time lately, and I am very unhappy with the code layout of OZMTool..

Only real option would be a full rewrite imho..

Much appreciate what you have done already. Was finally able to compile it on 5.6 QT. Curious that Ozmtool was able to add all the Oz files without having to delete any networking modules as it seems it is able to expand the main firmware volume. For my own nefarious purposes hope you don't mind me tinkering with the code to allow more than just OZ files to be inserted like Nvme ffs files while not deleting any other files to make room. Spoke to Coderush about this and he persuaded me to not go any further as his thoughts were that command line tools could be potentially dangerous. So was wondering what are your thoughts? Thanks.

Share this post


Link to post
Share on other sites

... not go any further as his thoughts were that command line tools could be potentially dangerous ...

Well, actions like modifying a BIOS image and flashing it afterwards is already dangerous, I agree.

 

For commandline-Tools in general, I disagree - why should they be generally considered dangerous ?

 

Specific case OZMTool vs. UEFITool though =>

OZMTool tries to be as verbose as possible by showing info for each file injected / deleted / compressed...

HOWEVER: You should always verify the proper condition of the output image by yourself!

OZMTool tried to warn the user if something failed - but such information is only as valuable as the code behind it...

 

Oh and about the resizing of Volumes: Yes, it's UEFITool under the hood, all the magic (except Kext / Dsdt actions) are possible due the magic work of CodeRush  :yes:

Share this post


Link to post
Share on other sites

Well, actions like modifying a BIOS image and flashing it afterwards is already dangerous, I agree.

 

For commandline-Tools in general, I disagree - why should they be generally considered dangerous ?

 

Specific case OZMTool vs. UEFITool though =>

OZMTool tries to be as verbose as possible by showing info for each file injected / deleted / compressed...

HOWEVER: You should always verify the proper condition of the output image by yourself!

OZMTool tried to warn the user if something failed - but such information is only as valuable as the code behind it...

 

Oh and about the resizing of Volumes: Yes, it's UEFITool under the hood, all the magic (except Kext / Dsdt actions) are possible due the magic work of CodeRush  :yes:

 

Well he put the fear in me. On one hand he's trying to spare me the pain from people blaming you (I mean me) if their motherboard is bricked. That I understand and appreciate. In matter of fact there was only one bios that the tool I found couldn't handle. Think it was from Asus. OZM complained that the firmware imploded so yes its risky however it worked for me with my Gigabyte bios.  I messed with the code so much I may start over myself as afraid that in the course of experimenting and learning I might have altered something as I added a property in the Treemodel to keep track of the size of each module. Anyhow l I found later your ozmtool can expand a firmware volume so why worry about how many bytes are free because it didn't matter! It just expanded the volume. Pretty cool but really is that as Coderush implied dangerous? I suppose it can be on the rare occasion. Thanks.

 

PS: Thanks for the tips. I will definitely implement verification routines. 

 

Also noticed you had a lot of '//To do later' comments in there. Didn't really affect the function. Maybe it was Coderush's 'To do later' comments. 

Share this post


Link to post
Share on other sites
cutheads-iMac:~ cuthead$ ./OZMTool --dsdtextract --out ./  --input ./F9
Killed: 9

why?

Share this post


Link to post
Share on other sites

For new mobos support i would suggest using MMTool 5.2.0.24 (Aptio V+ and all others with patched version) only thing (its .exe) and has to be into a wine container if used on mac, but it works very well then for a 500mb app :P

 

here you can get the lot. it contains also older versions and for the latest one. the untouched and patched ones

 

this is how it looks like if you don't know this tool

1177300193_ScreenShot.png.c2968cbd4ec3999fb36df8125f6bc5c1.png

Edited by LAbyOne

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 kylon
      Cloud Clover Editor is an open source application that allows you to manage the configuration of various Hackintosh Bootloaders.

      Open Cloud Clover Editor
       
      Cloud Clover Editor Wiki
      Cloud Clover Editor Sources
       
       
      Features
      Supports Clover EFI, Ozmosis, Chameleon, OpenCore GUI and Text Editor Mode CCE Bank Mobile friendly and more...  
      Officially supported browsers
      Chrome 42+ Microsoft Edge 14+ Firefox 39+ Safari 10+ Opera 29+ Opera Mobile 12+ Chrome for Android 75+ Firefox for Android 67+  
       
      Credits
      mackie100 - took some ideas from his app Clover EFI dev team Eric Slivka - new serial number Virtual1 - new serial number cecekpawon - PHP 5.3.3 patch, , help with the ACPI Loader Mode flag and more Micky1979 - Clover flying editor  (Discontinued) crusher. - Help with the ACPI Loader Mode flag Download-Fritz - Help with the ACPI Loader Mode flag Pavo - Ozmosis fields and values stehor - Ozmosis fields and values Sherlocks - General help and support gujiangjiang - General help and support  
      Please let me know if i forgot you!
    • By gorans
      Hi,
       
      after updating HS my WOL stopped working. It worked for sure in El Capitan, not sure in what version of HS stopped to work. I'm using Ozmosis as bootloader and IntelMausiEthernet (in S/L/E) for network. I created ssdt.aml with ssdtPRGen, and put it in EFI/Oz/Acpi/Load/.
      WOL is enabled in BIOS, wake for network access is checked
      pmset -g System-wide power settings: DestroyFVKeyOnStandby 0 Currently in use: standby 0 Sleep On Power Button 1 womp 1 hibernatefile /var/vm/sleepimage powernap 0 networkoversleep 1 disksleep 10 sleep 15 autopoweroffdelay 28800 hibernatemode 0 autopoweroff 0 ttyskeepawake 1 displaysleep 15 standbydelay 10800 If I put machine to sleep, WOL works for a short time, but not working if I let it sleep for a while.
       
      I deleted Ethernet in Network, rebooted and recreated it, but still the same.
       
      Hardware:
      MOBO:     Gigabyte Z97-D3H rev 1.1
      processor:    i5-4460 Haswell
      graphic:    Gigabyte GeForce GT 740 OC GDDR5 2GB (GV-N740D5OC-2GI)
      memory:    2 x 8GB Kingston
      disks:    Samsung SSD 850 EVO 120GB
              Seagate 2TB
              LG DVD±RW
      Sound:     VoodooHDA
      Network:    IntelMausiEthernet.kext
       
      Any advice?
       
      Best regards,
      Goran
    • By uglyJoe
      Hello everybody,

      I’m using Ozmosis with a Gigabyte H81M-HD3 but unfortunately this board hasn’t enough space in it’s ROM to store the apfs.efi, too.
      Than I have a second machine, my ZBox-Nano that not even has the space for the really necessary stuff.
      Sure, Clover is able to solve all this problems but I want to go with Ozmosis

      Here comes rEFInd into the game: http://www.rodsbooks.com/refind/
      This boot loader could be installed into the ESP.
      rEFInd is not only able to detect apfs formatted partitions but also to load uefi drivers!
      And after some weeks of testing, I claim that rEFInd is doing his job very well.

      rEFInd is open source so I take a look into it and found a good starting point to learn a little more about the UEFI. The result is a rEFInd version with some additions, that should make life easier and more colorful ….

      I’m using this „enhanced“ version in two different setup’s.

      First the H81M, that comes with ozmosis, hfsplus, fakesmc and a patched dsdt inside the ROM.
      Here rEFInd is only loading apfs.efi and scanning for macOS. The Oz directory on the ESP is not in use.

      Second the ZBox. I only replaced the FileSystem driver with EnhancedFat and patched the ROM to unlock the MSR.
      rEFInd is loading hfsplus, apfs and ozmosis and is scanning for macOS.
      Ozmosis is loading dsdt, ssdt, kext and defaults from the Oz directory on the ESP.

      If you like to test it: Installation is easy but do it at your own risk!
      Unzip the download and open the directory in Finder.
      It comes with rEFInd, ozmosis.efi, apfs.efi, hfsplus.efi and a Oz directory with mac mini defaults and fakesmc.kext.
      Goto Efi/Oz and adapt it, to suit your needs.
      Goto Efi/Boot/drivers_x64, if you have ozmosis or hfsplus installed into your ROM, delete it from the drivers directory because you don’t need to load it again.

      If you are ready to go, mount your ESP and copy shellX64.efi and the Efi directory into the ESP root.
      Btw.: This is a EDKII shell, that comes with some functions, which are needed by the nsh scripts I used for changing rEFInd’s configuration from the boot menu.


      This is a round up of the changes I made, but after some more testing I will create a fork on GitHub.
      Until then I can provide a patch against the current refind source, if someone is interested.

      rEFInd 0.11.2-enhanced

      Changes / Additions

      A. Configuration

      rEFInd is showing a message while scanning for devices.
      To disable this message use:
      hide_scan_msg 1


      Boot Splash is an extra banner used only with timeout -1
      This banner is splashing centered at the boot screen.
      boot_splash banners/banner-black.png


      Color Mode can be any combination from the following
      0=off
      1=icon_auto, 2=icon_value
      4=font_auto, 8=font_value
      16=menu_auto, 32=menu_value
      64=back_value

      color_mode 0 <- function is disabled (default)
      color_mode 21 <- icons, text and selections are tinted automatic
      background color from the banner
      color_mode 85 <- icons, text and selections are tinted automatic
      background color from value (for transparent banner)
      color_mode 101 <- icons, text are tinted automatic
      menu / selection color from value
      background color from value (for transparent banner)

      *_auto generates the color from the current background color
      *_value enables the corresponding rgb(a)_color
      rgba colors are in hex RED, GREEN, BLUE, ALPHA
      rgb colors are in hex RED, GREEN, BLUE

      rgba_color_icon f3,f3,f3,5e
      rgba_color_menu d3,d3,d3,5e
      rgba_color_font d3,d3,d3,5e
      rgb_color_back 0c,6f,b8
       
      Space between icons in pixel
      # big-icons(0-256) small-icons(0-64) y-spacing(0-64) icon_spacing 64 32 24  B. Behaviour

      The unmodified rEFInd is scanning all devices at start.
      Then it loads the drivers if any detected and scans the devices again.
      This is good for Mac's but we want to load the drivers for sure, so I change this a little.
      Now rEFInd only scans for the ESP to know it's location.
      Then it reads the config, load the drivers and start scanning devices.

      Also this version is able to detect the 'macOS Install Data'.
      This is necessary for installing and updating macOS on partitions formatted with apfs.

      New embed banner, arrows and selections.
      New embed font (Ubunutu-Mono 18pt and 28pt).
      New os_icons from https://github.com/munlik/refind-theme-regular
      New tool and function icons.
      Visual changes for creating the boot entries.
      Changed icon spacing
      And some more ...
       
      Update (14.12.07):
      - adaptable icon spacing
      - apfs.efi from macOS 10.13.2
       
       
      Have Fun!
       
      rEFInd-0.11.2-enhanced.zip
    • By sarkdavidson
      Specs: 
      Motherboard: B85M-D3H rev1.1  E3 1231 v3  Nvidia K620  BCM94331CD  
      Attached files work perfectly on 10.12.6. (Including DSDT/SSDT, BIOS ROM, Kexts)
      Ethernet, Wi-Fi, Bluetooth, Audio all work perfectly. 
       
      Ethernet Built-in Failed. (RealtekRTL8111.kext placed in EFI ) While on High Sierra (10.13.1, HFS+), Ethernet can be built in after reflashing Ozmosis ROM and clean installation, after which I logged in iMessage (Successfully), tried to plug in BCM94331CD and restarted. Then RTL8111 disappeared in the System Report. I wonder why? I'm a newbie to Ozmosis... : ( 
       
       
      Audio Built-In Failed. VoodooHDA works on 10.13.1, but it looks not stable and affects my Graphics card performance sometimes (Not for sure)
      I'd like to use AppleALC.kext with DSDT to build in audio. 
       
      I've tried all Layout-Id listed here (https://github.com/vit9696/AppleALC/tree/master/Resources/ALC892). Device (HDEF) { Name (_ADR, 0x001B0000) Method (_PRW, 0, NotSerialized) { Return (Package (0x02) { 0x0D, 0x05 }) } Method (_DSM, 4, NotSerialized) { Store (Package (0x04) { "layout-id", Buffer (0x04) { 0x77, 0x03, 0x00, 0x00 }, "PinConfigurations", Buffer (Zero) {} }, Local0) DTGP (Arg0, Arg1, Arg2, Arg3, RefOf (Local0)) Return (Local0) } }  Can anyone tell me what's wrong with my DSDT.aml or Ozmosis ROM? and how to fix it.
      Please.
       
       
       
       
       
       
    • By Si Vis Pacem
      I am running HS with Ozmosis and managed to forget to set boot mode to single user before latest HS update and due to me needing to add my R9 390 manually into the two relevant kexts - despite using WhatEverGreen - I was of course greeted by my display going black.
       
       
      Solution:
       
       
      Go into EDK-shell and change boot-args. As far as my limited knowledge of it goes, setvar only accepts HEX values.
       
       
      So
      setvar boot-args=2D73 will set your boot-args to "-s" and it worked.
       
       
      Hope that might come handy for someone in a similar situation.
×