Develop Bugs

Help with editing firmware for Tonghai headunit

Hi guys. I have a tonghai headunit that its stuck in boot. Just reboots everytime. This is due to a corrupted logo in the /etc/logo/ folder. The file is Audi.png
This os firmware i can succesfully flash http://www.mediafire.com/?4idf16t2w5uffl4
The problem is that it wont format the logos, so after the flashing, the issue maintains.
I have no hardware buttons. Just the reset the reboots the device or send it to force flash.
Can i somehow connect the unit to PC using a cable like otg?
Can someone with knowledge edit the fw to format the unit?
I have a system dump with the original logo files of that helps.
I dont know what to do.
Thanks

bump

I can't really help but if you want those that can then you'll need to post a lot more info on your unit.
Like what is it's processor, resolution, current rom, mcu version. And it must have worked at some point. So tell then what you did between it working and not working cos that is likely the problem.
Like I said, I can't help even if you post all that but the guys that know will at least have half a clue.
Sent from my SM-G920F using Tapatalk

Hi
did you solve the problem ( i've the same)?

Need Help Modding ROM

Hello,
I am new to modding/creating ROM's but have ok experience with android and linux themselves. I recently bought a Pumpkin android 4.4.4 head unit that has a RK3188-T SOM with 32GB nand and 2GB RAM at 1024x600. I thought it would work with malaysk's rom because it's a RK3188, but it gets stuck in a bootloop with the google stock android boot animation (the silver ANDROID with a shimmer going across). I've been trying to self teach/google how to mod the rom to make it work with my device but haven't been able to yet. I have the update.img's for both malaysk and pumpkin unpacked as well as their recovery and boot img's. I've also been trying to learn what it takes to pre-root the stock rom so I can at least get xposed up and running, but there's not really any good tutorials on that either. If anyone could help me out learning how to pre-root or how to/what to mod to get malaysk's rom working I'd be extremely grateful!!!!
Oh, also, with the unit at the boot animation, is that still the boot.img, or has boot.img passed control off to system.img at that point? Trying to narrow down where the problem is.
Thank you in advanced,
-Kyle

Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development

themissionimpossible said:
Your head unit unfortunately (or fortunately) is not an MTCB model, so Malaysk's MTCB ROM would never work on it.
Therefore the appropriate forum section for your question is this:
Android Head Units
or this other one should your HU's MCU version start with MTCD:
MTCD Discussion, Questions, Development
Click to expand...
Click to collapse
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle

kjcsg said:
That might explain why even once I get the malaysk recovery up and reinstall a second time, the unit seems to boot up, but both the recovery and system are almost comletely off the left side of the screen, only about 10% is visible on the left edge of the screen. I don't even know what the options are in that recovery screen, I know there's 7 options and I've found that option one boots into system, option 3 installs the update.img, option 2 does something but not sure what, and options 4-7 bounce right back to that recovery screen. Sadly, even with adb on by default I can't get this thing to connect to my pc. So, since those roms won't work, can you tell me how to pre-root the stock rom please? I've tried all the root apk's I could find, KingRoot would work, but with it I couldn't get SuperSU binaries installed properly so it's not the right kind of root I guess. And I'd love to know how to pre-root a rom anyways! Thx a ton!
-Kyle
Click to expand...
Click to collapse
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon

Goose247 said:
Not sure if it's the same for your unit but with MTCB head units go to settings/factory settings and when asked for the password type *#hct#root#
If you want to turn adb on go back to settings/factory settings and for the password type adbon
Click to expand...
Click to collapse
Unfortunately, my factory settings password entry only allows for numbers. I can't get the on screen kb to come up or the usb kb to type letters in the box.

Update: I got malaysk's rom up and running...However the touch screen is messed up (it receives input about an inch above where I tap). Then when I tried to reinstall the rom from settings with wiping it went back to the display off the left side of the screen. How I did it:
1) Install malaysk's rom from stock recovery (with "Check parameter..., E:Check failed at 0x4, Update Parameter..., Check parameter after update..." the first install part, and "E:1 parse errors" and "handle script error! ignore..." the second part)
2) Boot loop - USB kb hit ALT PRTSCR I until I get the recovery sliver on the left hand side of the screeen
3) This time I tried using the second option instead of third installing the pumpkin stock update.img and it boot looped the pumpkin boot animation
4) Reinstalled malaysk's rom using the pumpkin recovery again
5) Malaysk's rom booted up! Touch screen messed up but it booted up!
Now I'm redoing that and going to try to install the kld mcu.img's to get the touch screen working right along with the buttons and volume knob. Still no usb recognition on my pc tho sadly.

I'm trying to install the mcu img from recovery but even with the rom positioned correctly on screen the recovery is still a sliver on the left of my screen. Can someone tell me the options in recovery so I know what I'm selecting please and thank you.
Sent from my VS990 using XDA-Developers mobile app

Nvm, I found a picture online. Next question, does anyone know how to copy the mcu partition or modify mcu data? The pumpkin mcu is in bin format n the converter I have won't convert it to img because it's too big.
Sent from my VS990 using XDA-Developers mobile app

If you get it to work, please let us know here.

Well, from what I can tell, it won't work because the custom roms have different kernels causing the display to be off the screen, at least for the fused roms. I tried a non fused malaysk rom and it wasn't off the screen, but I couldn't get the mcu to work. To get the mcu to work you could try to copy the stock settings mcu update, I tried but it's over my head once I got it decompiled and tried following the code to see what it actually does when you click mcu update in the pumpkin settings. Because of kernels and reverse engineering the pumpkin mcu update are over my head for my current knowledge and understanding, I'm trying to get a refund for this unit and going to buy a joying unit since joying actively works with us, the modding community, giving us stock firmware and root and kernels and help and thus we get a much better unit and rom in the end! Joying understands the meaning of android and how it's supposed to be open source and collaborative for the community to work together to make the best goodies possible. I mean, for crying out loud, Google has gotten many of their features that they've put into their kk, lp, mm releases from us, from modders creating what they want and tuning android to it's best!!! Pumpkin, and as a related note, Verizon sucks!!! Alright, rant complete, any questions, let me know!
-kjcsg

Malaysk ROM MTCC

Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB

Hi Yabbie
I just recieved one of these at the weekend from Pumpkin, but the lower resolution screen
From the reading i have done I beielve these are MTCB units but have a new MCU , v 2.91, and for some reason they are now being indentified as MTCC - maybe a proper expert in here can clarify that.
I have sucessfully flashed a MTCB Malaysk 5.11 ROM , make sure you get the correct resolution for your screen but these do work. Do NOT try to change the MCU - the version we have appears to be the most recent but again that would need confirming by expert.
I installed into a BMW E92 and its working well, have DAB+ adapter as well ( from Joying , you need to download there .apk to get i working )
Cheers

ferrari312_uk said:
Hi Yabbie
I just recieved one of these at the weekend from Pumpkin, but the lower resolution screen
From the reading i have done I beielve these are MTCB units but have a new MCU , v 2.91, and for some reason they are now being indentified as MTCC - maybe a proper expert in here can clarify that.
I have sucessfully flashed a MTCB Malaysk 5.11 ROM , make sure you get the correct resolution for your screen but these do work. Do NOT try to change the MCU - the version we have appears to be the most recent but again that would need confirming by expert.
I installed into a BMW E92 and its working well, have DAB+ adapter as well ( from Joying , you need to download there .apk to get i working )
Cheers
Click to expand...
Click to collapse
Thanks so much for your reply, have just flashed MTCB Malaysk 5.11 ROM also and all is work as expected very happy

Ive noticed my button LED lights are not working , the screen still dims when i put the car lights on but the LEDs don't light up. Also the option to change the colors in settings is missing, i believe it was called Elements. any ideas?
note: when i enter recovery mode they come on in the menu.
Kind regards Yabbie

YabbieAu said:
Ive noticed my button LED lights are not working , the screen still dims when i put the car lights on but the LEDs don't light up. Also the option to change the colors in settings is missing, i believe it was called Elements. any ideas?
note: when i enter recovery mode they come on in the menu.
Kind regards Yabbie
Click to expand...
Click to collapse
Hi YabbieAu, I just got exactly same firmware version as you. Do you have other issues apart from above one after installing Malaysk ROM MTCB?

paulnorinn said:
Hi YabbieAu, I just got exactly same firmware version as you. Do you have other issues apart from above one after installing Malaysk ROM MTCB?
Click to expand...
Click to collapse
Apart from that I've had no issues with the rom , if i change RGB option to just G in Factory Settings and reboot the head unit the elements option returns under settings. In the elements menu i can get every colour working again expect red/yellow.

YabbieAu said:
Apart from that I've had no issues with the rom , if i change RGB option to just G in Factory Settings and reboot the head unit the elements option returns under settings. In the elements menu i can get every colour working again expect red/yellow.
Click to expand...
Click to collapse
Cool, I think I am going to try it soon.
Meanwhile, did you have a chance to get root working on original firmware? I just try it with Kingroot and did not seem to work...

Hi.
I've just installed the Auto Pumpkin MTCC KLD6 V2.91 into my Mondeo and was looking for ROM/ROOT options when I came across this thread
YabbieAu, Did you stick with the Malaysk ROM? How is it doing now?
The main reason I want to root and use a custom ROM is to get a better DAB+ app (I am trying some out on the stock ROM to see if any work first though) and to re-map some of the hardware buttons. I bought the DAB+ box from Auto Pumpkin and it works well, it's just that nasty GUI I want to change!

Hi guys,
I have just installed Malaysk ROM on my unit, I chose this one -> http://forum.xda-developers.com/and...rom-malaysk-roms-lollipop-5-1-1-mtcb-t3394209
and so far so good! I find boot time is quicker than the factory ROM. Also see a lot of feature that I can play with.

paulnorinn said:
Hi guys,
I have just installed Malaysk ROM on my unit, I chose this one -> http://forum.xda-developers.com/and...rom-malaysk-roms-lollipop-5-1-1-mtcb-t3394209
and so far so good! I find boot time is quicker than the factory ROM. Also see a lot of feature that I can play with.
Click to expand...
Click to collapse
I tried the same ROM for an MTCC device (1024x600) and can also confirm that is running very well

Bluetooth with Android 6.0.1
I have MTCC-KLD6-V2.97. I'm having issues with the bluetooth connecting to a Galaxy phone that has 6.0.1.
When i connect the phone via bluetooth, the bluetooth icon shows at the top of the screen then disappears after 5-10seconds. I can see on the phone that when it connects initialy it connects for Call Audio (HSP) and Media Audio (A2DP). After 5-10 seconds the phone shows that HSP is off leaving A2DP on. The Phone shows its still connected via bluetooth. No calls go through to the head unit.
Has anyone had this working with an Android 6.0.1 Phone? I was thinking maybe I should try Malaysk's ROM however I'm unsure if its an OS,MCU or Hardware issue. Any help or ideas would be appreciated.

I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.

sixstrum said:
I have the exact same issue. I'm also using a Note7 running 6.0.1. I'm running a Malaysk 5.1.1 ROM on my HU and having the same problem you described. Hoping there is a way to make this work in the future.
Click to expand...
Click to collapse
I've been doing a bit of research. While I don't know for sure it looks as if the issue lies with the MCU. I think the Bluetooth drivers are in there. Sadly I'm running the latest version. The supplier is going to talk with the factory who made it but don't like my chances.

moodie007 said:
I've been doing a bit of research. While I don't know for sure it looks as if the issue lies with the MCU. I think the Bluetooth drivers are in there. Sadly I'm running the latest version. The supplier is going to talk with the factory who made it but don't like my chances.
Click to expand...
Click to collapse
Likely shouldn't get our hopes up, but if you hear any good news please let me know!

sixstrum said:
Likely shouldn't get our hopes up, but if you hear any good news please let me know!
Click to expand...
Click to collapse
Here is an interesting update...... Ive just tried an Experia Z3 running Android 6.0.1...... It connected and maintains both Call and Media connections. What does that tell us.......

Sorry I've hijacked this thread. I've setup a new one in relation to my issue. Thanks.
http://forum.xda-developers.com/and...id-6-0-1-phone-bluetooth-issue-t3471331/page1

YabbieAu said:
Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB
Click to expand...
Click to collapse
Sorry for posting on wrong thread. :crying:

E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
I have recently acquired the same unit as YabbieAu.
I've just attempted to install Malaysk ROM however its turned to poo.
After it rebooted it took a long time but eventually loaded... sort of. Loaded as a black screen. Top tool bar but no launcher. Buttons don't work and it reboots after about 30 seconds.
If I boot to recovery I can not recover from SD. I get error messages. E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
Other error message are related. i.e. cant open or mount cache etc due to the fact the /cache symbolic link could not be mounted.
It appears the cache partitions need to be re-created?
Can anyone assist?
YabbieAu said:
Hello everyone, I'm looking at installing Malaysk rom on my Android Car head unit i imported. However i see all this discussion about MTCB/MTCD and nothing about MTCC. which Rom should i use? Will it be compatible? Any help would be greatly appreciated.
Brand
ROCKCHIP rk3188
MCU version
MTCC-KLD6-V2.91
Android version
5.1.1
1024*600
Kernel version
3.0.101+
[email protected] #42
Tue May 17 21:50:34 CST 2016
Build number
rk3188-userdebug 01062016:18:49:08
Model number
S07
CPU
ARM [email protected] (x4)
Memory
1024 MB
Click to expand...
Click to collapse

moodie007 said:
I have recently acquired the same unit as YabbieAu.
I've just attempted to install Malaysk ROM however its turned to poo.
After it rebooted it took a long time but eventually loaded... sort of. Loaded as a black screen. Top tool bar but no launcher. Buttons don't work and it reboots after about 30 seconds.
If I boot to recovery I can not recover from SD. I get error messages. E:Failed to mount /cache /dev/block/rknand_cache (block dev required)
Other error message are related. i.e. cant open or mount cache etc due to the fact the /cache symbolic link could not be mounted.
It appears the cache partitions need to be re-created?
Can anyone assist?
Click to expand...
Click to collapse
All good. I fixed it. Obtained latest image from supplier ver 2.97 Aug 02 2016
Removed unit from car. Connected USB cable to front USB port of head unit and other end to laptop.
Downloaded and installed RockChip Driver assistant v4.4 on laptop.
Downloaded RockChip Factory Tool v1.39 on laptop.
Applied power to yellow wire only (no acc) while holding power button. Once computer saw USB connection let go of power button. Screen remains black on head unit. This is bootloader mode.
Ran Factory Tool and and used the restore option to restore the update.img file provided by the supplier.
Once restore completed powered off and applied power to both yellow and red wires - power and acc.
Let unit complete boot. Took some time to do fresh install of apps etc.
All fixed.

moodie007 said:
All good. I fixed it. Obtained latest image from supplier ver 2.97 Aug 02 2016
Removed unit from car. Connected USB cable to front USB port of head unit and other end to laptop.
Downloaded and installed RockChip Driver assistant v4.4 on laptop.
Downloaded RockChip Factory Tool v1.39 on laptop.
Applied power to yellow wire only (no acc) while holding power button. Once computer saw USB connection let go of power button. Screen remains black on head unit. This is bootloader mode.
Ran Factory Tool and and used the restore option to restore the update.img file provided by the supplier.
Once restore completed powered off and applied power to both yellow and red wires - power and acc.
Let unit complete boot. Took some time to do fresh install of apps etc.
All fixed.
Click to expand...
Click to collapse
Were you able to install Malaysk ROM?

Tcl p66 50" - oreo 8 problem

Hello,
I have a problem after the official update to OREO 8: the instant switching-on of the TV no longer works.
the option is regularly activated in the android menu.
With the previous operating system I never had this problem.
I also reset the TV to factory data with no results.
Can anyone help me?
Many thanks in advance,
Michele

hey,
have the exact same problem over here... tv always boots up completely from scratch

realmastah said:
hey,
have the exact same problem over here... tv always boots up completely from scratch
Click to expand...
Click to collapse
they answered me from TCL ITALIA assistance, telling me that it is a known problem and that it will be solved (we hope) with an update ... update that they don't know when it will be released ...
Today I wrote to TCL EUROPE pointing out that this problem is not acceptable and that they give me solutions.
I will keep you updated on this.

Bafoth said:
Hello,
I have a problem after the official update to OREO 8: the instant switching-on of the TV no longer works.
the option is regularly activated in the android menu.
With the previous operating system I never had this problem.
I also reset the TV to factory data with no results.
Can anyone help me?
Many thanks in advance,
Michele
Click to expand...
Click to collapse
What version is your Oreo?
Try downloading V534.
Go to.
https://support.tclelectronics.com.au/software-updates/
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.

MirrorNeuz said:
What version is your Oreo?
Try downloading V534.
Go to.
(...)
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.
Click to expand...
Click to collapse
Does this firmware update work for European TVs as well? Has anybody tested it?
I have the exact same problem on my TCL 50DP660, bought in Germany.
I don't recommend this TV to anyone because of this particular bug. So annoying. Terrible user experience.

Okay, I tried to install Australian v534 on my TV and it didn't work, failed on validation, probably the signature doesn't match

49 inseries Thomson / TCL Percee TV instant start
I have the exact same issue with a 49 inch 6 series Thomson / TCL Percee TV bought in Spain. I am in contact with the manufactures. So far they have advised me to download and install the latest software version and completely reset the tv. This did nothing and the problem persists so I am awaiting their next response. I will update the thread if I receive a working solution. They also told me that it is not possible to roll back to the previous android version.

Same problem here with an TCL U55X9006 QLED. With the OREO.

Any news..?!

MirrorNeuz said:
What version is your Oreo?
Try downloading V534.
Go to.
https://support.tclelectronics.com.au/software-updates/
It's official TCL Australia Software Download Page.
V534 is stable and has no issue with Instant Power On feature.
Click to expand...
Click to collapse
Webpage does not exist, any idea what's happened to the software downloads?

https://drive.google.com/folderview?id=1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr
Wysłane z mojego TA-1033 przy użyciu Tapatalka

49 inseries Thomson / TCL Percee TV instant start
The link has an error in it. Try replacing the first full stop with @ e.g. [email protected]
This is for Aussie customers though. Someone else on this thread tried it and the download mismatched with their tv. I have not had any success with the latest European version that tcl/Thomson recommended I download and install. I have not heard back from them since. At the moment I cannot pursue as I am in the UK and the tv is in Spain. I intend to chase up again in new year when next over there.

Any news please ?

I fixed mine! Tried a bunch of stuff, almost bricked my TV (seriously) but now Instant Power On is working! I'll explain exactly what worked for me and how to do it:
DO IT AT YOUR OWN RISK, I take no responsibility for any damages:
Download the file Update.pkg from https://drive.google.com/drive/folders/16RcAprPvyJuiXiEpEbIgvGlIW493kKtQ (folder v528)
Add it to the root of USB Pen Drive
Turn off your TV and take the energy cable out
Insert the Pen Drive
Connect the energy cable while pressing and holding the Power button (the TV button, not the remote control)
Keep it pressed until the screen flicks
You will see a Update in Progress screen (a small gray square in the center of the screen), do not turn off your TV until it's finished
Wait for it to restart. In my case after the update it also wiped all data, if yours does not, try doing it manually before testing Instant Power On
Remember to disable auto updates
Notes:
My TV is a TCL 50DP660 (Percee TV)
Before starting the process it was updated to the latest version (v543)
I chose v528 randomly, I have no idea if it only works on this version
I believe the Update.pkg contains the full image, while the zip is meant for OTA upgrades, but I'm not sure
Maybe the fix came from doing a full installation and is not related to specific version. If you're feeling adventurous feel free to try another version, I'm fine
The reason why I almost bricked my TV is because I tried other stuff before doing this.Just for documenting, this is the complete step by step I did (not recommended):
I was trying random stuff to make Instant Power On work, first I enabled developer mode, ticked some options including "Stay Awake", "Show Taps" and "Pointer Location". Of of them caused my TV to restart and enter a bootloop. At this point I was only trying to make my TV work again. I couldn't find a way to factory reset, so I tried installing the .zip update again with no success, tried to install v528 zip with also no success. Then I tried to downgrade it to Android 7 installing the Update.pkg from version v373. At this point not only my TV would boot, it would also present a lot of image issues, flickering and trying to install the v543 zip started to fail in the middle of the process. At this point I was convinced it was bricked and I lost the guarantee. Then I tried to install the Update.pkg from version v528. I had to remove the pen drive right after the installation was finished otherwise it would go on a update loop. I really don't recommend trying any of those things, I only did because I was already in a boot loop and still I think I was quite lucky. I wasn't even expecting Instant Power On to work in the end of the process.
Good luck! Please send a feedback if you try these steps!

Well done Lucasl! Thanks for posting this excellent write up. I shall be giving this method a try in March when I have access to the tv again and will feed back.?

Lucasls, where did you manage to download the various versions from? Do you have a link? In case v528 does not work on my tv.
Thanks

A4Android said:
Lucasls, where did you manage to download the various versions from? Do you have a link? In case v528 does not work on my tv.
Thanks
Click to expand...
Click to collapse
The link I posted you can navigate through folders, but this is the link to root of the repository https://drive.google.com/drive/folders/1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr

Where do you find the upgrade.pgk files? It Is "original" or find on internet?!
I have fear of brick my TV Also... :crying:

franchini.luca said:
Where do you find the upgrade.pgk files? It Is "original" or find on internet?!
I have fear of brick my TV Also... :crying:
Click to expand...
Click to collapse
I found on internet, but I have no reason to believe they are tweaked. In fact I believe they are all signed (has a cryptographic signature that can only be made by the original vendor), because I think to install custom non signed by TCL firmware you first would need to unlock the bootloader. This is my experience with Android phones, I don't expect Android TVs to be any different.
If you Google for this Google Drive folder's link (https://drive.google.com/drive/folders/1vXfF1A3WtxTTU3CDRWraWyA7xd_dTGgr) you'll see it shows in many different forums with many different languages, but I can't know for sure who uploaded it in the first place... See: http://bit.ly/35KpebC
In my case I was desperate because my TV was already bootlooping when I tried to flash this image, so it's of course a harder decision when you have a fully functional TV.

I Ask you this becouse there Is a Little probability that that firmware are not for 55dp660 TV but for a similar model.
So the TV install the upgrade.pkg but TV gira in bootloop... :crying:

[tech support] Pumpkin PX3 MTCE HU, started bootlooping, need help recovering

Hello all,
I've run into an issue with my new head unit. I was just trying it out before installing it, got it powered up from my bench supply to test, and as soon as I installed a couple of apps (Plex and Google Play Music) it started bootlooping on me.
I figured I would go ahead and install a CFW since I do that for all my android devices anyway, but I've gotten myself into a pickle now. I can prompt the unit to attempt a firmware update, but all of the firmware releases I've found are in nupdate.img format, and the recovery is looking for a "kupdate.zip" format. I did try using the SD_Firmware_Tool to build an sdcard for this, but it seems to just be getting ignored.
The current behavior is that I get the "Pumpkin" bootloader logo, then it reboots. It no longer even shows the "android" loading screen as It did before I tried using the SD_Firmware_Tool.
For reference, I was trying to use the Hal9k rom from here
Getting to the onboard update menu works by holding the power button (pushing down the volume wheel) and hitting the reset button. I haven't been able to get it to boot into any other recovery modes yet, but if anyone happens to know of another button combo that should be working, please let me know.
I've put in an email to pumpkin support but I have a feeling they'll take a while to get back to me with the firmware, so hoping someone else might have something I can use in the meantime.

Well apparently I was mistaken about what CPU is under the hood of this thing (was going by a user review on the amazon page where I purchased it.)
According to the recovery it's loading into, this has an RK3368 rather than the RK3188 I expected

Little Update:
I'm trying out this unbrick for the PX5 to see if I can get it to use a more robust recovery. The current one keeps trying to mount a nonexistant drive location to run the kupdate.zip, and most of the pictures I've found of people's recoveries floating around on here have had the option to choose update files from different locations, so I think the recovery on this needs an update.
It's so far booting to a black (backlight on) screen and not progressing, so I hope the firmware update is going in the background and I just need to wait it out. Anyone know how long that firmware update process should take?

well I think my unit may just be new or different somehow, as none of the unbrick metbods seem to be working at the moment.
I've attached some pics of the unit's internals to see if that can help find a solution

How have you ascertained it to be an MTC(D/E) - it isnt

marchnz said:
How have you ascertained it to be an MTC(D/E) - it isnt
Click to expand...
Click to collapse
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?

Pyr0ball said:
I suppose there were some assumptions made based on what's already available on the market.
If it's not an MCT(#) then what is it?
Click to expand...
Click to collapse
An XDA search for [kupdate] yeilds the information.

Made some progress on figuring this module out