Big Sur breaks Voltageshift #44
Comments
|
Yes, this app should require upgrade by implement the DriverKit layer. |
|
That's too nice sicreative. Voltage shift is still used on a lot of Hackintoshes with Sky Kaby and Coffelake CPUs it'd be amazing to have this Kext back in working order with Big Sur. I'm excited!! |
|
its super useful for 5000USD bricks... (i9 2018 MBPs :) ) Thanks! |
It's not supposed to work with Broadwell+ MacBooks. |
Power limit and Boost limit does work!! (No under-voltage) |
|
Oh, I See |
|
It works on Big Sur for me. |
|
It actually resumed working after one of the frequent OS updates during the beta, and continued to work until recently. The "release candidate" of Big Sur appears to cause problems again (for me at least). After fixing the code signature issue described by others in the "killed" thread, and fixing permissions, it now shows "OC_Locked" in my CPU info, which I don't recall seeing before. When attempting to change any voltage parameters, it shows both before and after voltage offset as 0. No changes work. I'd love to hear if anyone else has it working on the release candidate of Big Sur. |
|
It works great for me on the release candidate!
I did get a version from a different GitHub thread, though, so try this version of the kext and executable: The only problem that I have is that the offsets don't stick through sleep, so I have to use a program to run a voltageshift shell script on every wake. |
|
Thank you for your quick reply! I must be missing something. I replaced the kext and exec with the ones you linked, fixed ownership, and rebooted as requested by system security settings. It still gives me this: |
|
Have you updated your Bios recently? If you have, you might have to undo the overclocking lock in order to undervolt. |
|
I'm on a Macbook, so no BIOS. |
|
on Macbooks only power limit and turbo limit works. |
|
**2014 MacBook Pro with Haswell i5-4278U I assure you voltage offsets worked-- verified by VoltageShift itself, as well as power draw/temperature/boost clocks under load. Undervolting too far caused crashes. |
|
There’s a chance that apple disabled undervolting for all macs in an update because of plundervolt, but I could be wrong. |
|
Good point, that's very possible. I don't have the knowledge to work around this. So if anyone manages to get things working on a mac running Big Sur release candidate or later, please chime in. |
|
I used the version Drowningfish223 provided and so far it is working without problems. Didn't need anything additional. I'm on a 2015 MBP with i5-5257U
Unrelated but I also managed to do -130mV CPU cache voltage after seeing Drowningfish223's picture. Thanks! |
|
|
I'm on macbook air 2013, where voltageshift always worked fine. Big sur broke everything, now i'm getting |
OC_Locked mean the SMC locked by Apple and no Overclock available. |
|
Funniest thing: i've tried SMC reset. Now I lost turboboost completely. Looks like apple introduced intentional slowdown (or voltageshift behaves buggy on my os) |
|
Removing the kext restored turbo operation. I will try to rebuild the kext with latest SDK (there were some hints in xcode rc release notes, that kexts need recompilation) |
|
I'm also getting the OC_Locked message. Is there anything that can be done to unlock it? |
|
After updating to Big Sur, undervolting stopped working for me too (even on Catalina). Based on the updated EFI and SMC, Apple seems to have closed the undervolting option on all Macs.
|
that was my biggest fear.. undervolting helped my 22nm i5 macbook air to run on max turbo infinitely long. And battery life was considerably better |
|
SMC lock by big sur firmware upgrade is confirmed. Luckily there is a way to downgrade https://support.apple.com/en-gb/HT201518 will try it out later |
Let me know if you can do something. But the link that you sent me will most likely not work. |
|
I seem to undervolt just fine even after the latest update. |
What is your MacBook and what is the firmware version? I have MacBook Pro 13 late 2013 |
|
I will look at the firmware version in 2-3 hours but its a macbook pro 13 early 2015, with i5-5257U. Also you may want to remove your edit history if you can, its visible. |
|
That’s awesome news. Does anyone know what tricks „Volta“ uses that allows undervolting with current firmware albeit maximum macOS Mojave support? |
seems it's not. Checked on my 2013 MBA (Mojave, latest firmware) |
I’m confused. Is Volta working for you? But voltageshift isn’t? |
@IsmaelHG programmer with which type of connector? Proprietary Apple's one? |
nothing works |
|
What tools do you use to check if it is working? |
That could work for rMBP 2013? |
If you have the Late 2013 model (4th gen intel haswell cpu), yes. |
My Mac (15" late 2013 ME293) was upgraded to Big Sur and then downgraded back to Catalina. After downgrading, the BIOS remains a Big Sur one (no voltage offset). Following your guide, I successfully modded it's BIOS. After writing the modded BIOS, the Mac need to turn on (after few seconds it turns off) twice, then it worked as expected. |
Worked here too on a mid 2014 macbook pro, using the windows apps I found it helped to erase before writing otherwise I was getting writes that didnt match the file. |
I had to patch it again after upgrading to big sur 11.5 |
|
@binh-geomatics @jtb-ship-it did you use ch341a and SOP8? I patched successfully over osx 11.3 but after I tried to do after 11.5 I bricked my rMBP 2013. I did use ubuntu to dump my original eprom rom thought terminal, and after UEFI patch I did try to write using ch341a programmer and I always get "Chip main memory with the contents are in disagreement" error. I get same error when I try to revert to backup rom. I'm using ch341a programmer v1.29 and v1.18 Original dump rom file has 8,388,608 bytes, same size as the one I did get from osx 11.3 |
|
Did you try clearing the rom first? I wasnt able to get a verified write with any program without erasing the rom first. |
|
@jtb-ship-it I didn't know about that. Thanks for your advice. I did a new try and know everything works fine! Im so happy (: |
Hallo, can i use this set https://www.amazon.com/Coomatec-Socket-Adapter-Programmer-Software/dp/B08KG7YM45/ref=pd_sbs_3/133-5296797-1568048?pd_rd_w=2xspB&pf_rd_p=3676f086-9496-4fd7-8490-77cf7f43f846&pf_rd_r=7H19D6JRXX7GR0FXSWAX&pd_rd_r=00eae9ef-acb6-438b-ab63-2ed4a5f086d6&pd_rd_wg=c5aCO&pd_rd_i=B08KG7YM45&psc=1 for flashing correct firmware? Thx. |
The CH341a is compatible with any 2013-2014 mac but the SOP8 clamp is only compatible with 15" MacBook Pro (A1398). |
|
Ok, I have MBP 15" 2014 (A1398), so I ordered set from Amazon. Can you please publish a pictorial guide to the complete procedure? I watched videos on Youtube how to use CH341A, I think I fully understood the principle of the whole operation, but I would like to be sure how to make the adjustment correctly on my MBP. I used to do BIOS adjustments on my Thinkpads. Thank you. |
|
Hi, I managed to successfully unlock firmware 431 on BigSur 11.5.2. Now I can perform CPU undervolting. Thank you very much. |
|
Would be necessary to patch again after latest 11.6 update? |
|
I think it may be possible to patch the firmware without an external programmer. Using dosdude's ROMTool [1], I was able to dump the 432.60.3.0.0 firmware for my Mid-2014 MacBook Pro 15" (MacBookPro11,2) [2]. Guided by @IsmaelHG's instructions [3], I can patch it. ROMTool also supports flashing the firmware ROM, but I haven't yet mustered the courage to do try this (partly due to [2]). Perhaps if there was a way to recover in case anything goes wrong... I was hoping I could unlock undervolting without having to flash the firmware ROM. On (some) machines, this is possible by means of a Modified GRUB Shell [4]. This doesn't seem to be an option on (my) MacBook as I cannot find a Setup section in the firmware (or "CFG Lock" and "OC Lock" strings). [1] http://dosdude1.com/apps/ (don't miss zippasswords.txt) |
ROM flash is mandatory to unlock FIVR control. As for the flashing without an external programmer, you can't either because the ROM region is write protected for security by Apple. There was a bug years ago that unlocked the write protection but it's fixed on newer ROM versions |
After months of "thinking" I finally decided to try bring back undervolt feature for my A1502 MacBook 13 inch late 2013; By mistake I updated Mojave to Big Sur, and the rolled back to Mojave - UEFI was updated and I was not able to downgrade it with Mojave installation. So, as we all figured out above, updating your UEFI will lock needed register (or smith like that), so undervolt would not be possible. |
|
Can anyone undervolt on macbook pro 16 2019? I installed voltageshift but after using sudo offset no voltage change :( |
I have successfully modified firmware for MBP on my Windows PC. I tried to do the patch in Mac OS Catalina and got the error message "UEFIPatch command not found". Can you tell me what I'm doing wrong? And what is the latest version of firmware on which the undervoltage unlock can be performed? I have a 15" rMBP mid 2014. |
That error means it can't find the UEFIPatch executable, make sure the terminal is opened on the same folder as the executable. And the patch is still working with the latest big sur security update (firmware version 432.60.3.0.0) |
|
Hi, Thanks |
|
Could someone please help me with configuring and connecting the CH341A programmer? I made an issue on the UnderVoltPatchMacBook GitHub page: IsmaelHG/UndervoltPatchMacBook#7 EDIT: I was able to get it working simply by making sure the SOP8's pin connector and the clip was on tight. The logic board did not need to have power for it to be read. I also left the CH341A as is. This confirms that the patch has worked to unlock undervaluing again on firmware 478.0.0.0.0. |
|
Has anyone tried this after Big Sur? I am now looking to try OCLP on my late 2013 15" MacBook Pro with Sonoma. Will that update my firmware from my patched Big Sur 478.0.0.0 firmware? Will that require patching it again? |
and others
macOS 11.0 Beta appears to break all functionality. Commands return no result initially. After changing ownership again with:
and trying a command again, we get the following error:
My (extremely limited) understanding is that there is has been a fundamental change in the way extensions are handled in 11.0. Any word on if this change can be worked around?
The text was updated successfully, but these errors were encountered: