Cara Memperbaiki Flashdisk Yg Write Protect Menggunakan CMD. Cara memperbaiki flashdisk minta format dengan CMD (Recovery RAW). Cara Mengatasi Flashdisk WriteProtect Dan MEMATIKANNYA.

I have a USB which is write protected: dmesg tail [89] sd 7:0:0:0: [sdb] Write Protect is on [98] sd 7:0:0:0: [sdb] Mode Sense: 23 00 80 00 [79] sd 7:0:0:0: [sdb] No Caching mode page present [88] sd 7:0:0:0: [sdb] Assuming drive cache: write through [18] sd 7:0:0:0: [sdb] No Caching mode page present [25] sd 7:0:0:0: [sdb] Assuming drive cache: write through [35] sdb: sdb1 [09] sd 7:0:0:0: [sdb] No Caching mode page present [15] sd 7:0:0:0: [sdb] Assuming drive cache: write through [21] sd 7:0:0:0: [sdb] Attached SCSI removable disk How can I turn the write protection off? What I've tried • Checked if it has a hardware switch - no • Tried to format it on windows and on Linux (via terminal too) • Tried fdisk chmod • Tried to fix this with several tools from Ubuntu software center • Used Google and have seen about 10,000 discussions about this problem but they were never solved Additional information fsck -n /dev/sdb1 fsck from util-linux 2.19.1 dosfsck 3.0.9, 31 Jan 2010, FAT32, LFN There are differences between boot sector and its backup. Differences: (offset:original/backup) 65:01/00 Not automatically fixing this. Free cluster summary wrong (968250 vs. Really 911911) Auto-correcting.

Leaving file system unchanged. /dev/sdb1: 50 files, 564 clusters fdisk -l Device boot.

Start End Blocks Id System /dev/sdb1 4030448 b W95 FAT32 umount /dev/sdb1 mkfs -t vfat /dev/sdb1 mkfs.vfat 3.0.9 (31 Jan 2010) mkfs.vfat: unable to open /dev/sdb1. @lliseil It's more than likely the reader's write protect switch is being pressed upon by the card inserted into it, normally by the tab on the card but the switch (not the tab) can become bent and stuck on. You can fix the sdcard reader by cutting off the write-protect switch pins, the ones that make physical contact with the lock tab on the card.

When the switch in the reader is open, write-protect is off, when it is closed (by being pressed upon the the tab on the card) write protect is on. Removing one or both of the switches metal arms will permanently disable write-protect on the reader.

– Dec 6 '16 at 0:49. After researching your question it appears that this is a not-too-uncommon problem with certain brands of USB flash drives (some older Samsung, a Kingston model) that would essentially just 'crap out' for no known reason. People had tried opening them and jumping two leads (maybe from a flaky switch?) to no avail. If you still have this drive and it's still in warranty I'd return it and get a replacement. I hate to break the bad news to you = but it appears you're out of luck in this situation as everything I've read points to hardware failure. Edit: I experienced an issue personally with a flash drive flaking out on me recently.

In my case, this was a Corsair Flash Voyager 128GB that started slowing down pretty drastically on me. While it didn't show the symptoms noted here, it occasionally would not mount and showed up as a 'Silicon Power' device. This was a result of the drive having accrued a large amount of bad sectors and dropping into diagnostic/programming mode. Since this is one of my more popular answers and this also falls into the category of 'failing flash drives,' I figured I'd include it here for reference. Angel's answer is good, but the actual commands weren't so easy for me. Lemon tree fools garden lyrics meaning.

This is what worked: Plug in the card (mine is an SD card with a manual write-protect switch on it, but the switch is off and it is writable on a Windows machine). Ubuntu mounted it automatically on /media/andrew/6AB0-1FD91, and dmesg showed the partition to be /dev/sdb1. Unmount it, and make it writeable sudo umount /dev/sdb1 sudo hdparm -r0 /dev/sdb Create a new mount point and mount it there (my userID from /etc/passwd is 1000) sudo mkdir /media/andrew/temp sudo mount -o uid=1000 /dev/sdb1 /media/andrew/temp it'll still complain that it's read-only. I don't know why I had to change this flag before AND after mounting, but that's the only way it worked for me.