Spoke too soon, got my hands on the service manual, but it's not very helpful unfortunately. The troubleshooting step is essentially "issue on T-Con?: Replace T-Con", no more detail than that.

I'll keep an eye out for a replacement T-CON, seems they're generally low availability, at least at non-ludicrous prices.
The service manual is another challenge to get, seems they're also like unobtanium.
I had a look for an authorised Samsung repair shop as well, since they'd have access to the diagnostic flows and service manuals. Seems the only one in my country closed last year 🙄

Yeah that's true. Do you know where I could find the firmware image for the T-con? I'd need to source an eMMC flasher in the meantime as well.

That was my initial impression too, but it seems odd that both processors would have corrupted firmware in the exact same way since they each have a dedicated eMMC, unless there was an interrupted update procedure where both eMMCs were being flashed simultaneously. It does also fallback successfully to FW#2, so my theory here is that FW#1 is something like a factory calibration FW, and is wiped prior to shipping allowing the processor to fallback to the consumer firmware in slot 2 on boot.

Found a UART Tx test point for the 2 display processors on the T-CON board. They're both outputting the same thing, and boot-looping with the following output about once per second.
```
_____ BTA0BL1 Core[0] EMMC_____
ERROR : FW#1_CORE0 magickey error(0x0)
BL1 EMMC FW#2 core0,1
_________________ BTA0FW DQHD(VD) _________________
Keil 5060183, Build(Apr 23 2023 14:06:03)
Multi Inferface Master SPI Init
FW 1, CFG/MS 1
Boot GPIO CNT Over
system reset!
```

Same issue, UART log hangs on a repeating `SecDrvTcon_ReadPowerOnStatus: 00 00 00 00`. I'll keep an eye out for a replacement T-CON board, and in the meantime continue trying to root-cause it in case it's an easily obtained component that needs replacing.

I found a UART Tx pin on the main board that seems to be attached to the main SoC, and is sending out a system log. I've attached a dump of the startup sequence, but the main takeaway is that startup is stalling on a repeating log output of `SecDrvTcon_ReadPowerOnStatus: 00 00 00 00`.
This points towards the power management on the TCON board being at fault (or something in that general direction). I did find that the 'PMIC_FB33_ALERT' test point was high, though I'm not sure if this is alert asserts on high or low level. The 3.3v test point reads 3.3v.
I have a thermal scope that...

Tried a replacement mainboard (BN41-03181A/BN94-18231Z), same issue persists. It's from a trusted seller, so unlikely (though not impossible) that the replacement has the same fault as the original.
I'll probe around some of the test points to see if I can narrow down the fault....

I've dumped the 2 16MB Winbond flash chips on the bottom of the main board. The left-hand one is erased and contains only 0xFF repeating. The rightmost contains what looks like valid data (found some ascii strings amongst general random binary).

Does anyone know what I should expect from these 2 chips? Or how I might verify if one/both has corrupted?

Re: New Members - please post your introductions here

Hello, here looking for help with a broken tv