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
SM2246XT   45 4c 95 93   4x4 82-00523-2   45 4c 95 82   1x1 SM3255TS Q AC   98 d7 98 b2   1x1 20-82-00369-1   45 4c 95 93   4x1 PS8035-0   98 3a a8 92   2x1 SM3257EN L -AA   98 de 98 92   1x1 IS917   98 3a 94 93   2x1 Monolith USB SM3257   ad 3a 18 03   1x1 TC90535   98 3a 94 93   1x1 IS917   89 a4 64 32   2x1
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.