Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

salvatorepolito
salvatorepolito
Posted
Posted

I've done some progress..

I took the german ozmosis bios for my board and applied MATS fix, replaced the original ssdt and dsdt with my own and also added some kext: Lilu, WhateverGreen, AppleIntelE1000e, USBInjector and AppleALC.

I also replaced SMCEmulator and its sensors with FakeSMC.

 

Now I got an error message in UefiTool: "PE32 image wit invalid DOS signature" on some of the new kexts. 

Can someone look at this bios before I flash it ?

 

https://www.dropbox.com/s/nnj554bfd1xm78x/Z87XUD4H-10b-Sierra_personalMod.rom.zip?dl=0

Link to comment
Share on other sites
crusher
crusher
Posted
Posted

I've done some progress..

I took the german ozmosis bios for my board and applied MATS fix, replaced the original ssdt and dsdt with my own and also added some kext: Lilu, WhateverGreen, AppleIntelE1000e, USBInjector and AppleALC.

I also replaced SMCEmulator and its sensors with FakeSMC.

 

Now I got an error message in UefiTool: "PE32 image wit invalid DOS signature" on some of the new kexts. 

Can someone look at this bios before I flash it ?

 

https://www.dropbox.com/s/nnj554bfd1xm78x/Z87XUD4H-10b-Sierra_personalMod.rom.zip?dl=0

attach kexts here and I can compress for you...

Link to comment
Share on other sites
medallo
medallo
Posted
Posted

greetings.

I'm sorry, but I don't understand a lot of things because it's my turn to translate.
I'm at 10.12.6.
For 10.13 what do I need to add and what do I need to remove from my bios with ozmosis?
or is it better to wait until the definite ozmosis comes out for 10.13?
Thanks for any help.

post-433991-0-06085100-1506106048_thumb.png

Link to comment
Share on other sites
cecekpawon
cecekpawon
Posted
Posted

Dont know what to say. Are you trying to load MacMiscDxe along with Ozmosis, or? But why? How can they read your config, based on what? Ozmosis will set everything you needs to boot OSX (assumed like MacMiscDxe from Hopper, except "VmwPkg/MacMiscDxe/ApfsHelper.c"). Is that open-source? I never use vmware, sorry.

Link to comment
Share on other sites
D1ves
D1ves
Posted
Posted

Dont know what to say. Are you trying to load MacMiscDxe along with Ozmosis, or? But why? How can they read your config, based on what? Ozmosis will set everything you needs to boot OSX (assumed like MacMiscDxe from Hopper, except "VmwPkg/MacMiscDxe/ApfsHelper.c"). Is that open-source? I never use vmware, sorry.

sorry for my bad english

it's not open-source,

because vmware-unlock can install and boot macos without any bootloader and fakesmc,so was VM ESXI,so i want to know how it works

so i extract this from vmware,and read with hopper,i found MacMiscDxe look's like a bootloader. the VmwSmbios look's like fakesmc and Model setting.the 1 to 10 is some config and kexts,like nullpower  USB ,and so on.the others you know like hfsplus.

so i inseart this into z97 and flash it,when it reboot,it change nothing, no hfs partition,no macos,windows os work well

i wanna know why this didn't work

 

this is the rom from vmware

vmx-efi64.zip

thanks

Link to comment
Share on other sites
davidm71
davidm71
Posted
Posted

Thanks. I've got a problem. 

After flashing this ozmosis bios my board couldn't boot, it does not post to bios. Could this be related to my dsdt and ssdt?

Also if I want to start from a stock bios how I can obtain more free space?

Could be because of CSM being enabled or disabled, Also could be the Video card. On my Z87 ud5h board i have to you Amibcp to toggle the default CSM setting or else I got stuck on a black screen. Also helped to update the video cards gop as a last resort but try the onboard motherboard video port first.

Link to comment
Share on other sites
salvatorepolito
salvatorepolito
Posted
Posted

Could be because of CSM being enabled or disabled, Also could be the Video card. On my Z87 ud5h board i have to you Amibcp to toggle the default CSM setting or else I got stuck on a black screen. Also helped to update the video cards gop as a last resort but try the onboard motherboard video port first.

I've flashed an uefi gop vbios some time ago. Also I need ti disabile csm to get osx boot. As I said, I was forced to switch to clover because of black screens with this vga. But I was having those after bois load (I was ablw to chance bios configs), now I couldn't enter.

 

 

Inviato dal mio iPhone utilizzando Tapatalk

 

Ps: I'm speaking an orrible english today, sorry

Link to comment
Share on other sites
davidm71
davidm71
Posted
Posted

I've flashed an uefi gop vbios some time ago. Also I need ti disabile csm to get osx boot. As I said, I was forced to switch to clover because of black screens with this vga. But I was having those after bois load (I was ablw to chance bios configs), now I couldn't enter.

 

 

Inviato dal mio iPhone utilizzando Tapatalk

 

Ps: I'm speaking an orrible english today, sorry

I'll tell you what. Send me your last working bios and I'll try to mod it for you. It also may be something in your Oz defaults file in the bios rom. Best guess.

Link to comment
Share on other sites
medallo
medallo
Posted
Posted

Greetings.

 I don't understand several things that I am obliged to translate. 
My bios is working well with 10.12.6. 
To have 10.13 What do i need to add and that I need to remove my bios OZ? Or is it better to wait until a final version of OZ to 10.13? Thanks for any help.

post-433991-0-70835100-1506364835_thumb.png

Link to comment
Share on other sites
Si Vis Pacem
Si Vis Pacem
Posted
Posted

@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.

 

 

post-481866-0-99371600-1506406252.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.

 

 

post-481866-0-01629100-1506406438_thumb.png

 

 

Save As different file ;) and flash it.

 

 

Link to comment
Share on other sites
elviejo
elviejo
Posted
Posted

@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?

Link to comment
Share on other sites
THe KiNG
THe KiNG
Posted
Posted

MY HUMBLE OPINION-The Theme Is Complete Nonsense.

EFI Came Up With Intel. UEFI then modified, easier and better, "not by the EFI boot for iron with Intel."

 

What?

That happen when you use google to translate from chinese...

This one I got it today in the mail:

 

 

You are free to replace our configuration device, we also provide technical support to help, why do you turn a blind eye And I do not agree with your practice, but you are bent on. I feel that I can not help you.

I am still trying to understand what he want to say ROFL...

  • Like 3
Link to comment
Share on other sites
griven
griven
Posted
Posted

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

  • Like 3
Link to comment
Share on other sites
D1ves
D1ves
Posted
Posted

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

Link to comment
Share on other sites
Aigors
Aigors
Posted
Posted

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 

Link to comment
Share on other sites
griven
griven
Posted
Posted

@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?

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