Jump to content
xpamamadeus

Ozmosis

6,140 posts in this topic

Recommended Posts

Advertisement

Besides the translator fun has anyone found a way to implement APFS more Apple like?

 

I browsed some of their ROM Images and found something which identifies itself as APFS Jumpstart Driver which I extracted and attached here. This file is about 12KB in weight and it´s the only reference to APFS I was able to find in Apples FD Images (sure I am a noob at all)...

 

Further on the shortened debug output of APFS.EFI shows that the driver claims that the Metadata indicates a JumpStart Record but the APFS Driver was not started from this Volume which I think is plausible since we start it directly from the ROM rather than from the Volume it should be nested on. My best guess is that APFS.EFI is not designed to be part of the ROM in fact it seems like it is designed to rest on the effected partitions and being started during the initialisation sequence via the Jumpstart Driver which ist part of Apples Firmware. Do you think it´s possible to find a similar mechanism for our OZ Roms since APFS.EFI is pretty heavy in weight and a lot of former working ROMS will become unusable with APFS and HighSierra if we don't find a better way as simply drop APFS.EFI into rom...

CFFB32F4-C2A8-48BB-A0EB-6C3CCA3FE847_apfs.ffs.zip

Share this post


Link to post
Share on other sites

in 10.13 release

EFIPayloads:

 - IM101.88Z.00CF.B00.1708080133
 - IM111.88Z.0037.B00.1708080241
 - IM112.88Z.005B.B00.1708080439
 - IM121.88Z.004D.B00.1708080012
 - IM131.88Z.010F.B00.1708080805
 - IM141.88Z.0123.B00.1708211404
 - IM142.88Z.0123.B00.1708211454
 - IM143.88Z.0123.B00.1708211454
 - IM144.88Z.0183.B00.1708080656
 - IM151.88Z.0211.B00.1708080656
 - IM161.88Z.0212.B00.1708080033
 - IM162.88Z.0212.B00.1708080033
 - IM171.88Z.0110.B00.1708080012
 - IM181.88Z.0151.B00.1708080034
 - IM183.88Z.0151.B00.1708080034
 - MB101.88Z.0154.B00.1708080122
 - MB61.88Z.00CB.B00.1708080203
 - MB71.88Z.003D.B00.1708080317
 - MB81.88Z.0168.B00.1708080033
 - MB91.88Z.0159.B00.1708080011
 - MBA31.88Z.0067.B00.1708080355
 - MBA41.88Z.007B.B00.1708072159
 - MBA51.88Z.00F4.B00.1708080803
 - MBA61.88Z.0103.B00.1708080653
 - MBA71.88Z.0171.B00.1708072210
 - MBP101.88Z.00F2.B00.1708080809
 - MBP102.88Z.010B.B00.1708080805
 - MBP111.88Z.0142.B00.1708080655
 - MBP112.88Z.0142.B00.1708080655
 - MBP114.88Z.0177.B00.1708080033
 - MBP121.88Z.0171.B00.1708080033
 - MBP131.88Z.0212.B00.1708080127
 - MBP132.88Z.0233.B00.1708080034
 - MBP133.88Z.0233.B00.1708080034
 - MBP141.88Z.0167.B00.1708080034
 - MBP142.88Z.0167.B00.1708080034
 - MBP143.88Z.0167.B00.1708080129
 - MBP61.88Z.005A.B00.1708072217
 - MBP71.88Z.003D.B00.1708080058
 - MBP81.88Z.004D.B00.1708080655
 - MBP91.88Z.00D7.B00.1708080744
 - MM41.88Z.0045.B00.1708072325
 - MM51.88Z.007B.B00.1708080744
 - MM61.88Z.010B.B00.1708080649
 - MM71.88Z.0224.B00.1708080033
 - MP61.88Z.0120.B00.1708080652


SMCJSONs:

 - Mac-031B6874CF7F642A: 2.14f24
 - Mac-189A3D4F975D5FFC: 2.16f68
 - Mac-27ADBB7B4CEE8E61: 2.15f7
 - Mac-2BD1B31983FE1663: 2.19f12
 - Mac-35C1E88140C3E6CF: 2.12f143
 - Mac-35C5E08120C7EEAF: 2.24f32
 - Mac-3CBD00234E554E41: 2.18f15
 - Mac-42FD25EABCABB274: 2.22f16
 - Mac-473D31EABEB93F9B: 2.36f97
 - Mac-65CE76090165799A: 2.33f10
 - Mac-66E35819EE2D0D05: 2.37f20
 - Mac-77EB7D7DAF985301: 2.17f7
 - Mac-7DF21CB3ED6977E5: 2.13f15
 - Mac-81E3E92DD6088272: 2.21f92
 - Mac-937CB26E2E02BB01: 2.27f2
 - Mac-9AE82516C7C6B903: 2.35f105
 - Mac-9F18E312C5C2BF0B: 2.26f2
 - Mac-A369DDC4E67F1C45: 2.31f36
 - Mac-A5C67F76ED83108C: 2.38f7
 - Mac-B809C3757DA9BB8D: 2.34f2
 - Mac-BE0E8AC46FE800CC: 2.25f87
 - Mac-DB15BD556843C820: 2.33f10
 - Mac-E43C1C25D4880AD6: 2.28f7
 - Mac-F60DEB81FF30ACF6: 2.20f18
 - Mac-FA842E06C61E91C5: 2.23f11
 - Mac-FFE5EF870D7BA81A: 2.32f20


FirmwareFeatures(Mask):

 - IM144.88Z.0183.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf00fe137
 - IM151.88Z.0211.B00.1708080656: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xf80fe137
 - IM171.88Z.0110.B00.1708080012: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - IM181.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - IM183.88Z.0151.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MB101.88Z.0154.B00.1708080122: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MB91.88Z.0159.B00.1708080011: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MBP131.88Z.0212.B00.1708080127: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP132.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP133.88Z.0233.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MBP141.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP142.88Z.0167.B00.1708080034: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe136
 - MBP143.88Z.0167.B00.1708080129: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xfc0fe13e
 - MP61.88Z.0120.B00.1708080652: FirmwareFeaturesMask=0xff1fff3f | FirmwareFeatures=0xe80fe136

good luck

Share this post


Link to post
Share on other sites

Hi, as far you know is there some problems with apfs and SSD without apple firmware?
I read over the web that using apfs on non apple SSD, you could corrupt filesystem because some control is implemented into firmware, and non apple ssd don't have this kind of "features" implemented 

did you heard something about it? 

Many thanks 

Share this post


Link to post
Share on other sites

@Aigors I guess you mean Pike´s post about APFS which he wrote on a pretty early beta stage of APFS Introduction am I right? As far as we know by now there is nothing special in Apple SSD Firmware about APFS at least not as Apple added Support for third Party NVME Vendors with HighSierra...

 

 

 

Right it has already been discussed but it has been discussed in a clover flavoured context and I guess we have to rethink about it in terms of OZ. If Apple is able to implement kind of a JumpStart driver into their ROM Images which takes care about loading and connecting APFS.EFI I guess it should be possible to do the same with OZ. Sure I am no Coder and do not understand the underlaying mechanisms but if it works for Macs why should it not work for us?

Share this post


Link to post
Share on other sites

@Aigors I guess you mean Pike´s post about APFS which he wrote on a pretty early beta stage of APFS Introduction am I right? As far as we know by now there is nothing special in Apple SSD Firmware about APFS at least not as Apple added Support for third Party NVME Vendors with HighSierra...

 

 

 

 

Right it has already been discussed but it has been discussed in a clover flavoured context and I guess we have to rethink about it in terms of OZ. If Apple is able to implement kind of a JumpStart driver into their ROM Images which takes care about loading and connecting APFS.EFI I guess it should be possible to do the same with OZ. Sure I am no Coder and do not understand the underlaying mechanisms but if it works for Macs why should it not work for us?

Griven, thank you: there's a bios from you on Hackintosh-forum.de for my board, GA Z97X UD3H. Do I have to assume that I'll be able to install High Sierra in APFS or not as per your questions about the implementation of this new file system in the Apple ROMs?

Share this post


Link to post
Share on other sites

The mentioned rom contains everything needed to install and run HighSierra :D

I asked about the implementaion of APFS because it´s not best or smartest way to just insert that heavy file into the Rom.

Share this post


Link to post
Share on other sites
Hi there,

 

Can someone help? I collected all files, but I have error in mmtool "error getting firmware information" (

Motherboard GA-H97M-D3H

"CORE_DXE" exported and compressed normally. But it does not load back(

I thought that there was not enough space, but no (

 

Help someone put ffs files in to the bios file.

 


 

Thank you!

Share this post


Link to post
Share on other sites

Tip: Use Uefitool.

 

Have this:

 

Snymok_ekrana_2017_09_30_v_10_59_00_DP.p

 

 

And I have no active buttons to "remove" and replace in the program (

 

Please help to assemble the firmware. Ideas are already over(

Share this post


Link to post
Share on other sites

@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

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 vit9696
      OpenCorePkg / Documentation / Configuration Template / Bugtracker   Discussion and installation should be done in a separate thread! This thread is for development only!
      Current status as of April 2019: Support for UEFI and DuetPkg (legacy) booting APFS and HFS+ compatibility ACPI patcher (adding, dropping, binary patching, relocation) Apple-compatible bless implementation DeviceProperties injection DataHub and SMBIOS generation Symbolic kext and kernel patcher Direct kext injection/patching/blocking within prelinkedkernel Installation/Recovery/FileVault 2 support  Configuration in config.plist with open documentation Simple boot picker for quick launch Direct boot from dmg images  
      Known defects (for 02.05.2019): Custom memory configuration is unsupported, and provided as is. Full secure boot compatibility is in progress. Hibernation support is missing.  
      For those, who are not familiar with the history, OpenCore is a project initially born in HermitCrabs Lab that unfortunately almost died before its birth. This release is both a rebirth and a complete rewrite of OpenCore, which brings a number of new ideas, and tries to preserve the smart moves incorporated by iNDi and his team. Other than that, I wish to express my deepest words of gratitude to Acidanthera and WWHC members: your participation was and remains the key for project success, and you are simply the best.
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • By ErmaC
      Slice is glad to present a new EFI bootloader.
      CLOVER
      Now version 2 rEFIt based.


      It is open source based on different projects: Chameleon, rEFIt, XNU, VirtualBox. The main is EDK2 latest revision.
      I also want to thank all who help Slice with the development. Credits and copyrights remain in the sources.
      http://cloverefiboot.sourceforge.net/

      Main features:


      If you have a question please provide outputs from DarwinDumper (formed from Trauma tool). Thanks Trauma!
      Continued by blackosx and STLVNUB.
      CloverGrower Downloads Installation How to do UEFI boot How to use - common words Calculator for Automatic DSDT fix Instructions for GraphicsInjector ATIConnector patching Any kexts patching with some Samples CustomEDID Hiding unnecessary menu entries Instruction for DSDT corrections to do DeviceInjection works Development Themes About kexts injection Instructions for P- and C-states generator Patching DSDT to get Sleep working CPU settings and geekbench ACPI tables loading DSDTmini Custom SMBios F.A.Q. iCloudFix Using mouse. How to make orange icons to be metallic How to make software RAID (by Magnifico) How to modify InstallESD.dmg (by shiecldk) Config.plist settings Using extra kexts and skipping kernelcache Choosing EFI drivers Configuration files Automatic config.plist creating Custom DSDT patches How to do sleep/wake working with UEFI BOOT DeviceID substitution (FakeID) Using Custom OS Icons Hibernation Floating regions Error allocating pages while starting OS -----------------
    • By ciriousjoker
      TLDR:
      I'm trying to boot MacOS on a Chromebook without UEFI. I'm stuck at getting the bootloader (Chameleon/Clover) to work.  
      My setup / context:
      I have an Acer Chromebook Spin 13.
      Available ports:
      2 x USB-C 1 x USB-A 3.0 MicroSD Slot No USB A 2.0 (I've read that Clover has problems with USB 3.0) Firmware:
      There's no UEFI firmware available and by default, it doesn't even allow booting anything other than ChromeOS. Thanks to MrChromebox (big shoutouts!), I flashed a custom legacy bios that allows me to boot anything linux related. This bios is flashed into the RW_LEGACY section of the existing bootloader (coreboot afaik) and doesn't have any configuration options. If I have to change a setting, I could try compiling his bios payload myself with the specific setting enabled.  
      What I've tried so far:
      Chameleon attempts:
      Only selected setting was "Install chameleon on the chosen path", rest was unselected.
       
      1 - Install chameleon first without restoring the basesystem:
      Output:
      > boot0: GPT
      > boot0: done
      (hangs; pressing power button once shuts down
      Chameleon installation log is attached as "Chameleon_Installer_Log_BEFORE".
       
      2 - Install Chameleon after restoring the base system:
      Output:
      > boot0: GPT
      > boot0: GPT
      > boot0: doneboot1: /boot       <- Exactly like that, no line break in between
      (hangs; pressing power button once shuts down)
       
      I haven't been able to reproduce #2 after wiping the drive and doing the same thing again. Subsequent attempts have resulted in either #1 of either Chameleon or Clover.
      Chameleon installation log is attached as "Chameleon_Installer_Log_AFTER".
       
      Clover attempts:
      I tried multiple settings and configurations, but all of them boiled down to either one of these.
       
      1 - Doesn't do anything, just hangs at "Booting from usb..."
      2 - Boots into the blue/grey mode as shown in the attached images.
      According to MrChromebox, this could be an old Tianocore DUET It doesn't detect anything (cpu frequency, ram, partitions or disks)  
      I've read pretty much every article, github readme and other types of documentation for coreboot, tianocore, clover, chameleon and MrChromebox' rw_legacy payloads and right now, I'm totally clueless as to what to try next...
       
      A few questions that came up:
      Why does chameleon hang? What is it looking for, /boot was clearly written to the disk by the Chameleon installer? What exactly is the blue/grey image? According to MrChromebox, it could be Tianocore DUET Where does it come from? Clover? The mainboard itself? Why does the blue/grey thing not detect my processor frequency or any partitions/drives? Can I use some sort of DUET bootloader to chainload Clover?  
      If you guys could answer any of them or if you have any other guesses or information as to what's happening, I'd be really happy!
      Chameleon_Installer_Log_BEFORE.txt
      Chameleon_Installer_Log_AFTER.txt





×