-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
OT? Report successful installs of Psychson: please share your results #48
Comments
+1 |
Hi, I have some Patriot Supersonic Express 16GB-Sticks and I can tell the following: DriveCom.exe /drive=I /action=GetInfo Successfully Tested Demo: RubberDucky works fine. (Windows 7 64bit) I had a little bit of panic since I wasn't able to re-flash the stick after flashing it with rubberducky, but I finally found the way to re-flash it. I have to manually set the Bootmode and then et as Firmware the FW03FF01V10353M.BIN and it is a normal stick again. |
Hi! I was able to run succesfully HID payload demo on cheap 32GB stick sold under "Medion" brand. For additional reflashes it was neccessary to short pins in order to enter boot mode. OS was Windows 7 64bit. |
apparently, I have to find a "small" solution to short pin 2 and 3; the first stick seems to be broken because I made that too often. |
Hi, I would like to share my results with you and ask for help regarding some additional points. On the day after I bought another USB Drive but this time from Toshiba (TransMemory TX 8GB 3.0) and it has the same compatible controller 2303 from Phison.I experienced the same errors again, but didn't give up. Since I had removed the case and was afraid of touch the metal parts of the USB Drive while plugged in, I decided to use a USB Hub. This time I could not only apply the custom firmware but could also restore it as a USB Drive again. I used the burner xxx04M.bin and the firmware xxx0053.bin and it worked. After that I used a tool from Phison called RestoreUsb or something like that and was able to format and restore it again, so that I could transfer files to it. I wanted more though. So I modified the 0053.bin firmware to inject the script and applied to the USB Drive. It worked. All Duckscripts work just fine now, but I couldn't use it as a storing Device anymore. The system shows that a USB Drive is plugged in, but I can't use it anymore only for running scripts. This leads to my first Question: A) Has anyone succeded in making a USB Drive run scripts while being able to store data? According to what I've read this isn't an easy task since every firmware modification can cause problems to the functionality of the Drive. I tried to do the same tasks without the USB HUb and I keep getting the DeviceIoControl failed:0079 error. I tried to restore both USB drives using different versions of MPALL, but it didn't work out. Sometime MPALL recognizes the plugged USB key, but says there is a read error (Code 255 I guess) and clicking on start is pointless since nothing happens. I tried to create different versions of MP.INI and QC.INI but it didn't help. B) How should I proceed to succeed in restoring my USB Drive to default settings using MPALL? C) I thought about buying another Toshiba Transmemory TX to dump its firmware and try to apply to the other Toshiba USB Drive to see if it works. Does it make sense? I still have the dumped firmware of the Toshiba Drive in a folder and I've heard that the Dumping proccess could sometimes result in firmwares with errors. D) Is that true? Thank you for your help and sharing your information with us. by the way, this is part of an academic project at my university. |
Action specified: GetInfo Patriot Supersonic Xpress 8GB stick |
How to manually set bootmode? thanks |
Original tests are performed in the Patriot 8GB Supersonic Xpress. It seems that this type of device is hard to get nowadays. In the issue list I can read a lot about Phison 2251-03 powered devices that DO NOT work as expected. Furthermore there are reports - in different postings - about devices that are working on Windows A but not on Windows B x86 / x64and / or device that are working on USB 2.0 but not on USB 3.0 ports or the other way around. My suggestion would be to post successes - IN ONE THREAD - including:
If would be really nice if the first poster can also attach a log of all steps followed since we then know for sure that punching in the wrong commands isn't the reason of a failure. Thanks in advance for sharing!
The text was updated successfully, but these errors were encountered: