Jump to content

Ozmosis


xpamamadeus
6,231 posts in this topic

Recommended Posts

Hi guys!

 

I'm having a problem with Hardware UUID - I force a UUID that I use since Chameleon because some programs use this to know if you they have had reinstalled in other system and count how many reinstall you did.

I use the same UUID in Clover and there works fine and worked fine with Ozmosis until I have upgraded to MacOS Sierra, now even I forcing UUID on Default.plist the system change the UUID after boot.

Is this happen with you guys?

 

Here my Default.plist

<?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.1</string>
  <key>Timestamp</key>
  <integer>0</integer>
  <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key>
  <dict>
	<key>BiosVersion</key>
	<string>MP61.88Z.0116.B04.1312061508</string>
	<key>BiosDate</key>
	<string>03/09/13</string>
	<key>ProductName</key>
	<string>MacPro6,1</string>
	<key>ProductFamily</key>
	<string>Mac Pro</string>
	<key>SystemVersion</key>
	<string>1.0</string>
	<key>SystemSerial</key>
	<string>F5KLCW72F693</string>
	<key>ProductId</key>
	<string>Mac-F60DEB81FF30ACF6</string>
	<key>BoardVersion</key>
	<string>10</string>
	<key>BaseBoardSerial</key>
	<string>C02140302D5DMT31M</string>
	<key>Manufacturer</key>
	<string>Apple Inc.</string>
	<key>ChassisAssetTag</key>
	<string>Pro-Enclosure</string>
	<key>EnclosureType</key>
	<integer>7</integer>
	<key>ProcessorSerial</key>
	<string>F5K3474002XFNN21A</string>
    <key>HardwareAddress</key>
	<string>FC:AA:14:F5:E1:DC</string>		
    <key>HardwareSignature</key>
	<string>5BF6E328-FDF2-57E0-AF18-9F767AC78912</string>
	<key>FirmwareVendor</key>
	<string>Apple</string>
  </dict>
  <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key>
  <dict>
    <key>BootEntryTemplate</key>
    <string>$label</string>
    <key>DarwinDiskTemplate</key>
    <string>$label</string>
    <key>DarwinRecoveryDiskTemplate</key>
    <string>$label ($platform.$major.$minor)</string>
    <key>DarwinCoreStorageTemplate</key>
    <string>$label</string>
    <key>AndroidDiskTemplate</key>
    <string>$label</string>
    <key>AndroidDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string>
    <key>LinuxDiskTemplate</key>
    <string>$label $build</string>
    <key>LinuxDiskOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>
    <key>LinuxRescueDiskTemplate</key>
    <string>$label Rescue</string>
    <key>LinuxRescueOptionTemplate</key>
    <string>initrd=$initfs root=UUID=$uuid ro</string>
    <key>EnableKextPatcher</key>
    <true/>
	<key>TimeOut</key>
	<integer>7</integer>
	<key>DisableNvidiaInjection</key>
	<true/>		
  </dict>
  <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key>
  <dict>
    <key>boot-args</key>
    <string>-v nv_disable=1</string>
    <key>csr-active-config</key>
    <integer size=32>0x7F</integer>
  </dict>
</dict>
</plist

And here the UUID after boot Sierra with Ozmosis.

 

Captura_de_Tela_2016_10_23_a_s_21_44_27.

Link to comment
Share on other sites

Hi guys!

 

I'm having a problem with Hardware UUID - I force a UUID that I use since Chameleon because some programs use this to know if you they have had reinstalled in other system and count how many reinstall you did.

 

I use the same UUID in Clover and there works fine and worked fine with Ozmosis until I have upgraded to MacOS Sierra, now even I forcing UUID on Default.plist the system change the UUID after boot.

 

Is this happen with you guys?

 

Here my Default.plist


    <key>HardwareSignature</key>
	<string>5BF6E328-FDF2-57E0-AF18-9F767AC78912</string>
	

 

Hardware signature generates UUID in OSX but they aren't the same...

 

If you want "5BF6E328-FDF2-57E0-AF18-9F767AC78912" as UUID, you have to enter something else in HardwareSignature. I remember I had to do it for one of my software... but I don't remember how I did to translate "HardwareSignature" to correct UUID. Sorry.

Link to comment
Share on other sites

The best would be to reinject your original number using Chameleon, download IOJones and look for "IODeviceTree/efi/platform/system-id". That's the value to enter in the form of "xxxxxxxx-xxxx-xxxx-xxxxxxxxxxxx" in the "HarwareSignature" key of Oz defaults.plist.

 

Unless you have already a copy of your old IORegistryExplorer or IOJones report when you used Chameleon (it was the way I've generated my correct HardwareUUID, thanks God I had this report...).

Link to comment
Share on other sites

Hardware signature generates UUID in OSX but they aren't the same...

 

If you want "5BF6E328-FDF2-57E0-AF18-9F767AC78912" as UUID, you have to enter something else in HardwareSignature. I remember I had to do it for one of my software... but I don't remember how I did to translate "HardwareSignature" to correct UUID. Sorry.

 

Thanks for reply, but something very weird it's happen, I changed the HardwareSignature and HardwareAddress (macAddress) to other but the UUID didn't change?!?


Then just for test I removed this fields from my Default.plist and still nothing changed?!?

 

I will delete the default.plist to see if still works, maybe there is another default.plist somewhere...

Link to comment
Share on other sites

Your original variables would still be saved in nvram. You need to reset nvram with a four finger reset after editing the Defaults.plist.

Thank you! You was correct!

 

And for my luck, I had written down the UUID that I had from the Chameleon and the MacAddress too, putting this information the correct UUID was generated again.  :D
 
Thank you guys for the ideias, I thought the HardwareSignature was a forced way like Clover does.
  • Like 2
Link to comment
Share on other sites

Anyone have any theme files for Ozmosis they want to share? Looking for the classic Silver mac look..

 

Also is there a way for when Oz is reset for it to run an nsh shell script automatically?

 

Thanks

 

Bump.,

Link to comment
Share on other sites

Hi,

 

Today I decided to improve my Dsdt, I get finally what I want for my GA H97-WIFI. Size is now less than 8ko.

I use Dsdt2Bios to import Dsdt in AmiBoardInfo, put into my bios and after flash, black screen  :(

 

I've found the bug and update Dsdt2Bios to rev 0.4.12  :yes:

 

https://www.dropbox.com/s/m0391hzhkprfrc5/Dsdt2Bios-0.4.12.zip?dl=0

 

Fred

  • Like 5
Link to comment
Share on other sites

Or one just adds everything *SMC* to *SMC*Helper and not to Clover?

Clover catch SMC keys set by system for boot.efi can take them.

Those keys are not random and not constatns

3:132  0:045  found AppleSMC protocol
3:137  0:004     fakesmc-key-LsBA-ui8:90 
3:141  0:004     fakesmc-key-NTOK-ui8:01 
3:146  0:004     fakesmc-key-NATi-ui16:00 00 
3:153  0:006     fakesmc-key-NATJ-ui8:00 
3:158  0:004     fakesmc-key-CLKH-{clh:00 00 70 80 00 01 19 40 
3:173  0:015     fakesmc-key-LSSS-ui16:02 00 
3:183  0:009     fakesmc-key-CLKT-ui32:00 01 33 03 
3:195  0:012     fakesmc-key-HBKP-ch8*:E8 8E 37 AF 92 7F 44 49 9E F2 CC 27 02 B5 7B F6 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 
3:249  0:054     fakesmc-key-MSDW-ui8:00 

Link to comment
Share on other sites

Hi,

 

Today I decided to improve my Dsdt, I get finally what I want for my GA H97-WIFI. Size is now less than 8ko.

I use Dsdt2Bios to import Dsdt in AmiBoardInfo, put into my bios and after flash, black screen  :(

 

I've found the bug and update Dsdt2Bios to rev 0.4.12  :yes:

 

https://www.dropbox.com/s/m0391hzhkprfrc5/Dsdt2Bios-0.4.12.zip?dl=0

 

Fred

Did you fix .rom problem? 

Link to comment
Share on other sites

Did you fix .rom problem? 

 

No.

 

do you have such hardware with .rom section ? hardware to recover bad flash ?

I ask that because I've an idea of how to bypass this limitation.

We need to leave same size of DSDT like that doesn't need to calculate new jump and so on.

Restriction is that DSDT should never be greater than original, lower is not a problem.

It should work but need somebody to test.

 

Fred

Link to comment
Share on other sites

  • 2 weeks later...

Hello,

 

I wrote a little soft to extract key from smc file provide by Apple.

Nothing great just for fun.

https://www.dropbox.com/s/eh65d1cs4p0pa4a/SmcExtract.zip?dl=0

 

In Mac-27ADBB7B4CEE8E6.csv look at col "E" seems to be an offset in 64k space.

Device (SMC)
{
    ***code***
    Name (_CRS, ResourceTemplate ()  // _CRS: Current Resource Settings
    {
        ***code***
        Memory32Fixed (ReadWrite,
                       0xFEF00000,         // Address Base
          ====>        0x00010000,         // Address Length
                      )
        IRQNoFlags () {6}
    })
}

Fred

 

It's not the good place, I know but can't post in dev forum.

Link to comment
Share on other sites

No.

 

do you have such hardware with .rom section ? hardware to recover bad flash ?

I ask that because I've an idea of how to bypass this limitation.

We need to leave same size of DSDT like that doesn't need to calculate new jump and so on.

Restriction is that DSDT should never be greater than original, lower is not a problem.

It should work but need somebody to test.

 

Fred

Hi fred,Yes i have such hardware

 

Inviato dal mio ASUS_Z00UD utilizzando Tapatalk

Link to comment
Share on other sites

What do you mean by 'offset'? I'm not on OS X, so can't run the app right now. :/

 

I mean address in 64 k space. 

 

Look at that.

 

OSK0 8336 0 ch8* 6849 1

OSK1 8336 0 ch8* 6887 1

 

MSTj 384 0 ui8  1282 16392

MSTf 384 0 ui8  1283 16392

 

 

HC0N 448 0 ui8  2008 8192

MSLS 448 0 ui8  2009 8192

GT0C 640 0 ui16 2012 8192

FRmp 640 0 ui16 2014 8192

 

https://www.dropbox.com/s/qkw37qokdxvw9oi/2013IM27.csv?dl=0

 

Fred

Link to comment
Share on other sites

Memory32Fixed (ReadWrite,
                       0xFEF00000,         // Address Base
          ====>        0x00010000,         // Address Length
                      )

 

If you mean this by '64 k space', this is for MMIO. Can't think of a reason why a key would point there tbh...

Link to comment
Share on other sites

Are there any future for Ozmosis and AMD GPU cards?

In the Clover section I can see, that they are working for it.

 

But how about Ozmosis?

 

I got following lines on verbose boot:

verbosebootamo5pv4zcx.jpg

 

Mainboard: Z77MX-QUO-AOS

GPU: PowerColor RX480 8GB

 

Screenshot is from setting GPU as primary output.

When I remove the ID from AMD4100X Kext I can boot, but only with VESA Graphics...

Link to comment
Share on other sites

Did you add the following NVRAM settings either per terminal or in your hopefully available Defaults.plist?

 

Terminal-Version:

Inject ATI
==========

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:DisableAtiInjection=%00

Changing ATI Framebuffers
=========================

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer=Futomaki

Or based on VendorSubsystemId

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer10029440=Futomaki

Or based on pci addressing

sudo nvram 1F8E0C02-58A9-4E34-AE22-2B63745FA101:AtiFramebuffer00.01.00=Futomaki

Remark: The Framebuffer "Futomaki" is only an example and should not be used for your Card. Same goes for the "VendorSubsystemId" with the numbers "10029440"...

 

Defaults.plist-Version:

// If DisableAtiInjection NEEDS to be enabled, change second line bellow and set to true, then add both line in Defaults.plist
<key>DisableAtiInjection</key>
<false/>

// If AtiFramebuffer NEEDS to be changed, modify second line bellow and set to correct one, then add both line in Defaults.plist
<key>AtiFramebuffer</key>
<string>ReplaceMe</string>
!! WARNING DisableAtiInjection needs to be set to false to function !!
  • Like 1
Link to comment
Share on other sites

×
×
  • Create New...