w550s/t550 LCD screen replacement - brightness set at max.

Not all would end up in Lenovos and, of those that would, not every customer would complain to their lcd dealer about a (minor) brightness-control issue only. There's also the fact that a B140HAN01.2 with the LEN edid won't have any issues (so an ex-Lenovo or Lenovo stock).

Not yet, but could make one. Only, it'd be simpler than the wifi white-list; edid-substitution only.

The Linux driver may look only at the panel's edid, not at the white-list. You could check how it's reported and verify it's an actual AUO.

Yes, but Intel HD blocks that route. One way to circumvent that would be to intercept the edid in RAM (using WinDbg and a direct-in-RAM editor), but that's even harder to do than making/flashing a hacked bios. Or ... perhaps, the ' safe-boot' -> ' overwrite registry' -> ' set registry permissions' trick may work (few posts back).

 

Didn't work with the "registry permissions" trick.
Each time the graphics driver is installed, the EDID is overwritten with AUO123D.

 

Hey, let me know if you was succeeded with the modded BIOS.

I've contacted intel before, and they told me maybe lenovo modded the original intel driver. But i've tried the original intel driver (from intel's website) and it doesn't work with that one too... So i think it was just a ********.

I've tried to contact lenovo, but failed because they do not try to help me in anything. So disappointing...

So anyway i think the best would be to modify the edid in the screen, but it's write protected. I don't know how to release it. We've reached a point with t456 but after stuck.

Anyway, it doesn't matter what we think about one thing is clear:
It works perfectly with linux and in bios without any issue! Always remember for this. So the laptop is 100% compatible with our screen, so it's only a driver issue...

 

Ok.
I just checked and I can't change brightness in BIOS.
It works only in Linux.

[EDIT] My mistake, it's working on BIOS too

 

Yes, and regarding that write-protect:

Instead of i2cdump, let's try i2cget this time:

Code:

i2cget 6 0x37

That's assuming the lcd is still on bus 6. That isn't a given, so check that first. Anyway, if that is the wp-byte then this would disable it:

Code:

i2cset 6 0x37 0x00

Only, that's quite a gamble without knowing the actual eeprom. If it's vcom then changing this value changes the voltage to the backlight. Something like 0x46 would be perfectly safe then, but 0x00 would result in a very messy screen (or even unreadable). Now, the eeprom can be checked by removing the black wrapper plastic and penning down the markings of all chips looking similar to this:

Spoiler: eeprom chip

Of course, if you feel really lucky, then try i2cset and write-edid.sh right after that. If successful then you have the LEN edid and brightness control should work after driver re-install. Make sure to use ' i2cset 6 0x37 0x48' right after write-edid.sh, whether this was working or not.

Come to think of it, it would be better if @mika91 checks with i2cdetect and i2cget first; if it's indeed vcom then the value could be slightly different from '48' (since every panel is different). If it's the same, then chances are better it's the write-protect.

 

My panel 0x37 value is 0xa7 this morning. (I changed brightness in bios)
Yesterday, I'm pretty sure it was another value.

So I tried a "i2cset 6 0x37 0X46"
Just after, I run a "i2cget 6 0x37".
The value is still 0xa7 !

 

How quaint ... since you're in Ubuntu and brightness control works; up/down brightness and re-check with i2cget?

Values:

Code:

hex     A7
binary  10100111
decimal 167

hex     48
binary  01001000
decimal 72

 

Ok, I'll try tonight.
Just to be sure, I don't need to make run "i2cdetect" or "i2cdump" after each brigthness changes?
"i2cget" read values on-the-fly, right?

 

Correct.

 

So the first try: 0xb7
and after another reboot, 0xa7 !

Changing brightness when I'm on linux doesn't change the value

 

Do you feel adventurous ?

Code:

hex     A7
binary  10100111
decimal 167

hex     B7
binary  10110111
decimal 183

hex     46
binary  01000110
decimal 70

This is just an educated guess (without knowing the actual eeprom), but these two examples work in roughly the same way:

Spoiler: eeprom write-protect methods

With these two, changing bit #7 to '0' first enables you to set 'wp = off' for the specific memory blocks. Assuming the 0x37 address is the write-protect byte and the edid eeprom works similar to the examples above (big "IF"s), then changing its value from A7 to 46 would've changed nothing with either if their write-protect pin (physical pin on the eeprom) was set to wp=on status (whether shorted to ground or voltage).

Doesn't look good ... but:

Code:

i2cset 6 0x37 0x27
i2cset 6 0x37 0x23

The first would set only the BPL/SRP0 bit to '0', permitting changes to bits #2-5. The second would set all wp sector bits to '0', disabling write-protect. But only IF the eeprom pin allows for this. When i2cget shows the values have stuck, then you could use write-edid.sh again, except successfully this time. Afterwards you'd want to set back the wp-byte:

Code:

i2cset 6 0x37 0x27
i2cset 6 0x37 0xA7

Dangerous stuff, though; could brick display. May want to leave this to @grosmar instead , considering the ' it's only a $80 display' remark. That would need a different hex value, btw:

Code:

i2cset 6 0x37 0x40

Only needs one i2cset, as bit 7 is already '0'. Chances are better for this panel anyway, if it's indeed, as it seems, permitting you to change bits #2-5 regardless of how the eeprom is hooked up.

 

Didn't work
It's still write-protected.

Thanks for your efforts @t456, but it looks like there is no solution to make this panel works under windows. Too bad...

 

is the QHD screen a drop in upgrade from the 1080p?

 

No, that needs 4-lane eDP, this is 2-lane. Minimum is a 4-lane cable, but the motherboard connector also needs to support the extra two lanes (four additional pins). This is unlikely, unless there's a similar Lenovo model that features a WQHD panel (or higher).

 

Nobody found a solution?

 

Guys, might not be the best solution, but i had the same issue on a t450, upgraded to a auo b140han01.2 specifically. the brightness control works in bios, but in windows that is totally borked and not working.

however, ive tried using redshift gui application and you can manually set the brightness then. it will revert back if the pc starts again or the app closes, but its very easy to reset that. i am in no way affiliated. ive tried ibrightness but that didnt work under windows 10

http://sourceforge.net/projects/redshiftgui/

 

Has anyone got to the bottom of this issue yet? I have a T550 with a 1920 x 1080 TN panel and I would really like to swap is for something better! Just one thought, is the brightness issue to do with the fact that a 1080 panel is being replaced with a 3k panel or is it to do with the screen technology? There are a few sites offering 1080 IPS panels which would definitely be a decent improvement - here's one https://www.laptopscreen.com/English/model/IBM-Lenovo/THINKPAD T550 20CK SERIES/

 

About to irder oneof these panels..
Does any one have a highres pic of the back of it showing the 8 legged ic (edid)

Can you not just remove and reprogram it with a programmer using the dump uplaoded a few pages back ?

Like we had to do with the early panel swaps in the t60's before edid programming over the cable was made aware..

Just a though

 

Welp, I switched over to Ubuntu and everything works fine. Would like to go back to windows

Is this what you wanted?
http://i.imgur.com/a5shWNU.jpg

 

I finally found info that was easy enough to follow to make the brightness controls of the Y580 ideapad work on a replacement panel. Something similiar to what I found and followed might work with the w550. The Y580 info is here http://forum.notebookreview.com/thr...01-v4-dual-channel-40-pin-cable.671690/page-5

 

Yes, unfortunately that will not work if your edid eeprom is write-protected, as with @grosmar 's and @mika91 's panels.

That ought to work, too; write-protection should not be in effect.

Spoiler: recap bios-modding discussion

Had the week off, so made two modded bioses (see 'recap' for background):

• ThinkPad T450, T450s bios v1.19 (jbuj54ww) for AUO123D - B140HAN01.2
• ThinkPad T550, W550s bios v1.10 (n11uj05w) for AUO12ED - B156HAN01.2

Spoiler: edid whitelist mod - B140HAN01.2

Spoiler: edid whitelist mod - B156HAN01.2

Spoiler: replacing bios whitelist volumes

So the 'LEN40A0 - N140BGE-EA3' and 'LEN40B0 - N156BGE-EA1' have been overwritten, respectively. Nothing serious; these should be perfectly safe to flash (run the 'winuptp64.exe' after extracting the .7z). However, I'm not familiar with the extent of Lenovo's shenanigans regarding flashing modded bioses. If it refuses to proceed; report back. Can extract the plain bios if necessary (these are embedded), but then you'd have to flash in DOS.

Of course, if you have an edid that is different from these replacements then it's not going to work, even if the panel is the same (edids have revisions, too). If so, use MonInfo and copy/paste the ' Raw data' section of the panel you want whitelisted.

 

Hey, thanks so much for this effort!

i replaced the panel with 1.2 and it's indeed listed as AUO123D.

I tried flashing your bios for T450 but got the following error:

OS = Windows 8.1 64bit
Driver Loading....Done
System BIOS Version -> JBET51WW
Applying BIOS Version -> JBET54WW
System EC Version -> JBHT14WW
Applying EC Version -> JBHT15WW
AC adapter/Battery check....OK.

BIOS Flashing....
The number of retries of BIOS update = 1
The number of retries of BIOS update = 2
The number of retries of BIOS update = 3
Failed.
Error : Failed to verify Secure Flash image.​

everything related to security in BIOS is disabled.

tried googling for 2 days but cannot see the solution.
could you please advice how to flash it?

 

Yes, was afraid that might happen. That's ' Secure Flash' for you; perfectly secure ... from the owner .

Will need force flash, yet this bios is still packed and not the plain bin we want. Also, it doesn't look like simple padding any more, unlike older versions ... so ... perhaps you can can make a backup of the bios currently present, that should be a nice, plain 4MB or 6MB file which we can use for the dos flashers. Not sure which tool works, though. Try writing this img to a usb stick and attempt making a backup with afudos, flashrom or fpt. There's a .txt for each, listing the various switches.

edit: wrong link

 

Hi,
I have dilema to decide.
I am LCD seller in EU and I sell screens on daily bases and i come to this problem with coded edids in screen long time ago on LVDS screens, to be able to sell all OEm screens, I have to find solution.
I try SW like you try here but no luck so i let mine supplier to create edid programer and all screens can be rewrite as I want, but only LVDS. After while LCDs with eDP connectors start selling and they have been perfect because you could change screens with any model you want no limits, but after while edid codes come again to eDP screens too so I call a guy in China and ask them if they have programer but with no luck and after month of looking i found one company in TW who has it, but they want too much money for it.
I want to ask you all of you who have this problem with brightness, will you be open to send screen to me for rewrite for postage and small fee so i can get money back for that programer?
i know you all say it pays for it self if i sell screens on daily bases, but you are wrong because it is not that big problem yet, it will be for me but maby with in 12months. btw sorry for mine anglish

 

I have similar problem with t450s windows 10. upgraded horrible TN screen with B14han01.3 ips panel from ebay. no brightness control except in bios/before windows loads. Found a program called "PangoBright" at download.com (cnets website) and seems to work for me now. any luck with the modded bios?
Cheers jimmy

 

I get the same Failed to verify Secure Flash image error on the T550

So do you need us to create a backup of the bios? Is there a difference between that and the bios lenovo has posted online?

Seeing with how much work you have put into this please send me your Paypal address so I can throw you a donation, I greatly appreciate the effort!

 

I also tried using all these tools but they can't run on x64 bit, am i supposed to run then on a live DOS cd? Sorry a bit new to this can you just explain it to me like I'm 5 years old what needs to be done?

 

Yes and yes. The Lenovo version is not the true bios, but that is embedded within their .bin all the same, extracted on-the-fly and the written to the bios chip (=eeprom). The one you backup from the bios chip will be the plain, unadulterated version.

Will then use that to make the same mod again. Difference is that this bios can be flashed from DOS, using low-level, generic flash programs, rather than the secure flash tool provided by Lenovo. Still, it will depend on just how secure the bios and its eeprom chip were implemented. With the latest versions even dos force flash will not work, leaving only the last resort; de-soldering the chip and flash with programmer. But then you might as well do that for the edid eeprom instead.

No need. But if you like; make a donation to Wikipedia .

Yes, but a usb stick will be fine. Write the .img to the stick with USB Image Tool or similar (use ' Restore' function):



Restart laptop and hit F12 while it's still booting. It should give you a menu with bootable device to choose from, including the usb stick. Choose the stick and you should be in DOS (it may beep annoyingly), then enter these commands:

Code:

cd afudos
afudos~1.exe backup.rom /O

Not sure which afudos version you need, but there's several on the image; try v3.07 first. If afudos refuses to make a backup then there's also flashrom and fpt:

Code:

flashrom.exe -p internal -r backuprom.rom
fpt.exe -d backup.rom -bios

 

I already donated to wiki, cause it's the right thing to do.

Cannot get your image file to boot. I mean it's 7z so I tried extracting it, renaming it to img, extracting and making it into an img. Quite lost.

Went back to Rufus to get FreeDOS to boot. Tried flashrom as well as fpt, no good. Didn't try afudos.

I'm running 1.09 btw, upgrades scare me. The bios is a Phoenix bios so I don't think afudos would work.

But is this the ROM you seek?
https://mega.nz/#!S5MjQCoS!jLnAZSOIuy3I8jT4fhMHHKZGmqqlaMk45EhxCyuCGB8

 

Ah, sorry; linked the wrong file. That version needed to be copy/pasted to the bootable stick's root. Try this file for writing the img; autoflash_2016_01_08.7z. FreeDOS won't work for most flash programs, the img version is MS-DOS and works for all the tools.

That's probably a serendipitous decision considering v1.10 will prevent flashing back to an older version. That usually also means no more modded bioses, either:

Spoiler: change list v1.10

Code:

CHANGES IN THIS RELEASE
  Version 1.10

[Important updates]
- Security fix addressed LEN-2015-002 SMM "Incursion" Attack and some security
  fixes.
  (Note) If the UEFI BIOS has been updated to version 1.10 or higher, it is no
         longer able to roll back to the version before 1.10 for security
         improvement.

[New functions or enhancements]
  Nothing.

[Problem fixes]
  Nothing.

A lot of vendors do this; their last bios fixes "nothing", but merely prevents users from having control over their machine. Always check the readme.txt before flashing a new version.

You could use phlash14 then. Rename the 16MB rom to 'BIOS.WPH' and enter:

Code:

phlash16.exe /BU

That should attempt to write the 1.09 again, but skip it since it's the same bios already, then write the current bios to 'bios.bak'.

It helps, but it is too large (padded) to fit on the eeprom. The backup from the dos tools should return the right size or, failing that, at least can help id the exact bios chip that was used. These all have neat size ranges, usually 64, 32 or 16 Mbit, which means the bare bios is 8, 4 or 2 Mbyte (mbit / 8). So file properties should say 8,388,608, 4,194,304 or 2,097,152 bytes (mbyte * 1024 * 1024).

 

No luck with any of the utilities. I got the img you have to boot and every utility threw an error including the phlash16. I tired running Winphlash but that still threw an error (I renamed my rom to BIOS.wph). The only thing that would work is Phoenix UEFI Winflash. So I guess only UEFI is available, not a bios? I'm very lost.

 

What errors, specifically?

And yes, seems like it. You've used WinFlash to write the 16MB backup? If so, then it's not yet the right file, but found a promising thread regarding the UEFI Winflash tool: Guide: BIOS-Downgrade from 5FCN95WW to 5FCN35WW.

Just a hunch: made a backup on the WayBack Machine (<- it's Wikipedia's peer ).

Although the post mentions only a downgrade, the second page ( backup) has a method to bypass the modded bioses errant checksum (result of making any mod). This is exceedingly good news; all switches are still present in the windows-based version and, even better, it appears to have an option to write only the module we've modified:

Spoiler: command line options

This is almost too easy ... oh well. Modded the v1.5.66 tool already, now only need to extract and modify appropriate modules of the v1.09 version of the T550/W550s bios. Can't use the v1.10 for the module flash, unfortunately. Hope to have time tomorrow or Sunday's, otherwise next weekend.

Just to make sure; your lcd is a B156HAN01.2, right? Otherwise it'd do little good; have to know the exact panel and even the panel's exact edid version. Run MonInfo and copy/paste the 'raw' section. And use the ' Shift+right click -> Open command window here'-option on the Phoenix UEFI Winflash v1.5.66 folder and run both backup options:

Code:

winflash.exe /bak /file biosbackup1.bin
winflash.exe /ro /file biosbackup2.bin

Not sure the ' Updates the module ...' and ' Replace the RAW module' refer to updating the bios on the system or merely patching a local bios file without flashing that. If it's the latter, then we need the .wph file mentioned in the first post of the Lenovo thread. Follow the first steps and try to obtain it from the v1.09 bios file (can't do so on my systems).

 

When I run the command line, the error is "unknown to support:file" yeah I have that screen. Would it be easier if you could just teamview to my PC (don't worry I'm wiping it soon)?
Email me at [email protected] (my spam account so I don't care if people see it)

 

Thanks for writing michal.f,
Can you mention some other laptops that you are having the same problem with?

Thanks!

 

Sure, will send a mail.

 

Jumping in here - I have the 1.2, and a 1.3 display along w/ my original 900p that came w/ the t450s. I've gotten up to the point w/ the write failed issue, and I've been studying a way to disable the write-protect. If anyone has any suggestions or other ideas, let them flow!

 

Found this AUO Spec PDF just now... has the EDID Specs for the 1.1 Panel, but no mention of Write Protection bits compared to another model I came across earlier. Found this with some good-ol google tricks.

https://www.glynshop.com/erp/owweb/Daten/DSS/Promate/Products/Specifications/AUO Products/B140HAN01.1_rev1.1 - GLYN.pdf.

-

NOTE: Don't try this on the AUO 14" , this is for a different panel and PIN-OUT below -----

You will notice on page 12 of the PDF, it talks about write-protection pin configuration. The way I see it - is if power is supplied to PIN 20 on this 51 PIN cable, then the EEPROM becomes writeable. The way it's described with the HIGH / LOW tells me it might be switchable . I can't be certain. Otherwise AUO has a different pin out config for writing the EDID to the device at the factory, of which we won't be able to work around w/ out some microscopes and lead cables!

https://www.glynshop.com/erp/owweb/.../AUO Products/PIDs/P550QVN01.0_rev0.3_GLY.pdf

 

Well ... one thing that defeats any write-protect method is programming directly to the eeprom:

Spoiler: CMN1735 - N173HGE-E11 - connector and eeproms

Spoiler: CMN1735 - N173HGE-E11 - eeprom programmer

Spoiler: CMN1735 - N173HGE-E11 - edid mod

No need for a microscope, though; only used tweezers for this. However, it does require a few tools:

• soldering iron
• good flux (unleaded solder)
• flux cleaner
• programmer (I2C capable, but better get one that supports SPI as well, so you can revive the odd bios and vbios, too)
• multimeter (to verify it's been properly re-soldered)

Do think the bios mod is significantly easier, yet the eeprom mod has its own perks. Of course, you'd still need the hacked bios in order to match the customised edid, unless you were to flash the white-listed Lenovo edid instead of a mod.

 

Hey,

Did anyone succeeded with the BIOS flash from t456?

 

Hi all

have the same issue with a new FHD screen on a X250, presume no one has made any more progress on a solution?

 

Hey guys, I have a T450s which I swapped in an IPS 1080p AU panel and same issue. I tried writing to the EDID with Linux and it's write protected.

I made a video of the panel installation of the panel, if anyone is interested:


Unfortunately when I installed the panel I didn't know about this problem. I wish I had peeled back the plastic to look for the EEPROM before installing it. Now I'll need to remove the sticker and bezel which I will do. If I can find the EEPROM I will attempt to remove write protection and document it for you guys.

This thread has been very informative though.

 

Cool! Thanks! I'm also very interested in a solution to this problem. I also installed my panel before recording this information...

 

I just read the EDID from the FHD panel that I installed in my t450s some months ago. It's a very nice IPS panel!

Code:

00000000: 00ff ffff ffff ff00 30e4 4604 0000 0000  ........0.F.....
00000010: 0017 0104 951f 1178 ea45 75a0 5b55 9227  .......x.Eu.[U.'
00000020: 0c50 5400 0000 0101 0101 0101 0101 0101  .PT.............
00000030: 0101 0101 0101 2e36 80a0 7038 1f40 3020  .......6..p8.@0
00000040: 3500 35ae 1000 001a 0000 0000 0000 0000  5.5.............
00000050: 0000 0000 0000 0000 0000 0000 00fe 004c  ...............L
00000060: 4720 4469 7370 6c61 790a 2020 0000 00fe  G Display.  ....
00000070: 004c 5031 3430 5746 332d 5350 4c31 00a8  .LP140WF3-SPL1..

I could write the EDID dump back to the panel without write errors (using edid-rw -w). Does that mean that there is no write protection? Or does it not detect the write protection because the dump is not different from what's already on the EEPROM?

The next step is to find an EDID dump from a T450s with this same panel originally installed.

P.S. I first noticed the brightness adjustment issue in Windows months after installing the newer panel. I normally run Linux and that just works.

 

I also just tested writing back with write-edid.sh. No error messages either. So, another hint that there is no write protection on the LG panel...

Any ideas on how to safely modify the EDID or how to obtain an EDID of this same panel installed by lenovo?

 

Use the ' LEN40A3 - LP140WF3-SPD1.bin' included in the white-list edid 7z archive I've linked previously. Checked the parameters; it's almost 1:1 identical to your SPL1, only difference is a slight change in colour coordinates, but these will be hard to spot.

Neither, unfortunately. Write-edid.sh merely returns the result after its batch i2cset operation. So whether you flash the same edid to a non-write-protected eeprom or a different one to a write-protected eeprom the result will be the same; it will return the old edid data. Only way to find out is flashing a different edid.

 

Hey t456,
Thanks for all of your work! trying to get my head around this all as I moved from a HD+ LP140WD2-TPD1 to a Full HD LP140WF1-SPU1 on my T450. I tried to dump the EDID, but it comes out as 256 bytes. Something going wrong there. Any idea what to do? Can I use one of your whitelist files?

 

Thanks for the tip!

No luck so far. The write proceeds without errors but afterwards the EDID data is the same as before the write.

After the first 128 bits I have another 128 bits of zeros. Depending on what range you dump you may or may not get those zeros.

 

Interesting. all i did was use this command: sudo get-edid > edidbackup.bin
Can I still use this file to edit and then flash back? I'm worried of doing anything.

 

Yes, it should be in binary format ( according to its manual). Upload it first, just in case.

Does the SPU1 run fine otherwise? It requires a 2-lane eDP cable and the SPD1 only needed a 1-lane type, so if it's doing alright then the stock display cable featured a few additional wires that were not in use with the 900p panel.

 

I see. the SPU1 works just fine, t
Here's the file. I edited the ID to fit my old panel. https://dl.dropboxusercontent.com/u/11984743/edidhybrid.bin