SATAFIRM S11 or How to bring an SSD to life on a Phison PS3111

artaa wrote:

As if anyone was interested

- all unnecessary toys are welcome, even when there is no time to play with them.

OKAY. ;-)

Somehow it will be sent.

For me, Cxie400 sees their ID memory, but there is no access to them, also SATAFIRM S11 is not always the same as when the controller is only in SBRM07.0 mode, i.e. only ROM Mode.
Then the described problem and its recovery attempt does not work.

For the GOODRAM CX400 512 GB drive it worked
The only problem is how to connect the drive - there is no question of an external SATA3 drive . Only under SATA directly to the board - the firmware unwinds instantly.

wiktorfeiner wrote:

For the GOODRAM CX400 512 GB drive it worked
The only problem is the method of connecting the drive - there is no question of an external SATA3 drive. Only under SATA directly to the board - the firmware unwinds instantly.

I checked on 4 platforms, with AHCI, without AHCI, SATAII SATAIII in no way was going to load the FW. Of course, I checked directly from the SATA port in ROM Mode, so I'm curious how you magically managed to put it FW?

I haven't looked at the topic DAAAWNO, but it's worth adding the following information:

THE OLDER VERSION OF THE CONTROLLER, i.e. PS3110, should also not be omitted by us ... SATAFIRM S10 - the same error as the one in the above topic and there are also countermeasures (analogous as in the description above).

I know it's a "politically" bad time*, but the guys from Russia did a great job and for this controller - here's the link: link

As above, I will not copy their work out of respect for it. There is EVERYTHING needed to bring SSD to life on PS3110.

The S10-flasher would be useful for the above-mentioned fun - I'm adding below, including the firmware package from the above-mentioned website:

_______________________________________________________________
* let's separate the Russian authorities from ordinary citizens. Anyone with an open mind will understand...

It's safe to say that the problem affects every cheap SSD, it doesn't matter the controller, whether it's Phison or another. It will fall the same, without warning.

Yes, SSDs usually fail without warning. Not only the cheapest ones, although made on better chips, statistically last longer.

As someone wise once said: users are divided into those who MAKE backups and those who WILL MAKE backups ;)

SSDs only accelerate the acquisition of correct habits...

a_jablon wrote:

SSDs only accelerate the acquisition of correct habits...

- it's a fact

However, in my case, I managed to put the disc back on its feet, but not for long, which confirms the fact that the Nandas are definitely relegated, the disc is trash. Greetings sincerely, for me the topic is finally finished.

buddy @Marvell_88i8945 - GOOD WORK anyway - congratulations. Hard drive but KNOWLEDGE priceless. It confirms what was the hypothesis: you bring the drive back to life, but the state of the NANDs causes the "short-lived" effect. Your work has not been in vain

For training, it's just a waste of time, PLN 150 went to live in about 4.5 months. And not with your programmers that don't work, only from PS3111 MPTOOL v2.8 but you need to have the JM20329 bridge, because it doesn't work on other bridges.

And that's what this topic is about, to write about. I'm not closing it on purpose

Marvell_88i8945 wrote:

you must have the JM20329 bridge, because it does not work on other bridges.

I also noticed that the PS-3111 somehow likes JMicron more. I don't have enough time to look at the issue in more detail, but I think something is up.

Yes, they wrote that it works on jm20329, and it actually works, but if NAND is thrown into space, it won't help either.

I have a problem, namely the s11 flasher program does not see a broken SSD drive (GOODRAM CX 400 512 GB), only a good one that I use. The SATAFIRM S11 drive sees CrystalDisk, device manager and disk management. Can anything be done about it?

Connect the failed drive to your desktop PC directly via SATA. Very often, the flasher does not see the drives connected via USB-SATA adapters.

If you connect via SATA and still can't see it, get to the electronics board (upload a photo if anything) - there will be solder pads used to put the disk into service mode - then it will appear.

I had it plugged in via SATA all the time but today when I turned on the computer I noticed that f11 flasher had detected this drive for me. I immediately uploaded the software and reset the computer and now it showed me something like this.

Can I still do something about it or is it already kaplica ?

What firmware version was there originally? At first glance, it looks like an INCOMPATIBLE version has been uploaded.

SBFM 61.5

@Kutanoid97 Update for Goodram CX400 won't he see it now?
https://www.elektroda.pl/rtvforum/topic3564332.html#17849529
https://www.goodram.com/wp-content/uploads/GOODRAM-SSD-firmware-updater_20211026.zip

It only sees a good drive

Try to upload these -> SBFM11.2_08082018.bin

Only now, apart from CrystalDisk, no other program or utility detects this disk for me

Friends,

as part of the fight with Phison PS3110 I broke a broken disk ;)

Maybe you'll have a cure for that....

Patient GoodRam CX100 240GB

PCB as below:



The disk came to me in a dead state, generally I played a bit with uploading the software to it, because what showed up in CrystalDiskInfo - it's about the firmware version in the software upload mode - nothing matched. I just haven't found any software that matches it ANYWHERE (or I'm unaware that I have one at my fingertips). You know: if they died, it's no loss anyway...

It turned out that the above-mentioned disk did not accept most of the softs from the Russian forum (links were a few posts above), but it got me on SAFM11.x and 12.x softs. The side effect was that it did not return SMART - smart is empty, not even a serial number ... Damn, what can I say: learned from experience that the wrong soft cannot be loaded on it (this was the conclusion from the experiments ) I decided to try a higher version, probably SAFM16.x. The problem is that, contrary to previous experience, IT WENT IN, but I lost contact with the surface of the disk.

Currently the drive shows up as SSD SCSI Disk Device in device manager, CrystalDiskInfo doesn't see it, no surface is visible. S10 flasher can't see it.

Is there any miraculous way to force it into a mode where s10-flasher will see it?

I attach a photo of the PCB, because I remember that it was done by shorting the soldering pads, but I don't remember which ones. It can be done, because experimenting on a USB adapter, I got this:



a bit stupid method: short circuit "on the stick" with slightly wet fingers.

Once I get to that, the flasher will work...

Added after 1 [hours] 10 [minutes]:

Update: after connecting via SATA and repeating the pressure in the same place it WORKED.

SAFM11.3 firmware uploaded, the disk can be seen, the surface can be seen, SMART if it didn't work, it doesn't work.

Is there a workaround or the RIGHT firmware for this drive?

Hi, thanks to your scribbles I managed to get two Apacers AS350 back on their feet, thanks ;)

As for the Goodram above: I just had a similar situation with one of the Apacers, after uploading the firmware, the effect was the same as yours, after restarting the computer, I uploaded the same firmware again and smart started to appear. I used flasher s11.

@rtj71 congratulations on successful repairs.

A question for the general forum users who managed to bring disks to life: how is the durability of such disks raised with the methods described above?

It is known: repair makes sense as long as it brings a lasting effect ;)

For me, so far, everything that I brought back to life with the above methods (about 10 pieces) is alive and well.

After the above-mentioned experiences, I steer clear of SiliconPower drives - I had most of them to do.

From experience, I see that the cheap PNY CS900 (another controller) should also be avoided with a wide berth. I haven't had to bring any of the Apacers AS350 to life so far, but judging by my colleague's statement, they are not "eternal", so it's probably just a matter of time.

There were several GoodRams (out of 3) and so far the one described above was the worst in resurrection. Because of the PS3110 I had to use the S10 flasher - the procedure works, it gives advice.

If someone had a problem with flasher's disk visibility, look for a jumper (2 pins) or use a magic method with a resistor, e.g.:



This is not always identifiable (hence the combinations above) but putting the drive in a mode where it shows up as 2/8/10MB (small) ensures that the flasher will see it.

BTW: the greatest successes are achieved when plugging drives directly into SATA. Working on SATA-USB adapters does not guarantee success.

Hello.
I was able to lift the GoodRam CX400-512 with the second method.
But I still have a CL100-480 FW: T0910A0 drive. Is there a chance to get this firmware from you, because there was no such firmware in these packages.
The drive did not go into SATAFIRM mode, but HDTune shows bad sectors, and in Smart: 2 reallocated. We managed to download the data, but the system keeps BSOD regularly.
I wanted to try to upload FW out of pure curiosity and see the effect.

Koenig wrote:

bad sectors

Koenig wrote:

the system crashes regularly BSOD.

- NAND degradation. Nothing will come of it.