[TOOL] - Topway TS10 firmware workbench

Search This thread

kid75_gl

Member
Oct 30, 2013
6
1
Galati
Hello I got sent the firmware but no instal files it is a big file 1.6gb my screen looks like yours but 10.4 inch I am having trouble starting radio is on but nothing on the screen stop start screen lights up anyway let me know if you want them
Ian
What firmware did you install? I am stuck in the same problem. I put the versions below but I get the same "Powered by Android" screen.

TS10.1.1_20220426.144752_THEME1-360
TS10.1.1_20220923.165357_WINDOW-THEME1-360
TS10.1.2_20210106.173438_THEME1
TS10.1.2_2021043.113940 avec formatage_THEME1
TS10.1.2_20210505.171701_TW1-V2
TS10.1.2_20210826.093418_THEME1
TS10.1.2_20211023.140539_TW1-V2
TS10.1.2_20220117.092632_THEME-V2
TS10.1.2_20220409.141645_WINDOW-THEME1
TS10.1.2_20220507.095321_THEME1
TS10.1.2_20220514.130539_TW1-V2
TS10.1.2_20220519.171713_WINDOW-THEME1
TS10.1.2_20220525.161312_THEME-V2
TS10.1.2_20220804.183432_WINDOW-OLS10_1280x720
TS10.2.2_20220621.174652_THEME1
 

justfishing

New member
Oct 17, 2022
2
0
they sent TS102.2_202208.144345_TW1-V2 it is like 2.7GB i am waiting for a different file now seems to take a while hopefully get a result. Mine sometimes doesn't start once I see the logo no issues beginning to think it is the canBus as i am getting a error on my OBD scanner not connecting to the the radio. might bypass the canBus box and fire 12v straight into the m=head unit to turn it on. As once it goes it goes no issues
 

binharmani

Member
Jan 10, 2008
20
4
giúp em với em cảm ơn bác
tools/twt: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
 

leon wang

New member
Feb 10, 2023
1
0
THX!I have used this tool to unpack and repack properly on my topway T5 device after modified some code.Which files and code under the superuser folder need to be modified for T5 adaptation in order to achieve root?
 

Pacjonek

Senior Member
Mar 24, 2010
257
81
Kraków
No, as Magisk will write in the boot.img and the device (at least TS10) will be converted into a brick, must reflash original firmware to recover !
Have you tried install Magisk by patching the boot.img image and then encrypting it with the "Kaier support tool" and then flashing ready a2191928-8a14-11ec-abc8-13ee0a7bad29 file?
All I know is that many people have tried after via fastboot and failed.
 

binharmani

Member
Jan 10, 2008
20
4
làm ơn giúp tôi
Step 1 of 7 - Unmounting firmware from '_mountpoint'...
umount: _mountpoint: not mounted.
Step 2 of 7 - Merging '1M' and 'raw_firmware' files into a file named 'merged_firmware'...
Step 3 of 7 - Updating checksum of '_tmp/merged_firmware' using 'twt'
tools/twt: error while loading shared libraries: libcrypto.so.3: cannot open shared object file: No such file or directory
root@linux-PC:/home/linux/Desktop/ts10_workbench-master/ts10_workbench-master#
 

bangs6996

Member
Dec 3, 2022
7
1
Hi thank you so much for the share all i had to do was Make my own twt and all is well.... .. My problem is trying to figure out the canbus files. .. My old system actually had a hidden app that would let me see the stream/packets of the canbus in real time . Was pretty cool to find some functions that the cloud files don't support .. like shifting gears ect..

On the ts10 2.2 I can't find the files that contains the packets as i need to change some around. I believe its in the file .
Ts10.1.1-100-8A1-A5C69D-230313.zip which extracts to 519184c0-50c7-11eb-b734-a319fb6824b8 122kb

but I can't figure out what the heck that file holds or if its chasing me down the wrong path., For all i know that is just a picture of some sort..
other files for canbus I believe are
com.tw.ac2_01_230321.apk
com.tw.carchoose_3f18_01_221105.apk
com.tw.carapps_01_871_220523.apk
com.tw.car_00_8A1_0000_200604.apk
files will change depending which car you choose ..

So my Question is does anybody have away for us to directly edit the canbus config file so we can make packets do different stuff..
 

CALEB3

Member
Aug 26, 2009
24
0
I have a question about using this tool. I used firmware from this llink: https://drive.google.com/drive/folders/1-d5AwV_clryDj-eL6DaPP4FkBPJ6uru9
I used version TS10.1.1_20220426.144752_THEME1-360
It is a version that fits to my head unit (Android 10)

Then I used Ubuntu with root rights to run the tool. There were some weird lines (marked red) in terminal window when injecting SU:

Selection from terminal window:


Injecting SU to firmware.

Copying 'su' binary to 'bin'...

cp: cannot create regular file '_mountpoint/system/bin/': No such file or directory

cp: cannot create regular file '_mountpoint/system/bin/sudaemon': No such file or directory




! Folder system/xbin not found: Creating 'xbin' inside 'system'...

mkdir: cannot create directory Äā‚¬Ā_mountpoint/system/xbinÄā‚¬ā„¢: No such file or directory

Copying 'su' binary to 'xbin'...

cp: cannot create regular file '_mountpoint/system/xbin/': No such file or directory

cp: cannot create regular file '_mountpoint/system/xbin/sudaemon': No such file or directory




Copying 'supolicy' binary to 'bin'...

cp: cannot create regular file '_mountpoint/system/bin/': No such file or directory



! Folder system/xbin not found: Creating 'xbin' inside 'system'...

mkdir: cannot create directory Äā‚¬Ā_mountpoint/system/xbinÄā‚¬ā„¢: No such file or directory

Copying 'supolicy' binary to 'xbin'...

cp: cannot create regular file '_mountpoint/system/xbin/': No such file or directory



Copying 'libsupol.so' binary to 'system/lib'...

cp: cannot create regular file '_mountpoint/system/lib/': No such file or directory

Copying 'libsupol.so' binary to 'system/lib64'...

cp: cannot create regular file '_mountpoint/system/lib64/': No such file or directory



Copying 'rooting.rc' file to firmware...

- 'rooting.rc' file copied successfully !



Patching init.rc to load 'su' binary as daemon...

WARNING !!! This is very dangerous, from now all apks will have root privileges automatically

This is a workaround, one day we will be able to patch the boot via magisk (maybe ?).



Modifying internal configuration files...

- file: /system/build.prop

sed: can't read _mountpoint/system/build.prop: No such file or directory

sed: can't read _mountpoint/system/build.prop: No such file or directory


- file: /system/etc/prop.default

sed: can't read _mountpoint/system/etc/prop.default: No such file or directory

sed: can't read _mountpoint/system/etc/prop.default: No such file or directory

sed: can't read _mountpoint/system/etc/prop.default: No such file or directory

sed: can't read _mountpoint/system/etc/prop.default: No such file or directory


Patching init.rc...

patching file _mountpoint/init.rc

Hunk #1 FAILED at 11.

Hunk #2 FAILED at 830.

patch: **** Can't reopen file _mountpoint/init.rc : No such file or directory


Done !



I also tried with newer version of the firmware - same result. I thought maybe the _mountpoint folder is wrong and created new mountpoint folder, adjusted the ini file accordingly, still the same.

Does this mean I didn't get root ?

Am I doing something wrong ?
 

jz30pe

Member
Jul 2, 2017
10
2
Saya mencari firmware versi boot untuk ts10 uis7862 screen resolusi 1280x720 : " 720x1280_M8_3L_ICNL9707_90_99_20210601 "
 

fabiodurgante

Member
May 19, 2016
25
1
What firmware did you install? I am stuck in the same problem. I put the versions below but I get the same "Powered by Android" screen.

TS10.1.1_20220426.144752_THEME1-360
TS10.1.1_20220923.165357_WINDOW-THEME1-360
TS10.1.2_20210106.173438_THEME1
TS10.1.2_2021043.113940 avec formatage_THEME1
TS10.1.2_20210505.171701_TW1-V2
TS10.1.2_20210826.093418_THEME1
TS10.1.2_20211023.140539_TW1-V2
TS10.1.2_20220117.092632_THEME-V2
TS10.1.2_20220409.141645_WINDOW-THEME1
TS10.1.2_20220507.095321_THEME1
TS10.1.2_20220514.130539_TW1-V2
TS10.1.2_20220519.171713_WINDOW-THEME1
TS10.1.2_20220525.161312_THEME-V2
TS10.1.2_20220804.183432_WINDOW-OLS10_1280x720
TS10.2.2_20220621.174652_THEME1
i need donwload ts10.1.2_20211023.140539_tw1-v2 this version work air condition and control whell for my where i download ???
 

Top Liked Posts

  • There are no posts matching your filters.
  • 4
    Hi fellows

    I'm a kind of newbie in the Android world, but I created a set of shell scripts to work with Topway TS10 Firmware:


    ---------------------------------------------------------------------------------------------------------------

    TS10-Firmware-Workbench​

    Scripts intended to mount the Topway TS10 Firmware, make modifications and reassemble the firmware They can retrieve the firmware from specified location and after modification, they can put the firmware into another specified location

    Files:

    1-) config.ini = A file to setup parameters, paths for the original firmware and patched firmware, temp directory to work with firmware files and mount point to edit the firmware

    2-) import_original.sh = Retrieves the files .0 .1 .2 and .3 from the location specified in config.ini

    3-) import_patched.sh = Retrieves the same files that 'import_original.sh' but from the patched location specified in the config.ini (normally a firmware that you've already patched before)

    4-) unpack.sh = Unpack the imported firmware and create the mount moint (as specified in the config.ini file) to work with the firmware

    5-) repack.sh = Unmount the modified firmware from the mount point, delete the mount point, split the firmware in files .0 .1 .2 and .3 and move it to the patched directory as specified in config.ini

    6-) inject_tweaks.sh = Modify locale, dataroaming and remove (if necessary) the values in ro.fota.device to avoid message "UI unauthorized, please contact the supplier"

    7-) inject_mods.sh = This will copy all the contents of the '_mods' folder inside firmware. I.E. I put a 'gps_debug.cfg' inside 'system/etc/' and it will be injected into firmware overwritting the existent

    :cool: inject_su.sh = This will inject su binary into firmware as a daemon, this is dangerous as the firmware is permanently rooted and the apps don't ask for permissions (they already have the root access) USE AT YOUR OWN RISK

    9-) clean_local.sh = This script will unmount the firmware and delete it, it will also delete temporary files. as its name says, it cleans the dir !

    External (included) tools:

    tools/twt (Topwaytool) forked from https://github.com/mkotyk/topwaytool

    _mods folder containing a sample file 'gps_debug.cfg'

    N'joy it !


    ---------------------------------------------------------------------------------------------------------------
    1
    Run as root

    only a53***** files needed !
    1
    Yes, that's right, I forgot about mount command, so you have to run it as root anyway
    1
    Absolute beginner to this so some basic questions!

    Where can I get the firmware for my unit? Ask the seller? Or can I extract from the HU (head unit)?

    I have 360 cameras and PA(park assist) is this all stored on the firmware? There will be no issues after update?

    Best way to backup existing apks? Do I need to do this? If not will I lose license keys like the post above?

    I heard of issues with a bootloop as the units have different size/resolution screens and you need to configure this. With my own firmware, do I need to do this?

    Do I need to do all the steps in your ordinal post or do I only need to get the firmware and do the 8th option if I mainly wanted root?

    Safest method for updating? Do I need to backup ROM?

    Any chance for a video or step by step guide? Lol
    1
    Chisene firmware could try to send personal data to their servers, you must snife the wifi/4G connections for potential data flow to china serversdd and what's in the packets !
    Ahhh, I see. So its a personal data privacy issue. Ok. If that is all, I can work with that. I don't plan on doing anything on my head unit involving sensitive information. The only thing that could potentially be at risk, for me anyway, is a gmail account, but I could always use an alternate account that is JUST for the head unit. The chinese can see where I go, and even listen to my music for all I care. I don't use Android Auto or CarPlay either.


    So, given the stated privacy risk, as long as I keep everything sensitive I do to my phone and PC only, and use a separate google account for just the head unit I could potentially mitigate the risk? Its really just used as a multimedia device with GPS, if I limit it to that activity I don't see a high level of risk. If im wrong, please clue me in. My phone does mostly everthing else better anyway and is on me when driving.