Database Info

Froyo (2.2) for HUAWEI U8120 [based on AOSP] (under development)

Froyo 2.2.2 port for Huawei U8120.
Maybe it will work on Huawei U8100/U8110 series, but for now it is focused on U8120.
So I dont know what behavior has on U8100 etc.
I must say a big thanks to Tom_G for his awesome work, especially for his froyo port on pulse.Without his work and his posts
on modaco forum, I will not be able to accomplish this.
kalt kaffe's 2.6.29 kernel.
Android 2.2.2 from aosp with some codeaurora changes.
JIT enabled.
Working:
RIL
Audio
GPS
Bluetooth
Wifi
SD card
Sensors
TSCalibration from codeaurora(still the app needs some improvements.For now use a stick or pen when you calibrate the screen)
Not working/bugs:
camera
broken layout on dialer
sdcard cannot be mounted in pc
Its still under development.This is not a finished rom and its not fully tested.
Probably it has problems that I have not yet encountered.So I would not suggest you to try it,
except if you have some experience and you want to help.
I have tried to make it as plain and simple as it gets.No google apps, no bootanimation etc.When all bugs are fixed then I will include them or I will post
my rom.But there are guys that are more expert in rom cooking than me.
Here is a zip with already compiled image files if someone wants to try it and post any bugs/fixes that have found.I have also uploaded here gapps if someone wants them(gmail,market etc)
Code: https://github.com/tas0s
Device tree: https://github.com/tas0s/android_device_huawei_u8120
Try it at your own risk.
Im not responsible for any damage that this may cause.

v.1 initial build

How to build it:
- Install git and gpg (gnupg).
- Download repo - http://source.android.com/source/git-repo.html
$ mkdir android
$ cd android
$ repo init -u https://github.com/tas0s/platform_manifest.git
$ repo sync
- Extract necessary binaries
Some compiled code from the official eclair roms is re-used in froyo. Because some of this code is not opensources I cannot included in the git repository.
The files can be extracted from any u8120 eclair rom.
Place the rom zip in the android directory an rename it to u8120_update.zip
navigate to /device/huawei/u8120:
cd device/huawei/u8120
Then execute from the android directory
$sh device/huawei/u8120/unzip_files.sh
else you can extract them from a working u8120 phone with an eclair rom (check that adb is enabled)
$device/huawei/u8120/extract_files.sh
- Building the system
Once thats done you can start compiling.
Follow the aosp instructions on setting up the build environment. - http://source.android.com/source/download.html
After the environment is setup.
$ cd android
$ source build/envsetup.sh
$ lunch
Select the device u8120.
$ make
I recommend using multiple threads for make if you have a multi core/processor system. By default make will use
1 thread (-j1), set it to use 2*NumberOfCPUsAvailable (so on my dual core -j4). Reducing the number of threads used will reduce the impact on
system performance while the build is running.
The output will be image files in {buildroot}/out/target/product/u8120/. Flash with fastboot.
$ fastboot flash boot out/target/product/u8120/boot.img
$ fastboot flash system out/target/product/u8120/system.img
$ fastboot flash userdata out/target/product/u8120/userdata.img
$ fastboot reboot
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.

for the future

thnx for the gifts up to it tomorrow

A question about camera problem, only video or all features?

bitye said:
A question about camera problem, only video or all features?
Click to expand...
Click to collapse
The camera fails after a few secs.When an image appears in the preview window.
I have read that the the way that android handles camera has changed in froyo.In cyanogen they are using a libcamera2 (just libcamera with a few changes I think so it can work with the new framework).
As you can see in the BoardConfig.mk I have already include the libcamera2 statements but not the lib
When I manage to get some free time I would try the libcamera2.Maybe until the end of the week or sooner.

Ρε πατριδα αξιζει η rom ή οχι;

tas0s said:
For some reason the generated boot.img fails to boot.Maybe I have something wrong about kernel base etc in the BoardConfig.mk.
For now just use the ramdisk.img and the provided kernel and pack it with dsixda's kitchen or with the huawei-u8100 tools that have been posted on the forum.
Then just use fastboot as stated above.
Click to expand...
Click to collapse
There's a little fix using bootbuilder for U8120, see this post:
http://android.modaco.com/content/t...l-r1-bootbuilder-for-pulsemini-alpha-release/
In the 6th reply you can find the info you could need it
Good luck!

Hi can you tell me on wich kernel it runs?
the 2.6.32 or2.6.29?
and if wiifi is completly fixed no crashes sleep works mac adress?
thanks

calibration fixed at this repo?

larissamafia said:
Ρε πατριδα αξιζει η rom ή οχι;
Click to expand...
Click to collapse
Πατριωτάκι δεν είναι για καθημερινή χρήση ακόμα.Γιαυτό δεν έχω βγάλει και έτοιμη rom.

@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.

tas0s said:
@Shiftok:
The calibration is integrated in the framework etc but it has some small issues.
As I say in the first post, it needs improvement.
@Cedric123:
Im using 2.6.29 kernel.The wifi works normally.If I remember right and MAC address.
Click to expand...
Click to collapse
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations

cedric123 said:
ah okey
does this work?
i extract boot.img
put my own zImage in it
repack boot.img
start Phone?
i rly want my own kernel in the ROM with my overclock funtion adn all my +kalt+kaffes optimizations
Click to expand...
Click to collapse
The kernel Im using is kalt kaffe's kernel.So I think that if you just replace the kernel and the kernel modules in /system/lib/modules you will be fine.
Im uploading now a zip with the compiled images.
It has the problems I mention in the first post etc.
Just an observation.If the calibration isnt correct the screen is always on landscape mode Propably because it gets wrong screen dimensions.So if you see something like that, calibrate your screen with the TSCalibration app.
When im done with the camera, I will fix the calibration bugs.

Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps

joilaroi said:
Hi. Im testing your rom.
I cannot mount the sdcard on computer. when i press to activate usb storage it does nothing in computer.
EDIT - i cant install anything because i dont have a file explorer to see the sdcard files. can you please add one or make an .img with the stock apps
Click to expand...
Click to collapse
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).

tas0s said:
Thank you very much for the feedback joilaroi.I have updated the first post with the sdcard bug.I tried myself and you are right.I will try to fix it.
As I know the stock android froyo hasnt any file manager/explorer.Maybe we can get it from cyanogens.
For now, you can do this.Flash the gapps update that I have in the first post,setup market etc and download a file manager from the market(ex.astro file explorer).
Click to expand...
Click to collapse
thanks. its what i am doing. if i find anything i will give feedback
EDIT - Cant install superuser and have permissions. it downloads su-2.3.1-bin-signed.zip to sdcard but its corrupted. maybe its better if its already on .img
Im getting more MFLOPS with 633Mhz in this rom than with 691Mhz with the other kernel. its now with 4.45 MFLOPS vs 4.1MFLOPS. Nice
Do you know where i can find su-2.3.1-bin-signed.zip?

Ubuntu 10.10 x64 under W7 VMWare will be enought for compile?
PC: C2D [email protected],2GHZ 8GB RAM
Laptop: Lenovo T410 i5 vPro 2,4GHz Quad Core 4GB RAM

I think yes

[Q] Haipad M701 and fingerprint reader

Hi ,
I have a Haipad M701 with me,
It is having this config:
4G Memory
Telechips 89xx board
Android 2.1-update1
MID-1.1
Kernel 2.6.29
I am trying to make a external USB fingerprint reader work with it.
The fingerprint device driver source was obtained from the vendor.
To enable the device i need to cross compile the fingerprint drivers.
But before i cud do that, i upgraded the firmware to Android 2.3(gingerbread) which is available in haipad.net(*w/o taking a backup*)(that is kernel 2.6.35).
Now, i am not able to cross-compile driver cos i took the kernel source (for 2.6.29) which telechips publicly opened to public.
So, Right now, i need the old Eclair(2.1,2.6.29) firmware, can anyone provide me that?
If not, is there any other way to achieve the cross-compilation?

In the meantime, i downloaded kernel source from android.com and branched to 2.6.35 which is the kernel version on device.
I compile the kernel and then cross compiled the fingerprint driver.
It compiled w/o any issues.
But when do a 'insmod', i get error:
Code:
mod_usbdpfp: version magic '2.6.35.7+ mod_unload modversions ARMv5 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
What could be the issue here?

You have two problems:
First on the tablet, copy the file /proc/config.gz out on your build pc.
Extract and copy file to .config in the 2.3.35.7 source.
Now you are ready to configure the kernel sources that you compile the vendor driver against.
do make menuconfig;
Fix problems:
1: wrong name of kernel.
Insert "-tcc" in general setup --> Local version.
You seem to have a "+" now. I do not know how you got that. If it is not in the kernel config, look in the Makefile in the root folder. The version is in the top. Make sure the 4th version line just says ".7" - no more.
2. Wrong system type.
You are compiling the modules for an Armv5 instead of Armv6. Go to Arm system type and choose Samsun S3C64XX. That is an Armv6.
The selector might look really strange. If that is the case, scroll to the bottom and scroll back up (now names appear one at a time), until you see the ()amsung S3C64XX.
Configure Makefile for crosscompile.
Now do a make dep; make modules.
Now you can compile the vendor driver against this source and get the correct module. Use modinfo modulename.ko; to see that the name and type corresponds to "'2.6.35.7-tcc mod_unload ARMv6".
I have just done this (for an usb net driver), and the resulting driver crashes the tablet So even if you can get a module build and loaded, it might not work because the system architecture (S3C64XX) is not really correct. In that case we really need the telechips 2.6.35.7 sources to build correct module.
But try it out, and good luck!

Thanks for the suggestion, xdamala.
I will try it out today itself and let you know

@xdamala,
I had to do 'make s3c6400_defconfig'
But, Now i get this error.
Code:
mod_usbdpfp: version magic '2.6.35.7-tcc-g67bb0cf-dirty mod_unload
ARMv6 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
I dont know how the 'g67bb0cf-dirty' gets added.
Each time i edit 'include/config/kernel.release' which contained that text, it automatically is updated on running 'make'.
Any idea??

I am not 100% on how the version string is constructed. But I think it is created from the top 4 lines in Makefile and the string you set in configuration.
I should not be necessary to do that s3c6400_defconfig. It is probaly what changes the string. I might have told you the wrong order of things in my other answer. It is important to set up Makefile first.
Do the steps (in order):
Start with clean 2.6.35.7 kernel code
edit Makefile in kernel root folder
Check version number in top
edit cross compile section to:
ARCH ?= arm
CROSS_COMPILE ?= ../../arm-eabi-4.4.3/bin/arm-eabi-
#or whatever fits your compiler. Note that this android tree gcc 4.4.3 is the one running M701 kernel is compiled with, so I prefer to use the same.
extract tablets /proc/config.gz to .config in root of kernel source (to remove unnecessary modules)
make menuconfig;
set -tcc in local version
choose S3C64XX system type
Exit (Save)
make dep ; make clean ; make modules; #Note you do not actually build the kernel, only modules.
In the Makefile from your driver there probably is a section something like this:
KDIR = /lib/modules/$(CURRENT)/build
edit to point to the folder of your kernel source.
make;
transfer fingerprintdriver.ko to tablet
Cross fingers, throw salt over your shoulder, pray, etc. etc.
insmod fingerprintdriver.ko;

@Xdamala
Code:
mod_usbdpfp: version magic '2.6.35.7-tcc+ mod_unload ARMv6 ' should be '2.6.35.7-tcc mod_unload ARMv6 '
Still the plus seems to be issue.
I checked in the main Makefile there is no '+'.
But in include/generated/utsrelease.h, there is
Code:
#define UTS_RELEASE "2.6.35.7-tcc+"

Well I use a kernel from kernel.org, not from the android tree.
Might be the reason for the "+".
I do not think that it makes any difference in this case.
Try with the kernel.org one. If it works it works, if not we might try to look at that "+"
By the way if all fails you can reinstall 2.1 on the tablet and build against the 2.6.29 kernel released by telechips. It should work.
The downside: 2.1 sucks, and usb in general sucks a lot on M701 2.1.
See my posts here:
http://www.androidtablets.net/forum/groups/11-haipad-m701-m701-r-d129-just-ordered-g10-haipad-m701.html.
In that case go to telechips kernel source:
make tcc8900_defconfig
make menuconfig. Exit + save.
make modules.
Then compile your driver against these sources.
Your driver should then work (this time we use the correct system type), but usb is quite bad on 2.1. So if I was you I would try a lot to make 2.3 work first.
Links:
Telechips kernel. Use Internet explorer to download (FF not working):
https://www.telechips.com/technical_support/kor/opensource/opensource_list.asp
Latest 2.1 firmware from Haipad:
http://u.115.com/file/c4rgup4f

xdamala said:
Latest 2.1 firmware from Haipad:
http://u.115.com/file/c4rgup4f
Click to expand...
Click to collapse
Thanks xdamala, thats what i needed, will check it out and let you know of the result tomm.

I will warn you that 2.1 comes with its own problems when it comes to usb.
Attach the device directly. Do not use a hub.

xdamala,
Method 1: Compile kernel source of 2.6.35.7 from kernel.org - Success
insmod driver.ko installed w/o any errors.
But, it seems i would need a power source for the fingerprint reader.
i dont think currently the Haipad support that mode.
Method 2: Flash(downgrade) m701 to 2.1 and try with the public kernel source which telechips have released - Failure
The FWDN program gives CRC check error while loading tcc8900_mtd.img.
Maybe bcos of corrupt download or the Haipad i have is a 4G memory one.
Which u think wud be?
Even if i accomplish providing power to the fingerprint device, i would need the C++ sample provided by the fingerprint vendor to be cross-compiled.
Otherwise, how can i test if the device works?
How to do that??

Hi
I did not see your post because it now came as page 2.
The tablet should provide some level of power to the reader. If you use the white converter cable that came with the tablet, it should tell the tablet to provide power (USB On The Go, see Wikipedia). It works with memory sticks and even hard drives. But I do not know if it is enough for that reader.
With 2.3 firmware you could use a power hub to give power to reader (still use white converter cable between tablet and hub). Do not use hubs on 2.1.
To check if tablet recognizes reader do this:
adb shell:
#dmesg -c
#insmod driver.ko
#dmesg
--Insert reader in usb
#dmesg
The output of dmesg should tell you how the kernel reacts when driver is loaded and reader inserted.
You can cross compile c++ code using same compiler as for the kernel. But you will have to compile program/libs statically, since android does not have the C++ libraries.
You can probably achieve this by putting a static keyword in a Makefile.
Also you need to direct the gcc to point at the cross compiler.
An other approach is to install Debian on the tablet inside an file image. I have done this. It is very nice. It gives you a complete (non graphical) Linux system. Compiler, libs and all. Also lsusb and other useful tools.
It is much easier to make Linux programs work like that.
But this Debian will run inside chroot, and cannot see the android system.
I used this tutorial:
http://www.saurik.com/id/10
However I used a bit different approach for starting up Debian system (using Debian own rc scripts).
If you can make the Debian Image, I will be happy to provide you with my scripts to manage it.
I do not know why you cannot install 2.1. It was the one you got fro my URL?
I just see now that Haipad has released a brand new 2.3 this night.
Do not attempt to load it. Last one did not work unless you had the very new tablet. I will try this new one tonight.
What is this project with the fingerprint reader? Tell me more.

Thanks xdamala,
Ya if it is possible, i would surely like to have a Debian on the pad.
I am just exploring things on it, so that we can have a external device work on the pads.
Let me check this url and will let you know
http://www.saurik.com/id/10
Click to expand...
Click to collapse
Ya, if you can help through the process, i will gladly accept it
Also, i didnt get any cable with my pad.
That was the first of issues. Had to buy it separately.
I had done the dmesg check as you told, but it didnt give any noticeable output.
The 2.1 firmware link that you gave, throwed a CRC error. what to do?

if you get a crc error on firmware it is probably because its the wrong firmware.
There are several different versions of this tablet so it can be a bit tricky.
This firmware is for a M701-R 4GB HY
There is 2 GB and 4GB versions. You have a 4 GB right.
There is HY and non HY versions (type of nand memory).
There a re with and without remote control. That is not so important.
I think any mix of the above is possible.
How to figure out if you have a HY version:
Insert usb to pc and enable usb storage.
If nan memory is shown as 3,08 GB (I think) it is an HY.
If it shows less (2,7 GB Ithink) it is a non-HY.
Determine your version and we can see if we can find a FirmWare for it.
Anyway I think you should keep your 2.3 for now. It just is better for USB.
What is the filename of the rar file with 2.3 rom you installed, and where did you get it from? (this might help me identify your tablet).
About usb cable. I now understand why you have no power on reader. If you read the wikipedia article about USB OTG (wikipedia) you will understand that the tablet is in slave mode and will not provide power and probably not talk to devices.
Also see here: http://www.maxim-ic.com/app-notes/index.mvp/id/1822
Can you get a memory stick to work?
You need something like this:
http://www.amazon.co.uk/Host-Cable-ARCHOS-Internet-Tablet/dp/B004TJC1IM/ref=sr_1_3?ie=UTF8.
It will short the correct pins in the mini usb plug, telling the tablet to be master and provide power.
It is possible to fix a cable yourself but I will not recommend it:
http://www.youtube.com/watch?v=COkLEJGo6vo&feature=youtu.be
I am a bit surprised that loading the driver produces no output in dmesg.
But if the tablet is not in host mode, it is not surprising that no output comes from inserting the reader. The tablet is not responding to it since it is in slave mode (like connection two usb sticks. Nothing happens).
I can not help you through the Debian. I used the tutorial I already linked.
If you do the same and add my scripts you should be able to make it work.
Alternatively you can get my Debian Image, but it is 1 GB file, and I need to clean out personal stuff and passwords.

Hi xdamala,
Ya, it seems to be a non-HY, cause i have around 1.4G space in nand
The file i downloaded was M701_2.3.rar, which i downloaded from haipad.net
I did buy the cable like u showed in amazon.com link, using that only am connecting the reader to pad.
And No, a memory stick also is not getting detected on that cable.
Attached that cable image.

Hi xdamala,
I have started creating the debian image, can you tell how you use the rc scripts?
Also, were you able to find the 2.1 image for M701 non-HY?
PS: I got the clockword mod recovery image from here http://androtab.info/telechips/firmwares
I used the one marked "Haipad M701 GB ROM 4K"
It worked for me.

Hi
Several things:
1: I think you have an 2GB version (non HY), not a 4G version.
2. It seems like the cable you bought is not correct. It has to be a HOST adapter/cable. Since nothing works with it I think what you have is just a male min-usb to female usb. It is not enough.
3. About Debian image. Which version of Debian are you using?

By the way I found out how to get rid of the "+" when using the Android kernel source. Move the folder .git to git. This will break git usage (unless you move it back). But it removes the "+" in version string.
Using Android kernel source might be better than stock kernel source.

Hi again,
1. Its a 2GB?? Oh but when i followed this link (translated it english)
Code:
http://www.inzipad.com/thread-334-1-1.html
My result was 4096, so i thought its a 4G one.
2. Oh. Then i will try to buy then one u have recommended.
3. I have dropped the step of building a Debian, cause i have a android application running and the input from the usb reader has to be sent to that application. So, I have to make it work natively on Android.

xdamala said:
You have two problems:
First on the tablet, copy the file /proc/config.gz out on your build pc.
Extract and copy file to .config in the 2.3.35.7 source.
Now you are ready to configure the kernel sources that you compile the vendor driver against.
do make menuconfig;
Fix problems:
1: wrong name of kernel.
Insert "-tcc" in general setup --> Local version.
You seem to have a "+" now. I do not know how you got that. If it is not in the kernel config, look in the Makefile in the root folder. The version is in the top. Make sure the 4th version line just says ".7" - no more.
2. Wrong system type.
You are compiling the modules for an Armv5 instead of Armv6. Go to Arm system type and choose Samsun S3C64XX. That is an Armv6.
The selector might look really strange. If that is the case, scroll to the bottom and scroll back up (now names appear one at a time), until you see the ()amsung S3C64XX.
Configure Makefile for crosscompile.
Now do a make dep; make modules.
Now you can compile the vendor driver against this source and get the correct module. Use modinfo modulename.ko; to see that the name and type corresponds to "'2.6.35.7-tcc mod_unload ARMv6".
I have just done this (for an usb net driver), and the resulting driver crashes the tablet So even if you can get a module build and loaded, it might not work because the system architecture (S3C64XX) is not really correct. In that case we really need the telechips 2.6.35.7 sources to build correct module.
But try it out, and good luck!
Click to expand...
Click to collapse
Thsi really works thanks for that

compile google sources with samsung ICS

Hi,
i'm trying to compile google sources version 4.0.4 with samsung sources from opensource samsung
From samsung sources i've only used the platform files. I've done all the steps that are in the platform readme:
How to build Mobule for Platform
- It is only for modules are needed to using Android build system.
- Please check its own install information under its folder for other module.
[Step to build]
1. Get android open source.
: version info - Android gingerbread 4.0.4
( Download site : source android)
2. Copy module that you want to build - to original android open source
If same module exist in android open source, you should replace it. (no overwrite)
# It is possible to build all modules at once.
3. Check module is in 'build\core\user_tags.mk'
If not, you should add your module name in it.
ex1) external\libjpega : Write "libjpega \" into "build\core\user_tags.mk"
ex2) external\libexifa : Write "libexifa \" into "build\core\user_tags.mk"
4. In case of 'external\bluetooth',
you should add following text in 'build\target\board\generic\BoardConfig.mk'
BOARD_HAVE_BLUETOOTH := true
BOARD_HAVE_BLUETOOTH_BCM := true
5. excute build command
./build.sh user
The command user was ./build.sh eng
Before running this command i've installer jdk 6 and follow the steps from android initializing
the ./build.sh eng run with success and after this i've run the make.
Some hours later i've got a new folder "OUT", inside there is a system folder but i've tryed to flash this folder with odin
and no success.
What am i doing wrong?
Thanks.

Trying to build the kernel + modules?
If i understand what your trying to do, Install new kernel and modules?
!!!!!Before you try this, do some research for your device and make sure this is the correct action!!!!!
you are looking for a file called: zImage
It should be in <build path>/arch/arm/boot/
To install the new kernel, you put your device into fastboot
Code: adb reboot-bootloader
Then you can install the new kernel:
Code: fastboot flash zimage /<path to your zImage file>/zImage
Then you can boot your device and manually copy over the modules.
Note: I didn't see in your steps where you mentioned configuring the kernel, are you doing this?

Thanks for your reply.
the kernel i've already compiled like you mentioned and it is ok i've flashed the zImage.
But there is another part that is the platform module that corresponds to the system.
When you have a Rom there are 3 things inside:
- boot.img that has the zImage (kernel)
- meta-inf
- system
i'm changing the code in one file that corresponds to the nfc part and them compile the samsung sources
and google sources to get that system.
after compile the is one folder out that has system.img but i can't flash this .img file the mobile phone gets like a stone :S
All Black!

Please describe the process you are using to flash the system.img.
Have you though about just copying over the modified files?
Also, if you could create a step by step list of your process, maybe we can figure out what's going wrong.

i've compiled the google+samsung sources and this created the system.img.
Then i used Heimdall to choose only system to flash and It didn't work.
i've tryed also to change only the nfc.apk file put it in the app folder tryed to flash the ROM (in this case from Cyanogenmod) and it didn't work.
Thanks.

pec0 said:
i've compiled the google+samsung sources and this created the system.img.
Then i used Heimdall to choose only system to flash and It didn't work.
i've tryed also to change only the nfc.apk file put it in the app folder tryed to flash the ROM (in this case from Cyanogenmod) and it didn't work.
Thanks.
Click to expand...
Click to collapse
have you tried to remove and install your nfc.apk using adb rather than trying to flash the entire rom? I would think all you need to do is mod the kernel, flash the kernel, then copy over any modules and replace the nfc.apk.

Unable to load wifi module for ASUS ROG Phone 1

Specifications:
Phone: ASUS ROG 1
Model Number: ASUS_Z01QD
Android version : 8.1.0
Firmware: WW-15.1630.1907.98
Kernel Version: 4.9.65-perf
I have an ASUS ROG 1 Phone. It came with Android 8.1 and firware version WW-15.1630.1907.98. I took the kernel source code from ASUS site. Source code version: <new user on XDA hence unable to post the src code link.>
Was able to build successfully and flash to the phone. Rooted the phone following to that. The problem is that the wifi wasnt working after flashing the new kernel .
1. I checked the modules loaded lsod, from adb and it didnt show the wil6210.ko loaded.
2. I tried insmod /modprobe wil6210.ko and was constantly getting the following errors:
a. disagrees about version of symbol module_layout android kernel
b. required key not available .
c. No such file or directory.
3. I tried building the kernel with the SIG flags disabled in the .config file and flashed to the phone. Yet ended up getting errors like no such file or directory and required key not available.
Any help will be really appreciated.
@nathanchance

You need to rebuild the Wi-Fi module against the source that you compiled then flash it. Alternatively, you can try building the Wi-Fi source into the kernel image but that is usually broken or you can force the module to load by whitelisting it in kernel/module.c (there are commits floating around that allow this) but it can open up a security vulnerability.

nathanchance said:
You need to rebuild the Wi-Fi module against the source that you compiled then flash it. Alternatively, you can try building the Wi-Fi source into the kernel image but that is usually broken or you can force the module to load by whitelisting it in kernel/module.c (there are commits floating around that allow this) but it can open up a security vulnerability.
Click to expand...
Click to collapse
Thanks for your reply.
The source code I downloaded from the ASUS website, the wifi module code was a part of it. So whille building the kernel the module <wil6210.ko> also got built along with it.
So the wifi module did get built against the same source.

Nethunter Kernel (Immensity Kernel)

*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael

Changelog:
•5/8/20 -> Fixed HID bug

Was waiting for someone to make this! Thanks!
Did you think about adding the drivedroid patch too?
Sent from my K20 Pro using XDA Labs

dr460nf1r3 said:
Was waiting for someone to make this! Thanks!
Did you think about adding the drivedroid patch too?
Click to expand...
Click to collapse
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it

moto-john said:
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it
Click to expand...
Click to collapse
Crazy. Thats pretty much all I wanted since this way the phone can replace usb sticks
Sent from my K20 Pro using XDA Labs

moto-john said:
*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael
Click to expand...
Click to collapse
Sir plz help how to add specific WiFi card firmware plz provide full tutorial

Ralink RT5370 WiFi chipeset ... support...?

Is injection mode also work with internal wifi adaptor?

[email protected] said:
Is injection mode also work with internal wifi adaptor?
Click to expand...
Click to collapse
Unfortunately no. Only monitor mode is supported. If you want injection you have to use am external wifi adapter

swapnilj210f said:
Ralink RT5370 WiFi chipeset ... support...?
Click to expand...
Click to collapse
Have you checked if it's recognised without a specific driver first?

Can miui12 be used？

DKarls said:
Can miui12 be used？
Click to expand...
Click to collapse
It's for AOSP only, so probably no

moto-john said:
It's for AOSP only, so probably no
Click to expand...
Click to collapse
I am on latest Evolution X (https://forum.xda-developers.com/k20-pro/development/rom-evolution-x-elle-t4179163), Magisk 21.1, Busybox 1.31.1, have nethunter store, app and terminal installed and chroot is working. Installed it with:
https://forum.xda-developers.com/k20-pro/how-to/guide-how-to-install-kali-nethunter-t3998623
I flashed your kernel via twrp. But unfortunately HID is not working. I dont know what i should do anymore. Maybe you could help.
Thanks for all your work so far
EDIT: Could it fix with a fresh reboot, great work my friend
---------- Post added at 02:15 AM ---------- Previous post was at 01:42 AM ----------
moto-john said:
I think you can do the same thing from the USB Arsenal section in the Nethunter App
Edit: No, wait. You are right. Will try to fix it
Edit 2: Figured out it works fine as it is. Just booted an iso from it
Click to expand...
Click to collapse
which iso did you test? ive tryed it with a kali linux live system and it didnt work.

moto-john said:
*ONLY FOR AOSP (Verified working on Evolution X)
This is my first Nethunter Kernel build. Based on UtsavTheGreat's Immensity Kernel this port provides all the benefits of the original Kernel with the added Nethunter functionality.
What's tested and working:
• Internal wifi monitor mode (Use the provided custom command in Nethunter app)
• Hid support (In the USB Arsenal section of the Nethunter app select hid USB function, disable adb and then click set USB function)
• External adapter support (TP-LINK TL-WN722N Tested, you may need to manually copy your WiFi card's firmware in "/vendor/firmware" from the provided zip. Also it appears as Wlan2 instead of Wlan1 if that matters)
Installation:
*Assuming you already have Magisk (and the BusyBox Magisk module), Nethunter store, Nethunter app, Kali chroot and Nethunter terminal installed.*
1) Flash the Nethunter_final.zip
2) Enjoy
Big thanks to the creator of Immensity Kernel
Source: https://github.com/Moto-John/kernel_xiaomi_raphael
Click to expand...
Click to collapse
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
You just have to copy the whole ath9k_htc folder in /vendor/firmware. Then it should recognize the firmware

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
Just realized you just couldn't find the vendor folder, If you use the miX file manager you should see it under the root section
https://streamable.com/lixw7d

moto-john said:
Just realized you just couldn't find the vendor folder, If you use the miX file manager you should see it under the root section
https://streamable.com/lixw7d
Click to expand...
Click to collapse
Yeah i could fix it meanwhile thank you
Everthing except drivedroid works like expected now ! do you have any advice? i tried different linux distros as well as different modis in drivedroid. I also tried the build-in image mounter of nethunter. I could not get it to work. You said u could boot. With which settings and distro did you tried it?
greetings chikko

chikko80 said:
Yeah i could fix it meanwhile thank you
Everthing except drivedroid works like expected now ! do you have any advice? i tried different linux distros as well as different modis in drivedroid. I also tried the build-in image mounter of nethunter. I could not get it to work. You said u could boot. With which settings and distro did you tried it?
greetings chikko
Click to expand...
Click to collapse
It definitely is a bit finicky. What I tested was linux mint and the built-in mounter. It definitely didn't want to work at first but after some plugging, unplugging and a few reboots which are seemingly unrelated it then worked pretty consistently every time I tried it

moto-john said:
You just have to copy the whole ath9k_htc folder in /vendor/firmware. Then it should recognize the firmware
Click to expand...
Click to collapse
Where can I find such firmware folder for rtl8812au ? Thanks in advance...

chikko80 said:
Trying to get a AR9271 chipset to work. Cant load modules with modprobe: modprobe: FATAL: Module ath9k_htc not found in directory /lib/modules/4.14.191-iMMENSITY-NethunterBuild-John//9938110c92
That is obviosuly no directory. In which directory do i have to copy the firmware? Which folder do you mean with /vendor/firmware?
Copyied the firmwares to /usr/lib/firmware and /lib/firmware, but still getting from dmesg that it couldnt found a firmware
Click to expand...
Click to collapse
Any idea where I could get such firmware folder for rtl8812au?