Kynyo Posted November 27, 2015 Share Posted November 27, 2015 Or you could download Coderush’s UEFIExtract tool then load up terminal and run $ ./UEFIExtract /path/to/Z77MXQUOAOS.H2N.OZ1669M.ROM Then drill down to the relevant section of the resulting expanded directory: Z77MXQUOAOS.H2N.OZ1669M.ROM.dump/2\ BIOS\ region/2\ 8C8CE578-8A3D-4F1C-9935-896185C32DD3/0\ FV_MAIN_NESTED/0\ Compressed\ section/0\ Volume\ image\ section/0\ 8C8CE578-8A3D-4F1C-9935-896185C32DD3/191\ OzmosisDefaults and open the 0\ Compressed\ section/0\ Raw\ section/body.bin file in a text editor. Good tip! Thanks. Link to comment Share on other sites More sharing options...
Aigors Posted November 27, 2015 Share Posted November 27, 2015 As far you know there is a working mouse in this version? Link to comment Share on other sites More sharing options...
alanlcarlos Posted November 27, 2015 Share Posted November 27, 2015 This version of HDMI / DVI does not work, what do I do? Ozmosis old and Clover Work VGA work, but not Widescreen Resolution. z77m-d3h Gt640 2gb Ozmosis 1669 Link to comment Share on other sites More sharing options...
Aigors Posted November 27, 2015 Share Posted November 27, 2015 This version of HDMI / DVI does not work, what do I do? Ozmosis old and Clover Work VGA work, but not Widescreen Resolution. z77m-d3h Gt640 2gb Ozmosis 1669 Have you tried to disable NvidiaCard using DisableNvidiaInjection? As far The King Wrote, you have to disable nvidia card Link to comment Share on other sites More sharing options...
Aigors Posted November 27, 2015 Share Posted November 27, 2015 Do i need to use special bootargs ? Link to comment Share on other sites More sharing options...
Allrounder Posted November 27, 2015 Share Posted November 27, 2015 How about FileVault2 and 1669? Link to comment Share on other sites More sharing options...
alanlcarlos Posted November 27, 2015 Share Posted November 27, 2015 DisableNvidiaInjection true or false, both not solve. Monitor is not recognized the system starts with black screen. But I can see the screen with the Splashtop app on iPad. QE/CI NVidia driver Work, but not Hdmi/ Dvi Link to comment Share on other sites More sharing options...
mhaeuser Posted November 27, 2015 Share Posted November 27, 2015 Do i need to use special bootargs ? No. How about FileVault2 and 1669? Not quite there. Link to comment Share on other sites More sharing options...
THe KiNG Posted November 27, 2015 Share Posted November 27, 2015 DisableNvidiaInjection true or false, both not solve. Monitor is not recognized the system starts with black screen. But I can see the screen with the Splashtop app on iPad. QE/CI NVidia driver Work, but not Hdmi/ Dvi Dumps? Link to comment Share on other sites More sharing options...
alanlcarlos Posted November 27, 2015 Share Posted November 27, 2015 Used this http://www.hackintosh-forum.de/index.php/Attachment/16449-Z77MD3H-15a-OZM-DSDT-G-1669m-rom-zip/ Link to comment Share on other sites More sharing options...
Mrengles Posted November 27, 2015 Share Posted November 27, 2015 Does anyone know why my Macintosh HD and Recover HD are not showing as boot options? The physical drives show under AHCI SATA setup in UEFI/Bios but not as boot option for Ozmosis? Link to comment Share on other sites More sharing options...
THe KiNG Posted November 27, 2015 Share Posted November 27, 2015 Used this http://www.hackintosh-forum.de/index.php/Attachment/16449-Z77MD3H-15a-OZM-DSDT-G-1669m-rom-zip/ ..and where are the dumps? With/Without DisableNvidiaInjection Link to comment Share on other sites More sharing options...
bs0d Posted November 27, 2015 Share Posted November 27, 2015 Does anyone know why my Macintosh HD and Recover HD are not showing as boot options? The physical drives show under AHCI SATA setup in UEFI/Bios but not as boot option for Ozmosis? maybe they're not blessed ? Link to comment Share on other sites More sharing options...
Mrengles Posted November 27, 2015 Share Posted November 27, 2015 maybe they're not blessed ? How would I bless them? $sudo touch /Volumes/Macintosh \HD Link to comment Share on other sites More sharing options...
bs0d Posted November 27, 2015 Share Posted November 27, 2015 (edited) something like sudo bless --folder "/Volumes/Backup/System/Library/CoreServices" the os x installer would normally do this, obviously substitute the path to CoreServices info from here https://bombich.com/kb/ccc4/what-makes-volume-bootable Edited November 27, 2015 by bs0d Link to comment Share on other sites More sharing options...
Mrengles Posted November 27, 2015 Share Posted November 27, 2015 (edited) something like sudo bless --folder "/Volumes/Backup/System/Library/CoreServices" the os x installer would normally do this, obviously substitute the path to CoreServices info from here https://bombich.com/kb/ccc4/what-makes-volume-bootable Thanks! I'll take a look.. Didn't work, but thanks for trying to help. If i go back to 1479 works just fine... Oz 1669M won't even find my El Capitan Installer USB... Its not finding any of my OS X Maybe OZMTool 0.3 is not working right with 1669M? Edited November 27, 2015 by Mrengles Link to comment Share on other sites More sharing options...
bs0d Posted November 27, 2015 Share Posted November 27, 2015 which version of HFS+ filesystem driver are you using ? Link to comment Share on other sites More sharing options...
Mrengles Posted November 27, 2015 Share Posted November 27, 2015 What are the minimal FFS files need for Ozmosis 1669M same as 1479 when injecting into uefi/bios? Link to comment Share on other sites More sharing options...
bs0d Posted November 27, 2015 Share Posted November 27, 2015 ozmosis.ffs & hfsplus.ffs Link to comment Share on other sites More sharing options...
Mrengles Posted November 27, 2015 Share Posted November 27, 2015 (edited) which version of HFS+ filesystem driver are you using ? The one extracted from 1669M... Good idea, I'm gonna try the one from my previous working setup... I tried using the HFSPlus.ffs from 1479 but having the same effect. The second after flashing my older Oz1479 firmware the Darwin Boot options appear. What dumps logs do the developers need? So that I can help provide feedback to get this fixed or figured out? If I add the HermitShellX64.ffs it will show as a boot device, but thats all. enabling the ASMedia SATAS Mode doesn't change anything either. <?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>BaseBoardAssetTag</key> <string>Not Specified</string> <key>BaseBoardSerial</key> <string></string> <key>BiosDate</key> <string>06/12/2013</string> <key>BiosVersion</key> <string>MP61.88Z.0116.B04.1312061508</string> <key>BoardVersion</key> <string>MacPro6,1</string> <key>ChassisAssetTag</key> <string>Pro-Enclosure</string> <key>EnclosureType</key> <integer>7</integer> <key>FirmwareFeatures</key> <real>3758355766</real> <key>FirmwareFeaturesMask</key> <real>3758358327</real> <key>FirmwareRevision</key> <integer>1</integer> <key>FirmwareVendor</key> <string>Apple Inc.</string> <key>HardwareAddress</key> <string></string> <key>HardwareSignature</key> <string></string> <key>Manufacturer</key> <string>Apple Inc.</string> <key>ProductFamily</key> <string>MacPro</string> <key>ProductId</key> <string>string> <key>ProductName</key> <string>MacPro6,1</string> <key>SystemSKU</key> <string>Not Specified</string> <key>SystemSerial</key> <string></string> <key>SystemVersion</key> <string>1.0</string> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>AndroidDiskOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid androidboot.hardware=android_x86 ro SRC=$path</string> <key>AndroidDiskTemplate</key> <string>$label</string> <key>LinuxDiskTemplate</key> <string>$label $build</string> <key>LinuxDiskOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid ro</string> <key>LinuxRescueOptionTemplate</key> <string>initrd=$initfs root=UUID=$uuid ro</string> <key>LinuxRescueDiskTemplate</key> <string>$label Rescue</string> <key>AAPL,ig-platform-id</key> <integer>23199751</integer> <key>AAPL,snb_platform_id</key> <integer>196624</integer> <key>AcpiLoaderMode</key> <integer>69</integer> <key>AtiFramebuffer</key> <string>Not Specified</string> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinCoreStorageTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label ($platform.$major.$minor)</string> <key>DisableAtiInjection</key> <false/> <key>DisableBootEntriesFilter</key> <false/> <key>DisableIntelInjection</key> <false/> <key>DisableNvidaInjection</key> <false/> <key>DisableVoodooHda</key> <true/> <key>UserInterface</key> <false/> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>csr-active-config</key> <integer size=32>0x0</integer> <key>boot-args</key> <string></string> </dict> </dict> </plist> Thanks bs0d for your help so far! Gratitude, Robert aka Mrengles Edited November 28, 2015 by Mrengles Link to comment Share on other sites More sharing options...
alanlcarlos Posted November 28, 2015 Share Posted November 28, 2015 ..and where are the dumps? With/Without DisableNvidiaInjection sorry , did not understand , what is " dump" ? logs or ozmosisdefaults with DisableNvidiaInjection and without ? Link to comment Share on other sites More sharing options...
bs0d Posted November 28, 2015 Share Posted November 28, 2015 @Mrengles - try with a vanilla Defaults.plist from the newest released rom (there could be an issue with the file and the relevant templates aren't being added as variables). You can try entering the HermitShell and use the bdmesg command there to view/make a log. You can also load boot.efi (fsX:\System\Library\CoreServices\boot.efi) through the shell and use bdmesg in OS X. (where fsX is the volume containing OS X) Link to comment Share on other sites More sharing options...
Mrengles Posted November 28, 2015 Share Posted November 28, 2015 @Mrengles - try with a vanilla Defaults.plist from the newest released rom (there could be an issue with the file and the relevant templates aren't being added as variables). You can try entering the HermitShell and use the bdmesg command there to view/make a log. You can also load boot.efi (fsX:\System\Library\CoreServices\boot.efi) through the shell and use bdmesg in OS X. (where fsX is the volume containing OS X) sure I'll give it a try and post back... Can you please post the default.plist file you would like me to use? I have seen a couple since the 1669 release but not sure which is newest... Link to comment Share on other sites More sharing options...
mhaeuser Posted November 28, 2015 Share Posted November 28, 2015 sure I'll give it a try and post back... Can you please post the default.plist file you would like me to use? I have seen a couple since the 1669 release but not sure which is newest... Just use none, Ozmosis has the untouched one built-in. Link to comment Share on other sites More sharing options...
Mrengles Posted November 28, 2015 Share Posted November 28, 2015 (edited) Just use none, Ozmosis has the untouched one built-in. Okay will do... in the mean while here's the bdmesg log... I used the attached defaults.plist and tried booting without defaults.plist same results and same bdmesg log. If I try to manually boot.efi with fs1:\System\Library\CoreServices\boot.efi just sits at black screen and hangs... =( bdmesg.txt Defaults.txt Edited November 28, 2015 by Mrengles Link to comment Share on other sites More sharing options...
Recommended Posts