Jump to content

Doridian

Active Members
  • Content Count

    8
  • Joined

  • Last visited

Everything posted by Doridian

  1. As long as you can attach to serial and there is a firmware.bin file available from Hak5 it should work, yes.
  2. The update you can download from hak5 is ltieraly a raw binary image (update-1.0.1.bin). So you can just flash that thing. It is what I did. All you do is flash that to $firmware_addr (which should actually be 0x9f000000 IIRC)
  3. You can follow Darren Kitchen's post above for getting it hooked up (cracking it open and finding the serial port). Hook that serial port up immediately, but do not plug the Signal Owl's USB cable in to make sure it does not get any power. Then you get your hands on the update-1.0.1.bin (from the Hak5 downloads site, it is just the latest firmware update) Then you download my repository and follow the instructions (make sure you have the NodeJS runtime installed) Then you follow the app's instructions (it will tell you when to plug the Signal Owl into power)
  4. Having the same problem. On my Cloud C2 server I can see the reverse SSH session arriving and in TCP ESTABLISHED state. When I connect to the websocket via CLI, I get an error "device not connected" from the WebSocket, which the UI does not seem to handle gracefully (the API however DOES return the device is indeed connected in the API the browser calls before doing the WebSocket).
  5. I have made a script to flash it with the minimalistic thing as outlined above. Flashing/recovering via this procedure takes roughly 4 HOURS. Link to GitHub for anyone courious: https://github.com/Doridian/slow-uboot-flasher
  6. Also @Darren Kitchen as the Owl comes with a "small" (can only flash, I believe it is referred to as a ledger) firmware at first. Can a link to that be provided? If it is smaller, it'd take less time to flash obviously.
  7. Thanks for this topic. I managed to brick my Owl by messing around with sysupgrade (I botched my arming mode config and couldn't connect to it anymore, but I could connect fine by pushing a payload that started sshd). So it erased parts of my flash, whooops (squashfs is corrupted, the kernel still mostly boots via serial console, but most files just don't work at all). Anyway, I wrote a nodejs script that can now send the image to it via serial using a single "mm" command and its auto-increment feature. Excruciatingly slow, but sadly, despite u-boot claiming there is two eth interfaces fo
×
×
  • Create New...