ohjeongwook/dumpflash

Verbose Mode Available?

Opened this issue · 2 comments

roflware commented

Hi,

First off, thanks so much for this code, as well as awesome reverse engineering articles. They are what inspired me to try my hand at this.

On two different chips I have been looking at, I either get "AttributeError: NandIO instance has no attribute 'Manufacturer'" or "ZeroDivisionError: integer division or modulo by zero". I am looking at a Spansion and a Samsung chip. I realize that Spansion is not supported, but when supplying the hex address for the Manufacturer based upon the chip, I am presented with the same result.

Either way, is there any way to display a more verbose output as opposed to erroring out? I am using the Xbox 360 clip (which you mentioned as having potential in one of your articles along with the recommended FTDI breakout board). When I apply the appropriate pressure to the clip, I typically get unrecognized manufacturer, but I wanted to be more certain that the issue is the unrecognized chip, rather than a faulty connection with the 360 clip.

Is there any form of verbosity that can be added to your code to see what it is attempting to read? That will give me more confidence in my hardware, and that it is more of a recognition of the chip problem.

Thanks!

ohjeongwook commented

Hello.

The zero division error is usually the sign of initialization error, which usually comes from the bad contact between the chip and TSOP socket. You might try to press the chip and socket lightly when you perform the dump. But, you said you already did it. Especially Xbox 360 clip is known to have bad contact with the chip - desoldering the chip and mounting on TSOP socket is more desirable. Another issue is that when you actually put the clip on the chip, it might awake the system and boot it up and it will interfere with the clip - this is what I observed with more than one device.

I'm adding more debugging messages now - I'll push the code soon.

roflware commented

Appreciate it, and I look forward to that commit, should be useful.

Also, if I get a Manufacturer ID not found, I imagine that my clip is connected well enough, it's just a matter of the chip not being supported? Would I receive a message about the Manufacturer ID not found if the chip is supported, but it awakes the system? I noticed that with a few USB drives I tested powered on, I wasn't sure if that would generate the same error message.

Totally agree that desoldering the chip would be the best bet for dumping data, but I wanted to avoid that if possible.

Thanks!