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

Has anyone tried to revive an Gigabyte SSD GP-GSTFS31100TNTD, not sure what is the fw use in this one since the phision id tool just shows Model: PS3111 because the disc is in Rom mode

>>20889757 care to explain what did you did exactly? I just can't revive my gigabyte ssd

I have a problem with a Goodram CX400 256GB, after plugging it in it doesn't show in the BIOS or whatever. Looking for information on the failure of this series I found information about resetting the drive via a jumper, question is this applicable in this case + which jumpers exactly? unfortunately I have not dug into the schematic.

You've got this SSD on a completely different controller - you can see from the photo that it's Maxio, not Phison. Do you care about the content, or about bringing the drive back to life? With that said, I'm not going to blush - in either case I wouldn't count on success too much.

Exclusively looking to bring it back to life, the drive is basically unused, worked a few days. I know it's a different controller but this topic has 'most life' that's why I posted it here

In my case the process stops with an error at 15%.
I have read that this is a problem for the new disks with maskROM SBRM09.2.
Has anyone managed to solve this problem?

Would anyone be able to guide me to the correct shorting points?
After a long hiatus from trying to resurrect the drive, I got back into it. To start, I wanted to put it into the correct mode by shorting it on the board, but I'm not sure if I'm doing it in the right place (red line in the picture). After this process the drive just disappears completely, and is only restored by another unplugging.
Its model is specifically a Goodram CL100 gen 3 480GB with TB2AG23AYN2241 bones.
I'm also wondering if it's me doing something wrong, or if it's just that the drive is dead after my previous attempts to upload FW (it seems to me that those few months back the programs were seeing it normally, now it's only visible in the system when there's no jumper, as "SATAFIRM S11").

EDIT:
now I'm still looking, that after jumpering in these places, it is visible in the Intel Rapid program as "PS3111" with FW "SBRM09.2". The question is why can't other programs, such as MPTool, see it?
On the other hand, without the jumper, in the same program, as the former "SATAFIRM S11" with the correct capacity, but with FW "SBFMLAW5".

You're plugging in the right place. What MPTool doesn't see it? This thread has gotten so big that I would ask for more detail where we touch on individual cases.

MPTool v2.2.85, however the information about its malfunction is no longer valid. Programs started to see the disk normally, but e.g. MPTool throws "Device Invalid!" when trying to start.
All other fixes fail (including an attempt to change the FW with a flasher, where the process stops at 15% and the drive then enters ROM mode on its own).
I don't know if this drive has such damaged NAND's that my rescue attempts won't help, or maybe I'm doing something wrong and, for example, uploading the wrong FW (I've only tried with "SBFM61.5", which, according to colleagues abroad, is supposed to fit instead of the current "SBFMLAW5").

So the same problem as with me
I have read on other forums that it is a problem with MaskROM SBRM09.2
However, I could not find a solution.

Hello, the Goodram CX400 512GB in crystaldiskinfo has the name satafirm s11 has gone into super position, it is both alive and can be read, it is visible normally under windows but at the same time it is dead, because nothing can be written on it, I mean it can be, but the content disappears after restarting the computer. My question is whether it is possible to restore it without destroying the data, or is the only way to restore it usable is the method described in this thread? Thank you in advance for your reply.

You may have another problem. In order to realistically write/erase content on NAND chips, the Fowler-Nordheim tunneling phenomenon is used, which requires raising the voltage to several volts (the exact value depends on the memory chips used). If the voltage boost process fails, the electrons do not physically get through the insulator layer, the charge in the floating gate does not change, and the effect you are writing about follows. The drive thinks it has written something, but in fact it has not, and after a reset it continues to read the old contents.

@Parnyschab Current detection of this SSD present to us for analysis.

I've already copied the data from it, I'm just wondering if it can be restored to working order or is it kaput and there's no point in wasting time on this drive?

If this reading is true -> (634TB ?), only disposal remains.

>>21816253 >>21816253 So it died a natural death. Thanks for the information.