logo elektroda
logo elektroda
X
logo elektroda
Advanced Search
logo elektroda

49PUS7909/12 QV14.1E_LA UART Logs Show Boot Loop, USB Firmware Not Executing

benjavd 1329 7
ADVERTISEMENT
Report a violation of the law
Reply | New topic

  • USB drive detected but firmware not executing

    #1 21791722
    benjavd
    Level 2  
    Posts: 4
    Hello,

    My television is no longer booting - 49pus7909_12 QV14.1E_LA chassis LCD.
    I connected it using a UART board and was able to retrieve the console logs.
    I tried booting from a FAT-formatted USB drive with autorun_AND1E_000.010.170.000.upg placed in the root folder, and then with WipeDataTool.upg, but it seems that the USB files cannot be executed.

    I am attaching the logs from a normal (failing) boot and a boot while pressing the joystick down (recovery mode).

    During a normal start, the TV only shows the Philips logo.
    In recovery mode, the screen stays pink/violet.

    Thank you very much for any ideas or help.
    Best regards,
    Benjamin
    AI: Could you please provide details about the USB drive you are using (brand, capacity, exact formatting method), and confirm whether the TV shows any sign of detecting the USB (such as LED activity or messages in the UART logs) when it is inserted?
    It's an 8 GB USB key, formatted as FAT. When I plug the USB in I see those messages at the console:
    [ 25.989857] sd 0:0:0:0: [sda] No Caching mode page found
    [ 25.995394] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 26.005477] sd 0:0:0:0: [sda] No Caching mode page found
    [ 26.011073] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 26.022242] sd 0:0:0:0: [sda] No Caching mode page found
    [ 26.027792] sd 0:0:0:0: [sda] Assuming drive cache: write through

    AI: During the boot process (both normal and recovery modes), do you notice any blinking LEDs, error codes on the screen, or sounds from the TV that might help identify the stage at which it fails?
    No, the only thing I see is what's explained in the post.
    Attachments:
    • boot_logs_recovery.txt (18.82 KB) You must be logged in to download this attachment.
    • boot_logs.txt (8.52 KB) You must be logged in to download this attachment.
  • ADVERTISEMENT
  • ADVERTISEMENT
  • #3 21794382
    tmszwojcicki
    Level 16  
    Posts: 195
    Help: 15
    Rate: 58
    Find on the web the upgrade_loader file for this chassis....
  • ADVERTISEMENT
  • #4 21796464
    benjavd
    Level 2  
    Posts: 4
    >>21794382

    Hello, seems a nice idea, but I can't find it for this chassis.
    Any advice is welcome.

    Thanks in advance,
    Benjamin
  • ADVERTISEMENT
  • #5 21797122
    ARMAGEDOON
    Level 16  
    Posts: 109
    Help: 16
    Rate: 29
    Create a directory on usb upgrades and upload autorun_AND1E_000.010.170.000.upg to it
    Create on usb catalog upgrades and upload autorun_AND1E_000.010.170.000.upg

  • USB firmware not executed despite normal boot logs

    #6 21797187
    benjavd
    Level 2  
    Posts: 4
    Hello,
    Thanks for your advice.
    Unfortunately, the file is not executed...

    End of the normal boot:
    ...
    MV_OPENCRYPTO_DeviceKey_Initialize, line: 299, otp_status = 0xff
    MV_OPENCRYPTO_DeviceKey_Initialize, line: 301, tmp_test = 0xc
    rkek be selected
    BindInfo:
    00000000 00000000 00000000 00000000 543581d7 63b34296 00000000 48000000 3dffefea 0000186a 000000ff 2d06d12d 5f0ee799 078040e2
    [ 2.079448] sd 0:0:0:0: [sda] No Caching mode page found
    [ 2.085007] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 2.095207] sd 0:0:0:0: [sda] No Caching mode page found
    [ 2.100697] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 2.110698] sd 0:0:0:0: [sda] No Caching mode page found
    [ 2.116224] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 2.457481] FW is downloaded
    [ 2.494896] vmeta user count:0, set voltage 1150000:1150000
    [ 2.988661] usb_reset_device() successful.
    [ 3.091661] init: cannot find '/system/bin/rild', disabling 'ril-daemon'
    [ 3.100453] init: cannot find '/system/etc/install-recovery.sh', disabling 'flash_recovery'
    [ 3.110927] init: cannot find '/system/bin/suspend_utils', disabling 'suspend_utils'
    [ 4697]W(SM): msg with invalid func-id 90 or start/end byte has been discarded
    [ 4861]W(SM): Initialising LED intensity values from TV settings database
    [ 4868]W(SM):
    Wake reason 0x0
    [ 4883]W(SM): WM == 0
    [ 5798]I(SM): #########wdt1 enable
    [ 5.052749] init: no such service 'bootanim'
    [ 5.269147] BT: Loading driver
    [ 5.272498] Marvell Bluetooth USB driver
    [ 5.276664] bt_usb_probe: intf bdeaae00 id 7f0eddf0
    [ 5.281529] VID/PID = 1286/2044, Boot2 version = 3201
    [ 5.293198] FW is Active
    [ 5.303245] BT: Create /dev/mbtchar0
    [ 5.363137] BT: Create /dev/mfmchar0
    [ 5.425842] BT: Driver loaded successfully
    [ 24800]W(SM): SOC is Alive !!!
    [ 44801]W(SM): SOC is Alive !!!
    [ 61000]I(SM): Chip Temperature: 38 degC(raw_data = 814)
    [ 64803]W(SM): SOC is Alive !!!

    end of the recovery log boot:
    [DRMFIGO-LOG] - [MV_TSPDRV_CRYPTO_SetReturnAddress] NthCryptoEngineFifoCmdReg [0xf330]
    [DRMFIGO-LOG] - [MV_TSPDRV_CRYPTO_SetReturnAddress] Set Crypto Engine CH[1] uReturnAddress[0x288]
    [DRMFIGO-LOG] - [MV_TSPDRV_CRYPTO_SetReturnAddress] NthCryptoEngineFifoCmdReg [0xf338]
    [DRMFIGO-LOG] - [MV_TSPDRV_CRYPTO_SetReturnAddress] Set Crypto Engine CH[2] uReturnAddress[0x298]
    [DRMFIGO-LOG] - [MV_TSPDRV_CRYPTO_ResetCtrl ] Set Crypto Engine to uResetVal[0]
    [DRMFIGO-LOG] - [MV_TSPDRV_SefEngineInit ] Section Filter Engine Init
    [DRMFIGO***ERROR***] - [MV_TSPDRV_SefEngineInit ] SefEngine already initialized!!
    [DRMFIGO-LOG] - [MV_TSPDRV_SefEngineReset ] Write 1 to RESET bit
    [DRMFIGO-LOG] - [MV_TSPDRV_SefEngineReset ] Disable all rules
    [DRMFIGO-LOG] - [MV_TSPDRV_SefEngineReset ] Clear SECTION RULE SRAM
    [DRMFIGO-LOG] - [MV_TSPDRV_SefEngineReset ] Write 0 to RESET bit
    [DRMFIGO-LOG] - [MV_DMXDRV_SwdEngineReset ] Set SWD to uResetVal[1]
    [DRMFIGO-LOG] - [MV_DMXDRV_SwdEngineReset ] Set SWD to uResetVal[0]
    {line: 128}
    {line: 128}
    {line: 128}
    {line: 128}
    [ 3.304268] vmeta user count:0, set voltage 1150000:1150000
    Alloc CmdQue handler 0x30ddf460
    Alloc List handler 0x30ddf478
    Alloc CmdQue handler 0x30ddf658
    Alloc List handler 0x30ddf670
    Alloc CmdQue handler 0x30ddf850
    Alloc List handler 0x30ddf868
    Alloc CmdQue handler 0x30ddfa48
    Alloc List handler 0x30ddfa60
    {line: 128}
    [ 3.598616] sd 0:0:0:0: [sda] No Caching mode page found
    [ 3.604512] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 3.614491] sd 0:0:0:0: [sda] No Caching mode page found
    [ 3.620001] sd 0:0:0:0: [sda] Assuming drive cache: write through
    [ 3.629866] sd 0:0:0:0: [sda] No Caching mode page found
    [ 3.635387] sd 0:0:0:0: [sda] Assuming drive cache: write through
    sh: rm: not found
    [ 31968]W(SM): SOC is Alive !!!
    [ 51970]W(SM): SOC is Alive !!!
    [ 61000]I(SM): Chip Temperature: 50 degC(raw_data = 846)
    [ 71971]W(SM): SOC is Alive !!!
    [ 91972]W(SM): SOC is Alive !!!
    [ 111974]W(SM): SOC is Alive !!!
    [ 121000]I(SM): Chip Temperature: 52 degC(raw_data = 851)

    I don't understand why the file is not executed...

    Thanks a lot for your help,
    Benjamin
  • #8 21798198
    benjavd
    Level 2  
    Posts: 4
    Thanks for all your advice.
    Unfortunately, it seems the issue occurs before the USB key can be mounted, so the file can't be executed.
    I'm not sure, but anyway, nothing more happens when I plug in the USB key.
    Does it mean that I need to replace the board (or the eMMC)?

    Benjamin
Reply | New topic
Report a violation of the law

Topic summary

LABEL_AI_GENERATED
Philips 49PUS7909/12 LCD TV with QV14.1E_LA chassis is stuck in a boot loop, showing only the Philips logo during normal startup and a pink/violet screen in recovery mode. UART logs were captured, and attempts to run USB recovery firmware from a FAT-formatted 8 GB USB stick using autorun_AND1E_000.010.170.000.upg and WipeDataTool.upg did not execute, apparently because the set does not reach USB mounting. Suggestions included checking for a motherboard memory/eMMC fault and using the correct upgrade_loader file or placing the firmware in an upgrades directory on USB.
AI summary based on the discussion. May contain errors.
ADVERTISEMENT