No HDMI Output on My Raspberry Pi 4

Overview

No image on your Raspberry Pi 4 HDMI output? Check the display connection, boot media and display configuration before assuming the board is faulty. For a single display, start with HDMI0, the micro HDMI port nearest the USB-C power connector.

Check the HDMI port

1. Shut down your Pi and disconnect power.
2. Connect a known-good micro HDMI cable to HDMI0, nearest the power connector.
3. Check that your monitor is on the matching HDMI input, then power on the Pi.

A rainbow screen alone does not identify the fault. If it remains on screen, continue with the SD card and power checks below.

Check the SD card

A corrupt or incorrectly flashed card can prevent booting. With power disconnected, remove and reinsert the card. If necessary, use Raspberry Pi Imager to write a fresh Raspberry Pi OS image to a known-good card.

Check LED indicators

The red power LED and green activity LED can help distinguish power or boot-media problems from a display problem. Note any repeating flash pattern and compare it with the official LED warning codes. A green LED that does not flash is a reason to check the card, not proof that the board or card is faulty.

Check HDMI cable and display

• Try another micro HDMI cable or adapter.
• Test the monitor with another device and check its selected input.
• Try another display to rule out a compatibility or mode-detection issue.

Booting without a monitor

First check whether the Pi failed to boot or only has no graphical display. If you can connect using SSH, it has booted. A missing remote desktop then needs display or remote-service troubleshooting; forcing video does not enable SSH, set up networking, or repair power and SD card faults.

For comparison, shut down, attach a known-good HDMI display, and boot again. Back up each boot configuration file before editing it. If the Pi remains unreachable, check power, boot media and network setup as well.

Legacy headless workaround

1. On the older image, open its boot configuration:

   sudo nano /boot/config.txt

2. Add this on its own line, save, then reboot:

   hdmi_force_hotplug=1

3. To force a resolution, run sudo raspi-config. Only if that version offers Display Options → Resolution, choose a modest mode from its list and reboot with sudo reboot. Newer menus differ.

The hotplug setting asks the legacy firmware to behave as though an HDMI display is connected. Remove the line you added if it does not help. The older hdmi_safe=1 troubleshooting option is also a legacy setting; use the KMS method below for a KMS image.

Force a display mode on modern KMS

For KMS console or display-output troubleshooting, use the kernel display mode. Current images normally keep the file at /boot/firmware/cmdline.txt; some older images mount it at /boot/cmdline.txt. Use the path present on your image and make a backup first.

1. Open the file, for example:

   sudo nano /boot/firmware/cmdline.txt

2. Append a space and this token to the existing line:

   video=HDMI-A-1:1280x720@60D

3. Keep the entire original command line on one line. Do not replace its existing contents or put this token on a second line. Save, reboot, and test.

This example forces a digital output at 1280 × 720, 60 Hz. Choose a mode your intended display supports. HDMI-A-1 corresponds to HDMI0; HDMI-A-2 to HDMI1.

To undo, remove only the token you added and reboot. A forced HDMI mode does not guarantee that every VNC or Wayland remote desktop service will work; configure that service separately. For a current desktop with a connected screen, use Preferences → Control Centre → Screens to adjust display settings.

Further help

If the problem persists, email support@vilros.com or call 855-207-9254 with your order number, OS version, display connection and any LED pattern. Mention whether SSH works and which configuration changes you tried.