Contribute
Register

<< Solved >> HighSierra won't boot after kextbeast install

Status
Not open for further replies.
Joined
Mar 16, 2018
Messages
66
Motherboard
Gigabyte Z370 AORUS Gaming 5
CPU
i7-8700K
Graphics
RX 580
Mac
  1. MacBook Pro
Mobile Phone
  1. iOS
Dear friends,
I wanted to post this topic about a problem I have and I hope you can help me.
I already posted in this forum about activating my magic mouse 2 with the ASUS BT400 dongle and it didn't work.
Things got complicated and I cant boot my system on my hackintosh anymore. What did I do?
I installed beastkext and copied the kext files from http://RehabMan-BrcmPatchRAM-2015-1016.zip into the folder "Library/Expansions".
Afterwards the system didnt boot anymore. I can boot it in safe mode (not all usb ports and two ssd disk work).
I can boot it without problems from my BOOT USB and everything works fine.
So what happened? Did someone maybe have the same problem and does anyone know any solution to this problem?
I tried to mount an EFI partition from my USB but it did not work. He reports these pictures. : /
I'm also thinking about reinstalling the entire system. I have Backup, but I do not know if Backup with Time Machine works with Hackintosh.
Thanks in advance! Best Regards!
 

Attachments

  • 58858018_2320191331592876_2945350565707644928_n.jpg
    58858018_2320191331592876_2945350565707644928_n.jpg
    268.7 KB · Views: 80
  • 59211526_1021334554921569_964117336434933760_n.jpg
    59211526_1021334554921569_964117336434933760_n.jpg
    702.1 KB · Views: 81
Dear friends,
I wanted to post this topic about a problem I have and I hope you can help me.
I already posted in this forum about activating my magic mouse 2 with the ASUS BT400 dongle and it didn't work.
Things got complicated and I cant boot my system on my hackintosh anymore. What did I do?
I installed beastkext and copied the kext files from http://RehabMan-BrcmPatchRAM-2015-1016.zip into the folder "Library/Expansions".
Afterwards the system didnt boot anymore. I can boot it in safe mode (not all usb ports and two ssd disk work).
I can boot it without problems from my BOOT USB and everything works fine.
So what happened? Did someone maybe have the same problem and does anyone know any solution to this problem?
I tried to mount an EFI partition from my USB but it did not work. He reports these pictures. : /
I'm also thinking about reinstalling the entire system. I have Backup, but I do not know if Backup with Time Machine works with Hackintosh.
Thanks in advance! Best Regards!

Hello again. Thank you for starting a new thread :thumbup:

Okay, I have done some testing for you on my own Z370.

I found that the BrcmBluetoothinjector, BrcmFirmwareData, BrcmPatchRAM and BrcmPatchRAM2 kexts did NOT cause any problems for booting.

So the problem you are having must be something else.

The screen grabs you posted show that there is a problem finding the necessary boot files. If the UniBeast installer boots fine then the main drive SSD/HDD EFI partition or folder might have been corrupted.

1) If you boot with UniBeast to get into your system, run DiskUtil and check your main drive for Errors.

2) If it is okay, make a note of the main drive disk id (disk0s2, disk1s2 etc etc).

3) Run EFI Mounter v3 and you will find two choices from which to mount. Choose the main drive EFI you checked above NOT the Unibeast drive. It will show in the list as "disk0s1, disk1s1" etc etc.

4) Can you see the EFI drive icon on your desktop? Check if there is an EFI folder in it. If so COPY this to somewhere safe. You will then be able to use your previous configuration files to update any new installation you might decide to do. Plus, importantly, it keeps your current Serial numbers intact.

5) Navigate to your Library/Extensions folder and delete all those Brcm*.* kexts.

6) Run Terminal and use the command:

Code:
sudo kextcache -i /

This will rebuild your caches and remove all traces of the Brcm* kexts.

7) Reboot using the UniBeast USB again.

What you do next is up to you. You could try running MultiBeast to re-install Clover on the main drive. If you do this you may lose some other settings from the old configuration but you can easily reinstate those by copying the old config.plist back etc.

If you are unsure about any of the above, then just ask.

:)
 
Last edited:
Hello again :)
I managed to run the system from my hard drive. I managed it by moving the kext files from the old EFI partitions. However, now we see the text with "afsi mounting" Is there a solution for this? For now, everything works fine and the system is up and running smoothly. Of course, the Magic Mouse 2 does not works and it's ok for me.
 

Attachments

  • 8F23CBF5-A822-4AA5-8B58-D11C1B606F15.jpeg
    8F23CBF5-A822-4AA5-8B58-D11C1B606F15.jpeg
    1.7 MB · Views: 80
  • 451D4303-5FED-4E6B-B1E0-423255D0F686.jpeg
    451D4303-5FED-4E6B-B1E0-423255D0F686.jpeg
    2.5 MB · Views: 83
  • 9E297F5B-EE62-4777-AD92-D7F05AC23611.jpeg
    9E297F5B-EE62-4777-AD92-D7F05AC23611.jpeg
    1.7 MB · Views: 91
Hello again :)
I managed to run the system from my hard drive. I managed it by moving the kext files from the old EFI partitions. However, now we see the text with "afsi mounting" Is there a solution for this? For now, everything works fine and the system is up and running smoothly. Of course, the Magic Mouse 2 does not works and it's ok for me.

Good news. Well done :thumbup:

Yes, this text is APFS early logging and occurs during boot. There are a few threads which explain how to disable it, or hide it, if it bothers you. There is also a replacement for the apfs.efi file in the EFI folders and it's called ApfsDriverLoader-64.efi along with AppleImageLoader-64.efi BUT I really, really don't want to suggest you try it unless you feel confident etc.

(If you do want to, here are some links: Here - Here again & Yet another Here . There are others if you search...).
 
Status
Not open for further replies.
Back
Top