False Read-Only-Flag on USBstick

  • SpinRite v6.1 Release #3
    The 3rd release of SpinRite v6.1 is published and may be obtained by all SpinRite v6.0 owners at the SpinRite v6.1 Pre-Release page. (SpinRite will shortly be officially updated to v6.1 so this page will be renamed.) The primary new feature, and the reason for this release, was the discovery of memory problems in some systems that were affecting SpinRite's operation. So SpinRite now incorporates a built-in test of the system's memory. For the full story, please see this page in the "Pre-Release Announcements & Feedback" forum.
  • Be sure to checkout “Tips & Tricks”
    Dear Guest Visitor → Once you register and log-in please checkout the “Tips & Tricks” page for some very handy tips!

  • BootAble – FreeDOS boot testing freeware

    To obtain direct, low-level access to a system's mass storage drives, SpinRite runs under a GRC-customized version of FreeDOS which has been modified to add compatibility with all file systems. In order to run SpinRite it must first be possible to boot FreeDOS.

    GRC's “BootAble” freeware allows anyone to easily create BIOS-bootable media in order to workout and confirm the details of getting a machine to boot FreeDOS through a BIOS. Once the means of doing that has been determined, the media created by SpinRite can be booted and run in the same way.

    The participants here, who have taken the time to share their knowledge and experience, their successes and some frustrations with booting their computers into FreeDOS, have created a valuable knowledgebase which will benefit everyone who follows.

    You may click on the image to the right to obtain your own copy of BootAble. Then use the knowledge and experience documented here to boot your computer(s) into FreeDOS. And please do not hesitate to ask questions – nowhere else can better answers be found.

    (You may permanently close this reminder with the 'X' in the upper right.)


New member
Aug 26, 2021
Hello generous people.
I have this case with a Kingston USB stick on which it was accidentally disconnected from the notebook connector while copying file.
After that it became Read-Only, which means that I can not format, or repartition it not even with initDisk.

I come here to post because I see a deep knowledge.
Most answers that I get are about it going to end-of-life.
But this happenes with a disconnection and then communication data was corrupted.
Then in my understanding it should be reparable by software.
But no software outthere seem to solve this.
I don't think that is an electronic fusible burned out with current inside.
I feel that a part of the equation is missing.

Thanks in advance !!

I am seeking for the knowledge.
I thought I clarified with the equation analogy.
This is totally software related.

However, the link that you gave is not 5usd is about 37usd:
US$ 4.99 + US$ 31.58 (between shipping and taxes)
Any missused dollars are better expent as donation for the multiple world crisis this days.
Hi DiskTuna.
Thanks to your Tips, I was able to do a big step.
I got to those vague chinese and rusian websites and with help of chrome translator I got to download ChipGenius + GetFlashInfo + GetInfo and confirm that a Phison chip PS2251-03 and there is corruption and the WriteProtection flag and some others as it can be seen in GetInfo from the chip-manufacturer company. http://dl.mydigit.net/special/up/phison.html
(Luckly I worked manufacturing LED TVs so I am familiar with the vague information)

I am attaching the file that I was able get so far.
Windows's diskpart tool shows “Current Read-only State: Yes” which matched with file "GetInfoPartitionSetting.PNG" showing corrupted "Write Protect Status" field.
I don't fully understand how is this zone enabled to be writable at all. It would mean that any software can read and write to it, but none seem to offer that feature. Probably because of the discardable-price.

I am not sure how to continue from here since GetInfo tells me the firmware version is MPALL v3.27.0A and there is no download available for that version. Probably there is an upgraded compatible firmware. I have downloaded many of them but I cant figure it out which one may be compatible.

I think that if I get to edit the field "Write Protected Status" with an aceptable value copied from another working usbstick, then the device can get recovered. It is not unwritable, it just have a corrupted flag.

If you have any more clues, I would appreciate it so I can possibly reach a further conclusion out of it.


  • Kingston16GB_WriteProtected.zip
    355.7 KB · Views: 276