Phison PS225107 USB Drive.

[hack3rcon]

Hello,
I have a "Phison PS225107" USB drive and I want to fix it. I download some tolls like "ST-TOOL" and "Phison_MPALL v3.70", but none of them worked
Any idea to fix it?

Thank you.

Attachments

[ddrecovery]

What is wrong with the flash drive?
Bent?
Not being seen in Computer Management etc etc.

[fzabkar]

It identifies itself as "2307 PRAM", which means that there is no data access. I expect that this is a typical firmware "panic" scenario.

[Arch Stanton]

It identifies itself as "2307 PRAM", which means that there is no data access. I expect that this is a typical firmware "panic" scenario.

Where did you dig up this cool info?

[fzabkar]

The OP's screenshots have a reference to "2307 PRAM".

[Arch Stanton]

The OP's screenshots have a reference to "2307 PRAM".

Yes, I can see that. How did you reach the panic mode conclusion?

Speaking of .. been doing my own Googling too, and I came across the issue being reported on USB 3. When device was connected to USB 2 it did ID correctly.

Then took an older USB flash drive and connected it to my USB Stabilizer. When forced to USB 2 is does ID, when forced to USB 3 it does not.

[fzabkar]

Maybe I'm wrong, but when I search for "2307 PRAM", I get lots of hits where users say that their USB drive has changed its identity and is reporting "no media". Isn't that a "firmware" problem?

[Arch Stanton]

Oh no, I didn't mean you are wrong! I was just curious where you got the info from. Maybe the Device name being 2307 Boot Rom is even more telling? As if it's stuck at some point.

[fzabkar]

ISTM that if the controller can't make sense of the situation, it would revert to a manufacturing mode. This is the mode one would expect when the NAND is blank or uninitialised. I would think you would see a similar ID if you were to short the NAND's Ready/Busy* pin to ground.

[Arch Stanton]

Very useful info ..

[hack3rcon]

What is wrong with the flash drive?
Bent?
Not being seen in Computer Management etc etc.

Yes.
Which tool can fix it? ST-TOOL show me a green text but...

Attachments

[ddrecovery]

I have not used this tool so no nothing about it, but it looks like it successfully 'mapped' the data (32GB), whatever that means.
Do you know if this program does actually save the data somewhere? (I suspect not).
Have you tried recovering it in Linux?

[Arch Stanton]

I think he's trying to refurbish it or something. In general data is unrecoverable after using such tools.

[hack3rcon]

I want to save this USB drive.

[ddrecovery]

I want to save this USB drive.

Can you clarify.
Do you want to save the data?
Or just save the flash drive to be used again without the data?

[hack3rcon]

I want to save this USB drive.

Can you clarify.
Do you want to save the data?
Or just save the flash drive to be used again without the data?

Just save the flash drive to be used again.

[hack3rcon]

Any idea?

[HaQue]

from when I was stupid enough to play with these tools, IIRC there are more steps required. Such as formatting the memory, or writing the config (burning?) it to the drive. If you hunt around there were some poorly translated word docs that kind of explained the process. There may be some forum posts on one of the USBdev.ru type forums that very vaguely hint at the correct procedure. This is risky at best, a small brick likely. These tools are intended for factory, and they have proper equipment for writing the drives.