This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Gizmoe said:
This is a question for someone with really good knowledge of system files within android. I have taken the 3.06.405.1 RUU and cooked it into a rom to use for myself using the dsixda kitchen. Everything works just fine except wifi. I cannot get past the obtaining IP adress when trying to connect to wifi. I have searched through the phone trying to find the files that control wifi and am stumped. Which files would i need to extract from stock rom to make the wifi obtain an IP. I know my router is good because my wife is using it with no issues. When i cooked the rom i had to change the boot.img to one from a rom that i know can boot because the one in the ruu would not get past splash screen. Do i need to try a different boot.img or is there files that i need to replace that are inspire 4g specific.
I have already tried kernels from VU, Klquicksall and lordmod. Any help on this matter would be greatly appreciated.
Click to expand...
Click to collapse
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Gene Poole said:
The wifi is based on the Broadcom 4329 chipset and the bcm4329.ko kernel module is required for wifi operation (it is stored in the /system/lib/modules/ directory on the phone). The module should match the kernel and should have been compiled with the kernel build. You don't mention what kernel you're using so I can't comment further. bcm4329.ko from a different kernel build may work, but with varying degrees of success.
Click to expand...
Click to collapse
Thank you very much gene I appreciate it. I did replace that file but did not make sure it matched the kernel. I will give it another shot. And for others that read this I still am using Bindroid as my daily I'm just trying to figure out how to build roms too. I thank all the devs for the great tools available to do so, mainly the kitchen.
Related
I've got Ubuntu up and running and I'm willing to rebuild the kernel to enable tethering.
Problem 1 is that I have not received my Magic yet
Problem 2 is that I have no idea what I need to do
So who wants to help?
sammypwns said:
I've got Ubuntu up and running and I'm willing to rebuild the kernel to enable tethering.
Problem 1 is that I have not received my Magic yet
Problem 2 is that I have no idea what I need to do
So who wants to help?
Click to expand...
Click to collapse
I'll help. I've got tethering working using Azilink, but it would be nice to get it working using the Hero's built-in tethering option. Here's my post at ubuntuforums.org:
http://ubuntuforums.org/showthread.php?t=1202059
So are you rebuilding the kernel to get the iptables? I can't even get to make Ubuntu see the Magic as a communications device now.
It took me about 15 minutes to get the SDK up and running on Ubuntu 32 bit but I don't know where to find the source for the kernel or evena copy of the kernel itself. Once I have those it shouldn't take more than 5 minutes to compile the kernel including iptables. In fact if I had the source to a kernel that does allow tethering it would be even faster because I could just drag and drop what I need into the build directory. I haven't seen the source but I think that the HTC branded kernel only differs by a few files and it might even be easier to move the HTC files to the Google kernel. Need more help and testers.
sammypwns said:
It took me about 15 minutes to get the SDK up and running on Ubuntu 32 bit but I don't know where to find the source for the kernel or evena copy of the kernel itself. Once I have those it shouldn't take more than 5 minutes to compile the kernel including iptables. In fact if I had the source to a kernel that does allow tethering it would be even faster because I could just drag and drop what I need into the build directory. I haven't seen the source but I think that the HTC branded kernel only differs by a few files and it might even be easier to move the HTC files to the Google kernel. Need more help and testers.
Click to expand...
Click to collapse
Do you have the port tools? They allow you to unpack the boot.img. I'll upload the port tools for you:
http://www.mediafire.com/?fnzdtnj4gmy
Just put all of the tools in your /android/tools folder.
To unpack the boot.img, you just have to run this command:
unpack-H.pl boot.img
Click to expand...
Click to collapse
That's it. Good-luck. Messing around with the kernel is way above my know-how.
@hotweiss thanks a bunch
This guide shows you how to push the IP tables on the Magic:
http://android-unleashed.com/2008/1...d-g1-phone-with-iptables-no-proxy-needed.html
do I just need to incorprate the iptables binary with the kernel when I build it. Again I haven't seen either kernel to compare them.
sammypwns said:
do I just need to incorprate the iptables binary with the kernel when I build it. Again I haven't seen either kernel to compare them.
Click to expand...
Click to collapse
Haven't done it myself yet, but it looks like it's just an issue of following a few steps. The biggest problem right now is to make Ubuntu see the Magic as a modem.
again I don't have my magic yet so I can't comment on that but if anyone has a google branded version could you please check and see if you can get ubuntu to recognize it as a modem. if so then we know that it has only to do with the kernel itself.
EDIT: Also I can't get unpack-H.pl to work, i keep getting bash: /home/sammy/android-sdk-linux_x86-1.5_r2/tools/unpack-H.pl: Permission denied
sammypwns said:
again I don't have my magic yet so I can't comment on that but if anyone has a google branded version could you please check and see if you can get ubuntu to recognize it as a modem. if so then we know that it has only to do with the kernel itself.
EDIT: Also I can't get unpack-H.pl to work, i keep getting bash: /home/sammy/android-sdk-linux_x86-1.5_r2/tools/unpack-H.pl: Permission denied
Click to expand...
Click to collapse
right click on unpack-H.pl, set the permissions, and make it executable.
hotweiss said:
This guide shows you how to push the IP tables on the Magic:
http://android-unleashed.com/2008/1...d-g1-phone-with-iptables-no-proxy-needed.html
Click to expand...
Click to collapse
well you dint need go all the steps , just pushing iptables and insmod should be enough if you use wifi tethering app. but is the kernel in htc magic and g1 the same , do they run the same binary ?
i will check it but dont know if it works.
Edit :
No ipfilter in the kernel = not working
the binary itself works just fine (strange)
its because the kernel is missing netfilter too. there are actually 3 things we require for this to work. we need to build netfilter as a module, build iptables as a module and then include the iptables binary so that other programs can talk to it. unfortunately i don't have a magic but if you could pm me your im screen names we could do this faster
sammypwns said:
its because the kernel is missing netfilter too. there are actually 3 things we require for this to work. we need to build netfilter as a module, build iptables as a module and then include the iptables binary so that other programs can talk to it. unfortunately i don't have a magic but if you could pm me your im screen names we could do this faster
Click to expand...
Click to collapse
Things will be complicated by the fact that the Rogers and T-Mobile Magic's are different. I'm still confident that we'll work it out.
hotweiss the google branded ion does not require these modules
Again please forgive me if the is noobish but can't find the answered anywhere. I have tried yo flash a few different versions using daz tutorial with replacing the boot.ing file so that swap and apps2sd would work. Ever since then any version of jac hero I use with that boot.ing the WiFi won't turn on. Have tried 3 different wlan.ko files and that didn't work. If I go back to the old boot.img like fatal1ty with enhancements the WiFi works. But I have seenothers get it working on a 32B device. Which mine is the Google io phone. Does anyone know if I am just grabbing a wrong boot.img do I need a different wlan.ko any help would be appreciated. Thank you.
It is really pissing me off that i can't get wifi to work properly when porting Dream roms over to the 32A. I have changed all drivers, a heap of wifi and init files but still nothing.....
We have rebuilt the boot image with the correct kernel, replaced wlan driver, renamed trout files etc......
Wifi will start up and find the networks nearby but will not connect to any.
Anyone have any suggestions? I am hoping there is one little file we are missing that a simple transfer of that file will get it working.....
Radix and I have tried a bit as well as a few others. He might be able to pop in and say exactly what he has done with what files (I am at work so can't remember everything i have tried to change)....
IDEAS?
****edit*** just noticed this tweet from haykuro: "rogers peeps: you may be able to flash all sorts of craziness soon. "
I have had no problem getting WiFi to work on any of the Dream-based ROMS. As long as the wlan.ko matches whatever kernel you are using (from whatever boot.img you are using) it seems to work as normal.
I'd imagine you will never have much success using a different wlan.ko and kernel combination than was compiled for.
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
MontAlbert said:
is that with 32A or 32B? Interesting on the matching thing- i think we tried that- we used Amon_RAs kernel and wlan.ko.....
Would we have to use the entire boot image and not just the kernel?
Click to expand...
Click to collapse
I use the entire boot.img (I know this is lazy and loses alot of the cool features of the ROM) and then the corresponding wlan.ko from whatever image the ROM came.
ok. I was trying to keep as much of the original intact as possible.....
I've tried replacing the entire boot.img - makes no difference - wifi will load, but not actually get an IP with any of the newer roms (like cyanogen's or JACxROM).
I suspect it's interacting with some of the /system/bin/ files and something has changed in that department that makes it incompatible with our kernel/wlan.ko.
I've tried replacing wpa_supplicant/wpa_cli/wlan_loader and no luck.
Hi guys,
Over at the HTC Hero forum I have been developing a kitchen to help ordinary people learn how to build their own ROM. It allows you to do basic things such as rooting a shipped ROM, adding apps2sd, modifying the task killer memory threshold, etc.
The appropriate settings are now in place to make it work for the Dream.
Here is the link to the kitchen:
http://forum.xda-developers.com/showthread.php?t=633246
Before you flash your new custom ROM made from this kitchen, please make a Nandroid backup first of your existing ROM!
Thank you, and enjoy!
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
carz12 said:
Working so far on Ubuntu, figures I just learned how to use git and make my own EBI1 kernels 2 days ago, thanks for this. I'll let you know once I flash a rom how it goes.
Click to expand...
Click to collapse
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
dsixda said:
Cool, thanks. I am most concerned about how the wireless tethering option will work on the Dream because it requires a kernel fix for Android 1.5 and 1.6. The kitchen is supposed to do that automatically but it will replace your existing kernel.
BTW looks like you are from my home town of Edmonton!
Click to expand...
Click to collapse
I may need to go to EBI0 to test if it replaces the kernel?
carz12 said:
It's not booting, I used my own nan sys and boot img's, set up a working directory and then rebuilt, long time at rogers screen and then boot animation for a minute then a blank back-lit screen, I'll logcat and post it later, time for work.
Is this compatible with the EBI1 dream?
Click to expand...
Click to collapse
What is different about EBI1 from a kernel level? If all you did was extract the system and boot.img, and then build without modifying anything, then that should work.
EDIT: If this is a customized ROM (e.g. with custom kernel) then the update-script file under META-INF\.... may need some manual tweaking. The Option 1 in the menu is recommended only for stock ROMs, because this option creates a simple generic update-script file.
If you are indeed using a custom ROM then I'd try to get the original update.zip file of this ROM, which already has the correct update-script file. Just copy that update-script into your existing kitchen.
Or even simpler, just use the original update.zip file and run Option 11 instead of the Nandroid backup.
carz12 said:
I may need to go to EBI0 to test if it replaces the kernel?
Click to expand...
Click to collapse
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
dsixda said:
I am not familiar with all the different Dreams, but it will replace the kernel if you have a 1.5 or 1.6 ROM.
Click to expand...
Click to collapse
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'll try this tomorrow. Looks cool.
downloading now, ill let you know how things go tomorrow.
carz12 said:
What would happen if I just replaced the wlan.ko and boot.img-kernel in the dream_1_6_update folder with my ebi1 versions? could I test out the add wireless tether option?
Click to expand...
Click to collapse
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
carz12 said:
It works on my rogers dream, I took the original rom for the g1, set up a working directory, replaced the launcher, took out a few apps, replaced the boot.img and wlan.ko with the ebi1 compatible versions I compiled and put in my own prop files, booted right up, thanks for this. Can't test the tethering thing as it'll change the kernel on me.
Click to expand...
Click to collapse
That's great news so far! Thank you
will ROMs created work with MyTouch 3G
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Lets hope I am setting this up now to try it for my touch 3g
nicknowsky said:
will ROMs created work with MyTouch 3G
Click to expand...
Click to collapse
Since it's the HTC Magic, yes it should! Please try and let me know.
I'll create a thread for this in the Magic forum so that people can post their feedback there. Thank you
EDIT: Here's the thread where you can post Magic/myTouch 3G feedback:
http://forum.xda-developers.com/showthread.php?t=651470
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
holmes901 said:
Question...What section on the HTC site would I look for the shipped rom.exe...Specific device = Mytouch?
Click to expand...
Click to collapse
Just do a search in XDA for Mytouch/Magic shipped ROMs. Usually there are links to the original ROMs in the Wiki page for your device.
dsixda said:
I'm not sure exactly what the modified boot.img-kernel in the kitchen has, but I'm guessing it's a couple of networking-related variables that were changed. If your kernel has those modifications then maybe it will work. Doesn't hurt to try
Let me know if it works, then we can use your version for individuals who are cooking Rogers ROMs.
A question: Is it possible to tell that a ROM is for a Rogers Dream (ie. somewhere in the build.prop)? In that way, the script can automatically decide what action to take.
Click to expand...
Click to collapse
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
carz12 said:
I'll try it out tonight, the sources I used to compile were wes's and his kernel has tethering support unless I broke it, I've never used tethering before.
Click to expand...
Click to collapse
Tethering is actually useful even if you don't need it all the time, eg. if your desktop PC cannot access the internet or your wife is using an iPod touch to access the internet in a restaurant.
So do Rogers Dreams require a special kernel, due to the 911 fix? So I guess the stock ROM update has the proper kernel, but modifications like the wireless tether for a Rogers Dream would require a patched Rogers kernel.
Hi!
I would like to establish a Cisco IPSEC-connection with my Xoom, using get-a-robot-vpnc. The problem is that I'm missing a tun-kernel-module and can't find one for the xoom on the web
Does anyone have one for the Xoom WiFi only running 3.2 (Build HTJ85B) with stock kernel?
Thanks!
McDV
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Questions and requests belong in Q&A. Thread moved.
tonyb15re said:
Pulled this out of the EU32Update file, not sure if its what youre looking for??
Click to expand...
Click to collapse
Thanks, I tried this but it looks like it's only for that ROM.
Maybe someone else has a tun-kernel-module for the stock 3.2?!
Greetings
McDV
yup, I'd like to see this too..
Just instal tiamat kernel 2.1 it contains tun.ko and several other modules.
http://forum.xda-developers.com/showthread.php?t=1200063
also you need to use this modified vpn connections
http://forum.xda-developers.com/showpost.php?p=12124163&postcount=23
Here is tun.ko for 3.2 stock.
wonderful! many, many thanks.
hi,
Will this work on 3.2.1? I copied it /system/lib/modules but when I try to openvpn I get cannot allocate tun/tap dev dynamically.
Is this just a bad file for 3.2.1 or am I missing something else?
I did install busybox and openvpn.
Thanks,
Your tun.ko kernel module needs to be compiled specifically against your kernel source. I don't work with stock anymore, however the developer kernel now floating on xda have this module specifically rolled into their kernels. You would have to root however to install these kernels.
Thanks Kevdog..
I searched and i couldn't find any for 3.2.1. I am the rooted stock 3.2.1 already downloaded from xda. Just need to tun.ko for 3.2.1.
If u know where to find, please send me the link.
Thanks.
Ok 3.2.1 -- Stock or Rooted? What kernel are you running?
I got my rom from this thread
http://forum.xda-developers.com/showthread.php?t=1278214
Thanks,
Ok -- I know this is a lot of work, however I tried it myself and I'm not sure if the rom you linked to is corrupted or my download process failed. (***Rant -- why all the developers who put out files don't match the file to an md5 sum so us users can verify the integrity of the dowload -- I'll never know!!), but I can't seem to extract your system.img. You'll need a tool such as unyaffs to unpack the system.img and then search around in the modules folder until you find the tun.ko. Or you could just flash a Tiamat 3.2.1 kernel which has these modules built in!!
I checked checksum and it was correct before I installed it. Not sure what u mean, I thought this rom doesn't have it period.
I also tried to use tiamat 2.2 which says its for 3.2 but it got stuck at boot for 30 minutes at the honeycomb screen. I thought maybe tiamat ker
Net doesn't support 3.2.1 yet.
http://forum.xda-developers.com/showthread.php?t=1200063
As far as i know this is latest. Doesn't mention 3.2.1. Didn't work for me.
I don't want to go to tiamat rom to avoid a full rebuild.