X230 “compatible but unsupported”

[ajbritain4]

Hey, having some issues flashing my X230 with this. The machine is running BIOS 2.60, EC 1.3. Have run 1vyprep before attempting the jailbreak.

The following are the result of attempting the BIOS mod on this machine - the results of the exploit are:

BIOS: G2ETA0WW
Version: 2.60
Flash size: 12288

Today the text in the first screenshot is giving the additional message “Warning: Can’t autodetect IBM/Lenovo ThinkPad X230, DMI info unavailable”

Thanks!

[digmorepaka]

Could you post the output of dmidecode -t system?

[ajbritain4]

Yes certainly - here you go:

Thanks!

[digmorepaka]

I see what's the problem. Your SMBIOS tables are kinda screwed up. 1vyrain expects "ThinkPad [Model]" in the Family line, you don't have that there. This is the first time ive seen a report of this so it is probably isolated. You can flash manually with the following chain of commands after it says that it is compatible:

dd if=/dev/zero of=/tmp/pad bs=1M count=8
cat /tmp/pad /root/bios/X230.rom > /tmp/12M.rom

/root/flashrom/flashrom -p internal:laptop=force_I_want_a_brick -w /tmp/12M.rom --ifd -i bios -N

[ajbritain4]

Perfect thank you for looking into it - that’s worked absolutely fine! Thanks so much

[ajbritain4]

Hi - just reopened this again as I am looking to flash with the LVDS patch this time around but the SMBIOS tables still seem to be incorrect. Are you able to advise on a way to flash with the LVDS patch by command line as above? Thanks!

[digmorepaka]

Same command but the rom is X330.rom.

[ajbritain4]

D’oh - sorry - thanks for the reply, I assumed it would be a patch applied on the fly! Cheers

[digmorepaka]

Discovered T530 with similar problem image

TODO: Fix autodetection for these rare cases where the model number is weird.

[digmorepaka]

https://termbin.com/33cr6

[mrbigmouth502]

I see what's the problem. Your SMBIOS tables are kinda screwed up. 1vyrain expects "ThinkPad [Model]" in the Family line, you don't have that there. This is the first time ive seen a report of this so it is probably isolated. You can flash manually with the following chain of commands after it says that it is compatible:

dd if=/dev/zero of=/tmp/pad bs=1M count=8
cat /tmp/pad /root/bios/X230.rom > /tmp/12M.rom

/root/flashrom/flashrom -p internal:laptop=force_I_want_a_brick -w /tmp/12M.rom --ifd -i bios -N

I just used this method to force a flash on my X230T, and it worked perfectly! I can't thank you enough for this. :)

[maximzxc]

@digmorepaka just for your info, I'm having the same issue, can't detect family, so used a similar workaround as you suggested and all works well, but after the flashing suspend stopped working, could it be related to SMBIOS tables issue that was mentioned above?

Also, most likely unrelated to 1vyrain, I have another issue -- sound card after booting is often not working, OS just can't detect it, nor on Windows nor on Linux, could it be also related to SMBIOS somehow?

[aristipp]

I see what's the problem. Your SMBIOS tables are kinda screwed up. 1vyrain expects "ThinkPad [Model]" in the Family line, you don't have that there. This is the first time ive seen a report of this so it is probably isolated. You can flash manually with the following chain of commands after it says that it is compatible:

dd if=/dev/zero of=/tmp/pad bs=1M count=8
cat /tmp/pad /root/bios/X230.rom > /tmp/12M.rom

/root/flashrom/flashrom -p internal:laptop=force_I_want_a_brick -w /tmp/12M.rom --ifd -i bios -N

I just used this method to force a flash on my X230T, and it worked perfectly! I can't thank you enough for this. :)

Same problem here, but flashing the bios manually worked without problems. Thanks for the good work!

[digmorepaka]

For anybody stumbling across this. This is NOT how you flash an incompatible UEFI version. This is how you flash a machine with a screwed up model number.

[HolimaX]

For anybody stumbling across this. This is NOT how you flash an incompatible UEFI version. This is how you flash a machine with a screwed up model number.

... so did it work or not? Comment seems it did, but the Bug is still open...

[digmorepaka]

... so did it work or not? Comment seems it did, but the Bug is still open...

Have not fixed the bug, workaround works. Very few seem to exhibit it thankfully. Should still fix it. Maybe some time,