Develop Bugs

(?) Joying/Pumpkin 5.1.1 Android Headunit Netflix Problem

I am trying to find a good head unit for my Scion TC 05, and an android tablet/headunit is perfect for its radio hatch.
I have recently purchased several android head units. The first being a Pyle 480x800 DVD + android headunit, model PLDNAND692. It ran 4.4.4 KitKat, but the screen resolution was too low, dpi made interface look terrible, and DVD drive was not needed. Netflix played fine though. It runs a RK3066, yet a quad core configuration.
I returned the Pyle due to the old software, low res screen, and overall buggyness with DVD drive.
Recently purchased both a Pumpkin and a Joying Headunit from amazon, and both have no problems with Hulu, Youtube, and other streaming video services, but when trying to view Netflix on either, I am met with a Error code 0013. I have tried all possible fixes, including clearing data, uninstall/reinstall, installing an older build, and a factory reset. Please help.

1) go to system->apps
2) force stop
3) clear data and clear cache
4) uninstall
5) reinstall

nixfu said:
1) go to system->apps
2) force stop
3) clear data and clear cache
4) uninstall
5) reinstall
Click to expand...
Click to collapse
Already did that.
Did it again for good measure, same result
Sent from my SM-G935T using Tapatalk

Emailed with joying, and they confirmed that Netflix has a problem with mtcd units with lollipop. I just bought the kit kat version of the radio instead. Much smoother UX, and doesn't have the memory leak problem lollipop is known for. Lollipop looks better, granted, but their kit Kat models are more fleshed out. And way easier to root.
Sent from my SM-G935T using Tapatalk

thachosenone said:
Emailed with joying, and they confirmed that Netflix has a problem with mtcd units with lollipop. I just bought the kit kat version of the radio instead. Much smoother UX, and doesn't have the memory leak problem lollipop is known for. Lollipop looks better, granted, but their kit Kat models are more fleshed out. And way easier to root.
Click to expand...
Click to collapse
I just bought lollipop version, can you root and downgrade to KK?

[email protected] said:
I just bought lollipop version, can you root and downgrade to KK?
Click to expand...
Click to collapse
Don't even need to root. Just flash a compatible 4.4. ROM.
I also have a Lollipop unit (KLD6 2.97, RK3188, 1024*600) downgraded to 4.4 and couldn't be happier.

m00n61 said:
Don't even need to root. Just flash a compatible 4.4. ROM.
I also have a Lollipop unit (KLD6 2.97, RK3188, 1024*600) downgraded to 4.4 and couldn't be happier.
Click to expand...
Click to collapse
Did you get firmware from Joying website?

[email protected] said:
Did you get firmware from Joying website?
Click to expand...
Click to collapse
No, I am using Booroondook's 4.4. ROM - get it from HERE
Installation procedure HERE
I like Booroondook's ROM because it's very close to stock.
If you fancy flashy graphics, get Malaysk's ROM from this thread
Both are rooted, have FUSE, Xposed framework and allow for lots of customizations.

m00n61 said:
No, I am using Booroondook's 4.4. ROM - get it from HERE
Installation procedure HERE
I like Booroondook's ROM because it's very close to stock.
If you fancy flashy graphics, get Malaysk's ROM from this thread
Both are rooted, have FUSE, Xposed framework and allow for lots of customizations.
Click to expand...
Click to collapse
Thanks a lot! Any reason why carjoying say dont update 5.1.1 units with Malaysk rom from XDA? Anyway I guess it doesn't matter if I am downgrading.

[email protected] said:
Thanks a lot! Any reason why carjoying say dont update 5.1.1 units with Malaysk rom from XDA? Anyway I guess it doesn't matter if I am downgrading.
Click to expand...
Click to collapse
Make sure you have a MTCB or MTCC unit.
Joying also produces MTCD units and those are not compatible. Actually they say: If you have Malaysk don't try to upgrade to 5.1 using our ROM image, that is for MTCD units and will not work on yours.
If you do have a MTCD unit check the dedicated section.

m00n61 said:
Make sure you have a MTCB or MTCC unit.
Joying also produces MTCD units and those are not compatible. Actually they say: If you have Malaysk don't try to upgrade to 5.1 using our ROM image, that is for MTCD units and will not work on yours.
If you do have a MTCD unit check the dedicated section.
Click to expand...
Click to collapse
Mine is MTCD

[email protected] said:
Mine is MTCD
Click to expand...
Click to collapse
You can still try @Malaysk MTCD ROM:
http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309

m00n61 said:
You can still try @Malaysk MTCD ROM:
http://forum.xda-developers.com/and...lopment/rom-malaysk-roms-mtcd-device-t3385309
Click to expand...
Click to collapse
Thanks, looks like I'll be busy over the weekend then!

So instead of following advise I decided to attempt to root my device with the thinking that I may be able to take a nandroid backup before tinkering with custom firmware. Anyway I followed another thread directions for rooting my particular device using the *#... code through settings factory reset and then kingroot, SuperSU etc etc.
IT WORKED!
I then for no reason opened the kingroot app again and it started its process again by me possibly clicking something and the device rebooted and got stuck on Joying screen bootloop, I couldn't even get back into recovery...for some time.
I know this is way off topic as this is more related to root than this threads topic but there seems to be limited threads on these devices and I thought by chance someone might be able to help.
I have been able to boot to recovery several times and factory reset, install stock firmware, update firmware etc but all seem to install then get stuck on lollipop screen.
Please see attached photo, this is where I'm at.
I'm sure, given that I can boot to recovery I should be able to fix this issue eventually with the right firmware files but I am more curious about the file structures when you download a firmware package.
Some downloads just have .img file and some have two files dupdate.img and dmcu.img.
Can someone explain what these files are and why some downloads only have dupdate.img.
Also if someone has a solution for my issue or a link to another thread that could help please let me know or I guess I'll keep flashing firmware packages until something happens.
Happy new year!
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my A0001 using XDA-Developers mobile app

I was able to fix my HU with Malaysk method after I had rooted the device and rendered it officially bricked!
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
Here is a link to my post in another thread.
http://forum.xda-developers.com/showthread.php?p=70353375
Sent from my A0001 using XDA-Developers mobile app

MTCD_KD factory firmware

Here you will find latest firmware for MTCD_KD units.
Inside each rar file you'll find 3 files (dmcu.img, dupdate.img and info_MTCD_KD_Vx.xx_x.txt)
Please contact me for all the firmwares (newer or older) there's not in the list (Let's build a good bulk download area). I will upload and update ASAP the post with the firmware. Be sure you have both .img files and a plain text file (txt) with all the "Version info" screenshot like the ones below.
MCU version:
MTCD_KD_V1.82_1
Aug 26 2016 09:28:58
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #92
Tue Aug 23 20:06:29 CST 2016
Build number:
rk3188-userdebug 25082016.09:47:50
Download (mega) 363.0 MB
MCU version:
MTCD_KD_V1.95b_1
Nov 2 2016 20:26:29
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #237
Wed Nov 2 16:18:31 CST 2016
Build number:
rk3188-userdebug 02112016.19:56:40
Download (mega) 378.2 MB (Thanks to pb40!)
MCU version:
MTCD_KD_V2.06_1
Dec 20 2016 18:37:12
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #39
Fri Dec 2 15:38:02 CST 2016
Build number:
rk3188-userdebug 19122016.20:49:30
Download (mega) 396.7 MB (Thanks to cupi1234!)
MCU version:
MTCD_KD_V2.06_2
Dec 20 2016 18:37:12
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #39
Fri Dec 2 15:38:02 CST 2016
Build number:
rk3188-userdebug 19122016.20:49:30
Download (mega) 396.7 MB (Thanks to pb40!)
MCU version:
MTCD_KD_V2.16_2
Feb 10 2017 14:28:05
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #80
Wed Jan 11 19:06:42 CST 2017
Build number:
rk3188-userdebug 09022017.00:46:00
Download (mega) 428.3 MB (Thanks to RazGame!)
MCU version:
MTCD_KD_V2.40_1
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Mar 16 2017 13:58:09
Android version:
5.1.1
Kernel version:
3.0.101+
[email protected] #207
Fri Apr 7 12:19:26 CST 2017
Build number:
rk3188-userdebug 14042017.02:02:55
Download (mega) 429.9 MB (Thanks to RazGame (mcu V2.40_1) and Kalti94 (Android 14.04.2017)!)

I changed MCU using 1.82_2 version but It is a KGL MCU version; are you sure it is correct file?

Same! It's wrong:
I'll try to search the correct one!
Notice me if you have the correct one

me too
It is a KGL 1.6v MCU version

Yap, I've bricked my unit due to the wrong MCU file, even if I thought it was for KD. I downloaded it from above link. Be sure what you post and be extra sure what you will flash on your unit. It is better to get MCU file directly from supplier.

Hello,
a new firmware for KD version 1.95 :https:...//1fichier.com/?u8w51aayog
and dmcu :https:...//1fichier.com/?9ml29nbddd

Any changelog?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

On my car, a Peugeot 308 no modification for the moment since the V 1.82 but the apk parameter car works better with the canbus.

pb40 said:
Hello,
a new firmware for KD version 1.95 :https:...//1fichier.com/?u8w51aayog
and dmcu :https:...//1fichier.com/?9ml29nbddd
Click to expand...
Click to collapse
What about AF? In my HU, when I make a long trip, I lose broadcast, it seems like RDS (or AF) doesn't work properly
pb40 said:
On my car, a Peugeot 308 no modification for the moment since the V 1.82 but the apk parameter car works better with the canbus.
Click to expand...
Click to collapse
What do you mean with "the apk parameter car works better with the canbus"
Which parameters?
Thanks
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Looking forward to hearing how this is working. My KD unit is stable using @da_anton slimmed down ROM, so I am going to let you guys test this first. Please post if there are any changes that are noticible.
Since the Joying MCU file was working on the KD units, I wonder if the opposite is true.
Patton

The apk allows an access to the screen of the car on the canbus number 50.( for PSA 308) and I have no more an unexpected reboot on the long trip.

Which apk?
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

In the tray where you see all apps you have one preinstalled all named "control settings" the one with orange icon.
Inside the app you have a page named "control settings" again . In control settings you have soft keys that emulate input from the original RD4 or other stock radio installed by Peugeot. It allows you to access the menus on the EMF screen of the car (see picture attached)
Before that option was made available in the late September update you had no way to access these Peugeot settings. The only way to do something as simple as set EMF date and time was to attach back the original car radio set.
All of this may also apply to any car manufacturer/model where the original radio set have specific keys for accessing settings other than radio related ones.

In my KD HU I have installed JY MCU 1.90 and now installed KD 1.95b (the new one): I hope to improve AF function with this update

Just installed and everything works ok.
Tomorrow i'll test to see if i notice any improvements. Please post if you see anything new.
Main post updated with the .rar file (mega server)

colostro said:
In my KD HU I have installed JY MCU 1.90 and now installed KD 1.95b (the new one): I hope to improve AF function with this update
Click to expand...
Click to collapse
I'll try to install this firmware and will report. So far couldn't find AF working in any way. Radio is just lost and have to search for it again. I'm with Malaysk Octobre firmware, so do you guys think that installing this one can brick the device? I've read somewhere that reverting back to original FW from Malaysk one can brick the device (think on Joying site)... Although mine is not a JY, let's just hope it won't.
So far I've several issues regarding my Peugeot 308 MTCD-KD HU. Here's a brief list of them:
1) on a long trip (longer than 2 hours), the display goes blank and nothing helps to bring the UI back. Steering wheel buttons work, turning volume up or down shows the gauge on the display, but that's all and none of the UI parts are visible. The one and only solution is restarting the HU.
2) the USB devices (both 3G modem and a USB flash) get unmounted at random times. Frustrating when you're listening music from flash drive. SD card never got unmounted tho, so a 16GB full of music seems to be half a solution. I lose the 3G modem tho and it's always at random time, but it always unmounts. Tried to remove the modem and use the USB flash drive only to clear any doubts, but still the flash drive unmounts
3) Sometimes when I press the home button, launcher crashes...
4) (last but not least) sometimes GPS locks in seconds after I run my car and sometimes it takes more than 10-15 mins, sometimes it never locks. It sees many satellites, GPS antenna is on the dash, just behind the windshield, no problem with signal strength. GPS monitors prove the signal strength is high. I've read about Lollipop problems with GPS, so I wonder is it a possible reason and is there a fix, or even is there an Android 4.4 for my unit. If so - I'll gladly flash it.
Sometimes (rarely tho) the HU becomes very laggy, for example when I try to increase volume from steering wheel, it reacts after several seconds

The roms serve for all vehicles or each vehicle it's own rom?
Enviado desde mi SM-N910F mediante Tapatalk

Hello. I've also got KD 1.95b. Is it possible to make root and install Xposed? I want to install MTC-Service app.

karolp1993 said:
Hello. I've also got KD 1.95b. Is it possible to make root and install Xposed? I want to install MTC-Service app.
Click to expand...
Click to collapse
Yes, you can install Xposed.
When I can write a guide, I'll post the tutorial.
Stay tuned
Inviato dal mio Redmi Note 3 utilizzando Tapatalk

Inter981 please
They are suitable for all vehicles or you have to change something. I am waiting to receive from the supplier the rom mtcd_mx 1.97a_1 Nov 16.2016 is a Renault megane 3
Enviado desde mi SM-N910F mediante Tapatalk
---------- Post added at 08:52 AM ---------- Previous post was at 08:51 AM ----------
Enviado desde mi SM-N910F mediante Tapatalk
---------- Post added at 08:53 AM ---------- Previous post was at 08:52 AM ----------
Enviado desde mi SM-N910F mediante Tapatalk

Shield TV 2015 (full) OTA 5.02 zip file (NON-PRO) uploaded on MEGA

Shield TV 2015 (NON-PRO) Nougat update version 5.02 is live.
OTA is downloaded to the usual folder: /data/data/com.nvidia.ota/app_download
Filename: PUBLIC02360be7475c0283d8953276654991ff.zip
size: 1.03 GB (1,115,129,317 bytes)
https://mega.nz/#!1VoVSbrR!s4XbFCGF6QSilIL6TBHg-DBU1ogMgOwXVofELfLxBro

I wonder if we can expect this One to land on Launch Day? Which would/should be on 20170130.

@sammarbella
I think you have posted a wrong zip, first the size is not 1.03 gb and secondly it looks like is v5.0 instead 5.0.2

Thanks! Can anyone please post the flash instruction for this update?

xanthrax said:
@sammarbella
I think you have posted a wrong zip, first the size is not 1.03 gb and secondly it looks like is v5.0 instead 5.0.2
Click to expand...
Click to collapse
Nothing wrong was posted.
It's the 5.02 (full) OTA zip file for Shield TV 2015 16 gb version, the posted size is once downloaded.
Copied from my Shield TV 2015 yesterday after it was downloaded by the OS software update service.
There is no such "5.0" for Shield TV 2015 16 gb version, the first one is this one: 5.02.

Ok, I'll check again later today, I've flashed it and I have checked the version and it was 5.0... maybe I didn't see properly
Sent from my Darkside of Oneplus 3T

xanthrax said:
Ok, I'll check again later today, I've flashed it and I have checked the version and it was 5.0... maybe I didn't see properly
Click to expand...
Click to collapse
...Or maybe Nvidia devs and Nvidia reps are not in sync in relation to OS upgrades nomenclatures.
https://forums.geforce.com/default/...grade-5-0-2-feedback-thread-for-shield-2015-/

sammarbella said:
...Or maybe Nvidia devs and Nvidia reps are not in sync in relation to OS upgrades nomenclatures.
https://forums.geforce.com/default/...grade-5-0-2-feedback-thread-for-shield-2015-/
Click to expand...
Click to collapse
Would you mind to check your update version shown on your device? This is mine after flashing your zip, do to root and maybe other twrp reasons I couldn't update it ota
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Sent from my Darkside of Oneplus 3T

xanthrax said:
Would you mind to check your update version shown on your device? This is mine after flashing your zip, do to root and maybe other twrp reasons I couldn't update it ota
Click to expand...
Click to collapse
Who said that i already upgraded to Nougat?
I uploaded to MEGA the OTA file i got yesterday in my Shield TV 2015 16 GB but i didn't upgraded yet.
I'm not in a hurry to upgrade until i'm completely sure that i can update the old TWRP i have right now with the new hacked one and flash OTA and flash supersu from it without problems.
As i posted in my previous post a Nvidia rep made a sticky post announcing on Nvidia Geforce forums that the Shield TV 2015 (FINALLY) got the Nougat upgrade and labelled it 5.02 OTA upgrade and that upgrade is the one i posted.
This 5.02 OTA upgrade is pressumed to have the same fixes already added to 5.01 and 5.02 OTA fixes released for Shield TV 2017 version and therefore the proper number should be 5.02 and not 5.00 even on Shield TV 2015 16 GB.
If some Nvidia dev forgot to name the 2015 OTA properly as 5.02 (or 5.0.2) i can't help...
Hopefully for the Shield TV 2015 owners the Shield TV 2017 owners were the betatesters (5.00 and 5.01) and early adopters can skip 2 OTA versions bugs and get directly the 5.02 OTA version.

Great, many thanks!
I converted the contents to system.img and vendor.img.
This is in build.prop:
ro.build.display.id=NRD90M.1915764_835.9903
ro.build.version.incremental=1915764_835.9903
ro.build.version.sdk=24
ro.build.version.release=7.0
ro.build.date=Sun Jan 22 04:42:16 PST 2017
ro.build.version.ota=5.0(24.28.401.110)
Click to expand...
Click to collapse
So it is android 7.

I woke up this afternoon and i see this nice advice when i tried to watch some TV:
I checked then the downloaded OTA zip file and it's exactly the same name and size that i already uploaded to MEGA:
1,115,129,317 bytes
It's funny different file managers report the exact same size in bytes: 1,115,129,317 bytes but one (X-plore) say it's 1.04 GB and the other (Directory Opus) 1.03 GB:

Nvidia loves you apparently ...hmmm ... grab it and put it up in the cloud lol

xanthrax said:
Nvidia loves you apparently ...hmmm ... grab it and put it up in the cloud lol
Click to expand...
Click to collapse
LOL
I don't care if the installer says "5.0.2" and the about say "5.0" after install for my Shield TV 2015 IF we are getting the 5.01 and 5.02 bugfixes already added to Shield TV 2017 third Nougat OS version.

true ... actually the update is running fine so far , no problems founded , cheers pal !

Does anyone know if it's possible to flash this via Fastboot? I tried to downgrade a 2015 Shield TV from 5.0 to 3.3 to get DRM working again for the HDHomeRun Green app, and it won't boot now. I can get to the Fastboot menu but that's it. Of course Nvidia hasn't posted the 5.0 image for the 2015 Shield yet so I'm kind of stuck right now.

Is the 2017 firmware the same firmware that is used on the 2015 model?
My 2015 model is prompting me to update to firmware 5.02. Although mine is rooted so I don't think I can just let it update. Maybe I will just download the one from the original post. I don't see the 5.02 version available to download from their website.

scope666 said:
Does anyone know if it's possible to flash this via Fastboot? I tried to downgrade a 2015 Shield TV from 5.0 to 3.3 to get DRM working again for the HDHomeRun Green app, and it won't boot now. I can get to the Fastboot menu but that's it. Of course Nvidia hasn't posted the 5.0 image for the 2015 Shield yet so I'm kind of stuck right now.
Click to expand...
Click to collapse
You don't need the 5.0.(2) OS image if you want to downgrade to 3.3, simply flash the available 3.3.0 OS image.
Maybe you'll need the stock recovery flashed before but it's also available:
https://developer.nvidia.com/gameworksdownload

TC93 said:
Is the 2017 firmware the same firmware that is used on the 2015 model?
My 2015 model is prompting me to update to firmware 5.02. Although mine is rooted so I don't think I can just let it update. Maybe I will just download the one from the original post. I don't see the 5.02 version available to download from their website.
Click to expand...
Click to collapse
This is the OTA 5.02 for Shield TV 2015 16 GB, Nvidia will post it on his website in a week (more or less) as Nvidia rep said me in the official thread:
ManuelGuzman said:
sammarbella said:
Any ETA for Shield TV 2015 5.0.2 image upload on https://developer.nvidia.com/gameworksdownload ?
Click to expand...
Click to collapse
Usually it is about a week after a software OTA update has been released.
Click to expand...
Click to collapse
https://forums.geforce.com/default/...thread-for-shield-2015-/post/5068094/#5068094
This is NOT the same firmware as 2017.
Don't try to flash this OTA file on a 2017 model it'll brick it.

sammarbella said:
You don't need the 5.0.(2) OS image if you want to downgrade to 3.3, simply flash the available 3.3.0 OS image.
Maybe you'll need the stock recovery flashed before but it's also available:
https://developer.nvidia.com/gameworksdownload
Click to expand...
Click to collapse
It won't boot after flashing the full 3.3 image set ... that's why I wanted to try 5.0 .... perhaps something changed going from "M" to "N" ... and its preventing the downgrade. See others with the issue here:
https://forums.geforce.com/default/...attempt-to-downgrade-firmware-to-3-3-failed-/

scope666 said:
It won't boot after flashing the full 3.3 image set ... that's why I wanted to try 5.0 .... perhaps something changed going from "M" to "N" ... and its preventing the downgrade
Click to expand...
Click to collapse
If you want to flash the 5.02 image you have it in the first post of this thread.

Dasaita - Latest MCU and Updates for Rockchip CPU platform Stereos

Warm Notice：
If your system is working well, please do not upgrade it !!!
Because the upgrade is risky, it might lead to CRASH, BLACK SCREEN, OR SYSTEM ERROR;
Unless there is a major bug in the car system, it unable to be used normally.
At this time, you can choose to upgrade the system to solve it.
contact your dealer to make sure you are choosing the right firmware and right update steps
MTCH
3.80 : https://www.dropbox.com/s/4kl7j2gsgdjt527/MTCH_HA_V3.80.rar?dl=0
MTCE MCU
3.78：https://www.dropbox.com/s/3hd3ci3rp07ddnt/dmcu.img?dl=0
Android 11 Update
MAX11 Version：Make Sure your unit is PX6 Andorid 11
HA3_rk3399_11.0_ota(20220601)
HA3_rk3399_11.0_20200601_ota.rar
Shared with Dropbox
www.dropbox.com
Vivid 11 Version Make Sure your unit is PX6 Andorid 11
telenav_vivid_rk3399_11.0_ota(20220518)
telenav_vivid_rk3399_11.0_ota(20220518).zip
Shared with Dropbox
www.dropbox.com
HCT Firmware PX6 Android 11 Make Sure your unit is PX6 Andorid 11
HCT8_rk3399_11.0_ota2820220412
HCT8_rk3399_11.0_ota(20220412)升级包.zip
Shared with Dropbox
www.dropbox.com
Android 10 Update
MAX10 Version：Make Sure your unit is PX6 Andorid 10
HA3_rk3399_10.0_ota(20220521)
ha3_rk3399_10.0_ota(20220521+bt_mcu).zip
Shared with Dropbox
www.dropbox.com
Vivid 10 Version: Make Sure your unit is PX6 Andorid 10
telenav_vivid_rk3399_10.0_ota(20220518)
telenav_vivid_rk3399_10.0_ota(20220518).zip
Shared with Dropbox
www.dropbox.com
Scout 10 Version : Make Sure your unit is PX6 Andorid 10
telenav_scout_rk3399_10.0_20220527
telenav_scout_rk3399_10.0_ota(20220527).zip
Shared with Dropbox
www.dropbox.com

hotaudio said:
hi guys
I will share the latest link with MCU and updates here
V2.40 https://drive.google.com/open?id=0B_wOizoYdqYQcUpEVDc0ZHVDaG8
does anyone have online drive recommend ? my google drive is full
the android 6.0 update is more than 1 GB :angel:
Click to expand...
Click to collapse
Perhaps a second Google account to host just the updates?
Thanks for the updated MCU - will be applying to this unit:
http://www.ebay.com/itm/Android-6-0...ash=item3adbb3b7b6:g:QI8AAOSwTuJYt3cd&vxp=mtr
Do these MCU updates have a change log of some sort?

I have downloaded and instead the latest MCU and full firmware. It still goes to sleep instead of turning off, draining the car's battery. ?

93starletgt said:
I have downloaded and instead the latest MCU and full firmware. It still goes to sleep instead of turning off, draining the car's battery. ?
Click to expand...
Click to collapse
what unit you have

hotaudio said:
what unit you have
Click to expand...
Click to collapse
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html

Can i use it for Erisin ES6405v?
MTCD_KGL_V2.11_1
Px5 Soc
For Volkswagen

93starletgt said:
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html
Click to expand...
Click to collapse
this unit universal do not eat the consume the car battery . just be sure you ACC cable not connect to B+

93starletgt said:
The same one you're adverstising:
https://www.aliexpress.com/item/Das...h-2-DIN-Universal-Car-NO-DVD/32789102885.html
Click to expand...
Click to collapse
this unit universal do not eat the consume the car battery . just be sure you ACC cable not connect to B+

Ati_gangster said:
Can i use it for Erisin ES6405v?
MTCD_KGL_V2.11_1
Px5 Soc
For Volkswagen
Click to expand...
Click to collapse
I did not try , but I do not recommend to use on other brand

PX5_6.0 UPDATE (20170304) sendspace
link dont work, can you check it?

@hotaudio Android O starts support aptX codec and another codecs. May you add something for better BT sound quality ?
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}

I am really confused as to which file I put on the SD card to update the MCU. Can someone please point me in the right direction. Super NoOb here.
Is the first file the MCU update and the second file the android update?

@hotaudio Can you update your bluetooth phone app to include a mute button? It is relatively useless for me without this feature (need to be on mute over long meeting calls with a kid in the car)
or otherwise provide information on how to replace this app with another phone app?

dfarmer0033 said:
I am really confused as to which file I put on the SD card to update the MCU. Can someone please point me in the right direction. Super NoOb here.
Is the first file the MCU update and the second file the android update?
Click to expand...
Click to collapse
the mcu update is just a few Kilobytes while the ROM (firmware) update is above 700MB
the mcu update file shall be named as dmcu.img (if you received a Zip file with both ROM & MCU, decompress it to get both)
put it on SDcard as mentioned and go to settings>System information>MCU update

@hotaudio is there a easy way to gain root for your system?

I was able to update. Everything went fine except now when I turn the car on and the HU wakes up it displays "Unfortunately Music has stopped working". Anyone know of a fix. Might try a wipe and install of the update. Any thoughts appreciated.

dfarmer0033 said:
I was able to update. Everything went fine except now when I turn the car on and the HU wakes up it displays "Unfortunately Music has stopped working". Anyone know of a fix. Might try a wipe and install of the update. Any thoughts appreciated.
Click to expand...
Click to collapse
Same issue - 030217 update. When I had originally installed the 030417 update from another PX5 thread here, this issue was not present. I downgraded to the 030217 update to stick with the current Dasaita build.

droc.noles said:
Same issue - 030217 update. When I had originally installed the 030417 update from another PX5 thread here, this issue was not present. I downgraded to the 030217 update to stick with the current Dasaita build.
Click to expand...
Click to collapse
Which version is in the zip file at the top of this thread? That is the one I used.

hotaudio said:
hi guys
PX5_6.0 UPDATE (20170324) https://www.sendspace.com/pro/dl/jpnu9k
Click to expand...
Click to collapse
@hotaudio any chance you could give us a basic change log on these upates? What is new/fixed in 2017/03/24 ? Same goes for MCU updates. Thanks!

aeonfluxcapacitor said:
@hotaudio any chance you could give us a basic change log on these upates? What is new/fixed in 2017/03/24 ? Same goes for MCU updates. Thanks!
Click to expand...
Click to collapse
hi
is the system update , fix the google maps sound bugs

TCL S434 Firmware Question

Hi!
I just purchased a TCL 43S434 and I've been searching through the forums here learning what I can about it.
From what I can find, it sounds like firmware version V440 is the latest firmware I could find on these forums for my particular TV. The part that is confusing me is it would appear that the version I am running now is V122 (Unless I'm not reading this right), not V440. I would have expected these to be sequential, so I'm concerned I'm on a much older firmware. OTA update feature says there are no updates available for me.
{
"lightbox_close": "Close",
"lightbox_next": "Next",
"lightbox_previous": "Previous",
"lightbox_error": "The requested content cannot be loaded. Please try again later.",
"lightbox_start_slideshow": "Start slideshow",
"lightbox_stop_slideshow": "Stop slideshow",
"lightbox_full_screen": "Full screen",
"lightbox_thumbnails": "Thumbnails",
"lightbox_download": "Download",
"lightbox_share": "Share",
"lightbox_zoom": "Zoom",
"lightbox_new_window": "New window",
"lightbox_toggle_sidebar": "Toggle sidebar"
}
Anyone have any information that can share with me to help me understand what I'm working with?
Thanks!

What is release date of firmware ?
Android 9 ?
As per pic....V8-R51MT02-......you can install version with Android 11.

Hi @stasiof, thank you for the quick response. I was hoping you would find your way to my post as you seemed very knowledgable on the topic when I was doing some searching around.
I've attached (below) another screenshot that should hopefully answer your questions.
Can you tell me a little about what the R51MT02 relates to? Why exactly does that determine I can run Android 11? Where might one find newer firmware with say Android 11 on it? I assume on this forum somewhere.
Thank you for all your help.

Ok, let start with some history....
Previous S434 models (2020 version) has a bit different hardware inside TV.
This is how you found firmware V440.....
V8-R851T02-LF1V440.017008
Anyway ,this you can't flash ,as your is now V8-R51MT02.
I found your version and you can keep as backup....V122:
http://na-update.cedock.com/apps/resource2/V8R51MT02/V8-R51MT02-LF1V122/FOTA-OTA/V8-R51MT02-LF1V122.019313.zip
Other then this I found test version V999 dated Apr 26 2021....1.12GB
http://na-update.cedock.com/apps/resource2/V8R51MT02/V8-R51MT02-LF1V999/FOTA-OTA/V8-R51MT02-LF1V999.019587.zip
About Android 11...
Models 2021 rather then N.America version using same firmware......
V8-R51MT02 with A11.
As your model is without Dolby Vision and some other stuff, not sure how
will run on your model.
More info about this firmwares...
TCL 2021 Android TVs (C05/G05/BeyondTV6/BeyondTV4)
(43/50/55/65/75") P725...LED https://www.tcl.com/eu/en/tvs/p725 (50/55/65/75") C725...QLED https://www.tcl.com/eu/en/tvs/c725 (65/75") X925...MiniLED https://www.tcl.com/au/en/products/x925/75X925.html RT51M Platform (Realtek RTD2851M)...
forum.xda-developers.com
If I found other firmware, I will post here....in future.

Thanks so much for providing this extra information!
I have read through that thread you linked about the newer firmware. And I have one follow up question. After going through the thread, it appears that the latest firmware for R51MT02 is V256 (link to your post in that thread https://forum.xda-developers.com/t/...c05-beyondtv6-beyondtv4.4255729/post-85161485)
In that post you mentioned that V256 has a build date of June 05th. and that appears to be the latest R51MT02 firmware (V8-R51MT02-LF1V256). Is there a particular reason I would want to run that V999 (build date April 26th) version you referenced instead of this V256?
Also, as a side note. It's interesting that the V256 security patch is 2020-12-05 when the security patch in my V122 is 2021-1-05. Just a curiosity.
Thanks again!

V999 posted above is Android 9 (still) test version deducated for N.America models.
V256 is Android 11 global version, bigger in zip file (200MB more) ,for wider range of TCL models with RT51M chassis (as your).
Security patch date is not so important.
If not happy ,with both, you can always flash your present version V122 back.
Edit:
If everything ok with your firmware , I will leave as it.

Can someone confirm whether IPTV applications (Smart IPTV, Timate etc) works on the V256 firmware?

i have the 43s434 model and it has a black screen the links above dont load to download the firmware the one that did the tv said no update available...is there a link to any firmware that i can use to fix my tv. tcl is putting me through loops and my tv is still under warranty. thanks. also i have the north america 43s434 model. also what is the process after downloading. do i out the downloaded zip and go or extract that zip and put the zip inside on the usb. im at a point where im at a loss of hope other than buying a new one at this point.

rob219 said:
i have the 43s434 model and it has a black screen the links above dont load to download the firmware the one that did the tv said no update available...is there a link to any firmware that i can use to fix my tv. tcl is putting me through loops and my tv is still under warranty. thanks. also i have the north america 43s434 model. also what is the process after downloading. do i out the downloaded zip and go or extract that zip and put the zip inside on the usb. im at a point where im at a loss of hope other than buying a new one at this point.
Click to expand...
Click to collapse
Did you remember firmware installed?
R851T02 or R51MT02 platform ?
Above links not working ,as TCL change server.

im not sure which one it was made in January 2021 i can try both all the ones ive tried so far say no update package found when i use the usb

Solarean said:
Hi!
I just purchased a TCL 43S434 and I've been searching through the forums here learning what I can about it.
From what I can find, it sounds like firmware version V440 is the latest firmware I could find on these forums for my particular TV. The part that is confusing me is it would appear that the version I am running now is V122 (Unless I'm not reading this right), not V440. I would have expected these to be sequential, so I'm concerned I'm on a much older firmware. OTA update feature says there are no updates available for me.
View attachment 5360229
Anyone have any information that can share with me to help me understand what I'm working with?
Thanks!
Click to expand...
Click to collapse
rob219 said:
i have the 43s434 model and it has a black screen the links above dont load to download the firmware the one that did the tv said no update available...is there a link to any firmware that i can use to fix my tv. tcl is putting me through loops and my tv is still under warranty. thanks. also i have the north america 43s434 model. also what is the process after downloading. do i out the downloaded zip and go or extract that zip and put the zip inside on the usb. im at a point where im at a loss of hope other than buying a new one at this point.
Click to expand...
Click to collapse
You guys have any luck?

stasiof said:
Did you remember firmware installed?
R851T02 or R51MT02 platform ?
Above links not working ,as TCL change server.
Click to expand...
Click to collapse
I have Model 55S434
V8-R851T02-LF1V458.018656
What’s the latest firmware I can use?

skunkd said:
I have Model 55S434
V8-R851T02-LF1V458.018656
What’s the latest firmware I can use?
Click to expand...
Click to collapse
You have latest known version ,with platform R851T02, for NA model.

vonDubenshire said:
You guys have any luck?
Click to expand...
Click to collapse
nope couldn't get any firmware to work i got lucky and got a update version of the same tv on warranty

Weird question can you get HDR10+ logo to show on some stuff with this TV? It technically can't according to specs but I can get the logo instead of HDR if it's HDR10+

my new 43s434 is on V8-R851T02-LF1V449.018073 and see here 458 is the newest version but it says mine is up to date when I try network update. any idea if I can do a manual update without messing it up.