Kext Editor

0 views
Skip to first unread message

Griselda Humbarger

unread,
Aug 4, 2024, 3:26:40 PM8/4/24
to circdumbstarur
KextUtility is a program that repairs all kexts permissions very fast.

Kext Utility provides the next operations:

- Install multiple kext files simultaneously;

- Fast repair all kexts permissions for system and Extra folders;

- Pack kext files to mkext cache file.

- UnPack mkext cache files.


So I did this to edit my ATIRadeon9700.kext to add my device I.D. to the list, but now when I try to boot it freezes on the gray screen with the apple in the middle. I have a feeling it has something to do with the video card....Radeon X800GTO PCIe. Is there anyway to reverse what I have done from the terminal on the DVD setup screen?


Mid-2010 MacBook Pros have an issue related to the GPU that causes frequent GPU panic crashes. Someone on the Mac Rumors forums posted a solution which involved editing a plist inside of a kext file. This is their solution.


Restart you computer. Navigate to the kext file, right click Show Package Content. Now go to Contents then you can find the Info.plist file. You might needs to change permission of the file before you can edit it. After you're done, boot into recovery again. Open Terminal and type:


So, found an Akitio thunder 3 as I cant wait for the Node Lite, went to run the enabler script for the older tb chip, first problem, tells me I need t one a root user, quick google and I have a root user and good to go, but then I run into this...


You need to disable SIP first. Boot into Recovery mode ( + R). Click the Utilities top menu and select Terminal. Type csrutil disable. Reboot and you should be able to run TB3-enabler.


Thought it it might be because I had a screen connected but still nothing with everything unplugged. Although when I force apply is says backup already exist and when I follow the file path I have two files, one that I assume is patched and a .original?


Thanks for the replies guys... glad the terminal gubbins makes sense to someone! I have reinstalled my entire OS and the same problem exists... would it be anything to do with being on a 2017 MacBook? I have a backup of the original kext, will look into the Hex editor but if you say its not very reliable I may not bother and just see how it works in Windows (Thunder 3 is in the post as I couldn't wait for the Node Lite to be released).


Thanks for replying buddy, that sounds promising but a little over my head (to be honest this whole Hex find/replace thing is new to me). Would you be able to post again once you've fixed permissions and let me know if boot time is sorted because it sounds like although everything is working something is a little off... if you've managed to get TB82 chips working in HS that might be big news?


I'm using the laptop at work today and ports are working fine so hopefully the script hasn't been damaged in a way that effects anything although I feel shut down takes longer than it used to... a pal has the same laptop so I could grab his vanilla kext if need be.


I feel like I'm missing something obvious... Every article I've seen online tells me to put the kext in that directory and run kextload.. But how the heck do I get write permissions to that directory??


Some cards can be made to work in OS X with custom ROM, however OS X extensions does not support the card's hardwired device ID, so it would result in a Kernel Panic at boot. If the card is close to another officially supported card in OS X or use the same GPU, there's an easy hack which will allow it to operate in OS X.


NVIDIA Quadro 4 (nv25) series, the card is very close to GeForce 4 Ti series, using same GPU and PCB layout. Some even have dual DVI outputs.

Custom GeForce 4 Ti ROM will make the card work as a Mac Card, but a Kernel Panic will happen every time you try to boot with original NVIDIA extensions.


o Know the hardware Device ID of your card

o Have your card flashed and working with a Mac ROM, you can test your card in OS 9 (currently available ROM for Quadro 4 700 XGL)

o have XCODE tools installed (available on original OS X install CD or DVD), you only need Property List Editor for this hack.


1. Go to your root disk (OS X installation) and go to folder /System/Library/Extensions

2. Back up the extensions you're going to modifiy (here NVDAResman.kext and NVDANV20Hal.kext). Keep one copy of each in a safe place, and one copy of each in your desktop. Last 2 copies are going to be edited.

3. Right-Click on the first extension you copied on your desktop and use "show package content" option. The extension will open as a classic folder.


5. Save the edited Info.plist and proceed the same way with the second extension.

6. Copy the edited extensions packages back to your Extensions folder ( /System/Library/Extensions ), OS X will ask you the administrator password.

7. Use Disk Utility or Terminal command line to repair OS X permissions and shut your Mac down.

8. Install you card, boot and enjoy !


Install and manage kext files and repair various permissions by running simultaneous processes in the suite compatible with OS X Mavericks, Yosemite, El Capitan and MacOS Sierra. Loadable kernel modules are available for incorporating additional components.


You can download Kext Utility 2.6.6 for Mac from our software library for free. Our built-in antivirus checked this Mac download and rated it as 100% safe. Commonly, this application's installer has the following filenames: kext_utility.app.v2.6.1.zip and kext_utility.app.v2.5.1.zip etc.


The application is included in System Tools. The current setup file available for download requires 281 KB of hard disk space. The latest version of the program can be downloaded for Mac OS X 10.5.0 or later. This app's bundle is identified as ru.cVad.KextUtility. This free software for Mac OS X was originally developed by cVad. The following versions: 2.6 and 2.5 are the most frequently downloaded ones by the program users.


Yesterday my M1 Macbook Air running macOS Monterey 12.1 popped up a dialog window titled System Extension Updated, with a message that said something like "A program has updated system extension(s). To finish the update, you must approve it in the Security & Privacy System Preferences", and two buttons, OK and Open Security Preferences. I clicked Open Security Preferences (without first taking a screenshot of the dialog window which then disappeared, so I can't be sure of the message exactly) thinking that System Preferences would show which application/extension has been updated. But all that System Preferences > Security & Privacy > General says is that "Your current security settings prevent the installation of system extensions" and a button titled Enable system extensions...


I don't want to enable system extensions without first knowing which system extension and which app this all has to do with. I can tell that none of the installed apps or extensions have been updated recently by looking at the Last Modified dates in System Information > Applications and System Information > Extensions respectively. Also, System Information > Legacy Software says "No information found."


One of your apps is trying to install an updated kernel extension (which macOS incorrectly labelled as a system extension). This is a special piece of software that integrates directly with the macOS kernel (XNU), the very core of macOS.


The kernel is the most privileged software in any operating system; it acts as the go-between for system software and hardware resources. By implication, any kernel extensions installed also receive these extreme privileges, as they run in kernel-space. Because of this, you should only install kernel extensions that you absolutely need, and only those that require these extreme privileges.


If any kexts appear in there, right-click (or hold down Control as you click on) one of them, then select Show Package Contents. Check the Info.plist file inside for info about the developer of the kext.


Unfortunately, I'm not sure of a way to query which kexts are pending approval. You could check in /Library/Extensions or /Library/Apple/System/Library/Extensions and check if any new (non-Apple) kexts are there.


If you want to see in System Preferences which developer is trying to load a kext, you can temporarily permit third-party kexts by starting up in macOS Recovery and modifying the security settings. Once third-party kexts are permitted, System Preferences (in Security and Privacy) should prompt you to approve the requested kext and restart your Mac. Before you approve the kext, you should be able to see which developer is trying to load it.


To return to Full Security and deny all third-party kexts, complete the above steps again, but choose Full Security instead. Or, run this command in Terminal (doesn't require macOS Recovery): sudo bputil -f


I'll first mention that I did restart my computer before posting here just to see if that would either cause the "Your current security settings prevent the installation of system extensions" message in System Preferences to disappear or the System Extension Updated dialog window to reappear. Neither of those things happened.

3a8082e126
Reply all
Reply to author
Forward
0 new messages