Hi there, i’ve installed EOS a while ago and stumbled upon the same issue, i cant SUDO or PACMAN -S Because password is locking me out, i’ve verified that the password i used was correct and no the fact that it’s hidden shouldnt be what’s causing it because i’m sure i typed it right, what are my options ?
Machine Log info, idk if that helps
https://0x0.st/84aJ.txt
Typically that will often mean you have a PAM lockout from entering the password wrong more than 3 times in a short period.
Other causes, perhaps are that you’re not listed in the sudoers file.
Welcome to the forum 
Well if the password gets not accepted three times it will lock you out for a while.
Rebooting usually solves that problem.
Guess you already checked by typing the password in a text editor or something like that to make it visible.
If nothing works you might try the following arch wiki
I’m pretty new, how do i get into the kernel parameters ? during boot ?
in terminal, give us the output of
wheel
generated from AI:
Your user isn’t in the wheel group, so sudo just silently refuses access.
Let’s fix that by booting into a live ISO and adding your user to the wheel group using a chroot. Here’s a full step-by-step guide:
Fix: Add Your User to the wheel Group via Chroot
1. Boot into EndeavourOS Live USB
Use the same ISO you installed from.
Boot into the live environment (select “EndeavourOS Live” in the menu).
2. Identify Your Root Partition
Open a terminal in the live session and run:
lsblk
Look for your Linux root partition — usually labeled something like sda2, nvme0n1p2, etc. It should be the largest partition and have a mount point listed as / (if already mounted) or just no mount if not.
Let’s assume it’s /dev/sda2 for this guide — replace with your actual one!
3. Mount the System and Chroot Into It
sudo mount /dev/sdXn /mnt # replace sdXn with your root partition
sudo mount --bind /dev /mnt/dev
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys
sudo chroot /mnt
Now you’re “inside” your installed system.
4. Add Your User to the wheel Group
Run this inside the chroot:
usermod -aG wheel yourusername
Replace yourusername with your actual username.
5. Exit and Reboot
exit
sudo umount -R /mnt
reboot
Remove the USB when prompted and boot into your system as normal.
Final Step: Test It
Once back in your system, open a terminal and try:
sudo echo success
You should be prompted for your password, and it should work now!
Why is that? How did you come to this conclusion?
This is not the appropriate command to check if a user belongs to wheel group or not.
If you want to check that you can do it with:
id
I’m afraid, you jumped into a conclusion too soon. There is a probability that you may be right but judging from the “evidence” presented so far, we cannot draw the conclusion that OP’s user doesn’t belong to wheel group.
Umm 3rd, maybe you should stop helping us now. If you don’t actually know how to do things yourself, you shouldn’t post advise.
I seriously doubt that he’s not in the sudo group (but it is possible), we should verify that before issuing potentially suspect AI logic. There are easier ways (arch-chroot) than the somewhat convoluted but more generic method presented here.
Ok, here’s two things…first lets find out if you’re in the wheel group.
‘grep userid /etc/group’ (replace userid with your username)
If that is the case, then you’re probably just locked out as I mentioned above. Just wait 10 or 15 minutes and try again. If you keep trying you’ll keep extending the lock.
Regarding different instructions, both are valid, there’s usually at least 20 ways to cook a cat in LinuxLand.
The command groups is often used to print the groups the user is in.
alright fine . i’ll just observe
uid=1000(MyName) gid=1001(MyName) groupes=1001MyName),3(sys),981(rfkill),998(wheel),1000(autologin)
So i’m in wheel but can’t access the command because i’m not in sudoers list ?
@Raosty Please stop with the AI stuff.
If you have the default install of sudo (came with the install), wheel is allowed to use sudo.
Click on the “kernel parameters”!
Bit harsh on the newbie eh ?
I was warned arch forums can be a bit brutal lol.
Guess it’s true.
Believe me, you haven’t seen anything yet. If you want to be blistered, go post on the official Arch forums, and ask about something in EndeavourOS 
Or better yet, ask about something and then sign with ‘Btw, I use EndeavourOS’.
Assuming root and using
faillock --user USERNAME --reset
replacing with the correct username, will also reset the lock ..
That is after su or similar.
Correct, but you can also just wait (which is often simpler if no easy way to root).
initrd=\08e5967edca8491bb0f837970dd9d2b7\6.14.4-arch1-2\initrd nvme_load=YES nowatchdog rw root=UUID=c2349522-ceb6-4f0d-93d3-c59f64fc52c0 systemd.debug_shell nvidia_drm.modeset=1 systemd.machine_id=08e5967edca8491bb0f837970dd9d2b7
I’ve managed to add the systemddebug_shell to the kernel parameters but cant access said shell, i must have done smth wrong