Database Info

Problem with modules compilation for 3.0.8

Hi,
I've got problem with building Android kernel modules. I'm using GoClever A73 with Android ICS (4.0.3, kernel 3.0.8) for Eken T02 (both are Allwinner A10 based). I'm trying to compile modules for this kernel. Module I've found in Android has following modinfo:
Code:
filename: /home/sid/usbnet.ko
license: GPL
description: USB network driver framework
author: David Brownell
depends:
vermagic: 3.0.8+ preempt mod_unload modversions ARMv7
parm: msg_level:Override default message level (int)
And file:
Code:
/home/sid/usbnet.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
I'm using sources from github: madprogrammer/linux-aurora . I want to build for example usbserial.ko and pl2303.ko. I've built module with modinfo:
Code:
filename: drivers/usb/serial/usbserial.ko
license: GPL
description: USB Serial Driver core
author: Greg Kroah-Hartman, [email protected],
depends:
vermagic: 3.0.8+ preempt mod_unload modversions ARMv7
parm: vendor:User specified USB idVendor (ushort)
parm: product:User specified USB idProduct (ushort)
parm: debug:Debug enabled or not (bool)
Code:
drivers/usb/serial/usbserial.ko: ELF 32-bit LSB relocatable, ARM, version 1 (SYSV), not stripped
But when I'm trying to insmod module I've got Exec format error. There is a line:
Code:
usbserial: no symbol version for module_layout
strace says:
Code:
(...)
init_module(" ELF", 0xb634) = -1 ENOEXEC (Exec format error)
(...)
I'm think that there are some config values set in wrong way but haven't idea which.
There is .config in attachement. (Unfortunetely kernel running on Android doesn't provide config through /proc).
Have You got any idea where I made mistake?
Thanks

sorry buddy, I have no answer for you, but if you manage to build kernel, please post it here... thanks!

There is an SlateDroid post that might help you out.
I still can't post outside links, so ...
www dot slatedroid dot com
+
/topic/27852-generic-usb-serial-gps-hal-driver/page__view__findpost__p__344837
Regards,
Rodrigo

[Q]Android vendor/modules drivers question

I work with olinuxino A13 and Im using it as a touch screen control for different machines
using MODBUS protocols with a FTDI chip serial connection on USB.
I have found drivers for android and I put them in /system/vendor/modules/ftdi_sio.ko
and initialize them in preinstall.sh like this:
Code:
/system/bin/insmod /system/vendor/modules/ftdi_sio.ko
chmod 0666 /dev/ttyS0
chmod 0666 /dev/ttyS1
chmod 0666 /dev/ttyS2
chmod 0666 /dev/ttyS3
chmod 0666 /dev/bus/usb/*
And it works.
Now I have personal tablet with same android version 4.0.3 and 3.0.8 kernel
with cortex A5 dualcore processor.
Im trying the same thing and It doesnt work... also there isnt a /system/vendor/modules folder only /system/vendor/ so I created it but still.
I need this for test and portability when going on work trips...
Im no good with linux, so am I missing something or I do something completely wrong?
When I manually insmod ftdi_sio.ko in ADB I get this:
<3>[ 112.575894] ftdi_sio: version magic '3.0.8 preempt mod_unload modversions
ARMv7 ' should be '3.0.8-tcc preempt mod_unload ARMv7 '
Can I edit a compiled .ko?

[Q] Galaxy Tab 2 + USB ETHERNET (ASIX) Problem

Hello, i have a problem with my Samsung Galaxy Tab 2 7" (GT-P3110 ).
I want you to operate the device with ASIX AX88772 X usb ethernet card.
This was followed by the description:
http://forum.xda-developers.com/showthread.php?t=2131825
Downloaded:
Android Cross compiling Toolchain from github,
GT-P3110 source code ( from http://opensource.samsung.com/ , GT-P3110_JB_Opensource_Update1.zip )
I issue the following commands:
Code:
export CROSS_COMPILE=/root/git/Android_Toolchains/arm-eabi-4.4.3/bin/arm-eabi-
make ARCH=arm android_espresso_omap4430_r04_user_defconfig
make menuconfig
make modules
The translation is done right, created the asix.ko and usbnet.ko in /drivers/net/usb.
I grab this modules to tablet, but after the insmod commands get the following message:
Code:
[email protected]:/system/lib/modules # insmod usbnet.ko
insmod: init_module 'usbnet.ko' failed (Exec format error)
[email protected]:/system/lib/modules # insmod asix.ko
insmod: init_module 'asix.ko' failed (Exec format error)
Can you help me? What could be the problem?
My sw verisons(on device):
Android ver: 4.1.2
Kernel ver: 3.0.31-812001
Build no. JZO54K.P3110XXDMA2

biokill said:
Hello, i have a problem with my Samsung Galaxy Tab 2 7" (GT-P3110 ).
I want you to operate the device with ASIX AX88772 X usb ethernet card.
Can you help me? What could be the problem?
My sw verisons(on device):
Android ver: 4.1.2
Kernel ver: 3.0.31-812001
Build no. JZO54K.P3110XXDMA2
Click to expand...
Click to collapse
run
'head Makefile' inside your kernel source folder... what is reported?

Thank You
biokill said:
Hello, i have a problem with my Samsung Galaxy Tab 2 7" (GT-P3110 ).
I want you to operate the device with ASIX AX88772 X usb ethernet card.
This was followed by the description:
http://forum.xda-developers.com/showthread.php?t=2131825
Downloaded:
Android Cross compiling Toolchain from github,
GT-P3110 source code ( from http://opensource.samsung.com/ , GT-P3110_JB_Opensource_Update1.zip )
I issue the following commands:
Code:
export CROSS_COMPILE=/root/git/Android_Toolchains/arm-eabi-4.4.3/bin/arm-eabi-
make ARCH=arm android_espresso_omap4430_r04_user_defconfig
make menuconfig
make modules
The translation is done right, created the asix.ko and usbnet.ko in /drivers/net/usb.
I grab this modules to tablet, but after the insmod commands get the following message:
Code:
[email protected]:/system/lib/modules # insmod usbnet.ko
insmod: init_module 'usbnet.ko' failed (Exec format error)
[email protected]:/system/lib/modules # insmod asix.ko
insmod: init_module 'asix.ko' failed (Exec format error)
Can you help me? What could be the problem?
My sw verisons(on device):
Android ver: 4.1.2
Kernel ver: 3.0.31-812001
Build no. JZO54K.P3110XXDMA2
Click to expand...
Click to collapse
Can you please provide me with these modules I have the same need in my case ? If I can try the modules on my side

biokill said:
Hello, i have a problem with my Samsung Galaxy Tab 2 7" (GT-P3110 ).
Click to expand...
Click to collapse
Its also possible the compiler used is different, check the README in the kernel source.. I got my compiler from
https://github.com/AdiPat/Android_Toolchains

need help to root cloned samsung s4

cpu architecture arm Cortex-A7
cores 4
revision r0p4
gpu renderer mali-400 mp
model gt-i9500(mtk6589_e_lca)
manufacturer alps
board mtk6589_e_lca
hardware mtk6589
android version 4.4.4 (i dont why its like that. but when i check it its jelly bean)
kernel architecture armv7l
kernel version 3.4.39 (eng.whl.1407204932)
ram 456
rom 0.14
all i want is to root this device to install link2sd (
Please help please please
thanks in advance

Try Framaroot.

vantt1 said:
Try Framaroot.
Click to expand...
Click to collapse
i have tried framaroot, but it didnt work (
it says "failed try another exploit if available"
boromir and barahir are available exploits but neither works

vantt1 said:
Try Framaroot.
Click to expand...
Click to collapse
sir additional info. please help (
Root Access is not properly configured or was not granted.
Super User Application Status:
Superuser application - is NOT installed.
SuperSU application - is NOT installed.
System File Properties for Root Access:
Standard Location
Check Command: ls -l /system/bin/su:
Result: /system/bin/su: No such file or directory
Analysis: File /system/bin/su does not exist.
Standard Location
Check Command: ls -l /system/xbin/su:
Result: /system/xbin/su: No such file or directory
Analysis: File /system/xbin/su does not exist.
Alternative Location
Check Command: ls -l /sbin/su:
Result: /sbin/su: Permission denied
Analysis: File system permissions restricted and denied access.
Alternative Location
Check Command: ls -l /system/xbin/sudo:
Result: /system/xbin/sudo: No such file or directory
Analysis: File /system/xbin/sudo does not exist.
Root User ID and Group ID Status:
SU binary not found or not operating properly
System Environment PATH: /sbin /vendor/bin /system/sbin /system/bin /system/xbin
ADB Shell Default User:
ADB shell setting for standard access, stored in default.prop, is configured as: shell (non root) user - ro.secure=1
results from root checker

Hi
Jhobeth said:
cpu architecture arm Cortex-A7
cores 4
revision r0p4
gpu renderer mali-400 mp
model gt-i9500(mtk6589_e_lca)
manufacturer alps
board mtk6589_e_lca
hardware mtk6589
android version 4.4.4 (i dont why its like that. but when i check it its jelly bean)
kernel architecture armv7l
kernel version 3.4.39 (eng.whl.1407204932)
ram 456
rom 0.14
all i want is to root this device to install link2sd (
Please help please please
thanks in advance
Click to expand...
Click to collapse
Hello friend, I have the same phone mtk6589_e_lca,
but mine is dead soft brick, please send me your preloader.bin ?, Might save me

cara baixa o vroot no baixaki que da certo

board: mtk6589_e_lca
Hii. i have the same problem please help i need your rom

[Completed] E: Error executing updater binary in zip - Problem

Hello. I have problem with cyanogenmod 13 ported from MtkRoms. When i try flash rom, latest TWRP 2.8.2.0 give me that error :
apply parsed perms: lsetfilecon of /system/lost+found to u : object_r:system_file:s0 failed: Operation not supported on transport endpoint set_metadata_recursive: some changes failed
E: Error executing updater binary in zip
I try cm 12.1 or Resurrection Remix working fine. "Asserts" in updater-script don't exist.
My phone it is Goclever Insignia 500 here is specs:
720 x 1280 px (5,00") 294 ppi
CPU: MediaTek MT6582 4x1.3GHZ
GPU: ARM Mali-400 MP2 @500 MHz
1GB Ram
Any ideas?

Hello,
Welcome to XDA.
You can edit the updater script so that it recognizes your model number correctly by changing the line in the script for "ro.product".
Edit that line and enter the correct ro.product value for your device model(ro.product can be found in your stock build.prop file if you don't know what it is) then save the file and repackage everything correctly for flashing.
Or you can just remove the ro.product line from the script completely but that can be risky depending on anything you didn't get right in your porting of the ROM.