Skip to content
DiagnosticsRouterTroubleshooting

StarHub Fibre TV Set-Top Box Has No Picture After Restart

The set-top box powers on but the television shows no source or a blank screen. The guide distinguishes the affected component, identifies a safe test path, and explains when StarHub support must act.

Quick Answer

First, select the physical HDMI input used by the set-top box and test another known working HDMI cable. Next, check ONT and set-top-box indicator states using StarHub's supported boot sequence. Avoid resets that risk data or account access.

StarHub troubleshooting: The set-top box powers on but the television shows no source or a blank screen. This guide addresses StarHub Fibre TV Set-Top Box Has No Picture After Restart through reversible checks before escalation. The aim is to identify whether the failure is local to a device, tied to an account or plan, or outside the home network. Follow the branches that fit your actual symptoms rather than applying every possible reset.

Targeted recovery and proof

Select the physical HDMI input used by the set-top box and test another known working HDMI cable. Capture the exact wording of any message, the device model or app version where visible, and when the issue first appeared. In service and banking accounts, retain only a redacted reference; do not include passwords, OTPs, private messages or full customer identifiers in public screenshots.

Why the first observation matters: Singapore broadband and cellular issues are often split between the in-home radio network, the optical access network and the service account. A connected Wi-Fi icon does not demonstrate successful provider-side routing. The proposed first test helps decide which component actually needs work. A second attempt should be made only if it is safe and cannot duplicate a charge, delete content or create an unwanted public post.

Repair only the failing link

  • Original failure: The set-top box powers on but the television shows no source or a blank screen.
  • First discriminating check: Select the physical HDMI input used by the set-top box and test another known working HDMI cable.
  • Independent comparison: Check ONT and set-top-box indicator states using StarHub's supported boot sequence.
  • Higher-confidence test: Separate HDMI handshake failure from an inactive fibre-TV service using box status and firmware information.

Singapore fibre connections may include an ONT/ONR plus a separate router. The relevant model determines which LEDs and ports matter; an integrated router may not have the same labels. When the situation does not match the available controls, consult the current product guide instead of guessing a menu location. Distinguish a physical or signal problem from an authentication or entitlement problem before making settings changes.

Step-by-Step Troubleshooting

Choose Beginner for reversible checks; Advanced explains the service or device dependency and what evidence to collect.

Confirm the StarHub failure

Observed symptom: The set-top box powers on but the television shows no source or a blank screen. Write down the error or status exactly as displayed, and confirm which device, login or playback operation is affected. Avoid collecting unnecessary private information.

Perform the first StarHub check

Select the physical HDMI input used by the set-top box and test another known working HDMI cable. Keep the result. If this reveals an account, network or upstream outage, skip local resets and move to the corresponding service workflow.

Compare without deleting data

Check ONT and set-top-box indicator states using StarHub's supported boot sequence. Make only this reversible comparison, keeping app drafts, existing SIM profiles, router settings or streaming downloads intact.

Retest the failed action

Repeat the original action once when doing so is safe. Compare the result with The set-top box powers on but the television shows no source or a blank screen. and stop if fixed. Avoid removing fibre patch cords or resetting subscriber activation settings.

Interpreting the results for StarHub

Observed evidence What it implies Next action
The original problem is limited to a single app or device. Local permissions, saved settings, app version or a damaged session are plausible. Check ONT and set-top-box indicator states using StarHub's supported boot sequence.
Multiple clients or titles fail while related functions work. A shared dependency such as service authorization, upstream routing or a specific feature may be affected. Select the physical HDMI input used by the set-top box and test another known working HDMI cable.
Official account or service status indicates restrictions or an outage. Local reinstall or repeated configuration changes are unlikely to solve a provider-side condition. Separate HDMI handshake failure from an inactive fibre-TV service using box status and firmware information.

Safe repair decision

If the fibre or carrier service is unavailable for every device, provider-side status and provisioning come first. If one client alone fails, investigate that client and its connection method before touching shared equipment. Use the least disruptive confirmed action first. When a change works, stop. When it fails, restore that one setting and continue with the next diagnostic branch rather than stacking unverified fixes.

Separate device state from service state

Select the physical HDMI input used by the set-top box and test another known working HDMI cable. If this gives a different result on another legitimate client, record the difference. A shared failure deserves a service or network check; an isolated failure deserves a device, account or application check. Compare like-for-like actions and note whether the same error text remains.

Use the secondary check, not a blind reset

Check ONT and set-top-box indicator states using StarHub's supported boot sequence. Record any resulting status before attempting to reinstall software, clear app data, remove a SIM profile or reset a shared router. Such resets can erase drafts, locally stored messages, Wi-Fi configurations, paired home devices or offline downloads.

Advanced diagnosis for a persistent problem

Separate HDMI handshake failure from an inactive fibre-TV service using box status and firmware information. This step is useful when the quick comparison leaves more than one possible cause. The objective is not to force the service into an undocumented mode, but to provide actionable evidence to the product vendor or network operator.

What should not be changed yet

Risk specific to this problem: Avoid removing fibre patch cords or resetting subscriber activation settings. Use official menus and trusted downloads only. If a proposed fix asks for account secrets, unsupported firmware, third-party authentication pages or irreversible deletion, stop and check vendor instructions first.

Verify the repair

Return to the same operation that failed initially: The set-top box powers on but the television shows no source or a blank screen. Confirm whether the precise symptom has disappeared and note the settings changed. Check a representative local service and an independent secure website; where relevant, repeat on a second device to show that the improvement is not only an app cache artifact. A connection indicator, login screen or app launch is not enough when the original failure occurred only during a later action.

Solution Checklist

0/12 completed

What to send to support if the problem continues

Provide the product name (StarHub), exact message or visible state, approximate timestamp and time zone, device model, app/firmware version, what the first check revealed and what happened after the secondary test. State whether this is one device, one account or all users on the same service. Avoid removing fibre patch cords or resetting subscriber activation settings. Ask support to examine the relevant entitlement, service status or technical logs without posting private account data.

Official Resources

StarHub support documentation

Did this solution fix your problem?

Optional feedback helps us improve this guide. Never send private data.

PRBLEM / COMMUNITY

Discuss This Solution

Ask a question, compare results, or share a safe fix that worked for you.

Describe the exact issueInclude the error, device or software version, and what you already tried.
Protect your informationNever post passwords, recovery codes, private logs or personal data.
Retry if the discussion does not load

Disqus hosts the discussion. Comments load automatically as you approach this section and may use cookies.

Can't find your answer?

Tell our editors which problem needs a guide. Do not include passwords, API keys, email addresses, private URLs, or full error logs.

Analyze Error

Paste an error message to identify its likely category. Analysis takes place in your browser; only a short error category will be used if you choose to search.

Do not paste passwords, tokens, private URLs or full logs.