a bitmap viewer for Flash Extractor

[book14]

Sometimes, you're only one step away from successfully recovering your data. Although FE is no longer updated, it is still a powerful tool for me. The existing Layout can let me know if this case can be successful. Then, sometimes when we set parameters, it's not so observable, so I wrote a bitmap analysis tool for FE. Why do I say "for FE"? Because I can open it directly or drop the file into this program. With it, I no longer need to open a xx 3000, and set flash parameters to view the bitmap, and I no longer need to wait for the polar bear to run for three minutes.

One of the keys to success depends on whether we read the chip well. In Bitmap, we can verify the quality of the chip by observing whether the graphic near SA is complete or contains a lot of noise (for example, Figure 1, of course, there are many factors that are good or bad for reading, so it is not discussed here).
This app mainly offers two features.
First, the bitmap measurement function, through the observation of coordinates, such as Figure 1, the x-axis to the service area, a total of 18272 bytes, if there is no other SA at the beginning, then the size of the layout can be selected is 1142 (18272/16=1142). FE could have used ECC to determine the template, but if it encounters bad bytes, it is not easy to find.
Similarly, in Figure 2, we can see that the distance from the beginning of the ECC in the previous segment to the start of the second segment of ECC is 1096.
Looking at Figure 3 again, this time we look at the Y axis. There are 1536 pages in a block, but only 1152 are useful, and the next 384 are blank; whether before or after “Block Pair”, they always have to be cut.
Second, the bad byte checking function. In FE, Software Bad Bytes needs to set the number of Block and Groups. The block parameter is how many pages are in a block. Sometimes, in AUTO FF, we will accidentally cut the FF contained in SA, so that the Layout position is wrong and cannot take effect. At this time, we can copy the bad bytes cut by FE in the Job file and then paste them into this software to check if they are cut properly. Of course, the bad bytes in the software can also be pasted back to the original Job file. As shown in Figure 4, it is divided into two groups with a size of 258.

The software is available to friends who love FE as much as I do. If you are interested in the software, you can send me a private message.

Attachments

[melvin]

I no longer need to wait for the polar bear to run for three minutes.

will definitely try the tool.

[book14]

Thanks. And I forgot to tell you that the hotkey to mark a bad byte is "control + left mouse button".
The first time you click is to mark it, and if you click again, it will be unmarked.

[Arch Stanton]

PM sent. Looks awesome!

[NANDoff]

very interesting indeed
nice work

[sin]

Incredible work! <3
--