Kingston USB3.0 DataTraveler 100 G3 Phison 2251-07-V

[jerovsek]

Hello,

I receive this pen drive for datarecovery.
I was able to recover some smaller files(smaller then 1MB), but bigger not.
With chip off I read one physical chip with two parts.
I apply ECC correction and read retry, but there is still big amount of unreaded pages.
Read retry mode checking failed.

Any suggestion.

Thank you

[Lardman]

Try a different application/hardware.
Clean and re-tin connector pins.
Get creative with the temperature control.
Get creative with the voltage control.
Just keep retrying.

There's no magic solution for failing nand - tune the recovery the best you can and keep hammering at it until you have enough or as much as you can get.

[jerovsek]

hello Lardman

thank you for sugegstions

i have only PC3000flash
i play with different voltages but from 83k chanis it read only few hundreds
RR works from 2.150V and up
with 2.100 appear window wit hex differences. This is only solution I didn't try, because I was not shure with it, is it OK or not.

Currently suggestion RR type for this TLC hynix chip is type 36

[Arch Stanton]

Hello,

I receive this pen drive for datarecovery.
I was able to recover some smaller files(smaller then 1MB), but bigger not.
Thank you

You mean before you chipped-off? Files were < 1 MB or larger but truncated? Was it due to read errors? Or perhaps fragmentation?

[jerovsek]

before I chip off I can see files/file structure with all atributes/sizes, but was able to copy files smaller than 1Mb. Those files are ok.
But I was unable to recover files, which are larger then 1MB.

As I can see, there are unread parts from start to the end of each part of memory chip. Thats why smaller files are recoverable and larger not.

[Arch Stanton]

Yeah but what exactly happened when you tried to copy those 1+ MB? Files larger did not copy at all, or did copy but only partially copied, truncated at 1 MB?

I assume you tried cloning it before chip-off, what happened?

The 1 MB doesn't make much sense to me in relation to typical page/block sizes (I am no expert on the matter but still trying to apply common sense I fail to see the rationale of the 1 MB cut-off).

[Lardman]

The 1 MB doesn't make much sense to me in relation to typical page/block sizes (I am no expert on the matter but still trying to apply common sense I fail to see the rationale of the 1 MB cut-off).

I'm guessing the size is a coincidence rather than a cause.

[Arch Stanton]

I'm guessing the size is a coincidence rather than a cause.

Ah, yes! Anyway, my point is, wasn't logical recovery given up on rather easily .. I mean truncated files due to file corruption, file system corruption or fragmentation aren't solved by chip-off per se. But you're right, I got carried away with the 1 MB thing.

[pepe]

i would also have had tried imaging it through interface... then work on the image.

pepe

[HaQue]

If the damage is not actual representation of the files and structure (which means you are S.O.L) then it is likely you don't have parameters correct for this job.

These controllers can be simple block pair with join by page, but also more complicated such as this FE example:

Code:

Layout
  PS2251-V 1158_1150 Xor 0561_384_256
Mix
  Input
    Order  0/1
  Join by Page
    Parts  2
    Page   0xc00000
  Cross Block
    Field  Block Number
    Block  0x600000
    Parts  4
  Divide
    Field  Block Renum
    Value  0x4
  Block Renum
    Block  0x600000
    Page   0x4000
Assembler
  Block Number
    Block Size   0x600000
    Bank Space   0x4000
    Banks        00 / 0x000 / 0x164f
    Mix          4 / 0x4000


mess that up and you won't get a proper filesystem, or you could also get partial recovery.

maybe post a pic of the device, both sides, and the parameters for the PC3K task

[Lardman]

Hello,
I apply ECC correction and read retry, but there is still big amount of unreaded pages.
Read retry mode checking failed.

jerovsek appears to have a decade of experience, I assumed everything possible would have already been done to get an image via the controller and that failed - so a move to chip off. The blocks need to be read before anything can be reassembled otherwise they're just white space. My understanding was the OP was stuck at this point but if it's read correctly and there are still problems then time to examine the layout.

[jerovsek]

thank you all for suggestions

first I try with logical recovery and image creation.
With image creation there was a lot of read problems. That was the reason for chip off.

Now I need to read as much as possible from chip. I don't get better result from read retry.

Any suggestion, what I need to tune to get better results?

Thank you

[HaQue]

Whats the chip ID?

[Bolo]

@Haque: for sure ad 3a 18 03

[HaQue]

if it is, then Yuk! This is a WL chip, it doesn't have software bad bytes does it? if you look on the PCB and identify the normal VCC pins, are there any others that are also tied to the regular VCC pins? Maybe you need what SC NR calls a power mod.

[Amarbir[CDR-Labs]]

Read This Too -> https://forum.hddguru.com/viewtopic.php?f=27&t=40000