Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Screen contrast is controlled by firmware #2

Open
advancingu opened this issue May 7, 2015 · 563 comments
Open

Screen contrast is controlled by firmware #2

advancingu opened this issue May 7, 2015 · 563 comments
Labels
known workaround

Comments

@advancingu
Copy link
Owner

The screen brightness is controlled by firmware and correlates with the brightness of content on screen.

This means the screen automatically dims when dark content is shown and brightens when bright content is shown.

There is no known method to turn this mechanism off.
@sojusnik
Copy link

sojusnik commented May 8, 2015

There's also an online test regarding this issue:

http://tylerwatt12.com/dc/

@advancingu
Copy link
Owner Author

Yes, definitely fading in for me, i.e. my laptop is affected. Is there anything that can be done to stop this? It's highly annoying.

@advancingu
Copy link
Owner Author

I spoke with Dell business support yesterday and was told there is an engineering team currently looking into this together with the display panel vendor, as apparently the brightness adjustment is done in the display firmware. They were now trying to expose an on/off switch in the BIOS to allow the user to toggle the behavior, however the support person was not able to tell me when or even if there would be a BIOS update.

@gaborkr
Copy link

gaborkr commented May 11, 2015

The funny thing about this "feature" is that it is supposed to work the other way around: increase brightness with a dark background, and decrease it on a bright background - this would be useful.

@volo1st
Copy link

volo1st commented Jun 15, 2015

Definitely, it's not a feature, it's a BUG.

Imagine that when you are hacking something with a dark themed editor/IDE, and then switch to your browser, this stupid adaptive brightness thing will burn you eyes.

I have to installed redshift to the system to reduce the bluish tint which make the screen even more glare, and another plugin in Chrome to make all white background grey to avoid my eyes been burnt, heck.

@advancingu
Copy link
Owner Author

I checked with Dell business support again yesterday and unfortunately there is still no ETA for a fix.

@utack
Copy link

utack commented Jun 30, 2015

Customer support as of today had no clue when the feature is going to be ready..

@AndrewBogdanov
Copy link

Any updates about this issue? I'm still looking for a solution, like a lot of us, I guess

@uncon
Copy link

uncon commented Jul 7, 2015

I used to noticed this, but some time back I stopped seeing this behavior. I have completed the linked test several times, and I cannot reproduce this dynamic change in brightness at all. Unfortunately, I can't correlate this to anything that changed, but I don't believe I've seen this since A04. (I have a QHD display.)

@AndrewBogdanov
Copy link

Hey, uncon. I have an FHD screen and I'm definitely seeing this even after I've updated to A04.

@mattkrems
Copy link

My FHD screen ordered from Dell's website (256 GB, 8 GB ram options) definitely has this problem. With no clear timeframe for a fix, I think I have to return. Thanks for letting me down Dell!

@advancingu
Copy link
Owner Author

@AndrewBogdanov @mkrems If you haven't yet done so, I suggest you contact Dell support and ask them about the issue and when it will be fixed. I've heard that they do listen to support to some degree, so the more negative feedback they get about this issue, the more likely they are going to be implementing a fix.

@AndrewBogdanov
Copy link

@advancingu will definitely do that today

@mattkrems
Copy link

@advancingu Yeah, I talk to tech support a few days ago, and they took me through a process of reinstalling driver and firmware. I tried to tell him this was a known problem, and they really need to fix this as lots of people are upset and returning their laptops, but I don't think the message got through:(

@advancingu
Copy link
Owner Author

If you have the official developer edition, it should be eligible for so called "ProSupport". Supposedly support personnel there is held to a higher quality standard than regular support. If you use chat to communicate with them you can also send them a link to this report.

@antonyh
Copy link

antonyh commented Jul 18, 2015

I'm lucky that I don't have this problem, so it may depend on the hardware.

dmesg reports:
Dell Inc. XPS 13 9343/0310JH, BIOS A04 05/15/2015
ELAN Touchscreen.

Xorg.0.log indicates:
intel(0): EDID vendor "SHP", prod id 5153

get-edid confirms SHP panel, unknown model.

Could Dell have changed components, or fixed it in A04, or different SHP model/firmware?

@advancingu
Copy link
Owner Author

Perhaps the touchscreen panel is not affected. Mine is the matte non-touch with 1920x1080 resolution and it suffers from this issue.
Xorg.0.log contains:

intel(0): EDID vendor "SHP", prod id 5152

@AndrewBogdanov
Copy link

I also have a matte non-touch version FHD. How can I check those logs that you provided?

@advancingu
Copy link
Owner Author

cat /var/log/Xorg.0.log | grep EDID

@AndrewBogdanov
Copy link

Is it a cmd command? Will it work on Windows?

@advancingu
Copy link
Owner Author

This command works on Linux only. To determine if your model is affected, follow the link provided here.

@AndrewBogdanov
Copy link

Yeah, I tried that link and my screen shows logo via fading for 3 seconds or so.

@advancingu
Copy link
Owner Author

Then please contact Dell support and tell them that you dislike this "feature" and ask them to provide an option to turn it off. This is the only chance to ever get rid of this behavior.

@AndrewBogdanov
Copy link

So, I've conacted Dell Support Agent yesterday and he was working with my machine remotely for 3 hours or so, trying defferent things like updating bios, drivers etc. The bottom line: this is a hardware issue of integrated video card. So I will be sending request for warranty mother board replacement. I will update on this topic when it will be replaced to the new one.

@advancingu
Copy link
Owner Author

@AndrewBogdanov Good luck and thanks for posting an update.

@tmadhavan
Copy link

Such a shame that this issue hasn't been (officially) addressed. I've been hoping to get an XPS 13 but currently it's unusable for photography.

Having said that - my housemate just bought a (FHD) XPS 13, and doesn't seem to have the brightness bug. I will try to find out what BIOS rev. he has and report back.

(Also on Windows 10, though this is irrelevant if it's firmware, I know.)

@AndrewBogdanov
Copy link

I think this bug might be happening for a limited range of devices. For example my video card also have some issue when running simple surface test, so it can be some kind of bug in hardware itself. I will be able to tell for sure only when my motherboard will be replaced. But the guy from support told me that this issue will go away with a new motherboard.

@tmadhavan
Copy link

I don't think it's a bug as far as Dell is concerned, unfortunately - they clearly market it as a feature. Ridiculous that it cannot be disabled, though.

@utack
Copy link

utack commented Jul 30, 2015

In this case I want a documented way to intentionally produce a bug that breaks this "feature" please...

@AndrewBogdanov
Copy link

I don't believe it's a feature in any way. Where did you see they've been market that?

@peddy22
Copy link

peddy22 commented Feb 9, 2020 •
edited

https://www.aliexpress.com/item/13-3-LCD-Screen-matrix-display-LTN133HL10-201-1920-1080-non-touch-LTN133HL10-panel-For-samsung/32919265906.html?spm=a2g0s.9042311.0.0.78594c4do0Hbg1

Just make sure you ask for the exact model. Also this is the 13.3" model with the modified lid and bezel (also from China) where the concern is whether the LCD will actually fit within the display. Nitrocaster recommends 12.5" models on his site.

Edit: seller tried selling me another monitor don't get this

@fishynimo
Copy link

Hi, I have dell latitude 7370 with FHD pannel without touchscreen.
Without thinking much, I ran firmware upgrade through the file I downloaded from this link.
"https://www.reddit.com/r/Dell/comments/72ibws/howto_disable_cabc_on_a_dell_latitude_7370/"
Now, I can only use the laptop with an external monitor.
I think the screen is bricked. I read through the forum. Things were a bit technical.
I will really appreciate if anyone can tell me if I can make my screen work again like normal.
The bricked screen can't work again unless the hardware (screen) gets actually replaced???

Thank you so much.

@peddy22
Copy link

peddy22 commented Feb 17, 2020 •
edited

Hi, I have dell latitude 7370 with FHD pannel without touchscreen.
Without thinking much, I ran firmware upgrade through the file I downloaded from this link.
"https://www.reddit.com/r/Dell/comments/72ibws/howto_disable_cabc_on_a_dell_latitude_7370/"
Now, I can only use the laptop with an external monitor.
I think the screen is bricked. I read through the forum. Things were a bit technical.
I will really appreciate if anyone can tell me if I can make my screen work again like normal.
The bricked screen can't work again unless the hardware (screen) gets actually replaced???

Thank you so much.

You'll have to disassemble the screen and tell us the exact model number printed on the back of your LCD; then we can use the table above to determine which file might be suitable to flash.

@fishynimo
Copy link

I really appreciate your reply! I think the screen is Sharp SHP1460 (LQ133M1).
Thank you so much again for the tip :)

@fishynimo
Copy link

Oh I see. I will take it apart and figure out the exact model number! Thank you again!

@pyraxiate
Copy link

pyraxiate commented Feb 18, 2020 •
edited

Well add me to this boat :( I have the XPS 9365 ( 2 in one ) with QHD display. The dynamic backlight control was killing me, so I downloaded the firmware specific to my model from Dell. Now I no longer have I display unless I connect externally.

What is the easiest way to take the display apart to get the exact part number? Thanks in advance!

Edit - scratch that. It's sealed via glue and I'm still under warranty. The part is on a 2 month backorder though 😭

From what I've researched, the QHD display doesn't have many different panels. What's my best option here ? Could I try flashing something ? I can't break it any worse than it already is lol

The dilemma is that it shows no internal display in device manager and when I tried to re-run the firmware package, it says no compatible device found :/

@pyraxiate
Copy link

pyraxiate commented Feb 18, 2020 •
edited

So I get a write fail using the firmware for my model. Does that mean I'm out of luck? Is there a chance my motherboard is damaged too? Thanks again!
Screenshot_20200218-124925_VNC Viewer

Screenshot_20200218-130913_VNC Viewer

@fishynimo
Copy link

Hi, I have a question. Once I figure out a specific panel number, how can I flash the firmware to my laptop? Do I have to get an external flashing device??
I will really appreciate if anyone could give me a direction to the next step :)
Thank you so much!

@pyraxiate
Copy link

pyraxiate commented Feb 20, 2020 via email

@peddy22
Copy link

peddy22 commented Feb 20, 2020 •
edited

Hi, I have a question. Once I figure out a specific panel number, how can I flash the firmware to my laptop? Do I have to get an external flashing device??
I will really appreciate if anyone could give me a direction to the next step :)
Thank you so much!

just run the relevant exe

I think I'm in the same boat as you. I have a Dell 9365 QHD panel, so I just tried running the firmware to my specific model vs a specific panel by opening up the path the firmware extracted to. It still didn't work though. I'm still under warranty and waiting to see if Dell will take care of me before tearing anything apart. I'm Worried the motherboard is affected and not just the panel
…
On Wed, Feb 19, 2020, 9:37 PM fishynimo @.***> wrote: Hi, I have a question. Once I figure out a specific panel number, how can I flash the firmware to my laptop? Do I have to get an external flashing device?? I will really appreciate if anyone could give me a direction to the next step :) Thank you so much! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=AOS6AEMILP7LFASWYNFHVN3RDXUIBA5CNFSM4BCLYP32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMKQFLA#issuecomment-588579500>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOS6AEJM5CPM7R3ZLSKT5D3RDXUIBANCNFSM4BCLYP3Q .

yeah it goes without saying that you shouldn't take a laptop under warranty apart

you can always mess with your old display after your warranty runs out

@pyraxiate
Copy link

pyraxiate commented Feb 24, 2020 •
edited

Hi, I have a question. Once I figure out a specific panel number, how can I flash the firmware to my laptop? Do I have to get an external flashing device??
I will really appreciate if anyone could give me a direction to the next step :)
Thank you so much!

just run the relevant exe

I think I'm in the same boat as you. I have a Dell 9365 QHD panel, so I just tried running the firmware to my specific model vs a specific panel by opening up the path the firmware extracted to. It still didn't work though. I'm still under warranty and waiting to see if Dell will take care of me before tearing anything apart. I'm Worried the motherboard is affected and not just the panel
…
On Wed, Feb 19, 2020, 9:37 PM fishynimo @.***> wrote: Hi, I have a question. Once I figure out a specific panel number, how can I flash the firmware to my laptop? Do I have to get an external flashing device?? I will really appreciate if anyone could give me a direction to the next step :) Thank you so much! — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#2?email_source=notifications&email_token=AOS6AEMILP7LFASWYNFHVN3RDXUIBA5CNFSM4BCLYP32YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEMKQFLA#issuecomment-588579500>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AOS6AEJM5CPM7R3ZLSKT5D3RDXUIBANCNFSM4BCLYP3Q .

yeah it goes without saying that you shouldn't take a laptop under warranty apart

you can always mess with your old display after your warranty runs out

So the LCD was on backorder. They will be sending a " technician" to replace it. I will know at that point whether the igpu controller in the main board is damaged or if it's the display only. I have been reading and it seems that the boards controller being hosed is a possibility. I hope not though.

@static-void
Copy link

It is possible I guess to figure out how to program the displays over I2C manually (without using the windows software from the DELL downloads), e.g. I have done it for the RTD2662 LCD controller here https://github.com/static-void/rtd266x_programmer

However it seems the controllers have built in I2C flash so the protocol would need to be reverse engineered either by disassembling the programming software or by snooping the firmware upload as it happens.

If it's of interest to anyone else, I converted one of the hex files (from 312K3/9343
for the LQ133Z1JW01) to bin using objdump, and took a wild guess that it was 8051 assembler.. my guess seems to be correct. Looking at the differences between the CABC on and off versions, there are no actual code changes, there are just a few differences in some of the data bytes. I don't have time to investigate further (nor do I have any sharp displays, alive or dead), but the next step would be to figure out how the data is used and then examined some of the differences between CABC on/off firmwares for the other sharp displays. It might be possible to figure out how to disable CABC on sharp LCDs other than those DELL provides firmwares for, assuming their "CABC ON" firmware could be dumped using the DELL tools.

@AlzubaidiTurki

This comment has been minimized.

Sign in to view
@pyraxiate
Copy link

Just giving an update. Dell replaced the entire LCD Assembly on my XPS13 2-in-1 9365 and all is well again. No more flickering either. Seems only the LCD control board on the panel was corrupted luckily.

Hope this helps!

@Onedutch
Copy link

Onedutch commented Apr 6, 2020

See my, I think Bricked LCD message at https://www.dell.com/community/XPS/XPS-13-9365-PanelFW-DBC-bricked-the-Panel-Unable-to-flash-again/m-p/7531918 for my XPS 9365 QHD+ screen. I posted it pre-reading this impressive and massive thread. Started reading and using google 5 hours ago. I hope @Tharre can give a comment / verdict if I need a replacement LCD because of an "I2C bus is stuck on I2C_DEFER" or perhaps with the right steps I can get the QHD+ screen working again. It wasn't till about now that I found that dell uses "Hidden Files and Folders" feature to hide the "TCON_DP_REWORK_TOOL.exe" program ;) TIP:so make sure you have Show hidden Files and Folders enabled after unzipping the Dell package.

@pyraxiate , could you help me out?
Did you again use the Dell official tool to disable the Dynamic Backlight Control after the replacement?
Could you (willing to) save the original (current) firmware with the Other >> Save Romcode command now you have a working QHD+ Display? See the comment from Tharre on the "18 Dec 2017" in this thread. I did it after I bricked blacked the LCD, so my guess it should look different from yours.

@Tharre , after using the official Dell DBC tool (twice) I bricked to black the LCD screen, I found this impressive thread. Now I'm very cautions to not brick the panel any further. I think the I2C bus is working cause I'm able to Save a Romcode (using Teamviewer to take over the XPS). The Bin is attached, the sha1 is not as mentioned in the thread and de Bin looks pretty empty :(
What would be the best steps? I don't have a saved romcode prior the first attempt to disable the DBC. The tool is automated, I started "PanelFW_DBC" several times and not the "TCON_DP_REWORK_TOOL" from within the 9365 folder.
Thank you for the (already) amount of time you have put in this thread. Attached you find some screenshots from the current situation.
Best Regards,
Tom

Combined EDID
Combined Update Tool

RomcodePostXPS9365.zip

@peddy22
Copy link

peddy22 commented Apr 7, 2020 •
edited

Dell doesn't care about internet people.

The only thing I can add is to cold reboot after writing each consecutive firmware, be aware of the risks before trying to disable CABC, and overall don't try to do it.

You should be able to manage finding a QHD screen without backlight installed on the net, if someone can provide you with the model number.

@Onedutch
Copy link

Onedutch commented Apr 7, 2020 •
edited

@peddy22 Thank you also for the fast response and contribution to this thread :)

The only thing I can add is to cold reboot after writing each consecutive firmware, be aware of the risks before trying to disable CABC, and overall don't try to do it.
-- How can I perform a cold reboot?
-- What do you mean with consecutive firmware? Should I try the latest? I compared all the by you mentioned downloads from Dell. Mine Dell Driver package was not on your list it's a file called "APP_PanelFW_DBC_W10X64_A03_Setup-F9G6M_ZPE.exe" the HEX file "(Merge)160909_Sheep_revF.09+141202MCU_CABC on.hex" is the same (also SHA1) as in Dell Driver package 312K3 which is on your list! In the Dell Driver package 8GDDH I found a different HEX file (SHA1 also different) for enable "(Merge)160909_Sheep_revF.09+141202MCU_CABC on.hex" how ever the disable files are the both Dell Packages the same.
-- Be aware risks before trying to disable CABC, I allready tried and the LCD is black. Are you saying it's better to go for the firmware where CABC is enabled again? So I should try to use the folders who say "QHD_DBC__enable_"

You should be able to manage finding a QHD screen without backlight installed on the net, if someone can provide you with the model number.
-- I'm out of support, so it will be costly in money, reading this thread is costly in time :)

On another thread I read about the MonitorInfoView.exe program. I ran it and the output is attached. I also found the rd_data.bin in the c:\ it's zero's ..

@peddy22 Which advise would you give me to try? Like, as an example:

  • use the most actual released package "C:\Dell\Drivers\312K3" or should I stick with the one I used before, and bricked it with? Not starting "PanelFW_DBC.exe" butt start "TCON_DP_REWORK_TOOL.exe" inmediately
  • start with the CABC enabled folder?, As it was enabled and working?
  • Try to get a hold on a working firmware? Asked @pyraxiate for it :)
  • cold reboot
    -- Or something else? How can I tell if the I2C bus is bricked?

Thank you for your time en effort!
Regards, Tom

MonitorInfoView.zip
Output.txt

@peddy22
Copy link

peddy22 commented Apr 7, 2020 via email

@Onedutch
Copy link

Hello,
Today A tried to update the Rom-Code, I used "C:\Dell\Drivers\F9G6M-Clean\9365\QHD_DBC_enable" and pressed Write, is asks for confirmation. After several minutes I receive the message Write Fail.. I attached the screenshots, while writing the post the "Write Fail" changed into "loop:1,err:1" , unsure why it changed by itself. I then tried Others and Read EDID, also no luck.

I think it is easy to tell i you bricked it, looking at the status screen, if it says "Panel FW v0.00" the TCON tool isn't able to read the current status/firmware version..

Can I try something Else? I'm unsure what @peddy22 means with Coldboot. I had some more questions in my previous posting.

Any recommendations?

Regards, Onedutch

01
02
03
05
06

@lippylee
Copy link

lippylee commented May 4, 2020

Hi! Will anyone be able to share the fw updater danielpop2 uploaded? The links in the thread are all dead.
I intend to flash a Latitude 7370 with a SHP1460 and can't find any sources for the file. Thanks :)

@RikoF1
Copy link

RikoF1 commented May 10, 2020

So, I flashed the official tool on my SHP 1449 but because I didn't read properly I closed the app halfway through the flash because I though "loop 1, error 1" was just looping the installation while not being able to write on it. Right now I get WRITE FAIL everytime I run the app and FW is 0.00. From my guesses the screen is dead but could someone send me the stock firmware so I could give it a try? I'm just doing my best before I even send a message to Dell to see if they can replace the screen under warranty.

@peddy22
Copy link

peddy22 commented May 10, 2020 via email

@dainghia-tran
Copy link

Hello everyone, I've tried to disable DBC, and now it doesn't boot anymore. The front led light blinks 2 amber and 7 white. How can I fix it.

@RikoF1
Copy link

RikoF1 commented Jan 1, 2021

Hello everyone, I've tried to disable DBC, and now it doesn't boot anymore. The front led light blinks 2 amber and 7 white. How can I fix it.

Activate your warranty, only.

@dainghia-tran
Copy link

@RikoF1 thanks for your reply, I have the same problem with you, "WRITE FAIL" on SHP1449 and it got bricked after restarting.

@riconell
Copy link

riconell commented Mar 2, 2021 •
edited

Hello everyone. I recently bought a Latitude 7370 (FHD) which I absolutely love, except for its DBC. I saw that several users reported success in disabling it, but unfortunately all the links for the files they used are now dead.
HWiNFO reports my screen as a SHP1460. It seems the same panel is used in XPS 13 9360 for which Dell provides a DBC disabling application. Can I use it to disable DBC on my screen? If so, is there anything I'd need to modify in the files to make it work for me?
If not, could anyone kindly help me find a way to disable DBC?

EDIT:
I managed it! I'll write the steps down for future travelers.
How to disable Dynamic Brightness Control (DBC) on Dell Latitude 7370 (FHD):

  1. Don't install Intel DCH drivers! The flashing tool won't be able to connect with the screen and uninstalling them is a major pain. Instead, install these drivers.
  2. Check your screen model with HWiNFO or similar. This method worked for SHP1460, but I can't guarantee it will work for anyone, even with the same same screen model. Flashing firmware always has a risk of bricking your device.
  3. Download this package. Unzip it using 7zip.
  4. The folder we are looking for (the one named "9350") is hidden. If you can't see it, set your folder options to show hidden items.
  5. There are 4 folders inside, I assume "NT71395 FHD" are for FHD screens and "DP_Rework_ToolV17" are for QHD+ ones, but don't quote me on that. The executable in "DP_Rework_ToolV17" didn't detect my screen FW (read it as 0.00), the one in "NT71395 FHD" did. We of course use the "CABC off" flavour.
  6. Launch "TCON_DP_REWORK_TOOL.exe".
  7. Make sure "Panel FW" shows version other than 0.00
  8. Go to "Others" > "Save Romcode". This should create a backup of your current firmware in case things go south.
  9. Click "Write" and proceed through the prompts.
  10. In my case, the program went through 16 cycles of loop; error;. This got me very nervous, but in the end I got something among the lines of "Verification Failure". The number of loop attempts can probably be decreased in the .ini file, but I wouldn't want to touch anything there.
  11. After rebooting, DBC was gone!

@neilym82
Copy link

For anyone interested I have the XPS 9365 (2 in 1) with the QHD display & this is what I did . . .

Google search for "QHDFW_DBC.exe" & Download from the Dell website & then install / unpack . . .

Go To --> C:\Dell\Drivers\8GDDH\9365_7389\QHD_DBC_disable

View --> Enable hidden items

Run --> TCON_DP_REWORK_TOOL

File --> Open Hex/Bin file

Open --> (Merge)160909_Sheep_revF.09+141202MCU_CABC on.hex (in C:\Dell\Drivers\8GDDH\9365_7389\QHD_DBC_disable)

Write --> Reboot

FIXED --> NO MORE STUPID DBC ! ! !

@Koneko349
Copy link

I have a 2019 XPS 13 9365 (2-in-1) with an FHD display. Successfully flashed the display after identifying the correct display model and command

Used hwinfo to identify the display model

$ hwinfo

31: None 00.0: 10002 LCD Monitor
  [Created at monitor.125]
  Unique ID: rdCR.cvz7rjV_j40
  Parent ID: _Znp.zKzwl0Xmjf5
  Hardware Class: monitor
  Model: "6MD3N 133WF4 LCD Monitor" <-----
  Vendor: LGD "6MD3N 133WF4"        <-----
  Device: eisa 0x0536 
  Resolution: 1920x1080@60Hz
  Size: 294x165 mm
  Year of Manufacture: 2016
  Week of Manufacture: 0

Switched to Windows and downloaded this firmware package

https://dl.dell.com/FOLDER04623765M/2/APP_PanelFW_DBC_W10X64_A03_Setup-F9G6M_ZPE.exe

Checked PanelFWConfig.ini for 6MD3N which provided the correct command for the display

LGDANX2602\LGD_DBC_OFF_20170915\Intel_edp.bat

I am finally free of DBC!

@Alex139365
Copy link

I have a 2019 XPS 13 9365 (2-in-1) with an FHD display. Successfully flashed the display after identifying the correct display model and command

Used hwinfo to identify the display model

$ hwinfo

31: None 00.0: 10002 LCD Monitor
  [Created at monitor.125]
  Unique ID: rdCR.cvz7rjV_j40
  Parent ID: _Znp.zKzwl0Xmjf5
  Hardware Class: monitor
  Model: "6MD3N 133WF4 LCD Monitor" <-----
  Vendor: LGD "6MD3N 133WF4"        <-----
  Device: eisa 0x0536 
  Resolution: 1920x1080@60Hz
  Size: 294x165 mm
  Year of Manufacture: 2016
  Week of Manufacture: 0

Switched to Windows and downloaded this firmware package

https://dl.dell.com/FOLDER04623765M/2/APP_PanelFW_DBC_W10X64_A03_Setup-F9G6M_ZPE.exe

Checked PanelFWConfig.ini for 6MD3N which provided the correct command for the display

LGDANX2602\LGD_DBC_OFF_20170915\Intel_edp.bat

I am finally free of DBC!

Hi Koneko349, could you describe step by step display recovery, because I have the same screen model and got the same issue? Thanks

@lols
Copy link

lols commented Jul 1, 2022 •
edited

A description of my issue using dell 9360, i crack my screen, changed the display myself, tried to disable DBC using the dell tool, it cant detect intel driver even though it is installed, so i ran the tcon tool manually and just straight clicked write success
Reboot and it bricked, the display show image in 2 part and device will start and run for a short period of time before it auto shutdown even when in bios
Seems like there is a communication between the lcd and the motherboard, if lcd not connected, it will show the same symptom as with the bricked lcd connected. It will boot up fine with the cracked lcd

This is how i manage to solve the problem you will need a lcd with working firmware
1)remove battery/charger disconnect the bricked lcd, connect the cracked lcd with good firmware
2)plug charger or battery and boot up to the desktop,
3) run tcon tool from the disable dbc folder (9365 folder for my case even thought my model is 9360) if you want to patch disable, on menu select others save romcode and select yes when it ask new rom code...... do you want to update, after that dont click write

(If not careful, you risk shorting out your motherboard/ lcd board when removing the plug/ plugging in)
4)After it has done reading and save to the file, put the laptop to sleep, what i did was because i have access to the display pcb(i change the screen but not the outer case)i carefully unplug the cable that was connected to the lcd pcb, align it and slowly plug in to the bricked display and wake the laptop, now the laptop will still display image in 2parts but it will not auto force shutdown
(Reason why i pick the plug near the board is because it is a thin plug and the pins are more easy to check and align rather than selecting the one on the motherboard, if you go for the motherboard plug be very careful not to slanted plug in it can cause short between pins) Also take note of static electricity if you have carpet or weather is dry, touch some grounded equipment that are connected to 3 pin plug(with the earthing pin/ grounding pin)

5)On tcon tool, select file > open and select the dumped rom code from the cracked working display, click write and wait for it to finish and reboot
6) now the bricked display is normal again but the colour seems to be off, better than stuck with a bricked display that make the laptop unable to boot and with image split into 2
7) if you own a colorimeter like me, i have the old xrite i1display, i just set off to calibrate my screen and colour is acceptable now, not good but better than bricked display

Down side of this method is

  1. need a working display
  2. risk shorting out by hot plugging the display cable
  3. bad colour mine was slightly green instead of the usual 7500k blue tint

Story is before u click the write, you need to save romcode which will read the lcd eeprom then merge/patch with the disable dbc hex file dell have(since it ask if you want to update the rom code which you cant say no when u want to save a rom code), then you click write which will write back the original romcode that is from you display + the DBC patch code = new code for the lcd eeprom.

How i brick is is because i dumbly think that it will just write the DBC patch code and auto patch the rom code from the lcd
so i did not select save romcode and just only clicked write after i open the tool, which it will clear the eeprom and only write the DBC code thats why the lcd controller fall back to default values and the image split into parts and motherboard cant communicate with the lcd and it force shut off, no way to stop it from deciding to shutting down. VERY VERY BAD DELL, cant boot the laptop to desktop without internal display connected, unacceptable. The time approx to auto shut down is 1minute i guess, pretty fast, i only reach the login screen and straight boom auto off no power, had to press button to start again then same problem

Hope my encounter will help future user, i almost lost a new lcd by trying to disable DBC.......

Attached is the save romcode from my working cracked display with DBC disabled
lololol.zip

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
known workaround
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests