logo elektroda
logo elektroda
X
logo elektroda

Philips 42PFL6008S/12 TV: Unresponsive Remote & Keyboard, Error 22, Chassis QFU 1.2E LA

Top Serwis 11742 8
ADVERTISEMENT
Treść została przetłumaczona polish » english Zobacz oryginalną wersję tematu
  • #1 16110423
    Top Serwis
    Level 24  
    After turning on, the TV does not respond to the remote control or the keyboard, the stby does not light up.
    After about a minute, the stby LED. error signals 2 short flashes pause and 2 short flashes.
    The chassis of this tv is QFU 1.2E LA, there is no error 22 description in the description of this model.
    The voltage from the power supply and on the board is correct. The TV does not respond to the rescue soft pendrive.
    Request for help.
  • ADVERTISEMENT
  • #2 16111825
    lisek
    Service technician RTV
    W trybie SDM masz ten error22 ?
    - w stby Led miga x2 dwa razy to nic nie znaczy
    * zazwyczaj jak wejdziesz w SDM to error 53 (NAND)

    Przy czym może to być:
    - uszkodzenie CPU, zasilanie np. 1.25V, inne zasilanie 2,5V
    - wsad NAND, ..... ?

    Quote:
    Chassis QFU1.2E LA
    HiDTV FUSION

    The QFU1.2E LA chassis is part of the FUSION platform and
    covers sets in the 6xxx, 7xxx, 8xxx and 9xxx range.
    QFU1.2
    - 40/46/55/60PFL8008s
    - 42/47/55PFL7#08
    - 42/47/55PFL6008
    * all P/nr. : 3104 313 66124 / or 3104 303 54945

    It uses the same chipset as the earlier QFU1.1E LA chassis.
    * MediaTek MT5580 one-core
    * QFU2.1E LA/ QFU1.1E LA (cpu: Trident fusion240) / QFU1.2E LA

    Only circuits that differ from this chassis are described in this
    manual. For all other info, refer to the QFU1.1E LA manual.


    Philips 42PFL6008S/12 TV: Unresponsive Remote & Keyboard, Error 22, Chassis QFU 1.2E LA

    Z SM
    Quote:
    Back-up Software Upgrade Application If the default software upgrade application does not start (could be due to a corrupted boot sector) via the above described method, try activating the “back-up software upgrade application”.

    How to start the “back-up software upgrade application” manually :

    1. Disconnect the TV from the Mains/AC Power.
    2. Press the “CURSOR DOWN”-button on a Philips TV remote control while reconnecting the TV to the Mains/AC Power.
    *(attention : not supported by use of RF4CE remote due to the fact this application is not running yet at the time of the “CURSOR-DOWN” request ).
    3. The back-up software upgrade application will start.
  • ADVERTISEMENT
  • #3 16117710
    tomasz wojcicki
    Level 23  
    In this case, replacement of DDR memory can also help, as long as hynix companies are used.
  • #4 16119628
    Top Serwis
    Level 24  
    Ram is Hynix.
  • ADVERTISEMENT
  • #5 16119951
    tomasz wojcicki
    Level 23  
    What error is when you short the SDM jumper ??
  • #6 16121279
    Top Serwis
    Level 24  
    Error 53 in SDM mode.

    Added after 1 [hours] 30 [minutes]:

    In SDM mode, I connected to the network with the down arrow button pressed and the TV came to life.
    I'm testing for now.
  • ADVERTISEMENT
  • #7 16121496
    tomasz wojcicki
    Level 23  
    Unfortunately, I have to withdraw my post about dramatic memory because my play came back with the same symptom after 2 weeks :(
  • #8 16121513
    Top Serwis
    Level 24  
    It may also be the case in this case, because tv froze the image for a while, a strange pixelosis and restart appeared. So the damage is probably "maturing".
  • #9 16133540
    Top Serwis
    Level 24  
    The next day the problem returned. At the customer's request, I replaced the motherboard, which restored proper operation.

Topic summary

The Philips 42PFL6008S/12 TV exhibits an unresponsive state with no reaction to the remote or keyboard, indicated by a standby LED signaling error 22 (two short flashes, pause, two short flashes). Users suggest that the issue may stem from a faulty CPU or NAND memory, with error 53 appearing in SDM mode. One user successfully revived the TV by connecting it to power while pressing the down arrow button, but the problem recurred after two weeks. Ultimately, replacing the motherboard resolved the issue, restoring normal functionality.
Summary generated by the language model.
ADVERTISEMENT