Flash Extractor
Soft-Center
About     Shop     Downloads     Manual     Library     Forum     Services     Contacts
Software bad bytes
Some memory chips have broken bytes at pages
Controller can not use this bytes to store data
So it skip this bytes



Flash-Extractor expects that data is sequential
So we must cut unused bytes
And fill free space at end of page with ff to keep same page size



Hardware bad bytes

Some memory chips is tested at factory
List of bad bytes positions gen be read from chip with special command
NAND_Reader read this positions and store them in 01_01.dump.bb file
Then we can use "Cut bad bytes" step in mix editor to remove bad bytes

Software bad bytes

Some controllers test memory chips by its own method
They form list of bad bytes and store it somewhere in memory
We do not know where they store it
And can not use it to remove bad bytes

So, before use Flash Extractor,
we need find positions of bad bytes and remove them
Last added
Monolith Micro SD_13   ec de 98 ce   2x2   v2 UT163-T6   2c d3 94 a5   2x1 SD_51   2c 88 04 4b   2x4 PS2233-F   98 d5 98 83   1x1 IT1167BE-48A   ec d7 98 ca   1x1 82-00258-1   45 c7 98 82   1x1 SM2685BA   45 de 94 93   1x1 Monolith USB_15   2c 44 44 4b   1x1 SD_61   2c a4 e5 54   2x4   v2 SD_6   89 d7 d5 3e   2x2
News
22.02.2018 Bad Bytes Editor
18.10.2017 Power adapter
07.10.2016 Conatiner v9
07.09.2016 VT / Auto - new mode
27.07.2016 CR2 files support
Other products
Soft-Center ltd.