Jump to content
janek202

Kext Wizard - Easy to use Kext Installer and more

272 posts in this topic

Recommended Posts

Advertisement
so we can install Lion's kext and rebuild its cache from inside SL? and vice-versa?

Yes. I used "touch" command, so system takes care of rebuilding cache, instead of rebuilding it manually. At least it should work like that.

Share this post


Link to post
Share on other sites
Hi all.

Recently I was working on new utility for kexts. Version 3.0 seems to be finished, so I decided to show this app on international forum.

Hi I like a lot your app can you/ will you provide source, pleaseee?

Share this post


Link to post
Share on other sites

Thanks, it's very nice, better than Kext Utility and Kext Helper b7 combined. May it rest in peace.

Share this post


Link to post
Share on other sites

Great.

But does this new utility handle the rights of kext "correct" if i use kext utitlity works but next OS X Diskutility must repair all of them again.

Share this post


Link to post
Share on other sites
Great.

But does this new utility handle the rights of kext "correct" if i use kext utitlity works but next OS X Diskutility must repair all of them again.

Yes.

Maintenance: First it sets owner (root:wheel) and permissions (755) for the whole System/Library/Extensions. Some system kexts requires other permissions etc. so after that it repairs permissions on whole target disk using: "diskutil repairpermissions".

 

Installation: It sets owner and permissions only for newly installed kexts. Others aren't modified. After that it rebuilds cache.

 

So there's no need to run Disk Utility after using my application.

Share this post


Link to post
Share on other sites

If anyone would like to make a translation to other language (currently English and Polish) please let me know. I will create necessary files.

Share this post


Link to post
Share on other sites

Dzięki! Miło widzieć rodaków wspierających społeczność OSX86 :)

 

Thanks!

Share this post


Link to post
Share on other sites
Hi all.

Recently I was working on new utility for kexts. Version 3.0 seems to be finished, so I decided to show this app on international forum.

 

Features:

1. Maintenance: Repair permissions, and rebuild cache for Extra and System/Library/Extensions.

Both directories: Extra/Extensions and Extra/KextStore are supported.

2. Installation: Install kexts to Extra or S/L/E and create mkext.

3. Unpacker: Check mkext's content kexts and unpack it.

4. Kext Information: Check kext's architectures and dependencies.

5. Loaded: Shows list of currently loaded kexts in system.

Hi Janek,

 

This was long overdue and many thanks for your hard work.

 

I would like to suggest some additional features in the 'Loaded' section:

 

-Would it be possible to emulate the functionality of the 'Extensions' section of System Profiler ?

 

What would be useful is the location of the loaded kexts.

 

These could be displayed in a new window with the ability to save the info to a text file.

 

Kind regards,

Rn

Share this post


Link to post
Share on other sites
-Would it be possible to emulate the functionality of the 'Extensions' section of System Profiler ?

What would be useful is the location of the loaded kexts.

Ok. I will add this in version 3.1. I found a way to search kexts also in /Extra by their bundle-id.

Share this post


Link to post
Share on other sites

Version 3.1 (Probably Beta).

Improved filtering. More info about selected kext.

Please report me any bugs etc.

When everything will be ok I will update first post with new version.

 

Edit: Version 3.1 is now official. Check the first post.

Share this post


Link to post
Share on other sites
Version 3.1 (Probably Beta).

 

Hi Janek,

 

A couple of suggestions for future releases:

 

1- Could you make 'renaming of Extra/Extensions folder to Extra/KextStore Optional. That may be useful for backward compatibility.

 

2- I know it's early days but it would be nice to output some information messages as to what it is doing (a bit like Kext Utility). That way, one would know whether it is running or stuck.

 

Thanks again,

Regards

Rn

Share this post


Link to post
Share on other sites
1- Could you make 'renaming of Extra/Extensions folder to Extra/KextStore Optional. That may be useful for backward compatibility.

Well, I think it's pointless. Extensions will be renamed to KextStore only when "Rebuild mkext" option is selected. Chameleon loads kexts in that order:

1. Extra/Extensions folder

2. Extra/Extensions.mkext

Keeping Extensions folder and mkext is pointless, because kexts will be loaded only from E/E directory. That's why if you want to use mkext (some kexts works only that way) you have change Extensions' name (usually to KextStore).

If you repair permissions, install new kexts etc. this folder won't be renamed.

2- I know it's early days but it would be nice to output some information messages as to what it is doing (a bit like Kext Utility). That way, one would know whether it is running or stuck.

I will think about it, but usually the only function that takes some time is repairing permissions to whole disk (Option repair S/L/E permissions).

 

Edit: No one reported me any bugs so version 3.1 is officially published.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By ITzTravelInTime
      Hi guys, this thread is to show you a new and open source app, created by me, that I called TINU:
       
      The name means: TINU Is Not #####, the U refers to a popular software that is used to create macOS hackintosh installers (that for good reasons is banned on this forum), but the aim of the name is to explain that this app is a totally different thing from that software and works in a totally different way.
       
      This app basically is a graphical interface for the createinstallmedia executable that is inside the macOS and Mac OS X installer apps, it is capable to create a bootable installer completely vanilla like what you do using the command line method, and also this method is recommended by apple itself. In addition to this, this app provvides to you simplicity and flexybility, and lets you to avoid most of the steps needed with every other app.
       
      TINU allows you to create easily a bootable macOS installer without messing around with command line stuff and without using disk utility, all you need to do is use the app and then install clover on the usb drive once TINU has finished or leave it as is if you want to use it on a real Mac.
       
      Features:
        - Simple to use UI that allows you to easily start the bootable macOS installer creation process
        - It can work with every macOS installer app that has the createinstallmedia executable inside of its resources folder (including also beta and newly released installers)
        - You can use any volume you want that can be erased and is at least 7 GB of size (if the volume's drive is not in GUID format, TINU will format it to make it GUID!)
        - Works on Mac OS recovery, so you can create a bootable macOS installer from the macOS installer itself or from the macOS recovery, and you can use TINU to install macOS too.
        - All vanilla, the bootable macOS installers created with this tool are 100% vanilla, just like you created them using the command line "createinstallmedia" method in the terminal
        - Open source, you will know what this program does on your computer and also you can create your own version by downloading and playing with the source code
        - Does not require to do anything of special first, just open the program, and make sure you have a USB drive pulugged in and that you have a macOS installer app in the system.
        - No need to go in disk utility first, TINU can format your drive/partition for you
        - Uses recent and more modern APIs and SDKs and Swift 3 language
        - Transparent graphics style available (use alt + s on the keyboard or View->Use transparent style)
        - Works using the latest versions of macOS and will also support newer Mac installers out of the box without needing for an update
        - Advanced section, to customize your bootable macOS installer
       
        Features that are planned for some future versions:
        - Integrated EFI partition mounter tool (TINU can already mount EFI partitions from version 2.0, but a dedicated section which allows to mount every EFI partition in the system will be added)
        - Install clover and configure clover
        - Install kexts inside the kexts folder of clover
        - Clover drivers customization
        - Use custom dsdt in clover
        - integrated pre-made clover config templates database from a remote and open repository
        - Support for other languages, at least Italian
       
      Rquirements:
       - A computer that runs Mac OS X Yosemite or a more recent version (Mac OS X El Capitan is required to use TINU in a macOS recovery or installer)
       - A drive or a free partition (on a drive which already supports GUID) of at least 7 GB that you want to turn into a macOS/Mac OS X installer
       - A copy of a macOS/Mac OS X installer app (Maveriks or newer versions are supported) in the /Applications folder or in the root of any storage drive in your machine (excepted the drive or volume you want to turn into your macOS install media)
       
      Download:
        - You can download the pre-made and code signed binary from the releases section of the github repo: https://github.com/ITzTravelInTime/TINU/releases
        - Or you can just build your own copy by just downloading the source code and then using Xcode (requires Xcode 8):  https://github.com/ITzTravelInTime/TINU

      Frequently asked questions:
      https://github.com/ITzTravelInTime/TINU/wiki/FAQs

      Useful links:
       Thread (english) on insanelymac.com:
        - http://www.insanelymac.com/forum/topic/326959-tinu-the-macos-installer-creator-app-mac-app/
       
       Thread (italian) on insanelymac.com:
        - https://www.insanelymac.com/forum/topic/333261-tinu-app-per-creare-chiavette-di-installazione-di-macos-thread-in-italiano/
       
       Thread (english-german) on hackintosh-forum.de:
        - https://www.hackintosh-forum.de/index.php/Thread/33630-TINU/
       
       Facebook hackintosh help and beta testing (Italian only):
        - https://www.facebook.com/groups/Italia.hackintosh/?fref=ts
       
      Contact me (project creator):
        - Insanelymac.com profile: http://www.insanelymac.com/forum/user/1390153-itztravelintime/
        - email: piecaruso97@gmail.com

      Note that:
       - This software is under GNU GPL v3 license so any new branch/mod/third party release must be open source and under the same license
       - I (project creator) assume no responsibility for any use of this app and this source code, and also for any kind of hardware and software damage to any computer and any device or peripheral that may come from this app or source code during it's use and outside it's usage
       - I (project creator) do not guarantee support to you, this is only an open source project, not a product released by a company!
       - This project is born only for educational and demonstrative purposes, it's not intended to be used for commercial purposes and it will never be, don't use source code from this project to create apps or software for that aim.
       - This is a no-profit project, born only to let people to create macOS install medias in a more simple way and also to learn how to create this kind of apps.
       
       Credits:
        - Apple for macos and installer apps and scripts
        - People that helped me a lot:
         Francesco Perchiazzi, Nicola Tomarelli, Roberto Sciortino, Raffaele Sonnessa, Ermanno Nicoletti, Tommaso Dimatore, Michele Vitiello Bonaventura, Massimiliano Faralli, Davide Dessì, Giorgio Dall'Aglio, Thomas Tempelmann, Peter Paul Chato.   
        - Special thanks to Italian Hackintosh group!! for help (https://www.facebook.com/groups/Italia.hackintosh/?fref=ts)
        - Pietro Caruso (ITzTravelInTime) for creating, maintaing and developing this project
       
      I leave also some screenshots as well
       
       
       
       
       
       
       
       

    • By PoisonApple666
      I have a bootable clover usb stick and it goes through the first part of the install to a fresh SSD...then on the first reboot Mojave tells me that the installer resources cannot be found....does anyone know what this means
       
      Thanks very much,
      R
       
    • By fusion71au
      This is a brief guide on how to create a vanilla El Capitan (also same process for Sierra) OS X Installer USB with an updated prelinked kernel containing FakeSMC.

      It is tailored for those users who want to understand the “nuts and bolts” of how to create an installer and also to help brush up on their terminal skills (rather than have one made for them with the numerous automated “tools” available or even Apple’s createinstallmedia) :
       
       
      Specifically, it is also a “Proof of Concept” which shows that installation is possible without even having to rely on boot loader kext injection.

      Prerequisites
      Existing Yosemite installation (or Mavericks - see post#4 for steps 7,8) “Install OS X El Capitan.app" downloaded to the Applications folder Pacifist FakeSMC.kext - Slice or Kozlek branch Bootloader - Clover or Chameleon 8GB or larger USB drive (16GB recommended), formatted HFS+ (MBR or GUID) named “Installer”  
      Procedure
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Open OS X terminal and type the following lines, followed by <Enter> after each line.
          The image restore and file copying may take a while to complete, and at the end of the process, the Installer volume is renamed to “OS X Base System"....
       
      sudo -s hdiutil attach /Applications/Install\ OS\ X\ El\ Capitan.app/Contents/SharedSupport/InstallESD.dmg asr restore -source /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg  -target /Volumes/Installer -erase -format HFS+ -noprompt -noverify rm /Volumes/OS\ X\ Base\ System/System/Installation/Packages cp -av /Volumes/OS\ X\ Install\ ESD/Packages /Volumes/OS\ X\ Base\ System/System/Installation cp -av /Volumes/OS\ X\ Install\ ESD/BaseSystem.dmg /Volumes/OS\ X\ Install\ ESD/BaseSystem.chunklist /Volumes/OS\ X\ Base\ System diskutil unmount /Volumes/OS\ X\ Install\ ESD exit 3.  Right click on the “OS X Base System” Volume and click “Get Info”
       

      4.  Click on the lock icon and untick “Ignore ownership on this volume”
       

      5.  Extract/Copy the El Capitan Kernels folder into /System/Library/ of the USB with Pacifist.  NB It is found in the "Essentials.pkg" in /System/Installation/Packages
       

      6.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel —> OG.prelinkedkernel
       

      7.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of the installer USB using Finder.
       

      8.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel…..
       
      sudo -s chmod -R 755 /Volumes/OS\ X\ Base\ System/Library/Extensions chown -R 0:0 /Volumes/OS\ X\ Base\ System/Library/Extensions touch /Volumes/OS\ X\ Base\ System/System/Library/Extensions kextcache -u /Volumes/OS\ X\ Base\ System exit Any errors should be noted but the output below is normal e.g.


      9. Install your Bootloader targeting the OS X Base System volume
       
       
       
       
      10.  Boot your system with the USB without injected kexts into the OS X Installer GUI....
       
       
       
       
       
      Post Install
      The original prelinked kernel in a fresh install of El Capitan will also lack FakeSMC ie it will only be linked to Apple signed kexts.  In order to boot into El Capitan the first time around without boot loader kext injection, the PLK needs to be rebuilt for the El Capitan volume like we did for the installer:
       
      1.  Boot into Yosemite with the kext-dev-mode=1 boot flag
      2.  Delete or Rename the original /System/Library/PrelinkedKernels/prelinkedkernel for the El Capitan volume —> OG.prelinkedkernel
      3.  Copy FakeSMC.kext and other necessary kexts (e.g. VoodooPS2Controller.kext for laptops) into the /Library/Extensions folder of El Capitan using Finder
      4.  Back in terminal, type the following lines, followed by <Enter> after each line to rebuild the prelinkedkernel.  In this example, the El Capitan volume is named "El_Capitan" - change if you have named it something else...
      sudo -s chmod -R 755 /Volumes/El_Capitan/Library/Extensions chown -R 0:0 /Volumes/El_Capitan/Library/Extensions touch /Volumes/El_Capitan/System/Library/Extensions kextcache -u /Volumes/El_Capitan exit 5. Install your Bootloader targeting the El Capitan volume.  This step is only necessary if you are installing El Capitan on a new drive without existing boot loader (not required if installing on a disk with existing boot loader beside Yosemite).
      6. Reboot your system without injected kexts into El Capitan!
       
       
      Other links
      The All-In-One Guide to Vanilla OS X for beginners
       
      Updates for Sierra and High Sierra   Custom Prelinkedkernel Generator Tool I have made a custom prelinkedkernel generator "PLK.tool" for Sierra + El Capitan.  Instructions:   1.  Download and extract the attached BaseSystem_PLK.tool.zip into your ~/Downloads folder.   2.  Copy any extra kexts necessary for booting your hack to ~/Downloads/BaseSystem/ExtraKexts (e.g. FakeSMC, VoodooPS2Controller), making sure SIP is disabled. 3.  Copy BaseSystem.dmg to ~/Downloads/BaseSystem  4.  Open terminal and run the following commands... cd ~/Downloads/BaseSystem chmod +x PLK.tool ./PLK.tool ---> supply your admin password ---> will place your new custom prelinkedkernel on the desktop.       macOS High Sierra bypass Firmware and MBR checks in post#13.
      BaseSystem_PLK.tool_ElCap.zip
      BaseSystem_PLK.tool_Sierra.zip
      BaseSystem_PLK.tool_Mojave.zip (need to run in Mojave to avoid dependency errors)
       
    • By bobso
      hi I have this build:
       
      - AMD Athlon X4 631
      - ASRock A75M-HVS (link)
      - AMD HD 6670
      - 8GB DDR3
      - 250GB HDD
       
      Which version of MacOS can I install?
      Which kernel?
×