Contribute
Register

Issues while trying to install Mac OS Mojave

Status
Not open for further replies.
Right okay, sorry about the last post, I should’ve read the rules before posting.

Again, after trying what you said in your last post, it is still not working, attached is the result and my BIOS settings.

If you want anything else from me, then let me know.
  • Verbose Boot ->Prohibit Entry Error.
    • cause: USB port related
  • Currently used CLOVER not uploaded as suggested in my post #9 for diagnostic clues in EFI/CLOVER/kexts/Other and config.plist_Devices
  • BIOS options in the uploaded screen shots have some problems including Disabled EHCI that can cause the Verbose boot error .[ See all edited images.]
  • For more information about this error, check this post-> #6
 

Attachments

  • Screen Shot 2019-08-02 at 8.35.45 PM.png
    Screen Shot 2019-08-02 at 8.35.45 PM.png
    868.9 KB · Views: 77
  • Screen Shot 2019-08-02 at 8.35.45 PM.png
    Screen Shot 2019-08-02 at 8.35.45 PM.png
    868.9 KB · Views: 66
  • Screen Shot 2019-08-02 at 8.36.55 PM.png
    Screen Shot 2019-08-02 at 8.36.55 PM.png
    638.4 KB · Views: 79
  • Screen Shot 2019-08-02 at 8.37.20 PM.png
    Screen Shot 2019-08-02 at 8.37.20 PM.png
    829 KB · Views: 69
  • Screen Shot 2019-08-02 at 8.38.22 PM.png
    Screen Shot 2019-08-02 at 8.38.22 PM.png
    667.9 KB · Views: 78
  • Screen Shot 2019-08-02 at 8.38.39 PM.png
    Screen Shot 2019-08-02 at 8.38.39 PM.png
    704.3 KB · Views: 69
  • Screen Shot 2019-08-02 at 8.39.06 PM.png
    Screen Shot 2019-08-02 at 8.39.06 PM.png
    665.1 KB · Views: 79
  • Screen Shot 2019-08-02 at 8.39.21 PM.png
    Screen Shot 2019-08-02 at 8.39.21 PM.png
    481 KB · Views: 76
  • 1.Prohibit Entry Error.png
    1.Prohibit Entry Error.png
    968.3 KB · Views: 88
  • Verbose Boot ->Prohibit Entry Error.
    • cause: USB port related
  • Currently used CLOVER not uploaded as suggested in my post #9 for diagnostic clues in EFI/CLOVER/kexts/Other and config.plist_Devices
  • BIOS options in the uploaded screen shots have some problems including Disabled EHCI that can cause the Verbose boot error .[ See all edited images.]
  • For more information about this error, check this post-> #6

Attached is the screenshots of the BIOS you asked for and my current Clover folder.
 

Attachments

  • CLOVER.zip
    2.9 MB · Views: 52
  • IMG_0042.jpeg
    IMG_0042.jpeg
    1.9 MB · Views: 63
  • IMG_0043.jpeg
    IMG_0043.jpeg
    1.7 MB · Views: 58
Attached is the screenshots of the BIOS you asked for and my current Clover folder.

  • I have uploaded edited Relevant BIOS Screen shot dealing with Graphics Display for you to change
  • I have Edited and annotated EFI_CLOVER FileTree with changes I suggest using.
  • I have reviewed your config.plist and found problems and annotated on Screen shots
    • in config.plist_Gui_USB, there is no [] FixOwnership that can cause current Verbose boot issue
    • I've annotated changes with needed [] for USB [and Audio and Graphics Intel GFX FakeID]
  • I suggest making all the changers in config.plist as annotated.
  • You might need additional changes in config.plist_ACPI.
    • But that depends on Verbose boot screen problems that might be encountered later.
 

Attachments

  • 1.BIOS Graphics Display.png
    1.BIOS Graphics Display.png
    713.8 KB · Views: 83
  • 2.EFI_CLOVER FileTree.png
    2.EFI_CLOVER FileTree.png
    214.9 KB · Views: 91
  • 3.config.plist_ACPI.png
    3.config.plist_ACPI.png
    284.6 KB · Views: 71
  • 4.config.plist_Boot.png
    4.config.plist_Boot.png
    259 KB · Views: 73
  • 5.config.plist_Devices.png
    5.config.plist_Devices.png
    224.3 KB · Views: 76
  • 6..config.plist_Gui.png
    6..config.plist_Gui.png
    224.5 KB · Views: 74
  • 7.config.plist_Graphics.png
    7.config.plist_Graphics.png
    217.6 KB · Views: 78
  • 8.config.plist_Kernel and Kext Patches.png
    8.config.plist_Kernel and Kext Patches.png
    213.7 KB · Views: 51
  • 9.config.plist_Rt Variables.png
    9.config.plist_Rt Variables.png
    256.5 KB · Views: 81
  • 10.config.plist_SMBIOS.png
    10.config.plist_SMBIOS.png
    233 KB · Views: 74
  • 11.config.plist_System Parameters.png
    11.config.plist_System Parameters.png
    266.3 KB · Views: 87
So I tried what you said and as soon as it got to the screen that I attached, then the system would instantly reboot, every time.

Clover folder is the same as last time and BIOS settings are what you recommended.
 

Attachments

  • 639EBE95-5AE0-4435-A77B-B1B7EC25D7BE.jpeg
    639EBE95-5AE0-4435-A77B-B1B7EC25D7BE.jpeg
    2 MB · Views: 62
Last edited:
So I tried what you said and as soon as it got to the screen that I attached, then the system would instantly reboot, every time.

Clover folder is the same as last time and BIOS settings are what you recommended.

After changing some BIOS settings, I managed to boot up to a prohibited symbol again. Not really sure to do now, maybe my computer is not compatible with macOS, maybe someone can help me?
 
After changing some BIOS settings, I managed to boot up to a prohibited symbol again. Not really sure to do now, maybe my computer is not compatible with macOS, maybe someone can help me?
Sorry, I cannot help you with answers like
After changing some BIOS settings, I managed to boot up to a prohibited symbol again.
Without knowing what changes you had made in the BIOS, I cannot predict what caused the issue except guessing you might have Disabled EHCI. I don't have clairvoyance to know how your current BIOS options look like without you uploading them or stating what exactly was changed.
Clover folder is the same as last time
I wasted my time to show you the problems in your uploaded CLOVER that caused the Prohibit Entry " and suggested changes in kexts _Other and config.plist_Devices to prevent you from getting the "Prohibit Entry Sign" in verbose boot. You had ignored that and preferred to use the same defective CLOVER!
 
After changing some BIOS settings, I managed to boot up to a prohibited symbol again. Not really sure to do now, maybe my computer is not compatible with macOS, maybe someone can help me?

Have you tried nv_disable=1 boot arg.
 
Status
Not open for further replies.
Back
Top