<< Solved >> Installation stuck at AppleUSBHostResources

[turtlelee]

First, sorry for my poor English T^T. I'll try my best to explain my problems clearly.


I mainly use the clover efi which provided by this website(Clover_v2.4k_r4586)

if i don't change anything it'll stuck at AppleUSBHostResource...

https://imgur.com/YFdL6b9

if i let USB Ownership and USB Injection on, it'll stuck at EndRandomSeed

if i use other version Clover which can customize(plus OsxAptioFix3Drv-64.efi or other likely efi), it'll error load kernel cache.

Of course I have try prekexts like whatevergreen, lilu, FakeSMC, USBInjectAll.
But just seems it doesn't work.

Thanks!

 

[turtlelee]

Bios setting:
1. Load Optimized Defaults -> Can't find
2. If your CPU supports VT-d, disable it -> Done
3. If your system has CFG-Lock, disable it -> Can't find
4. If your system has Secure Boot Mode, disable it -> Doesn't have
5. Set OS Type to Other OS -> Can't find
6. If your system has IO Serial Port, disable it -> Done
7. Set XHCI Handoff to Enabled -> If mean Legacy USB3.0 Support, then Done

All use USB2.0 port.

Clover EFI use v2.4k_r4844.
Have choosed ApfsdriverLoader-64 and AptioMemoryfix-64.

Config:
USB-Inject -> Check
USB-Fixownership -> Check

Kext/others:
AppleALC, FakeSMC, Lilu, USBInjectALL, WhateverGreen

And it stuck at End RandomSeed.

Or should I use older OSX?
Is there any suggestions ;_;?

 

[turtlelee]

Now, if I enter Boot OS X Install from Install macOS Mojave with -v-f.
It'll stuck at End RandomSeed ++++++

Search lots of threads, the reason is lost apito memory-fix.
This problem may have be fixed in recently Clover EFI version?
And of course there is AptioMemoryfix-64 in my boot usb/EFI.

But my RAM slot A1 is invalid. Will this cause the problem?

thx.

 

[cmn699]

Now, if I enter Boot OS X Install from Install macOS Mojave with -v-f.
It'll stuck at End RandomSeed ++++++

Search lots of threads, the reason is lost apito memory-fix.
This problem may have be fixed in recently Clover EFI version?
And of course there is AptioMemoryfix-64 in my boot usb/EFI.

But my RAM slot A1 is invalid. Will this cause the problem?

thx.

Not a good idea not to upload(attach) verbose boot screen to the Forum and instead just paraphrase a line of text as the only observation from Monitor screen.
The quoted line" End RandomSeed ++++++ " if the monitor screen is truly stuck, is from a Memory Mapping problem

• A memory Mapping problem can occasionally appear without any real damage or problem to BIOS, RAM, or software inside the Boot disk and may disappear with a reboot.
• If it is persistent, it can be from a hardware or software issue.
• Start with Software troubleshoot because of the need to shut down , power off electrostatic precautions etc involved in Removal of RAM modules and examination of RAM sockets
• Software mainly responsible for Memory Mapping is inside /EFI/CLOVER/drivers64UEFI
• Hardware is the RAM module or RAM socket or actual damaged or incompatible RAM: May need to open the case remove the RAM module, clean its pins , clean the socket off dust and debris and reinsert and try again.
• If still problem try each module one at a time.
• If RAM works in WINDOWS or Linux it is unlikely to be a Defective RAM
• If you are sure your RAM slot A1 is invalid, that can cause Memory Mapping error you have posted.

 

[turtlelee]

I have inserted the RAM to A1 more strongly, it do work... ok, well, it just contact not well.
I gave up using the slot for a year haha.

But the OSx installation still makes me disappointed ;_;

My ram are Micron Ballistix sport ram 4G DDR3-1600
In windows all fine.
I had installed Mountain Lion~Maverick before.
Maybe I'll try may cousins PC later.

Thank you very much!

 

[cmn699]

I have inserted the RAM to A1 more strongly, it do work... ok, well, it just contact not well.
I gave up using the slot for a year haha.

But the OSx installation still makes me disappointed ;_;

My ram are Micron Ballistix sport ram 4G DDR3-1600
In windows all fine.
I had installed Mountain Lion~Maverick before.
Maybe I'll try may cousins PC later.

Thank you very much!

Do you have only 1 x 4GB DDR3 -1600 RAM total? or is that the RAM Module in Slot A1 and you have other RAMS in other slots?
When you forcibly insert the RAM in SLOT A1 and go to BIOS, does your BIOS see all the total inserted RAM?
If the TOTAL RAM in the BIOS is what you have inserted RAM is unlikely the issue.
If that is the case, see my uploaded CLOVER/EFI/drivers64UEFI and you insert the same EFI files in your CLOVER/EFI/drivers64UEFI also.
Edit CLOVER/kexts/Other >add XHCIunsupported.kext [See image]

I suggest editing your config.plist. (See images BOOT|Graphics|RT Varaiables)
Edited and annotated config.plist SECTIONS are uploaded to show what you can try in your system and then save that and boot and take verbose boot screen to upload.

 

[turtlelee]

I have 3 x 4GB ram, and bios could see all RAM.
So I think this has be O.K.

And I just upgrade my BIOS version. Then it works... Sorry for my idiot behavior.
But all of this are useful, I learn a lot. I can expect there will be more problems;_;
Even I'll help my cousin to install OSX with his AMD cpu haha...

Now it can't format my Intel SSD to MacOS extend(GUID). I'll search it first

P.s. What's the meaning about 0x3->0x67?

Thank you very much!!

 

[cmn699]

I have 3 x 4GB ram, and bios could see all RAM.
So I think this has be O.K.

And I just upgrade my BIOS version. Then it works... Sorry for my idiot behavior.
But all of this are useful, I learn a lot. I can expect there will be more problems;_;
Even I'll help my cousin to install OSX with his AMD cpu haha...

Now it can't format my Intel SSD to MacOS extend(GUID). I'll search it first

P.s. What's the meaning about 0x3->0x67?

Thank you very much!!

P.s. What's the meaning about 0x3->0x67?

This is about disabling System Integrity Protection (SIP) by changing the current value of 0x30 to 0x67 for CsrActiveConfig.
This SIP Disabling is required to enable kexts (non-Mac) from /CLOVER/kexts/Other to be loaded to enable booting.

Now it can't format my Intel SSD to MacOS extend(GUID). I'll search it first

You should Format SSD in APFS for MOJAVE.
DO NOT FORMAT in HFS+J; you will face problem during installation.

 

[turtlelee]

Thanks for your remind!!