[Sony Xperia T, TL, TX, V] updateing:
OK finally there is a permanent solution for this problem.But this method is still under test.I will not be responsible for anything damaged.You choose whether to try it.

Then you should have working screen on your TX~You can enjoy the leaked 4.3 now~

========================================================

WHY IT WORKS

As the old post said,we can gather correct register data from a normal screen and write back to the problem ones.Here is the data I collected:

http://xdaforums.com/showthread.php?t=2607323

Thanks Sakilia,you are our phone's lifesaver!

And I did a comparison between the dumped data and my own,finding that only a few registers were changed.I checked the interfaces provided by the screen driver and found several ways to write the differences to screen.I tried them all but only one way,which is like the previous corruption process,really worked.

After the data was written into the screen,everything looks nice except the color(what a mess!).It was caused by the incomplete data dump.However,after reading something about register operation,I found that hex commands in MDW30 driver and MDX80 driver were just the in the same format (register number + data)and there are several registers used to store color correction data.So in no time did I find the missing parts and wrote them into my screen.Finally the screen works as before!

Old post:

========================================================

This morning I wanted to find a zImage that could boot 9.2.A.0.278 LT30p leaked firmware on my LT29i.Among the zImages I have,there is one extracted from LT30p CM10.2.But I didn't remember it and flashed it on my phone.Then the terrible "inverted screen" came...

After ~5hrs researching,I found that after cross-flashing,the panel was recognized as MDX80 instead of the correct MDW30_1e.

Maybe RECOVER_PANEL config caused this...The 30p kernel found there was a panel but it couldn't recognize it,so the kernel thought the panel was corrupt and executed the recovering process,after which our MDW30 was overwritten with MDX80 register data.But MDX80 driver fails to initialize the panel with commands required by MDW30 so the panel displays thing upside down...

I think that now that it loads MDX80 driver,why can't we add MDW30 init commands to the MDX80 driver?And there comes the key!

I just copied init_cmds and on_cmds from mdw30.c and replaced the ones in mdx80.c.It works!

And here is my work:

There are some "unused" warnings in the file,but it does finish the compiling and work.

That should do with "Touch Firmware version C" devices.:victory:

As for the color correction:

echo 1 > /sys/devices/platform/mipi_dsi.524288/eco_mode
echo 0 > /sys/devices/platform/mipi_dsi.524288/eco_mode

Don't forget about the space after 1 or 0 !

A little bug:screen gamma correction and ECO MODE aren't working properly.The color is a bit different from stock kernel.

There is another way:dump the correct register values from a normal TX and write our own NV Recover data using CONFIG_FB_MSM_RECOVER_PANEL.

But I don't know how to dump data.Anyone can help?So that we won't have to re-compile the kernel every time we flash a new firmware...

Added v2:Changed cabc_user_param to MDW30's

=======================================================

If you use my work,please give proper credits.Thanks!