EEPROM WRITE PROTECTED
I just replaced a system board on a Lenovo T410 Thinkpad. Type 2537. When running the maintenance disk (version 1.78) to change the serial number and system type on the system board I get the error message that the EEPROM is write protected. It suggests I restart holding the ESC key, etc. but when I do that, there isn't an option to unlock the EEPROM. Any suggestions on how to proceed will greatly be appreciated. I have tried scanning through other forums but no one seems to have a definite answer.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I suggest returning the new motherboard as DOA.
The EEPROM is probably faulty, or not seated properly.
Manual - http://download.lenovo.com/ibmdl/pub/pc/pccbbs/mobiles_pdf/45n3577_01.pdf
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
unfortunately ,there aren't any of those either. . . and believe it or not, calling Lenovo tech support directly didn't provide any help. I couldn't believe that when he told me they don't help with that type of issue.
ASKER
It turns out that the hard drive was encrypted. I'm not sure why this mattered but I was finally able to get in touch with Lenovo tech support and they told me if the customer's hard drive had been encrypted (which it was) then I would get that error. They said the only way around it was to send it back to the company's IT department and have them reimage the drive and let them put the serial number on the board themselves or send it in to Lenovo and then have the customer contact them. Of course, the customer sent the laptop in for reimaging, and i sent them the software to put the serial number on the board. Thanks for all of you who sent in suggestions.
ASKER
Both of the answers provided were valid answers provided that it was the particular issue I was having. I was having a unique issue that no one could have expected or knew about unless directly worked for Lenovo or actually had that issue before.
ASKER