Bios write protected error

bios write protected error

You don't. Once the drive is dead, it's dead. The drive is bad. Write protected mode is a safety feature to hopefully allow you to recover. Hello all,. after many successfull changes, the phoenix bios became "write protected" (near than 6 error messages when i want to save. Error: BIOS is write-protected. Help The bios doenst has any option of disable-enable write-protection. How can i flash it? Thanks.

Bios write protected error - apologise

How should I format/repair a write-protected laptop SSD with I/O errors?

Flash chips are limited to writing information onto blank pages. Although flash drives can erase and reuse areas of storage, this is a relatively slow process, and is limited to erasing fairly large blocks of memory (typically e.g. 512 pages of 528 bytes) at a time. While it would be theoretically possible to design a flash drive that would respond to a write requests by erasing the old data and then immediately reusing the same storage, no practical drives do that. Instead, they will write the new data to a new location, and record somewhere the facts that the data should be read from a new location, and that the copy in the old location is no longer needed. When the drive is idle, it will find the blocks that have the largest number of obsolete pages on them and erase them in preparation for reuse.

All of this can work very well and very efficiently provided that the mechanisms the drive uses for storing book-keeping information remain reliable. If the bookkeeping information becomes corrupted, however, the drive may erroneously reuse blocks that hold live data. This would obviously be bad if the drives hold user data, but can be downright disastrous if the blocks hold bookkeeping data.

Although quality drives should maintain bookkeeping data with enough cross-checks to minimize the likelihood of data loss in case part of it gets corrupted, there are limits to the amount of cross-checking that drives can do while maintaining a reasonable level of performance. Consequently, if corruption is detected, many drives will enter a "safe mode" to avoid any possibility of further corruption.

A nasty quirk of flash memory, btw, is that if a block of memory has been erased a certain number of times, it may get into a state where reading it immediately after writing will correctly yield the data written, but bits may spontaneously change later after month or so. When everything is working correctly, drives will keep track of how many times each block has been erased and will cease trying to use a block once it has been erased too many times. If a drive's bookkeeping information gets corrupted, however, it will have no way of knowing how many times blocks have been erased, and thus have no way of knowing which blocks are safe to use. Worse, it will have no way of knowing whether any particular block that it has just written will be reliable for any meaningful length of time.

If one has data recovery tools that know how the bookkeeping information for a particular drive is stored, they may be possible to do a much better job of recovering drive contents than would be possible using normal methods of reading and writing. If a drive has both a "current" and "obsolete" copies of a a few blocks of bookkeeping information, for example, and some of the information that was corrupted on the current copies is correct on the "obsolete" ones, a data recovery tool may be able to use different combinations of old and new data to see if any of them "make sense" when looking at the drives' contents as a whole. A drive would not have enough RAM and CPU horsepower to accomplish such things, but specialized data recovery tools could. Because different drives use different bookkeeping approaches, however, I would expect the necessary tools to be highly specialized and for many types of drive might only exist on if a data-recovery specialist has needed to create one.

answered Sep 11, 2020 at 15:37

user avatar
supercatsupercat

1,71999 silver badges88 bronze badges

Carnegie Mellon University's Computer Emergency Response Team (CERT) has issued a security bulletin regarding a vulnerability found in many BIOS firmware implementations. If exploited, an attacker would have the ability to flash your motherboard's BIOS.

x86-based computers employ a number of security measures to protect the BIOS from attacks, one such measure being write protection. A chipset's register includes a pair of bits that either enable or disable write protection. When the bit is on, BIOS write protection is enabled; when it's off, it's disabled.

The default state of the bit is disabled. When a system is turned on, it's up to the BIOS to enable write protection. The issue arises when a system is put into sleep mode.

This mode is treated like a system reset which sets the write protection state to disabled. As mentioned, the bit is set to "on" during a normal startup but when waking from sleep, there's no mechanism to set the bit back to enabled and thus, write protection remains disabled.

CERT points out that devices from Apple and Dell are both impacted by the flaw. Apple began issuing updates to correct the matter on June 30 while Dell has provided CERT with a list of vulnerable devices. It also lists a number of other PC makers although their status is as unknown as of writing.

The best course of action at this point is to check with your motherboard vendor to make sure you have the latest firmware updates (and to keep checking back if the issue hasn't yet been addressed by your board maker).

Image courtesy Tom's Hardware

Keep Reading

Top Stories

TechSpot Video: Strange But True Tech Facts

thanks in advance for reading this post and for any reply or help ;)



i have a msi 845 pro and i made a mistake by reseting de bios putting the jumper in resenting mode with the main power on so

i have corrupted the information of my bios and it stops at the initialization of the keyboard controller "i know this cause

the motherboard has 4 leds indicating problems in the POST.

Now a have another pc matsonic ms8308ep(266)so i start it with a DOS diskete then i remove the bios from it and replace for

the msi 845 pro bios to make the flash but...i cant flash it cause by default the msi 845 pro bios is write protected.

can you guys help me with this? to bypass this write protection?

i´m using these tools:
http://www.msi.com.tw/program/support/b ... =89&kind=1
i tryed with all the releases, but almost at the end of the rom loading it stops and says: flash rom erasing error

2 of the names of the images im trying to load to the bios are:1st realease "A6529IMS.100" latest release "A6529IMS.130"

i´m only asking for a flag or parameter to put after "amifl827.exe" or if you can give a link to some manual or tutorial to

help me in this crusade ;)

or a program that gives me access from dos or windows to the cmos of the bios to disable the flash write protection ;)"like

winbios http://english.aopen.com.tw/tech/techinside/WinBIOS.htm" i dont have winbios so i dont know if it works with my

boards

ps-both boards have amibios ;)

waiting eagerly for any answer if possible ;)


regards
satanic

Win-Raid Forum

Hey Guys ,
i am Lara from Germany i say hello to all here :wink:

I have a Problem with my Uefi . I have are HP 8560p Elitebook with Intel i7 Prozessor .
I can not upgrade my Uefi , because the previous owner from the HP 8560p , has write protection set.
I have the newest Uefi file from HP . In the Logfile is are error message : Uefi can not installed ,write protection set …

Now i have found the program CHIPSEC .
I working on this for 1 Week . I have all instructions i from here befoling:

  1. Create the USB with Boot Efi File
    https ://chipsec.github.io/USB%20with%20UEFI%20Shell.html
    This not working , the instructions was correctly executed.
  2. Create the USB from this instructions :
    www. basicinputoutput.com/2016/05/a-tour-of-intel-chipsec.html
    Also these detailed instructions not working with USB Start.

Now i think this is another problem in the UEFI Settings .
I have Windows 7 and Windows 10 for working this problem installed in Uefi Modus.

Can someone help me solve this problem .

The program CHIPSEC runnig in Windows 10 , I just don’t know how to get it to work :frowning:
I have the program Python 3… and Chipsec from Githup “Master file” downloaded , see here :
https:// github.com/chipsec/chipsec

Can anyone help me CHIPSEC Runnig in Windwos 10 with python with professional instructions please :slight_smile:
Or have anyone are idea , why not chipsec stardet with the USB instructions .

Greetz Lara

Edit by Fernando: Unneeded blank lines removed (for better readability and to save space) and thread title customized
grep wpsw wpsw_cur = 1 # [RO/int] Firmware write protect hardware switch current position

A value of indicates that write protection is enabled.

Software Write Protection and Write Protection Range Status

To check software write protection and write protection range status, run the following commands. Note that the write protection range is independent from the software write protection status (if sw write protection is disabled, it means you can manipulate the protection range).

  • EC:
  • AP:

If PD (Power Delivery) firmware is present, this additional command can be run:

  • EC:

Disabling write protect

The typical sequence for disabling write protection is to disable hardware write protect, disable software write protect, and clear the write protection ranges.

Disabling hardware write protect

Write Protect Screw

  • Power down the device and open the case
    • Locate and remove the write protect screw on the motherboard.
  • Restart the device

Cr50

  • Use Servo to connect to the Cr50 console
    • Enter the chroot with
    • Ensure servod is running with if necessary.
    • Run to discover the pty file for the console.
    • Connect to that console with minicom, cu, or screen.
  • Perform the “CCD open” process to enable functionality.

If you don‘t want to go through the CCD open process or don’t have a suzyQ, you can open the case and remove the battery to disable hardware write protect.

  • Disassemble the device, locate the battery connector, remove the battery connector from the PCB to disconnect the battery.
  • Reassemble the device, insert the original OEM charger (necessary since the battery is no longer providing power to the system), then boot to developer mode.

Servo Header

Servo when connected can override the native write protection (either using the write protect screw or the security element). For systems with a servo header:

  • Connect servo board to the Chrome OS device
  • Enter the chroot with
  • Start servod inside the chroot:
  • Force write-protect on via the servo header: .

In all cases, after the device is back up, verify that write protection is disabled by running , it should now output .

Disabling software write protect

NOTE: You cannot disable software write protect if hardware write protect is enabled.

  • Run .
  • Run . If message is displayed, check if the write protect screw has been removed. Do an EC Reset.
  • For devices with PD,
    • Samus: .
    • Glados: followed by and .

Disabling the Protected Range

NOTE: You cannot manipulate the protected range (BP bits) if software write protect is enabled.

  • flashrom -p host --wp-range 0x0 0x0

TODO(kmshelton): Make this less brittle by replacing with a reference to the flashrom man page (once it covers wp-range).

Enabling write protect

Enabling hardware write protect

Hardware write protect can be controlled by 3 different mechanisms:

  • A write-protect screw, when present,
  • Cr50 firmware, when present, and
  • A pin on the servo header, when servo is connected

Write Protect Screw

For systems with a write-protect screw:

  • Power down the device and open the case
  • Insert the write protect screw on the motherboard.
  • Restart the device
  • should now output

Cr50

For systems that use Cr50, you can control it on the device itself:

  • Run to check the current system (look for “Flash WP”).
  • If CCD factory mode was enabled, run to enable WP protect.
    • This command will fail if factory mode is not enabled. Newer Chrome OS versions allow to enable flash write protection by running
  • See also the internal crosops docs.

Or you can control it with a suzyQ:

Servo Header

  • Connect servo board to the Chrome OS device
  • Enter the chroot with
  • Start servod inside the chroot:
  • Force write-protect on via the servo header: .

Enabling software write protect and specifying the RO region as the protected range

For AP firmware,

flashrom -p host -r /tmp/bios.bin fmap_decode /tmp/bios.bin

and locate the section in the output.

  • Run . Example:
flashrom -p host --wp-enable --wp-range 0x00000000 0x00200000

For EC firmware,

  • Check WP range
    • Run .