Database Users

[Q] 2DIN 'S07' Android 4.4 Using RK3066 - Root?

I recently bought a generic android head unit from Ali Express. It actually works well but I really need to connect it to a CAN bus and write some additional software (background: I want to replace the factory unit in a Nissan Leaf, so it needs to display some vehicle info, show the heater settings and set up the charge timer). I have experience in Android app development and embedded Linux, but I'm still a 'noob' when it comes to Android hacking (root access etc).
I'm pretty sure I will need root access to do what I want. It has 'CAN tx / rx' pins on the back, and I am pretty sure they are wired to one of the serial interfaces internally (I will need an adapter to convert UART to CAN as well). I played around with an app to access the serial ports (i.e. ttyxxx) but I didn't have permission to use many of them - probably the ones I wanted!
I don't want to re-write the existing music player, amp control and radio; I just want to add a new app to carry out my vehicle-specific functions.
I tried the root process given here but it didn't work.
Here are the device details:
Model: S07
MCU Version: MTCB-HA-V2.60
Android Version: 4.4.4_01062015
Kernel Version: 3.0.36+ [email protected] #278
CPU: ARM7 1.6G x 2
CPU/SOC is an RK3066 on a modular board. Pictures attached.
It doesn't have any physical buttons except reset - there are touch sensitive buttons for power, back and volume. It has one SD card slot for map data and no USB on the front (several on the back).
I haven't figured out how to get to the recovery console, or connect it to a PC via USB.
Any suggestions for how to root? Or get to recovery console?
Anyone else with a similar device?

Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work

Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
MayfairDROID said:
Check out the Huefi thread above. It has everything you need. first page covers root. basically, download the rom you want, put it on the GPS SD card, insert it, and wait for it to ask you to update. Once you do that, it will be rooted. there is no other way to root it if it has 4.4.4. DO NOT INSTALL A MCU file for it unless it is for HA devices. HA is the manufacture of the unit, and if you use an MCU file for a different device, you run the risk of loosing the physical buttons on the unit. This can be repaired by going into recovery and flashing the HA MCU, but that is a lot of extra work
Click to expand...
Click to collapse

jcolebaker said:
Hi! Thanks for your reply.
I was wary about installing a new image because I don't want to lose the existing radio app and amplifier controls (which are specific to the device rather than the RK3066 SOC module, if I have understood the structure correctly).
* Would a new image replace these apps, or are they actually in the MCU firmware anyway?
* Can I back up my current image first? I looked at some backup tools, but they all needed root access... =Catch 22.
Sorry for noob questions... I'm getting the hang of Linux but still new to messing with Android at a low level. I'd love to play around with a stripped Ubuntu or similar on the device, but I don't want to have to write my own software for the radio parts - at least not yet.
BTW do you know how the bootloader system works? Is it possible to boot from SD card or USB (therefore allowing some other OS to be booted without replacing the onboard image)?
Click to expand...
Click to collapse
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.

MayfairDROID said:
I cant help with the bootloader issues, but I can with some of the others:
-Radio and Amplifier apps are the same on all units, or should I say is compatible across all units. If you were to go into the settings, then factory settings and enter 126 as the password, you can see all the settings you need to make sure your unit functions after upgrading your rom image.
-You can not back up your factory image. its not possible. You can always reach out to your seller and ask them if they will send you a copy of the factory firmware.
Click to expand...
Click to collapse
SUCCESS! I just downloaded and installed the latest image from Malaysk (I think?) and it looks like it is working well! Radio, music player and amplifier work, and I have root access. Woo! So far so good... Thanks!

Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank

aribetty7811 said:
Hello Friends, I read your post. Like anything happens
I want to update my Car Stereo Radio Head Unit
Here are the device details:
Model; S07
MTCB-JY-v2.44
MAR 24 2015 9:46:14
ANDROID VERSION 4.4.4_25032015
kernel version
3.0.36+
ROOT @ UBUNTU # 766
Build number
rk3066.eng4.4.4 25032015.13: 08: 43
CPU
arm7 1.6 GHz (x2)
But that is not the screen resolusion 880 // 1024
Knowing that I have to Huifei / KGL, Klyde, or RoadMaster
Thank
Click to expand...
Click to collapse
Hi, I also didn't know the screen resolution, and it is not mentioned on the "About" screen.
In the settings menus, I found some options for recording a video of the display (I don't know why!) and the maximum resolution there was 1024 x 600. I figured that you wouldn't bother to record at higher res than the screen had, so the resolution must be 1024x600. This seemed to work!
My stereo has absolutely NO branding on it anywhere so I don't know whether it's a clone of Huifei or something else, but it worked with the "Malaysk" firmware, which I downloaded from the Huifie file repository (linked from here), under firmware->Malaysk ROM->Malaysk DualCore RK3066).
I picked the bottom one (12th Jun 15, 1024x600 with different launcher).

jcolebaker said:
Anyone else with a similar device?
Click to expand...
Click to collapse
I just installed the same unit. Only complaints are streaming music via Bluetooth only works if you open up the Bluetooth app (probably because android doesn't act as a Bluetooth sink). The other issue is, I cannot seem to change the brightness of the screen...its a touch too dim for daylight (I have a convertible) and a bit too bright for nighttime.
Glad to see you got a custom rom working.

Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk

vdubskey said:
Hey jcolebaker, do you think you could post what the LCD model number is? Is it a Hannstar HSD070IFW1-A?
Sent from my Nexus 6 using Tapatalk
Click to expand...
Click to collapse
Sorry not sure what the LCD is - I don't want to pull it apart. It has a board on the back which has the following on it:
BL-TFT-V2.2(HCT)
That's soldered to another board that says:
P/N:BL-7inch-7000-KB-V00 20150311

Update question
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
---------- Post added at 11:06 PM ---------- Previous post was at 10:42 PM ----------
dovoto said:
Do I burn the update.img file to the sd card or do I simply copy it? And does it have to be my gps sd card or can it be a spare blank one?
Thanks
Click to expand...
Click to collapse
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?

dovoto said:
Doesn't appear to be an img file in the context of "burn it" so I think that answers that question (just copy it) The head unit doesn't seem to do anything when I drop it in though (either with it on when I insert it or with it already inserted during a reset). Any thoughts?
Click to expand...
Click to collapse
The file should be "update.zip". I used a new SD card - try formatting one with FAT32.
You just copy it to the card and insert it - I think the stock Android image automatically checks for update files that look like this, and loads them. This process worked OK for me - if not then hopefully someone here knows more about the update process than me.

HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks

Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
I think the file is "update.img" not "update.zip". Anyway I have not figured out how to get to the boot loader on mine, and I never got any recovery console. Sorry I am too much of a beginner myself to suggest anything.

HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Instead of flashing a new image, go to the factory settings and type in *#hct#root#
This should give you root, no need to flash a new image

Logicsystem360 said:
HI !
I also try to root my 2din android without success... I have the same as your and I fail to get recovery and the android can't detect the update.img (or update.zip)
I have tried many tips, my sd card is in fat32, well detected by android ...
Do you have the tip to access to the recovery ?
Thanks
Click to expand...
Click to collapse
Bonjour.
If you would like more than root and you're still having trouble getting into recovery with your Hot Audio RK3066 1024x600 2 DIN Head Unit, the steps below have worked for me when the system does not automatically detect the mcu or update.img.
*** Prior to flashing any OEM or Custom ROM firmware, I recommend using a backup app like Titanium to save all your existing apps and data to your external micro sd card or usb memory stick.
1) Install Quick Boot or a similar apk from the play store.
2) Attach a wireless usb or usb keyboard and confirm it is working as intended. I use a Lenovo N5902 but most usb or wireless usb keyboards should work for this task.
3) Make sure you have the update and or mcu image file on your gps micro sd card or an attached usb memory stick (not the zip file).
4) Open Quick Boot, select recovery, and the system will shut down and boot into recovery.
5) Use your usb keyboard to scroll or arrow down to the update option with correct img file location, then press enter to execute the mcu or android firmware update or both.
6) After you update the android firmware, it is highly recommended that you go into the Settings > Backup & Reset, and select reset to factory and check the box to delete all data from the internal sd card. This reset to factory and internal sd card wipe should give your updated android system a clean start and help avoid system issues due to left over data from the previous firmware.
7) Delete the mcu and or update image from your external micro sd card. Done.
Hope this helps...
Best to all,
R

wrong thread. sorry

Android dvd s07 update
Hi,
I want update my android car dvd mercedes w203 2006
MCU version: MTCB-KGL-V2.80
Android version:
4.4.4._07012016
3.0.36+
[email protected] #2321
I need files to update, please help

"UI and mcu does not match" plz help me

My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 6.0.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-09-06 17:39:41 KEQ_(NOR)__90_C9_7706_5009_CAN(XianDai)_Newlap
Please help me solve the problem.
Thanks.

no0496 said:
My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 6.0.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-09-06 17:39:41 KEQ_(NOR)__90_C9_7706_5009_CAN(XianDai)_Newlap
Please help me solve the problem.
Thanks.
Click to expand...
Click to collapse
So.if I understood correctly....
You have updated your unit (not joying) with the joying Android 6 firmware. And now you have issues on boot as it appears a message that "ui and mcu dont match"
Do your unit boot?
Apparently joying has been placed a security check to avoid others use their software....
You have to enter into recovery menu to downgrade to your seller Android ROm.
Check on forums how to get into recovery.
Some guy wrote about plugging a keyboard and some key combination resulted into recovery menu.
There you can force to upload a new software (this time use the one supplied by your seller)
Enviado desde mi D6603 mediante Tapatalk

ikerg said:
So.if I understood correctly....
You have updated your unit (not joying) with the joying Android 6 firmware. And now you have issues on boot as it appears a message that "ui and mcu dont match"
Do your unit boot?
Apparently joying has been placed a security check to avoid others use their software....
You have to enter into recovery menu to downgrade to your seller Android ROm.
Check on forums how to get into recovery.
Some guy wrote about plugging a keyboard and some key combination resulted into recovery menu.
There you can force to upload a new software (this time use the one supplied by your seller)
Enviado desde mi D6603 mediante Tapatalk
Click to expand...
Click to collapse
The boot is normal. I asked the seller, but I do not know how to get into recovery mode.
I still do not have enough information.
10.1 인치 쿼드 코어 안드로이드 5.1 자동차 DVD 플레이어 기아 스포티지 2011 2012 2013 2014 2015 자동차 라디오 스테레오 gps 네비게이션 시스템
s.aliexpress.com/ruQJ3YRr
(from AliExpress Android)
That's the product I bought.

doitright6 said:
That is *NOT* the product you own. The specifications on that product indicate "RK3188 Cortex A9 Quad Core 1.6GHz CPU"
Yours is clearly an Intel/Sofia x86 CPU, which is so different that if you tried to install intel/sofia firmware on the rk3188 unit, it definitely would not boot.
Now there is something I find extremely interesting about your unit;
the MCU string indicates that it is an FYT5009 unit, just like the Joying, but with a manufacturer of "KEQ". Up until now, we have only seen Joying units with the FYT5009. If you can figure out how to load the Joying MCU firmware on there, then it just might work. This might be accomplished by just re-running the update process. There is a file that you would have to rename though -- 5009_20.zip has to be renamed to 5009_60.zip.
But beware; there is also the possibility that the Joying MCU firmware could brick the thing. I doubt it though, it is likely that yours is built from the same schematics.
Click to expand...
Click to collapse
The product is SOFIA chipset is right. It is written by the seller differently from the actual one.
I will attach an image link before the update.
Blog.naver.com/no0496/221001239611
As doitright6 said, it is not a joying product, but it could be updated in the same way.
I will attach the updated JOYING 6.0 firmware and my unit's 5.1.1 genuine firmware.
Please let me know how to fix it.
[JOING 6.0]
drive.google.com/open?id=0BymwBAxBOI-TU0pMQ2REZmV3djA
[my unit 5.1.1]
drive.google.com/open?id=0BymwBAxBOI-Tb0xLV0pjR2JHcXM
Thanks.

My Android unit is not a joying product. However, I am using the same CPU chipset (intel sofia).
Joying has been updated to the new version of Android 6.0, so it Like that string "UI and mcu does not match". I have genuine firmware but I can not downgrade it.
Help me eliminate red letters and yellow background in my product.
I can not attach a photo because I am a new member. Sorry.
My product information is
Android Version: 5.1.1
CPU Info: Intel ATOM 4QuadCore. GPU4D: MALI450 MP4
System Info: APP 1024x600 2016-10-09 19:11:44
MCU Version: 2016-10-19 11:20:27 RUL_(NOR)__90_C9_685x_5009_CAN(DaZhong)_Newlap
Please help me solve the problem.
Thanks.

Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.

Hi
How Can I know which MCU I should use
If my MCU looks like MCU version 5.3.1836-13E50201-160106
Thank you

Did this helped i am also stucked on the same situation

guys
have you solved this issue , please help me too

Omer.afzal said:
Did this helped i am also stucked on the same situation
Click to expand...
Click to collapse
helmi_zr1 said:
guys
have you solved this issue , please help me too
Click to expand...
Click to collapse
Did you both miss post #6? If that doesn't work, what was your result? Failing that - what does the reseller suggest?

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
sir
i have been trying to change the no. but couls not able to do it
kindly let me know whats the easy way

You're not going to be able to do it if you have not rooted your HU.

nic2k said:
You're not going to be able to do it if you have not rooted your HU.
Click to expand...
Click to collapse
thank you i will try to root my device and let you

helmi_zr1 said:
thank you i will try to root my device and let you
Click to expand...
Click to collapse
thank you sir the top message have been removed
thank you so much for your help :good::good::good::good:
now one more thing
how i can downgrade to the old firmware since i saw the file in my HU but when i try to selected the unit is not doing any things
do you have any idea ?

please help!
Hi!
I want to ask for help. I have a radio that the seller has corrupted with an update. the update was not good. i put up joying software and it works properly with it, but in the yellow bar above there is that "UI AND MCU DOEST NOT MATCH".put the latest update on it.2020-04-07.
thank you!
managed to root the device but fyt.prop filet is not included in the System / App folder. what could be the solution
land Mou [email protected] 16:26 4)
-keys
System Info
kernel:#1 SMP PREEMPT Tue Apr 7 12:20:56 CST 2020
platform 12)6313 LFN Full Band carplay
touch:goodix 911_1060 (5a422c2b)E:0
panel:none
radiotype:nxp6xXx_6686(dft)(0)
audiotype:dsp55
APP 1024x600 2020-04-09 09:10:18
System 2020-04-07 12:15:23 Tuesday
03L G23P46F04 veT. 1.U
EO/2020:03:2:16:50:18 blink
HTXY
---------------Device Status
System Application Info
System Application Information
CPU Info
CPU:Intel X86_Octa-Core 1.8GHZ [email protected] GB(Memory) + 64 GB(Storage)
MCU Version
2019.11.18 09:58:08 KEQ_53_C63L_G23P48F64_Ver: 1.0
Bluetooth Version
BLINK 2161_RELEASE0/2020:03:2:16:50:18_blink

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
Do you know the manufacturer number for this MCU?
MCU version: 2020.08.21 17:11:25 YIN_53_L82_G23P48F64_V:1.0
Thank you.

javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
how can i enter i no found folder fyt.prop help

Hello friend i have the same problem i had rooted device and did change number 43 to 9 you had written, but screen warning now like written like this
UI AND MCU DOES NOT MATCH! (PCBA)
do you have a solution?
javierortiz2 said:
Enter in System /app folder and edit fyt.prop
change line
ro. build. fytmanufacturer=xx
with
ro.build.fytmanufacturer=9
save the file.
Use a root acces file explorer like solid explorer, with root privileges.
Reboot, may be done.
Click to expand...
Click to collapse
e

I can't find fyt.prop file and I had rooted. I have android 10 , is there another solution?

In the same boat. Found the file in CX file explorer (yes, I'm rooted and CX is in root mode), but it won't save my changes ("Cannot save the file".).
Is there a known way to edit and save the fyt.prop file?
At least I only have $20 and a few evenings invested (I found my unit brand new at a thrift store). Been one of my better behaved ones but I got greedy on updates. Also, I flashed the wrong file because I misread my MCU version number, and what *should* have been the right file loops when I try to flash it (reboots after the "CUSTOMER ID" text of the MCU update, have to reset to end the loop)... Whoops!

Help identify unit, manufacturer code ZQ?

I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.

mondo1287 said:
I bought one of these Chinese Android boxes that integrate with your existing head unit and I'm trying to find any information about it, and which forum I should be posting questions to. FWIW I have a VW Touareg with an RNS850 system that is basically the same thing as the Audi MMI 3g+ system, but with a touch screen.
Here is some model and version info:
Model: ZQ8002
MCU: TUREG-ZQAND-1.1
APP: MTK-8002_C37_GA1_DZSJ_DaZhong_EN_2019-05-27
Android: 6.0
CPU: 4 core 32-bit CPU Coetex-A7 @1.3G
RAM: 2GB
Flash: 16GB
Baseband Version: MOLY.WR8.W1449.MD.WG.MP.V61.P3
Kernel: 3.18.19 [email protected] #2
Hostname: fise8321_tb_m (seen via ADB shell)
It has a "Factory Settings" menu similar to other Android head units I've seen mentioned here. That presents a numeric keypad. I figured out a few codes for it:
0000: Bunch of debugging toggles, also toggle for ZLink CarPlay
5555: Just says "ok" when you enter it. I think this turns on ADB over TCP. I was able to ADB to it after this, but I had also use a terminal emulator to enable it.
9999: Single item to allow installation of "APP", which I assume is the firmware?
The box on Amazon: https://www.amazon.com/gp/product/B07PJGLD41/ref=ppx_yo_dt_b_asin_title_o00_s00?ie=UTF8&psc=1
Main issues I'm trying to solve right now is that my skip track buttons on my steering wheel aren't doing anything, even though I can see the CAN bus events in the logs when I press the buttons. I'm hoping there's a Factory Setting code I haven't found that might let me change the CAN Bus settings. It has carCanBus and FactorySettings apks that I was able to decompile, but didn't find anything useful.
Click to expand...
Click to collapse
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]

Albe Vala said:
Hi Mondo! How are you?, I've updated my interface like ypurs with a wrong MCU. Could you send my your? I need the file MCU TUREG-ZQAND-1.1. Thanks a lot. My email is [email protected]
Click to expand...
Click to collapse
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!

mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
I don't know how is it possible to exctract the MCU file (.bin) by the interface. I could try to find online anything to do it. i try to find softwars and so on, if i'will try i tell you something. I send many mails to producer of the unit, but everytime i do it, he tell me to waiting for response of the engineering department......and i wait. My MCU was TUREG-ZQAND-1.3 but i think your version 1.1 coluld going rigt for mine.

Not (android-auto) requested moderator move to Android head units forum.

mondo1287 said:
Hi Albe, is this something I could copy off of the unit? I have not had mine installed for a couple of years, but I am interested in trying to get this thing updated to possibly fix some of the issues I had with it. It may be a long time before I work on it, but if you could provide the file system path to copy the MCU file, I will provide it for you. If it's more involved than just copying a file, just let me know what I need to do or link me to a guide. Thanks!
Click to expand...
Click to collapse
Hi Mondo. I've find how could you extract the MCU file from your ZQ android interface. read the thread that i link you now! I wiat for your reply. https://www.androidiani.com/forum/autoradio-android/546699-f-q-px5-autoradio-android.html. At the end of Point "2" you can read how to export your mcu file! Thanks a lot and best regards.

MCU version of Erisin ES6292B 9" PX6???

I received an Erisin ES6292B 9" PX6 for Mercedes Benz.
I don't know why but for some reason I was sure it was a MTCD/E version so without prior checking, I immediately went for the upgrade to Hal9K MOD.
The upgrade finished and the unit rebooted. I am not sure if I saw the boot logo (I think not) but as if this was not enough, during first boot, someone in the workshop cut the power to the car and the unit was bricked!
I wrote to Erisin and they sent me the Stock image to try to apply from recovery. However it is impossible to enter recovery with any way I tried. As long as I hold the reset button the unit is dead. When I release it the backlit starts but the screen remains black even after 10 minutes. No recovery, not even boot logo! It seems the MCU firmware is corrupted.
At the moment I have an ST-LINK/V2 programmer in my hands to go for unbricking with Wadzio method but STILL NO ANSWER FROM ERISIN IF MY UNIT IS MTCD/E or different.
Anyone knows?
Also, anyone knows a direct link to download recovery.bin for my unit?

What are the names of the files that were being applied for upgrade? Are you able to share these - assume you had two files, one MCU and the other android.
Also the stock image ersin supplied.
Note the wadzio Unbrick is for MCU unbricking, are you sure that the MCU is bricked? I.e. you are sure you were upgrading the MCU, because from your description, sounds like you were upgrading the SOM/Android.
Details are everything.

marchnz said:
What are the names of the files that were being applied for upgrade? Are you able to share these - assume you had two files, one MCU and the other android.
Also the stock image ersin supplied.
Note the wadzio Unbrick is for MCU unbricking, are you sure that the MCU is bricked? I.e. you are sure you were upgrading the MCU, because from your description, sounds like you were upgrading the SOM/Android.
Details are everything.
Click to expand...
Click to collapse
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery

When there is no boot logo, I guess it is the MCU. Correct?

aphilgr1 said:
When there is no boot logo, I guess it is the MCU. Correct?
Click to expand...
Click to collapse
Not necessarily, no.

aphilgr1 said:
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery
Click to expand...
Click to collapse
The zip doesn't contain an MCU, and is an android OTA zip, therefore if your power outage occurred while applying this file, the SOM emmc/nand is probably corrupt, and you might not be able to enter recovery.
I've had a number of SOMs sent to me exhibiting the same symptom, so not uncommon.
If unable to SDCard boot, SOM recovery via OTG is the likely path to recovery. Refer my threads/signature.

marchnz said:
The zip doesn't contain an MCU, and is an android OTA zip, therefore if your power outage occurred while applying this file, the SOM emmc/nand is probably corrupt, and you might not be able to enter recovery.
I've had a number of SOMs sent to me exhibiting the same symptom, so not uncommon.
If unable to SDCard boot, SOM recovery via OTG is the likely path to recovery. Refer my threads/signature.
Click to expand...
Click to collapse
I still have not managed to find out if my MCU version is MTCD/E or other. Still waiting for Erisin's response. They requested a video with symptoms which I already sent.
Supposedly my MCU's version is an STM32 and I tried to install Hal9k's ROM (specific for MTCD/E) wouldn't that corrupt the MCU? To my thinking, this is the most probable scenario.

aphilgr1 said:
I still have not managed to find out if my MCU version is MTCD/E or other. Still waiting for Erisin's response. They requested a video with symptoms which I already sent.
Supposedly my MCU's version is an STM32 and I tried to install Hal9k's ROM (specific for MTCD/E) wouldn't that corrupt the MCU? To my thinking, this is the most probable scenario.
Click to expand...
Click to collapse
The files you list are not MCU updates.
Its trivial to determine if you have an MTCD MCU using Wadzio's decryption tool, however & once again, the MCU is separate to Android. You cannot flash the "wrong" platform MCU (ie. MTCD vs STM MCU) in recovery.
Once again; the files you list are ANDROID and not MCU. Unless you havent described what you were doing to "upgrade" the unit, which lead to corruption; the SOM is bricked and not MCU.
Again, for clarity, MCU and ANDROID are not the same. They are separate images and cannot be flashed together.

marchnz said:
Once again; the files you list are ANDROID and not MCU. Unless you havent described what you were doing to "upgrade" the unit, which lead to corruption; the SOM is bricked and not MCU.
Click to expand...
Click to collapse
Kind of getting there. Ha ha, my knowledge is very epidermic! Tomorrow I ll try the SOM recovery via OTG as you suggested and report. Thanks for your time

Just a (silly?) question: Could we say MCU is equivalent to bios on a PC and Android is the equivalent to PC OS? If the MCU (=bios) is still untouched, even with Android (=PC OS) corrupted, why is it impossible to boot from SD or simply access recovery?

aphilgr1 said:
This is the link to the Hal9k PX6 Custom ROM
This is the link to my unit's stock ROM
I assume my MCU is bricked because I cannot enter recovery
Click to expand...
Click to collapse
Hello. | have an Erisin ES6283C 8" Android 9.0 Car Stereo DAB+ 4G WiFi HDMI GPS Sat Nav for Mercedes C/CLK/CLC Class W203 W209.
They (Erisin) provided me the same stock ROM as yours.
For sure your MCU is STM32, as mine.

aphilgr1 said:
Just a (silly?) question: Could we say MCU is equivalent to bios on a PC and Android is the equivalent to PC OS? If the MCU (=bios) is still untouched, even with Android (=PC OS) corrupted, why is it impossible to boot from SD or simply access recovery?
Click to expand...
Click to collapse
The MCU is more like say an auxillary fan and button controller, connected to a serial port, but still controlling the power supply to the computer.
Why impossible to boot or access recovery - corrupt emmc/nand.
Your unit doesnt look like an MTCD/E device.

Unfortunately hardware used in my PX6 implementation is quite different from what shown in SOM recovery over OTG page. I don't have the tools needed to uncover the SOM (75W soldering etc). Judging from the bottom, it seems the SOM is embedded on the mainboard and there may not be any pins accessible. However, rk3399 supports what is called MaskRom mode (a relevant link translated from Chinese) allowing programming of the SOM with the use of a male to male usb cable. But this would be possible only if we access the interior and find that the test points to bridge exist. My last resort if nothing else is possible.
Another issue I am facing is that my firmware is not in update.img format but comes in .zip split in several files. I think I need to repack it in .img format in order to be able to program my unit with existing tools and I don't know how
Just a last (stupid?) question. Accessing the MCU via ST-LINK/V2 programmer is possible. If we new the starting memory address of the SOM firmware or the various parts, would it be possible to flash from there?

florynn2003 said:
Hello. | have an Erisin ES6283C 8" Android 9.0 Car Stereo DAB+ 4G WiFi HDMI GPS Sat Nav for Mercedes C/CLK/CLC Class W203 W209.
They (Erisin) provided me the same stock ROM as yours.
For sure your MCU is STM32, as mine.
Click to expand...
Click to collapse
It is an STM32 eventually. I managed to unbrick it but the MCU was changed. Both firmware and config. I am stuck with an 800X480 desktop on a 1024X600 display.
Can you export your MCU.cfg file and send it to me please? I think you need to go to settings/about then toggle between Kernel Version and OS Version 6 times in total to enter hidden menu. If a password is asked, try 666666 or 123456. From there you can go down and select export config.
Thanks in advance!

aphilgr1 said:
It is an STM32 eventually. I managed to unbrick it but the MCU was changed. Both firmware and config. I am stuck with an 800X480 desktop on a 1024X600 display.
Can you export your MCU.cfg file and send it to me please? I think you need to go to settings/about then toggle between Kernel Version and OS Version 6 times in total to enter hidden menu. If a password is asked, try 666666 or 123456. From there you can go down and select export config.
Thanks in advance!
Click to expand...
Click to collapse
I tried to export config data (is the only export in the menu) and it's only a 1KB file. I think it's the config only for HU startup. I searched all the settings (including the Hidden section) and I have nothing to export the MCU config.

florynn2003 said:
I tried to export config data (is the only export in the menu) and it's only a 1KB file. I think it's the config only for HU startup. I searched all the settings (including the Hidden section) and I have nothing to export the MCU config.
Click to expand...
Click to collapse
This is exactly what I am looking for. Can you share please?

aphilgr1 said:
This is exactly what I am looking for. Can you share please?
Click to expand...
Click to collapse
here you go

Wondering if you managed to fix your HU? Also, what rom did you settle on?
Also, is that blue material on your HU metal or painted plastic?

lachlan102 said:
Wondering if you managed to fix your HU? Also, what rom did you settle on?
Also, is that blue material on your HU metal or painted plastic?
Click to expand...
Click to collapse
https://forum.xda-developers.com/showpost.php?p=81930477&postcount=100

Hi! Dumb question: I own an Erisin ES7802B which came with Android 8.0, where can I check or find if I can update my product? Thanks in advance!

Need Android 10 Model: px5 MTCU_HT Custom Firmware

Hey there
My Head Unit is no longer saving the last used memory and the radio just stopped working this week.
I am looking for custom firmware to try and hopefully get my unit working properly.
I have searched online and with not a lot of luck. I found someone with custom Firmware on Youtube
but I have used his firmware on another unit a few years back and you can't turn off the auto screen saver option
so I would rather not use his firmware again.
Any Help?
My specs:
Pumpkin Android Radio
Model: px5 (1024 x 600)
Android Version: 10
Last security Update: 5. May 2020
Build NUmber: rk3368-userdebig 10
Kernel-Version: 4.19.111
MCU-Version: MTCU_HT_V3.71_1 Dec 19 2020
CPU: Octa-core Cortex-A53 @ 1.5G
Memory: 3937 MB
I hope someone can help
Thank you in advance.

The file I uploaded is the firmware update the seller sent to me.
Seller instructions:
Update methods:
Download the link on your computer--Don’t unzip the file update.zip. Copy this file " update.zip" to the USB root directory. Connect the USB stick to the USB port of the radio. If the radio detects the update immediately and wants to install it, click on Cancel.
Then open Settings> System> System Updates> tick the box > click Install.
I installed it all Okay. Still have the same problems.
I also found this firmware
Hal9k_Mod_5.0_MTCx_HCTx_PX5_eng.rar
From
And it also installed Okay. Looks very different (I don't really like it that much, far too bright) however I still have the same problems.
I am starting to think it's a hardware problem.
I will post back after trying something else.

techno489 said:
Factory yhss1_PX5-A10-rk3368-MTCU_HT(20211111).zip
Click to expand...
Click to collapse
This firmware is based on the custom firmware of "Factory yhss1_PX5-A10-rk3368-MTCU_HT(20211111)"
Яндекс
Найдётся всё
disk.yandex.ru

techno489 said:
The file I uploaded is the firmware update the seller sent to me.
Seller instructions:
Update methods:
Download the link on your computer--Don’t unzip the file update.zip. Copy this file " update.zip" to the USB root directory. Connect the USB stick to the USB port of the radio. If the radio detects the update immediately and wants to install it, click on Cancel.
Then open Settings> System> System Updates> tick the box > click Install.
I installed it all Okay. Still have the same problems.
I also found this firmware
Hal9k_Mod_5.0_MTCx_HCTx_PX5_eng.rar
From
And it also installed Okay. Looks very different (I don't really like it that much, far too bright) however I still have the same problems.
I am starting to think it's a hardware problem.
I will post back after trying something else.
Click to expand...
Click to collapse
You even did not tell anything about your issues you are facing. What do you mean with:
My Head Unit is no longer saving the last used memory and the radio just stopped working this week.
Click to expand...
Click to collapse
So really think about that and communicate correctly.
The same would be if you call your workshop that your car does something wrong and don´t tell them what happens.
Would you get any instructions? I think not.
So tell us the issues and then thee might be some answer possible.
@localos : I think just pushing links to any firmware version without having a bug report does not make any sense.