CloverBootloader: [SOLVED] r5131 breaks CFGLock.efi (by Brumbaer) if run via 'Tools' entry - fine with r5130

after replacing 5131 EFI/BOOT/BOOTX64.efi with the previous 5130 BOOTX64.efi, functionality is back to what it’s supposed to be: Screenshot

my sample Clover EFI with CFGLock.efi.zip

Asus VivoBook S15 S510UA BQ514T, BIOS x510UAR 310. Let me know if you need any logs.

Link to topic @ insanelymac: CFGLock - unlock (MSR 0xE2) by Brummbär

About this issue

Original URL
State: closed
Created 3 years ago
Comments: 18 (4 by maintainers)

Most upvoted comments

I tried with 5130 and it said "Can’t find any Variable with cfg in name. As you said, let’s forget about that. If an other tool doesn’t work, let’s open a new issue.

jief666 on Mar 28, 2021

@SergeySlice I hope this point to the right sources, please check: Active pull-request | Original source under review.

cecekpawon on Mar 20, 2021

@mackonsti

Hi @LeeBinder you are launching this via an interactive UEFI Shell correct?

No - it’s not supposed to be necessary to do so, esp. with Brummbär’s original CFGlock.efi because it does not even use (let alone require) any params to be added interactively. It’s like: the bug is that the car does not drive forward anymore, so let’s drive it backwards via reverse gear, so at least it runs … that’s not how to solve an issue 😉

I have downloaded the latest CFG Unlock tool from https://github.com/utopia-team/opencore-debug/releases […] Brumbaer’s (excellent) work was taken over by this team, it seems

yes, OC debugs’s “utopia team” took over Brummbär’s CFGlock.efi code, re-labeled it ControlMsrE2.efi and made it interactive, requiring one of three arguments to be passed over. Unfortunately not even that is working in Clover, see Issue #376 😦

Both tools, ControlMsrE2.efi and legacy CFGLock.efi, work just fine if invoked via GUI of current OC, both debug and release editions, so I’m 100% confident team Clover will manage to at least get one of the MSR E2 unlock tools working (again) 🥇

LeeBinder on Mar 14, 2021