joanorsky wrote:
I'm gonna do the new dump on a beeprog+. Any special configuration i need to know for the dump?
Page size : 512b
Spare size : 16b
Block size : 32 pages
Number of blocks : 1024
Tension : 3.3v
... Right?
yes, but as jermy said, config exists, always use the preset if possible.
I am glad this is finally to this stage. I don't think I conveyed as good as Sean showing the idea in pictures, but in my second post on page 1:
Haque wrote:
Usually you would have bytes called spare area that holds the FTL information. The actual FTL can be tricky or impossible to see as a whole because it is mad up of both hardware (ecc engines, xor engines) and the bytes in the spare area (block numbers, page numbers, page rotations, block conditions, ecc , and more) there is a huge amount of schemes used, and DATA Recovery is performed using only a subset of these attributes of the FTL.
sometimes it can be as simple as looking at each page sequentially, or each page will have a block number and you just piece it together. Other times some info is actually stored by the OS or another special area of the chip such as in TLC chips, and putting it together is a whole lot harder.
Normally there will be some relationship of the Spare area bytes. So if you cut out each spare area bytes and put each spare area 1 after the other, you can see easily the patterns. ever SA might have the 4th and 5th byte FF FF followed by a number that you can tell increments. you can then guess that the incremented number is a page number or block number. I don't see any relationship with the bytes of this dumps SA. Franc could be right and this could be ECC. ECC looks like random data. So this means we should be looking for a translation table that maps the physical pages/blocks to the data image/images. as the TT holds the information instead of the spare area.
If you look in a hex editor, and set the bytes displayed across as the page size (normally a hex editor is 16 bytes across) then these patterns show up quite well. VNR has a bitmap view that is excellent for this work.
Putting the User Data back together should be fairly easy after dumping properly.
if you look at the last 16 bytes in seans pictures, you can easily see how a pattern would emerge after you line up all the SA's in a row
FAQ
Search
Login
Register
HDDGURU FILES
). As i can tell the ECC code is present on the initial dump (1st post)... and the code without ECC was done by fzabkar on 12th post (
