Jump to content
giovanealex

Deleted kexts, OSX stuck on boot, anything else to do on Recovery Mode Terminal?

2 posts in this topic

Recommended Posts

Hi guys.

Sometimes I am a complete noob, so I deleted two kexts from S/L/E and now my Asus Q200E laptop with OS X El Capitan boot hangs on kernel panic. I still can enter go through Clover to reach Recovery Mode and use Terminal, so I've put the two kexts on a USB pendrive and after some struggle I've managed to succefully copy them using Terminal, but the boot is still stuck on kernel panic. As I remember, these are the commands I've typed:

mount -rw

cp -a /Volumes/usb-stick/name.kext /Volumes/my-osx-drive/System/Library/Extensions

Is there anything else I should do? Is anything wrong? Should I type some command else? For instance, should I type something to fix permissions and rebuild cache?

Thanks a lot!

Share this post


Link to post
Share on other sites
Advertisement

Hi,

 

When in the terminal, check if the kexts are copied. 

ls /Volumes/my-osx-drive/System/Library/Extensions/name-of-kext.kext

If it does not give a notice that the file or folder can not be found, it should be present. 

2018-03-20-135247_634x113_scrot.png.6e51a5b584173721cdfefcfc45315df1.png

(Second line reads in Dutch, "Can not get access to '.....' File or folder does not exist.)

If however you get a notice, try to copy the files again, this time with verbose output:

cp -a -v /Volumes/usb-stick/name.kext /Volumes/my-osx-drive/System/Library/Extensions

This way you can trace what goes wrong. 

 

After all is copied, repair and rebuild.

rm -f /Volumes/my-osx-drive/System/Library/PrelinkedKernels/prelinkedkernel
touch /Volumes/my-osx-drive/System/Library/Extensions
kextcache -u /Volumes/my-osx-drive

 

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 stuckinstandby
      Hello
       
      My wife's early 2009 Snow Leopard iMac has started failing to boot properly and I'm looking for some troubleshooting tips.
       
      Booting from cold, it gets past the logon screen and starts loading the desktop. It's quite slow at this point, but does load all the (hundreds of!) icons on the desktop. It also tries to re-open Firefox which had a lot of tabs open. Initially it would load a Firefox window but not complete loading the internals. On one boot I think I managed to close Firefox and now it still tries to load but just displays "Firefox" in the title bar with no windows.
       
      I can initially access a few menus, spotlight, Finder, the dock, but any further action results in a beach ball for these, and they can't be accessed again. I was able to navigate Finder to try to launch Terminal but just it just gave me the beach ball.
       
      I've left it like this for about half an hour but it doesn't get any further and I have to force shutdown (long press of power button).
       
      I tried booting to safe mode (holding down S on startup) but the end result was the same.
       
      I've been able to boot to a live ubuntu USB disk and can access files on the hard disk, so I've started a backup. We have a time machine backup but it's not that recent.
       
      I'm hoping it's just a corrupt file, but suspect it's the hard disk starting to fail.
       
      What's the best way to troubleshoot this?
       
      Thanks
    • 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
    • By johnny28
      Ho installato da tempo High Sierra su un disco SDD separato, mentre su un'altro SSD c'è Windows 10 e su di un al'tro disco Linux-Ubuntu.
      Purtroppo non so come e perché, ma sicuramente per qualcosa che ho fatto, ma che non ricordo, all'avvio del PC, quando premo il tasto F12 per selezionare il sistema operativo da avviare, mi compare ancora OSX, ma Clover putroppo non si avvia (si vede il messaggio Faild to open \EFI\BOOT\grubx64.efi - Not Found  ecc... start_image() returned Not Found).
       
      E' possibile riavviare High-Sierra già installato (partizione APFS), in un qualche modo?
    • By FernandoCoverdale
      Buenas!
      recuerdo que cuando empece a instalar el clover para hacer mi hackintosh el boot de clover tenia una cuenta atrás en la que pasado “no se si eran 5 o 6 segundos”se iniciaba la opcion de arranque de high sierra del disco duro que es la que se marca por defecto, seguramente habré instalado un theme que me lo deja fijo y no recuerdo como volver activarlo.
      gracias de antemano!!!
      adjunto foto

×