Please do not post a support request without first reading and following the advice in

  • Hi,
    I am using a Retropie 4.6 on a Pi 4 - 8gb model. Display is all ok and fine on my 27" LCD monitor. When I am trying to connect it to my Samsung 55" HD TV (QE55Q70RATXXU) every time I am getting 'No signal/No HDMI cable connected" on my TV's HDMI 2 connection. A TV box is connected on TV's HDMI 1. This is a smart TV. I am using official Raspberry Pi 4 power supply with 5.1V and 3.0A rating. Pi is in Argon1 case. I have tried all below settings in config.txt


    Nothing is working for me to get the display on the TV.
    Other thing I noted that after trying to connect to TV when I connect Pi back on my LCD monitor it won't show display for some reason. I have to remove the power USB C connection from Pi and then reconnect it to get the display back and I can see the boot loader screen. After that no Retropie logo or ES screen. I have to press 'F4' and it shows the terminal screen. I have to remove the 'hdmi_force_hotplug=1' from the config.txt file and reboot the Pi to get everything back to normal. This happens only after I tried the Pi on HD TV, otherwise 'hdmi_force_hotplug=1' works fine with the monitor.

    I want some setting for my Pi to work on both my monitor and HD TV. Any help please.

  • Global Moderator

    Can you try adding to your config.txt


    and see if you get an image on your TV ? If that doesn't work, try a different HDMI port on your TV.

  • @mitu Thanks for the reply.
    Should I use 'hdmi_safe=1' with all the above settings in the config.txt or just use this on its own and disable the rest?

  • Global Moderator

    @aadi You can leave just hdmi_safe=1 and comment out your additions.

  • @mitu Leaving just 'hdmi_safe=1' and commented out above entries not making any difference. It seems like nothing is connected at all. No connection. Have also tried different HDMI ports on the TV but it is same. I am totally lost now, please help.

  • Global Moderator

    @aadi Post you entire config.txt on and provide the link.

  • @mitu Here you go config.txt

  • Global Moderator

    I'd advise to drop the overclock and try with a simpler config.txt:

    # Enable DRM VC4 V3D driver on top of the dispmanx display stack

  • I am experiencing this exact issue with a Samsung UN55MU800D (55" as well). I have scoured the internet without success for a solution to get the Pi to work on the tv. I currently have it attached to a 32" Samsung smart tv, no issues at all. It also works on computer monitors.

    I too have tried the usual HDMI tweaks in config.txt. None of these have helped including HDMI safe mode. I have gone as far as to create other disks with 64-bit Raspberry Pi OS and Ubuntu, use different HDMI cables, and run the signal through a receiver, all with the same issue of no signal detected.

    I am by no means an expert, I'm a hobbyist who knows enough to be dangerous. I vaguely remember there being a service menu on Samsung TVs that gives controls well beyond that of the standard menu. I will try to remember the codes to get in there and see if there is anything of use.

  • Global Moderator

    @anorine if you're willing to experiment, can you dump the EDID of the TV and post it here ? You need to use SSH to connect to your Pi and run

    tvservice -d UN55MU800D.edid
    base64 UN55MU800D.edid
    # post the resulting text

  • I had a similar problem with a older SAMSUNG tv, here is what worked for me:

  • I used to have issues with my pi4 2GB getting to display 1080p on my 4k vizio tv.
    A firmware update might've fixed it. Updating retropie and answering yes to updating the kernel should do it. If not, run sudo rpi-eeprom-update manually.
    I have also tested on two different 4k samsung tv's. I don't remember the model numbers. The 40in is 3-4yrs old. The 65in is 1-2yrs old.
    I use:

  • @mitu Here's the text that came out after the commands:


    Additionally, after hours of messing with this, when I plugged it in today it was magically working. I had just rebuilt the box after an issue with SSD corruption. I'm still willing to pull data/test to help anyone else who has come across this issue. I also plan on rebooting a few times to see if this is a fluke.

Contributions to the project are always appreciated, so if you would like to support us with a donation you can do so here.

Hosting provided by Mythic-Beasts. See the Hosting Information page for more information.