yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Tony2k:
I have a FYT 1 with latest update and I like to add another launcher but I don't know wich SDK I need to choose. Anybody could tell me please?
[FYT Android Head Units] LLIyT_HuK:
Is it possible to make the root rights check normal, and not check for the presence of SuperSu? To make FMC work with Magisk.
[FYT Android Head Units] mariodantas:
Did you test the apk ?, shoud work with magisk, if yes, please advice and I'll release it !
[FYT Android Head Units] LLIyT_HuK:
Sorry, I had a lot of work, I'll try to check it today.
[FYT Android Head Units] mariodantas:
Take your time fellow !
[FYT Android Head Units] Ragpuss:
Hi guys and thank you for the firmware releases which work very well.

I have a Chinese LHD Tesla style head unit 7862s which I chopped a little to fit into my RHD Jaguar XF,

everything seems to work well but the dual heater temperature controls work for LHD still, so I have to adjust from the passenger side to get both to move together.

Is there a way to have this swap over ? I'm guessing it will be in my allappupdate.bin file or the CanBus file but I don't know how to find that section (if it exists) or how to edit it.

Can anyone help with this or is there an allappupdate.bin file for a Jaguar XF 2014 right hand drive that I can use ?

I have been trying to find one but with no luck so far.

Thank you for any help.
[FYT Android Head Units] surfer63:
In Settings -> Factory -> Original Car Agreement, there is a setting "Drivers Door position ( left / right drivers position )".

Maybe that might work on your heater as well.
[FYT Android Head Units] Ragpuss:
Thanks for the reply,

I tried that, unfortunately the heater stays the same way around :(
[FYT Android Head Units] mariodantas:
Many thanks to @LLIyT_HuK who is testing my apk (that will be) capable of coupling with magisk rooted kernels !
[FYT Android Head Units] Ragpuss:
Thanks for the reply,

I tried that, unfortunately the heater stays the same way around :(

I think it must be a setting in the CANBUS but I have no idea how to get the file or edit it :(
[FYT Android Head Units] segu45:
I have installed the version for 8581 for my new multimedia. It has been installed and upon restarting I got the message "encryption IC authentication failure code 2". Could someone tell me why he says this? thank you.
[FYT Android Head Units] faria:
Have you tried this yet?:

https://xdaforums.com/t/general-fyt...-q-a-mods-tips-firmware.4396339/post-86349165
[FYT Android Head Units] LLIyT_HuK:
Errors in the status bar are different.

"UI and MCU does not match" - change the identifier in the config.

"Plugin serial port/dev/ttyS1 was used" - disable BSP Serial Debug in developer settings

"Encryption IC authentication failure CODE :2" - return native MS.apk
[FYT Android Head Units] aiui:
Hi, @mariodantas I was looking at your website and I saw something called by you (Upgrade Bundles) maybe because I don't have much experience but I don't know what it is or if it matters to install.

I still searched the post but didn't find anything on the subject.

thanks
[FYT Android Head Units] mariodantas:
Just download them and read the instructions inside the ZIP, I'll explain in a near future in the website !
[FYT Android Head Units] mariodantas:
~This guy @LLIyT_HuK is a hero !
[FYT Android Head Units] Ragpuss:
Are these apps still current or does the latest firmware have newer versions of these files already included ?

Thank you.
[FYT Android Head Units] mariodantas:
These bundles were extracted from AllAppUpdate.bin for FYT 1 and FYT 31 units, forgot to mentionit in readme, they are at leas 6 months old, anyway I'll remove them from FYT FACTORY as I'm not laintaining them anymore. Don't have time for all that stuff now, as my life has changed !
[FYT Android Head Units] mariodantas:
New release today:

2023-09-25

FMC: Added: Backup FMC settings to cloud when doing a local settings backup (if network available).

TYPE: FMC-UPDATE
[FYT Android Head Units] Ragpuss:
Thanks for the reply, talking of the FYT1 and 31 I have had a problem installing the latest firmware from your factory for the 7862, once installed I loose all of my can bus and nothing works, no settings will save and I have to flash back to my original backup files.

In FYTprop I have " ro.build.fytmanufacturer=51 " is this not compatible with the firmware ? I'm pretty new at this stuff so I'm not too sure on which files do what but your older firmware worked.
[FYT Android Head Units] mariodantas:
The MD-EDITION Kernel and App are compatible but not the bundles !
[FYT Android Head Units] ronald_w.:
Unfortunately I cannot confirm that. The script is executed but because /dev/block/dm-2 does not exist, the rooting process fails.

Firmware: iying_7862-9863-_-720-1280-w8-dab-360_-_20230814he_2023-08-15_0035
[FYT Android Head Units] surfer63:
Can you explain what is going wrong?

And if you refer to the last "Failed to open .." message, then first do your homework and read through this forum about what it means.
[FYT Android Head Units] j0hn83:
That does not cause the rooting process to fail.

The "/dev/block/dm-2 does not exist" error appears on every single firmware flash. It is an irrelevant error and can be safely ignored.

There are dozens, if not hundreds, of mentions of this across multiple threads.
[FYT Android Head Units] ronald_w.:
magisk is not installed and the boot image is not rooted
[FYT Android Head Units] Clandaries:
After installing the script you have to install magisk manager manually
[FYT Android Head Units] ronald_w.:
I had already done that, but magisk doesn't recognize root.
[FYT Android Head Units] mariodantas:
Nothing to do with dm-2, this isn't the cause !
[FYT Android Head Units] gordgelin:
if you already messed up your system before applying root script, you have to factory reset your device and install INCLUDED magisk manager for it to recognize root
[FYT Android Head Units] ronald_w.:
When running the script, can I save a log file to the USB stick to find the cause?

The background to my attempt with magisk is that I cannot lock the device with the FMC with the root offered. FMC requires root rights even though the root schema is activated. SD-Maid and Solidexplorer have root access without any problems.
[FYT Android Head Units] ronald_w.:
The system was freshly installed with the latest firmware update from iying.
[FYT Android Head Units] gordgelin:
there was no error, boot patched, just install included magisk manager 23.0 and update magisk if you need for some reason. if you used some other version of magisk manager or smthing - do factory reset and install included version
[FYT Android Head Units] ronald_w.:
thanks for the quick reply. I'll try again.
[FYT Android Head Units] ronald_w.:
Unfortunately, another attempt was unsuccessful. Magisk doesn't recognize root and wants to patch a file to install it.
[FYT Android Head Units] gordgelin:
there is no need to reapply root script since boot is already patched, you need to FACTORY RESET unit and install magisk manager
[FYT Android Head Units] ronald_w.:
This is the result after a new Installation. See picture 2.

I will install the MD Edition 8581 platforms again tomorrow. There, root works in any case. (even though I would rather use Magisk)​
[FYT Android Head Units] I[E:
@mariodantas, for the 8581 kernel the Kernel_Version.txt shows the January build date. Is that the case, or is the file just not changed? If you missed the thread, I posted one with a June build date. 8581 firmware In case you wanted a newer version.
[FYT Android Head Units] j0hn83:
Picture 2 shows you installing firmware?

I think you misunderstand @gordgelin

When he says factory reset he does not mean install a fresh copy of your firmware.

You simply need to go in to the settings of the head unit and choose factory reset.

Once it is reset you then install the included magisk manager.

Have you tried the factory reset option?
[FYT Android Head Units] ronald_w.:
Thank you for pointing this out. A factory reset is for me the last solution because thereby all data will be deleted and I lose my applications and data. I will first try again with Mario's MD Edition. If there is still the problem with not recognizing the root scheme to lock the device, I will try again magisk with factory reset.

Update:

The installation of Mario's MD firmware went smoothly, as usual. After activating the root scheme, the programs that require root access have this again without problems. Only Mario's own program does not recognize the root scheme. Therefore, I had asked before in the thread what could be the reason for this. This was also the reason why I want to try it with magisk. I have now made a backup and will try again magisk with factory reset.

Update2

The root also works with magisk. But whether the effort after a factory reset is justified, I dare to doubt. I will leave it like this for now, even if Mario's FYT Management Center does not have root access. What I need root access works with both variants.
[FYT Android Head Units] surfer63:
I assume that is the same 26 June 8581 kernel that I used for my OK and MD builds.
[FYT Android Head Units] I[E:
It is. I downloaded Mario's new one to look at it and saw the January build date and wasn't sure if he had seen the newer one.
[FYT Android Head Units] shin76loko:
СTell me, is the kernel suitable for the screen resolution? 720 * 1208?
[FYT Android Head Units] aikair66:
The kernel firmware does not depend on the screen resolution in any way. Install for your processor.
[FYT Android Head Units] Specy01:
I do not think it has already been asked and before doing the installation I wanted to ask you: the registration takes place only if there is a SIM card in the HU or does it also take place if the internet is provided to the HU via smartphone hotspot? Thank you for your reply.
[FYT Android Head Units] aikair66:
Activation occurs when the Internet is available, regardless of how the device receives it. The Internet can be distributed in any available way, including a SIM card inserted into the external or internal slots of the GU.
[FYT Android Head Units] surfer63:
@gordgelin :

Just a totally different question/remark/suggestion about your universal script.

You call the Magisck script from the lsec script ( /cache/mgsk/boot_patch.sh /dev/block/by-name/boot )

The magisck script makes a copy of the original boot.img ( dd if=/dev/block/by-name/boot of=/storage/sdcard1/stock_boot.img )

and as last step in the lsec script you remove the magisck stuff from the cache.

Have you ever considered of making another last step after the removal ( rm -rf /cache/mgsk ) to also make a backup of the rooted boot.img?

Something like:

rm -rf /cache/mgsk

##############################################################################
#
# Now backing up your rooted boot.img
# Afterwards you will find the original boot.img as "stock_boot.img"
# and your rooted boot.img as "rooted_boot.img" on your USB-stick.
#
##############################################################################

dd if=/dev/block/by-name/boot of=/storage/sdcard1/rooted_boot.img

##############################################################################
#
# Ready. You will now see the green counter increase and
# you can remove the USB stick
#
##############################################################################
[FYT Android Head Units] aikair66:
I have never used the GU lock from FMC before. Today I tried to make a block. When unlocking the head unit, a window pops up with the input of the email address. When you click on the address entry line, a window pops up with my email address (and all saved passwords), with which I have already unlocked the device. Clicking on my email address unlocks the device. Some kind of unprotected blocking is obtained. What do you say about this. So anyone can unlock my device in my absence. Question to Mariodantas, is there any way to fix this? Or make a password lock.
[FYT Android Head Units] gordgelin:
what's the possible reason to do this?
[FYT Android Head Units] surfer63:
Just for convenience.

To give the user another possible option to do what he/she wants.
[FYT Android Head Units] gordgelin:
i will consider this updating the script next time
[FYT Android Head Units] mariodantas:
New release today

2023-10-09

Kernel: 2023-08-31

FMC: Fixed: Sometimes FMC asks twice for email when unlocking unit.

TYPE: MD-EDITION-UPDATE or FMC-UPDATE
[FYT Android Head Units] Kaelub:
Do we need to download and reflash? Or does your software have an update feature? Im at work so I cant check
[FYT Android Head Units] mariodantas:
New release today

2023-10-13

Kernel: 2023-09-23

TYPE: MD-EDITION-UPDATE
[FYT Android Head Units] trap63:
today I reinstalled MD FW and now it returns "not compatible". Yesterday on first install no issue. I reinstalled previous MKD M6Pro_PLUS_UI4_2000x1200_TOPPAL_APP20230602_YILING_RU_SYSTEM_1684828881 and same results: not compatible.
[FYT Android Head Units] Kaelub:
Do we need to download to usb and reflash? Or does the app have an update feature?
[FYT Android Head Units] surfer63:
Why do you ask twice? And why do you not simply go to Marios FYT factory website and read the instructions that come with every download? Also for this FMC update.

He provided a lot of info and took a lot of time to write it, and then you expect him to spend even more time on lazy users who do not read one single line?

You see that I won't answer you either.

Read! Read! Read!
[FYT Android Head Units] Kaelub:
I didn't realize I already asked. I don't expect anything from anyone. If he chooses not to respond, I am not upset.

You seem to be upset though. For that, I am sorry.
[FYT Android Head Units] Ushas:
Please tell me why the Upgrade Bundles folder disappeared. Thank you.
[FYT Android Head Units] trap63:
@mariodantas I am still crazy, if you install old FYT com.mariodantas.fytmanagementcenter-1.0-signed-release of March all works, as soon as you update, apk returns with "no compatible with this device". Same as when install you new release. Yesterday all works well both this apk and MD FW, not more possible to run. Mine is not UDT and Teyes. All works well yesterday. OLD FYTmanagement activated with any issues.
[FYT Android Head Units] Kaelub:
When you have time, can you update post#1? Trying to find out more about update.
[FYT Android Head Units] surfer63:
Did you already visit the FYT Factory website and did you read the "Installation Instructions"?
[FYT Android Head Units] Kaelub:
Yeah. It doesn't look different than before the update. Maybe I need to refresh my browser... I'll try that
[FYT Android Head Units] Kaelub:
I figured it out. You have to click the download link. Then there is a folder called FMC UPDATE... Inside there is instructions. Very much the opposite of obvious.
[FYT Android Head Units] mariodantas:
Ho yes I just did it, full of keystrokes when writing in English, thanks for the tip!
[FYT Android Head Units] Specy01:
Hi Mario, I would like to install your firmware, but there are some points in your post that I do not understand.

You say uninstall FYT Management center user edition before installing your firmware. I don't know if, in my HU, I have this "FYT Management center user edition, also sorry I'm Newby, and i have no idea what it is. I have already read Surfer63's treath more than once but it seems to me that it does not mention it. Can you please explain me what it is and how to do it if one has it? My HU has nothing more than the original firmware installed, updated to the latest firmware of Mekede of 32/09/2023 With the apps of 07/09/23.
[FYT Android Head Units] Moldeb:
"If already installed" means by you, it's not part of any factory image. And you know what apps you've installed, right?
[FYT Android Head Units] Specy01:
That's what i thought then, but before i made any mistakes and wasted time, i wanted to be sure. I didn't install anything, just the original firmware and Spotify. Then i can install it. Thank you moldeb. Can you please, explain to me, what this FYT Management center user edition is? Thank you.
[FYT Android Head Units] Moldeb:
It was (is?) basically a stand-alone version of FMC that Mario released earlier and that's been made redundant by MD Edition. So the section you've found is basically addressed to users of the old tool. MD Edition brings its own FMC tool and that would conflict with the old one.
[FYT Android Head Units] Specy01:
Thank you moldeb
[FYT Android Head Units] Dima_Ov:
Здравствуйте, Мариодантас, можно ли преобразовать ядро 7862 в ядро 8581? Так как нового ядра для 8581 нет, а есть новое ядро для 7862. В чем между ними разница? Или подскажите как это сделать, я сам попробую.

Mod translation: Hello Mariodantas, is it possible to convert a 7862 core to an 8581 core? Since there is no new core for the 8581, but there is a new core for the 7862. What is the difference between them? Or tell me how to do it, I’ll try it myself.
[FYT Android Head Units] surfer63:
@mariodantas

I installed your MD-Edition with FMC again, but I had switched my unit to Dutch. Even though the translations are quite alright in general, some are terribly wrong.

"disabled" as in "désactivé" was translated as "gehandicapt" ("handicapé").

"Close" as in "close this application" was translated as "dichtbij" ("près") as in "close to me" ("près de moi").

And I improved a number of other strings. Some are just hard to translate as we do not really have a Dutch word for it, but Google Translate still tries to do a "creative" translation.

Quite hilarious, but not correct :)

No priority whatsoever, but if you do another compilation, you might want to add it (values-nl/strings.xml)
[FYT Android Head Units] mariodantas:
New release today.

2023-10-17

FMC: Now it informs user if updated version of FMC has been released (if network available)

TYPE: FMC-UPDATE
[FYT Android Head Units] mariodantas:
Done @surfer63

can you please refix these below ?

<resources>
<string name="app_name">Applicatie vergrendeld</string>
<string name="enter_a_new_password_txt">Voer een nieuw wachtwoord in</string>
<string name="confirm_password_txt">bevestig wachtwoord</string>
<string name="password_changed_txt">Wachtwoord veranderd</string>
<string name="please_enter_a_new_password_again_txt">Voer opnieuw een nieuw wachtwoord in</string>
<string name="max_8_characters_txt">Maximaal 8 karakters</string>
<string name="please_enter_current_password_txt">Voer het huidige wachtwoord in</string>
<string name="password_is_set_txt">Wachtwoord is ingesteld</string>
<string name="incorrect_password_txt">Incorrect wachtwoord</string>
<string name="password_disabled_txt">Wachtwoord uitgeschakeld</string>
<string name="enter_your_password_txt">Voer uw wachtwoord in</string>
<string name="clear_txt">Duidelijk</string>
<string name="forgot_password_txt">Wachtwoord vergeten ?</string>
</resources>

These are for the lock FMC with password, a separate package
[FYT Android Head Units] surfer63:
Only the second but last is not correct.

<resources>
<string name="app_name">Applicatie vergrendeld</string>
<string name="enter_a_new_password_txt">Voer een nieuw wachtwoord in</string>
<string name="confirm_password_txt">bevestig wachtwoord</string>
<string name="password_changed_txt">Wachtwoord veranderd</string
<string name="please_enter_a_new_password_again_txt">Voer opnieuw een nieuw wachtwoord in</string>
<string name="max_8_characters_txt">Maximaal 8 karakters</string>
<string name="please_enter_current_password_txt">Voer het huidige wachtwoord in</string>
<string name="password_is_set_txt">Wachtwoord is ingesteld</string>
<string name="incorrect_password_txt">Incorrect wachtwoord</string>
<string name="password_disabled_txt">Wachtwoord uitgeschakeld</string>
<string name="enter_your_password_txt">Voer uw wachtwoord in</string>
<string name="clear_txt">Wissen</string>
<string name="forgot_password_txt">Wachtwoord vergeten ?</string>
</resources>

That is if clear_txt means to wipe the text.

If it means "is the text clear to you", then the original is correct.
[FYT Android Head Units] badwhip:
Mariodantas you use to have all your version of md edition on your server now it seems to be the latest one but you use to have two versions one with main services and one without. Is the current latest one one without mainservices? I need the one that will allow apps to start up after slwep. Thanks
[FYT Android Head Units] mariodantas:
If you need dont kill apps, you need WITH_MAINSERVICE, if not, if you need auto start apps at boot, FMC does the job (no need of custom mainservice)
[FYT Android Head Units] surfer63:
You don't need anything for that. That will work with a plain FYT firmware as well.

Settings->User

Application Setting ( which applications you want to auto-start when you start your car and unit )
[FYT Android Head Units] trap63:
What's the matter, it don't works? Installed over stock firmware sent yday from Navifly? It' s a UIS7862S 1200x2000. Same error (not compatible) after several reflash on various firmware.
[FYT Android Head Units] surfer63:
What kind of unit do you actually have? I can see it is a FYT, but what brand/reseller?
[FYT Android Head Units] badwhip:
Yes I done that in passed but when I go to your website to get the lastest that is marked with mainservices I only find one so it confuses me because you use to offer both in separate downloads.
[FYT Android Head Units] trap63:
@surfer63 here 116
[FYT Android Head Units] badwhip:
Atoto radio only gives you one app to auto start they do allot of things to prevent you from changing things.mario custom software really made the atoto work so much better
[FYT Android Head Units] surfer63:
It should only give this message if you use the standard version and run it on a Teyes,

if (Objects.equals(_SharedData.m9739E("ro.build.fytmanufacturer"), "95")) {
startActivity(new Intent(getApplicationContext(), NotCompatibleDeviceActivity.class));
finish();
}

OR if you run the Teyes version on a non-Teyes unit, like your Mekede/NaviFly/whatever with id =116.

So to be sure: which version did you download?
[FYT Android Head Units] trap63:
this one .....2023-10-17__FYT7862_FW_MD_EDITION_WITH_MAINSERVICE not Teyes
[FYT Android Head Units] surfer63:
Go into Settings -> Apps and select the FMC center. Then delete all storage: normal and cache, and reboot the unit.

See if that helps.
[FYT Android Head Units] trap63:
it's curious, if you install MD edition with first release of FMT all works, as soon as you update standalone FMT reports not compatible
[FYT Android Head Units] LLIyT_HuK:
I have already received more than one review about this problem on the latest build of the Mario system.
[FYT Android Head Units] trap63:
previous did not this issue.
[FYT Android Head Units] trap63:
not works, I uninstall and flash with stock firmware. I am tired , two days of install several firmwares to receive same error, never happened in past.