"Unknown device" DT100 16GB bricked ?

Question

"Unknown device" DT100 16GB bricked ?

Closed this issue 4 years ago · 7 comments

heyy boysssss. I have a Kingston DT100 16GB 3.0 (2307). After following the japanese guy tutorial, I did Hello World on my new badusb and after that I tried to change the text. I converted the code with duckenconder and did the same thing of the original hello world but when I connect my USB on the port I get the unknown device error. I've tried to pin 2 and 3 to bootmode but I still get the same error. Is there a way to repair this ?

Answer 1 · 2018-09-09T15:58:03.000Z

Short pins 26 and 27 to enter BootMode

Answer 2 · 2018-09-12T16:53:53.000Z

Sorry, 2 and 3 = 26 and 27. Still the same ;/

Answer 3 · 2018-09-12T16:58:20.000Z

Strange, i have a 2307 and no matter how many times i brick it i can allways enter boot mode by shorting the pins.

Answer 4 · 2018-09-12T17:00:23.000Z

Just to be sure, are you shorting the pins as you plug the device, or are you trying to short them after plugging?

Answer 5 · 2018-09-12T17:04:10.000Z

I'm shorting the pins and after I connect the device with the pins shorted

Answer 6 · 2018-09-12T17:06:33.000Z

Is it common notify me as "Unknown device" but works fine on Drivecom ?

Answer 7 · 2018-09-12T17:17:45.000Z

Yes, it happened the same to me, if you go to Device Manager and change the drivers from Composite to Mass Storage you'll see that the device is recognized with no problems. I guess there is some trouble with the descriptors. I managed to get this to work after removing the Mass Storage Device interface and it's endpoints from the descriptor in the source code, so the device will be recognized only as a keyboard and not as a composite device. The downside is that i lost the ability to send SCSI commands (now i need to short the pins every time i want to jump to BootMode). In your case, if you can communicate with the device using DriveCom, then you can put it in BootMode and use MPALL to burn the official firmware.