Jump to content
xpamamadeus

Ozmosis

6,132 posts in this topic

Recommended Posts

Advertisement

in GM INSTALLTION:

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

in my real macbook pro with GM

 

MBP133

 

$nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures

$nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures >%f5%0f%fd

 

4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask ?%ff%1f%ff

 

FF:0xFD0FF53E

FFM:0xFF1FFF3F
 
??????????????????????
=.=

Share this post


Link to post
Share on other sites

Maybe the best way is to load both apfs & Ozmosis from disk with correct order:

 

bcfg driver add 0 apfs.efi "apfs"
bcfg driver add 1 Ozmosis.efi "Ozmosis"
Or create a driver to load apfs.efi from disk before Ozmosis, after screen fully initialized (optional to block text output while loading apfs.efi by overriding EFI_TEXT_STRING).

Please..

I think i can make that happen and prepare a driver that first loads afps.efi and then ozmosis.efi in that order both from disk. Making them load from a firmware volume however is a little more tricky. For one you would have to somehow nuder both files so they dont auto load when inside the firmware. Wonder if telling genffs theyre efi_applications is enough to cripple that. Then you load both files both files manually in the driver from firmware should work.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

I extract the "bootloader" from VM,i inseart it into Z97-D3H,but it not work,some bigone teach me,pl

 

 

new.zip

 

 

 

 

the MacMiscDxe looks like ozmosis

 

 

someone teach me,help me

 

 

:(

 

 

@cecekpawon

@crusher.

Edited by craike

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Here you go:

here

 

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?

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

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.

 

 

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.

 

 

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

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

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





    • 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
×