Jump to content
xpamamadeus

Ozmosis

6,187 posts in this topic

Recommended Posts

 

Thank you very much

the AcpiPatcher seems to work well.

 

two things:

 

1.unlike clover, it also patch the ssdt in /EFI/OZ/ACPI/LOAD

 

2.the AcpiPatcherLog.txt not showing anything related to acpi

00:100 (00:100) | KernextPatcher (rev 93): Start at 2017.10.14, 15:47:52 (GMT+0)00:100 (00:000) | Running from: MemoryMapped(0xB,0xC0672004,0xC14C8003)/FvFile(99665243-5AED-4D57-92AF-8C785FBC7558)
00:101 (00:001) | Loaded Plist: PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0)/HD(1,GPT,2F1C32E4-C0E8-4AA8-B446-9083BC297831,0x28,0x64000)\EFI\KernextPatcher.plist
00:101 (00:000) | KextsToPatch: 3 requested
00:101 (00:000) |  - [00]: AppleUSBXHCIPCI (Remove USB limit MacOS HighSierra) | MatchOS: 10.13.x | BinPatch | len: 4
00:101 (00:000) |  - [01]: AppleUSBXHCIPCI (Remove USB limit MacOS Sierra) | MatchOS: 10.12.x | BinPatch | len: 7
00:101 (00:000) |  - [02]: AirPortAtheros40 (Wi-Fi Region to 0x64) | BinPatch | len: 7

Clover patches SSDT as well but in another folder.

Share this post


Link to post
Share on other sites
Advertisement
1.unlike clover, it also patch the ssdt in /EFI/OZ/ACPI/LOAD

 

Clover patches SSDT as well but in another folder.

 

Far as I know, isnt Clover will patch all loaded ssdts unless user decided to drop oem ssdt? >>>

Thats why Clover have this such of messages:

12:627 (00:000) | :: PatchAllSSDT
12:627 (00:000) | Patching Table ID: 'SataTabl' | Len: 0x877
12:627 (00:000) |  - [00]: (GFX0 [to] GFX2) (47465830 -> 47465832) bin not Found / already patched!

Im not sure what 'another folder' is :)

 

2.the AcpiPatcherLog.txt not showing anything related to acpi

 

You may try another build here. Prev it used same instance of Clover Memlog lib.

 

Any way to boot Sierra/High Sierra with SIP enabled?

 

With Oz, sorry I believe no.

 

Ok, whats the trick in getting Oz (my version) to work with High Sierra, 

:king:  :hammer:  :wallbash:  :boxing:  :geek:  :happymac:

Share this post


Link to post
Share on other sites

AcpiPatcher. Sample included.

Thank you very much! Did I correctly understand, that I should to insert AB6CE992-8D17-4C3A-A414-0FEAA3904504.ffs and AcpiPatcher.plist into the Ozmosis, then flash it and place AcpiPatcherLog.tht in the EFI folder for correct use of AcpiPatcher? Or AcpiPatcher.plist should olso be in the EFI folder?

Share this post


Link to post
Share on other sites

Hi cecekpawon,

is one of your extensions able to patch AppleIntelCPUPowerManagement (AsusAICPUPM) dynamically at boot?

With a new hack, I'm using ozmosis.efi from EFI. I got HS installed with the help of NullCPUPowerManagement.kext, then I patched AppleIntelCPUPowerManagement.kext and removed NullCPUPowerManagement.kext to get working PM.
But this way I can't start Recovery...

 

Any help?

Share this post


Link to post
Share on other sites

 

 

Far as I know, isnt Clover will patch all loaded ssdts unless user decided to drop oem ssdt?

 

Clover patches all SSDT's in firmware but not those which are loaded from EFI folder (from my experience).

Both approach are fine of course,

Just mean I can't share same ssdt between Clover and Oz.

 

 

Sent from my ONEPLUS A5000 using Tapatalk

Share this post


Link to post
Share on other sites

You can flash the ffs, but plist must be in one of your EFI folder. Patcher will start to looking its config from self dir / 1st founded ESP (like previously release). PatcherLog.txt will automatically created. I suggest to play safe first by bcfg the driver instead of flashing it. Please reload your current KernextPatcher (if any, due the MemLog problem mentioned above) to work with this AcpiPatcher. >>>

Share this post


Link to post
Share on other sites

is one of your extensions able to patch AppleIntelCPUPowerManagement (AsusAICPUPM) dynamically at boot?

But this way I can't start Recovery...

 

As long the kext is on prelinked, yes. About recovery >>> I dont have HS :)

 

Clover patches all SSDT's in firmware but not those which are loaded from EFI folder (from my experience).

Both approach are fine of course,

Just mean I can't share same ssdt between Clover and Oz.

 

I take a look the source again and yeah you are right. Clover will patch all ssdt and load user ssdt right after. Please take my beer..

I think it could be done, by start patching all loaded OEM tables (or just indexing em all as filters to patch later) immediately after successfully reading user config instead of after exitbootservices, but why?

If I start this proc on exitbootservices I can convinced the loaded image is valid darwin boot.efi to prevent applying patch to other OS, but with another problem Oz already done injecting all user tables.

Do you have any concrete example and its benefit to only patching OEM tables?

Im start thinking to add another plist entry (like drop table) as filters by each signatures to ignored. But man..

Share this post


Link to post
Share on other sites

It's doesn't really matter to me, just one drawback is I need different ssdt for clover and Oz.

 

I use (among others)

GFX0-->IGPU

PEGP-->GFX0

In clover my ssdt is already using the modified devices for injsction.

If I use the same ssdt with Oz I have two devices named IGPU.

So my ssdt with Oz still use PEGP and GFX0

 

Sent from my ONEPLUS A5000 using Tapatalk

Share this post


Link to post
Share on other sites

As long the kext is on prelinked, yes. About recovery >>> I dont have HS :)

 

 

...

 

Yes, I add a boot entry for the recovery with bcfg from shell.

But at boot I got a kernel panic because of the missing patch.

The mb has a locked msr.

Share this post


Link to post
Share on other sites

It's doesn't really matter to me, just one drawback is I need different ssdt for clover and Oz.

 

Yes as I expected. After we were done renaming device name with patcher, our custom ssdt should pointing to wrong device. Thats why I will stick to this way ATM since its make more sense for me to patch all loaded ssdts. But maybe I will find more convenience way later..

 

Yes, I add a boot entry for the recovery with bcfg from shell.

 

You can mount your recovery and check the targeted kext is on prelinkedkernel with LZVN decompressor or check your log with Debug ON to list all kexts. More..

/Volumes/Recovery HD/com.apple.recovery.boot/prelinkedkernel
<key>Preferences</key>
<dict>
  <key>Debug</key>
  <true/>
  <key>SaveLogToFile</key>
  <true/>
</dict>

Share this post


Link to post
Share on other sites

This thread was made by a hacker. Its 'ilegally' taken from QUO bios get shared for everyone. Im bit late to join the party, whereas fun part is on earliest pages on this thread. I believe Ozmosis designed as professional product, but it seem halted for a while before it reaches their main goal.

 

 

I get slap this time, sorry DF, Im just too dumb.

 

About APFS, ATM, why dont we just learn like unsupported mac did? Even real mac, they manually load all required drivers from disk. While most people here refuse to do the same ways.

 

 

Here the related contents from dosdude1s script

hey bro,there is no "APFS Boot Selector.prefPane" and "BOOTX64.efi" in the zip file.

how can i use it??????

Share this post


Link to post
Share on other sites

just found startup.nsh

hey god,i search it ,no result. :P  :P  :P  :P  :P

just found startup.nsh

 

is this ?

echo -off
set StartupDelay 1
set -v efishellmode 1.1.2
set apfsBootUUIDdir ".apfsbootuuid"
set macOSBootFile "System\Library\CoreServices\boot.efi"
set targetUUID "A43465F6-5134-3A38-A3D1-9171AAFB3C02"
for %i run (0 9)
if exist fs%i:\EFI\apfs.efi then
load fs%i:\EFI\apfs.efi
connect -r
map -u
endif
endfor
for %m run (0 9)
if exist "fs%m:\%apfsBootUUIDdir%\%targetUUID%" then
echo "Starting macOS..."
fs%m:\%macOSBootFile%
exit
endif
endfor
for %l in A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
if exist "fs%l:\%apfsBootUUIDdir%\%targetUUID%" then
echo "Starting macOS..."
fs%l:\%macOSBootFile%
exit
else
if %l == Z then
echo "Boot file not found, exiting..."
endif
endif
endfor

This is a complete file:

apfs.zip

 

 

Please tolerate my pending performance :P  :P  :P  :P  :P 

Share this post


Link to post
Share on other sites

You can flash the ffs, but plist must be in one of your EFI folder. Patcher will start to looking its config from self dir / 1st founded ESP (like previously release). PatcherLog.txt will automatically created. I suggest to play safe first by bcfg the driver instead of flashing it. Please reload your current KernextPatcher (if any, due the MemLog problem mentioned above) to work with this AcpiPatcher. >>>

 

So It isn't most suitable for me. Clover patches DSDT.aml in firmware, bat config.plist is located in EFI folder. And I need that config.plist also be in the firmware. But thanks anyway!

Share this post


Link to post
Share on other sites

Any ideas? Who could help my with that

 

Sent from my Nexus 4 using Tapatalk

Share this post


Link to post
Share on other sites

You can flash the ffs, but plist must be in one of your EFI folder. Patcher will start to looking its config from self dir / 1st founded ESP (like previously release). PatcherLog.txt will automatically created. I suggest to play safe first by bcfg the driver instead of flashing it. Please reload your current KernextPatcher (if any, due the MemLog problem mentioned above) to work with this AcpiPatcher. >>>

Hi

flashed the new patchers and now the logs are fine

thanks again, really appreciate your work.

Share this post


Link to post
Share on other sites

same. DSDT has bad header

 

For which MoBo are you trying to?

Dsdt2Bios is not needed for the X99 Board, you can extract DSDT directly for the first Freeform Modules at the bottom of the freeform list inside ROM as: extract Body .aml

 

Keep in mind that Ozmosis will not work for your X99 board exept by chance

Share this post


Link to post
Share on other sites

For which MoBo are you trying to?

Dsdt2Bios is not needed for the X99 Board, you can extract DSDT directly for the first Freeform Modules at the bottom of the freeform list inside ROM as: extract Body .aml

 

Keep in mind that Ozmosis will not work for your X99 board exept by chance

 

exactly, its x99. and I am unable to find that freeform list... exept by chance sounds not impossible

Share this post


Link to post
Share on other sites

exactly, its x99. and I am unable to find that freeform list... exept by chance sounds not impossible

AmiBoardInfo search with UEFITool.

post-608882-0-01536400-1508101590_thumb.png

 

later extrach PE32 body like a bin. Use drag and drop bin file on DSDT2bios and u have DSDT-Original.aml

Share this post


Link to post
Share on other sites

No not, since x99, x100 series Board, they are only in FreeForm modules. Here's how:

 

post-334538-0-86198000-1508102903_thumb.png

 

Select that raw as in the png above, and choose Extract Body then all files and name it xxxx.aml

 

Or here's the extracted one from the 3.20 ROM: DSDT.aml.zip, you can try Ozmosis at your own risk, the ROM is not protected, just add the Ozmosis stuffs.

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 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
    • By cvad
      Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows.
      Special utility from cvad & russian MAC community for new hackintosh users.
       
      BDU_v2.1.2018.023b.zip
      MakeCloverBDUReadyZip.bat.zip
      Enjoy...
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
      BDU_v2.1.2015.016b.zip
      BDU_v2.1.2015.018b.zip
      BDU_v2.1.2016.019b.zip
      BDU_v2.1.2016.020b.zip
      BDU_v2.1.2017.021b.zip
      BDU_v2.1.2017.022b.zip
×