Jump to content
About Just Joined group Read more... ×
xpamamadeus

Ozmosis

6,216 posts in this topic

Recommended Posts

Hello,

 

Where/How do I have to do that to remove verbose output :

 

 

To suppress verbose output apfs.efi

Find: 00554889E54883EC4048
Replace: 00C34889E54883EC4048

 

Thank you

Share this post


Link to post
Share on other sites
Advertisement

I have the GA-Z87X-UD5H and would advise you mod your MATS table because your going to have kernel panics. Few pages back I detailed how I was able

to fix that problem on my board and for you should be very similar. Besides that not sure that APFS works at all and you should use HFS+ formated installation.

 

Hi, thanks for the info. I've got an ozmosis bios for my board from a German forum. It says that is updated for Sierra using OZM 167x. 

At the moment I really don't know if is the latest or not.

 

I would  like to use this "prepared" bios but I would inject my own patched dsdt and ssdt. I also had to patch this MATS table. 

Can you help me doing this?

I need use the provided OzmosisDefault or is best to adjust with my Serial, MLB, etc.. ?

Share this post


Link to post
Share on other sites

Hi, thanks for the info. I've got an ozmosis bios for my board from a German forum. It says that is updated for Sierra using OZM 167x. 

At the moment I really don't know if is the latest or not.

 

I would  like to use this "prepared" bios but I would inject my own patched dsdt and ssdt. I also had to patch this MATS table. 

Can you help me doing this?

I need use the provided OzmosisDefault or is best to adjust with my Serial, MLB, etc.. ?

 

 

Hi,

 

Look at this:

 

http://www.insanelymac.com/forum/topic/291655-ozmosis/page-260?do=findComment&comment=2457092

 

If you still cant figure it out post your bios.

 

Prefer you do it than me..

 

Thanks

Share this post


Link to post
Share on other sites

Hi,

 

Look at this:

 

http://www.insanelymac.com/forum/topic/291655-ozmosis/page-260?do=findComment&comment=2457092

 

If you still cant figure it out post your bios.

 

Prefer you do it than me..

 

Thanks

 

I'm trying.

 

So, I've open this german bios with UEFITool, finded these two module 'OnOffChargeDXE' and 'OnOffChargeSMM' and I've extracted the compressed PE32 body.

But now if I open these .bin with HexEdit where I can find this Compiler ID String? 

 

 

EDIT: I've found it. Disassembling MATS Table I found that:

 Asl Compiler ID : "w x2"

So I think I've to look at w x2 into those PE32 and replace with INTL

Share this post


Link to post
Share on other sites

Yes thats the ticket! You got it! What you do is search for the occurrence of 'w x2' and change it to 'INTL' in one of those modules inside a hex editor, save and replace.

 

 

 

Also anyone care to comment about what is required to have AFPS properly working?

 

Thank you.

Share this post


Link to post
Share on other sites

To have APFS properly working you have to use Kext2FFS to convert latest apfs.efi to ffs, then use UEFITool to integrate module into bios, flash bios, profit!

To make work easy for you, here's the compressed .ffs, just use UEFITool and insert it. After flash reset nvram using command option P R and High Sierra entry should appear over boot manager entry.

Share this post


Link to post
Share on other sites

To have APFS properly working you have to use Kext2FFS to convert latest apfs.efi to ffs, then use UEFITool to integrate module into bios, flash bios, profit!

To make work easy for you, here's the compressed .ffs, just use UEFITool and insert it. After flash reset nvram using command option P R and High Sierra entry should appear over boot manager entry.

 

Thank you. Though I wonder what all that talk was about having to load it via bcfg all about?

 

Thanks again.

Share this post


Link to post
Share on other sites

 

Don't know if still relevant, here with (SJ_UnderWater aka PHPdev32) Patcho:

cp apfs.efi apfs.bak
./patcho 0000 554889E54883EC4048 C34889E54883EC4048 apfs.efi

 

Thank you it works great!

Share this post


Link to post
Share on other sites

Loading via bcfg it's not enough, driver should be initialized properly, "jumpstart like". This method is fast and simple.

 

 

Whats all this talk about "jumpstarting" the driver? The only issue I ever had was Ozmosis menu acting up on my system. Was that ever fixed?

 

Thanks

Share this post


Link to post
Share on other sites

Well, no it does not. It will load if added via EFI Shell and bcfg driver ADD but it won't connect to any device so even if the driver is loaded nothing will happen unless you connect it to a proper device (use the connect command to attach it to a given device) and that's where jumpstart comes into place. Jumpstart typically means that a driver will be started even if no devices are associated with it it will connect to suitable Devices if they are available. UEFI Drivers which are placed inside of the ROM will load if you fire up your Machine and they will load before the drives are initialised to make sure the Filesystems are recognised.  Drivers which are added via bcfg depend on a fully initialised and readable Disk to load them. In Case of the APFS Driver it will be loaded but as a Filesystem driver it won't attach to anything since the drives have already been scanned and attached...

 

If you boot into the (u)EFI Shell you might be able to attach the driver to a drive with the connect or reconnect Command both will trigger a scan of the device Tree which automatically will connect APFS but this thing has to be repeated every time you boot up your PC in order to connect APFS...

Share this post


Link to post
Share on other sites

Well, no it does not. It will load if added via EFI Shell and bcfg driver ADD but it won't connect to any device so even if the driver is loaded nothing will happen unless you connect it to a proper device (use the connect command to attach it to a given device) and that's where jumpstart comes into place. Jumpstart typically means that a driver will be started even if no devices are associated with it it will connect to suitable Devices if they are available. UEFI Drivers which are placed inside of the ROM will load if you fire up your Machine and they will load before the drives are initialised to make sure the Filesystems are recognised.  Drivers which are added via bcfg depend on a fully initialised and readable Disk to load them. In Case of the APFS Driver it will be loaded but as a Filesystem driver it won't attach to anything since the drives have already been scanned and attached...

 

If you boot into the (u)EFI Shell you might be able to attach the driver to a drive with the connect or reconnect Command both will trigger a scan of the device Tree which automatically will connect APFS but this thing has to be repeated every time you boot up your PC in order to connect APFS...

Very interesting. I think I understand. Your saying that by the time the apfs driver loads from firmware the drives or partitions have been assigned to another driver. In that case are there any uefi system calls or block io protocols that can be loaded in a custom driver that loads the apfs driver and auto connects the drive for you?

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

Share this post


Link to post
Share on other sites

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

  • Recently Browsing   0 members

    No registered users viewing this page.

Announcements

  • Similar Content

    • By utilman
      Hello 2 everybody

      Can someone give me helpfully links to an installation of Catalina on a Lenovo Thinkpad T510.

      Or what is the latest currently working macOS for an Lenovo T510 with an i5 and integrated GPU (Intel)?

      Because the Links in the old threads are not working anymore.

      Thank you very much
    • By cvad
      View File 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.
       
      Enjoy...
       
      For more information and complete instructions please see this topic.
       
      Anyone who likes the program, please support its Community Score.
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
    • By PropoFlexWX4
      After hearing that OpenCore is so much better than Clover, and that it will probably be able to boot Big Sur before Clover does, I decided to take the jump.
       
      Running Catalina 10.15.5 18F101 with OC 0.5.9.
       
      So far I like the result. The OS feels faster, boots faster.
      And absolutely everything works (sleep, network, etc...)
       
      So, that's it? Is there anything else I have to do?
    • By MacPato
      ALL-IN-ONE OPENCORE EFI CREATION UTILITY
      OC Gen-X Opencore EFI Creator Utility  First-Ever Beta is now released to the Public for Testing. Bugs or Issues please submit bug reports via the GitHub page! https://github.com/Pavo-IM/OC-Gen-X  Also, tell us what you think and what future features you would like to see in the release.
      Opencore Generation X is a Utility to create a pre-structured EFI Folder to the Desktop Based on the selection of the user. This Application is currently in beta testing it was designed and developed to make it easy to get Opencore installed. The configuration file is based on the dortania guide.

      if you have any request, suggestions feel free to make a submission at the GitHub page   Disclaimer: This application is not endorsed or support by the opencore development team, all app support and bugs must be reported via the app repo page : https://github.com/Pavo-IM/OC-Gen-X         
×