Related
Hello to everybody. I tried to search this forums, but didn't find the solution.
Is it possible to disable WPA2 wifi authentication in windows mobile 6.1 device? I have issues with connecting to WPA2/AES network (device crashes to black screen). Manual setting to WPA/TKIP does not work, because it is overrided with WPA2/AES.
Some information here on the MSDN website:
http://msdn.microsoft.com/en-us/library/aa916274.aspx
There doesn't seem to be anything to disable WPA2 though
Thanks for the links. But after long time googling and reading some technical stuff, I am more and more convinced, that it is hardcoded into wifi drivers and it isn't possible to change it .
Better solution should be use of correct-WPA2-working driver, but I am neither programmer, nor experienced cooker to use driver from different type of WPA2-working device with same wifi chip.
EDIT: I found, that it crashes before showing of login dialog (PEAP auth), so that must be problem with WPA2 pre-authenication.
torrentonly said:
Thanks for the links. But after long time googling and reading some technical stuff, I am more and more convinced, that it is hardcoded into wifi drivers and it isn't possible to change it .
Better solution should be use of correct-WPA2-working driver, but I am neither programmer, nor experienced cooker to use driver from different type of WPA2-working device with same wifi chip.
EDIT: I found, that it crashes before showing of login dialog (PEAP auth), so that must be problem with WPA2 pre-authenication.
Click to expand...
Click to collapse
I have WPA2/AES working on my Kaiser with the (almost) stock 5.2.19212 ROM. I did update the WiFi driver in my kitchen though (TNETW1251.dll version 3.55, dated 10/06/2008). I have never had any issues with WPA2 though, even before I upgraded to WM6.1.
Andy
I have Vox and it crashes with every ROM, original & custom without difference. Mainboard replacement didn't solve this problem, so that must be software issue. Where did you get that updated TNETW1251.dll? Here I only found patched one for ICS.
torrentonly said:
I have Vox and it crashes with every ROM, original & custom without difference. Mainboard replacement didn't solve this problem, so that must be software issue. Where did you get that updated TNETW1251.dll? Here I only found patched one for ICS.
Click to expand...
Click to collapse
I can't remember where I got it from originally - more than likely a post in the Kaiser ROM Development forum. I am not sure its the same driver on the VOX but here it is anyway (just delete the .zip extension).
Andy
Too bad, another driver for same wifi chip doesn't work (doesn't load on startup). Maybe because of different chipset. But thanks anyway.
I am trying to connect to my university's wireless.
We have two different wireless ssid's that i can connect to with my laptop.
The first, called UBC is unsecured, but when you connect, it takes you to a web page where you enter your username/password.
The second, called ubcsecure, can authenticate with either WPA2 or WPA ( it shows up as WPA2-Enterprise).
The encryption method is AES for WPA2, and TKIP for WPA.
EAP type: PEAP v0 , Authentication protocol is MS-CHAP-V2
there is an option for mutual authentication using a certification server:
secure.wireless.ubc.ca
I am unable to connect to either using the stock HTC magic ROM, the HoFo community rom, and most recently, myHero 1.0.1
I have tried editing /system/etc/wifi/wpa_supplicant.conf to include
network={
ssid="ubcsecure"
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP
identity="[email protected]"
password="password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
Any ideas as to how to connect?
Data wipe.
Try to reset your phone's basic settings.
It could rebuild the information necessary to acquire the specific IP from their connection.
Manually entering the data couldn't hurt either. This is something that usually I would consider consulting the school about. Privatized internet connections could cause a number of issues for those seeking to utilize Wi-Fi.
The NAT settings might be too strict to support a handheld device.
Me too!
have you found any other solution??
i m here in ubc as well with my htc magic 1.5
when i'm trying to connect to ubc,, it keeps requiring the ip but doesnt connet
and ubcsecure doesnt even show up!
is really frustrating not being able to use internet in universityyy..
i thought by activating the wpa enterprise will work for the ubcsercure, i guess not??
will any of the heros rom work??
Im having this problem too.. anyone find a fix?
I have no idea why but ubcsecure seems to be working using JesterBlur ROM. http://forum.xda-developers.com/showthread.php?t=567122
it works on the Dream? or sapphire? I don't think it matters but... be interesting to know
Dream. Theres a version for the Sapphire. Maybe give it a shot? ubcsecure still working here.
Ask for working setting
absolutcamper said:
Dream. Theres a version for the Sapphire. Maybe give it a shot? ubcsecure still working here.
Click to expand...
Click to collapse
Did you use the UI setting or you edit the "wpa_supplicant.conf" file manually?
would you please send us your "wpa_supplicant.conf" file or its ubcsecure part? it would be the great help to have a working setting.
Cheers,
Ali
I used the UI that came up during first boot. How can I get to that file?
the wpa_supplicant is in /data/misc/wifi. But considering how it works using the ui settings, i dont think changing the config file will work...but please still post it.
I also tried replacing the wlan.ko from the jesterblur rom... and doesnt seem to be compatible with magic which is apparently normal because there is a patch for magic users that fixes wifi apparently. I will try the wlan.ko from the fix soon probably to see if it works.
Hi guys,
I'm at UBC with the same problem (I can't even connect to the regular UBC network). I went to the UBC help desk and they basically told me that they don't support android at all. The funny thing is I can connect to the fatport network with no problems but cannot connect to ubc, ubcsecure or eduroam networks on campus. I'm currently runnning on Cyanongen 4.2.4 (waiting for 32a kernel to upgrade to 4.2.5) on a rogers htc magic.
Anyway, the point of this post. If anyones interested in meeting up at UBC to find a solution to this problem it'd be great. I'm hoping we can eventually create a package of some sort that'll fix any android phone but lets focus on fixing the current prob first.
Also @fnkaze - aren't the dream and sapphire the same thing?
Er, i think the dream is the G1 and the sapphire is the G2 aka the rogers magic... well i think the dream has a differnt wifi driver? maybe.. thats the problem
I think the reason why they dont support android is because the stock rogers rom doesnt have native wpa2 support i think.... but the custom roms should have it.. the hero rom does have it... at home my wpa2 wifi works fine
I can also connect to fatport, i think the eduroam is also using the same thing...tho ive heard eduroam seems to work on the rogers rom at different univeristies..
I still have yet to try the jester rom wifi driver tho, ill try it soon...
Thanks for the clarification. And the reason eduroam works at other universities is because the WPA encryption settings are based on the uni's actual/main wireless network. So at different universites the authentication protocols might be a bit different.
What phone do you have? The dream or the magic? The jester rom doesn't work on my magic.
i have the magic, but i think it should work on the magic, they also have a seperate patch to get Wifi working for the it.. so im assuming its possible..
So yeah, Concordia University in Montreal has the same WPA2-Enterprise and this is how I got WIFI to work on my Magic (with HoFo's Sense UI ROM, would still probably work with a rooted 1.5/1.6 ROM)
In fact it will probably work with any rooted Dream or Magic
Remember you need your phone to be rooted for this to work, you will also need to have the drivers installed for your phone from the Android SDK.
- Go into recovery mode
- mount the /data/ folder
Code:
adb shell mount /data
- With ADB Pull the /data/misc/wifi/wpa_supplicant.conf file to your computer (in this example it will go to the tools folder where you have your androidsdk)
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf .
- Make a backup of your conf file in case you mess something up
- Edit it and add in the configuration settings given by your University for Linux wpa_supplicant.conf files, so in your case
Code:
network={
ssid="ubcsecure"
proto=WPA
key_mgmt=WPA-EAP
pairwise=TKIP
group=TKIP
eap=PEAP
identity="[email protected]"
password="password"
phase1="peaplabel=0"
phase2="auth=MSCHAPV2"
}
- With ADB Push the wpa_supplicant.conf from your computer to the /data/misc/wifi/ folder
Code:
adb push wpa_supplicant.conf /data/misc/wifi/
mydewji13 said:
UBC help desk and they basically told me that they don't support android at all.
Also @fnkaze - aren't the dream and sapphire the same thing?
Click to expand...
Click to collapse
Honestly that person at the helpdesk probably doesn't even know what Android is. If they says they don't support Android at all, well using their logic any Linux distro using wpa_supplicant.conf isn't supported which OBVIOUSLY isn't the case.
And no the Dream and Magic are far from being the same device.
Thanks!
I'll try this solution and see if it works. Will post back to let you know how it goes.
Hi,
Ok, I just finished installing the sdk, fixing udev to recognize my phone etc...
The problem I'm having is that everytime I run:
Code:
adb shell mount /data
I get the following error:
Code:
mount: cannot read /etc/fstab: No such file or directory
Help?!?!
NVM after reading the adb -help i tried this:
Code:
adb pull /data/misc/wifi/wpa_supplicant.conf /home/myuser
Ok something really wierd happened...I pushed a new wpa supplicant file and the rebooted the phone and it stopped seeing wireless networks! But ubcsecure showed up as a known network. If I long press it an 'forget it' I can see networks again, but still cant connect to any ubc network?
WTF>?
Is there anyway I could use by ubuntu wpa_supplicant settings? Anyone know where the file is on Karmic? b/c I cant find it at all
I have no permissions to publish to HD Mini ROM Development, published the solution here.
I have the solution to put wifi in Android 2.2 of Schlunds, the problem is in the process "htcUPCTLoader.exe" not allowed to continue with the process.
The assignment of IP must be static, do not get the IP automatically
Here I leave kernel with the new install
TESTED ONLY WITH ANDROID 2.2 Schlunds
Sorry for my bad English
hey thanks man
maybe u will find a fix for derefas sd card fix too?
Does not work for me. The zImage and Module are exactly the same files I use.
The Problem ist not the htcUPCTLoader.exe process.
tzacapaca send me his working 2.2. image and it still dont work for me.
The reason must be something else...
Perhaps bootloader or startup.txt?
codiak said:
Does not work for me. The zImage and Module are exactly the same files I use.
The Problem ist not the htcUPCTLoader.exe process.
tzacapaca send me his working 2.2. image and it still dont work for me.
The reason must be something else...
Perhaps bootloader or startup.txt?
Click to expand...
Click to collapse
Or the Windows Mobile rom used?
After trying the Android images, I had a lot of GPS issues under WinMo (not working anymore). At the end it was fixed, but could it be that the WinMo roms can be of influence on Android?
MobileMini said:
Or the Windows Mobile rom used?
After trying the Android images, I had a lot of GPS issues under WinMo (not working anymore). At the end it was fixed, but could it be that the WinMo roms can be of influence on Android?
Click to expand...
Click to collapse
I start to believe is this...i'm gonna use use Stock ROM and i will keep you posted if it will be any changes
nsourm has a dualbootloader in his ROM
Maybe its better to boot Android not from "within" WinMo.
Can someone test that?
codiak said:
Does not work for me. The zImage and Module are exactly the same files I use.
The Problem ist not the htcUPCTLoader.exe process.
tzacapaca send me his working 2.2. image and it still dont work for me.
The reason must be something else...
Perhaps bootloader or startup.txt?
Click to expand...
Click to collapse
In my case the prob was "htcUPCTLoader.exe" it was not allowing deamon to start..so i had to kill it and then run the run.bat file....
Can u try it this way..??..connecting the Mini with pc..running run.bat...after that killing htcUPCTLoader.exe process in task manager..and then running run.bat file again..??.... it might work....if not..then there's no harm done
I dont need to try. The kernel module file (*.ko) in the image is updated. So the problem (at least for me) is not adb push. must be something different.
Codiak, your not alone. I am also not able to turn WiFi on. Do you get Error when you go to the settings to turn it on? It's like its not picking up the WiFi on the mobile.
The only thing I changed was adding in the run.bat
Code:
taskkill / F / IM htcUPCTLoader.exe
On beginning of everything, to finish the process before starting the adb. I haven't touched anything of the files zImage and adb.exe
http://www.megaupload.com/?d=3NKI5Z0U
This is my system (android 2.2) running Wifi.
Sak_1 said:
I have no permissions to publish to HD Mini ROM Development, published the solution here.
I have the solution to put wifi in Android 2.2 of Schlunds, the problem is in the process "htcUPCTLoader.exe" not allowed to continue with the process.
The assignment of IP must be static, do not get the IP automatically
Here I leave kernel with the new install
TESTED ONLY WITH ANDROID 2.2 Schlunds
Sorry for my bad English
Click to expand...
Click to collapse
Thank you for all you've done! Unfortunately,it didn't work on my mini. (my windows rom is 1.38). Still,thank you!
JAntrobus said:
Codiak, your not alone. I am also not able to turn WiFi on. Do you get Error when you go to the settings to turn it on? It's like its not picking up the WiFi on the mobile.
Click to expand...
Click to collapse
Its the same behavior as the fixed module was not installed.
If you tab Wifi, it just grays out and do nothing. No error message.
See, im on the standard ROM. And no matter what I try, I get the same.
Ok, so it not seem to be WiMo ROM related. I use a custom one.
So my last idea is the bootloader (haret)...
Okay everybody, I noticed something:
I could patch the bcm4329.ko file, after android booted. Now you have to restart android in order to enable wlan. Often it happend to me, that an error in the android wifi settings showed up. So I went back to windows mobile and checked my wifi setting there.
As I've also encountered the GPS problem, where one had to switch GPS on and off again in android to make it work in windows again I also tried it with wlan. Before I run haret, I switched off wlan in windows. Now android was able to initialize and start wlan.
Also it was not possible for me to enable wifi, if the usb cable was still connected to the phone before the first successful operation of wlan. Afterwards it surprisingly also worked with a connected cable. Since I'm at work now, I can not test wlan itself, as it is only possible to connect via DCHP here. This evening I'll try to do so with a static IP.
By the way, this dynamic vs. static IP thing is a common problem in froyo. You'll find a lot of discussions in the internet for other devices like samsung galaxy and so on.
codiak said:
Ok, so it not seem to be WiMo ROM related. I use a custom one.
So my last idea is the bootloader (haret)...
Click to expand...
Click to collapse
i dont think anyone touched haret after cotulla patched it for mini
seppe82 said:
Okay everybody, I noticed something:
I could patch the bcm4329.ko file, after android booted. Now you have to restart android in order to enable wlan. Often it happend to me, that an error in the android wifi settings showed up. So I went back to windows mobile and checked my wifi setting there.
As I've also encountered the GPS problem, where one had to switch GPS on and off again in android to make it work in windows again I also tried it with wlan. Before I run haret, I switched off wlan in windows. Now android was able to initialize and start wlan.
Also it was not possible for me to enable wifi, if the usb cable was still connected to the phone before the first successful operation of wlan. Afterwards it surprisingly also worked with a connected cable. Since I'm at work now, I can not test wlan itself, as it is only possible to connect via DCHP here. This evening I'll try to do so with a static IP.
By the way, this dynamic vs. static IP thing is a common problem in froyo. You'll find a lot of discussions in the internet for other devices like samsung galaxy and so on.
Click to expand...
Click to collapse
It worked, mine no longer displays as error. But I dont have any WiFi's to connect to as im also at work. But it looks much more promising.
Just we need to start looking into getting the battery reconised by Android, having to go into Windows to charge my phone.
seppe82 said:
Okay everybody, I noticed something:
I could patch the bcm4329.ko file, after android booted. Now you have to restart android in order to enable wlan. Often it happend to me, that an error in the android wifi settings showed up. So I went back to windows mobile and checked my wifi setting there.
As I've also encountered the GPS problem, where one had to switch GPS on and off again in android to make it work in windows again I also tried it with wlan. Before I run haret, I switched off wlan in windows. Now android was able to initialize and start wlan.
Also it was not possible for me to enable wifi, if the usb cable was still connected to the phone before the first successful operation of wlan. Afterwards it surprisingly also worked with a connected cable. Since I'm at work now, I can not test wlan itself, as it is only possible to connect via DCHP here. This evening I'll try to do so with a static IP.
By the way, this dynamic vs. static IP thing is a common problem in froyo. You'll find a lot of discussions in the internet for other devices like samsung galaxy and so on.
Click to expand...
Click to collapse
Dont work for me My Wifi in WiMo was allready off. I changed it to on and booted Android = no luck. Rebooted to WiMo and disabled Wifi and booted Android again = no luck.
Did you get a error message before while switchig wifi on in android? I do not get a message. it just grays out
codiak said:
Dont work for me My Wifi in WiMo was allready off. I changed it to on and booted Android = no luck. Rebooted to WiMo and disabled Wifi and booted Android again = no luck.
Did you get a error message before while switchig wifi on in android? I do not get a message. it just grays out
Click to expand...
Click to collapse
Unfortunately there wasn't any precise error message. As you said it only was greyed out with "Fehler" (error) written below the wlan switch. It's strange that there still isn't any solution working for everyone.
For me, no "Fehler" came up. Just grayed out. Same behavior like I never applied the patched module. But i can see the patched .ko file in the phone
I´m using tzacapaca patched ext2 file that works for him...
So, as suggested here, i'll post my question in this thread - it's kinda lost already in here, but maybe some of the users from the thread i am not allowed to post to, will read this...
Using this [15.May.2012] NexusHD2-ICS-4.0.4-CM9-HWA V2.1 (Kernel: tytung_HWA_r2.3-uniMAC) rom, everything's working fine, wlan works, i can use ADB over Wifi to debug,...
now i am developing a app that uses usb-host, therefore i can flash the update from here [26 MAY] USB Host mode for HD2, and now i have to use adb over usb - as the usb-port does not support adb anymore in this mode. but the problem now is - i can enable wlan, i see the networks around, but i can't connect to my wlan anymore - nor any other wlan. once i flash back the backup i made, the phone boots and i can use wlan again... so there's a connection between flashing the usb-host.zip and wlan not working anymore...
so... to any people using this zip on their device - do you have the same problem, or can you still connect to a wlan after applying the usb-host.zip?
ah, nevermind, the usb-host.zip changed the kernel or something else that resulted ni a different wlan-mac-address -> no connection possible.
now it look's like there's no ftdi driver included, but i can not ask for those (already mentioned on page 11 in the usb-host thread) as i am not allowed to post here...
so... can anyone help me out, and copy my post over to the usb-host thread, or if any of the devs are reading this... i'd be very thankful for the mentioned lib_ftdi.so module...
Ive been happy with this configuration and was successfully rooted, however i can no longer join wifi connections on this Config via DHCP only can access my WLAN via a static IP which is no use on other wifi connections out of the house!
i posted my problem here: http://forum.xda-developers.com/galaxy-note-3/help/access-wlan-via-dhcp-connection-using-t3373293
but as yet ive had no replies.
I would like to change to a new configuration to hopefully allow me to use WLAN via DHCP connections once more, its been 2 years since i done any updates so im a little rusty, could someone advise a good ROM to change too? and the roughly the order to do it in, ie: Rom/bootloader/kernel. Ive read that my issue could be Kernel related so i guess i should look to update that.
help would be much appreciated!
Solved installed new ROM all good!