Wrong Flashing Procedure? about psychson

[brandonlw]

Yes, everything was correct.

You may need to unhide the device (by changing the "hide empty drives" option in Control Panel's Folder Options) before you can communicate with it.
What OS are you running, and is it 32-bit or 64-bit?
What type of USB port are you plugging it into (2.0, 3.0)?

I suspect there may be two issues people are having:

1. Communication with the hidden drive while running custom firmware may not be reliable for some.
2. The firmware dump may be corrupted or incomplete.

For (1), knowing your OS and environment may help me reproduce the issue.
For (2), if your dump isn't working, I would recommend trying to flash an official firmware image from the Useful Links section. (Even though you started with 1.04.53, anything that ends in .53 should be okay).

To get to a point where you can flash new firmware, you can enter boot mode by taking apart the drive and shorting pins on the chip, which is explained in the wiki.

[UbarRolf]

Brandon, thanks for your fast answer!

So, I already unhid the device, since the device manager in Windows showed me a "Portable Device" on "D:".

I am running Windows 8 64bit and was plugging the usb drive into a USB 2.0 slot.

The funny thing was, if I try to set the BootMode with "DriveCom.exe /drive=D /action=SetBootMode" no error is thrown (although I cannot flash the drive afterwards...).

[brandonlw]

At what point it does fail when trying to flash the drive after entering boot mode?

If it fails after saying "Executing...", that implies the firmware image might be bad, which is why I recommend getting one from the Useful Links section.