BTU - Project LOKI.05 - Time to get Sticky

When I last left you I have a 2.2 gig file downloading so we could install our Stick Fingers Kali-Pi.

Well today when checking my computer I had a successful download, so now it is time to get this OS on a card and into some Pi!

I am running Windows and per the recommendation I will use Win32 Disk Imager to get my 2.2 gig image onto my 32 gig card.

I probably don't have the latest version but this one has been working fine for me.

I click on Write to start it off.

Yes, because otherwise I won't be getting any Sticky-Pi!

Woohoo.  We like those messages.

Now it is time to eject that card and place it into our Pi.  Also time to actually take those previously shown parts and put them together to see some Pi booting!

So first attempt to boot, no good.  I get power but no flicker on activity.

Out of curiosity, I pulled an older card with a dated version of Raspian and put it into the Raspberry Pi 3b+.  It gave me the Rainbow display that showed my OS was not current for the new card.

So throwing my new image into the old Raspberry Pi b shows no boot as well.

Placing the old card back into the RPi shows a fast and simple boot.  So both Pi's are looking good. 

Doing a little research showed that some cards have problems with Kali so I decided to pick up another 32meg card:

So new SanDisk card, and I quickly load the downloaded image on to test it out.

Still not getting a good boot.  Deciding to go look at the site some more I see they have a new version just released:

So I downloaded the newest version and loaded it onto both cards.

Still no boot.

Okay, maybe I should try Raspian or even Noobs...

Not sure why I can download the 2+ gig file for Sticky Pi but I can't get either of Raspian or Noobs download.  What is really irritating about both of them is that the download until almost reaching the end and then pop a failure.  So gigs are downloaded and time is spent but nothing good is received.  :-(

As can happen when you are grasping at IT straws I decided to try Etcher instead of Win32 Disk Imager.

This definitely took longer then the Imager, hopefully it will work!

Yes! Success!  So now you can see activity lights and Kali starting to load!  Etcher for the win in this case.  The extra cards and days of downloads could have been avoided if I tried Etcher first.  At least we have success.

Log in screen!

And now full Kali Desktop!  Load complete.

In the next blogs I want to delve into the actual tool sets for Bluetooth and getting it to work with a portable screen since it is coming on vacation with me and my normal desktop test environment will not be available.