ammoune78 Posted June 12, 2017 Share Posted June 12, 2017 Only SMC 2.22f6 modified to avoid kp: Fake-2.22f6-SMC.zip Link to comment Share on other sites More sharing options...
Kynyo Posted June 12, 2017 Share Posted June 12, 2017 I had to remove GPUSensors from bios to avoid KP, i guess its due Pascal GPU inside the system. Still not able to cleaninstall completely using Ozmosis, i receive ROM does not support APFS, firmwarecheck error. Oz boots normally, it's automatically seen at Bootmanager as HighSierra 10.13 after flashing firmware with APFS.ffs inside it. Link to comment Share on other sites More sharing options...
ammoune78 Posted June 12, 2017 Share Posted June 12, 2017 I juste want to notice that who have firmware error that didn't pass, should have to correct data of it's SMBios section on OzmosisDefaults! Until you get's OSInstal.Pkg blablabla is damaged then it's ok, until someone find the trick to pass this message because, when passed it, OS begin's the install process 1 Link to comment Share on other sites More sharing options...
Kynyo Posted June 12, 2017 Share Posted June 12, 2017 Did you succeded? Or do we have to think another way to bypass that firmware verification. Link to comment Share on other sites More sharing options...
modbin Posted June 12, 2017 Share Posted June 12, 2017 You can see the Firmware error in install.log OSInstaller[599]: ROM Features failed to open IORegistryEntry! Which means u don't have IODeviceTree:/rom@0 but something else. 2 Link to comment Share on other sites More sharing options...
ammoune78 Posted June 12, 2017 Share Posted June 12, 2017 You can see the Firmware error in install.log OSInstaller[599]: ROM Features failed to open IORegistryEntry! Which means u don't have IODeviceTree:/rom@0 but something else. I have rom@f0000 But i passed the firmware check error, this occurred one the first reboot, but when i chose to restart, after booting I have OSInstall.pkg damaged, this is my last station i'm still here! i'm still stopped by this OSInstall.pkg! Link to comment Share on other sites More sharing options...
Kynyo Posted June 12, 2017 Share Posted June 12, 2017 After changing SMBIOS BIOS date to 05/01/2017 now i get this: Installer Log 2 06-12-17.txt Link to comment Share on other sites More sharing options...
IronManJFF Posted June 12, 2017 Share Posted June 12, 2017 Got this far ... Good news is that I can select the APFS partition at boot. Any idea what Firmware Features and Mask I need put into Defaults.plist. QUO board SMBIOS iMac 13,2 (BIOS IM131.88Z.010A.B05.1210121459) Link to comment Share on other sites More sharing options...
firefly_can_fly Posted June 12, 2017 Share Posted June 12, 2017 Got this far ... Good news is that I can select the APFS partition at boot. Any idea what Firmware Features and Mask I need put into Defaults.plist. QUO board SMBIOS iMac 13,2 (BIOS IM131.88Z.010A.B05.1210121459) Try this and don't forget to update bios version and bios release date: http://www.insanelymac.com/forum/topic/324194-pre-release-macos-high-sierra/page-9?do=findComment&comment=2436659 Link to comment Share on other sites More sharing options...
bs0d Posted June 12, 2017 Share Posted June 12, 2017 i think another small binary patch is required to force dmi table type0->BiosSegment = 0 currently it uses the same as the system. 2 Link to comment Share on other sites More sharing options...
cecekpawon Posted June 12, 2017 Share Posted June 12, 2017 To suppress verbose output apfs.efi Find: 00554889E54883EC4048 Replace: 00C34889E54883EC4048 6 Link to comment Share on other sites More sharing options...
Kynyo Posted June 12, 2017 Share Posted June 12, 2017 HS working flawlessly in dualboot with Windows 10. Just make two HFS+ partitions by erasing disk using Paragon Hard disk Manager. Then Install HS and tick upgrade APFS, After that boot W10 UEFI and proceed with installation by formatting second HFS partition as NTFS. Install and Enjoy! 1 Link to comment Share on other sites More sharing options...
IronManJFF Posted June 12, 2017 Share Posted June 12, 2017 till no go with <?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>Date</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosDate</key> <string>10/12/2012</string> <key>BiosVersion</key> <string>IM131.88Z.010A.B05.1210121459</string> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>C02LL669DNMP</string> <key>BaseBoardSerial</key> <string>C02LL669DNMP12345</string> <key>FirmwareFeatures</key> <integer>3909612855</integer> <key>FirmwareFeaturesMask</key> <integer>4280287039</integer> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v nvda_drv=1</string> <key>csr-active-config</key> <integer>103</integer> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>DisableNvidiaInjection</key> <true/> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> </dict> </dict> </plist> Jun 12 21:57:59 iMac OSInstaller[580]: ROM Features failed to open IORegistryEntry! Jun 12 21:57:59 iMac OSInstaller[580]: ROM does not support APFS Jun 12 21:57:59 iMac storagekitd[581]: Bless of /System/Library/CoreServices failed with status 2 Jun 12 21:57:59 iMac OSInstaller[580]: OSIInstallElement <OSIVerifyROMElement: 0x7fc0be02c630> errored out:Error Domain=com.apple.osinstall Code=512 "An error occurred while verifying firmware." UserInfo={NSLocalizedDescription=An error occurred while verifying firmware.} Link to comment Share on other sites More sharing options...
griven Posted June 12, 2017 Share Posted June 12, 2017 It seems like OZ does not inject the proper values to overcome this Issue... I played around with it a couple of hours and never overcame the Firmware Check Error. I changed FakeSMC to SMC Version 2.22f16 and also made sure my Boot-Rom-Version matches the last know version but still no luck. Since Clover is able to inject prober Values I guess @bs0d is right since regardless of what you set in the defaults the error persists. @cecekpawon blessing the APF Drive does the trick once blessed OZ picks it up and add a Bootentry Link to comment Share on other sites More sharing options...
ammoune78 Posted June 13, 2017 Share Posted June 13, 2017 After changing SMBIOS BIOS date to 05/01/2017 now i get this: You still have to do this according to the IstallLog you've posted: I juste want to notice that who have firmware error that didn't pass, should have to correct data of it's SMBios section on OzmosisDefaults! Until you get's OSInstal.Pkg blablabla is damaged then it's ok, until someone find the trick to pass this message because, when passed it, OS begin's the install process What king of Mac you're playing! Link to comment Share on other sites More sharing options...
elviejo Posted June 13, 2017 Share Posted June 13, 2017 (edited) till no go with <?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>Date</key> <integer>0</integer> <key>Defaults:4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102</key> <dict> <key>BiosDate</key> <string>10/12/2012</string> <key>BiosVersion</key> <string>IM131.88Z.010A.B05.1210121459</string> <key>ProductId</key> <string>Mac-FC02E91DDD3FA6A4</string> <key>ProductFamily</key> <string>iMac</string> <key>ProductName</key> <string>iMac13,2</string> <key>SystemSerial</key> <string>C02LL669DNMP</string> <key>BaseBoardSerial</key> <string>C02LL669DNMP12345</string> <key>FirmwareFeatures</key> <integer>3909612855</integer> <key>FirmwareFeaturesMask</key> <integer>4280287039</integer> </dict> <key>Defaults:7C436110-AB2A-4BBB-A880-FE41995C9F82</key> <dict> <key>boot-args</key> <string>-v nvda_drv=1</string> <key>csr-active-config</key> <integer>103</integer> </dict> <key>Defaults:1F8E0C02-58A9-4E34-AE22-2B63745FA101</key> <dict> <key>DisableNvidiaInjection</key> <true/> <key>BootEntryTemplate</key> <string>$label</string> <key>DarwinDiskTemplate</key> <string>$label $platform.$major.$minor</string> <key>DarwinRecoveryDiskTemplate</key> <string>$label $platform.$major.$minor</string> </dict> </dict> </plist> Jun 12 21:57:59 iMac OSInstaller[580]: ROM Features failed to open IORegistryEntry! Jun 12 21:57:59 iMac OSInstaller[580]: ROM does not support APFS Jun 12 21:57:59 iMac storagekitd[581]: Bless of /System/Library/CoreServices failed with status 2 Jun 12 21:57:59 iMac OSInstaller[580]: OSIInstallElement <OSIVerifyROMElement: 0x7fc0be02c630> errored out:Error Domain=com.apple.osinstall Code=512 "An error occurred while verifying firmware." UserInfo={NSLocalizedDescription=An error occurred while verifying firmware.} Use it like this <key>FirmwareFeatures</key> <string>0xe907f537</string> <key>FirmwareFeaturesMask</key> <string>0xff1fff3f</string> not as integer. Good luck Edited June 13, 2017 by elviejo 2 Link to comment Share on other sites More sharing options...
ammoune78 Posted June 13, 2017 Share Posted June 13, 2017 Use it like this <key>FirmwareFeatures</key> <string>0xe907f537</string> <key>FirmwareFeaturesMask</key> <string>0xff1fff3f</string> not as integer. Good luck did you passed the OSInstall.pkg error with this FF & FFM? Should it work with iMac15,1? Ozmosis read it as strings? Link to comment Share on other sites More sharing options...
D1ves Posted June 13, 2017 Share Posted June 13, 2017 did you passed the OSInstall.pkg error with this FF & FFM? Should it work with iMac15,1? Ozmosis read it as strings? no bro,Ozmosis read it as strings/data/number,i test them all But it is of no damn use. 1 Link to comment Share on other sites More sharing options...
TypeThree Posted June 13, 2017 Share Posted June 13, 2017 I can't tell if it makes that big of a difference but FirmwareFeatures /-mask, Revision and so on should be integer and a hex value... You can see it if you extract the OzmosisDefaults.plist from untouched but Ozm modified UEFIs after new Ozm releases in the past. It's also stated here: http://www.insanelymac.com/forum/topic/291655-ozmosis/page-159?do=findComment&comment=2192157and here: http://www.insanelymac.com/forum/topic/291655-ozmosis/page-95?do=findComment&comment=2062449 Link to comment Share on other sites More sharing options...
D1ves Posted June 13, 2017 Share Posted June 13, 2017 I can't tell if it makes that big of a difference but FirmwareFeatures /-mask, Revision and so on should be integer and a hex value... You can see it if you extract the OzmosisDefaults.plist from untouched but Ozm modified UEFIs after new Ozm releases in the past. It's also stated here: http://www.insanelymac.com/forum/topic/291655-ozmosis/page-159?do=findComment&comment=2192157and here: http://www.insanelymac.com/forum/topic/291655-ozmosis/page-95?do=findComment&comment=2062449 sorry bro,i do some tests,no matter what class you select,the value in nvram is same As long as your value is correct,like 'CpuType',i use '0501' with class 'data',it work well too 1 Link to comment Share on other sites More sharing options...
IronManJFF Posted June 13, 2017 Share Posted June 13, 2017 Use it like this <key>FirmwareFeatures</key> <string>0xe907f537</string> <key>FirmwareFeaturesMask</key> <string>0xff1fff3f</string> not as integer. Good luck That did not work at all .. the variables were rejected ... Can you provide me with a nvram dump from DarwinDumper Link to comment Share on other sites More sharing options...
D1ves Posted June 13, 2017 Share Posted June 13, 2017 That did not work at all .. the variables were rejected ... Can you provide me with a nvram dump from DarwinDumper on the real mac 1 Link to comment Share on other sites More sharing options...
elviejo Posted June 13, 2017 Share Posted June 13, 2017 To be clear I have made the installation with createinstallmedia on a usb stick and clover with the givet parameters, when I try to make the installation with oz it fails ( I think we need to modify the OzmosisDefaults to incorporate the parameters, I'm going to try that approach tomorrow ), after installed you can boot directly with oz modified to incorporate the two files provided by cecekpawon Link to comment Share on other sites More sharing options...
Kynyo Posted June 13, 2017 Share Posted June 13, 2017 A interesting approach of Ozmosis install i saw it here 4 Link to comment Share on other sites More sharing options...
Aigors Posted June 13, 2017 Share Posted June 13, 2017 A interesting approach of Ozmosis install i saw it here I have some trouble with russian language sometimes also with English Link to comment Share on other sites More sharing options...
Recommended Posts