Jump to content

Ozmosis

xpamamadeus

By xpamamadeus,
in Ozmosis

 Share
6,231 posts in this topic

Recommended Posts

maleorderbride
maleorderbride
Posted
Posted

Ok here is a bash script that you can use, just replace the "Replace"

#!/bin/bash
#SMBIOS
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=MM61.88Z.0106.B00.1208091121
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=Macmini6,2
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=Macmini
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-F65AE981FFA204ED
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU=MD389LL/A
#OzmosisNVRAM
sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-fakesmc-use-nvram"

#APPLE
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=Replace e.g %90%90%9090%90
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures=%C0%00%7F%FF
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask=%C0%00%14%03 

#CODE
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosDate
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BoardVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:Manufacturer
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProcessorSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ChassisAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:CpuType
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:EnclosureType

#CODE
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

The "ROM" is your Lan wired MAC address.

Ozmosis uses it's own nvram to pass boot-args.

OK, and how do I add npci=0x2000 or its equivalent? 

There has to be a way to do it in the BIOS image, but yes.  Adding the boot-args to the com.apple.boot.plist does succeed in passing them on to the OS.

 

However, that method means I can not boot an App Store download =/

Link to comment
Share on other sites
The_Village_Idiot
The_Village_Idiot
Posted
Posted

Here you go...

An Ozmosis firmware for P8H77-M LE.

I tested it and it works.

 

You can flash it using FTK under Windows or the new DPCIManager (which uses flashrom) under OS X.

 

Alternatively you can download it here:

https://www.dropbox.com/s/8mz31poubfk1vof/P8H77MLE_Ozmosis.zip

 

PMPatch is applied on the BIOS.

It also has mods for Asus SLIC and custom LAN MAC address (de:ad:ba:be:c0:de)

 

Enjoy :D

a few questions, as i want to multiboot windows 7 and osx on this same exact board.

 

1. any adverse effect on my windows installation?

2. can this be used using asus updater or via FTK only?

3. i have already downloaded your other modified BIOS for this same board (the one which came with DSDT), do i use that or this osmosis?

Link to comment
Share on other sites
Andy Vandijck
Andy Vandijck
Posted
Posted

a few questions, as i want to multiboot windows 7 and osx on this same exact board.

 

1. any adverse effect on my windows installation?

2. can this be used using asus updater or via FTK only?

3. i have already downloaded your other modified BIOS for this same board (the one which came with DSDT), do i use that or this osmosis?

1. I use Windows 7 in UEFI install.

It works in that case.

Don't know about legacy Windows boot, haven't tested that.

It works just fine.

2. It's a binary, not a cap file.

You can flash it with flashrom under OS X or use FTK on Windows.

3. This Ozmosis contains a mod to directly boot OS X.

You can thus choose.

Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted
How to change smbios to macmini6,2?
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=MM61.88Z.0106.B00.1208091121
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=Macmini6,2
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=xxxxxxxxxxxx
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=Macmini
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-F65AE981FFA204ED

xxxxxxxxxxxx=serial that need to be generated using clover comfigurator or chameleon wizard. 

Hope this will work for u.

Enjoy

 

 

Hello xpamamadeus,

 

setting the nvram variables does not survive a reboot.

Even settings boot-args='dart=0 -v' is removed from nvram after reboot.

 

Is there any trick to unlock write-access into nvram?

My board is ASUS P8Z77-V LX UEFI ver.2204.

 

Also one question regarding HermitShell - how can it be access?

 

best regards

Link to comment
Share on other sites
Son_Of_Mole
Son_Of_Mole
Posted
Posted

Hi,

 

I have a few questions guys,

 

What is the point of this? From what I can tell you still need all the files and setting that are used in the normal hackintosh bootloader's. All we are doing is making it harder to change settings / bootloader once we implement it into the BIOS.

 

I can see that it would be nice not to have to modify the Apple installers to install the OS and just boot the USB drive right after making it from the App store... But the con's do out weigh the pro's

 

Is there anything new here? Am I missing something or is it just a new way to play around with?

 

Let me know what you think,

 

Thanks

 

 Ross

Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted

 

sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-fakesmc-use-nvram npci=0x2000"

 

Your Firmware MUST support NVRAM writing, sometimes you need to backtrack a few versions and find one that does.

 

 

Curiosity aside, my firmware does support NVRAM writing booting from chameleon, only osmosis does not access the written values.

 

@Ross, the pro is you don't need a bootloader installed to a HFS+ partiton, you can choose OS X out of bios bootmenu!

That's cluesless. FakeSMC is load from an FFS module. Additional you can add other kexts as UEFI modules, so you can make

a very stable and static mod.

 

The con in the case of osmosis is, that it's not opensource and build for a specific gigabyte board.

 

Loading chameleon or Clover as an UEFI bootloader would be the most awesome stuff I guess ;)

I found some guys already working on it at projectosx.

Link to comment
Share on other sites
maleorderbride
maleorderbride
Posted
Posted

Thanks for that STLVNUB.  It does indeed appear that this bios revision (4302) does not allow me to write to NVRAM on my P9X79 Pro.  I will check earlier versions to see if they allow it.

 

This may be a silly question, but if earlier BIOS versions routinely gain or lose the ability to write to NVRAM from within the OS, then might we not edit that ability back into the latest BIOS versions ourselves?

Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted 
29:165 00:000 Found Mac OS X 10.8.4 (10.8.4) 12E55
29:165 00:000 Found 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args "<null string>" (0)
29:165 00:000 Found LoadedImage->LoadOptions "<null string>" (0)
29:165 00:000 LoadedImage->LoadOptions "slide=0" (16)

Try sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-v"

then type sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args 

It should say "-v"

Reboot and check bootlog

or run sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args again and see if it says "-v"

if not you need to file FW that works (1701 or 1440)

You may loose a few features but you will gain more ;)

 

I'm sorry to say the settings are gone on reboot :(

Link to comment
Share on other sites
truemac
truemac
Posted
Posted

hi

iMessage Works again!!!

i had to change the BaseBoardSerial number,

like this

sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=C02140302XXXXXXX

MLB shows now 17 Bytes, befor shows 12 Bytes

06:343 00:000 Setting RS+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB 17 bytes - Success
06:343 00:000 Setting RS+BS 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM 6 bytes - Success

Xp thank you for a nice theard!

  • Like 1
Link to comment
Share on other sites
ivanwinkel
ivanwinkel
Posted
Posted

Thx for THE hard work.

I tried to make a modded bios myself.

And got iT working, but with one problem. Nvram didn't stick.

 

Now I finaly found THE bios wich holds THE nvram.

ITS bios f2f.

I am busy modding iT als we speak.

Let you al know how iT Will turn out

Link to comment
Share on other sites
tonydickinson
tonydickinson
Posted
Posted

@STLVNUB

 

If I can find a reasonably priced case, power supply and Ram I might have a go at using the Gigabyte Z77MX-D3H TH with Ozmosis, as you have had great success with a very similar motherboard.

 

The important issue is saving nvram - looking at the BIOS available ex GB your board has far more available, mine has only three F6b, F5, and F3. I see the latest official BIOS for your board is F16d.

 

I am asking this as I am slightly wary of buying the bits I need, if the BIOS available lock the OS writing to nvram.

 

So question - Have you any thoughts to guide me on this issue?

 

Thanks

Link to comment
Share on other sites
tonydickinson
tonydickinson
Posted
Posted

I would think that with the F3 and F5 bios, NVRAM is writable, so I would go with the F5.

F6b has Secure boot and I think part of that is the locking of NVRAM. Maybe Google might help with this.

 

I would say my F13 is possibly the base for the F3. There seems to be a pattern here.

Mine has been out a little longer, hence the more bios files. I am using F15, The F16 series started having Secure boot enabled and that is when the NVRAm locking started.

 

Ozmosis can only get better, and by that, I mean support some of the Newer boards (Z87 etc) so it is up to you.

 

It's looks like a nice MB, probably closer to the Quo board, If iI had the money, I'd probably go for it.

 

Hope this helps.

Thanks STLVNUB very useful. Where I live,  we get good deals on IT stuff as its very competitive. I had an issue with ITunes playing movies and managed to get a good deal off a friend who has a store here and I got the GB Z77 board to see whether the same iTunes issue would manifest  on the GB board, which had green screen issues while trying to play iTunes movies on the Z77 Asus Sabertooth. There was no change and after a couple of days reverted back to the Sabertooth.

 

Z87 well all the signs were that the saving nvram issues where confined to Z77 and as you will see in the AsusROG thread  the indications where that Z87 were not affected. But alas this board ( the ASUS Z87 Dual Deluxe with Thunderbolt2 ) does require EmuVariableUefi-64.efi  to save Nvram. I was disappointed as a couple of guys with the Gryphon (is it?) suggests that nvram is saved. No so in my case - also there are not too many "old" bios versions around for the Z87.

 

See http://rog.asus.com/forum/showthread.php?32906-ASUS-UEFI-vBIOS-tool-for-GTX-600-series-cards!-It-s-Here!/page10 posts #91/92/94/95

EDIT: Rereading all that - I wonder if he is mistaken as some Gigabyte BIOS are the same. My own noob guess is that this comes from Intel rather than the  Mboard manufactures.

I will let you know how I get on.

Link to comment
Share on other sites
SyJet
SyJet
Posted
Posted

Ok here is a bash script that you can use, just replace the "Replace"

#!/bin/bash
#SMBIOS
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion=MM61.88Z.0106.B00.1208091121
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName=Macmini6,2
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily=Macmini
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId=Mac-F65AE981FFA204ED
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace
sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU=MD389LL/A
#OzmosisNVRAM
sudo nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:boot-args="-fakesmc-use-nvram"

#APPLE
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM=Replace e.g %90%90%9090%90
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures=%C0%00%7F%FF
sudo nvram 4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask=%C0%00%14%03 

#CODE
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BiosDate
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductName
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductFamily
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProductId
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BoardVersion
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:Manufacturer
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ProcessorSerial
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSKU
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:ChassisAssetTag
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:CpuType
#4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:EnclosureType

#CODE
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:ROM
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:MLB
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeatures
#4D1EDE05-38C7-4A6A-9CC6-4BCCA8B38C14:FirmwareFeaturesMask

The "ROM" is your Lan wired MAC address.

Ozmosis uses it's own nvram to pass boot-args.

 

Your Firmware must support NVRAM saving, sometimes you may need to backtrack a few versions to find one that does, then any NVRAM settings will stick.

I had to go from F16g to F15

 

 

 

Anyone wishing to do this mod, may find this handy

#205

Turns kexts into Ffs for inclusion into Firmware.  ;)

What is the difference between 

sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace

and

sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace

?

 

And what about the iMac13,2?

Link to comment
Share on other sites
TimeWalker75a
TimeWalker75a
Posted
Posted

What is the difference between 

sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:SystemSerial=replace

and

sudo nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:BaseBoardSerial=Replace

?

 

And what about the iMac13,2?

System Serial is just regular serial number of a given Mac model, BaseBoard Serial is 17 character (essentially MLB), namely used for Messages.

Link to comment
Share on other sites
maleorderbride
maleorderbride
Posted
Posted

If the ability to write to NVRAM changes with a BIOS update then clearly the ability to do so is a part of the BIOS programming.

 

Like any other part we should be able to isolate it, or the parts that are requisite for it, and then insert them into BIOS versions that do not normally have this ability.

Link to comment
Share on other sites
StoneTemplePilots
StoneTemplePilots
Posted
Posted

If the ability to write to NVRAM changes with a BIOS update then clearly the ability to do so is a part of the BIOS programming.

 

Like any other part we should be able to isolate it, or the parts that are requisite for it, and then insert them into BIOS versions that do not normally have this ability.

 

But as mentioned above the issues writing to NVRAM is NOT a BIOS version issue, cause booting from Clover or Chameleon you can still write to NVRAM, also from linux.

The problem is ozmosis-specific :) and as long as ozmosis isn't opensource we won't be able to figure it out.

For the moment I decided to quit with ozmosis due to several other issues, for example in UEFI shell it's causing a sudden reset/reboot, problem verified on P8Z77-V LX and GA-Z77-D3H.

Link to comment
Share on other sites
xpamamadeus
xpamamadeus
Posted
  • Author
Posted

But as mentioned above the issues writing to NVRAM is NOT a BIOS version issue, cause booting from Clover or Chameleon you can still write to NVRAM, also from linux.

The problem is ozmosis-specific :) and as long as ozmosis isn't opensource we won't be able to figure it out.

For the moment I decided to quit with ozmosis due to several other issues, for example in UEFI shell it's causing a sudden reset/reboot, problem verified on P8Z77-V LX and GA-Z77-D3H.

http://www.projectosx.com/forum/index.php?showtopic=2854

Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...