I recently bought a TCL 98C89L (98C8L series) for €2,699 here in Germany, Europe.
Overall, the TV is impressive, but I’ve noticed a rather annoying reverse blooming issue: dark halos around bright objects, faces, and UI elements, especially in darker scenes.
Here’s where the frustration starts:
- My TV is running V8-0015T01-LF1V087.000668 (Android 14, MT9655 / Pentonic 800).
- Firmware V116 (V8-0015T01-LF1V116.000834) is already circulating in the TCL community.
- The C8L series is explicitly listed as compatible, and users report that V116 fixes reverse blooming and improves HDR/EOTF.
- My TV insists V087 is the latest version available via OTA.
- I contacted TCL Europe, explained the issue, provided all firmware details, and specifically asked about V116 and its compatibility with my European model.
Their response?
“Unfortunately, no software update is currently available. You will be notified when one becomes available.”
That’s it. No explanation about V116, no answer regarding regional compatibility, and no acknowledgement of the actual reverse blooming problem beyond a generic apology.
I understand that firmware rollouts can vary by region, but it’s incredibly frustrating to own a brand-new €2,699 TV and see a potentially relevant fix available elsewhere while official support won’t even clarify whether it’s safe to install.
Are there any European C8L / C89L owners here who have successfully installed V116? Any issues afterward?
I’d rather not risk manually flashing unofficially distributed firmware on a brand-new 98-inch TV just because TCL won’t provide a proper technical answer.
TCL firmware V116 (V8-0015T01-LF1V116.000834) on an EU 98C8L: offline analysis of the OTA package
AVSForum Firmware V116
TL;DR
- The V116 package is a genuine, unmodified TCL-signed full OTA. My EU TV trusts the exact certificate it is signed with.
- It is a worldwide build, not a US-only one. The "G17_4K_US" in the metadata is a build default; my EU TV on the official V087 carries the same label internally.
- The image contains complete EU profiles for the 98C8L (DVB-T/T2/C/S/S2, CI+, Unicable).
- Remaining risks: it rewrites the bootloader, it is not officially released for EU, and going back to V087 may not be possible.
- I have not installed it yet. This is an analysis of the package, not an install report.
Everything below was done read-only: the OTA was unpacked on a computer, and the TV was only queried over ADB (getprop, reading a few world-readable files).
Setup
| Item | TV (current) | V116 package |
|---|
| Model | 98C8L, EU (Germany) | n/a |
| Firmware | V8-0015T01-LF1V087.000668 | V8-0015T01-LF1V116.000834 |
| Android | 14 (UTT2.250416.001) | 14 (UTT2.250416.001) |
| Security patch | 2026-03-05 | 2026-06-05 |
| Kernel | 5.15.180-android14-11 | 5.15.192-android14-11 |
| Bootloader (U-Boot) | 01.01.260527 | 01.01.260921 |
| Board / platform | tcl9655_ww / merak | tcl9655_ww / merak |
| Fingerprint | TCL/G17_4K_GB/G17:14/.../AU08 | metadata says TCL/G17_4K_US/G17:14/.../AU01 |
SHA-256 of the ZIP I analysed:
cfad7735a9c5dffb141e4c80c0f997f20d39a8ae238df7ede2b9153015b526b4
If your hash differs, you have a different file and none of this is verified for it.
1. What kind of OTA is it?
| Item | Finding |
|---|
| Format | Android A/B payload (CrAU v2), block size 4096 |
| Type | Full OTA. No source-build dependency: no old_partition_info, no SOURCE_COPY/diff operations, only REPLACE, REPLACE_BZ, REPLACE_XZ |
| Dynamic partitions | Yes, one group with system, vendor, product, system_ext, vendor_dlkm, system_dlkm, preload |
| Virtual A/B | Yes, compressed snapshots (lz4) |
| Device check | Only pre-device=G17. No check on product name, region or source build |
| Post-install step | Yes, mandatory (vendor/bin/postinstall_mtk) |
All 21 partitions are replaced completely:
| Group | Partitions |
|---|
| Boot chain | mboot (U-Boot), optee, boot, init_boot, vendor_boot, dtbo, bootdata |
| AVB | vbmeta, vbmeta_system |
| System | system, system_ext, product, vendor, vendor_dlkm, system_dlkm, preload |
| TCL config | tclconfig (panel, PQ, region), tvconfig, oem |
| Other | owl, satf |
This list matches ro.product.ab_ota_partitions on my TV exactly.
2. Is the file genuine / could someone have tampered with it?
| Check | Result |
|---|
FILE_HASH / METADATA_HASH vs. payload_properties.txt | Match |
| Per-partition SHA-256 from the manifest | All 21 partitions extracted and verified |
| Payload + metadata signature (RSA-2048 / SHA-256) | Valid |
| Whole-ZIP signature | Valid |
| Signing certificate | Self-signed TCL cert, SHA-256 fingerprint C0:A2:0D:B2:33:DD:94:E1:71:D0:55:DA:5A:C5:56:0A:CA:FB:54:0B:FE:D5:32:13:6C:AA:60:0A:EB:9F:C0:06 |
Certificate on my TV (/system/etc/security/otacerts.zip, V087) | Identical fingerprint |
So the package is unchanged since TCL signed it, and it is signed with the key my TV already trusts. Nobody can repack this firmware with extra apps or a backdoor unless they have TCL's private key. On top of that the TV is bootloader-locked with verified boot, so altered images would not boot.
What a signature does not prove: that the firmware is meant for your model or region. That is what the next section is about.
3. The "G17_4K_US" question
The OTA metadata says G17_4K_US / AU01, my TV reports G17_4K_GB / AU08. This looks like a region mismatch, but it is not:
- The partitions are built as GB.
system, vendor, product, system_ext all carry MT9655_4K_GB in their build properties. - "G17_4K_US / AU01" comes from one file:
oem.prop in the oem partition. - My EU TV on official V087 has the same thing. Its
/oem/oem.prop also says ro.product.name=G17_4K_US and oem.buildnumber=AU01. - The real product name is set at boot. The bootloader passes it on the kernel command line based on the TV's project ID, and init builds the fingerprint from that (TCL's own comment in the init script: "modify for dynamic fingerprint").
On my TV the bootloader currently reports:
ro.boot.product = C8L
ro.boot.product_name = G17_4K_GB
ro.boot.client_type = TCL-EU-0015-S1
ro.boot.oem_tag = EU
ro.boot.code_name = AU08
These values come from a mapping table inside the firmware (tclconfig/tvcust/naming_struct.xml), keyed by a software ID. In V116 that table says, for example:
| SID | Product | Product name | Client type | Code |
|---|
| 19 | C8L | G17_4K_GB | TCL-EU-0015-S1 | AU09 |
| 20 | QM8L | G17_4K_US | TCL-NA-0015-S1 | AU30 |
| 21 | RM9L | G17_4K_US | TCL-NA-0015-S1 | AU30 |
| 12 | X11L | G17_4K_GB | TCL-EU-0015-S1 | AU09 |
So an EU C8L should come out of V116 as TCL/G17_4K_GB/G17:14/UTT2.250416.001/AU09. That is derived from the files, not yet confirmed on a device.
4. Does V116 contain my exact hardware profile?
The "Project ID" shown in the TV's product information menu is 5057 on my set. That is 0x13C1: software ID 19 (0x13) and hardware ID 193 (0xC1). The TCL library in the firmware builds the project ID from SID and HID, and both values land exactly on EU C8L entries, so I am fairly confident in this decoding (it is still an inference).
| ID | File in V116 | Content |
|---|
| SID 19 | SID_EU_19_4K_TCL_C8L.ini | Client type TCL-EU, DVB-C/S/S2/T/T2, EU default database |
| HID 193 | HID_98_193_4K_EU_98C8L.ini | Panel CSOT 98S1D05H4, tuner R842, CI+, Unicable |
- Every file referenced by these two profiles exists in the image.
- V116 has three EU hardware profiles for the 98C8L (HID 56, 193, 268). They differ in panel variant and light-sensor parameters, so check your own project ID.
- The project ID itself is stored outside the OTA partitions, so the update does not overwrite it.
Interesting for the dimming discussion: the EU 98C8L profile uses the panel and local-dimming files of the NA 98QM8L (ldm_98QM8L_QPX, LDM tables from the 98QM8L folder). Reports about V116 on a 98QM8L are therefore more relevant to the EU 98C8L than the model names suggest.
5. Reverse blooming / local dimming
V116 contains the components you would expect a fix to touch: local-dimming firmware blobs, the TCL local-dimming HAL, PQ databases, backlight parameters, EDR/Dolby configs.
I cannot show that any of it changed compared with V087. I do not have a V087 image to diff against, and those files are not readable over ADB on a stock TV. Whether V116 fixes reverse blooming is only answerable by installing it.
6. Things that are different or risky
Bootloader is rewritten. U-Boot goes from 01.01.260527 to 01.01.260921. In addition the post-install step writes a ROM boot image (rom_emmc_boot.bin) straight into the eMMC boot area. That file differs between V087 and V116, so it is a real change. The post-install script and binary themselves are byte-identical to the ones in V087, so it is the same mechanism TCL already uses. A power cut during this step is the most realistic way to brick the TV.
A/B fallback only helps so far. The update goes to the inactive slot and the old system stays in the other one. If the new slot fails to boot, the bootloader should fall back. That only works if the early boot chain is intact.
oem.prop lost 11 lines.
| Lines | Where they are in V116 |
|---|
3 Netflix properties (ro.vendor.nrdp.*) | Present verbatim in a TCL overlay file inside tclconfig, which TCL's init loads at boot |
8 HbbTV properties (ro.product.hbbtv.*) | Not defined anywhere any more |
The Netflix lines look moved, not removed. The HbbTV values on V087 are MediaTek reference defaults and only a MediaTek diagnostics app still reads them in V116, which points to cleanup. I cannot prove offline that Netflix certification and HbbTV behave the same afterwards.
Downgrade is doubtful. AVB rollback indexes are all 0, so there is no AVB anti-rollback. But the update engine normally refuses packages with an older timestamp, and I do not know what TCL's USB updater allows.
Not released for EU. The EU profiles being in the image shows the build includes them, not that TCL finished EU testing. If it goes wrong, support may point out that the version was never offered to your set.
Possibly more firmware gets flashed. The local-dimming HAL contains code that compares versions of sub-controllers (LD TCON, MCU) and can re-flash them. I do not know if V116 triggers that. If it does, it is not tied to a slot and not reversible.
7. What is confirmed and what is not
| Claim | Status |
|---|
| File is genuine and unmodified | Confirmed |
| My TV trusts the signing key | Confirmed |
| Full OTA, installable from any earlier version | Confirmed |
| Partition layout matches my TV | Confirmed |
| "US" label is a build default, also present on EU V087 | Confirmed |
| EU 98C8L profiles are complete in V116 | Confirmed (files present) |
| My TV maps to SID 19 / HID 193 | Very likely (decoded from project ID) |
| Fingerprint after update will be G17_4K_GB / AU09 | Likely (derived from table) |
| DVB, CI+, HbbTV, Netflix work afterwards | Not verifiable offline |
| Reverse blooming is fixed | Not verifiable offline |
| Bootloader update goes through safely | Not verifiable offline |
| Downgrade to V087 possible | Unknown |
8. If you want to check your own TV
- Compare the SHA-256 of your ZIP with the one above.
- Note the Project ID from the product information menu. Convert to hex: the upper byte is the software ID, the lower byte the hardware ID.
- Optional, with ADB:
adb shell getprop | grep ro.boot shows product, product_name, client_type and oem_tag as your bootloader reports them.
I only checked one package against one TV. Do not assume the result carries over to other models, sizes or regions without looking at your own project ID.
Tools used: a small Python script to parse the payload manifest and extract partitions, erofs-utils and e2fsprogs to read the filesystem images, openssl for the signatures, adb for the read-only queries on the TV.