FORUMS
Remove All Ads from XDA

MTCD Intel Sofia Units (WIFI & 3G) Repository [NOT JOYING]

2,088 posts
Thanks Meter: 568
 
By ikerg, Senior Member on 6th January 2017, 03:59 PM
Post Reply Email Thread
This thread is intended to collect the MCU and ROM Updates for the different MTCD Headunits (Not Joying) based on the Sofia 3230RK (X3) Intel+RockChip SoC.
Many users are buying their headunits and the information between MTCD and Joying (non MTCD) is mixed.

Information about the processor is presented by [email protected] on the following thread:
https://forum.xda-developers.com/and...l-cpu-t3494083

Other thread for Intel Sofia Units (Joying and MTCD) is:
https://forum.xda-developers.com/and...specs-t3468322

This Unit is an upgrade of the MTCD based on RK3188 Chipset.
It has been released on late 2016 and it seems to be the MTCD standard (lollipop 5.1.1) prior to manufacturers upgrade to the new PX5 platform

The unit consists on two parts:
  • MCU board, which controls physical buttons and A/V inputs/outputs to/from the headunit. This board interacts with Android OS.
  • ANDROID part. The main Operating System.

Both MCU and Android ROM interact together to achieve the functionality of the unit

Joying Intel Sofia Units are not supported in this thread as they have different MCU type, and, therefore, the Android part will be customized as well to interact with that MCU

When an update is released two files are provided:
  • The Android ROM (update.zip file)is based on Lollipop 5.1.1 and it is common for all the MCTD Sofia Units
  • the MCU (dmcu.img) is specific for each manufacturer and it should never be updated with other manufacturer mcu update file (unpredicted response from physical buttons - or CAN bus responses, or bricking the unit)

Manufacturers.
The Manufacturer is identified by the XXX when consutling the device information [MTCD_XXX_Version]:
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HOtAudio under 1.93_1 version)
Known manufacturers for MTCD Intel Sofia are:
HotAudio --> HA
???????? --> HXD
BonRoad--> HCT
Erisin/Pumpkin --> LM
Xtrons --> GS
(this list will be updated according to users report new manufacturers)

MTCD Unit Types
All units are close the same. Only physical buttons or added functionalities by external CAN bus decoder (provided by the manufacturer) can differenciate them. Two main different types are identified:
  • MTCD Sofia Intel units with WIFI Only (not 3G built in - SIM slot) - called sofia3grw
  • MTCD Sofia Intel units with 3G built in - SIM slot and 3G Antenna - called sofia3gr

Roms for WIFI version can´t be installed onto Headunits with Built in 3G and viceverse. Initially the updating script detects which version of headunit is installed and aborts the installation. A script modification can be done to force the update, but it has been reported that RIL and BASEBAND is missing (3G capability is lost) if WIFI version ROM is forced to update over 3G built in headunit (rest of the funcionality is not affected)

Android ROM Updates.
The following links provide the update for the Android part of the system. The file shall be renamed to update.zip. NOrmally the links below contains both Android ROM and MCU updates. Be careful to not use the dmcu.img file if you are not sure that it fits to your headunit's manufacturer.

September 22th 2016:October 21th 2016:December 20th 2016January 3rd 2017March 2nd 2017March 28th 2017April 24th 2017 --> MARSHMALLOW!!!MCU Updates.
The following links provide the update for the MCU board. The file shall be renamed to dmcu.img

HA --> Date: ?????? Version: 1.97: https://mega.nz/#!Q8YQjYTY!qZxma-VF3...YRzeHcF9sNdm8g
HA --> Date Feb 27, 2017 Version 2.30: https://mega.nz/#!xxhjySaB!qoAYJBPv4...XEo6CtcLdoQxp0
HXD --> Date: ????? Version: 2.05: https://drive.google.com/open?id=0Bz...1ZoTW53VVo4OWM
HXD --> Date: ????? Version: 2.15: https://yadi.sk/d/zbHCpME33HgJsQ
LM --> Date: Dec, 17, 2016 Version: 2.04: https://www.dropbox.com/s/naqrfnjzf2...1dmcu.img?dl=0
LM --> Date: Feb, 28, 2017 Version: 2.30_2: https://mega.nz/#!Fc1DHDgJ!SzSj01-uw...qDd1QFL3Qq5o6g
LM --> Date: March 2017, Version: 2.41_1: https://mega.nz/#!dQdkiDQR!PeaZO5QSr...5WHZK3C-lr52Eo
GS -->
Date: ? Version: 1.87_2:
Date: ? Version: 1.93_1:
Date: Dec 23, 2016. Version: 2.04: https://mega.nz/#!st4xFarS!kKV_-CqvW...Qx6C_hPi2szDjM
HCT --> Date: ? Version: ?
HXD -->
Date: Jan 23, 2017. Version: 2.05: https://mega.nz/#!YxpiVIJQ!hQDMiUEOs...apcQTaVzt5s3Kg
The Following 18 Users Say Thank You to ikerg For This Useful Post: [ View ] Gift ikerg Ad-Free
 
 
6th January 2017, 04:49 PM |#2  
Member
Thanks Meter: 7
 
More
Erisin ES3092Y
http://www.erisin.com/erisin-es3092y...wifi_p726.html
Attached Thumbnails
Click image for larger version

Name:	Screenshot_2016-11-11_222957.jpg
Views:	5858
Size:	27.9 KB
ID:	3993002  
The Following 2 Users Say Thank You to tally3tally For This Useful Post: [ View ] Gift tally3tally Ad-Free
6th January 2017, 04:50 PM |#3  
OP Senior Member
Thanks Meter: 568
 
More
ANDROID ROM CHANGELOG
(this changelog will be updated as new releases were found)
Magenta versions are those included in repository (OP)

20160910
* Separate the Bluetooth music and Bluetooth applications
* Remove the system default music application in addition to preview part of the application UI
* Remove the side control learning is not practical key learning, optimization of the non-functional keys can not learn
* Remove the system with their own input method desktop shortcut
* Status bar Bluetooth icon policy optimization
* Fixed Music4 autoplay lock time to 8 seconds
* Modify the audio policy BUG
* Repair the Bluetooth music playback pause state to get too slow strategy
* Update the GPS patch
* Remove the side control learning inside the voice and intercom icon
* Added a third-party button to confirm the key support up and down
* power amplifier mode to increase the touch area
* the control settings
* the factory set the default length of other models increased
* prevention and control, touch, panel learning to change the volume of a single learning
* canbus05 update

20160921
* factory setting plus encoder knob mode
* change the main interface Bluetooth music Click to enter the Bluetooth application
* to solve the Bluetooth music interface switch does not return to the Bluetooth interface after the ACC problem;
* update the kernel, MtcManager on switch machine strategy
* handle the download phone book when the cancellation of mobile phone side caused by abnormal restart vehicle;

20160922
* update the camera driver, AVIN and driving records at the same time running off ACC and then turn on driving record does not start
* Radio RDS display incomplete BUG

20160923
* KERNEL modified ADV7180 some chip initialization identification BUG, ??CVBS may not be able to show some of the conditions are improved

20160926
* update wing card software;
* update the mobile Internet software;
* Fixed radio rds psn problem
* Add canbus96 Beiqi Shenbao (wisdom City)

20160928
* update the mobile Internet software;

20160929
*GPS patch restore back to August 31 state ?

20160930
*Factory setting other prohibited to enter the reversing screen to be V1.91 version of the above mcu

20161010
* canbus21 Yan flutter Honda agreement
* TV touch bias
* to optimize the browser to close wifi 3g Internet access problems

20161017
* GPS patch optimization search star problem

20161019
* modify the default power settings factory boot volume

20161021
* update the Bluetooth phone book Bug;
* in the choice of GPS applications to increase the selection of driving assistant map navigation;
* canbus

20161027
* factory settings increase usbdvr and cvbsdvr hidden display
* avin Audio mode through mcu configuration

20161028
* steering wheel control to increase voice wake-up, intercom learning;

20161101
* Factory settings and amplifier volume and dvr settings and mcu v1.95 and above to upgrade the role of Kai
* canbus 81

20161102
*Update canbus81 increase 97 surging Mercedes-Benz agreement 98 Chery City Chery agreement

20161104
*Factory Settings Translation
*Modify AVIN focus issues;
*Steering wheel control to increase voice wake - up, intercom learning;

20161109
*Off acc memory navigation problem
*Canbus
*Modify the Bluetooth can download the card inside the phone book information;

20161112
*Factory default password to 3333 only show the logo settings

20161115
* touch auxiliary function will be added to the system comes with settings, Settings -> Display -> touch support

20161117
* canbus
* the factory settings mcu configuration hidden logo

20161118
* modify the public version of the audio BUG
* Factory settings BUG repair

20161123
* off AC off B + off in the AC does not remember the problem
* optimization of low temperature Huaping

20161125
* Sofia important update RK, to solve the very few cases of panic and camera crashes,

20161128
* Resolve CVBS in some cases synchronization loss, resulting in the screen flash BUG

20161130
* The last version can not solve the standby problem

20161201
* SOFIA standby timing adjustment

20161207
* Add the patch optimization card logo
* Update recovery

20161217
* Exit reversing flash about the problem
* Update google play

20170103
* Update Google Pack 20161220
* Update HCTCarTouch
* Canbus
The Following 4 Users Say Thank You to ikerg For This Useful Post: [ View ] Gift ikerg Ad-Free
6th January 2017, 05:05 PM |#4  
OP Senior Member
Thanks Meter: 568
 
More
Root and Other Stuff
MTCD Intel Sofia Units Rooting Methods: METHOD1
The easiest way to root our units is by using an update.zip file. It will be detected by the unit as a normal update.
This file injects the root privileges into the boot partition.
boot.img is being used, modified and reinstalled onto the Headunit, so it is recommended to use the same boot.img as was into the non rooted system.

I have prepared some root files for both 3G and WIFI units using differents boot.img files (extracted from different ROMs - they shall be renamed to update.zip prior copied into the USB/SD).

EDIT -> root update.zip file only can be installed from recovery menu.
To enter into recovery menu:
* Press reset button and hold until you see the button lights blinking (10 secs approx.)
* Release and press again until you see the lollipop logo
* Release and wait to the recovery menu.
Once into recovery, use the reset button for:
* Move along the options (short press)
* Select an option (long press)



Sofia3gr (3G version):Sofia3grw (WIFI only version):MTCD Intel Sofia Units Rooting Methods: METHOD 2
This Method is by using adb over WIFI. This has been reported to work under New Android 6.0.1 ROM
Instructions:
In Android:
1) Download "Terminal" apk from Google Play
2) Open Terminal and put the following commands:
su
setprop persist.adb.tcp.port 5555
In PC:
3) Download the zip file from this post
4) Decompress the zip on a folder of your Hard Disk
5) execute CMD in Windows
6) Go to that folder and put the following command: install xxx.xxx.xxx.xxx
(xxx.xxx.xxx.xxx is the IP of your HeadUnit under the same WIFI as your PC)
Wait for the Succeed Message
7) Reboot your Unit


Differences between 3G version and WIFI only version ROMS
According what i have seen, only differs on the default.prop file. This file can not be edited into the installed ROM, as it is part of the boot and, even edited (i.e with root explorer), once rebooted, the file will be reverted to the original state, as it is written into the ramdisk.

MTCD Intel Sofia Units TWRP

On Russian 4Pda forum (Thanks InvisiBot & Lemegor) have built a compatible TWRP 2.8.7.0 for our Units. I have semi-translated the previously google translated russian text and included the attachments (thanks @lemlY):
TWRP is available in two versions:
  • Temporary - TWRP uncompressed onto a ramdisk (in memory) over the stock recovery. It is a relatively safe option, TWRP disappears after a reboot;
  • Permanent - TWRP is replacing stock recovery.

Installation known Issues:
As a result of testing, after a number of installations in a few days, it has been found that during the installation of the zip-file with TWRP (temporary or permanent) the unit can enter in a freeze state.

In the case of freezing when you try to install the Temporary TWRP, you need to remove the stick and interrupt the power (which may already be for someone to challenge).
In the case of freezing during installation of permanent TWRP , after the restart noted that the partition recovery is inoperable.
  • If hung but loaded into Android, the recovery partition can attempted to be restored by using the dd method (see below)
  • If hung and not loaded into Android, you may get broken in bootloop recovery. The only solution to restore the device may be achieved only by soldering hub (to 27 & 28 pin) to the Headunit be detected by Computer USB and then flash firmware via FlashToolE2 .
    Flasher Program (FlashToolE2) --> https://drive.google.com/open?id=0Bz...WhXZHdjNDEzSlU
    Recovery Flash for Sofia 3GRW (WIFI) --> https://drive.google.com/open?id=0Bz...EpSeG9Na0RJQ0E
    Recovery Flash for Sofia 3GR (3G) --> NOT AVAILABLE

After a successful install of TWRP, it works fine .
[I]Perhaps a more reliable version of the installation - is flashing TWRP / recovery using dd from under Android:[/B]

adb connect ip-address-HU
adb root
adb shell "dd if = / mnt / usb_storage3 / = recovery.img of / dev / block / mmcblk0p10"


TEMPORARY TWRP
* Sofia 3GR 2.8.7.0 --> https://drive.google.com/open?id=0Bz...TdLQzNBXzVTNlE
* Sofia 3GRW 2.8.7.0 --> https://drive.google.com/open?id=0Bz...TNxU2JrUy1xd1U

PERMANENT TWRP
* Sofia 3GR 2.8.7.0 -->
* Sofia 3GRW 2.8.7.0 -->

IMPORTANT!!
All this process has been tested on WIFI version of units. Files can't be interchanged between 3GR & 3GRW because of different electronics.

After TWRP , the MCU upgrade will no loger works. In case of needed to upgrade the MCU, you can go back to stock recovery:
* Sofia 3GR Stock Recovery --> https://drive.google.com/open?id=0Bz...VJPNnEzY1lfY1E
* Sofia 3GRW Stock Recovery --> https://drive.google.com/open?id=0Bz...nZLc0ZpTmM2QkE



MTCD Intel Sofia Units 3GR vs 3GRW
default.prop differences are shown on the following image (left=WIFI; right=3G)
Attached Thumbnails
Click image for larger version

Name:	3grw_vs_3gr.jpg
Views:	2400
Size:	201.9 KB
ID:	3999051  
The Following 2 Users Say Thank You to ikerg For This Useful Post: [ View ] Gift ikerg Ad-Free
6th January 2017, 05:19 PM |#5  
OP Senior Member
Thanks Meter: 568
 
More
Tools for Our MTCD Intel units
Developing Tools
Update.zip has some files inside:
  • Boot.img --> contains the boot partition data. In this partition is injected the SuperSU for granting Rooting
  • system.new.dat --> contains the Android System data (all apps and everithing)
  • fwu_image.bin --> Not sure about this file... it seems to be related with some kind of fastbooting.

A) Android Image Kitchen v2.32 --> To pack/unpack partition images (boot.img)

B) Auto Tool v3.0 x64 --> To pack/unpack System ANdroid images (system.new.dat)

All the packages included in ROM (system.new.dat) are odexed. It contains the apk file (style of application) and a .odex file (with the operation code of the app) inside a "x86" folder
in order to get the source code for any package:
1) Unpackage the system.new.dat included on update.zip by using Auto Tool v3
2) look for your package to be studied (located on "\system_\app\PackageName" or on "\system_\priv_app\PackageName")
3) deodex the file (located on "..\PackageName\x86" (convert .odex to dex). this can be achieved with oat2dex.jar included on BackSmali package

4) Get the Java File (.jar) from dex File with dex2jar package (included on dex-tools-2.1)
(e.g. d2j-dex2jar MTCManager.dex will create a MTCManager-dex2jar.jar file
5) you can decompile the jar file to a human readable java format by jd-GUI package



UPDATE: Here you can find a decompiled version for all MTCXXXX apps for any debug/investigation purpose. They are in smali format.
https://drive.google.com/open?id=0Bz...FFsczB0bS1vTWs
The Following User Says Thank You to ikerg For This Useful Post: [ View ] Gift ikerg Ad-Free
6th January 2017, 06:15 PM |#6  
Junior Member
Thanks Meter: 3
 
More
MTCD Intel Sofia Units (WIFI & 3G) Repository [NOT JOYING]
According to some screenshots posted by [email protected], the BonAudio MCU is MTCD_HCT_xxxx.

I'm very interested in getting a BMW E46 version of these units - MTCD with Intel processor. From what I have read the Bluetooth on these is available to android, and not restricted by the MCU.. this would solve many Bluetooth issues - hopefully these will be able to pair with devices that have a Bluetooth pin code.
The Following User Says Thank You to gumanov For This Useful Post: [ View ] Gift gumanov Ad-Free
6th January 2017, 09:03 PM |#7  
OP Senior Member
Thanks Meter: 568
 
More
Quote:
Originally Posted by gumanov

According to some screenshots posted by [email protected], the BonAudio MCU is MTCD_HCT_xxxx.

I'm very interested in getting a BMW E46 version of these units - MTCD with Intel processor. From what I have read the Bluetooth on these is available to android, and not restricted by the MCU.. this would solve many Bluetooth issues - hopefully these will be able to pair with devices that have a Bluetooth pin code.

These MTCD intel can pair with any bluetooth device (including those with PIN code)....there is an option to select the PIN prioir to pair the devices
6th January 2017, 09:45 PM |#8  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by ikerg

These MTCD intel can pair with any bluetooth device (including those with PIN code)....there is an option to select the PIN prioir to pair the devices



Is it similar to an android phone with a pop up message asking for the pin? Or is it like my MTCC unit where you can set a default unit pin in the Bluetooth settings page?
6th January 2017, 10:02 PM |#9  
OP Senior Member
Thanks Meter: 568
 
More
Quote:
Originally Posted by gumanov

Is it similar to an android phone with a pop up message asking for the pin? Or is it like my MTCC unit where you can set a default unit pin in the Bluetooth settings page?

Like mtcc. You set a default pin. I have a icar3 obd2 bt paired that handles a 1234 pincode running perfectly with torque and dashcommand

Enviado desde mi D6603 mediante Tapatalk
6th January 2017, 10:20 PM |#10  
Junior Member
Thanks Meter: 3
 
More
Quote:
Originally Posted by ikerg

Like mtcc. You set a default pin. I have a icar3 obd2 bt paired that handles a 1234 pincode running perfectly with torque and dashcommand

Enviado desde mi D6603 mediante Tapatalk



Ah ok. I have an OBD2 adapter with modified firmware specific for BMW's - it's supposed to connect with the android app "Deep OBD for BMW". My MTCC unit pairs and connects with the adapter but the app does not see the adapter at all. Does this have to do with the fact that the Bluetooth is managed by the MCU and not the android OS? Is that not the case for these new MTCD Intel units - Is the OS managing the Bluetooth now?

I'm hoping I'll be able to use my modified OBD if I end up buying an MTCD Intel.
7th January 2017, 05:34 PM |#11  
Junior Member
Thanks Meter: 3
 
More
Does a single DIN unit of this type exist yet?
MTCD Intel, single DIN unit (Not Joying, since it isn't MTCD)

Since there currently isn't one specific to the BMW E46, I was thinking about getting a generic single DIN unit, and takings its' internals out (everything but the display), and putting it all into my single din MTCC unit which is specific to the BMW E46 (physical layout).
Post Reply Subscribe to Thread

Guest Quick Reply (no urls or BBcode)
Message:
Previous Thread Next Thread
Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes