yashsingh1/xdaforums huggingface dataset:
[FYT Android Head Units] Streets97f:
This is great stuff. I wish I had the programing knowledge to implement this for my Teyes CC3 360 version. The Teyes CC3 360 firmware version is still Oct 2022...will this work with the original posted FFW 2.0 without the different signature method? Link to the Teyes CC3 360 firmware: https://teyes.com.au/pages/cc3-360-october-2022-26-10-2022

I'm really trying to replace the factory com.syu.ms.apk with @seb21 modded syu.ms.apk. https://xdaforums.com/t/modded-syu-ms-apk.4514689/ I can follow steps if someone is willing to walk me through using the FFW to upack and pack the firmware. Or if someone is willing to do the work of upacking, replacing the com.syu.ms.apk and repacking, I can definitely donate some $. I know there are a few people on this forum that are looking for this same firmware w/ the mod and this would be very helpful for them as well. Thanks
[FYT Android Head Units] mariodantas:
Send me the stuff that you need to sign (6315_1.zip) I'll do it for you !
[FYT Android Head Units] Streets97f:
You’re awesome! I’ll send you the firmware zip and @seb21 ’s modded syu.ms.apk this evening after work.

Definitely send me a link to your donate page so I can contribute anyway I can.
[FYT Android Head Units] mariodantas:
Oh don't worry about that fellow, justr send me your stuff and I'll sign it for you and send you back !

In a few days I'll provide you the stack capable of signing this kernels, even for your T'eyes device !
[FYT Android Head Units] Streets97f:
Nice, I appreciate it!

1. 6315_1.zip - the Oct 2022 Teyes CC3 360 firmware.

here is the link (the file is too big to attach). https://drive.google.com/drive/folders/12QMf-kSmgH4cWqe5TXRm_T4jxybzj3AT

2. 190000000_com.syu.ms.apk - the syu.ms.apk from @seb21 that needs to replace the factory com.syu.ms.apk in the repacked signed firmware. (This should hopefully extend control of steering wheel controls via the CAN with his Mod Config App.)
[FYT Android Head Units] Clandaries:
Is it possible to install a pre rooted firmware for the CC3 if someone has already patched the firmware?

i will receive the CC3 in maybe two weeks and would love to have root. But i have no Linux or Linux skills so far.

Regards
[FYT Android Head Units] surfer63:
Yes, rooting is part of the kernel and the boot image inside that kernel.

so you could take a rooted 6315_1.zip
[FYT Android Head Units] Clandaries:
Thats cool. Would someone PM me a patched firmware for the CC3?

Regards
[FYT Android Head Units] wooko0:
I use your tool on ubuntu20.4, but it prompts this error. What should I do?

Processing 'product' image ...

BROTLI -- Handling product.new.dat.br...

Converting product.new.dat file into product.img file

Creating _mountpoint/product folder...

Adding '128 Mb' extra size to _tmp/_firmware/product.img ...

128+0 records in

128+0 records out

134217728 bytes (134 MB, 128 MiB) copied, 0.0719805 s, 1.9 GB/s

e2fsck 1.46.5 (30-Dec-2021)

ext2fs_open2: Bad magic number in super-block

e2fsck: Superblock invalid, trying backup blocks...

e2fsck: Bad magic number in super-block while trying to open _tmp/_firmware/product.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4

filesystem. If the device is valid and it really contains an ext2/ext3/ext4

filesystem (and not swap or ufs or something else), then the superblock

is corrupt, and you might try running e2fsck with an alternate superblock:

e2fsck -b 8193 <device>

or

e2fsck -b 32768 <device>

resize2fs 1.46.5 (30-Dec-2021)

resize2fs: Bad magic number in super-block while trying to open _tmp/_firmware/product.img

Couldn't find valid filesystem superblock.

Mounting image...

Done with image product !
[FYT Android Head Units] surfer63:
This means that the created EXT4 partition image is corrupt.

Did you try it a second time? or third time? If not, do so.

Secondly: In the unpack.sh script you will find a line:

dd if=/dev/zero bs=1M count=128 >> $unzippedPath$i.img #> /dev/null 2>&1

Change that to:

dd status=progress if=/dev/zero bs=1M count=128 >> $unzippedPath$i.img

See what the progress mentions and see if you get error messages.

The "#> /dev/null 2>&1" hides all output from the commands, which in this case is unwanted.

Otherwise: check if your hard disk contains bad sectors.
[FYT Android Head Units] wooko0:
I tried many times and reinstalled ubuntu several times.
[FYT Android Head Units] wooko0:
Processing 'system' image...

BROTLI -- Handling system.new.dat.br..

Converting system.new.dat file into system.ing file

Creating _mountpoint/system folder.

Adding "128 Mb' extra size to

dd: unrecognized operand 'stats

_tmp/_firmware/system.ing

Try 'dd --help' for more information.

e2fsck 1.46.5 (30-Dec-2021)

e2fsck: Attempt to read block from filesystem resulted in short read while trying to open _tmp/_firmware/system. ing

Could this be a zero-length partition?

resize2fs 1.46.5 (30-Dec-2021)

resize2fs: Attempt to read block from filesysten resulted in short read while trying to open _tmp/_firmware/system. img

Couldn't find valid filesystem superblock.
[FYT Android Head Units] wooko0:
My Ubuntu is installed with Python 3. After editing unpack.sh, it can be used normally，thx
[FYT Android Head Units] mesofranico:
What did you change to make it work?
[FYT Android Head Units] wooko0:
thx @surfer63

edit unpack.sh ：

python3 ./tools/sdat2img.py $unzippedPath$i.transfer.list $unzippedPath$i.new.dat $unzippedPath$i.img > /dev/null 2>&1

edit repack.sh ：

python3 ./tools/img2sdat.py $unzippedPath$i.new -v 4 -o $unzippedPath -p $i #> /dev/null 2>&1
[FYT Android Head Units] surfer63:
@mariodantas: The sdat2img.py and img2sdat.py are quite old and not testing for python2 or python3.

The simplest way to adapt that is in your unpack.sh script and not in the python files, by using something like:

echo "$(tput setaf 6)Converting $i.new.dat file into $i.img file$(tput setaf 7)"
if [ ! -e /usr/bin/python3 ]
then
# No python3 binary found. We have python2
./tools/sdat2img.py $unzippedPath$i.transfer.list $unzippedPath$i.new.dat $unzippedPath$i.img > /dev/null 2>&1
else
# Yes. python3 exists. Use it
python3 ./tools/sdat2img.py $unzippedPath$i.transfer.list $unzippedPath$i.new.dat $unzippedPath$i.img > /dev/null 2>&1
fi
rm $unzippedPath$i.new.dat

and then do the same for the img2sdat line.

You can of course do the same in python using the sys.sys_info tuple, but that is less simple. And you need to adapt the shebang line.
[FYT Android Head Units] mariodantas:
Thanks @surfer63 will implement !
[FYT Android Head Units] j0hn83:
What app do you use to check the signed zip?

I noticed the Atoto 6315_1.zip wouldn't install on my unit. It was complaining about the signature.

I signed it with the FYT Firmware Workbench script and it now installs fine.

No idea what to use to check zip signatures though.

Also noticed the FYT workbench takes over an hour in total on my Raspberry Pi 3B but only about 10 minutes on a VM on my laptop so I know where I'll be doing this in future.
[FYT Android Head Units] surfer63:
The SignApkv2.jar can only sign, not verify. A second big drawback is that it is only for Android 8, while android 8 is out of service since 2014 although you can still get it for every platform and you still can get paid support.

If you have some java or openjdk installed, you have "jarsigner" to sign and verify jars, but it can also be used for zips.

I more or less stopped my modding activities, but this winter I tried zipsign. I compiled it and tried it, but never really tried it on a 6315_1.zip to flash it.

I might unzip marios 6315_1.zip, rezip and sign it and then flash it, but I was just too lazy.

My Acer Chromebook with Linux Sansbox is also 4x as fast as my 4GB RPi 4B.
[FYT Android Head Units] iamrance.asa:
How did you sign the newer builds? I tried using the same signing method from the #1 post workbench with the provided sign keys but it failed during install. The tool kept giving me errors with bc provider on the repack so I tried doing things manually, just don't know how to properly sign for a build from early this year
[FYT Android Head Units] Th_D:
Hi,

Have you successfully managed installing the seb21 modded apk on your cc3 360 ?
[FYT Android Head Units] ahmed68:
hi everyone where i can find faq for this program , i can use it with 6316_1.zip or not .
[FYT Android Head Units] surfer63:
Yes, you can.

See also thread "KERNEL] FYT 7862 optimized rooted kernel MD-EDITION and non-rooted Kernel OK-Edition (optionally with FMC or Sebs modded com.syu.ms)". It contains an updated version.
[FYT Android Head Units] ahmed68:
thank you so much dear friend
[FYT Android Head Units] ahmed68:
when i edit the pc firmware for fyt unit to replace the emmc and flash it by RESEARCHDOWNLOAD , I haven't seen the OEM block in lot of stock firmware , because of this, I realized that it was not a native block from Google , decided to move all files from oem to product . as a result, the unit began to work differently , when completely removed the oem block from the GPT , I stitched a new GPT after the green inscription wait for mcu rst command .

Головные устройства Teyes X1 - 4PDA

Головные устройства Teyes X1, [Головное устройство][Автомагнитола][Android]

4pda.to
[FYT Android Head Units] surfer63:
You are on T'eyes. That works differently.

All FYTs have a separate kernel and AllAppUpdate.bin.

T'eyes has this integrated and uses the elable partition for this.

I also made a T'eyes MD-Edition full firmware based on the May2023 CC3 firmware, but so far I did not hear of users using it successfully.
[FYT Android Head Units] ahmed68:
yes i see in the last teyes firmware for CC32K RU-2023.5.11 all application in the elable partition .
[FYT Android Head Units] ahmed68:
this the stock GPT for pc firmwre ɪts hævnt elable and oem=AllAppUpdate.bin partition size in mb

<Partitions>

<!-- size unit is MBytes -->

<Partition id="prodnv" size="10"/>

<Partition id="miscdata" size="1"/>

<Partition id="recovery" size="40"/>

<Partition id="misc" size="1"/>

<Partition id="trustos" size="6"/>

<Partition id="trustos_bak" size="6"/>

<Partition id="sml" size="1"/>

<Partition id="sml_bak" size="1"/>

<Partition id="uboot" size="1"/>

<Partition id="uboot_bak" size="1"/>

<Partition id="uboot_log" size="4"/>

<Partition id="logo" size="6"/>

<Partition id="fbootlogo" size="6"/>

<Partition id="l_fixnv1" size="2"/>

<Partition id="l_fixnv2" size="2"/>

<Partition id="l_runtimenv1" size="2"/>

<Partition id="l_runtimenv2" size="2"/>

<Partition id="gpsgl" size="1"/>

<Partition id="gpsbd" size="1"/>

<Partition id="wcnmodem" size="10"/>

<Partition id="persist" size="2"/>

<Partition id="l_modem" size="25"/>

<Partition id="l_deltanv" size="1"/>

<Partition id="l_gdsp" size="10"/>

<Partition id="l_ldsp" size="20"/>

<Partition id="pm_sys" size="1"/>

<Partition id="teecfg" size="1"/>

<Partition id="teecfg_bak" size="1"/>

<Partition id="boot" size="35"/>

<Partition id="dtbo" size="8"/>

<Partition id="super" size="4100"/>

<Partition id="cache" size="150"/>

<Partition id="socko" size="75"/>

<Partition id="odmko" size="25"/>

<Partition id="vbmeta" size="1"/>

<Partition id="vbmeta_bak" size="1"/>

<Partition id="metadata" size="16"/>

<Partition id="sysdumpdb" size="10"/>

<Partition id="vbmeta_system" size="1"/>

<Partition id="vbmeta_vendor" size="1"/>

<Partition id="userdata" size="0xFFFFFFFF"/>

</Partitions>
[FYT Android Head Units] surfer63:
You are making it too difficult. You need to look inside the 6315_1.zip. In the "dynamic_partitions_op_list" are the relevant partitions for you as modder
[FYT Android Head Units] ahmed68:
i check the error log in the teyes firmware there are a lot of errors , I want to create a mod that look like google firmware , now navigation starts quickly.
[FYT Android Head Units] gordgelin:
it is hardly possible since android framework here is heavily modified to work as head unit, not a tablet/phone, and also many other things too. making it more google-like == breaking functionality for sure.
[FYT Android Head Units] ahmed68:
i make it and its work beter than stock firmware but i flash it by this command

#!/system/bin/sh

#

dd if=/storage/sdcard1/super.img of=/dev/block/by-name/super
[FYT Android Head Units] gordgelin:
since all hardware related functions rely on chinese framework and software, starting from fm/bt/dsp/mcu/canbus, you can't make it more google, these things will just stop working properly or at all

i do not know what you mean exactly by more google like, but to some degree system can be refined of course but not much
[FYT Android Head Units] ahmed68:
in the last modification teyes CC32K the engineer of teyes company understanding why many programs not work correctly , because the program in oem block cant have any primation due to a lot of application worked slowly or did not work at all , it was decided to move all applications to elable block , i understand the elable its not original block for google firmware i move it to product /
[FYT Android Head Units] gordgelin:
ok, i see you are not just familiar enough with this platform yet. i do not know what you mean saying "google firmware" but chinese oem software are definitely, at least in part, path-dependent to elable/oem partitions, and there is nothing from google in these partitions, except heavily modified system ui
[FYT Android Head Units] Clandaries:
Maybe you can share your work @ahmed68
[FYT Android Head Units] ahmed68:
its only for teyes x1 4g

File on MEGA

mega.nz
[FYT Android Head Units] surfer63:
The Google software is always in the product partition.

The FYT application layer is in the elable partition inside the kernel on T'eyes.

On all other FYTs the Application layer is in the AllAppUpdate.bin and flashed to /oem.

There are design documents where which applications/software should be installed in which partition. Technically it does not really matter like older firmwares simply show.
[FYT Android Head Units] gordgelin:
but it does matter for chinese application layer at least in part so moving oem software somewhere else is really bad idea
[FYT Android Head Units] surfer63:
What do you mean with Chinese application layer?

And Android firmwares in general use quite a lot of symbolic links. These should be changed to point to the right partition/folder, but then it should function.
[FYT Android Head Units] gordgelin:
there are some hardcoded references to /oem and/or /elable partitions in libs/apps/system. of course it can be partly resolved by links but it is not the case here. it seems he tries just to move everything except few config files to /product
[FYT Android Head Units] surfer63:
With hardcoded you mean inside the APK's? Because that would make it terribly difficult indeed (and I didn't know that).

If it is only file/folder symlinks inside the partitions, you can change the symlinks when repartitioning.

That is how you do it (I assume), how Mario does it (I assume) and how I do it when working on T'eyes firmware (which I only did once).

I agree: his way of working is wrong and will not lead to the desired results. Apart from the fact that it is indeed useless to make your unit like a Pixel phone or so.
[FYT Android Head Units] ahmed68:
thats mean all how make mod firmware in the wrong way because all apps names is changed , if that true the unit will play bad , after my work the unit play quickly you can test that
[FYT Android Head Units] laoyang88:
specialty of China. Also included in Chinese phones. Kicked out Google services. app can only be hardcoded. The advantage is that it can be used after installation. Does not depend on resources such as other libraries.
[FYT Android Head Units] ahmed68:
how i can mount the work folder
[FYT Android Head Units] drummerjoey567:
Is there a an easy way to put in @seb21's modded apk into @gordgelin's latest firmware for the CC3 2K? Maybe incorporate it into a after release? I have his firmware and would love cutomizable Canbus wheel controls, it's one of the main things lacking in the Teyes products. I've read through multiple threads and am still unsure how to do it, or if it will even work.
[FYT Android Head Units] gordgelin:
no, it is not compatible with my firmware since my ms.apk also modified and as stated in firmware description it is better not to install any other ms.apk
[FYT Android Head Units] 00day:
Processing 'product' image ...

BROTLI -- Handling product.new.dat.br...
rm: cannot remove '_tmp/_firmware/product.new.dat.br': No such file or directory
Converting product.new.dat file into product.img file
rm: cannot remove '_tmp/_firmware/product.new.dat': No such file or directory
Creating _mountpoint/product folder...
Adding '128 Mb' extra size to _tmp/_firmware/product.img ...
128+0 records in
128+0 records out
134217728 bytes (134 MB, 128 MiB) copied, 0.771373 s, 174 MB/s
e2fsck 1.47.0 (5-Feb-2023)
ext2fs_open2: Bad magic number in super-block
e2fsck: Superblock invalid, trying backup blocks...
e2fsck: Bad magic number in super-block while trying to open _tmp/_firmware/product.img

The superblock could not be read or does not describe a valid ext2/ext3/ext4
filesystem. If the device is valid and it really contains an ext2/ext3/ext4
filesystem (and not swap or ufs or something else), then the superblock
is corrupt, and you might try running e2fsck with an alternate superblock:
e2fsck -b 8193 <device>
or
e2fsck -b 32768 <device>

resize2fs 1.47.0 (5-Feb-2023)
resize2fs: Bad magic number in super-block while trying to open _tmp/_firmware/product.img
Couldn't find valid filesystem superblock.
Mounting image...

Done with image product !

Hi, i cant resolve this error code. Does someone have an idea how to fix this?
[FYT Android Head Units] surfer63:
It already starts with the first error "rm: cannot remove '_tmp/_firmware/product.new.dat.br': No such file or directory"

But this doesn't give us any clue at all where this comes from.

But you might also have a look at this thread and look at the heading "How are these kernels created?".

I moved on from Mario's scripts and expanded them.

But first of all: What do you want to achieve? Can't you use one of the kernels in above mentioned thread?
[FYT Android Head Units] xd2sue6w4i:
Hello guys. First of all, excuse me for my English, it's not native to me.

I downloaded "FYT-Firmware-Workbench.zip" from post #1, but it has old signature method with "SignApkv2.jar" file, which is the same as file from post #26. MarioDantas wrote "the post 26 uses the older sign methos that's supported by t'eyes". So my question is, where i can find new "SignApkv2.jar" or maybe "SignApkv3.jar" to sign my moded firmware, because with original "SignApkv2.jar" it fails with error about illegal firmware. Thanks.
[FYT Android Head Units] BakaValen:
Same exact issue. Please let me know if you find a fix.
[FYT Android Head Units] BakaValen:
Yeah. I fixed that by reading........... ffs....

Go to the following post and use the new zip file.

FYT Firmware Workbench 2.0

# FYT-Firmware-Workbench PLEASE DO NOT USE WITH T'EYES CC3 FIRMWARE Scripts intended to mount the FYT UIS7862 firmware, make modifications and reassemble it back They can retrieve the firmware from specified location and after modification...

xdaforums.com

That signs it. I dunno if it will flash yet tho.
[FYT Android Head Units] wipika1:
I'm scratching my head on why the elable.img is not mounted correctly.

I've tried 3 different FYT firmwares (my unit's, @surfer63's modified, and a generic makede one) and all partitions mount fine, but this happens with elable:

con@DESKTOP-IJ4DPQG:/mnt/d/FYT/_mountpoint/elable$ ls -al
total 24
drwxr-xr-x. 3 root root 4096 Dec 31 2008 .
drwxrwxrwx 1 con con 4096 May 18 20:31 ..
-rw-r--r--. 1 root root 630 Dec 31 2008 for_build_err
drwx------. 2 root root 16384 Dec 31 2008 lost+found
con@DESKTOP-IJ4DPQG:/mnt/d/FYT/_mountpoint/elable$

any thoughts?
[FYT Android Head Units] surfer63:
And why do you think it is not mounted correctly, because it is empty?

What did you expect there? On my Mekede I see the same.

What is the size of the elable.new.dat.br inside your 6315_1.zip? Something like 700 ~1000 bytes (that is bytes, not megabytes or kilobytes).

In that case it is empty.
[FYT Android Head Units] wipika1:
I read in another forum that I could find the syu.canbus.apk along with the other syu.* apks in the elable partition. Guess that's not the case? What would the for_build_err indicate?

I want to unpack the CANbus apk and look into the command codes for my car's protocol to figure out some specific A/C control codes.
[FYT Android Head Units] surfer63:
The Canbus apk is in the AllAppUpdate.bin
[FYT Android Head Units] wipika1:
yes...yes it is :oops::oops:. Once again thanks for the help @surfer63 !
[HTC Vox] dekraan:
Does it exist?

Hello! I have just upgraded my mobile with the dr. Martin Gonzo Rom to WM 6.1, unfortunately it is only in English!

Does it exist in the Dutch language? I am looking for Dutch interface and menu's! I've tried creating my own rom, with the Rom Language updater, but that error-ed on me, for reasons I do not understand.

Is there anyone who knows more? Does it exist? Doesn't it? Who has one?

Thank you for your time! :)
[HTC Vox] FeareX:
I would be interested in this too. It would be even better if fireburned's cleanrom gets translated.

Want dat leest toch wel wat makkelijker :)
[HTC Vox] dekraan:
Mee eens :-) de Engelse versie is top, maar geef mij toch maar ouderwetsch Hollandsch!

-- on topic:

has anyone heard of a dutch version? Is it possible or? Is anyone able to build one with dr gonzos language builder, found somewhere else on this forum? I failed miserably!
[HTC Vox] Nicker:
jaah die wil ik ook wel

aka

I would like that
[HTC Vox] coone:
Inderdaad, dat zou ik ook wel willen

Indeed, that I would also like to. :D
[HTC Vox] FeareX:
anyone?! who can at least tell us how to do it??

i have absolutely no idea where to begin :o
[HTC Vox] frauhottelmann:
Well you need to find SYS language for 6.1 and then translate the mui files from HTC to Dutch, then we can talk about making a ROM!
[HTC Vox] dekraan:
That sounds difficult, but in a country filled with nerds (oh oh), there must be a dutchman or -woman capable of understanding what you just said ;)

But who?
[HTC Vox] spone1:
There is a S740 Orange ROM around, WM6.1 based which contains about 10 languages, including the Dutch language. Tried fiddling around with the mui files for my S730 but that didn't work out very well so far...
[HTC Vox] octaviafm:
There is a NoThrills WM 6.1 NLD *Dutch* V3 - Dutch ROM with the brand new OS build 19202

here's the link;

http://xdaforums.com/showthread.php?t=379401

good luck:):
[HTC Vox] NeoS:
^ That's a Kaiser rom. That won't work on a vox, right?

If anyone has found a Dutch WM 6.1 rom, please let me know.
[HTC Vox] frauhottelmann:
I may have the files necessary for cooking a dutch ROM, but I don't have the time right now. Maybe in two weeks.
[HTC Vox] ETR:
That'd be awesome :)
[HTC Vox] NeoS:
That would definitely be awesome. I know my girl would really appreciate it.
[HTC Vox] frauhottelmann:
Uh I just noticed that the last one was my 1000th post :D

Yeah, just not the next week since I am going to be really busy!
[HTC Vox] Deksel:
Frauhottelman, keep up the good work... really like the rose 0.4!

If you do find some spare time, I would be interested in a Dutch rom as well... wish I could do it myself, but some guys are good in building houses and some are good at making rom's ;-)

good luck and thanks for the rose!
[HTC Vox] [1]-Puchie:
I almost can't wait, it would be very nice if you can cook one :rolleyes:
[HTC Vox] frauhottelmann:
Next week. And then I don't even know if it'll work!? :D
[HTC Vox] [1]-Puchie:
I have lots of trust in you :D
[HTC Vox] erwinbennink:
I hope there is comming a ducht rom too! Is someone making it already?

Sorry for my poor englisch :(
[HTC Vox] [1]-Puchie:
As you can read above, if frauhottelmann has got some sparetime he'll try to cook one. So if you've got a little patience there will be one ;)
[HTC Vox] erwinbennink:
Nice!!! I am waiting!
[HTC Vox] frauhottelmann:
If I get bored on the week end I'll try to make one!
[HTC Vox] hansschuiling:
Let me know if i can help with translation etc... happy to help out. :D