Display Drivers

Read Before Any Updates/Flashing

Display driver is a major source of bricking in this HU and there are many of them. Before attempting patching of xyauto drivers or flash the HU. Gain a general understanding first and consider doing backups. Read here

Translation of these files on xyauto file server is "Screen Parameter" Probably a better name as the LCD screen is programmed to display the boot logo on HU's cold boot. But display driver has been used by many so just following this name.

Show logo before Android boot

Usually, computer operating system (OS) boot first to install all the device drivers to communicate with various hardware. So how do you initialize and setup a complex device like the LCD panel to display a logo before Android even boot?

This HU boots a partition called logo where an initial boot logo and LCD panel initialization parameters are stored. This is booted before Android OS starts booting so the HU can display something to notify the user it is working. What this means is the Android OS doesn't need to know anything about initializing the LCD panel. It depends on the logo partition.

logo.bin logo.mrf Display driver

These terms are often used interchangeably. Here is what each means

logo.mrf

This file contains

• bootup logo

• LCD panel initialization parameters

This is the source file that is flashed into the HU and stored in the logo partition. logo.mrf ( MRF = MediaTek ROM Format ) is often much smaller ( ~1K*1K resolution HUs ~8MB, ~2K*1K HUs near 30MB ) than the logo partition (commonly 64MB)

Each logo.mrf contains initialization for just a single LCD panel model.

logo.bin

This is often the extracted logo partition saved file name. Partition extraction software usually just blindly extract the entire partition and save it in a .bin (binary) file. The actual useful section of the .bin file is usually smaller (size of original logo.mrf file)

Display driver

This often refers to the xyauto update file with .gz extension which contains mainly logo.mrf. Additional files are inside but are just the machinery to execute the update.

.gz file can also include other updates such as UI or apps besides logo.mrf. These can be quite dangerous since the user can not easily see they are also flashing logo.bin

Many logo.mrf

We are seeing an explosion of 1280*720 mipi display panels so many logo.mrf exist for this spec. Wrong one will cause display bricking. Consider backing up the HU. See here

xyauto leaves HU manufacturers to install logo.mrf because they frequently change new LCD panel ( an expensive component ) with lower cost and improved spec (eg resolution). Each new LCD panel results in a new logo.mrf. This is the reason there are so many logo.mrf files and wrong one can display brick the HU ( Android will still boot, backlight on, but no display ) It can be expected # of logo.mrf will continue to increase going forward.

If a wrong logo.mrf is flashed ( even unknowningly hidden inside a small xyauto update ), HU will be display bricked.

As an example, an HU vender in India with brand name Trak N Tell is providing 5760B HUs with high modifications

• Multiple LCD panel models. Maybe some are from India based LCD panel manufacturer?

• Customized ad supported launcher to help reduce HU price

No clear logo.mrf for an HU

Currently no way to identify the LCD panel driver from your HU by software. As noted, LCD is initialized before Android even boots so Android doesn't even know the LCD panel model.

Panel model ID potentially could be printed on the back of the LCD. This ID could match display driver file name strings to help identify ( link )

However, in general, there is no easy way to identify which logo.mrf  or display driver will work with an HU. The best logo file is extracted from the HU through backup. Unfortunately it isn't a simple process. Read Backup

xyauto probably archive these display drivers on their file server. But file server access has been blocked since 2023/24. Going forward, newer LCD panels model in the HU likely will be easier to brick when flashing with older xyauto updates ( with logo.mrf hidden inside ) and the possibility of finding display drivers reduced with the closed xyauto file server. Therefore, backing up your own logo file is essential before flashing any software from xyauto.

Find logo.mrf without Backup

Ideally, you have extracted your own logo file that matches your HU's LCD panel ( see Backup ) Since there are many logo.mrf files, here are ways to fine possible ones that work

• If HU is disassembled, look at the back of the LCD panel for panel model ID. Some display drivers will have panel model ID as part of the display driver file name. see here

• If have System Info picture (link) and/or remember the resolution + (lvds or mipi) interface. Can try those first.

• Following are directories with Display drivers

  • Display driver only Note for any resolution, multiple exist in repository and unfortunately all are potential candidates. Review "logo.mrf PARTIAL SUMMARY" to see how many match the Display spec ( resolution + lvds or mipi ). Note the summary's resolution (and those in the file names) is NOT horizontal * vertical. It could also be vertical * horizontal. To determine orientation, looked at the corresponding .png file in the repository.  logo.mrf are are inside display driver .gz files ( unzip and look inside customer_ota directory  )

  •  Display driver with other apps

  • Display driver with UIs also contain display drivers along with other UI launchers and app. logo.mrf PARTIAL_SUMMARY and .png file are also in these directories to summarize resolution and orientation.

  • s.xygala.com Display Drivers s.xygala.com is xygala file server that appeared 2025 (xygala keep on changing servers) This likely contain the most recent complete list of display drivers (over 270) Screen Reference List.pdf in the directory contains the complete list and summary for each file. This list include screena nd IC model #s which can be helfpul if HU is disassembled. Some drivers have 2 files (2nd one with name appended with (1)) with different sizes. Don't know why.

Statistics

No complete statistics exist but there are a few patterns

• Older HUs ( ~2022 ) have fewer display drivers.

• Newer HUs ( 2024+, maybe 2023 also? ) with 1280*720mipi LCDs have much larger panel model variation. It seems every time someone post on the xdaforum thread, its a different LCD panel requiring a different logo.mrf.

• Have seen 1 very new HU ( late 2024 by India seller Trak n Tell for India market ) with no archived display driver. Luckily the owner saved it with backup ( also made a driver from this for he repository ) Read here and here

Make Display Driver from newly found logo

Post #3904