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 3a a5 82   2x2 PS3108-S8-I   98 de 94 93   4x2 PS2251-07-V   ad 3a 18 03   1x2 SM3267L-AC   98 3a 98 a3   2x2 AU6989SNBT-GT-2   89 84 64 3c   2x1 PS2251-07-V   98 3a 94 93   1x2 Monolith SD_18   2c 84 64 3c   2x2 SD_61   2c 64 64 56   2x1 AU6998SN   2c a4 64 32   1x2 AU6989SNHL-G-5   98 de 94 93   1x1
17.03.2018 Adapter BGA-272
22.02.2018 Bad Bytes Editor
18.10.2017 Power adapter
07.10.2016 Conatiner v9
07.09.2016 VT / Auto - new mode
Other products
Soft-Center ltd.