Full what ? This is the Bios Region Backup !!! like before !
There needs two files read from any Eerom Chip so :
--- Flash Devices Found ---
MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)
1. 8192 KB MX25L6405D
2. 4096 KB MX25L3205D
Then the wor will be possible !
Regards
(05-08-2015, 02:57 AM)BDMaster Wrote: [ -> ]Full what ? This is the Bios Region Backup !!! like before !
There needs two files read from any Eerom Chip so :
--- Flash Devices Found ---
MX25L6405D ID:0xC22017 Size: 8192KB (65536Kb)
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb)
1. 8192 KB MX25L6405D
2. 4096 KB MX25L3205D
Then the wor will be possible !
Regards
Sorry I understand now. You need the dump from both files. I only upload Bios region (8192 KB MX25L6405D).
How do I dump (4096 KB MX25L3205D)?
You wrote " Waiting for the EEPROM Programmer and SOIC8 Test Clip to come in.... "
So I thinked You are using the SPI Programmer to read the chips !
It's possible only using SPI PGM !
Regards
(05-09-2015, 05:27 AM)BDMaster Wrote: [ -> ]You wrote " Waiting for the EEPROM Programmer and SOIC8 Test Clip to come in.... "
So I thinked You are using the SPI Programmer to read the chips !
It's possible only using SPI PGM !
Regards
Yes I have EEPROM Programmer and SOIC8 Test Clip. I tried to read chip but keep getting error:
[
attachment=8553]
So I desolder the chip and tried to use SOIC8 Test Clip but same error. I think the SOIC8 Test clip is BAD.
I put chip on PCB and reads good.
Here is file
MX25L3205D ID:0xC22016 Size: 4096KB (32768Kb) file
(05-13-2015, 03:31 AM)BDMaster Wrote: [ -> ]Here you go :
http://rghost.net/7jVWT6BBb
Let me know
Regards
Donate to me . . . look into my Signature 
Thank you BDMaster!
I flashed the chip, soldered it back to systemboard, and crossed my fingers. Everything works!
Transfer speed comparison:
Before @ 144mbps:
[
attachment=8568]
After @ 866.7mbps:
[
attachment=8569]
Cheers!
I want to report success using your methods and files - indirectly. I also used a RasperryPi with a $5 SO8 clip and the flashrom tool.
I'm no x86 guru, but fully understood the rest of the procedure. The part I needed to work out was the actual BIOS modification:
- I used PhoenixTool to compare the changes between JimmyZ's original upload and BDMaster's modified version of 2.63. I found the 7904 byte module that was changed to remove the whitelist.
- Next, I analysed a software tool dump of my original Lenovo 2.59 bios and found the same 7904 byte module with the same MD5 as JimmyZ's - different filename though. Finally, I updated to Lenovo's standard 2.64 BIOS, dumped the result and found the same 7904 byte module with the same MD5 and same filename as JimmyZ's. Lenovo apparently doesn't change this code too often.
- Using PhoenixTool, I merged BDMaster's modified module into my 2.64 dump.
The SO8 clip worked very well for in-circuit programming. I left VCC/3.3V disconnected, using just MISO, MOSI, CLK, CE and GND. These data lines have resistors between the flash chip and the Intel chipset, meaning you will have no problem driving the flash chip directly in-circuit.
The X230 will power up the LAN/flash 3.3V domain with the computer turned off
if Wake-On-LAN is active and an AC source is plugged in. You need to activate WoL in the BIOS and (in my experience) plug in a live Ethernet cable. If the X230's RJ45 lights are on then the flash chip will be supplied with a safe 3.3V in the way that Lenovo intended.
PhoenixTool method:
https://www.bios-mods.com/forum/Thread-S...0#pid62410
RaspberryPi flashrom:
https://github.com/bibanon/Coreboot-Thin...spberry-Pi
The standard 8-pin SOP package from the MX datasheet quoted on the Coreboot page applies to the X230.
I tried flashrom SPI speeds of 512KHz and 2048KHz. Both worked 100% reliably.
Nice work
Many thanks for your report my friend !!!
Regards