I haven’t used my computer in a while, i powered it back on, and now it’s stuck in grub rescue, i gave the computer to a friend a while back so he might’ve played with something he shouldn’t, i have 2 drives, one is an ssd, the other is an hdd, i tried ls, and looked through all the partitions, my root partition is (hd1,gpt2), i tried “set prefix=(hd1,gpt2)/boot/grub” then “set root=(hd1,gpt2)” and did “insmod normal” and it said:
“file name ‘/boot/grub/i386-pc/normal.mod’ not found.”
So normally i looked through /boot/grub, all i found was “grubenv grub.cfg.pacsave”, what do i do now?
Without more information, there’s no way to know. Especially since my crystal ball has been acting up.
But, just for in case, that command should be run from a chroot environment, which requires a Live USB, so if you don’t have a Live USB and aren’t in a chroot environment, chances are more than good it won’t work. Excellent in fact. Guaranteed I think.
For in case you were unaware:
How to chroot
Ensure you’ve got a relatively new ISO or at least one with a still supported LTS kernel.
Write/copy/dd the ISO to a USB thumb drive.
When done, boot with the above mentioned USB thumb drive into the live environment.
Once booted, open a terminal and enter the following command to enter the chroot encironment:
manjaro-chroot -a
If you have more than one Linux installation, select the correct one to use from the list provided.
When done, you should now be in the chroot environment.
But, be careful, as you’re now in an actualroot environment on your computer, so any changes you make will persist after a restart.
I did “pacman -Su grub” waited for it to complete, then did update-grub, the command ran, then i rebooted, still shows grub rescue and still says “error: file ‘/boot/grub/i386-pc/normal.mod’ not found”
I already had a live usb, i booted from it chroot’d into my linux install with manjaro-chroot -a and did as the post you linked me said to do, which is why i said update-grub didn’t work
You do know that it’d be easier to assist if we have more information? It’s true.
So please, provide more information, as requested by this:
Also, we need the output of:
fdisk -l
lsblk -f
…from a chroot environment.
So run the commands, and post the outputs according to:
Tip:
When posting terminal output, copy the output and paste it here, wrapped in three (3) backticks, before AND after the pasted text. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Sed
sollicitudin dolor
eget nisl elit id
condimentum
arcu erat varius
cursus sem quis eros.
Instead of like this:
Sed sollicitudin dolor eget nisl elit id condimentum arcu erat varius cursus sem quis eros.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby increasing legibility thus making it easier for those trying to provide assistance.
For more information, please see:
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
From the chroot encironment, please provide the output of:
cat /etc/default/grub
You mentioned that your friend could have changed stuff on your PC. Well, it looks to me as if the drives had either been changed, formatted or disconnected and reconnected differently. In all cases I’d suggest you use a live environment to backup your stuff and rather reinstall your Manjaro. (And Windows too, since you’ve got that as well. Or so it seems.)
GRUB_DEFAULT=saved
GRUB_DISTRIBUTOR="Manjaro"
GRUB_CMDLINE_LINUX_DEFAULT="quiet apparmor=1 security=apparmor resume=UUID=11e0da9a-9c9c-4711-8847-bc08ac54f8c9 udev.log_priority=3g splash vt.global_cursor_default=0"
GRUB_CMDLINE_LINUX=""
# If you want to enable the save default function, uncomment the following
# line, and set GRUB_DEFAULT to saved.
GRUB_SAVEDEFAULT=true
# Uncomment to disable submenus in boot menu
#GRUB_DISABLE_SUBMENU=y
# Preload both GPT and MBR modules so that they are not missed
GRUB_PRELOAD_MODULES="part_gpt part_msdos"
# Uncomment to enable booting from LUKS encrypted devices
#GRUB_ENABLE_CRYPTODISK=y
# Uncomment to use basic console
#GRUB_TERMINAL_INPUT=console
# Uncomment to disable graphical terminal
#GRUB_TERMINAL_OUTPUT=console
# The resolution used on graphical terminal
# note that you can use only modes which your graphic card supports via VBE
# you can see them in real GRUB with the command 'videoinfo'
GRUB_GFXMODE=auto
# Uncomment to allow the kernel use the same resolution used by grub
GRUB_GFXPAYLOAD_LINUX=keep
# Uncomment if you want GRUB to pass to the Linux kernel the old parameter
# format "root=/dev/xxx" instead of "root=/dev/disk/by-uuid/xxx"
#GRUB_DISABLE_LINUX_UUID=true
# Uncomment to disable generation of recovery mode menu entries
GRUB_DISABLE_RECOVERY=true
# Uncomment this option to enable os-prober execution in the grub-mkconfig command
GRUB_DISABLE_OS_PROBER=false
# Uncomment and set to the desired menu colors. Used by normal and wallpaper
# modes only. Entries specified as foreground/background.
GRUB_COLOR_NORMAL="light-gray/black"
GRUB_COLOR_HIGHLIGHT="green/black"
# Uncomment one of them for the gfx desired, a image background or a gfxtheme
#GRUB_BACKGROUND="/usr/share/grub/background.png"
# Uncomment to get a beep at GRUB start
#GRUB_INIT_TUNE="480 440 1"
# Uncomment to ensure that the root filesystem is mounted read-only so that
# systemd-fsck can run the check automatically. We use 'fsck' by default, which
# needs 'rw' as boot parameter, to avoid delay in boot-time. 'fsck' needs to be
# removed from 'mkinitcpio.conf' to make 'systemd-fsck' work.
# See also Arch-Wiki: https://wiki.archlinux.org/index.php/Fsck#Boot_time_checking
#GRUB_ROOT_FS_RO=true
GRUB_TIMEOUT_STYLE="menu"
GRUB_TIMEOUT="10"
GRUB_THEME="/usr/share/grub/themes/Shodan/theme.txt"
OK, looks like the machine was hybernated at some stage. Or possibly suspended.
Run this to remove the RESUME= part:
sed -i 's/resume=UUID=11e0da9a-9c9c-4711-8847-bc08ac54f8c9//g' /etc/default/grub
Note:
I don’t know if this will work or break something. I really don’t know what’ll happen. But it might work, or you’ll be right where you started. So. not worse off.
Tip: 
and rather reinstall your Manjaro. (And Windows too, since you’ve got that as well. Or so it seems.)