[Solved] Kingston DT100 G3 32GB Flash Drive - Firmware Repair & Phison Tool Troubleshooting

Hello, I have a Kingston DT100 G3 32GB. The pendrive is almost new, but the write speed was terrible, so I figured that maybe it would format the memory on a low level, I ran the pendrive repair tool (phison format & restore) and the pendrive died
There is no data for recovery, the pen value is negligible. But I would like to know if a repair is possible anyway. I tried various versions of Phison MPALL to no avail, usually after setting everything up there was an error uploading the firmware etc. I simply bet that without the appropriate firmware, which is rather not available, I will not do anything ...

Before the surgery, it looked like this:


Po - pen visible only in USB 2.0, there is an unidentified device in 3.0:
[code:1:0b1a51cc81]
Description: [G:]Urządzenie pamięci masowej USB(13FE USB DISK 50X)
Device Type: Mass Storage Device

Protocal Version: USB 2.10

You have a choice:
1. RMA -> https://www.kingston.com/pl/company/warranty
or
2. Read -> https://www.elektroda.pl/rtvforum/topic3444498.html#17117218

Phison GetInfo will show the current ID_BLK Ver. , 1.4.6.0

From the link Restore does not detect full, UPTool crashes "Flash Fail 1" ID_BLK Ver. same zeros. RMA is missing, no proof of purchase.

Testmod now to be done:
"For PS2251-07 controller:
if 48PIN: 25-28PINS, sample 26 + 27
if 64PIN: 34-37PINS, sample 35 + 36 "

How to disassemble this flash drive, see the video:
https://youtube.com/watch?v=-ZzZsMfhmmo

Pen entered 2307 PRAM mode

In another version, MPALL can see what flash is, but whether in normal mode or PRAM it does not upload the firmware

sylweksylwina wrote:

Pen entered 2307 PRAM mode

How you think it's good or bad

Keep trying with this modification ST-TOOL -a -> ST-TOOL 9000 v3.7F.92 mod .
https://www.elektroda.pl/rtvforum/topic3596706.html#18057604

In testmode, basically nothing happens after clicking start:


in normal mode it shows like this, and after pressing start error 0x1049:





EDIT, I changed a few parameters in the config, now it hangs on IB check, I'll wait, we'll see what comes out of it.

Added after 3 [hours] 4 [minutes]:

So yes, I connected in testmode to USB 3.0, changed the configuration to 3.0 accordingly and did an autodetect when choosing pendrive IDs. It had ground and threw it out:



Now there is no message that the USB device is not recognized after connecting to port 3.0, only the pendrive immediately goes into testmode. I noticed that when you select Scan class HLF instead of L + H, it immediately crashes 0x1080

During the memory scan process, it finds a huge amount of bad blocks. The pendrive cannot be repaired.