Firmware & OTA guidance
Right file, steps and OTA setup for your model and build, plus wrong-flash recovery.
B2B product support center
For traders, brands and project buyers using DataMax TV boxes, signage players and projectors: one tracked desk for firmware, diagnosis, spares and RMA.
Unit reboots under 4K playback after update
How we support
Trade customers first: cases are logged, traced to a batch, and handled during working days by ticket.
Right file, steps and OTA setup for your model and build, plus wrong-flash recovery.
Firmware, settings and hardware checks via your video, logs and screenshots, before return.
Spare parts and assessed returns for confirmed failures, per the warranty terms in your PI.
Repeat orders and fleets get a dedicated window that knows your SKU, branch and history.
Repeat buyers and fleet operators never restart from zero: your window holds SKU lists, branches, shipment history and quality records.
Set up a support window
Before you write
All six ready, most tickets clear Triage in one pass.
The ticket board
Each status shows who is acting and what comes next on our engineers’ board.
Via the inquiry form or contact page; a ticket ID is issued.
Model, PO and warranty confirmed; an engineering owner is assigned.
Firmware, settings and hardware checked remotely; logs and files are exchanged.
Most cases close remotely; confirmed failures get an RMA with terms per contract / PI.
You confirm the fix; the ticket closes and root cause is logged against the batch.
No ticket number means no tracking. Resend chat requests via the inquiry form or contact page so they enter the board.
Common requests
Pick a lane and reach the right terms before opening a ticket.
Update steps, recovery files, branch confirmation.
Faulty units, claims and assessed returns.
Remotes, adapters and common spare parts.
Need documents? Download the catalog for specs and model sheets.
Firmware & OTA
Most “dead after update” cases are wrong-branch files, not hardware.
Project SKUs ship a dedicated build and update from that branch. A generic or another customer’s file can remove features, branding and certification.
A shared SoC does not mean shared firmware: Wi-Fi module, timing, remote map or DRM keys may differ. Match the full label model name.
Updates stay within certification; unapproved builds can affect certified services, and we coordinate the compliant path.
Don’t keep retrying the file. Open a ticket with the label photo and current screen and engineering guides recovery; steps also in the support FAQ.
Five-minute self-triage
A large share of support tickets turn out to be environmental or configuration issues rather than faulty hardware — the wrong input selected, a tired HDMI cable, a remote that lost pairing. Working through the six checks on the right takes minutes and, when the symptom survives them, gives the ticket exactly the evidence engineering needs to start diagnosing immediately.
Two rules make every case faster: match firmware to the full label model name, never to the chipset, and keep custom-project units on their own branch — the firmware rules above explain why crossing either line creates the “died after update” tickets we see most.
When the symptom is environmental in the field, the buying-stage documentation often prevents it: the dust-free engine guide for projector airflow and service intervals, and the warranty page for exactly how confirmed failures move through RMA.
Usually a wrong-branch file rather than hardware. Confirm the exact label model name and the firmware file used, stop retrying, and open a ticket for the correct recovery image.
Verify the selected source/input, try a known-good HDMI cable and port, and power-cycle display and device together. HDCP handshakes often clear with this sequence.
Check the 2.4/5 GHz band and AP capacity first, then confirm the wireless module fitted to the SKU — modules differ by configuration even within one model family.
Voice remotes pair over Bluetooth, not line of sight: re-pair from Settings and check batteries. IR-only remotes need a clear path to the front window.
Check HDMI/ARC routing and any passthrough setting against your amplifier, test the internal speaker path, and confirm the content is not an unsupported audio format.
Clear vents of dust, confirm mounting clearance and airflow, and review the dust-free engine guidance — thermal shutdown is protection, not a fault by itself.
Behind every ticket
The campus that built your order: a repair loop, aging and four quality gates.
Parts and PCBA checked against an approved sample; suspect lots quarantined.
First-article and patrol inspection at each station, with AOI fixtures.
100% functional test and aging, plus RF verification on wireless models.
Golden-sample audit, then drop and packaging checks before sealing.
Support FAQ
Settings → System update shows the OTA path for your build. For manual updates use only the file for the full label model name; custom builds take their branch package from support.
Stop, do not re-run it. Send the label photo, file name used and a current-screen photo. Many units recover with the correct image or recovery procedure; some may need rework.
Every request gets a ticket number and is handled during working days, tracked by ticket. We quote no fixed hours — faults differ — but complete checklist items up front speed the first technical reply.
It follows your contract and proforma invoice. In-warranty failures follow the agreed warranty terms; out-of-warranty or misuse damage is quoted before return, and the ticket states shipping before goods move.
Remotes, adapters and common spares come via the parts / sample channel with model and quantity. For fleets, add a small spare-parts ratio to the batch order.
End users are supported by the seller — the trading company, brand or retailer holding warranty and invoicing. In-warranty claims reach us through that channel with the PO; out-of-warranty repair is quoted case by case. Buyers with an active PO contact us directly.
Work through the chain in order: confirm the display is on the HDMI input the box is plugged into, swap in a known-good short HDMI cable, try the other port if available, and power-cycle the display and box together (this re-runs the HDCP handshake). Also check whether the box has output set to a resolution the display does not support — a recovery boot with a reset of display settings is part of the guided procedure. If two known-good cables and ports still show no signal, open a ticket with the model label and a short video of the sequence.
First replace the batteries and make sure no other paired remote or gamepad is nearby. Put the remote within a metre of the box, open Settings → Remotes & Accessories and choose add/pair accessory, holding the pair buttons on the remote as shown in the model guide. If the remote previously paired and disappeared after an update, remove the old entry and pair again; IR fallback still works for basic keys during troubleshooting. Persistent pairing failure on one unit after a known-good remote test goes through the ticket board as a hardware case.
Not necessarily — thermal protection shuts the light source down when airflow is blocked, which is the most common cause in ceiling-mounted or enclosed installations. Check that vents are not pressed against a ceiling or sealed inside a tight box, that filters and intake areas are clear of dust, and that ambient room temperature is within the operating range; the dust-free optical-engine page explains which models are designed for long service intervals. If shutdowns continue with confirmed clear airflow and normal temperature, treat it as a fault and open a ticket with a video, mounting photo and the firmware version.
See also the warranty page, or start on the inquiry form.
Attach the six checklist items and your case is resolved against the order’s production records.