Flash Extractor
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
IS917   45 3e 97 93   1x1 SM3268P-AB   98 de 88 a3   1x1 SM2246XT H AA   2c a4 64 32   4x4 Monolith Micro SD 2   98 d7 99 b2   1x1 SM3268P-AB   45 3c 98 b3   2x1 Monolith Micro SD_1   98 d7 99 b2   1x2 PS2251-68-5   98 de 94 93   2x1 SM3257Q AA   ec d7 98 ca   2x2 SM3267L-AB   98 d7 98 92   1x1 Monolith Micro SD PS 1146   98 3a 98 b3   1x1
20.04.2018 Sector Number Slow
17.03.2018 Adapter BGA-272
22.02.2018 Bad Bytes Editor
18.10.2017 Power adapter
07.10.2016 Conatiner v9
Other products
Soft-Center ltd.