R3V0L4T0R

I appreciate you taking the time to respond to my questions.. I wasnt trying to insult anyone but I feel pretty insulted myself. I clearly read and re read all of the things that people have told me to read. Im not someone who is sitting here waiting to be spoon fed anything. I was just looking for a clear answer. Ive been working on this problem for days now.. also there is a section called questions and a section called bugs as they relate to the ducky. I was simply trying to cover my bases and be seen, I asked for clarification and none was forthcoming. You might also note that the nature of my problem changed after the firmware flash and so i asked another question,. Anyways. Taking your advice with my Ducky... When i put a newly created inject. bin file alone on my sd card named specifically as "inject.bin", it will not deploy when pressing the button in twin duck mode. http://i39.tinypic.com/w71wyv.png I have waited for the machine to recognize my ducky as a drive and waited a minute beyond that as well attempting to re-deploy with no results. I would try another firmware if someone had a specific one they thought would be more helpful but all the ones I have tried have failed. ​I apologize for wasting everyone's time and asking for clarification. I thought I might be able to add something to this project but apparently I was incorrect. Moderators can remove me from the site if need be..

Interesting that no where in your signature info does it say that some firmwares if they cannot find the inject.bin on the root of the card deploy their own. See that was one sentence and it answered a question. You wrote two and did nothing but make me feel bad. Thanks for taking the time out to help someone out. Your'e a real standup guy.

Thanks for the response, Your answer to me is verifying once again that my duck is faulty. I can place it into my win box with the twin duck firmware and the computer recognizes the duck as mass storage and its called DUCKY.. The syntax of the bin files are nothing like what is executing..

Flashed back to c_duck_v2.1.hex formatted my card to verify its cleanliness. Put inject.bin onto root of card deployed ducky into machine recognized as mass storage pushed button nothing. everytime same results. here is the state on my sd card before and after, seems pretty root to me. http://i44.tinypic.com/21c81fn.png So what am i missing other than not using the linux based java encoder? I really dont want to go through any more trouble trying to get my VM enviroment to handle getting online and getting access to my sd card and then using linux make something I should be able to download or make in windows really easily. If running a linux box is mandatory for this duck to work Ill just send it back cause that is silly. I understand that only cool kids use linux and Im not really as stupid as i seem (CompTIA A+ and whatnot) but I think there should be an easy way to verify if the duck works or not without having to go through all this trouble. This has been four solid days of reading and work and nothing should be this difficult. I am sure by now someone has read this and realizes that my duck is faulty so if they could just get with me on an exchange i can get off the forums and go enjoy my life. If the online encoder doesnt work maybe there should be a sticky about that? Something along the lines of the duck must be encoded with the encoder provided or it will not work. pretty simple and it would have kept me from buying one. Most of us rookies saw that site as a way for us to catch up.. As a side note. Maybe someone should write a tutorial on flashing that includes all the information. Things like adding the hex files to the bin file location of the program.bat might have been a nice note that could have saved me a lot of time. I know none of you want rookies joining in but Ive never felt more ostracized by a community before. You were all rookies once.

I just had to verify that i am in fact NOT a moron. when I open the card at the root level and can see the inject.bin file i just downloaded and it is the only thing on the card, that is in fact, on the root of the card. If that is the case then there is something wrong with my duck because it isn't seeing the bin files on the root and the firmware is delivering one. Now back to duckfirmware.hex. .. SD card root level. one inject.bin encoded online from a script that I wrote (is this the issue, is the online bin maker corrupt?) ducky delivers payload that goes to the site still.. I believe I have tried every combination of anything I can figure..can someone verify that if in fact I am putting a fresh inject.bin onto the root of the card and it still doesn't work that there might be something wrong with my duck. Can i send it in for inspection??

ok that makes sense.. I think my problem is understanding the root of the card issue. I thought that if the card was blank and formatted and I put it in a reader in a windows machine, downloaded an inject.bin from the online encoder and put it straight onto the card, that would be enough. Am I wrong? With the java encoders Im having a little trouble still, Im running Backtrack in a vm and am still new enough to Linux that what seems simple to you guys is a nightmare for me. I have everything updated i think (in terms of java) and can watch the duckencoder go through its paces but at the end it doesnt create the bin file because of some missing main warning. I read on it for 11 hours yesterday and still dont get it. I dont want to have to use a vm box to create a bin file if i dont have too.. All i really want to do is verify that the duck works. Im beginning to learn that i am not smart enough to have a toy like this although it seems like a simple answer would set me straight. Is there a way to get an inject.bin file created without using linux? or to put it on my card using windows drag and drop or anything like that? When I put something on the sd card in the traditional drag and drop fashion does it not go directly to the root?? Surely there are windows command prompts to make this happen too? Running all this in a vm is making it more challenging i think.. I flashed back to the duckfirmware.hex this morning also although I miss the pretty colors of the twin duck :( Im so ready for this thing to work.

I have read and re-read both of the links you have provided and I guess im not getting it. Is there a way someone could just tell me exactly what is supposed to be on the sd card? I thought it should be empty at the root except for the single inject.bin file i created with the encoder? Is this wrong? Do I have to use the included encoder or does the one on the website work? If i produce a .bin file there can i not drag and drop it onto the sd card? Why when I put an sd card in with a single inject.bin does it then default to the website opening and put another inject.bin file on my cd card, visable when i reinsert if for inspection in my reader? Im not trying to be a bother but I have read every post on the forum...twice...and I cant figure out why this is acting this way..

I flashed my ducky to the firmware at the bottom of this page https://github.com/hak5darren/USB-Rubber-Ducky/wiki/Downloads and everything seems to work but now when I deploy any .bin my duck opens up a browser to hak5, which is cute but not very helpful. Sometimes after running an additional .bin file will appear on my sd.. so one goes on two end up there after deployment which only opens the link to the website is there something wrong with the online encoder that I dont know about? Does anyone have a fix for this? Ive tried different cards but all formatted to FAT and cant get this issue resolved. Any help would be really appreciated.

Can anyone help me?

Just as a follow up, I confirmed that the sd card is named "Ducky" I have placed several different .bin files onto the root of the card and renamed them "duck.exe" I am still getting the same results..\ Perhaps Im doing something else wrong? Im still confused about why my duck wont operate in any of the firmwares other than twin duck also. I hate being new.

Just to clarify, Are you saying that any inject.bin file I have on the sd card that i wish to deploy needs to be renamed to duck.exe? to work? My sd card itself is labled Ducky.

Im sorry man Im not trying to be rude at all and i genuinely thought I answered your questions. You asked me what firmware I flashed and I answered the c_duck.hex i got from the google code site, which i think is the twin duck. You asked what script I used and I mentioned that I had tried several but here is one ive tried : DELAY 3000 GUI R DELAY 200 STRING notepad ENTER DELAY 200 STRING Hello World!!! ENTER I enter this into the website Ducky Toolkit encoder found here ----->http://ducktoolkit-411.rhcloud.com/Home.jsp download the inject bin file put it on the root of my sc card put said sc card into the ducky and insert the ducky into my usb port....where.... it is recognized as a drive (I assume because of the twin duck firmware)... then when I press the button (again no matter what the script was) I get this http://i39.tinypic.com/28ixmpy.jpg it opens a cmd which the script isnt asking for and imputs a bunch of weird stuff.. again im not trying to be rude and I really would like to solve this problem but I dont know how to answer any more than I have. I gave the extra background stuff cause I thought it might be relevant..

Im not sure where the correct place to post this question is sorry. I wasn't sure if it was a bug or user error. It doesnt matter what script I use but for sake of argument let say i used the standard "hello world", open a gui after a delay and whatnot, because I have used several scripts, including that one, from simple to hard, all compiled to inject.bin files online with the ducky toolkit site. Is this my problem? Something with that compiler? Always with the same result. In the beginning I was having major general red led issues and did my research, got the driver issue resolved and began looking for a firmware update. Any of the standard "inject and execute" firmwares go solid red led, and yes, ive tried different cards throughout the firmware trials as well (the included card, a 2gig Samsung and an 8gig Kingston). This led me to believe maybe i got a bad duck, but.. When i flashed to the c_duck.hex i got some pretty lights again, my device was recognized in win7 as a storage drive and when i push the button things seem to happen... But its always the same thing and not what the scripts are saying as Ive gone through and executed them myself just to learn cause i like to know stuff.. so what am i doing wrong> other than posting this in the wrong section? Please move it to the appropriate area if need be and Ill ask forgiveness and that you dont crash my stupid box. Im not smart enough to post a picture of the output in the cmd prompt apparently. :/

Hello all Complete n00b here, Got my ducky today and started fiddling and quickly had the red LED of death issue. I flashed the firmware until i settled on The twin duck c_duck.hex which would be how id like to use the duck. Now, however, whenever I load an inject.bin and activate it with the button my payload gets held up at a cmd prompt where the payload slowly starts filling in things and eventually gives up. I can duplicate it and post what it says if need be but i thought maybe someone might have had the same problem be able to laugh and point at me and then offer a fix. Im running win7 and my driver for the duck is up to date. So my thoughts are torn between believing i got a faulty duck, because if i flash to the standard firmware or any of its flavors the device gets red-led-locked, and believing that i am an idiot and did something wrong.. Any help would be very appreciated. <a href="http://tinypic.com?ref=28ixmpy" target="_blank"><img src="http://i39.tinypic.com/28ixmpy.jpg" border="0" alt="Image and video hosting by TinyPic"></a>

Ok so I got my new Ducky and Flashed it successfully to c_duck_us.hex and all seems well, but every time i go to run a payload it executes to the cmd prompt and begins typing there, very slowly and eventually asks the comp to do something it cant and quits. Im running win7 and I have updated my driver for the ducky chip and gone through a whole bunch of different firmwares until i found one that would actually let me execute a payload. Initially my duck didnt seem to like any sd cards or want to do much quacking at all. so i flashed it and got it to commit to the twin duck architecture but now when i try to execute it hangs up at the cmd.. Any advise would be great!