Related
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/an...t/intel-cpu-mtcd-mtc-units-intel-cpu-t3494083
Other thread for Intel Sofia Units (Joying and MTCD) is:
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-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:
WIFI --> https://drive.google.com/file/d/0Bz8umNL1qrsoTDcwX1ViMG1BbFU/view
3G --> N/A
October 21th 2016:
WIFI -->http://mail.qq.com/cgi-bin/ftnExs_d...4d4a574b357e&t=exs_ftn_download&code=9549cc86
3G --> http://mail.qq.com/cgi-bin/ftnExs_d...16145541637d&t=exs_ftn_download&code=74f8f43c
December 20th 2016
WIFI --> https://mail.qq.com/cgi-bin/ftnExs_...50a52151646500747061d4f0a46345b&code=f3c35c64 or https://drive.google.com/open?id=0B5k39tJWUEHIMFFuVTdXSThNSzA
3G --> https://www.dropbox.com/s/fw2ghw8m4f6nvun/update 20161220.zip?dl=0 (Source: Pumpking. Thanks @sorinblu)
January 3rd 2017
WIFI --> N/A
3G --> https://drive.google.com/file/d/0B6c7wyyjyJofNlB1U0VFOG91aUE/view?usp=drive_web [Source: HotAudio. Thanks Mr.Yuan (@hotaudio)]
March 2nd 2017
WIFI --> N/A
3G --> https://mega.nz/#!RdkTADJa!_7dmoYNMMC-BfyQUqfvM8zLWGV9B0_Gf2HR-kI_2ZxU [Source: Pumpkin. Thanks (@manderson77)]
March 28th 2017
WIFI --> N/A
3G --> https://mega.nz/#!BRsC1TrL!I9DMTHJzfso3GlPtEGy7iMCvFLVPESrgAHfntdHi_uo [Source: Pumpkin. Thanks (@manderson77)]
April 24th 2017 --> MARSHMALLOW!!!
WIFI --> N/A
3G --> https://www.sendspace.com/pro/dl/3wj088 [Source: Dasaita. Thanks (@hotaudio)]
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-VF3HQXlN0yklxWaNZFPH9tdYRzeHcF9sNdm8g
HA --> Date Feb 27, 2017 Version 2.30: https://mega.nz/#!xxhjySaB!qoAYJBPv4cKsAOviU4QtE8W-Ys7k5XEo6CtcLdoQxp0
HXD --> Date: ????? Version: 2.05: https://drive.google.com/open?id=0BzpR8k0kgZq3Y1ZoTW53VVo4OWM
HXD --> Date: ????? Version: 2.15: https://yadi.sk/d/zbHCpME33HgJsQ
LM --> Date: Dec, 17, 2016 Version: 2.04: https://www.dropbox.com/s/naqrfnjzf2yubh0/LM_12-17-16_v2.04_1dmcu.img?dl=0
LM --> Date: Feb, 28, 2017 Version: 2.30_2: https://mega.nz/#!Fc1DHDgJ!SzSj01-uwRumYAlJ-mTWZpwPwXz-TqDd1QFL3Qq5o6g
LM --> Date: March 2017, Version: 2.41_1: https://mega.nz/#!dQdkiDQR!PeaZO5QSrG7L-755GWUwlMsuxnbB85WHZK3C-lr52Eo
GS -->
Date: ? Version: 1.87_2:
Date: ? Version: 1.93_1:
Date: Dec 23, 2016. Version: 2.04: https://mega.nz/#!st4xFarS!kKV_-CqvWB19jmSS3gGb0Rfhbj-guQx6C_hPi2szDjM
HCT --> Date: ? Version: ?
HXD -->
Date: Jan 23, 2017. Version: 2.05: https://mega.nz/#!YxpiVIJQ!hQDMiUEOsAbVtxbDNw8ndDyFGHcazapcQTaVzt5s3Kg
Erisin ES3092Y
http://www.erisin.com/erisin-es3092...d-51-os-car-gps-sat-nav-dab-3g-wifi_p726.html
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
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):
Based on boot.img from October 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3c08teWJJbHpqLVE
Based on boot.img from December 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3eUp4c0F3dV9Hd28
Based on boot.img from March 2017 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3bTlDdG5Qc2ZoNDA
Sofia3grw (WIFI only version):
Based on boot.img from September 2016 ROM: https://drive.google.com/open?id=0BzpR8k0kgZq3bkdhMFdyQ2lSbTA (the one published on the russian forum)
Based on boot.img from December 2016 ROM (latest): https://drive.google.com/open?id=0BzpR8k0kgZq3U1RjMThZSFhHZlk
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=0BzpR8k0kgZq3eWhXZHdjNDEzSlU
Recovery Flash for Sofia 3GRW (WIFI) --> https://drive.google.com/open?id=0BzpR8k0kgZq3TEpSeG9Na0RJQ0E
Recovery Flash for Sofia 3GR (3G) --> NOT AVAILABLE
After a successful install of TWRP, it works fine .
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=0BzpR8k0kgZq3QTdLQzNBXzVTNlE
* Sofia 3GRW 2.8.7.0 --> https://drive.google.com/open?id=0BzpR8k0kgZq3YTNxU2JrUy1xd1U
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=0BzpR8k0kgZq3NVJPNnEzY1lfY1E
* Sofia 3GRW Stock Recovery --> https://drive.google.com/open?id=0BzpR8k0kgZq3RnZLc0ZpTmM2QkE
MTCD Intel Sofia Units 3GR vs 3GRW
default.prop differences are shown on the following image (left=WIFI; right=3G)
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=0BzpR8k0kgZq3cFFsczB0bS1vTWs
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.
gumanov said:
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.
Click to expand...
Click to collapse
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
ikerg said:
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
Click to expand...
Click to collapse
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?
gumanov said:
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?
Click to expand...
Click to collapse
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
ikerg said:
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
Click to expand...
Click to collapse
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.
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).
gumanov said:
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).
Click to expand...
Click to collapse
I dont know if the Display is the same between MTCC and MTCD... go to this thread to see some images (OP) of the interior of a MTCD/intel in order you figure out if this can be feasible:
https://forum.xda-developers.com/an...opment/2gb-ram-intel-cpu-heres-specs-t3468322
I think you can ask manufacturer all the parts (except any display and/or frame) in order to reduce the final price.
I am planning to release a Prerooted Versions for 3G and WIFI MTCD units. Meanwhile on Post#4 you can find Rooting update files for latest December versions of ROM.
Some info needed
Hi, I'm new owner of a Pumpkin Rq0278 unit that seems apparently a rebranded Erisin one. The unis has Sofia3gr processor and the MCU is an LM type. The unit work almost good except the AF of the FM tuner that is not working at all. My questions are:
- can I try to flash my unit with your firmware avoiding issues?
- can I root my unit using your root update without modifying my firmware?
- I don't know very well how the android units work, the tuner is managed by the android part or by the MCU? In last case would be useful to try a MCU firmware update?
Many thanks in advance
zio_mario said:
Hi, I'm new owner of a Pumpkin Rq0278 unit that seems apparently a rebranded Erisin one. The unis has Sofia3gr processor and the MCU is an LM type. The unit work almost good except the AF of the FM tuner that is not working at all. My questions are:
- can I try to flash my unit with your firmware avoiding issues?
- can I root my unit using your root update without modifying my firmware?
- I don't know very well how the android units work, the tuner is managed by the android part or by the MCU? In last case would be useful to try a MCU firmware update?
Many thanks in advance
Click to expand...
Click to collapse
What kind of problems you have with the Tuner?
Have you set it up to your Region? Tuner in America/Asia/Europe manages different frequency ranges.
the Tuner is managed by the MCU. You can set it up on Settings > Factory Settings
enter the password 126
You can see specific options for the Radio and check that you have it configured properly to your region
If not solved you have to ask for newer MCU update to Pumpkin
The Android part (ROM) is interchangeable between different manufacturers (check that you have a MTCD unit based on INtel platform):
If your unit has 3G built in --> You have a sofia3gr-car and sofia3gr device
If your unit has not 3G built in (WIFI only) --> You have a sofia3gr-car ans sofia3grw device
You can update your Android ROM by using the corresponding update to your device from the repository on the OP
The rooting method SHOULD NOT ALTER anything, just adds the root permissions from the boot image.
I published different root files according to the Boot image data and device type
The 126 at factory settings not working for me. Is there anyone know the right number?
Dear Ikerg,
Thanks for your quick answer!
My unit has an Intel CPU with 3g built-in so is a Sofia3gr. The problem of my tuner is the AF functionality that is not working properly. I already checked the configuration in the factory menu (3368 is the pass code), I tried also to change it using China, Australia and so on but nothing changed. I saw that my MCU is not in the last release but for the moment Pumpkin support didn't provide me any upgrade, only for the Android part. Looking in the forum it seems that the img of my unit has the same code name as the Erisin Intel 2gb units (LM). I would like to try one of the available update but I don't won't to brick the unit!!!
About the Android part I'm interest to have root permissions as usually in my android devices in order to be able to perform some backup and other operations. So I can use one of the two update.zip you posted without flashing your complete firmware? At the end of the flashing I can simply do a cache format or a full wipe is needed? I have some doubts because you wrote that the root update contains a boot.img file that must match with the one of my non rooted image. Now I have my original Pumpkin image. The size of the file is exactly the same but comparing the content the files are not equal.
Last question about the Android ROM, you posted several version with related changelog, those versions are made by you or did you collected it from the different brand? Do you think I can have some benefit to install the most updated one from you against the one I have now in my unit (version date is 20.12.2016)?
Thanks again!
zio_mario said:
Looking in the forum it seems that the img of my unit has the same code name as the Erisin Intel 2gb units (LM). I would like to try one of the available update but I don't won't to brick the unit!!!
Click to expand...
Click to collapse
If your unit is LM you can safely update the mcu as it is sourced from same manufacturer (pumpkin and erisin probably will have same rebranded models)
zio_mario said:
...I have some doubts because you wrote that the root update contains a boot.img file that must match with the one of my non rooted image. Now I have my original Pumpkin image. The size of the file is exactly the same but comparing the content the files are not equal...
Click to expand...
Click to collapse
With respect to the root....i only had a update.zip with root that was published some months ago in a Russian forum, which was for wifi version. Some guy reported that flashing that update file on a 3g built-in model can caused to loose the 3G capability.
So I did extract the boot.img and compared with the non rooted boot.img and checked what changed.
I did compare as well two boot.img (non rooted) from same build for wifi and 3g versions and noticed what changed
So finally I put it altogether on a new boot.img from last version i had and build the zip back and signed.
I have not tried it yet, but it is supposed to work.
When I said that boot.img shall match I meant that it is recommended to be for the same date build. If you flash an older boot.img over newer release you can loose any enhancements that could be performed on the newest release. (But according I saw, nothing remarkable)
All the boot.img files for our units must be same sized as it is uploaded onto partition of the unit (which matches that partition the size)
zio_mario said:
...Do you think I can have some benefit to install the most updated one from you against the one I have now in my unit (version date is 20.12.2016)?...
Click to expand...
Click to collapse
If you look at the changelog (just google-translated from the original Chinese changelog from the developer - I think developer is the same for all the brands) only changed the update of Google services (which you can update from google play) so I don't think you will notice any change. (It could be fine if you provide me a link with your december release for 3g built-in model rom to complete the repository)
Anyway if something was wrong you can safely go back with a original update.zip from the recovery menu.
Enviado desde mi D6603 mediante Tapatalk
ikerg said:
If you look at the changelog (just google-translated from the original Chinese changelog from the developer - I think developer is the same for all the brands) only changed the update of Google services (which you can update from google play) so I don't think you will notice any change. (It could be fine if you provide me a link with your december release for 3g built-in model rom to complete the repository)
Click to expand...
Click to collapse
Here you are the link containing the December release from Pumpkin (only Android ROM)
h t t p s ://mega.nz/#!UQsD1DiC!VolW1UbNkRHq8D65aMoxJ1G2B5qmqxYuuyCrhn_Sp8s
Is it possible for you to prepare a root update.zip containing the boot.img of the release I linked? (I have no experience in this kind of operations).
The purpose is to have a unit much updated as possible, a clean installation and root present. The maximum would be to have also a recovery able to perform backup/restore like TWRP but I didn't find nothing till now.
For info, about my AF problems I flashed the last MCU firmware (LM 2.04) but I tried the FM tuner only in the park so wasn't possible to appreciate some progress... Tomorrow I'll try
Last thing, why the password is not the same if the ROM is supposed to be the same for all the brands? You said 126, mine is 3368
Is this thread also for pumpkin RQ0278E?
Στάλθηκε από το BTV-DL09 μου χρησιμοποιώντας Tapatalk
This thread is intended on collect the information about Android 8 (Oreo) over the Android units that features:
PX5 Platform Core Board
MTCD/MTCE MCU Type
The information below is a copy of the same thread for Android 6 by @aarick
Post 2: Firmware
Post 3: Tips, Tricks and Fixes - Rooting instruction here
Post 4: Bugs/Issues
Post 5: Useful apps
Post 6: Useful links
For those not familiar with the PX5 Head unit, the specs are below:
OS: Android 8.0 Oreo
CPU: Rockchip PX5 A53 Octa-Core
RAM: 2GB or 4GB DDR3
ROM: 32GB
Audio output: 4*45W
Features:
Built-in Radio Tuner (RDS Enabled) (18 FM and 12 AM stations Preset)
Built-in USB & SD Slot
Region Free DVD Player
Screen Mirroring
Steering wheel controls (SWC) and Canbus interface
Optional compatible accessories:
DAB+ USB Tuner
TPMS
4G/3G Dongle
OBD02 Module
Camera
DVR
External Mic
The head unit comprises of two parts:
a MicroController Unit(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 head unit.
MCU
MCU type discussed here is MTCD or MTCE (if your unit has not MTCD/MTCE type MCU this thread is not for your unit)
MTCE is a software upgrade for MTCD, so they are identical in terms of hardware
Manufacturers.
The Manufacturer is identified by the XXX when consulting the MCU information under "device information" [MTCE_XXX_Version]. Take into accout that you should always refer the MANUFACTURER name (not the seller) on the forums for help/assistance. Giving the name for the Seller does not give any information but confusion.
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HotAudio under 1.93_1 version)
e.g: MTCE_GS_2.75 (MTCE Unit with MCU for GESHI manufacturer under 2.75 version)
Known manufacturers for MTCD/E PX5 are:
______________ _____________
GS = GE_SHI (ShenZhen GESHI Electronics And Technology CO.,LTD. Brands: KA JUN DA. Website: http://www.szgeshi.com )
KD = KU_DUO (Shenzhen Kuduo Electronic Technology Co. Ltd.)
HA = (Guangzhou Huge Circle Electronic Technology Co., Ltd. Brands: HOTAUDIO/DASAITA. webSite: http://www.hot-audio.com)
JY = JIE_YOU (Shenzhen Jieyou Electronic. Brands: JIE YOU J)
LM = LEI_MA (Lei Electronics Inc)
MX = MAI_XIN (Shenzhen Mai Xin Da Technology Co. Ltd)
ZH = ZHI_HANG (Guangzhou Zhihang Electronics Technology CO., LTD. Brands: WINCA/ROADNAV/STQ) http://www.roadnav.com.cn)
HZC = HANG_ZHI_CHEN (Same as ZH??)
HXD = HE_XIN_DA
KGL = KAI_GE_LE (Shenzhen Kaigele Electronics Co., Ltd Brands: HUIFEI. Website: http://www.kaigele.com/enus/)
KLD = KE_LAI_DE
KSP = KA_SI_PU (Kasi Pu Technology Co., Ltd. Shenzhen)
XRC = XIN_RUI_CHANG (Xinrui Electronic Technology Co. Ltd)
HLA = (Shenzhen Hualingan Electronic Co. Ltd. Brands:HUALINGAN. Website: http://www.dvdplayer.com.cn/)
(this list will be updated according to users report new manufacturers)
Some information I found on the CPU:
Rockchip PX5 Press Release
Firmware Post
MCU Upgrades Repository:
https://forum.xda-developers.com/showpost.php?p=72622240&postcount=2
ANDROID 8 (Oreo) stock Update List:
All the stock and custom PX5 MTCD/MTCE firmwares are valid for all PX5 MTCD/E units independently of manufacturer/seller/amount of RAM/amount of ROM
December 19th 2017. Source Dasaita. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/kc1azp
January 8th 2018. Source HCT. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/empate
January 18th 2018. Source GS. Thanks @kumarai --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 8.0/GS
February 28th 2018. Source HCT. --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 8.0/HCT
March 5th 2018. Source Dasaita. Thanks @hotaudio --> https://www.sendspace.com/pro/dl/v7cuby
March 13th 2018. Source Xtrons (GS). Thanks @catelusii --> https://1drv.ms/u/s!AjrY0uqbW_kBhCr0zB8pj-rIig_U
April 13th 2018. Source Dasaita (HA). Thanks @hotaudio https://www.sendspace.com/pro/dl/7smety
May 16th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/q9mr31
June 11th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/np2t2w
June 27th 2018. Source HCT. Thanks @fastebp
https://www.sendspace.com/pro/dl/nkez0x
July 5th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/dl/2l056f
July 17th 2018. Source Dasaita (HA). Thanks @hotaudio
https://www.sendspace.com/pro/lo8ztf
ANDROID 6.0 -> ANDROID 8 UPGRADE WARNING
Due to change in partition system and upgrade in recovery system, update can't be performed using the OTA Android 8 files over Android 6.0 as usual method (direct or Recovery) as it will result in an error (or could get a bricked device...)
The only available methods are:
1) Upgrade by using SDCARD slot:
Thanks to @marchnz for the Oreo ROM Dumping, to @kumarai for the recovery change procedure, to @SkyBeam2048 for the compiled solutions for Upgrading/Downgrading (and the comprehensive instructions)
The following Procedure can be used :
https://forum.xda-developers.com/showthread.php?t=3736950
Note1. Your unit MUST have a SDCARD slot with direct access to recovery (Not all SDCARD slots on all units can - some sdcard slots have been reported to be another usb port extension [USB3] and they will not work for upgrading)
Note2. USB port is not able to upgrade the recovery as required.
Click to expand...
Click to collapse
2) Upgrade by extracting the SOM and connecting a homemade OTG USB cable:
Instructions for making the OTG cable:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
For upgrading via OTG cable it is recommended to use Rockchip Tools for the Android 6 to 8 upgrade from a PC (to put the unit into "loader Mode" and then flash the supplied firmware)
Custom Oreo Firmwares:
@Malaysk has been released a prerooted Android 8 image with several improvements and modifications:
https://forum.xda-developers.com/an...-malaysk-roms-px5-2-4-gb-8-0-android-t3762724
Tips, Tricks and Fixes
Root for stock ROMs.
[*] Method 1: SDCard & Flashing Update File
Android 8 ROM Root requires to boot.img to be modified and loaded during the Flasing process. @kumarai has been released a first Oreo Root files based on GS ROM from January.
This information is extracted from:
https://forum.xda-developers.com/showpost.php?p=75741195&postcount=519
ROOT rights for Oreo based on GS firmware from 20180118
Receiving the root only through the loading card. The load map contains a modified recovery, and the update.zip update is modified by the boot.
Download archive
Yandex - https://yadi.sk/d/pFSNkK4_3SwNx5
Google - https://drive.google.com/file/d/1xpz...GmaEPfsjd/view
The archive contains the following folders:
Androud-8-sdupdateROOT
CreateCD
SD Formatter
UpdateZIP-patch-root
- In the CreateCD folder, create a bootable card using SD_Firmware_Tool (the program is configured, no checkboxes are set)
- Image to create a map from the folder Androud-8-sdupdateROOT
- After creating the boot card, delete sdupdate.img from the card
- Copy from the UpdateZIP-patch-root folder to the root of the card's SD update.zip
We insert the card into the recorder, reboot, install the update from the SD Card
Remove the card and reboot the radio.
Map formatted with the program from the folder SD Formatter
The root system / app script writes to MagiskManager-v5.6.1.apk
Click to expand...
Click to collapse
[*] Method 2: Injecting supersu via ADB
Originally Posted by Copycat228
Hello!
Use the following instruction to receive permanent root on Android 8 using adb without flashing device:
On Head Unit, install terminal emulator on device and run two following commands and reboot device. This will open ADB witj root permissions on the port 5555
Code:
setprop persist.adb.tcp.port 5555
setprop sys.rkadb.root 1
On your PC, download latest "SuperSu" zip archive from official site, extract su binary from arm64 directory inside the archive
On your PC, create new file called "rooting.rc" with following content:
Code:
service rooting /system/bin/su --daemon
class main
priority 10
user root
oneshot
seclabel u:object_r:system_file:s0
From your PC run:
Code:
# adb connect "device_ip"
# adb root
# adb connect "device_ip"
# adb remount
# adb shell setenforce 0
# adb push su /system/xbin/su
# adb push su /system/bin/su
# adb shell chmod 06755 /system/bin/su
# adb shell chmod 06755 /system/xbin/su
# adb shell /system/bin/su --install
# adb shell /system/bin/su --daemon&
# adb push rooting.rc /system/etc/init/rooting.rc
On Head Unit, install SuperSu from PlayMarket and ask "NO" when application ask to update the module
Click to expand...
Click to collapse
Reboot and enjoy!
https://youtu.be/4v9s89fYIZ4
Bugs/Issues
Q&A
1. I have a MTCD RK3188 unit. Can I use the firmware updates here published?
No. All the stuff here published is for RK3368 (PX5) MTCD/E units. Only the MCU files could be used for your unit (if it is really a MTCD/E)
2. How do I know if my unit is a MTCD/E?
Go to Settings> Device Information and check the MCU version. it MUST be:
MTCD_XXXXX_yyyyy.
MTCE_XXXXX_yyyyy.
Where XXXXX is the acronym for the manufacturer and yyyy is the version for the MCU file
3. I cant find MTCDs MCU updates, but MTCE. Can I update a MTCE over a MTCD?
HCT developers, starting from MCU version 2.65, has been renamed the MCTD as MTCE. It is reported to be a major software update and it is fully compatible with MTCD MCU. Therefore, you can upgrade to MTCE from MTCD safely.
4. My MCU is XXX and i can't find new updates from manufacturer for a long time. Can I update from other Brand MCU?
Not all the MTCD MCUs are the same, but quite similar between them. There is a thread that is collecting all the MCU cross compatibility based on user experiences.
https://forum.xda-developers.com/an.../mtcd-verified-cross-compatible-mcus-t3624724
5. How Do I enter into recovery menu?
Depending on the HeadUnit, the entering into recovery process could vary.
Reset Button Procedure (You need a needle to access that button inside the Reset hole)
Applicable to:
[*] HeadUnits with no physical buttons on Headunit (just capacitive buttons) [Brands: Dasaita]
1. Press Reset and hold until button light blinks (15-20secs)
2. Release Reset and press again. Hold it until you see the Marshmallow logo
3. Release Reset and wait for the Recovery menu to appear
[*] Power Button Procedure [Brands: Dasaita]
Applicable to:
[*] HeadUnits with physical power button on Headunit [Brands: Dasaita]
[*]When none of the above procedures worked:
1. Disconnected all power from the unit... ACC & BAT disconnected
2. Prepared 12V power supply with on negative and two positive connectors
3. Connected negative to GND & one positive to BAT
4. Connected USB keyboard
5. Press right ALT (ALT GR on some keyboards) and PrintScreen
6. Connected the other positive lead to ACC (unit does not work if both BAT and ACC are not connected)
6a. Start pressing repeatedly on E (not holding E pressed, but press...release... press... release..... rapidly)
7. The boot logo shows (MarshMallow...etc) and after a few seconds the unit reboots itself
8. Release right CTRL & PrintScreen and continue to repeatedly press on E.
9. The Recovery shows on screen.
6. I have a complete Bricked Unit with a continuous loop. What can I do?
First of all, you have to try to reload the firmware into the unit. As you are not loaded into Android system, you must reload the firmware by using the recovery menu. To enter into recovery menu read the FAQ#5.
Most of the times, reloading the Android firmware solve the issue. Try with different firmwares if you can't succeed at first time. When, even having tried to update your firmware from recovery, but it did not succeed, you probably have corrupted your NAND. In that case a more complex solution is available (desoldering/soldering is required) to come the unit back to life. Thanks @marchnz for the detailed description on the following thread:
https://forum.xda-developers.com/an...tions-development/px5-stuck-bootloop-t3635412
7. My HeaadUnit never shuts off and, even several days, after switching engine on the Headunit starts in a few secons....Can I kill my car battery?
These units are designed to enter into deep sleep state detecting ACC off, in order to avoid each time you connect the car, you had to wait a full cold boot (20secs) and they just wake up in 2seconds. During This sleep state, the Headunit consumes a small current (just 100-150mA). Such current can't drain your battery.
Some manufacturers (like Dasaita (HA)) have implemented a menu in which, apart of Auto-Sleep you select at which time you want to HeadUnit shuts off completely, useful for long car unused periods.
8. My apps are killed during Sleep and they don't start again after waking up
These HeadUnits kills background processes (except specific ones) during deep sleep state (see Q&A#6). The killing process is managed by MTCManager.apk file. A developer (@graser) has been released a tool that is based on adding apps/services to a whitelist to pevent the unit killed them during sleep. You need root & Xposed Framework. Currently only working on Android 6. wait for a Android 8 upgrade
9.How can I root my unit?
PX5 devices under MM can be rooted easily by means of using kingoroot app (not kingroot), but Android 8 is more complicated (see Post#2)
10.My Bluetooth is not Working. What can I do?
Some specific implementations for MD725 bluetooth device are lack of necessary Blueooth SDK file into Android image. Currently no solution has been found apart from waiting HCT (software developers) to release an Android 8 upgrade with the required SDK included.
Useful apps
Tool Unpack Repack system.new.dat system.img For Windows v3
Current Oreo update file is based on a "update.zip" file (not classic .img file). When decompressing a file system.new.dat contains all the system information and apks. This tool can unpack and repack these kind of files:
https://forum.xda-developers.com/an...tool-tool-unpack-repack-dat-img-v2-0-t3284806
Useful links
Reserved
---------------
Interesting... Hoping for someone to release an upgrade method....
emre33 said:
ANDROID 6.0 -> ANDROID 8 UPGRADE WARNING
Bootable SDCard to GPS slot??? boot.img, uboot.img
Click to expand...
Click to collapse
What's that mean then?
Sent from my [device_name] using XDA-Developers Legacy app
Reverse camera interrupts head unit sound, is this a software limitation or hardware?
Reverse volume in settings
Sent from my [device_name] using XDA-Developers Legacy app
Hi,what is rar password?
jtheg said:
Reverse volume in settings
Sent from my [device_name] using XDA-Developers Legacy app
Click to expand...
Click to collapse
Will take a look tonight. Thanks
zeyret said:
Hi,what is rar password?
Click to expand...
Click to collapse
No password
Hi,
I have GS px5 HU how can I install it? Please help Thanks!
kispako89 said:
Hi,
I have GS px5 HU how can I install it? Please help Thanks!
Click to expand...
Click to collapse
YES!
Why don't we all jump in and ask that question without reading at least the first page
Hi, just bought my unit recently. Was very happy with the RK3188 version, just a little slow. This one is much faster, only the display is a big disappointment in my eyes. The colores are not really rich in contrast. Grey font on white background is not really readable. Is this the same issue for you too?
dboff said:
Hi, just bought my unit recently. Was very happy with the RK3188 version, just a little slow. This one is much faster, only the display is a big disappointment in my eyes. The colores are not really rich in contrast. Grey font on white background is not really readable. Is this the same issue for you too?
Click to expand...
Click to collapse
I don't know which specific model you have, but I have experienced some of the same. Grey on white is hard to see. I think it helps to view the screen from a more direct angle. I am also experimenting with a sun blocker for when the sunlight angle is very shallow. I may possibly try substituting a 10" screen from a 4gb Marshmallow model. And finally I've ordered a model with a 9" display which is not for my car but I believe it will fit, to see if the screen is any better. I think the 10" Intel Joyings had the best screen, incident light reflects off the pixels instead of the faceplate. Having said all that, the Oreo model I have seems useable, although I haven't taken it on what I would call a road trip yet.
As I still have not opened my Unit, looks like OTG USB is possible only on board modify at least according to https://forum.xda-developers.com/showpost.php?p=73057218&postcount=3 and based on provided schematics in https://forum.xda-developers.com/an...id-head-units-general/mtcd-schematic-t3637816 wonder if there is a way to simplify the process.
I'll have my new GS 8.0 PX5 4.0GB ram unit next week, I'll do a small comparison between my current GS 6.0 PX5 2.0GB unit.
Cheers
Mat
This thread is intended on collect the information about Android 9 (Pie) over the Android units that features:
PX5 Platform Core Board
MTCD/MTCE MCU Type
The information below is a copy of the same thread for Android 6 by @aarick and my own thread for Android 8
Post 2: Firmware
Post 3: Tips, Tricks and Fixes - Rooting instruction here
Post 4: Bugs/Issues
Post 5: Useful apps
Post 6: Useful links
For those not familiar with the PX5 Head unit, the specs are below:
OS: Android 8.0 Oreo
CPU: Rockchip PX5 A53 Octa-Core
RAM: 2GB or 4GB DDR3
ROM: 32GB
Audio output: 4*45W
Features:
Built-in Radio Tuner (RDS Enabled) (18 FM and 12 AM stations Preset)
Built-in USB & SD Slot
Region Free DVD Player
Screen Mirroring
Steering wheel controls (SWC) and Canbus interface
Optional compatible accessories:
DAB+ USB Tuner
TPMS
4G/3G Dongle
OBD2 Module
Camera
DVR
External Mic
The head unit comprises of two parts:
a MicroController Unit(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 head unit.
MCU
MCU type discussed here is MTCD or MTCE (if your unit has not MTCD/MTCE type MCU this thread is not for your unit)
MTCE is a software upgrade for MTCD, so they are identical in terms of hardware
Manufacturers.
The Manufacturer is identified by the XXX when consulting the MCU information under "device information" [MTCE_XXX_Version]. Take into accout that you should always refer the MANUFACTURER name (not the seller) on the forums for help/assistance. Giving the name for the Seller does not give any information but confusion.
e.g: MTCD_HA_1.93_1 (MTCD Unit with MCU for HotAudio under 1.93_1 version)
e.g: MTCE_GS_2.75 (MTCE Unit with MCU for GESHI manufacturer under 2.75 version)
Known manufacturers for MTCD/E PX5 are:
______________ _____________
GS = GE_SHI (ShenZhen GESHI Electronics And Technology CO.,LTD. Brands: KA JUN DA. Website: http://www.szgeshi.com )
KD = KU_DUO (Shenzhen Kuduo Electronic Technology Co. Ltd.)
HA = (Guangzhou Huge Circle Electronic Technology Co., Ltd. Brands: HOTAUDIO/DASAITA. webSite: http://www.hot-audio.com)
JY = JIE_YOU (Shenzhen Jieyou Electronic. Brands: JIE YOU J)
LM = LEI_MA (Lei Electronics Inc)
MX = MAI_XIN (Shenzhen Mai Xin Da Technology Co. Ltd)
ZH = ZHI_HANG (Guangzhou Zhihang Electronics Technology CO., LTD. Brands: WINCA/ROADNAV/STQ) http://www.roadnav.com.cn)
HZC = HANG_ZHI_CHEN (Same as ZH??)
HXD = HE_XIN_DA
KGL = KAI_GE_LE (Shenzhen Kaigele Electronics Co., Ltd Brands: HUIFEI. Website: http://www.kaigele.com/enus/)
KLD = KE_LAI_DE
KSP = KA_SI_PU (Kasi Pu Technology Co., Ltd. Shenzhen)
XRC = XIN_RUI_CHANG (Xinrui Electronic Technology Co. Ltd)
HLA = (Shenzhen Hualingan Electronic Co. Ltd. Brands:HUALINGAN. Website: http://www.dvdplayer.com.cn/)
(this list will be updated according to users report new manufacturers)
Some information I found on the CPU:
Rockchip PX5 Press Release
Firmware
Current PX5 Android 9 firmware development:
Stock
Date: March 22th 2019. Source: HCT. New UI --> https://yadi.sk/d/umCvHqCDzHccr/RockChip PX5 Android 9
Date: April 15th 2019. Source: Dasaita. Classic Blue UI from Dasaita --> https://www.sendspace.com/pro/dl/so9wg2
Date: May 3th 2019. Source: Unknown. --> https://yadi.sk/d/tyLXd4E-xXeylQ
Date: May 5th 2019. Source: MX. --> https://yadi.sk/d/DyLTKQsIQOx7Vg
Date: May 21th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/uv1jkf
Date: May 28th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/tso1eg
Date: May 31th 2019. Source: Dasaita. --> https://www.sendspace.com/pro/dl/yzg5we
Date: Jun 12th 2019. Source: MX. --> https://yadi.sk/d/nsQpvo_4yLv5BA
Date: Jul 31th 2019. Source: Dasaita. -->
https://www.sendspace.com/pro/dl/xj0pve
Date: Aug 13th 2019. Source: MX. -->
https://dosya.co/dpm1tyyojqxu/HCT4_PX5_9.0_Ota(20190813).7z.html
Custom
No custom firmwares have been released yet
Installation:
When upgrading from already Android 9:
Just copy the update.zip extracted from the downloaded OTA firmware downloaded into a root folder of a USB storage.
Upgrade system from Recovery or just update for the specific menu in settings
When upgrading from Android 6 or Android 8 (instructions taken from Hal9K thread)
a) If you have a sdcard slot:
Download Hal9k_Mod_3.x_upgrade_to_Android_9.0.rar
Uncompress it on PC
insert a recently FAT32 formatted micro SDcard into PC (by means of USB adaptor) --> It is recommended 8Gb or lower capacity for this purpose (max working 16Gb)
execute the SD_Firmware_Tool.exe file
Select the Drive which the sdcard is detected by your PC as target
Check that only the option "Update Firmware" is marked
on Firmware select the provided file: bootcard.img on Parent folder
Press "Create"
Wait for the bootable SDcard is created
Go to the Sdcard and replace the file sdupdate.img with the one provided on Parent Folder
in the HeadUnit:
insert micro sdcard on the slot marked as GPS/sdcard
reboot Unit -> Settings > Factory Settings: Password--> hctreboot
the recovery will be automatically upgraded and loaded into display
Use the USB with the upate.zip file in root folder and plug into the USB port
select on recovery: Upgrade system > From USB storage
The Android 9 image will be loaded into the headunit.
You can follow this video as well : https://www.youtube.com/watch?reload=9&v=EhEdeD5RICk
b) if you dont have a sdcard slot or previous metod does not work for you as your sdcard slot is just an USB extension
b1) By means of ModInstaller apk made by Hal9k
This is the easiest way for those who don't have sdcard slot.
Instructions here --> http://hal9k.ru/?page_id=207
b2) By means of OTG Cable
This procedure requires some kind of soldering knowledge and Android knowledge.
You must need a OTG USB cable (build your own) as per the following post:
https://forum.xda-developers.com/an...px3-5-headunit-mod-recover-flash-som-t3766892
Download Hal9k_Mod_3.x_upgrade_to_Android_9.0.rar and look for sdupdate.img file
Download BatchTool_1.7 or AndroidTool 2.39 from this post and download Drivers from this URL
Install the corresponding Drivers (select x86 or x64 depedning on your Windows version)
Open your Headunit and extract the PX5 SOM from the Motherboard
Connect the OTG USB cable into the PX5 SOM as per the previous thread and to the PC
Execute BatchTool.exe or AndroidTool.exe. In AndroidTool go to the Firmware Updte tab
The app will inform you that a USB is detected .
Load the sdupdate.img file on Firmware (FW) option
Press Upgrade button
When Upgraded...plug again the SOM into the Headunit...
Start unit and ente into recovery...you will find a 9.x.x recovery version
Proceed with the system upgrade as previous section from a USB storage
Note: if the app does not detect any device, check the drivers are installed
If the device is detected as mass storage, press oer the switch button to change the mode to a loader (the mode for the device to receive a flash file)
Reserved
Issues and Bugs
features:
Split screen --> Only on MX ROM
Issues found:
The clock is not updated when waking up from sleep --> Corrected from May updates
Not compatible Apps
Car Launcher Pro --> When trying to add a shortcut of an app, the list of selectable apps is blank
Useful Apps
Useful Apps for PX5 Android 9
MTCDialer 1.2.3 --> New Version for this app supporting for Android 9. Thanks @f1x & @scorillo_ro
https://github.com/scorillo/MtcDialer/releases/download/1.2.3/com.f1x.mtcdialer-1.2.3.apk
This app allows to Use Google Voice Assistant to Dial to your Contacts stored in your HeadUnit
To make a call just say a name of the contact stored in your PhoneBook, e.g. "Mom" or "Britney Spears" (if you have one ) or say some digits, e.g. "One One One Seven Six Five Four Two Zero"
No Internet Connection is required.
Reserved (6)
Great, but you should maybe change “ the information about Android 8 (Pie) over the Android units that features” to Android 9 (Pie)!
Done...the risk of the copy/paste
Enviado desde mi SM-G950F mediante Tapatalk
Hi everyone
I also switched to Android 9,
problems: clock not running from autosleep and missing TTS voice, I installed google speech synthesizer but it doesn't feel good.
does anyone have solutions?
Hi,
This update work for PX5 - MTCE_HXD?
Does it add the "Split Screen" feature that is missing from my head Unit?
Can someone tell me how to add this feature?
I have Android 9 but my builder has not enabled this option.
Thanks for your answer....
zimass said:
Hi,
This update work for PX5 - MTCE_HXD?
Does it add the "Split Screen" feature that is missing from my head Unit?
Can someone tell me how to add this feature?
I have Android 9 but my builder has not enabled this option.
Thanks for your answer....
Click to expand...
Click to collapse
sure you can as you have a MTCE unit
I have not tried the split screen, but i will
ikerg said:
sure you can as you have a MTCE unit
I have not tried the split screen, but i will
Click to expand...
Click to collapse
ok thank you, so I'll wait before updating.
I contacted the manufacturer who tells me that Android 9 does not support Spilt Screen on this head unit.
It's curious because Android 8 integrates this feature well
So I've the Android 9 May update on my Dasaita HU. It's really stable and the clock shows the correct time now. The only thing missing is the split screen but i guess it's s well known and discussed issue.
My question now is, I've seen a few videos and pics of Android 9 with white and dark interface (depending on the time of day), i can't see any setting in Dasaita PX5 HU to get this. Is there any compatable Android 9 Rom i can download to get this UI?
Sent from my SM-N950F using Tapatalk
That's possible to downgrade an PX5 MTCD Android 9 to Android 8 with Split screen option ?
naira1 said:
So I've the Android 9 May update on my Dasaita HU. It's really stable and the clock shows the correct time now. The only thing missing is the split screen but i guess it's s well known and discussed issue.
My question now is, I've seen a few videos and pics of Android 9 with white and dark interface (depending on the time of day), i can't see any setting in Dasaita PX5 HU to get this. Is there any compatable Android 9 Rom i can download to get this UI?
Sent from my SM-N950F using Tapatalk
Click to expand...
Click to collapse
That rom was the first one distributed by hct (I think) which published the own hal9k.
The rest of roms are based on different manufacturers. I dont know if the mx version is similar to the hct one or we need wait for new release of that specific version.
EDIT:
According to this video, the Last MX version has the ui you want and split is working as well
https://youtu.be/iht_nFyXo1I
Download it from second post
Remember that any rom for mtcd unit px5 is compatible to your unit...not only dasaita ones
Enviado desde mi SM-G950F mediante Tapatalk
zimass said:
That's possible to downgrade an PX5 MTCD Android 9 to Android 8 with Split screen option ?
Click to expand...
Click to collapse
It is possible
Enviado desde mi SM-G950F mediante Tapatalk
sorry but I'm a newbie with this type of update.
My head unit doesn't have SD card support.
But I have 2 USB ports.
When I put the update file at the root of the USB key the specific menu does not start the update.
How to update from the Recovery mode?
ps : the MX update link is broken ... Someone would know where to find the file?
---------- Post added at 05:04 PM ---------- Previous post was at 04:20 PM ----------
ikerg said:
It is possible
Enviado desde mi SM-G950F mediante Tapatalk
Click to expand...
Click to collapse
How to do ?
zimass said:
sorry but I'm a newbie with this type of update.
My head unit doesn't have SD card support.
But I have 2 USB ports.
When I put the update file at the root of the USB key the specific menu does not start the update.
How to update from the Recovery mode?
ps : the MX update link is broken ... Someone would know where to find the file?
---------- Post added at 05:04 PM ---------- Previous post was at 04:20 PM ----------
How to do ?
Click to expand...
Click to collapse
Read the post #2: SDCARD or OTG Cable that you must make by your own.
ikerg said:
Read the post #2: SDCARD or OTG Cable that you must make by your own.
Click to expand...
Click to collapse
By recovery mode
Update by USB it's not possible?
MX-link is broken. I would appreciate if you could create a new link.
Thanks
Hi everyone
I buy new Smart TV and I was happy befor I find out that the Installed OS have no google play service and nether GApps.
This TV manufactured by some 3th party company but they sell it as TCL 55C715 (hardware is different from original one)
could anyone help me find a compatible firmware that have google play service or help how enable google play on this OS.
a similar but different brand is the one talk about it here
I neeed BIG Help for Wisdom Customize Android 9 tv OS go back AOSP Android tv OS
I neeed BIG Help for Wisdom Customize Android 9 tv OS go back AOSP Android tv OS China 55" 4K Led TV I want AOSP Android TV OS Software My tv : -No Android Settings, -No Android Tv Launcher and no many AOSP apps Product Details 1. Market...
forum.xda-developers.com
All info about my TV:
I'm guessing you've bought this tv from Iran, right?
I got Daewoo DSL-55K5700U, and I'm in the same situation. managed to install google apps. Go to apkmirror (Android TV) and download what you need, just a little heads up, I assume your TV's CPU Architecture is armeabi-v7a, so download the correct versions of apps for your TV…
Hope it would be useful…
https://www.digikala.com/product/dk...ی-دی-هوشمند-دوو-مدل-dsl-55k5700u-سایز-55-اینچ
jabi_james said:
I'm guessing you've bought this tv from Iran, right?
I got Daewoo DSL-55K5700U, and I'm in the same situation. managed to install google apps. Go to apkmirror (Android TV) and download what you need, just a little heads up, I assume your TV's CPU Architecture is armeabi-v7a, so download the correct versions of apps for your TV…
Hope it would be useful…
View attachment 5729475
https://www.digikala.com/product/dkp-4228697/تلویزیون-ال-ای-دی-هوشمند-دوو-مدل-dsl-55k5700u-سایز-55-اینچ
Click to expand...
Click to collapse
i have this tv too,
can i install different rom (for example : android tv) on my device?
because i tierd for ****y ui and limitations
Hi Everyone,
I hope you are fine, I have 2 Smart TV´s TCL 43A423, Accidentally, In one of them, It was set with resttricted mode and the code was forgotten, It cannot be remembered, While trying to insert the code 1234, it gives a very very short of time trying to enter it in order to unlock it and its been a hard time
I was wondering and there should be a way to reinstall locally the adnoird Tv software, thoguh a USB drive, Any response will be much appreciated or please route me to the correct threat in case this is not the one
Kind regards
Try code 0423.
I beleive (not sure) is RT41 platform and thread is here:
Flash/update files for TCL ES560/S6500/S5300
This is a list of update packages and installation images for TCL ES560/S6500/S5300, chassis RT41. If you're unsure whether your TCL TV is chassis RT41 or not, you may check it in Settings > About > Contact us menu. If your Software version...
forum.xda-developers.com
stasiof said:
Try code 0423.
I beleive (not sure) is RT41 platform and thread is here:
Flash/update files for TCL ES560/S6500/S5300
This is a list of update packages and installation images for TCL ES560/S6500/S5300, chassis RT41. If you're unsure whether your TCL TV is chassis RT41 or not, you may check it in Settings > About > Contact us menu. If your Software version...
forum.xda-developers.com
Click to expand...
Click to collapse
Hi,
Thank you for your response, my TV is not a 41 chasis, based on the code, however, I researched according a instruction manual and states the same code 0423 but for parental control, do you think, will work to unlock restricted profile since this is different from parental control?? The chasis I got is V8-R851T02-LF1V634. 018640, Also I have tested by cresting a restricted profile and entered the code and it didnt worked
-- The default password is 1234. You can change it to a
new one.
-- The super password is 0423. If you forget your code,
enter the super password to override any existing
codes.
You have R851T02 platform.
I suggest you to reflash firmware with IMG file.
Thread for your TV is here:
TCL Android TV model 55p8m / Android Recovery TCL/BeyondTV/BeyondTV
My TCL Android TV model 55p8m has stuck and can't press any key in remote. The screen gives options to - Try Again - Factory data reset, but do not know how to select one of this option and continue without a keyboard or remote connected to the...
forum.xda-developers.com