Few messages are as frustrating as a black screen with the words “No Signal” floating in the corner, especially when the device on the other end of the cable is clearly powered on. An HDMI no signal error almost never means your TV is broken. In the overwhelming majority of cases it is a handshake that failed, a port that was never selected, a cable that cannot carry the bandwidth being asked of it, or a receiver sitting in the middle of the chain that lost its way. This tutorial walks through a methodical, port by port process so you stop guessing. Work through the steps as written, because each one rules out a whole category of fault before the next begins.

What “No Signal” Actually Means
When you connect a source such as a console, streaming stick, or PC to a TV, the two devices exchange information before a single frame appears. The source asks what resolutions, refresh rates and colour formats the display supports, the display answers, and then a copy protection negotiation known as HDCP takes place. Only after all of that succeeds does video start flowing. A “No Signal” message simply means the TV is receiving nothing usable on the input you are watching.
That single message therefore covers several very different faults: a sleeping source, the wrong input selected, a failed handshake, a cable that cannot carry the format being sent, or a soundbar or receiver failing to pass video through. Diagnose efficiently by testing these in order of likelihood rather than replacing hardware first.
Tools and Preparation
- A known-good HDMI cable, ideally a certified High Speed or Ultra High Speed cable rated for the bandwidth your source needs.
- Both remote controls: one for the TV and one for the source device.
- A second source device, such as a streaming stick or laptop, to use as a test signal.
- A torch or phone light so you can read the tiny port labels on the back panel of the TV.
Before you start, note which physical port the source is plugged into and confirm which HDMI input the TV is displaying. A surprising share of no signal calls end here, with a device on HDMI 3 while the TV shows HDMI 1.
Step by Step: Fixing the HDMI No Signal Error
- Confirm the source is actually awake. Look for a power light on the console, box or stick. Streaming devices in deep standby sometimes need a button press on their own remote rather than the TV remote. If the source has its own display or fan noise, use that to confirm it is running.
- Cycle the TV inputs manually. Press the Input or Source button and step through every HDMI entry one at a time, pausing two or three seconds on each. Some TVs hide unused inputs, so if the port you want is missing, look in the settings menu for an option to show all inputs or rename them.
- Reseat both ends of the cable. Unplug the HDMI cable from the TV and from the source, wait a moment, then push each end fully home until it seats with a light click or firm stop. Wall-mounted TVs are the worst offenders here because gravity slowly works cables loose over months.
- Perform a full handshake reset. Power off the TV and the source, then unplug both from the mains for at least sixty seconds. Unplugging matters because modern TVs keep a standby rail live and hold the failed handshake state in memory. Plug the TV back in first, let it boot fully, then power the source. This single step resolves a large share of no signal faults.
- Try a different HDMI port on the TV. Move the cable to another input and select it. If the picture returns, the original port may have a damaged pin or a firmware quirk. Note that not every port is equal: on many sets only one or two ports support the highest bandwidth modes or eARC, and the rest are limited.
- Swap in a known-good cable. Cables fail silently, especially long runs and cheap bundled ones. Anything above 4K 60Hz demands a properly certified cable.
- Test the TV with a different source. Plug a laptop or streaming stick into the same port with the same cable. If that works, the fault lives in the original source device. If nothing works on any port with any cable, the fault is far more likely to be the TV input board.
- Lower the output resolution on the source. Consoles and PCs can be set to a mode the TV cannot accept, producing a black screen. Boot the console into its safe or low-resolution recovery mode, or on a PC connect a second display and drop the resolution to 1080p 60Hz before reconnecting.
- Bypass any receiver or soundbar. If your source runs through an AV receiver or a soundbar with HDMI pass-through, connect the source straight to the TV. If the picture appears, the middle device is the problem and needs its own power cycle, input check or firmware update.
- Check for firmware updates. Update the TV, the source and any receiver. HDMI compatibility fixes are among the most common items in TV firmware release notes.
Understanding HDCP Failures
HDCP is the copy protection layer that must succeed before protected content plays. When it fails you may get a no signal message, a black screen with sound, or an explicit HDCP error. Streaming apps trigger this most often because they refuse to output anything unless the chain is verified end to end. The classic causes are an older splitter or switch, a receiver supporting an earlier HDCP revision than the source expects, or a long passive cable that degrades the signal enough to break verification. Removing every optional box between source and TV is the fastest test, then reintroduce devices one at a time until the failure returns.

When the Problem Is Bandwidth, Not the Connection
Modern sources ask a lot of a cable. A 4K 120Hz signal with high dynamic range and full colour sampling moves far more data than 4K 60Hz, and a cable that was perfectly stable last year can fail the moment you enable a higher refresh mode. Symptoms include a picture that works at 60Hz but drops out at 120Hz, intermittent black flashes, or sparkles across the image.
Two settings usually decide the outcome. First, most TVs have a per-port option named Enhanced, HDMI Deep Colour or Input Signal Plus that must be enabled before that port accepts the highest bandwidth formats. Second, keep cable runs short, since passive cables lose margin with length; for long runs use a certified active or optical cable.
If you are pairing a new console with a display and want ports that handle these modes without drama, it helps to shop from a shortlist built around that capability. Our roundup of the best HDMI 2.1 gaming TVs covers sets with full bandwidth inputs, while the broader guide to the best TVs for gaming weighs input lag and picture quality alongside connectivity.
Receivers, Soundbars and Pass-Through Problems
Once audio gear joins the chain, the number of things that can break rises sharply. A receiver has to accept the video, decode the audio and pass the picture onward without losing the handshake. If it is set to the wrong input, stuck in a standby state or running old firmware, the TV reports no signal even though the source is working perfectly.
Power cycle the receiver along with everything else, and always power devices back on from the display outward: TV first, then receiver, then source, so each device can read the capabilities of the one downstream. Check that the receiver input assignment matches the physical port you used, and confirm its output goes to a TV port supporting the format you want.
An increasingly common alternative is to send video straight from each source to the TV and return audio to the sound system over eARC. That removes the receiver from the video path entirely, so a handshake fault can no longer black out the picture. It requires a TV and sound device that both support the standard, and our guides to the best gaming TVs with eARC and the best soundbar speakers explain which combinations handle lossless formats cleanly. For a full multi-channel setup, the best surround sound speakers guide covers how the pieces fit together.
Safety and Handling Notes
- Power down devices before removing or inserting HDMI cables, since hot-plugging can occasionally damage a port during a surge.
- Never force a connector. HDMI plugs go in one way only, and forcing one bends the internal pins beyond repair.
- Support cable weight on a wall-mounted TV with a clip or channel so the port is not slowly levered apart.
Common Mistakes to Avoid
The first mistake is replacing the cable before doing a proper power-cycle reset. Cables do fail, but handshake states fail far more often, and buying a new cable that appears to fix the issue often just means the act of unplugging everything cleared the fault. The second is buying an expensive cable in the belief that price improves picture quality. A digital signal either arrives intact or it does not, so what matters is certification for the bandwidth you need, not premium branding.
A third error is testing several variables at once, which tells you nothing about which change mattered. Alter one thing, test, then move on. Finally, a per-port bandwidth toggle left disabled is among the most frequent causes of a high refresh source showing nothing at all.
Frequently Asked Questions
Why does the no signal error appear only sometimes?
Intermittent faults usually point to a marginal cable, a loose connector or a device that renegotiates the handshake when it wakes from standby. Reseat both ends, then try a shorter certified cable before suspecting the TV itself.
Does cable length really cause no signal?
Yes. Passive copper cables lose signal margin with distance, and problems appear first at the highest resolutions and refresh rates. Beyond a few metres, use a certified active or fibre optic cable.
Why do I get sound but no picture?
That pattern usually indicates an HDCP or format mismatch rather than a broken connection. Lower the source resolution, disable high dynamic range temporarily, and remove any splitter or switch from the chain.
Should I reset my TV to factory settings?
Only as a late step. A factory reset clears stored input data and can resolve stubborn handshake faults, but it also wipes your app logins and picture calibration, so exhaust the simpler options first.
Final Thoughts
An HDMI no signal error looks alarming but responds well to a disciplined process. Confirm the source is awake, verify you are watching the right input, reseat the cable, then perform a full sixty second power-cycle reset with everything unplugged. From there, isolate by swapping ports, cables and sources one variable at a time, and remember to check the per-port bandwidth setting whenever a high refresh mode is involved. If a receiver or soundbar sits in the chain, test a direct connection early, since pass-through devices cause more black screens than any cable ever will. Follow that order and you will resolve most cases in a few minutes without spending anything.
