Database Users

help me. Ui overlay problem. non mtcb/mtcd, not joying.

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.
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
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.
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.
Please help me solve the problem.

With the head unit rooted and a root file explorer you have to edit the ro.build.fytmanufacturer line in fyt.prop and change the number at the end to match that of KEQ
Which from what i have been able to tell with google searchinf is 15
So you would make the line say ro.build.fytmanufacturer=15
After you make the change, save the file and reboot the head unit. If all goes well the mismatch banner will be gone.

how did you know that KEQ is 15? What is DAOH?

Joying PX5 Bootloop after firmware update

Hello,
I just updated my Joying Android HU. After reboot, it just boot loop of JOYING logo. Maybe i use wrong firmware. I also not sure what is my Joying model number, FYT or MTCB or etc. Here's the detail of show on the screen, before i update:
Model Number: PX5
Processor: 8 Core 64 bit CPU [email protected]
Memory: 2GB
Resolution: 1024x600
Machine Code: 0700118B0000AA55
Android Version: 6.0.1
Android Security Patch Level: October 1 2016
Baseband Version: Unknown
Kernel Version: 3.10.0 [email protected] #53
Build Number: MXC89L-release-keys-20171110-V7.0
APP Version: TP6735 0.0.54
MCU Version: TP6735 4.33
16GB ROM
Can expert here please advise what i need to do?
Thank you

JackSharing said:
Hello,
I just updated my Joying Android HU. After reboot, it just boot loop of JOYING logo. Maybe i use wrong firmware. I also not sure what is my Joying model number, FYT or MTCB or etc. Here's the detail of show on the screen, before i update:
Model Number: PX5
Processor: 8 Core 64 bit CPU [email protected]
Memory: 2GB
Resolution: 1024x600
Machine Code: 0700118B0000AA55
Android Version: 6.0.1
Android Security Patch Level: October 1 2016
Baseband Version: Unknown
Kernel Version: 3.10.0 [email protected] #53
Build Number: MXC89L-release-keys-20171110-V7.0
APP Version: TP6735 0.0.54
MCU Version: TP6735 4.33
16GB ROM
Click to expand...
Click to collapse
Do you have a joying type id?
Which firmware did you try to flash?
Do you have a fan and/or heatsink on your unit? The Joying units can become quite hot during flashing and even too hot: the 1GB units even more.. That can also cause the boot loop. It might even help to take it partially out of the dash and use a hair dryer on cooling stand via the top of one of the holes in the side (and then of course: install a fan!)

surfer63 said:
Do you have a joying type id?
Which firmware did you try to flash?
Do you have a fan and/or heatsink on your unit? The Joying units can become quite hot during flashing and even too hot: the 1GB units even more.. That can also cause the boot loop. It might even help to take it partially out of the dash and use a hair dryer on cooling stand via the top of one of the holes in the side (and then of course: install a fan!)
Click to expand...
Click to collapse
THanks for the reply.
I did modified my car aircond to allow small hole to blow to the back of the HU.
From the info i gave, what is type of HU?

Additional Info. The physical look is the same like in this video:

JackSharing said:
Additional Info. The physical look is the same like in this video:
Click to expand...
Click to collapse
I overlooked the Android version 6.0.1 on your PX5. This means you have a QD unit. Joying used to have an upgrade from 6 to 8, but that has disappeared. You can not simply flash an android 8 version onto a version 6.0.1.
Contact Joying at one of their email addresses.

Youtube video that i give is upgrade from 6 to 8. Do you mean this tutorial?

JackSharing said:
Youtube video that i give is upgrade from 6 to 8. Do you mean this tutorial?
Click to expand...
Click to collapse
I know it is the upgrade video. Joying did have a special upgrade firmware version some 8-10 (?) months ago. It is no longer on their blog. And simply flashing a version 8 onto a version 6 does not work. That's why I advised to contact Joying.

surfer63 said:
I know it is the upgrade video. Joying did have a special upgrade firmware version some 8-10 (?) months ago. It is no longer on their blog. And simply flashing a version 8 onto a version 6 does not work. That's why I advised to contact Joying.
Click to expand...
Click to collapse
Ok. I think this is the reason why i have bootloop. THank you.

problem after reset head unit

Hi,
I have a android head unit with following specs:
Processor type : Quadcore-T3
Android version : 7.1.1
MCU version: T5.3.19-23-41-E43101-180519
System version: V8.3.2_20180528.165457_PH-TW2-CarPlay
DVD version: 2.13.13-1200xh
after i do reset my head unit, the sound of my car become so little, I can barely hear it. I tried to choose correct model in car model in extra settings but that didnt work. Is there anyway to fix that ?
I also want to upgrade my firmware, what should i do and which firmware is compatible with my head unit ? thank you for your support

Noob questing for updating unbranded HeadUnit

Hi All,
I have been reading up a number of threads and would like some guidance of how to update my headunit.
Ive purchased a preowned car which it came with the Headunit. It is a VW Jetta (2015 model) not sure if its the stock unit.
As i cant find the model, i understand that might be difficult as it needs to match the resolution.
I have some details below:
Model Number: S07 (not sure which brand that even is)
MCU version: MTCB-KGL-v2.5.5
Android version: 4.4.4_01062015
CPU: Arm v7 1.6Ghz
Memory: 1024mb
I know i will need a KGL firmware but i see some mentions which i should not flash the MCU.

I just saw this thread...
https://forum.xda-developers.com/an.../comprehensive-updated-mcu-list-mtcd-t3476880
Seems like its just about placing the img file to the root of the sd card
rickbath said:
Hi All,
I have been reading up a number of threads and would like some guidance of how to update my headunit.
Ive purchased a preowned car which it came with the Headunit. It is a VW Jetta (2015 model) not sure if its the stock unit.
As i cant find the model, i understand that might be difficult as it needs to match the resolution.
I have some details below:
Model Number: S07 (not sure which brand that even is)
MCU version: MTCB-KGL-v2.5.5
Android version: 4.4.4_01062015
CPU: Arm v7 1.6Ghz
Memory: 1024mb
I know i will need a KGL firmware but i see some mentions which i should not flash the MCU.
Click to expand...
Click to collapse

ive just tried to flash it but have a problem when i entered the bootloader mode.
It mentioned unable to read sd card. Any ideas?

Winca/Roadnav S200 PX5 ZHAN_(NOR) MCU & firmware (Opel Astra J)

Hi guys. Maybe and hopefully someone of you can help me here.
I bought a used Android system based on the Winca S200 with ZHAN_(NOR) MCU for the Opel Astra J. While looking for new system software I stupidly flashed a newer system version, but the wrong MCU, so that the canbus box and all vehicle information are no longer recognized.
I therefore urgently need the system software with which the device was delivered (I have attached photos of it.) Does anyone have a dump or backup of this firmware and MCU? The dealer from whom the device was purchased also no longer offers support for these devices.
Android version
8.0.0
Build number
px5-userdebug 8.0.0 OPR5.170623.007 eng.bsp. 20180411.192159 test-keys
Information of the system
APP 1024x600 2018-05-07 11:19:58
CPU info
CPU: ARM Cortex-A53 eight-core 2+32G PX5, GPU: PowerVR G6110
MCU version
2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
DVD version
2018-03-26 16:08:56 R-86C-096I-NC-NP-1.0-PI2S
BT version
BLINK_8723DS_RELEASE/2018:04:02:18:14:50
CAN version
V2.32.000BYPTDA

droidmanuser said:
Hi guys. Maybe and hopefully someone of you can help me here.
I bought a used Android system based on the Winca S200 with ZHAN_(NOR) MCU for the Opel Astra J. While looking for new system software I stupidly flashed a newer system version, but the wrong MCU, so that the canbus box and all vehicle information are no longer recognized.
I therefore urgently need the system software with which the device was delivered (I have attached photos of it.) Does anyone have a dump or backup of this firmware and MCU? The dealer from whom the device was purchased also no longer offers support for these devices.
Android version
8.0.0
Build number
px5-userdebug 8.0.0 OPR5.170623.007 eng.bsp. 20180411.192159 test-keys
Information of the system
APP 1024x600 2018-05-07 11:19:58
CPU info
CPU: ARM Cortex-A53 eight-core 2+32G PX5, GPU: PowerVR G6110
MCU version
2018-04-16 17:04:06 ZHAN_(NOR)__90_C9RD6686_CAN(A)PX5D1804160
DVD version
2018-03-26 16:08:56 R-86C-096I-NC-NP-1.0-PI2S
BT version
BLINK_8723DS_RELEASE/2018:04:02:18:14:50
CAN version
V2.32.000BYPTD
Click to expand...
Click to collapse
hi
can you take photos of serial number i have been dealing with this type of head unit , i wish i can help , just send me the serial number , since mcu and software is different

mustafaspirit said:
hi
can you take photos of serial number i have been dealing with this type of head unit , i wish i can help , just send me the serial number , since mcu and software is different
Click to expand...
Click to collapse
Of course, but where to find it?
Attached a photo. That's all I have. I hope you can help me.

mustafaspirit said:
hi
can you take photos of serial number i have been dealing with this type of head unit , i wish i can help , just send me the serial number , since mcu and software is different
Click to expand...
Click to collapse
Finally two more photos. The first from the device itself, the second from the touchscreen. I really hope you or someone else can help me.

Hi .
I have sheet of links for different models Your model is not included in my sheet of links of different models .
The software process is to have two steps ..
First software ( android system).
Second software is for mcu that much your canbus type related to your car model..
Here are the models i have in list if you think you can check one of them i can share with you

@mustafaspirit
Well, I think there is no similar software for my unit... do you have other sources maybe?

@mustafaspirit
Short update. I got the MCU from Renault Kelos (W329A) now from another xda user here. This MCU is exactly the same as mine from factory. And my Canbus-Box was detected again, too.
But I'm still on search for the factory system software. By the way, what do you think where to trying to get it? Even you could not get support? I tried to contact Winca/Roadnav, but they did not response until now.

check with the russian model farCar I used its firmeware and MCU for my S300 and it was exactly the same. https://far-car.ru/garantiya_i_servis/
Unfortnatly I can't find any official firmware for Winca to update with. If any has it please share.

I have winca s300 and I have a problem with the mcu and I contacted winca and did not find a response and I want that mcu "zhan_53_c63l_g32190000d5" ver:1.0