Naerz Posted August 8, 2017 Share Posted August 8, 2017 Hello, so i just have my bash bunny, i know how it works, and how to configure it. But, my firmware is 1.0 and i want to update it. The installation is very simple and i don't understand why i can upgrade properly. i explain myself, after doing step by step the installation, the installation doing well, no lef failed occured and take time. in the usb folder, version.txt is in 1.3 and i have all of my payloads. when i log into the tty of the BB, only udisk remains and a file version.txt who tell me i am in 1.3 Payloads don't work ´cause i don't have the basic tools (ducky.py, Q , Quake and led) so i reset my BB and i'am in 1.0 so here my problem, i absolutely want to update, and i do the same installation 5-6 times. Same error. i don't know what to do, after each installation only udisk remains in the bb. i write this post, maybe someone can help me? i saw few people getting the same problem but no solution was proposed else to recovery then re-install (it didn't fix my problem :( ) I hope to a faster answer ! Thanks furether guys! Quote Link to comment Share on other sites More sharing options...
Naerz Posted August 8, 2017 Author Share Posted August 8, 2017 I tried to install with the help of the new udapter tool .. but same problem :( Quote Link to comment Share on other sites More sharing options...
Naerz Posted August 8, 2017 Author Share Posted August 8, 2017 So i try to install the 1.1 firmware but still the same problems. The installation finish, trying to log to the tty, only udisk + "version.txt" remains ... I'm stuck. Don't know why it doesnt install properly. Doing a Recovery to 1.0 ATM. I will need some explanation please. :( Quote Link to comment Share on other sites More sharing options...
Naerz Posted August 8, 2017 Author Share Posted August 8, 2017 So, i'm on it still last post :x Probleme isn't solve. But, firmware 1.0 work fine, some ducky script work and some payloads too. I can tell my Bash_bunny is working. With an updated firmware, installed by tool udapter or by myself, switch1 == switch 2 == arming mode. Basic payloads don't working + basic ducky scripts too. Can some admin or people who encountered the problem can reply ? 'Cause, i used both tool_udapter and basic installation so i can tell, i didn't do wrong. (Just verify and copy a gunzip file woooow :b) Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted August 8, 2017 Share Posted August 8, 2017 There is no problem - firmware v1.1 and above cleaned up the /root/ folder and other files a lot. Make sure to update your Bash Bunny to firmware v1.3 and ensure your payloads are up-to-date. 1 Quote Link to comment Share on other sites More sharing options...
PrimeNe Posted August 9, 2017 Share Posted August 9, 2017 Just do "cd .." and it should take you a level back to the folder where you have everything. Quote Link to comment Share on other sites More sharing options...
Sebkinne Posted August 9, 2017 Share Posted August 9, 2017 4 minutes ago, PrimeNe said: Just do "cd .." and it should take you a level back to the folder where you have everything. No it doesn't. The applications, scripts, and files were moved to completely different locations, and the PATH variable was fixed so that you can still call Q, QUACK, ATTACKMODE, etc. 1 Quote Link to comment Share on other sites More sharing options...
couchTornado Posted September 14, 2017 Share Posted September 14, 2017 I believe Naerz is having a similar issue to the one I experienced after upgrading to 1.3. "when i log into the tty of the BB, only udisk remains and a file version.txt who tell me i am in 1.3" This sounds to me like he is doing an ls on the udisk mount point but of course it appears to be empty because the USB drive is failing to mount. Or at least that's what it looks like to me. I'll upgrade from 1.0 to 1.2 today and see if that fixes the issue. It may be that since the filesystem is already mounted to the host system (Windows/Mac) it is unable to mount in two os'es at the same time and isn't supposed to show up via serial when in arm mode. In that case, I'm just chasing red herrings and leading folks astray. If that's the case, apologies to all. Quote Link to comment Share on other sites More sharing options...
Dave-ee Jones Posted September 14, 2017 Share Posted September 14, 2017 (edited) 5 hours ago, couchTornado said: I believe Naerz is having a similar issue to the one I experienced after upgrading to 1.3. "when i log into the tty of the BB, only udisk remains and a file version.txt who tell me i am in 1.3" This sounds to me like he is doing an ls on the udisk mount point but of course it appears to be empty because the USB drive is failing to mount. Or at least that's what it looks like to me. I'll upgrade from 1.0 to 1.2 today and see if that fixes the issue. It may be that since the filesystem is already mounted to the host system (Windows/Mac) it is unable to mount in two os'es at the same time and isn't supposed to show up via serial when in arm mode. In that case, I'm just chasing red herrings and leading folks astray. If that's the case, apologies to all. *To do this method shown below you need F1.3. It doesn't show the mount when you login to the Bunny's console. E.g: cd / Takes you to the very root. You may notice the root directory, and all the other folders and things. You may also notice that if you try: cd /root/udisk It will show nothing in there at all. However, your USB still has storage. Type in this command: udisk mount Then type in this command: cd /root/udisk Then type in this command: ls VOILA! *takes a bow* I would like to thank Sebkinne for his amazing work here. Edited September 14, 2017 by Dave-ee Jones Quote Link to comment Share on other sites More sharing options...
couchTornado Posted September 15, 2017 Share Posted September 15, 2017 Awesome! Thanks Dave-ee Jones! Just tried the above in firmware 1.2_249 and it worked as advertised. I will upgrade to 1.3 again, as that doesn't appear to be the problem. The nmapper script still didn't work, so my speculation about its inability to mount and write to the USB storage from Debian was incorrect. Back to the drawing board. Quote Link to comment Share on other sites More sharing options...
Dave-ee Jones Posted September 18, 2017 Share Posted September 18, 2017 Good to hear, I didn't realise it also worked in 1.2 but it makes sense, I guess. Good luck from here on out! Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.