Database Info

Is it possible to "download" software straight from the unit?

Hello everyone,
I would like to know if it is possible to somehow "download" the Android software from a MTCD unit?
Like how you use update.img to update the software, except in reverse. Is there any way to download a copy of the system image, preferably in a convenient, usable update.img form, from a unit?
Thanks in advance.

I don't know the answer, I also want to know!
+ The same question but for the mcu.img
Sent from my Moto G (5) using Tapatalk

Sould be possible with the stock HA ROM from dasaita.

[email protected] said:
Sould be possible with the stock HA ROM from dasaita.
Click to expand...
Click to collapse
HA ROM from dasaita - what's that? Never head of a manufacturer like that?
What I meant was is there a possibility of downloading the ROM from any Android MTCD device (KGL, KLD, MX, GS, whatever), in a re-usable form (such as update.img) to be used on another Android-based device?

Yes, HA has an OTA update function for ROMs but I am not sure if it works. When the last update came out I've tried to update but it showed me that there is no update available. So I had to update manually. I am not sure if it didn't work because I have a GS with HA ROM, if the update wasn't published via OTA or if this function isn't workning yet because it is new.
OTA MCU updates aren't available.

NaviPR said:
Hello everyone,
I would like to know if it is possible to somehow "download" the Android software from a MTCD unit?
Like how you use update.img to update the software, except in reverse. Is there any way to download a copy of the system image, preferably in a convenient, usable update.img form, from a unit?
Thanks in advance.
Click to expand...
Click to collapse
TitaniumBackup once you get it set up you can create a update.zip
As for the MCU when your done fixing your factory settings before you exit his export

Cid6.7 said:
TitaniumBackup once you get it set up you can create a update.zip
As for the MCU when your done fixing your factory settings before you exit his export
Click to expand...
Click to collapse
Do you have a specific configuration for TitaniumBackup that can be used?

bump

bump!

Android Radio update MTCD_KGL RK3188

Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z

Lollipop
piotr_waw said:
Hello,
I have a car radio on the Android MCU system version MTCD_KGL_V1.53a_1 compilation number rk3188-userdebug 27052016.
Can I update to a newer version of android, because it is 5.1.1 now?
On the forum I found MCU updates for KGL v.2.83. Where can I find a ROM for my radio.
I tried to update the MCU, but unfortunately I'm making a mistake. I do not know what I'm doing wrong. I downloaded the MCU from the site
https://forum.xda-developers.com/showthread.php?t=3246386
I copied to the card and changed the mcu.img file to dmcu.img. Unfortunately, it lights up the error.
I do not know if I should update the ROM first and then the MCU first.
Greetings Piotr Z
Click to expand...
Click to collapse
I have read that if you upgrade your android system to the newer version; something about the GPS maps will no longer work. Not sure but you might want to look for that.
I have the same system A-Media Auto, MTCD-KGL_v1.53a_1
I found a newer version KGL_10-20-2016_1.92a_4_dmcu.img but I can't get the Head to find the .img file
I tried the SD card in the slot, GPS slot and a USB cable. Still System Update cannot find the .img file. Frustrated I gave up.
I did find that the SYGIC maps works good with the unit. I didn't like the IGO that came with it and wiped the map SD.
I also loaded Car Launcher v2.4.074 which is more appealing.
The backup camera is kind of squirrelly, works when it wants to.
Thinking about getting a new head unit with a flat screen, no buttons and knobs, but not sure if I want to go with a name brand or pure android version.
Will try to insert an image of my unit but I am new at this. The image wants me to put in a http url
/home/pok1/Downloads/20190316_134105.jpg

Question Firmware update for ZHAN Andriod FYT compitable platform

Hi,
Is there firmware update for ZHAN platform with the attached specs. It is FYT compatible, can I install Joying FW instead where it has similar specs. Did any one try it?
Thanks

Hello,
I have this platform too.
Are you found any alternative rom?
Any alternative application for Radio? Bluetouth phone etc?

[email protected] said:
Hello,
I have this platform too.
Are you found any alternative rom?
Any alternative application for Radio? Bluetouth phone etc?
Click to expand...
Click to collapse
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.

mashrom said:
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.
Click to expand...
Click to collapse
I was afraid too update my radio, becaus I`m not android developer.
I`m Windows developer and c#
If you update some application can you write what application you modified and what bug resolved?
If you wont share my this apps?

mashrom said:
Hi,
I found some platfroms pretty similar to ours but not with the same name. Like Joying, Tyes, Witson, and FarCar. The one that is most similar from my point of view is FarCar. I didn't do a full flash for any of them because I was afraid that any of the functionalties will get broken for any reason. So, I was asking for anyone who did it and successed before doing mine. For the time being, I extracted some OEM Apps from Allapp.pkg and updated mine to resolve some issues and it was working.
Click to expand...
Click to collapse

[email protected] said:
I was afraid too update my radio, becaus I`m not android developer.
I`m Windows developer and c#
If you update some application can you write what application you modified and what bug resolved?
If you wont share my this apps?
Click to expand...
Click to collapse
I updated Winca app as it had couple of annoying bugs like AC every moment pops up on the screen with no reason, and the reverse Camera lines weren't moving with the steering. And updated the bluetooth app in a hope to get the OBD to get paired ,but it didn't unfortunatly and it made no change from the older one I had.

I knew that @mclaudio did already the firmware upgrade for ZHAN to Joying a while ago. Can you give here your experience with that tips and tricks and any malfunction you face?

mashrom said:
I knew that @mclaudio did already the firmware upgrade for ZHAN to Joying a while ago. Can you give here your experience with that tips and tricks and any malfunction you face?
Click to expand...
Click to collapse
It is not that difficult.
- do not update the MCU.
- Check your config.txt for sys.fyt.bluetooth_type. Joying uses sys.fyt.bluetooth_type =1, maybe yours is different. From terminal do: `getprop sys.fyt.bluetooth_type` and add that value to the config.txt.
- check your manufacturer id: `getprop ro.build.fytmanufacturer` and open the Joying allap.pkg and edit the fyt.prop, set `ro.build.fytmanufacturer` to `ro.build.fytmanufacturer=<ZHAN id>` (Joying is 43) and repack the Joying Allap.pkg. Now you can flash the Joying firmware.

surfer63 said:
It is not that difficult.
- do not update the MCU.
- Check your config.txt for sys.fyt.bluetooth_type. Joying uses sys.fyt.bluetooth_type =1, maybe yours is different. From terminal do: `getprop sys.fyt.bluetooth_type` and add that value to the config.txt.
- check your manufacturer id: `getprop ro.build.fytmanufacturer` and open the Joying allap.pkg and edit the fyt.prop, set `ro.build.fytmanufacturer` to `ro.build.fytmanufacturer=<ZHAN id>` (Joying is 43) and repack the Joying Allap.pkg. Now you can flash the Joying firmware.
Click to expand...
Click to collapse
Thanks Boss seems easy.
I got the parameters values of mine it is ro.build.fytmanufacturer=53 and sys.fyt.bluetooth_type=3. I will give it a shoot wish me luck
One another question about sys.fyt.bluetooth_type. I changed it to 0 as you described in a your post and finally the OBD is connected. Now phone is unable to connect to the orignal OEM phone dialer and the phone dialer is not searching any more. Returning back to the default 3 in my case dialer works again but the OBD not seen anymore. Is that normal and happening to all and is there a way to connect to either OBD or the phone without changiing the parameter every time?
cheers,

mashrom said:
I got the parameters values of mine it is ro.build.fytmanufacturer=53 and sys.fyt.bluetooth_type=3. I will give it a shoot wish me luck
One another question about sys.fyt.bluetooth_type. I changed it to 0 as you described in a your post and finally the OBD is connected. Now phone is unable to connect to the orignal OEM phone dialer and the phone dialer is not searching any more. Returning back to the default 3 in my case dialer works again but the OBD not seen anymore. Is that normal and happening to all and is there a way to connect to either OBD or the phone without changiing the parameter every time?
Click to expand...
Click to collapse
I don't know. I also (or actually finally) bought an OBD dongle around Christmas time. For me it connects and a few seconds later it disconnects.
And to be honest: I completely forgot about that 'sys.fyt.bluetooth_type' property myself for OBD. I will start testing the coming days.

Please you have any mod or rom for my model?
If yes - can you share it ?

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

waleed atef said:
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
Click to expand...
Click to collapse
I don't understand what you want.
You want that ""zhan_53_c63l_g32190000d5" ver:1.0"?
You hve it already as your screenshot shows.

I make wrong update another version and not working ... I need this version

waleed atef said:
I make wrong update another version and not working ... I need this version
Click to expand...
Click to collapse
What is wrong? Does your unit not work at all? Do you have erorr messages to share with us?

and the button not assign right

this mcu after wrong updated

waleed atef said:
View attachment 5897525and the button not assign right
Click to expand...
Click to collapse
This yellow bar means that your FYT layer does not correspond with your MCU. That does not mean that your unit need to be reflashed.
First try my scipt from my thread post #3: 3. Script to correct the fytmanufacturer id in the fyt.prop.
If you still have your original firmware check first for the manufacturer.id. If you don't have it then try first with value 53 which is for a Winca. However, Zhan is also 53.

surfer63 said:
This yellow bar means that your FYT layer does not correspond with your MCU. That does not mean that your unit need to be reflashed.
First try my scipt from my thread post #3: 3. Script to correct the fytmanufacturer id in the fyt.prop.
If you still have your original firmware check first for the manufacturer.id. If you don't have it then try first with value 53 which is for a Winca. However, Zhan is also 53.
Click to expand...
Click to collapse
I make upate from mcu update or another way .... thank you

I don't know make it ... Please help me

Question China FYT flashing to Joying?

Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.

Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
short answer, no. Note, MCU is not android.
You have latest mcu (53) = YIN. what is it you actually want or think the joying firmware will provide?
Suggest reading forums.

marchnz said:
short answer, no. Note, MCU is not android.
You have latest mcu (53) = YIN. what is it you actually want or think the joying firmware will provide?
Suggest reading forums.
Click to expand...
Click to collapse
Hi, so my issue is that the UI that it provided is not to my liking... i would want to change the UI but the seller told me that he have no idea how to do it. my friends model... same but 10 inch.... has the option in changing the UI.
In my Factory setting page... the only available UI is UI17. I was looking at other threads and was wondering if TS10 firmware works for my device. The UI that TS10 provides looks nicer.
Sorry... but i dont really understand much despite reading. IMO its just a hardware trying to flash with different firmware... and base on the similarity of the device... i fail to understand the complexity in it.... (Im probably wrong in this aspect)
P.S. Im totally new to this and is trying to digest....

I'm not sure if your firmware will allow it, but there are other launchers that can be installed from the Google Play Store. They will change the interface and many of them have different themes that you can switch to. You can view them directly on your head unit from the Play store. Here are a few:
CarWebGuru Car Launcher - Apps on Google Play
Car launcher with themes, widgets, music control, gps tracker, and customization
play.google.com
Car Launcher - Apps on Google Play
Launcher for use in the car
play.google.com
AGAMA Car Launcher - Apps on Google Play
Home screen for car multimedia systems for Android OS (30 day TRIAL)
play.google.com
After installing one or more of them, they may ask you to switch the default launcher when you run them. You don't have to. You can try them and if you don't like them, delete them. I believe if you go "home", if will go back to your original launcher if you didn't switch the default. When you go into the settings, under Apps, one of the options is to display and define the default applications for different functions. You can also change them there. I use CarWebGuru and it looks very different from my original launcher.
If anything goes wrong, as a last resort, you can always switch back to your original firmware.

Just out of curiosity, go to Google Play and look for "Fake Device Tester" and check if that is really an Android 10. I have an unbranded FYT in my car (vertical Tesla-style) and it's a fake.

I need firmware for this car stereo I don't know model and name can you tell me please? Where and how to download?

Tarz89 said:
I need firmware for this car stereo I don't know model and name can you tell me please? Where and how to download?
Click to expand...
Click to collapse
What did the reseller offer

Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
ido the same after that bluetooth and radio not working
dont do that
istill serach for solution for this problem and icant fix it

ali libya said:
ido the same after that bluetooth and radio not working
dont do that
istill serach for solution for this problem and icant fix it
Click to expand...
Click to collapse
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?

surfer63 said:
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?
Click to expand...
Click to collapse
Now every thing ok radio working
Only problem is bluetooth software or app now working
Give me messeage
Activation failed error 65535
Due u know any solution
Thnx again bro

surfer63 said:
You first should have read the documentation on this forum, including how to make a flashable backup of your unknown FYT unit before flashing it with something else.
And what did you do? Flashing the firmware or trying to upgrade your MCU with a Joying MCU (rule no. 1: Never ever do that !!!, and this is also rule no. 2 to 15)
Your flashed Joying firmware probably has in its config.txt the following line
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
The radio not working is probably due to a mcu firmware mismatch. Joying is type 43 (ro.build.fytmanufacturer=43). Your unit is probably 0 or 116, or some other value. Do you still have your orignal firmware with the original fyt.prop?
Click to expand...
Click to collapse
First of all iwant to say thanks
U are hero
Bluetooth working now
Tank u again

surfer63 said:
Code:
sys.fyt.bluetooth_type=1
I guess your unit needs either 0 or 2.
Click to expand...
Click to collapse
Hi. Can I access this directly in my unit?
Or do I need to reflash with my backup of unknown FYT unit. I've been getting the activation failed error 65535 when I bought it.

notJimz said:
Hi. Can I access this directly in my unit?
Or do I need to reflash with my backup of unknown FYT unit. I've been getting the activation failed error 65535 when I bought it.
Click to expand...
Click to collapse
Install a terminal app and give the command in the terminal:
Code:
getprop > /storage/sdcard1/properties.txt
Copy the "properties.txt" to your pc/laptop and check the *fyt* lines.

Did anyone find a fitting mcu for this unit ? I have the same problem

Selvinlyh said:
Hi. I bought a Chinese FYT head unit that look exactly like Joying...
Was wondering if it's possible to upgrade it's MCU to a Joying one.
I tried downloading Joying firmware however when I plugged into my head unit... It doesn't work like Joying where it automatically update the firmware.
The zip file from Joying consist of a big zip file.. after extracting, there are some folders together with another big zip file.
I went to settings, factory, and selected MCU Upgrade .. but it doesn't recognize any of the files within.
If possible I hope this community could teach me how to upgrade my MCU....
Thanks in advance.
My unit information can be found in the attachment. PS. Not sure why XDA don't let me attach image.
Click to expand...
Click to collapse
I was able to flash Joying software. posted some notes before, see if it helps:
Carlink change DPI?
I recently bought FYT based head unit that comes with wireless car play (reseller called Xima). the app for wireless car play is Carlink. default resolution is about 480p. the Carlink app setting page doesn't give much options beside noice...
forum.xda-developers.com

Xtrons PQS Series/PX6 1280x480 Android 10 image (PX6) needed

Hey all,
does anybody have an Android 10 firmware image for the Xtrons PQS series head units or for a PX6 in general with a screen resolution of 1280x480? Xtrons just sent me an update.zip but no full image to restore my HU to a working state.

If you have the correct firmware installed, then maybe the resolution was changed during the previous installation, read the last page from message #89, here I explain how to change the resolution using the dmcu.ext file, in message #98 the owner is xtrons and for a resolution of 1280x480, he used screen :11. During these attempts, it is important to enter recovery, if you do not have this option and the screen goes black, then there will be a problem with the corrective update. First, save the current factory settings in the dmcu.cfg file. Factory settings/ EXPORT/ save dmcu.cfg to external storage, in case of problems with it, update from recovery MCU, all settings will return to their original state. I am not responsible for any mistakes, you do everything at your own risk.
MTCD/E MCU firmware modification
At the beginning: Flash/Upload modified MCU firmware can brick unit !!!! (in particular from an unknown source, untested etc.) Maybe this thread will not only affect the modification of the MCU firmware. I hope that this will help us understand...
forum.xda-developers.com
There are other numbers for 1280x480 in all-display-timings.txt that you can try. Open the dmcu.ext file in notepad and change the number:
Яндекс
Найдётся всё
disk.yandex.ru