If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

I did some more exploring. I didn't notice previously that both Add Boot Option and Path for Boot Option are required. With Add Boot Option you can enter anything however with Path for Boot Option you must navigate to a .efi file. I tried EFI\kali\grubx64.efi for Add Boot Option but can find no grubx64.efi file in navigating through all the choices with Path for Boot Option. The files I could find were bootx64.efi, bootmgfw.efi, memtest.efi and bootmgr.efi. The only Path option I have tried thus far is bootx64.efi and when I do that and hit Create the boot order is populated with EFI\kali\grux64.efi (PO: WDC WD5000LPVX-80V0TT0)....and it boots to Windows.

I booted to Kali live, mount command was ok but nautilus /mnt/EFI resulted in "unable to get contents of the bookmarks file: error opening file /root/.gti.bookmarks: no such file or directory exists" a window popped up showing the three folders visible in CMOS>add new boot option: ASUS BOOT MICROSOFT no Kali folder and no Kali folder beneath any of those three folders (and no grubx64.efi file). I tried running the grub install again but again saw the "mount point doesn't exist" error upon mount --bind /dev /mnt/dev despite upon running mount /dev/sda1 /mnt again the output is "mount point already exists".

When it reports mount point does not exist, create a mount point using mkdir /mnt/dev before executing that command. Try it again. You have to install grub. Show the screenshot of terminal when you run those commands.

did mkdir had to do mkdir for both mnt/boot and mnt/boot/efi. chroot would not work - as you'll see I screwed up and did a chroot /root first then chroot /mnt saw "failed to run command 'bin/bash' : no such file or directory. All previous commands had run without errors. I tried the next command out of curiosity. First tried mkdir /run/lvm saw "file exists" then ran mount --bind /hostrun/lvm /run/lvm saw "special device /hostrun/lvm does not exist". Tried mkdir /hostrun/lvm "no such file or directory" next tried mkdir /mnt/hostrun/lvm "file exists" and again ran mount --bind /hostrun/lvm /run/lvm but of course still saw "special device /hostrun/lvm does not exist. So....what did I screw up about the chroot command? and do I perform mkdir /hostrun then mkdir /hostrun/lvm and THEN the mount --bind /hostrun/lvm /run/lvm again?

Ran again no errors (besides file already exists) until chroot - which I did correctly (chroot /mnt) this time. Tried sudo chroot /mnt no joy (same error). I tried again to go further and again no joy specifically "special device /hostrun/lvm does not exist". Why won't chroot work? Also tried grub-install /dev/sda - should sda have a number after it or is /dev/sda correct? grub-install resulted in "command not found" something possibly of interest is the fdisk -l output yesterday had sdb.... whereas today it is sda....

When it says mount point does not exist you can create one using mkdir as i told you before. If it now says file exist it just means that the mount point already exists and you don't have to create one with mkdir. I think you have already learned this.

The error with chroot /mnt, i made an update to my original post. Run it again.

_defalt! Yes you are correct in that I understand that if the file/folder already exists it means "good! I don't have to create it!". I ran chroot /mnt/bin/bash as noted in your updated instructions - I took a new pic of them before booting up to Kali Live. I see a different error now "chroot: cannot change root directory to '/mnt/bin/bash': Not a directory" I tried "sudo chroot /mnt/bin/bash got the same error. I can confirm that yes I am booting 64-bit Kali image 2018.1 on my 64 bit machine. I got tired of the delay booting to CD-ROM so I created a 64 bit Kali USB stick per the instructions on the Kali site. I can now boot to Kali Live in under a minute. I did go on to the rest of the commands but got the same results as before.

_defalt? I saw you again changed the chroot instruction to chroot /mnt /usr/bin/bash so I tried again. This time the mount -o remount,rw command wouldn't work - the result was "mount: /mnt/boot/efi: mount or bad..." sorry I must be very tired as I didn't get the entire error in my screen cap and I can't remember if offhand AND I'm too tired to try this again, this evening. I double-triple-quadruple checked my syntax and it looked correct.

In the snip I was looking at I wasn't sure if there was a space between /mnt and /usr/bin/bash on the chroot command so I tried both. It looked more like there was a space so I tried it that way. There was an error either way "chroot: failed to run command 'usr/bin/bash': no such directory" with the space and "chroot: cannot change root directory to 'mnt/usr/bin/bash' no such directory" without the space.

i had installed kali with win 10 in dual boot. but i accidently deleted the kali partition and swap area. using UEFI mode I can successfully boot into win 10. but when I try to boot into BIOS mode to do fresh install of kali, it shows error like "no such partition, grub rescue". How to get rid of this?

i had installed kali with win 10 in dual boot. but i accidently deleted the kali partition and swap area. using UEFI mode I can successfully boot into win 10. but when I try to boot into BIOS mode to do fresh install of kali, it shows error like "no such partition, grub rescue". How to get rid of this?

Why are you booting into BIOS mode when kali can be installed in UEFI mode?