I'm using Win 7 x64 and can't use Kali Linux Live USB Install tutorial because Win32 Disk Imager doesn't work.
But with Universal USB Installer everything works great, so maybe it's time to update article?
Printable View
I'm using Win 7 x64 and can't use Kali Linux Live USB Install tutorial because Win32 Disk Imager doesn't work.
But with Universal USB Installer everything works great, so maybe it's time to update article?
I agree Universal USB Insaller worked perfect fo windows... Does a Kail Team member own Win32 Disk Imager? If not, i dont see why you guys dont remove it from the article. Ive been at it since Chriistmas eve trying to beat that black screen with a blinking cursor issue on a dual boot with Windows 8.1 .
(Added Keywords hoping to help people who ewere in my situation.
Happy Holidays guys
I need some help installing kali using the dd command, I only have machines running linux so I can't create a the bootable usb on windows,
so far i tried
dd if = /home/myusername/Desktop/kali.iso of = /dev/sdb bs = 512k,
command above is not working since that's not the path of my usb drive, I need help finding the path. I tried using dmesg | grep -i usb but i get too many stuff and I don't seeem to find the path of the usb,
please help thanks.
I'm planning to install kali on an external drive wich has 2 partitions. The first one is all my important data. The second partition i created is a 30GB FAT partition.
diskutil list prompts the following:
/dev/disk2
#: TYPE NAME SIZE IDENTIFIER
0: GUID_partition_scheme *500GB disk2
1: EFI EFI 209MB disk2s1
2: Apple_HFS myDisk 464GB disk2s2
3: Microsoft Basic Data KALI 35GB disk2s3
Can I use the IDENTIFIER with the dd command ? I tried the IDENTIFIER with the diskutil unmountdisk but it unmounted both partitions( myDisk,KALI).
help :(
try the "diskutil list" command. It wil prompt all the disks mounted. Your usb should be something like /dev/disk2 or 3 or whatever.
Hi, Brian --
The best way to identify the path for the USB drive you want to target is to perform the command
fdisk -l
without the USB drive inserted, and then again with it inserted. You'll see which device is now there and wasn't previously. Note that this command shows you the path to the partitions, which look like "/dev/sda1", "/dev/sdb2", or (on my Kali system) "/dev/mmcblk0p1" and "/dev/mmcblk0p2".
The device path, which is what you want here, is the part that all the partitions have in common: "/dev/sdb" in the first case and "/dev/mmcblk0" in the second. So when I flash a USB drive on my Kali system, the command is something like
dd if=/path/to/my/Kali.iso of=/dev/mmcblk0 bs=512k
I exactly followed the official guide, created usb, installed refind, refind detects usb however when i press enter in refind i get black screen with the text, : no bootable device -- insert boot device press any key... help
Hey guys,
I'm new to the forums and I am trying to get the Kali Linux Live to USB setup. I have followed the directions and downloaded the 64bit ISO and verified the sha1 hash. All looks good. I used Win32 Disk Imager to create an image on a USB stick. I booted from the stick and went with Graphical Install but I get the "Error Reading Release File" and unable to mount CD-ROM.
I tried Universal-USB-Installer and UNetbootin, all of which result in the same error.
Anyway to resolve this issue?
Thanks.
Sadly this version of Kali Linux seems to be pretty broken.
What I have tried so far is to write it to a 16Gb memory stick from an Arch Linux installation using dd, dcfldd (Forensic accurate version of dd)
These attempts all had the same outcome, the computer stopped at boot with a blinking cursor after selecting boot from USB (HP EliteBook 8540p)
Taking it into Windows, the first attempt at writing it from Win32USB, same result as I achieved in Linux with dd, stuck at blinking cursor.
However, if we change up and use "Universal USB installer" version 1.5.9.4, the ISO will boot, but it will never start X server and as such you are left at the command line.
From there I tried reviving it, but no dice as I have no idea how it is meant to be set up.
Trying the latest Universal USB Installer, everything goes to pot, and it halts the system during the loading of the Linux kernel, claiming the XZ compression is corrupt.
This leads me to believe something is seriously wrong with this release of Kali Linux.
Why should one follow the procedure for "USB persistence" rather than install Kali to USB as if it is a hard drive? Is it not better to treat it as a HD so that the persistence container doesn't keep growing forever?