Research leads me to deduce the culprit as the windows sleep-wake bug that trashed this SSD (both red and green LEDs stuck on during power up). I have a long out-of-warranty OCZ Vertex 2 SSD 120G that is no longer recognized by any BIOS on any machine I try. I know this is a dated thread, but I’ve scoured the web for help with little results. Any idea or more experienced reverse engineering hints are welcome. The binwalk shows a lot of LZMA compressed headers which is the same algorithm what is used by the qrc files. The Qt has a resource system to store files in the binary itself. The second way is the good old reveng: Disassembling of the updater tool to get out the resource files contents and hope that: - The actual hardware - firmware association is stored in some kind of db (xml, sqlite, etc.) - The firmware files are not encrypted and can be written to the flash raw. He does not seems to be active anymore on that forum. I have written a PM to him, but he have not answered. So that (s)he should know how the web backend should work, so how could I download my drive's firmware. You will have two results the forum above and a forum entry: If you check his/her posts on the forum: there are a lot of SATA and sql related posts. Do a quick google search for the "release/sf/ppro" string. Ah and they shared a link to a working fum.php url: Check that XML. The following itresting string can be found in the binary: tools.xml minver fwinfo.xml Pick one preferably unique string: the "fum.php?d=" Do a google search and you will get one result: The folks over that forum are trying to downgrade a firmware by mimicing the. I see two more possibility: Social engineering: The tool itself is written in Qt, by an Indian programmer. My problem is that I cannot get the drive to a state where the uploader tool could rewrite the flash. If I short any of the relevant pins it will not detect so I will end up in the unsoldered state.
0 kommentar(er)
