Search the Community: Showing results for tags '0x1'.
Found 1 result
Egonaut posted a topic in Tutorials (The Genius Bar)BEFORE TRYING THIS, DO THE OBVIOUS SOLUTION! REPLACE YOUR OPTIOFIX EFI FILE WITH VERSION 2, OR WITH VERSION 1. ONLY PROCEED IF DOING THIS DOES NOT WORK. Alright, so my first attempt at helping people that isn’t in a private discord. Hope this goes well. No one has posted this as a direct solution to someone asking for help with this error, so I thought I’d be the one to share it. I encountered this problem when I rebooted after making some minor changes and discovered I couldn’t boot back into the disk. All over the web, people keep suggesting clover-side tweaks and replacing kexts, and while they may solve the problem for some, absolutely nothing was working for me (and a few others), even when booting with no kernel cache at all. No boot flags worked, no .efi files would solve it. Holding spacebar in clover, no change. So, the solution ended up being system side, and not clover related. You needed to delete your prelinked kernel from the HDD and rebuild it. To do this, you just have to be able to get to your recovery drive or use an install USB that’ll give you access to the disk. Clover got me into my recovery drive just fine, another hint that it wasn’t related to clover - but regardless, whatever works for you. After you’re in a terminal, type the following commands. Df -h This will list all of your volumes, make sure you’re targeting your installation drive. If your volume has a space in the name, such as "Mac OS HS", you'll need to format it as such: "Mac\ OS\ HS" - This is simply how the command line associates spaces. touch /Volumes/[NAME HERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE] In my case, I replaced [NAME HERE] with my installation drive - "macOS\ 10.13". Chances are, this command will give you the error "Child process [directory] has exited due to signal 10" The line immediately after that will give you another bit of extremely important information that you need to take note of. "Error 107 rebuilding /System/Library/PrelinkedKernels/prelinkedkernel" That directory is what we're going to be targeting to fix our system. So, time to nuke it. rm -rf [location to /prelinkedkernel/prelinkedkernel] MAKE SURE YOU DOUBLE CHECK IT IS EXACTLY WHAT WAS OUTPUT WHEN YOU TRIED THE COMMAND ABOVE. IMPORTANT: YOU MAY RECEIVE A READ ONLY ERROR! DO NOT PANIC. I've done this on multiple machines and it really is hit or miss whether or not this will appear. Regardless, the solution is simple. The following code tag only applies to if you encounter this issue. Fsck mount -uw / RE-ENTER THE FOLLOWING COMMAND! You need a more specific location now. rm -rf /Volumes/[NAME]/System/Library/PrelinkedKernels/prelinkedkernel touch /Volumes/[NAME]/System/Library/Extensions && kextcache -u /Volumes/[Name] Now you should be receiving "/Volumes/[NAME] locked; waiting for lock." This is a good thing. Wait a few seconds, you'll receive "Lock acquired; proceeding." After that, you'll be back at -bash-3.2#, and it will appear as if nothing happened. Again, this is expected. For people who didn't have to use the Fsck command, simply type the following and receive the usual "Waiting for lock; Lock received" response. touch /Volumes/[NAMEHERE]/System/Library/Extensions && kextcache -u /Volumes/[NAME HERE] Now, use your up arrow on the keyboard to re-enter this command. If nothing happens, you're golden. If it detects kexts with invalid signatures, that's still okay - but for future reference, don't go the ##### approach/philosophy of installing kexts to your system drive. Take this as a warning. Go ahead and reboot, and start your installation just like normal. You'll now get past the 0x1 error. Congratulations! If you get hung up anywhere, go back to clover and add “-f” to the boot flags, then boot again. You should make it back to your desktop with no damage whatsoever. Like nothing ever happened! Now, as for what causes this, I honestly have no idea. All I know is when you have a working system, make some kind of modication/tweak/installation that HS doesn't agree with, you can possibly get this error on some systems. It's rare, but exists, and unfortunately this is the only way I've been able to get past it. It's not too much work, so don't be too intimidated. You'll have your system back in no time. If you'd like some personalized 1-on-1 support, read my signature and contact me that way. I'm more than happy to help, or at the very least take some time out of my day to analyze your issue and give my thoughts. Thanks for reading my first guide, I'm hoping to publish some more fixes to make High Sierra as painless as possible for every user.