Software Development FYT Firmware Workbench 2.0

[mariodantas]

# 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, they can put the packed and signed 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 ZIP file 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 = (autorun after import*) Unpack the imported firmware and create the mount moints (as specified in the config.ini file) to work with the firmware

5-) tweaker.sh = Allows change Locale, Language, Country and allows enabling ADB and OTG (if hardware supports it)

6-) inject_mods = Copies all contents of "_mods" folder into system partition, like gps.conf or even bootanimation, up to you to creat the same folder structure with your own files to inject

7-) repack.sh = Unmount the modified firmware from the mount points, delete the mount points, assembly the new ZIP file, sign it and move it to the patched directory as specified in config.ini

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 local workbench !


N'joy it !

[CHANGELOG]

2.0 Introduces a different ZIP signature method

1.0 Initial release

 

[surfer63]

Did you already try to flash it? I seed that you sign with the test keys but does that now work on the 7862?
On the previous architectures the recovery did not allow self signed zips.

 

[mariodantas]

Yes it works well, of course I flashed a modified 6315_1 befor make this post. You can trust the scripts, take a look at the tweaker.sh who allow you to modify some settings, Locale,Region, Coutry, and more to come !

 

[surfer63]

Hi,

I tried your tools. Nice work.

I first did the "import_original.sh" and then the "unpack.sh". I did use this on a RPi4 running Debian Linux. All my Linux machines are currently RPi boxes and I use my headless server RPi4 for most stuff I do myself on images. (Next to that I have a Chromebook running Linux as well, but that one doesn't allow me to mount images in the linux sandbox.)

In the unpack.sh I get errors after brotli on the resizing of all the images:

**********************************************
 
 Processing 'system' image ...
 
BROTLI -- Handling system.new.dat.br...
Converting system.new.dat file into system.img file

When tring the "Converting .." is where it goes wrong without error message. The sdat2img is using "#!/usr/bin/env python" which, on an python3 only system gives "/usr/bin/env: ‘python’: No such file or directory"
When I change the call to "python3 sdat2img.py <etcetera>" it works. It might be better to use something like

if [ `which python` ]; then
    ./tools/sdat2img.py
elif [ `which python3`]; then
    python3 ./tools/sdat2img.py
else
    printf "\n\nNo python found!!\n\n"
    exit 1
fi

Otherwise your created dat file is 0 bytes (simply an echo of 0 bytes to a new file), then giving corrupt empty images of 128 MB when trying to resize them.

And about the resizing/shrinking of the images: Why do you do that?
Simply leave the img as is and mount it read-write, not read-only.
Please use

mount -t ext4 -o loop,rw $unzippedPath$i.img $MOUNTPOINT/$i

and then simply copy (as root) your stuff in or make the modifications directly (as root). After unmounting you can immediately repack and brotli-compress it again. No extra intermediate steps necessary.

****
And some other remarks (actually a bit of nit-picking, please don't feel offended. I think you did a great job):
You use and pack a 64bit jdk with it, which is of course very convenient in most cases but doesn't work on my ARM raspberry pi.
I would put something in the shell script like

echo "Singning '${FIRMWAREZIPFILENAME}' file..."
if [ -n `which java` ]; then
    # Not found. Use packed version and hope it is a 64bit system
    tools/jdk64/bin/java -jar tools/SignApkv2.jar <etcetera>
else
    # Use system version
    java -jar <etcetera>
fi

You also use

echo " "
echo "READY !!!."
echo " "

Why not use

printf "\n\nREADY !!!\n\n"

 

[mariodantas]

Don't feel offended at all fellow, that's normal you're improving the scripts so suit your needs, that's normal, and your code (above) seems much more adapted than mine, I packed a 64bit java 8 cause java 11 does not sign the ZIP, (or at least I didn't reach the sign correctly)

Y have a giltab at home with that projects (FYT, TS10 etc....) y you want to participate and pull-request your changes, os help me improving that scripts, you're welcome and I'll send you the link via PM

 

[surfer63]

I packed a 64bit java 8 cause java 11 does not sign the ZIP, (or at least I didn't reach the sign correctly)

Yes, you are right. the signapkv2 is already very old. I forgot that. I just tested and java V11 comes without the sun packages.

 

[mariodantas]

Will add and arm64 java 8 and detect the proc architecture by scripts to select the right java

 

[mariodantas]

@surfer63 I forgot to tell you that I released FYT Firmware Workbench 2.0 which includes another 6315_1 signature method (no more signapkV2), (as required with lsec6315update after Jul/2/22) thos signs well the new 6315_1 files, so we can still modify their contents and repack again and flash without the message: "Please use legal system"

 

[j-5]

I finally got my images to mount. (had to sudo)
I used the modifications @surfer63 suggested. (python3 was the trick here)

edit: are the mountpoints supposed to be RO? I'm getting "no space.." error running the tweaker.

 

[mariodantas]

I finally got my images to mount. (had to sudo)
I used the modifications @surfer63 suggested. (python3 was the trick here)

edit: are the mountpoints supposed to be RO? I'm getting "no space.." error running the tweaker.

No, they shoud have 128Mb + each uhntil repack

NOTE: before running FYT Firmware Workbench do a "sudo su" (you must run as ROOT) that's why it didn't work flawlessly, I'll modify the scripts to ask for sudo su if needed !

 

[surfer63]

@mariodantas : Your FYT workbench was still in the Android head units section. I had it moved to the FYT forum.

 

[j-5]

No, they shoud have 128Mb + each uhntil repack

NOTE: before running FYT Firmware Workbench do a "sudo su" (you must run as ROOT) that's why it didn't work flawlessly, I'll modify the scripts to ask for sudo su if needed !

OK, got it.
I had commented out the "expand' part, my bad .

 

[Aaaron16]

Is there a github repo for the latest scripts? I'd love to try this out.

 

[mariodantas]

No Github, I'll release some fixes soon !

 

[jp08]

I'll release some fixes soon !

this is very good, thanks for your hard work!
I am also having trouble parsing the system.new.dat.br file (I only chose to edit it in config). After changing to python3, file began to be mounted and repack. But I get an error on the device in the middle of installation related to "dynamic_partitions_op_list" even though I didn't change anything

 

[Andy826]

Where are the 2.0 tools?

 

[cryptyk]

Where are the 2.0 tools?

In the OP

 

[mariodantas]

And about the resizing/shrinking of the images: Why do you do that?

@surfer63 I do that to allow me to add content inside, if not, the free size is 0Kb after mount

 

[ahmed123]

@mariodantas The CC3 Firmware Tools don't seem to work with the January firmware. The error when using them on the January firmware is:

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/elable.img

Any chance of this being fixed please?

 

[mariodantas]

Any chance of this being fixed please?

Not compatible with CC3 anymore