Hmm. It doesnt suddenly. Maybe a restart will help?
Edit: it says the same thing also when only using efibootmgr (with sudo too)
Yeah, try restarting. You need to make sure you arenât booting in Compatibility Support Mode or Legacy Mode or anything like that. (But then, it worked in your earlier screenshot, so presumably you arenât doing that.)
Nah i started in normal mode
Ok it worked after a restart. It added a new boot entry. Sorry for the formatting
Commands
liveuser@localhost-live:~$ efibootmgr --create --index 0002 --disk /dev/nvme0n1 --part 1 --loader \\EFI\\fedora\\shimx64.efi --label "Fedora (interne SSD)" Could not prepare Boot variable: Permission denied liveuser@localhost-live:~$ sudo efibootmgr --create --index 0002 --disk /dev/nvme0n1 --part 1 --loader \\EFI\\fedora\\shimx64.efi --label "Fedora (interne SSD)" BootCurrent: 001E Timeout: 0 seconds BootOrder: 0001,0000,0002,001A,001B,001C,001E,001D,0020,0021,001F Boot0000* Windows Boot Manager HD(1,GPT,61e81dd0-0fbf-4c1a-938f-18365e878569,0x800,0x64000)/\EFI\Microsoft\Boot\bootmgfw.efi57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000000000100000010000000040000007fff0400 Boot0001* Fedora HD(1,GPT,a0929102-aabb-4ed3-9c12-ad7a4c0daec4,0x800,0x12c000)/\EFI\fedora\shimx64.efi Boot0010 Setup FvFile(721c8b66-426c-4e86-8e99-3457c46ab0b9) Boot0011 Boot Menu FvFile(126a762d-5758-4fca-8531-201a7f57f850) Boot0012 Diagnostic Splash Screen FvFile(a7d8d9a6-6ab0-4aeb-ad9d-163e59a7a380) Boot0013 Lenovo Diagnostics FvFile(3f7e615b-0d45-4f80-88dc-26b234958560) Boot0014 ThinkShield secure wipe FvFile(3593a0d5-bd52-43a0-808e-cbff5ece2477) Boot0015 ThinkShield Passwordless Power-On Device Manager FvFile(08448b41-7f83-49be-82a7-0e84790ab133) Boot0016 Wi-Fi Configuration FvFile(d3aaff0f-cb22-4792-896c-802c2e9383ba)2d004100700070000000 Boot0017 Asset Information FvFile(da465b87-a26f-4c12-b78a-0361428fa026) Boot0018 Startup Interrupt Menu FvFile(f46ee6f4-4785-43a3-923d-7f786c3c8479) Boot0019 Rescue and Recovery FvFile(665d3f60-ad3e-4cad-8e26-db46eee9f1b5) Boot001A USB CD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,86701296aa5a7848b66cd49dd3ba6a55) Boot001B USB FDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,6ff015a28830b543a8b8641009461e49) Boot001C* NVMe0 VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,001c199932d94c4eae9aa0b6e98eb8a400) Boot001D* Other HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ca88c2349e7ae947beeb43038a5aeae700) Boot001E* USB HDD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,33e821aaaf33bc4789bd419f88c50803) Boot001F PXE BOOT VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,78a84aaf2b2afc4ea79cf5cc8f3d3803) Boot0020 LENOVO CLOUD VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri(https://download.lenovo.com/pccbbs/cdeploy/efi/boot.efi) Boot0021 ON-PREMISE VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,ad38ccbbf7edf04d959cf42aa74d3650)/Uri() Boot0022 Regulatory Information FvFile(478c92a0-2622-42b7-a65d-5894169e4d24) Boot0023* Boot Next Boot Option VenMsg(bc7838d2-0f82-4d60-8316-c068ee79d25b,91af625956449f41a7b91f4f892ab0f6) Boot0002* Fedora (interne SSD) HD(1,GPT,61e81dd0-0fbf-4c1a-938f-18365e878569,0x800,0x64000)/\EFI\fedora\shimx64.efi liveuser@localhost-live:~$
Edit: kinda fixed formatting 
Thatâs a lot of boot entries 
but our new one at the end looks good.
Now try rebooting and going into your BIOS boot menu (hit F12 or whatever key your BIOS uses) and hopefully youâre going to see that âFedora (interne SSD)â option available to boot from.
Hell yeah man. Youâre the best. It worked.
Is there anything else we need to do? Like checking something in my regular fedora?
I think its ok enough when I just remove the wrong Fedora bootloader(is that the correct term?) from the boot order in my bios settings and set the new one as the first? Or would you recommend me to remove the old/bad one?
And just as a short question: do my grub settings look normal to you? I only remember adding abmlevel as a parameter, but I dont recall the others.
Excellent! 
To be honest I think thereâs no particular need to check anything else. If you can boot into your old Fedora, then the installer wonât have touched it.
Looks like all that happened is that the EFI entry got removed, and we just needed to add it back with efibootmgr. (I suspect that would have worked even without doing the âreinstall bootloaderâ steps.)
That all looks normal to me for an install with disk encryption.
Allright that sounds good, again thank you my man I hope you have a wonderful day 