You should be able to do this from within the firmware settings itself. Usually under the last tab to the right I think.
“Remove powercord and remove battery. Wait a few minutes then power up without the battery.”
Only with the powercord from what I can read in that link.
I don’t see any tabs to the right in the Bios settings I sent above. It’s all one menu and no mention of firmware settings
battery clearly says do not disassemble, what’s the easiest way to remove it?
I guess you need to figure out that one by yourself 
Perhaps it is enough to “gently” disconnect the connector?
Watch some YT videos for how-to.
You have the bottom of the case off. How many m.2 drives are in it. One or two? Your original post with lsblk command only shows one drive. Not sure why it was showing two drives? I don’t see any settings in the bios that would indicate it is a raid setup? The bios hardly has any settings that I can see unless there’s more pages?
Edit: I only see one drive beside the battery.
Yes it only has one drive. No idea why originally in the Bios it showed two, though after removing all boot entries now it only shows one.
Yes the Bios has very few settings and there aren’t any additional pages.
I feel so lost, will try tonight to do something with the battery… 
I also have another laptop available for 36 hours then I have to catch a flight… what a timing for this unexplainable issue
What is loaded on the laptop. Just EndeavourOS?
Your UEFI basically has very little in the way of settings. Did you ever enable TPM and remove the keys then turn off and try again to turn off secure boot.
Edit: I think you did this before. Anyway is it possible for you to boot on another live usb such as PopOs? If you can do that and maybe i can get a look at some more info such as the hardware.
I would like to see inxi -Faz --no-host
Also i see here are items below the screenshot you posted that allow you to set the default Bios settings. This will most likely have secure boot on and maybe TPM also. Try to disable secure boot but leave TPM on after setting the defaults. See if any different.
Yes, Just EOS.
Tried to set default then disable secure boot but nothing, restarts showing secure boot enabled.
Working right now on trying to boot into Pop Os.
getting this error trying to boot into a live USB with newest Pop OS version
also trying to boot into live USB with newest EOS iso gets into the usual boot fail and no boot device error
I just don’t have enough information about the hardware that you have. I did find this about the error message you are showing but it is different hardware. Some laptops have special keys such as Ctrl s to open a certain screen in the bios to get into other settings that you don’t see normally. I don’t know on your hardware how it is set up? If it is possible to get it to boot then it would be nice to see the hardware. You may have to install inxi first. Then inxi -Faz --no-host
Here is the info regarding that error but it is on a zenbook.
Here is more of the same. It is all related to secure boot and keys.
Have you set an administrator password? A quick Google search suggests you might need to do this before you can disable Secure Boot in some implementations of the InsydeH20 BIOS.
If you do, make sure that you can remember what password you set. A forgotten BIOS password can be difficult (and sometimes essentially impossible) to reset.
I managed to get this booting into tails.
System:
Kernel: 5.9.0-0.bpo.2-amd64 x86_64 bits: 64 Desktop: Gnome 3.30.2
Distro: unknown
Machine:
Type: Laptop System: HUAWEI product: HLYL-WXX9 v: M1090 serial: <filter>
Mobo: HUAWEI model: HLYL-WXX9-PCB v: M1090 serial: <filter> UEFI: HUAWEI
v: 1.07 date: 12/14/2020
Battery:
ID-1: BAT1 charge: 32.0 Wh condition: 54.4/54.9 Wh (99%)
CPU:
Topology: 8-Core model: AMD Ryzen 7 4800H with Radeon Graphics bits: 64
type: MT MCP family: 17 (23) model-id: 60 (96) stepping: 1
microcode: 8600104 L2 cache: 4096 KiB
Speed: 1397 MHz min/max: 1400/2900 MHz Core speeds (MHz): 1: 1397 2: 1395
3: 1397 4: 1405 5: 1397 6: 1394 7: 1397 8: 1396 9: 1400 10: 1397 11: 1397
12: 1397 13: 1397 14: 1397 15: 1397 16: 1397
Vulnerabilities: Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: spec_store_bypass
mitigation: Speculative Store Bypass disabled via prctl and seccomp
Type: spectre_v1
mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Full AMD retpoline, IBPB: conditional,
IBRS_FW, STIBP: conditional, RSB filling
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Renoir driver: amdgpu v: kernel
Display: x11 server: X.Org 1.20.4 driver: amdgpu
resolution: 1920x1080~60Hz
OpenGL: renderer: llvmpipe (LLVM 7.0 128 bits) v: 3.3 Mesa 18.3.6
Audio:
Device-1: AMD driver: snd_hda_intel
Device-2: AMD Raven/Raven2/FireFlight/Renoir Audio Processor driver: N/A
Device-3: AMD Family 17h HD Audio driver: snd_hda_intel
Sound Server: ALSA v: k5.9.0-0.bpo.2-amd64
Network:
Device-1: Realtek driver: rtw_8822ce
IF: wlan0 state: up mac: <filter>
Drives:
Local Storage: total: 536.56 GiB used: 11.91 GiB (2.2%)
ID-1: /dev/nvme0n1 vendor: Western Digital
model: PC SN730 SDBPNTY-512G-1027 size: 476.94 GiB block size:
physical: 512 B logical: 512 B
ID-2: /dev/sda type: USB vendor: Lexar model: USB Flash Drive
size: 59.62 GiB block size: physical: 512 B logical: 512 B
Partition:
ID-1: / raw size: N/A size: 7.54 GiB used: 152.2 MiB (2.0%) fs: overlay
source: ERR-102
Sensors:
Missing: Required tool sensors not installed. Check --recommends
Info:
Processes: 322 Uptime: 2m Memory: 15.08 GiB used: 924.3 MiB (6.0%)
Shell: bash inxi: 3.0.32
I don’t see anything odd about the hardware. How did you manage to get it to boot? Is there a Bios update for this laptop? Not sure what you have on this laptop but if you got it booted on PopOS it might be worth trying to get whatever files off you want saved.
for the first time ever, no idea how it seemed it saved the setting of secure boot disabled (tpm as well but that was never an issue).
now every time I boot I get this
perhaps if I could restore the original EOS boot image now it would work without secure boot?
I managed to boot into EOS live ISO (newest version). will immediately pull out all files I need. besides this, anything I can try to make it work without doing a fresh install?
EDIT: if I navigate into /boot/efi Is completely empty
Since it seemed from your efibootmgr that you don’t have an efi boot entry for enos, I would at least try reinstalling the bootloader from the live iso.
You would need to look at the following for how to chroot:
and how to reinstall the bootloader: