Czy wolisz polską wersję strony elektroda?
Nie, dziękuję Przekieruj mnie tamHorizon 50HL7590U/B firmware
• Horizon does not publish stand-alone firmware packages for the 50HL7590U/B on the open Web.
• Updates are delivered either (a) automatically “over-the-air” (OTA) through the TV’s Update menu when it is on-line, or (b) through authorised Horizon / Vestel service channels that rely on the exact main-board and panel code of your set.
• Therefore, the safe way to obtain or re-flash firmware is to ① try the built-in OTA routine and, if that fails, ② contact Horizon customer support or an approved service centre with your serial number, chassis (main-board) code and panel code.
Key points
– Firmware is board- and panel-specific (typically Vestel 17MB– series), so using any “similar” dump from forums risks permanently bricking the TV.
– Service centres can generate the correct USB update package once they know your hardware combination.
– A factory/service-menu reset often cures software-level problems without a full re-flash.
Hardware platform
• Most Horizon sets in the “HL” range are built on Vestel chassis. For a 2021-2022 50" UHD Android TV that is usually a 17MB180 / 17MB211 or close variant, paired with an Innolux or VES panel.
• The firmware package (bootloader, Linux kernel, Android OS, panel-gamma tables, EDID, logo, Widevine keys, etc.) is generated per chassis + panel combination.
• Flash devices: eMMC (Android partition table) + a small SPI NOR for the boot-ROM. Both may need re-programming if corrupted.
Standard update path (Horizon menu)
Settings → Support → System Update → “Check for Updates”.
– TV fetches a signed .pkg over HTTPS from Vestel’s server.
– Signature is verified against a key stored in ROM; if it fails, the TV refuses to flash.
USB-service update path (used by technicians)
Prerequisites: FAT-32 USB ≤ 32 GB, root directory contains files provided by Horizon:
usb_auto_update_A1.txt
MBxxy_en.bin
MBxxy_resource.pkgProcedure (typical Vestel):
Because the loader does no on-screen validation of panel compatibility, a wrong package can leave you with:
• black screen / backlight only,
• duplicated / mirrored image,
• continuous boot loop (Vestel logo),
• in worst case, unreadable eMMC and dead boot-ROM.
Troubleshooting without new firmware
• Hidden (“hotel”) service menu: INFO → MENU → MUTE → POWER or 4725 on remote.
• Factory reset, NVM clear and panel re-selection often recover colour-space, HDMI-CEC or boot-loop anomalies caused by NVM corruption.
• Always note Panel Type and S/W Version before erasing NVM; you will have to re-enter them manually.
Why firmware may be required
– TV stuck on logo / infinite reboot after power outage.
– No picture, backlight on (“blank panel EDID”).
– Replacing main-board with a used board from another brand (logo mismatch, panel incompatibility).
– Security-patch or Android-version upgrade requested by end user (rarely possible outside OTA).
• 2023-2024: Vestel moved from 17MB1xx Linux-only boards to MB230 / MB301 Android 11/12 SoCs; their update packages are now signed and region-locked—public dumps are increasingly unusable.
• Service networks access Vestel’s cloud (sota.vestel.com) with a dealer login; consumer downloads are discouraged to curb piracy and DRM key leakage.
• Community forums (Elektroda, BadCaps) show repeated cases where “near-match” firmware caused mirrored picture or disabled tuners—reinforcing the need for exact panel ID matching.
Analogies
• Think of the firmware as a BIOS + full Android OS + monitor ICC profile, married to your specific screen. Flashing the wrong one is like installing a car ECU programmed for a diesel engine into a petrol engine car—it fits the connector, starts briefly, then fails.
Examples
• A Toshiba-branded 17MB170 board flashed into a JVC set will boot but show a duplicated image until a service-menu “Panel Selection” is corrected or the proper firmware is re-flashed.
• Horizon 43HL series shares the same 17MB211 board but different panel timings; using its file on a 50HL7590 will light the back-light yet keep the panel dark.
• Firmware is intellectual property; unauthorised distribution violates Horizon/Vestel copyright and may circumvent DRM (Widevine Level 1).
• EU consumer law: A firmware replacement performed by an unqualified party during the legal warranty period (2 years EU-wide) can void the warranty if the fault is linked to the intervention.
• Safety: Interrupting AC power during flashing can corrupt the bootloader, requiring SPI-chip desoldering and in-circuit programming—procedures involving high-temperature soldering and mains isolation.
Potential challenges & mitigation
• TV does not read USB → try second port, smaller USB, rename to sda1.
• LED stays red → wrong key combo; consult service manual.
• Boot loop continues → eMMC bad; board swap or BGA re-flow may be required.
• There are no guarantees that Horizon will supply firmware to end users; some regions require service-centre handling.
• If eMMC is physically damaged (common after power surges), firmware alone will not fix the unit.
• Third-party dumps found on forums might lack Widevine keys → Netflix/Amazon HD will fail even if the TV boots.
• Vestel MB180/MB211 service manuals (available on Elektrotanya) for deeper understanding of recovery procedures.
• Study of secure-boot chain on Amlogic-based Android SoCs used by new Vestel boards.
• Investigation into creating user backups of NVM and eMMC partitions before problems occur (using ADB or UART-boot).
Resources
• Horizon Europe support: https://horizon.ro/support
• Vestel Global service login (technicians only): https://sota.vestel.com
• Forums with verified dumps (read-only for caution): elektroda.com, badcaps.net
The firmware for the Horizon 50HL7590U/B is not publicly downloadable; it is paired to the exact Vestel main-board and LCD panel installed in your set. First attempt an OTA update via the TV’s menu. If the TV is unresponsive or OTA fails, obtain the correct USB package directly from Horizon or an authorised service centre—supplying model, serial, main-board and panel codes. Flashing unofficial dumps carries a high risk of bricking, warranty loss and DRM failure. Follow service-grade precautions, keep power stable, and verify panel settings after any firmware action.