yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Hammerhand.17:
Ok, perfect then. I guess then I won't have any problem flashing these firmwares because it's a vertical unit; I know how to find joying firmware (in its blog), but I don't know where to find I find T'eyes sspro firmware; and, if I can flash any of them, is there a difference? Any advantage or disadvantage? Will they erase my unit? and last but not least, would my car specific settings (Ford Mondeo here) be kept?

How would I modify the settings you adviced?

I used you backup indeed, and made a oem backup as well.

About the ringtone, I used your software and used a mp3 ringtone, but then sound of ringtone stopped working.

Sorry if there are a lot of questions.

PS. Ok, a last question: can any firmware be rooted with magisk through the script that writes patched_boot.img?
[FYT Android Head Units] surfer63:
Starting from top to bottom.

I can't remember whether you mentioned you had a vertical unit, but if so I forgot.

As far as I know T'eyes does not have vertical units, so they are not suitable then.

The Joying firmware will not erase your unit, although it is a one-liner in a config file if you prefer that (post 1 of this thread).

I don't know whether your Ford Mondeo settings will be saved, but make a sreenshot of your current CAB-bus settings. It is FYT having the same software, so you should be able to set it back.

Modifying settings is described in several posts and the basics are described in post 1 and 2 of this thread. In fyt.prop change ro.build.fytmanufacturer=43 to your ro.build.fytmanufacturer=1. In the config.txt change the sys.fyt.bluetooth_type=1 to your sys.fyt.bluetooth_type=0.

ringtone: I'm lost there. I just tested again and for me it works. Your unit being a FYT compatible, and looking at your HWgetinfo, it "should" work. I do not know why it doesn't. Something with length, size, kbps, cbr vs vbr?

Theoretically any firmware can be rooted with Magisk as long as you can get a copy of the boot image and are able to write it back.
[FYT Android Head Units] tchleb:
The firmware for the teyes spro and many informations you can find at 4pda.

The translation works fine with Google.

https://4pda.ru/forum/index.php?showtopic=927325
[FYT Android Head Units] Hammerhand.17:
Ok, so I should take firmware for manual rotable units, right?

I'm pretty sure that can-bus settings are not editable in my unit; I mean, I can see them but can't edit them.

I will try again with the ringtone, and will try with another shorter mp3 file.

Thanks.

Ok, will give it a try, but [MENTION=2550900]surfer63[/MENTION] told me that they will not be compatible because of my screen position (vertical).
[FYT Android Head Units] angelparras:
It is possible to change the steering wheel key functions for opening spotify and waze with src button?
[FYT Android Head Units] surfer63:
Don't cross-post the same question to several threads. It is highly annoying and if people answer you, the info is completely shattered over this forum.
[FYT Android Head Units] angelparras:
Sorry, i had too much tabs opened and i didn´t noticed you were the same person.
[FYT Android Head Units] gamer765:
Removed since it doesnt work. Had to borrow a car to test it since I got no feedback.
[FYT Android Head Units] bixxewoscht:
Thank you [MENTION=2550900]surfer63[/MENTION] for giving the Intel SC9853i Head Units some love.

I also have one of those units from sinosmart. It is a vertical screen/ tesla style one with Android 10.

Will these modded apps work on the different screen size too? I like the radio mod better than my built in app.

Also if I want to install modded apps do i need to look after a special firmware or do they work on all firmwares?

I just got some new firmware files from sinosmart.

Last question, I read through this thread but not all pages, did you guys find a way to make the MODE SW-key go only through user specific apps?

I have something like changing the audio source in mind: Radio -> Spotify -> Poweramp.

Next week I'm gonna put the unnit on my table and try to optimizy it to my needs, probably with fcc launcher if it works. Until then I'm trying to gather as much information as possible to keep the process (hopefully) kind of short, so I can put the HU back in my car soon.

Thanks in advance.
[FYT Android Head Units] surfer63:
And Android 10 and different screen layout. I'm afraid the different screen layout for "normal" Joying app is the biggest issue. As you are on Android 10 you can't use any of the main server mods.

That will not work. 2-3 days ago I explained that to AngelParras in one of the other threads.
[FYT Android Head Units] xadamadax:
Disregard
[FYT Android Head Units] rackxp:
[MENTION=2550900]surfer63[/MENTION] is it possible to flash a 1280x720 unit with a non joying rom?

I want to try and strip the slink from the unit so I can try and use carlinkit car play dongle to try and get better resolution on the car play app.
[FYT Android Head Units] gamer765:
You can flash non joying rom on your unit, but keep in mind the supported resolution of the rom you're flashing. Make sure it supports 720p resolution or you'll never see the launcher screen. I believe you can just install carlinkit on your existing rom and just dont install ZLink. It's not completely possible to strip ZLink from the FYT rom since its partially built-in to the rom, specifically in com.syu.ms. I found some ZLink stuff in it when digging into the Teyes DRM scheme for their launchers. On that note, while looking into the Teyes launchers, it looks like com.syu.ms plays a role in the DRM process. I've been probing it little by little, and found the launcher to be looking for the following 2 props: "ro.fyt.hongfan_key" and "ro.fyt.hongfan_appsecret". And a request if anyone can. Anyone that has a 9 inch IPS screen model with 1024*600 resolution and is rooted, if they could backup their fytdata partition. Also if any Teyes users here can do the same, maybe some of the Teyes props can be found there.
[FYT Android Head Units] gamer765:
So quick update, the Teyes launcher activation info is located in the fytdata partition, specifically /dev/block/platform/soc/soc:ap-ahb/c0c00000.sdio/by-name/fytdata. Teyes users, do not publicly post your fytdata partition info, if you wish to share it, for research purposes, please do so by PM to me. This partition appears to be holding lots of proprietary info that the fyt resellers are refusing to provide us, even if for legitimate purposes. In this partition theres lcdconfig configurations, activation keys for reseller proprietary features, etc. There's a few attack vectors for the DRM, we can either patch the apps and manually unlock proprietary features 1 by 1, patch up libsyu_jni.so only so it'll always return true on validation requests, thus avoiding the need to manually patch apps and having the required data in the fytdata partition. The final approach would be to keygen an activation code and store it in fytdata so it'll always activate without mods.
[FYT Android Head Units] gamer765:
I'm preparing a quick patch to the syu_jni and will post it soon. Fully untested since I don't have a 1024*600 device to test on Teyes launcher, unless anyone has a working configuration to revert a 1280*720 screen back to 1024*600.

Update: Did a quick patch in IDA, remove .x64 and .x86 extensions and place in appropriate lib folders. Dont forget to make a backup. Best tested with Teyes unmodified launchers.

Removed due to lack of interest/testing.
[FYT Android Head Units] gamer765:
Cracked Teyes DRM.
[FYT Android Head Units] xadamadax:
The ones that say Android 10 aren't really Android 10, they're still Android 8.1 in my experience. They just change it to say 10 and add a different boot image. Same goes for the sc9583i units i have seen that have Android 9 advertised as the os.

All the exact same rom.
[FYT Android Head Units] Guyzer73:
Evening All,

Firstly thanks for all the hard work, been busy and haven't been here for a while.

So I tried installing Surfer63's modified radio app as per post 3 and it all seemed to install, unfortunately when I selected radio there is a scaling problem, namely the lower part of the app is missing. Now I suspect this is because I have a 1280x480 res screen and the app is perhaps scaled for 1280x720?

Is there anyway to set the resolution of the radio, I presume not?

As such I assume to rectify this (I tried the Radio ORG apk as well) I'll need to download my current firmware (Sept 19) decompile the Allapp.pkg and then extract the radio apk out and then repackage only that and flash it in the normal way. This way would avoid fresh install and wiping data.... Am I right in this logic?

While I'm at I might revert to the stock mainserver from the Nokill main server and play around with the skipkillappp.prop instead.

Cheers for any feedback.

Guy
[FYT Android Head Units] gamer765:
Correct, you need to reflash the radio apk back to your stock apk from the latest rom.
[FYT Android Head Units] dominicanodcora:
keep going. i like it.

---------- Post added at 08:11 PM ---------- Previous post was at 08:04 PM ----------

i searched for camera and nothing came up so i will ask. I switched from Dasaita PX5 to the latest Joying SC9853i on my Jeep Wrangler and 1 thing i miss is the FCAM application. It's function is to view rear camera while driving forward to see what you are towing. i tried extracting the fcam app but when i try to install it on my joying it says app not installed. can someone help?
[FYT Android Head Units] jhha:
I want to replace/update gps.conf file in /system/etc/ to get a better GPS reception. (since no root yet) :)

Can someone direct me where to put it in Allapp.pkg to get it work. :o

Or maybe someone can make it for me??? ;)
[FYT Android Head Units] Hammerhand.17:
Well, I found some problems. Somehow, touch screen started to act weird (changed vertical to horizontal and so on), so I tried to apply latest update (2019-11-28, because my unit is vertical adn this one is marked as "rotatable"). Touchscreen works fine (seems that it's not a hardware issue), but still can't rest, because:

- Everything is 90 degrees rotated, and I can't find how to rotate to vertical.

- Climate control appears when I switch the car on, but are unresponsive (mine were touch buttons, because I have no climate control buttons in my car).

So, to sum up, I thought to restore my backup, created with the scrip attached ("Full backup") with the next script ("restore backup"), but some of the partitions show "fail" and radio doesn't work. Could you please help me?
[FYT Android Head Units] surfer63:
I can't see the image as it is not found when I click on it.

The first thing I would try is to flash the firmware again. You do not mention whether you alredy tried that.
[FYT Android Head Units] Hammerhand.17:
Red lines are the normal output, finished with "fail".

I can't flash my original firmware because the seller didn't give me. My only chance to go back to my "stock" is restoring the backup

Enviado desde mi ONEPLUS A6013 mediante Tapatalk
[FYT Android Head Units] surfer63:
I only see the thumbnail, but when I click it, the forum mentions "not found". Please upload again. I have no idea which partions fail.

I did not create the restore script and I did not check it either.

The first thing I now see are the lines:

printf "write secvm.raw.img to partition /secvm ...."
dd if=/dev/block/mmcblk0p7 of=/storage/sdcard1/secvm.raw.img

This should be:

printf "write secvm.raw.img to partition /secvm ...."
dd if=/storage/sdcard1/secvm.raw.img of=/dev/block/mmcblk0p7

You might try to restore again, but if multiple partitions fail you have an issue.

Note that you need to take the original secvm.raw.img you created, and not the one already on your usb-stick as that one has been overwritten.

Possible next step (if restoring fails again): Can you still flash the Joying software, even though rotation and the airco notification is not good?

If so, you need to share your zipped system.img and zipped oem img via Google drive, Onedrive, mega nz, or something else.

It should contain the specific settings for your unit. If you can flash the Joying firmware, we could then make an update script to "reinstall" the specific settings from the backup you made for your unit.
[FYT Android Head Units] Hammerhand.17:
Ok, I have tried to restore again, and several partitions give error:

recovery-resource.dat

oem.raw.img

I'm going to share a folder with videos and screenshots of the process (is very fast, so I took screenshots from the video): https://drive.google.com/drive/folders/1o5x2lcHJ9adsipdcK1ovTFxOjSk7d6Oq?usp=sharing

I have been able to apply update again, and so is why I uploaded system and oem too.

The *.img files I used are those created throught the backup script.
[FYT Android Head Units] surfer63:
oem is absolutely necessary.

Your drive access is protected so I sent you an access request
[FYT Android Head Units] Hammerhand.17:
In fact, I wrote oem restore line myself, as it wasn't in your script. Maybe I did it wrong.

Sorry for the access not granted
[FYT Android Head Units] surfer63:
No, you did it correctly. (and like mentioned: I did not write the restore script).

The reason why the following command fails, is quite logical after all:

printf "Now copy the recovery data file from /system/etc/ ...."
cp /storage/sdcard1/recovery-resource.dat /system/etc/

The file is restored to the raw partition, but that probably only works after having made the raw partition read-write, as it is read-only in this script.

I would have made that error as well. And even if it would have worked: then the raw image gets restored and would have overwritten it again. But that restore fails as well.

The most important partitions being oem and raw are failing.

I will have a look today.
[FYT Android Head Units] Hammerhand.17:
Thanks a lot. My knowledge doesn't go further
[FYT Android Head Units] surfer63:
There is no gps.conf on our systems. It is all programmed into the system apps.

So why do you think adding a gps.conf (from your phone?) would improve it?
[FYT Android Head Units] mastrv:
Perhaps they were hoping to do something similar to what happened on my smartphone.

I updated the gps.conf on my phone to improve the gps functionality. I'm not sure the reason but it's related to NTP and AGPS. Changing the time server to point to itself, 127.0.0.1, improved the response time and so allowed the gps to locate/lock quickly. On my Samsung Note3, it would many times not provide a gps lock in an adequate time, if at all, for many applications and after the change, it did.

Found info at: https://xdaforums.com/galaxy-note-3/development/rom-devs-fix-gps-users-ntp-to-localhost-t3531891
[FYT Android Head Units] Hammerhand.17:
Ok, so I've seen in dev_listing I used from hwget the following lines:

lrwxrwxrwx 1 root root 21 2020-06-14 13:43 boot -> /dev/block/mmcblk0p25
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 cache -> /dev/block/mmcblk0p27
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 chargelogo -> /dev/block/mmcblk0p13
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 fytback -> /dev/block/mmcblk0p33
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 fytdata -> /dev/block/mmcblk0p32
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_deltanv -> /dev/block/mmcblk0p21
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_fixnv1 -> /dev/block/mmcblk0p14
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_fixnv2 -> /dev/block/mmcblk0p15
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_ldsp -> /dev/block/mmcblk0p23
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_modem -> /dev/block/mmcblk0p20
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_runtimenv1 -> /dev/block/mmcblk0p16
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_runtimenv2 -> /dev/block/mmcblk0p17
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 l_tgdsp -> /dev/block/mmcblk0p22
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 logo -> /dev/block/mmcblk0p12
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 misc -> /dev/block/mmcblk0p4
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 miscdata -> /dev/block/mmcblk0p2
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 mobilevisor -> /dev/block/mmcblk0p9
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 mvconfig -> /dev/block/mmcblk0p8
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 persist -> /dev/block/mmcblk0p18
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 pm_sys -> /dev/block/mmcblk0p24
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 prodnv -> /dev/block/mmcblk0p1
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 recovery -> /dev/block/mmcblk0p3
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 secvm -> /dev/block/mmcblk0p7
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 system -> /dev/block/mmcblk0p26
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 trustos -> /dev/block/mmcblk0p5
lrwxrwxrwx 1 root root 20 2020-06-14 13:43 trustos_bak -> /dev/block/mmcblk0p6
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 uboot -> /dev/block/mmcblk0p10
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 uboot_bak -> /dev/block/mmcblk0p11
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 uboot_log -> /dev/block/mmcblk0p31
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 userdata -> /dev/block/mmcblk0p34
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 vbmeta -> /dev/block/mmcblk0p29
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 vbmeta_bak -> /dev/block/mmcblk0p30
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 vendor -> /dev/block/mmcblk0p28
lrwxrwxrwx 1 root root 21 2020-06-14 13:43 wcnmodem -> /dev/block/mmcblk0p19

In the restore script, OEM is restored to /dev/block/mmcblk0p33, which, in my unit corresponds to fytback (and I don't see any "oem" partition here). Maybe this is the reason that I am not being able to restore? Maybe there is a way to use the restore script and then write the content of my OEM backup to the one in the unit?
[FYT Android Head Units] surfer63:
I don't know. I see also other partitions unknown to me (or maybe it is just another name).

I have been a bit busy this weekend with releasing (other) software.

I think I will create a new Allapp.pkg for you together with some config files to flash, to make your unit as "original" again as possible.
[FYT Android Head Units] Hammerhand.17:
Thanks a lot. The A/C control is a very big issue for me. Tell me if you need any other file, please
[FYT Android Head Units] surfer63:
Only for Hammerhand.17! Do not flash to your Joying!

Unzip the linked zip file to a USB-stick or SD-card.

It should install all original apks and all original configuration files from your system.raw.img and oem.raw.img.

From Mega NZ: https://mega.nz/file/tRlhWbBR#fFeb_dPUtXHsV0QD_MfLw4z463uvwZ4w3tNpp0RFDpM

If it doesn't give the wanted/desired result, I might need your vendor.raw.img as well.
[FYT Android Head Units] Hammerhand.17:
Ok, I tried it twice, no results.

First attempt: with joying update installed, it does restore the settings page (it's like in my unit), but A/C control does not appear either; everything works fine, except for a message (something like "there is an internal problem with your unit". Then everything seems to work (except A/C control, like I said).

Second attempt: I restored my backup, then used your file to restore /oem & /system; script gives an error: "chmdo 0600 /system/build.prop fail!". Unit get stuck in "ford" logo. (maybe something to see with restoring /oem partition through my backup? Should I try it without this line and then apply your file?)

I have uploaded vendor.raw.img to the same link I provided.

Thanks for your efforts!!

Edit: I corrected chmdo to chmod, now it didn't return error, but the result is the same.
[FYT Android Head Units] surfer63:
Your own backup will not work correctly when restoring.

The

chmdo 0600 /system/build.prop

is a stupid typo. It should be

chmod 0600 /system/build.prop

.

It does not really matter for functionality. The chmod 0600 makes it "safer".

With regard to the Air Conditioning: Are you sure you selected the correct canbus protocol? If that is not correct you will not see the Airco either.

But it in that case you might not see open/closed doors/trunk either.

Note as well that Ford is one of the few brands where the Aircondition is 2-way. You can indeed modify it from the unit. Maybe that requires a special setting as well.

Finally: Did you modify the MCU firmware when flashing one of the total firmwares?
[FYT Android Head Units] Hammerhand.17:
I guess it is chosen in "car type select". Several options for "ford Mondeo" appears, I've tried all of them and none made a/c appear; with some of them, doors opening appears, in other don't (but, should I reboot after every test?; The functioning of the doors didn't need reboot).

Take account that my a/c control is in the touch screen (I have no buttons for it), but I can't see any option for it (and the Chinese translation to Spanish complicated it even more)

The only thing I did is flash the update from joying blog, changing in fyt.prop ro.build.fytmanufacturer=43 to my ro.build.fytmanufacturer=1. In the config.txt changed the sys.fyt.bluetooth_type=1 to my sys.fyt.bluetooth_type=0.

I don't know if it modifies the mcu firmware.

Edit: I attach several photos: first two are the info from my original firmware, last two the info from my current firmware. I can't see difference between mcu and can info:

https://m.imgur.com/a/Uft9WqU

https://m.imgur.com/rHEgvvg

https://m.imgur.com/xwHyvBa
[FYT Android Head Units] surfer63:
I see only 3 images.

The first mentions Android 8.0. So your first version was not an 8.1.0 after all. That could mean that this can't be correctly restored as the underlying Android version and drivers is different from the 8.1.0 version. I guess you now have some mix of both.

I guess that's why the oem and system img failed, and why the partitions do not match.

You might need a large, partial rewrite of /sys, /system and /vendor as well, and maybe more, and that is hard to do.
[FYT Android Head Units] Hammerhand.17:
No, this was changed by me manually, because your mod tool refused to install the no kill mod, but it was 8.1 for sure.

The first link has two images
[FYT Android Head Units] surfer63:
I'm a bit lost now. The vendor image does not really help. I will do a last check this weekend.
[FYT Android Head Units] Hammerhand.17:
Ok, un going to upload all my backup to the same location, just in case it could help you. I thank you again
[FYT Android Head Units] surfer63:
I had a system crash (running another linux from a usb-stick that crippled my system) and have to repartition/reinstall quite some software (Linux), and lost all my data. Of course I have 90% of my data backuped, which I now need to restore as well. But I do not have backups of your data (or of all of those other users delivering hwget_info.zips and other stuff).

I don't have time now to look at your issue as I now have other personal priorities.

Maybe early next week.
[FYT Android Head Units] Hammerhand.17:
Of course, I thank you anyway for all your efforts, and I hope you recover your stuffs. If you can take a look in other moment, it will be good, but first things first. Good luck!

Just a question: should I reboot any time I select another option in system settings, to see if A/C control appears, or is it useless?
[FYT Android Head Units] surfer63:
After setting it, you have to close the Settings program but then it should immediately work.

I'm back on track. I will take a last look tonight.
[FYT Android Head Units] Hammerhand.17:
Take a rest, I think I have found the original firmware in 4pda and I'm going to try it in a couple of hours.

Edit: I can confirm, don't lose more of your time. Now everything works fine, it seems horizontal units doesn't support touch control for climate.

Thanks again!!
[FYT Android Head Units] rackxp:
Is their any other firmwares that might support the 1280x720 other then joyings?
[FYT Android Head Units] xadamadax:
So, my partner came across the ~30gb of source code for these (~16gb compressed), just about to find somewhere to upload it and will share ? includes the code for all of the FYT apk's as well