Contribute
Register

Can't boot into Mojave after installation

Status
Not open for further replies.
Joined
Aug 20, 2012
Messages
61
Motherboard
Gigabyte Z77X-UD5H
CPU
Intel i7 3770K 3.5Ghz @ 4.3Ghz
Graphics
MSI Radeon RX 580 Armor 8GB OC
Mac
  1. MacBook Pro
Mobile Phone
  1. Android
  2. iOS
Luckily I did make a copy of the SSD with CCC, which is where I'm now writing this from.

It was running 10.12 (Sierra) and I ran the Mojave update. Followed the instructions to install directly, but I may have done something wrong.
It did a bunch of reboots on its own. It did eventually boot into Mojave, with no Wi-Fi and no sound.
I rebooted and never again was I able to boot into Mojave, unless I use the safe mode boot flag.

Verbose mode tells me it's stalling a bit with something related to PEGP (what is that?).
And then eventually outputs the `IOFB?: newUserClient waitQuiteController failed...` lines.

Attaching both a pic of the verbose result when booting (no safe mode), as well as a copy of the /EFI/CLOVER folder.

Any tips on what to try next?
 

Attachments

  • IMG_20190620_194615.jpg
    IMG_20190620_194615.jpg
    2.6 MB · Views: 96
  • CLOVER.zip
    1.2 MB · Views: 67
Luckily I did make a copy of the SSD with CCC, which is where I'm now writing this from.

It was running 10.12 (Sierra) and I ran the Mojave update. Followed the instructions to install directly, but I may have done something wrong.
It did a bunch of reboots on its own. It did eventually boot into Mojave, with no Wi-Fi and no sound.
I rebooted and never again was I able to boot into Mojave, unless I use the safe mode boot flag.

Verbose mode tells me it's stalling a bit with something related to PEGP (what is that?).
And then eventually outputs the `IOFB?: newUserClient waitQuiteController failed...` lines.

Attaching both a pic of the verbose result when booting (no safe mode), as well as a copy of the /EFI/CLOVER folder.

Any tips on what to try next?
  • Your uploaded CLOVER lacks all important components like AptioFix .. in drivers64UEFI, essential kexts in CLOVER/kexts/Other (it is empty) and your config.plist requires a complete make over(Many SECTIONS are blank) .
    • See the edited CLOVER FileTree Screen shot of your CLOVER and a screen shot for comparison of a working EFI_CLOVER FileTree on a similar MoBo (GA-Z77X-UP5Th) running Mojave 10.14.5 (works also with 10.14.6 Beta and Catalina 10.15. Beta 2)
 

Attachments

  • 1.CLOVER FileTree.png
    1.CLOVER FileTree.png
    71 KB · Views: 79
  • 2.EFI _CLOVER FileTree that works.png
    2.EFI _CLOVER FileTree that works.png
    109.4 KB · Views: 100
Oh, that's embarrassing... That wasn't even the folder I should have attached.
Sorry about that.

Attaching the real one now.
It seems I have some of those kexts, but not all of them...
 

Attachments

  • CLOVER.zip
    1.5 MB · Views: 57
@cmn699 after going through your file tree I added a couple of kexts to /CLOVER/kexts/Other, being the current list:
* AppleALC
* FakeSMC
* IntelMausiEthernet
* Lilu
* RealtekRTL8111
* WatheverGreen

Removed the other FakeSMC related kexts I previously had just to check if it would help.
Also removed the faulty drive which was getting the I/O error.

I'm now getting a GFX0 timeout error (attached).
Still not able to boot.
 

Attachments

  • IMG_20190621_152951.jpg
    IMG_20190621_152951.jpg
    2.8 MB · Views: 48
@cmn699 after going through your file tree I added a couple of kexts to /CLOVER/kexts/Other, being the current list:
* AppleALC
* FakeSMC
* IntelMausiEthernet
* Lilu
* RealtekRTL8111
* WatheverGreen

Removed the other FakeSMC related kexts I previously had just to check if it would help.
Also removed the faulty drive which was getting the I/O error.

I'm now getting a GFX0 timeout error (attached).
Still not able to boot.

The verbose boot screen is referring to some delay/pause/freeze from Graphics card.
It is not specific pinpointing the exact problem.
To define the problem and suggest the next best step, I need a bit more information.
  • Please upload the CLOVER Folder (as zipped) from the currently edited EFI of your booting Mojave UEFI USB Installer Flash disk
    • Your previously uploaded (2nd time) CLOVER has also some problems in kexts/Other and in config.plist _Graphics, Rt Variables, System Parameters SECTIONS
  • Please Upload the BIOS options chosen for the boot (preferably screen shots) this USB Installer has to use in conjunction with its Clover Bootloader and needed files from the important Folders in EFI/CLOVER.
    • Best way to get BIOS Screen Captures is to do AutoCapture using F-12 Key while viewing various menu tabs and sub-menus in BIOS and saving the images to the FAT32 formatted EFI Partition of the USB Installer Flash disk to open and see after attaching it to Real Mac or Working Hackintosh.
 
Please upload the CLOVER Folder (as zipped) from the currently edited EFI of your booting Mojave UEFI USB Installer Flash disk

I don't have a USB installer flash drive. I followed this guide.
Are you referring to the CLOVER folder in the EFI partition?
 
I don't have a USB installer flash drive. I followed this guide.
Are you referring to the CLOVER folder in the EFI partition?
  • My bad.
  • It is from the Booting disk, in this case its' your Sierra System Hard Disk.
  • I hope you had already updated its CLOVER EFI Bootloader to the current CLOVER Version BEFORE attempting Sierra to Mojave OS Upgrade.
  • When you do that it may not always replace all the needed files as we want to make the Upgrade to succeed.
  • You still have to open , view and EDIT the EFI _CLOVER and config.plist BEFORE attempting the upgrade.
    • In my view this part is NOT emphasized clearly in the guide. Only to verify and add needed kexts are emphasized.
    • The part dealing with config.plist or checking CLOVER/drivers64UEFI are often overlooked and may be causing issues leading to boot failure.
  • Since you cannot upload the EFI from this System Disk, take photos of the following to upload:
    • Clover Boot Manager Screen with icons view
    • Options_Boot Args:
    • Options_GraphicsInjector
    • Options_System BIOS
    • Options_System Parameters.
  • If any of the options there has a problem, we can make a temporary fix by editing that Options_Submenu to see if you can reach the Login Screen and the Desktop to make a permanent fix by viewing and editing EFI_CLOVER of system disk.
  • I still need to verify BIOS options as they might have changed with Forced shut down and Reboot during your attempted installation causing CMOS corruptions.
  • Please note CBM _Options screen editing suggested above is a temporary fix for wrong or missing options in config.plist.
    • There is NO way to add missing kexts in CLOVER/kexts/Other or missing EFI files in CLOVER/drivers64UEFI
      • To overcome such problem, we need a USB installer Disk
 
  • It is from the Booting disk, in this case its' your Sierra System Hard Disk.
In that case, that's the 2nd one I posted above.

  • In my view this part is NOT emphasized clearly in the guide. Only to verify and add needed kexts are emphasized.
It sure isn't. I don't remember doing any of that.

  • I hope you had already updated its CLOVER EFI Bootloader to the current CLOVER Version BEFORE attempting Sierra to Mojave OS Upgrade.
It's on version 4934 right now. Can't recall exactly when I installed it, but I remember seeing the version number was higher than the one requested in the guide.

I'm attaching photos and screenshots of both Clover and BIOS settings.
As an unfortunate update, I've managed to screw something up in the bootable clone drive, and it's also not booting right now. That's to say I now have no way of editing/reading/copying files from the Mojave (named Sierra for lack of an update) drive.

Hope we can sort this out, otherwise, clean install it is...
Thanks for your help @cmn699!
 

Attachments

  • BIOS.zip
    1.2 MB · Views: 49
  • CLOVER_settings.zip
    4.5 MB · Views: 81
In that case, that's the 2nd one I posted above.


It sure isn't. I don't remember doing any of that.


It's on version 4934 right now. Can't recall exactly when I installed it, but I remember seeing the version number was higher than the one requested in the guide.

I'm attaching photos and screenshots of both Clover and BIOS settings.
As an unfortunate update, I've managed to screw something up in the bootable clone drive, and it's also not booting right now. That's to say I now have no way of editing/reading/copying files from the Mojave (named Sierra for lack of an update) drive.

Hope we can sort this out, otherwise, clean install it is...
Thanks for your help @cmn699!
  • I am uploading the edited BIOS screen captures with some annotations for you to consider
  • In CBM _Options_ Graphics Injector->Graphics is Nvidia GTX 660 Ti.
  • You have made BIOS Peripherals_ Initial Display as "Auto";
    • I suggest changing BIOS _Peripherals_initial Display to : PCIE
  • In CBM Options_ Boot Args Try editing as shown in my uploaded image _1.CBM_Options_Boot Args
  • In CBM _Options_System Parameters your SIP value is 0x3 ; I suggest changing that to 0x67 using the Uploaded image 2.CBM_System Parameters_SIP Disabled Check Boxes as the model.
As previously mentioned, this is a long shot; if the problem is in the CLOVER/drivers64UEFI contents or kexts/Other , the above troubleshoot cannot fix the issue.
 

Attachments

  • 2.BIOS Version and Clock.png
    2.BIOS Version and Clock.png
    171.6 KB · Views: 68
  • 1.XMP.png
    1.XMP.png
    164.9 KB · Views: 73
  • 3.BIOS Features.png
    3.BIOS Features.png
    216.2 KB · Views: 75
  • 4.BIOS Features.png
    4.BIOS Features.png
    205.2 KB · Views: 60
  • 5.Peripherals.png
    5.Peripherals.png
    218.2 KB · Views: 61
  • 6.Peripherals.png
    6.Peripherals.png
    217 KB · Views: 75
  • 7.Power Management.png
    7.Power Management.png
    188.7 KB · Views: 67
  • 1.CBM_Options _Boot Args .png
    1.CBM_Options _Boot Args .png
    555.5 KB · Views: 59
  • 2.CBM_System Parameters_SIP Disabled Check Boxes.png
    2.CBM_System Parameters_SIP Disabled Check Boxes.png
    1.4 MB · Views: 59
I went through the BIOS options you suggested but now when it boots it makes an error sound like "____ _ _ _" (1 long + 3 short). Doesn't even get to the BIOS screen anymore.

On your image 6, you're assuming I have HDMI connected to the motherboard port, but it isn't, it's connected to the graphics card. Anything I should change there?
And how do I get back to the BIOS now?
 
Status
Not open for further replies.
Back
Top