Search results

Looping back on this to close it out with some lesson's learnt which might hopefully help others. These are important points/steps which worked for me and I don't see getting mentioned much (at least for High Sierra install). When creating a new system: 1.) Have NO drives added except USB and...

Just when I thought I was making progress... :banghead: I made a working drive for High Sierra, boots up fine with the EFI in use. Followed EXACTLY same process (same USB installed stick with Unibeast) to create another drive. The only difference is this new one is a Samsung EVO 870 1Tb whereas...

UBD, Thanks once again for your help. Finally got to the bottom of the issue... kind of... Turns out that the config.plist being in the "wrong location" meant that it wasn't the one being loaded. I'm still at a loss what config.plist file was actually being used on boot-up, but I feel as though...

Sorry I think was just an unfortunate crop of the screen grab there. See attached, I've widened it out. When I mount the EFI partition of 'Main Original' (using CC) it has all the appropriate EFI/ABC folders (although the strange part is the config.plist is in the root, not under Clover...

Yes but I’ve checked those drives. I can’t find a config.plist file anywhere that matches the systems properties. Dumbfounded.

I'm sorry if this is a stupid question but I can't get my head around it... Please correct my understanding... I have booted into an EFI partition of a drive and so Clover should run in accordance with the contents of the EFI folder that resides in that partition? Right? So in my case for...

OMG. I’m in shock. Just before receiving this reply I thought I’d go ahead and clean up ghost drives for a laugh with the bcfg dump method. Sure enough, BOOM, EFI shows up on USB! Can’t believe those entries were wreaking so much havoc! Lesson learnt. Hallelujah! Just trying out the installer...

I did that at the time but installer never came back. All I had was a grey screen, couldn’t do anything. Regardless, I’m just mentioning it because it was when my EFI recognition issue began & I’m not sure whether there’d be a link. Main problem is EFI recognition right now.

I’m not sure if this provides any clue to what’s happened but this all started after I actually got through to the installer at one point. ie, EFI was recognized, bootloader loaded, I ran kext injections, got to installer point, but then got an error (attached). I read this was because bios date...

Yep definitely using 8.4.0. And running it out of Applications directory. And SIP disabled.

I’ll try removing that drive and creating USB again but I’m not very hopeful. I’d like to try though because getting Unibeast working sounds hellavalot less convoluted than that manual install method!

Does that tell you anything?

Do you think the ghosting issue is affecting the USB EFI discovery issue? I'd prefer not going down that path if I didnt need to and it wasn't going to address my initial issue.

btw, here is a super weird observation... when running Unibeast installer creator on the Catalina machine, it was quite fast and the EFI partition was left empty at the end. Nothing copied to it. On the other hand, when running exact same Unibeast installer on a High Sierra machine, it took much...

Okay thanks UDB. I’ll try that. I’ve run out of options at this stage. Just one other thing. I’ve removed everything from mobo except the USB and this is what I get on F12 (attached). Do you have any idea what those Mac OS X and UEFI OS entries are? They reappear even when clearing CMOS (none of...

Just did a fresh install again. Here you can see it mounted and empty.

yep. I experimented with putting a working EFI folder on there just to see if that did anything (it didn't).

Partition seems setup ok?

UDB, thought I would check this but I'm not sure what the equivalent setting nomenclature is for this in the Gigabyte BIOS world... Is it xHCI mode? Boot Mode selection I have as UEFI and Legacy. There is a USB Storage Device section but I have that as Auto. There is an option to change that to...