Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6234 posts in this topic

Recommended Posts

Recommended

Posted by THe KiNG,

SINCE SOMEBODY PUBLISHED THE SOURCE CODE WITHOUT OUR PERMISSION I ANOUNCE HERE THAT ANY USE OF THE CODE IN PART OR IN WHOLE IS ILLEGAL AND ACTIONS IN COURT WILL BE MADE AGAINST STLVNUB USER THAT WAS THE SOURCE OF THE LEAKED SOURCE EVEN WE HAD A VERY CLEAR STATEMENT THAT HE CANNOT DO THIS, AND THE OTHER WHO USE THE CODE AND ALREADY PUBLISHED BINARIES HERE ON THIS FORUM AND OTHER FORUMS. LET ME BE VERY CLEAR: OZMOSIS WAS, IS AND IT WILL REMAIN CLOSED SOURCE. NO FUTHER RELEASES WILL BE MADE AN
Recommended by Allan
  • Haha
  • Like

4 reactions

Go to this post
edifice98
edifice98
Posted
Posted

I hope work for you. After test tell me how to work your Oz!!!

 

I really appreciate the help. Unfortunately it did not work. I could no longer get into the BIOS setup or choose boot devices. I could read my OS X partitions when using Q-Flash so I know that some of it worked. I just couldn't boot anything until I re-flashed with a stock BIOS.

Pavo
Pavo
Posted
Posted

I really appreciate the help. Unfortunately it did not work. I could no longer get into the BIOS setup or choose boot devices. I could read my OS X partitions when using Q-Flash so I know that some of it worked. I just couldn't boot anything until I re-flashed with a stock BIOS.

Try this one:

Z87XHD3.F4.zip

edifice98
edifice98
Posted
Posted

Try this one:

  Odd.. Same situation. Can read HFS from Q-Flash but can't get to the boot menu or settings. I am starting to think my computer wants me to use clover just to torture me. I will have to think about this and try and figure out what might be unique about my system.

 

Thanks!

crusher
crusher
Posted
Posted

  Odd.. Same situation. Can read HFS from Q-Flash but can't get to the boot menu or settings. I am starting to think my computer wants me to use clover just to torture me. I will have to think about this and try and figure out what might be unique about my system.

 

Thanks!

Look problem in z87 mobo with OZ1479 you try with OZ894!!!

I attach your rom file with Ozmosis 894:

 

 

I inject this file in rom:

|185|PartitionDxe   |1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609|008C5645|0018CC|DRVR|
|186|HfsPlus        |4CF484CD-135F-4FDC-BAFB-1AA104B48D36|008C6F11|00379C|DRVR|
|187|EnhancedFat    |961578FE-B6B7-44C3-AF35-6BC705CD2B1F|008CA6AD|003451|DRVR|
|188|OzmosisDefaults|99F2839C-57C3-411E-ABC3-ADE5267D960D|008CDAFE|000760|DRVR|
|189|Ozmosis        |AAE65279-0761-41D1-BA13-4A3C1383603F|008CE25E|01CAE4|DRVR|
|190|OzmosisTheme   |AC255206-DCF9-4837-8353-72BBBC0AC849|008EAD42|026366|FRFM|
|191|SmcEmulatorKext|DADE1001-1B31-4FE4-8557-26FCEFC78275|009110A8|00859B|FRFM|
|192|DisablerKext   |DADE1002-1B31-4FE4-8557-26FCEFC78275|00919643|00323C|FRFM|
|193|InjectorKext   |DADE1003-1B31-4FE4-8557-26FCEFC78275|0091C87F|00023F|FRFM|
  • Like 1
edifice98
edifice98
Posted
Posted

 

Look problem in z87 mobo with OZ1479 you try with OZ894!!!

I attach your rom file with Ozmosis 894:

attachicon.gifZ87XHD3.F4-CRU_OZM894.zip

 

I inject this file in rom:

|185|PartitionDxe   |1FA1F39E-FEFF-4AAE-BD7B-38A070A3B609|008C5645|0018CC|DRVR|
|186|HfsPlus        |4CF484CD-135F-4FDC-BAFB-1AA104B48D36|008C6F11|00379C|DRVR|
|187|EnhancedFat    |961578FE-B6B7-44C3-AF35-6BC705CD2B1F|008CA6AD|003451|DRVR|
|188|OzmosisDefaults|99F2839C-57C3-411E-ABC3-ADE5267D960D|008CDAFE|000760|DRVR|
|189|Ozmosis        |AAE65279-0761-41D1-BA13-4A3C1383603F|008CE25E|01CAE4|DRVR|
|190|OzmosisTheme   |AC255206-DCF9-4837-8353-72BBBC0AC849|008EAD42|026366|FRFM|
|191|SmcEmulatorKext|DADE1001-1B31-4FE4-8557-26FCEFC78275|009110A8|00859B|FRFM|
|192|DisablerKext   |DADE1002-1B31-4FE4-8557-26FCEFC78275|00919643|00323C|FRFM|
|193|InjectorKext   |DADE1003-1B31-4FE4-8557-26FCEFC78275|0091C87F|00023F|FRFM|

  Thank You! It works :)

IronManJFF
IronManJFF
Posted
Posted

Would love too but .. I have a QUO board and even tough I could update FakeSMC with the latest version by putting it in the ESP it will not contain the proper 'sensor profile'.  Also seems like Hermit Crabs either renamed some part of FakeSMC or develop a private branch for it which is why I am asking if someone 'knows'  if there will be an update to the Hermit Crabs BIOS. If so I may wait, if not I will try to find a way to update it

THe KiNG
THe KiNG
Posted
Posted

Would love too but .. I have a QUO board and even tough I could update FakeSMC with the latest version by putting it in the ESP it will not contain the proper 'sensor profile'.  Also seems like Hermit Crabs either renamed some part of FakeSMC or develop a private branch for it which is why I am asking if someone 'knows'  if there will be an update to the Hermit Crabs BIOS. If so I may wait, if not I will try to find a way to update it

There is nothing developed separate, is just the revision mentioned in the release note with IOLog "spam" removed.

The sensor profile you can easy extract from LPCSensors plist and apply to whatever version you want to use, you just need to extract the ffs uncompressed select the xml part of it and save as whatever.plist using any hex editor...

If those look complicated you can just wait.

Patience is a virtue...

  • Like 2
IronManJFF
IronManJFF
Posted
Posted

There is nothing developed separate, is just the revision mentioned in the release note with IOLog "spam" removed.

The sensor profile you can easy extract from LPCSensors plist and apply to whatever version you want to use, you just need to extract the ffs uncompressed select the xml part of it and save as whatever.plist using any hex editor...

If those look complicated you can just wait.

Patience is a virtue...

 

Thanks TheKing, it is just that I cannot find version 1290 on kozlek repo which led me to believe that the Hermit Crabs boys had done something special... having that extra bit of info I think I can manage from here...

 

Learning a little bit more everyday

THe KiNG
THe KiNG
Posted
Posted

...it is just that I cannot find version 1290 on kozlek repo which led me to believe that the Hermit Crabs boys had done something special... 

As of today there are 1372 revisions in kozlek repo, if you want the one used in Hermit BIOS just pull the 1290 commit.

  • 2 weeks later...
Tosk
Tosk
Posted
Posted

Been having an issue with Ozmosis on my board.

 

I have a GA-Z97-HD3 v2.1. I followed the steps to insert Ozmosis into BIOS version F8. Everything seemed to go fine. Flash was successful, however I cannot get anything to boot in either UEFI or legacy mode. I have an HDD with Mavericks on it. The BIOS detects the HFS+ volume and the Recovery HD volume on the drive, but refuses to do anything when attempting to boot (goes immediately to a black screen). Booting Windows 8 in legacy mode on a separate drive also does not work (goes to a frozen cursor in the top left).

 

I am unsure where I went wrong or what the next step is to troubleshoot this issue.

  • 4 weeks later...
pmcnano
pmcnano
Posted
Posted

Ok, first time I come for actual help! lol

 

Im trying to inject a different AAPL,ig-platform-id, however I tried via nvram and it doesnt seem to be working. I have read that it has to be in decimal, but also seen some examples in hexa (like in the official readme file).

 

I even tried using the defaults.plist in /Efi/Oz and its not being loaded. 

 

I injected the new OzmosisDefaults.plist with the AAPL and it is still injecting the default one. Heres the defaults.plist (serials removed)

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Version</key>
	<string>1.0.0</string>
	<key>Date</key>
	<integer>0</integer>
	<key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
	<dict>
		<key>BiosVersion</key>
		<string>MM51.88Z.0077.B0F.1110201309</string>
		<key>BiosDate</key>
		<string>09/03/2013</string>
		<key>ProductName</key>
		<string>Macmini5,1</string>
		<key>ProductFamily</key>
		<string>iMac</string>
		<key>SystemVersion</key>
		<string>1.0</string>
		<key>SystemSerial</key>
		<string>blablabla</string>
		<key>ProductId</key>
		<string>Mac-8ED6AF5B48C039E1</string>
		<key>BoardVersion</key>
		<string>Proto1</string>
		<key>BaseBoardSerial</key>
		<string>blalbabla</string>
		<key>Manufacturer</key>
		<string>Apple Inc.</string>
		<key>ProcessorSerial</key>
		<string>blablabla</string>
		<key>SystemSKU</key>
		<string>System SKU#</string>
		<key>BaseBoardAssetTag</key>
		<string>Base Board Asset Tag#</string>
		<key>ChassisAssetTag</key>
		<string>Asset Tag#</string>
	</dict>
	<key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
	<dict>
		<key>boot-args</key>
		<string>kext-dev-mode=1 -v</string>
	</dict>
	<key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
	<dict>
		<key>DisableIntelInjection</key>
		<string>false</string>
		<key>AAPL,ig-platform-id</key>
		<string>0xa260006</string>
	</dict>
</dict>
</plist>

as you can see here, its not being used:

07:457 00:000 Found Intel Intel HD Graphics 4600 [8086:0412] PciRoot(0x0)/Pci(0x2,0x0)
07:457 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "model" = "Intel HD Graphics 4600" (22) - Success
07:457 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "built-in" = 00  (1) - Success
07:457 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "class-code" = 00 00 03 00  (4) - Success
07:457 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "hda-gfx" = "onboard-1" (10) - Success
07:458 00:000  Injected PciRoot(0x0)/Pci(0x2,0x0) - "AAPL,ig-platform-id" = 0D 22 00 03  (4) - Success

Anyway, all this is because I cant get HD4600 kexts loading. This is the first time I encounter something like this. I am using a new (meaning never experienced with this before) motherboard, and a different processor, but they are not that far different. 

 

GA-B85-HD3 ( In my last build I used B85-UD3H)
Core i5 4460 (last build 4440, they both have HD4600)

 

Any insights?

pmcnano
pmcnano
Posted
Posted

Thanks Pavo, any clue why it isnt working from nvram? Right now im building the new bios, flash, etc.

 

edit:

 

Ok, I remembered I had another motherboard lying around. a GA-Z97-SLI and it works perfectly. So.....its something with the motherboard.  I will start from the beggining!

 

Thanks

 

Edit2: do you think it has something to do with deleting coreCSM?, Im using full UEFI. 

 

edit3: CoreCSM isnt the problem. Doing a painfull 1 by 1 bios editing process.

 

edit4: ok, lets say this motherboard is incompatible. As soon as I add ozmosis.fss to the bios, video is broken (im loading from clover not ozmosis). I dont have nothing more to check, so...any ideas?

Pavo
Pavo
Posted
Posted

Thanks Pavo, any clue why it isnt working from nvram? Right now im building the new bios, flash, etc.

 

edit:

 

Ok, I remembered I had another motherboard lying around. a GA-Z97-SLI and it works perfectly. So.....its something with the motherboard.  I will start from the beggining!

 

Thanks

 

Edit2: do you think it has something to do with deleting coreCSM?, Im using full UEFI. 

 

edit3: CoreCSM isnt the problem. Doing a painfull 1 by 1 bios editing process.

 

edit4: ok, lets say this motherboard is incompatible. As soon as I add ozmosis.fss to the bios, video is broken (im loading from clover not ozmosis). I dont have nothing more to check, so...any ideas?

Never ever ever delete CORECSM, you have nothing to fall back on if your gfx doesn't have GOP

crusher
crusher
Posted
Posted

Hermit shell labs  :drool:  good you didn't write Hermit pike slaps  :hysterical:

 

Sorry for OT...

The KING I have a problem with El Capitan DP4 and Beta 2 how to fix that on Oz. I install FakeSMC in S/L/E and I have no luck.

Where is the problem on my Oz. What you think!!!!?

 

Guest
This topic is now closed to further replies.
 Share
Go to topic listing
×
×
  • Create New...