[SOLVED(?)]WiFi settings reset themselves 802.1x EAP w/ TTLS and 2nd phase PAP

[Guest aMpeX]

Once again, cheers to everyone.

Today I found out, that I cannot connect my Optimus 2X to the wireless network of my university. This is due to the fact, that the setting for the 2nd phase authenticitation in the respective network setting keeps resetting itself to "none" everytime I try to set it to PAP.

Can anybody try this out? (Create a new network with 802.1x EAP encryption and set the EAP-method to TTLS and the 2nd phase auth to "PAP", close the settings pane, and open it again and see if it resetted itself)

Are there any solutions to this?

Greetings

aMpeX

V10b

dirty kernel

20110218 baseband.

Edit:

Preliminary solution:

1) Download the wpa_supplicant file from here http://www.megaupload.com/?d=AR8I833Z Thanks to simonsy89 for supplying it. As far as I am concerened, any wpa_supplicant from an Eclair ROM does work, 0.6.9 is the version that shipped with Eclair. The version on Froyo is 0.6.10 which has a flaw preventing it from connecting to enterprise WiFi's using 802.1x EAP.

2) Copy the file to /system/bin/ MAKE SURE TO BACKUP YOUR EXISTING FILE FIRST!!!

(ROOT NEEDED) Copy wpa_supplicant to your adb dir


adb remount

adb push wpa_supplicant /system/bin/wpa_supplicant

3) Make sure the correct permissions for the file are set. You can do so by doing the following:

adb shell

$su

#mount -o remount, rw -t yaffs2 /dev/block/mmcblk01p1 /system

#chmod 755 /system/bin/wpa_supplicant

Further information on the issue can be obtained here: http://code.google.com/p/android/issues/detail?id=8804

Post #46 proposes the same solution.

Enjoy

aMpeX

Edited April 10, 2011 by aMpeX

[Guest aMpeX]

Used Wifi Advanced Configuration Editor to edit the parameters. Will report on monday if it worked.

[Guest simonsy89]

Used Wifi Advanced Configuration Editor to edit the parameters. Will report on monday if it worked.

Hi, this problem is caused by a bug in the wpa_supplicant file of the new version of android froyo 2.2.2 . I solved the problem replacing that file with another one patched.

Replace the file in the folder system/bin/wpa_supplicant with this one http://www.megaupload.com/?d=AR8I833Z.

[Guest aMpeX]

Hi, this problem is caused by a bug in the wpa_supplicant file of the new version of android froyo 2.2.2 . I solved the problem replacing that file with another one patched.

Replace the file in the folder system/bin/wpa_supplicant with this one http://www.megaupload.com/?d=AR8I833Z.

Wow, thanks. I will try that tomorrow.

How did you find out about this ?

[Guest simonsy89]

Wow, thanks. I will try that tomorrow.

How did you find out about this ?

I had the same problem, so I tried to watch the logcat and I discovered that there was a problem with the handshake authentication to the network. Searching the internet I discovered it was a known problem with versions 2.2.x of Froyo

[Guest aMpeX]

What's super important is that you set the proper permissions for wpa_supplicant after you push it over.

I almost thought I had bricked my WiFi because it would throw a "Network Scan not possible" even after I pushed back the original file.

just to leave this here for other users after me:

adb shell

$su

#mount -o remount, rw -t yaffs2 /dev/block/mmcblk01p1 /system

#chmod 755 /system/bin/wpa_supplicant

I'll be putting these findingss and your files to the first post and check back when I confirmed it tomorrow.

Cheers

aMpeX

[Guest Timon2x]

check back when I confirmed it tomorrow.

Did it work?

[Guest aMpeX]

Did it work?

It's embarrassing but, I don't know.... discovered I had a braindead typo in there all along, it does work however, but I don't know if that fixed it.

[Guest Timon2x]

Too bad, I'm having a similar problem with the university wifi net but i can exclude typos. I tried pretty much everything besides rooting.

[Guest aMpeX]

try WiFi advanced configuration editor to rule out any configuration error in your wpa_supplicant.conf

If that doesn't work, you're pretty much out of options, except for applying the solution simonsy posted above.

You don't have to root permanently, a temporary shell root with SuperOneClick will vanish after a reboot.

[Guest Timon2x]

Replacing the wpa_supplicant binary worked on first try - thx,

really weird old bug with cisco ap's that's still in new released 2.2 phones

I solved the problem replacing that file with another one patched.

@simonsy89 - Where's the patched file taken from?

[Guest MaasOne]

What's super important is that you set the proper permissions for wpa_supplicant after you push it over.

I almost thought I had bricked my WiFi because it would throw a "Network Scan not possible" even after I pushed back the original file.

just to leave this here for other users after me:

adb shell

$su

#mount -o remount, rw -t yaffs2 /dev/block/mmcblk01p1 /system

#chmod 755 /system/bin/wpa_supplicant

I'll be putting these findingss and your files to the first post and check back when I confirmed it tomorrow.

Cheers

aMpeX

I'm having the same problem on Honeycomb. I bricked my WiFi with that file, but also the shell command (mount -o remount...) will not be accepted. It seems, I can't give any write permission to that file.

Is the file compatible with Honeycomb?

Is the "mount -o remount, rw..." command correct?

Flashing the original system.img fixes the problem of bricked WiFi (replacing with original wpa_supplicant and permissions), but of course the 802.1x problem is still alive.

greetz

Maas