The laptop takes a very long time to take the battery out of, or perform any hardware operations on for that matter. How could I achieve the same affect with a debian live usb?
This doesn’t make sense that you can boot on a Debian live usb but not an the EOS live usb? How did you install it?
install what?
Oh it’s a newer laptop with an internal battery. Okay i get that.
How did you install EOS?
from a live usb, I think I ran rm -r on the root partition or something - I’m looking for a more graceful command
edit: I actually changed the boot order in uefi, which I no longer have access to
I’ve been here since the beginning. EOS installs and runs flawlessly on every desktop. I have no idea what you have done to mess up your system but it has nothing to do with EndeavourOS! That much i know.
this statement is contrasted by debian live usb booting and endeavouros liveusb not booting
If you can boot on a live usb debian then create another live usb of eos. Maybe something is wrong with it.
I tried dding the Endeavouros iso to my usb 3 times, that’s not it
I just managed to get into the bios/uefi screen, but it freezes whenever I try to use the same bios/uefi screen entry process with the endeavouros usb plugged in. Any suggestions?
I think i would boot off the debian and use efibootmgr and clear all of the entries that are loaded.
Edit: There is a command for that but i don’r know what it is. You can use efibbotmgr commands to do it.
Edit2: The idea is to clear the firmware of all entries.
Okay, if you could list a few of the commands that I’ll need with efibootmgr when doing that, the solution to this thread might be near.
What does it show
efibootmgr
Edit: Commands are on this page will help you to remove the entries.
hello, I think I might be able to recover that system, what should I do to recover the static libraries mentioned in the original post?
Also, I’ve tried changing boot order with efibootmgr but it had no effect during the boot process, even though efibootmgr showed it as changed.
This is an encrypted installation?
I’ve gotten to a point where I’ve already gotten to an irreversible point in the reinstallation process.
- The
efibootmgr -o bootOrder
command did eventually work - I’ll keep this open in case anyone comes up with a solution to the original question (how can I recover the system as it’s described)
You didn’t answer the question. Is it an encrypted install?
No, it was not an encrypted install.
Are you still not able to arch-chroot?
Edit: If it were me i would try another Arch based live ISO and see if you can boot from it. Then arch-chroot and try updating or reinstalling that file.