I've tried a few times and no matter what option I select I can't get KALI running. I've tried a few USB sticks, and an SD card, but no matter what I do, I always get the same message.
"the CD-ROM does not seem to contain a valid 'Release'..."
I installed Backtrack5 with no issue, but nothing I do seems to get KALI running..
Is this a known issue with the install? Google comes at me with a few others asking for help on the issue, but nothing seems to get me through..
I find it very funny BTW that the method proposed in several posts, leads to a windows app..Irony seems to be lost on posters. Ha.
Used dd command on Ubuntu 12.04 LTS. Appeared to work with sudo. On some machines the USB will not begin boot, on another it says isolinux.bin missing. Its a 16 gig usb. Have used Linux for seven or more years with dozens of distro installs from CD to USB. Never had these issues with unetbootin. Since I am following directions I am unsure what the problem is. Any help?
thanks a lot broh..
hey,
i downloaded the 64 bit *.iso from http://www.kali.org/downloads/ first with Google Chrome and then with Internet Explorer. I tried several USB-Sticks and a lot of tools for creating a bootable USB-Stick (unetbootin, rufus, universal-USB-Installer, LinuxLive USB Creator, dd and of course the win32diskImager) and it won't work.
When I start my pc I can select the USB-Stick in the boot-menu but the stick doesn't boot. Instead of booting the linux live system, Windows starts. If I deactivate booting from the HDD in the Bios, nothing happens. I tried it with two computers: a 5 year old pc (Windows 7) and my new laptop of the samsung series 9 (Windows 8).
The *.iso is not damaged I think, 'cause it works in VirtualBox...
So can anyone of you help me or has an idea how to get it work?
Hope for anwers!
Kali Linux USB Installation using LinuxLive USB Creator
Howto Install HDD Kali on a USB Key
Clean your laptop fan | basic knowledge
thanks a lot!![]()
Question: Downloaded the mini iso to create a live-USB but when the stick boots, it only gives me the options to install, and not to run as live. Kali 1.05 64 bit mini iso downloaded. Thanks folks.
for some reason my computer wont boot past "verifying dmi data pool" on a usb stick. I'v tried different tools for creating the the live usb; rusuf, uui, lili, even the win32 image creator recommended in the tutorial (this one corrupted my usb stick). iv successfully booted different versions of linux on my system already both from usb stick and dvd's but kali just doesnt seem to load past that screen. iv tried booting it on my computer at work which is intel based and i use the amd64 iso and it worked perfectly.
any advice/help is greatfully appreciated.
system: amd mobo dual core 2.3ghz, 4g ram and nvidia graphx card currently running win8 and BT5.
Hello, i am having the exact same problem, same bios as well. Tried both 64 and 32 bit, multiple downloads of each, checked the downloads were not corrupt, followed the instructions on kali.org all to no avail. I have wiped the hard drive with parted magic, still nothing.
Thanks
Try LiLi USB creator, worked perfectly for me. Its Linux Live USB Creator.
Hello all i am a noob when it comes to kali this is my first time doing live usb option i got it all running ok and i got persistence done correctly.I just have a 2 quick questions, since i have USB persistence does that mean when i update that it will stick and not dissapear soon as i reboot.the reason i ask is because the persistence folders contents never change after i update but when i reboot and log back on and try to upgrade software it says that its all up to date and thats after i downloaded the 340MB update. if anyone could please help me i would appreciate it.Question #2 how do i install programs like firefox and make them actually stay and load when i use persistence?
Hi everyone.
For those of you who have tried everything under the sun to get Kali to boot from a USB (Live or otherwise), I feel your pain. Here's what I discovered...hopefully it will help someone avoid the anguish.
If your BIOS has UEFI enabled, you're screwed unless you can enable "Legacy" support and disable "Secure Boot". But EVEN THEN, you may be screwed. You can try some of the UEFI fixes out there (as I have done) but none of them have worked, at least for me. No matter what I try, the USB stick is simply ignored during the boot process and Windows happily rears its ugly login screen. My particular BIOS (American Megatrends) just flat hates booting from a USB, no matter what combination of changes I make.
As to the USB itself, I tried:
LiLi, unetbootin, Universal-USB-installer, Win32 Disk Imager (ad nauseam)
I am running Windows 8 (unfortunately) on a new machine (i7 4700 Haswell blah) and while the laptop is a screamer, Windows 8 and my BIOS just ignore UEFI settings.
Until (and ONLY until) Kali distro is built to address the UEFI issue, I'm afraid we are left running Kali in a VBox (or similar)...which actually works great, but totally not portable.
Anyway, best of luck to everyone.
I have followed the directions to make a live cd with persistence and they work flawlessly! but i would like to mix it up a little.... I have a 64gb usb disk that i would like to create 3 partitions on....
1) Kali Live (≈3gb)
2) persistence (≈27gb)
3) fat32 storage drive (≈27gb)
Heres my problem. If I create the fat32 partition with gparted when I create the persistence partition it works for mac or linux but if i try to use the usb disc on a windows machine the fat32 partition "needs to be formatted". If I do that it wipes out the first partition (Kali Live). I could get this to work by doing a full install to the usb but I find a live disk runs faster even with persistence and if I ever screw something up I can just delete the files from the persistence partition and stat again.
if anyone knows how I can accomplish this I would love some help!
Hi everyone,
I am having trouble with installing Kali from a live usb. I can boot the live flawlessly, however every time I try to install the system, the installation fails. I've tried downloading again, and many different tools (lili usb creator, universal usb install, unetbootin), but the result is the same. I paste the last few lines of the syslog. If anyone could help me, I would really appreciate it.
Oct 20 16:23:01 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 16:23:01 main-menu[4805]: INFO: Menu item 'user-setup-udeb' selected
Oct 20 16:23:08 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 16:23:09 main-menu[4805]: INFO: Menu item 'clock-setup' selected
Oct 20 14:23:05 clock-setup: Sun Oct 20 14:23:05 UTC 2013
Oct 20 14:23:05 clock-setup: rdate: adjust local clock by -7203.368444 seconds
Oct 20 14:23:06 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 14:23:06 main-menu[4805]: INFO: Menu item 'disk-detect' selected
Oct 20 14:23:06 anna-install: Installing mmc-modules
Oct 20 14:23:06 mtp-probe: checking bus 1, device 4: "/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5"
Oct 20 14:23:06 mtp-probe: checking bus 2, device 3: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.3"
Oct 20 14:23:06 mtp-probe: checking bus 2, device 4: "/sys/devices/pci0000:00/0000:00:1d.0/usb2/2-1/2-1.8"
Oct 20 14:23:06 mtp-probe: bus: 2, device: 3 was not an MTP device
Oct 20 14:23:06 mtp-probe: bus: 2, device: 4 was not an MTP device
Oct 20 14:23:06 mtp-probe: bus: 1, device: 4 was not an MTP device
Oct 20 14:23:06 hw-detect: Missing modules 'eth1394 (FireWire ethernet)
Oct 20 14:23:07 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Oct 20 14:23:07 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
Oct 20 14:23:07 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing
Oct 20 14:23:08 check-missing-firmware: /dev/.udev/firmware-missing does not exist, skipping
Oct 20 14:23:08 check-missing-firmware: /run/udev/firmware-missing does not exist, skipping
Oct 20 14:23:08 check-missing-firmware: no missing firmware in /dev/.udev/firmware-missing /run/udev/firmware-missing
Oct 20 14:23:08 main-menu[4805]: (process:8917): modprobe: invalid option -- 'l'
Oct 20 14:23:08 main-menu[4805]: (process:8917): modprobe: invalid option -- 'l'
Oct 20 14:23:09 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 14:23:09 main-menu[4805]: INFO: Menu item 'partman-base' selected
Oct 20 14:23:09 anna-install: Installing partman-auto-lvm
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (cdebconf-udeb): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (di-utils): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (kernel-image-3.7-trunk-amd64-di): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (core-modules-3.7-trunk-amd64-di): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (libdebian-installer4-udeb): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (archdetect): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: resolver (hw-detect): package doesn't exist (ignored)
Oct 20 14:23:09 anna[9594]: DEBUG: retrieving partman-auto-lvm 47
Oct 20 14:23:09 anna[9594]: DEBUG: retrieving partman-lvm 82
Oct 20 14:23:10 anna[9594]: DEBUG: retrieving lvm2-udeb 2.02.95-7
Oct 20 14:23:10 anna-install: Installing partman-auto-crypto
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (cdebconf-udeb): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (di-utils): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (kernel-image-3.7-trunk-amd64-di): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (core-modules-3.7-trunk-amd64-di): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (fat-modules): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (libdebian-installer4-udeb): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (archdetect): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: resolver (hw-detect): package doesn't exist (ignored)
Oct 20 14:23:10 anna[9694]: DEBUG: retrieving partman-auto-crypto 19
Oct 20 14:23:10 anna[9694]: DEBUG: retrieving partman-crypto 57
Oct 20 14:23:11 kernel: [ 396.557198] btrfs: Unknown symbol zlib_deflateInit2 (err 0)
Oct 20 14:23:11 kernel: [ 396.596819] JFS: nTxBlock = 8192, nTxLock = 65536
Oct 20 14:23:12 md-devices: mdadm: No arrays found in config file or automatically
Oct 20 14:23:12 partman: No matching physical volumes found
Oct 20 14:23:12 partman: Reading all physical volumes. This may take a while...
Oct 20 14:23:12 partman: No volume groups found
Oct 20 14:23:12 partman-lvm: No volume groups found
Oct 20 14:23:39 partman: mke2fs 1.42.5 (29-Jul-2012)
Oct 20 14:23:41 apt-install: Queueing package e2fsprogs for later installation
Oct 20 14:23:41 main-menu[4805]: (process:9580): WARNING: could not open /lib/modules/3.7-trunk-amd64/modules.builtin: No such file or directory
Oct 20 14:23:41 main-menu[4805]: (process:9580): /bin/perform_recipe: line 38: reuse_partitions: not found
Oct 20 14:23:41 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 14:23:41 main-menu[4805]: INFO: Menu item 'live-installer' selected
Oct 20 14:23:41 base-installer: info: Using squashfs support for /cdrom/live/filesystem.squashfs
Oct 20 14:23:41 anna-install: Installing squashfs-modules
Oct 20 14:23:41 anna[12696]: DEBUG: resolver (kernel-image-3.7-trunk-amd64-di): package doesn't exist (ignored)
Oct 20 14:23:41 anna[12696]: DEBUG: retrieving squashfs-modules-3.7-trunk-amd64-di 3.7.2-0+kali8
Oct 20 14:28:02 kernel: [ 687.152850] SQUASHFS error: Unable to read data cache entry [50f042ba]
....
Oct 20 14:28:02 kernel: [ 687.153161] SQUASHFS error: xz_dec_run error, data probably corrupt
...
Oct 20 14:28:02 kernel: [ 687.163082] SQUASHFS error: Unable to read data cache entry [50f042ba]
Oct 20 14:28:02 base-installer: error: The tar process copying the live system failed (only 201124 out of 290107 files have been copied, last file was ).
Oct 20 14:28:02 main-menu[4805]: (process:12641): tar: read error: Input/output error
Oct 20 14:28:02 main-menu[4805]: (process:12641): tar: short read
Oct 20 14:28:02 main-menu[4805]: WARNING **: Configuring 'live-installer' failed with error code 1
Oct 20 14:28:02 main-menu[4805]: WARNING **: Menu item 'live-installer' failed.
Oct 20 14:28:59 main-menu[4805]: INFO: Modifying debconf priority limit from 'high' to 'medium'
Oct 20 14:28:59 debconf: Setting debconf/priority to medium
Oct 20 14:28:59 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 14:29:07 main-menu[4805]: INFO: Menu item 'save-logs' selected
Oct 20 14:29:20 main-menu[4805]: DEBUG: resolver (libgcc1): package doesn't exist (ignored)
Oct 20 14:29:29 main-menu[4805]: INFO: Menu item 'di-utils-exit-installer' selected
I was successful in making live boot USB using Win 32 image burner,
but i am not able to utilize remaining 6 GB of my 8 GB pendrive,
it is giving following error. what should i do?
Error.JPG
i install kali linux 1.0.5 on my laptop with windows7 than when i restart isee black sreen with blinking underscore in anther mean i have than same problem
what the recovery disks you use
and how you fixed
Is there a way to add the persistent partition regardless of the name of the USB device?
E.G: adding the uuid to the script instead of /sdb?
Secondly:
Is it possible to modify the live.cfg in the isolinux folder so that I do not have to add "persistence" all the time?
I tried this by editing the kali image with ultraiso, but the CD wouldn boot afterwards. Same thing with the USB stick.
My overall goal would be a USB stick with a full kali that is capable of adding and keeping updates AND still works on every Computer plugged into.
I have a couple pretty noob questions I'm hoping someone can help me with...
1. What is the advantage of installing a "Live Kali" instead of just a regular Kali installation? What's the value of being "fresh" each time?
2. If I setup a persistence partition, and mount it according to the instructions, what is actually persisted in terms of OS settings and packages? I notice that there are over 100 updates in the system updates, so are these updates persisted if installed?
3. Why is the recommended partitioning 4GB FAT32, and rest EXT4? Why not just make it all EXT4? ...and why only 4GB? When I ran the system updates, it ran out of space on the /rootfs (which had been given 3GB).
I realize these are fundamental questions, so I appreciate the noob help in advance.
I'm trying to set up Kali from a Stay USB, but I've got FUT 14 Coins Xbox a issue. The USB Generate will start to a Stay edition absolutely, but when I try to set up from the Fifa 14 PC Coins USB, the set up program gripes that I don't have the difficult disk in the DVD produce. Well, of course I don't--it should come from the USB produce. And I can't get previous that level. Anyone having the same problem?
you can use LiLi Creator "Linux Live Creator".![]()
I am banging my head here.
I'm trying to install the 64 bit version. I've tried putting it on a USB stick from a macbook, a linux box and a windows machine. I've used different usb sticks, unique downloads of the iso and different installation tools. Installs to USB fine, fails on boot up with very similar messages along the lines of failed sector.
Can't see anyone complaining of the same problems. It's utterly bizarre. I don't expect anyone to fix this, just wanted to vent steam.
Just tried installing ubuntu on one of the sticks, boots up fine. I would say it's a fundamental problem with the ISO but clearly others would have it too. Very confused.
So I have a major issue. I downloaded kali 64 bit, put it on a flash drive using the guide you guys have and followed all of them to try and install it. I partitioned my drives and went to install the system but I just got an error about halfway through saying it cant install the system. so now the only way I can even use my pc at the moment is to launch Kali Linux live through my usb. So my question is, what do I do to get it to install correctly? I encrypted one of my drives during the first half of setting everything up so I don't know if I'm screwed now? Maybe I can get a friend to put everything on his usb and try to install it again?
Installing to a USB / removable media:
You may follow other directions to install to a DVD.
For USB / flash media devices, the scheme seems to go like this:
Download the ISO to somewhere.
dd the ISO to somewhere, maybe a USB / flash / removable media.
DO NOT try to update, upgrade or dist-upgrade the target (of=) of the dd.
Now boot to the USB / flash / removable media
Finally, select the Install to a different USB / flash / removable media with AT LEAST 12 GB of storage. You MUST have a network connection available for a long time; I do not yet understand why, but it will not reliable install unless it can see the Internet.
Choose your partitioning, etc. as your disks, USB, flash or other media permit.
I worked this for a couple of weeks to learn these conditions.
Please contribute when / as you are able.
weasel
Hey what's up. im having problems when booting it from my SanDisk Cruzer Micro usb stick. It does not boot, but my bios recognizes the USB.
My laptop is an HP and has Windows 8 installed. I disabled secure boot and legacy support.
Is there any incompatibility between HP and SanDisk USB's?
If not, why does it not boot? I burned it with Unetbootin and LiLi and any of them worked.
Thanks in advance^^
Which program did u use to burn the iso into a DVD? :3
Good evening muts,
I'm sorry, I've seen the hint to post problems with the live usb-installation here too late. So I do it now again - here.
I've installed Kali Linux 1.0.5 with unetbootin 5.85 and along with the named document "Kali Linux Live USB install". The article was quiet good and easy to work with it.
The installations worked both. That one with unetbootin and the official one.
My problem is, that no installation starts, allthough USB-Booting is allowed in the BIOS.
Is here anybody who has a good idea, what my mistake is?
TIA,
MGS
Hi Juan,
I took K3b. It works with gnome, too.
Regards,
MGS
Hi, I will try with that program, thanks ^^
Hello everyone, I finally booted Backtrack and Kali Linux from USB, but now I have a problem and its that both dont recognize my wireless card :S. I booted it on my notebook(small one) and works without problems.
My laptop is an HP Pavilon g6 Notebook PC and has Windows 8.
Anyone knows how to fix it?
Thanks in advance, Juan.
I was installing kali linux on my windows7 pc from usb.During installation,I did something wrong(during memory partition) and now my usb size is reduced from 3.76GB to2.35GB.Please,help on how to fix it.
I used dd if=kali.iso of=/dev/sdc bs=512k to create my usb thumb drive install of kali 1.05. It works well until I boot into windows 7 and try to add a file to the thumb drive. Windows 7 says the drive is unformatted and offers to format it for me. I used fdisk -l and the partition type is 17 a Hidden IFS (e.g., HPFS) partition. I then tried LiLi to create a bootable thumb drive and it writes out the file, everything boots fine, but it looks like the files and folders are a little different between the 2 different methods of writing the iso to the thumb drive.
1) Why can't windows write files to the drive when I use dd to write out the iso?
2) Why do the 2 methods (dd vs LiLi) create slightly different layouts?
I like the bleeding edge, but I don't like blood loss!
Does anyone know for sure that Kali Linux is bootable from a USB with the Series 3 Chromebook?
I've used this guide here from Kali's docs, using the 1.0.6 ARMHF Kali, but I'm running into this error: ERROR: cgpt add: GptSanityCheck() returned 2: GPT_ERROR_INVALID_HEADERS. This happens after trying cgpt add for KERN-A or KERN-B.
I have:
[LIST][*]Confirmed the location of the USB at /dev/sda[*]Quadruple checked commands entered[*]Checked SHA1 sum
Cgpt show /dev/sda throws back the same error.
Any ideas?
Put on usb kali 1.06 amd64. after reboot-windows 8.1 hangs, nothing works. 2 times pereustanavlival windows.
I'm in college majoring in Cybersecurity and very new to Linux. I started using Backtrack 5 R3 as dual boot with Windows 8 a few months ago to prepare for Linux security classes and now that Backtrack is no longer being maintained I want to remove it and install Kali. Is there a way to do this without wiping my entire HDD? If so any help in that direction would be greatly appreciated. Thanks!
What about a usb installation with persistence through a USB installer? such as Unetbootin Universal USB installer.
Will all the services work when you do everything in the tutorial. Because I did it and I cannot install nvidia drivers can someone help me. PM me please
Installing from a live CD directly to a USB pendrive worked flawlessly for me.
Used a USB 3.0, 16GB scandisk. Grub had issues with installing automatically. I had to specify the Master Boot Record to be set to (in my case) /dev/sdc.
For some technical reason Win32 is good to make Windows USB ISO's boot, but is no good to make Linux USB ISO's boot.
Download Unetbootin (extract if necessary & run - installing it is not necessary). I know for a fact that Unetbootin always works for creating Linux USB ISO boots on a windows system.
Another solution is to Install VMWare or Virtualbox and drop your downloaded Linux ISO into it & run.
Good Luck
I've tried to install KALI live usb
then I make a persistence mode and successfully,
but when i update repository and after the restart and only appear blank screen, even though I've been following the appropriate instructions here.
No one knows the solution?
Hi everyone. I've been trying to integrate Kali (as substitution to BT5) into the pretty old Katana multiboot "environment" (if it doesn't ring a bell, you can pertain it as simply multiboot pendrive using syslinux; you place each of your distros into separate folder and add apropriate boot menu section to .cfg file) using guidelines have been laid in this topic, generally with success (it boots in live mode), but there is a thing that bothers me. BT5 didn't have "tools", "pool" and "dists" folder in the root of iso image. What should I do with theese? Should I place them in the folder with live image of kali, or in the root of pendrive? Or probably some another options should be added to kernel parameters string? My ultimate goal is to not only make it bootable, but also ready to be installed from the pendrive, won't the absense of aforementioned folders prevent or somehow break setup process?
Hi guys,
I'm the developper behind LinuxLive USB Creator and I'm trying to find a way to make Kali live USB with persistence in a file.
I tried a few boot options such as persistence-path,persistence-storage but none worked so far.
Can you help me ?
Hello, i'm tying to install Kali on a usb key but i'm not able to.
I downloaded the iso (i tried 32 and 64...), i tried many tools : unetboot, win32 disk manager, linux live USB creator universal linux boot... But everytime when i tried to boot on the key, it's not working, the boot is not detected, i tried the key on 3 computers and it's the same.
This is how i do :
- i format the key using SD formatter
- i run a boot creator program ( unetboot, Linux live USB creator...) then i follow the process, i add the iso file then start... I wait until the program says it's done.
- Retart the computer change the boot priority to usb.
But it does'nt start, the key is not detected as bootable...
What's wrong ? Can you help ?
This my first time using this forum and I may have posted in the incorrect place with my first post! I have created a usb boot drive with Kali 32 and booted to a win7 machine. I get Invalid or corrupt kernel image' when I choose the any of the live versions. I have searched for solutions and followed some suggestions but it still does it! Does anyone have any suggestions?
Thanks
after numerous attemps i finally managed to put a working image on my usb, i had to use win32 disk imager, why do i have to use windows to install a linux distro?!
anyway:
dd if=kali.iso of=/dev/sdb bs=512k failed
unetbootin failed
other programs failed
I successfully used Win32 Disk Manager (see thread)
-e