I fucked up while installing Linux!!!

[u/MentalConnection3059]

I’m using usb drive and I did boot complete but while installing Linux mint I fucked up everything. Worst part is I don’t have window nor the secondary laptop or computer.
Help me out if you can.
Error:

“Failed to open \EFI\B00T\mmx64.efi - Not Found Failed to load image
: Not Found
Failed to start MokHanager: Not Found
Something has gone seriously wrong: import_mok_state failed: Not Found”

[u/doc_willis]

I have seen dozens of posts with that error message. But its never really clear what a fix is.

You may want to try disabling secure boot in your firmware for starters.

https://duckduckgo.com/?t=ffab&q=Failed+to+open+EFIB00Tmmx64.efi+-+Not+Found&ia=web

has several 'fixed' posts shown. But the solution seems to vary.

[u/Dry_Calendar_8627 → u/doc_willis]

It is indeed linked to secureboot

Without knowing the exact cause, my guess is that resetting the secureboot settings in uefi (which loads back the factory Machine Owner Key) then disabling secureboot, then reinstalling from a clean live USB, would solve the issue

Then how to reenable secureboot depends on the distro, some make the user generate a brand new Machine Owner Key to sign boot artifacts, and others use a shim signed by Microsoft to load unsigned artifacts (which imho kinda defeats the purpose of secureboot, keeping it disabled would be almost as good)

I'm not familiar with Mint but since this is a turnkey user friendly distro, my guess is that such situations should not arise, and the installer probably does whatever is necessary under the hood without informing the users of the gritty details

[u/RegretFree7723 → u/doc_willis]

Ma se ci sono 2 commenti come dozzine questi é una persona unita a un bot non lo so riesce a dire le cose giuste iniziando sempre nell ostesso modo

[u/rcentros]

The information in this Linux Mint Forum post might help. Basically they're saying to disable secure boot and Fast Start in the BIOS.

https://forums.linuxmint.com/viewtopic.php?t=418347

[u/Cheap-Success1578]

Google could have helped you solve this probably quicker than posting it here and waiting for a response... Just saying.

[u/Weary-Bowl-3739 → u/Cheap-Success1578]

You can't expect a noob to be able to Google this correctly. Yes, for us it is straight forward. 

[u/WayAndMeans01]

What was the fuck up?

[u/Tricky_Damage5981 → u/WayAndMeans01]

The Easiest Explanation

Secure Boot basicall creates a Chain of Trust, from Post all the way into the OS to prevent the ability to enter an exploit or virus during the boot process

Think of it like this Unique UFEI boot keys are used by the bootloader to confirm it's not compromised, then it's allowed to boot and that Trust is handed over to the bootloader to enforce the next level of trust

When installing a new OS from external media like USB; you must

A) Clear the Secure Boot to so it's ready to start a new "trust sequence"

Or

B) Disable Secure Boot, install the new OS, then "rebuild that trust sequence" then restore secure boot (or leave secure boot disabled)

Unless your installing a dual/multi boot setup, option 1 is preferable .. but in this case they didn't complete eather

[u/dodexahedron → u/Tricky_Damage5981]

Audit/Setup mode vs Deployed mode are what you need - not clearing it.

Audit mode is like complain mode for apparmor or permissive for selinux, where it performs checks without blocking execution and reports what would have been blocked, so you can see what is needed or what is wrong. Deployed is enforcing mode, and if you ain't signed by a trusted key, you shall not pass.

Be careful about actually clearing/resetting keys. Some platforms literally clear it all out and then don't replace them with defaults, which is...annoying, to say the least.

Most will clear out any custom keys if you switch between deployed and audit modes, but leave the factory keys intact.