Ozmosis

ammoune78 · July 5, 2017

For who want to add a simple knowledge about Intel ACPICA Tools

MakAsus · July 5, 2017

cecekpawon removed the linked kextpatcher.efi, I don't know if i have permission to post it again!

kextpatcher.efi doesn't need to be on your BIOS file but instead, put it in Efi/ Oz/ kextpatcher.efi. Your ATI 5770 can be flashed easily with the help of the guide that cecekpawon posted to you, just make sure that:

- if your VBIOS comes from a dump, you must remove the end padding, so that the flasher doesn't complain about the big size of the file.

- make sure you don't remove extra data when removing padding.

- make sure the new size is not a problem. To do so, check the size of the VBIOS dump = this is the size of the chip.

Or go to SAPPHIRE support, login or create a new account, create a new ticket for your G-Card, and make a request for the last ROM update, with this one you can you should have more free space.

I'm trying to modify Sapphire Vapor-X HD 5770 bios downloaded from Sapphiretech. But Junipers have a small 128 KiB Flash ROM, and the modded ROM was around 136 KiB, so I couldn't flash it. I have not heard about successful modifications of this card. I sent a request in support of the manufacturer and I'm waiting for an answer.

davidm71 · July 5, 2017

In my opinion, disable this option via DMIEDIT.exe, or leave your BIOS as is if it worked with HS! Or you will have a headache, forget to mod it about 2 weak or month, then try again!

I just checked with AMIBCP and the VIA1394 option was disabled from beginning so maybe thats why its saying 'Invalid Firewire guid' because it was turned off and was expecting firewire. As I never use Firewire I suppose my next step is to remove every Firewire Kext there is. Thanks.

ammoune78 · July 5, 2017

IMO, enable it from amibcp and disable it from the bios settings, because i think now the option are not showed from bios settings

Sent from my iPhone using Tapatalk

davidm71 · July 5, 2017

I'm sorry I meant that the selection choice was set to disable and that the option itself was not neither disabled or enabled.

For example I disabled 'iGPu' selection choice though it still appeared in the menu.

cecekpawon · July 5, 2017

Heres the latest status of current patcher:

- Able to hook ExitBootServices (sorry DF, my bad)

- Able to log to file

- Unable to get to the right address for prelinkinfo, related to relocbase (memfix) I think

Some updates with readme.

0:100 (0:100) | KernextPatcher: Start at 2017.7.5, 17:49:57 (GMT+7)
0:106 (0:006) | Load plist: '\EFI\KernextPatcher.plist' ... Success
0:106 (0:000) | Parsing plist: ... Success
0:106 (0:000) | Found '\EFI\KernextPatcher.plist' : Root = '\', DevicePath = 'PciRoot(0x0)/Pci(0x1D,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045EF5,0x1000,0x64000)'
0:106 (0:000) | KextsToPatch: 2 requested
0:106 (0:000) |  - [00]: AppleHDA (ALC892 - 1) | MatchOS: 10.12 | BinPatch | len: 4
0:106 (0:000) |  - [01]: com.apple.driver.AppleHDA (ALC892 - 2) | BinPatch | len: 4
0:106 (0:000) | KernelToPatch: 1 requested
0:106 (0:000) |  - [00]: startupExt | patch disabled, skip
0:151 (0:045) | StartImage (C8907A18)
0:151 (0:000) | FilePath: \EFI\oz2.efi
0:151 (0:000) | ImageBase: CB8DD000 - CB939360 (5C360)
4:088 (3:936) | StartImage (C7323598)
4:088 (0:000) | FilePath: \System\Library\CoreServices\boot.efi
4:088 (0:000) | ImageBase: A955C000 - A95E9000 (8D000)
4:132 (0:043) | OSVersion: 10.12.5 | BuildVersion: 16F73
4:729 (0:596) | KernelAndKextPatcherInit: Start
4:734 (0:005) | Found mBootArgs at 0xBB44A000
4:734 (0:000) | RelocBase: 0xB86E9000
4:734 (0:000) | Found 64 bit kernel at 0xB88E9000
4:735 (0:000) | Loaded Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 | VersionMajor: 16 | VersionMinor: 6 | Revision: 0
4:735 (0:000) | Cached: Yes
4:735 (0:000) | KernelAndKextPatcherInit: End
4:735 (0:000) | Filtering KextPatches:
4:735 (0:000) |  - [00]: AppleHDA (ALC892 - 1) | BinPatch | [MatchOS: 10.12 | MatchBuild: All] ==> allowed
4:735 (0:000) |  - [01]: com.apple.driver.AppleHDA (ALC892 - 2) | BinPatch | [MatchOS: All | MatchBuild: All] ==> allowed
4:735 (0:000) | AnyKextPatch: driverAddr = B983C000, driverSize = F000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:735 (0:000) | AnyKextPatch: driverAddr = B9893000, driverSize = 1D000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:736 (0:000) | AnyKextPatch: driverAddr = B98E7000, driverSize = 152000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:740 (0:003) | AnyKextPatch: driverAddr = B9A39000, driverSize = 109000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Success : 2 replaces done
4:743 (0:003) | AnyKextPatch: driverAddr = B9A39000, driverSize = 109000 | AnyKext = com.apple.driver.AppleHDA (ALC892 - 2) | Binary patch | Success : 2 replaces done
4:845 (0:102) | AnyKextPatch: driverAddr = B86E9000, driverSize = 0 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:866 (0:020) | AnyKextPatch: driverAddr = BAFCE000, driverSize = BB436370 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:877 (0:011) | KernextPatcher: End

bs0d · July 5, 2017

Clover has a symbol based patcher now eh ?

cecekpawon · July 5, 2017

Erghm, officially no lord.. was roughly mixed from Bareboot / Revoboot / KernelPatcher :lol:

bs0d · July 5, 2017

~~i dont see symbol based patching in any of those care to link ?~~

ignore that.

Edited July 5, 2017 by bs0d

MakAsus · July 6, 2017

Some updates with readme.

0:100 (0:100) | KernextPatcher: Start at 2017.7.5, 17:49:57 (GMT+7)
0:106 (0:006) | Load plist: '\EFI\KernextPatcher.plist' ... Success
0:106 (0:000) | Parsing plist: ... Success
0:106 (0:000) | Found '\EFI\KernextPatcher.plist' : Root = '\', DevicePath = 'PciRoot(0x0)/Pci(0x1D,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045EF5,0x1000,0x64000)'
0:106 (0:000) | KextsToPatch: 2 requested
0:106 (0:000) |  - [00]: AppleHDA (ALC892 - 1) | MatchOS: 10.12 | BinPatch | len: 4
0:106 (0:000) |  - [01]: com.apple.driver.AppleHDA (ALC892 - 2) | BinPatch | len: 4
0:106 (0:000) | KernelToPatch: 1 requested
0:106 (0:000) |  - [00]: startupExt | patch disabled, skip
0:151 (0:045) | StartImage (C8907A18)
0:151 (0:000) | FilePath: \EFI\oz2.efi
0:151 (0:000) | ImageBase: CB8DD000 - CB939360 (5C360)
4:088 (3:936) | StartImage (C7323598)
4:088 (0:000) | FilePath: \System\Library\CoreServices\boot.efi
4:088 (0:000) | ImageBase: A955C000 - A95E9000 (8D000)
4:132 (0:043) | OSVersion: 10.12.5 | BuildVersion: 16F73
4:729 (0:596) | KernelAndKextPatcherInit: Start
4:734 (0:005) | Found mBootArgs at 0xBB44A000
4:734 (0:000) | RelocBase: 0xB86E9000
4:734 (0:000) | Found 64 bit kernel at 0xB88E9000
4:735 (0:000) | Loaded Darwin Kernel Version 16.6.0: Fri Apr 14 16:21:16 PDT 2017; root:xnu-3789.60.24~6/RELEASE_X86_64 | VersionMajor: 16 | VersionMinor: 6 | Revision: 0
4:735 (0:000) | Cached: Yes
4:735 (0:000) | KernelAndKextPatcherInit: End
4:735 (0:000) | Filtering KextPatches:
4:735 (0:000) |  - [00]: AppleHDA (ALC892 - 1) | BinPatch | [MatchOS: 10.12 | MatchBuild: All] ==> allowed
4:735 (0:000) |  - [01]: com.apple.driver.AppleHDA (ALC892 - 2) | BinPatch | [MatchOS: All | MatchBuild: All] ==> allowed
4:735 (0:000) | AnyKextPatch: driverAddr = B983C000, driverSize = F000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:735 (0:000) | AnyKextPatch: driverAddr = B9893000, driverSize = 1D000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:736 (0:000) | AnyKextPatch: driverAddr = B98E7000, driverSize = 152000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:740 (0:003) | AnyKextPatch: driverAddr = B9A39000, driverSize = 109000 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Success : 2 replaces done
4:743 (0:003) | AnyKextPatch: driverAddr = B9A39000, driverSize = 109000 | AnyKext = com.apple.driver.AppleHDA (ALC892 - 2) | Binary patch | Success : 2 replaces done
4:845 (0:102) | AnyKextPatch: driverAddr = B86E9000, driverSize = 0 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:866 (0:020) | AnyKextPatch: driverAddr = BAFCE000, driverSize = BB436370 | AnyKext = AppleHDA (ALC892 - 1) | Binary patch | Error : 0 replaces done
4:877 (0:011) | KernextPatcher: End

Thank you very much, I will test it, As soon as I get to the computer!

xpamamadeus · July 6, 2017

I just checked with AMIBCP and the VIA1394 option was disabled from beginning so maybe thats why its saying 'Invalid Firewire guid' because it was turned off and was expecting firewire. As I never use Firewire I suppose my next step is to remove every Firewire Kext there is. Thanks.

Fix for firewire is here 4 years old but working.

http://www.insanelymac.com/forum/topic/288829-guide-gigabyte-z77x-ud5h-clover-uefi-installtweak-guide/?p=1919030

davidm71 · July 6, 2017

Fix for firewire is here 4 years old but working.

http://www.insanelymac.com/forum/topic/288829-guide-gigabyte-z77x-ud5h-clover-uefi-installtweak-guide/?p=1919030

Thanks I really appreciate that.. Wonder if there is a dsdt fix instead of using a kext? Very cool find. Thank you.

xpamamadeus · July 6, 2017

Thanks I really appreciate that.. Wonder if there is a dsdt fix instead of using a kext? Very cool find. Thank you.

Its not a kext.

Its fixed universal driver for firewire device.

Some of motherboards like asrock have proper fireware but gigabyte and maybe some others not.

davidm71 · July 6, 2017

Its not a kext.

Its fixed universal driver for firewire device.

Some of motherboards like asrock have proper fireware but gigabyte and maybe some others not.

Well its only a cosmetic issue when verbose listings is on. Cant really tell otherwise. Deleted my Via 1394 modules from my firmware fwiw.

Thanks

cecekpawon · July 7, 2017

00:893 00:000 Found Horizontal Theme version 0.1.8 by BlackFrog

~~Is BlackFrog == blackosx?~~ Any other theme for Oz? Thanks

Edited July 7, 2017 by cecekpawon

MakAsus · July 8, 2017

Thank you very much, I will test it, As soon as I get to the computer!

It does not work for me. I do not know what I'm doing wrong. Logs do not create and when loading in the verbose mode nothing displays.

In shell I put this:

fs0:

CD EFI

bcfg driver add 0 KernextPatcher.efi KernextPatcher

cecekpawon · July 9, 2017

Sad but TRUE.. If you have already have Ozmosis in firmware, I can guarantee that will not work for you.
(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage with bcfg.
Take my minimalist setup below as your reference (you can run it from USB drive like me as a test):

.
└── EFI
    ├── KernextPatcher.efi
    ├── KernextPatcher.plist
    ├── KernextPatcherLog.txt
    ├── Oz
    │   ├── Acpi
    │   │   ├── Dump
    │   │   └── Load
    │   │       ├── SSDT-1.aml
    │   │       └── SSDT-2.aml
    │   ├── Darwin
    │   │   └── Extensions
    │   │       └── Common
    │   │           └── FakeSMC.kext
    │   │               └── Contents
    │   │                   ├── Info.plist
    │   │                   └── MacOS
    │   │                       └── FakeSMC
    │   └── theme.bin
    └── Ozmosis.efi

Start shell and type following commands:

# list drivers

bcfg driver dump

Option: 00. Variable: Driver0000
  Desc    - KernextPatcher
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\KernextPatcher.efi
  Optional- N
Option: 01. Variable: Driver0001
  Desc    - Ozmosis
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\Ozmosis.efi
  Optional- N

# remove any existing drivers

bcfg driver rm 0
...

# register drivers

fs0:
cd EFI
bcfg driver add 0 KernextPatcher.efi "KernextPatcher"
bcfg driver add 1 Ozmosis.efi "Ozmosis"

** Need to register KernextPatcher before Ozmosis
** To reorder the sequence: bcfg driver mv 0 1
** If succeed, patcher will create "KernextPatcherLog.txt" log-file

MakAsus · July 10, 2017

Sad but TRUE.. If you have already have Ozmosis in firmware, I can guarantee that will not work for you.

(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage with bcfg.

Take my minimalist setup below as your reference (you can run it from USB drive like me as a test):

.
└── EFI
    ├── KernextPatcher.efi
    ├── KernextPatcher.plist
    ├── KernextPatcherLog.txt
    ├── Oz
    │   ├── Acpi
    │   │   ├── Dump
    │   │   └── Load
    │   │       ├── SSDT-1.aml
    │   │       └── SSDT-2.aml
    │   ├── Darwin
    │   │   └── Extensions
    │   │       └── Common
    │   │           └── FakeSMC.kext
    │   │               └── Contents
    │   │                   ├── Info.plist
    │   │                   └── MacOS
    │   │                       └── FakeSMC
    │   └── theme.bin
    └── Ozmosis.efi

Start shell and type following commands:

# list drivers

bcfg driver dump

Option: 00. Variable: Driver0000
  Desc    - KernextPatcher
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\KernextPatcher.efi
  Optional- N
Option: 01. Variable: Driver0001
  Desc    - Ozmosis
  DevPath - PciRoot(0x0)/Pci(0x1d,0x0)/USB(0x1,0x0)/USB(0x5,0x0)/HD(1,MBR,0x00045ef5,0x1000,0x64000)/\EFI\Ozmosis.efi
  Optional- N

# remove any existing drivers

bcfg driver rm 0
...

# register drivers

fs0:
cd EFI
bcfg driver add 0 KernextPatcher.efi "KernextPatcher"
bcfg driver add 1 Ozmosis.efi "Ozmosis"

** Need to register KernextPatcher before Ozmosis

** To reorder the sequence: bcfg driver mv 0 1

** If succeed, patcher will create "KernextPatcherLog.txt" log-file

OK, I understood. But I was flushing KernextPatcher into the BIOS and it did not work also. Should I KernextPatcher.plist so flush in BIOS to make it work? Or from the BIOS it can’t work at all? Thanks!

netzgiest · July 10, 2017

I think try to change GUID on 11xxx-xxxx-xxxx ... and flash it before ozmosis.efi, maybe then it will be loaded first. try use kext2ffs for kernext.plist as well as ozmosisdefaults.plist

cecekpawon · July 10, 2017

I am not worried about bricking the board, how about you?

Latest precompiled binary can be found here.

ammoune78 · July 10, 2017

OK, I understood. But I was flushing KernextPatcher into the BIOS and it did not work also. Should I KernextPatcher.plist so flush in BIOS to make it work? Or from the BIOS it can’t work at all? Thanks!

You just had to read, nothing more:

If you have already have Ozmosis in firmware, I can guarantee that will not work for you.

(For now) To use this patcher with Ozmosis, you need to load patcher & Ozmosis from your storage (HDD Only) with bcfg.

Again this schema explain it:

└── EFI

├── KernextPatcher.efi

├── KernextPatcher.plist

├── KernextPatcherLog.txt

└── Ozmosis.efi

And this the only way to use it and not inside the BIOS, to avoid problems after flashing

elviejo · July 11, 2017

With the new beta 3 my ozmosis no longer detect the high sierra apfs, I have to boot to sierra and select high sierra as a startup disk to boot it. I'm going to try with the new apfs.efi to see what happen.

elviejo · July 11, 2017

Back in business with the new apfs. :thumbsup_anim:

IronManJFF · July 11, 2017

Will update to Beta 3 tonite ..

griven · July 11, 2017

Has anyone found a way to suppress the APFs Driver debug output ?!

@cecekpawon just tried out your KernextPatcher for the moment being only with one kernel patch (XCPM on Ivy for HighSierra) and it really works. Great job man I´ll add more patches and report back if something does not work as expected (Patcher added via bfcg Oz in ROM). Thank you very much for this great thing

Ozmosis

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites