Sebkinne Posted October 20, 2017 Share Posted October 20, 2017 Hey everyone, We have recently discovered a bug in the update process of the Bash Bunny, which causes boot-loops. The bug is triggered if the upgrade file had been extracted, renamed, or was otherwise altered. Fortunately, we have now found a fix for the issue: Plug in the Bash Bunny and unplug it immediately when the initial green LED turns off Repeat step #1 three times Plug the Bash Bunny back in and wait for it to reset. You should see either a "police" pattern or a red blinking LED. Set the switch to the switch1 position (furthest from the USB port) Wait for the device to reboot (indicated by the green led) and set the switch to arming mode immediately as the green light turns off. If all went well, you should now be able to access the Mass Storage partition of the Bash Bunny (or serial in). Delete any leftover update files (such as "ch_fw_1.3_264 (1).tar.gz") Safely eject / sync the Bash Bunny Reboot your device, by re-plugging it, while keeping the switch in arming mode. This should get your Bash Bunny up-and-running on firmware v1.0, allowing you to properly upgrade to the latest version. We recommend using the Bash Bunny Updater for this. We have released firmware 1.4 which prevents this bug from being triggered. Note: These instructions are not the same as the one from this thread. Similar, but more reliable. 2 4 Link to comment Share on other sites More sharing options...
Recommended Posts