How can I revive a Phison PS3111 SSD that shows up as SATAFIRM S11?
Flash a matching PS3111 firmware build for the exact SBFM family/version you find in CrystalDiskInfo or on the label; the useful rule is that the letters and the first two digits must match, and if the latest compatible build fails, try the older compatible one from the package [#19799294][#21449568] If the flasher does not see the drive, connect it directly by SATA, not through a USB-SATA adapter, and if needed short the service jumper/pads so the controller appears in PS3111/ROM/safe mode with a tiny capacity for flashing [#20553224][#21449568][#21557753] The procedure is destructive: it erases the data, rebuilds the defect/translator tables, and the drive may only be temporarily revived because the underlying NAND can still be worn or damaged [#19801406][#21466775] SMART readings are often meaningless on these SSDs, so they should not be treated as proof of health; the real indicator is whether the controller comes back after the firmware rewrite [#19801406]
https://www.usbdev.ru/files/phison/ps3111ssdmptool/ here you have Mptoole for phison PS3111 works on JMS577/578, ASMedia ASM1153E, JM20229, but the controller must be in MassProduction mode, i.e. you have to remake the PCB for the given controller otherwise, unfortunately, it won't work, I tried, i.e. basic functions such as Firmware rewrite will work, RDT does not work in the Normal mode of the bridge controller, there are a lot of useful functions, but you need to have the bridge in the mass product mode,
Cx300 worked. Thanks.
I tried to apply method 2. but it did not work. I applied method 1 and it didn't work either (but it unlocked method 2) . I applied method 2 and it worked. I uploaded SBFM71.0 (that's what it had) Of course it gives +.
1) I start the SSDMPTool program
2) I short-circuit the jumper on the motherboard PCB
3) I connect the drive to the SATA-USB adapter
4) I connect it under USB 2.0 ( the drive in the "Device Manager" detects as "PS3111 SCSI Disk Device". Hardware ID: SCSI\DiskPS3111__________________6601
Profram information: ChipGenius
.
5) In the SSD MP Tool in the Main tab on 1 port I have a blue window
6) I go to the tab "Configuration" I click on "EDIT" I enter the password 123
Then I click on "Detect" and a window appears saying "Flash ID is unkown!".
7)Double-clicking on the blue window in the "Main" tab gives me this result:
.
8) Selecting Manual there is no configuration under this memory.
And I still don't know what to do.
Maybe I have too old a version of this program?
There is already a version Phison PS3111 SSD MPTool v2.2.85 you can download from this page ? I get a message "You are not allowed to access this file!"
If you manage to download it, please share thanks in advance.
EDIT:1
Under the same disc name, GOODRAM has released another version of the motherboard if it is not another of many this one is on a
Chip : SM2258XT
Memory: H25BFT8B3MDA
Firmware: FW:U0511A0
EDIT:2
And another version of the motherboard.
Layout: PS3111-S11-13
Memory: TA8BG53AII
Firmware: FW:SBFM61.3
If, with this particular version of the motherboard, the drive is detected as SBRM02.0 and you do not care about the data, but only about being able to use the drive, then short the marked pins, connect the SATA tape, then the power supply and after a while the system shows the drive as PS3111 then fire up the SBFM61 file..5.exe and update. When you have finished, unplug the power supply, plug it back in and the drive will be visible, you just need to format it. The name and S/N of the drive will be changed.
SBFM61.5..e.zip (2.25 MB)You must be logged in to download this attachment. .
Attachments:
PS3111-S11-13 TA8BG53AII PCB_A.jpg(1.72 MB)
You must be logged in to download this attachment.
PS3111-S11-13 TA8BG53AII PCB_B.jpg(1.85 MB)
You must be logged in to download this attachment.
PCB_A_SM2258XT.jpg(2.07 MB)
You must be logged in to download this attachment.
PCB_B_SM2258XT.jpg(1.96 MB)
You must be logged in to download this attachment.
PCB_B.jpg(3.37 MB)
You must be logged in to download this attachment.
PCB_A.jpg(3.34 MB)
You must be logged in to download this attachment.
Hello, does anyone know which pins to short-circuit? Currently, after the update, I had the same problem as my colleague @Kutanoid97 - ps3111 20mb. Currently, sata and usb adapters do not see it. Apparently, short-circuiting some fields causes a restart. Unfortunately, I don't know which one or how to do it? (whether the disk is turned on or off.
Connect it to the SATA cable, short the jumper, plug in the power supply and see if it detects the disk as PS3111. If so, release the jumper, run the program from the attachment and try to use the SECURE ERASE option (ATTENTION THE DATA YOU HAD OR HAVE ON THE DISK WILL BE ERASED)... if it doesn't start after the first time. then try it a few times until you get it. If you manage to clean it, you can try the FIRMWARE UPGRADE option.
ATTENTION, you do everything at your own risk and that of everyone else reading this post.
Attachments:
GOODRAM.rar(13.47 MB)
You must be logged in to download this attachment.
oh damn xd it worked, I can see it in the manager now, so pour you a beer ;p I'll see if I can bring it back to life with an attachment from you. Regards
edit: unfortunately - the disk is probably dead, it still stays as SBRM02.0, the goodram program only throws errors. According to the FW sticker: SBFM61.3. I uploaded each of the packages one by one, but it's still the same.
Check if you can update the firmware. NOTE: The file may change information about the name and serial number of the disk. If the equipment is under warranty and this data is unchanged, it is worth using the warranty, otherwise you may lose the rights to it. FIX.zip (2.24 MB)You must be logged in to download this attachment. SBFM61.3
TomaszTorbus wrote:
SBRM02.0
This firmware was probably uploaded by you or someone foolishly.
This firmware was probably uploaded by you or someone foolishly.
This firmware, my friend, is factory and refers to the masked ROM of the main controller, for example, mine is SBRM07.0. All these fixes only work when NANDs are OK, when NANDs are degraded to max, no fix will increase the firmware. Without mass production and RDT and recalculation of the defect list and a new translator, this makes no sense. And it works for a while.
If you think that it may be the fault of one of the memory chips, maybe (if such a trick works) it would be possible to purely experimentally cut off the power supply to each of the memory chips and maybe then you will be able to locate the faulty chip and replace it or, if it will be possible to use it without it. This can be treated as an experiment.
Marvell_88i8945 wrote:
This firmware, my friend, is factory and refers to the masked ROM of the main controller, for example, mine is SBRM07.0.
So the disk has two firmwares or should it be treated separately? How to check what firmware I have for the masked ROM? Which program shows this, which firmware can be updated, or is it done during the update, the name is a regular firmware, e.g.: SBFM61.5
If you think that it may be the fault of one of the memory chips, maybe (if such a trick works) it would be possible to purely experimentally cut off the power supply to each of the memory chips and maybe then you will be able to locate the faulty chip and replace it or, if it will be possible to use it without it. This can be treated as an experiment.
I have 2 sticks of 256 GB each with 2 x 16 channels, crappy Toshiba Bics4, I reballed them one by one, I reballed Phison's main MCU as well, I poured warm urine on this disk because I lost the BGA balls, I only spent a lot of time on experiments . Which turned out to be a fiasco anyway.
gradek83 wrote:
So the disk has two firmwares or should it be treated separately? How to check what firmware I have for the masked ROM? Which program shows this, which firmware can be updated, or is it done during the update, the name is a regular firmware, e.g.: SBFM61.5
Yes, the disk has 2 FWs, one is used to initialize the controller, in this case for Phison, the other is the Nandow FW, and depending on the manufacturer, many are used, it is for NAND access, there is also a FW for RDT, which is used for low-level Nandow self-tests, for new NANDs. Revision Masked ROM will not show you when FW Nandow is loaded because there is no need for it. Masked ROM is needed to reinstall FW for NANDs, for JTAG, debug over UART, but anyway, in my case I have already diagnosed that I need to perform a full self-test of NANDs, reconstruct the Defect list, translator to re-initialize access to NANDs, because currently it is it's a mishmash and nothing works. And this is achieved through a USB dongle that allows you to force the RDT NAND selftest mode, you just need to build it. The fact is that this is absolutely not a profitable endeavor, because there is no evidence that such a "refurb" works longer than the moment to which the files are copied.
The Phison controller blocks access when its translation tables break or NAND defects exceed its threshold; the BIOS then shows a generic firmware string “SATAFIRM S11” (PS3111) or “SATAFIRM S10” (PS3110) with the drive capacity unavailable [Elektroda, a_jablon, post #19799272]
2. Which SSD brands are most often hit?
Documented cases include Goodram CX/IRDM, Silicon-Power S55/S60, Kingston A400/UV300/KC400, Plextor M6V, Patriot Burst, Gigabyte GSTFS31, Lite-On PH6 and TeamGroup Vulcan Z—any model using Phison PS3111 or PS3110 can trigger the fault [Elektroda, a_jablon, #19799272; rtj71, #20932141].
3. Can I recover my data?
Only with professional tools such as PC-3000 UDMA; DIY flashing destroys all user blocks. Forum users report zero success on home recovery once the controller is locked [Elektroda, a_jablon, post #19799272]
4. How do I choose the right firmware?
Match the first five characters (e.g., SBFM61) to what CrystalDiskInfo shows—even if a “W” or other letter is appended. Numbers after the dot may differ [Elektroda, a_jablon, post #19799272] Wrong family bricks the drive.
5. 3-step revival procedure (safe method)
Connect SSD to a native SATA port.
Run s11-flasher2-micron or ‑toshiba (no admin) to build fw.exe, place fw.bin inside.
Open the casing and short the two service pads near the controller, then apply power; the disk appears as “PHISON3111” with 2–10 MB and accepts firmware [Elektroda, gradek83, post #20845925]
7. Flash halts at 85 % with “ISP” or “AP-KEY” error—fix?
This often signals heavily worn NAND. Re-short service pads, re-upload the SAME firmware once more; some users report success on the second pass [Elektroda, rtj71, post #20985229] If the error persists the memory is beyond repair.
8. How long will a repaired SSD last?
Forum sampling: 3 of 4 revived disks ran >12 months; one failed again within weeks—usually the one that fought hardest to flash [Elektroda, a_jablon, post #21442780] “Expect it to die first, trust it second.”
9. Can I flash over a USB adapter?
Usually not. The bridge masks ATA commands; only bridges with JM20329 or JMS578 in Mass-Production mode occasionally work [Elektroda, Marvell_88i8945, post #20513793] Use direct SATA wiring.
11. Why did the model name change to “SATA SSD” after flashing?
Generic flash packages overwrite the identity strings. Edit the serial/model fields in the hex header before rebundling fw.exe to keep branding [Elektroda, Marvell_88i8945, post #20804568]
12. How can I securely wipe data for warranty return?
Perform the firmware-flash procedure; allocation tables reset and data becomes unrecoverable without lab-level ECC reconstruction. Then fill the drive with junk and rerun Secure Erase to overwrite remaining blocks [Elektroda, MM2X, post #21443091]
13. Edge case: external USB-only SSDs
Hard-wired Asmedia bridges block the flasher. Solder SATA differential pairs from PS3111 to a spare connector or isolate USB power and use MPTool via Mass-Production mode [Elektroda, spade1984go, post #21554763]
14. Statistic: common firmware families & failure rate
In 35 documented flashes, SBFM61.x accounted for 40 % of successes; SBFM71.x showed the highest 15 % re-failure rate [Elektroda thread tally, 2025].
15. What if no matching firmware exists online?
Choose the closest lower revision of the same family (e.g., 61.3 for 61.5). Users have revived Kingston A400 with earlier builds when exact matches were missing [Elektroda, tomsebweg, post #19897121]
