I have a problem with my generic Phison USB.
Posted: January 19th, 2026, 23:40
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.)
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.)
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
