Philips 55PUS7909

[Narex]

Hello.
I have a broken Philips 55PUS7909 TV. The board number is 715rlpcb0000000401.
After connecting to power supply, the backlight turns on for 15 seconds and then turns off. No other signs of life. I tried wipedatatool but without success. I also searched the forum, but I did not specifically encounter this problem. TV is not stuck in bootloop.
Can anyone tell if the error is in the eMMC or in some processor?

Thanks

Similar topic
https://www.badcaps.net/forum/showth...t=72767&page=2

Here is the service log:
^@/��S����[   0] sys_init start. boot_strap=0x00000514 (source=eMMC), boot_state=0x0
08:16:20.128 ^M^M^^^^M  248] image verified, start at 0x^M0920000...
08:16:20.375 ^M^^^^^Mz kernel starting... MV88DE3114(BG2Q)‑A1 total 4 cpu^^^^^^^^^M, v2.0.0.21, Aug 5 2014 14:39:52
08:16:20.419 0213[  303] start_bootloader
08:16:20.428 ^MU�URx_message 5b 5b 20 
08:16:20.505 ^MLAUNCH_ITM is set to zero
08:16:20.507 ^Mboard_number = 9
08:16:20.509 ^MuiBoot = 0
08:16:20.510 
08:16:20.510 ^MI2C switch set as 0
08:16:20.512 
08:16:20.662 ^MI2C switch set as 1
08:16:20.664 ^M‑‑‑‑‑‑‑‑‑ I2C Initialization^^^^^^^^M‑‑‑‑‑‑‑‑‑‑
08:16:20.668 ^MI2C_INIT: I2C‑2 bus 
08:16:20.669 I2C_INIT: I2C‑1 bus 
08:16:20.675 I2C_INIT: I2C‑0 bus 
08:16:20.683 ^MDD^^^^^^^^^^^^^^^M reg 0xF7CB0BAC value : 0x00021421 
08:16:20.687 ^MDDR reg 0xF7CB0C00 value : 0x00004031 
08:16:20.690 ^Mleakage info 608.
08:16:20.692 cpu from 1200 to 1275
08:16:20.695 ^Mset vcpu to 1225mv
08:16:20.697 set vcpu to 1250mv
08:16:20.700 set vcpu to 1275mv
08:16:20.704 set Vcpu to 1275 mv.
08:16:20.708 core from ^^^^^^^M200 to 1125
08:16:20.711 ^Mset Vcore to 1175mv
08:16:20.713 ^Mset Vcore to 1150mv
08:16:20.715 set Vcore to 1125mv
08:16:20.718 set Vcore to 1125 mv.
08:16:20.721 ^M^^^Mlash_ts_init() success.
08:16:20.839 
08:16:20.839 ^MRDKDMP BG2Q [Oct^^^M27 2017 18:04:12]
08:16:20.842 ^MPinmux configuration:
08:16:20.844 
08:16:20.844 GSM 0xf7fcd040 0x009c0261;
08:16:20.847 ^M0xf7ea0014: 00000072 00240611 00000253 1249008a 
08:16:20.851 ^M0xf7ea0028: 01249492 00000048 1ca54009 0430e44d 
08:16:20.856 ^M0xf7ea003c: 00000000 00000000 0000001f 63c06a52 
08:16:20.860 ^MClock configuration:
08:16:20.862 ^M VCO_B^I^Ifrequency 1620
08:16:20.865 ^M AVPLLB[4]^Ifrequency 300
08:16:20.867 ^M AVPLLB[5]^Ifrequency 800
08:16:20.869 ^M AVPLLB[6]^Ifrequency 1680
08:16:20.872 ^M AVPLLB[7]^Ifrequency 610
08:16:20.874 ^M cpuP^^^^^^Ml^I^Ifrequency 1200
08:16:20.876 ^M memPll^I^Ifrequency 1500
08:16:20.878 ^M sysPll^I^Ifrequency 800
08:16:20.881 ^M dClk^I^Ifrequency 375
08:16:20.882  cpuClk^I^Ifrequency 1200
08:16:20.885 ^M sysClk^I^Ifrequency 400
08:16:20.887 ^M drmClk^I^Ifrequency 400
08:16:20.889 ^M cfgClk^I^Ifrequency 100
08:16:20.891 ^M gfxClk^I^Ifrequency 400
08:16:20.893 ^M zspClk^I^Ifrequency 400
08:16:20.895  perifClk^Ifrequency 200
08:16:20.898 ^M pCubeClk^Ifrequency 610
08:16:20.900 ^M vScopeClk^Ifrequency 610
08:16:20.902 ^M nfcEccClk^Ifrequency 100
08:16:20.905 ^M vppSysClk^Ifrequency 400
08:16:20.907 ^M appClk^I^Ifrequency 800
08:16:20.909 ^M gfx3DCoreClk^Ifrequency 420
08:16:20.912 ^M gfx3DSysClk^Ifrequency 400
08:16:20.914 ^M arcRefClk^Ifrequency 400
08:16:20.917 ^M vipClk^I^Ifrequency 400
08:16:20.919 ^M sdioXinClk^Ifrequency 200
08:16:20.921 ^M sdio1XinClk^Ifrequency 200
08:16:20.924 ^M gfx3DShClk^Ifrequency 420
08:16:20.926 ^M avif0Clk^Ifrequency 300
08:16:20.928 ^M avif1Clk^Ifrequency 300
08:16:20.931 ^M[00,sd00] bootloader: part1(start=0, blks=1, version=201710271804), part2(start=0, blks=1, version=000000000000)
08:16:20.941 ^M[01,sd01] fts: part1(start=32, blks=32, version=201710271804), part2(start=32, blks=32, version=000000000000)
08:16:20.951 ^M[02,sd02] recovery: part1(start=64, blks=120, version=201710271804), part2(start=64, blks=120, version=000000000000)
08:16:20.961 ^M[03,sd03] tzk_recovery: part1(start=184, blks=8, version=201710271804), part2(start=184, blks=8, version=000000000000)
08:16:20.972 ^M[04,sd04] factory_setting: part1(start=192, blks=128, version=201710271804), part2(start=192, blks=128, version=000000000000)
08:16:20.983 ^M[05,sd05] itm: part1(start=320, blks=128, version=201710271804), part2(start=320, blks=128, version=000000000000)
08:16:20.994 ^M[06,sd06] boot: part1(start=448, blks=24, version=201710271804), part2(start=448, blks=24, version=000000000000)
08:16:21.004 ^M[07,sd07] tzk_normal: part1(start=472, blks=8, ver^^^^^^^^^Mion=201710271804), part2(start=472, blks=8, version=000000000000)
08:16:21.014 [08,sd08] system: part1(start=480, blks=1600, version=201710271804), part2(start=480, blks=1600, ve^^Msion=000000000000)
08:16:21.025 ^M[09,sd09] user_setting: part1(start=2080, blks=960, version=201710271804), part2(start=2080, blks=960, version=000000000000)
08:16:21.037 ^M[10,sd10] cache: part1(start=3040, blks=896, version=201710271804), part2(start=3040, blks=896, version=000000000000)
08:16:21.047 ^M[11,sd11] firmware: part1(start=3936, blks=64, version=201710271804), part2(start=3936, blks=64, version=000000000000)
08:16:21.058 ^M[12,sd12] factory_data: part1(start=4000, blks=32, version=201710271804), part2(start=4000, blks=32, version=000000000000)
08:16:21.069 ^M[13,sd13] userdata: part1(start=4032, blks=3328, version=201710271804), part2(start=4032, blks=3328, version=000000000000)
08:16:21.080 ^Mget macaddr from fts: 1c:5a:6b:7d:10:ef
08:16:21.084 ^Mmacaddr=1c:5a:6b:7d:10:ef
08:16:21.086 ^Mtzk boot with normal mode by default
08:16:21.090 ^Mstart to kick off SM CPU: start 0x3ff0449c, size 63216
08:16:21.095 ^^MSM ^^^MPU is kicked [o f f. 
08:16:21.127 ^M L 1as]Itp(oSwMe)r:m oendtee irs maniont 
08:16:21.131 S^Mt[ a n db y f t s6:]W (cSraMs)h:c oEuntnetreri.nag naddroci_di:n i3t.
08:16:21.137 
08:16:21.137 f^Mt[s :  bo o t1l2]oaWd(eSrM).c:o mLemaavndi:n g 
08:16:21.142 ^Madc_init.
08:16:21.143 ^M[   18]W(SM): PWM Initialized
08:16:21.146 ^M[   21]I(SM): begin to run tasks
08:16:21.149 ^^^^^M[   514]W(SM): Joystick connected 
08:16:21.642 ^M^^^Merify boot image passed.
08:16:22.053 ^M^^^MTP Temperature: 0 celsius ^Megree
08:16:22.078 ^MChip Version: 0xa1d
08:16:22.080 ^MSend bootmode=0 to SM.
08:16:22.082 ^Mget macaddr from fts: 1c:5a:6b:7d:10:ef
08:16:22.086 ^Mmacaddr=1c:5a:6b:7d:10:ef
08:16:22.088 ^MGenerated bootargs: androidboot.hardware=AND1E quiet lpj=11935744 root=/dev/ram0 androidboot.console=ttyS0 console=ttyS0,115200 init=/init vmalloc=448M quiet macaddr=1c:5a:6b:7d:10:ef emmc_ts.dev_id=1 emmc_ts.size=16777216 emmc_ts.erasesize=524288 emmc_ts.wr^^^^^^^^^^Mtesize=512
08:16:22.113 update system memory region: (0x01000000, 0x3f800000)‑>(0x40000000, 0x00800000)
08:16:22.121 update system^^^^^^^^^^^^^^^^^^^^^^^^^Mmemory region(TZ): (0x40000000, 0x00800000)‑>(0x40000000, 0x40000000)
08:16:22.131 ion_pool_num : 0x00000004, ion‑attributes‑num‑per‑pool : 0x00000002
08:16:22.138 pool[0]: name: SW_noncache, base =0x02800000 , size = 0x00800000 ion_attr[0]: 0x00000002 ion_attr[1]: 0x00000939 
08:16:22.149 ^Mpool[1]: name: SW_other, base =0x03000000 , size = 0x16c00000 ion_attr[0]: 0x00000002 ion_attr[1]: 0x00000f3d 
08:16:22.159 ^Mpool[2]: name: NW_all, base =0x19c00000 , size = 0x22300000 ion_attr[0]: 0x00000002 ion_attr[1]: 0x00000f36 
08:16:22.169 ^Mpool[3]: name: NW_noncache, base =0x3bf00000 , size = 0x02000000 ion_attr[0]: 0x00000002 ion_attr[1]: 0x00000f3a 
08:16:22.179 ^MRespo^^^^Mding to SM...
08:16:22.181 ^Mdon't do dts customization for A1D
08:16:22.184 ^M[ 2062] Boot normal GTV image
08:16:22.187 Start kernel at 0x40008000
08:16:22.193 ^^^MUncompressing Linux..^M^^Mdone, booting the kernel.
08:16:33.302 ^@
08:16:39.117 Connection lost

[Narex]

Re: Philips 55PUS7909 no picture

does anyone know what the problem is?

[Maalobs]

Re: Philips 55PUS7909

Where did you catch the bootlog from, did you record serial output from SOC-TXD-SERVICE?

You seem to have some setting incorrect in your serial adapter, use 8N1 (8-bit, no parity, 1 stop bit) and try different speeds, start with 115200 and 57600.
Control characters have been inserted and some characters have been replaced, maybe entire lines are missing.
From the output that you do have, it looks like the system has successfully reached the transition away from the semi-standby state, and there it halts, so maybe it entered protection mode.
If you can record a bootlog without artefacts, perhaps there is additional information there?

You can download the service manual for your model from this page.

Chapter 5 is the interesting part for you, and read through section 5.5.1 first.
If you attach mains power and leave it for several minutes, does the TV eventually begin blinking the power LED according to signals in table 5-1?
Study the fault finding flowcharts in sections 5.3.1 to 5.3.6.

If you identify all of the various power rails and measure resistance to ground from each of them, maybe you'll find a short circuit?
The service manual covers several models, so refer to table 2-1 to find the circuit diagrams and PCB layouts that are specific to your model.

See what happens if you unplug backlight, Ambilight, and even the TCON board, can you produce a different error condition?

There seems to be a hardware SDM in this model, at least according to the flowcharts.
If you follow those comments and start the TV in SDM mode, then it will override the protection mode and you will be able to measure voltages on all power rails.
Do that in short bursts, one rail at a time, so you don't leave it on for too long and maybe fry something that is drawing too much power.