Jump to content

OZMTool - An Ozmosis Toolbox


tuxuser
 Share

73 posts in this topic

Recommended Posts

Hi,

 

I was using OZMtool 0.3 in windows to roll my own using ozmtool --create by injecting ffs and dsdt files into a rom and I got this error message at end:

 

NOTE: 'parseInputFile: descriptor parsing failed, descriptor region has intersection with bios region' can be ignored..

 

Worry??

 

Thanks

Link to comment
Share on other sites

  • 2 weeks later...

NOTE: 'parseInputFile: descriptor parsing failed, descriptor region has intersection with bios region' can be ignored..

 

It already says to ignore that... so just do..

It just happens cause gigabyte does not follow the specs 100%

 

Really nothin critical

Link to comment
Share on other sites

  • 4 weeks later...

Hi Tuxuser,

 

Thanks for a great tool.

I saw in release .3 the option "- Adding option to replace .efi files inside FFS capsules (Drivers, Ozmosis)

Is it possible to replace an existing driver in Ozmosis for an other one e.g. AppleIntelE1000e.fss ?

 

Thanks in advance

Link to comment
Share on other sites

  • 3 weeks later...

Hi, one "bugreport" or i dont know, if i use ozmtools to insert patched DSDT i saw nothing strange, no error but my asus P8Z77-I Deluxe doesn't boot, if i use "old method" ( dsdt2bios from FredWst ) i get : this file contains :ROM section, i don't know why with ozmtools it seems goes right, but i use ozmtools it goes wrong 

 

Many thanks

Link to comment
Share on other sites

Hi, one "bugreport" or i dont know, if i use ozmtools to insert patched DSDT i saw nothing strange, no error but my asus P8Z77-I Deluxe doesn't boot, if i use "old method" ( dsdt2bios from FredWst ) i get : this file contains :ROM section, i don't know why with ozmtools it seems goes right, but i use ozmtools it goes wrong 

 

Many thanks

Here you go and good luck!!!!

 

  • Like 1
Link to comment
Share on other sites

I first extract DSDT with your rom after use MaciASL and fixed...After this I use OZMTool and inject in your rom file!!!!

Thank you, it's' my same procedure, i will try after work when will be at home, in my case it doesn't work it seems that AmboardInfo has several section there are not present in other bios, i will inform you about any progress 

Link to comment
Share on other sites

Thank you, it's' my same procedure, i will try after work when will be at home, in my case it doesn't work it seems that AmboardInfo has several section there are not present in other bios, i will inform you about any progress 

Ok. I‘here and you post question if something is not clear!!

Link to comment
Share on other sites

Do you try my rom file?

Yes, i' tried your rom file without success 

 

post-840738-0-16484500-1434045416_thumb.png

 

As you can see in Amiboardinfo there are several section, i suspect there are responsible for not working if use ozmotool --dsdtinject 

Link to comment
Share on other sites

./OZMTool --ozmcreate -f Your ffs files -d your DSDT.aml -i your original rom -o your rom created
./OZMTool --dsdtextract -i your original rom -o Folder for extracted DSDT

I know command line, now i'm using my own bios with original DSDT at the end of installation, i will try to integrate DSDT with ozmtool program

Link to comment
Share on other sites

I've been having trouble getting my BIOS patched with Ozmosis.  I have an ASUS Z87I-DELUXE motherboard.  Every time I run the program, I get this message:

Treys-iMac:OZMTool_v0 Trey$ ./OZMTool --ozmcreate --aggressivity 1 -f ./ffs --dsdt DSDT.aml --out Z87ID-OZM.CAP --input Z87ID-1104-ORIG.CAP
OZMTool - v0.3
Warning: No KEXT-dir given! Injecting only Ozmosis files!
Info: Aggressivity level set to 'Delete network stuff from BIOS'...
Inserting supplied DSDT into image...
* Dumped AmiBoardInfo from BIOS...
* Injecting DSDT into AmiBoardInfo...
Info: PE32 has DYNAMIC_BASE set -> no Code Patching required...
 * Patching header...
SizeOfInitialzedData: E460 --> ED20
SizeOfImage: ED40 --> F600
 * Patching directory entries...
 - DataDirectory 05:
VirtualAddress: ED20 --> F5E0
 * Patching sections...
 - Section: .text
Nothing to do here...
 - Section: .rdata
Nothing to do here...
 - Section: .data
PhysicalAddress: E30E --> EBCE
SizeOfRawData: E320 --> EBE0
 - Section: .empty
VirtualAddress: ED00 --> F5C0
PointerToRawData: ED00 --> F5C0
 - Section: .reloc
VirtualAddress: ED20 --> F5E0
PointerToRawData: ED20 --> F5E0
 * Patching actual relocations...
 - Relocation Table 0:
Nothing to do here - VirtualAddress < DSDTOffset (0 < A70)
 - Relocation Table 1:
 - VirtualAddress: E000 --> F000
 - Relocation: 0
Offset: BB8 --> 478
 - Relocation: 1
Offset: C30 --> 4F0
 - Relocation: 2
Offset: C38 --> 4F8
* Injected new DSDT into AmiBoardInfo
* Replaced AmiBoardInfo in BIOS with patched one
Injecting FFS into BIOS...
 * Current file: 'AppleIntelE1000e.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'BrcmPatchRAM.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'FakeSMC.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'realtekALC.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'toledaARPT.ffs'...
* File not existant, inserting at the end of volume
Deleting network BIOS stuff (PXE) to save space...
* Removed 'TcpDxe' [B1625D3C-9D2D-4E0D-B864-8A763EE4EC50] succesfully!
* Removed 'Dhcp4Dxe' [8DD9176E-EE87-4F0E-8A84-3F998311F930] succesfully!
* Removed 'Ip4ConfigDxe' [8F9296EF-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Ip4Dxe' [8F92960F-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Mtftp4Dxe' [61AFA223-8AC8-4440-9AB5-762B1BF05156] succesfully!
* Removed 'Udp4Dxe' [10EE5462-B207-4A4F-ABD8-CB522ECAA3A4] succesfully!
* Removed 'Dhcp6Dxe' [8DD9176D-EE87-4F0E-8A84-3F998311F930] succesfully!
* Removed 'Ip6Dxe' [8F92960E-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Mtftp6Dxe' [61AFA251-8AC8-4440-9AB5-762B1BF05156] succesfully!
* Removed 'Udp6Dxe' [10EE54AE-B207-4A4F-ABD8-CB522ECAA3A4] succesfully!
Deleting non required Filesystem FFS...
* Removed 'FileSystem' [93022F8C-1F09-47EF-BBB2-5814FF609DF5] succesfully!
Reconstructing final image...
reconstruct: Aptio capsule checksum and signature can now become invalid
reconstructVolume: 8C8CE578-8A3D-4F1C-9935-896185C32DD3: root volume can't be grown
ERROR: Image exploded...
! Program exited with errors !


Status code: 17

I'm not sure what to do next to solve my problem. Any ideas?

 

Stock BIOS: Z87I-DELUXE-SI-1204.zip

Link to comment
Share on other sites

I've been having trouble getting my BIOS patched with Ozmosis.  I have an ASUS Z87I-DELUXE motherboard.  Every time I run the program, I get this message:

Treys-iMac:OZMTool_v0 Trey$ ./OZMTool --ozmcreate --aggressivity 1 -f ./ffs --dsdt DSDT.aml --out Z87ID-OZM.CAP --input Z87ID-1104-ORIG.CAP
OZMTool - v0.3
Warning: No KEXT-dir given! Injecting only Ozmosis files!
Info: Aggressivity level set to 'Delete network stuff from BIOS'...
Inserting supplied DSDT into image...
* Dumped AmiBoardInfo from BIOS...
* Injecting DSDT into AmiBoardInfo...
Info: PE32 has DYNAMIC_BASE set -> no Code Patching required...
 * Patching header...
SizeOfInitialzedData: E460 --> ED20
SizeOfImage: ED40 --> F600
 * Patching directory entries...
 - DataDirectory 05:
VirtualAddress: ED20 --> F5E0
 * Patching sections...
 - Section: .text
Nothing to do here...
 - Section: .rdata
Nothing to do here...
 - Section: .data
PhysicalAddress: E30E --> EBCE
SizeOfRawData: E320 --> EBE0
 - Section: .empty
VirtualAddress: ED00 --> F5C0
PointerToRawData: ED00 --> F5C0
 - Section: .reloc
VirtualAddress: ED20 --> F5E0
PointerToRawData: ED20 --> F5E0
 * Patching actual relocations...
 - Relocation Table 0:
Nothing to do here - VirtualAddress < DSDTOffset (0 < A70)
 - Relocation Table 1:
 - VirtualAddress: E000 --> F000
 - Relocation: 0
Offset: BB8 --> 478
 - Relocation: 1
Offset: C30 --> 4F0
 - Relocation: 2
Offset: C38 --> 4F8
* Injected new DSDT into AmiBoardInfo
* Replaced AmiBoardInfo in BIOS with patched one
Injecting FFS into BIOS...
 * Current file: 'AppleIntelE1000e.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'BrcmPatchRAM.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'FakeSMC.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'realtekALC.ffs'...
* File not existant, inserting at the end of volume
 * Current file: 'toledaARPT.ffs'...
* File not existant, inserting at the end of volume
Deleting network BIOS stuff (PXE) to save space...
* Removed 'TcpDxe' [B1625D3C-9D2D-4E0D-B864-8A763EE4EC50] succesfully!
* Removed 'Dhcp4Dxe' [8DD9176E-EE87-4F0E-8A84-3F998311F930] succesfully!
* Removed 'Ip4ConfigDxe' [8F9296EF-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Ip4Dxe' [8F92960F-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Mtftp4Dxe' [61AFA223-8AC8-4440-9AB5-762B1BF05156] succesfully!
* Removed 'Udp4Dxe' [10EE5462-B207-4A4F-ABD8-CB522ECAA3A4] succesfully!
* Removed 'Dhcp6Dxe' [8DD9176D-EE87-4F0E-8A84-3F998311F930] succesfully!
* Removed 'Ip6Dxe' [8F92960E-2880-4659-B857-915A8901BDC8] succesfully!
* Removed 'Mtftp6Dxe' [61AFA251-8AC8-4440-9AB5-762B1BF05156] succesfully!
* Removed 'Udp6Dxe' [10EE54AE-B207-4A4F-ABD8-CB522ECAA3A4] succesfully!
Deleting non required Filesystem FFS...
* Removed 'FileSystem' [93022F8C-1F09-47EF-BBB2-5814FF609DF5] succesfully!
Reconstructing final image...
reconstruct: Aptio capsule checksum and signature can now become invalid
reconstructVolume: 8C8CE578-8A3D-4F1C-9935-896185C32DD3: root volume can't be grown
ERROR: Image exploded...
! Program exited with errors !


Status code: 17

I'm not sure what to do next to solve my problem. Any ideas?

 

Stock BIOS: Z87I-DELUXE-SI-1204.zip

You need more room to put ozmosis stuff, try to use aggressivity switch 

Dont use pure bios, it's CAP file it means it's' signed and any operation invalid the signing, if you try to flash with utility inside bios, fail because the signature is invalid due to manipulation.

Z87I-DELUXE-SI-Ozmo-1204.zip

 

This is your bios with minimal required ozmosis stuff, it's' missing DSDT because i cant edit  

Link to comment
Share on other sites

 

You need more room to put ozmosis stuff, try to use aggressivity switch 

Dont use pure bios, it's CAP file it means it's' signed and any operation invalid the signing, if you try to flash with utility inside bios, fail because the signature is invalid due to manipulation.

zip.gif  Z87I-DELUXE-SI-Ozmo-1204.zip   5.32MB   0 downloads

 

This is your bios with minimal required ozmosis stuff, it's' missing DSDT because i cant edit  

 

Thank you Aigors.  The way I've flashed Oz BIOS before was using the EZFlash button on the back of my mobo with the CAP file on my USB.  It seems to skip the signing/verification problems..

T

How would I flash the BIN file you gave me?  If I were to do it again, how would I get the BIN from the CAP file to patch with Ozmtool?

Link to comment
Share on other sites

Thank you Aigors.  The way I've flashed Oz BIOS before was using the EZFlash button on the back of my mobo with the CAP file on my USB.  It seems to skip the signing/verification problems..

T

How would I flash the BIN file you gave me?  If I were to do it again, how would I get the BIN from the CAP file to patch with Ozmtool?

 

My fault, this is cap file with minimum ozmosis requirements 

Z87I-DELUXE-OZMO-SI-1204-CAP.zip

 

post-840738-0-13441800-1434551763_thumb.png

Link to comment
Share on other sites

  • 1 month later...

http://www.insanelymac.com/forum/topic/301407-guide-insert-ozmosis-into-uefi-bios/?p=2158000

C:\Users\fbifido\Desktop\BIOS>OZMTool --ozmcreate --aggressivity 1 --compressdxe --out EFI_OZM.ROM --input EFI.ROM
OZMTool - v0.3
ERROR: No FFS directory file supplied!

C:\Users\fbifido\Desktop\BIOS>pause
Press any key to continue . . .

 

Any Help Please & Thanks

Link to comment
Share on other sites

 Share

×
×
  • Create New...