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

Search This thread


Jan 11, 2014
Hello everyone, I'm having two strange issues when trying to update from Android 8 to 10 using Alex's OTG method.
I have updated the MCU (MTCE GS 3.44_3) and downloaded the latest version of RKDevTool and an HCT7 PX5 Android 10 IMG (20200612), as he recommended it directly (in the comments).

RKDevTool v2.74 recognizes my device and is able to start the process.
While performing the same steps as in Alex's video, it also does a "Reset Device" step (without problems). However, right after that comes the "Download Firmware" step which fails almost immediately (screenshot of RKDevTool). In Alex's video the "reset" step does not occur.

In the log file I get this error DownloadImage-->device did not support directLBA to write gpt
Full log here:
19:40:35 448 瑞芯微开发工具 v2.7.4.0 start run
19:42:48 773 RKDevTool v2.7.4.0 start run
19:43:13 075 Layer<1-3>:Test Device Start
19:43:13 086 Layer<1-3>:Test Device Success
19:43:18 094 <LAYER 1-3> ERROR:ReadCapability-->RKU_ReadCapability failed,err(-8)
19:43:18 103 Layer<1-3>:Check Chip Start
19:43:23 110 Error:RKU_Write-->WriteFile failed,bRet=0,err=995,size=31,write=0
19:43:25 126 INFO:RKU_ResetPipe-->DeviceIoControl OK
19:43:25 135 Layer<1-3>: Check Chip Success
19:43:25 145 Layer<1-3>:Get FlashInfo Start
19:43:25 152 <LAYER 1-3> INFO:FlashInfo: 00 00 A8 03 00 04 04 00 28 00 01
19:43:25 159 <LAYER 1-3> INFO:GetFlashInfo-->Emmc storage.
19:43:25 168 Layer<1-3>:Get FlashInfo Success
19:43:25 178 Layer<1-3>:prepare IDB Start
19:43:25 185 <LAYER 1-3> INFO:CS(1) (29952MB) (SAMSUNG)
19:43:25 200 Layer<1-3>:prepare IDB Success
19:43:25 210 Layer<1-3>: Download IDB Start
19:43:25 440 Layer<1-3>: Download IDB Success
19:43:25 449 Layer<1-3>:Reset Device Start
19:43:26 460 Layer<1-3>:Reset Device Success
19:43:26 479 Layer<1-3>:Wait For Loader Start
19:43:26 899 Layer<1-3>:Wait For Loader Success
19:43:26 907 Layer<1-3>:Test Device Start
19:43:26 918 Layer<1-3>:Test Device Success
19:43:26 928 Layer<1-3>: Download Firmware Start
19:43:26 934 <LAYER 1-3> ERROR: DownloadImage-->device did not support directLBA to write gpt
19:43:26 945 Error:Layer<1-3>: Download Firmware Fail

I'm guessing the problem is really the last error, but after looking for a while I can't seem to find an explanation. Does any of you know what this means?

I also noted that Alex used RKDevTool v2.73. Could the software be causing this issue? I tried finding older versions but without any success. If anyone has the 2.73 I'd like to give it a try.


Model: PX5
Android: 8.0.0
Kernel:4.4.93+ rocky@r930 #46
Build Number: px5-userdebug 8.0.0 OPR5.170623.007 eng.htc.20181222.10490 test-keys
MCU version: MTCE_GS_V3.44_3
Last edited:


New member
Oct 23, 2020
I have exactly the same issue... I also tried with 2.73 and I receive the same error... you can find it on github project /rockchip-linux/tools/blob/118d3d2a0ce47af2561e07c891250e3e0293d80a/windows/RKDevTool_Release_v2.73.zip (I can't provide the full link as I'm new to this forum).


Senior Member
Nov 26, 2012
Alex 'got' the method from my thread.
Format storage first in maskrom.
Yes versions of rktool can yield different results.

Refer my thread for details.
Last edited:


New member
Oct 24, 2020

I would like to upgrade my radio. I can do it ?

Android: 173434
MCU: S32F0_XinRC-18-W_20200727-9:21_HD1_7708_D_FF_C8
APP: PX5C_C54_HA1_Xrc2-10-EN_2020-08-03-1727


Feb 6, 2021
Hi All, sorry if this is asked before as I am a newbie to this form.

The issue is, I am unable to mirror my Samsung A51 with my PX5. The EasyConnection app that I get builtin with the unit says something like 'This version is illegal to use with this software'.

I am not sure if Android Auto works in this unit or not?
Or if there is any other hassle free yet mature mirroring app I can use?


Senior Member
Apr 3, 2007
Try screen mirroring apps from the play store, or buy a Carplay/Android Auto Dongle, theyre pretty cheap.


Senior Member
Apr 3, 2007
Easy connected used to work.

The dongles work on any Android head unit running android 4 and above.


Feb 6, 2021
Easy connected used to work.

The dongles work on any Android head unit running android 4 and above.
I am getting this when using EasyConnection:
Easy connected used to work.

The dongles work on any Android head unit running android 4 and above.
Easy connected used to work.

The dongles work on any Android head unit running android 4 and above.

I am gettimg this when using EasyConnect:


Senior Member
Aug 12, 2017
Just wondering how hard it would be to change a screen on one of these units?

I have a px5 for an Audi A3 and have cracked the screen so the touch screen only works in certain places.
I’m happy with the unit so have no need to buy a new one really so I’ve emailed xtrons who have said they can provide me with a replacement screen (at a cost).

Is it easy enough to do?
I’m pretty good with things and tend to do most things myself but I can’t find any info online/YouTube on how to do it and little electronics parts and pcb’s is something I’ve never played around with before.

This below is the exact unit I have



Apr 6, 2017
If it is a "normal" Chinese unit you can relatively easy replace the screen or the touch digitizer. At you tube there are movies about it. The problem will be to find the right spare part. But when you take it apart you might find some indication about the typenumber etc.


Senior Member
Aug 12, 2017
If it is a "normal" Chinese unit you can relatively easy replace the screen or the touch digitizer. At you tube there are movies about it. The problem will be to find the right spare part. But when you take it apart you might find some indication about the typenumber etc.
I bought it from xtrons and gave them their model number from the email they sent me when I bought it and they said they could provide me a replacement so hopefully it would be the right one with me giving them the model number.


Senior Member
Apr 26, 2011
Hi guys,
I have Eonon 2170: PX5 1024x600 A 8.0.0
MCU MTCE_WWW_V2.80_1 Mar 1 2018

long ago, I've tried A9 update, first, it wouldn't install, after an update from XDA, it installed but not everything worked properly, hence I went back to manufacturer's build, etc, as I also had some BT trouble on hands free, intermittent disconnect.

anyhow, I guess by now A9 has been fully debugged..?

so, what should I try, Android 9 or 10 ?
is there any must do, can't do before I try ?
what's the 'best path forward' ?
thanks for any tips or ...


Senior Member
Apr 3, 2007
All versions of Pie are buggy, factory or custom (customs are just modded factory ROMs anyway).

Having said that the bugs arent to do with BT or things no working properly, theyre mainly random reboots.
  • Like
Reactions: marchnz
This picture should show how to get it.
Hi, I have my lanewatch camera is not working.
When I turn on the right signal, it shows black screen and says no video signal.

On my wiring harness, it has 2 yellow rca cable. One says Camera back in and Video in. (see pic)
I'm not sure if I have the right cable and am looking for the cable that has right camera cable input.

Do you have a picture of yours that can share?
And what is the yellow rca labeled for lanewatch camera?



  • s-l1600.jpg
    86.7 KB · Views: 14

Top Liked Posts

  • There are no posts matching your filters.
  • 28
    Permanent root on android 8 via ADB without flashing

    Use the following instruction to receive permanent root on Android 8 using adb without flashing device:

    1. 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
      setprop persist.adb.tcp.port 5555
      setprop sys.rkadb.root 1
    2. On your PC, download latest "SuperSu" zip archive from official site, extract su binary from arm64 directory inside the archive
    3. On your PC, create new file called "rooting.rc" with following content:
      service rooting /system/bin/su --daemon
          class main
          priority 10
          user root
          seclabel u:object_r:system_file:s0
    4. From your PC run:
      # 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
    5. On Head Unit, install SuperSu from PlayMarket and ask "NO" when application ask to update the module
    6. Reboot and enjoy!
    This thread is intended on collect the information about Android 8 (Oreo) over the Android units that features:
    PX5 Platform Core Board

    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
    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
    4G/3G Dongle
    OBD02 Module
    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 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

    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:

    ANDROID 8 (Oreo) stock Update List:

    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 :
    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.
    2) Upgrade by extracting the SOM and connecting a homemade OTG USB cable:
    Instructions for making the OTG cable:


    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:
    Received a new update from Xtrons GS-PE PX5 8.0 September 20th
    Someone might want to mirror it before it gets pulled.

    GS-PE系列_PX5_8.0_优化亿联BUG 问题,MCU 优化电池电量显示(20180920)
    (GS-PE series _PX5_8.0_ optimizes the BUG problem of the billion, MCU optimizes the battery level display (20180920))

    MCU = MTCE_GS_V2.94_3 Sept 13 2018
    Build = px5-userdebug 8.0.0 OPR5.170623.007 eng.hct.20180919.204159 test-keys Sept 19 2018
    Kernel = 4.4.93+ rocky@hctr930 #343 Sept 15 2018