Develop Bugs

MTCD - Verified Cross compatible MCUs

This thread is to document MCUs found to be cross-compatible between MTCD units, which includes PX3 and PX5 variants, which share identical mainboard hardware and MCU Chip STM32F091.
The following MTCD & MTCE (as of v2.56) MCUs have been validated as cross compatible on 1024x600 units:
- MLT - 01/07/17 - caution - has resulted in issues for some @leonkernan
- JY
- KBT - 08/12/2017 - thanks @abagos
- KD (v2.40_2 - enables bluetooth hands free in both front speakers)
- KGL
- KSP thanks @Overmann
- GS - Note "version unmatch" error and fix below No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80 - March 2018
- GS compatible on MX (see post #513)
- HA (v2.56 06/07/17 - note v2.52 on enables "shutdown delay when acc off" menu) HA MTCE (30/09/17) V2.65 https://www.sendspace.com/pro/dl/ufie8k
See this thread for pics where MCU HA and KD has been applied on JY. https://forum.xda-developers.com/showpost.php?p=72737797&postcount=640
I initially upgraded to KD 2.40, then HA v2.52 after first exporting the MCU settings.
Note that I had to reapply MCU settings in [factory sertings] to configure radio, LED, bluetooth, hardware keys, volume levels between radio, bluetooth, system etc.
MCUs were previously thought to be manufacturer specific - e.g. HA, JY, GS, KD, however I have found that they are compatible and of interest where there is either a specific issue with your MCU (e.g. bluetooth out of one speaker, to enable PX5 sleep mode control) or the vendor has long ceased to support & release updates - such as JY.
MCU cross-compatibility became of interest to me when I upgraded my JY [MCU v2.06_2] PX3 with a HCT PX5 SOM and wanted to enable the MCU specific menu item [shutdown delay when ACC off] to control sleep as found on HA/Dasaita.
I first noted that from an XDA post listing JY an KD v2.06_2 being identical and on that assumption, upgraded to KDv2.40_2, which successfully applied - but had to reconfigure factory settings.
Following on, I found a post which has an image of a GS board & MCU chip - noted it was identical to the MTCD JY MCU chip [STM32F091] - then came across a post where a user had inadvertently applied a MTCD GS MCU to a MTCD JY without bricking it.
I then started comparing same version number firmware files from various manufacturer MCUs with a text compare tool. From this work, I had enough info to compare the latest HA v2.52 and conclude it 'should' be compatible. Indeed it is.
As always, check first (suggest confirming MTCD, MCU Chip part number, view/compare the fw files, ensure you have original MCU FW, backup MCU settings or document the settings to ensure your hardware controls, volume control, bluetooth, radio, canbus etc are setup correctly). Apply at your own risk.
Please post your results and I will update this thread.
Updates:
UPDATE: 26/06/2017 Users of 800x480 Users must also apply file[dmcu.ext], a text file containing:
For PX3 --> screen:3
For PX5 --> screen:1
01/07/17 - MLT
06/07/17 - KGL confirmed and new HA v2.56
30/09/17 - MTCE MCU confimed compatible
08/03/18 - MTCE JY/GS/HA compatible - No issue experienced on MTCE going from JY 2.80 to GS 2.78 and back to HA 2.80
GS Specific Notes:
Oberbergler said:
For all those with a GS: Our unit is compatible with the MTCE MCU but you have to restore your settings and maybe to manually reconfigure your touchscreen and buttons. There is a simple function to do this in the factory settings (126) which is called key study. My touchscreen was also swapped by the x axis. I had to go with the swapped touchscreen into the settings, configure it, reboot the unit and everything was fine. For the buttons you have also the possibility to use short press and long press buttons, which is great because our units (at least mine) has only five buttons and no return button. So I use now the power off button as return in short press mode and power off in long press
Click to expand...
Click to collapse
Version unmatch see this post where user resolved by reapplying MCU AND Software APK Fix Here
- Attached Version Unmatch APK fix to this post, thanks @Wadzio
GS Configuration Settings file:
Bose321 said:
Here it is: https://gerbenbol.com/android/dmcu.cfg.
Click to expand...
Click to collapse
Do not dilute this thread by posting "how-to" questions such as - how do I update the MCU, what unit do I have, can I do it, how do I find factory settings, etc. This thread is to document cross-compatible MCUs and the fixes they apply.

Hi! Confirmed, I've upgraded to PX5 (JY UL135). Flashed KD2.40 over JY 2.06_2 then flashed HA 2.52 and everything is working as it should be. Thanks for your work.

I can confirm a cross compatibility as well.
My Unit is a xtrons device with die MCU firmware GS 2.43 and yesterday i did flash the HA 2.52. But be sure to save your mcu config first. Otherwise the hardware buttons won't do what they were supposed to do. But after flashing the firmware and restoring the config, everything is back to normal.

To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.

Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.

f1x said:
Some time ago I tried to investigate what actually those abbrevations mean. In my understanding GS, JY, HA is related to the canbus profiles, not directly to the reseller. It seems to be reasonable because MCU has really tiny flash capacity and add all canbus configurations to one chip would be impossible.
Click to expand...
Click to collapse
No, you are wrong there - the letters very definitely relate to the manufacturer, NOT the CAN Bus profiles KLD = "Klyde" KGL, = "Kai Ge Le", JY = "Joyous" etc, this has been established for years.
The seller has NOTHING to do with the software at all.
The CAN Bus profiles are named in factory settings
On MTCB/C headunits there was a slight difference in the code between MCU types so they were not interchangeable (apart from BN and HA), it would seem that on MTCD units there is no such variation in the code.

Does this also apply to LM_ (Erisin) MCUs?
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv

SpeedyCarv said:
I have a Erisin 5048 HU with MCU 2.41_1. Does anyone have any experience in flashing a different MCU to a LM_ type MCU? I´m worried to brick my HU if a flash a higher HA_ version.
Any info would be highly appreciated.
Greetings
Speedycarv
Click to expand...
Click to collapse
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.

typos1 said:
There are no "Erisin" MCUs - Erisin are a seller only, they sell units made by several manufacturers. You have an "LM" unit.
I would stick to what @marchnz has tested already, although having said that, on the MTCB/C units if you flash the wrong MCU you can simply flash the correct MCU to correct it, cant say if its the same for MTCD units, up to you if you want to risk it.
Click to expand...
Click to collapse
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..

SpeedyCarv said:
My level of knowledge has not grown in any way after reading your post.
Thank you anyway..
Click to expand...
Click to collapse
Maybe read it again ?
Basically, you could risk trying it - MTCB/C units can be restored if the wrong MCU is flashed, maybe MTCD units could be restored if the wrong MCU is flashed also ? But maybe not, so that is your decision whether to try or not.
Otherwise stick to what @marchnz has said and do not try it.
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Cant make it any clearer than that.

typos1 said:
Maybe read it again ?
And your unit is NOT an "Erisin" unit, they are sellers and sell units from many manufacturers, you have an LM MTCD unit.
Click to expand...
Click to collapse
Not necessary to read again. I already knew that. That's what i tried to express in typing "my level of knowledge has not grown" Sorry if i write misunderstandable, i'm not a native speaker (German).
Thank you again for your time and patience

typos1 said:
To make it easier to re-apply the settings, you can use the mcu.cfg function and flash it with the MCU, just in case anyone didnt know.
Click to expand...
Click to collapse
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?

Wout2426 said:
Can you explain me how ? Do I put the mcu.cfg file with the new mcu in the root of gps SD ?
In factory settings I see only the option to export, not to import. Or did I miss something ?
Click to expand...
Click to collapse
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.

typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
Or, once mcu has been upgraded, you can remove the mcu update (.img) from the root of the gps card and apply the config (.cfg) on the root of the gps card separately - by running the 'upgrade MCU', it will see .cfg file and apply it.

Update for 800x480 users who update to the latest MCU - you must also apply a dmcu.ext
DMCU.EXT details
DMCU.EXT & screen resolution setting/howto/details
dmcu.ext details for PX5 800x480
That said - why is anyone purchasing a PX5 unit with 800x480?!?!

KD --> HA for 800x480 Screen
I have had quite an experience over the weekend, but am able to report successfully updating a PX3 MTCD_KD unit to a PX5 with the HA2.52 MCU Code.
For those of us with 800x480 screen sizes, as now noted in the main thread, we need to create the dmcu.ext file with the appropriate screen size to be flashed with the dmcu.img file.
Just a note that if you run across the issue of not having the appropriate resolution; don't freak out.
One interesting note I hadn't mentioned before is that after the PX5 started thinking it was 1024, I replaced it with the PX3. The PX3 booted thinking it was 1024 also. After reverting the PX3 to 800 (flashing with screen:3), I replaced the PX5. The PX5 however, did not revert back to 800, but remained at 1024. The PX5 did not revert back to 800 until after I reflashed the MCU, specifically stating it was to be 800 (screen:1).

So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.

typos1 said:
Thats correct, just put the mcu.cfg file on the SD card with the mcu.img.
Click to expand...
Click to collapse
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.

Bose321 said:
I assume you mean "dmcu.img" and "dmcu.cfg"? That's how my downloaded img and backup cfg are called.
Click to expand...
Click to collapse
Yeah, thats right - the "d" is just there to show its an MTCD MCU not an MTCB or MTCC one.

1-2-Hak said:
So I tried HA 2.52 on Xtrons TB706APL
I get the following error on reboot.
After I update from dmcu.cfg it goes away but if you go into factory settings and change anything it comes back.
I also didnt see the option for the shutdown that this mcu is supposed to have.
Click to expand...
Click to collapse
The shutdown option is under System Settings --> extra settings. You wont find it in the factory settings. Just FYI.
Which dmcu.cfg did you use? I might be wrong, but it seems to me it might be dangerous to use different dmcu.cfg files with different versions of the MCU Code.

Rooting and installing Lineage OS on AGM X1

Update: The instructions below are for the AGM X1 eu version, for the AGM X1 International version follow this thread, it's a work in progress and not available yet.
As you might be aware the AGM X1 is a fantastic rugged android, aside from the great hardware, the source code of the phone is available to devs. The combination of excellent ruggedness, hardware and open source makes the AGM X1 "the best choice in phones" at the moment for me period.
Unfortunately the information on how to root and install the available Lineage OS port is not very clear
I spent a few hours trying to find the best place to start and it's quite difficult to find
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
This page contains a post below the main top section of the page.
https://w3bsit3-dns.com/forum/index.php?showtopic=814951
Here's the start of the important stuff with some additional information that I added
"The jist of the thread
TWRP 3.1.0 for AGM X1
---------------------
AGM-X1-flash-TWRP-root.zip ( 21,66 ?? )
https://w3bsit3-dns.com/forum/dl/post/10034644/AGM-X1-flash-TWRP-root.zip
OR
Download TWRP + ROOT from Google
https://drive.google.com/open?id=0B871Z4mt2B7Qb0RLMVlSemR4Szg
sha256sum
AGM-X1-flash-TWRP-root.zip b34b19f6666f0456f68e3a452c97aacf2fd3f1b06819ef7a633d95259d22a25f
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d
Now here comes the difficult part, trying to decipher the following text
Text from thread (bad english)
Installation takes place in a similar way as inthis post, Except that you need to choose the same name! The fifth! The item and the installation of the root rights occurs automatically when you exit TWRP.
Can anyone help me with this, I cannot decipher the above paragraph. Also note that this forum is broken and not working correctly as a site (many issues including: no registration available and also the important link in the paragraph above does not work)https://forum-lw-1.xda-cdn.com/images/smilies/rolleyes.gif
P.s not interested in king root method (too many mentions of malware), will use twrp.
Update: (thanks to Skill3r)
clearer guide - also note that this zip contains twrp 3.0 instead of 3.1 due to backups not working with 3.1 (important)
https://forum.xda-developers.com/an...m-snapdragon-617-4gb-64-t3533020/post71877054
The steps :
First You need to download this package and extract it : http://www53.zippyshare.com/v/3sgYq5cu/file.html
sha256sum
AGM-X1-flash-TWRP - Skill3r MOD.rar a0e755dc513b716e5a5369481f0761a4c6a9ec60401bd9c0c060579da87f3668
Contents with sha256 hash
adb.exe f05ff055b2ce9213d0b349da7ef713664d66a13134be76820cd072cd1e44211a same as twrp 3.1 version
AdbWinApi.dll 14a51482aa003db79a400f4b15c158397fe6d57ee6606b3d633fa431a7bfdf4b same as twrp 3.1 version
AdbWinUsbApi.dll 041c6859bb4fc78d3a903dd901298cd1ecfb75b6be0646b74954cd722280a407 same as twrp 3.1 version
fastboot.exe 632f4f2039b76082f2c090f6aec43893e93e8b32d0aae6b7cfa03f9b71d5d897 same as twrp 3.1 version
One-key-flash-twrp.bat f3e5a611166e970cb41a0040979da305b9d91abc44537cab9af94110381fbf54 different from 3.1 version
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae different from 3.1 version
SR3-SuperSU-v2.79-SR3-20170114223742.zip e147970ca377a184a177092f4c4a8022420cc30785fdaf95e16703da8312426d same as twrp 3.1 version
1) Enable the developper settings
Go to Settings>About phone and hit "kernel version" 7 times to unlock
2) Enable the OEM bootloader unlock
Find in settings>dev options
3) Enable the USB debugging
Also in settings>dev options
4) Plug an usb cable and when the windows ask for the RSA identity of the computer, allow it and check to always allow the computer.
5) Shutdown your phone
6) Press VOL down + power and after long press the power button
7) Now in recovery mode, go to reboot to bootloader, a green message is shown with fastboot.
8) Now launch the One-key-flash-twrp.bat in package and plug your phone
9) Press any key and follow the instructions in the script.
10) TWRP should launch, you need to swipe to allow modifications in system
11) Press a key in the script, TWRP should reload, TWRP is now installed in the phone, you need to allow modifications in system again.
12) To root the phone, you just need to exit TWRP, he gonna ask to root the phone, you just need to swipe to root the phone.
Now you have TWRP installed and the phone is rooted.
If something goes wrong and bootloop the phone, please just follow the AGM instructions with the original package and the procedure to reflash the rom (on the external SD card and with VOL UP + VOL Down + Power)

I've made progress, but I'm stuck on finding a suitable driver for the adb interface on windows XP for the AGM X1.
For drivers I've tried
NOT WORKING! Google USB drivers
https://developer.android.com/studio/run/win-usb.html
sha256sum
latest_usb_driver_windows.zip 1ee1d023a99ffac962af4454eb9b9900f6858c687b4d5311e8fb361548d6c078
NOT WORKING!
https://forum.hovatek.com/thread-16965.html
which should bring you here
https://drive.google.com/file/d/0B4S-Z726VJ2SLW9zNXdqWDBQQkE/view
sha256sum
a3312727a77c3ab89e0d7463cd252cffec554a182f78195f6908f62132c5c174
The important file in the zip archive is
SHA-256 08e5e7e5f30801b363f08a6106425faa1c505bd048a18c846a5b3e5959a4998e
Called
Setup.exe
Qualcomm_USB_Driver_V1.0.exe
among others.......
MD5
906c4effd6a20be22ea026a43a3cb7b3
SHA-1
89df6ca0d893d9355741d8ca11cdebea1fbbb095
NOT WORKING!
Univeral drivers
https://github.com/koush/UniversalAdbDriver
https://adb.clockworkmod.com/
sha256sum
UniversalAdbDriverSetup.msi 4e77e303bba6cf84588bdb6da91f7a875d406f7930cbe9f4d2aae0b643c0c928
NOTE: Problem installing: universal adb driver, there was a problem with this windows installer
Does any one have any advise please. Obviously I've checked the Manufacturers site they have not provided a driver. The chipset is Qualcomm MSM8952.
Thanks in advance.

Hello, for the drivers, simply plug the phone on USB and select CD in options (where you can check 'simply reload' mtp etc ...)
On the computer you can install the drivers now

Hi Skill3r,
Recommended (MAYBE THE DRIVERS WORK ON OTHER VERSIONS OF WINDOWS, BUT LINUX IS SO MUCH EASIER/BETTER)
I gave up on Windows XP. Now I'm using Xubuntu 16.04 LTS and EVERYTHING IS CONNECTING TO THE COMPUTER with this guide (without going to qtadb installation)
http://bernaerts.dyndns.org/linux/74-ubuntu/354-ubuntu-xenial-android-adb-fastboot-qtadb
p.s the vendor ID is "Qualcomm, Inc": with the code: 05c6 (it's in that github download in the link above, no need to add it specially just follow the guide)
The phone is recognized no special drivers required IT ALL THERE ALREADY! I took the commands from the bat file, changed (take away .exe e.g fastboot.exe to fastboot)
So the problem I'm getting now just after loading twrp with this command
fastboot boot recovery_AGM-X1_es_by_MD5dev.img
And this problem is............
That the touchscreen is unresponsive and I'm unable to check the box and swipe to allow TWRP to modify the system.
I have the AGM X1 International edition.

For me also:
Wenn I´m in the TWRP menu, i´m nt able to click on a button or swipe the last button, because the Touchscreen doesn´t work.
How can I solve this problem, install twrp and root the phone? because i would install LINAGEOS...or what is the best Rom/Custom Rom for the agm x1?
Please help me.
thanks

Both twrp image files below (twrp 3 and 3.1) have the touchscreen problem
sha256
AGM-X1-TWRP-3.1.0.img 22b7d529511b0b191c09e850c14b0d4ed6e32cdddc6defd688bcd78d40be2528
recovery_AMG-X1_es_by_MDSdev.img 3eb8df185afaacaae4a754ba3c18e5e86ea140f0b115ab73d28fe2ba64088fae
motsch_, what version of AGM X1 do you have, international?
Have you found any references to this problem in the main discussion pages.
We need to look for any references to this problem, or special img's for this version of phone.
Here's the older xda thread on the agm x1
https://forum.xda-developers.com/ge...ualcomm-snapdragon-617-4gb-64-t3533005/page12

Hi,
how can I see which version does i have?
For the moment i havent found any solution for installing twrp.
I have rooted the phone with Kingroot.
Doesnt exist a solution for us?

We can go to "settings" > "about phone" > scroll to bottom and let me know the
hardware version
software version
kernel version
I know mine is X1 international not EU as I just bought it and the EU version is discontinued, it has the following
hardware version: V1.00
software version: L1253.6.03.01.BYD
kernel version: 3.10.73
Also is there any awesome developers out there that would be interested in making a TWRP version - forked from the original TWRP and put on github.
And maybe then make your own port of Lineage, again with all changes to original Lineage forked on github.
Open Source and transparency of course is the reason for this.
Any one else with a AGM X1, please chime in because if we can get just a few dollars together we can get this done very quickly.
I pledge $25 for round one

Here's a reference to the touchscreen issue
https://translate.google.com/transl.../index.php?showtopic=814951&st=460&edit-text=
08/01/17, 18:45
"Am11go,
I downloaded AGM X1 TWRP Supersu from the caps, it helped, booted TWRP, but the screen did not react at all, like all buttons except on / off, it extinguishes the screen and does not include anymore ... Apparently the hands are crooked, although with bv5000 It was. How to determine which TWRP, under which version?"

if you can find a solution, can you let me please know that?

Found on 4PDA :
Demanda Sam, dit - il. TWRP assemblé avec le noyau et DTB de L1253.6.02.01.BYD. Maintenant , l'écran tactile fonctionne très bien.
hxxps://4pda.ru/forum/dl/post/10490628/twrp_3.0_L1253.6.02.01.BYD.zip
hxxps://4pda.ru/forum/dl/post/10490629/twrp_3.1_L1253.6.02.01.BYD.zip

AGM X1
HARDWARE & VERSIONS
International version
screen: Edo rm67191 fhd Amoled non-oleofobic non-sunlight readable
HW: Qualcomm MSM8952 hs8952qc
Hw other: RAM 4 Gb LPDDR3 933 mhz
fingerprint reader – FPC1020
notification led – aw2013
camera – Omnivision OV13850 13MP ??
SW: Android 5.1.1 LMY47V
L1253.6.02.01.BYD
EU version
screen: Samsung s6e3fa3 fhd super amoled oleofobic?? non-sunlight readable??
HW: Qualcomm MSM8952 hs8952qc
SW: Android 5.1.1 LMY47V
L1253.6.02.01.EU
Gold version
screen: like international?
HW: same?
SW: like international?
reference discussions: https://4pda.ru/forum/index.php?showtopic=793964
https://forum.xda-developers.com/ge...gm-x1-qualcomm-snapdragon-617-4gb-64-t3533005
https://www.movilesdualsim.com/foros/agm-x1-sd617.1152/
about screen: https://www.devicespecifications.com/en/editor-review/993738/3
http://gearopen.com/phones/agm-x1-review-rugged-smartphone-not-drown-but-froze-53924/
KERNEL SOURCE
https://github.com/zhaochengw/android_kernel_agm_agma3eu
KERNEL CONFIGS EU vs INTERNATIONAL MAIN DIFFERENCE
EU
CONFIG_TOUCHSCREEN_GT1XX=y
CONFIG_TOUCHSCREEN_GT1X_GESTURE=y
CONFIG_TOUCHSCREEN_GT1X_FH=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20 is not set
INTERNATIONAL
# CONFIG_TOUCHSCREEN_GT1XX is not set
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_I2C_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_RMI_DEV_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_TEST_REPORTING_V20=y
CONFIG_TOUCHSCREEN_SYNAPTICS_DSX_FW_UPDATE_V20=y
# CONFIG_TOUCHSCREEN_SYNAPTICS_GLOVE is not set
I compared the kernel configs from latest international lollipop rom with the one from Flyme OS 5 (compatible with x1 EU). I have not a boot.img from latest EU firmware, but should not matter.
This should explain the black screen when trying to install EU rom on International X1.
I found these options are not enabled in standard kernels, they may be of interest:
CONFIG_MSM_VPU CONFIG_POWER_AVS_MSM CONFIG_USB_MSM_ACA
reference: how extract kernel configs with extract-ikconfig (from kernel_dir/scripts)
https://github.com/MotorolaMobilityLLC/kernel-msm/issues/73
ROMS
EU: stock,lineage 13, flymeOs 5-6 https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: only stock (latest is L1253.6.03.02.BYD)
lineage 13 (removed) https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62399105
PORTING ROMS AND KERNELS
From EU to International:
take EU roms and replace boot.img with one from International roms? (kernel and dtb table??)
From other Phones:
- Similar MSM8952 Phones: https://www.gizmotimes.com/lists/phones-qualcomm-snapdragon-617-processor/19660
- Guides: https://forum.xda-developers.com/android/general/how-to-port-roms-easy-100-t2804390
https://forum.xda-developers.com/showthread.php?t=2707438
http://ohheyitslou.blogspot.it/2011/09/ohheyitslou-custom-android-kernel-guide.html
- Interesting Kernels: https://forum.xda-developers.com/moto-g4-plus/development/kernel-elementalx-g4-0-01-t3424836
On Snapdragon 617 at the moment should be possible Overclock, but I have found no Voltage control patches from other phones kernels.
TWRP
EU: https://4pda.ru/forum/index.php?showtopic=814951
INTERNATIONAL: https://4pda.ru/forum/index.php?showtopic=814951&st=300#entry62309514
TWRP 3.0 for android 5, TWRP 3.1.0 should be for android 6 and it may have problems with restoring
TWRP reference info https://www.movilesdualsim.com/tema/twrp-by-mdsdev-para-el-x1.168070/

Hi liamotoub,
Thanks for the information. So Lineage OS is not available on the international version of the AGM X1 yet. I see.
Also Thank you skill3r for the links, I see they are 404 now unfortunately.
liamotoub, you seem to know what you're doing? would you consider taking on this as a project.
It's certainly worth keeping an eye on 4PDA, pitty I cannot read russian. If any members of 4PDA in the loop regarding the AGM X1 international are reading this please chime in. Thank you all

Hello, unfortunately I'm not a programmer, I just do "trial and error".
404 is a 4pda.ru error for not registered users, follow this guide to register
hxxps://doorsgeek.blogspot.it/2015/08/4pdaru-loginregister-captcha-tutorial.html
To read just use google translate
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D793964%26st%3D1300&sandbox=1
PS. another phone with a lot of ROMs (android 5 6 7) and similar hardware of X1 (msm8952) is ZTE Nubia Z11 mini
hxxps://translate.google.com/translate?hl=it&sl=ru&tl=en&u=https%3A%2F%2F4pda.ru%2Fforum%2Findex.php%3Fshowtopic%3D803370&sandbox=1

and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1

motsch_ said:
and what can i do with the "twrp_3.0_L1253.6.02.01.BYD.img" from the download from 4pda?
I would install twrp on my x1
Click to expand...
Click to collapse
With TWRP you can flash another image (lineage OS for example, when we find or make a suitable version for the international version AGM X1)
TWRP will also give you the option to get root permissions, so you can use certain apps that require it. It's like the difference between user and administrator account in windows. It's called rooting because Android is based on Linux, the root account is the account with "super user" privileges, your phone will be open to allow more areas of the system to be used/wrote to/read. It allows your phone it's full potential.
With TWRP we can also do backups and restores of the entire existing ROM and phone contents
So TWRP is the first step before we get the ROM (lineage OS) on the phone https://forum-lw-1.xda-cdn.com/images/smilies/cowboy.gif
Another option for rooting is available called King Root however this comes with a lot of MALWARE AND ADWARE and it is advised not to use it. Besides it doesn't have all the flashing, backup and restore tools anyway. It just gets you root.
That is why we really need to find a working copy of TWRP for the AGM X1

INSTRUCTION TO COMPILE KERNEL (with android ndk on linux 64bit)
git clone hxxps://github.com/zhaochengw/android_kernel_agm_agma3eu
cd android_kernel_agm_agma3eu
export ARCH=arm64
export SUBARCH=arm64
export CROSS_COMPILE=/opt/android-ndk/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/bin/aarch64-linux-android-
[adapt commandline to your installation or use the one in the kernel sources (toolchains/aarch64-linux-android-4.9/bin)]
make xconfig
[load your agm X1 config file, EU version is in arch/arm64/configs/agma3eu_defconfig,and make your changes]
make -jX
[where X is number of your cpu cores]
bootimg/dtbTool -o dt.img -s 2048 -p ./scripts/dtc/ ./arch/arm/boot/dts
bootimg/mkbootimg --ramdisk bootimg/ramdisk_agma3eu.img --ramdisk_offset 0x01000000 --base 0x80000000 --tags_offset 0x00000100 --pagesize 2048 --kernel arch/arm64/boot/Image.gz --cmdline "console=ttyHSL0,115200,n8 androidboot.console=ttyHSL0 androidboot.hardware=qcom msm_rtb.filter=0x237 ehci-hcd.park=3 androidboot.bootdevice=7824900.sdhci lpm_levels.sleep_disabled=1 earlyprintk" --dt dt.img --output boot.img
Image.gz ramdisk_agma3eu.img dt.img will be incapsulated in boot.img.
Test if kernel works:
#adb push boot.img boot
If not boot restore previous boot image.
notes:
1.if you load the international kernel config, and you got some errors related to VENDOR, enable
CONFIG_MACH_HIS_SMARTPHONE CONFIG_HIS_BOOT_INFO
and fill CONFIG_HIS_VENDOR_NAME: Android CONFIG_HIS_PRODUCT_NAME:agma3eu
2.if you got an error related to msm_dba_internal.h not found, edit
drivers/video/msm/msm_dba/msm_dba.c and replace #include <msm_dba_internal.h> with #include "msm_dba_internal.h"
PS. replacing my boot.img is not sufficient to make Lineage 13 and FlymeOS5 work, they go in bootloop.

I've uploaded the TWRP versions for the AGM X1 "International version" from the 4PDA links above, to save somebody the trouble of signing up. Version 3.1 is what you want I think (but maybe the backups/restores don't work on v3.1 as skill3r has pointed out or maybe the international version is different?)
SHA-256
72422060a34a995a6f29da1c0a6d5737f7df3ad426d0a7105267730f22e74b9c
File name twrp_3.0_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!0yZCyIaA!lUnmyeQNinQlzIcwfWZ8F5l6Pz2jlumxzhVx57U6G-M
SHA-256
96c92a52805c0db4fc84c652199887e93a30dae3fe3ead36e14715f7fc736d22
File name twrp_3.1_L1253.6.02.01.BYD.zip
Download: https://mega.nz/#!FmxmFKgK!cCfNsGj3gRMVkl_EI6ROI2-5RbFQsuyElFxRIvN76ug
Also, liamotoub, send me your PayPal address and I'll send a few dollars your way, that information is great thus far

These 2 files should be TWRP 3.0.3 and 3.1.0 right?
I want to point out that also the latest 3.1.1 ( relased for the gold X1 by a Spanish forum, movilesdualsim) works on international X1 mega:#!vB9g3Aab!_gyrr6rP_rJDheGgIseI2u2TglNw1vmv7dDjUnDYJb4 with not encrypted phone.
To try it without touching the recovery partition use:
#adb reboot bootloader
#fastboot boot recovery_name.img
EDIT: it give some problems when flashing new INTernational ROMs, because they think the phone is GOLD and refuse to install due to their updater-script; should be sufficient to modify the build.prop of this recovery or a similar file, with international version "signature".
TWRP 3.0.3 3.1.1, those that I tried, fail to recognize encrypted fylesistems, so backups of this kind will not work.
Another minor bug is the wrong date (1970) in automatic naming of backups folder, but that's common on most phones.
I managed to make FlymeOs 5.1 boot on international X1, but I don't recomend it, it's full of bloatwares and wifi and other things looks to be not working
https://mega.nz/#!djJ3jbbT!Kr6qMyTcggsrYyPeDnySHpp7EOgUZnG-tvTqewdqkmk
Make full working nandroid backup before trying it.
To port lineage 13 I think marshmallow kernel sources are needed, with present sources only lollipop roms could be ported AFAIK, like CM 12.1.
Question to X1 users: on stock rooted rom, do root requesting apps (afwall, kernel audiutor etc) start at boot time? On mine no, I have to start them manually.
On stock rom beware of these preinstalled apps, may be adware:
com.gangyun.beautysnap
com.oupeng.max.hisense

Is there any specific advantage using the TWRP movilesdualsim 3.1.1 version rather than the 4PDA versions other than a slightly higher version.
If I encrypt my phone would there be any other issues other than not being able to do twrp backups and restores? It would still work?

PX5 MTCD/E Head Unit Discussion Thread [Rockchip PX5 A53 | Android 8.0 | 2/4GB RAM]

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

PX5 MTCD/E Head Unit Discussion Thread [Rockchip PX5 A53 | Android 9.0 | 2/4GB RAM]

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

Everything U need 4 PX5 For MTCD/E "this thread is not for discussion"

Everything U need 4 PX5 For MTCD/E
"this thread is not for discussion"
android 10

link 4 image & mcu
------------------------------------------------
Yandex
Finds everything
disk.yandex.com

link 4 program chip unit with out device
------------------------------------------------------------------------------------------------
[PX3 & 5] [OTG] - No Headunit Mod, recover or flash a SOM with a simple USB cable
"Factory" Recovery for MTCx PX3, PX5 and PX6 SOM. Finally - OTG for all without modifying your head-unit. With only basic electronic/soldering skills, get OTG and fearlessly flash or recover a 'bricked' MTCD/E (HCT printed on SOM) Rockchip PX3...
forum.xda-developers.com

link 4 program device
-------------------------------------------------------------------
upgrade method to another android version for Rockchip unit (px6 px5 Px30 and other )
following the official Rockchip upgrade tool https://forum.xda-developers.com/android-auto/mtcd-software-development/mtcd-e-android-10-upgrade-using-t4123933 if you are upgrading from the same version ex android 9 to android 9 you don't need...
forum.xda-developers.com

link 4 root
-------------------------------------------------------------------
Root for Android 10 PX6 MTCE
I tested this on my Dasaita px6 mtce head unit once I installed Android 10 (thanks Diavol for the tip) I know that there are other ways to do this, but this is how I accomplished it. ****************DO THIS AT YOUR OWN...
forum.xda-developers.com

viper4android
---------------------------------------------------------
magisk 20.4
link 4 custom channel
Root for Android 10 PX6 MTCE
I tested this on my Dasaita px6 mtce head unit once I installed Android 10 (thanks Diavol for the tip) I know that there are other ways to do this, but this is how I accomplished it. ****************DO THIS AT YOUR OWN...
forum.xda-developers.com
---------------------------------------------------------
preset
GitHub - jadilson12/Viper4Android-presets: This repository finds a collection of preset for viper4android 2.7+
This repository finds a collection of preset for viper4android 2.7+ - GitHub - jadilson12/Viper4Android-presets: This repository finds a collection of preset for viper4android 2.7+
github.com

mtcdtools
-----------------------------------------------------
[Release][PX3|PX5] MtcdTools-Control music players, customize buttons, voice control
Hello, Today is time to release second application with more powerful features on-board. I would like to introduce MtcdTools. MtcdTools ReadMe HOWTO HOWTO by Geniee33 Source code Latest release...
forum.xda-developers.com

[MOD][MCU] BD375xx Sound Processor​-----------------------------------------------------------------------
[MOD][MCU] BD375xx Sound Processor
I spent some time and I prepared SoundPatch similar to 7floor modification. The difference is: It's no need any hardware modification, only patched MCU firmware and modified android Amplifier apk That's how it looks: Remember I am not...
forum.xda-developers.com
-----------------------------------------------------------------------
android 10
[MOD][MCU] BD375xx Sound Processor
I spent some time and I prepared SoundPatch similar to 7floor modification. The difference is: It's no need any hardware modification, only patched MCU firmware and modified android Amplifier apk That's how it looks: Remember I am not...
forum.xda-developers.com
*************************
4 root
[MOD][MCU] BD375xx Sound Processor
I spent some time and I prepared SoundPatch similar to 7floor modification. The difference is: It's no need any hardware modification, only patched MCU firmware and modified android Amplifier apk That's how it looks: Remember I am not...
forum.xda-developers.com

htc7 launcher
----------------------------------------------
HCT4_PX5_10.0_ota(2020/06/24) MX/WITSON
Android 10.0 version from MX/Witson for PX5 Head Units. Day/Night Theme is included! Enjoy :) Download: Fast --> Download build.prop: # begin common build properties # autogenerated by build/make/tools/buildinfo_common.sh...
forum.xda-developers.com

sadaghiani said:
Everything U need 4 PX5
android 10
Click to expand...
Click to collapse
For MTCD/E ... please update thread description, we don't want to be confusing other variant owners. Also suggest including a comment "this thread is not for discussion".
Also, I've asked mods to move to the general section.
You might want to include the links in my signature;
- schematic
- recovery and backup (SDCard and Factory OTG recovery when all else fails.)
Good thread.

schematic
-------------------------------------------------------------------
MTCD schematic
Found - MTCD Schematic. A most valuable find on russian android car audio forum and attached here. [Android Car Audio] The schematic corresponds to a GS Mainboard I have as a spare part. It varies to my JY board in terms of USB operation...
forum.xda-developers.com

recovery and backup (SDCard and Factory OTG recovery when all else fails.)
-----------------------------------------------------------------------------------
PX5 stuck in bootloop
This Post details how OTG/LOADER can be achieved to recover a corrupt PX5 or PX3 - any RockChip MTCx SOM Update 2/2018 - anyone can make a gig without modifying their main board. BUT FIRST try a USB port, some have OTG out of the box. From...
forum.xda-developers.com