General General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware
- Thread starter surfer63
- Start date
You can't really back up the user installed programs and settings. I tried, the OP said some things that looks like that's what he meant but I spoke to him over DM and turns out I misinterpreted. It's a backup of the STOCK system apps and settings, like what you'd get with a factory reset.How do I get a backup with all the programs I have in it with all the settings ?
Question: On my Atoto, Bluetooth is treated like a source that gets muted when not in use (much like FM or Aux, when you switch away from the "source", it stops playing sound). Is that how it works on other devices as well?
I find it annoying if I'm playing audio from Spotify or some other app in the system, and my phone is connected and THINKS it is playing sound, but nothing can be heard unless I press the Bluetooth app (which then pauses whatever else is playing to switch to that "source").
Notifications and voice notes, for example, is silly like this. I don't want to switch sources to hear the sound, and my phone's speaker won't play them because it thinks the radio is!
Is that just Atoto or do all FYT Spreadtrum uis7862 units work this way?
I find it annoying if I'm playing audio from Spotify or some other app in the system, and my phone is connected and THINKS it is playing sound, but nothing can be heard unless I press the Bluetooth app (which then pauses whatever else is playing to switch to that "source").
Notifications and voice notes, for example, is silly like this. I don't want to switch sources to hear the sound, and my phone's speaker won't play them because it thinks the radio is!
Is that just Atoto or do all FYT Spreadtrum uis7862 units work this way?
There once was a working app called AudioBT. This made a virtual call when playing sounds on the phone.
It was possible to listen to Whatsapp voice notes and after it was played the call ends.
But this is not working anymore because the author is not active anymore. You can find AudioBT in the Playstore.
There are apps called bluetooth streamer, but they are streaming until you press stop.
I try to find an alternative to AudioBT but cant find one.
Maybe it is possible for those people who builds the head units and codes the firmware.
Until now i could not find a good app for forcing a virtual call when playing sounds on the smartphone...
It was possible to listen to Whatsapp voice notes and after it was played the call ends.
But this is not working anymore because the author is not active anymore. You can find AudioBT in the Playstore.
There are apps called bluetooth streamer, but they are streaming until you press stop.
I try to find an alternative to AudioBT but cant find one.
Maybe it is possible for those people who builds the head units and codes the firmware.
Until now i could not find a good app for forcing a virtual call when playing sounds on the smartphone...
So just to be clear, this is how all the units work? It's not just an Atoto thing, the BT system is considered a source that gets muted on all of them?
I complained about this to Atoto, and they actually issues an update that now pauses other sources whenever audio on BT is playing. The problem is, it still doesn't PLAY, as the system is muted unless I press the BT icon, but Spotify, Amazon Music, etc, actually PAUSE for the duration of the audio. Then when it finishes, audio is resumed. This is actually REALLY annoying, because every notification I get pauses the audio for a couple of seconds. I can't hear the notification, but I hear the glitch in the music. It's actually the WORST of both worlds, I'd rather have it play the audio like any other system sound (the way it does if using Carlink as a phone connection) and maybe NOT pause the music? Having it pause the music but still be muted is stupid IMO.
BUT... it shows Atoto is trying to actually address this, this feature was introduced in a March firmware update. That fact alone is huge, because I've mentioned it for months and they said theyd see if there is something they can do and now its... something! I'm speaking to an Atoto Rep about it, she's been following up and says their engineers are looking into fixing it right now. If it can work, that's good news for all of us I guess, I thought maybe this was just an Atoto thing. I know they handle Bluetooth differently (2 bluetooth stacks, one for incoming phone headset/A2DP connections which they call BT1, and a second standard Android bluetooth system for things like keyboards, OBD readers, tethered data sharing etc which they call BT2).
Hi.
About 2-3 updates ago my BT on HU doesnt work.
It doesnt show on BT App on HU aby phones and also I cant find this HU on phone.
What to do?
About 2-3 updates ago my BT on HU doesnt work.
It doesnt show on BT App on HU aby phones and also I cant find this HU on phone.
What to do?
Did you update your unit with a firmware from another reseller? Sometimes the "sys.fyt.bluetooth_type=" is really different having another BT module. Then it will not work.
Buen día.
Compre un Junsun V1 Pro en diciembre, que tiene UIS8581.
He intentado hacer una copia de seguridad con los archivos que se encuentran aquí sin éxito.
También él trató de mejorar el micrófono, sin poderlo, además de que cuando conecta un micrófono externo hace que no capte ningún sonido, ni en el micrófono externo ni en el micrófono integrado.
A ver si me pueden ayudar.
Muchas gracias.
Compre un Junsun V1 Pro en diciembre, que tiene UIS8581.
He intentado hacer una copia de seguridad con los archivos que se encuentran aquí sin éxito.
También él trató de mejorar el micrófono, sin poderlo, además de que cuando conecta un micrófono externo hace que no capte ningún sonido, ni en el micrófono externo ni en el micrófono integrado.
A ver si me pueden ayudar.
Muchas gracias.
And now in English please. Please switch off your auto-translate.
So your backup was not successful. Please explain what happened. This tells us absolutely nothing, so we can't help.
That's not a FYT I think. FYTs do not support OTA updates apart from Teyes (I think).
What kind of unit do you have?
Good morning. I bought a Junsun V1 Pro in December, which has UIS8581. I have tried to make a backup with the files found here without success. I have also tried to improve the microphone, without being able to, apart from the fact that when I connect an external microphone it causes me to not pick up any sound, neither in the external microphone nor in the integrated microphone. Let's see if they can help me. Thank you so much.
So you used Google translate
The question remains the same: What errors did you see? What really happened?
Only saying "I have tried to make a backup with the files found here without success" does not tell us anything.
Last edited:
Thanks for your quick response.
In case of microphone upgrade download config.txt and lsec6316update files, install them on a fat32 usb stick. The radio when connecting the usb stick only does what appears in the photo, without changing anything.
On the subject of backup, I downloaded the appbackup.zip file, unzipped it and installed it on a clean usb to fat32. The text appears the same text of the image.
In case of microphone upgrade download config.txt and lsec6316update files, install them on a fat32 usb stick. The radio when connecting the usb stick only does what appears in the photo, without changing anything.
On the subject of backup, I downloaded the appbackup.zip file, unzipped it and installed it on a clean usb to fat32. The text appears the same text of the image.
Attachments
Similar threads
Top Liked Posts
-
3
There are two solutions:
- Unpack the AllAppUpdate.bin, remove the unwanted apps, repack and flash.
- Use an lsec script that simply removes or disables the apps from the unit.
The second option is actually the simplest and can be used on any "existing" FYT system, where the disabler has the option to enable the app again (requires another script). See attached for the screenbutton an "app_remover" and "app_disabler" script. Extend for your needs.
Note that in few occassions the numbers in front of the package name can be different based on the fytmanufacturer id. Joying for example often has something like "190043001_com.syu.radio.apk" instead of "190000001_com.syu.radio.apk".
I hope these scripts are clear.
Edit: And when modifying these scripts on Windows, use a good editor like notepad++ and not Notepad from windows.2
You are absolutely right. I apologize for my sloppiness. I simply took one of my own scripts and only changed the "190000000_com.fyt.screenbutton/190000000_com.fyt.screenbutton.apk" FYT part, because I had used my script for a priv-app.
I corrected the scripts in above posts.
Thanks for pointing this out.
With regard to the package name: It is 99% of the time the name after the long number for the FYT apps. FYT has taken over SYU in 2015/2016. FYT was the hardware builder. SYU the Android (and before that the WinCE) software builder. That is why most apps are called "<number>.com.syu.<app_name>, while some of the newer apps, also for Teyes, are called "<number>.com.fyt.<app_name>".
And indeed: there are apps to show the package name (my FytHWOneKey apk for example).
And if you use play.google.com from the browser on your PC and you search for example for "Magic Earth", it will show your search result and when you click the app, you see in the address bar something like https://play.google.com/store/apps/details?id=com.generalmagic.magicearth.
The last part is the package name (like for Google Maps: https://play.google.com/store/apps/details?id=com.google.android.apps.maps)
Of course this does not work for the FYT/SYU apps1
Actually the same. Download Marios MD-edition. It installs fmc, which is a 3rd party app, in the same way. Mario makes it a private app (/oem/priv-app), but that is not necessary at all for any normal app.
Or have a look at my carlink installer. It also install libraries.
Edit: Updated the incorrect link.1Absolutely pretty amazed that the new Android Auto (Coolwalk / split screen) works fine on my Joying head unit. Get in the car, phone in pants, unit auto connects, shows live Maps and starts playing audio through YouTube Music.
All wireless and without enabling tethering as well.
Reads aloud new Whatsapp messages etc. Very pleased
-
8
How do I change the ringtone on these 7862(s) and uis8581a (sc9863) units?
This is an absolute shameless copy of a 4pda post by tyuktha and Monkey_D_Luffy. All credits go to them.
As we are not allowed to link to 4pda I will simply recreate it here.
- Create a "btring" folder on your internal memory (see Spoiler "btring folder on internal sdcard"). You can also use the linked btring.zip archive. It contains the folder with contents like configuration, the standard ringtone, the standard ringtone but lower volume and a "the Doors" ringtone (my phone ringtone).
- Move your favorite ringtone into the btring folder
- Open the bluetooth app.
- Click the gear icon to access the settings screen (see Spoiler "Steps in BT app to activate other ringtone": icon numbered 1).
- Scroll down to the Ringtone option (see Spoiler "Steps in BT app to activate other ringtone": icon numbered 2).
- Click on the right side in the line on the "Set" option (see Spoiler "Steps in BT app to activate other ringtone": icon numbered 3).
- Select a ringtone from the folder.
I also added this as Q25 under Q&A - Questions & Answers in post #1
5I also added a Q26 under Q&A - Questions & Answers in post #1 to describe how to make a screenshot on the unit.
I see a lot of shiny, reflecting, not so good images made with smartphones. I sometimes do that as well if I do not have a proper way to transfer images from my unit. In that case a smartphone is fine, but otherwise a proper screenshot is always better.4I have a Mekede M500s with a ro.build.fytmanufacturer=116 (fyt.prop) and a ro.sf.swrotation=90 (config.txt).
I tested it with a Joying AllAppUpdate.bin with a ro.build.fytmanufacturer=43 (fyt.prop) and a ro.sf.swrotation=270 (fyt.prop and config.txt).
I simply used the "pre-flash" script to copy my Mekede 500s config to USB-stick and then flashed the Joying bin using the "flash" script. It all worked fine be it that some apps had slightly different icons and layout, but that is obvious.
Then I took a Mekede AllAppUpdate.bin and flashed it back.
All good.
You can find both scripts in one zip in post #3 under bullet #4.
Let me know your experience and inform me about typos or unclarities in the "00_Readme" or forumpost "Readme".
Anyone wanting to use this in his/her own scripts: be my guest! If you improve it, please let me know.4I just realized that it is really simple to use any FYT AllAppUpdate.bin and still do not get errors of the fytmanufacturer and the like.
I could create a lsec cript that might be called "preflash", which copies from the unit the existing fyt.prop and config.txt out of the /oem/app folder and save it to a folder on the USB-stick called "myconfiguration".
Then you copy any AllAppUpdate.bin to your USB-stick.
Then you unzip a script called "flash-script" to the USB-stick.
The lsec6315update would simply flash the AllAppUpdate.bin and this lsec "flash-script" would simply copy your saved/backuped fyt.prop and config.txt back onto the unit.
And upon reboot you have the new Android apps with your own config.txt and fyt.prop.4
Already working on it but it is the (extended) Pentecost weekend, so I have other "obligations".
Scripts and "Readme_First" have been written as that was easy, but I want to first test it myself. -
42Last revised: 20 May 2023.
This thread tries to be 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.
- 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.
General unit information
Q&A - Questions & Answers
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 (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 (@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 6315_1.zip" 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 syu.ms.apk.
- 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/8581 units.
27Last revised: 28 May 2023.
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:
- 6315_1.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 6315_1.zip "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
Some commands that can be put inside updatecfg.txt
Code: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.
Or you want to improve the microphone function a little, you can add or modify the following lines:Code:ro.product.locale = pt_BR ro.sf.swrotation=0
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).Code:persist.sys.zlink.mic.vol=9.9 persist.audio.mic.senstivity=1 persist.btmic.gain=10 persist.btspk.gain=7
28-05-2023: I added two scripts in post #3 under bullet #4 to let you flash any AllAppUpdate.bin to your unit.
II. AllAppUpdate.bin
III. The 6315_1.zip
(Inside also "III-a. More details about the files inside the 6315_1.zip and how to decompress and unpack/"open" them" and "III-b. Recompress uncompressed images from the 6315_1.zip to squashfs format for small (!) and easy access. (Not for flashing.)")
IV. Some info on partitions
V. The lsec_updatesh folder, lsec6315update binary and 7862lsec.sh script (and what about "universal" scripts)
VI. Compatibilty between uis7862 (ums512) Firmwares
VII. FYT firmware types over the different CPU configurations
VIII. Flashing a Full firmware, an AllAppUpdate.bin or a new system/kernel/core from another reseller
IX. If everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo.
20Backup 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 6315_1.zip (for uis7862) or a 6316_1.zip (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.
14Mods 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 (ro.build.fytmanufacturer= 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 ro.build.fytmanufacturer 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).
Important
BEFORE YOU FLASH ANYTHING TO YOUR UNIT, YOU FIRST NEED TO RUN THE "PRE-FLASH" SCRIPT !!
Steps to perform
- Take a clean FAT32 formatted USB-stick (or a (micro-)SD-card in some USB reader/writer).
- 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).
- 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.
- Delete the "lsec_updatesh" folder including contents on your USB-stick !
- 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.
- Copy the AllAppUpdate.bin that you downloaded somewhere onto the USB-stick.
- Also flashing the 6315_1.zip or 6316_1.zip?
- UIS7862: If you want to flash the kernel as well, copy the 6315_1.zip onto the USB-stick.
- UIS8581a: If you want to flash the kernel as well, copy the 6316_1.zip onto the USB-stick.
- Now copy the contents of the "flash" folder onto the USB-stick.
- 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.
- Copy (not move) the config.txt inside the "myconfiguration" folder into the root of the USB-stick.
- You can now flash your unit using this USB-stick.
Remarks
- 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: flash_any_AllAppUpdate.zip12
Hi.
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 syu.ms.apk with this modded apk. Mod Config App.apk is normally installed as every apk.
