csava wrote:
Reading a chip correctly is never a straightforward task. If you think that simply putting the chip into an adapter and pressing a button can achieve accurate reading, it may lead to a misunderstanding and create a communication barrier between us. The reason why most common chips can be easily read is due to the efforts made by the tool developers behind the scenes.
Take the example of the most common TSOP48 flash chip. Firstly, developers need to collect a large number of chips from different manufacturers and production periods and conduct tests and statistics on each one. These chips typically have the same data bus and fixed pin positions, but the locations of VCC/VCCQ/VSS/VSSQ might vary. So, it requires different power configurations to be arranged, allowing the tool to automatically switch to the correct configuration when you press the read button.
Secondly, the chip configuration data is often confidential and only accessible to authorized manufacturers. Even without the data sheet, one can try to guess a configuration based on correctly configured chips from the same manufacturer and different periods as a reference. The process involves reading and validating the chip step by step. This can be quite challenging for those without enough experience in this field, as it requires an understanding of the addressing method of NAND flash.
Thirdly, regarding Read Retry, in the era of 2D NAND flash, there was usually only one type of Read Retry. However, with the advent of 3D NAND, various methods to correct chip errors were introduced, including but not limited to Read Calibration, Read Offset, and ZQ Calibration. There are no publicly available instructions on the internet that tell us how to correctly configure the register commands and addresses, so almost all the work is done through reverse engineering.
Lastly, setting the correct voltage and thresholds is another complexity. While 2D NAND usually only requires 3.3VCC for reading, newer flash chips come with multiple voltage options, and you need to set different VCC and VCCQ accordingly.
I want to emphasize that even for the easiest-to-read non-Monolith chips, a significant amount of behind-the-scenes work is needed. Otherwise, you will be limited to using ready-made templates to solve previous old cases. If these templates have even a 1% difference from your case, you will get stuck at those differences. Every year, I encounter many cases abandoned by other laboratories because they couldn't recover the data. Typically, they get stuck in 1-2 places. As long as these issues are resolved, the case can be successfully recovered.
Absolutely. You can clearly see in the bitmap. The whole geometry analysis is pending.The reading protocol some what worked....Lot to set with the voltages , sizes and reading protocol. One size never fits all and going off by even 1% would yield very unforgiving results.
--
FAQ
Search
Login
Register
HDDGURU FILES
, Anyways i am still very convinced something is wrong somewhere seriously . This Includes you and me both our configs . I am sure next week i will have something from Rusolut TS , BTW Sin i saw this its just been added -> 