Related
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Edit 5-Nov-2016, some FAQ:
Unpacking and repacking a rockchip ROM
Adding root to the ROM
Make it easy on yourself: ROM kitchen by da_anton
it starts video playback on boot. its not your rom, its the original as well, but weird.
---------- Post added at 07:41 AM ---------- Previous post was at 07:28 AM ----------
What tool you use to unpack rom?
Hi!!! Thanks for your work I'm going to wipe my ROM (I think there's some garbage after deleting Kingoroot) and put your ROM into my unit.
Great work
wskelly said:
For those that want a rooted stock ROM, without having to use Kingoroot, here you go.
jy190_rooted.zip
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
I've made two harmless changes to stock that you can change after flashing:
Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
Default Timezone is America/Detroit instead of China/Shanghai (same reason as above)
Prerequisite: Probably you will want to get the JY1.90 ROM from Joying directly, and update your HU with it because Joying includes an updated MCU image. I am *not* including the MCU image here because one of you is going to flash it onto the wrong hardware and brick your HU. I am only providing the ROM image, just like Malaysk does.
1. To install, first extract dupdate.img from the zip.
2. Copy dupdate.img to the root directory of a USB stick or SD card
3. Enter recovery, flash. If coming from stock you can probably flash without clearing all. If coming from Malaysk you might want to clear all first.
Understand what you are doing. Read Malaysk's thread about flashing, and read all of his warnings, as they all apply here.
Thanks to Malaysk for his ROM and all of the other tweaks he's done. If you want something beyond stock, try his.
Thanks to Joying for making this unit, there is nothing else like it on the market. As long as continues to work, I'll continue to be very happy with it.
Thanks once more to Joying for being (so far) pretty friendly to the DIY/modding/hacking crowd. I've never seen a company so open with flashing and modding, and continuing to update their own firmware for their customers. It is nice to see, so let's not abuse it. Mod responsibly.
There won't be any additional support from me. This is a rooted stock ROM, that's it.
Click to expand...
Click to collapse
wskelly said:
This is the JY 1.90 ROM + SuperSU installed, no garbage, no Kingoroot or whatever. I took the 1.90 Joying image, unpacked it, manually installed SuperSU (basically duplicating what the SuperSU installation script does), and repackaged it. It is running on my Jeep HU right now and SuperSU is fully functional.
Click to expand...
Click to collapse
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
da_anton said:
Great idea and thanks for the work! Thought of that myself! Could you perhaps tell me how you made that ROM? How did you manage to extract the img file and put everything back together? Did you use imgRePackerRK? Thanks!
Click to expand...
Click to collapse
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
wskelly said:
[*]Default Bluetooth device name is "JoyingJeep" instead of "CAR-KIT" (tired of changing it manually to the name I want)
.
Click to expand...
Click to collapse
hey I also named my Joying that
This is great! If I hadn't install the Sept Joying image last weekend, I would have totally installed this. Thank so much!
One suggestion though, if you decide to make another one at some point, you might want to install the xposed framework (I did this via flashfire) and appsettings 1.13. I can provide a link to each, that are known good, as the 'regular' framework and App Settings 1.10 (from xposed directly) doesn't work. I know it's designed as 'stock' but at minimum the framework just makes sense, I think.
wskelly said:
Yes, I used imgrepackerrk on Linux. After dumping the contents you are left with more img files. These are all block storage. In Linux, it is possible to mount these img files and manipulate their contents just like any block device.
Afterward, you can repack everything again with imgrepackerrk.
Sent from my Moto G using Tapatalk
Click to expand...
Click to collapse
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
da_anton said:
Thanks! Great work! Got it working today and made my first ROM based on yours. I removed some apps which are just wasting RAM and I don't need.
Click to expand...
Click to collapse
Awesome! Keep tinkering! This is how everyone gets started. ?
Sent from my Moto G using Tapatalk
Hi !, I'm not 100% sure but try to change radio reg at the Factory options.....
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Yes. Earlier post
mlkemac said:
Thank you for the work!
Question, how did you extract the img file. the typical utilities i use for android seem to be incompatible with this system image.
Found!
http://forum.xda-developers.com/showthread.php?t=2257331
Click to expand...
Click to collapse
See post #5.
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
da_anton said:
@wskelly could you maybe tell me exactly what you did to include SuperSU in ROM? I would like to integrate it into the ROM builder scripts here https://github.com/da-anton/MTCD_ROM-cooking. Would be great!
Click to expand...
Click to collapse
Yes, I kind of did already. If you look into the SuperSU thread here in Xda, you can get the latest version. Inside the flashable zip, there is a dir
META-INF/com/google/android
Then you'll find install-binary, which is actually a shell script. (this directory structure is the actually standard format for recovery-flashable zips)
In the shell script the author goes into great detail about what his where and with what permissions.
The big caveat for your efforts is that we have sdk 22 (5.1.1) and things are different depending on which version of Android you have (some Joying units are KitKat). The installation script handles every version of Android so far and this is all detailed by the author in the script.
Another warning: the installation script runs another binary tool that will "convert" wine of the binaries to "pie" executables. Because the ones I want are compiled for ARMv7, and I'm on Intel modding the ROM, I'm not sure if I can run that tool with confidence. So, I took the su binary files from Malaysk's ROM, which I know work. This is why SuperSU tells you that the binary is out of date right away. You must follow the chaos and chcon instructions in the installation script exactly. (I think malaysk is missing some of those steps because his rom would always fail to update su via the app)
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
I'm on my phone so hopefully spellings and the path names aren't too messed up.
I'm curious if removing the recovery.img and bootloader.img if it will still flash. Flashing those two partitions every time is asking for trouble eventually.
Sent from my Moto G using Tapatalk
pinkpanther28 said:
Greetings,
I am very new to these head units got my first one 2 months ago. been reading and learning a lot here. I have a KGL and installed this rom, its working great and its a bit visually different then the one's I have used for KGL. Glad to know we have options on roms and tweaking we can do.
I do have a small annoyance that I hope some one can help me with. I had hoped this rom would solve it but unfortunately not. The radio RDS feature, on all the roms I have used the problem stays the same. I am in the US and its set to Europe RDS PTY code. So I can see the all the station and song information but the Station genera is wrong. like country music stations listed as pop and rock stations listed as Drama. I figure their is a file that the radio ap references to know what label to use and display. I have searched for this file or ap location but have had no luck in finding were it would be located. Can anyone point me in the right direction on how to possible fix it so the radio displays the correct station type? Sorry to hijack a thread but my post count is not high enough to allow me to start my own. search has not helped. Thanks all.
Click to expand...
Click to collapse
Yea, this post is *completely* off topic and deserves its own thread. Maybe someone here will start a new thread for you.
Sent from my Moto G using Tapatalk
wskelly said:
So my recommendation is to look at the installation script, and follow the instructions in the comments section which are very detailed about what goes where. Except instead of using SuperSU installation files, you should take the files from my ROM. **You may try to use the files from SuperSU, but likely you will get a bootloop (because of the pie format issue), worth trying though. Also worth trying the pie conversion on Intel.
Click to expand...
Click to collapse
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
da_anton said:
OK. I created a module in the MTCD ROM builder for that. How exactly did you set the links without chroot? Maybe you could have a look a my version and could tell me if anything is missing :angel:
https://github.com/da-anton/MTCD_ROM-cooking/blob/master/modules/install_supersu.sh
Click to expand...
Click to collapse
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Sent from my Moto G using Tapatalk
wskelly said:
Awesome script! I was way too lazy to do this but I wished I had it! ? I actually started to mod the SuperSU script to root the local ROM but I just got lazy.
To link without chrooting you can use the -f (force) option.
I am on my phone and didn't get to look at the whole script yet but you could just try to root stock and see if it works?
Nice job!
Click to expand...
Click to collapse
Thanks! I already tried that and my unit is stuck in a boot loop now. Guess it's because I forgot to include the binary from Malaysk and used the official one instead will try the next days to fix my 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!
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
I have an old Samsung phone running on Marshmallow. I want to build android and flash it on the old phone. Many take Google Pixel to show how to do it and say it’s not possible to do it on non-Google device. Is there a way to get around it?
KrishnaD3V said:
I have an old Samsung phone running on Marshmallow. I want to build android and flash it on the old phone. Many take Google Pixel to show how to do it and say it’s not possible to do it on non-Google device. Is there a way to get around it?
Click to expand...
Click to collapse
Sure. Here's some reading material on how to build a custom Android operating system. https://www.androidauthority.com/build-custom-android-rom-720453/
If it all seems too much, you could instead install a custom Android operating system prebuilt by others. One such example is LineageOS which has its own website and installation instructions.
You will have to first determine the exact model and sub-variant of your Samsung phone.
Then determine whether it is network carrier unlocked.
Then determine whether the bootloader is allowed to be unlocked (allow oem unlocking).
LineageOS Downloads
download.lineageos.org
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
KrishnaD3V said:
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
Click to expand...
Click to collapse
Depends on the the exact device model? (Go to settings =>About phone) (or in the dialler, type *#0*# then tap on 'version'). Then search the XDA forum for that device, then spend some time scrolling through the posts to find the info you're searching for. https://forum.xda-developers.com/c/samsung.11975/
*#0*# doesn’t give any option for version. So I thought to see in settings. What ‘version’ should I look for?
Go to settings =>About phone
Look for a code which which looks similar to SM-GTI9100
KrishnaD3V said:
Thanks for the reply
Do you know how to obtain proprietary binaries for a device?
Click to expand...
Click to collapse
Either extract them from phone's Stock ROM file, or pull them out of phone.
zpunout said:
Go to settings =>About phone
Look for a code which which looks similar to SM-GTI9100
Click to expand...
Click to collapse
It’s SM-A800I running android 6.0.1 . And it’s not on the list that you sent. What can I do?
jwoegerbauer said:
Either extract them from phone's Stock ROM file, or pull them out of phone.
Click to expand...
Click to collapse
I do have the stock rom file but I can’t find guide on how to do so. I found a video where person extracts it from lineage os. Is the process going to be the same? And by the way does it matter which version of stock rom I have because the phone came with android 5 and I updated it to 6 with official update.
KrishnaD3V said:
It’s SM-A800I running android 6.0.1 . And it’s not on the list that you sent. What can I do?
Click to expand...
Click to collapse
Yeah, there's not much development on that device, I read somewhere that Samsung supposedly never released the source code. It is hard to search for, but I did find this link: https://forum.xda-developers.com/t/...al-cyanogenmod-13-for-galaxy-a800f-i.3344081/
I did find out that the nickname of your SM-A800I model is "a8hplte" which might help you in search engines.
Looks like a dead end to me though.
KrishnaD3V said:
I do have the stock rom file but I can’t find guide on how to do so. I found a video where person extracts it from lineage os. Is the process going to be the same? And by the way does it matter which version of stock rom I have because the phone came with android 5 and I updated it to 6 with official update.
Click to expand...
Click to collapse
The so-called binary blobs are kinds of hardware drivers, you can't simply extract them of a Custom ROM, you have to extract them from a phone's original Stock ROM, as I told you this already earlier.
These binary blobs typically are found under /vendor/lib(64), some also under /system, /etc and /bin.
Most of the blobs are executable files or libraries, run as independent services on phone's boot.
jwoegerbauer said:
The so-called binary blobs are kinds of hardware drivers, you can't simply extract them of a Custom ROM, you have to extract them from a phone's original Stock ROM, as I told you this already earlier.
These binary blobs typically are found under /vendor/lib(64), some also under /system, /etc and /bin.
Most of the blobs are executable files or libraries, run as independent services on phone's boot.
Click to expand...
Click to collapse
Thanks for the info
zpunout said:
Yeah, there's not much development on that device, I read somewhere that Samsung supposedly never released the source code. It is hard to search for, but I did find this link: https://forum.xda-developers.com/t/...al-cyanogenmod-13-for-galaxy-a800f-i.3344081/
I did find out that the nickname of your SM-A800I model is "a8hplte" which might help you in search engines.
Looks like a dead end to me though.
Click to expand...
Click to collapse
Not so beginner friendly I guess . I try my luck extracting the blobs as described by
jwoegerbauer.
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