Contribute
Register

EFI Agent v1.3.2 (menu bar utility)

Hmm... Sadly I too am now getting:

392776


... with version 1.1.2

Similarly, opening the package and running the MountEFI through Terminal shows no errors.

I'm using High Sierra 10.13.6 HFS+ at the moment. My Mojave install is on an unattached SSD.

Thanks for all your work on this :thumbup:

:)
 
Here's the situation: when I start MountEFI, there's no error message, thing looks pretty normal. But when I click the icon on menu bar for the first time, it doesn't respond and no menu shows. And when I click the icon second time, the menu shows and nothing on it.

Here's the error message on console, wish it helps.
392853
 
Can you download from the official link again and then run MountEFI.app/Contents/MacOS/MountEFI from Terminal and see if it spits out any errors.


@headkaze,

Downloaded Version 1.1.2 and ran from terminal, no errors and no partition scheme :-

392954

Reinstalled version 1.0.8 and everything works ok :-

392956

Not sure if its relevant but i few things to consider :-
  1. Running Mojave 10.14.3
  2. MacOS system partition is formatted as HFS+ not APFS
  3. My Laptop has a single 1TB NVMe with a complex Partition scheme (multiboot - MacOS,Windows 10, Linux)
  4. As you can see from the second image MountEFI does not highlight the boot EFI in green ?
Will test latest version on my desktop hack and see if it works on that.

Cheers
Jay

Update: Just tested Version 1.1.2 on my Desktop hack, unfortunately no dice .. same issue .. no Partition Scheme.
So I guess that eliminates options 2 & 3 in the above list ....
 
Last edited:
That did it ... MountEFI Version 1.1.3 now working for me .... Nice Job buddy :)

Great! But I do see it is not highlighting your EFI boot drive. Can you run the latest Hackintool and show me if you have the following NVRAM variable.
 

Attachments

  • EFIBootDevice.png
    EFIBootDevice.png
    594.4 KB · Views: 166
Great! But I do see it is not highlighting your EFI boot drive. Can you run the latest Hackintool and show me if you have the following NVRAM variable.


@headkaze,

Hummm you must have read my mind as i was just about to post that its not highlighting my boot EFI drive ?
No Versions of MountEFI or Hackingtool so far have done that for me on any of my Hacks ....

Checking NVRAM variables with the latest version of Hackingtool shows that 'efi-boot-devce' is not a variable in NVRAM :-

392990
As well as missing from my desktop hack it's also missing on my laptop hack ?

Both builds are using AptioMemoryFix-64.efi for native NVRAM which is working fine for all other NVRAM variables.

Any suggestions ? .... I could try manually adding it , i can get the UUID from terminal -> diskutil :-

392993
But would need the full code of the <array> / <dict> from yourself ....


Cheers
Jay
 
Last edited:
I have no idea I'm afraid. Maybe @RehabMan can give us a clue?

Any chance you can copy and paste your Variable Value code for 'efi-boot-devce'
I'll replace your UUID with mine and see what happens ....

Cheers
Jay
 
Works fine for me : 1.1.3 nice app. ;)

392994
 
Last edited:
Back
Top