Jump to content
xpamamadeus

Ozmosis

6,210 posts in this topic

Recommended Posts

Can anyone confirm if X86PlatformPlugin is being loaded on a real iMac13,2 (Late 2012) running High Sierra with the lastest  firmware upgrade ?

 

Reason why I am asking is because since High Sierra as soon as the plugin-type property=1  the system (QUO board, Ivy Bridge) will hang at boot when it tries to load X86PlatformPlugin. I suspect that Apple might have removed this property in the firmware for iMac 13,2. I think that this property migth now only be used to turn on xcpm mode but Ivy Bridge support has been remove from the xcpm kernel ...would also like to know for a real MacMini6,2 

Edited by IronManJFF
Added reason for asking

Share this post


Link to post
Share on other sites
Advertisement
On 1/9/2018 at 10:32 AM, STLVNUB said:

Here is OzmosisToolKit

Uses OzMTool to build a new rom

 

Usage:

Place your untouched rom into baseROM

Place your Ffs into Ffs

Run OzMToolKit.sh

 

Should end up with your finished rom in builtROM

Enjoy

 

PS if anyone wants to expand on script feel free.

 

OzmosisToolKit.zip

 

It's not working

 

mumus-iMac:~ mumu$ /Users/mumu/Downloads/OzmosisToolKit/OzMToolKit.sh

Running OzMToolKit V 0.0

from /Users/mumu/Downloads/OzmosisToolKit

getrom=0

You have 1 Roms: 

base.rom

Running OZMTool, using base as the base image

Creating base.rom

OZMTool - v0.3

Warning: No KEXT-dir given! Injecting only Ozmosis files!

Warning: No DSDT file given! Will leave DSDT as-is!

Info: Aggressivity level set to 'Do nothing - Inject as-is'...

Info: Compressing CORE_DXE is selected!

Injecting FFS into BIOS...

 * Current file: '1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609_PartitionDxe.ffs'...

* File not existant, inserting at the end of volume

 * Current file: '4CF484CD-135F-4FDC-BAFB-1AA104B48D36_HfsPlus.ffs'...

* File not existant, inserting at the end of volume

 * Current file: '961578FE-B6B7-44C3-AF35-6BC705CD2B1F_EnhancedFat.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'AAE65279-0761-41D1-BA13-4A3C1383603F_Ozmosis.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'AC255206-DCF9-4837-8353-72BBBC0AC849_OzmosisHorizontalTheme.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'B34E5765-2E04-4DAF-867F-7F40BE6FC33D_Extfs.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'C57AD6B7-0515-40A8-9D21-551652854E37_HermitShellX64.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'DADE1001-1B31-4FE4-8557-26FCEFC78275_SmcEmulatorKext.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'DADE1002-1B31-4FE4-8557-26FCEFC78275_DisablerKext.ffs'...

* File not existant, inserting at the end of volume

 * Current file: 'DADE1003-1B31-4FE4-8557-26FCEFC78275_InjectorKext.ffs'...

* File not existant, inserting at the end of volume

Compressing CORE_DXE to save space...

* File was injected compressed successfully!

Deleting non required Filesystem FFS...

* Removed 'FileSystem' [93022F8C-1F09-47EF-BBB2-5814FF609DF5] succesfully!

Reconstructing final image...

reconstructVolume: 8C8CE578-8A3D-4F1C-9935-896185C32DD3: root volume can't be grown

ERROR: Image exploded...

! Program exited with errors !

 

Status code: 17

mumus-iMac:~ mumu$ 

Share this post


Link to post
Share on other sites

Your rom image doesn't have much more space to insert all that files, so you have to make a choice for what files you will keep and what files you'll not need! At that stage you only have to do that manually IMHO!

Share this post


Link to post
Share on other sites

What board you have, but instead update your signature to know the hardware you have, so I can build one for you!

Share this post


Link to post
Share on other sites
On May 22, 2018 at 2:43 PM, IronManJFF said:

Can anyone confirm if X86PlatformPlugin is being loaded on a real iMac13,2 (Late 2012) running High Sierra with the lastest  firmware upgrade ?

 

Reason why I am asking is because since High Sierra as soon as the plugin-type property=1  the system (QUO board, Ivy Bridge) will hang at boot when it tries to load X86PlatformPlugin. I suspect that Apple might have removed this property in the firmware for iMac 13,2. I think that this property migth now only be used to turn on xcpm mode but Ivy Bridge support has been remove from the xcpm kernel ...would also like to know for a real MacMini6,2 

Bump ... Anyone can confirm ?

Share this post


Link to post
Share on other sites

Hi Guys,

A day ago I suddenly encountered a problem with Oz and don't understand what's causing it or how to fix it. 

Everything was Ok, I made almost everything I wanted and make it 100% working, but after I turned off the computer and powered it up after I came back - always after boot it just a black screen and nothing happens. No verbose mode, or HDD activity blinking on the case, but windows working without a problem. 

Even if I try to load install USB drive - it's not booting:

https://drive.google.com/file/d/1uiDCA5vloKhLZW0mNyGma0gN___hM2wf/view?usp=sharing

 

I reflashed BIOS about 20 times in every way possible, checked md5 and even went couple times to original bios and after flash Oz infused. Bios setting rechecked countless times and the result is the same. 
Maybe I'm missing something out? 

Share this post


Link to post
Share on other sites

Guys, is there any kind of logging Oz can do and where can it be seen? 

Currently nothing from what i did helped, the last idea - to swap hardware (but it's a blind idea because of no other ideas)) 

Share this post


Link to post
Share on other sites
On 6/3/2018 at 4:34 PM, firefly_can_fly said:

I made almost everything I wanted and make it 100% working, but after I turned off the computer and powered it up after I came back - always after boot it just a black screen and nothing happens

Did you install or update any kexts or something else on the EFI? Oz behaves like this when you have e.g a kext with a plugin folder installed...

 

You could also try the radical method: safe and delete you EFI folder or partition and try again.

Share this post


Link to post
Share on other sites

I found the reason. Problem was because of bad contacts on sata cables. I thought this would show up somehow another way, but it's like that. As soon as I replaced them - everything started to works. It's dumb, but it is so. 

I make cleaning and all that stuff, but somehow it went like that. 

Share this post


Link to post
Share on other sites

Just use your kexts from L/E or S/L/E for the moment and update your defaults to all the newest values (FirmwareFeatures, BIOS Dates/Versions etc.). Also use the newest available APFS.efi.

This way you should normally be able to install Mojave...

Edited by TypeThree

Share this post


Link to post
Share on other sites

You should not place anything into /S/L/E  (even tough it still works) use /L/E instead. It is only a matter of time before Apple disallows any non-Apple provided kext into /S/L/E.

Share this post


Link to post
Share on other sites
17 hours ago, TypeThree said:

Just use your kexts from S/L/E for the moment and update your defaults to all the newest values (FirmwareFeatures, BIOS Dates/Versions etc.). Also use the newest available APFS.efi.

This way you should normally be able to install Mojave...

Nope. Something akin to "Your computers firmware needs to be updated" gets displayed. And that was booting with an Oz updated with the 10.14 apfs.efi. 

 

Neither direct install nor boot with Oz after install via Clover works. FirmwareFeatures was the only one that changed as far as I could see.

 

If you kindly share your FakeSmc which is working for you, that would be great!

Share this post


Link to post
Share on other sites
49 minutes ago, Si Vis Pacem said:

Nope. Something akin to "Your computers firmware needs to be updated" gets displayed. And that was booting with an Oz updated with the 10.14 apfs.efi. 

 

What values do you have for BiosDate and BiosVersion in Defaults.plist ?

Share this post


Link to post
Share on other sites
2 hours ago, cecekpawon said:

Hello @Si Vis Pacem you are trying to say that the old patched ozmosis was able to boot 10.14 with injected kexts without any additional patches? By only updating firmware related infos? Thanks

 

Maybe yes, need only to update smbios related date, i booted fine without injecting FakeSMC and its Sensors, Realtek RTL8111, Lilu, AppleALC and IntelGraphicsFixup. When 10.14 installed, Oz can boot with that kexts injected, and load them fine, the problem is only when the first boot and the second for install. It doesn't boot three time in 10.14 like clover for the install steps, strange but very smooth and concrete.

 

2 hours ago, IronManJFF said:

 

What values do you have for BiosDate and BiosVersion in Defaults.plist ?

 

Check Ozmosis configurator for that, boot with DGPU and disable IGPU, you'll install 10.14, you must have a working APFS for that. If not, and after install succeed, you won't be able to see the 10.14 drive, unless that working APFS or booting from clover.

Share this post


Link to post
Share on other sites
17 hours ago, ammoune78 said:

i booted fine without injecting FakeSMC and its Sensors, Realtek RTL8111, Lilu, AppleALC and IntelGraphicsFixup

Could you specify that? I can't really believe that you were able to install Mojave without the use of at least FakeSMC... Did you inject the Kexts from L/E or S/L/E? 

 

It would be awesome if somebody could verify that it's possible to run Mojave with Ozmosis when injecting Kexts from outside the EFI. This way we would know that only KextInjection from EFI needs to be fixed to make Ozm compatible with Mojave.

 

Regarding SMBios, what did you update? BIOS Version, BIOS Date, FirmwareFeatures and FirmwareFeaturesMask?

Edited by TypeThree

Share this post


Link to post
Share on other sites
17 minutes ago, TypeThree said:

Could you specify that? I can't really believe that you were able to install Mojave without the use of at least FakeSMC... Did you inject the Kexts from L/E or S/L/E? 

 

It would be awesome if somebody could verify that it's possible to run Mojave with Ozmosis when injecting Kexts from outside the EFI. This way we would know that only KextInjection from EFI needs to be fixed to make Ozm compatible with Mojave.

 

Regarding SMBios, what did you update? BIOS Version, BIOS Date, FirmwareFeatures and FirmwareFeaturesMask?

 

No, the FakeSMC is on ROM but doesn't get loaded during install process, also showing AppleACPICPU and other things problem, but just wait and reach the install screen.

 

SMBios should be updated using Ozmosis Configurator as well, it's simple, don't need any kind of hassle, just try but be patient and do not reboot the machine even if showing errors, because after installing it will not show them, and all the things will be injected as well. Be sure to have working APFS otherwise you'll not be able to see the drive, i'm having this problem now.

Share this post


Link to post
Share on other sites

Have anyone succeed booting Mojave with Intel HD4600 graphics, with R9 280X already done, but HD4600 just reboot loops.

Share this post


Link to post
Share on other sites

Is there anyone that can try to boot Mojave with Intel HD4600 only using Ozmosis please?

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 Rohan20
      Opencore is running really really slow on Catalina 10.15.4. So It was running perfectly before I put the ssdt-pnlf for enabling Brightness control. it is running really slow and I verified my config with the sanity checker and its all correct. can someone please help. I am attaching my oc folder.

       
      https://www.dropbox.com/s/drkek0eaz19ina5/OC.zip?dl=0
       
    • By StarFighter_77
      I built this hack years ago now. Started with Lion, now on El Cap. I want to update now to High Sierra.

      I think I messed up my Clover when I downloaded the update .pkg and just installed it without taking my time or customizing the install. Was on Clover r3423, now I think I'm on r5104

      I've been searching and reading this site and others for a few days before making this thread, but I need help compiling what I've learned to get my system running correctly again and ready to update to High Sierra. Then, eventually, I want to update my graphics card, switch to UEFI (if necessary) and update to Mojave.

      I couldn't get system to boot. Could get to Clover and all the options, except the Shell... I hit enter on the Shell and I get black screen and nothing.

      The only way I got it to boot was to add -v to boot args, and change smbios from 14,2 to 13,2. Not sure why that worked still. Also I'm running two monitors, but I can only now run one of them off the Intel 3000 Graphics and the second one off my GFX Card.

      So now I'm afraid to shut down or reboot.... I could really use some help with Clover.

      I'm pretty sure my config file in Clover is not right. Also, some of the files in my Clover backups are not in the new Clover install. (2.5k 5104)

      If someone could please take a look at the files I've attached and help me sort this out, I would be grateful. Thank you, Thank you, Thank you.

      I've attached
      - The last boot log
      - The current Clover folder from the EFI partition after performing Clover update. (.zip)
      - The Clover backup that was working before Clover update (.zip)
      - Library/Extensions Folder (screen shot)
      - System/Library/Extensions Folder (.zip)

      Here is my current hardware:

      Mobo: GIGABYTE GA-Z68MX-UD2H-B3

      CPU: Intel Core i7-2600K

      GPU: GIGABYTE ATI Radeon HD6870 1GB DDR5 2DVI/HDMI/2x

      RAM: Corsair Vengeance Blue 16 GB DDR3 SDRAM Dual Channel Memory Kit CMZ16GX3M4A1600?C9B

      HD0 (for OS and Apps): OCZ Technology 120 GB Vertex Series SATA II Solid State Drive

      HD1 (file storage, Adobe scratch disk): Samsung 1 TB Spinpoint 7200 RPM 32MB Cache SATA

      BURNER: LG CD/DVD Burner Model GH22NS50

      CPU COOLER: Corsair Cooling Hydro Series H50 All in One High-performanc?e CPU Cooler CWCH50-1

      P/S: Antec CP-850 850 Watt CPX Power Supply Unit

      CASE: Antec Performance One P183 V3 Case
      CLOVER.zip
      CloverBackup.zip
      bootlog.txt

      S_L_E.zip
    • By dgsga
      Can I propose a new subforum be created for the new OpenCorePkg OpenCore front end being created by vit9696 and others, it is a fantastic piece of work:
      https://github.com/acidanthera/OpenCorePkg
      Even at version 0.1 it runs my Mojave 10.14.4 setup very nearly flawlessly. It consists of a 10KB bootstrap BootX64.efi and a 200KB OpenCore.efi OS loader. All configuration is done using a very well documented config.plist 
       
       
    • 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.
       
       
       
       
      Feel free to "Rate File"
      Submitter cvad Submitted 04/28/2013 Category Bootloaders  
×