I have a problem with my generic Phison USB.

[NelsonRomero]

Hi all, I have a problem with a PHISON USB drive: This USB was giving me writing protection issues for years and that is when I discovered the Phison Format & Restore software and they worked properly when I used them. However, I noted that the USB was slowly degrading because sometimes it disconnected itself (even if I had it plugged on the ports of the back) and the file transfer was slower; I really didn’t care because it was still working as intended.

It wasn’t until two months ago when the writing protection returned to the USB. Since it already happened to me before I knew that I had to use that program again, and when I was restoring the USB with Phison Format & Restore ver. 3.24.0.0 (the version that I always used to fix this) and used the “Restore” option it disconnected itself during the restoring: I always used to plug the USB on the ports of the back to assure that there were no issues related to “plugging the drive incorrectly” but this time it disconnected itself automatically. When this happened I unplugged it and plugged it again and Windows no longer detected it, using the Phison program gave me an error and none of the solutions available related to this error worked for me, so I searched in different websites and I found some Phison MP Tools programs, most of these had compatibility errors so I downloaded those that worked exclusively for my USB (P2251-07). The one that worked for me was the Phison ST-TOOL ver. 3.80.0E_2020.01.16 SZ… but it just happens that when I was setting my USB with that (without modifying the Firmware) there was a power outage in my house and when I turned on my computer again and checked the USB it no longer had its original technical name (USB DISK 50X) but instead had 2307 Boot ROM as its internal title and whenever I used that program again the process no longer worked.

Since the program didn’t work with the stock firmware, I tried to do the process with the other Phison MPALL programs that were compatible with the USB model and its parameters such as VID and PID, the only one that didn’t give me compatibility errors was Phison MPALL v5.030A and its variants such as 0A-DL7 0B-DL20 AND 0D-DL20 beta (all of these version 5.03.0). I got the CT ReadOnlyPage error with the stock firmware so I tried switching it to a new firmware (burn file is BN07V502TAW.BIN and firmware file is FW07V50253TW.BIN) and I got the CT- BurnErrorFile error. Since I was getting the error due to the burn file, I decided to change the burn file and it seemed to work (BN07V106M.BIN) but the CT Firmware Error appeared; no matter what I tried I would always get an error either on the burn file or the firmware file. I tried this with the Phison ST-TOOL ver. 3.80.0E that I used before, this time with the correspondent burn and firmware files, but had no luck; it doesn’t matter what version of Phison MPALL or ST-TOOL compatible with my USB I use nor the version of the burn and firmware files, I always got errors and the progress wouldn’t take off from the beginning (The only change was when I downloaded a burn and firmware file from Github, when I tried this with them the USB would instantly disconnect when I flashed it).

To conclude: Is it worth it to try and fix this USB, or should I buy another one? What steps do I have to follow if its possible to fix it? Like I said, I had no luck with any program (MPALL and ST-TOOL) nor .BIN files (Burn and Firmware) that were compatible with my USB, and the formatting software didn’t work either since it wouldn’t detect the USB. These days have been stressful because I don’t like to throw away tech stuff when it apparently stops working and evading any loss of time is worth it too; I’d like to know in which moment the USB was permanently damaged, when I was restoring it with Restore 3.24.0.0 or when the power outage happened while using Phison ST-TOOL? (I included a PDF file with references: The software I used, the errors I got, the USB model, images and data of the USB, as well as the respective files and parameters. I’m willing to receive any kind of answers. Thank you.)

Attachments

USB PICTURES_compressed.pdf

(1.59 MiB) Downloaded 54 times

[SWM]

Look for FW for Hunix memory. Try it on the Auto ISP first.
https://fex.net/ru/s/nozx93b

[NelsonRomero]

Look for FW for Hunix memory. Try it on the Auto ISP first.
https://fex.net/ru/s/nozx93b

What Firmware does i have to use? I tried in the Auto ISP and gave me the same error of CT-ReadOnlyPageData.

Attachments

[SWM]

Try this configuration:

Or switch to test mode.

[NelsonRomero]

Try this configuration:

The attachment PS2251_07.png is no longer available

Or switch to test mode.

It gave me this other error, So ¿How i can switch to test mode?

Attachments

[SWM]

This should help. Just remember to set it up as shown in the image above (except erase first).
I don't see any point in switching it to test mode yet—it's already in ROM mode. You need to choose the right utility (or bin and fw).

Attachments

MPALL_F1_7F00_DL07_v503_0A.7z

(1.29 MiB) Downloaded 56 times

[SWM]

Sorry, I think you've already tried this...

[SWM]

From ST-ISP.INI (MPAll 5.13) only:
[2307]
HV_PG_ED3_D1_HynixFirmware = 2307_D1_20160322.BIN
HV_BX_ED3_D1_HynixFirmware = 2307_D1_20160322.BIN

[SWM]

FLASH VENDOR: Kinston
MODEL: kingston DT50
VID: 13FE
PID: 5500
CHIP VENDOR: Phison
CONTROLLER: PS2251-07 (PS2307)
MEMORY CHIP: AD3A1803 -HYNIX (TLC)
MEMORY SIZE: 16
It's quite possible that there are no binaries on PS2307 and HYNIX (TLC)...

[SWM]

From usbdev.ru

Attachments

Firmware PS2251-07.7z

(719.91 KiB) Downloaded 49 times

[NelsonRomero]

Sorry, I think you've already tried this...

Yep, I tried that and is the same result, (From the image of Auto Burner and Firmware Error) And idk what is the correct BN and FW files.

[NelsonRomero]

From ST-ISP.INI (MPAll 5.13) only:
[2307]
HV_PG_ED3_D1_HynixFirmware = 2307_D1_20160322.BIN
HV_BX_ED3_D1_HynixFirmware = 2307_D1_20160322.BIN

I got an error with these settings, thus i think its a compatibility error.

Attachments

new_error.PNG (9.33 KiB) Viewed 1155 times

[NelsonRomero]

FLASH VENDOR: Kinston
MODEL: kingston DT50
VID: 13FE
PID: 5500
CHIP VENDOR: Phison
CONTROLLER: PS2251-07 (PS2307)
MEMORY CHIP: AD3A1803 -HYNIX (TLC)
MEMORY SIZE: 16
It's quite possible that there are no binaries on PS2307 and HYNIX (TLC)...

So, if the USB has no vital data does that mean its no longer recoverable? (Here is other data related to my USB, With the UsbDriveInfo Software)

Attachments

[SWM]

OS information is useless for repairs. Then GetInfo.exe is better.
Now all that's left is to try UPTooL...
https://www.cryptoprofi.info/?p=18268
For PS2307 and Nynix TLC, the only online queries are for MPTool resources. I haven't found a solution.

Attachments

UPTool_Ver2094(Release)_20150909.7z

(1.32 MiB) Downloaded 32 times

[NelsonRomero]

OS information is useless for repairs. Then GetInfo.exe is better.
Now all that's left is to try UPTooL...
https://www.cryptoprofi.info/?p=18268
For PS2307 and Nynix TLC, the only online queries are for MPTool resources. I haven't found a solution.

Wow I had never heard of UPTool before, I tried it, but it doesn't seem to be compatible with my USB (I say this because the message appears in red, and when I click “START,” nothing happens). And about GetInfo, here are some images that may be useful.

Attachments

[NelsonRomero]

OS information is useless for repairs. Then GetInfo.exe is better.
Now all that's left is to try UPTooL...
https://www.cryptoprofi.info/?p=18268
For PS2307 and Nynix TLC, the only online queries are for MPTool resources. I haven't found a solution.

Wow I had never heard of UPTool before, I tried it, but it doesn't seem to be compatible with my USB (I say this because the message appears in red, and when I click “START,” nothing happens). And about GetInfo, here are some images that may be useful.

, My bad! I'm sorry, Here is the actual info of GetInfo

Attachments

[SWM]

I wonder what this one will write.

Attachments

UPTool_Ver2094(AD3A1803)_20150909.7z

(1.32 MiB) Downloaded 48 times

[NelsonRomero]

I wonder what this one will write.

The blue text appears, So is compatible with the USB, but when I click "START", the program closes automatically after 5 seconds, I think it's because the configuration by default, is not the same as the USB (I think so).

Attachments

UPTool_Compatible.PNG (11.19 KiB) Viewed 958 times

[SWM]

Unable to find complete information on the memory chip... Last option...

Attachments

UPTool_Ver2094(SWM)_20150909.7z

(1.32 MiB) Downloaded 35 times

[NelsonRomero]

Unable to find complete information on the memory chip... Last option...

When I run the process with this version of the program, I get this errors and the Windows warning that appears when the device is not detected, and I notice that the USB automatically disconnects every time I try to flash. I'm already giving up on this USB...

Attachments

Final2.PNG (4.19 KiB) Viewed 909 times

Final.PNG (2.75 KiB) Viewed 909 times