• Introducing XDA Computing: Discussion zones for Hardware, Software, and more!    Check it out!
  • Fill out your device list and let everyone know which phones you have!    Edit Your Device Inventory

Flash/update files for TCL ES560/S6500/S5300

Search This thread

HighLow73

Member
Apr 26, 2021
7
4
I have the iffaclon variant of s6500, and currently on build V8-R41KT01-LF1V353. I have forced the TV to run at 1080p instead of 720p with adb command. But there does not seem to be any implementation of Frame Rate matching, meaning the TV always runs at 60fps when using the built in android. Is there any way to fix this or implement the dynamic fps matching feature.

It works fine for HDMI inputs though. My Sky Box triggers 50HZ automatically. Curious to see if anyone have explored on this topic.
 

kuzo

Senior Member
Sep 30, 2008
110
34
Catamarca
I have the iffaclon variant of s6500, and currently on build V8-R41KT01-LF1V353. I have forced the TV to run at 1080p instead of 720p with adb command. But there does not seem to be any implementation of Frame Rate matching, meaning the TV always runs at 60fps when using the built in android. Is there any way to fix this or implement the dynamic fps matching feature.

It works fine for HDMI inputs though. My Sky Box triggers 50HZ automatically. Curious to see if anyone have explored on this topic.
How did you get the tv to work in 1080p with adb? ... any tutorial?
 

HighLow73

Member
Apr 26, 2021
7
4
How did you get the tv to work in 1080p with adb? ... any tutorial?
Connect to abd mode "adb connect IP:5555"
Backup existing config "adb shell dumpsys display > backup.txt"
Change the resolution "adb shell wm size 1920x1080"
Change the screen dpi "adb shell wm density 313" (313 for my 40 inch display, check your display size and change it accordingly)

You do need marshmallow and higher for wm to be available in system i believe. Mine is in Pie.
 
  • Like
Reactions: Keig0

wozzo34516

Member
Nov 6, 2012
19
3
Connect to abd mode "adb connect IP:5555"
Backup existing config "adb shell dumpsys display > backup.txt"
Change the resolution "adb shell wm size 1920x1080"
Change the screen dpi "adb shell wm density 313" (313 for my 40 inch display, check your display size and change it accordingly)

You do need marshmallow and higher for wm to be available in system i believe. Mine is in Pie.
I've got a question. How to connect tv to the adb mode? on tv with app, or with laptop? I've got minimal adb and fastboot, which i used on my phones. Best regards
 

HighLow73

Member
Apr 26, 2021
7
4
I've got a question. How to connect tv to the adb mode? on tv with app, or with laptop? I've got minimal adb and fastboot, which i used on my phones. Best regards
Easiest way it to use wireless adb. Enable it in developer settings in tv. Both laptop and tv should be in same WiFi. You can get the TV's ip address from wifi settings.

Then in your adb in laptop, use adb connect IP:5555

5555 is the port that adb runs on when enabled wirelessly
 
  • Like
Reactions: wozzo34516

Keig0

New member
Apr 21, 2021
2
0
Connect to abd mode "adb connect IP:5555"
Backup existing config "adb shell dumpsys display > backup.txt"
Change the resolution "adb shell wm size 1920x1080"
Change the screen dpi "adb shell wm density 313" (313 for my 40 inch display, check your display size and change it accordingly)

You do need marshmallow and higher for wm to be available in system i believe. Mine is in Pie.
After executing these commands successfully the changes are significant in the home screen, however Kodi in the system info still printed out 1280*720p, and I'm not sure that the videos are playing in 1920x1080p now. Why didn't apply to Kodi and other apps?
 

HighLow73

Member
Apr 26, 2021
7
4
After executing these commands successfully the changes are significant in the home screen, however Kodi in the system info still printed out 1280*720p, and I'm not sure that the videos are playing in 1920x1080p now. Why didn't apply to Kodi and other apps?
Yeah Kodi UI is stuck at 720p no idea why. But when you play video, that would be 1080p.
 
  • Like
Reactions: Keig0

Top Liked Posts

  • There are no posts matching your filters.
  • 2
    V8-R41KT01-LF1V367


    build date= Jan 25 2021
    build= 1611534792
    security_patch= 2020-12-01
    gmsversion= Android_9_Pie
    product.build.fingerprint= TCL/UnionTV/UnionTV:9/PPR2.180905.006.A1/builder.20210125.083312:user/release-keys
    OTA size= 987MB
    bootloader date= Jun 23 2021
    1
    Hola José. Tengo la misma Tv y estoy con la versión 343. Ningún problema hasta ahora. Saludos
    English please....and latest is V360 OTA.
    1
    It has been a while, but I just updated the list.
    TCL released two new rooted images.
    I have pulled mmcblk0boot1 and mmcblk0boot0 but magisk is fiving me an unsupported format?
    Unfortunately, the boot/kernel image is likely to be encrypted. Furthermore, the kernel seems to have been split from the root file system.
    What you may be wanting is to dump the root file system, which likely seems to be the /vendor (mmcblk0p11) partition.
  • 8
    This is a list of update packages and installation images for TCL ES560/S6500/S5300, chassis RT41.
    If you're unsure whether your TCL TV is chassis RT41 or not, you may check it in Settings > About > Contact us menu. If your Software version starts with V8-R41KT01-LF1, you may proceed with the installation. IF YOU DO NOT HAVE A RT41 CHASSIS, THE INSTALLATION WILL FAIL.
    There are two kinds of packages for this TV, download mode packages and Android OTA packages. Download mode packages will erase your data, while Android OTA packages will keep your data.

    Android OTA packages:
    Version 190.
    Version 234.
    Version 241.
    Version 272.
    Version 305.
    Version 353.
    Version 360.
    Version 364.
    Version 367.
    After downloading the package, please, do read the manual included (especially if you want to update to Android 9).

    Download mode packages:
    Version 064.
    Version 076.
    Version 080.
    Version 114.
    Version 117.
    Version 133.
    Version 138.
    Version 139.
    Version 144.
    Version 155.
    Version 180.
    Version 216.
    Version 226.
    Version 229.
    Version 234.
    Version 241.
    Version 242.
    Version 243.
    Version 245.
    Version 250. (Downgraded kernel.)
    Version 255.
    Version 257.
    Version 272.
    Version 284.
    Version 292.
    Version 305.
    Version 343.
    Version 364.
    Rooted download mode packages:
    Version 289.
    Version 353.
    Version 361.
    These packages have an Update.img file. Copy the image file to the root of your USB drive, plug the USB drive into the TV, then boot the TV into download mode.

    How do I boot into download mode?
    1) Hold the power button on the remote control until the power off menu is shown.
    2) Select Yes to turn off the TV.
    3) When the power LED turns off, press and hold the TV's power button.
    4) When the power LED begins to blink, release the power button.
    Another way to boot into download mode is to unplug the TV's power cord, then hold the TV's power button while plugging the power cord back. When the power LED begins to blink, release the power button.
    The TV should boot into download mode and begin the installation process. DO NOT POWER OFF THE TV DURING THE INSTALLATION PROCESS!
    3
    Were you able to do it? I have a rca that is the same too. Tell me about your experience, please, thank you!

    I tried both the OTA and the full firmware install and both installed without a single issue, even the TV started with the "Hitachi" logo and everything so it went just like an official update, the latest firmware (v255) that some user posted here didn't gave me any issues at all, I could even say that it runs better than the original, and they improved some image settings related options, so go for it, if the chasis model number match shouldn't be a problem then, the system checks anyway if the firmware it's valid for installation.
    2
    V8-R41KT01-LF1V367


    build date= Jan 25 2021
    build= 1611534792
    security_patch= 2020-12-01
    gmsversion= Android_9_Pie
    product.build.fingerprint= TCL/UnionTV/UnionTV:9/PPR2.180905.006.A1/builder.20210125.083312:user/release-keys
    OTA size= 987MB
    bootloader date= Jun 23 2021
    2
    Hi I have a Hitachi that is virtually exactly the TCL 6500, it's the same device only with the "Hitachi" brand on it, even the cablebox remote control had to be pair with TCL code number and the software version of mine starts correctly with V8-R41KT01-LF1, should I try to update with these packages? Those this updates arrive at least later or the TV will update only to android 9 via manual update?
    Go for it son

    Enviado desde mi ONEPLUS A6003 mediante Tapatalk

    ---------- Post added at 11:01 AM ---------- Previous post was at 10:58 AM ----------

    Does it worth to update to V255 (im on 241... pretty stable) ? any caveat or something that brokes?
    Thanks for your comments.
    I'm on 255 , everything works fine except for that creepy app named com.tcl.tvweishi (Tv protection).. it crashes when opening file manager or other options in it .

    Enviado desde mi ONEPLUS A6003 mediante Tapatalk
    2
    i have a TCL 40ES560, does chromecast built-in works with tv in standby for any of you? It never worked for me, tried every firmware, I have the option for network standby, fast turn on, everything seems set up as it should, but as soon as I turn the tv to standby it is no longer usable to cast to.. I have another Android TV from sony in my living room and it never had this problem