(?) Joying/Pumpkin 5.1.1 Android Headunit Netflix Problem - MTCB Android Head Units Q&A

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

Related

Rockchip RK3168 and RK3188 Root Method Working!

Bought a Certified 7" MID-73005 tablet with an RK3168 chip inside.
I could not find a root method... I couldnt even find the right USB drivers.
Found the method for the RK3188, which is the quad core variant of the 3168.
Tried it, and it works perfectly! Rooted baby!
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
Just thought others might like to know, seeing as these chips are still fairly new and not much out on them yet.
resinis said:
Bought a Certified 7" MID-73005 tablet with an RK3168 chip inside.
I could not find a root method... I couldnt even find the right USB drivers.
Found the method for the RK3188, which is the quad core variant of the 3168.
Tried it, and it works perfectly! Rooted baby!
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
Just thought others might like to know, seeing as these chips are still fairly new and not much out on them yet.
Click to expand...
Click to collapse
I know this a bit off topic but, does that have an HDMI out? Currently looking into buying one.
I have the same chip and i rooted it but now i want to install cwm on it how do i do that?
resinis said:
Bought a Certified 7" MID-73005 tablet with an RK3168 chip inside.
I could not find a root method... I couldnt even find the right USB drivers.
Found the method for the RK3188, which is the quad core variant of the 3168.
Tried it, and it works perfectly! Rooted baby!
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
Just thought others might like to know, seeing as these chips are still fairly new and not much out on them yet.
Click to expand...
Click to collapse
THANK YOU THANK YOU THANK YOU!!!!!! Looked high and low for the steps to do this and it worked on my 7 yr old daughters Kocaso M1066 tablet!
Truly a great find!
resinis said:
Bought a Certified 7" MID-73005 tablet with an RK3168 chip inside.
I could not find a root method... I couldnt even find the right USB drivers.
Found the method for the RK3188, which is the quad core variant of the 3168.
Tried it, and it works perfectly! Rooted baby!
http://www.slatedroid.com/topic/88850-rooting-rk3188-tablets/
Just thought others might like to know, seeing as these chips are still fairly new and not much out on them yet.
Click to expand...
Click to collapse
this didn't work for me. no errors while rooting but still m tab isn't rooted. pls help...
axlina said:
this didn't work for me. no errors while rooting but still m tab isn't rooted. pls help...
Click to expand...
Click to collapse
What kind of tablet do you have?
ANDROID...A New Digital Revolution Of Incredible Developers
ianmb said:
What kind of tablet do you have?
ANDROID...A New Digital Revolution Of Incredible Developers
Click to expand...
Click to collapse
this one
http://www.intelkom.hr/opis.php?id=4696
axlina said:
this one
http://www.intelkom.hr/opis.php?id=4696
Click to expand...
Click to collapse
That has the same processor as the tablet I rooted. You use the root program that was linked to in this thread? Did your tablet reboot 3 times?
ANDROID...A New Digital Revolution Of Incredible Developers
ianmb said:
That has the same processor as the tablet I rooted. You use the root program that was linked to in this thread? Did your tablet reboot 3 times?
ANDROID...A New Digital Revolution Of Incredible Developers
Click to expand...
Click to collapse
Yes it did reboot. I don't know if this is important i didn't find this option
{
"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"
}
https://www.dropbox.com/s/pdewri7n5t97704/root2.png
axlina said:
Yes it did reboot. I don't know if this is important i didn't find this option
https://www.dropbox.com/s/pdewri7n5t97704/root2.png
Click to expand...
Click to collapse
What option...? Whatever you posted isn't showing.
ANDROID...A New Digital Revolution Of Incredible Developers
ianmb said:
What option...? Whatever you posted isn't showing.
ANDROID...A New Digital Revolution Of Incredible Developers
Click to expand...
Click to collapse
Don't you see dropbox link with an image?
this is what the pic should show
uid=0(root) gid=0(root)
-----If the ID shows as 0/root than continue, otherwise close and start again...
axlina said:
Don't you see dropbox link with an image?
this is what the pic should show
uid=0(root) gid=0(root)
-----If the ID shows as 0/root than continue, otherwise close and start again...
Click to expand...
Click to collapse
When you ran the root script on your PC did those come up as 0/root? If so you should have pressed the space bar to continue. That would have been the first reboot if I remember correctly. Then it does a second script with same as far as uid=0(root) gid=0(root) then continue by pressing space bar...2nd reboot. Then 3rd script same as above uid...gid, space bar, 3rd reboot...then you should be rooted. Make sure tablet is on and USB debugging is checked before you start and you have the device driver installed.
Basically it is asking you if you see uid=0(root) gid=0(root) after it runs each script. If so continue.
ANDROID...A New Digital Revolution Of Incredible Developers
Which root file did you download? Was it the TPsparky.rar file?
https://www.dropbox.com/s/mhue9su5ir2a21v/TPSarky-Root.rar
Just extract files and run the TPSparky.bat file as Administrator on PC.
This is the one I used and it worked first time!
Cube U9gtV - RK3188 Quad Core
Thanks. It worked perfectly for my Cube.
I only saw "uid=0(root) gid=0(root)" before the last reboot. I almost didn't realize it was there. I believe it was in the line just above the question about it being there. The first 2 reboots just told me wait until the OS loaded then press any key (spacebar) to reboot. After the last reboot, I ran an app Root Checker and it worked. Thanks again.
thanks! working on AWC 3188
works
Just tried this method on the yarvik noble mini tab07-485 and it works thank you very much.
Now I just need a cool rom.
Any ideas let me know.
Thanks.
Have tried this on CHUWI v17HD seems to work , get id 0 etc and superuser is installed however when I use supersu I get the message "The is no SU binary and SuperSU cannot install it - any solutions?
THX!
Works fine with MyAudio7 704T series tablet.
Win7 64bit op system was used.
Many thanks.
Have tried this on CHUWI v17HD seems to work , get id 0 etc and superuser is installed however when I use supersu I get the message "The is no SU binary and SuperSU cannot install it - any solutions?
Click to expand...
Click to collapse
Same by me... have u solved it please?
Gudboj said:
Same by me... have u solved it please?
Click to expand...
Click to collapse
Try updating SU through the Play store. It might work.
ANDROID...A New Digital Revolution Of Incredible Developers
ianmb said:
Try updating SU through the Play store. It might work.
Click to expand...
Click to collapse
Hi, what SU do u mean? SuperSU or what app? Can you post the link to the app, please?

Root: Joying 5.1.1 Unit

I ended spending a fair amount of time chasing down a working root method, in the interest of saving time for anyone else who is looking I wanted to post the steps I took.
1.) Settings > Factory Settings > Enter Password: *#hct#root#
2.) Install Kingo Root: https://root-apk.kingoapp.com/kingoroot-download.htm
3.) Install SuperSU
3.) Install SuperSU Me: https://sites.google.com/site/androidxdacom/file/supersu-me-v6.7.apk?attredirects=0
Device will reboot, you'll want to update the SSU binary, and you'll be good to go.
Thank You for this info, it worked for me :good:
This works on every joying 5.1 unit?
How do you like the Joying brand?
Worked on mine. Thanks man
Sent from my SM-G935T using Tapatalk
---------- Post added at 09:23 PM ---------- Previous post was at 09:20 PM ----------
I have the double din 7 inch in my wrx, finding a proper trim kit that fit around the unit for me was tricky.. as they are a few mm bigger side to side and up an down that standard double dins. But was able to finally find one that was seamless for the wrx. Personally love mine. The pioneers and alpine are getting better but still think my joying is superior.. that's just my opinions.
Sent from my SM-G935T using Tapatalk
Just wanted to confirm for anyone interested that this process is still valid for the latest Joying build (6/12).
http://forum.xda-developers.com/and...tcd-device-t3385309/post67428387#post67428387
what are you doing with root access on the head unit?
bumpaudio said:
what are you doing with root access on the head unit?
Click to expand...
Click to collapse
AD blocking.
Tasker needs root to make some things with hardware.
Отправлено с моего Nexus 6 через Tapatalk
bumpaudio said:
what are you doing with root access on the head unit?
Click to expand...
Click to collapse
Replacing system apps, backups, etc.
w0rdie said:
I ended spending a fair amount of time chasing down a working root method, in the interest of saving time for anyone else who is looking I wanted to post the steps I took.
1.) Settings > Factory Settings > Enter Password: *#hct#root#
2.) Install Kingo Root: https://root-apk.kingoapp.com/kingoroot-download.htm
3.) Install SuperSU
3.) Install SuperSU Me: https://sites.google.com/site/androidxdacom/file/supersu-me-v6.7.apk?attredirects=0
Device will reboot, you'll want to update the SSU binary, and you'll be good to go.
Click to expand...
Click to collapse
I've got an MTCD in the mail and am trying to figure out the best way to take control over it.
That part about "kingo root" is scary as all hell. Who knows what its doing! And despite replacing it later on with "supersu" (which is not much less frightening, since it too is closed source), that is no guarantee that you are removing all remnants of it.
I suggest that this is not a good process to follow.
From what I understand, the recovery on these devices does NOT enforce signed updates. That means that the proper way to install something like this, is to inject it directly into an update. Just skip the exploit step altogether.
/////CANCEL QUESTION: One question I have though; what does the factory settings password actually do?//////
Answer: This turns on root. The silly things comes WITH ROOT ALREADY AVAILABLE!
Its actually better to NOT install any kind of root (kingoroot or supersu), since its already there, just blocked from the android side. This is more secure than leaving the device open to potential exploit, and gives you an avenue to go in and mess with things.
I
I am attempting this method and followed your instructions. I got a message that said adb root and I installed king root and my device rebooted. Super SU says my device is not rooted and Super-Sume gets stuck at "Preparing environment please wait..."
Can I get help?
Anyone know if it is possible to install TWRP? Anyone tried?
Well mine worked fine, then supersu app disappeared and reboot, now I'm stuck with bootloop and can't get into recovery!! Help! RK3188 800*480 MTCD.
Sent from my A0001 using XDA-Developers mobile app
Hi guys, I was able to fix my HU which was completely munted by following this thread.
https://forum.xda-developers.com/an...lopment/rom-malaysk-roms-mtcd-device-t3385309
I used the SD tool to create a boot card, then got the error which is shown in the thread then followed the next page which tells you to use the SD card and a USB thumb drive with the update file on it.
When the error shows up you eject the SD card and the system goes to recovery. Use the install from USB and clear all function and it does its thing.
The joying screen showed up for some time (about 5-10mins) but after booted to system and I'm in business again.
Don't follow my instructions here this is just a brief explanation of what I did, use the link above and try all steps and follow carefully.
Attached photo of the error screen I had in recovery FYI.
Please note this was after I used root method of factory settings code, king root and super su and I did have root access/ the binaries updated etc etc, so don't be scared to try as you can recover your system.
Also the firmware I used was the latest 5.1.1 from Joying website.
My unit is: RK3188 (800*480) MTCD which shipped in December 2016 with android 5.1.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"
}
Sent from my A0001 using XDA-Developers mobile app
[email protected] said:
Anyone know if it is possible to install TWRP? Anyone tried?
Click to expand...
Click to collapse
anyone?
An FYI,
I just got an Eonon GA 2155 w/ Android 5.1.1.
I tried other rooting methods without any success.
I used Kingoroot and it worked great. Compared to my Galaxy phones, a pie of cake.
Thanks to the OP
joying 5.1.1
I don't see a factory settings menu! Did they hide it or are my glasses in need of an upgrade.
rvroamer said:
I don't see a factory settings menu! Did they hide it or are my glasses in need of an upgrade.
Click to expand...
Click to collapse
They moved it to car settings and removed the ability to root through factory settings. (password for factory settings is 3368) there is no * or # button. Can someone please find a work around?!?!
jaaluk said:
They moved it to car settings and removed the ability to root through factory settings. (password for factory settings is 3368) there is no * or # button. Can someone please find a work around?!?!
Click to expand...
Click to collapse
I have one of these units coming, I would like to know as well how to root it since it's apparently disabled.
Anyone ? No more possibilities to root now ?
i tried hooking up an USB keyboard to be able to type in the missing characters, but no success.

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

Help, I screwed up ... PX5

When updating my PX5 from Android 8 to Android 10 of my Mitsubishi Outlander the radio got messed up, the physical buttons stop working, and it gives a version error, where can I get the correct version for this radio? thanks ...
{
"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"
}
Seems like you flashed an MCU as well as the ROM and it was the MCU from a different manufacturer, in order to restore it you need to find out which manufacturer your unit is from. Do you know ?
typos1 said:
Seems like you flashed an MCU as well as the ROM and it was the MCU from a different manufacturer, in order to restore it you need to find out which manufacturer your unit is from. Do you know ?
Click to expand...
Click to collapse
hello, unfortunately I don't know the manufacturer, I bought it on Aliexpress, and now the seller is no longer active, and there is no manufacturer reference on the radio.
Take some pics of the sides, back and underneath if the unit - may be able to identify it. Do you remember what the MCU was before ?
EDIT : Hold on, that wallpaper suggest that it might be a KGL unit - upload those photos to confirm. Flashing a KGL MCU may help, but with no mcu.cfg it may be a struggle to restore everything. Having said that the wallpaper will have just come from the ROM you flashed, so probably best open the unit up and get the manufacturer from the motherboard to be certain.
typos1 said:
Take some pics of the sides, back and underneath if the unit - may be able to identify it. Do you remember what the MCU was before ?
EDIT : Hold on, that wallpaper suggest that it might be a KGL unit - upload those photos to confirm. Flashing a KGL MCU may help, but with no mcu.cfg it may be a struggle to restore everything. Having said that the wallpaper will have just come from the ROM you flashed, so probably best open the unit up and get the manufacturer from the motherboard o be certain.
Click to expand...
Click to collapse
Hello typos1 tomorrow I put the photos of the motherboard, thank you very much for your help....
Ok, no probs
typos1 said:
Ok, no probs
Click to expand...
Click to collapse
hello Typos1, I disassembled the unit and took these pictures, will it help to identify? thanks
Ok, see where is says "XRC" ? That means you have an XRC unit, so flash the latest XRC MCU from the link in my signature and let me know if it sorts it.
typos1 said:
Ok, see where is says "XRC" ? That means you have an XRC unit, so flash the latest XRC MCU from the link in my signature and let me know if it sorts it.
Click to expand...
Click to collapse
Ok Type1, morning I will try, if one day you come to Portugal let me know, I want to buy you beer.
thanks
No probs, there may still be some things for you to do after you have flashed the MCU though, so let me know how you get on.
typos1 said:
No probs, there may still be some things for you to do after you have flashed the MCU though, so let me know how you get on.
Click to expand...
Click to collapse
hello typos1 , so far so good, with your help everything went well, over the weekend I’m going to install the unit in the car to test it, because right now it’s connected to a PC power supply, thanks again...
Cool, so everythings working ? I d install a later XRC MCU if I were you though.
typos1 said:
Cool, so everythings working ? I d install a later XRC MCU if I were you though.
Click to expand...
Click to collapse
hello typos1, I detected a problem, damn it, when I turn the physical sound button to the left, the sound decreases is correct, but when I turn to the right to increase the sound it decreases too, do you know what it could be?
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Yes, it is because you did not go into factory settings and export your MCU settings before you flashed the MCU, you need to do this always, I understand it is because you did not know what you are doing but that is why you have the problem.
Go into factory settings and try and remap the buttons, but I dont think it works on the volume kob, you can also try changing the knob mode in factory settings. If none of this works you need to find someone with another XRC unit and try flashnig their mcu.cfg.
ineedroot69 said:
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Click to expand...
Click to collapse
He did not "modify" it, he flashed a ROM without realising that there was an MCU file with it. As for mods, people have modified these stereos for years - check out all the threads about it - and mnay of these mods are very useful and correct bugs from the factory.
typos1 said:
He did not "modify" it, he flashed a ROM without realising that there was an MCU file with it. As for mods, people have modified these stereos for years - check out all the threads about it - and mnay of these mods are very useful and correct bugs from the factory.
Click to expand...
Click to collapse
yeah im not trying to criticize something im just amaze that people would "flash" not "modify" btw stuff as long as there running android such as car stereo system instead of sticking to stock version
What he flashed was a stock update, so still not a mod.
The factory ROMs are not good, again, for years people on here have modified and improved the facpory ROM, many, including me would never even use the factory ROM at all.
ineedroot69 said:
why do people keep modifying car radio like that's so risky it would be terrible while your driving and radio suddenly start out of nowhere
Click to expand...
Click to collapse
calm, what led me to do the upgrade was the radio brought factory problems, the clock was always incorrect, gps was never in the right place, etc., and the seller never supported me ...
typos1 said:
Yes, it is because you did not go into factory settings and export your MCU settings before you flashed the MCU, you need to do this always, I understand it is because you did not know what you are doing but that is why you have the problem.
Go into factory settings and try and remap the buttons, but I dont think it works on the volume kob, you can also try changing the knob mode in factory settings. If none of this works you need to find someone with another XRC unit and try flashnig their mcu.cfg.
Click to expand...
Click to collapse
Hello typos1, is it possible to downgrade the MCU? there are other versions in this list ...there may be one that can be compatible ?
Yandex
Finds everything
disk.yandex.com

MCU & Android update for dummies (erisin es6963c)

Originally this thread was my stupid questions about how to update android car head unit. As a novice to these things it felt bit complicated but I assure you, it's actually easier than rooting a phone for example. I make simple steps, so people new to this can get the picture and not spam all threads with stupid questions (like we all do lol)
1. Update MCU
First things first, you need to update your head units MCU to most recent version. MCU stands for MicroControllerUnit, and you need to be specific and use ONLY right file for your head unit! (For example my unit is shown in picture, it's MTCD/E machine, it got PX5 coreboard and it's made by Leica semiconductor & electronics company, which is abbreviated as LM; So in this context I would download for example MTCE_LM_v3.67 file.
After downloading, unzip, put dmcu.img to root folder of the usb stick or sd card, stick it on and go to head units Settings > System > Update MCU.
It's really important that you use ONLY right file for your head unit!!!
Here you can find list of MCU files:
XDA - Comprehensive list of MCUs for MTCD/E head units
Yandex - Comprehensive list of MCUs for MTCD/E head units
2. Install new Android version
Newer android version can be referred as ROM or FirmWare (As I see it, FW is MCU and Android OS is ROM but let's not get into debate or complicate when I'm trying to KISS it)
user @marchnz has compiled nice thread on how to update to android 10.
If you don't have SD card on your hand or you are lazy/hesitant/what ever, you can use ModInstaller Pro made by @Hal9k_ It's safe and makes life a breeze!
I recommend updating step by step 6>7>8>9>10 and before proceeding to custom rom, install appropriate stock android version first. I advice to backup important files and do a factory reset before flashing new rom and after install wipe data/ factory reset (ModInstaller Pro does this for you after it's done installing). Also pay attention
Here's a list to stock android files.
Yandex - Stock android versions
It's best to check from factory settings what BT-module you have, before proceeding to upgrade. Make sure to check that your devices BT-module works with the android version you intend to install or you just waste time flashing different versions. And it's completely normal if you dont get it right the first time. I have WQ_BC6/8 BT-module and had to use WQ_BC8 before android 10 and now WQ_BC6 on android 10 (if i remember correctly). If you have MD-725 or SD-968 BT-module you can try using BT codec from earlier Android version. Don't even bother trying to get these modules work on Android 10, not gonna happen. It's better to solder a new BT-module if you really want Android 10.
If SD-968 was working in Android 8, but does not work in Android 9. Solution: replace the module driver /system/bin/sdsdk968 with the old version. Do not forget to set permissions 755 on the file. Same can be tried on MD-725 from Android 6/7 to Android 8, I don't guarantee it will work. Files are out there (and in your machine before making the update).
If you happen to install package with wrong resolution, you can try to fix it using this (yandex).
For different look you can try different launchers from google play or yandex link again.
That's it. Not too complicated. If you want to root your head unit, easiest way is to flash a custom rom that has It done for you already. I really recommend ModInstaller Pro even though it cost a bit. But it saves time and nerves and it's safe to use especially for novice. By doing yourself without knowledge you might end up bricking your device!
For me this new territory of android car head units was like a swampland even though I'm experienced on rooting and flashing android phones but for example adb sideloading is most of the time not even an option when playing with these head units.
I spent hours and days to get into this, but now I can update a head unit and make app installs and settings in under 1 hour.
Remember every unit is different! Not everything works on all devices. Get to know the unit you are playing with, update MCU, after that decide what android version is ok with your device (BT-module) then update (highly recommend ModInstaller Pro)
{
"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"
}
Yandex
Finds everything
disk.yandex.com
This is MCU update
This is forums for learing
So got that new MCU and experienced with different ROMs. Got the machine work bit faster but Im still experiencing problems with BT. I had Malaysk Oreo and BT mic sounded underwater, not sure if it was using internal and external mic at the same time. Didn't rule that out when I went trying Hal9k Pie, didn't get any BT connectivity.
Now I'm planning to roll back to Oreo or earlier or ordering RF210 module and taking a shot. I'm just hesitant on both options because rolling back might get that device work slower and in the other hand tinkering the inners of the machine is always a risk. Any recommendations especially on rom side is appreciated. New HU is not an options.
I tried hal9k android 9 and got BT to connect, but hands-free is not working. I have to select WQ_BC8 from factory settings for BT and then it gives CAR-KIT device name in bluetooth. Does anyone have any knowledge about this BT module and can it work in more recent versions of android?
Didn't have much luck getting BT work well on Android 8 & 9 custom roms, didn't even try BT connectivity on stock roms. Don't know if it was just user error or custom roms I tried, but magically in Android 10 BT worked great, both stock and custom rom. Still need to make sure OBD connection works.
If people new to these things need help, please don't hesitate to ask a question! My idea for this thread is a collection of dumb questions so we don't litter official threads meant for other use than FAQ.

Categories

Resources