Announcement

Collapse
No announcement yet.

Philips 55pfs8159 android tv bootloop

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

    #41
    Re: Philips 55pfs8159 android tv bootloop

    Originally posted by samtron123 View Post
    so far I have the data on USB stick but I do not see, because television does not have a picture or menu, just stay on the light
    you make us confuse about your posting.. now you write TV stay on and nothing on screen. and you wrote and joined this thread which it is boot loop

    Originally posted by samtron123 View Post
    Hello how many thanks firstly
    unfortunately I do not get that far, I tried everything,
    I come to nothing in recovery mode no screen is displayed
    i was wondering how TV with boot loop can write data on USB as you showed us at yours posts #36 attachment

    your TV seem not boot loop you have other hard ware issue who knows.. let some one near to you check it and test it.. sorry i cant help any more

    Comment


      #42
      Re: Philips 55pfs8159 android tv bootloop

      Originally posted by Alschepmist View Post
      So now with extra tool i can acces emmc with my pc as any one a dump or recovery.img file?

      Hello, I wrote about it all the time
      what are you writing me
      have you read the schematic synonymous, what a problem is when the background light is on but no picture and menu only sound is there ??

      Comment


        #43
        Re: Philips 55pfs8159 android tv bootloop

        Hello everybody
        is there a possibility for this problem, can one delete and reprogram the EMMC with Jtag ??
        many thanks

        Comment


          #44
          Re: Philips 55pfs8159 android tv bootloop

          I had the same one a few years ago. Unfortunately, it was burned... You are lucky if you have this one.

          Comment


            #45
            Re: Philips 55pfs8159 android tv bootloop

            Originally posted by JessieNelson View Post
            I had the same one a few years ago. Unfortunately, it was burned... You are lucky if you have this one.

            Hello, I have a question
            which EMMC chip is there?
            Unfortunately, I can not read mine
            where did you burn?
            many thanks

            Comment


              #46
              Re: Philips 55pfs8159 android tv bootloop

              How do you get the NAND empty when it's full?

              Comment


                #47
                Re: Philips 55pfs8159 android tv bootloop

                Good day, Can connect to PC and lerren the memory
                one more question which NAND is there in the description I need
                many thanks

                Comment


                  #48
                  Re: Philips 55pfs8159 android tv bootloop

                  Hello can someone help me?
                  is it possible to create a protocol from this TV?
                  I have a usb uart silicon labs unfortunately I get from TV no protocol but only garbage as a special sign
                  many thanks

                  Comment


                    #49
                    Re: Philips 55pfs8159 android tv bootloop

                    Originally posted by Alschepmist View Post
                    So i think iv founded the problem a corrupted firmware i think or bootloader
                    with uart mode (iv new uart programator ) i become this code


                    FATAL ERROR! There is no bootable image on this machine!

                    Code:
                    I2C switch set as 1
                    --------- I2C Initialization ----------
                    I2C_INIT: I2C-2 bus
                    I2C_INIT: I2C-1 bus
                    I2C_INIT: I2C-0 bus
                    DDR reg 0xF7CB0BAC value : 0x00021421
                    DDR reg 0xF7CB0C00 value : 0x00004031
                    leakage info 464.
                    set Vcpu to 1300mV, default setting by hardware.
                    set Vcore to 1150mV, default setting by hardware.
                    flash_ts_init() success.
                    
                    RDKDMP BG2Q [Oct 27 2017 18:04:12]
                    Pinmux configuration:
                    
                    GSM 0xf7fcd040 0x009c0261;
                    0xf7ea0014: 00000072 00240611 00000253 1249008a
                    0xf7ea0028: 01249492 00000048 1ca54009 0430e44d
                    0xf7ea003c: 00000000 00000000 0000001f 63c06a52
                    Clock configuration:
                     VCO_B     frequency 1620
                     AVPLLB[4]   frequency 300
                     AVPLLB[5]   frequency 800
                     AVPLLB[6]   frequency 1680
                     AVPLLB[7]   frequency 610
                     cpuPll     frequency 1200
                     memPll     frequency 1500
                     sysPll     frequency 800
                     dClk      frequency 375
                     cpuClk     frequency 1200
                     sysClk     frequency 400
                     drmClk     frequency 400
                     cfgClk     frequency 100
                     gfxClk     frequency 400
                     zspClk     frequency 400
                     perifClk    frequency 200
                     pCubeClk    frequency 610
                     vScopeClk   frequency 610
                     nfcEccClk   frequency 100
                     vppSysClk   frequency 400
                     appClk     frequency 800
                     gfx3DCoreClk  frequency 420
                     gfx3DSysClk  frequency 400
                     arcRefClk   frequency 400
                     vipClk     frequency 400
                     sdioXinClk   frequency 200
                     sdio1XinClk  frequency 200
                     gfx3DShClk   frequency 420
                     avif0Clk    frequency 300
                     avif1Clk    frequency 300
                    [00,sd00] bootloader: part1(start=0, blks=1, version=201710271804), part2(start=
                    0, blks=1, version=000000000000)
                    [01,sd01] fts: part1(start=32, blks=32, version=201710271804), part2(start=32, b
                    lks=32, version=000000000000)
                    [02,sd02] recovery: part1(start=64, blks=120, version=201710271804), part2(start
                    =64, blks=120, version=000000000000)
                    [03,sd03] tzk_recovery: part1(start=184, blks=8, version=201710271804), part2(st
                    art=184, blks=8, version=000000000000)
                    [04,sd04] factory_setting: part1(start=192, blks=128, version=201710271804), par
                    t2(start=192, blks=128, version=000000000000)
                    [05,sd05] itm: part1(start=320, blks=128, version=201710271804), part2(start=320
                    , blks=128, version=000000000000)
                    [06,sd06] boot: part1(start=448, blks=24, version=201710271804), part2(start=448
                    , blks=24, version=000000000000)
                    [07,sd07] tzk_normal: part1(start=472, blks=8, version=201710271804), part2(star
                    t=472, blks=8, version=000000000000)
                    [08,sd08] system: part1(start=480, blks=1600, version=201710271804), part2(start
                    =480, blks=1600, version=000000000000)
                    [09,sd09] user_setting: part1(start=2080, blks=960, version=201710271804), part2
                    (start=2080, blks=960, version=000000000000)
                    [10,sd10] cache: part1(start=3040, blks=896, version=201710271804), part2(start=
                    3040, blks=896, version=000000000000)
                    [11,sd11] firmware: part1(start=3936, blks=64, version=201710271804), part2(star
                    t=3936, blks=64, version=000000000000)
                    [12,sd12] factory_data: part1(start=4000, blks=32, version=201710271804), part2(
                    start=4000, blks=32, version=000000000000)
                    [13,sd13] userdata: part1(start=4032, blks=3328, version=201710271804), part2(st
                    art=4032, blks=3328, version=000000000000)
                    get macaddr from fts:
                    cpu id:38bdc6b3 5359eb9c
                    macaddr=00:B3:53:59:EB:9C
                    tzk boot with normal mode
                    start to kick off SM CPU: start 0x3ff0449c, size 63216
                    SM CPU is kicked [ of f .
                     L 1as]It(pSoMwe)r:m eondte eirs mnaoint
                    St[a nd b y 6]W(SM): Entering adc_init.
                    [   10]W(SM): Leaving adc_init.
                    [   13]W(SM): PWM Initialized
                    [   16]I(SM): begin to run tasks
                    [   509]W(SM): Joystick connected
                    [3.019337] TZ CPU0 ERROR[tz_sw_verify_image:75] verify image fail, src=0x19c0000
                    0, len=0x004c0c00, dst=0x19c00000GIH magic num is not correct (0x482a4d49 != 0xe
                    ea8f2bc)!!!
                    FATAL ERROR! There is no bootable image on this machine!
                    tbdzz---- Img_Ld_And_Start error! Spinning now!
                    œëYS³Æ½8[   0] sys_init start. boot_strap=0x00000514 (source=eMMC), boot_state
                    =0x0
                    [  278] image verified, start at 0x00920000...
                    tz kernel starting... MV88DE3114(BG2Q)-A1 total 4 cpus, v2.0.0.21, Aug 5 2014 1
                    4:39:52
                    0321[  333] start_bootloader
                    UªULAUNCH_ITM is set to zero
                    board_number = 6
                    uiBoot = 0
                    
                    I2C switch set as 0
                    Hello, I'm net here but have the same TV and the same problem. Mine also reboots on the Philips logo. Did you even fix this ?

                    (How did you get the logs ?)

                    Danke

                    Comment


                      #50
                      Re: Philips 55pfs8159 android tv bootloop

                      try with win 7 32 bit usb uart silicon
                      Last edited by samtron786; 08-27-2020, 04:45 AM.

                      Comment


                        #51
                        Re: Philips 55pfs8159 android tv bootloop

                        Win XP

                        Comment


                          #52
                          Re: Philips 55pfs8159 android tv bootloop

                          Hello, together give new version of Youtube for philips 55pfs8159 ??
                          many thanks

                          Comment


                            #53
                            Re: Philips 55pfs8159 android tv bootloop

                            is it a problem of every Android TV? I have an AKAI repaired at november, now i cant sell it no more because Youtube no more works..

                            Comment


                              #54
                              Re: Philips 55pfs8159 android tv bootloop

                              .........
                              Last edited by Diah; 03-12-2021, 07:41 AM.

                              Comment


                                #55
                                Re: Philips 55pfs8159 android tv bootloop

                                Why you give me your advices? Wasn't i not a professor? I already installed that app and also others and it doesn't work... just to complete my sentence i had contacted local Akai support and after pathetic waste of time in their tests it ended up on their request for payed assistance that i obviously declined.. my *alls goes to full.. damned smart TVs
                                Last edited by Davi.p; 03-12-2021, 07:06 AM.

                                Comment

                                Working...
                                X