SamyGO

erdem_ua wrote: Smartsmurf, does u-boot can't help here?
Doesn't it executed before loading linux kernel?
Could trying external firmware might be a solution?

On CI devices - yes. AFAIK, on CI+ devices the secured bootloader directly loads the kernel. I was not able to enter u-boot.

Might your u-boot haven`t been re-flashed?

It is definitely CI+ device looking at your full model number...Sorry...

Give please other log files to inspect.

How about u-boot?

Now you have to bring it to Service and say, you have upgraded your TV with right firmware according user manual.

My apologies...

As i know (no one reported else in this forum and few other abroad forums about samsung and samygo bricked devices - Service does not check anything on TV - it changes mainboard and gives TV back to user if tv is under warranty.
So you can say a laud your problem occur after normal flashing with right firmware downloaded from samsung.
I do not believe anyone dumps mainboard directly from NAND for reason. Feel free to go to Service.


p.s. i merge your topic with related FFB repair topic.

juuso wrote:So you can say a laud your problem occur after normal flashing with right firmware downloaded from samsung.

I would not do so. For example the german Samsung page states:

www.samsung.de wrote: Bitte beachten Sie: Ein BIOS-, Firmware- oder Micom-Update geschieht immer auf eigenes Risiko und ist von der Garantie/Gew?hrleistung ausgeschlossen! Nur die Verwendung der Firmware von samsung.de schlie?t eventuelle Defekte am Ger?t aus.

Basically it says, that BIOS, firmware or micom updates will not be covered by warranty. So better claim, it just broke without any change on it...