loader for kingfast SM2258XT available?

635 views
Skip to first unread message

Alandata Recovery

unread,
Jan 10, 2024, 7:00:27 PM1/10/24
to datarecoveryce.
I have had the MRT SSD option for a few years and have never been able to recover
a single SSD with it.
It all seems to come down to loaders that they dont have.

It ID's Has correct size, cant read data

pc3K Supported?

image.png

image.png

Here is what it looks like in normal mode

image.png

and in safemode
image.png

--
Alandata Data Recovery -  (949)287-3282  
"Cleanroom Data Recovery of RAID, VMware, NAS, Linux, Tape, Disk, Forensics"

pbzcbf...@gmail.com

unread,
Jan 10, 2024, 7:21:35 PM1/10/24
to DataRecoveryCertification

Alandata Recovery

unread,
Jan 10, 2024, 8:10:38 PM1/10/24
to datarecovery...@googlegroups.com
wow tons of info
thanks!


On Wed, Jan 10, 2024 at 4:21 PM pbzcbf...@gmail.com <pbzcbf...@gmail.com> wrote:
https://www.hddoracle.com/viewtopic.php?p=23124#p23124

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/datarecoverycertification/8e31c6bb-14d1-4543-afae-6848bf827017n%40googlegroups.com.

jol qwerr

unread,
Jan 10, 2024, 10:46:04 PM1/10/24
to datarecovery...@googlegroups.com
the last piture shows that LDR was loaded successfully
So next you've to rebuild the translator
n start extracting date
done!

jol qwerr

unread,
Jan 10, 2024, 10:46:51 PM1/10/24
to datarecovery...@googlegroups.com
Damn auto currect
Data*

pbzcbf...@gmail.com

unread,
Jan 11, 2024, 6:57:29 PM1/11/24
to DataRecoveryCertification
When you are choosing a loader, what do you look for?

FWIW, if you dump the 512-byte SMART attribute data sector of a working Silicon Motion SSD, you can see text strings which identify the controller, NAND and firmware version.


Alandata Recovery

unread,
Jan 12, 2024, 5:00:16 PM1/12/24
to datarecovery...@googlegroups.com
It looks like the nands are
Hynix 144L

I think I need a rom debug that matches
I have found these ROMDEBUG modules..

Thanks !

image.png
=========================

SSD state:
Wether it is in a ready state : ..............: Yes
Firmware working mode : ......................: LDR
SSD error code : .............................: 0x00(No error)
Whether SSD is locked  : .....................: No
Whether in safe mode : .......................: No
Whether access user area : ...................: No
Whether access SA  : .........................: Yes
Enter ROM Debug mode : .......................: success

View chip information...
Chip id : ....................................: 0xAD5E28221090
Vendor : .....................................: Hynix
Flash type : .................................: 144L QLC 16k

Chip capacity : ..............................: 68688 Mb
channel number : .............................: 4
Chip number per channel : ....................: 2
Chip layers : ................................: 4
Number of logical units : ....................: 1
Number of chip storage blocks : ..............: 0x4F8
Number of pages per storage block : ..........: 0x1B00
Page size : ..................................: 0x2000
Maximum retry level : ........................: 0x0

-------------------------------------
 Channel  Chip              Id
       0     0  0xAD5E28221090
       0     1  0xAD5E28221090
       1     0  0xAD5E28221090
       1     1  0xAD5E28221090
       2     0  0xAD5E28221090
       2     1  0xAD5E28221090
       3     0  0xAD5E28221090
       3     1  0xAD5E28221090
-------------------------------------
---End---
===============================

--
Data Recovery Certification Group / for issue with google group please email sc...@myharddrivedied.com
---
You received this message because you are subscribed to the Google Groups "DataRecoveryCertification" group.
To unsubscribe from this group and stop receiving emails from it, send an email to datarecoverycertif...@googlegroups.com.

Alandata Recovery

unread,
Jan 13, 2024, 3:24:24 PM1/13/24
to datarecovery...@googlegroups.com
I got it to start downloading the chip dumps
The first one took about 24 hours
and only totals 21gb
21gb x 8 chips = 168 gb

this is a 512 gb ssd - so it does not seem like this is working correctly.

==========================
Read data : ..................................: Channel:0, Chip:0, Block:0x04f2
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x04f3
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x04f4
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x04f6
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x04f7
Read successfully

Read data : ..................................: Channel:0, Chip:1, Block:0x0000
Read successfully
Read data : ..................................: Channel:0, Chip:1, Block:0x0004
Read successfully
Read data : ..................................: Channel:0, Chip:1, Block:0x0007
Read successfully
Read data : ..................................: Channel:0, Chip:1, Block:0x000a
Read successfully
Read data : ..................................: Channel:0, Chip:1, Block:0x000e
Read successfully

============
heres the setup
I loaded the default loader
then loaded a rom_debug module
image.png
After that it let me download modules, some got errors

Bootisp had some clues
------
image.png
image.png
image.png

===========
Selected family : ............................: Silicon Power Slim S55 (SM2258XT)
Master Controller model : ....................: SM2258XT

Chip id : ....................................: 0xAD5E28221090
Vendor : .....................................: Hynix

SSD state:
Wether it is in a ready state : ..............: Yes
Firmware working mode : ......................: ROM

SSD error code : .............................: 0x00(No error)
Whether SSD is locked  : .....................: No
Whether in safe mode : .......................: Yes

Whether access user area : ...................: No
Whether access SA  : .........................: No

Load loader...
Dafault Loader name : ........................: P0617B 58TLC_00
Werite default Loader : ......................: success
Load default Loader code : ...................: success
Obtain Loader version from firmware : ........:

Read Loader : ................................: Fail
Load loader : ................................: Fail

Basic SSD information:
Read chip information : ......................: success

Chip id : ....................................: 0xAD5E28221090
Vendor : .....................................: Hynix
Flash type : .................................: 144L QLC 16k
Chip capacity : ..............................: 68688 Mb
channel number : .............................: 4
Chip number per channel : ....................: 2
Chip layers : ................................: 4
Number of logical units : ....................: 1
Number of chip storage blocks : ..............: 0x4F8
Number of pages per storage block : ..........: 0x1B00
Page size : ..................................: 0x2000
Maximum retry level : ........................: 0x0

Load relocation block table : ................: Fail


Load CP list......
CP list data is not found in HDD, use the default CP list!


Load CP list... : ............................: success

Read password information...
Read password information : ..................: Fail

 Saving CP...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\ConfigParams\
Save module: 8000 : ..........................: OK
Save module: 8001 : ..........................: OK
Save module: 8006 : ..........................: ERR(Read Fail)
Save module: 8007 : ..........................: ERR(Read Fail)

 Saving CP...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\ConfigParams\
Save module: 8003 : ..........................: ERR(Read Fail)
Save module: 8004 : ..........................: OK
Save module: 0003 : ..........................: ERR(Read Fail)
Save module: 0004 : ..........................: ERR(Read Fail)
Save module: 0005 : ..........................: ERR(Read Fail)
image.png
 Module is backed up!

Backup firmware...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\Firmware\
Save ISP, Copy 00 : ..........................: OK
Save ISP, Copy 01 : ..........................: OK
Save ISP, Copy 02 : ..........................: OK
Save ISP, Copy 03 : ..........................: OK
Save BootISP, Copy 00 : ......................: OK
Save BootISP, Copy 01 : ......................: OK
Save BootISP, Copy 02 : ......................: OK
Save BootISP, Copy 03 : ......................: OK
---End---
The logical address cannot be accessed, and HDD ID cannot be editied!

 View password information
CP list data is not found in HDD, use the default CP list!
Read password information : ..................: Fail
Dump Flash chip...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\Dumps\
Starting block: 0x0000
End block: 0x04f7
Ignore service area : ........................: No
Read data : ..................................: Channel:0, Chip:0, Start Block:0x0000, End Block:0x04f7, Page:0x0000, Count:8792064
Abnormal error
---End---
Dafault Loader name : ........................: P0617B 58TLC_00
Werite default Loader : ......................: success
Load default Loader code : ...................: success
Obtain Loader version from firmware : ........:

Read Loader : ................................: Fail

Enter ROM Debug mode...


SSD state:
Wether it is in a ready state : ..............: Yes
Firmware working mode : ......................: LDR
SSD error code : .............................: 0x00(No error)
Whether SSD is locked  : .....................: No
Whether in safe mode : .......................: No
Whether access user area : ...................: No
Whether access SA  : .........................: Yes
Enter ROM Debug mode : .......................: success

 Saving CP...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\ConfigParams\
Save module: 8000 : ..........................: OK
Save module: 8001 : ..........................: OK
Save module: 8003 : ..........................: ERR(Read Fail)
Save module: 8004 : ..........................: OK
Save module: 0003 : ..........................: ERR(Read Fail)
Save module: 0004 : ..........................: ERR(Read Fail)
Save module: 0005 : ..........................: ERR(Read Fail)

 Module is backed up!

 Saving CP...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\ConfigParams\
Save module: 0005 : ..........................: ERR(Read Fail)

 Module is backed up!

Save service block...
Save path: C:\UserDataFile\SSD-Silicon Power-Silicon Motion\SM2258AB-80-10000000-20141211-(03)5526888-20080228-0xAD5E28221090_wah2\Data\SABlocks\
Starting block: 0x0000
End block: 0x04f7
Ignore service area : ........................: No
Read data : ..................................: Channel:0, Chip:0, Block:0x0000
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x0004
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x0007
Read successfully
Read data : ..................................: Channel:0, Chip:0, Block:0x000a

Alandata Recovery

unread,
Jan 13, 2024, 3:25:10 PM1/13/24
to datarecovery...@googlegroups.com
if anyone has a solution or suggestions - I will pay for support - Thanks

img

unread,
Jan 13, 2024, 4:21:55 PM1/13/24
to datarecovery...@googlegroups.com

I am not here for the money and maybe I'm on a wrong track but based on

  Channel  Chip              Id
       0     0  0xAD5E28221090
       0     1  0xAD5E28221090
       1     0  0xAD5E28221090
       1     1  0xAD5E28221090
       2     0  0xAD5E28221090
       2     1  0xAD5E28221090
       3     0  0xAD5E28221090
       3     1  0xAD5E28221090

shouldn't we have to seen different / unique chip IDs (4 of them at least)?


Alandata Recovery

unread,
Jan 13, 2024, 4:59:53 PM1/13/24
to datarecovery...@googlegroups.com
I think the chip ID is the model number of the chip It's not like the serial number... 

pbzcbf...@gmail.com

unread,
Jan 13, 2024, 6:47:54 PM1/13/24
to DataRecoveryCertification
0xAD 0x5E ... is a Flash ID that is returned by the chip in response to a particular command. 0xAD belongs to SK Hynix.

I found the attached FWTag.SET file in one of the MPTool packages at this site:


This is the line that most closely matches the NAND part number (H25QFT8B3A8R):

   Hynix,512Gbit,H25QFT8A1A8R(V4)=HYNV4

Therefore, ISTM that one of the following loaders would be the closest match.

; HY3D-V4:
SMI MPTool SM2258XT HY3D-V4 R0205A FWR0124A0 ; SM2258XT_HY3D-V4_PKGR0205A_FWR0124A0_20180301.rarsize: 995 988 bytes
SMI MPTool SM2258XT HY3D-V4 R0404A FWR0330A0 ; SM2258XT_HY3D-V4_PKGR0404A_FWR0330A0.rarsize: 888 664 bytes
SMI MPTool SM2258XT HY3D-V4 R1012A FWR1001A0 ; SM2258XT_HY3D-V4_PKGR1012A_FWR1001A0.rarsize: 939 441 bytes
SMI MPTool SM2258XT HY3D-V4 S0103A FWR1226B0 ; SM2258XT_HY3D-V4_PKGS0103A_FWR1226B0.rarsize: 878 119 bytes
SMI MPTool SM2258XT HY3D-V4 S0215A FWS0330B0 ; SM2258XT_HY3D-V4_PKGS0402A_FWS0330B0.rarsize: 882 636 bytes
SMI MPTool SM2258XT HY3D-V4 S0722A FWS0712B0 ; SM2258XT_HY3D-V4_PKGS0722A_FWS0712B0.rarsize: 1 116 467 bytes
SMI MPTool SM2258XT HY3D-V4 S0925A FWS0924A0 ; SM2258XT_HY3D-V4_PKGS0925A_FWS0924A0.rarsize: 1 153 270 bytes
SMI MPTool SM2258XT(AD) HY3D-V4 U0105A FWT1130A0 ; SM2258XT(AD)_HY3D-V4_PKGU0105A_FWT1130A0.rarsize: 1 321 041 bytes

I could be wrong, though.
FWTag.7z
Reply all
Reply to author
Forward
0 new messages