[Update 1.0 to 1.3, only udisk remains in the /root/ folder]

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) 

[Update 1.0 to 1.3, only udisk remains in the /root/ folder]

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. :(

[Update 1.0 to 1.3, only udisk remains in the /root/ folder]

I tried to install with the help of the new udapter tool .. but same problem :(

[Update 1.0 to 1.3, only udisk remains in the /root/ folder]

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!