HDD GURU FORUMS

Looking for PS5019-E19 (E19T) MPTool / factory package for SSSTC XA1-311024

I have a SSSTC XA1-311024 1TB M.2 2230 SSD that is not working. No data recovery needed, just want to use it again.

* Model: SSSTC XA1-311024
* PN: M1106370-007
* PCB: XA1-311024 REV 21
* Controller: Phison PS5019-E19-35
* NAND: SK hynix H25BFT8G5M3R-BDJ

Current symptoms:
* Enumerates as NVMe normally
* PCI Vendor 1987 (Phison)
* Firmware reported as EJRM01.2
* Windows detects disk as "PCIe SSD"
* Serial number present
* Capacity reported as exactly 1,048,576 bytes (1 MB)
* Disk appears Online/Healthy but RAW
* Flash ID utility shows 0 MB and cannot obtain NAND information
* SMART/reliability counters mostly blank

PowerShell reports:
FirmwareVersion : EJRM01.2
Size : 1048576
BusType : NVMe

I already found an E19 firmware BIN named EJF10002_05082021.BIN, but it appears to be from a different firmware family than EJRM01.2, so I am not willing to flash it blindly.

I am specifically looking for:
* PS5019-E19 / E19T MPTool
* EJRM01.2 factory package
* SSSTC XA1-311024 manufacturing package
* Matching config / parameter files for H25BFT8G5M3R NAND

Has anyone recovered a 1 MB-capacity PS5019 drive in this state, or does anyone know which MPTool branch supports EJRM firmware?

EJRM01.2 is a masked ROM version. This state usually indicates a physical malfunction, such as a malfunctioning memory chip controller, etc. Such a drive is likely unrepairable without additional physical intervention.

Use the phison nvme flash id utility from VLO to obtain more detailed information about the chips map and its manufacturer.

Thank you for the info. This is what the utility showed when connected to nvme slot on the mobo:

v0.386a
OS: 10.0 build 26200
Drive : 0(NVME)
Driver : W10(0:3)
Model :
Fw :
Size : 0 MB [0.0 GB]
LBA Size: 1
CEL not supported

At least the controller type should be detected. There seems to be a driver issue here. Try connecting the drive via an NVMe-to-USB adapter.

This is what is shown in an enclosure:
v0.386a
OS: 10.0 build 26200
Drive : 1(USB)
Bridge : JMS
Model : PCIe SSD
Fw : EJRM01.2
Size : 1 MB [0.0 GB]
LBA Size: 512
CEL not supported

You should use Phison nvme flash id, not Phison nvme flash id 2.
http://vlo.name:3000/ssdtool/

Enclosure:
v0.3a
OS: 10.0 build 26200
Drive : 1(USB)
Bridge : JMS
Model : PCIe SSD
Fw : EJRM01.2
Size : 1 MB [0.0 GB]
LBA Size : 512
Controller: PS5019-E19 in Rom Mode
FlashID : 0xad,0x5e,0x2a,0x33,0x0,0xa0,0xad,0x5e [0x0f 0x00 0x02 0x02] - Hynix 3dv5-96L TLC 16k 2048Gb/CE 512Gb/die
Bank00: 0x5e,0x2a,0x33,0x0,0xa0,0xad,0x5e -
Bank01: 0x5e,0x2a,0x33,0x0,0xa0,0xad,0x5e -
Bank02: 0x5e,0x2a,0x33,0x0,0xa0,0xad,0x5e -
Bank03: 0x5e,0x2a,0x33,0x0,0xa0,0xad,0x5e -
List of banks possible incorrect

I am reading from online help that Flash ID v1 reports PS5019-E19 in ROM Mode and successfully reads Hynix 3dv5-96L TLC NAND IDs on all banks. Does this indicate a missing/corrupted firmware configuration and would a PS5019 MPTool rebuild be the appropriate next step? If so, how to obtain it?

I suggest getting a new SSD instead of fighting this corpse of a SSD

I have other ssds and data recovery isn't a problem. Trying to bring this back to life

I am in the exact same situation as you, created an account just to follow up haha.

Did you happen to get any resolution?

I have a XBOX Series S I'm repairing, the SSD is not detectable at all, seems to be marked as 1MB, and the Xbox's CPU's are locked to the SSD, so I need to recover the 1st partition on this SSD in order to fix the XBOX. There is no alternative.

SSSTC XA1-31512, PN M1106374-007
Phison PS5019-E19-35 controller
SK hynix H25BFT8F5M3R NAND
Firmware currently reports EJRM01.2

From what I'm reading, I kinda wondered if I could simply flash a firmware upgrade onto the chip, to attempt to repair. :-/

No. People stopped helping

chasemdev, Take this drive to data recovery engineers, or you'll ruin it completely.
The first thing MPTool does when flashing a drive is destroy the data.

bluejay3246, I don't have a drive with these chips and don't have compatible firmware, so I can't really offer any advice. But the SSD itself is acting strange. The chip IDs are offset by 1 byte. This might be normal, but I doubt it. Most likely, there's something wrong with the controller.