How to repair fedora bootloader (standard install failed to install bootloader)

android@clr~ $ lsblk -f
NAME            FSTYPE      FSVER    LABEL       UUID                                   FSAVAIL FSUSE% MOUNTPOINT
├─sda1          vfat        FAT32                E336-730F                               775.8M     3% /run/media/android/E336-730F
├─sda2          ext4        1.0                  deeb34fe-12f3-43da-a15a-d5bafebaae8b    828.5M     8% /run/media/android/deeb34fe-12f3-43da-a15a-d5bafebaae8b
├─sda3          ext4        1.0                  bb99b31e-059d-42b2-84d0-e5d18118b5cf     84.6G    15% /
├─sda4          ext4        1.0                  ab32383d-0597-403c-8f1c-d3b419550848                  
├─sda5          LVM2_member LVM2 001             0NAEw4-3iv5-uMV9-8qQy-JvLe-3QYj-4MdJ0C                
│ ├─fedora-swap swap        1                    8d43a610-b428-40cd-8a36-b9ed28b9fd3e                  
│ ├─fedora-home ext4        1.0                  a8046952-0e31-4a79-859b-94ed16b3273f                  
│ └─fedora-root ext4        1.0                  d8d9a5ab-5c1a-430a-acb3-d491a1c5d1da                  
└─sda6          ntfs                 router_data 4416017316016770                        105.9G    62% /home/android/routerbind/4416017316016770
android@clr~ $ ls /run/media/android/deeb34fe-12f3-43da-a15a-d5bafebaae8b
efi  grub2  loader  loader.0  lost+found  ostree
android@clr~ $

android@clr~ $ efibootmgr -v
BootCurrent: 0000
Timeout: 2 seconds
BootOrder: 0001,0000,002E,0018,0019
Boot0000* Linux bootloader	HD(1,GPT,e38b7f80-b206-4738-9d94-e92f1765eb2a,0x800,0x192000)/File(\EFI\org.clearlinux\bootloaderx64.efi)
Boot0001* Fedora	HD(1,GPT,e38b7f80-b206-4738-9d94-e92f1765eb2a,0x800,0x192000)/File(\EFI\fedora\shimx64.efi)
Boot0018* UEFI: IP4 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/MAC(e0db55a63999,0)/IPv4(,0,0)AMBO
Boot0019* UEFI: IP6 Realtek PCIe FE Family Controller	PciRoot(0x0)/Pci(0x1c,0x5)/Pci(0x0,0x0)/MAC(e0db55a63999,0)/IPv6([::]:<->[::]:,0,0)AMBO
Boot002E* UEFI OS	HD(1,GPT,e38b7f80-b206-4738-9d94-e92f1765eb2a,0x800,0x192000)/File(\EFI\BOOT\BOOTX64.EFI)
android@clr~ $

Be careful to follow the instructions for UEFI systems.

How are you running those commands (from live media or from the affected machine?)

That depends on whether you can boot the installed system somehow. If you can’t, you’ll have to use a live medium (or e.g. attach your disk to another system) and chroot into it to perform the operations.

this happened in fedora silverblue failed install.