(this item also posted on PPCGeeks)
I'd like to start by thanking arrrghhh and BoominSVX for running thru some tests to see whether or not I had actually found a working solution.
NOTE: This solution requires altering a configuration file. How you alter the file is entirely up to you (vi, desktop utilizing adb, telekinesis, etc.).
I recommend backing up any file that you plan to edit or replace prior to mucking about with it.
WARNING: Instructions will tell you to turn off or restart Wi-Fi.
This is to ensure that the changes you have made to your configuration files are reloaded by wpa_supplicant.
Simply changing the configuration file is not sufficient!
In addition, I am not responsible for any damage that these instructions may cause to your device, your data, and/or your well-being.
PERFORM THESE ACTIONS AT YOUR RISK
The following instructions will take you through the 'long' method:
Connecting to WEP-enabled Wi-Fi (Easy/Standard)
Go to Settings->Wireless & Networks -> Wi-Fi settings
Turn on Wi-Fi if it is not enabled
Setup your Wi-Fi connection
If your AP shows up in the list, select it and type in your WEP key
If your AP does not show up, use the Add Wi-Fi network. On the popup, type your SSID, select 'WEP' for Security, and type your WEP key in the Password.
NOTE: At this point, the Wi-Fi status will go from "Scanning..." to "Connecting..." to "Disconnected"
Turn Off Wi-Fi
Backup the following file: /data/misc/wifi/wpa_supplicant.conf
The file contents should be similar to this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
The priority=1 may or may not be present, based on whether you selected from the scan list, or added it manually.
Edit /data/misc/wifi/wpa_supplicant.conf and remove either OPEN or SHARED from the auth_alg line. Which one depends on whether the access point is using OPEN, SHARED (if it's using both you can choose which one you prefer to use)
After editing, OPEN will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN
wep_key0=YOURWEPKEYHERE
priority=1
}
After editing, SHARED will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
Go to Settings->Wireless & Networks and turn on Wi-Fi.
Your Wi-Fi status should now show the following values:
"Scanning..."
"Connecting..."
"Obtaining an IP address YOURSSIDHERE..."
"Connected to YOURSSIDHERE"
NOTE: If you fail to connect, return to step 4 and try using the other auth_alg value.
Some routers may be configured to only support one authentication mode.
That's the long method - for people who have never connected to a Wi-Fi connection, or don't mind losing saved APs can do the following
Connecting to WEP-enabled Wi-Fi (Advanced)
Create your own wpa_supplicant.conf file, either by hand, using the above code snippets, or one of the template files in the zip
Replace YOURSSIDHERE with the value of your ssid.
Replace YOURWEPKEYHERE with the value of your WEP key.
Place your edited wpa_supplicant.conf file in the /data/misc/wifi directory on your device
Restart/Turn on Wi-Fi
This method has been tested using FRX04 system image, with both Stock and F22's updated rootfs.img file, and against both FRX04 shipped and WisTilt2's debug kernels.
Feel free to share your success and/or failure stories in this thread.
lol, thanks for this. Now I just need to figure out how to communicate with my device using telekinesis....
I don't use WEP, but the masses that seemingly need it will love you for this. Still not sure how we're going to commit it .
Great work, thanks a lot!
So if I'm understanding this right, this modification is specific to an individual WEP access point, and has to be made once for each new WEP access point you come across? I wonder where we could make a change so that XDAndroid will make this change automatically.
I was trying to get WEP working earlier too, and I noticed that by using a different wpa_supplicant (not conf) file, I was able to connect to WEP access point and send and receive data, but for some reason DNS just wouldn't work.
manekineko said:
Great work, thanks a lot!
So if I'm understanding this right, this modification is specific to an individual WEP access point, and has to be made once for each new WEP access point you come across? I wonder where we could make a change so that XDAndroid will make this change automatically.
I was trying to get WEP working earlier too, and I noticed that by using a different wpa_supplicant (not conf) file, I was able to connect to WEP access point and send and receive data, but for some reason DNS just wouldn't work.
Click to expand...
Click to collapse
You are correct - the configuration is handled on a per-network basis. Remembered networks will be stored in that file, so a wpa_supplicant.conf can contain multiple network={ ... } structures, and each structure could contain an auth_alg line.
I don't know the status of other devices, and forcing it to write a specific value might break ones that are currently working.
There is speculation that a newer version of wpa_supplicant (we're running 0.5.x as is my understanding) may be able to handle the conf file the way it is currently written. The fact that a you used a different version and were able to connect would tend to confirm that.
Do you happen to know what version of wpa_supplicant you were using when it did connect?
Pohket said:
You are correct - the configuration is handled on a per-network basis. Remembered networks will be stored in that file, so a wpa_supplicant.conf can contain multiple network={ ... } structures, and each structure could contain an auth_alg line.
I don't know the status of other devices, and forcing it to write a specific value might break ones that are currently working.
There is speculation that a newer version of wpa_supplicant (we're running 0.5.x as is my understanding) may be able to handle the conf file the way it is currently written. The fact that a you used a different version and were able to connect would tend to confirm that.
Do you happen to know what version of wpa_supplicant you were using when it did connect?
Click to expand...
Click to collapse
Here's my post on it:
http://forum.xda-developers.com/showthread.php?p=11016773
I believe this was using wpa_supplicant v0.5.11.
Hehehehe, WEP works. Thanks for the tip.
this is bigger for me than gettin the cam working.
thx
its great but sorry i dont know how to mount it and where plz help ?? thanks in advance
wifi-ace
I'm using wifi-ace (android market or here: code.google.com/p/android-wifi-ace/) and wep is working fine.
Found it during my search for the hidden network problem.
You are able to adjust everything with this app.
So you don't need to change the "wpa_supplicant.conf", the app
does it for you.
My hidden network at home is working fine now
ohh i dont know how to use this program plzz anyone tell me how to mount this ???
ammmma2 said:
ohh i dont know how to use this program plzz anyone tell me how to mount this ???
Click to expand...
Click to collapse
Download it from the Market.
NO WIFI
Pohket said:
(this item also posted on PPCGeeks)
I'd like to start by thanking arrrghhh and BoominSVX for running thru some tests to see whether or not I had actually found a working solution.
NOTE: This solution requires altering a configuration file. How you alter the file is entirely up to you (vi, desktop utilizing adb, telekinesis, etc.).
I recommend backing up any file that you plan to edit or replace prior to mucking about with it.
WARNING: Instructions will tell you to turn off or restart Wi-Fi.
This is to ensure that the changes you have made to your configuration files are reloaded by wpa_supplicant.
Simply changing the configuration file is not sufficient!
In addition, I am not responsible for any damage that these instructions may cause to your device, your data, and/or your well-being.
PERFORM THESE ACTIONS AT YOUR RISK
The following instructions will take you through the 'long' method:
Connecting to WEP-enabled Wi-Fi (Easy/Standard)
Go to Settings->Wireless & Networks -> Wi-Fi settings
Turn on Wi-Fi if it is not enabled
Setup your Wi-Fi connection
If your AP shows up in the list, select it and type in your WEP key
If your AP does not show up, use the Add Wi-Fi network. On the popup, type your SSID, select 'WEP' for Security, and type your WEP key in the Password.
NOTE: At this point, the Wi-Fi status will go from "Scanning..." to "Connecting..." to "Disconnected"
Turn Off Wi-Fi
Backup the following file: /data/misc/wifi/wpa_supplicant.conf
The file contents should be similar to this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
The priority=1 may or may not be present, based on whether you selected from the scan list, or added it manually.
Edit /data/misc/wifi/wpa_supplicant.conf and remove either OPEN or SHARED from the auth_alg line. Which one depends on whether the access point is using OPEN, SHARED (if it's using both you can choose which one you prefer to use)
After editing, OPEN will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=OPEN
wep_key0=YOURWEPKEYHERE
priority=1
}
After editing, SHARED will look like this:
Code:
ctrl_interface=eth0
update_config=1
network={
ssid="YOURSSIDHERE"
key_mgmt=NONE
auth_alg=SHARED
wep_key0=YOURWEPKEYHERE
priority=1
}
Go to Settings->Wireless & Networks and turn on Wi-Fi.
Your Wi-Fi status should now show the following values:
"Scanning..."
"Connecting..."
"Obtaining an IP address YOURSSIDHERE..."
"Connected to YOURSSIDHERE"
NOTE: If you fail to connect, return to step 4 and try using the other auth_alg value.
Some routers may be configured to only support one authentication mode.
That's the long method - for people who have never connected to a Wi-Fi connection, or don't mind losing saved APs can do the following
Connecting to WEP-enabled Wi-Fi (Advanced)
Create your own wpa_supplicant.conf file, either by hand, using the above code snippets, or one of the template files in the zip
Replace YOURSSIDHERE with the value of your ssid.
Replace YOURWEPKEYHERE with the value of your WEP key.
Place your edited wpa_supplicant.conf file in the /data/misc/wifi directory on your device
Restart/Turn on Wi-Fi
This method has been tested using FRX04 system image, with both Stock and F22's updated rootfs.img file, and against both FRX04 shipped and WisTilt2's debug kernels.
Feel free to share your success and/or failure stories in this thread.
Click to expand...
Click to collapse
I do not understand how do I get to this file? I tried to use wifiace and terminal emulator but still no connection only scan, connect, and disconnect. I put my ssid and password in correctly but it still shows the lock symbol and also I can put any number in and it doesn't change just remembered, secured with wep! Any help and I really don't understand the Android SDK usage! thanks again!
SteelLife said:
I do not understand how do I get to this file? I tried to use wifiace and terminal emulator but still no connection only scan, connect, and disconnect. I put my ssid and password in correctly but it still shows the lock symbol and also I can put any number in and it doesn't change just remembered, secured with wep! Any help and I really don't understand the Android SDK usage! thanks again!
Click to expand...
Click to collapse
If you have any choice in the matter, please, please use WPA, or better yet WPA2 with AES.
WEP is ridiculously insecure, and only slightly better than running a completely open network.
If it's not your AP, and you have no choice... wifi-ace works great. Much easier than this method, although this method does work.
With previous experience in network security, a WEP key can be broken in as little as 2-5 Minutes. 30 Minutes with no prior knowledge and just following a guide.
For security sake, use WPA or WPA2 with either encryption, they are equally difficult to break the key.
Cracking a WEP key is as simple as collecting enough unique IVs and running it against a cracking tool.
Cracking a WPA/WPA2 key is not so simple, you need a handshake packet, then you need to run the handshake packet against a dictionary attack (that can last 30 minutes with a big dictionary on a good computer) until you find the word, if it is not in the dictionary it will have to be brute-forced requiring 7392 days on a very very good computer for a key that is 8 random characters. Hackers purely wont waste their time.
WPA/WPA2 is safe, for now. Use that.
arrrghhh said:
If you have any choice in the matter, please, please use WPA, or better yet WPA2 with AES.
WEP is ridiculously insecure, and only slightly better than running a completely open network.
If it's not your AP, and you have no choice... wifi-ace works great. Much easier than this method, although this method does work.
Click to expand...
Click to collapse
I have no choice! I tried the wifi-ace but it only scan connect disconnect. I don't know! Is there away to erased my SSID so I can start over!
Finallly online!
Ok, Im online had to put password in one of the key management thru wifi-ace!
thanks all!
SteelLife said:
I have no choice! I tried the wifi-ace but it only scan connect disconnect. I don't know! Is there away to erased my SSID so I can start over!
Click to expand...
Click to collapse
Do you not own the WAP? You should get rid of WEP at all costs.
arrrghhh said:
Do you not own the WAP? You should get rid of WEP at all costs.
Click to expand...
Click to collapse
Building share and want to stay on wep for whatever reason I don't know!
SteelLife said:
Building share and want to stay on wep for whatever reason I don't know!
Click to expand...
Click to collapse
Tell them anybody with a laptop and basic knowledge can hack into it no prob. Then not only could they potentially steal your internets, they could also easily get into your machines, as the intruder is now on your LAN.
Meh, do what you gotta do. Just be wary of the consequences for choosing poor security methods.
arrrghhh said:
Tell them anybody with a laptop and basic knowledge can hack into it no prob. Then not only could they potentially steal your internets, they could also easily get into your machines, as the intruder is now on your LAN.
Meh, do what you gotta do. Just be wary of the consequences for choosing poor security methods.
Click to expand...
Click to collapse
I know have been telling them for 6 months to change too no prevail!
Hi!
I tried several guides on the internet to change my MAC address, at first, using one of the "MAC spoofer" Apps, but they all just change it "softly" so you can't connect to Password protected Routers (same happens if you use the busybox/terminal method), but my router is password protected and i need that protection. Next i've tried this guide:
"After your rooted head into terminal emulation type su and go into /data/misc/wifi
Look for a file called nvram.txt
Copy it to your sdcard and then to your cpu desktop open it with notepad and at the bottom of nvram.txt is the mac address
This i was able to verify and test on android Citrus Ciena
Edit that mac address and save it as nvram1.txt onto sdcard
Now go back to data wifi misc and copy nvram.txt to nvram.bak
Head into gui and then settings then wifi then turn on the wifi but don't connect to any wifi
turn off the wifi,switch back to terminal
Copy the nvram1.txt to data misc wifi
remove the original (make sure you got it backed up)
Rename nvram1.txt to nvram.txt
head back into gui and then settings then wifi
Now for me it immediately stated unable to turn on wifi
Ignore it and try to turn it on anyways
When it turns on your newly edited mac address will take effect
Connect to your AP
NOW B4 REBOOTING YOU MUST CHANGE NVRAM BACK TO THE ORIGINAL!"
but I haven't found the nvram.txt, so i searched and searched and found out the "s3 version" of it, is "/etc/wifi/nvram_net.txt" but in this file, my s3 shows me a completely different MAC, as my handy actually has. I tried the method with this file anyway, but it didn't work, i still had my old mac, but the MAC written in the file was not reset, so it seems like the system doesn't even care about the MAC-line in that file. So next I found the ".mac.info" file in "/efc/wifi/" and in this file, there is just my MAC written, which really is my actual MAC. So i tried the Method i've pasted above with that file, and it didn't work, the system did just overwrite that file and as i checked after turning my WLAN back on, there was again my old MAC in the file. Then i tried changing it and making it read-only through Root Explorer, but it didn't work either. This time the system afterwards still had the old MAC, but the file didn't change, so in .mac.info there was still my new MAC written, but the system still had the old one. After some time i checken the file once again, and then suddenly the old MAC was written in the file, and the system did automaticly gave writing-permission back. Now i'm just desperate, so if anyone can tell my any method to change the MAC, which works on galaxy s3, please tell me.
Try Pry-Fi from Chainfire.
https://play.google.com/store/apps/details?id=eu.chainfire.pryfi
____________________________________________
P3110 / I9300 / I9100 / NEXUS 5 / iPAD2