Database Info

[Q] pppwidget on our tab??

Has anyone tested if it works on our tab or not....Plus does anyone know ho to find the power output of our tab's usb host mode????
I'll be geting my new usbotg cable soon so i'll also try n post the result....
For those who don't know about pppwidget, its a which allows you to use your 3G/2G stick(dongle) on your tab using the otg cable...
Market link
Read More about project here..

Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).

proudfoot said:
Hi thanks for this information, I tried this and it requires extra kernel modules (option, which is not included in cm10 kernel).
Click to expand...
Click to collapse
Can you please tell the steps you took and the result you got...This isn't supposed to need any modules except usb_modswitch which it already include....It works on CM10 nexus 7 too...Which dongle did you use???

Yup, it works it requires couple of modules not included in cm10 p5100 kernel, i already build the modules (see attachment) . Enjoy
I uses zte cdma modem, that modem requires 'option' module but most 3g/CDMA dongle uses this module.
You just need to copy those modules to /system/lib/modules.
edit: forgot to actually attaching the modules ~_~

Update: Vpn doesn't seem to work with pppwidget.
Update2: works, needs to manually set the gateway

cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....

kan_bleach said:
cool...i'll get back to you in couple of days(waiting for my new otg cable)... can you please give the .c file for the modules also....still learning all this stuff so wlll be helpful....
Click to expand...
Click to collapse
clone it from here -> https://github.com/cmenard/android_kernel_samsung_espresso10
as for compiling it follow/adapt from this tutorial -> http://stevechui.blogspot.com/2011/10/compiling-kernel-modules-tunko-for.html

Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???

kan_bleach said:
Its giving 'port not found'....any solutions??
Did you directly connected the dongle to tab or used a powered hub???
Click to expand...
Click to collapse
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?

proudfoot said:
Directly, what the log (it should be in /sdcard/pppwidget/log/) say?
edit: actually with this -> http://www.amazon.com/Samsung-EPL-1PL0BEGXAR-USB-Connection-Kit/dp/B005518J6Q it's still count as directly right?
Click to expand...
Click to collapse
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..

kan_bleach said:
Yup that's direct
Checked the log...mod_switch successful, but loading option module fails...option.ko is in the correct folder..
I tried insmod but it says operation not permitted...
Tried su and then insmod but then it says failed (trying using terminal emulator)..
Click to expand...
Click to collapse
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.

proudfoot said:
Your option.ko probably not compatible with the kernel, try to do
Code:
strings option.ko | grep vermagic
uname -a
and compare both output, it should be similar.
also if you use insmod I think you'll need to insmod usb_wwan.ko first, because option.ko depends on that module, so it should be
Code:
insmod usb_wwan.ko
insmod option.ko
then, move the pppwidget to launcher and plug the dongle.
Click to expand...
Click to collapse
Tried the command...output is the same...still not able to use insmod...
Log
Code:
USB_ModeSwitch log from Sat Oct 27 16:23:19 IST 2012
Raw args from udev: 1-1.4/1-1.4:1.0
Using top device dir /sys/bus/usb/devices/1-1.4
----------------
USB values from sysfs:
manufacturer ZTE, Incorporated
product USB Storage
serial 000000000002
----------------
bNumConfigurations is 1 - don't check for active configuration
SCSI attributes not needed, moving on
checking config: /data/data/de.draisberghof.pppwidget/app_tmp/19d2.fff5
! matched. Reading config data
config: TargetVendor set to 19d2
config: TargetProductList set to fff1,fffe,ffff
Driver module is "option", ID path is /sys/bus/usb-serial/drivers/option1
Logger is: /system/bin/log
Command to be run:
usb_modeswitch -I -W -D -s 20 -u -1 -b 1 -g 14 -v 19d2 -p fff5 -f $configBuffer
Verbose debug output of usb_modeswitch and libusb follows
(Note that some USB errors are to be expected in the process)
--------------------------------
Reading long config from command line
* usb_modeswitch: handle USB devices with multiple modes
* Version 1.2.4 (C) Josua Dietze 2012
* Based on libusb0 (0.1.12 and above)
! PLEASE REPORT NEW CONFIGURATIONS !
DefaultVendor= 0x19d2
DefaultProduct= 0xfff5
TargetVendor= 0x19d2
TargetProduct= not set
TargetClass= not set
TargetProductList="fff1,fffe,ffff"
DetachStorageOnly=0
HuaweiMode=0
SierraMode=0
SonyMode=0
QisdaMode=0
GCTMode=0
KobilMode=0
SequansMode=0
MobileActionMode=0
CiscoMode=0
MessageEndpoint= not set
MessageContent="5553424312345678c00000008000069f030000000000000000000000000000"
NeedResponse=0
ResponseEndpoint= not set
InquireDevice disabled
Success check enabled, max. wait time 20 seconds
System integration mode enabled
Use given bus/device number: 001/014 ...
Looking for default devices ...
bus/device number matched
searching devices, found USB ID 19d2:fff5
found matching vendor ID
found matching product ID
adding device
Found device in default mode, class or configuration (1)
Skipping the check for the current configuration
Using interface number 0
Using endpoints 0x0a (out) and 0x89 (in)
USB description data (for identification)
-------------------------
Manufacturer: ZTE, Incorporated
Product: USB Storage
Serial No.: 000000000002
-------------------------
Looking for active driver ...
OK, driver found; name unknown, limitation of libusb1
OK, driver "unkown" detached
Setting up communication with interface 0
Using endpoint 0x0a for message sending ...
Trying to send message 1 to endpoint 0x0a ...
OK, message successfully sent
Resetting response endpoint 0x89
Resetting message endpoint 0x0a
Could not reset endpoint (probably harmless): -34
Device is gone, skipping any further commands
Bus/dev search active, referring success check to wrapper. Bye.
ok:busdev
--------------------------------
(end of usb_modeswitch output)
Checking success of mode switch for max. 20 seconds ...
Waiting for device file system (1 sec.) ...
Reading attributes ...
All attributes matched
Mode switching was successful, found 19d2:fff1 (ZTE, Incorporated: ZTE CDMA Tech)
Now checking for bound driver ...
No driver has bound to interface 0
Module loader is /system/bin/insmod
Trying to find module "option"

Have you try to insert those modules manually first, before running pppwidget and plug-in the dongle? I think we use the same dongle, so it should works ~_~
anyway this is how i get this to work:
1. create directory /data/loca/modules/ on tab
2. move all those modules (option.ko, usb_wwan.ko, ppp_async.ko) to this directory.
3. su and insmod all those modules:
Code:
insmod /data/local/modules/usb_wwan.ko
insmod /data/local/modules/option.ko
insmod /data/local/modules/ppp_async.ko
5. move pppwidget to launcher and plug the dongle.
optional:
create this script and put it in /data/local/userinit.d/93loadmod directory
Code:
#!/system/bin/sh
/system/bin/insmod /data/local/modules/usb_wwan.ko
/system/bin/insmod /data/local/modules/option.ko
/system/bin/insmod /data/local/modules/ppp_async.ko
so it will load all those modules at boot time.

I am doing the same thing...but insmod is giving error
When i run the insmod command i get
insmod: init_module 'usb_wwan.ko' failed(Exec format error)

kan_bleach said:
insmod: init_module 'usb_wwan.ko' failed(Exec format error)
Click to expand...
Click to collapse
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)

proudfoot said:
From a bit of googling it looks like your module is not build for your kernel (or even build for wrong architecture), what is your kernel? and where do you get the modules, do you compile it yourself or is it from somebody else?
try to do dmesg after you do insmod to see more information.
btw, the module that i have posted only works for p5100 and cm10 kernel (3.0.8-CM-g11fad65)
Click to expand...
Click to collapse
I used the modules you posted...I am using CMOC-10 kernel....Maybe that is the issue...But the kernels are supposed to be identical except for the OC and the governors feature...i am on 3.0.8-CM-gbd034d0

kan_bleach said:
gbd034d0
Click to expand...
Click to collapse
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.

proudfoot said:
Yup that the problem, it needs to have the same extra version number even though it comes from same source. I guess I could compile it for you.
Click to expand...
Click to collapse
Please do...

kan_bleach said:
Please do...
Click to expand...
Click to collapse
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.

proudfoot said:
Here, I hope it works because it comes from cm10 source, I only change the extra version to match yours.
Click to expand...
Click to collapse
Thanks i'll try and post the result...can you give me the github link for the cm10 kernal for our tab???

Need help to get Tom Tom working on Intel device

Hi Guys,
As we all know Tom Tom does not work on the intel units.
For the MTCB devices there is a way to get it working: https://forum.xda-developers.com/an...lution-tomtom-connection-to-internet-t3368026 To get that working you need xposed installed. Since we can not install xposed we can not use that methode.
If we look at this post: https://forum.xda-developers.com/showpost.php?p=69772506&postcount=109 someone already tried to put a serial into the default.prop file but that does not work.
I found this page: http://stackoverflow.com/questions/19368712/where-is-ro-boot-serialno-and-ro-serialno-stored that does not work neither.
http://forum.odroid.com/viewtopic.php?f=94&t=12243
This page says we need to extract the boot.file and use the CarlivImageKitchen tool to extract it so we can modified the file.
I could find the boot.img in the latest update from joying: https://www.carjoying.com/Joying-blog/59.html location: 5009_20.zip.
I tried to extract the boot.img and unpack it with the Kitchen tool and found the init.rc file. Also found the on boot section and added the following lines:
Code:
# Set serial number.
setprop ro.serialno 1234567812345678
setprop ro.boot.serialno 1234567812345678
setprop ril.serialnumber 1234567812345678
Also added those lines to the default.prop file.
Repacked the file and put everything together.
We know that if we put a usb stick with the latest firmware in the usb input from the device it will automatic update and so also the new serial numbers.
The point is, i only wrote a android program a few times and i do not know much about boot files etc.
My question to your developers (because you are 100x times better then i am) would this work? What could probably go wrong if we add 3 lines in the ini.rc file?
Hoping to get some help from you guys!

According to the steps you need to do to get root i found the command to copy the boot.img to the device:
Code:
adb shell dd if=/mnt/usb_storage/USB_DISK0/udisk0/boot.img of=/dev/block/mmcblk0p9
I used the boot.img from the root steps. Added the command in the init.rc file and default.prop. Copied it back to the device and booted.
No luck with the ro.serialno and ro.boot.serialno. serialno was changed to what i have set.
The values of ro.serialno are overwritten somewhere else

Hi,
Have you been able to change the serial no. yet? I'm also waiting for a solution to install Tomtom GO on to this intel headunit

Nope still no success.
I don't have any idea what i can do to fix it.

Put here photo whit error tomtom go please and model headunit and android .

General HowTo: Root Joying SC9853i Head Unit

First off a big thanks to the guys at {Mod edit} for doing all the hard work, I'm just writing this post as a guide for those who don't speak Russian - like myself
Second thanks to all those on the Original Thread (https://forum.xda-developers.com/an...ying-android-8-1-intel-airmont-eight-t3897206) for helping me finally find an android head unit worth buying.
Compatible Firmware Versions:
9853i 800X480 2019.3.20
9853i 1024X600 2019.3.29
"New" 9853i 1280X480 新UI 2019.3.18
"Old" 9853i 1280X480 旧UI 2019.3.18
Legacy Support
2019.3.5
https://forum.xda-developers.com/showpost.php?p=79310679&postcount=43
Changelog:
April 10 2019:
Added new files for several units
Previous Changelogs:
April 4 2019:
Fixed typo in Developer instructions
Added "Ultra Wide" version
March 28 2019:
Simplified Installation Process
Reformatted instructions
Warnings
I am not responsible for bricked devices. Proceed through this rooting process at your own risk.
Rooting your device will void Joying's waranty. (Even though it can be uninstalled in Magisk Manager).
Prereqs
BLANK Flash drive or MicroSD card (1GB is plenty)
A copy of the "Joying Root 9853i ***.zip" appropriate to your device (attached)
Head unit running latest version of Joying firmware (https://www.joyingauto.eu/blog/post/joying-intel-airmont-sc9853i-car-stereo-latest-update/)
Rooting Your Device
Plug your Flash Drive or MicroSD into your computer. Make sure there's nothing on it.
Extract the contents of the device-appropriate archive to your flash drive. You should have 2 files: "lsec6521update" and "6521_1.zip".
Go to your head unit. Moment of truth; no turning back once you begin this next step! Plug your flash drive into the head unit. The update will be detected and the update will automatically begin.
Your head unit will reboot into recovery and install the update containg root. DO NOT POWER OFF YOUR DEVICE OR UNPLUG THE FLASH DRIVE DURING THIS PROCESS!!! If you do, you may permanantly brick your device! Once prompted by the update process, remove your Flash Drive and let it boot back up into Android.
If you would like the more in depth "developer" tutorial, attached is Developer.zip.
Inside I included "Readme.rtf" - a copy of the developer instructions with screenshots.

Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**

I truly TRULY hope you win the lottery..........or maybe even get a raise at work!! LOL.
Thanks!
I literally ordered my HU about 20 min ago. When it gets here Ill check your file with the one I get.

prrlhkr said:
Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
Click to expand...
Click to collapse
Friend, you are a Lord of Joying!!
Succesful, device rooted at 2 minutes! Enough this zip file and the magisk apk! Many thanks! Now I begin hunting for radio skins and etc

prrlhkr said:
Senior members, after following the above proceedure, I have a Joying-signed "6521_1.zip" file containg Magisk.
Is this file specific to my unit or will others be able to flash this file to get root? If so it would make the rooting process a lot faster and noob-friendly. Thanks!
Please see attached update file.
Unzip to root of an empty flash drive and plug into head unit. Device will update automatically.
**FLASH AT YOUR OWN RISK, I AM NOT RESPONSIBLE FOR BRICKED UNITS**
Click to expand...
Click to collapse
Well done :good:
The magisk patched boot image you have created, is valid for all Joying SC9853i FYT machines. It is based on the firmware and not on your specific unit, and the firmware is identical for all Joyings.
So everyone on the same firmware version with an Intel Joying can use your patched boot image.
The only "but" here is that the boot image can change over firmware versions, so please specify the firmware version for which your patched boot image is, e.g. the "9853i 2019.3.5" version (I assume). It shouldn't make a difference at all whether it is for the 1024x600, 800x480, with or without 4G. All those specifics are not in the boot image.
So the release date is important for the version.
And because of the possible "but": You need to create a new boot image per new firmware version. So if Joying releases a new firmware and you flash it, you better not use your already created boot image, but create a new patched boot image.
If your lucky, nothing has changed and you can use the same.
If you are unlucky you will "soft-brick" your unit, but even in that case there is no worry. You simply take the Joying firmware again and flash it again. Flashing is done by the recovery image. So an incorrect boot image will not boot your unit, but via recovery (reset with a needle or so in the reset (RST) hole) you can simply flash your unit again.

surfer63 said:
Well done :good:
The magisk patched boot image you have created, is valid for all Joying SC9853i FYT machines. It is based on the firmware and not on your specific unit, and the firmware is identical for all Joyings.
So everyone on the same firmware version with an Intel Joying can use your patched boot image.
Click to expand...
Click to collapse
If that's the case could someone upload their signed zip file as I just can't get signing to work on my Mac. Thanks in advance.

colonel_lp said:
If that's the case could someone upload their signed zip file as I just can't get signing to work on my Mac. Thanks in advance.
Click to expand...
Click to collapse
@prrlhkr added it to the 2nd post of this thread.

Whether SC9853i receives any attention by developers like Sofia&PX5 in the future? Extra Tools apk made by Surfer is excellent and mods are enviable

CTDPeti said:
Whether SC9853i receives any attention by developers like Sofia&PX5 in the future? Extra Tools apk made by Surfer is excellent and mods are enviable
Click to expand...
Click to collapse
I will extend my JET apk.
Xposed need to be tested for install. Maybe a direct install from the Xposed installer itself. This should be feasible considered the fact that the Magisk rooting, once successful, should allow for transparent install of Xposed. This would mean that you download the Intel 8.1 version installer and try it.
If it does work, most Xposed modules, including my XFytTweaker should work. I already had a quick look at the server apk, and all functions, calls, etc. are the same. they have not changed over Sogia3G to PX5 now to Intel SC98539i.

surfer63 said:
I will extend my JET apk.
Click to expand...
Click to collapse
EDIT: Rewrite of this post.
To be able to start on this I need from someone with a rooted unit a system listing.
So from a terminal
Code:
su
ls -lR /system > /sdcard/system_list.txt
ls -lR /sys > /sdcard/sys_list.txt
And please attach both files "system_list.txt" and "sys_list.txt" to a post (you might want to zip it )

tried to do but permission denied with su, hope this is what you need, I'm a noob, sorry

CTDPeti said:
tried to do but permission denied with su, hope this is what you need, I'm a noob, sorry
Click to expand...
Click to collapse
Thanks for your attempt, but this is not what I need.
Did you do the "ls -lR"? (uppercase R? This is important on linux systems where the underlying core is of Android).
The su command is actually necessary for the "/sys" folder/file system.
You say that su permission is denied. What error did you get? Did you get a Magisk popup asking you to give root access to the application (once/next 15 minutes/always)?
See also this useful site: https://www.didgeridoohan.com/magisk/HomePage

surfer63 said:
Thanks for your attempt, but this is not what I need.
Did you do the "ls -lR"? (uppercase R? This is important on linux systems where the underlying core is of Android).
The su command is actually necessary for the "/sys" folder/file system.
You say that su permission is denied. What error did you get? Did you get a Magisk popup asking you to give root access to the application (once/next 15 minutes/always)?
See also this useful site: https://www.didgeridoohan.com/magisk/HomePage
Click to expand...
Click to collapse
Sorry for the previous mistache but now i'm in my garage and mendig my motorbike (yeah, spring beginnig in Central Europe ) with some tools and beers. Previous terminal command apk wasn't fully compatible with magisk and not to ask superuser grants. I found a new one and tried to generate other files, hope it is good enough but it is not so easily from an average garage...

CTDPeti said:
Previous terminal command apk wasn't fully compatible with magisk and not to ask superuser grants. I found a new one and tried to generate other files, hope it is good enough but it is not so easily from an average garage...
Click to expand...
Click to collapse
This is exactly what I need. Thanks.
I will start extending the JET apk

surfer63 said:
This is exactly what I need. Thanks.
I will start extending the JET apk
Click to expand...
Click to collapse
One more question. For quite some functionalities I need to mount /system "read-write". That is different per unit. From a terminal it is on the Sofia 3GR:
Code:
su
mount -o remount,rw /system
on the PX5:
Code:
su
mount -o rw,remount /system
(see that the rw and remount are reversed)
If I mix them up on both models I get the error "device or resource busy" or something like that.
So those on a rooted 9853i, please try both commands. If they both work it is nice, if both don't work we have another issue (or challenge, whatever you want to call it)

surfer63 said:
One more question. For quite some functionalities I need to mount /system "read-write". That is different per unit. From a terminal it is on the Sofia 3GR:
Code:
su
mount -o remount,rw /system
on the PX5:
Code:
su
mount -o rw,remount /system
(see that the rw and remount are reversed)
If I mix them up on both models I get the error "device or resource busy" or something like that.
So those on a rooted 9853i, please try both commands. If they both work it is nice, if both don't work we have another issue (or challenge, whatever you want to call it)
Click to expand...
Click to collapse
They both work for me no problems, is this what you're looking for?

prrlhkr said:
They both work for me no problems, is this what you're looking for?
Click to expand...
Click to collapse
Yes, it is.
That is also how it works on every linux/unix system and how it should work, but not on the Joying Android 6 and Android 8 systems.
When I was expanding my JET apk to PX5 (from Sofia) It took me quite some time to understand that the stupid Android versions on those systems were not behaving like they were supposed to.
Edit: as example on my PX5:
Code:
px5:/ $ su
px5:/ # mount -o remount,rw /system
mount: '/devblock/platform/ff0f0000.dwmmc/by-name/system'-> '/system': Device or resource busy
1|px5:/ # mount -o rw,remount /system
px5:/ #
Every unix/linux guru would consider me crazy, until they see it themselves. And on the Sofia it is the other way round.
Stupid FYT.

All,
I made the first experimetal JET apk which can be used on the FYT based Joying Intel Airmont sp9853i as well.
As that is here actually off-topic, I posted that version in the Joying Extra Tools thread.
Please continue in that thread for all JET related questions/remarks/etc. and let's keep this thread for the actual rooting questions/remarks.

surfer63 said:
All,
I made the first experimetal JET apk which can be used on the FYT based Joying Intel Airmont sp9853i as well.
As that is here actually off-topic, I posted that version in the Joying Extra Tools thread.
Please continue in that thread for all JET related questions/remarks/etc. and let's keep this thread for the actual rooting questions/remarks.
Click to expand...
Click to collapse
Surfer, mine is frozen, see attachment

CTDPeti said:
Surfer, mine is frozen, see attachment
Click to expand...
Click to collapse
Thanks. One error detected, maybe 2. Please continue this in the "Joying Extra Tools apk" thread.
With frozen I hope you mean the app, not your unit.
A frozen app can be closed via the App-manager: the rectangle top-right.
Edit: Did you get the question to give root access to the JET apk?

Software Development 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, 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

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.

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 !

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:
Bash:
**********************************************
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
Code:
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
Code:
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
Bash:
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
Bash:
echo " "
echo "READY !!!."
echo " "
Why not use
Code:
printf "\n\nREADY !!!\n\n"

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

mariodantas said:
I packed a 64bit java 8 cause java 11 does not sign the ZIP, (or at least I didn't reach the sign correctly)
Click to expand...
Click to collapse
Yes, you are right. the signapkv2 is already very old. I forgot that. I just tested and java V11 comes without the sun packages.

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

@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"

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.

j-5 said:
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.
Click to expand...
Click to collapse
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 !

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

mariodantas said:
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 !
Click to expand...
Click to collapse
OK, got it.
I had commented out the "expand' part, my bad .

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

No Github, I'll release some fixes soon !

mariodantas said:
I'll release some fixes soon !
Click to expand...
Click to collapse
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

Where are the 2.0 tools?

Andy826 said:
Where are the 2.0 tools?
Click to expand...
Click to collapse
In the OP

surfer63 said:
And about the resizing/shrinking of the images: Why do you do that?
Click to expand...
Click to collapse
@surfer63 I do that to allow me to add content inside, if not, the free size is 0Kb after mount

@mariodantas The CC3 Firmware Tools don't seem to work with the January firmware. The error when using them on the January firmware is:
Code:
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?

ahmed123 said:
Any chance of this being fixed please?
Click to expand...
Click to collapse
Not compatible with CC3 anymore

Help with ADB shell locked with password

Hello,
I'm trying to install apk apps but the system block any explor files at all to access apk files.
So I use ADB and connected successfully
With HU unit android 9 (aarch64) but when I am trying to use command (install -r path/xxx.apk)
Request verfiy password.
Check attachment.
How to remove password or decryption?
Thank you

Hi there! Have you solved the problem?

Is it an MTCD unit. Post MCU Version.