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

Search This thread


Senior Member
May 9, 2013
Thats not true. I have perfect reception. I even get Danish radio ststions and the border is 60km away from us.

If you have an active antenna you have to connect the blue cable.

Or in the settings on some head units you have to turn antenna power on.


Senior Member
May 9, 2013
Of what? Antenna, Radio? Map? Do i have to take out the radio and show the blue wire? What do you want?



  • Beweis.png
    959.7 KB · Views: 18


Senior Member
May 25, 2022
Your unit it is t10 not fyt, no ? t10 unit have strog radio signal, i talk with isudar
this cable for antenna+12v signal=0 !



  • 61wS3XurtLL._AC_UL210_SR210,210_.jpg
    4.9 KB · Views: 10
Last edited:


May 7, 2023
Does anyone know how to control the sensitivity of the BT microphone? External microphone connected. Please how to find fiction step by step. Thank you


Senior Member
May 4, 2010
Your unit it is t10 not fyt, no ? t10 unit have strog radio signal, i talk with isudar
"Listen" to what @Clandaries says.
This has nothing to do with either FYT or another type of unit (MCD/E, Topways, whatever)
This has to do with having an active antenna or not.
If you have an active antenna, you need to connect the "blue wire". It is a blue wire on a FYT. If your unit is not a FYT, the color may be different.

Edit: The wire should be called "ANT power" or "Antenna Power" or something alike.


May 7, 2023
Does anyone know how to control the sensitivity of the BT microphone? External microphone connected. Please how to find fiction step by step. Thank you


Senior Member
May 25, 2022
"Listen" to what @Clandaries says.
This has nothing to do with either FYT or another type of unit (MCD/E, Topways, whatever)
This has to do with having an active antenna or not.
If you have an active antenna, you need to connect the "blue wire". It is a blue wire on a FYT. If your unit is not a FYT, the color may be different.
i tell, i dont have active antenna, it is car antenna, please see cable
what modele of antenna you have ?


Senior Member
May 25, 2022
surfer63, i have app (tv app) why i cant use, i dont see video, it is problem from dev app ?
the older versions worked, but I can't use them anymore, ask for an update, I connect to the radio via hotspot, the internet works
i need too activate in radio video codecs >?, i tried evrything, reset radio, reinstall app...
"exoplayer_001" error
mp4 work ok
Last edited:


Senior Member
May 4, 2010
i tell, i dont have active antenna, it is car antenna, please see cable
what modele of antenna you have ?
Our posts crossed.
So, you purchased that 12V antenna amplifier in combination with one of those two wires in the image below?
Did Isudar told you to buy that? And then connect the red wire to the blue "Ant power" or "Ant cont"?
surfer63, i have app (tv app) why i cant use, i dont see video, it is problem from dev app ?
the older versions worked, but I can't use them anymore, ask for an update, I connect to the radio via hotspot, the internet works
i need too activate in radio video codecs >?, i tried evrything, reset radio, reinstall app...
"exoplayer_001" error
mp4 work ok
I really have no idea. I never used such an app. Did you contact the developer? [email protected]
Last edited:


Senior Member
May 25, 2022
edit post, cable for car antenna without amplifier
i put only red cable from amplifier to 12v power to blue from radio,but signal increase ZERO, my radio signal work ok only in town after 15 km dissaster signal, with rns 510 signal it is more strong, this radio isudar v72 it is dissaster !
Last edited:


Senior Member
Jan 5, 2012
you cant, this chinese radio it is very bad for radio signal, signal it is strong only in town, i have isudar v72, not recomand to buy anything from isudar !
No idea about Isudar specifically, but my FYT 7862 (Mekede M500s) has a great reception. I would even say FM reception is slightly better than my original Kia stereo (made by LG I believe).

I use adapters to connect to my cars OEM aerials for FM & GPS and both work perfectly.
The FM aerial has no power connected from the radio.

Find the wiring diagram for your cars original radio and see if it has an ANTENNA POWER wire, or something named similar.
If it does have this wire then you need to connect that to ANT POWER/ANT CONT on your Isudar working and enable antenna power in the settings (Settings > Factory > Original Car Agreement > Antenna Power).

If it does not have this wire then do not connect anything to the antenna that has power as it can cause interference on passive aerials.


Feb 11, 2011
Hello all,

I have a Joying JY-FQS08N4G-B and a problem.
Resolution 1280x800

I wanted to change the key assignment and have installed the modded
Now I have a black screen.
I have tried to install the update from Joying, but no success.
I can't confirm anything, the screen stays dark. Only the soft keys are illuminated.

Can you please help me.

Top Liked Posts

  • 1
    Does the ’Acc’ wire to headunit come directly from your car wiring or from the CAN-adapter? By knowing that we would be able to distinguish whether it is the car acc wire logic being less desired or CAN-adapter fw/settings issue.
    Thanks for replying. The 'Acc' wire comes from the car wiring. The stereo was supplied with the correct plug for my car and interfaces with the climate controls and basic dashboard info like the FM frequency.
    What have you figured out or considered from the posts that have covered these issues for you?
    Thanks for replying too. WIth regards to the switching off issue (1), I've tried updating the firmware to MD Edition and switching the +12VDC and ACC in the Factory settings menu. It's receving power when the key is in the ACC position as the stereo stays on for 10 seconds, which is the interval I set in the settings. The stock stereo supplied with the car used to stay on for 20 mins, or until the driver's door was opened, whichever was sooner.

    As for the mono FM audio issue (2), again I was hoping updating to MD Edition might help. I also swapped the antenna cable from a single FAKRA to double FAKRA, to take advantage of both aerials on the car. I tried using NavRadio+ (free edition) rather than the included FM radio app. I searched the forums for keywords like "mono" and "FM" but all the results seemed to relate to phone Androids like Moto G. Apologies if I missed a previous thread that covers either of these issues.

  • 4
    Can I add new apps to "app" folder in AllAppUpdate.bin instead of "vital-app" folder.
    In the APP folder, applications will be "system".
    From the folder Vital-App will be installed as "third party", with the possibility of removal.
    Hello @surfer63 , can I use ANT wire for powering up my fan (i.e. could this 12V output power up my fan current-wise)? The fan I bought to install on my unit is a 70mA ball bearing fan, as it was advised here... The reason for asking this question is that my unit has two wiring harnesses, the one that has ground (required for fan -) also has ANT wire and the AMP wire is on the second wiring harness. So, aesthetically, it would be neater to use both (+) and (-) from one wiring harness. (I know I wouldn't see wirings after installation, I'm just curious to know if ANT could be used for this purpose but I can live with using AMP wire). Thanks
    Why not just take ACC?
    Can someone inform how can I run this unit at home (not inside car)? I apparently need some power adapter but i have no idea about it. If possible, can you link the item on aliexpress etc.? Thanks.

    I have a bench test setup for the units I resell, just chopped up a spare harness and spliced into some banana plugs connecting to a 12v power supply. To power on the unit, you just need +12v on the yellow and red wires (pins 2/3), and ground the black wire (pin 1). You can also wire up anything else you want to test, such as illumination, reverse, speaker output, etc
    Hi all,

    So I decided to give the firmware flashing a try.

    I'd edited the fyt.prop from the AllAppUpdate.bin of the Joying 1280 x 720 MIPI Screen New UI firmware using Notepad++ to change ro.fyt.uiid= from 2 to 4, then got the 5 files in my formatted USB drive and got down to it.

    I ended up with this:


    And after the GOOGLE word loading was done and it rebooted I got this:


    And it went into a loop :cry:

    Am I understanding it correctly that the problem was specifically with the config.txt file and not the rest of the files?

    Anyway, I decided to download a fresh copy of the Joying firmware, and this time I thought about what @bluemask69 said about not changing the uiid and I decided to try a Hail Mary and straight copying the 5 files from the new download over to the (re)formatted USB drive, unmolested :LOL: i.e. I did not make any changes at all, ro.fyt.uiid=2 was left untouched.

    And it worked :love: I did not get any errors during or after. The GOOGLE word during the loading was upright this time ... the previous failed flashing the GOOGLE word loading was -90degrees like the above photos.

    I don't understand though ... in a full firmware flash, the original company's boot animation still remains? I see @surfer63's guide to change boot animation, but does anyone know where I get my hands on the Joying boot animation that corresponds with this particular firmware? EDIT: Nevermind, I found this firmware’s “Powered by Android” logo … selected it, and now the original company’s is gone.
    Hi all,

    So I'd flashed my unit with the Joying 15 May 2023 update. Everything runs fine.

    However, it seems installing launcher from @mariodantas' FYT Factory doesn't work now? Or at the very least, it seems it doesn't work if it's a "UI4" because it does not overwrite the stock UI4. I tried a "UI6" as well and it does not overwrite the stock UI6. Or did I miss any setting after the flashing?

    I'd tested installing 1 which is "UI20" and it works, so I guess it's just not overwriting the stock launcher.
    Hi all ... I had an issue which turned out to be a setting I assume I’d set previously (I can’t remember it) but got wiped during the flash to the Joying 15 May 2023 update. I assumed it was a problem with the firmware, and I tried PeaceOS, which faced the same issue … I later realised what the issue was and set it correctly.

    However, due to curiosity and (no offence, please) PeaceOS isn’t quite for me … so I decided to revert to the Joying firmware, but at the same time try some modifications:
    • Unzipping AllAppUpdate.bin and deleting UI4 and UI6; default launcher in config.txt was changed from UI6 to UI13
    • Deleting the stock Joying Radio and Music folders and replacing them with the ones from PeaceOS (if this is something frowned upon, I apologise, but it was for testing purposes)
    I repacked this AllAppUpdate.bin using WinRAR with compression set to “Store” and put it in my USB stick along with the other files.

    And I got the config.txt read file fail + loop again 😭

    I tried several variations, but nothing worked … kept ending up with the same thing.

    I then decided to try 1 last thing - download 7Zip and used that to repack AllAppUpdate.bin …

    … and it worked 😍

    Conclusion: WinRAR works only with unzipping … I can unzip firmwares and AllAppUpdate.bin files with it, a firmware update directly unzipped into a USB stick using WinRAR without any modifications works … WinRAR just isn’t working correctly (at least, for me) with the repacking of AllAppUpdate.bin. For this repacking, it really is best to use 7Zip as stated in @surfer63 ’s guide.

    So I currently have the Joying 15 May 2023 firmware with PeaceOS’s black-and-white stock music and radio apps, and I am able to install / uninstall UI4s and UI6s from @mariodantas ‘s site. All seems stable for now … will monitor for a bit.
    I got you. So basically, adding those apks to "app" folder is safe, right? I just might not be able to uninstall them (that I'm not planning to do so) like a normal app
    True, but note that the space in the OEM partition has a limit)
  • 51
    Last revised: 13 August 2023

    This thread tries to be a "one fits all" thread about FYT based Spreadtrum Unisoc uis7862(s) (Unisoc ums512) and uis8581a (sc9863) 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 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

    To start with: the uis7862 and uis7862 are 100% identical and compatible. The 7862s is just the same CPU but slightly faster.

    CPU uis7862 64bit 8-core (2x ARM Cortex-A75 @ 1.8 GHz, 6x ARM Cortex-A55 @ 1.8 GHz)
    CPU uis7862s 64bit 8-core (2x ARM Cortex-A75 @ 2.0 GHz, 6x ARM Cortex-A55 @ 2.0 GHz)
    CPU uis8581a 64bit 8-core (4x ARM Cortex-A55 @ 1.6 GHz, 4x ARM Cortex-A55 @ 1.2 GHz)

    CPU: uis7862 (ums512) versus the new uis7862s (ums512). Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
    CPU: uis8581a (ums sc9863) versus the uis7862. Specs/Benchmarks/Info. (Also allows you to compare with other CPUs).
    Android version: Android 10 (API/SDK 29); Fake Android 11 & 12 (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

    Firmware always comes with an update/flash binary, a kernel zip, an application layer bin and a few config and additional files/scripts.
    The kernel, which contains the basic Android layer with drivers and kernel modules is inside the for a uis7862, and inside the for a uis8581a.
    The update/flash binary is the lsec6315update for the uis7862, and the lsec6316update for the uis8581a. Those lsec update/flash binaries check for the right hardware and the right kernel zip. For example: You can't flash the kernel zip from a 782(s) CPU onto a uis8581a.
    The application layer is the AllAppUpdate.bin. It is 100% compatible over the uis7862(s) and uis8581a. Note that FYT is bad in multi-resolution. Although the application layer should be compatible, they make differences for all resolutions to 1280x720 and those for 2000x1200. Also the Tesla units get apks with other resolutions and an extra aircondition apk. Funtionally they are 100% identical.

    Atoto, Ebilaen, Eki, Farcar, Funrover, Idoing, Isudar, Joying (only uis7862), Junsun, Mekede, NaviFly, Sinosmart, T'eyes (only uis7862), Winca, Zhan. There are more resellers, but not all of their models might be FYTs. Same for some resellers in this list.

    A few remarks about which CPU to choose (my vision).
    The UIS8581a is in general 15~20% slower than the "standard" uis7862, which is again about 5~10% slower than the "new" uis7862s.
    What will you notice in real life: Almost nothing!
    When to chose a uis7862(s)? If you have a 2000x1200 resolution screen, I would go for the 7862 or the 7862s. Bigger screens require faster CPUs. The 8581a is strong enough to "power" such a screen, but here you might notice the difference when fast screen rendering is required. This is not for video, but in case of navigation apps that need to calculate long routes or calculate/redraw every split-second for example, but nowadays with OpenGL rendering in those apps it might not be an issue at all.
    If you compare the uis8581a with the previous intel airmont sc9853i, which FYT no longer makes, the uis8581a is again ~20% faster than the sc9853i. I never had the idea that my previous sc9853i was slow, on the contrary.

    Go for 4GB memory or more. 3GB might be enough for a "light user", but you might experience delays in starting new apps as other apps first need to be stopped/swapped out.
    Note that these units still come with EMMC flash memory, like in cheap phones, instead of the (much) faster UFS (in better phones). So loading apps from storage will not be much faster on a 8581a versus a uis7862(s).

    Q&A - Questions & Answers

    Q1: I already see uis7862(s)/8581a units having Android 11 and even Android 12, what about it?
    These Android 11 & 12 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(s) and uis8581a) units compatible? Is all (uis7862(s) and 8581a) firmware compatible?
    See also above under "General unit information".
    The uis7862(s) units based on FYT are all hardware and software compatible. Also the uis8581a units based on FYT are all hardware and software 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.
    Firmware always comes with a kernel (uis7862(s) ->; uis8581a -> and the application layer AllAppUpdate.bin. The kernels are only compatible for that CPU. The application layer is compatible for the usi8581a and the uis7862(s)

    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 (or uis8581a) supplier to my FYT uis7862 unit (or 8581a)?
    NOT directly, but with some tweaks: Yes. Read post #2 carefully and especially section VIII. Note that you cannot flash a uis7862 kernel to a ui8581a and vice versa.

    Q7: Can I flash the MCU firmware from another FYT uis7862/uis8581a to my uis78962/uis8581a 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 less safe as malware, etcetera have a much better 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. Note that there is a difference for units after approximately August 2022 (Pro models) and units before that time.

    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?
    uis7862: 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.
    uis8581a: Copy the lsec6316update 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

    Q23: I need a SIM/Carrier to work with my FYT unit and my provider
    • make a text file named "IMEI0" (no extension)
    • edit it to put in two IMEI values that are valid and compatible with your provider. (one for each SIM slot)
    • copy to USB stick and plug it into your unit
    • Your unit will (should) show a notification "imei changed".
    After reboot your unit should have the new IMEI in the settings. (thanks to @j-5)

    Q24: How do I enable splitscreen on these units?
    See post #1394 for an explanation with screenshots.

    Q25: How do I change the ringtone (and/or thereby lower it in volume) on these 7862(s) and uis8581a (sc9863) units?
    See post #1951 on how to do this. (This is an absolute shameless copy of a 4pda post by tyuktha and Monkey_D_Luffy. All credits go to them.)

    Q26: How do I make a screenshot (instead of a reflecting, not so good and not always sharp, smartphone photo).
    • Drag down the status bar at the top of your screen.
    • Drag it a second time further down.
    • In the top right you will find a scissors icon.
    • This scissors icon can be used to make a screenshot.
    • Your screenshot will be saved in "Pictures/screenshots" on your internal memory.
    Q27: SOC or SOM? What is the difference?
    A lot of times we talk here about SOCs, but are these FYT "motherboards" now SOCs or SOMs?
    A SOC (System on a Chip) contains the central processing unit (CPU), GPU, memory, input/output interfaces, and more.
    A SOM (System on Module) contains all required system functions into a module, including processor, storage (eMMC or Flash), memory (DDR) and I/O controller and other components. You can more or less say that the FYT motherboards have a SOC (uis7862(S) or uis8581a or sc7705) as a SOC and combine that in a SOM with often the same hardware components.
    So I would prefer to talk about SOMs in case of SOCs when talking about the motherboards inside these FYTs, but actually it is a grey area for the FYTs. They build relatively modular to be able to use the same hardware with different CPU (SOC) and memory configurations.

    Q28: Bluetooth: Connect other devices and issues with that. Differences between "uis7862/uis8581 and newer US7862S.
    (credits to @gordgelin)
    The "older" T'eyes CC3, Joyings and Mekedes come with an internal BT chip and an RealTek Bluetooth chip. In the config.txt they are respectively mentioned as sys.fyt.bluetooth_type=0 and sys.fyt.bluetooth_type=1, where sys.fyt.bluetooth_type=1 is always the default. value 0 gives you more possibilities, but perhaps at the cost of fewer "higher"BLE functions.
    The new uis7862S models come with a Qualcomm BT chip and have the sys.fyt.bluetooth_type=7 inside the config.txt. You can change this to 0 to connect more peripherals, but loose audio HD streaming.
    In post #2556, @gordgelin shows images of the several BT chips. See also the 5-6 posts before that post.
    Some ui8581a/sc9863 units also come with a sys.fyt.bluetooth_type=8. What kind of BT chip this is is currently unknown (hint: Please someone send me the details ;)).

    (End of Q&A - Questions & Answers)

    FYT Settings explained

    Thanks to @hanichl for first write-up.
    Thanks to @mastrv for corrections and further additions.
    Thanks to @leo06 for corrections on GPS mix Setting/explanation.
    Thanks to @daviddosa for further additions.

    Note that 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.
    Joying now also wrote an online manual on the JOYING FACTORY SETTING USER MANUAL and the JOYING STEREO SETTING USER MANUAL.



    • Wlan (same as stock Android)
    • Data Usage (same as stock Android)
    • SIM Info (same as stock Android)
    • More (same as stock Android under Advanced Networking)
      • 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 ( On/Off: emits 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 on older units (brand units: before approximately July 2022; for brandless units you never know)
    • 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; mode 1 -> GPS only; mode 2: GPS + GLONASS )​

    - Apps​

    ( show / remove installed apps; same as stock Android )​

    - 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 (Strange Chinese translation: (Dis)Allow display of video during driving . It means when handbrake is not used.)
    • 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 in reverse gear, does 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 = Will reduce/mute media/radio when "speaking" navigation instruction; OFF = media will not be reduced/muted when navigation app issues instruction ). Some other translations than English mention this as "audio mix between navigation and media". Note also that most modern navigation apps have a setting themselves to mute or even shortly pause the media player when issueing a navigation instruction.
    • 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 ). Only works if "GPS mix" setting (one above) is set to ON.
    • 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 )
    • Launcher App Setting (This configures which app is displayed in the PIP window of launchers that have this PIP-window)
    • 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 ( shows external temperature in notification bar when CANbus is present)
      • Automatic start and stop ( ?? )
      • Radar Display ON/OFF ( When car is put in reverse gear, it will show the reverse camera or an image with edges of your parking sensors (if you have them))
      • 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 (Change how far the parking lines curve. This to adjust it correctly to your camer/car)
      • 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 (updates software in CANbus decoder; Be careful: this can soft-brick your decoder)
    • Car Model ( define the canbox manufacturer, params )
    • Back MIC switch -> When set to "On" the internal microphone is switched on, but only new M6 pro hardware. When set to "Off" the internal microphone is switched off. Use this "Off" setting when you have an external microphone connected. Do not use both microphones at the same time as it will only give you worse microphone performance. If you have an old(er) firmware and not the new M6 pro, you need to use this trick as described by Vitaly (@gordgelin ).
    • 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 (Try this in case you have an AHD camera on a non AHD unit, or the other way round).
    • Boot Screen logo
    • Set Screen
    • Touch Screen Calibration
    • Panel Key Learning
    • Front View
    • Cancel the reverse into the front view (If you have back and front camera, it will switch to front camera when "leaving" the reverse gear)
    • MCU Panel Key (Set buttons like Band/Radio, Phone, Music) on the side of the screen to On/Off.
    • Unknown sources ( allow apps to be installed from unknown sources )
    • Door lock interference
    • Reverse power supply (Be careful !: Switch functionality of Cont and ACC inside radio)
    • Volume balance settings
    • MCU upgrade (Only upgrade the MCU firmware; Be very carefull to ONLY use the firmware for your type of unit)
    • Backlight current adjustment (Set display brightness but be carefull. It can blacken your screen entirely. There is no safe low position. passwd: 5768)
    • Home Launcher Selection (Option to chose one of installed FTY launchers. passwd: 8086)
    • 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 (Switch off head unit or switch to deep sleep, when ACC is turned off)
    • 360 switch
    • Backup Test
    • Plug In Serial Device Setting


    • Location (same as stock Android)
    • Security (same as stock Android)
    • Language And Input (same as stock Android)
    • Google Settings (same as stock Android)
    • Backup And Reset (same as stock Android)
    • Account (same as stock Android)
    • Delay Power Off When ACC Off (After ACC of the delay time to put unit in sleep or off: OFF / 3 sec / 10 sec / 3 min)
    • 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.
    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.
    • 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 (@mariodantas ) created/build the website "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.)
      • He now also created a new firmware (MD-edition) that after flashing gives you some very handy and essentials options for on-the-fly rooting and root access for selected apps, starting apps from boot, make firmware backups, save your /data/data partition, etc.
    • @seb21 made a modded combination of the com_syu_ms.apk and a Config.apk. This combi allows you to change the "hard-coded" steering wheel buttons in case you have/use a CANbus and add "no kill" functionality. See Modded
    • getinfo script. This is in fact an extension of my HWGetInfo.apk, but as an lsec script. It gives more info than the HWGetInfo.apk as it runs as a flashable script thereby having full access to the system.
    • Disable airconditions app on Tesla style uis7862/8581a units (see post #1780)
    • Modded Launcher 34 (see thread "Modded Launcher 34 for uis7862(s) and uis8581a (and probably uis8514a)")
    Last revised: 12 July 2023.

    More about Firmware(s)​

    This post is valid for FYT uis7862(s) (ums512) and uis8581a (sc9863) units running Android 10 or fake Android 11 or 12.

    Contents of a firmware zip:

    Note that the firmwares for the uis7862 and the uis8581a only differ on the flashing binary and the kernel zip. Configuration files are the same. Some resellers deliver a firmware that contain two kernel zips and two flashing binaries, as the flashing binary will only work on the hardware it is intended for flashing the correct kernel zip.
    • Kernel:
      • the kernel zip for the uis7862(s).
      • the kernel zip for the uis8581a.
      • The or 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 for the uis7862 "should" be interchangeable between all 800x480, 1024x600 and 1280x720 models. The same for the for the uis8581a. Special resolutions come with specific lcdconfig.txt files.
    • The binaries that do the flashing of the firmware:
      • lsec6315update for the uis7862(s)
      • lsec6316update for the uis8581a.
      • These are the binaries that do the flashing of the firmware, optionally install a boot image or boot animation, optionally run scrips from the lsec_update folder after the flashing process itself has finished. These binaries can also be used to only flash a boot image, boot animation, or run scripts.
    • AllAppUpdate.bin: Special zip 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 or use the scripts from post #3, bullet #4.
    • config.txt: file comparible to the build.prop which can contain additional properties.
    • 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. These are very limited cross-compatible. do not flash these if your do not know exactly what you are doing.

    I. (Factory) Firmwares

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

    * Modded Firmwares:

    See for compatibility 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. You see that we specify 0 from the rotation. This is because android is normally for portrait like screens. Our landscape models have a value ro.sf.swrotation=90 decrees as they are actually 90 degrees rotated. A Tesla style unit therefore is again 0 degrees and sometimes 180 degrees.
    ro.product.locale = pt_BR
    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).

    28-05-2023: I added two scripts in post #3 under bullet #4 to let you flash any AllAppUpdate.bin to your uis7862(s) or uis8581a unit.

    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. (like for example from inside a folder "AllAppUpdate" from an unzipped AllAppUpdate.bin.
    When using zip you can do "zip -r -0 --password 048a02243bb74474b25233bda3cd02f8 ./AllAppUpdate.bin *".
    When using 7zip you can do "7z a -r -m0=Copy -p048a02243bb74474b25233bda3cd02f8 ./AllAppUpdate.bin *".

    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> and the ro.fyt.uiid=<z>. This 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 or
    Again: the is the kernel for the uis7862. The is the kernel for the uis8581a.
    (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, with hardware drivers and kernel modules and "the basic Google apks" , but without additional unit application layer apks like the launchers, radio, music player, etcetera.
    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 own hardware, mostly through the MCU.

    This is theoretically identical for all FYT uis7862 units and can therefore be used on all FYT uis7862 units. This is theoretically identical for all FYT uis8581a units, apart from T'eyes units. (DISCLAIMER: Experimenting with this falls under your own responsibility).
    You can unzip the or and replace the boot.img (and root it) 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 and Note that T'eyes does it slightly different.
    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/lsec6316update binary and script (and what about "universal" scripts)

    The flashing process consists of a number of steps:
    1. flashing the core/kernel software ( for uis7862(s) and for the uis8581a)
    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(s) and lsec6316update file on a uis8581a.
    A USB-stick used to execute a script on a uis7862(s) or a uis8581a should contain:
    lsec6315update (uis7862(s))
    lsec_update/ (uis7862(s))
    lsec6316update (uis8581a)
    lsec_update/ (uis8581a)
    "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 on a uis7862 or use the script on a uis8581a. Note: 99.9% of the time these scripts are identical as you work on the application layer.
    • Flash a new config.txt to your unit: Simply copy your modified config.txt and the lsec6315update or lsec6316update binary onto a clean USB-stick.

    For more info on writing scripts, see below.
    Creating your own lsec script to copy/replace a modified FYT apk.

    If you want to create your own script to flash a modified FYT apk to your unit to replace an existing FYT apk, you can use the following steps.
    Below is described for a uis7862 (ums512) and for a uis8581 (sc9863a). These units are compatible.
    On your USB-stick you need to have the following files.
    lsec6315update                       (binary)
    lsec6316update                       (binary)
    lsec_updatesh                        (folder)
                    (shell script)
                    (shell script)
    OEM_APP                              (folder)
            190000000_to_be_replaced     (folder of the apk)
                    190000000_to_be_replaced.apk  (some apk we want to replace)
    Inside folder "lsec_updatesh" you have to create two shell scripts (on Windows NOT with notepad, but a good ascii editor).
    The binary "lsec6315update" and shell script "" are for a uis7862.
    The binary "lsec6316update" and shell script "" are for a uis8581.
    (You can do the same for two other type of FYT units: the "lsec6521update" and "" for a sc9853i. And the "lsec6523update" and "" script for a 7731. Note that these two units are also compatible. I have created scripts (for other purposes) that contain 4 binaries and 3 scripts, as the script is the same for the sc9853i and the 7731).

    Note that for replacing FYT apks, the script and the script can be identical as they use the same firmware when it comes to AllAppUpdate.bin.
    Let's say we have an apk called 190000000_to_be_replaced.apk.
    The following is for ALL 7862 and 8581 FYT units, but not T'eyes units. Those T'eyes guys do it differently (and let you pay for a lot of things).
    On ALL the other non-T'eyes FYT units, the apks are installed in folder "/oem/app" inside their own folder "190000000_to_be_replaced". In that folder we then copy the "190000000_to_be_replaced.apk".
    We use the following template for our script.

    #Remove the current app data/program cache/cache. This is only necessary for some applications, but it never harms
    rm -rf /data/dalvik-cache/profiles/190000000_to_be_replaced
    rm -rf /data/data/190000000_to_be_replaced
    rm -rf /data/dalvik-cache/arm64/*190000000_to_be_replaced*
    # Copying file to /oem/app
    cp -r /storage/sdcard1/OEM_APP/* /oem/app/
    # Updating folder/file access rights
    chown -R 0.0 /oem/app/190000000_to_be_replaced
    chmod 755 /oem/app/190000000_to_be_replaced
    chmod 644 /oem/app/190000000_to_be_replaced/190000000_to_be_replaced.apk

    If your script needs to do other things you can take a look at some of the scripts in my github repository.

    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(s_ units. The same is valid for the for usi8581a 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 and lately also id=1) 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 (of for a usi8581a) 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 (or the lsec6316update for a usi8581a).
        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!
    • Inside this file you will find a line with ro.fyt.uiid=<x>. Write down that number as well!
    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 (This does not work on Teyes units unless you use the Vincent Vega mods from @gordgelin).
    • 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 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!

    appBackup 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. 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).


    2. 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


    3. 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


    4. Two scripts to flash any FYT AllAppUpdate.bin to your unit.​

    EDIT: Some of the new Mekede M6Pro models and comparables from other resellers come with an lcdconfig for their 2000x1200 K screens. My scripts below do not take those files into account. I "think" that when you encounter an lcdconfig on the new downloaded firmware, you have to remove it and stick to the one installed on your unit.

    What do these scripts do and how to use them
    These scripts are for both the uis7862 (ums512) and for the UIS8581a (sc9863a).
    The AllAppUpdate.bin, that contains the FYT application layer, is for both CPUs the same.
    The scripts make a copy of your current config and use that to flash your unit using that config of your unit.

    Some information to start with
    FYT units do have an MCU and based on the type of manufacturer you can have a different MCU firmware. This MCU firmware is totally different from the normal downloadable firmware that you can get for your unit having new functionality, bugfixes, etcetera..
    The Android layer is universal on FYTs but works slighly different for different MCUs.
    How this Android layer should act on the underlaying MCU is determined by a property called which can have several values.
    A second and third property are the:
    • sys.fyt.bluetooth_type property which is normally 0 or 1, but on the new M6Pro/M6Plus models anything up to 7
    • ro.sf.swrotation. This property defines the screen orientation and is in 95% of the cases 90 (degrees), for Joyings often 270 and for Tesla screens (0 or 180).
    These properties are in the fyt.prop file and in the config.txt file. These files are copied from your unit onto the usb-stick by the pre-flash script.


    Steps to perform
    1. Take a clean FAT32 formatted USB-stick (or a (micro-)SD-card in some USB reader/writer).
    2. Copy the contents inside the "pre-flash" folder onto the USB-stick (not the pre-flash folder with contents, but the contents inside the pre-flash folder).
    3. Insert it into your unit, let it reboot and go into recovery mode, and wait until the green message tells you that you can remove it again.
    4. Delete the "lsec_updatesh" folder including contents on your USB-stick !
    5. Make sure to keep the "myconfiguration" folder and check its contents: It must contain a config.txt and a fyt.prop. If correct: copy this myconfiguration also to a save place. You never know when you need a backup. If the folder does not contain those files or one of them, then don't continue but ask in the forum.
    6. Copy the AllAppUpdate.bin that you downloaded somewhere onto the USB-stick.
    7. Also flashing the or
      • UIS7862: If you want to flash the kernel as well, copy the onto the USB-stick.
      • UIS8581a: If you want to flash the kernel as well, copy the onto the USB-stick.
    8. Now copy the contents of the "flash" folder onto the USB-stick.
    9. Check your "lsec_updatesh" folder. Do you now also have a "lsec_updatesh (1)" folder, or inside the "lsec_updatesh" folder something like a "7862 (1).sh"? It means that you did not delete the "lsec_updatesh" folder on the USB-stick, or that your file manager does not overwrite on copying. In this case: Redo step 4.
    10. Copy (not move) the config.txt inside the "myconfiguration" folder into the root of the USB-stick.
    11. You can now flash your unit using this USB-stick.

    • If you are thinking of using this in combination with @mariodantas' kernel, you need to know what you do. Mario's kernel comes with its own scripts and fmc app. Of course you can combine this if you know what you do, but do not simply copy everything on top of each other on this USB-stick. Please keep it separate.
    • You can also combine it with PeaceOS, but also in this case @LLIyT_HuK's version comes with it's own scripts. So know what you do.
    • The flashing script uses "twipe_data" in its "updatecfg.txt". This will clear your settings and all 3rd party apps which you downloaded from the Play Store or sideloaded from other locations. You can disable that by putting a # in front of the twipe_data line, but that is your own responsibility.
    • Most newer firmwares nowadays come with an lsec script and a fyt_build.prop. This fyt_build.prop comes with a fake property to set Android to 11 or 12. I refuse to go with that absolutely incorrect and despicable behavior and I will not copy it.
    • Once you have made your pre-flash copy of your config, you can also use the flash script to copy any modified fyt.prop or config.txt to your unit without using an AllAppUpdate.bin.

    You can download both scripts in one zip:
    Thanks for the good idea!
    Unfortunately in my case, the cars SWC are all through CANBUS and so I haven't connected the KEY1/KEY2 inputs to the HU at all. In so doing, I am relying on the CANBUS manufacturer to intepret those button presses as "mode, vol +, vol - ", which is unfortunately unable to be remapped at the moment.

    I may just install a simple aftermarket remote to the KEY1/KEY2, to use my current SWC controls, AND the after market ones in parallel. Then I will remap the after market buttons, to whatever I want, eg. Button 1 = Spotify, Button 2 = Tidal etc ".

    Will update if I manage to get the parts off Aliexpress soon!

    Maybe i have solution for you.
    I have modded the ms.apk to add some extra functionality. One of the extras is to modify Canbus based Steering Wheel Controls. The mod is two part : modded ms.apk and settings app.
    All info is in explanation.txt file.
    You must replace your with this modded apk. Mod Config App.apk is normally installed as every apk.