Database Develop

tun.ko for NEXUS ONE available?

as I am behind the GFW of CN I am eager to get openvpn to work (trying with TunnelDroid, with vpn binaries of WITOPIA...
unfortunately i can't get the connection to work, and apparently it is because of the lacking tun.ko
I took the only tun.ko I can find online (vpn connnections, for DROID...), but apparently the current Nexus One kernel does not support.
Does anybody have a tun.ko file that works on Nexus One?
thanks....

I have the exact same problem.......I need a tun.ko to start using witopia to get through the stupid ISP block on google Voice !!
So if anyone has any working tun.ko PLEASE PLEASE help us out !!

I got it !!
Finally......I managed to extract the tun.ko from Modaco's latest build, so credit goes to Modaco for this, I just extracted it for those who like to stick to Stock Roms (like myself for now).
I tested it and it works

How do you guys like openvpn on android? is it pretty stable? Has anyone tried using Access Server?

Are you sure you're running the stock OS?
I am still getting those messages:
insmod: init_module 'tun.ko' failed (Exec format error)
and in dmesg:
tun: version magic '2.6.29.6-cm-teknologist-0.1 preempt mod_unload ARMv7 ' should be '2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7 '

@chirayu : Well, I dont like it so much right since it still needs ALOT of work. Its lacking ALOT of things right now.
@sjakub : Yep, im running the latest ERE36 update. But yea its a stock image.
I didnt see any of the errors you mentioned. I got differnet errors while I was trying it with Witopia, which didnt really work out, but it doesnt seem like a tun driver issue, it was something about an encryption key not available, still working on that.

I have ERE27, that could be why. Where did you get that update from?
Can you get some other module from that phone (like bcm4329.ko) and look for 'vermagic' string inside?

Also, how did you extract tun.ko from that build? Maybe it's possible to extract one from the ERE27-based build?

sjakub said:
Also, how did you extract tun.ko from that build? Maybe it's possible to extract one from the ERE27-based build?
Click to expand...
Click to collapse
Well, the tun.ko is tested and works fine on ERE27 and ERE36 updates so that shouldnt be the problem.
As for the other files, like bcm4329.ko . Why would you need that ? It should be there by default ? as far as i know that module is responsible for certain wireless activities, I do have that file with me if you need it.
As to how i extracted, its simple.....I made a NAND backup of my stock image then flashed Modaco's latest update including the tecknologist kernel which supported tunneling and therefore included the tun.ko. Copied the file to the sdcard, then restored the backup and copied the files to /system/lib/modules

I don't NEED that module.
I would like to know what is the value of "vermagic" inside.
This is the string that describes the version of the kernel used.
Now, if it's something like '2.6.29-01117-g4bc62c2' and the one in the tun.ko you posted is '2.6.29.6-cm-teknologist-0.1' it means that you're somehow able to load module that has a different vermagic than a kernel. If the vermagic in bcm4329.ko is '2.6.29.6-cm-teknologist-0.1' it means that you have a different version of the kernel (and not the stock one). I have no idea why it would be working with ERE27 in that case, unless it was modified ERE27, not the stock one. Or, you were able to load an incompatible module somehow. In that case I would start investigating how to do that with my kernel as well

Hm, or you could check you phone's info:
Could you, on your phone, go to "Settings->About phone" and check what it says under "Kernel version"?
Thanks!

Finaly! I figured out how to build tun.ko module for the stock kernel.
If anybody wants to repeat that:
* I have Android OpenSource installed in /opt/android
* In /opt/android I did: git clone git://android.git.kernel.org/kernel/msm.git kernel-nexus
* In kernel-nexus I did:
- git checkout -b origin/android-msm-2.6.29-nexusone
- git checkout HEAD^
(The last operation reverses one revision, I needed a previous revision from the tree. Different revisions generate modules with different vermagic values)
(Actually, instead of previous two this should work as well - it should checkout the correct revision: git checkout 4bc62c230b2942bea72c3b5258e3e4f1d6cb534b )
- make ARCH=arm CROSS_COMPILE=/opt/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- distclean
- adb pull /proc/config.gz
- gunzip config.gz
- mv config .config
- Edited .config: changed "# CONFIG_TUN is not set" to: "CONFIG_TUN=m"
- make ARCH=arm CROSS_COMPILE=/opt/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- modules
- The driver ends up in: drivers/net/tun.ko
- You can verify if it is going to match the kernel by running:
+ strings drivers/net/tun.ko | grep 2.6.29
+ It should produce "vermagic=2.6.29-01117-g4bc62c2 preempt mod_unload ARMv7"
+ The "2.6.29-01117-g4bc62c2" should be the same as the "Kernel version" in "Settings->About phone" on your phone.
* Now you can upload the module to your phone. I did:
- adb shell mount -o remount,rw /dev/block/mtdblock3 /system
- adb push drivers/net/tun.ko /system/lib/modules/
- adb shell mount -o remount,ro /dev/block/mtdblock3 /system
- And you can use adb shell, enter /system/lib/modules and run: insmod tun.ko
- It should work
The module is attached.

hey Sjakub..
I have tried using your module and I got the same thing like with the one i extracted from Modaco's mod. The tunnel droid gets stuck at "Connecting" any ideas?
Thanks again for all your work mate appreciate it !

Cyanogen Roms have built-in openvpn support. I don't have any problem using Tunneldroid on CM 5.0.4.1. I got the tun.ko error only when I was on the stock ROM. I'm also behind the GFW. Witopia does the trick for me.

thank you sjakub~i used to use your tun.ko working very well with tunneldroid.but after i update the kernel that supports tethering.the tun.ko doesn't work... the new kernel version is:2.6.29-gad36b87-dirty...

The tun.ko module has to be compatible with the kernel you have. Where did you get the kernel from? You need to find a source of exactly that kernel version and compile tun.ko yourself.

sjakub said:
The tun.ko module has to be compatible with the kernel you have. Where did you get the kernel from? You need to find a source of exactly that kernel version and compile tun.ko yourself.
Click to expand...
Click to collapse
i download the kernel for my nexus one from here ——code.google.com/p/android-wifi-tether/
and i follow the steps in the site to flash my rom :code.google.com/p/android-wifi-tether/wiki/NexusOneKernelUpdate
finally...i'm not able to use the previous workable tun.ko which you built...and i'm afraid that i was too amateur to complie tun.ko myself even though you have already list out the compiling steps...

Try asking authors of the wifi-tether for that module. That's probably the easiest way

sjakub said:
Try asking authors of the wifi-tether for that module. That's probably the easiest way
Click to expand...
Click to collapse
okay~i manage to browse that source in google code,though,i can't found tun.ko module.or maybe i will flash cyanogen rom which consist of all the necessary things

anyone brewing a tun.ko for nexus one froyo stock kernel. I don't see aosp code to build right now.

Compiling code for 2.6.27

I'm not sure where to start on this one... I have some C code I want to compile for the kernel, but of course, there is no ability to install gcc on an unrooted phone.
Cygwin seems to compile code into EXEs, but I need to build it as a linux binary. Help?

building CM 10.x from source and some questions

Hi, I tried to build cm10.1 and 10.2 from source and partially succeeeded.
I followed guide here http://wiki.cyanogenmod.org/w/Build_for_ovation
The guide is for 10.2, but for 10.1 it was fortunately enough to replace version number in
Code:
repo init -u git://github.com/CyanogenMod/android.git -b cm-10.2
I hit some issues with pulling proprietary files. First I did it on server far far away so adb pull was not an option. I chose to wget and unpack matching verygreen's binary build to 'system' folder and then simply replaced "adb pull /system ..." with "cp system ..." in extract-files.sh. This sort of worked but many files were not found. Most were elsewhere, two were not found at all. Here is a diff
Code:
diff --git a/proprietary-files.txt b/proprietary-files.txt
index 83304b5..c779f18 100644
--- a/proprietary-files.txt
+++ b/proprietary-files.txt
@@ -30,16 +30,16 @@ lib/libion.so
# Firmware
vendor/firmware/smc_pa.ift
vendor/firmware/ducati-m3.bin
-vendor/firmware/wl127x-fw-4-plt.bin
-vendor/firmware/wl1271-nvs.bin
-vendor/firmware/TIInit_7.6.15.bts
-vendor/firmware/wl127x-fw-4-mr.bin
-vendor/firmware/ini_files/RFMD_D_E5.ini
-vendor/firmware/ini_files/TQS_S_2.6.ini
-vendor/firmware/ini_files/RFMD_S_3.5.ini
-vendor/firmware/ini_files/TQS_D_1.0.ini
-vendor/firmware/ini_files/TQS_D_1.7.ini
-vendor/firmware/ini_files/TQS_S_2.5.ini
-vendor/firmware/wl1271-nvs_127x.bin
-vendor/firmware/wl127x-fw-4-sr.bin
+etc/firmware/TIInit_7.6.15.bts
+etc/firmware/ti-connectivity/wl127x-fw-4-plt.bin
+etc/firmware/ti-connectivity/wl1271-nvs.bin.orig
+etc/firmware/ti-connectivity/wl127x-fw-4-mr.bin
+etc/firmware/ti-connectivity/ini_files/RFMD_D_E5.ini
+etc/firmware/ti-connectivity/ini_files/TQS_S_2.6.ini
+etc/firmware/ti-connectivity/ini_files/RFMD_S_3.5.ini
+etc/firmware/ti-connectivity/ini_files/TQS_D_1.0.ini
+etc/firmware/ti-connectivity/ini_files/TQS_D_1.7.ini
+etc/firmware/ti-connectivity/ini_files/TQS_S_2.5.ini
+#etc/firmware/ti-connectivity/wl1271-nvs_127x.bin
+etc/firmware/ti-connectivity/wl127x-fw-4-sr.bin
After this change the build works and I end up with basic flashable zip file, great
Now the questions:
1. How to build the "sdcard" variant? I guess there is at least a different fstab but maybe there are more changes needed?
2. How to modify linux kernel configuration? I'd like to compile in at least few usb gamepad drivers. Will kernel modules be automatically included in system image?
3. how to build specific stable version like CM-10.1.3 instead of current one?
Thanks for answers and big thanks to all people who made building from source possible.

fanoush said:
I hit some issues with pulling proprietary files. First I did it on server far far away so adb pull was not an option. I chose to wget and unpack matching verygreen's binary build to 'system' folder and then simply replaced "adb pull /system ..." with "cp system ..." in extract-files.sh. This sort of worked but many files were not found. Most were elsewhere, two were not found at all.
Click to expand...
Click to collapse
You can just use TheMuppets repo for prop files -- that's what CM uses as well. https://github.com/TheMuppets/proprietary_vendor_bn/tree/cm-10.2
fanoush said:
1. How to build the "sdcard" variant? I guess there is at least a different fstab but maybe there are more changes needed?
2. How to modify linux kernel configuration? I'd like to compile in at least few usb gamepad drivers. Will kernel modules be automatically included in system image?
3. how to build specific stable version like CM-10.1.3 instead of current one?
Click to expand...
Click to collapse
1. Sorry, I've never looked into this.
2. The kernel sources are pulled from android_kernel_bn_omap, and go into kernel/bn/omap. You can fork or patch this depending on if you want to use git or not. I strongly would recommend forking this on github and committing your changes for your own reference.
In addition, the kernel configs (including sdcard) are at kernel/bn/omap/arch/arm/configs/, and you need to edit the appropriate config file as well to enable any new features you patch into the kernel source.
3. You can use "repo forall -c git checkout tag_name" to sync the repos with a specific release tag (in this case the tag you want is "cm-10.1.3").

jisoo said:
You can just use TheMuppets repo for prop files -- that's what CM uses as well. https://github.com/TheMuppets/proprietary_vendor_bn/tree/cm-10.2
Click to expand...
Click to collapse
Thanks, this worked. I have created file .repo/local_manifests/muppets_bn_manifest.xml with
Code:
<?xml version="1.0" encoding="UTF-8"?>
<manifest>
<project name="TheMuppets/proprietary_vendor_bn.git" path="vendor/bn" remote="github" revision="cm-10.1"/>
</manifest>
and it worked.
jisoo said:
the kernel configs (including sdcard) are at kernel/bn/omap/arch/arm/configs/, and you need to edit the appropriate config file as well to enable any new features you patch into the kernel source.
Click to expand...
Click to collapse
Thanks. Found out kernel config name is probably defined in device/bn/ovation/BoardConfig.mk as
Code:
TARGET_KERNEL_CONFIG := cyanogenmod_ovation_green_defconfig
so I can probablymake my own kernel config and change it there
So the last thing left is the config for sdcard version. I wonder how verygreen builds it (probably from same source tree as emmc version?) and how the different configuration is switched when building both versions.

fanoush said:
Found out kernel config name is probably defined in device/bn/ovation/BoardConfig.mk as
Code:
TARGET_KERNEL_CONFIG := cyanogenmod_ovation_green_defconfig
so I can probablymake my own kernel config and change it there
So the last thing left is the config for sdcard version. I wonder how verygreen builds it (probably from same source tree as emmc version?) and how the different configuration is switched when building both versions.
Click to expand...
Click to collapse
In the same folder, there's also the cyanogenmod_ovation_green_sdcard_defconfig kernel config which has some USB and booting options changed from the emmc config.
I think you need to at least modify the kernel config and fstab, but I think the installation/set-up script also needs to be quite different. I would suggest you ping bokbokan a message (he's done a SD version of CM-10.1 here) to see what else is needed.
I suspect it's more than a trivial amount of changes...

Booting .4.5.2 Kernel (Apollo - Old Bootloader)

@Cpasjuste,
In the image headers I noticed that the ramdisk and tag addresses have changed.
ramdisk addr: 0x02000000 -> 0x01000000
tags addr: 0x01e00000 -> 0x00000100
Please correct me if I'm wrong...
The bootloader (lk) loads the ramdisk and kernel tags (device tree) at these physical RAM locations.

@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- The DT syntax seems to have changed (arch/arm/boot/dts/thor.dtsi), this may be the problem for our old bootloader ?!
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt, kernels and bootloaders are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
I asked to hashcode for that but I guess he is very busy.

Cpasjuste said:
@ggow
Yes i saw that but it have no effect. I'm focusing on the .dt part because I found a few things :
- The DT images can correctly be extracted with a tool named "mkboot".
- When using the DT image from kk kernel, the bootloader complains about DT not found (fastboot boot boot.img)
- Opened both DT image in hex editor, noticed some differences in the headers. I switched kk DT headers by jb DT headers, the bootloader don't complain
anymore so I guess it can now found it. But the kernel will just hang immediately.
- Now I'd like to use compiled dt from kk kernel, but has you may have noticed the DT compilation fail about "fb_mem" not declared. I think I need to fix this, then maybe use old jb tools ( $KERNEL_OUT/scripts/dtc/dtc -p 2048 -O dtb -o thor-v1.dtb arch/arm/boot/dts/thor-v1.dts) to compile them, unlike kk kernel which now compile them with the kernel.
From what iv read dt and kernels are linked together, so there is also maybe some changes to be done in the dt sources. But this start to be out of my knowledge.
Click to expand...
Click to collapse
I noticed the "fb_mem" not declared error and couldn't find any reference to it anywhere. I switched the dt.img header also and got to the point where the kernel was not dumping out to fastboot any more, but instead bootloops.
I have messaged amazon once again to post the source code for apollo and thor for update .4.1.1 .

Hehe we are at the same point it seems (nowhere)

Today I did spent a lot of time on this. After a lot of dt hacks/test I'm unable to resolve this problem for now. So I had another idea and started to port kexec hardboot for our device. I'm at the point where is successfully load kernel and DT (something is different for our device, the msm_id struct, which I solved) and reboot but will hang or restart just after a few seconds of the reboot. I think I'm almost there but I may have some problem to find correct memory addresses which are not overwritten by the boot loader. Let me know if you want to take a look I'll upload patches. But well even if we succeed we may still encounter the same DT problem.
In the "dt.img" there is 3 dtb files in, which are scanned by the bootloader for the correct hw revision. I did find that our device use the "thor-v2-apq.dts/.dtb" dt file for booting (not the thor-v1 nor v2) which correspond to our hardware revision. This is in correlation to the 4.1 kernel which only compile this dtb.
When loading the 4.1 dt image with kexec I was able to debug and see that while the header of each dtb parts have changed, there's still the correct hw revision included (of course!?). This one is correctly loaded by kexec and so probably by the bootloader (but in the new dt.img we still need to modify the img header for our bootloader to find it). By the way, I wonder how this final dt.img is built !?
I just don't know yet what is the thor.dtsi file in the 4.1 kernel, the one missing the fb_mem def. This is not included in the dt.img so should it be modified to match our old thor-v2-apq.dts instead the new one ?
By the way manual compilation (and decompilation!) does work with the dtc utility (apt-get install device-tree-compiler).

Yes, upload the the patches for kexec. Definitely interested in taking a look. I have configured a kernel last night with kexec config enabled (great minds think alike)
This DT problem is troubling me. Perhaps not everything is included in this kernel for Apollo or Thor to boot.
I received a reply from amazon, they said they will post the missing source for the last 3 updates very soon (no idea of time frame).
Sent from my Full Android on C6603 using Tapatalk

I don't think the sources are the problem as we have it on stock 4.1 boot.img. I'll upload the patches tomorrow with a little briefing.

@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.

Cpasjuste said:
@ggow : 4.1.1 kernel booted (not from sources. As you noted this sources may be incomplete).
I'll post the kernel this night, with a clean 4.1.1 system if i have the time.
Click to expand...
Click to collapse
Good News, well done

ggow said:
Good News, well done
Click to expand...
Click to collapse
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img

Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app

cdub50 said:
Good work looking forward to testing it out.
Sent from my Optimus G using XDA Free mobile app
Click to expand...
Click to collapse
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !

Cpasjuste said:
This is a wip for you. You need to wait for a root exploit on 4.1.1 for using it !
Click to expand...
Click to collapse
Ah gotcha. Hopefully that will be sooner than later.
Sent from my Optimus G using XDA Free mobile app

Cpasjuste said:
Finally, sorry for the delay So here is the modded 4.1.1 boot image. In short : binary extract correct dts from 4.1.1 stock dt image and happend it to 4.1.1 stock zImage.
Didn't had the time to finish my gapps rom based on 4.1.1 but should not be too long
http://android.mydedibox.fr/hdx/boot-4.1.1.img
Click to expand...
Click to collapse
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...

ggow said:
Thanks for that
Which number dts is the correct one (there are 3). I need to do the same for Apollo...
Click to expand...
Click to collapse
From what i remember this is the third (which is thor-v2-apq.dtb)

Well, cm is still a ***** to get ported :/, tree days on it without success.
Else the new odex framework is not deodexable by baksmali. If you ever have a solution let me know (You may not need that but I'm in a dead end).

So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).

Cpasjuste said:
So @ggow, did you made some progress on resurecting your device ?
In the meantime i did get msm aosp up and running ! (but no wifi, qcmediaplayer not found for no apparernt reason which prevent some audio to work, slow ui transitions and probably more stuff to fix).
Click to expand...
Click to collapse
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk

ggow said:
So far no...
What I think could have happenned is the synaptic dsx firmware and configuration has been updated or corrupted by the new kernel.
I am in the process trying to figure out exactly what I need to do to fix it. I have found a utility which can be used to force an update to an older version of synaptic firmware.
I might have to write a utility to extract the firmware and configuration area from a working device.
Will let you know what I find.
Sent from my Kindle Fire HDX 7 using Tapatalk
Click to expand...
Click to collapse
Yep i was just going to talk you about this. I'm trying to fix wifi on the aosp build and discovered this lines in dmesg :
<6>[ 6.404807] synaptics_dsx_i2c 2-0020: fwu_start_reflash: Requesting firmware image Synaptics.3.B.thor.img
<6>[ 6.414184] synaptics_dsx_i2c 2-0020: Firwmare size 45056, config size 512
<6>[ 6.421216] synaptics_dsx_i2c 2-0020: Device firmware id 1509905.
<6>[ 6.427045] synaptics_dsx_i2c 2-0020: Device config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.434233] synaptics_dsx_i2c 2-0020: .img config ID 0x13, 0x07, 0x00, 0x02
<6>[ 6.441127] synaptics_dsx_i2c 2-0020: Nothing needs to be updated
<6>[ 6.447230] synaptics_dsx_i2c 2-0020: fwu_start_reflash: No need to do reflash.
Click to expand...
Click to collapse

Thank you for your work! I hope your problem will spill over into different firmware for our device. With the support of LTE I hope.

I9300 Kexec-Hardboot

Hello! So I've been trying to Kexec-Hardboot another custom kernel. I'm using Agni Kernel which has Kexec-Hardboot implemented. I patched the guest kernel to copy atags to be able to make it a guest kernel. Everytime I try to execute the guest kernel, the phone turns off for about 30 seconds and then boots to the ptevious kernel.
kexec --load-hardboot zImage --initrd=ramdisk --mem-min=0x44000000 --command-line=" androidboot.selinux=permissive buildvariant=userdebug"
kexec -e
Tried different --mem-min values but still the same. Tried cat'ing /proc/cmdline for --command-line. I even Tried recompiling Agni and enabling ram_console and copy atags. Still the same. If anyone could please help me here. Thanks
EDIT: Managed to implement kexec on TWRP but still the same. last_kmsg shows no trace of kexec

Post it in Q&A section not here

Sorry I didn't know there was a discussion section for this. I can't move this thread.