Saturn

Thank you so very much for your response, Dav-ee! Running the script that you linked worked like a charm! You just saved me $100 US. Let me explain the steps to take from here for the sake of completion. Hopefully this thread will help at least one other person. 1.) Serial into your bash bunny. Instructions for this can be found on the wiki. 2.) Execute "nano sebscript.sh" (or whatever name you would like.) 3.) Paste the code that Dav-ee linked into the file you have just created, and save the file. 4.) Execute "chmod a+x sebscript.sh" 5.) Execute "./sebscript.sh reformat" 6.) sebscript.sh will then ask if you are sure that you want to reformat. If you do, execute "y" 7.) Your bunny will then reboot, and you should be good to go! Pics or it didn't happen: Thanks again to seb and dav-ee. I owe you guys a beer.

Welcome back to the thread, all! Picking up where we left off: Following the standard installation instructions yields no results. The bunny still boots into arming mode just fine (considering), but never attempts to update. Possibly due to the junk files in the root directory, or maybe due to the gremlins that caused this to happen in the first place. And yes, I would love to just delete these files, but: The files and directories on the drive cannot be deleted. So for the time being, I'm stuck in 1.0_167 **It was at this time that right clicking the device to safely eject started crashing explorer.exe** Stumped, I opened up putty to see if I could serial in, and I could! So I guess I have two questions: 1.) Do I need to apt-get install udisks? I've tried to set up ICS on my Windows box to no avail (RNDIS_ETHERNET payload doesn't run), so I may have to switch over to my ubuntu box and see if I can work some magic there. 2.) Would formatting the storage part of the bunny brick it? Could I try to wipe it clean and attempt an update with only the firmware in the root directory? *Just curious* Thanks for taking the time to read my quibbles, -Saturn

Thank you for taking time out of your day to respond to me. It means a lot. I have had a few more exciting developments since your response. Unfortunately, I have to go to work, so I will have to continue this when I return. To those that are lurking: this is going to be a fun one (if you enjoy problem solving as much as I do). Feel free to chip in once I post the most recent developments.

Good day, fellow security enthusiasts! I seem to have found myself in a bit of a pickle... I just updated to the most recent version (1.3), and I noticed that my bunny had renamed itself. Odd... I nervously double clicked on the drive and was greeted by this assortment of characters. So, my steps. 1.) I downloaded the most recent firmware from the wiki. 2.) I placed it in the root directory of the bunny, blah blah, police lights, blue light, successful install! Or so I thought. 3.) After I saw the above result, I downloaded the bunnyupdater. When I attempted to run it, it said that it couldn't find the bunny version and exited. (the astute among you may notice that there is no version.txt. I assume that this caused the error.) 4.) I performed a recovery using the exact instructions from the wiki. To my horror, I was greeted by this same sight. I have now stopped messing with it and come running to my peers. Hopefully this community of hackers, gurus and IT ninjas can get me up and running again.