Gradou Posted October 20, 2021 Share Posted October 20, 2021 On 10/19/2021 at 6:42 AM, SavageAUS said: 19 hours ago, SavageAUS said: MacBookPro16,4 and iMacPro1,1. Both updated now just had to use OC by booting from USB to get the update to show then just let Clover do the rest. Sent from my iPhone using Tapatalk Sent from my iPhone using Tapatalk With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me : 1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key : <key>RtVariables</key> <dict> <key>HWTarget</key> <string>J137AP</string> to see the update 2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway). It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update. I hope Slice will find it easier Link to comment Share on other sites More sharing options...
Slice Posted October 20, 2021 Share Posted October 20, 2021 I have the update just after removing HWTarget. And no back! Link to comment Share on other sites More sharing options...
Gradou Posted October 20, 2021 Share Posted October 20, 2021 25 minutes ago, Slice said: I have the update just after removing HWTarget. And no back! "And no back !" I don't understand !!!?? Link to comment Share on other sites More sharing options...
kushwavez Posted October 20, 2021 Share Posted October 20, 2021 I still don't understand why is it working for me with the old Clover v5138 without any modifications. Maybe the older SMBIOS? I'm using MBP11,4 Link to comment Share on other sites More sharing options...
Jief_Machak Posted October 20, 2021 Share Posted October 20, 2021 7 hours ago, chris1111 said: Before the commit After latest commit https://github.com/CloverHackyColor/CloverBootloader/commit/710b2dcee554de0a06627b0797a16cf8adb669ce Clover config Validator ➤ Validate nothing Not test latest today commit https://github.com/CloverHackyColor/CloverBootloader/commit/be9b4c2d7fef57e75ceb8f12bab41202348f8ad2 if that fix 6 hours ago, Matgen84 said: CCPV don't work also with commit be9b4c2d7 😪 Wait and see. ccpv worked. It was just that the message "Your plist looks so wonderful" wasn't displayed. Fixed. 3 1 Link to comment Share on other sites More sharing options...
chris1111 Posted October 20, 2021 Share Posted October 20, 2021 (edited) 2 hours ago, Jief_Machak said: ccpv worked. It was just that the message "Your plist looks so wonderful" wasn't displayed. Fixed. Your fixed not fixed Validator validate nothing from config.plist This is used to validate, then how can you say that it works if you do not see the errors or the warnings or simply display that it is good? Please explain to me because I don't understand d Edited October 20, 2021 by chris1111 Link to comment Share on other sites More sharing options...
LAbyOne Posted October 20, 2021 Share Posted October 20, 2021 @chris1111 maybe you'r plist is fine the way it is? becose tested with old version here and got this So just build the latest and got this so the tool seems working Then if Not working for you means No flattered plist that's another thing. Do not forget the old saying -> no news good news 4 Link to comment Share on other sites More sharing options...
chris1111 Posted October 20, 2021 Share Posted October 20, 2021 1 hour ago, LAbyOne said: @chris1111 maybe you'r plist is fine the way it is? Do not forget the old saying -> no news good news Yes thanks thats make sens 1 Link to comment Share on other sites More sharing options...
LAbyOne Posted October 21, 2021 Share Posted October 21, 2021 @chris1111 Just out of curiosity I gave a quick look at the code, and the message is there, so no way it wouldn't appear normally when the plist is correct you should see it infact doing a test with config-sample.plist here's what i get so i was wondering if something is happening with your plist... can you try also with clover's sample.plist and see what gives? if that gives you the same and the one you have installed still gives none there's probably something that prevent it. just assuming... 1 Link to comment Share on other sites More sharing options...
LockDown Posted October 21, 2021 Share Posted October 21, 2021 (edited) @Slice boot7 is gone? BTW, legacy needs openruntime in BIOS folder, else it wont boot to desktop. Edited October 21, 2021 by LockDown Link to comment Share on other sites More sharing options...
chris1111 Posted October 21, 2021 Share Posted October 21, 2021 (edited) 18 minutes ago, LAbyOne said: @chris1111 Just out of curiosity I gave a quick look at the code, and the message is there, so no way it wouldn't appear normally when the plist is correct you should see it infact doing a test with config-sample.plist here's what i get so i was wondering if something is happening with your plist... can you try also with clover's sample.plist and see what gives? if that gives you the same and the one you have installed still gives none there's probably something that prevent it. just assuming... I test the config simple.plist it say plist wonderfull but explain my why before the commit the validator validate my plist and the sample plist both wonderfull then now it say nothing maybe somthing new mandatary on the plist file for validate? I will check the diferance of the file Edited October 21, 2021 by chris1111 1 Link to comment Share on other sites More sharing options...
rramon Posted October 21, 2021 Share Posted October 21, 2021 (edited) 15 hours ago, Gradou said: With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me : 1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key : <key>RtVariables</key> <dict> <key>HWTarget</key> <string>J137AP</string> to see the update 2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway). It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update. I hope Slice will find it easier @Gradou @Slice Does this mean that we have to remove FirmwareFeatures and FirmwareFeaturesMask alltogether from our config.plist? I am confused because prior it was said to add Extended values and leave the „old“ values in place. What‘s the correct way? 13 hours ago, Slice said: I have the update just after removing HWTarget. And no back! What do you mean exactly? Thanks both for clarifying Edited October 21, 2021 by rramon Link to comment Share on other sites More sharing options...
Gradou Posted October 21, 2021 Share Posted October 21, 2021 15 hours ago, Gradou said: With Clover 5141 and SMBIOS iMacPro1,1 for Update 12.0.1 : 2 sequences for me : 1) Without RestrictEvents, boot Clover with config.plist containing (in BIOS section) ExtendedFirmwareFeatures 0x8FD8FF53E and ExtendedFirmwareFeaturesMask 0x8FF9FFF3F (without "old" FirmwareFeatures & FirmwareFeaturesMask) and this key : <key>RtVariables</key> <dict> <key>HWTarget</key> <string>J137AP</string> to see the update 2) While the update is downloading, put RestrictEvents in Kext folder, and disable the HWTarget Key, otherwise the update is not done (in my situation anyway). It is not very simple !!😄 But this is the only way, apart from using a non-T2 SMBIOS, that I have found to achieve this update. I hope Slice will find it easier Modifications : 1) With (and not without) RestrictEvents and its bootarg: -revsbvmm 2) Remove only the HWTarget Key, we can leave RestrictEvents and its bootarg: -revsbvmm Link to comment Share on other sites More sharing options...
rramon Posted October 21, 2021 Share Posted October 21, 2021 @Gradou This is the first time I read about a bootarg that needs to be set if one is using RestrictEvents.kext Anyway, I am talking about the settings when not using the kext. And in the quoted post you stated that one has to boot without the „old“ values for FirmwareFeatures and FirmwareFeaturesMask. This is the first time I read this because - as I said - it was said to add the new values and not to remove the old ones. Link to comment Share on other sites More sharing options...
SavageAUS Posted October 21, 2021 Share Posted October 21, 2021 Clarification is definitely needed. Do we need RestrictEvents kext?If so does it need a bootarg?Do we need the ExtendedFirmwareFeatures and it’s mask?Do we also need FirmwareFeatures and it’s mask or just ExtendedFirmwareFeatures and it’s mask?All these broken poorly informed posts are getting beyond the joke. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
Gradou Posted October 21, 2021 Share Posted October 21, 2021 41 minutes ago, SavageAUS said: Clarification is definitely needed. Do we need RestrictEvents kext? If so does it need a bootarg?Yes Do we need the ExtendedFirmwareFeatures and it’s mask?Yes Do we also need FirmwareFeatures and it’s mask or just ExtendedFirmwareFeatures and it’s mask?Just ExtendedFirmwareFeatures and it’s mask You need also HWTarget Key to obtain the update, but remove it to install All these broken poorly informed posts are getting beyond the joke. I don't untderstand, are you angry ? if Yes, why ? you could be kind anyway, right ? Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
chris1111 Posted October 21, 2021 Share Posted October 21, 2021 (edited) 3 hours ago, MifJpnAlphaPlus said: Hello. me too. Please use it for testing,if you can. config.plist.zip 6.05 kB · 5 downloads Thank you. The plist not works Spoiler Edited October 21, 2021 by chris1111 Not works Link to comment Share on other sites More sharing options...
SavageAUS Posted October 21, 2021 Share Posted October 21, 2021 No not angry nor do I need to explain my post. Just simply stating the facts. Sent from my iPhone using Tapatalk 2 Link to comment Share on other sites More sharing options...
chris1111 Posted October 21, 2021 Share Posted October 21, 2021 4 minutes ago, MifJpnAlphaPlus said: Hello. Sorry for the lack of explanation. If I comment out the Efiversion in the config.plist or add one, ccpv says "Good!” I wonder why. Thanks. Tell im to @Jief_Machak I dont know 1 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 21, 2021 Share Posted October 21, 2021 Hi @Jief_Machak I try commit 23e4b83 : ccpv display nothing if my IvyBridge config.plist and my Z390 config.plist are good 😪 Maybe I misunderstood the commit. 1 Link to comment Share on other sites More sharing options...
LAbyOne Posted October 21, 2021 Share Posted October 21, 2021 (edited) @Matgen84 all those plist issues are apparently caused by the new default "Efiversion" string. as @MifJpnAlphaPlus reported, commenting it out, gives the expected statement, while rolling back to the older version gives obviously the error. So just wait until @Jief_Machak find out what's causing this Edited October 21, 2021 by LAbyOne 2 Link to comment Share on other sites More sharing options...
Slice Posted October 21, 2021 Share Posted October 21, 2021 9 hours ago, rramon said: @Gradou @Slice Does this mean that we have to remove FirmwareFeatures and FirmwareFeaturesMask alltogether from our config.plist? I am confused because prior it was said to add Extended values and leave the „old“ values in place. What‘s the correct way? What do you mean exactly? Thanks both for clarifying In the new systems like Monterey bootefi asked about ExtendedFirmwareFeatures and if not found then FirmwareFeatures. So we may keep only extended. But I am not sure about old systems on old hardware. So my recommendation is to keep both features. There is no conflicts. Next question is HWTarget. I implemented this feature but I don't know its influence on the system. I am watching if someone will use this feature and found some advantage. Still no. My experience that with HWTarget I see no SoftwareUpdate while without it I got the update. So I removed it from my config.plist forever and ever. (...no back...) 1 2 Link to comment Share on other sites More sharing options...
Matgen84 Posted October 21, 2021 Share Posted October 21, 2021 20 minutes ago, Slice said: Next question is HWTarget. I implemented this feature but I don't know its influence on the system. I am watching if someone will use this feature and found some advantage. Still no. My experience that with HWTarget I see no SoftwareUpdate while without it I got the update. So I removed it from my config.plist forever and ever. (...no back...) Thanks @Slice HWTarget might be useful for those using SMBIOS T2 chips like Imac20 for example. Link to comment Share on other sites More sharing options...
SavageAUS Posted October 21, 2021 Share Posted October 21, 2021 If I knew what value to set for hw.target it might be useful too. MacBookPro16,4 and iMacPro1,1. Sent from my iPhone using Tapatalk Link to comment Share on other sites More sharing options...
PG7 Posted October 21, 2021 Share Posted October 21, 2021 On 10/20/2021 at 10:32 PM, chris1111 said: Your fixed not fixed Validator validate nothing from config.plist This is used to validate, then how can you say that it works if you do not see the errors or the warnings or simply display that it is good? Please explain to me because I don't understand d Chris, here everything is working normally I use the PKG and the Clover Configurator of the Github of this same compilation look here before and after and everything is normal 1 Spoiler 2 Spoiler 1 Link to comment Share on other sites More sharing options...
Recommended Posts