General General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware

Search This thread


Senior Member
Apr 20, 2010
English please. Read the sticky moderator posts.

Sorry, I thought I wrote it in English, maybe it was the chrome translator

Hello, I have a FYT device, the model M700S from the Navitree brand, version 8gb of RAM 128gb of internal memory, here is the link ( ?orderId=8145570029879167). I have a 2011 citroen c5, I'm having some problems

1st main is the poor FM reception, I have a way to improve the FM reception, I already put a signal amplifier but it didn't improve anything
2° whenever I start the car the navradio + opens and closes twice but it keeps playing, but if the last time I turned off the car the music player is already playing the navradio + it no longer opens and continues to play the music player normally until i turn navradio+ back on, but if when i turn off the car navradio+ is playing then the screen shows navradio+ turning on and off twice in a row do you know how to solve it?
3° my car has parking sensors in the front and in the rear, for the rear I have no problem, it shows the radar image with the rear and the front and the camera but for the front it only shows the vips but the image does not appear from the radar, is it possible to make the image appear?
I tried to solve all these situations but I didn't have any success thank you very much for your help I apologize for my english


Senior Member
Dec 1, 2010
Mailed Joying about my disappointment concerning the "Android 12" update. Got to say they responded quickly (as always) and, imho, quite reasonable.

Relatively speaking that is, as I still find the way they implemented the USB tethering somewhat misleading/poorly chosen.

"I am sorry friend, we release Android 12 just mainly to add the USB Tethering function to differentiate from previous firmware, that's why our advertisement is still Android 10.0, not changed to Android 12 to attract more traffic, if this disappoints you, we felt deeply sorry for this, We will learn this lesson and do better in the future, and be more cautiously."
Well because when they list "Android 12" on AlliExpress, than you can get some money back. After doing the Fake Device Test....

I have already fallen for one headunit that contains a fake Android version, and I'm waiting for AlliExpress to step in. Ofcourse I'm hoping for full refund. Or at least partially, because I would need the frame and harness anyway if I decide to go with one of these FYT units. Which some ship from Europe, and that takes away one reason not to order above € 150....


Senior Member
Dec 1, 2010
Still says Android 10 on both Ali and their own site. But we'll be watchin' :cool:
I saw Mekede ( Which has warehouses in Europe ) claims that their units are running on Android 11, but atleast they display API Level 29. Which means it's fake and in fact running Android 10.

Because of being cheated by EKIY, I'm now looking for another headunit. These FYT headunits, seem more to my liking. But would they atleast work good? Without having to look for many workarounds?

I didn't read the whole thread, but have been looking into these devices for a while and because of my experience with Android smartphones in the past. And my ignorance... I have bought a head-unit that in fact runs on Android 8.1 instead of Android 10, because it was a fake Android version:(

It seems to be common practice sadly to fake Android versions..... anyone know if these FYT already support wireless Android Auto? I heard lately lots of head-units supporting it, without resellers knowing it.


Aug 8, 2022
Hello forum members, I have installed a Mekede m600s car radio with canbus rz-vw-58 in my 2003 Passat b5 car, and therefore I need your help with a problem that I cannot solve with the help of the seller. the problem is that only the steering wheel button function works nothing else, i tried all the protocols and the wiring from the car to the canbus and radio are properly connected. I bought a second canbus from my side RP5-VW-001 and with this canbus the door function is also displayed on the car radio with steering wheel button function, everything else is not. how can i solve this problem? and a question for you are canbus and car radio compatible with my car? sorry, i don't speak english, i translated everything with google translator


Aug 8, 2022
can one of you help me, after I installed this firmware I can't flash any other firmware, how can I flash the firmware from Mekede again


  • IMG_20220814_155108.jpg
    3.3 MB · Views: 26


Senior Member
Jun 6, 2012
hi, what does this error mean.
Extract actual lsecxxxxupdate file from latest ( really latest ) update file for your unit , and replace the actual file on the installation sd-card. then the update procedure will work well.
i assume, you try to do some adjustment stuff, as a "real" update with stock files would not throw this error.


Apr 9, 2022
Estrai il file lsecxxxxupdate effettivo dal file di aggiornamento più recente (veramente più recente) per la tua unità e sostituisci il file effettivo sulla scheda SD di installazione. quindi la procedura di aggiornamento funzionerà bene.
presumo che tu provi a fare alcune cose di regolazione, poiché un aggiornamento "reale" con file stock non genererebbe questo errore.
i wanted to try to modify the config for microphone


Senior Member
Jun 6, 2012
i wanted to try to modify the config for microphone
So, as mentioned, act as described. Download the latest ( complete ) update file from your manufacturers website.
Extract it and put the lsecxxxupdate file from the extracted data to your usb-stick or whatever you use.
then start your config process again. there are several descriptions to this subjet, start form post#1 and #2,


Aug 8, 2022
Be more specific: what unit do you use, what firmware, whats the goal of this ?
Looks like you havent the right firmware to flash your unit.
Be specific, detailed, act as if anyone else would ask You this question.
Then you shurely will get assistance :)
I have a Mekede M600S 6/128 fyt116 and had already described the problem in #post506 and wanted to possibly solve the existing problem with a different firmware, but as I noticed myself, it didn't do much


Aug 8, 2022
Why do you want to flash other firmware? Only because your screen is rotated? You can fix that easily. See post #3
No, I don't want to flash the car radio because of the display, my problem lies elsewhere, I've also tried to describe it as well as possible in post#506, if you need other data to help me with this problem, then let me know
Last edited:


Aug 8, 2022
Hello forum members, I solved the problem in post #507 myself by uploading my backup, but thank you very much for your help and the tips.

but my main problem still persists which is that the car radio doesn't display all the car info no clima, oil pressure, temperature etc except the door functions are displayed on the screen and the steering wheel button function works fine.

I have a VW Passat b5 car, year of construction 2003 and my HU is a Mekede m600s fyt 116 with 6g rom and 128g, my seller delivered it with a can-bus rz-vw-58 adapter, but with this can-bus Adapter only the steering wheel buttons worked. the seller suggested a firmware update and I did it and that didn't lead to a positive result, after my considerations I bought a new can-bus adapter (RP5-VW-001). with this addition, the door function is now also displayed in the HU screen. so I ask you for your help to solve the problem


Senior Member
Jun 6, 2012
Hello forum members, I solved the problem in post #507 myself by uploading my backup, but thank you very much for your help and the tips.

but my main problem still persists which is that the car radio doesn't display all the car info no clima, oil pressure, temperature etc except the door functions are displayed on the screen and the steering wheel button function works fine.

I have a VW Passat b5 car, year of construction 2003 and my HU is a Mekede m600s fyt 116 with 6g rom and 128g, my seller delivered it with a can-bus rz-vw-58 adapter, but with this can-bus Adapter only the steering wheel buttons worked. the seller suggested a firmware update and I did it and that didn't lead to a positive result, after my considerations I bought a new can-bus adapter (RP5-VW-001). with this addition, the door function is now also displayed in the HU screen. so I ask you for your help to solve the problem
Looks like concerning the canbus protocol, or a not matching canbus box.
Try to change the canbus box settings in System Settings, playing around with all available setings for your car ( preferred: some *vw* type , aka *vag* ).
Have a look at the new descriptions of settings of those units, newly added by Surfer63 and others.
To their contribution, you can locate these settings, and play around. Its the only way . goodluck
  • Like
Reactions: marchnz


Apr 9, 2022
So, as mentioned, act as described. Download the latest ( complete ) update file from your manufacturers website.
Extract it and put the lsecxxxupdate file from the extracted data to your usb-stick or whatever you use.
then start your config process again. there are several descriptions to this subjet, start form post#1 and #2,
Thanks for the help, I installed the config to improve the microphone, the result was negative, I had to go back to the original config of the mekede 700s, did the same thing happen to you too?

Top Liked Posts

  • 1
    What's the point of this Digital Wellbeing App anyway? Isn't it meant for smartwatches and stuff like that? So we wouldn't even need it on our units, unless you wanna Sync your smartwatch with the headunit.
    Yeah right, but according to statista there are now 6.6 billion smartphones on Earth. And how many head units? We are too insignificant to make an exception on the general "standard roll-out" policy.
    The sleep times, Sssh-times, etcetera, should definitly not happen when we are driving.
  • 4
    hello, I also have a uis7862 unit with a problem... it doesn't remember the numbers from the phone book when I connect the phone via bluetooth, please help me
    Disable share contacts within Google account settings on the headunit, and enable share contacts at Bluetooth settings of your phone. That should fix it.
    Ah.. I saw that it was an active discussion.. I was reading on the rooting forum but posted the question here.. apologies. will try to remove the digital wellbeing
    You simply need to deactivate the Digital Wellbeing App.
    On the first page I can't find any info what the twipe_cache command in the updatecfg.txt does.
    Just added that. Thanks for reminding me.
    It seems our Russian friends at 4PDA, already found a fix for the home launcher that keeps changing back to the default one: after changing to another one.

    So it's really that easy? And what's the point of this Digital Wellbeing App anyway? Or is it lost in translation?

    You simply need to deactivate the Digital Wellbeing App.

    Forgot to reply.
    I also added that to post #1 as Q&A 22.

    Are you using a Mekede as well? I still haven't updated Carlink, because I'm wondering if it's perhaps meant for use only on Joying? But did you install the zip? I tried the APK on my phone, and one thing I noticed: it contains another app logo, than the current Carlink on my headunit.

    I'm a bit reserved with flashing random versions of Carlink, just to not break things.
    I flash the last version that was post here and all work fine for me. I have a Navifly m700s
  • 26
    Last revised: 09 September 2022.

    This thread is supposed to become a "one fits all" thread about FYT based Spreadtrum uis7862 (Unisoc ums512) head units and its software, modded or not. The first few posts will be "collection" posts for all kind of info but will also link to other useful information that might be added later or in other threads.
    Part of the tips, mods, etcetera are also valid for FYT based sc9853i and sc9863a (uis8581) head units, and even for the older PX5 and Sofia-3GR.

    DISCLAIMER: Every action you do on your unit is on your own responsibility. I will help where I can (and probably a lot of other users as well), but I am never responsible.

    This thread is meant for:
    • Discussing firmwares (see post #2), modded firmwares, mods and rooting (not advised).
    • Tips, tricks, mods to improve the general usability of your unit.
    • Try to solve design errors/flaws where we expect that these Chinese resellers/suppliers will not do it.
    This thread is NOT meant for:
    • buyers advice (is this one better than that one?)
    • 4G providers, DAB+ modules or DAB+ software (see here for DAB-Z by @realzoulou), Navradio+ (see NavRadio+ ported to UIS7862-FYT devices by @KoTiX2 , sub-woofers, OEM cameras, OBD devices, TPMS or other peripheral devices.
    • ABSOLUTELY NOT for posts about "what is/are your favorite app(s)?"
    • Questions about repairs, warranty and the like. That is between you and the reseller. Questions about interchangeabilty of hardware are OK.
    Always first check the offical websites (if any) of the resellers in case of technical questions. Also: First contact your reseller in case of hardware issues or (not working) accessories.

    General unit information

    CPU: uis7862 (ums512). Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
    Android version: Android 10 (API/SDK 29); Fake Android 11 (still API/SDK 29). (Android level is a simple property. Always check at the API/SDK version)
    Producer: FYT
    WiFi: 2.4GHz and 5GHz. This 5GHz is really a benefit. Not only because of its faster 5GHz speed, but also because the 2.4GHz and BT negatively influcence each other dropping perfomance sometimes to 10% of "real" 2.4GHz. (Valid for all models without 5GHz, FYT or not).
    Bluetooth: V5.1
    Resellers: Atoto, Ebilaen, Eki, Farcar, Funrover, Idoing, Isudar, Joying, Junsun, Mekede, NaviFly, Sinosmart, T'eyes, Winca, Zhan. There are more resellers, but not all of their models might be FYTs. Same for some resellers in this list.

    Q&A - Questions & Answers

    Q1: I already see uis7862 units having Android 11 and even Android 12, what about it?
    These Android 11 versions are fake! The Android version is still Android 10 (API/SDK 29), but the Android version as displayed is a simple property which you can set to Android 11 (or 12 or 31 or 227). The API/SDK versions determines the real Android version. Don't believe statements like "we updated ...". Always look at the API/SDK version. If it says API/SDK 29 it is is Android 10. Real Android 11 is API/SDK 30.

    Q2: What are the several passwords on these uis7862 FYT units?
    • Factory menu / Developer options: 3368
    • Backlight Current Adjustment: 5768
    • Door lock interference: 0000
    • To change home launcher: 8086
    • Developer password: 7788, or tap 7 times on "About".

    Q3: Are all these (uis7862) units compatible? Is all (uis7862) firmware compatible?
    The uis7862 units based on FYT are all hardware compatible. Differences in audio chip, radio chip with or without RDS, DSP chip (DSP 14-band (low end) or DSP 32-band or not at all) are supported by the software. There are minor differences in MCU and firmware, which need to be taken into account when flashing firmwares,and sometimes also for flashing mods. This is all based on the so called reseller id.

    Q4: How compatible are FYT units over the years (uis7862 (ums512) vs uis8581a (sc9863) vs sc9853i vs sc7731 (uis8141e) vs PX5 vs Sofia3GR)?
    When it comes to firmware you really have to look at the CPU and reseller id (see below). Part of the "user apks" are quite exchangeable. When it comes to settings, behaviour, tips & tricks, etcetera, these units are mostly compatible over the entire range through the years and almost all settings are the same when it comes to (uis7862(ums512), sc9863a(ums8581a), sc9853i, px5, sofia3gr). So please take a look at Q&A, tips, info Roll-up (Joying) FYT SC9853i before asking questions.

    Q5: What is an MCU? What does it do?
    MCU stands for MicroController Unit (in this case). The MCU is a "CPU" itself with embedded (flashable) firmware that functions as interface and "translation" layer between the Android software and the hardware layer (Radio chip, Amp chip, DSP chips, etcetera).
    The MCU has some I/O lines to the hardware of the unit. A number of digital IN lines (ACC, headlights, reverse, parking brake) and digital OUT (antenna power, amplifier power) and a few analog IN lines (steering wheel 1 and 2). This overview is not complete.
    So actually your unit comes with the Android firmware (Android itself and the additional FYT unit programs) and with the MCU firmware. That MCU firmware is not always packaged with new firmware updates. Note that all these Chinese units use this MCU firmware instead of using Google Androids Automotive System.

    Q6: Can I flash firmware from another FYT uis7862 supplier to my FYT uis7862 unit?
    NOT directly, but with some tweaks: Yes. Read post #2 carefully and especially section VIII.

    Q7: Can I flash the MCU firmware from another FYT uis7862 to my uis78962 unit?
    NO. I repeat: No. If you really, really, really, really know what your doing then to some extend: Yes. Otherwise: Don't even think about it.

    Q8: How do I unpack/repack this AllAppUpdate.bin?
    See post #2 section II. (AllAppUpdate.bin).

    Q9: What is an AHD camera?
    AHD stands for "Analog High Definition". It has nothing to do with your screen resolution itself, but it is for your camera (1280x720 and 1920x1080). It requires it's own micro-processor for decoding in the unit. AHD cameras are therefore only supported on units that specifically mention this. You can however connect a "low res" DVR camera (720x576 or 720x480) to an AHD unit.

    Q10: Can I mod my unit? Are there custom firmwares available?
    Yes, you can mod your unit to some extent. See the posts about the AllAppUpdate.bin and 7862lsec scripts. There are no custom firmwares available. There are modded firmwares available. These contain some tweaks, minor layout changes and sometimes solve bugs, but are actually still the exact same firmware.

    Q11: Can I root my unit?
    Yes, you can. There are at least 3 possible ways to do this, but I don't recommend rooting. Not because rooting is tricky, or making your unit unstable, but rooting brings nothing. It only makes your unit lsess safe as malware, etcetera have a much beter chance to attack than on a non-rooted unit. You can mod some things easily yourself without (!) root. When rooting Google voice feedback is crippled as media channel 4 is somehow "blocked". Viper audio doesn't work properly and brings nothing extra on these DSP units. Anyway: Google for yourself if you still want to root your unit as it is possible if your really want it.

    Q12: How do I disable the internal microphone when using an external microphone?
    See this post.

    Q13: I flashed a firmware from another unit and now I have a big yellow bar with red text "ui and mcu does not match". What can I do?
    To start with: I know it should be "ui and mcu do not match", but that "does" is CHenglish. The reason for this is that the is different for the several resellers and you used an AllAppUpdate.bin from another reseller. You now have several options here:
    1. You still have the original firmware and can extract the from it (or you know it from the top of your head).
    2. You have no clue about this and you don't have the original firmware anymore.
    In case of (1), you could:
    • use the script Change Fytmanufacturer (bullet #3) that directly updates this inside the fyt.prop on your unit.
    • open the AllAppUpdate.bin (next post, topic II) and change the and repack it again and flash that AllAppUpdate.bin
    • Or simply flash the oroginal firmware, get the and start all over again.
    In case of (2) you have to flash the entire original firmware again ór use the script (link added later) to update the fyt.prop directly and try a number of ids until you have the correct one (There are not so many).

    Q14: I want to replace my boot animation and/or boot logo. How do I do that?
    Copy the lsec6315update binary and your and/or your LOGO.bmp onto a clean USB-stick and connect it to your unit. It will only flash your bootanimation and your boot logo.

    Q15: When my unit (cold) boots, the radio is always started. Can I prevent this from happening?
    You can't stop this. Not on a Joying and not on any other unit. And note that the radio app is actually only an interface that forwards commands to and receives data from the radio chip via the MCU. It is not an active app like your mediaplayer that does everything in Android.
    When the unit boots, the hardware is up and running long before Android is. That means that the radio chip and amplifier are already working before Android has even booted. That is why you hear the radio. And that is why every manufacturer starts the radio app on boot: to enable you to mute the radio channel from the app.
    The radio is never switched off as it cannot be switched off. It is only muted.

    Q16: Do I have a FYT unit or not?
    Use my HWGet_Info.apk. It will immediately show a lot of FYT properties (if it is a FYT) and give a zip with a lot more info as well.

    Q17: If I want to create my own scripts then which binary do I need and which script should I create?
    lsec6315updateuis7862 (ums512)
    lsec6316updatesc9863a (uis8581a)
    lsec6523updatesc7731 (uis8141e)

    You can make "Universal scripts" by simply using all binaries and create/duplicate all scripts and copy them onto one USB-stick (or inside a dowloadable zip). The unit will automatically select the correct binary and accompanying script.
    The binaries and scripts are "incompatible" on other units.

    Q18: My GPS reception is bad. What can I do?
    • If your car already had GPS, buy a "Fakra C Adapter Plug to SMA Male GPS" adapter (example) and use your cars GPS antenna (mostly on the top of the roof). 99% sure it is better than those cheapest possible GPS antennas you get with these units.
    • Buy a better GPS antenna. On Aliexpress you can buy a 32 dB or 38 dB antenna from 6-26 euros that are much better. Secondly: the standard GPS antennas come with long cables that loose signal.
    • The standard antenna: First check whether your SMA connector is firmly connected. Mostly it requires a little more force to fix than your fingers will yield.
    • The standard antenna: Check for a broken cable. Is it nicely curved or does it somewhere has a sharp bend.
    • Do not put it under large metal plates or metal reinforcement beams under your dashboard. Mostly it functions just fine below your dashboard, but not if you put it directly under a big metal beam/bar.
    • Place the antenna itself horizontally to give it the best "view".
    Q19: All my apps are killed when my unit goes into deep sleep. Can I prevent this? Or: How can I always start the XYZ apk when I start my car?
    • First of all read bullet #8 from my other "info" thread, but do NOT use solution 2, made for a sc9853i, for your uis7862.
    • In the Settings apk, go to "User" -> "Application Settings". In that menu you can autostart applications on cold boot or coming from (deep) sleep mode.
    • Use FYTstarter from @bambapin.

    Q20: I use Total Commander, FileXplorer or any other advanced file manager but can't write to my external USB-stick or SD-card. Why?
    You do need the documentsui.apk for it (deprecated as of Android 12). For whatever reason FYT doesn't compile it into their firmware. This DocumentsUI for Android 10 will help you. Install it, open it once and afterwards your filemanager will use it once to request access to (the root of) the USB-stick. When using another USB-stick (having another internal ID), you will have to give access to that USB stick as well. Same when you have formatted your USB-stick.

    Q21: I have a unit without active cooling (a fan) but still would like to cool my unit as it gets really hot and starts to throttle down giving terrible performance (and reduced life span). How can I add a cooling fan?
    You can buy a 12V PC-fan. Select a slowly spinning, ball bearing fan to make it as silent as possible. Connect it to the 12V AMP wires. From the Settings -> Sound, you can enable/disable the AMP. In this case that will start or stop the fan.

    Q22: I use a non-FYT Launcher (Nova, WebGuru, Agama, etcetera), but recently it always switches back to a FYT launcher or another after sleep / reboot / other actions.
    Go to: Settings - Device - Applications: Disable the Digital Wellbeing App
    (End of Q&A - Questions & Answers)

    FYT Settings explained

    Thanks to @hanichl for first write-up.
    Thanks to @mastrv for corrections and further additions.

    Note these are FYT Settings, which means it doesn't matter whether you have a Mekede, Joying, T'eyes or any other FYT unit. Note also that many settings are the same whether you are on a FYT uis7862, uis8514a, sc9853i, PX5 or Sofia 3GR, althought the number of settings have increased in newer models.
    T'eyes also has a site with instruction videos, which are still 90% up-to-date. See here.



    • Wlan
    • Data Usage
    • SIM Info
    • More
      • Mobile Network
      • Hotspot & Tethering
      • Airplane Mode
      • VPN


    - Display
    • Brightness Level ( brightness for day and night mode )
    • Wallpaper ( change wallpaper )
    • Auto Blackscreen ( black the screen after xx seconds/minutes )
    • Displayed NET Switch ( shows the connection speed in upper taskbar )

    - Sound​

    • Keypad Tone ( tone when pressing a key )
    • LOUDNESS ( Not entirely clear, but most proabably the same Loudness setting as on a HiFi installation before DSP was introduced, or for units without DSP )
    • AMP ON/OFF ( switching amplifier mode ). Note: In case your unit has a cooling fan installed, the setting AMP ON/OFF is also there to switch the fan On or Off
    • Power Conditioning ( absolute output volume from 0 to 60, all other audio settings are relative; if you think your audio is already too loud at position 5 (or so), you can decrease the absolute volume output here which means that Volume 5 is now lower )
    • Subwoofer ( set subwoofer volumes )
    • Equalizer ( set sound frequencies with equalizer )
    • Speed Compensated Volume ( set sound volume depending on the actual speed )

    - GPS​

    ( set / shows GPS modes GPS / GLONASS )​

    - Apps​

    ( show / remove installed apps )​

    - USB Video Output Setting​

    ( Some resellers sell external USB-connected DVD-players. This settings allows you to correct over/under scanning )​

    - USB Device Start​

    ( None / Carlink - application to start when USB device is connected )​


    • Press any key to start ( When you long-press the "Off" button on the top-left button array of your unit, your screen will switch off (but your unit does not go into deep-sleep). When you set this setting to ON, your unit will switch on again when pressing any button of your unit)
    • Brake wire for video in motion (Incorrect Chinese translation: (Dis)Allow display of video during driving )
    • Auto-start Navigation ( auto start navigation > needs Navi app to be set accordingly )
    • OSD Time ( on / off in notification bar)
    • Mirror view on reverse image ( if backup reverse cam is installed, and the video is 180 degree turned, this will switch to normal mode )
    • Mute audio when reversing ( decrease sound level if rear gear is processed, not completely mute )
    • Sound reduction when reversing ( reduces the sound when car is in reverse gear (driving backwards). Only works when previous Setting switched to ON )
    • Backlight control ( switches the leds behind the (soft-)buttons On/Off : or by switching on/off headlights, or based on time )
    • Default volume switch ( When your unit starts, do you always want to have the same default volume to start with )
    • Default boot volume ( sound volume which is preset on boot process; only works if previous setting switched to ON )
    • GPS Mix ( ON = uses both GPS and GLONASS / OFF = only use GPS )
    • Sound mixing scale ( Set volume of background audio when "navigation speaks" (for example: Volume currently 10 so navigation uses 10, background music uses volume set here )
    • Lantern settings ( set the colour palette for the hardware buttons LED )
    • Steering wheel setting ( Configure the steering wheel buttons; only for non-Canbus systems. Canbus systems are hard-coded )
    • Navi app ( app to start when NAVI Button is pressed AND to auto-start navigation ... see 3rd point ..
    • Map Data Copy ( Old setting for iGo to copy maps from internal memory to SD-card, so that it doesn't get deleted on a new firmware install )


    (requires password/pincode 3368)
    • Touch check
    • Original Car Agreement ( These settings are mostly controlled by the CANbus. The number of options can vary per CANbus type and can also work or not work per CANbus type. The number of options will be very limited without a CANbus. )
      • External Temperature ( provides external temperature )
      • Automatic start and stop ( ?? )
      • Radar Display ON/OFF ( Incorrect Chinese translation: Enables/disables the "beep" sound when too close to an object, so no display but sound )
      • Reverse Parking Line ( In case of a reverse camera show the parking lines )
      • Static Track ( Shows static reverse parking lines in case you don't want or have the "curving" parking lines )
      • Reversing track reversal ( If your reverse camera's left/right postion is reversed )
      • Max Reversing Angle
      • Door ON/OFF ( shows if a door is open )
      • Drivers Door position ( left / right drivers position )
      • Rear Door Exchange ( Similar to Drivers door position, but for back doors )
      • A/C Information ON/OFF ( Shows changes if you change AirConditioning temperature/ blower speed/ etcetera )
      • Car Audio Type ( AUX / IPOD-TV )
      • Reversal Previous And Next ( This reverses your CANbus steering wheel next/previous behavior (Spotyfy is known for this) )
      • Reversal Volume ( Reverses the Volume +/Volume - in case your CANbus steering wheel volume keys/arrows work the other way round )
      • Protocol Print ( When on, this displays the CANBUS messages overlayed on the screen )
      • Temperature unit switch ( Celsius/ Fahrenheit )
      • CAN box upgrade
    • Car Model ( define the canbox manufacturer, params )
    • Antenna normally on ( In case you have an electrically retracting / extending antenna. This will extend the Antenna when ACC switched on . OR some cars need constant 12V on the Antenna )
    • HD reversing video format
    • Boot Screen logo
    • Set Screen
    • Touch Screen Calibration
    • Panel Key Learning
    • Front View
    • Cancel the reverse into the front view
    • MCU Panel Key
    • Unknown sources ( allow apps to be installed from unknown sources )
    • Door lock interference
    • Reverse power supply
    • Volume balance settings
    • MCU upgrade
    • Backlight current adjustment
    • Home Launcher Selection
    • USB Error detection
    • USB protocol selection
    • A key to export ( exports Settings to /mnt/sdcard/SettingsConfig as json file, but how to import this )
    • Single 360
    • Activation
    • DVD Update
    • TV Type
    • Video Output Settings
    • OBD
    • Sleep mode Setting
    • 360 switch
    • Backup Test
    • Plug In Serial Device Setting


    • Location
    • Security
    • Language And Input
    • Google Settings
    • Backup And Reset
    • Account
    • Delay Power Off When ACC Off
    • Application Setting ( which applications you want to auto-start when you start your car and unit )


    • Date And Time
    • Accessibility
    • Developer Options
    • About Device
    • Device Info
    (End of FYT Settings explained)

    Mods, useful software, tweaks for your system, etcetera.

    Mods, useful software, tweaks for your system, etcetera.
    Some will be added later

    • Backup the firmware of your unit (see post #4). Useful if you do not have a firmware yet for your unit.
    • Disable or (re-)enable the mediaplayer at startup/wakeup (bullet #2).
    • Change Fytmanufacturer script to correct the fytmanufacturer id after a flash with another resellers AllAppUpdate.bin bullet #3).
    • DocumentsUI for Android 10. Without it you can't write to an external USB drive with other file managers. That is because the documentsUI is missing. Install it, open it once and afterwards your file managers can use it to get access.
    • Android Shortcut Settings: This program by Mario Dantas gives you access to some hidden settings in the (FYT) head units.
    • Mario Dantas' "uis7862 FYT Factory": A great and very extensive collection of launchers for FYT models and also a collection of (un)rooted kernels for your unit. (Read post #2 section III "The" for more info on kernels and how universal they are.)
    Last revised: 26 August 2022.

    More about Firmware(s)​

    This post is valid for FYT uis7862 (ums512) units running Android 10 or fake Android 11.

    Contents of a firmware zip:

    • The zip file contains all "standard" Android software, drivers and apks. It also contains the the boot.img; the system/vendor/oem partitions and a few other things. This "should" be interchangeable between all 800x480, 1024x600 and 1280x720 models. I don't know for the special resolutions, Tesla like units or rotable units. Probably they are by now also compatible.
    • AllAppUpdate.bin: Special file that contains all FYT apps (This can be (un)packed with any (un)zipper, but I prefer 7-zip). This file also contains special files with reseller specific configs. This one is only interchangeable between the same reseller-id, unless you change that reseller-id.
    • config.txt: file comparible to the build.prop which can contain additional properties.
    • lsec6315update: The binary that really does the update
    • oem: (OPTIONAL, DEPRECATED) Folder containing some additional apps. These are not automatically installed, but can be found in folder OEM in your internal memory (internal SC card called USB). Do not confuse this with the oem partition where the AllAppUpdate.bin will be installed to. I use this folder upon flashing to add some of my preferred apps that I want to have available, but not directly installed. Note: Nowadays the preferred location for these kind of apps is in the vital-app folder inside the AllAppUpdate.bin.
    • updatecfg.txt: Contains instructions for the flashing process
    • Stm32ud.bin: (OPTIONAL) binary to flash the MCU
    • GD32_E230_64K_Flash.Hex: (OPTIONAL) the hex file that contains the MCU firmware itself.

    I. (Factory) Firmwares

    (Please share official (!) download links for other resellers so I can add them here).

    * Modded Firmwares: Search for yourself on 4pda. Maybe later here.

    See for compatibilty between firmwares the below header "Compatibility between firmwares".

    Some commands that can be put inside updatecfg.txt
    twipe_all     # Wipe entire system
    twipe_data    # Will wipe data partition (but not /sdcard, internal memory). Wiping the /data partition will wipe all config, all 3rd party apps and updates of system apps. This is the same as a "reset to factory defaults"
    twipe_cache   # Will wipe the cache of the apps thereby removing the temporary files that are stored for those programs.
    twipe_sd      # Will wipe internal memory /sdcard (but not the data partition)
    dellapp       # Remove all 3rd party apps
    make_updates  # Make an upgrade U-disk boot file
    test          # test unit and firmware before flash

    Some properties that can be put inside config.txt. Say you live in Brazil and you want your locale settings immediately on Brazil, you can add that. As a second example we take a "Tesla style" unit which is actually a rotated horizontal unit:
    ro.product.locale = pt_BR
    ro.sf.swrotation = 90
    Or you want to improve the microphone function a little, you can add or modify the following lines:
    If you decide to download a 4pda Russian modded firmware, make sure you remove the settings from this config.txt file that makes this a Russian firmware (unless you are Russian, but in that case you probably would not be here).

    II. AllAppUpdate.bin

    The AllAppUpdate.bin is actually a password protected zip archive. You can use any zip, but preferably 7-zip for your platform (Linux, MacOS, windows) to create, modify or extract it.

    Specifications: zip format, non-compressed (store), password 048a02243bb74474b25233bda3cd02f8
    Unzip is simple: you only need to specifiy the password.
    When (re)creating a new AllAppUpdate.bin, make sure you follow the specifications. As far as I know "zip version standard 1 deflate" (aka "superfast" aka "Legacy compression") is used, but it does not always work depending on the implementation of parameters for the wide variety of zippers and zip-compatibles. A non-compressed archive always works and will be only 20-30% bigger as all apks and jars are already zip files and only the libraries will be compressed.

    Inside this AllAppUpdate.bin you will find all FYT based apks and libraries and next to that also two other files: fyt.prop and skipkillapp.prop.
    • The fyt.prop is identical to the build.prop but gives the option to add extra properties or replace/modify properties in the build.prop. And the fyt.prop contains the<xy> that is in 90% the only distinction between the several firmwares.
    • The skipkillapp.prop contains apps (package names) with values from -15 to 15.
      When going into "deep sleep" the packages not mentioned in this list will be killed. Applications in this list with positive values will absolutely be killed (unstable otherwise??). The ones with higher values first. The ones with values 1 and 0 as last, where the app with value 0 will be the last killed before going into deep sleep.
      The apps with negative values are considered system apps and will not be killed. In this case the most negative number (-15) has the highest priority. My assumption (not tested, not verified) is that negative numbers approaching 0 might be killed if the system needs the memory?
      So in other words: If you do not want that some of your apps are killed, you can add them to this "skipkillapp.prop" by their package name. Say you use @realzoulou's DAB-Z app, you would add a line for DAB-Z (com.zoulou.dab). Or for example if you are a Tasker user, which is normally killed as well:
      com.zoulou.dab = -10 = -10
      (I would suggest not using values like -15, -14, -13 to make sure you do not really interfere with the real system apps).
      And then you need to add this file (again) to your own AllAppUpdate.bin
    NOTE: In the previous version for the sc98531 you had the Allapp.pkg. You could put one or a few apks in there and it would simply only install/overwrite the apks inside that Allapp.pkg. The AllAppUpdate.bin will always completely erase the FYT apks on the oem partition. This means that you either need a full AllAppUpdate.bin with your (modded) FYT apk(s), or (advised) use the script approach to only add/overwrite/remove one or a few FYT (modded) apk(s).

    NOTE 2: In the "main server" apk, there is now inside assets/property an new file called unkill_app.txt. I "think" that file now contains the apps that should not be killed upon going into sleep mode. I still don't have my unit and I am actually not interested at all in "unkilling" apps, but it might be useful to test with this file.

    III. The
    (Inside also "III-a. More details about the files inside the and how to decompress and unpack/"open" them" and "III-b. Recompress uncompressed images from the to squashfs format for small (!) and easy access. (Not for flashing.)")

    The contains the "standard" Android software for this unit. This is more or less what every "plain vanilla" Android 10 release will contain, without additional apks (Compare it with standard Android where Samsung adds a lot of Samsung apps). This is the "base" firmware as you download it from the Android website and compile it.
    Note: Mentioning that this is "standard" Android is actually wrong. FYT modified the USB and bluetooth stack. In effect: they crippled it to only allow the USB and BT devices that they consider "allowed".
    Note 2: They also added drivers to this "plain Vanilla" Android to support their hardware, mostly through the MCU.

    This is theoretically identical for all FYT uis7862 units and can therefore be used on all FYT uis7862 units. (DISCLAIMER: Experimenting with this falls under your own responsibility).
    You can unzip the and replace the boot.img or modify the install script in "META-INF/com/google/android/updater-script", and then rezip it.
    All the other files in the zip are system signed files, which means that you can further unpack them, but not modifiy and recreate as you will never get the signing certificates from FYT.
    Other files inside the zip are mostly used to create and install the necessary partitions where the system software and Android software is installed to.

    III-a. More details about the files inside the and how to decompress and unpack/"open" them

    You will find for example the system*, vendor* and other "pairs of three" files. Next to these files you will see a number of bin files including the u-boot files, which are the bootloaders. You can consider these u-boot files like the BIOS on older, or UEFI on newer pcs.

    As example we look at the, system.patch.dat and system.transfer.list files. This set actually contains the system partition. The is a brotli compressed image. The patch files can contain patches and is implemented after the system.dat (but on our firmwares always empty). The transfer.list contains the "blocks" on how the system partition should be created.

    Let's unpack such a set of files.
    First we need to "brotli decompress" the (note that this binary doesn't show output and takes quite long).
    brotli -vd -o
    Now we need sdat2img to convert our created "sparse data image"(1) into a "disk image file"(2) being system.img. Note that sdat2img is a python script, so we need python as well (standard on linux, unix and MacOs).
    Code: system.transfer.list system.img

    On linux/MacOS we can now easily "mount" this system.img image file and check the contents:
    mkdir system
    sudo mount -o loop system.img system
    ls -Rl system

    (1) sparse image: To make the images smaller, and to reduce transfer time, Android generates system.img, vendor.img and other img partitions in sparse format. The image is split into chunks of multiples of 4096 bytes. Any chunks that contain no useful data are marked as "Don't care" and no data is sent.
    (2) disk image file: A disk image (file) is a type of file that contains an exact copy of a certain disk or partition. On Android (and linux) these are mostly ext4 partitions/disks but can also be Fat32/squashfs (compressed, often used in older Androids)/DMG (MacOS, also for installers)/NTFS, etcetera.

    III-b. Recompress uncompressed images from the to squashfs format for small (!) and easy access. (Not for flashing.)

    So you have your brotli compressed system image ( of approximately 500MB, which you can't use at all in this state.
    And you have uncompressed it to a system.img of 1.3GB (see previous section), which you need to "mount loop" to view it contents.
    Can I do this differently?
    Yes, you can with squashfs (explained for linux and/or MacOS), for which you first have to install the squashfs tools.
    Mount your system.img like mentioned above and then create a squashfs image.
    sudo mount -o loop system.img system
    sudo mksquashfs system system.img.sqsh
    sudo umount system

    Now you have a squashfs compressed system image of about 550-600 MB instead on an uncompressed system.img of about 1.3GB.
    To examine its contents you mount it like
    sudo mount -o loop system.img.sqsh system


    IV. Some info on partitions

    This info is referring to the partitions being created from within the
    Starting with Android 10, Google introduced "dynamic partitions". Below a quote directly taken from the Dynamic partitions page.
    Dynamic partitions are a userspace partitioning system for Android. Using this partitioning system, you can create, resize, or destroy partitions during over-the-air (OTA) updates. With dynamic partitions, vendors no longer have to worry about the individual sizes of partitions such as system, vendor, and product. Instead, the device allocates a super partition, and sub-partitions can be sized dynamically within it. Individual partition images no longer have to leave empty space for future OTAs. Instead, the remaining free space in super is available for all dynamic partitions.
    Apart from the /oem partition and a few others, the /system, /vendor and /product partition are read-only. In earlier FYTs, you could use the lsec script to make them read-write and then modifiy content, add/remove files/apks, etcetera from these partitions. The big disadvantage for modders with these new dynamic partitions is that you can't make them read-write anymore.

    V. The lsec_updatesh folder, lsec6315update binary and script (and what about "universal" scripts)

    The flashing process consists of a number of steps:
    1. flashing the core/kernel software (
    2. flashing the unit applicable apps and libraries plus initial properties (AllAppUpdate.bin)
    3. scripts that do "post flash" activities.
    The "flashing" executable/binary also starting the scripts, is the lsec6315update file on a uis7862.
    A USB-stick used to execute a script on a uis7862 should contain:
    "stuff that needs to be copied/moved/installed"
    Practical applications:
    • Making patches, an alternative to creating the AllAppUpdate.bin file by simply specifying an apk (or so) in your script.
    • Delete unnecessary files or applications (who uses the calculator app?), or overwite/change files like the fyt.prop, config.txt or others.
    • Set properties that normally require root/admin rights.
    • Create a nearly flashable backup using this script (to be added) by creating backups of your FYT apps and config files and immediately zip them to an AllAppUpdate.bin and add some more necessary files.
    • Creating backups of your partitions using the dd command. This can be handy on a device for which you do not have a firmware yet as backup.
    • Rooting your unit, also if you do not have a firmware from your supplier.
    • Make a "modded" ROM by simply doing all kind of modifications after the "normal" firmware flash using the script.
    • Flash a new config.txt to your unit: Simply copy your modified config.txt and the lsec7862update binary onto a clean USB-stick.

    For more info on writing scripts for a specific FYT unit by CPU or create "universal" scripts, see (this post => to be created)

    See this post #228 for more info about the "The lsec_updatesh folder and script" as it was used on the SC9853i (and now again on the sc7731 (uis8141e).

    VI. Compatibilty between uis7862 (ums512) Firmwares

    As mentioned under the relevant topics above:
    • The should be identical between all uis7862 units. Of course newer releases can contain updates, etcetera.
    • The AllAppUpdate.bin is application wise compatible between same aspect-ratio compatible screens like 800x480, 1024x600, 1280x720. The great separator here is the property. If you flash an AllAppUpdate.bin from a Mekede firmware (with id=1 or id=116) to a Joying (with id=43) or vice versa, you might get a perfectly working unit, but a big yellow bar in the top of your screen mentioning that the MCU is incompatible. However, due to real differences in MCU firmware (which is in general not compatible), you might also encounter serious issues. Not because the software is incompatible, but because it behaves differently on another MCU.
    • The optional MCU firmware. This is definitely NOT compatible!

    So what can you do when seeing upgrades from other suppliers?
    1. You could take the if it "seems" to be (far) more up-to-date than your currently installed system (/system, /vendor, /product). You can copy it to a clean USB-stick and copy the lsec6315update binary onto the USB-stick and flash it to your unit. In case of doubt, always ask
    2. If it contains a (much) newer AllAppUpdate.bin, you could unzip it, find the fyt.prop and update the id to the id in your original firmware/fyt.prop and repack the AllAppUpdate.bin. Then you copy to a USB-stick:
      • the just (re)created AllAppUpdate.bin.
      • an "update.cfg" containing "twipe_all (preferred) or "twipe_data".
      • the original or a modified "config.txt" onto it.
      • the lsec6315update onto it
        In case of questions, always ask.
    3. Another option will be described here, but not ready yet

    Some remarks about current "seemingly different" FYT units.
    • The uis7862 (ums512) versus the sc9863a (uis8581a) : These units are compatible on AllAppUpdate.bin, but note the That is also of importance here. They are NOT compatible on kernel/core level so you can't flash the (uis7862) or (uis8581a) to each other. However, with above mentioned measures you could flash a newer AllUpdate.bin from a uis7862 onto a uis8581a, or vice versa.
    • The sc9853i versus the sc7731 (uis8141e): Also these units are compatible on AllAppUpdate.bin, but note the That is also of importance here. They are NOT compatible on kernel/core level so you can't flash the (sc9853i) or (sc7731) to each other. However, with above mentioned measures you could flash a newer AllUpdate.bin from a sc9853i onto a sc7731, or vice versa.

    VII. FYT firmware types over the different CPU configurations

    To be written.

    VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller

    To start with: If you do not have a T'eyes unit, do not flash T'eyes firmware. T'eyes uses all kind of paid extensions, which you can only activate by paying and registering your T'eyes' unit id (which you do not have of course because you do not have a T'eyes). Next to that: If you do not use their extensions, the "normal" programs like Google Voice/Assistant can be blocked.

    Before flashing:
    First heck the FYT reseller id of your firmware. Install a good file manager like Total Commander. Go to /oem/app. In that folder you will find a file fyt.prop (In Total Commander, right-click the file, "Open As" -> Text". Inside this file you will find a line with, where the number is the id of the reseller id of your unit (43 is Joying). Write down that number!
    Another option to get all this info is running my HWGet_Info.apk on your unit which will immediately show some FYT properties and give a zip with a lot of info. This zip file is completely anonymous and does not contain any user data!

    Inside that same folder /oem/app you will find the file config.txt. Copy it to a USB-stick and save it carefully. In case you still have the original firmware of your supplier, you can find inside that zip/rar file the same config.txt. Make sure your have the config.txt belonging to your unit!
    If you copy a firmware from another reseller, or a modded AllAppUpdate.bin, this config.txt may have more or optimized options. Some options from the config.txt from your unit must be copied into the config.txt of this new firmware before flashing.
    The options that need to be copied from YOUR config.txt into the new config.txt:
    • Find the line ro.sf.swrotation=xy (values 0, 90, 180, 270) . Use the value from YOUR firmware in the config.txt for this new firmware.
    • find the line with sys.fyt.bluetooth_type=x. The value is normally 0 or 1, but can sometimes even have other values. Use the value from YOUR config.txt for this new firmware.
    What option to flash do I have:
    There are 3 options to flash:
    • Full firmware
    • System/kernel/core only: this is only the
    • Application software: this is only the AllAppUpdate.bin (plus some additional files).
    Actually you have a few more options:
    • You can flash a new and/or boot logo to your unit by copying the lsec6315update binary and your and/or your LOGO.bmp onto a clean USB-stick.
    • You can flash a new config.txt to your unit by only copying that config.txt and the lsec6315update binary onto a clean USB-stick.

    Create the USB-stick for flashing:
    • For a System/kernel/core only flash, copy the lsec6315update and the to a clean fat32 USB-stick. Connect it to your unit and flash it.
    • For an Application software flash, copy the lsec6315update, AllAppUpdate.bin, updatecfg.txt and config.txt to a clean fat32 USB-stick. Connect it to your unit and flash it. Note the above mentioned fyt.prop and config.txt
    • For a Full firmware, copy the lsec6315update,, AllAppUpdate.bin, updatecfg.txt and config.txt to a clean fat32 USB-stick. Connect it to your unit and flash it. Note the above mentioned fyt.prop and config.txt
    During flashing, let the software do its job and don't start playing with buttons, knobs, air conditioning, etcetera. After reboot wait 3-8 minutes more for some post-flash steps.

    IX. If everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo.

    - Download a fresh firmware from your reseller.
    - Unzip it to an SD-card/USB-stick (as normal)
    1) Simple solution: Put the USB-stick/SD-card in your unit and wait till it reboots and starts the flashing.
    2) More complex softbrick:
    • Put the USB-stick/SD-card in your unit
    • "push" the Reset (RST) with a paperclip or something like that.
    • When the boot logo appears, reset the unit again. Now the flashing process should start.
    3) Most complex softbrick:
    • Put the USB-stick/SD-card in your unit
    • "push" the Reset (RST) with a paperclip or something like that.
    • When the boot logo appears, reset the unit again. Now the flashing process should start.
    • Sometimes you need to reset up to 3x times.
    • If after 3 times resetting the flashing still doesn't start, your recovery partition is damaged.
    (or use your self created backup using the script from post #4)

    Backup the application data of your uis78672 (ums512) unit (or your sc9863a (uis8581a) unit).​

    This is especially useful if you do not have an official firmware from your supplier yet. The kernel/cores are universal on these FYT uis7862/uis8581a units, but the AppUpdate is not.

    This works on both the uis7862 and the uis8581a. I don't have this ui8581a unit but it is actually the same for these two types of FYT units.
    It does not backup the 360 camera setup/config!
    It will actually also make a backup of your sc9853i unit, but there it requires some extra follow up steps. Next to that: There are already many firmwares that can simply be downloaded.

    This script will create a directly flashable backup!

    Backup script

    • Unzip the contents of this zip onto a clean usb-stick.
    • Insert it into your unit and let it reboot.
    • It will make a backup of the specific firmware part into folder BACKUP onto the USB-stick (which should therefore have >1GB free space).
    • When it is done, you will have four (4) files in this BACKUP folder: AllAppUpdate.bin, config.txt, lsec6315update or lsec6316update, and updatecfg.txt
    • If you copy these four files to a clean usb-disk and also copy an (for uis7862) or a (for a uis8581), you can always restore your unit to its factory settings.

    Restore option I:
    For a uis7862: Copy the AllAppUpdate.bin, config.txt, lsec6315update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.
    For a uis8581: Copy the AllAppUpdate.bin, config.txt, lsec6316update, updatecfg.txt from the BACKUP folder onto a clean USB-stick. Insert that one in your unit and let it flash your unit.

    Restore option II:
    In case option I still gives you an unstable system, you need to do a complete flash. For that you also need to flash a new kernel/core.
    • Download the universal kernel/core for uis7862 (current version: 07 December 2021). (For uis8581 download yourself)
    • Unzip it to the same USB-stick which you used in "option I". This means that this content will be added to the USB-stick. It will not replace the content.
    • Insert that one in your unit and let it flash your unit.

    Mods and Tweaks​

    1. Modded Joying media player
    Removed. All media players now have folder based play options.
    2. disable or (re-)enable the mediaplayer at startup/wakeup.
    FYT mimics the behaviour of many builtin car units that it continues with the player or radio or BT connected phone player, that was active during "switch off". These 2 scripts can disable that behaviour (I want silence when I start my car) or enable it again (default FYT behaviour). This is a shameless copy of @gordgelin scripts with a slight modification where @gordgelin adds the command at the 16th line whereas most standard firmwares have max 8 lines or so. My script simply adds the line to 4th line of config.txt. Works on uis7862 (ums512), sc9863a (uis8581a) and sc9853i (could easily be ported to other FYT units as well).

    3. Script to correct the fytmanufacturer id in the fyt.prop
    In case you get a big yellow bar with red letters in the top of screen saying "UI and MCU does not match", your fytmanufacturer id ( XY) is incorrect.. (See also Q13/A in post 1 and section II. and vI. in post 2.
    If you still know the original id, you can use this script to correct that entry again without completely reflashing your unit.
    Read the README.txt carefully !!
    You can download this script: ChangeFytmanufacturer

    4. Script to correct the screen orientation of your unit.
    Probably you are here because you did not read the Forum well enough (especially "VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller" in post #2 and flashed a firmware to your FYT with a different screen orientation.

    What does this script do?
    It can set the correct orientation for your screen. This is set by a property called "ro.sf.swrotation=xy", where xy is a value of 0, 90, 180 or 270 . Use the value from YOUR ORIGINAL firmware in the config.txt.
    You will find a config.txt with this script that contains the default value for most units being ro.sf.swrotation=90
    In case you have no longer your original firmware you simply need to experiment with the above values until you have the right one.
    You can download this script: ro.sf.swrotation
    Hi, my little contribution for 7862 and 8581a

    Fyt Factory