Here is the detailed information of my devide. So it was working, but the password I supplied was too long, triggering that bug. That is the most I've seen it do. Got this result off a 128gb Sandisk Ultra from Frys. Operates in the following modes: mode3,7,21.
Please let me know what do you think about it? SetBootMode works I use command DriveCom. Kind regards from Poland, yoyebie Windows has a setting that hides drive letters for empty or ejected drives, which is what the drive will be when custom firmware is flashed to it. Before posting I searched and found this old topic: I read it but it didn't helped me much. From the moment of finished format I face with situation written above. Setting Up the Build-Environment The developer of the code recommends us to use any version of to compile the tools and for building custom firmware.
Burner images for Phison controllers. Is there some workaround or do I need to do something else? I suspect that once you do that, the tools will work. The payload works, so I suppose that flashing process went well but I'm concerned about the fact that the drive won't show up in Windows Explorer. If everything goes right, you will see a new folder with many different files inside. Might be wrong but is working for me with this drive : These are the pins i've been using and are working reliably now Contact the pins before and whilst plugging the drive in and the light should remain lit, if it goes off or flashes before you've sent the first command that means its not in boot mode and try again. When I try to execute command DriveCom. Many of you don't even know about my existence here on Null Byte, so I thought of contributing something rather interesting.
Apparently my DumpFirmware is corrupted. Since the circle is on the top left corner of my controller from this perspective , I have to connect the two pins of the left bottom side: You may need to open the picture in a new tab and zoom in. You can also overwrite the firmware by executing build. I guess all Sticks not working with this firmware cannot be used for script injection. You can search github for Dckuino.
I bricked the device to bring this information forward: Sandisk is using a different chip, or atleast a modified one, instead of the straight Phison chips. Use latest version at Thank you for the link, I will test with the latest release. I found out that this had a 2307 microcontroller, which I think should work according to github. Okay, about the badusb walkthrough above, I have two questions. No need to flash it with something as it already reads and executes ducky scripts out of the package. Hi First off, I've been a frequent visitor of your wonderful and informative site, only this is first time I am writing.
DriveCom and EmbedPayload should be in the. In addition, I tried to flash the custom firmware but I get the same result. The issue here is a bug in the Phison code, when supplying a password more than 16 characters long it treats it as a bad password. I am a Senior Application Security Consultant, researcher and software developer with more than 15 years of experience. .
Then you just flash the drive and it will run the script. I write about my research and security in general, development and software design, and whatever hobby has my attention at the moment. In the next section, I will focus how to resolve this issue. I had one, but because I didn't want to sacrifice it I ordered another one from the known supported devices list. My Toshiba stick worked with this fw, my Sandisk did not. InvalidOperationException: DeviceIoControl failed: 0079 bei DriveCom.
I will try the Sandisk Expensive failure, I know to see if the larger volume has better results than the 16gb model. Utility to view detailed information about the flash controllers Phison. Some of these payloads are nasty. All tested on 3 machines having Windows 7 X64 Ultimate. Silicon Power Blaze B30 no longer uses the Phison 2303 controller. Download their zip onto a Windows machine, double click DriveCom.
First of all i have to say that this is a great-detailed tutorial! Furthermore, I would like to mention that I really appreciate constructive feedback from you guys. Finding and downloading all the required tools took a bit of effort, but building and executing everything went smoothly. Using duckencoder I created a inject. It sucks since it was an expensive stick, but I took the hit so no one else does. Any idea what I should change there.