Starting at root@(none):
I got
sudo: unable to resolve host(none): Connection Refused
already exists
I got
sudo: unable to resolve host(none): Connection refused
btw sda3 is what partition? Home, boot...?

root partition is sda1? so what's sda3?

Please read post 13 again. I pointed out there that this is only an example and that you must use the correct partition device names for your system, not the ones used in the example. You need to find out those names and that is what you are going to use fdisk for.

Run fdisk -l and write down the correct partition numbers for the root partition and the efi system partition. The device names will be /dev/sdan where n is the partition number. So if the efi system partition is 1 and your root partition is 2, the device /dev/sda2 must be mounted somewhere on your rescue system (say on /mnt) and /dev/sda1 would then go on /mnt/boot/efi.

Again, these are examples only. You should be able to understand this.

If you are using the Kali DVD to run these commands, stop using sudo. By default when you log in to Kali you already are root. That is the default by design because of it's purpose. To give us a better idea of what you have, when you fun the: fdisk -l (Lower Case Letter L) how about posting the actual output here?

From your earlier posts, the problems you are having are because you have a windows UEFI install with a Legacy/CSM install of Kali. If for some reason, you don't or can't install Kali UEFI, the best you can hope for is to be able to switch to CSM/Legacy in the BIOS to boot Kali and to UEFI to boot windows.

You asked earlier about deleting Grub from the MBR. The page below explains that. Make sure you scroll down the page to the section: Option #2: Command to delete mbr only so you don't delete your partition table. You should be able to boot windows without making this change by setting the BIOS to boot UEFI. You'll need to have someone more familiar with UEFI confirm this.

https://www.cyberciti.biz/faq/linux-...rd-dd-command/

If you get this straightened out and still want to learn computer forensics, I would suggest you install Kali to a flash drive. Detailed instructions on there site and should eliminate a lot of these problems.

It is possible to convert a legacy mbr system to boot with uefi instead. I remember reading a HOWTO on doing this immediately after installation by remounting the hard drive on the installation image, mounting the efi system partition on it, and then installing GRUB in its proper location on the esp. Unfortunately I haven't been able to find that item again.

The existing GRUB stub in the mbr can be left in place. It doesn't do any harm because a UEFI running in native mode ignores the mbr.

I've read a lot of warnings against mixing UEFI native and legacy booting on a permanent basis. Sooner or later you're going to use the wrong method with bad results.

I have an UEFI computer

Your right, I've changed my mind about deleting the GRUB stub in MBR.

You mean like computers that run windows on uefi and linux on legacy on the same computer long term?

Correct

There's no mention in the article on how to delete just the small portion of grub that's sitting in the mbr. But thank you anyway. I've decided to leave it as is.

My windows is booting fine in UEFI

Yes, but when you installed Kali, you told the UEFI to behave like a BIOS. That's what "legacy mode" actually means.
Yes. It's not recommended.

I have a separate partition just for boot, should I still go ahead like you said above?

If you have a boot partition, start by mounting it on the empty /boot directory of your root partition. Then create /boot/efi in it. Then mount the esp on /boot/efi.

Could I get the code please?

Do I need to be online to do that?

Start by reading the man page for mount (man mount). See if you can work out the arguments you need to give it. It'll be good training for you. You really can't use Linux, especially a distro like Kali, if you expect to be spoon-fed all the time. I'll give you a clue: you need to tell mount what partition you want to mount, what kind of filesystem it's using, and where you want to mount it, in that order.

No. You only need to be online to use the Internet.

Yes there is. It is under Option #2: Command to delete MBR only (the last part highlighted in red) but as pointed out above, if you have UEFI set up it ignores the MBR so it's not a problem. I think it would be a good idea to post the actual output of commands like fdisk -l or gdisk -l and also what exactly you have on your separate boot partition. What's in the EFI partition would also be useful information.

I think your right.

Your saying Grub is that 446 bytes of MBR?
If Grub occupies that 446 bytes of the primary portion in MBR then what was occupying that 446 bytes of space prior to Grub's arrival?

I use fdisk -l for this?

No, you mount the efi partition on /boot/efi as I have described, and then use the ordinary Linux file management tools to find out what is in that directory. The whole point of uefi booting is that all boot code is in normal files that can be inspected from out of any operating system, and not in special "magical spaces" like the mbr.

You need some very basic education. Try reading this.

Nothing. From the information you posted, your windows was UEFI which does not use the MBR.