Database Users

HOW TO: Enable Wireless N on The Aria

EDIT:alot of people are unable to do this method because of errors writing to the system. it seems to restore the original bcm4329.ko upon reboot, so this patch has been cooked into the Roms. And wireless N is confirmed to work.
Just flash one of the below roms
Go Here For attn1's Liberated Beta 4 Rom with The Wireless N Patch Cooked in. http://forum.xda-developers.com/showthread.php?t=708434
heres his Beta 3 with wireless N cooked in - http://www.mediafire.com/?wenzltywoom
So i realized that the htc nexus one, htc desire, and htc evo all have the Bcm4329 wireless chip. And they all have wireless N enabled with hacks. Well I know from porting roms for the Aria that the aria also has a BCM4329 wireless chip. So i said to myself, why havent i enabled wireless N on my Aria.
well none of the methods worked except the manual method which isnt too difficult if you have some adb knowledge.just follow the exact steps and youll have no problem.
Prerequisites
-Must Be Rooted
-Must have clockwork recovery installed
-Must have the android sdk installed
ENABLING WIRELESS N
step 1- Download a hex editor
step 2-in a command prompt navigate to the /android-sdk/tools folder and type the following
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko.old
adb pull /system/lib/modules/bcm4329.ko ./bcm4329.ko
(this makes a backup of the original in case you want to go back to wireless G)
Step 3- in the hex editor open up the file you pulled(bcm4329.ko). Now the same as the htc Evo 4g, Htc added 2 strings that say "nmode" without the quotes. Use the search function to find the 2 strings. now you need to replace nmode with any different string. i used "-----" without the quotes for both.
when you're done save the file.
Step 5-now reboot into clockwork recovery and go the partitions menu. go down to mount /system and press the power button.
Step 6-now type this in the command shell.
adb push bcm4329.ko /system/lib/modules/bcm4329.ko
reboot your phone when its done and you now have wireless N enabled.

since the Aria has the same chip as the nexus,, then why wifitether does not work..?

Will try this on my Aria when I get home. Thank you in advance! Now, back to the wifi tethering debacle
Sent from my SAMSUNG-SGH-I897 using XDA App

We Aren't Sure why wireless tethering isn't working yet. But we're pretty sure its gotta be something disabled at the kernel level. It will only be a matter of time before we figure it out.

Is it confirmed that Wireless N is enabled after doing said method?
*edit*
Just tried it, and it's not picking up my Wireless N network, nor does my Wireless router show it connected to a Wireless N. Only Wireless G.
I also did a adb pull of the file I pushed back just to confirm the changes were made, and they are, but for some reason it's not working.

there are some others who are having problems getting this to work as well.
im gonna test it on a rom real quick.
try this-> forgetting the network then reconnecting and re entering the password. not sure if that will fix it but that is what i did when i first connected so maybe that had something to do with it.

I'll give that a try in a few min, and report back.
*edit*
Tried that, the scanning doesn't even pick up the Wireless N network, it only see's the 'G' network. (I have a dual band G & N router)

Well after reading the EVO thread regarding this method, it shows that people who did it are connected at over 54mbps, which is the max for G speeds.
I'm currently connected at 69mbps, so maybe I am on my N?

try to change your wireless N router to N-only and see if it connects and remains connected.

Seems I have no luck, router is in N only mode, but the wifi on the Aria is just 'scanning'.
It's a great idea, just wish it would work.

i dont know why anyone else is unable to get it working, but im patching a rom with this and gonna have someone test it and then ill know. there just seems to be problems with the writing files to the system.

I was starting to think it was a permissions issue, but I'm at a loss as to this one. It might need to be done from a update.zip file in ClockworkMod.

yeah, maybe.
Since there were problems writing files to /system i tried pre-patching a rom and it works. So we're going to just patch the liberated Rom and upload it. check the liberated Rom thread in a little while if you cant get this to work.

Can we add 'ad-hoc' WiFi like this??

Wondering if anyone is working on adding ad-hoc capabilities to future Xoom Roms so that the tablet can connect to these kind of networks.
Already been done with some Android devices here...
http://forum.xda-developers.com/showthread.php?t=754961

I agree this would be a great thing to have, I have the D1 and since it doesn't support infrastructure mode it won't work with my wifi tether app.
Unfortunately... from my understanding and someone please correct me if I'm wrong, we need to wait for the Android 3.0 source to be released. They have released the SDK but it doesn't appear that the actual source has been released yet.
This is definitely something I want to see and I have been playing around trying to see if I can get it to compile, while I have gotten it to compile it doesn't work and is actually an older version than what is included with the Xoom.

I tried following the directions here: http://modmymobile.com/forums/491-root-access/544146-connect-g1-ad-hoc-network-solved.html to no avail.... If anyone can figure out how to allow the xoom to connect to ad-hoc, that would be GREAT!

This method uses a recovery flash and since there isn't a custom recovery on the Xoom yet it wouldn't work. But while I was modding my wifes Nook Color I came across this thread. http://forum.xda-developers.com/showthread.php?t=868354
And it uses adb to push the new wpa supplicant file so it might be doable that way. The Xoom would need to be rooted (no problem there) and you might need to adb shell and push it from the internal memory rather than from the computer but it's a possibility. I just don't have my Xoom yet (pre-ordered from Staples!- should be here on the 28th)
I think that this might have some merit so give it a try guys.

mr_wrong_0 said:
This method uses a recovery flash and since there isn't a custom recovery on the Xoom yet it wouldn't work. But while I was modding my wifes Nook Color I came across this thread. http://forum.xda-developers.com/showthread.php?t=868354
And it uses adb to push the new wpa supplicant file so it might be doable that way. The Xoom would need to be rooted (no problem there) and you might need to adb shell and push it from the internal memory rather than from the computer but it's a possibility. I just don't have my Xoom yet (pre-ordered from Staples!- should be here on the 28th)
I think that this might have some merit so give it a try guys.
Click to expand...
Click to collapse
Interesting...I hope this works
Can someone please test this ASAP and post back if it works or not please?

I can throw up the wpa supplicant file that I used to solve this issue on my Galaxy Tab. I have no idea if the supplicant file is device specific (maybe someone can clarify), but it worked for me...had my Tab rooted and able to ad-hoc connect within about an hour, so I'm hoping it may help you guys. If you're interested, let me know, and I'll post it as soon as I get home tonight.
Sent from my SCH-I800 using XDA Premium App

Be careful playing with the wifi stuff. Make sure you make backups and take good notes. I was playing with my wpa_supplicant file and trying different bcm4329.ko modules, and somewhere along the way broke my wifi. I restored my original supplicant and broadcom modules, but I didn't get my wifi back until I flashed the stock images.
Sent from my Xoom using XDA Premium App

Thanks for the heads up. Yeah you have got to make backups and I wouldn't want to try it until they have the stock restore files for the wifi only model. I don't think I want to use the verizon restore files.

[GUIDE] Enable ad-hoc tethering on your Transformer (needs root!)

Update: If you are using the official firmware 8.6.5.9 (and obviously above) or any custom ROM based on it, you don't have to do anythink described here, because ad-hoc works natively. Thankfully ASUS fixed Googles unintelligible inability to enable connection to ad-hoc networks.
This renders this thread pretty much obsolete, but I won't delete it, just in case anyone doesn't want to or cannot update his device for whatever reason
Hi!
As there are only [Q]uestion threads about ad-hoc tethering by now, I thought I'd write a little guide how to enable it on our Transformer.
edit: If you are using Prime v1.5 (and above I guess), you don't have to do this. Roach2010 already included the modified wpa_supplicant, so you can already use ad-hoc tethering.
All credits and many thanks go to szym for the edited wpa_supplicant that makes ad-hoc possible for us!
!!! Always make a nandroid backup via recovery first! You can then reflash your backup if something fails !!!
I. Via root explorer (obviously requires root access):
If you bought root explorer from the market, you should be able to easily copy and replace the file.
1.) Go to /system/bin and copy the file „wpa_supplicant“ to your sd card as a backup.
2.) Then copy the „wpa_supplicant“ from the attached zip file and paste it into /system/bin.
3.) Long press the file and set permissions to rwxr-xr-x, like this:
User: read, write, execute
Group: read, execute
Others: read, execute
4.) Reboot
Finally tried it myself and works fine
II. Alternative method via adb (requires root access):
This is a forwarded guide from the Xoom section. I tried it myself and it works like a charm. You can find it here.
All credits for the following guide go to kelvie !
1.) Your Transformer has to be rooted! (you'll find a guide how to root here)
2.) Make a backup of your system/bin/wpa_supplicant first!
3.) Unpack the attached wpa_supplicant_xoom_wifi_adhoc.zip file to your adb folder. (if you don't know how to use adb, google for one of the many guides, or look below for another option via root explorer )
4.) push the file to system/bin/wpa_supplicant:
Code:
adb remount
adb push system/bin/wpa_supplicant /system/bin/wpa_supplicant
5.) Because zipfiles don't store permission, you have to make it executable as well:
Code:
adb shell chmod 755 /system/bin/wpa_supplicant
6.) You also have to change the permissions on /data/misc/wifi/wpa_supplicant.conf for some reason:
Code:
adb shell chown system.wifi /data/misc/wifi/wpa_supplicant.conf
7.) reboot
Again, many thanks to kelvie for the guide!
III. Easiest method (requires ClockWorkMod recovery and root):
1.)Download the attached CWM_adhoc_wpa_supplicant_TF101.zip to your sd-card. Make sure to copy it to /Removable/MicroSD, because /mnt/sdcard cannot be accessed from CWM
2.) Boot into CWM recovery.
3.) Hit "install zip from sdcard" --> "choose zip from sdcard", select the zip and confirm.
4.) Reboot
Done. You should now be able to tether your ad-hoc connection
This method doesn't seem to work because I missed an option and don't know right now how to fix it. So if somebody knows how to do this via edify script, please help me out:
Code:
chown system.wifi /data/misc/wifi/wpa_supplicant.conf
Use one of the methods above in the meantime, they works flawless.
__________________________________________________
Q&A
Q: Which app should I use for tethering on my phone? Do I need root access for tethering apps?
A: If your phone doesn't support native tethering, just search the Android Market for 'Wifi tether'. There are a lot of apps for that . I tested Barnacle Wifi Tether on my Sony Ericsson Xperia X10 with 2.3.4 MIUI ROM, which worked fine, but I guess all/most tether apps should work fine now. And yes, unless you have native tethering, your phone has to be rooted.
Q: Barnacle gives me the following error on the phone: "DHCP could not bind to DHCP port, address already in use", and my TF is stuck at "obtaining IP Address from barnacle". What should I do?
A: rpavich has found a solution for that. Thanks rpavich!
rpavich said:
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
__________________________________________________
Regards
qwer23
Edit: I wasn't sure if this belongs in General or Android Dev section, so mods feel free to move it where it fits best.
Edit2: Attached original wpa_supplicant files for 3.0 and 3.1 (don't know if there's a difference, but I doubt it) if someone wants to reset to stock.
If you find this guide helpful, consider pressing the thanks button
Click to expand...
Click to collapse

awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye

philsuf said:
awesome. a few more working confirmation from the others and i wont have to kiss my nokia e71 goodbye
Click to expand...
Click to collapse
No need to wait, you could just try it. If you back up your original wpa_supplicant first, you can always undo your changes. I also added an easier way via root explorer that should be easier.

i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.

Skeldave said:
i just tried it, it connected to barnacle wifi but i couldnt get the internet to work. ill try again tomorrow, it may be my phone.
Click to expand...
Click to collapse
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms

I've done this last week and noticed when stopping my hotspot on the phone the connection on the transformer shows it is still connected. So you have to manual disconnect if you want to reconnect again for later use. This is on my Nokia N8 Phone using JoikuSpot.

I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"

rpavich said:
I tried to do this via the root explorer and it said "you cannot paste here because the file system is read only"
Click to expand...
Click to collapse
On the top of your system directory in root explorer is a button, that says r/w. Push it and you'll get read/write mode.
Sent from my rooted X10i using awesome custom roms

thank you VERY much....I'll let you know how my tethering goes.

qwer23 said:
Did your phone show the barnacle symbol in the notification bar and tell you that a device is connected?
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Yes, the barnacle symbol was in the notification bar and my TF appeared on the 'client' tab, also the TF said that it was connected to barnacle wifi.
I'm going to try again now
EDIT: Worked perfectly this morning, thanks!
I did it via root explorer FYI

This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...

Ok...trouble getting this to work.
1.) On my Xperia X10; message in Barnacle:
"DHCP could not bind to DHCP port, address already in use"
2.) On my TF: it's stuck at "obtaining IP Address from barnacle"

Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)

rpavich said:
Ok....found the solution (on another XDA forum section)
I did the following and connected just fine!
1. Change SSID to whatever you want
2. Change Channel to 6
3. Custom Wifi Ad-hoc to none
4. Skip wpa_supplicant checked
5. Restart your phone (just to make sure...)
Click to expand...
Click to collapse
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms

jake21 said:
This seems like a rather minor change to wpa_suppliant.conf; any clue if google will fix this in honeycomb? Not sure I understand why it isn't enabled by default...
Click to expand...
Click to collapse
I don't have a clue either why this isn't enabled by default, but I think they'll add this in the 3.1 update. But it's just a suggestion, didn't read anything about it though.
Sent from my rooted X10i using awesome custom roms

qwer23 said:
Mind if i add this to the op? There might be others with this issue.
Sent from my rooted X10i using awesome custom roms
Click to expand...
Click to collapse
Not at all....as i said...I got that from another part of the XDA forum...

I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?

sanfaz said:
I used this method from my rooted OG Droid and the Xoom and it worked perfectly. I have to wait for my son in law to root my TF to try it out. Would I only need to root the TF for this to work?
Click to expand...
Click to collapse
At the moment you need to root both your TF and your phone. But if you use Clockworkmod, you probably don't need a rooted TF, because I'm preparing an update.zip to flash via CWM
Your phone has definitely to be rooted, ecxept it supports wifi tethering from stock.
edit: darn, amend scripting is no longer supported in Honeycomb. Anyone knows how to change the zip for edify scripting?
edit2: ok, probably got it solved. we'll see...

Ok, I added a zip file for easy install through ClockWorkMod to the OP. It installed fine on my TF101 and tethering works, but please backup your wpa_supplicant before installing this and report any errors. I didn't work with edify scripts before
I also restructured the guide itself, from easiest to most complicate method
Cheers
qwer23

Would this mod work with an old TP2 windows mobile phone? Will the TF then be able to use it's wifi signal?
Also, if the TF is rooted, will we be able to accept the 3.1 HC update?

Adhoc connectivity (wpa_supplicant)

adhoc connectivity worked on galaxy s2
this trick found from another thread
you need a rooted phone & root explorer
1. Unzip the file attached here (wpa_supplicant.zip) and send wpa_supplicant to your phone.
2. Using Root Explorer go to the folder were you save it (wpa_supplicant) and copy the file.
3. Using Root Explorer, enter the /system folder and press the Mount W/R button (upper right corner)
4. Now go to /system/bin and backup your current wpa_supplicant, and paste the new one.
5. Set permissions to wpa_supplicant like attached picture, then go back to /system and press Mount R/O (upper right corner, so you leave everything exactly like it was) and reboot. Done. Enjoy AD-HOC!

Thanks for the patch, but before you get banned by some moderator, please remove your first attachment. It's a paid app/ WAREZ.

Root Explorer is paid. Don't post it.

Tested & working on sgs 2! Thx man!

I can see the ah hoc network established from my laptop now.. but when I try to connect, it stays in a state "Obtaining IP address" .. so cannot access internet anyway .. Is there any workaround? Thanks.

Thanks dude
excellent, previously i was using connectify to connect my phone to Laptop but the signal strength was so poor and also after few mins it is used to go down. Now got rid of the problem using this file.
Thanks again

ace117 said:
Tested & working on sgs 2! Thx man!
Click to expand...
Click to collapse
+1 for me too.
P.S. just replaced the original file using Root Explorer.

hi,
the same here that varunmagical with VillainRom 2.4.2.
gs2 is able to find adhoc network but cannot obtain an IP.
very much thanks if you can find a solution...
++

Thanks a lot
it worked for me.

I replaced this file. This step is important:change the WPA to WEP encryption mode on PC. AD-hoc is ok using my SII I9100 mobile.Pls to try it. tks.

still not for me despite the wep ad-hoc network created from the mac.
Set permissions to wpa_supplicant like attached picture, then go back to /system and press Mount R/O (upper right corner, so you leave everything exactly like it was) and reboot. Done. Enjoy AD-HOC!
Click to expand...
Click to collapse
what are the permissions to set?
is it important to switch back to Mount R/W ?
thank you

i have a tablet running android 2.3.3 rooted with superoneclick...i follow the instractions to copy paste the wpa_supplicant using root explorer.but when i open my wifi shows false and my table restarts.what i do wrong...i am lucky that i made copy of the original file

I´m actually able to see network but not to connect to it, any advise??

I take it this is not ICS / CM9 compatible ??

Galaxy S II
CF rooted stock 2.3.6
Working in free and WEP modes.
But there were problems with WinXP configuration.
(In wifi network first have myself to connect to created adhoc network, only then phone sees adhoc network)

Galaxy Note's WIFI VERY unstable after replacing wpa_suppliant.
I wanted to connect my galaxy note to my iPad's Mywi for wifi (ad hoc) connection.
Thus i did the following steps:
- root galaxy note using zergrush
- downloaded xda's replacement wpa_suppliant
- downloaded root explorer
- uploaded the replacement wpa_suppliant file to the phone and replaced the original one at /systems/bin
After this, my phone was able to connect to iPad's Mywi, BUT connection is VERY unstable and gets disconnected every 5-10mins. Also it takes really long to get it connected back, like about 10-15mins for it to try to get connected.
I've tried re-doing the WHOLE of the steps above, INCLUDING re-rooting my phone, but to no avail. My Wifi function was working perfectly fine prior to this.
Can some kind souls out there please advice me if I've done anything wrong in my steps? Or if there's any way to solve this (WITHOUT re-doing it back to the original)? thanks!

Hi! Recently I bought the Galaxy W equipped with GB 2.3.6 and yesterday I installed the latest january's firmware upgrade.
Did anybody try to install the modified wpa_supplicant into that device?
Thank you!
Antonio

Set permissions to wpa_supplicant like attached picture? Which permissions? Can you upload that pic again or just tell us what to mark, owner group others? read write execute? And from special permissions: Set UID, Set GID, Sticky?
By default at my stock wpa_supplicant permissions are set and marked like: Owner=mark at read, write and execute, Group=mark at read and execute,
Others=mark at read and execute. None of special permissions are marked.
Should it be the same for new copied wpa_supplicant or?
Thanks in advance...

Just one little question here. I hope someone takes time to answer it. I have been around reading about adhoc this and adhoc that. But what I wanna know if these methodes that enable adhoc functionality, allow 2 mobile devices to get connected to each other. I mean like between 2 SGSII not between a PC and a SGSII?
Like making one of the SGSIIs the center and the other client (or infrastructure or whatever it's called)?? Is this possible with all these adhoc enablers?

Can't turn Wi Fi on after using the file from OP.
Using ICS/CM9 Hydra rom.

[HOWTO] Wi-Fi Tethering on MIUI

Start the rom's wifi tether from Settings > System > Tethering & Portable Hotspot > Portable Wi-Fi hotspot.
You should be able to connect to it, but you won't be able to use the Internet.
Now set up the NAT manually, for which which I've found a tutorial online*. We'll want to connect ppp0 to wl0.1.
Open a root shell and enter the following. (Note that /proc/sys/net/ipv4/ip_forward is set to 1 automatically when we enable the rom's tethering)
Code:
iptables -t nat -A POSTROUTING -o ppp0 -j MASQUERADE
iptables -A FORWARD -i ppp0 -o wl0.1 -m state --state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -i wl0.1 -o ppp0 -j ACCEPT
Now you'll be able to access the Internet from your computer.
Disclaimer: I haven't tried turning it off yet. I assume you just remove the three rules and then turn off the rom's tethering.
*new users can't post links, so just Google "linux nat"

Barnacle works fine for me, without any mods.

nunyazz said:
Barnacle works fine for me, without any mods.
Click to expand...
Click to collapse
ON miui rom?

http://www.revsys.com/writings/quicktips/nat.html
This link.

This works great. Is there any way to make these commands happen each time at startup? (Settings are lost on reboot)
Also does this have to run after wireless tether is enabled? Or does that not matter.

kallell said:
ON miui rom?
Click to expand...
Click to collapse
Yes. Both MIUI and CM7

nunyazz said:
Yes. Both MIUI and CM7
Click to expand...
Click to collapse
Can you post details for CM7 here
http://forum.xda-developers.com/showthread.php?t=1198835
I tried but never got it working. Exact steps would be appreciated.
Thank you.

justinjbaron said:
This works great. Is there any way to make these commands happen each time at startup? (Settings are lost on reboot)
Also does this have to run after wireless tether is enabled? Or does that not matter.
Click to expand...
Click to collapse
Add them to init.rc

webwhacker said:
Can you post details for CM7 here
http://forum.xda-developers.com/showthread.php?t=1198835
I tried but never got it working. Exact steps would be appreciated.
Thank you.
Click to expand...
Click to collapse
Install Barnacle, turn it on.
That is all....

same with wifi tether for me. install, go.
[Neuman]
SCH-I500 - EC09 Radio/MIUI FascinateMTD/Glitch V11.1 LL @1.2ghz -100mv/DarkWhite

i tried putting the commands in the init.rc under "on boot" but when i rebooted the file reverted back to what it was before i edited it and the backup of the original file i made was gone (init.rc.bak). can someone help me do this? i think the built-in tethering is just more convenient to use rather than installing barnacle and i'm hesitant to use it anyway cuz wifi tether didn't work for me
edit: i guess barnacle does work but i would still like to get this working if it doesn't get fixed in the next update

manic020 said:
i tried putting the commands in the init.rc under "on boot" but when i rebooted the file reverted back to what it was before i edited it and the backup of the original file i made was gone (init.rc.bak). can someone help me do this? i think the built-in tethering is just more convenient to use rather than installing barnacle and i'm hesitant to use it anyway cuz wifi tether didn't work for me
edit: i guess barnacle does work but i would still like to get this working if it doesn't get fixed in the next update
Click to expand...
Click to collapse
Does anyone happen to have any insight on this? I know this is an old thread...but I agree with this dude.

You need to unpack and repack the boot.img to make it stick. The init.rc is inside that.

cougarcougar said:
You need to unpack and repack the boot.img to make it stick. The init.rc is inside that.
Click to expand...
Click to collapse
old thread is old
Sent from my AOKP SCH-i500