General Modding your Joying/FYT SC9853i unit without root

Search This thread
By:
Advanced…
surfer63

surfer63

Senior Member
May 4, 2010
6,576
3,948
Zwolle
github.com
Raiden11X said:
My AllAppUpdate has a password so I can't extract it with 7zip. Using ApkPack to extract gives me an error with weird symbols. How do I get around this?
Click to expand...
Click to collapse
Wrong forum thread if you have a uis7862, or wrong downloaded zip if you really have a sc9853i.
And read before asking! All the answers are there.
General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware. post #1 and #2

Edit: Ah, I see you already did that, but you didn't alter your post.
 
Last edited:
  • Like
Reactions: Raiden11X and marchnz
Raiden11X

Raiden11X

Member
Oct 3, 2013
23
11
Sprint Samsung Galaxy Note II
Sprint HTC EVO 4G LTE
surfer63 said:
Wrong forum thread if you have a uis7862, or wrong downloaded zip if you really have a sc9853i.
And read before asking! All the answers are there.
General FYT based Spreadtrum uis7862 (unisoc ums512) - Q&A, Mods, tips, firmware. post #1 and #2

Edit: Ah, I see you already did that, but you didn't alter your post.
Click to expand...
Click to collapse
Yes, that's my fault. I should update it.

I actually wrote a guide on rooting the ATOTO A6 PF which has a lot of similarities with these units and I was looking at how to open up this file. I had googled a bit around that file and didn't really come up with anything. How it didn't take me to your Spreadtrum thread about it, I have no idea, but I loved some of your other posts and I actually went through one of your other posts and found my way to that one. Man, I love the stuff you post. Extremely thorough and easy to follow. Thank you for writing all of that up! I've been using that post and a handful of others whenever I get stuck or even just to learn a bit more about how it all works together. I haven't modded much since the KitKat days so it's definitely scratching an itch I've had in my brain for several years now.
 
Hammerhand.17

Hammerhand.17

Senior Member
May 29, 2010
670
134
Winterfell
surfer63 said:
I am very sorry.
Yes, I checked it last Sunday but it was no longer on my unit. I searched (again) my github repositories, my Google drive and my laptops and server, but can't find it anymore.
Click to expand...
Click to collapse

Thanks again for bothering.

I have been searching it and tried several 8.1, 9, & 10 versions, all of them fails. I don't know if it's an issue with permissions or something with my unit.

Don't you have any idea of what the issue could be? I will keep searching but I don't know how to go further.
 
surfer63

surfer63

Senior Member
May 4, 2010
6,576
3,948
Zwolle
github.com
Hammerhand.17 said:
Thanks again for bothering.

I have been searching it and tried several 8.1, 9, & 10 versions, all of them fails. I don't know if it's an issue with permissions or something with my unit.

Don't you have any idea of what the issue could be? I will keep searching but I don't know how to go further.
Click to expand...
Click to collapse
I don't know. I used one on my unit which I "simply" installed and that worked.
I think I copied one out of a 8.1 firmware for a phone having a sc9853i chip.
 
  • Like
Reactions: Hammerhand.17
Hammerhand.17

Hammerhand.17

Senior Member
May 29, 2010
670
134
Winterfell
surfer63 said:
Thanks for finding that one. :) I can't remember I posted that one.
Yes, probably that is the issue.
Click to expand...
Click to collapse
No, it isn't. I've flashed my original firmware (20191123) and same issue. Maybe I could try a full reset? I didn't want to do it because It's a pain to restore everything to internal memory, but maybe it could be my last bullet.

How could I do a complete reset, making sure it gets the same way as out of factory? I know I made some mods some time ago but can't remember what I did.
 
surfer63

surfer63

Senior Member
May 4, 2010
6,576
3,948
Zwolle
github.com
Hammerhand.17 said:
No, it isn't. I've flashed my original firmware (20191123) and same issue. Maybe I could try a full reset? I didn't want to do it because It's a pain to restore everything to internal memory, but maybe it could be my last bullet.

How could I do a complete reset, making sure it gets the same way as out of factory? I know I made some mods some time ago but can't remember what I did.
Click to expand...
Click to collapse
A complete reset is done by flashing a complete firmware.

However, please try as last resort the attached 8.1.0 version from LineageOS. I can install it on my sc9853i
 

Attachments

  • com.android.documentsui_8.1.0-27_minAPI27(nodpi)_apkmirror.com.apk
    2.3 MB · Views: 37
Hammerhand.17

Hammerhand.17

Senior Member
May 29, 2010
670
134
Winterfell
surfer63 said:
A complete reset is done by flashing a complete firmware.

However, please try as last resort the attached 8.1.0 version from LineageOS. I can install it on my sc9853i
Click to expand...
Click to collapse
Ok, I will do it tomorrow morning. If it works with your unit and not with mine, there is something with mine.

I've flashed firmware but my apps and account remains. I know an option on config.txt makes it reset (not at hand now, will search it later). Is this enough to make it as out of the box?
 
surfer63

surfer63

Senior Member
May 4, 2010
6,576
3,948
Zwolle
github.com
Hammerhand.17 said:
Ok, I will do it tomorrow morning. If it works with your unit and not with mine, there is something with mine.

I've flashed firmware but my apps and account remains. I know an option on config.txt makes it reset (not at hand now, will search it later). Is this enough to make it as out of the box?
Click to expand...
Click to collapse
You need the twipe_all in your updatecfg.txt to wipe everything clean.
 
M

mastrv

Senior Member
Jul 1, 2010
316
101
The error message about unhandled intent might be addressed by installing another app that handles that intent.

Can you provide a little more detail about your specific scenario again where the error message was showing up?

I believe I had an issue on mine related to that and what I ended up doing was installing Zip Archiver I believe. I think it was to specify/select a file to save a screenshot to. There are probably many other apps that would do this. They would have to be more recent apps that require at least Android 8, I believe.

I'm not sure if that will work, but it's much easier to try than re-flashing to factory and setting everything up.
 
Hammerhand.17

Hammerhand.17

Senior Member
May 29, 2010
670
134
Winterfell
mastrv said:
The error message about unhandled intent might be addressed by installing another app that handles that intent.

Can you provide a little more detail about your specific scenario again where the error message was showing up?

I believe I had an issue on mine related to that and what I ended up doing was installing Zip Archiver I believe. I think it was to specify/select a file to save a screenshot to. There are probably many other apps that would do this. They would have to be more recent apps that require at least Android 8, I believe.

I'm not sure if that will work, but it's much easier to try than re-flashing to factory and setting everything up.
Click to expand...
Click to collapse


It happens when I try to export poweramp settings. The app tries to use documentsui and it is not installed; if I install it, it always fc (no matter what version I use). If I try to import settings, it uses any of my file explorer (I have installed several of them to see if any of them works).

It's not an issue of poweramp: any app which tries to use documentsui finish in fc too: for instance, in titaniumbackup, if I try to change documents selector from file explorer (default) to documents provider, the result is the same.

I attach a logcat I took with poweramp intent. I have no idea of how to interpret it, maybe one of you know what it says.
 

Attachments

  • 2022-09-20-09-07-16.txt
    309.7 KB · Views: 18
C

Culdea

New member
Feb 24, 2011
4
0
Hello guys
I have a isudar media and I update it wit the firmware from teyes, I know it was not the smartest idea 😅. The problem that I have it now is that I can't update to the original frimware version because this error: Please use lsecxxx update file after 2022-07-02 !
The lsecxxx file is 2021 from the original frimware. How can I jump over this check to be able to install the original version ? Thank you for any suggestions.
20220922_180253.jpg
 
M

mastrv

Senior Member
Jul 1, 2010
316
101
Culdea said:
Hello guys
I have a isudar media and I update it wit the firmware from teyes, I know it was not the smartest idea 😅. The problem that I have it now is that I can't update to the original frimware version because this error: Please use lsecxxx update file after 2022-07-02 !
The lsecxxx file is 2021 from the original frimware. How can I jump over this check to be able to install the original version ? Thank you for any suggestions. View attachment 5717819
Click to expand...
Click to collapse
wrong thread.
 
You must log in or register to reply here.

Similar threads

surfer63
General General FYT based Spreadtrum uis7862(s) (unisoc ums512) & uis8581a (sc9863) - Q&A, Mods, tips, firmware
Replies
4K
Views
413K
G
gonzo99
realzoulou
General Joying Android 8.1 Intel Airmont eight-core 1.8GHz SC9853i (4GB RAM, 32GB flash)
Replies
2K
Views
326K
B
bambapin
P
General HowTo: Root Joying SC9853i Head Unit
Replies
634
Views
128K
surfer63
surfer63
surfer63
Software Development Joying Extra Tools apk - an apk to help you install mods, tweak your unit, etc.
Replies
2K
Views
214K
J
japioothuis
gtxaspec
  • Locked
Software Development [CLOSED] [ROM] [CUSTOM] [INTEL JOYING] GTX joying ROM V9a3 2018-04-22
Replies
2K
Views
322K
T
TNSMANI

Top Liked Posts

24 Hours All time
  • There are no posts matching your filters.
  • 11
    surfer63
    surfer63
    See title: Only for SC9853i Joying/FYT 8.1 units.
    Due to some changes in the flashing process since the previous PX5 and Sofia 3GR models it is now partly possible to mod your unit without root.

    Some info to start with:
    (partly from 4pda, partly from a "hint" from @julien_blanche, mostly from own knowledge)

    Contents of a firmware zip:
    Code: 
    6521_1.zip           # The zip that contains the boot.img; the system/vendor/oem partitions and a few other things.
Allapp.pkg           # Special file that contains all FYT apps (actually a special XAR archive.)
config.txt           # file comparible to the build.prop which can contain additional properties
lsec6521update       # The binary that really does the update
oem                  # Folder containing some additional apps
Stm32ud.bin          # The MCU binary. It is not always in every firmware
updatecfg.txt        # Contains instructions for the flashing process
crruptoff            # Special file for "WiFi only". Not in the normal firmwares. Be careful!


    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_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, for example:
    Code: 
    ro.product.locale = pt_BR

    The file crruptoff:
    If you have a unit with a 4G module, but you don't have 4G (or don't want to use it), you can use this file. Put one line in this crruptoff being "fixwifi" and save it to the sdcard/usb-stick you use for flashing.
    You can use it to get rid of the "No SIM" notification in your notification bar.     Does not work anymore on the later firmwares. Chances are minimal but maybe it might work again "some day".

    The Allapp.pkg
    The Allapp.pkg file is a special XAR archive with a directory structure. You can use ApkPack.exe to create or extract it.
    Folder path: This is where your files are being extracted to, or packed from
    File path: This is the file that is being created (packed), or where the files are extracted from.
    All apks (*.apk) and all libraries (*.so) will be installed as system apks and libraries, which means you can't uninstall them, but on the SC9853i units they are installed under /oem and not under /system.
    Inside this Allapp.pkg you will also find 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.
    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:
    Code: 
    com.zoulou.dab = -10
net.dinglisch.android.taskerm = -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 to your own allapp.pkg

    The lsec_updatesh folder and lsec.sh script
    Practical applications:
    • Making patches, an alternative to creating the Allapp.pkg package.
    • Work on all folders in the unit (which Allapp.pkg cannot do).
    • Delete unnecessary files or applications (who uses the calculator app?), or overwite files like the fyt.prop or others.
    • Modify/overwrite config files that are otherwise not modifiable (like bluetooth config?)
    • Setting properties that normally require root/admin rights.
    • 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 Custom ROM by simply doing all kind of modifications after the "normal" firmware flash.

    See for more info about the "The lsec_updatesh folder and lsec.sh script" in post #228.

    Creating an Allapp.pkg and flash it to your device (post #2)
    Some pre-build flashable images (post #3)
    And if everything goes wrong and your unit ends up in a boot loop or doesn't get past the boot logo. (post #4)
    View
    8
    surfer63
    surfer63
    Creating an Allapp.pkg and flash it to your device

    Use the (English) version of ApkPack.exe (english version attached) to unpack/repack an Allapp.pkg. (It also works with wine on Linux/MacOS)

    (See this youtube link for a really quick & dirty (and unsharp, sorry) video about what scrolls on your screen when flashing such a mini Allapp.pkg)

    (1) Quick example:
    • Create a folder Allapp
    • Copy some wanted apks or mods into the folder.
    • Use the ApkPack.exe to create the Allapp.pkg
    • Simply copy the "Allapp.pkg" and "lsec6521update" onto a clean FAT32 formatted SD-card or USB-stick.
    • Put the USB-stick into your unit and it will recognise the update and flash it to your unit.
    • Other options:
      • Copy the "Allapp.pkg", (optional) "updatecfg.txt", (optional) "config.txt" and "lsec6521update" onto a clean FAT32 formatted SD-card or USB-stick.
      • In my case having a 4G unit without using 4G and wanting to use Google Assistant for calls: Copy the Allapp.pkg, config.txt (see above), crruptoff (see above) and lsec6521update onto a clean FAT32 formatted USB-stick.
      • Note that when NOT using an updatecfg.txt, nothing will be wiped on your unit. Only added/replaced.

    (2) Another example:
    • Create folder Allapp on your pc/laptop
      • add (2019-08-14) main server mod with extended navi_app.txt and "BT to background" hacks. (see my github repo. Be careful to choose the one for your specific firmware date)
      • add BW-RDS radio mod (see my github repo. Only choose version for Android 8.1 if you want full functionality)
      • add oandbackup (dk.jens.backup_305.apk) (Free and open source backup restore apk)
      • add latest MagiskManager-v7.3.2.apk
    • Use apkpack.exe (attached) to create a new Allapp.pkg by selecting the folder to be packaged, the name of the file being Allapp.pkg, and select button "Packed" (sloppy translation from Chinese)
    • Copy created "Allapp.pkg" and "lsec6521update" onto a clean FAT32 formatted USB-stick.
    • Insert in your unit and the flashing process will start (Note: It will mention "Setting to factory defaults" before flash reboot, but it is really not doing that)
    • After the (very quick) flash and normal reboot, you will have 2 new apps and 2 modded apps.

    (3) Example for a FYT compatible SC9853i, like a Sinosmart or Zhan or "unnamed":
    You can also create your own Allapp.pkg, also with a modded Joying apk as the apks are actually identical, but there is one big naming issue to take into account!
    Even though the apks are identical having the same package name, they have different apk names. A normal install will check for the package name and replace the apk with that same package name, whatever its apk name (think of versions or build time stamps behind the the "normal" name). The flashing method simply looks at the apk name and will create an /oem/app/<apk_name>/<apk_name>.apk. In this case versions numbers of build timestamps will create again and again a new folder with the exact same apk and none will work.
    As an example for the radio app:
    • Joying: 190043001_com.syu.radio.apk
    • Sinosmart: 190042001_com.syu.radio.apk
    • "Some" unbranded: 190101001_com.syu.radio.apk
    Again: The apks are exactly the same but have a different name. If you simply flash one next to the other, both will not work anymore as both have the same internal package name being "com.syu.radio". So you have no radio at all.
    So, how to create an Allapp.pkg with a modded Joying apk for your FYT compatible SC9853i unit?
    • Check the name of your unit's radio app (or BT, Video, Music app). (If you don't know how you can use my HWGet_info.apk and open the resulting HWget_info.zip and look inside the "oem_listing.txt")
    • Find the name of the modded Joying app.
    • Rename the modded Joying app to the name of your app. So for example for Joying-> Sinosmart radio app: rename 190043001_com.syu.radio.apk to 190042001_com.syu.radio.apk (Joying to Sinosmart)
    • Create a folder Allapp
    • Copy the modded and now renamed Joying radio apk into the folder (repeat if relevant for other mods).
    • Use the ApkPack.exe to create the Allapp.pkg
    • Simply copy the "Allapp.pkg" and "lsec6521update" onto a clean FAT32 formatted SD-card or USB-stick.
    • Put the USB-stick into your unit and it will recognise the update and flash it to your unit.
    • Also create an Allap.pkg for your original app so you can always flash back the original app if you want (or need) to.
    View
    7
    surfer63
    surfer63
    Some pre-build flashable images

    Only for real Joying SC9853i units. Other FYT compatibles are not supported.
    All SC9853i FYT models are actually the same, but boot images are mostly different and apks have different names. In the latter case you would have 2 identical apks with the same package name, but with a different apk name residing in different folders. Neither of them will work anymore as Android doesn't know which one is the correct one.

    The zips that can be found in this post can be directly unzipped to a clean, empty Fat32 formatted USB-stick or SD-card. You do not need to be rooted and you don't need my JET apk.
    When this USB-stick or SD-card is inserted into your unit, the unit will recognize it as a flashable firmware and start flashing the files to your unit.

    Notes:
    • These flashable firmware files will leave all your installed apps and settings as they are. Only the files in these Allapp.pkg files will be overwritten.
    • The zips containing boot images will only overwrite the boot image. All apps and settings remain as they are.
    • The "combi" zips are just combinations of possible mods and/or boot images. They behave the same as the previous two.
    • The zips that can be downloaded from this post are all on one of my github repositories. You can find it here: SC98531BinRepo.
    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Boot images
    2019-11-28 | 20191128-rooted-boot-image (thanks to @rigattoni) | 20191128-normal-boot-image
    2019-09-17 | 20190917-rooted-boot-image | 20190917-normal-boot-image
    2019-08-14 | 20190814-rooted-boot-image (thanks to @julien_blanche)

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Main server apk mods (the 190000000_com.syu.ms.apk)
    The ORG version is the apk as delivered by Joying in their firmwares.
    The ORG_extended is the Joying one including an extended navi_app.txt, extended player_app.txt, extended navi_audio_from_playstatus.txt.
    The NoKill is the extended version where the normal functionality to kill all apps when going into "deep sleep" (turn of ignition), has been disabled.

    2020-04-07 | 2020-04-07-com_syu_ms-ORG | 2020-04-07-com_syu_ms-ORG_extended | 2020-04-07-com_syu_ms-nokill | ( Zips, modified smali files, modified assets text files, some info)
    2019-11-28 | 2019-11-28-com_syu_ms-ORG | 2019-11-28-com_syu_ms-ORG_extended | 2019-11-28-com_syu_ms-NoKill | ( Zips, modified smali files, modified assets text files, some info)
    2019-09-17 | 2019-09-17-com_syu_ms-ORG | 2019-09-17-com_syu_ms-ORG_extended | 2019-09-17-com_syu_ms-NoKill | ( Zips, modified smali files, modified assets text files, some info)
    2019-08-14 | 2019-08-14-com_syu_ms-ORG | 2019-08-14-com_syu_ms-ORG_extended | 2019-08-14-com_syu_ms-NoKill

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Other mods
    There are currently two mods for the radio: One very nice one from user @Soiski71 and one which I made.
    The ORG version in this case is the one delivered with the Joying firmwares.

    Radio | SC98531-Radio-ORG | SC98531-Radio-Mod (preview) | SC98531-Radio-Mod-Soiski71 (preview)

    ----------------------------------------------------------------------------------------------------------------------------------------------------------------
    Combinations
    These are combinations of above files which I found useful. Undoing them can be done by using one of the above ORG zips.
    2019-09-17 | 2019-09-17-radio_mainserver | 2019-09-17-rootedboot_radio_mainserver
    View
    4
    surfer63
    surfer63
    If everything goes wrong and your unit gets in a boot loop or stops on boot logo

    - Download a fresh firmware from the Joying blog.
    - Unzip it to an SD-card/USB-stick (as normal)
    - Put the USB-stick/SD-card in your unit and "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.
    View
    4
    M
    mastrv
    This post recaps some of the work done to enable voice calling using Google Assistant (GA) through a Bluetooth attached phone on an sc9853i FYT compatible Android Head Unit (HU). I have a TEyes SPro 4/64 with CC2 firmware installed. This should work on other FYT compatible, including Joying units, but no guarantees. This includes required files and instructions/steps for those that may find this at some point in the future.

    Attached is the software to enable GA voice calling:
    • Telecom script to update the Telecom server, if required. FYI, the Telecom server on my head unit was missing code to handle the voice call.
    • The updated simple phone app that is called by the GA when a voice call is made. The Telecom server calls this app when the voice call is made. This is a release version and not a debug version of the app.
    • GVC CallHandler I used. This app is called by the simple phone app. This app passes the details to the Bluetooth app to make the call.
    Instructions:
    • Ensure you have up to date/latest Google Assistant, Google app and the Google Contacts app and they have appropriate or all Permissions given...from Play store if you don't already have them.
    • Install the attached GVC CallHandler and CustomGVCBluetoothPhoneHandler applications normally and give them permission to make calls. Root is not required. The GVC app is available from the Google Play Store. That may work, but the attached is a version that I tested with.
    • Try voice calling using Google Assistant...say "Call xxxxx" where xxxxx is any of your contacts from Google Contacts. i don't believe that Google Assistant uses contacts from the Bluetooth phone app on the HU. If prompted, set the GVC CallHandler as the default app to make calls. One of two things will happen:
      1. It works and no messages or errors occur....the call will be made and you are finished! Note that there seems to be an issue where the first and/or second attempt don't work. Try the voice call a second or third time.
      2. It doesn't work and a message similar to "App isn't installed." then you need to replace the Android Telecom server app that is currently installed on your head unit.
    • To replace the Telecom server, unzip the attached telecom_script.zip to a usb drive and insert into the HU. This should invoke the standard update process. The script includes the original TEyes Telecom server from my unit and the new one from another Joying unit, as described in a previous post. When it runs, it creates some information from your unit as well as copying the existing Telecom server on your head unit to the USB drive. If you need it or want to re-install it at some point, save it somewhere. You can also get it back from your own firmware.
    • If it didn't work previously and you replaced your Telecom server, try the voice call again.
    • That's it...it should have worked.

    I'll be trying to figure out more info about the voice call not working on the initial attempt(s). I suspect I won't be able to determine the issue as I believe it occurs within the GVC app.

    If you update to a different / newer firmware in the future, you will probably have to repeat this process.
    View

New posts