Successfull fail on upgrade? (not bricked..yet)

[Sizzlik]

Hi..i got my 2nd owl..i did manage to brick the first one. With the new one, i followed instructions again and now im here:

When i plug the owl in..one slingle blink..then a few seconds nothing...then rapid blink like selection mode (the usb drive blinks with it) but the rapid is less then 3 secs..then kinda fast blink (like booting) ending in a solid for a few few feconds...2-3 blinks and then slow blink error because no payload

When i press the button then, it switches to the double blinking Arming mode and i can see the wifi spot and i can ssh to it.

I wanted to check the version and have read that there should be a version file in / , but i cant find a version file to cat.

Am i updated now or not? And why isnt it rapid blinking for 3 seconds?

Please help me fast..as i want to keep on playing with it, but i first need a confirmation at what state i am atm.
I did not put any payloads yet..nothing but the update file. And it seems to have been deleted after the upgrade from the usb drive

How can i check now..please help..i dont want to brick it again on day 1

Thanks for any help.

[chrizree]

I don't know if it is to any help and it's certainly not fast, but here's some information from my point of view.

 

At SSH logon, the banner similar to the one pasted below should show, it displays the current version of the Signal Owl firmware

 

BusyBox v1.30.1 () built-in shell (ash)

 .___.
 {o,o}
 /)__)  Hak5 Signal Owl
  "  "  Version 1.0.1
=======================================
 Built on OpenWRT 19.07
=======================================

 

The banner showing the version can of course also be obtained by viewing the /etc/banner file

My owl also shows up in my Cloud C2 instance with version 1.0.1, so that's yet another way to verify the current firmware version

 

Furthermore, I have no VERSION file (as some other Hak5 devices have) in the root of the file system

drwxr-xr-x    1 root     root             0 Sep  4 15:53 ./
drwxr-xr-x    1 root     root             0 Sep  4 15:53 ../
drwxr-xr-x    2 root     root           909 Sep  9  2019 bin/
drwxr-xr-x    4 root     root           980 Sep  5 20:45 dev/
drwxr-xr-x    1 root     root             0 Sep  4 15:14 etc/
drwxr-xr-x   11 root     root           525 Sep  5  2019 lib/
drwxr-xr-x    1 root     root             0 Sep  4 14:09 mnt/
drwxr-xr-x    5 root     root             0 Jan  1  1970 overlay/
dr-xr-xr-x   51 root     root             0 Jan  1  1970 proc/
drwxr-xr-x   16 root     root           223 Sep  5  2019 rom/
drwxr-xr-x    1 root     root             0 Sep  5 19:47 root/
drwxr-xr-x    2 root     root           797 Sep  9  2019 sbin/
dr-xr-xr-x   11 root     root             0 Jan  1  1970 sys/
drwxrwxrwt   18 root     root           480 Sep  5 20:47 tmp/
drwxr-xr-x    7 root     root           101 Aug  1  2019 usr/
lrwxrwxrwx    1 root     root             3 Sep  9  2019 var -> tmp/
drwxr-xr-x    2 root     root             3 Sep  9  2019 www/

 

The update file was removed from the USB memory device at (or after) the initial upgrade. I see nothing strange in this behavior really since it seems logic to remove it in order not to perhaps trigger yet another upgrade execution at next boot. It's most likely "by design" that it is removed from the USB memory device.