Ideas how to reprogram badusb / rubberducky

>>59437662
yes

>>59437662

sounds interesting

get a non-shit picture

File: IMG_2180.jpg (3MB, 4032x3024px) Image search: [Google]

3MB, 4032x3024px

This id the other side i cant seem to find anything

File: image.jpg (2MB, 4032x3024px) Image search: [Google]

2MB, 4032x3024px

There we go

File: AVR-ICSP.gif (2KB, 343x187px) Image search: [Google]

2KB, 343x187px

>>59437674

This is probably close to what you are dealing with

SDA suggests that it's an I2C header.

https://learn.sparkfun.com/tutorials/i2c

T3 is just ground.
T1 might be V+ since it connects right to the USB connector

The rest could be microcontroller IO or some part of I2C

>>59437759

One tool that you will need to deal with this is a multimeter

I suspect one of the chips is an FTDI. These are widely used in anything USB.

Perform a continuity test to see where the USB data pads go. The chip that they lead to is probably an FTDI and the other one will be a small computer

>>59437793
>>59437867

How can i even consider myself good with people like you guys haha i dont undestand a thing in boards like that :(

Thanks for your help

>>59437662
The 8-pin device is an eeprom. it contains the site info, and whatever code necessary to launch the browser. you will need to dump the eeprom contents to disk, edit the data as you see fit, then write it back to the eeprom. many low-cost devices available to do this, but you must work with the data in hex. i2ctools is your only friend here. a rasperry pi is ideally suited for this, as it already has an i2c bus interface.