Update: Just flash the flashable zip and use the app in my signature!
Download
-------------------- OLD POST BELOW ------------------------
I am trying to get support for USB OTG and NTFS support for FXP kernel too..
Hence I have compiled required modules against the FXP kernel source.
I am posting here to get maximum eyeballs of FXP kernel users.
If you are willing to test, please download and extract the files to /data/local/tmp
Then on terminal (adb shell / terminal emulator / script manager console ), try to insmod these modules like so (one line at a time)
Code:
insmod /data/local/tmp/usb-storage.ko
insmod /data/local/tmp/ntfs.ko
insmod /data/local/tmp/fuse.ko
insmod /data/local/tmp/isofs.ko
lsmod
Please post your output here..
Thanks for your time.
Download
Update: See OP (thanks to juninromualdo for reporting that it works)
Related
because i' m a new user i cannot post links, so, the blue words are thread on the xda-developers forum and the red words are external links.
install any pentest linux distro through chroot method ( [GUIDE] How to LINUX on Rooted TFP )
compile modules for your wifi dongle ( see notes below )
install aircrack-ng suite if the distro you choose not include it.
follow one of the thousands guide on how to crack wifi networks
NOTES:
compiling your driver:
if you have a RTL8187 chipset based wifi dongle follow ( [GUIDE] Using external USB wifi )
get the github.com/AndroidRoot/android_kernel_asus_tf201 ,
configure it properly for your wifi dongle,
Code:
make && make modules
find your module using find:
Code:
find /path/to/kernel -name "*.ko"
then, mount /system in 'rw' mode, copy the module in /system/lib/modules and remount /system in 'ro' mode.
so,
Code:
insmod /path/to/module.ko
that's all!
thanks to:
infernix and biggem001
Hi folks!
one user ask if there is a method for using USB WiFi dongle on TF201, I've a working WG111v3 [RTL8187] which i use for connect when signal is weak, sniffing wifi packets , dump WPA handshakes and make some love ;P.
however i get all this working on TF201 by compile the kernel modules.
because not all users have a chroot with a stock kernel tree, i think to realease a package with all these modules inside.
so, for extract the modules from the package :
tar xzf wifi_ko.tar.gz -C path/to/
or
tar xjf wifi_ko.tar.bz2 -C path/to/
and all you have to do for use the wifi dongle is:
1) open termianl emulator
2) su
3) insmod path/to/module.ko
4) ifconfig wlan1 up
5) wpa_supplicant -i wlan1 -c /path/to/wpa_supplicant.conf -B
6) dhcpcd wlan1
i suppose that the new device is wlan1.
the step 5 and 6 is for connecting to a wireless Access Point, but if you use the dongle for other purposes just skip these.
I make these modules with debug information, so, if you have some problem look at `dmesg | grep "$module" ' output.
for a working wpa_supplicant.conf file take the /data/misc/wifi/wpa_supplicant.conf and remove extra information such as device-id and other android stuff.
Here you are the packages: ( if someone want to upload to another hoster will be better )
https://docs.google.com/open?id=0B0RHupHzEorHWkRheUMxNjRPTGc
https://docs.google.com/open?id=0B0RHupHzEorHZ21NZ3dTNzNHYTQ
Hope this help.
Regeards.
( sorry for my doggish english , i will update it soon )
tux_mind said:
Hi folks!
one user ask if there is a method for using USB WiFi dongle on TF201, I've a working WG111v3 [RTL8187] which i use for connect when signal is weak, sniffing wifi packets , dump WPA handshakes and make some love ;P.
however i get all this working on TF201 by compile the kernel modules.
because not all users have a chroot with a stock kernel tree, i think to realease a package with all these modules inside.
so, for extract the modules from the package :
tar xzf wifi_ko.tar.gz -C path/to/
or
tar xjf wifi_ko.tar.bz2 -C path/to/
and all you have to do for use the wifi dongle is:
1) open termianl emulator
2) su
3) insmod path/to/module.ko
4) ifconfig wlan1 up
5) wpa_supplicant -i wlan1 -c /path/to/wpa_supplicant.conf -B
6) dhcpcd wlan1
i suppose that the new device is wlan1.
the step 5 and 6 is for connecting to a wireless Access Point, but if you use the dongle for other purposes just skip these.
I make these modules with debug information, so, if you have some problem look at `dmesg | grep "$module" ' output.
for a working wpa_supplicant.conf file take the /data/misc/wifi/wpa_supplicant.conf and remove extra information such as device-id and other android stuff.
Click to expand...
Click to collapse
is it possible to use this on Aurora 2??? thanks for the post!
This is great.. But have a question
tux_mind said:
Hi folks!
one user ask if there is a method for using USB WiFi dongle on TF201, I've a working WG111v3 [RTL8187] which i use for connect when signal is weak, sniffing wifi packets , dump WPA handshakes and make some love ;P.
however i get all this working on TF201 by compile the kernel modules.
because not all users have a chroot with a stock kernel tree, i think to realease a package with all these modules inside.
so, for extract the modules from the package :
tar xzf wifi_ko.tar.gz -C path/to/
or
tar xjf wifi_ko.tar.bz2 -C path/to/
and all you have to do for use the wifi dongle is:
1) open termianl emulator
2) su
3) insmod path/to/module.ko
4) ifconfig wlan1 up
5) wpa_supplicant -i wlan1 -c /path/to/wpa_supplicant.conf -B
6) dhcpcd wlan1
i suppose that the new device is wlan1.
the step 5 and 6 is for connecting to a wireless Access Point, but if you use the dongle for other purposes just skip these.
I make these modules with debug information, so, if you have some problem look at `dmesg | grep "$module" ' output.
for a working wpa_supplicant.conf file take the /data/misc/wifi/wpa_supplicant.conf and remove extra information such as device-id and other android stuff.
Hope this help.
Regeards.
( sorry for my doggish english , i will update it soon )
Click to expand...
Click to collapse
What kernel did you use to compile these drivers on?
Cannot insmod
Hello,
could you please answer what kernel version is this working with? Any chance you could re-compile with newest kernel? When trying to ismod, I'm getting error:
insmod: init_module '...path...' failed (No such file or directory)
Before you ask - yes, the path is correct, just init_module returns non-zero.
Thanks for any help,
Martin
Is it possible to have a Atheros AR9271 driver?
I tried all athXX.ko, but "init_module '...path...' failed (No such file or directory)"always happened.
tux_mind said:
Hi folks!
one user ask if there is a method for using USB WiFi dongle on TF201, I've a working WG111v3 [RTL8187] which i use for connect when signal is weak, sniffing wifi packets , dump WPA handshakes and make some love ;P.
however i get all this working on TF201 by compile the kernel modules.
because not all users have a chroot with a stock kernel tree, i think to realease a package with all these modules inside.
Click to expand...
Click to collapse
tennyleaz said:
Is it possible to have a Atheros AR9271 driver?
I tried all athXX.ko, but "init_module '...path...' failed (No such file or directory)"always happened.
Click to expand...
Click to collapse
if i remember fine you need the ath9k or the ath9k_htc module.
btw the main trouble is that the module fails to load the device firmware.
it is probably due to wrong path.
module was probably compiled with "/system/lib/firmware/htc_9271.fw" but you have "/lib/firmware/htc_9271.fw".
please check dmesg immediately after the modprobe, you will see the path used by the module.
i solved by doing a symlink from /system/lib to /lib.
sorry for late replies but i never comes on XDA.
i read now all the previous questions.
the kernel i use is this: https://github.com/tux-mind/tf201-kernel
insmod
Like a previous post I am getting: init_module rtl8192ce.ko failed (no such file or directory)
1) I could not find a path/to so I just made one on the MicroSD and extracted the files.
2) I am executing insmod rtl8192ce.ko from the path/to/ directory
3) To me the issue is that the insmod is trying to write to a location that does not exist.
4) Per a previous post I added a directory "firmware" under system/lib still no luck.
Any help would be appreciated.
Hello,
I've recently bought a MELE A1000 [link], which currently has ICS and Linux kernel version 3.0.8.
But I've come across a problem; my Xbox 360 wired usb joystick isn't working with the MELE.
Research tells me that the module isn't compiled/included in the kernel [link]
This gives me two options, each with it's problems:
1- Re-compile the kernel, including the Xpad module:
I'd have to get the kernel source (either this "generic" kernel, or this Allwinner-specific kernel) then include it in the boot image, which is specific for the MELEA1000 link (check the first comment with the Chinese link to the official image)
Problems with this option
a) I don't know if the generic kernel will work with my device (Are there differences other than included modules?)
b) I can't compile the specific Allwinner kernel for some reason
c) Will the specific boot image work with a custom kernel? I think so.
2- Compile and include the module with insmod
I'd have to get the source of the ffmemless module [Source] and the xpad module [Source], compile them and do insmod to get them working.
Problems with this option
a) I can't seem to compile the modules in the correct version for my kernel (kernel 3.0.8+ #24 PREEMPT, armv71)
b) the precompiled modules I found were for 2.6*
Easiest scenario: compile modules + insmod.
Ideal scenario: get custom kernel, working + mod the rom (this is not within this thread's scope)
Could you give me any links, ideas or keywords to help me continue?
PS: I'm a programmer and I have previously modded/compiled kernels (from Debian's official repositories though)
Thanks
With information I've been reading I got up to this point:
Download the ARM kernel
git clone git://github.com/amery/linux-allwinner.git
Install the necessary libraries / binaries
apt-get install gcc-4.4-arm-linux-gnueabi build-essential u-boot-tools (if u-boot-tools not found, try uboot-mkimage)
Configure
make ARCH=arm sun4i_defconfig
make ARCH=arm xconfig
Check the following modules:
Input device support -> Support for memoryless force-feedback device
Input device support -> Joystick / gamepad
Input device support -> Joystick / gamepad -> X-box gamepad
Compile the modules
make ARCH=arm CROSS_COMPILE=arm-linux-gnueabi- -j3 INSTALL_MOD_PATH=output modules
Then move the xpad.ko module to the MELE and run insmod xpad.ko, but I'm stuck with xpad: disagrees about version of symbol module_layout
I'm guessing this is a compile issue.
I've started a blog in which I'll try to document everything I do in the most detailed way I can.
Cheers
I think easier will be to get already compiled modules for A10 3.0.8+ from some firmware. I got cp210x.ko from "Aurora CM9 Nightly By Feiyu 0803.zip", successfully insmod-ed it into my device, and later added that insmod command to autorun with script manager app. I checked xpad module - it is in this firmware.
Often I find myself really liking a particular kernel for a particular device. The common problem I have found is that no CIFS support is added to the kernel.
I have donated to several kernel devs. I don't expect anything from them, I just wanted to show my appreciation.
However, usually my CIFS inquiries go unnoticed.
I would like to add CIFS support to other people's kernels for my personal use on my device.
I presume I will have to decompile and recompile kernels in the process?
Here is the specific case that I have :
Current setup:
Phone - Verizon Galaxy Note 2
ROM - Beans build 22 (Touchwiz)
Kernel - Perseus 36
I would like to use Imnuts' PBJ kernel. It doesn't support CIFS, whereas Perseus does.
So in theory I could extract the CIFS modules and inject them into PBJ? Any ideas? Any help would be appreciated. I would also be willing to donate to someone willing to build one for me (mods, let me know if that isn't cool to mention. ) I don't have a Linux box or the current means of acquiring a Linux box until early next year. I am curious if this can be done on Windows 7?
xdadevnube said:
Often I find myself really liking a particular kernel for a particular device. The common problem I have found is that no CIFS support is added to the kernel.
I have donated to several kernel devs. I don't expect anything from them, I just wanted to show my appreciation.
However, usually my CIFS inquiries go unnoticed.
I would like to add CIFS support to other people's kernels for my personal use on my device.
I presume I will have to decompile and recompile kernels in the process?
Here is the specific case that I have :
Current setup:
Phone - Verizon Galaxy Note 2
ROM - Beans build 22 (Touchwiz)
Kernel - Perseus 36
I would like to use Imnuts' PBJ kernel. It doesn't support CIFS, whereas Perseus does.
So in theory I could extract the CIFS modules and inject them into PBJ? Any ideas? Any help would be appreciated. I would also be willing to donate to someone willing to build one for me (mods, let me know if that isn't cool to mention. ) I don't have a Linux box or the current means of acquiring a Linux box until early next year. I am curious if this can be done on Windows 7?
Click to expand...
Click to collapse
There may be a simpler method of doing this using insmod and downloadable cifs.ko module rather then taking the developers kernel source and then compiling it to include the cifs.ko module, using the following steps:
1. Make sure you have the latest version of Busybox installed
2. Download this .7z file and extract it's contents the modules you want are md4.ko and cifs.ko (Even though the .zip says Nexus 10 it should still work on your device).
3. Take the md4.ko module and cifs.ko module and place them in your /system/lib/modules folder (Make sure to mount the /system folder as read/write first and if the /system/lib/modules folder doesn't exist make sure to create it and set the proper permissions which should be the same as the /system/lib folder).
4. Now that you have placed the md4.ko and cifs.ko module in the /system/lib/modules folder run the following command:
Code:
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
5. After that completes you should now be able to use the cifs.ko module to perform your desired task.
Let me know if you still have questions I'll be happy to help you out.
shimp208 said:
There may be a simpler method of doing this using insmod and downloadable cifs.ko module rather then taking the developers kernel source and then compiling it to include the cifs.ko module, using the following steps:
1. Make sure you have the latest version of Busybox installed
2. Download this .7z file and extract it's contents the modules you want are md4.ko and cifs.ko (Even though the .zip says Nexus 10 it should still work on your device).
3. Take the md4.ko module and cifs.ko module and place them in your /system/lib/modules folder (Make sure to mount the /system folder as read/write first and if the /system/lib/modules folder doesn't exist make sure to create it and set the proper permissions which should be the same as the /system/lib folder).
4. Now that you have placed the md4.ko and cifs.ko module in the /system/lib/modules folder run the following command:
Code:
insmod /system/lib/modules/md4.ko
insmod /system/lib/modules/cifs.ko
5. After that completes you should now be able to use the cifs.ko module to perform your desired task.
Let me know if you still have questions I'll be happy to help you out.
Click to expand...
Click to collapse
I'm trying to do this on my Nexus 10 with stock 5.1.1 rooted and busyboxed but i get the following error when attempting to insmount the modules:
255|[email protected]:/ # insmod /system/lib/modules/md4.ko
insmod: init_module '/system/lib/modules/md4.ko' failed (function not implemented)
Click to expand...
Click to collapse
modules folder and files are chmod 777, btw.
Did you ever find a solution to this? I'm stuck at the same error message.
Hello, i'm trying to add cifs.ko kernel's module to my rooted (with Magisk) Redmi Note 9 Pro (Joyeuse Global).
On my Ubuntu computer, i've cloned smb3-cifs-linux-stable-backports (linux 4.14, the same kernel version as my phone run) and compiled the cifs.ko module using
Code:
make -C . M=fs/cifs ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu-
The kernel module compiled successfully, then I've created a Magisk module which load into /vendor/lib/modules the compiled cifs.ko, but I get
Code:
insmod: failed to load cifs.ko: Required key not available
, but my compiled kernel module isn't signed and i've checked a factory kernel module : isn't signed too.
I don't know what i've done wrong, if someone can tells me how to do and how.
Thanks
could you resolve this? I want to add cifs in the same kernel (v4.14.180). do you have the cifs.ko file? thank you!