I couldn't find any info pertaining to this particular problem in the sticky threads, I was hoping if anyone could please help me out here. I am a complete and total noob when it comes to the Pi and this is my first time attempting to use it so bear with me here. I truly have no idea what i am doing wrong and I am getting a bit frustrated trying to understand it so any feedback is deeply appreciated.
I recently purchased the Raspberry Pi 3 Model B online. I do not have the Raspbian SD card that goes along with it, and I wanted to install Kali Linux as the OS anyways, so I bought a blank SD card and tried mounting the Kali Linux image onto it myself. I downloaded the Kali Linux image for the Pi 3 from this link (https://www.offensive-security.com/kali ... rm-images/
). I absolutely made sure this was the correct image file by verifying its SHA256sum, which is listed in the link above. I ran the following command in my terminal to verify the checksum on my image file:
shasum -a 256 kali-2017.01-rpi2.img.xz
The checksum was the exact same hash string as that one listed in the offensive-security download link, so I am 100% certain the image file is correct and not tampered with.
I used the dd utility to mount this image file onto my SD card using this guide (http://docs.kali.org/kali-on-arm/instal ... spberry-pi
). I firstly made sure I had the correct driver path for my SD card. I used the "sudo fdisk -l" command to see drive paths for devices (before and after plugging in my SD card). When I plugged my SD card in, i saw the following additional output come up:
Disk /dev/mmcblk0: 14.4 GiB, 15489564672 bytes, 30253056 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: dos
Disk identifier: 0x00000000
Device Boot Start End Sectors Size Id Type
/dev/mmcblk0p1 8192 30253055 30244864 14.4G c W95 FAT32 (LBA)
I took this to mean that the driver path for my SD card was /dev/mmcblk0.
So with this in mind, I opened up a new terminal window, went to the command directory of my image file, and executed the following command:
sudo dd if=kali-2017.01-rpi2.img.xz of=/dev/mmcblk0 bs=512k
I am almost absolutely certain this is the correct command and that it mounted the image file successfully onto my SD card because there were no error messages and I got the following (seemingly successful) output:
1715+1 records in
1715+1 records out
899350656 bytes (899 MB, 858 MiB) copied, 101.632 s, 8.8 MB/s
So, since it seemed to work, I then plugged the SD card into my Raspberry Pi, plugged in the charger, my HDMI cable (hooking it up to my monitor), and my USB mouse and keyboard.... and nothing happened.
The red light turns on when I charge the Raspberry Pi, so it absolutely works and can power on. It's just that absolutely nothing happens afterwards. I tried checking the HDMI output to make sure it was working, and it works fine. I have mounted image files for OS's onto USBs before completely without any issue. I truly cannot wrap my head around why this Pi won't boot or display anything on the screen and it is really worrying me because I put a decent wad of cash into this setup. The monitor isn't registering anything, it just says "no signal" even though the Pi is clearly turned on and charging. I heard that the Pi boots from the SD card drive by default so I don't understand why it isn't booting the OS.
If anyone could please offer me tips on what I should try instead please let me know.