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

Mate, read this topic thoroughly, you will know how to proceed.
I'm sorry, however you haven't made the minimum effort to check anything and are relying on us here without basic knowledge of your drive to work miracles.

For starters, CrystalDiskInfo, check what appears in the "software" field, you will know what to do next.

Not sure what's going on? You take a look at at least post #47 (page 2) from this topic and see what it should look like, then check on your own drive.
You will know the firmware version, the firmware_ps3111 + S11_flasher package from post #1, the path of action "VERSION 2: re-enforced FIRMWARE upload"....

As I wrote earlier, I managed to get my Gigabyte 240GB SSD back on its feet using the procedure outlined by my colleague @a_jablon. However, the main goal was not to save the drive (it's under warranty) but to be sure that I would erase the data irretrievably (well, maybe 99% sure).

So I started to pasture it by saving/deleting/transferring data to full capacity, this is what I've been doing for the second month with a frequency of every few days and for the hell of it it won't kick out, I'm waiting like salvation for "satafirm s11" (to complain) and it's as good as gone.
Have any of you perhaps, in the course of your practices here, encountered a trick that restores "satafirm s11", just for the heck of it, not by accident. I know it sounds silly, because here the repairmen themselves, do not spoil .

.

Sadly not, my experience confirms that after a repair (and firmware uplift) the damn things go absolutely fine, as if there was never a problem....

a_jablon wrote:

after repair (and firmware uplift) cholera some are running completely correctly, as if there was never a problem...

.
And as they die after repair do you have any time statistics?, you set up the topic two years ago, are there any that are already hulking 2 years?, because if so I'm left with just the angle .

In total, I repaired about a dozen units, of which I have 4 left with me. Of these 4 units, one died quickly, but it was the one that caused the most problems during resuscitation. The other 3pc - with the latest firmware (raised to the max) - are still running today, in "low-intensity" applications.

Efficiency: freely 75%...

What needs to be done: catapult it as far as possible... Put the system on it, torture it. Data to another drive, of course.

a_jablon wrote:

What you need to do: catapult it as much as possible.... Put the system on it, torture it. Data to another drive, of course.

.
Ok, thanks.

Hey All,

I just wanted to express my gratitude for the original guide. I ran into a CX400 512G2 in a SATAFIRM S11 state while I was browsing the used hardware market, the drive originally had only 5TB lifetime writes. Then I found this guide and managed to buy the drive for a little money. Originally it had SBFM 61.3.X firmware but shotrly after reviving it it went back to dead S11 state. Then I reflashed it with the version 61.5 and since then it seems to be working fine.
Honestly I don't really expect any long life from the drive, but it will be fine as long as it lives. Nothing important will be stored on it anyways.
So thanks again!

Oh well, it went back to S11 state again :/

Good evening gentlemen! Please let me know what maximum firmware I can install on my SSD GOODRAM CX-300 : 120GB (SSDPR-CX300-120).
Phison flash id:
v0.785a
Drive: 1(ATA)
OS: 10.0 build 19045
Model : SSDPR-CX300-120
Fw : SBFM11.2
Size : 114473 MB
Firmware lock supported [09 00 01 03].
P/N : 511-180831241 , SBSM11.1
S11fw: SBFM11.2, 2018Aug 8
Bank00 : 0x98,0x3a,0x98,0xa3,0x76,0x51,0x8,0x14 - Toshiba 15nm TLC 16k 128Gb/CE 128Gb/die
Controller : PS3111

Is it worth installing from such firmware versions? SBFM61.2, SBFM61.3, SBFM91.2?
Thank you!

@RazorUA https://www.elektroda.pl/rtvforum/attachments...hrase=CX300&mode=post_time&order=DESC

Estoy buscando el firmware SBFKq1.3 agradeceria si alguien lo tiene si lo pudiera compartir con la comunidad porfavor, no lo he encontrado en ningun lado ese firmware

SBFKq1.3 q ? drive is kingston?

>>21545756 Yes!, its an Kingston A400

Hey guys

I'm having an issue with a PHY 480GB external SSD. It's unfortunately hard wired with an Asmedia USB3 controller, no SATA options and the following info is available:

v0.844a
Drive: 3(USB)
OS: 10.0 build 26100
Model: PS3111
Fw : SBRM09.0
Size : 0 MB
Bank00: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank01: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank02: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank03: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank04: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank05: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank06: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank07: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank08: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank09: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank10: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank11: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank12: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank13: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank14: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Bank15: 0x98,0x3c,0x98,0xb3,0xf6,0xe3,0x8,0x1e - Toshiba 96L BiCS4 TLC 16k 256Gb/CE 256Gb/die 2Plane/die
Controller : PS3111 in Rom Mode

My problem is, how do i flash firmware onto it because the S11-Flasher does not recognize the drive (being USB)

Any thoughts?

It is possible that the USB-SATA bridge is interfering with the communication. You could look for documentation and try soldering a wire between the bridge and the controller for a direct connection over SATA.

>>21557753 a bit risky to advise soldering wires between SSD chips by an inexperienced user. And what if after your advice a user breaks something ? Will you repair the drive under warranty ?

On what guarantee? Do you even know how to read with understanding? Have you noticed what this topic is about? We are talking about a drive that is defective. If someone wants to repair it for the sake of repairing the drive itself, that means they apparently feel they can. Don't measure everyone by your yardstick. However, if he finds it beyond him or something goes wrong, then as he had a damaged disk, he will continue to have it. If you had read the whole thread carefully, you would have noticed that the repairs described in it don't always succeed, and even if they do, they don't always last. After this type of repair you can't have confidence in the drive anyway. But I get the feeling that I'm asking too much of you.

>>21557753

I don't have a problem soldering, as I have around 20 years of experience with this (microsoldering\hotair, etc). But if i go that route I imagine I'll need an actual SATA port and wires that extend from the controller to it, bypassing the bridge all together? And will this work without additional components?

You don't need a port - just clip directly to the wires. That way you avoid signal loss at the connector. If you can't find documentation, try identifying the two differential pairs between the controller and the USB-SATA bridge. You can catch the ground where you are comfortable. If you're going to have communication problems isolate the bridge so it doesn't get power, as its activity can interfere.

Hello
I have such a drive and only one firmware. Has anyone tried to upload another firmware to such a drive? With me so far the symptoms are that the drive boots sometimes even in 20 times always with a different frequency.

.

I have re-uploaded SBFMY1.3 but the drive reports as a SATA SSD and the capacity is 512GB and it is rather not this firmware. Before uploading the firmware it appeared in the s11-flasher that the SBRM09.0 firmware was recognised and there is no such firmware.

Would anyone have a FW: SBFMLA.5, for the CL100 drive from Goodram? Unfortunately the package from usbdev.ru does not have this particular one.

Swerybary wrote:

Has anyone perhaps FW: SBFMLA.5, for the CL100 drive from Goodram? Unfortunately the package from usbdev.ru doesn't have this particular one.

.
It doesn't have to be the same one. Please specify what kind of memory is there?

>>21604089 >>21604089 .
It is exactly the Goodram CL100 G3 480GB

Model : SATAFIRM S11
Fw : SBFMLAW5
Size : 457862 MB
Firmware lock supported [FB 00 01 02].
Drive unlocked [FB 00 01 03]
P/N : 511-230321273 , SBSMLA.5
S11fw: SBFMLA.5, 2022Jul19
S11rv: MLA.5-23
Original Model: SSDPR-CL100-480-G3
Bank00: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba 112L BiCS5 TLC 16k 512Gb/CE 512Gb/die 2Plane/die
Bank01: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba 112L BiCS5 TLC 16k 512Gb/CE 512Gb/die 2Plane/die
Bank08: 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba 112L BiCS5 TLC 16k 512Gb/CE 512Gb/die 2Plane/die
Bank09 : 0x98,0x3e,0x98,0x3,0x76,0xe4,0x8,0x1e - Toshiba 112L BiCS5 TLC 16k 512Gb/CE 512Gb/die 2Plane/die
Controller : PS3111
Flash CE : 4
Flash Channel : 2
Dram Size,MB : 32
Flash CE Mask : [++------ ++------]
Flash Mode/Clk: 3/7 (Set 3/7)
Block per Die : 3324
Block per CE : 6648
Page per Block : 1344
SLC Cache : 786432(0xc0000)
PE Cycle Limit : 3000

ParPage : 00
MaxBBPerPlane : 137
Plane : 2

>>19799272 Hey, I generally have the same problem with a Gigabyte drive on a Phison 3111, but with me Windows doesn't detect the drive at all, nothing, not a trace, although the BIOS has everything about it except one final thing n/e and I don't know how to revive the drive in that case.

mlodyszczvr wrote:

generally I have the same problem

- so follow the instructions described in this thread.


Describe the problem in a little more detail. How is this drive seen by the BIOS? How does MHDD or Victoria see it? What have you done so far in the way of diagnostics/repair and with what results? And remember that repairing is destructive to the content.

>>21631928 Ok, so yes, I started by trying to play around with the BIOS, changed from AHCI to IDE and nothing worked as it continued to not want to create a partition. So I tried further fiddling with the troubleshooting. The drive sometimes showed up, sometimes didn't, it's visible in the BIOS as just that S11. As for why I'm asking, because there's nothing written here, what to do as the system doesn't give a damn, that it doesn't see the drive anywhere at all, on all programs and it just writes me nowhere in the BIOS about the drive whether when I install Windows that one exists, or then when I try to fire up the computer, it sees that drive, wants to fire up on it, but the lack of Windows destroys that possibility. Only when I unplug it does it fire up on the HDD.

Added after 11 [minutes]: .

>>21631928 But now, after the 3rd system reset and change to GPT, it has come to life, that is, it is visible in the system as having worked for 93 years.

mlodyszczvr wrote:

partition wouldn't create

- because the disk is corrupted

mlodyszczvr wrote:

I tried to keep playing around with the troubleshooting.

- play around to your heart's content, but no one's looking at your hands and no one's going to guess what the fun was about. If you don't describe what you did and with what result, no one will guess.

mlodyszczvr wrote:

S11

then you have almost 6 pages regarding this problem.

mlodyszczvr wrote:

there is nothing written here about what to do, as the system doesn't give a damn

- among other things, this is what these 6 pages are about - read carefully and then write specifically what you have a problem with, because so far it seems as if you want to play tinker.

mlodyszczvr wrote:

lack of Windows destroys this possibility.

you won't boot Windows from a failed drive, and certainly not with this fault. You'll need to boot the system from another drive, and connect this one as a second drive.

>>21632177 Already seriously, seriously fixed, greetings

Added after 11 [minutes]:

>>21632177 But I have a question regarding whether the drive, despite having 100% in CrystalDiskInfo, will be worse, and if so, in what.

Hi everyone, I hope you can help me! I understand the process, but I don't know which pins to use for the Flash Mode short in this device.

I already tried a short where I marked it in red, but it didn't work, neither through SATA nor through a USB adapter. Does anyone know which pins to use for this drive? I really appreciate it!

mlodyszczvr wrote:

whether the drive, despite having 100% in CrystalDiskInfo, will be worse, and if so, in what.

- by reprogramming you have only fixed the firmware errors, but the memories themselves are already worn to some extent and this process cannot be reversed. Therefore, do not expect long and trouble-free operation, but rather that the drive may suddenly refuse to cooperate again.

serviciotecnicocanop wrote:

I've already tried short-circuiting where I've marked it in red,

- this is a good spot

serviciotecnicocanop wrote:

it didn't work

- perhaps because the PCB looks cruelly messed up and probably has damaged tracks. You'll need to patch the mechanical damage to the PCB first, before tackling the firmware issues.